yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] dertester123:
OP:

Hi,

i read a few pages and just wanted to share my experiences.

I had no problems with my device, i just wanted to know if i have bad blocks.

Info 8 showed me 3 bad block messages.

If i do task29 it also claims the 3 bad blocks.

After i did the steps in my quote task 2a was abel the "repair/mark" two of them. If i run info 8 after task 2a it only shows one left.

Im not sure what that means, i guess task 2a can only repair a range of blocks. The one that wasnt repaired (not sure if repair is the right word) had a slightly higher number than the other two that werent listed in task 8 again after task 2a.

To bad i forgot to save the mtty logs :/
[HD2 Android NAND Development] wilwilwel:
i've the same problemen and its hardware related. The connector of The digitizer(touchrecording) is just beneath The endcall and back button. Due to long usage of Theo phone the gel between the button and digitizer desolves making it disable The digitizer, hence your experience.

To void the digitizer getting disabled only touch the hardware buttons on the lower edge with your nail . You can flash stock spl radio and rom toe send IT for repair. EU has 2 year factorywarranty so htc will repair it.
[HD2 Android NAND Development] dertester123:
Well offtopic i thinks sorry..

@wilwilwel

Uhm do you mean me? Not sure what post you´re referring to, but my device is fine.

My post about this problem was just for people that dont have warranty..

In my case i bought a cheap HD2 with broken digitizer for 50€ and a new digitizer 50€ and repaired it myself. At this time i saw that thin layer of glue and had the problems. After placing a thin foil on it i have no more problems.

I dont tink that the cable itself will make problems due to heavy button usage.

But i hope that the new Android 4.0 Softbuttons will work with most builds, i really like them even if i have hardware buttons and with a bit lower dpi can get the place on the screen back ;D
[HD2 Android NAND Development] munjeni:
Hey, I started http://xdaforums.com/showthread.php?p=20222676 about problems with nand, please read
[HD2 Android NAND Development] lukas1234567890:
Hello, so I was also curious if or how many bad block has my HD2. Here is my result:

info 8

--- 2K bytes sector version ---

DEVICE NAME=samsung_KBY00N00HM

DEVICE ID=0xBC

DEVICE MAKER ID=0xEC

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 155 (0x9B) is bad block

BLOCK 213 (0xD5) is reversed block

BLOCK 907 (0x38B) is reversed block

BLOCK 908 (0x38C) is reversed block

BLOCK 909 (0x38D) is reversed block

BLOCK 910 (0x38E) is reversed block

BLOCK 911 (0x38F) is reversed block

BLOCK 969 (0x3C9) is bad block

BLOCK 1100 (0x44C) is bad block

BLOCK 1808 (0x710) is bad block

BLOCK 1960 (0x7A8) is reversed block

BLOCK 2007 (0x7D7) is bad block

BLOCK 2176 (0x880) is bad block

Partition[0], type=0x23, start=0x2, total=0xFE

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) = 0x80800

CE CheckSum Length(without sector info) = 0x80000

Cmd>

I am surprised, I have 6 bad blocks, but I never had any problems with my hd2, no problems with Windows mobile, no problems with android even WP7. I read the whole this interesting thread and I was almost sure that I have no bad blocks cause I had never any problem like people here described, but I also have 6 bad blocks. Maybe bad blocks are not as important as it looks on the first sight or there are another things important for our devices which causes restarts or other unwanted behaviour. Who knows?
[HD2 Android NAND Development] dertester123:
Well as far as i know the problems dont have to be critical. If a small file gets written to a bad block and the app/tool etc recognizes this its writing it to another postion.

Problematic are big files when there is no space in the partition, example: many users in Tytungs ics thread have no problems with bigger partitions but when its minimum to what they need for the system its making trouble...

=>Thats just what i guess. There are error logs in cwm, you should check this out.

Another question: was task 2a able to remove some/all bad blocks?

I had three and no problems. After task2a i got one left..
[HD2 Android NAND Development] lukas1234567890:
"Problematic are big files when there is no space in the partition, example: many users in Tytungs ics thread have no problems with bigger partitions but when its minimum to what they need for the system its making trouble..."

This is very good idea, maybe this is it!:)

I have never tried task2a, I even didn't know about mtty till now..I have installed

NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13] ROM now and it's very light, stable and amazing ROM, everything works perfect and I have no need to flash anything else...but I am gonna try ICS 4.03 ROM when or if all bugs will be fixed, so then I'll try task2a hoping it may solve some of my bad blocks. Thanks for reply, it's very interesting. I think really that big files could make problems, when there is not enough such a big place for a big file in NAND, cause our NAND is "cutted up" to small parts due to bad blocks. Sorry for my bad english.
[HD2 Android NAND Development] AngelDeath:
Just to answer some questions, and I by far am not an expert, but the premise is right: EXT4 would be better at handling file system errors then yaffs, even though yaffs is suppose to manage the FS I think because its not a "native" FS for our phones is where the problems of it handling it falls into. What would need happen is we would need someone to create a flashing tool, like magdlr to make it able to use ext 4before we could use a ext 4 cwm. And then all the roms would need to be re-done to support this file system, cause as of right now, we dont have a error checking tool at all in my book.

As for the task 2a, it will not work on the HD2 at all. The only reason you went from 3 to 1 is probably because it was a data corruption that was able to be corrected (think of a chkdsk /f command in windows) but a hard error would have remained.
[HD2 Android NAND Development] timoz73:
Any one for help, thanks in advance

hi, a noop compared to you guys, can someone help me, i only have bad block at 0x09d60000 , is this matters & how to fix it, thanks in advance for good hearted Devs (i am also attaching my log from CWM renamed to txt for uploading).

erase failure at 0x04bc0000

mtd: erase failure at 0x06480000

mtd: not erasing bad block at 0x09d60000

mtd: erase failure at 0x0e420000

mtd: erase failure at 0x0ebc0000

Formatting /cache...

Formatting /sd-ext...

N.B.:

I read most of the posts but really confused what to do, task2a or what is the correct procedures to preserve the good blocks left, thanks in advance....
[HD2 Android NAND Development] Zupp34:
If you have just one bad block then don't even stress about it because you can't fix it anyways. I haven't seen anyone confirm that task2a fixes bad blocks. I tried and it didn't do anything other than somehow 'fixing' reversed blocks. And even those came back to exactly how they were after I flashed a ROM.

As for avoiding bad blocks, I haven't a clue. I just hope that I don't get 100% bad blocks before the phone just dies on its own.
[HD2 Android NAND Development] dzatara:
Hi and thank you for this thread.

I got 2 bad blocks at /data.

I just want to ask you is it on nand or on the SD card thank you.

EDIT: recovery.txt
[HD2 Android NAND Development] farcry27:
Thanks pretty cool :)

I have a Phone that is fairly bad. I have managed to get all the way to loading Typhoon and running, installing the backed up apps,

(after multiple tries, cool down sessions etc) ... but its very temperamental now, freezes regularly.

Ran the Error check in CWM, http://freetexthost.com/ujz323ionr

I see no "system/xbin/badblocks". Any insight on this error report please?
[HD2 Android NAND Development] dertester123:
As i understand that error log is only.for the area of nand that was written to whike installing rom..

Check for voltage as it seems a kernel dev trend to set unstable low voltages..

And if you restore old data you shouldnt wonder of problems. Do everything cleab and than start "complaining". Works 1000 times and imports errors when you dont expect them..

Gesendet von meinem HTC HD2 mit Tapatalk
[HD2 Android NAND Development] lan78691:
Thank you for this information, it was really helpful in understanding why people experience bad flash problems. I really hope devs take some time to implement some of the things you suggested. It is important if we want to save our HD2's!
[HD2 Android NAND Development] farcry27:
Perhaps I should Elaborate. Started from scratch, a clean install. The problems started on the old rom: random reboots and freezes. I Started a clean install: had repeated failed flashing of the radio, when I got that right, CWM had a few bad flashes... Then the ROM has some bad flashes.

So before you start the blame game, find out what really happened.

the phone is now crashing load stage, with error screens, only the MAGLDR is stable.
[HD2 Android NAND Development] mvinceti:
Ok this bad block afects android roms.But can I flash stock wm6 and

run Android from sd or Magldr build.Or only flash Magldr and run sd build that way dont have to be infected with bad block and we will be able to run Android normal or im wrong?
[HD2 Android NAND Development] marzinho:
You may prepare bigger partitions as well. In example, if ROM requires 150MB for system partition, prepare 160MB for it. During flashing, badblocks will not be used for storing any data. As long as you don't have so many bad blocks, making bigger system partition should be enough.
[HD2 Android NAND Development] dertester123:
Even radio and clk gives you bad flashes?

What hspl do you use?

Already tried info 8?

Maby a bad cable/usb port as cause?...

If you checked this i would maby try to add an empty partition as first one so that all following partitions start later. I guess! That one of your first sectors could be bad and only affect clk .... but thats.just a guess..

I would do info 8 task 2a task 29 and everything clean.

I would even think about reflashing bootloader but thats to risky if something.fails there...

Gesendet von meinem HTC HD2 mit Tapatalk
[HD2 Android NAND Development] YZ:
How can I make an empty partition ?
[HD2 Android NAND Development] dertester123:
Havent done it myself yet.

But from what i read:

You can use a custom partition image to flash.

Or there is a clk version (1.6.5 i think but those version numbers confusing me, must read descriptions) that allows to directly create partitions.

If its at the beginning i would think about increasing misc/boot for example to get the bad blocks at the end of one of these partitions.

Magdlr version:

Example from another board translated

:

Example bad blocks: 468,1497 und 1546

- 467 = 58,375MB

fail1 - 468

469 - 1496 = 128,375MB (1027)

fail2 - 1497

1498 - 1545 = 5,87 MB (47)

fail2 - 1546

1547 - ...

Thats how the partitions looked. (the partition order to fit)

misc ya 8b

boot yboot|ro 40b

cache ya 419b

fail1 ya 1b

system ya 1027b

fail2 ya 1b

recovery rrecov|ro|nospr 47b recovery-raw.img

fail3 ya 1b

userdata ya|asize|hr allsize

Problema here is that its only possible to have 128mb for system and 22mb for data or the other way.

So you need to find roms that fit here ...

Buts thats just an example maby your bad blocks are better.

You should check dmesg for mtd/yaffs messages at these blocks and after a installation the error file from cwm.

=> Errorlog shouldn display (besides one entry in the xbin/badblock or something like this) and mtd should show in dmesg your bad blocks.

==> That would mean bad blocks are causing no trouble while flashing and marked by filesystem and not used by android.

If all are marked you shouldnt use task29 as it removes these marked bad blocks and filesystem needs to find them again what could cause an error at the first writes.

And heres a thing that helped me as best mtty order so far:

mtty < ist dein Freund

Cmd>set 14 0

Cmd>task 28 55aa

Cmd>info 8

Cmd>task 2a

Cmd>task 8

Should find and mark bad block so that even on first boot android filesystem finds them from the filesystem info.

Hope that helped ;D
[HD2 Android NAND Development] Stickman89:
This isn't specific to the HD2 it is a well known issue with I'd say every winmo device that ever got a NAND Android Port.

This was apparent on Vogue, Kaiser, Polaris, Rhodium and possibly more. Do you know what's concerning... To the best of my knowledge and also experience none of these devices displayed any of extreme issues that we are plagued with (overheating, random reboots, instability). My HTC Kaiser was extremely stable and even faster then WinMO (heck I'd go as far as saying faster then my HTC Hero) running android from NAND and I had numerous bad blocks, DZO's Tinboot (Bootloader) even reported these bad blocks on startup. Not to mention that these were ARM6 devices with even lower internal memory capacity then our HD2's. There must be an underlying issue that has been overlooked, this needs to be solved ASAP before it causes more damage to our devices.

Furthermore I specifically remember at the time of using my kaiser recieving reports with older and less mature releases of Tinboot that bad blocks error was recieved by users (device would hang at bootloader) but after flashing updated releases of tinboot constantly maintained by DZO users were reporting there previous issues experienced had disappeared. I may be proved wrong but these are all past experiences with using Android ports to NAND on a non native device but I'd say we need Cotulla to investigate this issue as it maybe bootloader specific regarding memory addresses...

Failing that contacting XDA member DZO asking whether he can shine some light on this particular issue as I'm sure if anyone at all could advise it'd be him...

Best Regards,

ST1Cl<^^aN
[HD2 Android NAND Development] dertester123:
To be honest i would go so far and say that many problems that we have are not relatet to bad blocks.

I dont want to blame kernel devs but the faster a kernel develops (fikret/dorimanx) the faster problems occour.

Thats nothing bad i only want to point out that our filesystem generally should work even with bad block if you give it a bit extra space on each partition. But there are otther problems.

As always its easy to blame the closest problem but sometimes i think there are little differences betwen some devices and we are already very close to the max. capabilites of the device.

Problems with bad ram, cpu getting old and not as accurate (due to electon migration?) etc...
[HD2 Android NAND Development] DeXeS:
If I understand what's been said in this thread, this partition layout would work for me?

BLOCK 47 (0x2F) is bad block

BLOCK 534 (0x216) is bad block

BLOCK 1889 (0x761) is bad block

BLOCK 3210 (0xC8A) is bad block

BLOCK 3212 (0xC8C) is bad block

misc ya 46b

fail1 ya 1b

cache ya 486b

fail2 ya 1b

system ya 1354b

fail3 ya 1b

boot yboot|ro 40b

recovery rrecov|ro|nospr 60b recovery-raw.img

userdata ya|asize|hr allsize (<-- contains block 3210 and 3212 but this partition contains ~156mb and that much userdata I don't have I figure..?)
[HD2 Android NAND Development] eybay:
Dexes i had the same with userdate partition. it gave me some hot reboots and a lot of apps which has been crashed.

Would be better if u do extra partition.
[HD2 Android NAND Development] DeXeS:
Hmm.. might repartition the userdata also so that partition also will avoid bad blocks.
[HD2 Android NAND Development] iamcxa:
hey friend, seems task 2a works for me! i did that and now seems working with no prob.

i have some problem and getting serious - just like when i finished install, my app will have some of them was been broken, its exists but can't be runs. but after i did task 2a seems all working again for me. and the recovery.log has no any bad block was be show.

so i guess, maybe if someone

has only a few bad blocks

, then he/she can use this way - task 2a to fix this issue.
[HD2 Android NAND Development] iamcxa:
i think what you mentioned is interesting. as someone known, i have a thread to process about android's IO scheduler, in the progression i even had some freeze when i try to tweak the schedulers. but be honest i don't know which one is the major issue - bad block or wrong setting for IO schedulers. and sad to say that, i'm afraid i can't do any test to get the answer for this question, because it may speed up to break my nand.
[HD2 Android NAND Development] dertester123:
Your thread (io tester) is very interesting i will read this when i got the time.

Well i had this issue myself as i was really really sure that my problems were caused by bad blocks as only one or two persons had the same problems i had.

But playing around a long time it seems like it was just a very unlucky combination of kernel and the first tests with voltage scaling that didnt work well on my phone.

I hope your tool will help finding issues that lead in this direction. I will report when i tried :D
[HD2 Android NAND Development] YZ:
Please insert the text as code.. or upload to pastebin.

Sent from my awesome HTC HD2.

Yz.
[HD2 Android NAND Development] dertester123:
In my opinion These symptoms you describe are voltage and kernel problems. Raise min voltage and frequency and try different kernel.

Let logcat run (most likly nothingwill happen because of non sleep) ...

What about info8 and dmesg? What is clk black reporting?

Gesendet von meinem HTC HD2 mit Tapatalk
[HD2 Android NAND Development] ricky886:
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 28 (0x1C) is reversed block

BLOCK 29 (0x1D) is reversed block

BLOCK 30 (0x1E) is reversed block

BLOCK 31 (0x1F) is reversed block

BLOCK 492 (0x1EC) is bad block

BLOCK 822 (0x336) is bad block

BLOCK 1856 (0x740) is bad block

BLOCK 1864 (0x748) is bad block

BLOCK 1892 (0x764) is bad block

BLOCK 2508 (0x9CC) is bad block

BLOCK 2896 (0xB50) is bad block

BLOCK 3277 (0xCCD) is bad block

BLOCK 6053 (0x17A5) is bad block

OS NOT FOUND !!!

I have followed this

Cmd>set 14 0

Cmd>task 28 55aa

Cmd>info 8

Cmd>task 2a

Cmd>task 8

OMG!! I have nine bad blocks;), and now how can i do?!:mad:

using Tmous HD2

I use adownloader the phone will stuck:(
[HD2 Android NAND Development] mrmcphisto77:
i'm stuck on:

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

OS NOT FOUND !!!

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 2831 FAIL !!!

erase_page - error bad status: 0xB791E960

ERASE block 2844 FAIL !!!

Write 0xFF start page=0x7C40, total page=0x383C0

restore SPL OK

restore MISC configuratoin OK

restore MFG configuratoin OK

Format ALL end

is the phone bricked at this point???
[HD2 Android NAND Development] dertester123:
hmm not sure why info8 is not working.

But clk/magldr is working?

I read about some people that had very strange problems and a reflash of HSPL helped. But that may be risky and should only be done if you tried everything else.
[HD2 Android NAND Development] Wildcopper:
The "problem" could very well come from the fact that people are flashing way more times than the device was originally intended to. Think about it... there have only been very few updates to the original OS of the HD2, WinMO, at HTC. If you stick to the official OS, you flash what? 2 times a year, at most? But here, some people flash several different Android versions every week into their device. They flash (and use) the NAND as much in one week than it was intended to be used in one year or more.

Just my 2 cents...
[HD2 Android NAND Development] dertester123:
yeah thats true. And I also think its the main reason for the problems. But flashing is only one rewrite on nand... And I don't know how often nand reads and writes due system use..

There are also many people that flashed only a few times and have bad blocks. And others like me flashing multiple times a week with only few bad blocks.

What I meant earlier was that many people see the cause of problems in bad blocks too fast. Problems like kernel features that are not compatible with few phones don't come to mind so easy when a problem is so popular like bad blocks.

Its good that the newClk black shows bad blocks as marked(good ones) . And to reassure you can check dmesg for entries. If they exist I think it's not a problem of bad blocks as android recognizes them properly.

I hope that the rumors about new Magldr are true and it has improved bad block handling..;)

Gesendet von meinem HTC HD2 mit Tapatalk
[HD2 Android NAND Development] slamsteel:
Luckily, I only have one bad block.

Thank God. I'm using lite versions of CM7 and were previously using MIUI.
[HD2 Android NAND Development] Marne Jr:
Just posting cause it maybe help someone...

I will tell my story just in case it helps someone...

I have 3 badblockS on my nand and tryed almost every rom 3,5 runny availaable on XDA...

When using ext part for usual installation, after some reboots and about 5 days of use I got my HD2 stucked at htc screen on boot or starting in that language choosing screen with all my customizations lost and that message "STORAGE ALMOST FULL" what was a no real situation cause even If i installed nothing I got it and titanium backup and storage menu could not detect my internal memory (I think it was blocked and the initiation could just be possible by things installed on SD-ext)...

I gave up of trying and was using SD version of 3.5 sense build until I find Mikhei777 rom's (http://xdaforums.com/showthread.php?t=1298188) and the option of installing everything on nand... And guess???

It works!!!

And I have no more stucks on rebooting the phone.

The problem of using an all nand rom is that you can get out of space too easy ...

Than I formatted my sd card to have 1Gb of ext4 on it and still an all nand rom on internal memory... then I went to recovery and installed appsd2 GUI.zip application and after rebooting I moved all my dalvik cache to SD-Ext...

Now I have an all nand rom in my HTC HD2 and the possibility of installing as many apps then I could If I was on regular SD-ext installation...

I think this option of all nand kind installation can use different part of nand to install the boot information and then bypass the badblocks !!!

Hope it can help someone...

Bye.
[HD2 Android NAND Development] ayyu3m:
Well said. I specially agree on the part where flashing a Windows Mobile rom has some kind of system which checks the NAND for bad block and avoid writing to them. This is evident because when you compare Android roms that refuse to install complaining of bad blocks in mtty. But if you try to install a WM rom just after the failure of Android rom flashing, the WM roms install smoothly.

Thus WM indeed has some error check. And this goes same for the devices which came by default with Android. You can flash those babies also with tons of roms of android but you would never encounter problems such as beyond the problems of a beta or unstable cooked rom.

All in all, we need to be aware that HD2 is a dying breed and its better to buy a default android device in the long run rather then sending for repairs.
[HD2 Android NAND Development] blade_:
so,is there a standard solution?i think to buy one with bad blocks and fix it..
[HD2 Android NAND Development] GODISMYCOPILOT:
yes DATAONEXT mod

im luck ive no bad blocks