To quote from his site (linked above), roughly translated:
Here I bring the new version.
• Code optimization.
• Fixed USB port allocation.
• Fixed black screen.
• Only have a USB MASS STORAGE USB connected to load FIRM LOADER.
• UPDATE NO FIRM while in USB mode LOADER.
Thanks for reporting bugs!
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!
I just got my second ps3 to day, EU 320GB Slim. My old one is a US 60GB Fat.
The first thing i did when i got it, was to update the FW from 3.40 to 3.41. Then i installed the FTPserver, and copyed every thing from the new ps3. Then i compared the dev_flash on Fat(US) one with the Slim(EU) one, and guess what...
They are identical in size: 177*360*300 byte, but then i tried to compress them winrar and check the MD5 check sums, but the compressed size did not end up as the same. Then i tried with to zip them with windows. They ended up with the same size, but the MD5 Check sum's where not the same.
So there are some small differences between the US FW and the EU FW.
Then i copied the dev_flash from the Slim one to usb stick and plugged it in to the Fat one, and started the Firm Loader. And it worked.
So in other words, it is possible to run the dev_flash from one ps3, on another ps3. They are not locked to the ps3. As some people claim....
My suggestion is to add a Firm loader function in PSgroove, make it mount the usb as the dev_flash in the memory.
From what i could see while updating to WF 3.41, the ps3 did not restart it self, it just exited the xmb, and started the FW update "OS".
And we will be able to update the FW on the usb mounted dev_flash. My other solution is a litle more drastic, but might work. Hook up the nand to a usb controller, and plug it in to a JBPS3, then use FTPserver to copy the files.
Edit: I just finished hash checking all the files in dev_flash on the US Fat, white the EU Slim one. They are IDENTICAL, all the MD5 checksums match up.
If you did not read what I wrote a few posts up, the infectus will only dump the encrypted raw data, and that's also including the ECC data. So unless someone makes a tool to unencrypt the nand dump then we won't be able to do it. We also need to find a way to get the encryption keys.
From what I can see, right now an infectus dump is totally useless.
I have an infectus and I also have a dead PS3 mobo with the dual nand chips. I can dump them for you guys if you'd like, but I don't think it will do any good at all since they will be encrypted and no one will be able to read whats in them. But I'll still do it anyways.
PM me if you are interested in my doing to for you.
I don't know what the current firmware is on that PS3 mobo, but it's been dead for quite some time so I would assume it's from be 3.0 firmware.... maybe even from around when 2.0 came out.