well i know why you want the QA flagging and honestly its quite useless now... as of 3.60 any previously qa flagged console acts "non-flagged" this is because of the fact that the qa keys have changed.
And likely will keep changing in future FWs. Similar to what they do with kernel function NIDs on the PSP.
idk if that would be the case unless 3.60 actually has its keys pwned... honestly they could do a few things like get rid of QA flagging all around or even make it so devkits dont share any retail keys etc... point is even when flagged the only use is being able to run retail selfs now. MGMT and all those other bonuses are all useless due to ip filter.
The only reason why I want to qa flag my ps3 is the fact that I can downgrade from 3.55 to 3.15 or other fw and the restrictions which gets removed.
Correct me if I'm wrong, but from what I read about the QA-flagging recently, the initial stages of the process are known to more than a few people, but the critical button combination required to open up the system is still a mystery. Here's hoping someone decides to share their knowledge, or a lucky individual stumbles across the combination!
http://psx-scene.com/forums/f149/qa-flags-discussion-86504/ I've been watching this very closely. It's close.
I dont think it is that close. Sure we can hash/decrypt/encrypt tokens now. But we still have no idea what flags to set within the token itself.
I was talking with a Dev this morning and he agrees with you, he thinks that they'll never figure it out, and even if they do it's going to be useless on a retail console anyway.
i know this question is noobish but isn't there hidden docs of QA flag type instructions of this? just curious sorry if this was questioned before
