[ Maj : v1.3 ] NAND Compare and Reconstruction Tool v1.2

MAJ : la v1.3 est dispo en section téléchargement.

Rab sort une nouvelle version de son outil "NAND Compare and Reconstruction Tool v1.2". Il permet de verifier l'integritée des block de 2 dump de nand different et de réparer ceux ci si vous avez un 3ème dump. Pour la réparation, il compare les 3 dumps et répare les block qui sont au moins identique sur 2 des 3 dumps.

nouveautées de la version 1.2:

- support des nand de 256mb
- utilisation d'une taille correcte de block pour les nand de 256/512mb (0x20000 + ecc)
- barre de progression ajoutée

L'outil a 2 fonctions :

- comparer 2 images (dump) de nand :

better than simply using md5 as it tells you which blocks are mismatched, which allows you to reread only those that are in error rather than the entire chip (speeding up the process)
one use of this is when verifying a write by reading back the nand and comparing it against the original you wrote, if you get a bad block just reread that individual block, patch it into the full read and compare again (files are reread each time you click compare, no need to reselect the same files in the gui)

- réparer une image depuis 3 dump incorrect:

assumes that read errors don't occur in same place each time, which is true for some read errors (e.g. lpt timing problems), if there is a good reason why you can't read something then this may not be true
this tool cannot recreate a nand out of nothing, if you give it 3 files full of zeros you'll get a recreated nand full of zeros, always look at a dump to make sure it looks correct (e.g. has a microsoft copyright at the top, once you've reconstructed a nand open it in 360 flash tool and make sure it reads ok there)
the tool works by comparing blocks between the 3 files, any block found matching in 2 (or 3) of the files will be considered good, you will be warned if not all blocks can be recovered, in which case you'll need to get more reads or look for a good reason why your reads are so bad

1.2 (2009/12/15)
- support for 256mb nand
- use correct block size for 256/512mb nand (0x20000 + ecc)
- added progress bar
1.1 (2009/12/13)
- support for 512mb nand (assumes same block size as 16mb)
1.0 (2009/12/12)
- first release