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)
 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.
Requirement: Console must be on 3.15 - 3.55 with peek/poke like the previous 'FactoryServiceMode Tool v0.2 - The Non-Dongle Factory/Service Mode 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 means to toggle Factory Service Mode (FSM) (ofcourse with RSOD console your options will be limited) (and no, FSM is not Recovery_Menu)
- Copy the .self in this release to the root of a USB flash drive.
- Rename the file to Lv2diag.self.
- Place the flash drive in the right most USB port.
- Toggle FSM.
- Boot PS3
- 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 rsodfix.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
In this specific case, the RSOD returned after a while -> conclusion: hardware failure. Cannot be solved by software alone.