The above video goes away if you are a member and logged in, so log in now!
Fixable or dead? –
Ok. I seem to have totally messed up my PS3. Maybe someone can help? If not, it's my own fault. I'll put it down to experience.
I have an old 60Gb PS3 - CECHG03. A year or 2 ago I upgraded it to KMEAW's 3.55 cfw and was running Multiman with no problem. Over the past few weeks I've been thinking of bringing it up to 4.2.1 using REBUG. Yesterday I decided to go for it after reading up on loads of different forums. I got to 4.2.1 really easily, upgraded Multiman to 2.0 as well but found I couldn't run any games from the external hard drive that I was able to run before. I kept getting the message "game quit: no request event". I thought I'd messed up somewhere so thought I'd use the '999' downgrader to get it back to 3.55. I did that which seemed to work. Then I decided to try the upgrade again. I tried upgrading through the dashboard and through recovery menu, but both times after it had copied to hard drive and tried to install it I'd get the message "the data is corrupted (8002F157)". I even tried reinstalling the official built in firmware thinking this would bring it back to factory status, but it still has the REBUG dashboard and still gives me the 8002F157 error on any fw uprade I try.
Should I just bin it or is there hope for it (and me!) yet?
i think u have to install rebug's 3.55 cfw then dehash and use qa flag then u can go to any fw you want...rebug 999 is just cfw 3.55 spoofed to 999 for downgrading...goto www.rebug.me and read the instructions for downgrading carefully it should be fixable...although i get that game quit msg everytime i select a game in multiman using rebug and it goes to the xmb...then i just select the game disk icon and play (game in drive..don't mater what the game is it will be the one i selected in multiman)
sony throws the first punch at 3.21 with removal of other os....hackers kick back at 3.41...at 3.55 hackers crack the bitch like a $5 whore and she has been bleeding ever since
This is actually expected behavior. All you need to do after that was go to the 'Game' menu and start playing as if you had a legit disc in your system. You should try that.
Originally Posted by andtiggertoo
Thanks for the quick replies. I followed your suggestion wartutor (debug 3.55cfw - qa flag - dehash), now it's back to a virgin 3.55 Guess I just start all over again now with rebug 4.21.1 + multiman.
Thanks again for your really useful and quick replies! I'll let you know if I get stuck again