Now, seeing as some punkass bitches have decided to bite the big bazooka by installing the Rogero PUP, I've decided to jump onto the Rogero bangwagon, and with that, I've also decided to create a QA/Status Survey thread, whilst basing the layout from the now-departed JLM's CEX-DEX-CEX Info Survey thread, especially when the main news article is getting clogged up with samey questions, and thus it gets harder to track down the installation statuses/issues that people have, so here goes:
Model Number:
CECH-2503B (320GB)
Original Firmware:
3.55OFW
Lowest Possible Firmware:
3.50OFW
Firmware Installed BEFORE the Firmware Upgrade:
3.55CFW KMEAW
Console QA Flag Status:
Enabled since the Rollback Brick Fix/Syscon Hash Reset phase/CEX-DEX conversion period - checked QA Flag status during every firmware change sans the 4.30 update and it was still enabled.
Firmware Before Installation:
3.55CFW KMEAW (CEX)
Firmware After Installation:
4.30CFW RogerO (CEX)
Highest CFW Firmware Used:
4.30CFW RogerO (CEX)
Firmware Changes Made on my PS3:
3.55CFW KMEAW CEX > 4.30CFW RogerO (CEX) (via Recovery Mode (MANUAL METHOD)) > Hybrid 4.25 to 3.55 CFW (CEX) (via XMB) > 3.55CFW RogerO v3.7 (CEX) (via Recovery Mode (MANUAL METHOD) - prompted me to install "firmware with version 4.40 or later" - but continued anyway) > 3.55CFW KMEAW (CEX) (via Recovery Mode (MANUAL METHOD)) > 4.30CFW RogerO (CEX) (via Recovery Mode (MANUAL METHOD) - I've also deleted the ToggleQA, EID RootKey Dumper and MemDump applications now, so I WILL NEED TO REINSTALL TOGGLEQA IF I NEED TO ROLL BACK!)
Additional Installation Actions Taken/Additional Notes:
- I DIDN'T uninstall multiMAN when prompted as I managed to change firmware versions successfully.
- I DIDN'T install the official 3.55 firmware PUP when some of the more paranoid (can't blame them) users did this.
- I was fortunate enough to have ToggleQA installed since the CEX-DEX conversion phase, so I didn't need to install it again at the time, but now that is not the case, so I WILL need to reinstall it later on.
- I also tested the 3.55 rollback method, and I've managed to do this successfully, although I was told to "install firmware version 4.40 or later" - just press the START+SELECT buttons, hold them down, and continue.
- PLEASE NOTE THAT on the non-KMEAW/official firmware PUPs, YOU WILL NOT get a chance to see the EULA in Recovery Mode, SO MAKE SURE YOU HAVE GOT THE RIGHT FIRMWARE PUP TO HAND BEFORE INSTALLING.
Special thanks go to RogerO, DeanK, The Three Musketeers, Andoma, E3 and everyone else who I forgot to mention for resurrecting the scene from a comatose state!
How are you planning to reinstall toggleQA while on 4.30. Are you just going to resign it for 4.xx. The only reason I ask is that I've stayed on Kmeaw, for simplicity, since the beginning, and now that software downgrade is an option I think I might just make the plunge as I can always get back to the magic 3.55 (with toggleQA installed).
Is this the right choice to upgrade since I don't want to keep stockpiling original eboots and it would be easier to replace those now than acquire more over the next few months. From what I've read too this is somewhat the new Kmeaw (just play and no extra steps needed) and just want to be sure since I almost bought TB and also pondered DEX as a new solution.
How are you planning to reinstall toggleQA while on 4.30. Are you just going to resign it for 4.xx. The only reason I ask is that I've stayed on Kmeaw, for simplicity, since the beginning, and now that software downgrade is an option I think I might just make the plunge as I can always get back to the magic 3.55 (with toggleQA installed).
Is this the right choice to upgrade since I don't want to keep stockpiling original eboots and it would be easier to replace those now than acquire more over the next few months. From what I've read too this is somewhat the new Kmeaw (just play and no extra steps needed) and just want to be sure since I almost bought TB and also pondered DEX as a new solution.
I think you can reinstall it, but not run it - the only time when the "encryption keys" aspect of application management come into play is when it is executed if I am right and seeing as I already activated it before, I don't need to run it again (God willing) unless it somehow gets deactivated when uninstalled (I doubt it).
sorry , don't mean to derail your thread but I thought if you already had QA activated, where you can do the combo, that you had to take it off and put it back on to reset the tokens and syscon? that some checks get set back on after a time and acitivities....
so as long as we have the qa token activated , where we can access the extra options via button combo, we don't have to do it again, even if it was put on months ago?
rant;
I hate syscon dehash stuff because I don't understand it, and apparently now adays you got to do it with anything you do with your ps3 other wise you brick. >.<
/rant
sorry , don't mean to derail your thread but I thought if you already had QA activated, where you can do the combo, that you had to take it off and put it back on to reset the tokens and syscon? that some checks get set back on after a time and acitivities....
so as long as we have the qa token activated , where we can access the extra options via button combo, we don't have to do it again, even if it was put on months ago?
rant;
I hate syscon dehash stuff because I don't understand it, and apparently now adays you got to do it with anything you do with your ps3 other wise you brick. >.<
/rant
From my experience, it stays activated throughout the firmware change but I think the only time when it gets deactivated is when you re-execute ToggleQA or install the Reset QA Flag application and execute it.
hey gDrive,
If people only would list things this way with "Bricks" things would be much clearer for dev's
i've noticed some info about the toggle_qa setting.....think we're going a bit "QA" overdrive these days lol j/k
It is required coming from 4.xx Hardware Flashing" then the first thing a user must do is perform the "Dehash" via toggle_qa+2xOFW355-Recovery or if you prefer FSM, it's the same--> 2xOFW355 to dehash the PS3, now if you do this the QA route, this app is ment to run only once after setting the "flag" in eeprom? syscon, beeps 3 times and reboots, then REMOVE the installer! as long you don't run "reset toggle" aka removing the toggle and its Debug settings below Network Settings, just check it after "SoftwareDowngrade" with button COMBO, Edy viewer etc..? then the flag is set and DEHASHED already
for 2xOFW3.55 FSM mode dehashing, i think its another story? when a user on a FSM dehashed PS3 updates to "any" ++356 again, ofw/cfw and goes back to 3.55, either hardware/OFW or the software/425to355 rogero pup/CFW, then the user must DEHASH the system again, or just install toggle_qa and be dome with it
not with the toggle_qa way! as long the token is set>>> button combo check, show? all good
if the qa toggle is setNEVER RUN the installer on the system, only if you remove it using the pkg for it
and, while on Rogero/E3 CFW 421/430 and "the toggle enabled", it's normal you don't see it on 4.xx, software downgrade back and check the settings again
DO NOT install the pkg and/or resigned for now!, it isn't required and maybe another brick story
if i'm putting you on the wrong track about this, someone please correct the info, anyhow i've tested the same as you guys and once qa is set and not removed, its wasting time installing the extra OFW355 each time, once again using the FSM route or a user on OFW355/never on ++356 and decide to update should just set the "qa token" and be done with it, if you later on goto OFW on it then remove/reset the toggle, clean everything up/format etc.. and you're good2go again
happy toggle j/k haha
Originally Posted by gDrive
Additional Installation Actions Taken/Additional Notes:
- I DIDN'T uninstall multiMAN when prompted as I managed to change firmware versions successfully.
- I DIDN'T install the official 3.55 firmware PUP when some of the more paranoid (can't blame them) users did this.
- I was fortunate enough to have ToggleQA installed since the CEX-DEX conversion phase, so I didn't need to install it again at the time, but now that is not the case, so I WILL need to reinstall it later on
Reply With Quote
Originally Posted by eXcaliber
