PS3 4.84.1 REBUG REX (w/ Cobra v8.01 + Rebug Toolbox v2.03.01) Released (+ DECR LE version)

ninku · Mar 26, 2019

aldostools said:
sLaunch and VSH Menu are two standalone plugins that are loaded directly from webMAN MOD using pad shortcuts (hold START or SELECT for 5 seconds on XMB to show them). They are always installed by webMAN MOD updater.

They no longer require to be installed in /dev_hdd0/boot_plugins.txt because wMM loads and unloads them dynamically, saving memory resources (because they are loaded only on demand).

Indeed, if they are loaded through /boot_plugin.txt they could cause conflict because 2 instances could be loaded in memory and causing a potential freeze.

Thanks, I put slaunch.sprx plugin in dev_hdd0 and uploaded it by boot_plugin.txt

So I have to delete the command line from boot_plugin.txt and load it by VSH is it?

aldostools · Mar 26, 2019

ninku said:
Thanks, I put slaunch.sprx plugin in dev_hdd0 and uploaded it by boot_plugin.txt

So I have to delete the command line from boot_plugin.txt and load it by VSH is it?

Yes, you have to delete the command line from boot_plugin.txt

webMAN MOD updater install both plugins automatically into /dev_hdd0/tmp/wm_res

If webMAN MOD find them in that folder, they will be loaded using the pad shortcut, which also can be disabled through /setup.ps3.

ninku · Mar 26, 2019

aldostools said:
Yes, you have to delete the command line from boot_plugin.txt

webMAN MOD updater install both plugins automatically into /dev_hdd0/tmp/wm_res

If webMAN MOD find them in that folder, they will be loaded using the pad shortcut, which also can be disabled through /setup.ps3.

Thanks a lot even for the help, just one more question will it always be necessary to activate Slaunch by VSH or will it load automatically when the system starts?

aldostools · Mar 26, 2019

ninku said:
Thanks a lot even for the help, just one more question will it always be necessary to activate Slaunch by VSH or will it load automatically when the system starts?

Only webMAN MOD needs to be listed in /boot_plugins.txt (or from /mamba_plugins.txt if you use MAMBA/PRX Loader)

webMAN MOD will load automatically VSH menu or sLaunch using the pad shortcuts SELECT or START respectively. sLaunch also can be loaded using L2+R2. These shortcuts can be enabled/disabled through http://127.0.0.1/setup.ps3

ninku · Mar 26, 2019

aldostools said:
Only webMAN MOD needs to be listed in /boot_plugins.txt (or from /mamba_plugins.txt if you use MAMBA/PRX Loader)

webMAN MOD will load automatically VSH menu or sLaunch using the pad shortcuts SELECT or START respectively. sLaunch also can be loaded using L2+R2. These shortcuts can be enabled/disabled through http://127.0.0.1/setup.ps3

Thank you, I appreciate your work. I really like Webman.

SiegHart93 · Mar 26, 2019

hi ! i have a question , does this rebug rex 4.84.1 have rsod bypass like in cobra ferrox ? because i want to install it but my ps3 is affected by rsod so i really hope this cfw have that option included ! thanks in advance...

Joonie · Mar 26, 2019

SiegHart93 said:
hi ! i have a question , does this rebug rex 4.84.1 have rsod bypass like in cobra ferrox ? because i want to install it but my ps3 is affected by rsod so i really hope this cfw have that option included ! thanks in advance...

The reason why I stopped supporting RSOD bypass since 4.70 is because I wanted to let people find out about their RSOD, because if this is bypassed and you will still have some issues while playing games as you're running your system in degraded state (VTRM corrupted),

I didn't want people to come back and say, "oh after I installed REBUG I get an error while launching games saying trophy something is failed. " (RSOD bypass).

I strongly suggest trying to fix your RSOD while on Ferrox CFW by running RSOD fix pkg released by @haxxxen or downgrade to rogero 3.55 3.7a then run lv2diag.self w/ FSM enabled.

aldostools · Mar 26, 2019

Joonie said:
The reason why I stopped supporting RSOD bypass since 4.70 is because I wanted to let people find out about their RSOD, because if this is bypassed and you will still have some issues while playing games as you're running your system in degraded state (VTRM corrupted),

I didn't want people to come back and say, "oh after I installed REBUG I get an error while launching games saying trophy something is failed. " (RSOD bypass).

I strongly suggest trying to fix your RSOD while on Ferrox CFW by running RSOD fix pkg released by @haxxxen or downgrade to rogero 3.55 3.7a then run lv2diag.self w/ FSM enabled.

Is it possible to bypass RSOD patching LV1/LV2 from an app? Or it is a patch that needs to be applied directly to CoreOS?

My idea is that webman could apply the RSOD patch if certain combo is pressed during the system boot. Allowing the user to install the RSOD fix without having to install another FW.

Joonie · Mar 26, 2019

aldostools said:
Is it possible to bypass RSOD patching LV1/LV2 from an app? Or it is a patch that needs to be applied directly to CoreOS?

My idea is that webman could apply the RSOD patch if certain combo is pressed during the system boot. Allowing the user to install the RSOD fix without having to install another FW.

The patch can get applied to nas_plugin.sprx and perhaps we could implement an opcode from COBRA to apply that however when it's RSOD it's hard to navigate XMB and webMAN also needs to be enabled prior to apply patches.. It'd be the best to use newcore + flag to apply RSOD or noBD patches like MLT did years ago.

aldostools · Mar 26, 2019

Joonie said:
The patch can get applied to nas_plugin.sprx and perhaps we could implement an opcode from COBRA to apply that however when it's RSOD it's hard to navigate XMB and webMAN also needs to be enabled prior to apply patches.. It'd be the best to use newcore + flag to apply RSOD or noBD patches like MLT did years ago.

What do you think of make Cobra apply the patch when database is rebuilt? As Cobra is now enabled by default, it would be a convenient feature.

Rebug Toolbox could be used to toggle on/off the option of RSOD bypass swaping nas_plugin.sprx like you do with other system files.

For instance, if Rebug Toolbox detects that the RSOD was enabled (nas_plugin.sprx was swapped), it could ask the user if he/she wants to turn of fthe RSOD bypass.

Joonie · Mar 26, 2019

aldostools said:
What do you think of make Cobra apply the patch when database is rebuilt? As Cobra is now enabled by default, it would be a convenient feature.

Rebug Toolbox could be used to toggle on/off the option of RSOD bypass swaping nas_plugin.sprx like you do with other system files.

For instance, if Rebug Toolbox detects that the RSOD was enabled (nas_plugin.sprx was swapped), it could ask the user if he/she wants to turn of fthe RSOD bypass.

Adding RSOD bypass to toolbox is not going to do any good when you can't really navigate XMB. Because when you boot to XMB you see Red screen instead of XMB and you won't be able to guess where the homebrew is to run and select options to toggle such things.

hmm now I read it again you were actually suggesting to toggle that patch off. I mean it's not really harmful to add it by default but I just don't want people to run CFW with degraded state, I'd rather have them fix somewhere without the normal CFW.

aldostools · Mar 26, 2019

Joonie said:
hmm now I read it again you were actually suggesting to toggle that patch off. I mean it's not really harmful to add it by default but I just don't want people to run CFW with degraded state, I'd rather have them fix somewhere without the normal CFW.

What I'm suggesting is to allow the RSOD by default as it is now... and apply the patch swapping the nas_plugin.sprx with one already patched when the database is rebuilt (like it does deleting /boot_plugins.txt).

When the user reboots, the RSOD will be bypassed and he can fix the RSOD. That way he/she don't have to reinstall another CFW, do the fix, then reinstall Rebug.

When he/she enter to Rebug Toolbox or even webMAN, could warn the user that the patched nas_plugin.sprx is active and ask to disable it to return to the normal mode that allows RSOD happen.

BTW Rebug already has a RSOD tool in Custom Firmware Tools > Service Tools > Advanced Service Tools.

Joonie · Mar 26, 2019

aldostools said:
What I'm suggesting is to allow the RSOD by default as it is now... and apply the patch swapping the nas_plugin.sprx with one already patched when the database is rebuilt (like it does deleting /boot_plugins.txt).

When the user reboots, the RSOD will be bypassed and he can fix the RSOD. That way he/she don't have to reinstall another CFW, do the fix, then reinstall Rebug.

When he/she enter to Rebug Toolbox or even webMAN, could warn the user that the patched nas_plugin.sprx is active and ask to disable it to return to the normal mode that allows RSOD happen.

ok let's say we added it and the user who has RSOD console doesn't even know if his has the problem and ended up disabling since Toolbox doesn't know how to detect whether the console is broken or not. And they end up disabling then get RSOD, You will need to install the CFW again.

Here's my stance on adding fix for broken consoles

if you add too many fixes then their result will be very misleading and confusing when users reporting issues.

when it comes to problem solving, the first thing we should do is isolation which is why I removed webMAN long time ago.

Things like noBT, noBD, RSOD (VTRM corruption) have multiple symptoms and you will have hard time figuring out when you add them all. My idea is to minimize this since one user's report can scare other people or confuse them unless they are aware of what their issues are.

Unfortunately with my current skills and knowledge there is no perfect way to auto-detect such things to provide.

aldostools · Mar 26, 2019

Joonie said:
ok let's say we added it and the user who has RSOD console doesn't even know if his has the problem and ended up disabling since Toolbox doesn't know how to detect whether the console is broken or not. And they end up disabling then get RSOD, You will need to install the CFW again.

Here's my stance on adding fix for broken consoles

if you add too many fixes then their result will be very misleading and confusing when users reporting issues.

when it comes to problem solving, the first thing we should do is isolation which is why I removed webMAN long time ago.

Things like noBT, noBD, RSOD (VTRM corruption) have multiple symptoms and you will have hard time figuring out when you add them all. My idea is to minimize this since one user's report can scare other people or confuse them unless they are aware of what their issues are.

Unfortunately with my current skills and knowledge there is no perfect way to auto-detect such things to provide.

I think I haven't explained the idea correctly. Here is an scenario:
1- User installs Rebug that comes with Cobra enabled by default.
2- At some time he/she gets a RSOD and can't navigate XMB.
3- Go to recovery and rebuild database
4- Cobra intercepts the action (in the same event where boot_plugins.txt is deleted) and it swaps nas_plugin.sprx with nas_plugin.skip_rsod.
(nas_plugin.skip_rsod now is named as nas_plugin.sprx, and the unpatched one as nas_plugin.original)
5- Now the system reboots and the user is able to bypass RSOD
6- At this point he/she can fix RSOD using the Custom Firmware Tools > Service Tools > RSOD fix
7- If webMAN is running it can tell the user in a popup that RSOD is being bypassed and must be turned off, because the nas_plugin.original file exists.
8- The user goes to Rebug Toolbox and toggle RSOD bypass off and reboots:
(nas_plugin.sprx now is named nas_plugin.skip_rsod, and the unpatched: nas_plugin.sprx)
9- The system is fixed and if RSOD happens again it will be shown. Go to step 3 if it happens.

Joonie · Mar 26, 2019

aldostools said:
I think I haven't explained correctly. Here is an scenario:
1- User installs Rebug that comes with Cobra enabled by default.
2- At some time he gets a RSOD and can't navigate XMB.
3- Go to recovery and rebuild database
4- Cobra intercepts the action and it swaps nas_plugin.sprx with nas_plugin.skip_rsod.
(nas_plugin.skip_rsod now is named nas_plugin.sprx, and the unpatched: nas_plugin.original)
5- Now the system reboots and the user is able to bypass RSOD
6- At this point he can fix RSOD using the Custom Firmware Tools > Service Tools > RSOD fix
7- If webMAN is running it can tells the user RSOD is being bypassed and must be turn it off, because the nas_plugin.original file exists.
8- The user go to Rebug Toolbox and toggle RSOD bypass off:
(nas_plugin.sprx now is named nas_plugin.skip_rsod, and the unpatched: nas_plugin.sprx)

I actually did understand after I re-read again, but wouldn't that be easier to have that patch applied dynamically by cobra? and use a flag to disable or enable? your method (fail-safe to swap nas_plugin back) doesn't work when cobra's off.

aldostools · Mar 26, 2019

Joonie said:
I actually did understand after I re-read again, but wouldn't that be easier to have that patch applied dynamically by cobra? and use a flag to disable or enable? your method (fail-safe to swap nas_plugin back) doesn't work when cobra's off.

If the patch can be applied dynamically, then it's a much easier method. I only proposed the swap file method because Rebug use it a lot for other tasks

You're right it would work only if Cobra is enabled, but now rebug has it enabled by default and most users will keep it enabled. That's much better than not having the option.

CriSisNYC · Mar 27, 2019

STLcardsWS, i didn't know how to come in contact with you so i went on ur account profile and you said to contact you on the forums, but anyways i need help with my playstation if your not too busy

SiegHart93 · Mar 27, 2019

Joonie said:
The reason why I stopped supporting RSOD bypass since 4.70 is because I wanted to let people find out about their RSOD, because if this is bypassed and you will still have some issues while playing games as you're running your system in degraded state (VTRM corrupted),

I didn't want people to come back and say, "oh after I installed REBUG I get an error while launching games saying trophy something is failed. " (RSOD bypass).

I strongly suggest trying to fix your RSOD while on Ferrox CFW by running RSOD fix pkg released by @haxxxen or downgrade to rogero 3.55 3.7a then run lv2diag.self w/ FSM enabled.

Thanks for the answer dude ! but i don't really know if my nor chip is seriously damaged or it can be fixed . i tried the rsod fix pkg and it works at certain points like for 1 day and the other day the rsod comes again with the typical trophy and savegame errors. I tried installing rebug rex and going to FSM to fix the rsod by cfw advanced service tools (rsod fix) but i always get an error with this option. i never tried downgrading to cfw 3.55 because im scared of loosing my data or messing up my ps3. I really need the exact steps of how to fix rsod like you said dude (downgrading to 3.55 and then FSM, etc...). i really want to install rebug rex as my main cfw thanks

Joonie · Mar 27, 2019

SiegHart93 said:
Thanks for the answer dude ! but i don't really know if my nor chip is seriously damaged or it can be fixed . i tried the rsod fix pkg and it works at certain points like for 1 day and the other day the rsod comes again with the typical trophy and savegame errors. I tried installing rebug rex and going to FSM to fix the rsod by cfw advanced service tools (rsod fix) but i always get an error with this option. i never tried downgrading to cfw 3.55 because im scared of loosing my data or messing up my ps3. I really need the exact steps of how to fix rsod like you said dude (downgrading to 3.55 and then FSM, etc...). i really want to install rebug rex as my main cfw thanks

That's most likely HW issue which typically gets fixed after NOR flash replacement.

But you're welcome to try downgrading to 3.55 then use FSM with that lv2diag.self for fixing RSOD. I can upload that self when I get home.

There's a final work around for the trophy issue with RSOD'd console.

You can unlock all trophies with REX so that way it wouldn't bother you about the trophy.

SiegHart93 · Mar 27, 2019

ok dude thank u so much (y) ! it will be really helpful to fix that persistent rsod that are going to explode my head :S

PS3 4.84.1 REBUG REX (w/ Cobra v8.01 + Rebug Toolbox v2.03.01) Released (+ DECR LE version)

ninku

aldostools

ninku

aldostools

ninku

SiegHart93

Joonie

aldostools

Joonie

aldostools

Joonie

aldostools

Joonie

aldostools

Joonie

aldostools

CriSisNYC

SiegHart93

Joonie

SiegHart93

Similar threads

Featured content

Trending content

Latest posts