RSOD - console bricked?

[RoversRob]

To cut a long story short, I went into FSM on kmeaw 3.55 with a view to downgrade to 4.41 then downgrade to 3.15 to remarry a logic board.

Anyhow, I placed my fat 32 USB into the far right port of my console with the 3.41 modified pup and the lvl2diag file and booted up... nothing, the console just went straight to the XMB, still in FSM. Tried again, nothing.

Ive remarried boards before, but never whilst on CFW, so I thought "hey lets put it on 3.55 OFW, Ive never had a problem with that". Just one problem - the jig I use to put my console into FSM is at my mates house, so I didnt want to exit FSM. So me, in all my infinite wisdom, put 3.55CFW onto a dongle and tried to install it whilst still in FSM.

It downloaded onto the console no prob, then switched off, then came back on to install with the "please dont turn off, installing etc etc" message. It didnt get past 0% and then I got the RSOD.

Heres what Ive tried so far:

• Taking the HDD out as soon as I see the installing message. This prevents the RSOD, and just gives me the error message telling me to restart and try again. If I restart with the HDD out, the console just turns itself back off again. If I restart with it in, RSOD comes back.
• Booting the console into recovery mode. Not working, I presume because Im in a deadly RSOD update loop.
• Putting the RSOD lv2diag file onto the dongle and sticking that in on start up. Was hoping this would work, seeing as I was in FSM when all this happened. No joy, though.

I dont have the FSM jig here to see if I could get back to the XMB in FSM again... I wouldnt rate my chances highly with that one though.

So, a couple of things really:

• Why would the console not do the downgrade in the first place when I was in FSM?
• Is there a way out of this that anyone knows about?

Ive got a feeling im fooked here.... waste of a £160 console

[No0bZiLLa]

why are you downgrading you rps3 to remarry ?

just get into fsm and use this...

dev_usb000.rar for 3.55

you dont need to downgrade anymore. just get into FSM and then remarry as usual, but dont downgrade :/

edit: im pretty sure you cant access recovery menu while in FSM, but i could be wrong. i once had a ps3 that was real messed up, it would boot without an hdd even in the ps3. the 3.41 modified file is known to kill ps3's so dont use it anymore, use the mothod i posted above to remarry drive, then once you remarry install qa flag firmware and QA flag that console.

if by chance your still in FSM, put the firmware that was on the ps3 before you tried to upgrade to CFW back on the thumb drive (probly 3.15 OFW) with the downgrade lv2diag.

i kinda need a little more info, did you exit FSM while on the modified 3.41 firmware?

what firmware was on it before you got RSOD? you need to install the firmware that was on the ps3 before you got rsod.

[RoversRob]

why are you downgrading you rps3 to remarry ?

just get into fsm and use this...

""Link I cannot re-quote""

you dont need to downgrade anymore. just get into FSM and then remarry as usual, but dont downgrade :/

edit: im pretty sure you cant access recovery menu while in FSM, but i could be wrong. i once had a ps3 that was real messed up, it would boot without an hdd even in the ps3. the 3.41 modified file is known to kill ps3's so dont use it anymore, use the mothod i posted above to remarry drive, then once you remarry install qa flag firmware and QA flag that console.

if by chance your still in FSM, put the firmware that was on the ps3 before you tried to upgrade to CFW back on the thumb drive (probly 3.15 OFW) with the downgrade lv2diag.

i kinda need a little more info, did you exit FSM while on the modified 3.41 firmware?

what firmware was on it before you got RSOD? you need to install the firmware that was on the ps3 before you got rsod.

Ah bollox, had no idea you could remarry on 3.55 now. Ive no idea what QA Flag is, but I suppose ill cross that bridge if and when I get out of RSOD.

Ok so the firmware history:

I never actually got it onto the modified 3.41 firmware. I started off on 3.15 and took it to my mates to get it into FSM with his psp. The jig wasnt working, so we upgraded to 3.55ofw and then KMEAW 3.55 and installed the FSM app (which of course, didnt work as apps wont boot up without the married drive inside).

It turned out his PSP was on the wrong firmware, so we amended that and put it into FSM (still on kmeaw 3.55 here).

I went home, put the modified 3.41 on a dongle, put it in and started up but it had no effect. No file update as usual when in FSM, just nothing. The console just started up on the XMB again (still in fsm and on kmeaw 3.55). This was when I put OFW 3.55 on the dongle and decided to do a system update via the XMB. This is the RSOD update loop Im now stuck in.

So:

Originally on 3.15ofw
Upgraded to 3.55ofw
Changed to 3.55 kmeaw
Entered FSM
Tried to revert to 3.55ofw on the XMB
RSOD

This is a phat CECHL 80gb btw. It seems that no matter what I put on a thumb drive its having no effect and instead just starting up on this update screen every time. I need to get this PSP and try and boot up in FSM again I think, but Im sceptical about that working.

[mad mike 96]

Kick it into FSM and use the RSOD fix method detailed on the PS3 DEV WIKI. It really does work. Give it a shot and this time have the file with you and ready at your mates to try it before leaving. Assuming you havent damaged the flash beyond repair the RSOD fix file should do the trick. Its really easy I repaired an RSOD just yesterday with this method.

When you fix that you should stay on 3.55 and remarry the drive as planned. pretty sure you wont need to QA flag the system as there is no need to dowqngrade the thing for the remarrying process. Either way it should be reatively easy to fix. best of luck m8.

[RoversRob]

Ok, so got the PSP and tried to boot back up into FSM. The ps3 turns itself off as it should do when you kick it into FSM, but when I turn it back on it just goes back to the same update screen. Any more ideas?

[RoversRob]

no other ideas before I flog it on ebay?

[No0bZiLLa]

put the firmware that was ont he ps3 before it RSOD on a thumb drive along with the lv2diag downgrader self. then put it in the right most usb port and turn it on. then after it installs, take the thub drive out and boot the ps3.

[RoversRob]

put the firmware that was ont he ps3 before it RSOD on a thumb drive along with the lv2diag downgrader self. then put it in the right most usb port and turn it on. then after it installs, take the thub drive out and boot the ps3.

No joy mate . Its just not taking anything from the thumb drive. It basically just boots up to the screen "The previous installation attempt was cancelled. Installing again, do not turn off the console" (or along those lines).

It boots up to that screen no matter what I do. Even when I run the FSM jig, the ps3 turns itself off as if to indicate it is now in FSM but upon turning it back on, it goes back to that installation screen and then RSOD.

[No0bZiLLa]

well, how much are you looking to get for this console? id be willing to buy it for the right price.

also, are you sure your using the correct lv2diag when installing the firmware from the thumb drive?

put this lv2diag and the firmware that was on the ps3 before you rsod. be sure to place the pup and this lv2diag on the root of the thumb drive

lv2diag



and this one you use to exit fsm

exit fsm lv2diag

[pip313]

I say this because you talk a awful lot about changing firmwares and you say you have a non matching bdrom but you don't talk about patching these firmwares to bypass the bdrom which would need to be done.

remove the hard drive and either format it or replace it, use a small one if you have to but you need to make the ps3 not have the update file thats on the hard drive, it wants to install that so you need to force it not to. hopefully you will now have the option to use another pup.

you tell us you used a modified 3.41 pup is it the 3.56 modded one for downgrade and if so did you patch it to not care that your bd rom can't be flashed as it is not married to the ps3? that may be what caused rsod to begin with, an incomplete firmware install

I just un rsod a cechl01 and after 5 tries with the rsodlv2diag.self I tried once with the rsod pup which is now near impossible to find if you don't already have it and it worked. reinstalled kmeaw twice to make sure its fixed and boom good to go. the rsod pup needs a rsod.pkg to be ran to do the actual fix but you have to get a firmware to fully install first (it will boot with rsod and no other cfw will)