yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] AngelDeath:
Sorry still away, but I didnt want anyone to think I forgot.

Unconn, the reason I asked for the read out is to compare to mine, and D3lta showed me something, but notice in our info 8 we are missing blocks 4,6,7,9 in the list, between the three of us, I thought at first that where thje bad blocks were, be d3lta's is not a samsung and he has the same blocks missing, if thats the boot, cache, and recovery, why those blocks in almost the middle of the nand?

But still have things to deal with, earthquake, severe storms, and now a Hurricane, whats next Mass locusts?

But I wanted to point that out.
[HD2 Android NAND Development] Unconn:
If you mean bad blocks? Yes eventually. It could be one year or 5. Also, the affect of the bad blocks when they happen could be very limited depending on the location of them.

I looked for fsck on my phone and I was not able to run or find it. What ROM were/are you running when you got this in logcat?

I also had this at first. I believe I had to restart mtty again to get the USB option to show up.
[HD2 Android NAND Development] ph03n!x:
I am running a CM7 nightly (08162011) complied by Arif Ali/ AirforcProductions. The /system/bin folder has fsck_msdos...

EDIT: Just realized it is only for FAT file systems... http://www.manpagez.com/man/8/fsck_msdos/

EDIT 2: Came across this old post by Cyanogen:

Wonder if CM7 has some sort of FS management?
[HD2 Android NAND Development] Unconn:
It is interesting. That we have the same blocks missing from our "reversed blocks" list, but I do not think we should worry about those. I think that it could be the way the HSPL is written, but I do not see it as an issue.

I am running a CM7 nightly also. It would be nice if CyanogenMod ran some sort of file system check (fsck) but I do not think this is happening in mine (will look around though). Maybe this never made it to the CM7 port we are using.

<5>[ 2.904968] Creating 10 MTD partitions on "msm_nand":
<5>[ 2.904998] 0x000004320000-0x000004420000 : "misc"
<5>[ 2.906707] 0x000004420000-0x000004920000 : "recovery"
<5>[ 2.912475] 0x000004920000-0x000004e20000 : "boot"
<5>[ 2.918243] 0x000004e20000-0x000005320000 : "sboot"
<5>[ 2.924011] 0x000005320000-0x00001b120000 : "system"
<5>[ 3.294586] 0x00001b120000-0x00001d420000 : "null1"
<4>[ 3.330444] ###BAD BLOCK 3735 1D2E0000###
<5>[ 3.332122] 0x00001d420000-0x000024020000 : "cache"
<5>[ 3.446533] 0x000024020000-0x000024f20000 : "null2"
<4>[ 3.449066] ###BAD BLOCK 4627 24260000###
<4>[ 3.462371] ###BAD BLOCK 4728 24F00000###
<5>[ 3.462890] 0x000024f20000-0x00003d120000 : "userdata"
<5>[ 3.870269] 0x00003d120000-0x00003e820000 : "null3"
<4>[ 3.871124] ###BAD BLOCK 7822 3D1C0000###

I was having issues once I put my bad blocks back into my system and user partitions. Just FYI the above layout is how I got around my bad blocks. This would not work for everyone because your bad blocks might not be in a place where you can partition like this. I have had only one reboot since since made this change (about a week now?) and it was a reboot from when I pulled the USB out without unmounting in Android.

What this tells me is that something should be handling the marking of bad blocks, even just at the file system level, and it is not.

I am going to have a little bit more of a look at why we do not seem to have a fsck command....
[HD2 Android NAND Development] Unconn:
I have had a look around and did some research and both of the above. They both have to do with the SD card mounting. The first one says fsck_msdos. This would fsck a vfat partition. The second one I am sure has to do with the SD card also and maybe doing a check of the vfat or ext partition.

Much like file system creation (mkfs.ext2, mkfs.vfat) fsck is specific to the file system. I have seen no fsck for yaffs. I think this is because the NAND and yaffs are supposed to handle bad blocks themselves. EDIT: One or the other are supposed to be assigned to handle bad blocks, NAND or yaffs.
[HD2 Android NAND Development] Unconn:
I know I have been posting a lot, but I have stumbled across something interesting. Nexus S uses EXT4 on it NAND and not YAFFS.

http://www.smartmobix.com/android_file_system_201102

http://arstechnica.com/open-source/...em-hits-android-no-need-to-fear-data-loss.ars

http://blog.gsmarena.com/android-2-...system-promises-better-dual-core-performance/

So since we CAN fsck EXT partitions, why could we not run EXT (with precautions) on our NAND? The Linux kernel supports this file system type by default and it is used in many apps2SD options. I have tried to format some of my NULL (see above) partitions as EXT2, but I do not seem to be successful. Maybe I will need to format them with EXT4. I know there are binaries around for this.

Any pointers/ideas/insults?
[HD2 Android NAND Development] pathaniya:
Does this apply to MIUI roms too, if yes, could please anyone tell where to that "Error Report" setting in any MIUI rom? Am on "Jan Willaims" MIUI rom but in "Advanced" tab there no "Error Reporting" tab/button.
[HD2 Android NAND Development] ph03n!x:
I have been doing some reading...

From Wikipedia

Source

Wikipedia

From the looks of it YAFFS2 *should* manage bad blocks without hampering regular operations. Not sure if something is required from the OS too for that to work.

I tried to figure out EXT implementation on NAND earlier, and could not find any documentation on it - let me give your links a read later...

This is not related to the ROM that you use, but the Phone (hardware)'s memory itself. The "Advanced" option we are discussing here is in ClockWorkMod Recovery, which is accessible on Magldr by holding down the power button while turning on the phone and choosing AD Recovery, or by holding down the Home key while turning on the phone in cLK.
[HD2 Android NAND Development] Satyan:
Hello Unconn, Can you please share how did you create the Custom Partition layout, as i think i would also be able to avoid the bad blocks and create a partition layout.

My Hd2 bad block layout from info 8 seems to be :

BLOCK 3852 (0xF0C) is bad block

BLOCK 4275 (0x10B3) is bad block

BLOCK 6931 (0x1B13) is bad block

BLOCK 7346 (0x1CB2) is bad block

from the last_kmsg

[ 1.838836] Creating 6 MTD partitions on "msm_nand":

[ 1.838867] 0x000004320000-0x000004420000 : "misc"

[ 1.840515] 0x000004420000-0x000004920000 : "recovery"

[ 1.846313] 0x000004920000-0x000004e20000 : "boot"

[ 1.852081] 0x000004e20000-0x00000ee20000 : "system"

[ 2.023834] 0x00000ee20000-0x00000f320000 : "cache"

[ 2.029632] 0x00000f320000-0x00003e820000 : "userdata"

[ 2.350280] ###BAD BLOCK 4349 21FA0000###

[ 2.406372] ###BAD BLOCK 4772 25480000###

[ 2.757476] ###BAD BLOCK 7428 3A080000###

[ 2.812316] ###BAD BLOCK 7843 3D460000###

Thanks !!
[HD2 Android NAND Development] Satyan:
i also noticed for some reason /system/lib/egl is always invalid characters in my case after rom extraction

# ls -l

ls: ./ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ: No such file or directory

ls: ./ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ: No such file or directory

ls: ./ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ: No such file or directory

ls: ./ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ: No such file or directory

ls: ./ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ: No such file or directory

ls: ./ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ: No such file or directory
[HD2 Android NAND Development] Unconn:
I will take a look at your blocks tomorrow. Been away from forum.
[HD2 Android NAND Development] Unconn:
I used your last_kmsg numbers:

NAME	MB
bootloader	67.125
misc	1
recovery	5
boot	5
sboot	5
system	350
cache	108
null1	58
userdata	328
null2	* (set it to 0 {zero} so that it uses remaining space)

This should put your bad blocks in the NULL partitions and still give you 350 /system, and 328 /userdata. This should be good enough for most ROMs. Can't really make you /system much smaller because of location of bad blocks. Try that and grab the bad blocks from either dmesg or last_kmsg and let us know if we have them isolated.
[HD2 Android NAND Development] Satyan:
Thanks for taking time for the analysis. however i am not sure how to implement this.. should i be rebuild the clk with this kind of partition table. or how ?

really appreciate your time !
[HD2 Android NAND Development] Unconn:
You can do it a few ways, but the way I did it was using the fastboot oem commands that were enabled/create in one of the development versions of clk. I would either clear all partitions and recreate them with the sizes quoted, or another way would be to only remove your /userdata partition, create /null1 and then recreate the /userdata to the correct size. You do not even have to create the last /null2 partition as long as you set the /userdata to a static size.

get clk 1.6de(?) into fastboot and try:

fastboot oem help

and then look at phone's screen.

HTH
[HD2 Android NAND Development] :
I noticed something strange.. on both of my hd2's, when I use fastboot erase system too much, more bad blocks start appearing..
[HD2 Android NAND Development] tmihai20:
I think I encountered the bad blocks issue too. I checked everything that AngelDeath said here, but I could't find any bad blocks. The weird issue is that autorotation didn't work anymore in my old setup. I used to modify the zip Tyween uploads and take out a few apps I am not using. The new zip was about 5 MB smaller. I have a laptop with Ubuntu and a desktop with Windows 7. I noticed that an untouched zip from Tyween shows Unix in properties on Windows 7 with WinRAR installed and DOS if I modified the zip with WinRAR or TotalCommander ( I don't know if this has any importance). I even tried unraring that zip and repackaging it with WinRAR, without any luck. Even if I used my modified zip for a fresh install, autorotation wouldn't work. This situation appeared only recently, I don't know when, it must be after flashing Typhoon 3.6.3 modified zip. I tried other ROMs (HyperdroidGBX CM7, Tytung's Gingerbread ROM, even flashing an unmodified zip for Typhoon 3.6.3) and autorotation is functioning with it. Can anyone give me an explanation? I spent about 5 hours yesterday trying to figure out what was wrong and I ended up flashing the original Typhoon 3.6.3 zip and taking out the apps with Titanium Backup.

Edit: It looks like my problems were cause by me. I modified build.prop in order to get market to recognize more apps. I put ro.product.board=mahimahi instead of ro.product.board=bravo, as it was in Tyween's ROM. I have modified it to ro.product.board=bravo and my HD2 is working properly again.
[HD2 Android NAND Development] Satyan:
I am able to get some stable bootloader with yesterdays update of HBOOT.

however i still cannot flash as a cwm update file... it breaks during the extraction process and does not full extract in the system partition.

i have to create a NAND img and flash it from fastboot to get it to work, any ideas ? ...
[HD2 Android NAND Development] Unconn:
That is similar to what I was getting. I could not get any of my Nandroid backups to restore. It seems the data.img was being created corrupt. If I TAR-ed the partition off to a file I could restore it fine. Sounds too me like those bad blocks are either in your system or might even be in the starting block of the partition.
[HD2 Android NAND Development] yugoport:
I think im another one in list, I'm having a lot of hot reboots with almost any miui build, more stable know with ladyboo build, but still having some random hot reboots.. I'm using a T-Mobile hd2.
[HD2 Android NAND Development] Satyan:
is there any way i can create the system.img with preserving the symlinks from the CWM image.

currently i am flashing and manually creating with adb, but it seems the moment cwm recovery is used the system becomes unstable....
[HD2 Android NAND Development] odoss:
Is there a way to see if the phone has bad blocks with windows 7 throught usb ?
[HD2 Android NAND Development] Sneakyghost:
@AngelDeath

since i am also experiencing described symptoms rather frequently (all sorts of random behaviour), i checked my HD2 with mtty (what a pain on x64 win7!) and found nothing, nada. No bad blocks. Just reporting back my experience. Same symptoms, no bad blocks. Not sure yet where else to go looking...
[HD2 Android NAND Development] D3LTA:
I have 2 even old hd2, on with samsung other hynix

Almost same flash behavior, samsumg one is my dev/test device..

And hynix one has been flashed more, but samsung has bad block and hynix non... quality issue i guess right?
[HD2 Android NAND Development] Visentinel:
I guess the only way to findout if you have Hynix or Samsung flash is to rip open the phone and read the chips ?
[HD2 Android NAND Development] AngelDeath:
No from what I read when you go into tri-color bootloader the top is the chip and would tell you the kind it is its like a code.
[HD2 Android NAND Development] D3LTA:
if you go to Tri-Color screen and look in top line:

SS stands for Samsung memory chipset.

HX stands for Hynix memory chipset.

also with mtty and info 8 you can see what memory chipset you have..
[HD2 Android NAND Development] clyder:
hi,

I am searching for a way to do a task 2a through Custom RUU, without mtty...just like we have modified nbh to do a task29. But no luck.

Anyone has any info on this?

This is needed for a friend who has problems making mtty to work.

It took me two hours of reinstalling drivers, rebooting until it finaly worked.
[HD2 Android NAND Development] YZ:
My phone won't boot android from nand anymore, task 29/task 2a doesn't help..

info 8

--- 2K bytes sector version ---

DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40

Checking block information

BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
BLOCK 955 (0x3BB) is reversed block
BLOCK 1082 (0x43A) is bad block
BLOCK 1084 (0x43C) is bad block
BLOCK 1135 (0x46F) is reversed block
BLOCK 3523 (0xDC3) is bad block
Partition[0], type=0x23, start=0x2, total=0x3E
Partition[1], type=0x0, start=0x0, total=0x0
Partition[2], type=0x0, start=0x0, total=0x0
Partition[3], type=0x0, start=0x0, total=0x0

CE Total Length(with sector info) = 0x20200
CE CheckSum Length(without sector info) = 0x20000

Cmd>

Cmd>task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=497, total block of CE=3599
erase_page - error bad status: 0xB791E960
ERASE block 619 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 874 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1082 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1084 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3523 FAIL !!!
Write 0xFF start page=0x7C40, total page=0x383C0
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end

Cmd>info 8

--- 2K bytes sector version ---

DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40

Checking block information

BLOCK 1082 (0x43A) is bad block
BLOCK 1084 (0x43C) is bad block
OS NOT FOUND !!!

After changing misc to 10, system to 160 and boot to 10, hyperdroid 3.0.0 booted, but everything Fc'ed.. I tried flashing another rom.. but it got stuck at the android screen..

is there a way to "go around" this issue?? I don't want to use winmo 6.5 on my hd2.. I hate it
[HD2 Android NAND Development] kokotas:
Hey,

here is a suggestion:

Using dan1j3l's cLK 1.6.5 you could change the order of the partitions and set the userdata partition first or you could create an unused "null" partition in order to "wrap" your bad blocks wherever they are.

I don't know your partition layout, but I'm guessing that your bad blocks

BLOCK 1082 (0x43A) is bad block
BLOCK 1084 (0x43C) is bad block

are located inside your misc partition and maybe that's causing the non-booting issue.

Regards
[HD2 Android NAND Development] YZ:
I don't know where they are located, but I changed system to 160, misc to 20 and boot to 10. My phone is booting now :)

Less space for userdata.. But I use app2sd anyways.
[HD2 Android NAND Development] odoss:
Oh God :(

Please devs make an app to avoid using thoses bad blocks like in win rom, it can be VERY VERY useful for everyone and for you, i have a lot of hot reboots these days because of that :(
[HD2 Android NAND Development] ph03n!x:
EXT4 on NAND should solve that...

Swyped from my HTC HD2 running CM7 (Gingerbread 2.3.7)
[HD2 Android NAND Development] roloracer:
Care to explain what you mean, sounds like you know how to fix this issue?

Sent from my HyperdroidCM7 HD2
[HD2 Android NAND Development] odoss:
How can EXT4 solve that ? please give more details ;)
[HD2 Android NAND Development] YZ:
+1 to that :O
[HD2 Android NAND Development] ph03n!x:
There was a discussion between me and @Unconn in this thread from page 20/ 21. In short, Nexus S has EXT4 in the NAND. This would mean that we can use fsck to check the partition for errors, unlike yaffs, where bad blocks are supposed to be managed by the NAND controller/ YAFFS.

While I am a novice in this area, it seems to me that we can manage bad blocks better with EXT4 (Read through the links posted by me and @Unconn in the linked posts). How do we get EXT4 on NAND is completely beyond me :)
[HD2 Android NAND Development] jcsy:
I have returned from a diagnosis of my HD2 and apparently, my CPU was having problems

Before I sent in my device, I had all kinds of random reboots, with data, without data, on charge, Windows, SD Android, NAND Android, Gaming, not gaming

After freezes, It would not boot until about 10-15 minutes

I performed many tests from Radio 2.06-2.15, many Windows ROM, SD Android and NAND ROM's whether with SENSE and WITHOUT, with CYANOGEN and with different kernels with and without SIM card, SD card, Task 29, etc

I couldnt even get Windows Phone 7 to boot (which I was able to initially before my CPU decided to funk up)

It always froze regardless of anything I do

FOR THOSE SUFFERING FROM BOOTLOOPS, FREEZING and ETC

I suggest you claim warranty while you can, as you can attempt every possible troubleshooting method and might not come to any resolution except to warranty or pay somewhat like 100 USD for a new CPU

I also suggest that you do not overclock, underclock too much as this is the only thing I noticed being the root of the problem initially and I do blame myself. I run stock now.

I have a second HD2 and that runs PERFECTLY WELL, with just 1 FLASH and no overclocking.

I hope my post brings awareness to all regarding flashing and hardware problems, and while it is not related to BOOT sectors, it is gravefully heart breaking when it affects our phones capacity to do anything
[HD2 Android NAND Development] pyrorob:
hey, i had an idea about this.. theres a few versions of cwm that are floating around that are ext4 compatible, theres also this:[EXT4 CONVERSION]] i think that if the mount points are adjusted in the script in the zip and we use a cwm that has ext4 support, we could use cwm to flash our internal nand to ext4.. the next thing would be to modify a script and initrd in a rom to recognize it, and it should work..? or am i totally off the wall with this idea?

fyi: after some looking up:

/dev/block/mtdblock3 /system

/dev/block/mtdblock5 /data
[HD2 Android NAND Development] tobiascrystal:
Would this be any help? http://xdaforums.com/showthread.php?t=1297587
[HD2 Android NAND Development] pyrorob:
yeah, that would be a quite usefull tool, but as from what i understand, the tool flashes a custom recovery to the device, now, the recovery's are like little roms themselves, they have there own kernels, they have to be tailored to the device.. so im fairly confident when i say that, that tool wont work on our devices unless you modified it with kernel code applicable for the hd2..
[HD2 Android NAND Development] tobiascrystal:
Cool

I kind of figured it wouldnt be a simple copy paste operation but with the awesome dev's around here (like Arif-ali he ported the TWRP recovery in less than a few hours!!!) stuff like this is childs play. However like mentioned before I do not know how much change it would take to get the curent roms working with the different EXT4 either. I did notice that they say in there that the Sensation is using EXT4 format anyway so this for their device is kind of redundant.

I just hoped that this would be a quick way to get it ported and tested.
[HD2 Android NAND Development] accountabc:
I think my HD2 might be another bad block victim... In the last few weeks I had my HD2 crash when installing something from market, after which it sorta factory resets itself... I haven't read through the intire thread (yet), but am I correct to conclude that there aren't any real solutions at the moment?

EDIT: i've now read through the intire thread. It seems like there are ways to mark bad blocks correctly in order to run Android from Nand, but no devs are actively working on it. kinda makes me sad :(. My Nand is toast; With Typhoon's CM7 I get a crash every time I hit the 38MB installed programs mark... Going to try to install a bigger (Sense) rom later today just to see if it even will boot, if not it'll be an SD build for me...
[HD2 Android NAND Development] MarkAtHome:
I totally agree. It is beyond me, but I am sure that we have the resources to address this.

Maybe it can't be done... ;-) ;-)

--
[HD2 Android NAND Development] t1h5ta3:
bump... looks like im a victim as well...

i got my hd2 from a guy that couldnt even get minmo to boot any more, i ran task 29 a bunch of times, flashed oem, more task 29 and it finaly booted...

ran android for a long time now i get all sorts of issues..
[HD2 Android NAND Development] fowl2:
Is there a yaffs2 diagnostic tool somewhere? I'd like to see write counts, bad blocks etc.

Surely "formatting" isn't the only way. (And hopefully it doesn't wipe write leveling data! )
[HD2 Android NAND Development] DannyBiker:
The only badblocks I have is this :

"Extracted file "/system/bin/badblocks"

It's in a "bin" folder not "xbin". Is it a bad block or not ? :confused:
[HD2 Android NAND Development] :
That's not a badblock, that's just a binary...