Database Users

[Q] Unable to flash ROM, vibrates 7 times sometimes or freezes during update

I purchased a non-working HD2 phone thinking I could fix it based on the description the seller gave, but I received it today and after messing around for a bit I'm starting to have some doubts.
The phone came with MAGLDR v1.13 on it already. First thing I did was try to install an Android ROM since it was the easiest. Unfortunately I had no microSD card for the phone so I used a direct install DFT ROM (http://forum.xda-developers.com/showthread.php?t=1062881 is the one I used). After installing it and restarting the phone, the ROM did not boot and MAGLDR faulted when booting on an error "0x1E Fatal Hit 1".
So then I decided to format the phone completely, reinstall SPL and try doing everything over again. That's when I ran into problems. The bootloader (2.08 SPL) loaded into the HD2 just fine, but now any ROM or RADIO I try to upload to the HD2 from my computer, fails. It just stops at 20-30% and doesn't increase anymore when installing a ROM. Sometimes it just stays at 0% and doesn't increase. Also, other times the HD2 vibrates 7 times when the installation of the ROM is beginning. I'm not exactly sure what the 7 vibrations mean, but after googling it sounds like hardware issues.
I fear there are bad sectors in the NAND. Is there any way to check for sure? Is there any way to repair those bad sectors? Are there any other suggestions that I should try?
EDIT:
Here is the output after running a few commands on MTTY, not looking good, right?
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=7662
erase_page - error bad status: 0xB791E960
ERASE block 2467 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3478 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3572 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3776 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3782 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 4297 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 5190 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 5204 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 5950 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 6023 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 6070 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 7173 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>task 28
Format start
Fill RSVD information for block 497 to 530
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=7662
erase_page - error bad status: 0xB791E960
ERASE block 2467 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3478 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3572 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3776 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3782 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 4297 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 5190 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 5204 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 5950 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 6023 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 6070 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 7173 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>
Click to expand...
Click to collapse
Please give me some advice, someone...

Make sure you have hard spl installed then try a Task29 that should format nand and if all goes well flash magldr (wp7 or android) or flash a lite wm6.5 rom
I recommend If you get past the task29 flash a lite wm6.5 since that actually is made for the hd2
Sent from my HD7 T9292 using XDA Windows Phone 7 App

I tried to do a task29 and it freezes in random spots...58%, 74%...then it worked!
But unfortunately the same thing happens when flashing a ROM...it keeps freezing in random places and I have yet to get it to 100% once...but I'll keep trying.
This is definitely indicative of bad sectors in the NAND memory, right? Is it possible to replace the memory if I open up the HD2, or would it be too much work? Has anyone ever done this?

That mimicks a bad harddrive... Freezes then eventually finishes but then when installing (flashing) its true colors show... If you can get stock SPL installed check if it has warranty and send it off to HTC.. Replacing internal parts are hard enough but when it comes to chips its not worth it
Sent from my HD7 T9292 using XDA Windows Phone 7 App

hakuchi18v said:
That mimicks a bad harddrive... Freezes then eventually finishes but then when installing (flashing) its true colors show... If you can get stock SPL installed check if it has warranty and send it off to HTC.. Replacing internal parts are hard enough but when it comes to chips its not worth it
Sent from my HD7 T9292 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Meh...not worth it, there is also a crack on the screen. I think I will just get another one off ebay, they are going for $150-$200 nowadays. I'll just make sure not to make the same mistake again, don't buy a product that is "for parts or not working" and assume it can be fixed regardless of the condition described by the seller.
Thanks for your help!

iwin2000 said:
Meh...not worth it, there is also a crack on the screen. I think I will just get another one off ebay, they are going for $150-$200 nowadays. I'll just make sure not to make the same mistake again, don't buy a product that is "for parts or not working" and assume it can be fixed regardless of the condition described by the seller.
Thanks for your help!
Click to expand...
Click to collapse
Your Welcome... Read the Descriptions! lol

Just for anyone reading this thread. Going by what XDA member facdemol says in his very hardware descriptive thread "Solving the thermal problems of HD2 or other snapdragon powered devices" the actual chips in the HD2 can not be replaced because they have some kind of resin surrounding the chips to help hold them in place. And it would take a very high temperature to make the resin loosen up enough to remove the chips. The high temperatures will ruin the main board.

mtty 1.42 problem????????

When i typed "task 29" i got error message below
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=3566
erase_page - error bad status: 0xB791D500
ERASE block 1971 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
can everyone give me a suggestion?

cheasamnang said:
can everyone give me a suggestion?
Click to expand...
Click to collapse
Yea, go read post 1 of the mtty thread.

Thanks you

[Q] HD2 fails to boot any rom

Hi guys,
could you please help me recover from a -non very smart- action I have performed and stack in the familiar white background with green htc...
I was using HSPL4 trying various custom roms. Once I 've decided to load
_HTC HD2_RUU_Leo_HTC_ELL_1.48.482.4_Radio_Signed_15.28. 50.07U_2.05.51.05_2_Ship through SD card (LEOIMG.nbh) the device stuck on white background+ green htc logo. When I enter to the bootloader, I read
[email protected] HX-BC (instead of PB81100 HX-BC)
SPL-1.42.0000 XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x30
The result is that all attempts to load ANY rom, ship or custom fails. I believe that my attempt to go to an original rom, overwritten COTULLA's HSPL boot-loader back to the protected defaults. (most probably in language ELL, sourced from Vodafone)
When I try to upload any rom I get "incompatible device ID"
Only HSPL (one) completed with "we 've hacked it" and then the device reboots back to white screen. Boot loader remains the same.
All other versions of HSPl (2,3 and 4) fail. Same with wipe task 29
Also tried to load through SD. Some roms stick to "loading" some othes fails with "68002"
I 'm just a step behind JTAG-ing my phone (but I 'll leave that for my last resort)
any suggestion will be appreciated.
thnx.
P.S. I accidentally asked the same question to an irrelevant thread but I don't know how to move it here. Sorry for the duplicate.

supplementary data that might help..
"info 0" from mtty reports
Cmd>info 0
Platform Model ID:[email protected]
Platform HW Board ID:4, UNKNOWN
I have also tried
Cmd>set 14 0
Cmd>task 29
Cmd>task 8
and try to load a stock rom, but didn't succeed
"info 8" now reports
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 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
OS NOT FOUND !!!
I'm suspecting that the corrupt "Platform Model ID:[email protected] " is causing all the trouble.
Can I change the model ID through mtty console?
if not any ideas ??
thnx.

memoryic said:
supplementary data that might help..
"info 0" from mtty reports
Cmd>info 0
Platform Model ID:[email protected]
Platform HW Board ID:4, UNKNOWN
I have also tried
Cmd>set 14 0
Cmd>task 29
Cmd>task 8
and try to load a stock rom, but didn't succeed
"info 8" now reports
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 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
OS NOT FOUND !!!
I'm suspecting that the corrupt "Platform Model ID:[email protected] " is causing all the trouble.
Can I change the model ID through mtty console?
if not any ideas ??
thnx.
Click to expand...
Click to collapse
Try this from mtty console:
cmd> task 2a
cmd > task 29
cmd> task 8
Not guaranteeing anything but worth a try!

Hi Shanman-2 and thank you for your support. While waiting for some ideas, I have already found and test the commands you suggest.
Result,
The device refused a couple of stock roms I ve tried, but eventually managed to load _HTC HD2_RUU_Leo_HTC_ELL_1.48.482.4_Radio_Signed_15.28. 50.07U_2.05.51.05_2_Ship through SD. Bootloader displayed the same (corrupted) Device ID
[email protected] HX-BC (instead of PB81100 HX-BC)
SPL-1.42.0000 XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x30
The normal booting mode stacks is white screen - green HTC logo.
So I 've repeated the procedure willing to try another stock rom
these are the last messages....
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: 0xB791D500
ERASE block 813 FAIL !!!
erase_page - error bad status: 0xB791D500
ERASE block 2385 FAIL !!!
erase_page - error bad status: 0xB791D500
ERASE block 2983 FAIL !!!
erase_page - error bad status: 0xB791D500
ERASE block 3212 FAIL !!!
Write 0xFF start page=0x7C40, total page=0x383C0
SPL check fail, actual:0xFFFFFFFF, expected:0x30353638
Wrong image, flash rejected
format ALL, restore SPL failed, addr=0x50000000
Format ALL end
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=3566
erase_page - error bad status: 0xB791D500
ERASE block 813 FAIL !!!
erase_page - error bad status: 0xB791D500
ERASE block 2385 FAIL !!!
erase_page - error bad status: 0xB791D500
ERASE block 2983 FAIL !!!
erase_page - error bad status: 0xB791D500
ERASE block 3212 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>task 8
... before my phone completely dies!
I 'm not sad I killed my phone, I 'm sad I 've tried everything possible to keep it alive but I failed. I have to admit I learn quite a lot of things hacking that poor thing.
Now I 'll get some rest and tomorrow I 'll start to gather info on JTAG resurrection.
Does anyone manage to D.I.Y. ?
thx de memoryic

Sorry to hear that.
Best guy to contact on xda that I know is T-Magnolia, he should be able to advise you about J-Tag.
Best of luck with it.
Sent from my NexusHD2 using xda premium

shanman-2 said:
Sorry to hear that.
Best guy to contact on xda that I know is T-Magnolia, he should be able to advise you about J-Tag.
Best of luck with it.
Click to expand...
Click to collapse
Thanks for the info, I 'll definitely need some advice (and the nb code to load). I 'll post about the progress..
memoryIC.

strange prob: cannot pass the tri color screen
Im sorry to post here but i have a strange problem that my hd2 cannot pass the tri color boot screen, even i have replaced the buttons.
I was previously running android on magldr and it suddenly crashed, since then, i am stuck on tri color. i ve reverted back to the stock from computer and from sd but still the same. Reverting back to hspl2.08, installed many things like task29, clk, mag, custom wm6.5, everything goes fine installation, but the damn cannot boot into any os. I am stuck at tri color screen.
one thing i have noticed that even after i install stock wm6.5, it automatically boots to tri color when connected to a charger, while it is not supposed to do so when mag is removed with task 29 and stock wm or custom.
I am advanced user and have used hd2 for 2 years and i know things like stock and spl and all that. Well i have Tmous with hspl2.08 and radio 2.14.50.
i think this is magldr related issue(since it is booting directly when a charger is connected).
Plz help....i dont want to miss this awesome device while another one of mine is complete brick dead.

[Q] bad blocks

i have been experiencing too much instability with nearly all the roms i flash even though i do exactly as the instructions say in each and every rom ... i searched about everything talking about instability ... Task 29 flash maglrd flash cwm with the sizes said in the rom's thread but always getting instability in the rom even though most of people reporting that the rom is stable and working great .... i thought it might be bad blocks and searched for how to check for bad blocks but couldn't find easy way to find out if i got bad blocks or not .... i did try several ways of checking but not getting the same results the thread is talking about .... so can someone plz help me find out whats wrong with my phone??!!
i know that there is too many threads talking about bad blocks and so on and i did nearly read all of them but still cant find a solution

Search for the" definitive mtty thread", there you will find out how to find out if you have bad blocks.
Haven't got link because I am not near my PC.
Edit: you might try and increase the system partition by 5 or 10mb when installing any ROM to compensate for bad blocks (if that is the problem).
Sent from my NexusHD2 using xda premium

well i read all mtty posts he is talking about clean up and so on but none of the commands in his post talking about check for bad blocks .... thanx for help anyways ... i'll give mtty method but is there any method or could give me a report of total internal memory used not used bad blocks system and so on.... as the scan disc in computers do when u scan ur hdd

Once you have mtty set up, the command is - info 8
This will tell you whether there are bad blocks or not!
Edit: This is what mine shows,
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 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 1680 (0x690) is reversed block
BLOCK 1681 (0x691) is reversed block
BLOCK 1979 (0x7BB) is reversed block
Partition[0], type=0x23, start=0x2, total=0xBE
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) = 0x60600
CE CheckSum Length(without sector info) = 0x60000
Fortunately I have the Hynix chipset which according to my research is less prone to bad blocks than the Samsung chipset. To check which one you have go into bootloader and on the first line HX-BC is Hynix and SS-BC is the Samsung chipset.
Sent from my NexusHD2 using xda premium

results i dont understand
hey how ru? ... thanx for help well ... i did all what was said in mtty thread and i got these results
i tried task 8 i got my phone restarted then task 28 then task 29 and thats the results i got
Cmd>task 28
Format start
Fill RSVD information for block 497 to 530
Storage start sector=0x0, total sector=0x0
Storage start block=33, total block=0
Bypass ExtROM Block (160+10)
Total Bad Block in CE: 0
Erase physical block from 532 to 344
ExtROM: Erase physical block from 3910 to 4080
si backup: Erase physical block from 4080 to 4096
Format end
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=3566
erase_page - error bad status: 0xB791E960
ERASE block 1726 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1911 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1913 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3338 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
it said total bad block is zero in task 28 why did it say erase block fail in task 29?!
and if its really clean without any bad blocks .... why am i always getting instability with all the roms im trying to flash even though i do exactly as the instructions say

Did you try "Info 8"?
Put the results up here
Sent from my NexusHD2 using xda premium

yep it restarted my phone ... didnt give me any results just restarted the phone ...

Not "task 8", "info 8" !!
Also the fact that task 29 fails is not a good omen!
Sent from my NexusHD2 using xda premium

Actually if you read the mtty thread you'll see that you should expect some errors during task29.ifyou get different errors than the ones mentioned in that thread, then there's a problem.
Also, when you talk about the process (task29,magldr,blahblah) at no point did you mention cleaning up the sd card,, there are things on both the fat32 and the ext that can potentially cause problems If left over from previous roms.
Also also,, sim cards can cause instability across allroms. Got another one to test with for a few hours?

wiammaren said:
i'll give mtty method but is there any method or could give me a report of total internal memory used not used bad blocks system and soon
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Open a terminal emulator and type: df and hit return.
This will give you a list of each partition size and used space.

you can use native sd!

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 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 972 (0x3CC) is reversed block
BLOCK 973 (0x3CD) is reversed block
BLOCK 974 (0x3CE) is reversed block
BLOCK 975 (0x3CF) is reversed block
BLOCK 976 (0x3D0) is reversed block
BLOCK 977 (0x3D1) is reversed block
BLOCK 978 (0x3D2) is reversed block
BLOCK 979 (0x3D3) is reversed block
BLOCK 980 (0x3D4) is reversed block
BLOCK 1726 (0x6BE) is bad block
BLOCK 1911 (0x777) is bad block
BLOCK 1913 (0x779) 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>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=3566
erase_page - error bad status: 0xB791E960
ERASE block 1726 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1911 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1913 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3338 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>task 28
Format start
Fill RSVD information for block 497 to 530
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
this is all the info im getting ... info 8 , task 29 task 28

samsamuel said:
Actually if you read the mtty thread you'll see that you should expect some errors during task29.ifyou get different errors than the ones mentioned in that thread, then there's a problem.
Also, when you talk about the process (task29,magldr,blahblah) at no point did you mention cleaning up the sd card,, there are things on both the fat32 and the ext that can potentially cause problems If left over from previous roms.
Also also,, sim cards can cause instability across allroms. Got another one to test with for a few hours?
Click to expand...
Click to collapse
before each flash i format my sd card and repartition it

Mtty

I have an Hd2 that was running Android JB. It froze one day and would not come back on. Since then I have been trying all methods to flash the Stock ROm and other android roms but kept getting the 1Efatal hit error. I ran Mtty and this is what I got:
Cmd>set 14 0
Cmd>set 14 0
crc=0xD2C8DA7F.
HTCST ÚÈÒHTCE
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=7662
erase_page - error bad status: 0xB791E960
ERASE block 2284 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 2395 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 2933 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 4078 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 7186 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>
Is there a way to correct these bad blocks or is the phone completely dead?

josephh71 said:
I have an Hd2 that was running Android JB. It froze one day and would not come back on. Since then I have been trying all methods to flash the Stock ROm and other android roms but kept getting the 1Efatal hit error. I ran Mtty and this is what I got:
Cmd>set 14 0
Cmd>set 14 0
crc=0xD2C8DA7F.
HTCST ÚÈÒHTCE
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=7662
erase_page - error bad status: 0xB791E960
ERASE block 2284 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 2395 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 2933 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 4078 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 7186 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>
Is there a way to correct these bad blocks or is the phone completely dead?
Click to expand...
Click to collapse
Also anyone thinking of asking either of the following questions:
1: "After task 29, I get this output in MTTY: Total Bad Block in CE: x"
2: "After task 29, I get this output in MTTY:
ERASE block xxx FAIL !!!
ERASE block xxx FAIL !!!"
(where x is a random number)
This has been asked 100+ times in this thread so this is the final time I will answer:
IT MEANS NOTHING..NADA..ZIP! I have not experienced ANY problem with this output...Please stop asking!
The above is taken from "The Definitive mtty thread".
the command for checking for bad blocks is..Cmd>info 8