View Single Post
Old 08-17-2012   #16
baileyscream
Senior Member
 
baileyscream's Avatar
 
Join Date: Feb 2011
Posts: 1,487
Likes: 531
Liked 1,010 Times in 506 Posts
Mentioned: 486 Post(s)
Tagged: 0 Thread(s)
Originally Posted by haz367 View Post
should u not check for QA flag first, because it was already downgraded? or never above 3.55, the last one u can safely update to kmeaw(rogero+spoof) do it via recovery

if the console was downgraded from 3.56++ and the guy u bought it from only putted rogero3.2(wich is safe for downgrade) on it, u cannot go straight to "kmeaw",rogero 3.4 is save to use as u noticed...
if downgraded! first qaflag it ( http://www.ps3devwiki.com/files/flash/Tools/toggle-qa/) or if already installed/qaflagged, check with the button combo(L1,2,R1,2,d-pad down+L3) all pushed at the same time on settings "network settings"

once it is qa flagged, install OFW3.55 via recovery, then install again ur favorit 355CFW
if the console isn't downgraded..meaning never above 355, forget all of it and just install "kmeaw"
and @ttlgeek

i think your getting at de-hashing via QA flag (shame on you @DEFAULTDNB for missing this "slaps wrists" ;P )
the rogero cfw is the downgrade firmware and although it is a great firmware (it is kmeaw after all just with the downgrade hashes added) but after its de-hashed its usually a different cfw that ppl put on ie rebug / kmeaw (origional one)
its unusual to still have rogero back on after de-hash although nothing wrong with it being on i would personaly de-hash before changing the firmware just to be safe than sorry

Last edited by baileyscream; 08-17-2012 at 06:08 PM.
baileyscream is offline   Reply With Quote
Likes: (2)