(adsbygoogle = window.adsbygoogle || []).push({}); Im sorry if this is in the wrong forum but i updated a while back and got stuck in servce mode on 3.56 (stupid mistake) and now i decided to update the the newest 3.56 hoping it would take me out of service mode, but now when it turns on it had a red screen with tons of writing in different languages (including English) that say "a serious error has occurred. Contact tech support for assistance"

Could anyone help me resolve this error? i dont want to have to pay $120 to send to sony for a new ps3 :/

Thanks,
deershoot3r

Put the dongle back in you used to put it in service mode. But that's the only way to get out of it.

so pretty much its only usable in service mode until a downgrader is released?


EDIT: I put in service mode but it still gives me red screen

EDIT: i fixed by changing hard drives but now im still stuck in service mode

I'm guessing your screwed dude if your on 3.56 OFW as there are no signed keys for this firmware yet. On 3.55 you could get out of it with the level 2 self file on a usb on the port closest to the blue ray drive. From why I have searched and read on the forum. I could be wrong lol

Lol that red screen means u just bricked it

Then i have NO good news for you mate

A Red Screen Of Death ( RSOD )
Can't be Fixed

I Repair Allot Of Ps3's for my hobby and had a Few of these
one Customer Gave It to me and bought another @ me for 10% off
so i sold him a new Ps3 and got his old RSOD one

took a few look over it and tried Hdmi cable and AV-cable but nothing worked .

so i decided to try the YLOD fix method

Heat gun @350 degrees and kick its *ss =D
but nothing worked

so i left it for a few days to rest and think about it .
i came up with an idea and soldered my Infectus Mod chip from another Ps3 to the RSOD one

then i can Read out the NAND memory
the Result ?

It Was a corrupt NAND

so it ISNT A BRICKED console ( saw someone saying that ??? )

but its a Bad NAND
if you brick it you get an Black or Yellow Screen Of death with NOTHING on it

so sorry for your loss man

Grtz.MysticalX & Team-Blizzard

actually i did fix it, i learned that if i put it in service mode and switch out the hard drives it works, luckily i had another 80 gig laying around.