Database Users

Unable to downgrade my SPL from 3.13 to 2.20

Hi there,
Hope you can help me...
Since i bought my Cruise, I flashed it to the newest ROM version of HTC and it automatically installed SPL 3.13 with.
The problem is that if I want to install the WM 6.5 rom, I have to "Downgrade" My SPL version from 3.13.0000 to 2.20.
I followed the steps explained by "Olipro", but when the upgrade starts, RUU kills activesync (seems to be normal) and when the phone normally reboots in bootloader mode (like when you flash a new rom), nothing happens. The phone didn't shutdown and tries to establish a new USB connection !
I tried to turn manually the phone in bootloader mode on to force the SPL update, but the % bar stays at 0 and RUU returns a communication error (262).
I tried also to install the wm 6.5 rom without install SPL 2.2, but it crashes (stays @ 0% too)
I don't know how to install this stinky version of HARD SPL.
Heeeellllpppp !!
NOTE : I tried with or without µSd, does the same thing.
Thx

hmm try disabling firewall and antivirus one of them may be blocking the connection. Thats my only thought about it.

Thank you for the answer but it don't work...

Nobody can help me ?

Try to extract the files from the newest htc rom to a new folder, and then copy the "RUU_Signed.nbh" from the SPL V2 folder to the extracted files (to the new folder) and run the "ROMUpdateUtility.exe" from the extracted files (from the new folder).

nope ...

Please, consider my asks...
I know there is necessarily a solution but I have not yet found.
I don't know where/why it is crashing.
What does the HTC need to downgrade the hardspl ?
Is there a protection that can't be bypassed with the 3.13 ?
The only thing that I can do atm, is flashing the official HTC rom (useless ^^).
The actual version of my rom is :
_HTC Touch Cruise_RUU_Polaris_HTC_FRA_3.13.406.0_radio_sign_25.85.30.07_1.59.42.15_Ship
Thanking you in advance...

Pixel69 said:
Please, consider my asks...
I know there is necessarily a solution but I have not yet found.
I don't know where/why it is crashing.
What does the HTC need to downgrade the hardspl ?
Is there a protection that can't be bypassed with the 3.13 ?
The only thing that I can do atm, is flashing the official HTC rom (useless ^^).
The actual version of my rom is :
_HTC Touch Cruise_RUU_Polaris_HTC_FRA_3.13.406.0_radio_sign_25.85.30.07_1.59.42.15_Ship
Thanking you in advance...
Click to expand...
Click to collapse
HSPL 3.13? In this ROM is ver. 3.13 drivers, not HSPL... If you have original ROM and you dont install Olipros HPSL, you have original HTC SPL...

When I enter bootloader mode, the HSPL version is : 3.13.0000
Of course it's the original htc HSPL.
The problem is that I can't downgrade it to the olipro's version : 2.20.

Did you try it on other PC?

2 PCs, 2 USB cables..
The official rom upgrade works fine, I dont think that the problem comes from the computer.

definite guide:
1. establish a connection with activesync via usb (orbit2 to pc)
2. start the romupdateutility provided in hardspl folder.
3. before it starts flashing, you need to also follow on-screen instructions on orbit2!!! execute jump-spl and stuff: click yes on orbit2!!
4. when the orbit2 states: Replug USB. you need to plug the usb-cable once off and then put it back to connect to your pc.
5. it starts flashing and restarts after its done.

Hi Manaaa,
I don't know what is jumpslp ??
I found it on the web (xda..), copied it in my "my documents" folder, ran it but it asks me a jump address (default is 0x00000000) and an spl (*nb) file..
What is jump spl ? What is the address to jump to? and where can I find the *nb file ?
In the olipro's hspl folder is only a *nbh file.
Thank you

I wouldn't recommend using a jump spl for our phones if there isn't one in the Hardspl Pack then one is not needed to be run.
Personally im still really confused by this so if i get it straight.
You are synced with activesync.
Run the file for Hardspl Run RomUpdateUtility.exe
Then go though. It switches off activesync.
Then what?? Exactly Does it ask you to replug the cable? Do you get the rom flash screen (with %) at all??
Also i dont think that spl flashes can be run from the booloader as it has to be a modded bootloader (jumpspl if you will), loaded by the program to be able to flash the new hardspl.
Also i know very little on this, this is as much as i understand it to be.

chris10230 said:
You are synced with activesync. OK
Run the file for Hardspl Run RomUpdateUtility.exe OK
Then go though. It switches off activesync. OK
Then what?? Exactly Does it ask you to replug the cable? NO
Do you get the rom flash screen (with %) at all?? NO
Click to expand...
Click to collapse
Normally, after killing activesync, the phone turns into bootloader mode. Mine stays in winCE and tries to establish new usb connection...
I also decided to force manually bootloader mode and killing activesync by myself.
I ran RUU again, it first checked the phone state (such as battery >50%, connectivity...)
CHECK : OK
Next step, by clicking "NEXT" on the RUU interface, the phone turns in "% mode" and the update starts but stays at 0%.
After a while, RUU returns an update error (such as 262).
Noway to flash hardSPL :'-( , v3.13 seems to be "write protected".

ERROR [262] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process. If this happens, you can just soft reset the device and run RUU again. The update process will then continue. At this stage the rom on the device is incomplete and it will not boot back up into Windows. You will need to place it into the bootloader to continue.
Click to expand...
Click to collapse
That is what error 262 is but really dont see why this happens either. And since you can boot into windows its not much help.
So it just wont go to flash it when you click it through, hmm
Your last resort would be to PM cmonex as she will have helped make this with oilpro. Ask and see if she can shed some light on this one. Maybe something has gone wrong somewhere (quite likely) that we don't know how to fix.
Stupid question but have you tried downloading, unzipping it again? May have been a bad dl... or unzip

Have tested it with about 10# DLs...
I PM'd Olipro, waiting for a response now

Flash back to HardSPL and don't Re-Plug
Hi Pixel,
Herewith are guide for you
1) Flash back to HardSPL and don't re-plug until end of session (5 minutes)
2) Flash back to original SPL 3.13 on this post . This original SPL for HTC Touch Cruise only
3) After you do this you cannot flash with other Cooked ROM or Shipped ROM
with different ID, unless you flash back to HardSPL
Good Luck my friend

I have exactely in the same configuration as Pixel69 with the same result.
I've tried to an other PC without any change.
Has somebody any idea?

Just had an idea what OS are you running to do it?
If its not 7 may not be fully compatible... Shot in the dark really

[Q] What i can do please?

Hi everyone! At first sorry because my english is not better than my french
My problem: I have an HTC hd2 with a white screen and the SPL 1.42.0000 (i can go to bootloader). I google it and can't find any solution, i tried to instal HSPL (with hspl2/3/4) without success (usb fail connection) i have the same error with an task29, and an hd2toolkit. I tried to instal from sdcard but i have the error "radio v2 fail".
I think this is a problem at height of XDA developers ^^
PS:I tried to change Computer or usb port and execute as administrator but nothing...
If you coul help me it will be realy nice.

is the phone recognized in device manager? If not its a driver problem.
also do the usual ( verify its not the usb cable, try different usb port,) if drivers are ok

thank you for your help
The computer recognize the device but without OS (white screen) i can't do anythings with Activesync, i tried other computers and other usb port/cable but nothing. I think isn't a driver's problem because the instalation with sd card don't work.

Anis92 said:
The computer recognize the device but without OS (white screen) i can't do anythings with Activesync, i tried other computers and other usb port/cable but nothing. I think isn't a driver's problem because the instalation with sd card don't work.
Click to expand...
Click to collapse
Don't understand what you mean by "white screen"?
Try installing a stock winmo for you device to make sure everything is ok...

i tried to instal an official htc rom from sd card but it doesn't work, by "white screen" i just wanted to say that when i turn on my phone the screen is white.

It sounds like you have done a Task 29 and you do not have a ROM on your HD2 right now. This is why you just boot to the white screen.
You do npot have to use Active Sync or Windows Mobile Device Center to flash via RUU. You just have to have them installed because the haqve the USB drivers for the HD2's WINCE Bootloader in the programs and they install the drivers when you install the program.
The drivers in Active Sync and WMDC allow you to have a HTC Sync connection in the bootloader. Just boot into the bootloader by holding down the volume down button while powering on yuour HD2. Next connect your HD2 to your computer via USB cable. Wait and watch for the Serial in the white bar of the bootloader to change to USB. When you see USB you can run a RUU.
Now to address your 1.42.0000 SPL, this is a older SPL version and you may have to keep trying different RUUs until you get one that will flash. Just make sure if you have a T-Mobile HD2 that you do not flash any radio version below 2.08.50.?? or any radio version that has a 51 in the radio where the 50 is in the first radio I mentioned, or you will brick your T-Mobile HD2. Look for the radio version in the RUU name it will be there.
Sometimes the HD2 develops what is referred to as a "stuck radio" when they have these early SPL versions like yours. This is why I say you may just have to keep trying different RUUs until you find one that will flash.

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

[Solved] Touch HD bricked????

I`m writing this after almost a full day of searching and testing with no luck.
I have friend who tried to upgrade Rom into his Touch HD and failed.
Right now all the phone does is to start in tricolor menu. I have tried several Roms but when trying to flash they get stuck at 0% and after a while it ends up with error 262. Same thing happens when trying to upgrade to HSPL also (i do not have a working Rom on this phone, just a tricolor menu which starts automatically when phone started ). I have tried to flash rom with SD card (2Gb), and with Ruu with Win7 and XP.
Info :
Blac100 32M
SPL-1.54.0000
MicroP-Blackstone (LED) V6
How can i recover this phone? Can anyone pls help me ?
I have attached a Print screen of my folder dedicated to this phone. Everything there i have tried.

oh my god...you tried to flash a ROM without SPL!? are zou crazy? first you have to flash HSPL, search for the latest spl 1.56 olinex and when you get the (.nbh) file, name it to Blacimg.nbh and put on SD card (on root!) then it will appear a confirming message to install the .nbh, and you confirm.
note: not having HSPL is pratically the same thing has having a locked bootloader...

mfsr98 said:
oh my god...you tried to flash a ROM without SPL!? are zou crazy? first you have to flash HSPL, search for the latest spl 1.56 olinex and when you get the (.nbh) file, name it to Blacimg.nbh and put on SD card (on root!) then it will appear a confirming message to install the .nbh, and you confirm.
note: not having HSPL is pratically the same thing has having a locked bootloader...
Click to expand...
Click to collapse
Yes i know... not me was the one who tried... i have received it like this, and trying to recover it. The idea is when trying to install HSPL it get stuck at 0%, and the alternate method implies booting into system... but i do not have a system on device. I have also tried to download the official rom from HTC website.... and after 1% it says "invalid vender ID".

Flash SPL from sd card. Name the file as BLACimg.nbh and put on sd root. Then enter Tricolor screen (If it doesnt go automatically) and confirm the flashing. Then SEE If you get the htc logo and a empty shell ( black screen) . If you do good, now normally Flash a ROM ( you can use sd method or throug pc
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
If it doesnt work try another sd

This what i`m trying, but it get stuck to "loading" . I have downloaded "HSPLWrapper_Blackstone_156OliNex" , started "HSPLWrapper_Blackstone_156OliNex.exe" , nbh file apeared in same folder, copied to SD (formated to Fat32, default alocation unit) started phone, gone in tricolor then "loading" message on screen and nothing else (for 10 minutes already).

hmmm... keep waiting

finaly solved
I have finaly solved it. First you need Windows XP on PC. Download USPL 2.5 and open a CMD window. Start utility to upgrade to HSPL OLINEX and after presing update , and progres bar apears on phone execute fast the uspl in cmd window (otherwise it will say it cannot open USB port). After this you phone will reboot in tricolor but instead of SPL you will se USPL 1.14. Disconect usb from phone and reconect it, now it should say is connected to USB. Relaunch the HSPL update utility and wait to get to 100%. When done phone will reboot into system (if you have any).

its a way, but you could simply flash hspl trough sd (use other sd if that doesnt work, I needed to cange too!)

mfsr98 said:
its a way, but you could simply flash hspl trough sd (use other sd if that doesnt work, I needed to cange too!)
Click to expand...
Click to collapse
Believe me ! i have tried with four different SD cards, one of them indeed did not worked (a 4Gb). I do not know exactly what happened to the phone but it was impossible to flash anything to that phone (except some shipped roms witch would fail after 1% with invalid vender ID on pc and some 28008 error via card) . As i said one post earlier, the only way was via USPL, witch needed a workaround method (because it too failed with "could not access usb port" error). And the USPL worked only on Win XP and had a very narrow time window to execute the file (to have the USB port accessible ). After changing to SPL 1.56 Olinex phone booted with the old WM 6.1 stock. But i have changed 3 other roms after that, finally settling to energy Rom. With Olinex i had no problem at all flashing the Roms. I have even flashed a new radio, with absolutely no problem. Don't know what was the problem exactly, but the old SPL 1.54 had some serious issues !
I`m just glad i have revived this phone (witch btw, is not even mine)....

the old SPL, was locked lol. It's the stock SPL straight from HTC. But doesnt matter, good thing you solved your problem

10x
Wow, thanks alot for this post. I've done the same thing as you and crashed my HTC. Problem solved with Win XP, but more simple. Just executed USPL.exe and, job done. I think in Win7 was the problem with certified drivers. Think that can be solved in a fresh instalation of Win7 but not with certified microsoft drivers or HTC Sync installed. Anyways thanks alot. You've been a lifesaver.

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