Database Users

How edit WM6 rom? WM5 ROM editing tool works badly

Hello. How edit WM6 rom in bin (BB000FF)? WM5 ROM editing tool works badly (files are unpacked not all). The size of firmware 39 mb. Firmware upload in 2 stages:
clean up the image temp buffer at 0x8C080000 Length 0x01B00000
MTTYDownloadImage "c:\wm6.bin"
:F=c:\wm6.bin
start download
S
Address 82040000Hh Length 02700000h
Format BINFS...
Format BINFS Completed. Continue to set BINFS type.
Set BINFS_TYPE success.
Before flashing new image , formatting old OS is completed!!
Start flashing new image!!!
*checksum = 0, skip checking
OEMFlashWrite(82040000h,8C080000h,01B00000h)
Update BINFS offset 0x00000000 length 0x01B00000 ...
Write BinFS Offset add=0x0 Length=0x1B00000 Checksum=0x8F6C825D
Write to BINFS partition from sector 0, length 28311552, 55296 sectors...
Read from BINFS from sector 0, length 28311552, 55296 sectors
Read complete
Read back BinFS Offset add=0x0 Length=0x1B00000 Checksum=0x8F6C825D
Update BINFS success.
*checksum = 0, skip checking
Image Download Finish
OEMFlashWrite(83B40000h,8C080000h,00C00000h)
Update BINFS offset 0x01B00000 length 0x00C00000 ...
Write BinFS Offset add=0x1B00000 Length=0xC00000 Checksum=0x5402F0E8
Write to BINFS partition from sector 55296, length 12582912, 24576 sectors...
Read from BINFS from sector 55296, length 12582912, 24576 sectors
Read complete
Read back BinFS Offset add=0x1B00000 Length=0xC00000 Checksum=0x5402F0E8
Update BINFS success.
Please reset the device to restart the program!!
DownloadImage success.

hello ? Thanks ? Please ? Good Bye ?
Anyway, tools works relatively great for cooking WM6 Romz...
Look for Artemis kitchen, all is include except htcrt for translating nb to nbh.

Need help about TASK 29

Hi,
I am frequently trying different Android NAND ROMs. Now i cant install rom. I am installing recovery what size rom needs, in magldr menu choosing 8 it saying no boot image something like that. I formated my HD2 with MTTY, report is:
Cmd>set 14 0
crc=0xD2C8DA7F.
HTCST ÚÈÒHTCE
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=3566
erase_page - error bad status: 0xB791D500
ERASE block 63 FAIL !!!
erase_page - error bad status: 0xB791D500
ERASE block 255 FAIL !!!
erase_page - error bad status: 0xB791D500
ERASE block 1536 FAIL !!!
erase_page - error bad status: 0xB791D500
ERASE block 1651 FAIL !!!
erase_page - error bad status: 0xB791D500
ERASE block 2690 FAIL !!!
erase_page - error bad status: 0xB791D500
ERASE block 2910 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
What does it mean? Leo wm 6.5 original ROM working and also i can flash with cwm 1.2 i think my HD2 has bad sectors on recovery sectors. Please help me is there any way to repair it.
Thank you.

[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.

[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.

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