robinsod
Changelog
Handling of bad blocks in Cx area Now you will see the bad blocks (and the replacements) listed as "notes". if you are very unlucky the block at 0x8400 (where the CB header is located) will be bad. In this case the tools will fail and the image is unusable today.
Handling of bad blocks in FS area (not 100% yet). Currently I test for bad blocks as I insert files into the flash image. If a bad block is detected it is simply skipped over. I had a look at a dump that contains bad blocks in the File System area and it appears the file system is unaware that some of the blocks it is using are marked as bad. I guess the flash driver silently does the remapping of bad blocks for the file system. I will fix this soon since it crashes the flash tool Wink
Handling of replacement blocks at end of flash image
Now you will see the bad blocks (and the replacements) listed as "notes". if you are very unlucky the block at 0x8400 (where the CB header is located) will be bad. In this case the tools will fail and the image is unusable today - sorry.
I used it to check my nand dumps to make sure they were clean, and had no bad blocks.
If you are using this for a nand dump, you must do the following step:
In Degraded.exe click 'Settings', set the 1BL Key to 'DD88AD0C9ED669E7B56794FB68563EFA', select the folder where the 1888 file system is located, and set 'File System Start' to '39'.
Clean Dump
Bad Dump
Download:
http://www.mediafire...php?fn2umwkzzin
