Has anyone figured out what firmware this works up to?
< or = 3.55
I tried it on a cechp01 fat and it worked just fine, after installation of the cfw, rsod shows again.
PS3 RSODFix Lv2Diag.self Red Screen of Death Tool is Released
Following up on the previous PS3 RSOD Fix comes an RSODFix Lv2Diag.self version 0.1 solution from homebrew developer CrashSerious for those experiencing the dreaded PlayStation 3 Red Screen of Death.
Download: PS3 RSODFix Lv2Diag.self v0.1
To quote: RSODfix Lv2diag tool
Last week someone found the *Proof of Concept* (POC) PUP/app in the wiki, awesome-- people are looking in the wiki! But the dev who put it there, did so as a POC and hadn't intended for it to be released yet because it required you to be able to install a pkg and run apps... something you couldn't do necessarily if you were RSOD. Now, we present you with the FULL and COMPLETE solution!
Now, Fixing the Red Screen Of Death (RSOD) could not be any easier with this new tool! There have been methods in the past that accomplished the same goal, but certainly the difficulty of use hindered many from successfully recovering their beloved console. As a further commitment to you never needing a dongle again, we bring you this release to work in conjunction with our second release. "Look ma, no dongle!"
Place this Lv2diag.self in the root of an empty USB flash dongle, and use any method to toggle Factory Service Mode (FSM) (We're partial to the second release we make today, but you can decide for yourself).
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 PlayStation 3 will automatically reboot to XMB. Upon failure, you will hear one or more beeps, and the PlayStation 3 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.
The RSOD is caused by a section of FLASH becoming corrupt, this tool causes that corrupt section to be recreated. During creation of this tool, the open-source ps3toolchain, and a slightly modified make_self were utilized. All code is original and makes use of no previously released or copyrighted code, this Lv2diag.self is made 100% with the PSL1GHT SDK so it can be shared freely and without concern for breaking any laws in your country. So, "no sony code inside!"
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.
Q: Why two releases?
A: Because they can be used independently and future plans are for more specific Lv2Diag.self's to do different tasks to be released. We didn't want there to be any confusion over what files to put together and how to use the separate tools.
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. Without the contents of the factory.txt file... we will not be able to help.
Q: Why didn't you just name the release .self file Lv2diag.self and save us a step?
A: We intend to release more fun tools for you at some point, this just helps you keep them
straight from the start.
More PlayStation 3 News...
I dont have anything to test this on. It is good to see something like this out.
doesn't work on mine
i got 1 beep. the ps3 reboot but still rsod
If you're on rsod status, and your console is no more than 3.55, you need a dongle preprogrammed for downgrade, using the old well know method. As always was. That's why i ask again the purpose of this tool.