Database Users

[Q] USB Device Not Recognised.

OK, I know that this question has been asked so many times before. I just cannot get my HD2 to connect to my PC at all. All I get is USB Device Not Recognized. Even though I installed the WMDC for 64 bit Win 7. I rebooted already. STILL get the SAME issue. Every time I go to boot the phone I keep getting Fatal Hit 1. Either that, or the phone vibrates 5 or 6 times and doesn't do anything. Can I get some help?
EDIT: The phone does not want to boot at all into Android. I did a hard reset thinking that would fix the USB problems. Now it doesn't want to do anything other than boot into Mag loader, or boot into the quad colored screen showing the spl and other info.
The original owner had installed NAND Android on it. When I go into the quad colored screen be holding down the vol- I get.
PB81120 SS-B3
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50

Still no Luck. Tried again today. I reinstalled WMDC and rebooted. I DO however have FULL access to Magloader. I just cannot connect it to my PC.
EDIT: I'm now flashing a WM 6.5.x ROM via SD card. Hopefully that will fix my problems.
EDIT 2: I successfully flashed NRG's Energy ROM WM 6.5.x. Now it will only boot to the NGR screen and do nothing until it vibrates 7 times in a row. I already tried doing a hard reset on the device. No luck.

I'm bumping this topic. If it helps at all. The model is the 1024 US Model.

when you are in the bootloader screen does it turn from serial to usb?
does it show that the device is found in windows?

Richy99 said:
when you are in the bootloader screen does it turn from serial to usb?
does it show that the device is found in windows?
Click to expand...
Click to collapse
It will only go to Serial, not USB. Windows 7 64 bit keeps seeing it as an unrecognized device. Even after I installed and reinstalled the WMDC driver.

1. You can try another USB Cable.
2. If you got Fatal Hit 1 error, maybe your phone have hardware problem (Boot or Flash problem)

I got it to boot ONCE! Then when I tried shutting it off. It froze on me. I had left it off for about a day. I don't have any other micro USB cables in the house other than the one I already have.
EDIT: Going to try and boot it up again. Hopefully if it's not a WMDC issue. It's the USB port that has to get replaced. (On the phone.)

Change the SPL to HSPL if not it will not reboot.

elmino said:
Change the SPL to HSPL if not it will not reboot.
Click to expand...
Click to collapse
It already has HSPL 2.08 installed.

I am starting to think the USB connecter in the phone is dead. The motherboard has the overheating issue as well. I will have to buy another HD2, or buy a motherboard for it.

If you can get it to boot you could try droid explorer , I find it never fails me , just google for it .
Sent from my HTC HD2 using XDA App

esengy west
I have the verry same problem. Phone doest react on USB at all, even my PC. Is it a death Usb port in the phone?
Greets,

[Q] Im stuck. White screen

Ok. I have a HTC HD2 t-mobile. Someone gave it to me to see if I can fix it. So I have NO clue how it got to the point it is at now. All I know is that you power on and its a white screen. No HTC logo. Just white.
Enter boot loader: Red/Green/Blue/Black/White.... Its says:
PB81120 SS-B3
SPL-2.10.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
SERIAL
Thats it. It doesnt connect to the computer.
What can I do? I tried:
CLEAN INSTALL
It’s a pretty long process, however, it takes a shorter time than the Installation of NAND Android. It takes me about 15minutes. It should take you about half an hour but no more than half an hour.
HSPL3, -2.08.HSPL.
[Head to my guide on How to install HSPL3, if you haven't install HSPL3 yet.]
Radio Version that supports 576 RAM(Radio2.15.50.14).
[Head to my guide on How to install radio , if you haven't install a suitable radio version yet.]
Wipe phone memory completely.
Install DFT MAGLDR.
Install ClockworkMod Recovery.
Create EXT3 Partition with ClockworkMod Recovery. (This step will wipe everything on our SD Card.)
Transfer ROM(zip file) to SD Card with ClockworkMod Recovery.
Install ROM from SD Card with ClockworkMod Recovery.
Details will be provided for each of the 6 steps.
But the phone and computer cant communicate. I have tried a hard reset. So thats where I am at now.

temp removed.

Ok. So I tried to flash the stock ROM from the SD card. It didnt complete. It says that it failed. It says at the top
00018003
LEOIMG.nbh - FAIL

Error happen
Read below for more information
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
Error Description: wait marker fails
Info: .\RSPL\BootLoader.cpp (225)

When I try to install HSPL3 I get this error
CRITICAL ERROR
FLOW: 00000006
Error code: 00000014
Description Unknown

I can not get HSLP on my phone. I have tried versions 2,3 and 4... Is the phone done???

So I know I am a pain. But I have searched and read just about everything I can. I have tried to flash the stock ROM, I get an error of Radio Fail. I can not flash any other ROMS because I can not install HSLP.... I can connect via USB. But Windows Mobile Device center does not acknowledge the phone. I have ran the Task29... well tried... it says image is corrupted. I have even stuck the dang thing in the freezer like I have seen in random posts. Nothing but a really cold phone.
When I try and install HSPL3 I get an option to choose 2.08.HSPL or 2.08.0000 I have tried both. I get the critical error... Error code 16 description unknown.
I have tried following every set of directions I can locate in xda... Nothing has worked at all.

McSpammer5 said:
temp removed.
Click to expand...
Click to collapse
???What does that mean???

Have you tried reflashing window mobile???
Sent from my LG-P999 using xda premium

Yes I tried to reflash several times. I went and bought a new SD card. Solved it. Got windows working properly... Now to move on to installing Android

yesiamanoob said:
Yes I tried to reflash several times. I went and bought a new SD card. Solved it. Got windows working properly... Now to move on to installing Android
Click to expand...
Click to collapse
Great...
Sent from my LG-P999 using xda premium

Hi to the experts!
I have a very similar problem, maybe "almost" identical...
My HD2 (Australian Telstra, stock in almost every way), and it has been reliable for 2 years from new.
Then last Saturday night it started "failing to load HTC Sense", but all the WinMo 6.5 stuff was still fine. This lasted for 2 days and I thought it was stable like this so I would have time to look for a new phone, but last night I turned it off and on again, and all I have is the white screen. Mine has the green htc on it, but the only way to make it go away is to take out the battery.
I tried the volume down / power ON and I get the RGB+W screen, and when I plugged it in via USB to my new laptop it loaded drivers and initiated Windows mobile device center - but it won't recognise that there is a device there.
Now my very strong desire is to somehow boot it to allow recovery of my contacts directory - I have just started a new job and have probably 40 or so new people in there since my last backup.
What are my options? Is there anyway to boot from SD card without erasing the whole of system memory??
Failing that, how do I flash back to stock?
thanks (in hope)
..Neil

Stock WM
Try installing stock WM 6.5. There are many links available for the same, google it.
Do this without the memory card.
Enter Bootloader by pressing volume down and power on button together.
Then run the WM ROM file on your computer. You must see the progress bar on your phone. Let it settle down.
Hope that helps..!!

[Q] Weird "00028002 Not allow" Error when Flashing

Hey there Community,
I really don't know much about mobiles, especially the HTC HD2 and flashing ROMs,
but somehow I got Android to work on my HTC HD2 1 year back and now wanted to sell my phone because I got a new one.
Therefore I needed to set up the factory settings and get Windows Mobile 6.5 back on my phone..
Unfortunately I failed hard while following the instructions of a tutorial that said I only needed to rename ruunbh to leoimg and put it on my SD-card and so on.
Halfway the update was interrupted and since then Iam getting "00028002 Not allow" error and can only boot to the bootloader saying "Upgrade ROM code error Please try again" And the usual things in the red disctrict and at the bottom it says that I got an USB-connection which seems to be wrong, because I can't see the device and so on.
I tried to install HSPL4 but it failed due to no USB-connection.
So what can I now do to make it work again? Iam really frustrated

Flashing image from sd is all good if it original correct country/vendor rom, if not you get your problem & things can be tricky as HSPL was replaced with standard SPL so care must be taken.
Either find a correct Vendor/country (CID) ROM for your HD2 or get it in bootloader & able to flash HSPL.
Would of thought for resale a good Android build would be more desirable.

I know what you mean, but the problem is that I just don't know what to do..
My phone is not branded or anything, so I couldn just go to htc.com and get me the newest winmo Rom?
The Problem is, what to do then, exactly?
It seems that I can't flash anything because I dont got usbconnection..

So no idea to original ROM country vendor !
usb connection may be due to driver issue on PC, install Activesync if on XP or WMDC 6.1 for Vista & Windows 7 then retry connecting hd2 via usb .
*Also make sure you know your version of HD2 & be aware of .51 radios killing US T-Mobile HD2s.

Try to flash 2.08.HSPL only (also in HSPL4). It is enough. You can also try these drivers to fix your USB connection.
And here you can find offical ROMs.

Drivers linked above are not suitable, install activesync or WMDC is best option.
Finding original ROM is not going to be easy if you have no clues to origin of handset ...

Also, just cost you don't "see" the phone from the p c doesn't mean you don't have a USB connection.... it will never show up in your drives list like it does when an os is running, and activesync (or wmdc) will also not see the phone when it's in bootloader.
If the phone shows "USB" (and your PC may even "ding" when its plugged in, that's all you can expect unless you look deeper,, into the hardware list, for example.
What does hspl line say?
I'd do....
Hspl4, choose 3.03.hspl (NOT 3.03.0000)
Flash unbranded 3.14 rom from USB
Report back.

I have same story - 00028002 not allow+no usb.
no one stock rom can be flashed.
completely lost and no idea what to do.

[Q] HTC HD2 bricked?

ok, here's the long and the short. I am pretty much a noob. i was very reluctant to post this as noobs should be able to find the answer without asking, asking just makes you an idiot according to the intro video when i signed up, but here goes. when i bought this phone it was stock. i successfully installed HSPL4 2.08, MAGLDR 113, CWM 5.0.2.8, and NEXUS HD2.ICS.CM9.hwa.v2.3a. Everything was great until I decided to flash the new nexus jellybean rom. you see this rom and most of the subsequent jellybean roms need a system partition of about 285mb. so here starts the trouble. i tried using hd2 toolkit to repartition and the usb would not connect. with the phone in flasher mode it would just sit there and say wait....USB and then show error number 260 i believe. after days of attempts at different methods and hour of reading forums all over the net, i decided to revert back to stock and start fresh. i followed all online instructions and reflashed spl 2.08.0000 onto the phone with the file downloaded from the t-mobile website. now the phone just sits on the multi colored screen. after several failed attempts i decided to reflash the HSPL 2.08 and go back the way i came. no success. doesn't matter what i do it just stays on the multicolored screen. so presently my phone says what the attached photo will show. thanks in advance for any help you can give.

u missed off the most important part of that pic, , the white bit at the bottom, , does it turn from serial to usb? what OS you running on the PC? have you updated windows mobile device centre? were you having usb troubles at all? tried all your usb ports? tried a different pc?
go try all that, post results.

it does switch from serial to usb when plugging into the pc. the operating system is windows 7 ultimate. i have tried all of the usb ports my pc has to offer. i am next going to attempt it on my wife's pc but her system is also windows 7. i even tried to run the software in xp compatibility mode. i have read that if the tri color screen is at least present, my phone is not truly bricked. is this so? i also have the most current version of windows mobile device center. and the usb troubles only were present originally. since then all software has shown a connection and status bar when working, on the pc as well as the phone.

If your pc cant recognized him am affraid some of the hardware (probably motherboard) is dead.

my pc does recogize the phone. when i change usb ports, it does install device driver software.

in that case please explain your problem in more detail, , a step by step including full filenames, everything that happens, no matter how small it seems, if you plug the usb in, type it, if you're telling us about the spl, don't put 2.08, , put 2.08.hspl or 2.08.0000, detail is everything.
also, go install 'myphoneexplorer' onto the pc, , you don't need to run it, but then we know for sure you have the correct usb drivers for magldr to use.

OK, I will begin. I put the battery in my phone, press power and volume down at same time. (don't really need to do this as just pressing the power button has the same effect) The tri color screen pops up. this is what it says:
PB81120 SS B3
SPL-2.08.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
I have been noticing that when this screen first comes up after about 1 sec. the screen flashes for about a half second and then stays this way. At the bottom in white it says serial. I now plug the USB in and it then changes to USB. I will now try to flash HSPL4. I have a file named HSPL4. I open the file, right click on th icon (application) called HSPL4 and select "run as administrator" Window for DFT HSPL4 for HTC LEO pops up. click on next. Please wait while installing HSPL comes up. New window opens, select HSPL version to install. click on drop box and select 2.08.HSPL. click next. please wait while installing pops up. now a window popped up for the first time:
CRITICAL ERROR
Flow: 00000006
Error Code: 00000011
Description: Unknown
I then click OK. the installer closes. I will proceed no further until I receive a response.

snowman2765 said:
OK, I will begin. I put the battery in my phone, press power and volume down at same time. (don't really need to do this as just pressing the power button has the same effect)
Click to expand...
Click to collapse
thats not a great sign
The tri color screen pops up. this is what it says:
PB81120 SS B3
SPL-2.08.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
I have been noticing that when this screen first comes up after about 1 sec. the screen flashes for about a half second and then stays this way.
Click to expand...
Click to collapse
perhaps you have an incompatible rom.img on the sd card, that often causes a brief flicker. Try with the sd card removed unless you are flashing from teh sd.
At the bottom in white it says serial. I now plug the USB in and it then changes to USB. I will now try to flash HSPL4. I have a file named HSPL4. I open the file, right click on th icon (application) called HSPL4 and select "run as administrator" Window for DFT HSPL4 for HTC LEO pops up. click on next. Please wait while installing HSPL comes up. New window opens, select HSPL version to install. click on drop box and select 2.08.HSPL. click next. please wait while installing pops up. now a window popped up for the first time:
CRITICAL ERROR
Flow: 00000006
Error Code: 00000011
Description: Unknown
I then click OK. the installer closes. I will proceed no further until I receive a response.
Click to expand...
Click to collapse
sounds like a variety of stuck radio/stuck spl or similar,
well, usual things to try would be - flashing the correct stock rom from sd (correct as in if the phone came from O2 uk, use an o2 uk rom, tmo germany, use a t mo germany, , if its a tmous, , , red end key green send key then ONLY use tmous roms, DO NOT use any other stock roms than tmous ones.
also worth trying the freezer trick, , chill teh phone for a half hour, then quickly try to flash, , if this works it points to failing hardware, , but not always, so worth a shot.
Oh, and dont use a front mounted usb port, , hspl doesn't like hubs and passthrough usb ports, , use one around back of the PC.

i have a stock tmous rom that i downloaded directly from the t-mobile website using my IMEI number. It comes through as an application. i right clicked on it and extracted the file. copied the RUU_signed.nbh and pasted it to my desktop. right clicked on that and renamed it to LEOIMAGE.nbh is this correct? i tried both ways upper and lower case letters. is there a right one? this is where all the tutorials seemed to get grey for me. what do i do next in order? i still have the original file on my pc and the one i renamed on my sd card in the phone. also i recall reading about using a maximum 4gb sd card. how critical is this as 8 is the smallest i have? as it stands i have only that file on the card and nothing else. before putting it on the card i formatted the card to fat32. also i only named it LEOIMAGE as it is already an .nbh file and if i name it LEOIMAGE.nbh, then it will become LEOIMAGE.nbh.nbh right?

snowman2765 said:
i have a stock tmous rom that i downloaded directly from the t-mobile website using my IMEI number. It comes through as an application. i right clicked on it and extracted the file. copied the RUU_signed.nbh and pasted it to my desktop. right clicked on that and renamed it to LEOIMAGE.nbh is this correct? i tried both ways upper and lower case letters. is there a right one? this is where all the tutorials seemed to get grey for me. what do i do next in order? i still have the original file on my pc and the one i renamed on my sd card in the phone. also i recall reading about using a maximum 4gb sd card. how critical is this as 8 is the smallest i have? as it stands i have only that file on the card and nothing else. before putting it on the card i formatted the card to fat32. also i only named it LEOIMAGE as it is already an .nbh file and if i name it LEOIMAGE.nbh, then it will become LEOIMAGE.nbh.nbh right?
Click to expand...
Click to collapse
LEOIMG.nbh is what it should be called!
Sent from my NexusHD2 using xda premium

ok i did manage to flash the stock rom from the sd card. everything went great install completed and it says update complete update success. i pull the battery wait about 5-10 secs and then restart the phone. the tri color screen comes up. now what?

Oh dear, that's unfortunate. Some people have had luck by disconnecting the bottom hardware buttons when this happens, but there's no simple "do this" answer .

i guess the only thing i can ask then is this. is there any way i can get it going with the win 6.5 on it so i can sell it? and could it have been something i did to the phone? and if i took for repair, do you have a ballpark as to what it could cost?

have we considered that maybe the volume down button is stuck in the "pressed" state?

well i guess i will take it in then, that now seems to be well past my comfort zone.

just wanted to say thanks to everyone for all of the help. the service tech checked out my phone and determined that it is an issue with the mother board. I found some available on the net for $100+ and then add another $45 to install. we have decided that it is not a worthwhile price to pay for a 4 year old handset so we will be scrapping it. my wife still has one though, so I probably will be back on these forums again.

A little update. I bought a parts phone from a posting online and replaced the mother board myself. Followed the directions from a video online, and all went pretty good. Powered up the pone after re-assembly, and let there be life! Flashed Nexus Jelly Bean, and the phone works great. Thanks everybody for all of your help.

one thing though, the phone will not accept a charge from the usb port, but it is recognized by the computer. i can flash mods and all but i have to charge the battery from a wall cradle by taking the battery out. does anybody else experience this problem?

HD2 does not charge
snowman2765 said:
one thing though, the phone will not accept a charge from the usb port, but it is recognized by the computer. i can flash mods and all but i have to charge the battery from a wall cradle by taking the battery out. does anybody else experience this problem?
Click to expand...
Click to collapse
Try a different USB cable or port. Don't use a USB hub plug directly into the computer.
David

Best401k said:
Try a different USB cable or port. Don't use a USB hub plug directly into the computer.
David
Click to expand...
Click to collapse
It could be a faulty USB port on MB too...

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