(adsbygoogle = window.adsbygoogle || []).push({}); Hello all, I've decided to make this tutorial as I've known 6 people that bricked their PS3 due to the 4.11 Rebug Spoofer recently released.

Requirements:
USB with 800 MB free space
3.55 PS3 already

[multipage=The Fast Way]
Another way to fix this mentioned by a slew of people is to restore your system through recovery menu with the original 3.55 update, and then install your custom firmware again. I haven't verified this way, so do this at your own risk.

[multipage=My Way]
Warning: You may have a chance of a perma brick using this method


First of all, you need to download these files:
RSOD Fix.pkg

You must login or register to view this content.


NORSOD patched PUP

You must login or register to view this content.


Now put the .PKG file onto the root of your USB like any other package file.
Once you've done that go to the root of your USB and make this: PS3 > UPDATE
Inside of the UPDATE folder you put the UPDAT.PUP
Go to your PS3 and hold down the power button. It will do a few beeps and then turn off, once it does that hold it down again until you hear 2 beeps in a row. Once you do that you let go of the power button. You're now in Recovery Mode.

From Recovery Mode, you scroll down to the last option: Update. MAKE SURE YOU DON'T HAVE ANY DISCS IN YOUR PS3 WHEN YOU DO THIS. Choose Update, and press select and start at the same time. It should recognize your USB with the update on it etc. Update it with that.

Once the update is finished, install the .PKG file. Then run it from the XMB.

Now, you are completely unbricked/red screened. All you have to do now is get the CFW you want to put back on it, and replace the UPDAT.PUP inside of your USB and update it through media device.

I hope this helped you guys, and if you have any questions feel free to ask. I do not take credit for these files, or the tutorial. I just wanted to share my find with you guys.

[multipage=The Safe Way]
You must login or register to view this content.

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 the download) 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.

If you hear a single beep and your PS3 returns to XMB it was successful (obviously)

If 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.
Method by: PS3 Prodigy

I got the red screen as well.
And installed the official 3.55 update from recovery mode.
Then reinstalled a decent cfw all working now

Multiple people said this works as well, so I'll add it to my tutorial.

---------- Post added at 07:43 PM ---------- Previous post was at 07:39 PM ----------



Ok great. A few things you could do (Most likely means nothing to you) is to install your PSN purchases. If it allows you to, you could start games that aren't bootable on 3.55. Eh. Idk. Good luck with whatever you do.

I had to do this a while back. I just reinstalled the cfw. Isn't it PS3UPDAT.PUP

I hope this is not the case of people installing the wrong spoof .rebug always has 1 for 355.2 & 1 for 355 regular CFW not CEX/DEX & the Rebug 355.2 specially made for Rebugs CFW should never be installed on a normal CFW 355 . The stand alone normal 355 spoof is for that ,since Rebug xmb has both CEX/DEX XMBs. Remember that for the people who have installed the wrong one .I have never had this happen to me & i been using every update .Only time i seen this was for a quick few seconds after uninstalling the spoof on a normal 355 & i restarted/rebooted my PS3 & it was gone..

People should not hot link Rebugs spoofs do to them not wanting people to & also so people can get the proper info/version before they just go ahead & install. rebug is real good about testing there releases before release i think this had to be a result of "impatient" for getting on PSN & user error installing wrong spoof or had a 999 spoofer installed before this that rebug did not make . This is the first i seen about this & i warned people about the 999 spoof for rebug made by a member at ps3news = spoofed only the firmware files which installing rebug update with that spoof or having that spoof installed would result in RSOD or worse he had told me when i asked if he spoofed the firmware files or rebug selector & the rebug selector was not spoofed as this is why the 999 spoof will cause RSOD if installed & set to rebug mode .

This is a warning for those who had wrong spoof or a 999 not made from rebug .Flash back to OFW 355 ,then start clean before using another spoof .

Apparently there is now a way to install this without a 3.55 PS3.
It will be released tomorrow...

I had 3.55.2 and I used the 3.55.2 update and it did it. I downloaded the files directly from Rebug.me. Some people may just be unlucky :cry:

Using that .PUP there is a risk of PERMA BRICK a much safer method to fixing RSOD is:

You must login or register to view this content.

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 the download) 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.

If you hear a single beep and your PS3 returns to XMB it was successful (obviously)

If 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,

Ah, I didn't see this method. Want me to update the thread with this way?

Yeah just add it :happygrin:...and let people know about the risk of using the .PUP method because it still works its just risky.