RSOD Fix

RSOD Fixing

Observations about RSOD

• Seems to appear mostly on consoles with Samsung NORS (CECHL**-CECH20**)
• May be caused by an error being thrown while writing to NOR (this is theory)
• Mostly caused by a corrupt area of flash called VTRM

The original RSOD "patch" was actually a MFW patch to bypass the RSOD. dev_flash' basic_plugins.sprx was modified to ignore the error condition to allow the console to boot. While this worked, certain things like trophies still didn't work correctly.

The actual RSOD fix occurs by the VTRM area on flash being rewritten. The ability to do this is already built into the firmware, it just needs to be called. See: RSOD Fix lv2diag.self below

RSOD Fix from Linux

 ps3dm_vtrm /dev/ps3dmproxy init

RSOD Fix from GameOS (OLD, no longer used, use lv2diag instead, permabrick risk)

OLD, no longer used - use lv2diag.self RSOD fix instead

1. Install the NORSOD patched PUP so that you can boot REDACTED/do not use
2. Install the rsodfix.gnpdrm.pkg package, and run it from XMB REDACTED/do not use
3. Reboot and install PROPER firmware (without lv2 rsod bandaid blinding "patch")
   
   

  Failure to install a proper firmware will further degrade hardware and corrupt flashregions until system permabricks beyond help.

no man has ever debricked a syscon.

RSOD Fix Factory Service Mode tool (recommended)

This method superceeds all previous (Linux + GameOS) versions, as it is no longer needed to reinstall a firmware or Linux.

RSODfix Lv2diag.self v0.1 - FULL and COMPLETE "Red Screen of Death "Solution

Information: The RSOD is caused by a section of FLASH becoming corrupt, this tool causes that corrupt section to be recreated.

Note: If you have a flasher, and you use this tool... be aware that with the RSOD lv2diag changes cvtrm. If you have a flasher and you use this, you need to make a new image, in fact, its a guarantee that your old flash images are no longer usable. Make new ones! Using an OLD flash image will *CAUSE* RSOD. Additionally, peruser/perconsole information will be reset so old trophies and savedata will not work... but that's a small price to pay for getting your console recovered.

Place this Lv2diag.self in the root of an empty USB flash dongle, and use any method to toggle Factory Service Mode (FSM)

1. Copy the .self in this release to the root of a USB flash drive.
2. Rename the file to Lv2diag.self.
3. Place the flash drive in the right most USB port.
4. Toggle FSM.
5. Boot PS3
6. During FSM boot, the Lv2diag.self will execute.

Upon success, you will hear a single beep, and the playstation3 will automatically reboot to XMB.
Upon failure, you will hear one or more beeps, and the playstation3 will shutdown. If you experience a failure, its likely due to your FLASH being corrupt beyond repair or a hardware problem, try it again-- but if repeated attempts at these easy instructions still yield no results...The outlook looks grim.

Q: I'm having problems... help!!!!?!?!?!?
A: Post the contents of the factory.txt, which is stored on the root of the USB flash drive where you put Lv2Diag.self, along with a detailed explanation and we will try to help you out. Even better, make sure to have dumps from before and after running the fix. The more information we have, the better we might help you.

Q: I tried it successfully but after a few days the RedScreen returns, why?
A: You have damaged hardware. Without replacing the malfunctioning hardware it cannot be solved. You need proper hardware to permanently fix it by the root. After you replaced the badly behaving hardware, run the Lv2diag.self again to make sure the affected flash region is recreated proper.

Differential Flash Analysis

Example of DIFF of a flashdump from a RSOD console and after running the RSOD Fix lv2diag.self: http://pastie.org/private/a7zfbhwz9wfaqr6h45xta

In this specific case, the RSOD returned after a while -> conclusion: hardware failure. Cannot be solved by software alone.