[HD2 Android NAND Development] Sneakyghost:
Read my docs, mate. I have been through most of the **** with MTTY and such.

Bad blocks are never corrected. They are called "Bad" blocks because they are bad, broken, unfixable. The Memory Controller is looking after them by itself. It flags unresponsive blocks as bad and redirects to a spare adress somewhere else in NAND. Every other layer above the Memory Controller then just writes around the Bad blocks. Also Task29 from MTTY or the LEOadvancedRUU or any other RUU (essentially, they all do the very same talk to chip) just write around those bad blocks. They MIGHT be improving filesystem structure aroundthose bad adresses but they never correct bad blocks. That is just a myth.

Take note of this: Irritatingly, my new HD2, which has bad blocks, is way more reliable then my old HD2 which had no bad blocks.

Most issues that look like bad blocks in NAND can, but don't necessarily have to be, actual Bad Blocks on SD. I have an SD that locks up every now and again and also drops the Mount on Phone and PC alike. Some tools say its bad sometimes. So i supsect it having one bad block somewhere. Sometimes, a repartition fixes that and the bad block never gets touched, the phone works brilliant. On other days, i already notice that bad block when moving the ROM.zip to card for preparing a new flash. I already know from experience, that when hitting the bad spot while copying basic files, the full installation will be faulty.

So i'd really go looking for bad behaviour of your card and if in doubt, check thoroughly with other cards. Run the ROM for a while on different cards.

Since Dan's or any other Sense ROM is highly dependent on SD-Cards (at least for the EU phone) it is only natural that cheapo bad cards affect the ROM very strong.

Also, i have the impression, that TmoUS owners who setup a native TmoUS layout without an SD-EXT come here complaining far less often than the EU users or those with an SD-dependent setup on a US phone.

Think about this mate.

---------- Post added at 04:25 AM ---------- Previous post was at 04:17 AM ----------

MTTY info8 will output bad blocks from a limited adress range

MTTY task29 will do a full format except spl, radio and splash region and will thus notice more bad blocks than info8 and will also inform you if it finds any.

MTTY also has another task that formats all including the SPL part, which is very dangerous and bricked my phone, because that task is not well documented here and i only found out after using it, that it will kill the spl if it's hacked (Hard-SPL'ed with cotullas own SPL). So i will not write it here in public as i fear to be responsible for damage done to phones but if you want to try out i can tell you via PM which command that is.

Hint: i found all commands the Phone understands by taking the SPL.nbh apart and looking for a command list (that is not encrypted and in plain text strings). I then tried them all blindfolded and bricked my phone... It was so badly bricked that it was hard to recover even with jTag it took more than one try to get it online again.

---------- Post added at 04:27 AM ---------- Previous post was at 04:25 AM ----------

Reading the provided Documents actually does answer this question too.