1. Sorry, this was in Part 4.
2. I was having only one issue prior to this -> When I'm trying to install kmeaw 3.55 CFW mentioned in part1 -> And PS3 said something like "existing firmware is already up-to-date. No need to install you idiot ". So I tought my current Rogero 3.55CFW is okay for this tutorial.
3. Don't know it's required or not -> My ps3 was hard-downgraded before.
Have one advice to dumb guys like me -> Please don't mess with you PS3 unless you have 100 bucks in your pocket.
Last edited by delger; 10-19-2012 at 05:06 AMReason: Automerged Doublepost
i've just read through the tutorial at the beginning of this thread, and i've got to say its a pretty full and comprehensive tutorial. I think if i had read this first, i would have probably given up and never tried going to dex.
But really ask yourselves first, is it really all worth it just for the sake of a few games. Cex to Dex is pretty safe but going backwards results in numerous bricks.
Last edited by G Sus; 10-19-2012 at 12:15 PMReason: Automerged Doublepost
When your ps3 was downgraded, you need to make sure it was de-hashed. So then its safe to update to a newer firmware.
Your using Rogero was not good because it has built in spoofer. Rogero has posted about this on his main site for Rogero CFW: tortuga-cove.com/forums/viewtopic.php?f=127&t=525&start=90#p8443
For all owners of PS3 consoles downgraded from 3.55+ using hardware flashers and Rogero_CFW_v3.x
To "Dehash the PS3" (Reset the syscon) and have the PS3 back to normal safer mode like any original ( non Downgraded ) PS3, here are the steps :
1- After completing the downgrade process and having Rogero CFW 3.x up and running, make sure you have the Blu-Ray drive attached or the QA Toggle package won't work.
2- Download the Rebug QA_Toggle package toggle_qa.pkg
3- Put the "toggle_qa.pkg" on USB and Install it on the PS3.
4- 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 one Beep and the PS3 will Restart back to XMB.
5- 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):
You should see Edy Viewer, Debug Settings, and Install Package Files if done correctly.
6- Now that you have QA flag set, Turn Off your PS3 and Turn it back on but into "Recovery Menu"
This Step is very important, it have to be from "Recovery Menu" and not a normal Update from XMB or the PS3 will Brick.
Here is how to access it:
a. Turn off PlayStation 3.
b. Turn it on and keep Holding The power button down; The system will turn on and turn off once again.
c. Once the System has been shutdown, Turn it on again and keep Holding The power button down (you will hear 1 beep first, keep holding) until you hear 2 consecutive beeps
d. When you hear the 2 beeps take finger off power button.
e. You will be prompted to plug in your controller via usb and then hit the PS button
f. The Recovery menu will pop up.
g. Last Option #6 is what you must use "System Update"
Alternatively you can simply use CondorStrike's Updater package to enter Recovery Menu directly from XMB without going through the boot sequences. --> Condor Updater v2.0
7- Now you must have any 3.55 OFW or CFW with original (non Patched) LV1 in your "USB:\PS3\UPDATE\PS3UPDAT.PUP", here's a link to 3.55-Kmeaw --> kmeaw355.PUP
8- Select the last option of the Recovery Menu --> System Update, then when prompted press and hold "Start+Select" for 5 seconds to start the update.
Once finished the PS3 will restart into XMB with the Syscon hashes reset back to 3.55 in both "ros0" and "ros1" and your PS3 is back like any original/non Downgraded PS3 that can use any CEX/DEX Fw without having to worry about disabling LV1 checks.
Now if someone did the downgrade for you, they should have done it. If you did the downgrade yourself, then it can be unbricked. Or get the person who did it to unbrick it. Well you have given good advice above.
Originally Posted by flaviud
how can i remove a spoofer? sorry but i have no idea
Which spoofer are you running. I can't remember the name of the one, but it has its own uninstaller when you run it, by pressing a button sequence.
Last edited by windrider42; 10-20-2012 at 02:30 AMReason: Automerged Doublepost