I decided it's best to open another topic, as the subject has changed and the other topic seems to have died more or less.
I have found out that the problem with my HD2 is that the radio is corrupted. However, I failed every time I tried flashing a new radio, even though I tried both USB and SD card methods.
Is there any way I can format the part of the memory where the radio is? I would also like to mention the fact that task29 failed too, as it never goes over 0%.
For anyone who doesn't know what my problem is: the device will not go further than a white screen of death when booting. I can get into the bootloader, but that seems to be useless up to now.
I would like to point out the fact that I successfully flashed a custom ROM via SD card, but that made no difference whatsoever.
boot to bootloader, what does it say next to 'spl'?
assuming the answer to the first part is something like ''x.xx.hspl'' then try flashing a new radio. Go for, example, 2,10 radio, that way it doesnt matter what rom is on there, it should work.
If teh answer to teh first part is ''x.xx.0000'' then hspl is not installed, and you should start over with hspl2 or hspl3
samsamuel said:
boot to bootloader, what does it say next to 'spl'?
assuming the answer to the first part is something like ''x.xx.hspl'' then try flashing a new radio. Go for, example, 2,10 radio, that way it doesnt matter what rom is on there, it should work.
If teh answer to teh first part is ''x.xx.0000'' then hspl is not installed, and you should start over with hspl2 or hspl3
Click to expand...
Click to collapse
I have tried several radios, such a 2.07, 2.10, 2.12 and neither of them worked.
I currently have 1.42.HSPL installed, so it should.
USB does nothing: one time it got to 1% then failed because of "the image being corrupt", and the other 100 times I tried it never went past 0%.
SD card is no better: the progress bar fills up then it says:
00018003
LEOIMG.nbh - FAIL
RADIO_V2 - FAIL
Update terminate - UPDATE FAILED
And that's it.
i should stop using sd card, for a start. Stick to one method (usb) and the possible problems immediately halve.
First off i would return to a stock rom. In my case i would use teh original o2 1.43 stock rom, but you can use the 1.66 wwe if you arent sure of your stock.
boot into bootloader and physically check that hspl is still installed - it can be removed by sd card flashing, even if teh rest of teh flash fails, so always worth double checking, not just assuming that it is still installed.
assuming it says 1.42.hspl as you expect, and not anything ending .0000, then connect to usb and wait for teh word 'serial' to become 'usb'
When it does, on your pc run the stockrom.exe file.
Please post any resulting success/errors..
(oh and dont make the newb mistake of leaving a rom image on your sd card, else it will try and flash that.
Step 1: Downloading WWE 1.66.405.2 from another thread I found here on XDA.
Step 2: Formatted SD card and put it back into the device as it was, empty.
Step 3: Physically checked that my bootloader says 1.42.HSPL and it does.
*** Waiting for download to finish ***
Step 4: Loaded the phone into bootloader and connected the cable, so that it says "USB" instead of "Serial".
Step 5: Run as administrator the _HTC HD2_RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship I downloaded earlier.
Step 6: Went through all the steps indicated by the installer and it began.
It's 17:35 here and progress is 0%. I will be waiting 10 more minutes, then edit this post.
EDIT: It's 17:42 and the Update Utility says:
ERROR [262]: UPDATE ERROR
The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the errors so you can continue with the update.
Step 7: I click on "Recover", then follow the four simple steps to recover my device.
Step 8: The Update Utility goes back to the "Update" button screen, and the whole process repeats over and over.
Any other advice?
SECOND EDIT: I forgot to mention that before clicking the "Update" button, I noticed that there was a blank space where the current image name should have been. Maybe this has something to do with all that is happening?
anrabi4 said:
Step 1: Downloading WWE 1.66.405.2 from another thread I found here on XDA.
Step 2: Formatted SD card and put it back into the device as it was, empty.
Step 3: Physically checked that my bootloader says 1.42.HSPL and it does.
*** Waiting for download to finish ***
Step 4: Loaded the phone into bootloader and connected the cable, so that it says "USB" instead of "Serial".
Step 5: Run as administrator the _HTC HD2_RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship I downloaded earlier.
Step 6: Went through all the steps indicated by the installer and it began.
It's 17:35 here and progress is 0%. I will be waiting 10 more minutes, then edit this post.
EDIT: It's 17:42 and the Update Utility says:
ERROR [262]: UPDATE ERROR
The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the errors so you can continue with the update.
Step 7: I click on "Recover", then follow the four simple steps to recover my device.
Step 8: The Update Utility goes back to the "Update" button screen, and the whole process repeats over and over.
Any other advice?
SECOND EDIT: I forgot to mention that before clicking the "Update" button, I noticed that there was a blank space where the current image name should have been. Maybe this has something to do with all that is happening?
Click to expand...
Click to collapse
im in the same boat mate and have yet to get it working..mine doesnt fail flashing all the time, but quite often. same thing with the radio v2 fail. i can use bootlader no problem, use hspl to lock and unlock no problem, sometimes a flash goes ok with usb but quite often it doesnt, and when flash from sd to say put a stock rom and relock it it will quite often fail exactly like yours but other times it says its a good flash. if its a good flash itll hard reset like normal, but just wont boot past the white htc screen. i agree at this point, it has to be something related to the radio...whether its corrupt like you were saying or some kind of hardware failure
just a note it is odd that a number of us are all having the same issue..its not just a few anymore
heh ignore, ill re read
samsamuel said:
step 2....... why? did i not advise against sd card flashing? when you run the update on your pc it is restarting the phone, which is immediately flashing the rom from your sdcard,,,,, not the one on your pc.
the problem is that it immediately has removed hspl, and so the rom fails the region check.
remove the nbh from your sd card, and do all the other steps. you may have to reapply hspl, so run hspl2 and choose either 1.42.hspl or 1.66.hspl
Click to expand...
Click to collapse
i just read his step 2 and it sounds like he is saying he formatted it and inserted it empty
the-wrangler said:
i just read his step 2 and it sounds like he is saying he formatted it and inserted it empty
Click to expand...
Click to collapse
heh, d;oh. ill re read and try again (it was the LEOIMG.nbh - FAIL RADIO_V2 - FAIL bits from teh earlier posts that had me thinking he was still using sd card, cos those are sd card flashing errors)
so with the communications erros, could be AV software, firewall, or simply wrong usb port. try all ports (im sure you have by now) and if poss try a whole different pc.
samsamuel said:
heh, d;oh. ill re read and try again
Click to expand...
Click to collapse
lol no worries, i sure appreciate any help fellows like him and i can get. im certainly not new to winmo and im totally stumped.
Also guys, if you are having trouble flashing from USB , try some basic troubleshooting, if you are sure everything on the phone is correct ...
Try different USB port, also USB hubs and flashing can be bad mojo ...
Try a set of usb ports on the back of the PC rather than the front.
Try a different PC
Try a different cable
I also know it sounds strange, but I have seen some anti virus cause a flash to fail because of active scanning and it tries scanning the files in the flash directory while the flash is going on and locks them ...
All I got .....
oh and if the rom you downloaded came as a zip, dont run it from within teh zip. extract it first.
watcher64 said:
Also guys, if you are having trouble flashing from USB , try some basic troubleshooting, if you are sure everything on the phone is correct ...
Try different USB port, also USB hubs and flashing can be bad mojo ...
Try a set of usb ports on the back of the PC rather than the front.
Try a different PC
Try a different cable
I also know it sounds strange, but I have seen some anti virus cause a flash to fail because of active scanning and it tries scanning the files in the flash directory while the flash is going on and locks them ...
All I got .....
Click to expand...
Click to collapse
thanks mate, cant speak for the op but ive tried 3 different computers (xp,vista,7) different cables, everything. seems like roms will flash but it doesnt recognize a radio when booting, hence the white screen with no rgd info..so stumped.
edit..tried many many stock and custom roms and just about every radio out
The thing is that you seem to need a non-corrupted ROM to flash a radio, and need a non-corrupted radio to flash a ROM. As we have neither of them, all I can say is good luck to the guys fixing it at the service center.
I have given up; I have LITERALLY tried every possible solution I could think of. Just for the sake of it, I'll make a list here:
1. Tried all USB ports available.
2. Tried installing different drivers for the Active Sync.
3. Tried task29 w/o MTTY.
4. Tried task29 with MTTY. (Successful, but useless)
5. Tried removing HSPL.
6. Tried changing HSPL.
7. Tried flashing custom ROM. (both USB and SD)
8. Tried flashing stock ROM. (both USB and SD)
9. Tried flashing radio. (both USB and SD)
10. Double (even triple) read all of your useful comments and posts, clicked and typed the hell out of my mouse and keyboard, googled for any possible term I could come up with which was related to our problem.
I have given up for today. Tomorrow morning, I`ll have access to another laptop and I`ll try performing the same operations there, hopefully there will be a difference. All I want now is to get rid of HSPL off that bootloading screen, so that the guys from HTC won't have any reason to decline my warranty.
If nothing works, I will microwave the device for 3-5 seconds, and hopefully it`ll stop booting.
If you guys have any other suggestions, do not hesitate.
anrabi4 said:
The thing is that you seem to need a non-corrupted ROM to flash a radio, and need a non-corrupted radio to flash a ROM. As we have neither of them, all I can say is good luck to the guys fixing it at the service center.
I have given up; I have LITERALLY tried every possible solution I could think of. Just for the sake of it, I'll make a list here:
1. Tried all USB ports available.
2. Tried installing different drivers for the Active Sync.
3. Tried task29 w/o MTTY.
4. Tried task29 with MTTY. (Successful, but useless)
5. Tried removing HSPL.
6. Tried changing HSPL.
7. Tried flashing custom ROM. (both USB and SD)
8. Tried flashing stock ROM. (both USB and SD)
9. Tried flashing radio. (both USB and SD)
10. Double (even triple) read all of your useful comments and posts, clicked and typed the hell out of my mouse and keyboard, googled for any possible term I could come up with which was related to our problem.
I have given up for today. Tomorrow morning, I`ll have access to another laptop and I`ll try performing the same operations there, hopefully there will be a difference. All I want now is to get rid of HSPL off that bootloading screen, so that the guys from HTC won't have any reason to decline my warranty.
If nothing works, I will microwave the device for 3-5 seconds, and hopefully it`ll stop booting.
If you guys have any other suggestions, do not hesitate.
Click to expand...
Click to collapse
lol i hear ya, my issue is i cant seem to locate my receipt of sale for the bloody warrenty...
the-wrangler said:
lol i hear ya, my issue is i cant seem to locate my receipt of sale for the bloody warrenty...
Click to expand...
Click to collapse
you should be able to contact the seller for proof, especially if it was a carrier or someone like p4u.
samsamuel said:
you should be able to contact the seller for proof, especially if it was a carrier or someone like p4u.
Click to expand...
Click to collapse
ya i have, im waiting with fingers crossed lol. stuck with a brutal android cliq until i can get my hd2 back running. really appreciate winmo and hd2 after having to use this
after all, the-wrangler, what are u going to do? you can't just send it in for repairs if you have got HSPL installed...
microwave as well?
anrabi4 said:
after all, the-wrangler, what are u going to do? you can't just send it in for repairs if you have got HSPL installed...
microwave as well?
Click to expand...
Click to collapse
no, bootloader works just fine and it flashes sometimes..flash stock from sd and hspl is back on with stock rom..just wont boot.
oh... lucky you, I suppose...
I sure wished I could get it back as well, really don`t want to use such drastic measures...
Hello...
I have a SD-bootable Android on a Dutty Windows ROM 6.5 with a working radio and HSPL 2.08. All perfectly working.
Now i want to go NAND and want to install MAGLDR. I start it as administrator, then i can select update and my phone goes straight from windows to bootloader. But after that i get the message that my workstation can't connect to my phone (althought boot loader says "USB"). I tried it directly from boot loader too and that too doesn't work (from there i can't even get the Update selection).
Could there be an issue with the Dutty ROM or has anyone else an explanation for this kind of behavior?! And is there anything i can do... maybe erase the whole ROM (HOW???) or anything?
Regards
Elmar
Is the error message by any chance "USB init failed"?
What version of Windows are you running? Also, do you have a firewall or antivirus application running? I have seen them interfere before and you could try temporarily disabling / deactivating them.
I have an antivirus (AVG), but it is only on Android, which i am not accessing when updating. As i said i tried from windows (6.5) and the update took me to the boot loader but then the windows application is trying to connect and then gets no connect and this error message appears :
"Error (260)
Check the following :
1. PDA Phone is connected via USB
2. USB cable is connected to the workstation"
And it is connected, which you can the on the fact, that the update is running my phone into the bootloader, but then i get stuck on 0% and after that the error message appears.
What you want to do is try disabling the allow usb option in active sync. Do this after you install magldr but before you try to flash the rom. This seems to fix the problem.
Sent from my Wimax infested cm6.1.2 SuperSonic
Hello again...
I am so sorry to have bothered you with my nonsense.
From the workstation i tried (which i strangely flashed all other ROM's before and had no problems) there had been missing the driver for the boot loader which pretty simple explains my problems here (Do'h).
Tried it from a workstation with internet connection and eureka, the driver installed and i could install magldr afterwards.
Thx for all your support and sorry for my homer-like thinking for not checking that before.
P.S. Any of you any recommandations for a good NAND ROM. I think i am going to try MDJ's CyanogenMod7. Or has anyone tried various and come to another good ROM?
Regards
Elmar
hey all,
Wanted to do a clean installation of cyanogenm7,
Step by step:
entered bootloader
run task29
enterbootloader
install radio 2.15.50.14
enterbootloader
install magldr113_daf
thats it..
now, it can never use usb flasher (in order to install cwm) from magldr
for only 2-3 times it connected from USB in bootloader, and now it does not happen either. and I couldnt install cwm on that bootloader ofcourse.
windows faults; device not recognized..
did it brick? and.. why?
I'm leaving town for a business meeting tomorrow and have no backup phone right now.
save me please! =)
came home to try on a machine with XP (activesync present)
cant connect and also XP gave the same error..
device not recognized..
any ideas?
went back to laptop, win7x6
it didn't recognize at first, as usual
then it went USB on bootloader.. (did a restart first, and then it says HTC USB SYnc is successfully installed)
task29 'd again
fine
radio install began and, lost connection in the middle.
now says rom code error as normal, but again not recgnizing the device...
If aynone interested, or anyone else having the same problem at the future,
the phone is at the service and the mainboard's gonna be replaced.
http://forum.xda-developers.com/showthread.php?p=15267315#post15267315
Maybe your usb cable is damaged
Might help if you do a fresh reinstalled of windows 6.5 will erase all. And try again.
Sent from my HD2 using XDA Premium App
if you were already running cm7 then all you needed to do to fresh isntall was boot into CWM and factory reset it and isntall the rom from zip
all those extra steps you have taken are pointless
I have the following hardware/software:
HTC HD2 with Nexus HD Gingerbread (something like that, flashed latest version some month ago), Norwegian phone
MAGLDR 1.13
Two PCs with windows 7, 64 bit
Windows mobile device center 6.1
Yesterday I decided I wanted to check if it was possible to have both my Android build (which I like a lot, thank you tytung!) and windows mobile 6.5, stock rom. Don't go into detail on whether this "dual boot" works or not, my problem is solely with flashing..
As far as I've come to understand I should be able to establish an activesync connection to my computer, then run the normal executable from HTC containing the stock ROM. The problem is, I'm unable to estabish an activesync connection.
1. I boot into magldr menu by holding down the power button for a sufficient amount of time
*** Menu shown ***
2. Select USB flasher, plug in USB
*** Says "Waiting for USB connection...", then, after some seconds, appends "USB" to the end of the line ***
3. Try to start Windows Mobile Device Center
*** "No connection" shown. ***
4. Entered sync center, tried "establish new sync partnership"
*** Phone is not shown in list over available sync partners ***
5. Been trying to reinstall drivers by navigating into device manager.
*** Computer reinstalls driver on repeat on step 2, but no different behavior ***
6. Tried to use command prompt, enter device manager with hidden items visible
*** did not help (no invisible drivers found) ***
7. Tried to boot into bootloader with USB connection by holding <vol down> for a sufficient amount of time on boot
*** Same behavior, but detects different hardware (qualcomm CDMA blablabla..) ***
8. Changed USB cables
*** Same behavior ***
My last "common factor" in my setup is my two 64 bit identical OSs, maybe it's a problem here but..
Hope you can help, also help us Norwegians hold hands if you got the time:
http://www.vg.no/nyheter/innenriks/oslobomben/lenke.php
(Press "Klikk her for å styrke lenken")
MAGLDR USB Flasher or TriColor-Bootloader will NEVER connect to ActiveSync!
Connection is only schown in deviece manager in Win7 under Mobile Devices->Microsoft USB Sync (MAGLDR USB Flasher) or Mobile Devices->HTC USB Sync (TriColor-Bootloader).
Oh no.. Even though I did all that reading I missed out on that part <.<
But all flashing requires an activesync connection.. (At least windows mobile stock rom does), so how is this to be done? Is it supposed to work by entering usb flasher and then run the stock rom update file?
Is it possible to have both windows mobile 6.5 and an android build on the phone simultaneously at all?
ActiveSync connection is only needed if you are flashing under win mobile.
If you want to flash a stock rom U have to do this from TriColor-Bootloader or a .nbh via sd-card, otherwise it will not work!
You can flash a WM-rom and install an android sd-build...but both to the same time on device is a no-go.
Allright, thanks mister.
Help!
Same problem .. but in device manager it's all correct but when i try to install HSPL or if i wanna use USB Flasher, it won't work, i'm stuck at Android ... some people sais my NAND was damaged but idk ... possibly tried over 100 ROM's now ...
---------- Post added at 04:26 PM ---------- Previous post was at 04:22 PM ----------
gFrenken97 said:
Same problem .. but in device manager it's all correct but when i try to install HSPL or if i wanna use USB Flasher, it won't work, i'm stuck at Android ... some people sais my NAND was damaged but idk ... possibly tried over 100 ROM's now ...
Click to expand...
Click to collapse
FIX: other USB port or PC yay!!
gFrenken97 said:
but in device manager it's all correct but when i try to install HSPL or if i wanna use USB Flasher, it won't work, i'm stuck at Android ... !
Click to expand...
Click to collapse
explain 'it wont work' , , , , , ''it wont work'' is one of the most useless sentences, and it gets used here daily.
In what way doesn't it work? what error does it give?
I can fix if your details match mine
I have just had the same experience with my hd2, and i figured it out.
Now, im using a T-Mobile UK HD2 512mb, I loaded the latest rom found on htc's website 'Tmobile UK RUU 3.14'.
I had to first use HSPL4 and flash my phone with the 3.06.0000 (its like that, there's only 2 numbers, other is 2.0 somthing, and not the hspl, the one ending in .0000. Sorry for a poor reply but its all off the top of my head =P)
When flashing I used the tri-colour screen (vol down and power buttons)
After that had flashed, i re-entered the tri-colour screen and opened the RUU.
From that it worked fine and on my way to another android rom.
I have done this a few times in the past but not for some time, hence my confusion.
Again, apologies for the mess of the reply but the gist is there
Hope it can be of some help
Regards, Dan
I've been trying to install ACA CLk update to my HD2 since last night. Task29 will not clear rom. Just reads communication error. I have tried it on 2 win7 pc's along with a win xp pc with same results. Please help.
i am having the same error.
whether i run the ROM update utility or use the HD2 tools from the tri-color boot screen, i always get the same UPDATE ERROR (262, i believe).
i'm using USB2, no cradle or dock, brand new HD2.
any help? i'm stuck in a windows environment!
just to be sure : the communication is ok between the computer and ur phone ? u see USB in bootloader?
yes it is between my windows based pc and my HD2. and i have tried through boot loader, seeing seriel first then connecting and then it says USB. i've tried leaving it attached when i restart sit goes straight to USB. i have tried connecting with activesync/windows mobile and then running the ROMupdateutility.exe
i always get the same error: it stalls out right when the progress bar appears and never gets above 0%. then the error screen shows on my PC and i have to go through the recovery process.
thank you for any and all assistance! and sorry for the typos, im normally use swype.
this might have been the problem.
i did not have HardSPL3 installed.
i have done it, and then MAGLDR installed fine.
i skipped Task29 mostly bc i never ran that on earlier installs.
so try HardSPL to solve it, maybe?
(i'm still pretty new to this, so take my suggestions with a few grains of salt)