[halogamer2145]

I have a CHECHL01 Ps3 that was on 3.55 kmeaw. Whenever I booted a game, it would always give me a trophy error. I thought there was something wrong with the CFW, so I downloaded REBUG 3.55.2 and went into recovery mode and installed it. During the installation it got to around 50% and then jumped to 100%. After this it rebooted and gave me RSOD. I looked up how to fix it and found out that reinstalling the firmware from service mode would do it. But no matter what firmware I try, it goes to 50% and then jumps to 100% and gives me the RSOD. I have tried 3.55 OFW and REBUG 3.55.2. I can't get to XMB, but I can get into Recovery. Can someone please help?

[Bigbones87]

@halogamer2145 There are two ways to try and fix this. The most recommended is to put the system into fsm and then use the rsod lvl2.diag fix to exit fsm. As the ps3 boots with the rsod lvl2.diag, it will make the system rewrite the cvtrm which is we're the rsod comes from, and then it will reset the console and exit fsm. It should boot up normal, if it doesn't then there will be a log file on the USB. The other way is install norsod.pup which bypasses the rsod long enough to install the rsodfix.pkg . Then you run the .pkg and it should restart, then you go back to 3.55 ofw and then to whatever cfw you want. Good luck.
************* [ - Post Merged - ] *************
You can read about both ways on ps3devwiki under rsod

[gangs_08]

...... .

[Bigbones87]

By the way, I have 3 chechL01 consoles and they all got rsod. Those consoles are notorious for the rsod because it is cause by a bad sector on the ps3 nor chip. This was the first console where they started using Samsung nors on the ps3 and they didn't get the bugs worked out till later.

[halogamer2145]

Thank you all for the replies! I was wondering if there was anyway to make a FSM dongle with HP Touchpad running android. I was only able to find ones for other phones. Why did I get RSOD after installing REBUG 3.55.2? Does this mean there is a hardware problem or was it just a one time thing?

[Bigbones87]

no one can say for sure. if you dont have a way to get into fsm, then install the norsod.pup from recovery menu. Then install the rsod fix.pkg and run it. it will beep and then restart the system. after it comes back up then install the 3.55 ofw and then go back to whatever firmware you want.

[halogamer2145]

I have read that the method with the PUP has a high risk for Perma-brick. I am just going to get into FSM with PSP and will post back the results.

[Bigbones87]

i dont think it is. probably one person reported it bricking his console and then everyone avoided it. I have done it on 3 consoles with no problem. It is your call. They both make the system rewrite the cvtrm. i was only telling you to do the norsod.pup as a last resort

[halogamer2145]

I tried the Lv2.diag method. It got into service mode and was successful. Here is the log:

+============================+
|                            |
|    RSODfix lv2diag tool    |
|                            |
+============================+
trm initialize starting ...
trm initialize finished ...
product mode disable starting ...
SUCCESS: read EPROM
SUCCESS: wrote to EPROM
SUCCESS: read EPROM
product mode disable finished ...
SUCCESS: rebooting ...

When I booted the ps3 after this, it was still RSOD. What should I do now?

[Bigbones87]

Try it again. If after a couple times it still fails to fix the rsod, the outcome looks grim. You could always try to change firmware to ofw 3.55 to see if that fixes it, or the norsod.pup would be the last thing. Try the Norsod.pup as a very last resort since you are worried about it. If it the console si useless and it bricks a useless console then who cares.