June 23, 2008 // 10:31 pm
- A lot has gone on, and nothing has gone on lately. Let's start with the nothing part first since it's shorter... we really have no monumental progress to report at the moment. Why? Simple, everything the resident PS3 Devs are working on is still a work-in-progress... when there is news we will post it.
So what is the "a lot" part that has gone on lately? Mostly stuff that may eventually lead to newsworthy progress. I myself have recently acquired nearly 1GB of new Sony goodies to play with, and I have been spending much of my freetime examining a lot of the included documentation.
One interesting thing we recently found out is that Sony has released a NEW model PS3 TEST. It is the DECHJ00J/DECHJ00A. It is supported in SDK version 2.17 and later, and features a 40GB Hard Disk Drive, and two USB ports. Like its retail counterpart, it also lacks PS2 hardware, so it can not play PS2 games.
I've also been working with another PS3 Dev on getting ProDG running with TargetManager on my Debug PS3. Up until now, we have been stuck with a neutered version and unfortunately the PS3 ProDG is unlike the old PS2 version, where you can just bypass the License Check and Program Terminate, or use the defunct ZENiTH generator.
Instead, ProDG for PS3 is similar to the PSP version utilizing a client license manager and license text file (ie snl2000.txt), and contrary to popular belief it not only supports PS3 Development TOOLS (ie DECR-1000) but also Debugging Stations (ie DECHA00A) when flashed with v1.8.0 or newer. Needless to say, we finally did it... so that is a minor milestone for us.
Now that you know what I've been busy with, here is a brief rundown of what a few of the other PS3 Devs are currently working on:
is currently awaiting delivery from flurix
of a PS3 stuck in Factory/Service Mode
(see picture below) with which he plans to dump the PS3's NAND Flashes... then we can begin work on unpacking and examining the flash in hopes of learning more about how to access that mode from within retail PS3 consoles. In doing so, we may be able to force other PS3's into service mode, and with time reflash the units as well.
is still working on swapping Flash Dumps between PS3 consoles. This isn't for the faint-hearted, as just recently his friend gave him a bricked 2.10 JAP console which was upgraded to 2.17... but the friend never dumped 2.17. The goal here is if NDT
can successfully swap PS3 Flash Dumps, then he can work on replicating the task for Debug Firmware to Retail consoles which has been his ongoing project. He is also working on comparing and examining the PS3 Flash Dump
requests which were filled by ahmet16
has been working on reversing the PS3's BD-EMU structure. It is similiar to an ISO file, but different at the same time. He is also working on gaining more understanding on the PS3's per disc crypt, as well as the disc hash that is stored on development discs. If he succeeds, we should be able to complete a non-(c) utility that will decrypt the disc layer of encryption on development discs, and retail discs if we are lucky! Furthermore we should be able to modify BRDGen
to properly master BD-EMU images, for those that want to use it with a TEST, but do not have the proper software.
Finally, in regards to the title of this Site News update... we received word from a little birdie @ Sony just a day or so after PS3 Firmware 2.36 Update's release that it indeed plugs a Web browser hole.
According to the source's documentation, this hole is present in PS3 Firmware up to 2.36. We are awaiting further details from our contact regarding specifics of the Web browser hole to determine how 'useful' it may or may not be, but until then unless you have a reason to update it may be best to remain on PS3 Firmware 2.35 just to be on the safe side.
for us today that Sony has blocked XVISTAMAN2005
's Install Debug Firmware on a Retail PS3 system
method in PS3 Firmware 2.36 for those curious. That's it for now!