[Helix00]

Alright guys let me try and explain what happened. I have a 60gb PS3 with kmeaw 3.55 installed on it. Since there are more and more games that can't be played on 3.55 I decided to upgrade to Rogero 4.30.

I installed Toggle QA and enabled it then I manually entered recover mode, went to system update and installed Rogero 4.30 v2.05. At this point I wasn't paying super close attention but the progress bar was slowly filling and when it finished my ps3 froze on a black screen. I let it sit for about 30mins but nothing was happening. Being frustrated I flipped the hard power switch on the back(probably a mistake).

When I turned the system back on all I get is a solid blue screen with no text. All the system lights are normal and I can eject and insert discs as always. I tried reset the video settings thinking that might be the problem but no luck. Next I tried entering recovery mode but I still get the blue screen. If I plug the controller in and push X the screen switches to solid black and just sits there.

Did I kill my PS3 or is there some way to fix this nightmare?

[BwE]

See if you can get into FSM.

[Helix00]

Originally Posted by BwE See if you can get into FSM.

You need a dongle to enter FSM right? In which case I don't have one, unfortunately.

[Hells Guardian]

I can tell you what happened. just keep tapping X this should reset the config file. you tried to install a firmware too old for this console and it failed right after start. Make sure there was no game in the drive when updating and such m8.

this seems to be the equivalent of the blue screen the PSP gives. meaning a corrupted config file. keep pressing x/o until it does something and you should see it reboot to 3.55 CFW that you were on.

[Helix00]

Originally Posted by Hells Guardian I can tell you what happened. just keep tapping X this should reset the config file. you tried to install a firmware too old for this console and it failed right after start. Make sure there was no game in the drive when updating and such m8. this seems to be the equivalent of the blue screen the PSP gives. meaning a corrupted config file. keep pressing x/o until it does something and you should see it reboot to 3.55 CFW that you were on.

I'm trying your suggestion now but it doesn't seem to be working.

I think I know what I did to brick it, I had an old game in drive when I tried to update and that seems to be what bricked it. It must have tried to install the older firmware from the disc rather than rogero. I might be out of luck.

[Mr.Dutch]

Originally Posted by Helix00 I think I know what I did to brick it, I had an old game in drive when I tried to update and that seems to be what bricked it.

i can't believe that this is true, why would the ps3 install firmware that is older then your current firmware, i have ridge racer in my ps3, never took it out.

i think it will only install firmware from a disc if that one is newer then the one you are installing from usb, and even then it won't brick your ps3.

was your ps3 ever downgraded?, and was the qa toggle installed succesful, did you verified it?

@baileyscream , back me up or burn me down, your choice.

[Hells Guardian]

If you have a console QA flagged and try to install an Update on 3.55 it doesn't matter what version it is.

This happened to me I just kept pressing buttons and eventually it kicked back to XMB.

[baileyscream]

Originally Posted by Mr.Dutch i can't believe that this is true, why would the ps3 install firmware that is older then your current firmware, i have ridge racer in my ps3, never took it out. i think it will only install firmware from a disc if that one is newer then the one you are installing from usb, and even then it won't brick your ps3. was your ps3 ever downgraded?, and was the qa toggle installed succesful, did you verified it? @baileyscream , back me up or burn me down, your choice.

he QA flagged the ps3
this allows lower firmware to be installed.
the first place the ps3 looks for firmware is..............the blueray drive

or it might be a fuse
************* [ - Post Merged - ] *************

Originally Posted by Helix00 I'm trying your suggestion now but it doesn't seem to be working. I think I know what I did to brick it, I had an old game in drive when I tried to update and that seems to be what bricked it. It must have tried to install the older firmware from the disc rather than rogero. I might be out of luck.

now its either the recovery or the fsm that is not on early firmware.
if its fsm then a dongle may not help.
i havent come across this personaly. i have read about it but with no feed back as to how its fixed.
right now @Hells Guardian seems to have solved this in the past so follow his advice
hells does the controller need to be connected via usb? do you remember. i'm just asking as the op seems to be having difficuly getting the "x" button fix to work.
or even a rough idea on a time (ie tap like crazy for 5 min?)

[Hells Guardian]

Probably needs to be linked Via USB I know it was when I had the problem. hold tight I'm going to brick my console and replicate the result.

[Helix00]

You guys are right the controller will only connects via usb. The wireless doesn't work. I let it sit for about an hour tapping X/O every few minutes, no luck so far but I appreciate the suggestion.