Brick Recovery Research

[Mistawes]

So would one dump work for all bricked PS3's then..? If I dumped my nand's, extracted keys etc, pasted them into a generic dump and write it back.. Would that do the trick, instead of getting a 2nd PS3 to work with.

Any chance you could upload your friends YLOD dump djseban? Would be great to try it out.

[djseban]

@Mistawes: Writing my friend's YLOD dump to your console won't work. You must resolder NAND-chip from YLOD-console to your console and then chagne keys to your :P
For clear all things, all the keys, bootloaders or metldr in bricked consoles are good! Metldr can have different sizes, but you can use your Metldr on any other PS3.

Regards

@edit: Lol, I did mistake :P I mean, that you can use metldr on your own PS3 with any NAND dump :P

[defyboy]

@Mistawes: Writing my friend's YLOD dump to your console won't work. You must resolder NAND-chip from YLOD-console to your console and then chagne keys to your :P
For clear all things, all the keys, bootloaders or metldr in bricked consoles are good! Metldr can have different sizes, but you can use your Metldr on any other PS3.

Regards

Incorrect, Metldr and bootldr are encrypted per console and will not work on any other console. All you need to do is rebuild coreos.pkg and flash it to the ros0 region on the bricked console. You do not need to dump another ps3 as you can extract what you need from the firmware update PUP.

The issue here is not bad blocks on NAND, The NAND chips are rated for 10,000,000 erase cycles per block.

[DeadlyFoez]

The issue here is not bad blocks on NAND, The NAND chips are rated for 10,000,000 erase cycles per block.

%90 of NAND chips have bad blocks. They come out of the factory with bad blocks all the time. It is normal. But that does create an issue for flashing files to your nand because if that file lands on a spot where there is a bad block then you have to skip that whole block, which also is listed in the TOC.

[Mistawes]

Thanks for the great info guys!

I've got a brick that sits on GLOD for 60 seconds before shutting off.. It was on OFW 2.30 updating to 3.15 but failed around 40-50% and the owner formatted the HDD to get out of an update loop, but it hasn't got recovery mode and PSGrade isn't making any difference.

So I'm looking to find or build (from a .PUP file) a clean dump to paste everything (keys, bootloader, metloader etc) into so it will hopefully work again. Since this isn't the usual coreos problem, is it actually fixable? It's a CECHG 256mb NAND model..

Thanks!

[fre3PS]

Look here:
K9F1G08U0A datasheet(12/37 Pages) SAMSUNG | 128M x 8 Bit / 256M x 8 Bit NAND Flash Memory

data sheet page 12 how to id initial bad blocks. i am just wondering whether the infectus software id these properly after we wipe the nands, as if we don't then we have to basically have capability where we wipe nand fully, go thru entire nand again and look for invalid blocks, store their locations and then write avoiding these blocks(2nd paragraph line 2 Page 12 shows how S/sung marks em from factory).

@Dj how are you writing to YLOD nands... using amoxiflash compare (selective write??) infectus s/ware?? i would rather repair the YLOD(hware issue) unit then take flash out to to repair brick... too risky.


i wonder if we had done something similar to what ChipD had done with the wii, piggy back a second nand chip on the original & have a toggle switch to switch between em. obviously we'd need two but then the PS3 would be the none wiser provided we kept both at the same FW.--> brick it, just switch it, boot, hot switch back, flash... like the old days of BIOS SAvIOR chips...

@ DF any release date on software.?? & is xavbox any better then infectus software??

[djseban]

@defyboy:... You must know, that coreos.pkg is arranged in several areas of your dump.. You can't simply copy coreos content and paste it to your dump...
@DeadlyFoez: Do you have any software, that can paste coreos content correctly in to the dump?

Regards

[DeadlyFoez]

Xavbox is a lot better than the infectus software.

No, I will NEVER be releasing the software. Besides my team, only 2 other people were lucky to beta test it, and that was before the final version was created. But due to the whole shit with sony and wanting to not get myself into any type of anything at all, the software and source is on a micro SDHC wedged between 2 pieces of wood. I have decided for, many reasons, a few weeks back to NEVER EVER release it.

There is already software available to do what you want to do, you all just need to learn a little on your own. Not everything can be given to you guys on a silver platter.

[defyboy]

%90 of NAND chips have bad blocks. They come out of the factory with bad blocks all the time. It is normal. But that does create an issue for flashing files to your nand because if that file lands on a spot where there is a bad block then you have to skip that whole block, which also is listed in the TOC.

I have been flashing these via the NOR interface on the starship chip, I assume this handles bad blocks automatically as I have no issues.

@defyboy:... You must know, that coreos.pkg is arranged in several areas of your dump.. You can't simply copy coreos content and paste it to your dump...
@DeadlyFoez: Do you have any software, that can paste coreos content correctly in to the dump?

Regards

I have RE'd the filesystem on flash as per here: Flash - PS3 Development Wiki and it is definitely in one contiguous chunk. Can you please elaborate.

[fre3PS]

Xavbox is a lot better than the infectus software.

There is already software available to do what you want to do, you all just ....

@ DF, no probs... can you at the very least point to software, no need for full blown tutorial or anything but would appreciate a starting point. i bought a few wanin bricks just to mess with... love to tinker ...

i am just not too sure which way to go ... get clean dump and insert keys into it and then write to nand or RMS way and just read nand replace the coreOs & diff write to nand using amoxiflash?? would like to hear your thoughts...