Bad Blocks?
If
bad blocks were found while dumping your NAND...
Open one of your NAND dumps in
360 flash dump tool 0.97
Don't worry if it says
BADKV all over the place, this is normal because you haven't entered the
CPU Key yet. (We will get to that later).
Check for a
bad blocks tab, next to the
file system tab.
If there is
no bad blocks tab, you have
no bad blocks.
If there
IS a bad blocks tab, click on the tab and verify that it looks like this:
Note: Bad Block ID 0x0349 [Offset: 0x00D8D200]
-> Block ID 0x0349 found @ 0x3FD [Offset: 01073A00]
You should see the above 2 lines of text, for each bad block you have.
The numbers may be different of course, depending on which blocks are bad, but the point is, for each bad block, you should see that the block was found @ another block.
This means that you did have bad blocks, but they have been corrected by the NANDs error correction, so they are legit bad blocks, and not just read errors due to dodgy soldering.
Example of 3 corrected bad blocks...
If the errors are at block
0x50 or above, no further action needs to be taken, because…
"Many user reports indicate that using Xell-Reloaded/Rawflash v3 to flash the Dashboard image, has a much better result over flashing with hardware flashers. This is because it helps to auto-remap the bad blocks in case they exist."
As we will be booting into
Xell-Reloaded, which will use
Rawflash v3 to flash the NAND later on, the bad blocks will be auto remapped for us.
But...
If you see:
Note: Bad Block ID 0x0349 [Offset: 0x00D8D200]
But NO
found @ location for the block, that means this bad block was the result of a read error with the NAND reader. Check your soldering and try again.
If you have Bad Blocks at 0x50 or below, check out Martin C's guide on how to manually remap them. (
Info)
If all checks out, you now have
2 good NAND dumps.
KEEP THEM SAFE. FOREVER.