Install Debug Firmware on a Retail PS3 system

[DarkSora17]

Sorry for the stupid question... But because there are non-functioning debug options, does that mean that unsigned code cannot be installed, implying that CJPC's backup launcher won't work? Thanks in advanced.

[evilsperm]

so for the most part all this debug firmware is doing to a retail console is just putting in menu options (non functioning) and killing some of the retail support options. So as far as it sits its nice to be able to be able to get the debug FW on the console but until there is a way to make it set into actual debug mode its useless.

Has anyone tried to downgrade the PS3 with this swap method? I have mine at 1.10 still, so I don't know if it says you have a higher firmware and errors out.

[adrianc1982]

Originally Posted by DarkSora17 Sorry for the stupid question...But because there are non-functioning debug options, does that mean that unsigned code cannot be installed, implying that CJPC's backup launcher won't work? Thanks in advanced.

Exactly thats why we are in a partial hybrid, devs are now looking into a way to convert to full developer console with infectus modchip or looking at the differences in the firmwares extracted from this "hybrid".

As it stands its worthless other than for educational purposes and to what it could lead with further tweaking.

[xandura]

excellent news, cant wait a package for download is available with a nice readme file so we can unleash the ps3s true power!

really play beyond!

[cyberfix]

Originally Posted by Nivalis If this were the case, someone with 1.10 could take a relatively small drive (say, 10gb or so), format it in ps3, runt he update then pul the drive.. connect it to a pc and use a drive management software to dump a byte for byte image of the drive to file, then people would have a 1.15? or so hdd image they could write to their drives and use...?.

I have been wondering about this similar scenario for months, but have never bought a drive or coordinated with somebody to get the drive image of a lower version firmware.

Basically, format a new drive in the PS3. Take a drive map of the drive. Start the upgrade to a newer firmware, stop it at the point where the last press "OK" message is. Then, take the drive out and do a difference map of the drive to see which section changed. This should be related to where the firmware was unpacked.

Do the same on a lower firmware and dump the changed section. Copy this changed section to the drive that had the update in progress (overwriting the in process updated section of the drive). Insert the drive and press OK to continue. Has anybody tried it this way or does swapping the drives produce the same results because it is always written to the same location?

[PS3 News]

Originally Posted by xandura excellent news, cant wait a package for download is available with a nice readme file so we can unleash the ps3s true power!

Package for what exactly? So far beyond getting non-functional Debug options in a Retail PS3's menu (following the simple instructions in the first post) nothing else has been accomplished thus far.

The PS3 Devs looking into it are trying to 'downgrade' via an Infectus-equipped PS3 console (in case it bricks) now, however, the PS3 won't even take the PUP because it's a lower version... they are trying various ways to spoof the version obviously, but without success yet.

[CJPC]

Originally Posted by cyberfix I have been wondering about this similar scenario for months, but have never bought a drive or coordinated with somebody to get the drive image of a lower version firmware. Basically, format a new drive in the PS3. Take a drive map of the drive. Start the upgrade to a newer firmware, stop it at the point where the last press "OK" message is. Then, take the drive out and do a difference map of the drive to see which section changed. This should be related to where the firmware was unpacked. Do the same on a lower firmware and dump the changed section. Copy this changed section to the drive that had the update in progress (overwriting the in process updated section of the drive). Insert the drive and press OK to continue. Has anybody tried it this way or does swapping the drives produce the same results because it is always written to the same location?

Simply put, no it wont work. Aside that the HDD is encrypted, and that each differs slightly, your talking around 200mb of data added to the HDD upon starting to install the update.

For example if my ps3 has 200mb of AB's, your PS3 will have 200mb of DF's. Yes, it wont be solid characters, but its just an example.

Now, its possible that it could work on the SAME PS3, but you would have to have these dumps before hand to be of any use!

Because of that, its really useless now, back in November 06, it might have been useful, but alas not now!

[maya2006]

did anyone who tried this... tried to reformat the HDD when the ps3 in the debug firmware? ... this might fix the problems of the debug options not working as the PS3 saves some options on HDD.

[flurix]

Originally Posted by maya2006 did anyone who tried this... tried to reformat the HDD when the ps3 in the debug firmware? ... this might fix the problems of the debug options not working as the PS3 saves some options on HDD.

Yes this was tried. Format System Cache as well as Format Hard Disk were tried and both worked, however they didn't change the functionality of the debugging options. Unless you get a kick out of making the PS3 think it has 0KB free or changing the region for movies you can't watch, nothing useful worked. Also, an option was actually missing out of the DEBUG settings, which was HDCP being On/Off. The option should've been present, but wasn't.

[NDT]

Originally Posted by Blanketman Here is a comment made by NDT (A NAND Patcher dev):

For what it worth we tryed on a 2.30 Jap system and it didn't worked anymore.
Latest success was on 2.10 system.