webMAN MOD

PS3 webMAN MOD - General Information Thread 1.47.48q

After updating webman mod i can't see the memory in use while using select + start in xmb menu
Check your activated combos in wMM setup menu. Maybe it de-selected itself for some reason. Also, I think that I once got the full version of wMM after checking for an update with the Standard edition (not sure), so maybe check if you still have the same edition.
 
After updating webman mod i can't see the memory in use while using select + start in xmb menu

It seems like you changed your font. Try using the standard font rounded or pop or select a smaller font.
You can try selecting the "Custom" language in /setup.ps3 which has some labels that fit better in the notification informartion when large fonts are used.
 
@aldostools The above issue might be related to the npsignin_plugin.rco. Not sure. If it is there might be a fix, I would need to do some tests with that game.

@Fabio2598 could you try rename the /dev_hdd0/tmp/wm_res/npsignin_plugin.rco to something else. Then reboot and try the Tiger Woods game again.

@DeViL303 I think I found the "freeze" issue when npsignin_plugin.rco is blocked.

If you start a game (in my case GT5) with a PS3 user that doesn't have a PSN account, when the game shows the Sign In to PSN the screen is dimmed and the user cannot cancel to continue playing the game. Pressing PS to show the ingame-XMB shows the "do not enter" icon. The PS menu allows to quit the game.
 
It seems like you changed your font. Try using the standard font rounded or pop or select a smaller font.
You can try selecting the "Custom" language in /setup.ps3 which has some labels that fit better in the notification informartion when large fonts are used.

I am using "pop" and my language it's spanish but this also happen when i am into a game when the font it's standard, webman mod changed "Almacenamiento" (storage) to "Almacenamiento del sistema" in this new version, maybe that it's the problem
 
I am using "pop" and my language it's spanish but this also happen when i am into a game when the font it's standard, webman mod changed "Almacenamiento" (storage) to "Almacenamiento del sistema" in this new version, maybe that it's the problem

Yes. That string is too long. I have changed the label to "Almacenamiento" and it shows fine.

Download the latest build from github, brewology or use the XMB online updater to get the fix.

Or use the attached file to replace /dev_hdd0/tmp/wm_lang/LANG_ES.TXT
 

Attachments

I think the problem is that you don't have PS3MAPI enabled in /setup.ps3 in the area for the shortcuts.
View attachment 33911

The function that creates the CFW syscalls again is a PS3MAPI opcode, that is accessed through syscall 8.
If PS3MAPI is Disabled the syscall 8 is fully disabled when you press R2+△.
Without syscall 8 the syscall can't be re-enabled unless you enter to the System Update screen via XMB.

When you enter to System Update screen, the /dev_flash/vsh/module/software_update_plugin.sprx is accessed and that triggers the function restore_syscalls() in Cobra when all the CFW syscalls are disabled and allow_restore_sc is enabled..

When PS3MAPI is Enabled, the syscall 8 is partially disabled (it simulates a fake disable) and the disabled CFW Syscalls can be restored.
View attachment 33912

The problem is that @Evilnat implemented the Create Syscalls in xai_plugin using the PS3MAPI opcode instead of enable allow_restore_sc temporarily and accessing /dev_flash/vsh/module/software_update_plugin.sprx
View attachment 33913

Yeah, you got it. After enabling the PS3MAPI there, all the Cobra features are working, including a "Create Syscalls" option. But even after disabling the syscalls, the syscall 8 setting is set to "Fully enabled" all the time.
 
Yeah, you got it. After enabling the PS3MAPI there, all the Cobra features are working, including a "Create Syscalls" option. But even after disabling the syscalls, the syscall 8 setting is set to "Fully enabled" all the time.

When syscalls are disabled, webMAN MOD cannot detect the current status (which is obtained through a PS3MAPI opcode using syscall 8), therefore it selects "Fully enabled" to let the user just press the button to restore the syscalls. :D
 
@aldostools
I had a weird issue with Webman Mod today, I tried to load Tiger Woods PGA Tour 14 and after I pressed start the screen went black and it just froze there. I tried to load it with MultiMan and after I pressed start it showed me the "You need to sign in to PSN to use online features" dimmed screen and then it allowed me to skip that and go onto the game.

I assumed the issue was with the PSN screen so I tried to use the setting to go offline when a game is loaded on webman settings but that didn't seem to work either. Is there any setting I'm overlooking that would make this work or is it a bug with WebMan itself? Thanks

@Fabio2598 @Lwiz A new update of webMAN MOD 1.47.36 is available on Github / Brewology / XMB online updater.
https://github.com/aldostools/webMAN-MOD/releases
https://store.brewology.com/ahomebrew.php?brewid=310

The package includes a new version of npsignin_plugin.rco by @DeViL303 that fixes the freeze issue reported in Tiger Woods PGA Tour 14 and many other games that try access PSN when the syscalls are still enabled and the current user doesn't have a PSN account.

Big thanks to @DeViL303 for this security patch and the fix.
 
@Fabio2598 @Lwiz A new update of webMAN MOD 1.47.36 is available on Github / Brewology / XMB online updater.
https://github.com/aldostools/webMAN-MOD/releases
https://store.brewology.com/ahomebrew.php?brewid=310

The package includes a new version of npsignin_plugin.rco by @DeViL303 that fixes the freeze issue reported in Tiger Woods PGA Tour 14 and many other games that try access PSN when the syscalls are still enabled and the current user doesn't have a PSN account.

Big thanks to @DeViL303 for this security patch and the fix.
I'll test it in the next few days and report back, thank you for the extremely quick bugfix
 
When syscalls are disabled, webMAN MOD cannot detect the current status (which is obtained through a PS3MAPI opcode using syscall 8), therefore it selects "Fully enabled" to let the user just press the button to restore the syscalls. :D

From the safety point of view, is there any difference between restoring the syscalls using the PS3MAPI or through the System Update screen (either method more prone to be detected by Sony)?
 
From the safety point of view, is there any difference between restoring the syscalls using the PS3MAPI or through the System Update screen (either method more prone to be detected by Sony)?

From the safety point of view, both methods of restoring the syscalls are *UNSAFE* if the user enable them still connected to PSN.

The syscalls must be re-enabled after logoff from PSN. Or just do a reboot.

From a technical point of view, both methods call the same function that creates the CFW syscalls in Cobra payload.

The difference is:
* PS3MAPI requires that the syscall8 be enabled or *partially disabled*. If the syscall is fully disabled, the PS3MAPI method will not work. If syscall8 is partially disabled, it must be fully re-enabled then call the opcode.

* The method of entering to the System Update (then exit) does not require any syscall enabled, because the function that creates the CFW syscalls is triggered by a hook in the function open_path; when the file "/dev_flash/vsh/module/software_update_plugin.sprx" is accessed.
 
1) @aldostools Would it be possible to add a toggle somewhere when entering on System Update so the PSN is forced to log off and then the syscalls are restored? Just in case.
2) I didn't update my CFW to 4.88 yet, still in Evilnat 4.87, is this restore syscalls feature only available in Evilnat CFW or is it only related to wMM?
 
1) @aldostools Would it be possible to add a toggle somewhere when entering on System Update so the PSN is forced to log off and then the syscalls are restored? Just in case.
2) I didn't update my CFW to 4.88 yet, still in Evilnat 4.87, is this restore syscalls feature only available in Evilnat CFW or is it only related to wMM?

think enabling syscalls is part of cobra 8.3. it's mentioned in the cobra section of the evilnat 4.88 thread.
 
1) @aldostools Would it be possible to add a toggle somewhere when entering on System Update so the PSN is forced to log off and then the syscalls are restored? Just in case.
2) I didn't update my CFW to 4.88 yet, still in Evilnat 4.87, is this restore syscalls feature only available in Evilnat CFW or is it only related to wMM?

1- The toggle to allow re-enable the CFW syscalls when entering to System Update already exists in CFW Tools menu of Evilnat 4.88, and it is turned off by default. The user must enable the feature to use that new function.
2- The restore syscalls is a feature of Cobra 8.3. Therefore only available in Evilnat 4.88 (or the unofficial Rebug 4.84.2 with Cobra 8.3)
 
1- The toggle to allow re-enable the CFW syscalls when entering to System Update already exists in CFW Tools menu of Evilnat 4.88, and it is turned off by default. The user must enable the feature to use that new function.
Probably you misunderstood what I wanted to say. My bad!
This feature if enabled you wrote above that
From the safety point of view, both methods of restoring the syscalls are *UNSAFE* if the user enable them still connected to PSN.
What I wanted to say is if you added a second toggle that would make this feature noob-proof: When entering into System Update it would DISABLE PSN (loggin you off) before restoring syscalls... would it be possible to do that? That way it will be always safe to restore syscalls because it will force you to logoff / block psn before restoring syscalls.

Anyway if possible, as you told it is a feature of Cobra 8.3, the Cobra would need to be updated on @Evilnat CFW to have this feature and not on wMM.
 
Do we have to treat every user as an idiot? It is a disabled feature by default after all.
i would prefer it to be disabled by default. i don't play online but i would be concerned about accidently reenabling syscalls if i did. because it might lead to accidental bans, it really is better being "idiot-proof" for his feature.
 
Back
Top