Database Users

Unlock CID in a smt5600

Hello
How do I unblock the CID in a smt5600????
And how do I program another rom???

neb2567 said:
Hello
How do I unblock the CID in a smt5600????
And how do I program another rom???
Click to expand...
Click to collapse
Read Karhoe's first post and follow it entirely. It is the first topic labled 'STICKY" on the Typhoon page. Read everything first, download everything you need. Read everything again, then follow it exactly.

raskell said:
Read Karhoe's first post and follow it entirely. It is the first topic labled 'STICKY" on the Typhoon page. Read everything first, download everything you need. Read everything again, then follow it exactly.
Click to expand...
Click to collapse
Thanks....
But in the Step 9 show me this:
------------------------------------------------------------------
*Image Download Finish
OEMFlashWrite(82040000h,8C080000h,01B00000h)
Update BINFS offset 0x00000000 length 0x01B00000 ...
Write BinFS Offset add=0x0 Length=0x1B00000 Checksum=0x95EA3E42
Write to BINFS partition from sector 4, length 28311552, 55296 sectors...
Can't write to DiskOnChip, status=27
Flash BINFS failed.
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
------------------------------------------------------------------
Help becouse the smartphone isn't turn on

neb2567 said:
Thanks....
But in the Step 9 show me this:
------------------------------------------------------------------
*Image Download Finish
OEMFlashWrite(82040000h,8C080000h,01B00000h)
Update BINFS offset 0x00000000 length 0x01B00000 ...
Write BinFS Offset add=0x0 Length=0x1B00000 Checksum=0x95EA3E42
Write to BINFS partition from sector 4, length 28311552, 55296 sectors...
Can't write to DiskOnChip, status=27
Flash BINFS failed.
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
------------------------------------------------------------------
Help becouse the smartphone isn't turn on
Click to expand...
Click to collapse
U fried ur phone.......
have U checked again by pressing camera button and then inserting cable.....
no sign of life???
IF YES then ur phone is not more than a paper weight.....
I followed all steps as prescribed in kar hoe's blog, and did seuccessfull upgrade......but revived back to WM2003SE coz of RAM s**king and battery draining......

dark_prince said:
U fried ur phone.......
have U checked again by pressing camera button and then inserting cable.....
no sign of life???
IF YES then ur phone is not more than a paper weight.....
I followed all steps as prescribed in kar hoe's blog, and did seuccessfull upgrade......but revived back to WM2003SE coz of RAM s**king and battery draining......
Click to expand...
Click to collapse
Neb's phone is back online. It was not bricked. Karhoe's instructions (which I think are excellent) does not say to copy the os.bin to the root directory of c:, it infers by its command line structure that you need to put it there.

raskell said:
Neb's phone is back online. It was not bricked. Karhoe's instructions (which I think are excellent) does not say to copy the os.bin to the root directory of c:, it infers by its command line structure that you need to put it there.
Click to expand...
Click to collapse
Yes, very thanks Raskell
The problem was the file bin....
Only write a version of windows mobile 5.0...
The others have the problem....
Thanks

neb2567 said:
Yes, very thanks Raskell
The problem was the file bin....
Only write a version of windows mobile 5.0...
The others have the problem....
Thanks
Click to expand...
Click to collapse
If you have problems to flash WM6 then try again to unlock your phone. Sounds like the CID or application unlock procedure did not take correctly. The reason you can flash WM5 is most likely because it is the OEM ROM version.
http://selberg.org/2005/07/22/unlock-an-audiovox-5600-for-free/
This link is the one I used to unlock my Cingluar Audiovox SMT5600. It may help you as well

Hello, I believe that the problem that I have is to try to put it in supercid, because when I want to change it at cid=11111 he doesn't make it

BA Disconnects as Update Starts

Hi,
Apologies in advance if I'm covering old ground.
I'm trying to re-flash a WM6 rom after my previous attempt just left me with the 4 colour screen permanently and as the links to mtty1.42.rar seem to be broken at the moment I decided to re-flash with a different rom.
the problem is that even though I can get the unit into boot-loader mode and the update software appears to see the BA when it checks versions etc. as soon as I hit the upgrade button the BA screen blanks and I get Error 112: CE ROM UPDATE ERROR.
I've tried different roms, different usb ports and different versions of activesync all with the same result.
Any help on this would be great and hopefully I haven't 'bricked' the unit.
Cheers
Duncan

Do you have PH20A2 or PH20B device?
mtty utility can be found using search button

It's a PH20B.
I've now found mtty after a fair bit of searching on other forums..now to see if I can make some sense of it's commands.
A further update: it seems that I've managed to corrupt just the OS part of the ROM. I managed a radio update successfully which means all the USB connection is fine for updating. It just can't access the OS part of the ROM.
Is there anyway to manually format that area of ROM so I can in effect install over clean unit? Infortunately I can't make sense of the mtty commands and don't know what memory address and for how log I should perform the format.
Cheers Duncan

try reflashing

You should know how to use search - however here is the link
http://forum.xda-developers.com/showthread.php?t=348030&highlight=mtty
(Is that hard to put "mtty" in the search field and set BA section only? )

Further update:
Now I don't even get the 4 colour screen. After soft and hard reset I get a dead device. I can put the device into bootloader mode (serial/usb) but as soon as the update software attempts to copy the rom across the screen blanks and I get the ROM Update Error.
Now my thought is to try and flash with the original rom for the device as I have another unit available but using the link from the BA wiki for dumping the ROM doesn't work. I have also tried searching for 'ROM Dump' within the BA section of the forum but there don't seem to be any definitive instructions for this, everyone just keeps asking why not use the wiki or search funtion....
I have used the wiki and the search funstion and I seem to be the first with this situation.
Soft Reset - Nothing
Hard Reset - Nothing
Bootloader - Able to flash the radio rom but as sson as i try to flash the OS rom the screen blanks and I get Error 112: CE ROM Update Error. When I take the device out of the cradle the screen comes back on with the Serial 2.xx screen and I'm back to square one.
I've tried to use the wiki to dump an exisiting working rom but the link on the wiki is broken. I have also searched the BA forum for these intructions but they're not covered as they're already in the wiki..... or not as the case is.
I appreciate you regular users get fed up with noobs coming on and expexting you to do all the work for them but so far I've spent 3 days searching both this site and others to try and resurect my device. I'm not dumb or lazy and would love to be able to do all this myself but without instructions I'm flying somewhat blind.
Any help would be great..... please??

[off topic]
no need for apologies...
we started once like you... some are far worse...
knowing one part and boasting with air on their heads...
since you managed to explain yourself on your first post.
knowing what to search (E.G. MTTY 1.42.rar)
you definitely searched the forum before you posted AND
you stated that the links are not working... that proves it.
we are the one who is sorry because some others think
that they are high and mighty, it sometimes blurs the opinion making.
i dont like opinionated people because i admit that am one too... sometimes...
but that doesnt mean i hate them...
[on-topic]
you never told us what happened when you tried the mtty procedure.
is your last post the result of your mtty experience?
please elaborate how did you end up with that... what did you do before you soft-reset and hard-reset?

SilverSamurai,
Thanks for the quick response.
After my last 'apparently' successful re-flash with Helmi's latest WM6 rom when I hard reset the device I had nothing but a blank black screen, no power LED or anything. Soft-reset was the same. I can reset into bootloader and the PC detects the device when I place it in the cradle. The first part of the update seems to work although it never detects the current OS installed, it always says upgrade from ' ' to 'ver 6.0.0' which is wierd because it always used to say the previous OS version. When I then hit next the progress bar shows on the PC but the BA screen immediately blanks and eventually the PC gives the ROM update error.
I have managed to re-flash the radio rom in this state which proved that I still have access tho the device from the PC.
Using mtty I can run through all the commands to recover from the 4 colour lines screen (even though I'm beyond that point).
USB>set 14 0
HTCST ÚÈÒHTCEUSB>task 28
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>task 0
USB>
It's almost as if the last flash didn't complete and has left the area for the OS 'dirty' with what ever it did manage to flash. What I was hoping to try was to re-format the entire OS section of memory and then try to re-flash again. Using mtty it says you can format sections of memory by stating a start address and the length you want to format but I don't have clue what these should be.
I've tried flashing with WM6, WM5 and a compatible version of 2003 with the same result every time. I would like to dump a rom from another BA I have and try with that but as mentioned earlier the link for that is down at the moment.
I think that's about it. If you need any more info let me know.
Many thanks
Duncan.

let's relist the things you did.
USB>set 14 0
Click to expand...
Click to collapse
1. start OS after a reset
result:
HTCST ÚÈÒHTCE
USB>task 28
Click to expand...
Click to collapse
2. format doc (Disc-On-Chip)
result:
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>task 0
Click to expand...
Click to collapse
3. do hardware clear boot.
Click to expand...
Click to collapse
since i dont want to experiment with my sole BA...
i tried to search for solution...
and with some of my computer instincts i came up with this suggestion...
try this command before "task 28"
"task 7 0" <-- this is the "Do flash ROM lock/unlock" command
"task 2a" <-- fix bad blocks on MFG bootloader and Storage
then try to reflash your BA.
my sources one | two
although it's not BA but i think mtty commands are generic.
it's worth a try.

SS,
Still no joy, it's exactly as it was before.
Just reading through some more posts for bootloader ant it seems at least one other person has the same problem - http://forum.xda-developers.com/showthread.php?t=345181&highlight=bootloader and no resolution posted for that either.
I think I may have got it beyond the point of return.
I've just tried to flash from the blank screen I end up with from the initial attempt and it still detects the device but fails in exactly the same way.

awww... im sorry to hear that.
but dont lose hope.
i'll try to read some more and search for solutions.
and i hope someone with the same problem as
yours that had their BA fixed comes to the foreground.
[off topic]
hmm... come to think of it... we're both Marvel SuperVillains

SilverSamurai said:
awww... im sorry to hear that.
but dont lose hope.
i'll try to read some more and search for solutions.
and i hope someone with the same problem as
yours that had their BA fixed comes to the foreground.
[off topic]
hmm... come to think of it... we're both Marvel SuperVillains
Click to expand...
Click to collapse
These steps are from my notes. Follow these steps. It worked for me last time i tried (3 months back)
2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
3. put your device into Bootloader Mode by pressing Power + Record Button and Soft Reset.
4. Run mtty (from downloaded) Choose WCEUSBSH001
5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.
6. type "task 28" to get your device formatted
7. type "task 0" to ask your device reboot
8. take the device out of the cradle, and manually reset it if it does not do that already.

i think he did all of those already,
that's why i posted this in response to his mtty experience.
wouldnt hurt to try it again though.

A bit more info:
I tried the mtty solution again but still the same result.
I finally managed to find the instructions for dumping and exisiting rom to SD card and pulled one from a working unit. I put the card into the faulty BA and booted into bootloader. Pressed 'Power Button' to flash from card and it appeared it was going to work........ until it got to 12% then it failed with the message 'Download Fail'. So still no better off.
What I'm going to try now as it seems anything is worth a try is use the address ranges used to dump the rom to try and format all 3 sections. See if that will give me a clean base to try and re-flash from the sd card. My only worry is if it will format the section of ROM used to store the bootloader info.
I'll post my results shortly.

Now I need to know how to get the bootloader password to enable me to use the 'erase' command through mtty.
The hunt coninues....

Yet more developments.
As the update from SD failed I thought I'd see if it was possible to dump the current contents of the rom to SD using the following
“d2s 80000000 02000000“
“d2s 60000000 00300000 sd a“
“d2s 70000000 01080000 sd a“
The first 2 commands completed fine and checksum was OK. On the 3r command 'd2s 70000000 01080000 sd a' it errored with the following result
USB>d2s 70000000 01080000 sd a
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SDetected one card
SD:ready for transfer OK
pc->drive.total_lba=1E8000
pc->drive.num_heads=0
pc->drive.sec_p_track=0
pc->drive.num_cylinders=0
pc->drive.block_size=200
pc->drive.features=0
pc->drive.RCA=B368
pc->drive.drv_type=40000000
pc->drive.securedAreaSize=0
pc->drive.securityDrv=0
pc->drive.busWidth=1
pc->drive.erasedSize=0
Total card size=3D000000
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
DOC_ReadBinary is fail: dwStartAddress=0,dwReadSize=40000.
DOC_ReadBinary is fail: dwStartAddress=0,dwTempReadLength=40000.
*DOC_ReadBinary is fail: dwStartAddress=40000,dwTempReadLength=40000.
*****************************************************************dwCheckSum of Storage=95609D16
cSectionNum=2
psImageSectionInfo[cSectionNum].dwCheckSum=0
psImageSectionInfo[cSectionNum].dwLength=1080000
Stored image of SD/MMC card checksum error!
Now my guess is the Doc_Read_Fail bits are the corrupt part of the rom. If I can find a way to repair these I could then try re-flashing the rom.

what was "task 2a"'s result?
i think that's the chkdsk option of mtty.
we're dissecting the innards of the bootloader.
little by little as we go along the way...
im learning something, i hope you can find the fix for your problem.

SilverSamurai,
Thanks for the help you gave but the unit has finally had enough and totally locked. No power or anything no matter how I try to reset it. I've tried charging for hours, discharging for hours, left the battery out for hours but to no avail. It seemed to take exception to me dumping the rom contents to the SD card. Maybe there was a hardware problem ?? Not sure.
I'll have to see if I can wangle another unit from the company I work for as we're currently selling a bunch that were purchased for a failed IT project on ebay.

it was sad to hear/read that.
anyways. at least we tried to revive it. but dont throw it away.
maybe someday there will be ways how to ressurect your BA.
Happy Computing! err... Mobile Computing!

Help!! Phone keeps acting possessed!!!

Ok, so i have a friends HD2 right now because she was having issues with it. After using it with the stock OS i immediately found the phone doing random tasks that i didnt initiate. For example, i would be in messages or email and it would just start calling the last dialed number over and over again. Id end the call and it would just start another. It would also just open voice commands without ever even touching the phone.
So i decided it was probably a OS bug or something, so i Installed a custom WINMO ROM and put android on it. It ran great for 2 days and it seemed i had fixed it. WRONG!! The bug is still there! What could be causing this issue?
I thought maybe it was the radio, but i flashed like 4 of them and it is still possessed!!
Anyone have any ideas???
Thanks

JohnnyVolcom5 said:
Ok, so i have a friends HD2 right now because she was having issues with it. After using it with the stock OS i immediately found the phone doing random tasks that i didnt initiate. For example, i would be in messages or email and it would just start calling the last dialed number over and over again. Id end the call and it would just start another. It would also just open voice commands without ever even touching the phone.
So i decided it was probably a OS bug or something, so i Installed a custom WINMO ROM and put android on it. It ran great for 2 days and it seemed i had fixed it. WRONG!! The bug is still there! What could be causing this issue?
I thought maybe it was the radio, but i flashed like 4 of them and it is still possessed!!
Anyone have any ideas???
Thanks
Click to expand...
Click to collapse
I would suggest flash to one radio, 2.15.50.14, do a task 29(very important to get rid of any traces of old files/data in your internal rom partition) then depending which way you're going, winmmo or android, flash that.

Just had to read the thread with a title like that
Roloracer has hit it on the nail, just follow his instructions, and don't forget to format the sd card on the PC before putting it back in the phone
In my house its only the wife that acts possessed, lol

johnerz said:
Just had to read the thread with a title like that
Roloracer has hit it on the nail, just follow his instructions, and don't forget to format the sd card on the PC before putting it back in the phone
In my house its only the wife that acts possessed, lol
Click to expand...
Click to collapse
feel you in the wife part! lol
I would recommend him to format the sd card in CWM since it's way easier to do over the pc way.
In CWM go to format card and select 1024 mb with a 0 swap.

roloracer said:
I would suggest flash to one radio, 2.15.50.14, do a task 29(very important to get rid of any traces of old files/data in your internal rom partition) then depending which way you're going, winmmo or android, flash that.
Click to expand...
Click to collapse
Well thats what radio i initially flashed and is the radio that is on there now.
What is task 29? (sorry, im fairly new to this)
As to formatting SD card, i did that on MY HD2 and it is running NAND DL Desire by Dandiest. I formatted in Gnome Parition. Made a 1536 partition ext4, then broke that up into another ext4 partition at 512.
Is this what i should do on her phone? She likes having both WINMO and Android.
Thanks for all the replies and help!!

JohnnyVolcom5 said:
Well thats what radio i initially flashed and is the radio that is on there now.
What is task 29? (sorry, im fairly new to this)
As to formatting SD card, i did that on MY HD2 and it is running NAND DL Desire by Dandiest. I formatted in Gnome Parition. Made a 1536 partition ext4, then broke that up into another ext4 partition at 512.
Is this what i should do on her phone? She likes having both WINMO and Android.
Thanks for all the replies and help!!
Click to expand...
Click to collapse
Task 29 HERE
I suggest you run the attached Task 29 .exe together in a folder with the
.nbh file of Radio 2.15.50.14
procedure: (HSPL a prerequisite)
1. take the Task 29.exe and the .nbh file of Radio 2.15.50.14 put these two in a folder
2. Enter bootlloader (with device off, long press volume down while briefly pressing power button)
3. connect device to pc via usb
4. run Task 29 as administrator (or just double click it)
5. dont panic if your screen goes completely while, just remove battery
6. put back battery, enter bootloader again and flash any custom winmo ROM

jigners said:
Task 29 HERE
I suggest you run the attached Task 29 .exe together in a folder with the
.nbh file of Radio 2.15.50.14
procedure: (HSPL a prerequisite)
1. take the Task 29.exe and the .nbh file of Radio 2.15.50.14 put these two in a folder
2. Enter bootlloader (with device off, long press volume down while briefly pressing power button)
3. connect device to pc via usb
4. run Task 29 as administrator (or just double click it)
5. dont panic if your screen goes completely while, just remove battery
6. put back battery, enter bootloader again and flash any custom winmo ROM
Click to expand...
Click to collapse
Thanks, i found a video and a thread here.
http://forum.xda-developers.com/showthread.php?t=644781
I will update everyone in a couple days. (for some reason after each new install it takes awhile for the phone to become "Possessed" again. Last one worked great for 2 days and then BOOM back to Exorcist BS!!!
Thanks again everyone!

jigners said:
6. put back battery, enter bootloader again and flash any custom winmo ROM
Click to expand...
Click to collapse
Couldnt I just run Task29 with radio, (it will still be HSPL right?) then flash MAGLDR and just flash a NAND android rom?
My guess is yes, but would like some verification before i do ir
NEVERMIND...I just read your NAND guide in your sig....(which i used to on MY hd2, awesome guide and thanks BTW)
I will explore a little more before i ask questions from now on.
Thanks again Guys. and i will still update as to if it works!

if you have the radio already flashed , you don't need to flash it ever again!!! even after task 29, you don't need to, task 29 doesn't touch where your radio is stored.
I flashed my phone to 2.15 radio back in last november and task 29 about 20 times since then and never had to mess with the radio.

[Q] cannot install radio version on my hd2

hi...i have a big problem...i cannot install an OS on my htc...especially a radio version...i receive an error at 100% saying that its not compatible or something like that....if i install a 6.5 Windows rom the phone won't start...so i'm guessing it is because of the radio....please someone help...tnx

Check if you phone gets hot... if yes then your phone has heating issues.
te be sure try this:
put you phone in fridge for 5-10 min ( take out battery, sim card, memory card and put phone in a bag to protect from water ), than try to install ( usb method or sd card method - i prefer last one)... probly everything will go ok but phone still wont boot up - if it does then its not heating issues.
I hope it works
PS: for heating issues visit link provided in my signature ( Solving the thermal problems of HD2 ) .

hi thx for the advice...but i do not think thats the problem now....maybe it was when it had an operating system and it kept restarting...but now i cant put on him a radio version...to install a os rom i can...but freezes in the logo screen...so i guees i need to install radio on it so the os will start..but i cant(....and i also tried to delete the memory with mtty and it failed also..at task 29 command or task 28 55aa says this:Cmd>set 14 0
crc=0xD2C8DA7F.
HTCST ÚÈÒHTCE
Cmd>task 28 55aa
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
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>
so i do not know what to do...

in the mtty thread, post 1, it says to ignore those error messages, , they are normal. MTTY (and task29) doesnt touch teh area of NAND where the radio is located anyway.
You seem to have what is sometimes referred to as a stuck radio, which doesnt work and wont flash.
Sorry, there is no actual fix for this, and the consensus seems to be that it is corrupt / bad NAND blocks.
The only solution which occasionally seems to work (but only in some cases) is cooling the phone as mentioned above.
Prepare your CORRECT stock rom on an sd card, phone into a bag in the fridge/freezer for long enough for it to be cold, then quickly sd card in, into bootloader, start it flashing, hope it takes. Ive seen people say it took on the 5th/10th/20th attempt, but for many it never takes.

ok thx...ill try the cooling method....regarding the mtty post...i've read it too...but there wrote to ignore errors...in my case says tag not found!not clear storage....like some kind of memory error...

QUOTE from mtty thread post 1
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Click to expand...
Click to collapse

samsamuel said:
... and the consensus seems to be that it is corrupt / bad NAND blocks.
Click to expand...
Click to collapse
totally agree with " samsamuel ".
About fixing a i told visit that thread because we are trying to find a solution about it... in my case i think it worked... my hd2 had same problem always filed at 8% - 9%, i tried fridge method everything went ok BUT phone didnt boot up it - stock at htc ... i installed android it booted but if i watch a movie or played games it will freeze and restart... then i installed wp7 same as android... many times it had fatal hit and wont boot until it cooled down, but now im able to watch a video @480p 3 times - length 80 min. im unable to flash stock rom because my volume buttons and keypad buttons dont work.

rzvcool003 said:
hi...i have a big problem...i cannot install an OS on my htc...especially a radio version...i receive an error at 100% saying that its not compatible or something like that....if i install a 6.5 Windows rom the phone won't start...so i'm guessing it is because of the radio....please someone help...tnx
Click to expand...
Click to collapse
why....do...you...type...like...this??

Fridge trick does work!
Hey guys, I got one TMOUS HD2 which boots randomly and won't flash any radio.
I tried everything ...HD2 toolkit, mtty , stock rom etc...nothing.
Last put the darn thing in the freezer for 30 minutes (cannot tell the temp )
And yeeeeeeeeeeeeeesssssssssssssssssss
IT WORKS!
EVERYONE WITH A STUCK RADIO SHOULD TRY IT.

[Q] problem while loading android

got nearly every thing done with my HD2 EU device
installed stock rom 6.5
HSPL 2.08
Radio_Leo_2.15.50.14
Magldr 1.13
then USB flasher
instillation done for any rom
then device restart i choose Boot AD NAND
then i get
Android load at 11800000
from NAND
yaffs2 part is /system
Load zImage
Load initrd.gz
[K]11808000:224ac0 12200000:281E6C
Load done!
123456
Go Go Go!
another thing to mention
tried to install WP7 using the same way
loaded successfully to the welcome screen
then when i touch screen to go on
it doesn't recognize that i did touched the screen
when i press the hard keys like volume or power
it's working

Ridil said:
got nearly every thing done with my HD2 EU device
installed stock rom 6.5
HSPL 2.08
Radio_Leo_2.15.50.14
Magldr 1.13
then USB flasher
instillation done for any rom
then device restart i choose Boot AD NAND
Click to expand...
Click to collapse
After flashing ROM with USB flasher, just reboot your phone without enter the magldr menu. just reboot and dont press any key.
Android should boot automatically.
Did you try this?

Ridil said:
got nearly every thing done with my HD2 EU device
installed stock rom 6.5
HSPL 2.08
Radio_Leo_2.15.50.14
Magldr 1.13
then USB flasher
instillation done for any rom
then device restart i choose Boot AD NAND
then i get
Android load at 11800000
from NAND
yaffs2 part is /system
Load zImage
Load initrd.gz
[K]11808000:224ac0 12200000:281E6C
Load done!
123456
Go Go Go!
another thing to mention
tried to install WP7 using the same way
loaded successfully to the welcome screen
then when i touch screen to go on
it doesn't recognize that i did touched the screen
when i press the hard keys like volume or power
it's working
Click to expand...
Click to collapse
By the way, flashing the DFT Stock ROM via USB flasher is outdated, DAF.exe is no longer used to flash ROMs, CWM is. I would recommend looking into using that as well.

Nigeldg said:
By the way, flashing the DFT Stock ROM via USB flasher is outdated, DAF.exe is no longer used to flash ROMs, CWM is. I would recommend looking into using that as well.
Click to expand...
Click to collapse
that is the other problem ,, till installing magldr every thing is okey
after that i try to install recovery or what ever i install it's always fail to run it
after recovery it also stops at Go Go Go

Ridil said:
that is the other problem ,, till installing magldr every thing is okey
after that i try to install recovery or what ever i install it's always fail to run it
after recovery it also stops at Go Go Go
Click to expand...
Click to collapse
try flashing recovery 5.0.2.6 or download HD2 TOOLKIT,best program out there,everything u need all on page,so easy to use

i did used HD2 toolkit
and installed CLK
then recovery from HD2 toolkit
and that error what i got
flash_read_image : failed (511 errors )
Error : cannot read recovery header
at the last line
cmdline : no console suspend = 1 wire.search_count=5 clk=1.4.0.1

i have the same problem ...
-> Android load at 11800000
from NAND
yaffs2 part is /system
Load zImage
Load initrd.gz
[K]11808000:224ac0 12200000:281E6C
Load done!
123456
Go Go Go!
another thing to mention
tried to install WP7 using the same way
loaded successfully to the welcome screen
then when i touch screen to go on
it doesn't recognize that i did touched the screen
when i press the hard keys like volume or power
it's working
i installed other android rom tried other partitions like 150/ 200/ 250 and tried various rom, still stuck at 123456, gogogo, tried to boot up from sd card, but i dunno what are the files that are supposed to be on the sd card, so its still stuck at 123456, gogogo too
so what can i do now ..

mail2richard said:
i have the same problem ...
-> Android load at 11800000
from NAND
yaffs2 part is /system
Load zImage
Load initrd.gz
[K]11808000:224ac0 12200000:281E6C
Load done!
123456
Go Go Go!
another thing to mention
tried to install WP7 using the same way
loaded successfully to the welcome screen
then when i touch screen to go on
it doesn't recognize that i did touched the screen
when i press the hard keys like volume or power
it's working
i installed other android rom tried other partitions like 150/ 200/ 250 and tried various rom, still stuck at 123456, gogogo, tried to boot up from sd card, but i dunno what are the files that are supposed to be on the sd card, so its still stuck at 123456, gogogo too
so what can i do now ..
Click to expand...
Click to collapse
format ur sd card and put the rom bk on ur sd card then try again,normally does the trick

what are the files on the SD card?
most of the time after i downloaded a zipped rom .. i have no idea what other files is needed.. also my clockworkmod dun appear to be working well even after a few installation (can i have a link) and i can only install using DAF.exe ... any DAF andriod rom 2.3 and up to recommend ? Thanks

mail2richard said:
what are the files on the SD card?
most of the time after i downloaded a zipped rom .. i have no idea what other files is needed.. also my clockworkmod dun appear to be working well even after a few installation (can i have a link) and i can only install using DAF.exe ... any DAF andriod rom 2.3 and up to recommend ? Thanks
Click to expand...
Click to collapse
running from daf is no more lol,are u using clkwork or magldr,either way the rom has to be on ur sd card in zip format obviously lol and thats it,but when u download a rom make sure u download the right 1,it shud say if its for clkwrk or magldr,also im using recovery 5.0.2.6,also does the rom u download require sd-ext(partitioning ur sd card) as for rom choice,i'd go for TBD ROM v.2.3,FU#KING SUPERB ROM,i've had it for a few days now,flashed the red theme,not been this happy with my fone for along time,i won't be flashing anything else for along time lol

Ridil said:
i did used HD2 toolkit
and installed CLK
then recovery from HD2 toolkit
and that error what i got
flash_read_image : failed (511 errors )
Error : cannot read recovery header
at the last line
cmdline : no console suspend = 1 wire.search_count=5 clk=1.4.0.1
Click to expand...
Click to collapse
i have the same issue.. any solutions ?

Same here... any solutions???

same here... what is the problem actualy?

i have the same problem~
>.<~~~
i think it is a hardware problem coz i open my hd2 in order to change the screen then start this problem.
but i dont understand why i can use and flash to WM 6.5 it's no problem.....
only Android...........
i help my Family (5 HD2)flash HD2 to Android many many times.~
i dont think is operating problem.......
i hv try MTTY but no use.
The following is a reference, we can c "task 29" is Abnormal.
You can also upload to share~
Cmd>set 14
crc=0xD2C8DA7F.
HTCST 硜浶TCE
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: 0xB791EA20
ERASE block 3227 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
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: 0xB791EA20
ERASE block 3227 FAIL !!!
Write 0xFF start page=0x7C40, total page=0x383C0
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
Cmd>
Click to expand...
Click to collapse