[liranantebi]

Yes. This is the location, guerrierodipace.
You are more than welcome to try it out, incognita.

You can have a look @ bailey's guide for instructions for the NANDs with progskeet. Use teensy NANDWay for reading writing.
I do not yet know how to 'crash' the PS3 with NANDs as the progskeet does. With the NOR it's easy - you pull the TRISTATE low (afaik).
So other powering options are:
1. Use external power - the teensy 3.3v regulator is not enough. you must use external source that have enough current (it's ~1.8A).
2. extract the NANDs from the motherboard and do offline reading.

I don't have a 360 clip yet - so i will be happy if someone would like to try it out with a clip.

The NANDWay.py script is straight forward:
info - extracts the id from the chip
dump - dumps the entire NAND contents to the local disk
write - writes and verifies everything.

I also would like to get NAND dump with bad blocks to test (i just need the dump). you can see that a NAND have bad blocks with flow rebuilder. it's ok for a NAND to have bad blocks. usually they are mapped during manufacturing and can develop over time.

future features:
1. Teensy should be powered from the PS3. How do I crash the NAND ps3?
2. Bad blocks. skip bad blocks as the ps3 does. the information is stored in the spare area - so most probably sony didn't erase it. i just need to have one dump with bad blocks in order to understand how to identify.
3. Differential write. writing+verifying is very slow. Differential writing can improve write time dramatically and avoid writing to un-needed places.
4. read/write parts of the NANDs. Like what NANDPro for the xbox does.