143w ago - A few days ago Spanish PS3 developer
JaicraB released PS3 USB Custom Firmware Loader v0.2, and today he updated it to version 0.3.
Download:
PS3 USB Custom Firmware Loader v0.3
To quote from his site (linked above), roughly translated:
Here I bring the new version.
Improvements:
• Code optimization.
• Fixed USB port allocation.
• Fixed black screen.
Recommendations:
• Only have a USB MASS STORAGE USB connected to load FIRM LOADER.
• UPDATE NO FIRM while in USB mode LOADER.
Thanks for reporting bugs!
why don't you just update to 3.41?
No, you didnt spoil my joy
I was wrong, and you are wrong
I have hash checked every file, and they are identical. Yes it is a memory dump, a nand flash memory dump, not a RAM memory dump. Nothing changes in the dev_flash, except when you do a fw update.
Here is my theory on how it is possible to make a copy of the dev_flash from almost any fw, old and new.
Can some one with a infectus chip and a JB pleas test this out
First flash the ps3 nand's to fw3.41,then start the ps3 with JB and install
USB Firm loader and FTPserver 1.0, then make a copy of the dev_flash to a usb stick.
Then start the Firm loader, while you are runing the dev_flash from the usb, flash the PS3 nand's to fw 3.50.
Then use FTPserver1.0 to acess the dev_flash0, this should contain the 3.50 fw!?
If this works, and i can't see why not, it could be done with any fw that people with the infectus chip have a made a copy of.
And no, the dev_flash is not locked to one ps3. I have tested.
And it does not contain any personal information.
I have hash ckecked two dev_flash folders, from two differnt ps3's with fw3.41, one Fat (US) and one Slim (EU), and they are identical.
The xRegistry file may also change between the different fw's,like entries for enabeling OtherOS on the old fw's and more 3D settings on the new fw's.
Wrong. Those are dump of a memory of a running system. The current state of it, like connected devices, installed games, opened menus so far may result in slight differences in the dumped memory.