This is just a short post to let everyone know we're still alive. Its been a quiet summer, most people were off on vacation (or on holiday, for our friends across the pond), including many of our own PS3 Devs.
However, the summer is over and we all went back to work in full force on the PS3, adding some new and very talented Devs along the way who will be helping out!
For starters, our very own ggparallel spent the past month or so along with NDT testing countless edited PS3 Firmwares on the PS3, and has been able to drastically refine our knowledge of the PS3's bootup procedure.
Below is a clear flowchart of the current theory of operation, the basic procedure is the same as we previously posted, that the system is booted in a "chain" so to speak. LV0 loads lv1ldr, which loads lv1.self (the Hypervisor).
Then depending on th... More »
As we promised earlier this week, we are going to explain a PS3 game's boot process, as well as explain why the PARAM.SFO is so important.
The Flowchart in the image attached below explains a PS3 game's startup procedure from insertion to its execution.
Most of it is self-explanatory upon viewing the chart, however, there are a few notes. Any Retail SELF on a Blu-ray disc is flagged so it can only be decrypted and executed from the disc, and nowhere else.
Furthermore, the PARAM.SFO is also of importance... Upon insertion, the PS3 reads the Title ID of the disc in the PARAM.SFO and inserts it into the DB. Once the game is executed and decrypted, the Title ID is checked yet again to make sure it matches. If it does not (think a disc swap), the PS3 will silently error, and return to XMB.
In a final note, our PS3 Devs have been digging through numerous documents and patents, and came to the conclusion that the PS3 uses AIX (Advance... More »
(7) 
