[Blazar]

Originally Posted by BobbyBangin Looks like your model is good to go. Now the problem seems to be with the fat CECHH models particularly. As always, you're doing this at your own risk. Just follow the instructions here http://www.tortuga-cove.com/forums/v...p?f=127&t=3636

Do I need to go back to 3.55 OFW before updating? Also, I don't remember what firmware was on the console when I bought it (it was 3.55 or less, not sure of the exact firmware version). Does the dehashing only apply if you've went above 3.55? It's possible that I've updated/downgraded between 3.5- firmwares (but never higher than 3.55) but I'm not entirely sure on that point. Thanks!

[BobbyBangin]

Originally Posted by RolandHazoto Yea I've tried direct boot, discless, with a disc, nothing. I did just check QA flag (with button combo) and discovered it is NOT enabled. Depsite making sure it was before upgrading. Should that have maintained through the update or would it not be enabled now? (and because of the error I obviously have no way of re-enabling it) I find this odd that I am the only one with this exact problem and no fix...

Yeah, not really sure what else you can do at this point. I've played 3 games that I know for a fact has had a modified eboot fix and they've all worked with no problems. So far the only bug I've had is MM taking forever to verify game data but that's only been on a couple games and they've all worked. I hope you get it sorted.

[RolandHazoto]

Originally Posted by BobbyBangin Yeah, not really sure what else you can do at this point. I've played 3 games that I know for a fact has had a modified eboot fix and they've all worked with no problems. So far the only bug I've had is MM taking forever to verify game data but that's only been on a couple games and they've all worked. I hope you get it sorted.

lol figures
A friend of mine just told me to stop being unique when I explained this ish to him... lol
Damn it all!
I've copied this issue over to tortuga in hopes that maybe someone there will help, if I don't get it fixed in a few hours I'm reverting back to kmeaw.
I'm hosting some gamers later today and we are gonna want stuff to play

[CMC888]

So far so good, CFW 4.21and MM 4.08 work fine. Of course the system now asks me to update to 4.30. Is there a 4.30 spoofer out yet?

[Simonbuck]

Originally Posted by RolandHazoto Yea I've tried direct boot, discless, with a disc, nothing. I did just check QA flag (with button combo) and discovered it is NOT enabled. Depsite making sure it was before upgrading. Should that have maintained through the update or would it not be enabled now? (and because of the error I obviously have no way of re-enabling it) I find this odd that I am the only one with this exact problem and no fix...

No your not the only one, the exact same thing happened to me yesterday when I went from V1 to V1.09 same error message on 4.21 games, I went back to 3.55 and started again still exactly the same problem.

I reverted back to V1 and everything is working fine again with no errors

I did post this prob pages and pages ago also over on the Cove, I didnt get a response.

Nevermind its all good on V1

[FrogDR]

ok gusy today i update my brother ps3 slim 2504B straight from Kmeaw to Rogero 1.09D from Recovery Menu and everything works great. without QA.

[Mustang_52]

This may be a dumb question but when I try to sign in to psn if wants me to update so of course I say no and exits back to xmb. I take it I won't be able to sign in unless it's spoofed to 4.30?

Sent from my EVO using Tapatalk 2

[sabi]

Originally Posted by RolandHazoto Man no one answered anything for me... Anyway I went to rebuild my database and it got stuck at 0% so I hard powered it off. This caused the file system to corrupt. I restored the file system and then rebuilt the database again. Now the only things that work for me are multiman and my ps1 eboots. Every PSN game and PS3 backup with a modified eboot is giving me 80010017 error. I used to get this error on 3.55 when trying to run a game that needed higher f/w... So is there an easy way to fix my library of games? Or am I going to have to resign each eboot 1 by 1? Update: Wow even DOA5 kicked me out with the same error! (obviously never cracked, should be 4.21 keys as far as I know) Ok so now I'm starting to think something isn't working right...

bro i was getting the samething befor but i got it fix very easy
frist u need to go back on CFW4.21 v1.00 frist


- Downgrading back to 3.55 is always possible using the following steps :
- Download the 4.25 downgrader PUP ---> 4.25 Downgrader mirror ---> 4.25 Downgrader
Size 176MB (184,595,263 bytes) MD5: 49d80e07fc1f5ca1b0840e02e94635db
- Rename the downloaded file to "PS3UPDAT.PUP" and put it on your USB in: "USB\PS3\UPDATE\PS3UPDAT.PUP"
- While on Rogero CFW4.21, go to System Update from XMB and install the 4.25 downgrader CFW.
- After the downgrader CFW installs you'll be on a hybrid CFW3.55 that will still shows ver4.21 from system settings.
- Enable QA flag by following these steps:

1- Download the Rebug QA_Toggle package from here ---> toggle_qa.pkg
2- Put the "toggle_qa.pkg" on USB and Install it on the PS3.
3- Run the "Rebug Toggle QA" from XMB, the screen will go Black and you will see HDD Led activity then if all went fine you will hear 2 or 3 Beeps and the PS3 will Restart back to XMB.
4- If you want to make sure QA flag was set, go to "Network Settings" then apply the following key combo (all at the same time):

L1 + L2 + L3 (press left stick) + R1 + R2 + dpad_down

You should see Edy Viewer, Debug Settings, and Install Package Files if done correctly.

- Now put "Rogero CEX-3.55 CFW V3.7" on your USB in: "USB\PS3\UPDATE\PS3UPDAT.PUP" ---> Rogero CEX-3.55 CFW V3.7.PUP
- Start the PS3 into Recovery Menu and install "Rogero CEX-3.55 CFW V3.7" (from Recovery Menu, this is important)
- Start the PS3 into Recovery Menu and install "Rogero CEX-3.55 CFW V3.7" again for the second time (from Recovery Menu, this is important)
( Installing "Rogero CEX-3.55 CFW V3.7" twice from Recovery will make sure to fill both "ros0/ros1" with ver3.55
to prevent any possible Brick after updating to other CFWs ).
- Once you're back on Rogero CFW3.55 v3.7 Start the PS3 into Recovery Menu and install any OFW/CFW 3.55 or a newer CFW 4.21

Useful Hint: you can simply use CondorStrike's Updater package from XMB to enter Recovery Menu directly from XMB without going through several restart/shutdown sequences. --> Condor Updater v2.0



- Updating from CFW4.21 v1.00 to the CFW4.21 v1.09 should be done using the following steps :
1- Proper Way ( CFW4.21 v1.00 --> CFW3.55 --> CFW4.21 v1.09 )
---- Downgrade back to ver3.55 using the guide above.
---- Once on Rogero CEX3.55 v3.7 you can update again from Recovery Menu into the new CFW4.21 v1.09

[parallx]

Originally Posted by RolandHazoto Yea I've tried direct boot, discless, with a disc, nothing. I did just check QA flag (with button combo) and discovered it is NOT enabled. Depsite making sure it was before upgrading. Should that have maintained through the update or would it not be enabled now? (and because of the error I obviously have no way of re-enabling it) I find this odd that I am the only one with this exact problem and no fix...

You are not the only one with this problem. What you have been describing for a few pages is what I have now as well. I was able to get 1 game working, but nothing else. Patched, unpatched, freshly copied over, no dice. Getting that same error code as you as well.

I went TB 3.55 > OFW 3.55 > Rogero 4.21 1.09

Then installed the new multiman, and now nothing loads except Multiman. Either black screen, shut down, or that error code.

The only thing of note is that my BluRay drive failed a week ago before I did any of these updates. Not sure if it's related or not.

[CMC888]

[QUOTE=Mustang_52;461289]This may be a dumb question but when I try to sign in to psn if wants me to update so of course I say no and exits back to xmb. I take it I won't be able to sign in unless it's spoofed to 4.30?

Ran in to the same problem. Did some research and there r tools to get on psn like LG5tool. Might try later on.