158w 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!
We can't get a proper dump until we get to correct offsets to get psgroove to run on this test console. We have tried RichDevX debug payload and it doesn't work at all, and we have come up with every payload under the sun to try to get it to take.
Now we are forced to have to dump elfs through lan and wireshark it to find the correct offsets, then we will be able to make a working payload and finely get a full dump of a debug.
Ok, but you forgot how the ps3 will boot a os to download those fw and install it?
First the hardware starts let us say this is lv0.Then hardware loads lv1,lv2,metldr,ect.ect. and devflash.
The JIG sends response code and gain access over the ps3's RAM.Now the files from usb stick come into the play and the JIG patch normall lv2 from cxd chip loaded to ram with lv2diag from usb stick. Still the console load the files from dev_flash wich will be the visible part of the whole thing.Remember dev_flash holds xregistry.sys among a lot other importend files like rco's,sprx's,xml's and even the vsh.self including a lot of other self's.
I'm not sure if we really can unbrick a fullbricked con only truth jig or software. If we where able to read and write both flash chips cxd and samsung we would be able to unbrick a full bricked ps3.