157w ago - A few weeks back we saw a video of PS Downgrade in action, and today ANTONIOPS at Spanish site Elotrolado.net (linked above) has posted up some videos showing PS3 Debug Firmware v2.15 being installed via PSDowngrade on a 40GB Retail version 3.41 console followed by running a PS Store demo.
Normally PlayStation 3 service boxes require a proper downgrade PUP file, however, comparing the SHA1 hash of the released PUP confirms it contains nothing special (just the old 3.41) so there appears to be something 'interesting' taking place when downgrading via PS Downgrade.
To quote, roughly translated: The noise you hear when you turn on the PS3 is the reader who is half repaired.
The Debug firmware I've installed the firmware downgrade PSDowngrade 3.41 to 2.15 Debug.
At the moment can only run signed code, such as a PS Store demo.
Those interested can check out the videos below!
Finally, in related news comes a brief guide from gliitch on installing PS3 Debug Firmware v1.0 on a Retail Console:
Put your PS3 into service mode, then once its powered down, plug in your usb stick with the files. it takes about 4 or so minutes to complete.
Wait for it to finish, and then turn the PS3 back on O_0 and vollia! 1.0 Debug on a retail PS3. Now, there isn't much point in doing this as it doesn't really have anything on it.
You can update straight back to FW 3.41 via usb by [RoOT] PS3/UPDAT.PUP/
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
Ahhh no my friend, doesn't work. Would be to easy and if peoples say it works then they lying. We already have successfully dumped the dev_flash of debug 3.41 fw and also have done some tests. Simply replacing the rco's doesn't lead into full debug fw and even the damn debug options still doesn't work.
I have an idea since it has been confirmed to be working by others.
Well first of all we need a new .hex which will make the jailbreak work with 2.15debug then we would require someone with an actual debug to get us some of the .rco files which needs replacing. When we have both we could just run the debug with the real .rcos on with firmware loader until someones finds a way to replace dev_flash files and it should function normally.
if my idea was stupid please excuse me was just thinking outside the box.