Database Users

Big problem with my HD2

I think it's taken a knock and now it won't boot. I just get a white screen. If I try a hard reset it gives me the text that I'll wipe all personal settings etc.
I've flashed to a duttys ROM and a 2.x.50.x radio and I'm on O2. Is there any way I can fix this as I'm guessing the ROm update voided the warrenty. As the Hard reset shows text I can see something is working but even plugging it into my PC via USB gets no response.
If anyone can help it would be a major relief.

Let it do the hard reset and see what happens. So you'll lose what ever MMS/SMS you didn't delete, the programs you have loaded since putting the ROM on, etc etc. Your not going to lose all your numbers unless they are stored on the actual phone and not the SIM card.
You could try doing a task29 on it and see if that helps. As for the warranty being voided it just depends on whether or not it can be wiped and loading with a OEM ROM back onto it with the correct HSPL before sending it back. You haven't bricked it if you can get into bootloader or hard reset.

I have tried the hard reset but no joy. It runs the reset but then on boot back to white screen. I'm not fussed about the contacts etc as it's all backed up. Have removed the SD card too.

Do a task29 on it. Flash a new radio and ROM(would suggest OEM) and then get back to us. Worst case something got knocked loose inside and it needs to go to HTC for repair.

craigpyro said:
I have tried the hard reset but no joy. It runs the reset but then on boot back to white screen. I'm not fussed about the contacts etc as it's all backed up. Have removed the SD card too.
Click to expand...
Click to collapse
i've encountered this lately for some strange reason ( being a flash junky) but found my way out of it.
flash your stock ROM via sdcard method, this will reset the spl to the original. (you can easily flash hspl anyway afterwards when you tire of the stock rom).

Ignore my post below. Have drained the battery overnight and this morning have been able to boot to:
PB81100 HX-BC
SPl-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x30
SERIAL
From here I'm hopeful I can do something.
_______________________________________________________________________________________________________
Sorry guys - but I don't understand how I am meant to do a task29 or ROM via SD card method when I cannot link by USB/ActiveSync or see anything on the screen.

craigpyro said:
....
Sorry guys - but I don't understand how I am meant to do a task29 or ROM via SD card method when I cannot link by USB/ActiveSync or see anything on the screen.
Click to expand...
Click to collapse
The microSD method does not require your phone to connect to the computer.
Here from the newbie guide to flashing a ROM:
Download a shipped Rom from *HERE*
- Rename the extension to .zip
- open it with winzip and extract the RUU_signed.nbh file to a folder
- Rename it to LEOIMG.nbh and copy it to the root of a microSD card thats been formatted to FAT32
- Insert your storage card into your phone
- Enter Bootloader and follow onscreen instructions to flash
This flashes your phone back to warranty status - it replaces the HardSPL, the ROM and the Radio.
Once your phone is repaired, you can always HardSPL your phone again.

I've tried using the HSPL tool to re-install back to 1.41 and other SPLs. The application says it's successful but when I restart the bootloader still reads:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x30
have tried Flashing ROMs and running Task29. Everytime the Bootloader switches to the updating progress bar then crashes out to Error [262].
I dont have a card reader to try from the SD card but even if I did I'm starting to feel doubtful.

are you sure, that the radio is compatible with the rom?
i'm pretty sure its the same fail.
DN41

OK - booting from FAT32 formatted microSD.
Stock ROM failed
Radio_2.08.50.05 failed

maybe a corrupt image file ? try downloading another one and see if that helps

I've tried 2 images. They get to different points at the radio install then fail. Try to get another img.

Starting to despair a little now. Trying to get just the radio on to start with.
This radio installs up to 100% (instead of about 20%) then reads:
00018003
LEOIMG.nbh - FAIL
Radio_V2Fail
Update Terminate
UPDATE FAIL
I really am getting desperate now having spent almost all day working on this.

Try using the supplied 2GB microSD card that came with the phone. Sometimes there are problems with using larger cards.

Thanks for the idea however I'm using a spare 1GB.

Silly question, but it is an O2 original ROM (assuming that is what your phone originally had on it) you downloaded and are flashing and not an HTC stock ROM (ie 1.66 WWE)?

I have tried both.

I am on the same issue here. Have read almost anything i could find to fix this. Am able to change spl through hspl2 successfully but showing the same spl 1.42 hspl in bootloader. The thing is only unable to flash radio. I can flash a custom rom with sd card but after flashing when it boot up only a white screen is showing. When i try to install a official stock rom it shows that the radio v2 not installed successfully. So its probably radio problem. Hope some one could help us fix this. I tried installing a radio with the sd card and still gets the radio v2 fail. Tried installing custom rom and radio with the usb but doest go beyond 0% and error shown in the pc. HELP HELP HELP
craigpyro said:
Starting to despair a little now. Trying to get just the radio on to start with.
This radio installs up to 100% (instead of about 20%) then reads:
00018003
LEOIMG.nbh - FAIL
Radio_V2Fail
Update Terminate
UPDATE FAIL
I really am getting desperate now having spent almost all day working on this.
Click to expand...
Click to collapse

With the steps I describe here I was able to recover the device.
http://forum.xda-developers.com/showthread.php?t=668347
But only if you follow the exact steps!
I tried many stock roms first and all were stuck on the radio.
Only the method I describe worked for me.
Good luck.

for you guys across the pond, don't you have to flash a .51 radio, not a .50 that you were using for the custom ROMs?

[TUT] NAND Android on your HD2

How To Install A NAND Android ROM On Your T-Mobile HD2​
(I am linking to several Original Threads in this tutorial. The "Nice Thing To Do" is hit the "Thanks" button at the bottom of those threads to let the author know we appreciate their help)
mskip wrote an excellent tut over on the Leo forums. I used his instructions to create my own method, which has never given me issues.
My method has been used by others and has a 100% success rate as of this writing.
You MUST be HSPL'd. This is not a joke. If you attempt this method without HSPL, your phone won't boot. I can not help you if you do this. If you have the 3.14 radio, try flashing: this stock ROM before HSPL. Thanks to xmoo for the link! Original thread is here.
Read the following steps. If you're confused, read the explanations below.
(Preparing)
Folder: Create a new folder on your Desktop. I named mine Flash. Put all downloads here.
HSPL: Cotulla's HSPL 3 is located here. (Original thread is here)
Task29: Download the Task29.exe program located here. Unzip it to a new folder. Replace the RUU_Signed.nbh file with your favorite radio. I use 2.15.50.14 (Original thread is here)
MAGLDR: Get MAGLDR 1.11 (or the latest version!) located here. Unzip this to a new folder.
ROM: Visit HD2 NAND Android Development thread here on XDA and download your new ROM. I am currently using this one, but will probably have a different one tomorrow Unzip this to a new folder.
SD Card: Back up everything you want to keep from your SD card, and then format it. Hint: dcim is where your pictures are stored (File System: Fat32, Allocation unit size: 16 kilobytes) Personally, I like to uncheck the "Quick format"; it takes up to an hour but ensures my card is in the best shape possible. Once your format is complete, you may replace your backed up files.
(Flashing)
(*Optional: Remove your SD and SIM cards, if you are paranoid, like me )
Connect your phone via USB to the PC and wait for any drivers to install.
Task29: Navigate to the Task29 folder and right-click on task29.exe and "Run as administrator". Your phone will reboot to the initial flash screen. You will have to reset to Bootloader.
Wait for your PC to update the drivers again.
MAGLDR: Navigate to the MAGDLR folder and right-click on ROMUpdateUtility.exe and "Run as administrator". Your phone will reboot to a new boot screen.
Wait for your PC to update the drivers again.
You should be booted to the new MAGLDR screen and see a series of options. Use your volume rocker to highlight "USB Flash" and press the green call button to select it.
Wait for your PC to update the drivers again.
ROM: Navigate to your new ROM folder and right-click DAF.exe and "Run as administrator".
Congratulations! When your phone reboots, it should start MAGLDR which will immediately boot your new Android NAND ROM!
Now, here are the details about the above instructions. You should only need them if you are confused.
(Preparing)
I use this to keep myself organized. I own several HTC phones and flash them all, so keeping things separate is a must for me.
Having a Hard Secondary Program Loader is a must for any NAND flash, whether it be Windows Mobile or Android. This will void your T-Mobile warranty, but can be fixed by flashing a Stock T-Mobile ROM via your microSD card. Check my sig for the tutorial link on how to do that.
This is the easiest method to do a task 29. The other is using mtty, which is beyond the scope of this tutorial. Task29 completely erases the existing files and partitions, preventing any loose data bits from causing issues with a new flash. You should always Task29 between NAND ROMs.
MAGLDR: A group of devs have been working on a NAND loader for some time and Cotulla and the Dark Forces Team (DAF) were the first to release a working loader. There may be more to come in the future, but this is the first (and has Tetris built in )
You should never ask the "best ROM for my phone" question. Every chef works hard on their build and considers it the best. Every user has their favorite chef and considers them the best. You should shop around to find the one that fits you best.
I consider formatting the SD card a must if I have any data written to it by a ROM. If you have installed Android to your card, you definitely want to do this!
(Flashing)
Your phone will boot into several different modes throughout the process. Each mode may require separate drives for WMDC to talk to it.
To reset to your bootloader, pull the battery and replace it. Hold down the "Volume Down" rocker and press the power (End Call) button. The phone should boot up to the tri-color screen. If it did not, keep trying!
Your PC may not need to search for drivers at this point, but wait and see anyway, just in case
MAGDLR will work as your new bootloader, but you can always access the original tri-color bootloader if you need to.
Don't worry if you get the missing "ADB" driver warning here. Only PCs with the Android SDK properly installed will have this driver.
You must flash your new ROM from the #4 screen via USB. It is the only way and the tri-color Bootloader method won't work here.
Again, you can ignore the missing "ADB" driver if it occurs. See above x2 for explanation.
Some chefs are renaming "DAF.exe" to "Install.exe" or "ANDR_INSTALL.exe". No matter what it's named, it should be the blue icon. See your ROM thread for detailed installation instructions if you get confused here.
Hope this helps!

262 Update Error
I have tried many different options, but none seem to go past the error. It showed white htc, on black background, and 0% update complete; and freeze about 7-10 minutes, then a popup with an update error message display.
[262] Update Error
I am running Energy ROM, with HSPL 2.8
The rest of my software info:
ROM version
27.Dec.2010WWE
ROM Date
08/30/10
Radio Version
2.07.50.27_2
Hardware info:
RAM size
576MB
Flash memory size
1024MB
If you have any suggestion for me, I am greatly appreciated.
Thanks in advanced.

DaraM said:
I have tried many different options, but none seem to go past the error. It showed white htc, on black background, and 0% update complete; and freeze about 7-10 minutes, then a popup with an update error message display.
[262] Update Error
Click to expand...
Click to collapse
Thanks for the plethora of information. In this case, it wasn't needed but most of the time it is
Error 262 means there is a link error between your phone and the PC. Some have solved this by re-installing ActiveSync or Windows Mobile Device Center. Some people said it was solved by simply unplugging the phone and trying a different USB port or cable.

After installing android rom in nand, device continously reboots
I followed all your steps and installed everything (there war an error encountered while installing the rom in the last step) but when my phone boots into android, after about a minute it will just restart itself and continue the same over and over without ever fully going into android.
can you please tell me how to get over this?

parthakolkata1 said:
I followed all your steps and installed everything (there war an error encountered while installing the rom in the last step) but when my phone boots into android, after about a minute it will just restart itself and continue the same over and over without ever fully going into android.
can you please tell me how to get over this?
Click to expand...
Click to collapse
It looks like the Android build you chose is either incompatible or was somehow corrupted when you downloaded it.
I suggest you delete the copy you have on your PC and download a different ROM, and then start over again.
Since there was an error, you don't want to try a fresh install without a task 29 and reinstalling hspl.
If you are using the Euro version of the HD2, don't try to install a TMOUS ROM, and vice versa. If you aren't sure, ask the chef who posted the ROM you want.
Hope this helps!

Radio Version
2.07.50.27_2
I think that the RADIO has to be 2.08.50.xx or a .50 greater.

Hello, I have some problems with my mob.phone HTC HD2: after get all the steps done my mobile stop working, then I tried install windows and tried turn on first time and my phone shows white screan with name HTC and don`t work at all,then i tried reset and Hard reset all setings and turn on again and than screan appears again with name HTC.
When i conect my phone to pc by usb, so my pc can`t find that phone.
Can you help me with this problem.
Thank you.

paulagrace said:
Hello, I have some problems with my mob.phone HTC HD2: after get all the steps done my mobile stop working, then I tried install windows and tried turn on first time and my phone shows white screan with name HTC and don`t work at all,then i tried reset and Hard reset all setings and turn on again and than screan appears again with name HTC.
When i conect my phone to pc by usb, so my pc can`t find that phone.
Can you help me with this problem.
Thank you.
Click to expand...
Click to collapse
One thing that was specified but not in the steps was HSPL. If you don't have that, you can't flash.

After having a bit of problem using the original tut you reference in your first post(basically it got locked on gogogo and a variety of problems thereafter), I am very happy to report that your variation on the method not only worked for me, but worked on the first attempt. And it has thus far done so each time I have tried it since. You cannot imagine my relief after all the frustration I had previously. So just wanted to let you know how helpful I found your post. Thanks!
The only edit I would suggest is that I believe USB Flashing is option 5 now instead of 4.
FWIW I was originally on ROM 2.13.531.1 (90963) WWE with Radio 2.10.50.26(now on 2.14.50.04).

gokun said:
The only edit I would suggest is that I believe USB Flashing is option 5 now instead of 4.
Click to expand...
Click to collapse
I just tried a fresh download of MAGLDR 1.11 and the option is still #4. Did you perchance grab version 1.12?
It would still work, but 1.12 gives you the additional option of installing and Windows 7 Phone ROM.

Yes on MAGLDR the option is 5 instead of 4.
Other than that, and the part about removing your sim and SD card, looks like an excellent guide.

apallohadas said:
Yes on MAGLDR the option is 5 instead of 4.
Other than that, and the part about removing your sim and SD card, looks like an excellent guide.
Click to expand...
Click to collapse
I am updating the tutorial to reflect on the changing menu numbers, thank you!
As far as the SIM and SD card removal, I did mention that this is optional but recommended. Yes, I realize that this is from the early days of flashing and is more than likely not needed, but in my defense this is my own method and I have never, ever had a bad flash. I've owned several HTC phones going back for a few years now and have not bricked a single one. I would consider that a pretty good track record, considering the number of posters who did brick their phone and have no idea what went wrong.
In light of your input, I will re-word the OT to ensure that the "optional" part is clarified.

Oh I totally hear ya.
I've never had a bad flash either. I think that some of the "Brickensteins" just do something wrong and don't mention it (like unplugging the phone mid-flash).
In your favor, I did read in one of the WP7 tutorials that the sd card should be removed, but since I don't plan on flashing that any time soon, I'll leave that wisdom with wiser hands

Thank you very much

HELP
Someone- anyone, I desperately need help. I went to a tmobile store because I was miserable with my HD2 and the man there gave me this website to turn my phone into an android, but i am NOT a tech person and now my phone is totally gone and I have no idea what I did wrong. I am so pissed I even did this. I need someone to help me.
my email is [email protected]

lalablu13 said:
Someone- anyone, I desperately need help. I went to a tmobile store because I was miserable with my HD2 and the man there gave me this website to turn my phone into an android, but i am NOT a tech person and now my phone is totally gone and I have no idea what I did wrong. I am so pissed I even did this. I need someone to help me.
my email is [email protected]
Click to expand...
Click to collapse
Ok do this hold the volume button down while powering on your HD2 and see if the multicolor bootloader screen comes up. If so you are not fubared. If you get bootloader you can save your HD2. Click on my Guide linked in my sig and read it then click the links at the top of my guide if you want to install Android or the link for WP7 if you want to install it. The links I have at the top of my guide are links to very good and extensive guide. If you want come post back here and I or others will help you and if you want to just PM me.

Please Help me...
I followed all your steps.. more then once. But every time I tried, I failed :[
I believe im doing everything right up until i have to connect my phone to run the DAF.exe file. When it says looking for usb, i have my phone connected but it then gives me this error;
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
I would love to use Android on my HD2.. so can someone help me? ._."

ol3randon said:
I followed all your steps.. more then once. But every time I tried, I failed :[
I believe im doing everything right up until i have to connect my phone to run the DAF.exe file. When it says looking for usb, i have my phone connected but it then gives me this error;
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
I would love to use Android on my HD2.. so can someone help me? ._."
Click to expand...
Click to collapse
You are using MAGLDR 1.13, not 1.11. On 1.13 (not covered by this tutorial), you have to choose "ROMUpdateUtility.exe", not "DAF.exe".

Bricked? Stuck at gray loading screen

I've been hacking/modding/flashing for years with numerous devices and have never been this far down this path...I searched around and haven't found an answer or the same situation so I'm sorry if I overlooked a similar thread.
I've been running WP7 on my HD2 for a few months after running Android from the SD and NAND for a few months before that. Yesterday my touchscreen started getting VERY difficult to use, with it being both innacurate and unresponsive. It got progressively worse so this morning I reflashed the WP7 ROM without any problems. Even after that it continued getting worse to the point where the phone was unusable because the touchscreen would not respond to anything so I couldn't unlock the phone. The hardware keys worked fine. So I decided I would try to go back to WM6.5 in an attempt to isolate whether it was software or hardware. I'm on my work computer so it doesn't have the proper drivers for flashing, so I formated my SD card, put a TMO-US WM6.5 build on the root of the card, renamed it LEOIMG.nbh and put it back in.
I booted to the tri-color screen, pressed power to confirm the flash. It flashed the progress bar and then went to the loading screen. It stayed there for around 30 minutes so I pulled the battery out and attempted to try again, but then a screen comes up for a half second that says "Software update Failed! Please Try Again" and then it goes back to the loading screen. If I try to go back to the Tri-color screen it shows it for a second and says "ROM code error Please try again" then returns to the loading screen. Anybody have any advice? Anybody seen this before?

Got a full filename for the rom you flashed?
In bootloader what's the full spl line say?
What size SD card? The stock tmous one?

wow.. unless some how the flash to wm conflicted with magldr that should had worked...
When you start the phone holding down the volume key... Do you have the SDcard still in it and it just kicks you out of the bootloader? Technically ad long as the boot loader shows up it should be fixable but it kicks you out.. that a problem

samsamuel said:
Got a full filename for the rom you flashed?
In bootloader what's the full spl line say?
What size SD card? The stock tmous one?
Click to expand...
Click to collapse
This is the ROM I was flashing on the SD:
RUU_Leo_1_5_TMOUS_2.10.531.1_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.zip
I got it from here:
http://forum.xda-developers.com/showthread.php?t=655653
The bootloader says 2.08.0000 then MicroP something. It just flashes so it is hard to read too fast.
I am using an 8GB Class 4 card. I also tried it with the stock 16GB one but it did the same thing. When I tried flashing it, however, it was the 8GB card.

hakuchi18v said:
wow.. unless some how the flash to wm conflicted with magldr that should had worked...
When you start the phone holding down the volume key... Do you have the SDcard still in it and it just kicks you out of the bootloader? Technically ad long as the boot loader shows up it should be fixable but it kicks you out.. that a problem
Click to expand...
Click to collapse
That's what I'm gathering as well. In my experience I've never been afraid of bricking because I've always been able to get to the bootloader. In this case, I can get to it, but it won't let me stay in it.

I finally got the phone to stay in bootloader mode, however when I try to flash any ROM, whether Task29, radio, stock, or cooked 6.5 it goes through the ROM Update Utility steps and then it stops at 0% for a few minutes before giving me an update communication error. This is what the Bootloader says:
PB81120 SS-B3
SPL-2.08.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
Upgrade ROM code error
Please Try Again
Thanks again for the help.

YOU donT have HSPL... Thats why flashing a cooked rom isnt working aswell ad everything else... flash a stock rom to get it up and running
Sent from my HTC HD2 using XDA App

Yep, there's the problem. Any spl ending. 0000 is stock, you have 2.08.0000, you actually need 2.08.hspl.
Don't feel too silly though, its the most basic error there is, but still turns up daily.

When you flash a stock Rom from the SDCard it removes the HSPL... So you can try flashing a Stock ROM to see if the screen issues continue or put HSPL back on and flash something to it

also, what size is your SD card? Quite often, SD Cards over 2GB in size fail for rom updates via the SD Card method.
You could also go here: http://psas.revskills.de/?q=node/ and download the free version.
Run The program and select:
Menu-Hardware forensics-WINCE SD Utils and get your card serial number. (needs a windows mobile phone connected via activesync to the pc (with the card in it) to work though)'
Once you get the code, PM it to me and I will make a goldcard.img for you.
That way you can flash any rom without having hspl on the phone.
Again, this will only work with a card under 4gb. 1 or 2gb is recommended.
Andy

[Q]stuck at recovery; serial change to usb

Hi everyone!
I am very sorry for such a n00b-post, but I really cannot find a solution.
The problem:
I recently got a HD2 of a friends who did not use it anymore, because Android suddently stopped working. Now it's stuck at a black screen [A] saying:
aMAGLDR V1.13
Build: Feb 1 2011 03:46:07
by Cotulla 2011
I tried resetting the phone using the red button near the battery, but it did not solve the problem. I am able to boot the HD2 into recovery-mode (colory screen) but then, after connecting to a pc it does not change from "serial" to "usb".
I have installed WMDC on my W7 64-bit system. I have also tried to use "RUU_Leo_HTC_NLD_1.66.404.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship" (from the 4shared "shipped LEO roms"), but none of them recognises my HD2 neither in Recovery nor in the black screen [A].
Is this phone useless? What can I try to revive it?
What might be helpfull: when normally booting, the phone vibrates once during the HTC-screen and 5 times after the black screen [A] appears.

andrejazzz said:
The problem:
Android suddently stopped working. Now it's stuck at a black screen [A] saying:
aMAGLDR V1.13
Build: Feb 1 2011 03:46:07
by Cotulla 2011
I am able to boot the HD2 into recovery-mode (colory screen) but then, after connecting to a pc it does not change from "serial" to "usb".
I have installed WMDC on my W7 64-bit system. I have also tried to use "RUU_Leo_HTC_NLD_1.66.404.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship" (from the 4shared "shipped LEO roms"), but none of them recognises my HD2 neither in Recovery nor in the black screen [A].
What might be helpfull: when normally booting, the phone vibrates once during the HTC-screen and 5 times after the black screen [A] appears.
Click to expand...
Click to collapse
Since you're unable to connect to PC, then you can't re-flash HSPL.
HSPL needed to force flash any shipped WM6.5 ROMs to HD2.
Then the only way is to flash original WM6.5 ROM for your device from uSD.
If you're not sure what CID, just download any HD2 shipped ROMs and try to flash from uSD.
Just be careful not to flash EU's ROM on T-Mobile device!
Extract the ".exe" file, then rename the ".nbh" file into "leo.nbh", copy that to root of uSD.
Power up your device while pressing vol down button.
Don't worry if the ROM refuse to flash, it's just a wrong CID.
But to make sure, connect your device to another clean PC (without android drivers inside, just WMDC), preferably a PC sets for syncing WP7/WP8 devices.
And make sure your device turns on by itself when charger is connected (auto turn on from off state).
That's just to make sure that usb connector is not damaged.
HD2 vibrate 1x at power on, it's normal.
Vibrate 5x after magldr shows up, I suspect something wrong with magldr or the ROM itself (corrupted or something).
Another possibility is some NAND bad blocks.
But if it's vibrate 5x at power on, then you have a bad luck.
The point is, flash the original ROM first.
If it's success, then flash HSPL.
After that, the rest is up to you..

Firstly, I want to thank you very much for your quick and extensive answer!
But I have only one tiny question: are these the ROMS which I can find at http: //www . 4shared . com/dir/22189940/b8552fa0/Shipped_Leo_ROMs.html#dir=MGRa1Cen ? And you mean I should just pick one and try?

You can also find HD2 shipped ROMs here.
Anything that has "TMO" are T-mobile ROMs, otherwise it's EU.
Again, don't flash EU's ROM on TMO devices!
The first 3 digit are the ROM version (1.66, 1.48. etc.), 3.14 is the latest WM6.5 ROM.
The next 3 digit are CID code (207, 404, 707, etc.).
Like I've said, if you don't know which CID for your HD2, then just download all ROMs from different CID then flash it one-by-one using uSD.

Thanks!
So far I have tried the 404 and 162 (edit: and 161, 911), but so far without luck. I'll keep you posted!
Tiny question: is it normal that I cannot shutdown in Recovery Mode?
Perhaps some useful info shown in Recovery:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40

Correct me if I'm wrong, but it looks like an EU HD2, TMO HD2 are rarely using hynix nand, made around late 2009 or early 2010.
Just try to flash ROM with CID for your friend's country first.
If failed, then try another CID.
There should be one or two info about CID number vs. country somewhere around.
Good luck!
Sent from my Windead Phone 7 using xda app-developers app

At this moment I have tried all the NLD roms with no result. Also I have tried roms from several european countries, but none of them works:/ Might it help if I give the serial number?
And what might be worth saying: my phone turns on when connected to AC power / wall-charger; when connected to charger the "serial" disappears...
Thanks for all your help!!!

Have you try connect to other PC?
When flasing ROM from uSD and failed, what error message you got?
If it's "CID mismatch" or something like that, than it's definitely a wrong CID.
If it's "ROM update error bla bla bla", it's most likely corrupted flash image or the uSD itself (use a small sized uSD, 1gb would be fine).
Even if you flash the correct CID, without removing HSPL first, it would still throw an error message "ROM update error bla bla bla" during flashing Radio.
Then it will restart and retry to flash again on it's own.
By the way, I don't know if there are ways to flash HSPL from uSD.
Or guide on how to make a "gold card".
I sugest you search it.
Worth to try if you couldn't find the correct CID for your device.
CID from serial number?
Yes, back in 2010/11 HTC site provides s/n checking for download the correct ROM.
But now it's gone.
Sent from my Windead Phone 7 using xda app-developers app

Thank you very, very much for helping such a newbie ^^
At this moment, I am able to get into the update-menu: I changed the filename to LEOIMG.nbh. The only problem is that all the Dutch images give the same error: 00018003 : Radio (V2) - FAIL.
What could I do to solve this error? Use the freezer-trick or wouldn't it make any sense?
edit: it does boot when I connect to another W7 pc with WMDC (replies " Not connected" ), only it automatically starts the update-procedure (which fails).

There are no such thing as newbie, that's why we need to learn.
Error 00018003 during Radio flash?
I have no idea what error is that.
But first, are you sure that your friend bought the phone on local shop?
I mean, not imported, or when he/she travel overseas, or has the mainboard swapped at HTC service center.
It happens to me when my second HD2 suddenly has no signal, about 2 years ago.
Brought it to local service center and they swapped the mainboard without telling me.
And the swapped mainboard has CID from 404 (europe), the original was 707 (indonesia).
Okay, back to error something.
WMDC won't recognize the phone unless it's a working WM6.5 device, or a working WP7 device with WP7 SDK + Zune installed on your PC.
Just put the phone into bootloader screen (3 color screen), then connect it to a clean PC.
Does the "Serial" changed to "USB"..?
If it does, reflash HSPL 2.08 using HSPL4 package.
Then flash Radio ROM only, 2.15.50.14 is a good one.
Again, an EU HD2 can use either EU's Radio ROM or T-Mobile's Radio ROM.
But a T-Mobile HD2 can only use a T-Mobile's ROM..!
If the "Serial" doesn't change to "USB" but on your PC makes sound like something is plugged in, open device manager and look for an unknown device (no drivers loaded).
Expand it, what does it says?

To be honest: I am not 100% sure that it is an European (Dutch) phone. What I saw when I opened the phone's back was that the warranty-seals on the screws were molested. I don't think he got the motherboard replaced: way to expensive in relation to a new phone...
The bootloader screen gives now the following text:
RUUNBH
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0X05
CotullaHSPL 0x40
Upgrade ROM error
Please try again
When I connected it to a clean pc, the phone booted and gave another upgrade-error, only this time on a black screen (I got the uSD out the phone).
After booting the phone and connecting to a pc the "serial" does not change to "usb"...
When I tried to install WMDC I get the error "Installationpackage not supported by processor". Seems like bullcrap, but there it ends. No yellow exclamation marks in Device Manager...
I have yet not tried to flash a T-Mobile ROM to the phone. I have tried all the NLD ROM's: 1.66.404 ; 1.48.404 ; 1.66.404 ; 3.14.404 ; 1.66.404 ; 1.43.404
I have yet not tried the other ROMs I downloaded, but I will tomorrow. To start 161 does not work.
Also: I cannot shutdown when in bootloader or MAGDLr, is that correct?

What colour are your call & end key buttons !
if white you have standard EU type model. T-Mobile EU models are same as any EU model & can flash any ROM/Radio
If green & red you have a T-Mobile USA model (TMOUS) & need correct ROM (found in HD2 Wiki)
T-Mobile USA model needs care as if flash wrong radio version you can brick it.
Flashing via SD card should be last choice as first stage of a SD card flash is install of the SPL to standard SPL from the nbh which means you have no CID bypass as HSPL gone.
ideally you need a Windows 7 32bit machine with a known working WMDC setup & try flashing a suitable rom once decided on EU or TMOUS device.
As you have HSPL on your HD2 already it will bypass CID if flash via PC so you can flash any CID code rom.
Try connecting device to PC (with known good WMDC) and use reset button on HD2 to boot to bootloader & see if get any luck in running ROM installer from PC.
If lucky the USB flash issue is PC & drivers rather than hardware on HD2.
I would suspect you have nand issues on HD2 or perhaps worse, if nand sometimes you can get it back if persistent & get something to flash completely.

Thanks MisterB for adds up.
So am I, suspected a nand issue.
The reason I want him to revert back to original SPL & Radio is to make sure that it's a nand related problems, not radio hardware problems.
If he managed to find the correct CID for his phone, he could easily reverts back in case somethings wrong in the future after playing with custom ROMs.
This also happens to my friend's phone a couple months ago.
But in her case, the bad blocks are definitely located where magldr resides, and many more on data partition.
She can flash shipped ROMs completely, but it refuses to boot.
Can't flash a WP7 ROM because magldr freezes when it's loading, can't even bring the menu screen.
She can run a native sd android build for a couple weeks, but then it acting strange again.
Then finally she just gave up and bought another phone.
@andrejazzz:
You can't shutdown on bootloader (3 color) screen.
Remove the battery is the only way to shutdown, or press the reset button to restart.
But you can shutdown/restart or anything else on magldr menu screen.
Press & hold power key right when magldr loads up (before it's start to "go go go").
In addition, you can download WMDC x86 version here, and x64 version here..

He may indeed need try SD flash but I would exhaust all options of USB cable flash via PC first as retaining HSPL will be useful to start with as any generic HTC ROM could be used for the USB cable flash.
If that is not possible then flashing via SD is only viable option & indeed many times only way get over bad boot/nand issues but with all the CID versions for HTC regions & operator branded regions you have a hard job knowing the right one, you could even try the right ROM & as it does not flash overlook it for further testing.
I see he has tried SD flashing but still has HSPL so either SD card is not best suited for nbh flashing or nand/hardware that bad even first stage of flash is not possible.
If I was testing this device & trying recovery I would probably try freezer test to cool device prior flashing & make good effort on USB flash before going on to SD card.
Most well used Android HD2s these days have nand or bga issues to some degree as android works the hardware so much harder than WM6.5.
You really need be sure PC & driver are known good for flashing & if going to SD flashing that SD card is suitable or you will waste a lot of time & effort.
Loads of links & tips for all the software & some threads are in the HD2 Wiki

I apologize for replying so late, but I have had no time: I had a few tests at school
@Mister B: I have a black HD2 with white icons, so I have a european model.
I have installed installed the X86 on a clean 32-bit system, but it does not recognize the phone. I have reinstalled the WMDC on my W7 64-bit system, but still it does not recognize the hd2. I have no other Windows Phones, so I am not able to verify the WMDC-installations.
When I connect to a pc, the phone boots and shows: "Software update failed! Please try again"
@Shadow_Nexus: Correct, that is exactly what happens. I do not completely understand what you mean with "Press & hold power key right when magldr loads up (before it's start to "go go go")", could you please explain?
@Mister B: How could I check if the SD-card might be the problem? It is a 16GB Class 4 Kingston SD. I have tried all the NLD-roms and other versions (random countries, not TMOUS). I have tried the freezer trick with a NLD-rom on a mSD, but it did not work.
Thanks for all your help!

Best using a 2gb or 4gb (8gb max) card for nbh flashing & do a proper fat32 format with something like hp format tool before using it.
link below may help:
http://forum.xda-developers.com/showthread.php?t=681317

Again, thank you very much for your reply. But: do you have any clue what ROM's I should try? I am asking this, because I have already tried all the NLD ROM's I found on the site @Shadow_Nexus gave in post #4, but every one of them returns the same error. Should I switch to another country and try, for example, all German ROM's?

I got my hands on another HD2 and when I connect that one to my pc it show up, named "HTC Sync". The bricked one still does not respond:/ Should I retry all the non-TMO roms I can find?
Edit: My brother "helped" me out and sold the phone...

[Q] Is this one bricked?

Hi there,
Got a HD2 Leo, basically unused.
However, I got no clue what happened to it before it found me, however this is what I get when booting it up:
postimg.org/image/3pqzwfnz7/
when plugged on PC, it installed some drivers and suggested Windows Mobile Center and the serial changes to USB.
When I hard reset it, it asks me to go back to factory settings, when I press VOLUP, it just goes into a endless reboot screen (not constantly rebooting)
Is this device bricked or is there still hope?
Thanks in advance!

poen17 said:
Hi there,
Got a HD2 Leo, basically unused.
However, I got no clue what happened to it before it found me, however this is what I get when booting it up:
postimg.org/image/3pqzwfnz7/
when plugged on PC, it installed some drivers and suggested Windows Mobile Center and the serial changes to USB.
When I hard reset it, it asks me to go back to factory settings, when I press VOLUP, it just goes into a endless reboot screen (not constantly rebooting)
Is this device bricked or is there still hope?
Thanks in advance!
Click to expand...
Click to collapse
there is hope. it looks to me as though everything has been wiped from the phone. But you have hspl installed. you now should decide what you want on your phone, wm6.5, wp7, android? This will determine what bootloader you will have to install.

Robbie P said:
there is hope. it looks to me as though everything has been wiped from the phone. But you have hspl installed. you now should decide what you want on your phone, wm6.5, wp7, android? This will determine what bootloader you will have to install.
Click to expand...
Click to collapse
Hey Robbie, thank man.
Well it seems I can get some stuff on there, right now I can nagivate though aMAGLDR V1.13, this after I updated the radio (before I couldn't do anything) However when opening it shortly says: SD KERNEL FAILED
However I have two issues, when opening Windows Mobility Center 6.1, it shows I do not have a connection (When selecting USB flasher in MAGLDR) and therefore when opening the DWI.exe from the computer (Can't access SD card, should I be able to?) I get:
An error has occurred
Read below for more information
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (1198)
Error Description: EnterBootloader missing
Info: .\RSPL\BootLoader.cpp (176)
What am I doing wrong here?

I assume you are trying to install wp7.
it might be something simple like the micro-usb lead being a charging one (2 wired) instead of a data one (4 wires). See if you can borrow one.
Open dwi.exe using right click and run as administrator.
sd kernel opened failed- means magldr is looking for Android zImage using ad sd booting, you have to first set the folder name (eg NativeSD) using ad sd dir for magldr to find it (of course a (Native)SD rom must first be installed for those files to be on your sdcard). But you don't need any of this unless you want to dual boot android wp7. The only command you need is boot wph.
See dxdy's signature for an excellent tutorial on flashing wp7