Database Users

Formatting radio

I decided it's best to open another topic, as the subject has changed and the other topic seems to have died more or less.
I have found out that the problem with my HD2 is that the radio is corrupted. However, I failed every time I tried flashing a new radio, even though I tried both USB and SD card methods.
Is there any way I can format the part of the memory where the radio is? I would also like to mention the fact that task29 failed too, as it never goes over 0%.
For anyone who doesn't know what my problem is: the device will not go further than a white screen of death when booting. I can get into the bootloader, but that seems to be useless up to now.
I would like to point out the fact that I successfully flashed a custom ROM via SD card, but that made no difference whatsoever.

boot to bootloader, what does it say next to 'spl'?
assuming the answer to the first part is something like ''x.xx.hspl'' then try flashing a new radio. Go for, example, 2,10 radio, that way it doesnt matter what rom is on there, it should work.
If teh answer to teh first part is ''x.xx.0000'' then hspl is not installed, and you should start over with hspl2 or hspl3

samsamuel said:
boot to bootloader, what does it say next to 'spl'?
assuming the answer to the first part is something like ''x.xx.hspl'' then try flashing a new radio. Go for, example, 2,10 radio, that way it doesnt matter what rom is on there, it should work.
If teh answer to teh first part is ''x.xx.0000'' then hspl is not installed, and you should start over with hspl2 or hspl3
Click to expand...
Click to collapse
I have tried several radios, such a 2.07, 2.10, 2.12 and neither of them worked.
I currently have 1.42.HSPL installed, so it should.
USB does nothing: one time it got to 1% then failed because of "the image being corrupt", and the other 100 times I tried it never went past 0%.
SD card is no better: the progress bar fills up then it says:
00018003
LEOIMG.nbh - FAIL
RADIO_V2 - FAIL
Update terminate - UPDATE FAILED
And that's it.

i should stop using sd card, for a start. Stick to one method (usb) and the possible problems immediately halve.
First off i would return to a stock rom. In my case i would use teh original o2 1.43 stock rom, but you can use the 1.66 wwe if you arent sure of your stock.
boot into bootloader and physically check that hspl is still installed - it can be removed by sd card flashing, even if teh rest of teh flash fails, so always worth double checking, not just assuming that it is still installed.
assuming it says 1.42.hspl as you expect, and not anything ending .0000, then connect to usb and wait for teh word 'serial' to become 'usb'
When it does, on your pc run the stockrom.exe file.
Please post any resulting success/errors..
(oh and dont make the newb mistake of leaving a rom image on your sd card, else it will try and flash that.

Step 1: Downloading WWE 1.66.405.2 from another thread I found here on XDA.
Step 2: Formatted SD card and put it back into the device as it was, empty.
Step 3: Physically checked that my bootloader says 1.42.HSPL and it does.
*** Waiting for download to finish ***
Step 4: Loaded the phone into bootloader and connected the cable, so that it says "USB" instead of "Serial".
Step 5: Run as administrator the _HTC HD2_RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship I downloaded earlier.
Step 6: Went through all the steps indicated by the installer and it began.
It's 17:35 here and progress is 0%. I will be waiting 10 more minutes, then edit this post.
EDIT: It's 17:42 and the Update Utility says:
ERROR [262]: UPDATE ERROR
The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the errors so you can continue with the update.
Step 7: I click on "Recover", then follow the four simple steps to recover my device.
Step 8: The Update Utility goes back to the "Update" button screen, and the whole process repeats over and over.
Any other advice?
SECOND EDIT: I forgot to mention that before clicking the "Update" button, I noticed that there was a blank space where the current image name should have been. Maybe this has something to do with all that is happening?

anrabi4 said:
Step 1: Downloading WWE 1.66.405.2 from another thread I found here on XDA.
Step 2: Formatted SD card and put it back into the device as it was, empty.
Step 3: Physically checked that my bootloader says 1.42.HSPL and it does.
*** Waiting for download to finish ***
Step 4: Loaded the phone into bootloader and connected the cable, so that it says "USB" instead of "Serial".
Step 5: Run as administrator the _HTC HD2_RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship I downloaded earlier.
Step 6: Went through all the steps indicated by the installer and it began.
It's 17:35 here and progress is 0%. I will be waiting 10 more minutes, then edit this post.
EDIT: It's 17:42 and the Update Utility says:
ERROR [262]: UPDATE ERROR
The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the errors so you can continue with the update.
Step 7: I click on "Recover", then follow the four simple steps to recover my device.
Step 8: The Update Utility goes back to the "Update" button screen, and the whole process repeats over and over.
Any other advice?
SECOND EDIT: I forgot to mention that before clicking the "Update" button, I noticed that there was a blank space where the current image name should have been. Maybe this has something to do with all that is happening?
Click to expand...
Click to collapse
im in the same boat mate and have yet to get it working..mine doesnt fail flashing all the time, but quite often. same thing with the radio v2 fail. i can use bootlader no problem, use hspl to lock and unlock no problem, sometimes a flash goes ok with usb but quite often it doesnt, and when flash from sd to say put a stock rom and relock it it will quite often fail exactly like yours but other times it says its a good flash. if its a good flash itll hard reset like normal, but just wont boot past the white htc screen. i agree at this point, it has to be something related to the radio...whether its corrupt like you were saying or some kind of hardware failure
just a note it is odd that a number of us are all having the same issue..its not just a few anymore

heh ignore, ill re read

samsamuel said:
step 2....... why? did i not advise against sd card flashing? when you run the update on your pc it is restarting the phone, which is immediately flashing the rom from your sdcard,,,,, not the one on your pc.
the problem is that it immediately has removed hspl, and so the rom fails the region check.
remove the nbh from your sd card, and do all the other steps. you may have to reapply hspl, so run hspl2 and choose either 1.42.hspl or 1.66.hspl
Click to expand...
Click to collapse
i just read his step 2 and it sounds like he is saying he formatted it and inserted it empty

the-wrangler said:
i just read his step 2 and it sounds like he is saying he formatted it and inserted it empty
Click to expand...
Click to collapse
heh, d;oh. ill re read and try again (it was the LEOIMG.nbh - FAIL RADIO_V2 - FAIL bits from teh earlier posts that had me thinking he was still using sd card, cos those are sd card flashing errors)
so with the communications erros, could be AV software, firewall, or simply wrong usb port. try all ports (im sure you have by now) and if poss try a whole different pc.

samsamuel said:
heh, d;oh. ill re read and try again
Click to expand...
Click to collapse
lol no worries, i sure appreciate any help fellows like him and i can get. im certainly not new to winmo and im totally stumped.

Also guys, if you are having trouble flashing from USB , try some basic troubleshooting, if you are sure everything on the phone is correct ...
Try different USB port, also USB hubs and flashing can be bad mojo ...
Try a set of usb ports on the back of the PC rather than the front.
Try a different PC
Try a different cable
I also know it sounds strange, but I have seen some anti virus cause a flash to fail because of active scanning and it tries scanning the files in the flash directory while the flash is going on and locks them ...
All I got .....

oh and if the rom you downloaded came as a zip, dont run it from within teh zip. extract it first.

watcher64 said:
Also guys, if you are having trouble flashing from USB , try some basic troubleshooting, if you are sure everything on the phone is correct ...
Try different USB port, also USB hubs and flashing can be bad mojo ...
Try a set of usb ports on the back of the PC rather than the front.
Try a different PC
Try a different cable
I also know it sounds strange, but I have seen some anti virus cause a flash to fail because of active scanning and it tries scanning the files in the flash directory while the flash is going on and locks them ...
All I got .....
Click to expand...
Click to collapse
thanks mate, cant speak for the op but ive tried 3 different computers (xp,vista,7) different cables, everything. seems like roms will flash but it doesnt recognize a radio when booting, hence the white screen with no rgd info..so stumped.
edit..tried many many stock and custom roms and just about every radio out

The thing is that you seem to need a non-corrupted ROM to flash a radio, and need a non-corrupted radio to flash a ROM. As we have neither of them, all I can say is good luck to the guys fixing it at the service center.
I have given up; I have LITERALLY tried every possible solution I could think of. Just for the sake of it, I'll make a list here:
1. Tried all USB ports available.
2. Tried installing different drivers for the Active Sync.
3. Tried task29 w/o MTTY.
4. Tried task29 with MTTY. (Successful, but useless)
5. Tried removing HSPL.
6. Tried changing HSPL.
7. Tried flashing custom ROM. (both USB and SD)
8. Tried flashing stock ROM. (both USB and SD)
9. Tried flashing radio. (both USB and SD)
10. Double (even triple) read all of your useful comments and posts, clicked and typed the hell out of my mouse and keyboard, googled for any possible term I could come up with which was related to our problem.
I have given up for today. Tomorrow morning, I`ll have access to another laptop and I`ll try performing the same operations there, hopefully there will be a difference. All I want now is to get rid of HSPL off that bootloading screen, so that the guys from HTC won't have any reason to decline my warranty.
If nothing works, I will microwave the device for 3-5 seconds, and hopefully it`ll stop booting.
If you guys have any other suggestions, do not hesitate.

anrabi4 said:
The thing is that you seem to need a non-corrupted ROM to flash a radio, and need a non-corrupted radio to flash a ROM. As we have neither of them, all I can say is good luck to the guys fixing it at the service center.
I have given up; I have LITERALLY tried every possible solution I could think of. Just for the sake of it, I'll make a list here:
1. Tried all USB ports available.
2. Tried installing different drivers for the Active Sync.
3. Tried task29 w/o MTTY.
4. Tried task29 with MTTY. (Successful, but useless)
5. Tried removing HSPL.
6. Tried changing HSPL.
7. Tried flashing custom ROM. (both USB and SD)
8. Tried flashing stock ROM. (both USB and SD)
9. Tried flashing radio. (both USB and SD)
10. Double (even triple) read all of your useful comments and posts, clicked and typed the hell out of my mouse and keyboard, googled for any possible term I could come up with which was related to our problem.
I have given up for today. Tomorrow morning, I`ll have access to another laptop and I`ll try performing the same operations there, hopefully there will be a difference. All I want now is to get rid of HSPL off that bootloading screen, so that the guys from HTC won't have any reason to decline my warranty.
If nothing works, I will microwave the device for 3-5 seconds, and hopefully it`ll stop booting.
If you guys have any other suggestions, do not hesitate.
Click to expand...
Click to collapse
lol i hear ya, my issue is i cant seem to locate my receipt of sale for the bloody warrenty...

the-wrangler said:
lol i hear ya, my issue is i cant seem to locate my receipt of sale for the bloody warrenty...
Click to expand...
Click to collapse
you should be able to contact the seller for proof, especially if it was a carrier or someone like p4u.

samsamuel said:
you should be able to contact the seller for proof, especially if it was a carrier or someone like p4u.
Click to expand...
Click to collapse
ya i have, im waiting with fingers crossed lol. stuck with a brutal android cliq until i can get my hd2 back running. really appreciate winmo and hd2 after having to use this

after all, the-wrangler, what are u going to do? you can't just send it in for repairs if you have got HSPL installed...
microwave as well?

anrabi4 said:
after all, the-wrangler, what are u going to do? you can't just send it in for repairs if you have got HSPL installed...
microwave as well?
Click to expand...
Click to collapse
no, bootloader works just fine and it flashes sometimes..flash stock from sd and hspl is back on with stock rom..just wont boot.

oh... lucky you, I suppose...
I sure wished I could get it back as well, really don`t want to use such drastic measures...

[Q] the image file is corrupted , please check your update utility

Hey all so my phone crapped out on me for some reason im not able to boot into my rom anymore and i wanted to uninstall Cotulla HSPL so that i can exchange phone through warranty. I keep getting error message "the image file is corrupted , please check your update utility" after trying to flash.
I am really stuck on this one, please help

Same problem with me, any news yet?
Did you send it back to HTC?

Bump
My friend is having this exact problem. Any solutions

dadogintown said:
Hey all so my phone crapped out on me for some reason im not able to boot into my rom anymore and i wanted to uninstall Cotulla HSPL so that i can exchange phone through warranty. I keep getting error message "the image file is corrupted , please check your update utility" after trying to flash.
I am really stuck on this one, please help
Click to expand...
Click to collapse
If you can go into bootloader screen (the four color screen), you still can uninstall HSPL. First off, turn off your phone. Then, press the volume down button AND the power on button, AT THE SAME TIME, until the four color screen appear (bootloader screen).
Now, connect your device to your PC, and wait until the text "Serial" change to "USB" (you should see it at the white color part)
Now, run HSPL 4 from your PC. Dont forget to turn off Anti Virus, Firewall, Internet Connection, Screen saver and your battery must be at least 50%. And if you are on Vista or win 7, run as an Administrator. If for some reason, Serial doesnt change to USB, you unplug it and try different USB port (try the rear USB port)
Now, you can choose which HSPL you want to remove.
Alternatively, you can erase HSPL using Micro SD Method.
Download your CORRECT STOCK ROM. Extract it, and find the fie named : RUU_signed.nbh . Rename it to : leoimg.nbh. Copy this file to the root of your SD Card. Before copy it, it is advisable to format the sd card using card reader and dont put other files except leoimg.nbh file.
Now go into bootloader screen as mentioned earlier. And follow the instruction screen.
Done.
Goodluck

Did you fix it??
Same problem here.
Give me some advice.
Thanks in advance!

[FIXED]cannot install NAND roms anymore[FIXED]

Error happen
Read below for more information
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
I got this when I first installed the standard DFT ROM, i found that by remving the accept USB connections in activesync resolved it and I was able to install. I then tried to install a different ROM and failed, I tried another and the same. I was initally getting RAPITOOL errors, dll not found. Reinstalled activesync and I am not getting those errors anymore but ROM still wont install. With error above.
Reinstalled Mag ok so bootloader installs still ok, anyone any ideas?
FECK, my NAND Android build has gone as well...

What helped for me:
- If USB is connected: right click on USB -> safely remove MAGLDR USB device
- remove MAGLDR USB driver from PC
- restart pc
- connect phone again via USB and let driver install
Should work fine again now. Guess something can go wrong in the USB driver sometimes.

mag does not show up as a device to remove, i will reboot and try again.

I think activesync reinstall resolved it as it worked after a rebooted, didnt reboot prior to that, thanks for your help anyway.

I spoke to soon, well managed to flash another ROM, didnt like it so flashed again, got half way through and then came up with error again, tried again, back to square one. Anyone ideas what is causing this?

rebooted, still the same, reinstalled activesync and rebooted, all ok again. Why is activesync required, cany anything else be used, anyone any idea what is happening here?

you can install magldr, radio or roms with ruu in 3 color mode in hspl...
get there with wol down key and end call button pressed
when magldr is already installed boot up your phone with pressing end call button until magldr menu appears
and then start you android flashing procedure the way cotulla explained it!
I had the 723 error too and what helped for me was executing the daf.exe with password secured admin rights (your profile on computer has to have admin rights and has to be password secured)

t3g said:
you can install magldr, radio or roms with ruu in 3 color mode in hspl...
get there with wol down key and end call button pressed
when magldr is already installed boot up your phone with pressing end call button until magldr menu appears
and then start you android flashing procedure the way cotulla explained it!
I had the 723 error too and what helped for me was executing the daf.exe with password secured admin rights (your profile on computer has to have admin rights and has to be password secured)
Click to expand...
Click to collapse
Hi, thanks for info but I am passed that point. I have already installed mag and tested my first ROM, I am having this problem when trying to flash new ROMS. I have now go another ROM on by reinstalling activesync and rebooting again, I am hoping someone is aware of this issue and let me know how to resolve it as I dont want to have to go through this rigmarole everytime I want to flash - as I am still at the stage of settling on a ROM and are trying all the current set.

In a much happier place right now. don't have to stress over winmo 6.5 anymore. Thank you all for your help. Lovin' Android on my HD2. So fast.

Try this http://forum.xda-developers.com/showthread.php?t=918698

And this might be helpful, too

deckoff said:
And this might be helpful, too
Click to expand...
Click to collapse
cheers but problem now solved after using android_install.exe rather than daf.exe

Magldr help

Guys can somebody help me? I'm trying to install this ROM and when I'm at the part where it says "Waiting for USB connection..." and box pops up and says "The application has failed to start because RAPI.dll was not found. Re-installing the application may fix the problem." How do I install RAPI.dll? Also right now my phone is in MAGLDR v1.12 and it's stuck at the USB Flasher mode screen saying "Wait USB...". Can I just take out my battery and power on and it will boot in to the previous NAND ROM I had on my HD2?
I've put a picture up of all the files that came with the download. I don't know what I'm doing! I'm new to this stuff.

Skellyyy said:
Guys can somebody help me? I'm trying to install this ROM and when I'm at the part where it says "Waiting for USB connection..." and box pops up and says "The application has failed to start because RAPI.dll was not found. Re-installing the application may fix the problem." How do I install RAPI.dll? Also right now my phone is in MAGLDR v1.12 and it's stuck at the USB Flasher mode screen saying "Wait USB...". Can I just take out my battery and power on and it will boot in to the previous NAND ROM I had on my HD2?
I've put a picture up of all the files that came with the download. I don't know what I'm doing! I'm new to this stuff.
Click to expand...
Click to collapse
Dont worry.
Press the power button and you will go to magldr menu.
Did you run daf.exe with right click and run as administrator?
If you did and it stil wont install, try unpacking the file you downloade again.
Did you connect the usb cable to the phone, before runing daf.exe?
Sorry, had to ask
Sent from my HTC HD2 using XDA App

lms1407 said:
Dont worry.
Press the power button and you will go to magldr menu.
Did you run daf.exe with right click and run as administrator?
If you did and it stil wont install, try unpacking the file you downloade again.
Did you connect the usb cable to the phone, before runing daf.exe?
Sorry, had to ask
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I tried the power button and it wouldn't go back.
Luckily, I used a different computer and it's installing as we speak. Pheeeewwww!
I didn't even have a .daf file. Only the ones I included in the post above.
If there's any problems, I'll get back on here.

Were you by chance using WinXP on the original PC? Many versions seem to need drivers installed for it to work, while it generally works without such on Vista & Win7.

RAPI.dll (Remote API) is included with ActiveSync or Windows Mobile Device Center. I guess the original machine didn't have the relevant one of them installed, or it did and for some reason RAPI.dll was missing/knackered. (This is just for future reference if anyone comes across this thread looking for possible answers.)
Glad it's working now

Hmmm guess what? I'm stuck flashing a new ROM now. It comes up and says "Wait USB... USB"
But the ROM won't flash?

Skellyyy said:
Hmmm guess what? I'm stuck flashing a new ROM now. It comes up and says "Wait USB... USB"
But the ROM won't flash?
Click to expand...
Click to collapse
What does it display on the phone screen?

lms1407 said:
What does it display on the phone screen?
Click to expand...
Click to collapse
It just has the MAGLDR bar thing with
aMAGLDR V1.12
Build: Jan 12 2011 21:09:22
by Cotulla 2011
_______________
USB Flasher mode
Wait USB... USB
Click to expand...
Click to collapse
That's all it says.

Skellyyy said:
It just has the MAGLDR bar thing with
That's all it says.
Click to expand...
Click to collapse
And when you start installer.exe - run as administrator - it stays on "waiting usb connection?
Check if active sync has "allow usb connections" dissabled! This is if you are on XP.
If this doesn't work, try another build and see what happens.

lms1407 said:
And when you start installer.exe - run as administrator - it stays on "waiting usb connection?
Check if active sync has "allow usb connections" dissabled! This is if you are on XP.
If this doesn't work, try another build and see what happens.
Click to expand...
Click to collapse
Yeah, it comes up screen after it though saying...
[Happen error
Read below for more information
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
"
Click to expand...
Click to collapse

Skellyyy said:
Yeah, it comes up screen after it though saying...
Click to expand...
Click to collapse
Come on, make an effort
http://www.google.com/cse?q=RSPL\RS...ub-2900107662879704:fs7umqefhnf&ie=ISO-8859-1
Go and read the first result on the page
Read the whole thread
Hope this helps finaly

lms1407 said:
Come on, make an effort
http://www.google.com/cse?q=RSPL\RS...ub-2900107662879704:fs7umqefhnf&ie=ISO-8859-1
Go and read the first result on the page
Read the whole thread
Hope this helps finaly
Click to expand...
Click to collapse
I appreciate all your help. But, I think my phone has froze in MAGLDR. Can I just take out the battery and reboot? Or will I have to reset the phone (red button) and flash my phone all over again?

Skellyyy said:
I appreciate all your help. But, I think my phone has froze in MAGLDR. Can I just take out the battery and reboot? Or will I have to reset the phone (red button) and flash my phone all over again?
Click to expand...
Click to collapse
Remove the battery, insert it again.
Hold the power button untill magldr menu appears.
Read the Help thread that i pointed you to.

lms1407 said:
Remove the battery, insert it again.
Hold the power button untill magldr menu appears.
Read the Help thread that i pointed you to.
Click to expand...
Click to collapse
Thank you for all your help kind sir! I didn't know yo could take the battery out while in MAGLDR. Rookie mistake.
I've thanked all your posts in this thread. Thank you!

Just a quick thing.... it's installing on MAGLDR, the ROM I had before had Partitions for DATA2SD, this one doesn't so I formatted it with one singled FAT32 partition. Now on MAGLDR it says, PARTITION LAYOUT NEW
Do you want to reserve date? Do I save it, clear it or abondon flashing?

I clicked to save it. Hopefully I didn't do the wrong thing.

Skellyyy said:
I clicked to save it. Hopefully I didn't do the wrong thing.
Click to expand...
Click to collapse
By saving the old data you might get errors - Force Close applications - later on when the Android system loads.
If mistakes happen you will have to format the card again - properly - and reflash clean.
What build are you flashing?

lms1407 said:
By saving the old data you might get errors - Force Close applications - later on when the Android system loads.
If mistakes happen you will have to format the card again - properly - and reflash clean.
What build are you flashing?
Click to expand...
Click to collapse
Will do. The ROM I was flashing was a clean gingerbread, now I'm using FutureShock MIUI. Recommend it!
Btw, do you install WP7 the same way as you do an Android ROM? Or is it a whole different process?

Skellyyy said:
Will do. The ROM I was flashing was a clean gingerbread, now I'm using FutureShock MIUI. Recommend it!
Btw, do you install WP7 the same way as you do an Android ROM? Or is it a whole different process?
Click to expand...
Click to collapse
It's the same, there is a whole thread about WP7. It should be easy, just remember that WP7 formats your card with it's own partition and then if you want to go back to Android you have to reformat gain.
Take it easy.

NEW TO THIS Please help..
I have rooted, flashed, modded, and repaired dozens of android native phones...
this one was quite different.. However.. i was able to successfully run Android 2.3 on one of my friends HD2's,, and another one is giving me HELL and back..
I had what i thought was stable Android 2.3 ROM after flashing DESIRE HD ROM through Clockwork.. I've been testing ROM's on this phone for a few days.. and today i decided to try to turn on the phone.. every time i turn it on... (tried hard reset),, i get to aMAGDLR V1.11 screen that is BLANK!!! ALL BLACK!!!
I do not know how to actually get the phone to turn on from this point. It is a tmous hd2 and i did flash a ".50" spl and whatnot... but today, this morning.. it decides to act up and i don't know what to do! any one have any ideas?

[Q] HD2 Bricked? Can get to bootloader, BUT...

So my dad tried to flash another ROM on his HD2.
When you simply try to turn it on, it vibrates and the screen goes white and stays that way.
When you go to the bootloader, it looks like this:
http: //seven-days-later.de/bricked.jpg
(Sorry, I'm new here, and not permitted to post links.)
Any try to put any other ROM on it either fails with this, frozen:
http: //seven-days-later.de/freeze.jpg or the program doesn't even manage to connect via USB.
Flashing from SD either just won't work (the white screen lights up shortly and goes away, faster than I can see what it says) or exits with error '00028002 not allow', depending on the ROM we try to flash.
Our best guess is, since the device's internal name is not a valid identifier of an HD 2 (the strange characters on the first screenshot), the ROMs/bootloader doesn't allow them to be flashed. What do you think?
Does anyone have an idea how we can get the system working again?

Ok this is a new one for me, I have never seen this in bootloader before.
I will help you out with the links as others here need to see this, bricked.jpg and freeze.jpg.
Ok you say it will not show USB inm the white bar of bootloader, correct?
Do you have the latest version of ActiveSync (XP) or WMDC (Vista, Windows 7) installed on your computer? Go here if not or not sure. It has USB drivers for the HD2.
Do you know for sure you have a good USB cable?
When you tried to flash via SD card did you use a 4 gig or smaller SD card freshly formatted with a full wipe and Fat 32?
Also do you have a TMOUS (T-Mobile US) HD2 or a International HD2?
Edit: I see from the freez.jpg that you have a International HD2.
If installing the latest version of ActiveSync or WMDC gets USB in the white bar then down load HSPL 4 linked in my guide that I have klinked in my sig and install HSPL 3.03 then try to flash the ROM. You cas use HSPL to revert back to SPL if want once you have flashed.

Gunnsn said:
So my dad tried to flash another ROM on his HD2.
When you simply try to turn it on, it vibrates and the screen goes white and stays that way.
When you go to the bootloader, it looks like this:
http: //seven-days-later.de/bricked.jpg
(Sorry, I'm new here, and not permitted to post links.)
Any try to put any other ROM on it either fails with this, frozen:
http: //seven-days-later.de/freeze.jpg or the program doesn't even manage to connect via USB.
Flashing from SD either just won't work (the white screen lights up shortly and goes away, faster than I can see what it says) or exits with error '00028002 not allow', depending on the ROM we try to flash.
Our best guess is, since the device's internal name is not a valid identifier of an HD 2 (the strange characters on the first screenshot), the ROMs/bootloader doesn't allow them to be flashed. What do you think?
Does anyone have an idea how we can get the system working again?
Click to expand...
Click to collapse
looks like nand corruption... try redoing an original rom from sdcard

Seen this a few times,, corrupted deviceID meaning everything fails, including goldcard, since nothing recognises it as a hd2 so refuse to flash.
No advice for you, other than there are a few threads here with that issue, which you should hunt down and read (search for "corrupted device ID") and of course you should try everything, SD flash, goldcard, hspl,,,sadly I'm fairly sure none of them end well. I hope I'm wrong.
JTAG would maybe do it.

samsamuel said:
Seen this a few times,, corrupted deviceID meaning everything fails, including goldcard, since nothing recognises it as a hd2 so refuse to flash.
No advice for you, other than there are a few threads here with that issue, which you should hunt down and read (search for "corrupted device ID") and of course you should try everything, SD flash, goldcard, hspl,,,sadly I'm fairly sure none of them end well. I hope I'm wrong.
JTAG would maybe do it.
Click to expand...
Click to collapse
I am with Sam here on this one I think JTAG can correct the Device I.D. cause it has a direct connection to the NAND chip and allows you to run diagnostic software on the NAND chip then correct any problems as long as it is not any physical damage to the NAND chip.
PM me if you are interested in JTAG, I can put you in touch with someone that can do it and is a professional.