PS4 News on Facebook! PS4 News on Twitter! PS4 News on YouTube! PS4 News RSS Feed!

Home PS4 News - Latest PlayStation 4 and PS3 News

June 21, 2011 // 7:22 pm - Following up on the previous article, today the full PS3 QA Flagging Method has been revealed including the button combo and token alongisde a PS3 QA Tutorial from Slynk.

To quote: A few weeks ago, several steps were revealed in the process of unlocking a special Quality Assurance (QA) mode on your PS3 console. The mode unlocks a special mode, which is typically only meant for official Sony testers.

Unfortunately, the steps revealed were only part of the process. Developers were scrambling to figure out the button combo that unlocked the special QA mode. In addition, developers still needed to figure out what to change in the QA dummy token. These two mysteries prevented developers from unlocking the mode.

Today however, the Quality Assurance mystery comes to an end. An anonymous and reputable source exclusively revealed to us the two remaining steps. The secret button combination that unlocks the hidden QA mode was revealed to us as being L1+L2+L3+R1+R2+dpad down. Furthermore, the anonymous source told us that users need to change byte 48 of the token seed to 0x02.

Combining this new information with the previously released QA information, developers have everything they need to unlock the mode. Please note, this is not to be attempted by beginners. However, with all of the information revealed here, developers will be able to create an application or custom firmware that automates the QA process.

Information courtesy of anonymous source: Change byte 48 of the token seed to 0x02, hash it, encrypt it, write it to eeprom and flag yourself. Button combo is L1+L2+L3+R1+R2+dpad down. Only works on retail firmware.

By byte 48, I mean the 48th byte. Note that in programming the array of the token seed begins with index 0. So the 48th byte would be seed[47];

This info is more than enough to get someone to make an app.

Previously released information regarding QA Mode:

[Register or Login to view code]

*runs away before the lawsuits come flooding in*

HMAC to make the 20 byte digest at the end of the token and erk/iv to decrypt/encrypt it with aes256cbc.

2 more steps to go. Need the button combo and what to change in the dummy token.

Brief Guide on How to QA Flag your PS3:

  • Be on 3.55 OFW (not Kmeaw or Rebug CFW)
  • Move the PS3 cursor/select “Network Setting”
  • Punch the following button combo with your PS3 controller: L2 + L1 + R1 + R2 + L3 + D-pad Down
  • That's it, the “Edy Viewer”, “Debug Settings”, “Install Package” Menu will now appear.

Notes: Install Package is useless and can’t install homebrew at the moment – only signed PKGs (and the first one in root of USB only).

Finally, to quote from squarepusher2: So since this QA thing is worthless anyway - here is the button combo - you need to have the cursor on 'Network Settings' - (it needs to be 3.55 OFW BTW - Rebug won't work - I've already established that) - and do the following button combo - L2 + L1 + R1 + R2 + L3 + D-pad Down.

There's your button combo. 'Edy Viewer' will pop up - Debug Settings will pop up - Install Package will pop up (but it's kinda useless anyway since only retail packages will install, and only the first PKG on the root of the USB stick - yes - seriously). Now you only need to figure out the rest. Yes, this one works - don't worry about it - just go figure out the rest.

BTW - in case some people immediately start trying this out and telling me 'Hey Square - this doesn't bleepin* work' - remember - there are still some pieces of the puzzle missing - the 'community' needs to figure these out. But the button combo is in the bag - don't worry about it anymore, don't go fruitlessly reversing anymore looking for a possible sign of life of this 'button combo' - you've got it. Now figure out the rest.

Full PS3 QA Flagging Method Revealed - Button Combo and Token

Full PS3 QA Flagging Method Revealed - Button Combo and Token

Follow us on Twitter, Facebook and drop by the PS3 Hacks and PS3 CFW forums for the latest PlayStation 3 scene and PS4 Hacks & JailBreak updates with PlayStation 4 homebrew.

#125 - racer0018 - January 13, 2012 // 3:44 am
racer0018's Avatar
It is just funny. I just remember the one thing my grand dad said to me. Money makes the world go around. Meaning if there is money to be made people will release things. Just sit and wait to see what happens. All that I know is that no one would be where we are now if someone didn't take risk and release something.

#124 - elser1 - January 13, 2012 // 3:15 am
elser1's Avatar
i wish dean would come back and make a cfw.. i agree with you though mate.. the scene is more like see what i can do.. as for you LOL kind of deal not nice is it..

#123 - spunkybunny - January 13, 2012 // 2:42 am
spunkybunny's Avatar
Quote Originally Posted by elser1 View Post
i wonder what happened to the gitbrew guys. oh well.. looks like there may not be 370cfw anytime soon.

The way the devs are in the ps3 scene I doubt we will ever see anything above 3.55 cfw.

They keep everything to themselves so I doubt we'll ever see any new CFW unless duplex release something as it looks like they are the only ones keeping the ps3 scene alive.

Deank has gone and so have just about all the other devs that were keeping it alive. when Duplex go thats it, ps3 scene dead.

#122 - moja - September 10, 2011 // 8:35 pm
moja's Avatar
It sounds kinda bitter, like someone leaked their stuff and they're just crossing their arms over it.

#121 - HeyManHRU - September 8, 2011 // 9:07 am
HeyManHRU's Avatar
No one knows what he meant. Maybe he put the exploits on a USB, taped it to a bird and let go of it.

Here is another announcement:

So it looks like we're not going to have a new CFW from Gitbrew any time soon (If at all).

#120 - elser1 - September 2, 2011 // 7:03 am
elser1's Avatar
cheers heyman! so they couldn't do it and gave up? i don't quite get what in the wild means.. LOL

looks like the only people with the 3.6+ cfw are the ones that have the knowledge and skill to make it for themself. i can't really blame people for not releasing it for every man n his dog to use.

#119 - HeyManHRU - September 2, 2011 // 6:39 am
HeyManHRU's Avatar
Here is a direct quote from "Snowydev" on twitter like 4 days ago.

Welp, gitbrews 2 exploits are now in the wild. Have fun with them, since we're not even going to bother.

#118 - elser1 - September 2, 2011 // 6:32 am
elser1's Avatar
i wonder what happened to the gitbrew guys. oh well.. looks like there may not be 370cfw anytime soon.

#117 - Ezio - September 2, 2011 // 5:13 am
Ezio's Avatar
As I imagined, Gitbrew guys have not been able to find the new keys. Expect to see what adrianc can do and if guys interested in the project dualboot (ie No_One and dospiedra) bring us new and exciting information about new keys.

#116 - PS4 News - September 2, 2011 // 3:53 am
PS4 News's Avatar
Here is another Gitbrew update as this is one of the OtherOS++ threads maintained here. To quote:

One of the main goals of the Gitbrew project was to bring back what Sony has disrespectfully removed from the majority of PlayStation 3 owners, OtherOS. We have successfully completed that goal with the release of OtherOS++ and since that time we have carried out a great deal of research resulting in progress unheard of in the "PS3 Scene" since Sony's lawsuits against Graf and Geobot.

OtherOS++ Project is the culmination of work done by Glevand and Gitbrew, building on top of open source work released by Graf.

Linux/BSD has extensive capabilities in the field of research and development making it a powerful tool to peruse and employ the console to its full use. Without Graf, we never would have completed this project. Here is to Graf, thank you for your courage in the fight for Linux.

Gitbrew will suspend work for PS3 related projects until further notice. Individual developers working under Gitbrew will continue work as usual for whatever projects that may be in progress. Gitbrew will continue to host our collection of mirrors, past and current projects as well as individual developer software. IRC server will stay active for otheros discussion and help (#otheros).

This does not mean all development has come to a halt; we have more releases planned for the future on other devices. We will also host an active community for homebrew developers of all systems.

Thanks to everyone in the scene that has contributed to our cause and special thanks to those who realize the information is out there waiting to be found. Our intention has been fulfilled.

Our content is open source and free, do what thou wilt with it.

For further questions, join our IRC. (ssl) #otheros

~dasmoover ~snowy ~glevand ~durandal