Database Users

[Q] SOD no matter what build

Well before everyone attacks me with "try searching on forums" responses, i have done that already. So here is my problem. no matter what build i use i will occassionally get sod and have to remove the battery to power it back on. the button lights turn on like its going to power on but no matter how long i wait it wont come out of sleep.
I have all display settings turned off in windows mobile before i boot into android, and i have auto like turned off in both windows and android. I have auto rotate turned off, and screen time out set to 30 min, which actually fixed my problem for a while. it always seems to happen that something happens that i have to power off my phone, and as soon as i do that is when it starts acting up and i get sod. it takes a few tries of taking out the battery for the phone to stop getting sod but after a few days it seems to come back.
I have even tried reformatting my sd card and still had the problem. i have the stock 16 gig sd card it came with. i havent flashed anything on the phone because i dont want to risk screwing up, so you guys are my last resort because i have tried everything.

Time to try different sd card.

In both windows and android, Auto light is off and you manually set the display backlight?
Have you tried the hyperdroid 1.7 version??

Vaizard84 said:
i havent flashed anything on the phone because i dont want to risk screwing up, so you guys are my last resort because i have tried everything.
Click to expand...
Click to collapse
Im pretty sure this is ur problem. Lots of things go wrong with stock.
its not as hard as it seems. just follow the intructions for ur specific hd2.
(look in the usa hd2 forums) if ur a usa hd2 user. IM SURE ITS A STICKY.
IF U WANT TRY THE OFFICIAL UPDATE FROM T-MOBILE!
i have heard good things about it

Unfortunately you have no choice but to flash the HSPL, a custom rom, and a radio. these are easy. ive flashed my phone countless times. I've also flashed other peoples HD2's countless times. Even when the phone was in the middle of flashing and the power went out at my house it did not brick the phone.
If you want to run android as a daily driver (like I do) my best advice is to flash the following.
HSPL (duh lol) http://forum.xda-developers.com/showpost.php?p=6891358&postcount=1893
Radio version 2.12.50 http://www.megaupload.com/?d=9GU2FF3X
WinMo rom http://forum.xda-developers.com/showthread.php?t=734238
(click on the first 'ChuckyDroidRom' picture under downloads in the first post.
You will use this utility to flash the 3.
http://forum.xda-developers.com/showthread.php?t=575524
when/if you download the 3 items, create a folder on your desktop. Name it something simple. Then inside that folder create 3 folders. name them HSPL, Radio, WinMo Rom. extract the downloaded items to their respective folders.
with the customRUU utility. extract the file to each of the folders.
Then,
Flash the HSPL first, the radio second, then the winmo rom.
when finished with those use the format sd card app in windows mobile to format your sd card (the program is set to format to android specs)
then copy whatever android build you want to the sd card.
Enjoy!
if you have any questions you may feel free to PM me. I will be home all day and would not mind helping you.

wow that is a lot easier than i thought well so far its working really nice, i havent got any sod yet, keeping my fingers crossed lol. thanks everyone for the help!

Vaizard84 said:
wow that is a lot easier than i thought well so far its working really nice, i havent got any sod yet, keeping my fingers crossed lol. thanks everyone for the help!
Click to expand...
Click to collapse
Yeah I promise you it was your radio/rom version. I had the EXACT same problem and nothing fixed it until I flashed and updated my radio. sometimes you just have to bit the bullet and dive deep!
cheers on your fixed phone, and knock on wood for no more SOD!

If you do experience SOD again. I recommend a faster SD card. I was having issues with any build I was using. Up to date flashed radio and lite WM rom, my only cure was faster SD card. I went from the stock 16GB C2, to an 8GB C6 (17.99 from Amazon), and I have not experienced SOD anymore. I have issues where sometimes the screen will not come back on right away, and I have to wait a few seconds, but it never sleeps on me anymore.

[Q] Kernels

ive tried many lovely roms on my dream, but all but one have horrific battery life, the one exception is gingeryoshi 1.1 with the new farmatito kernel, so i figured i could just install it to my preferred rom and id be away, however it seems not so simple as all that
first i tried installing it to the cos-ds image i was running at the time, it simply killed that stone dead, wouldnt boot past the boot anim. so i decided to test it on my current fave rom, beatmod 2.2, i did and it booted and seemed to run fast and reasonably problem free until it came to installing an apk i had on my sd card, where i found that it wouldnt read the card at all, it said no card inserted and on pulling and reinserting it displays damaged SD card and often causes many force closes on other running processes, so what is it that i need to change to get it working, it seems close enough that itll just need some tweaks so if someone could point me in the right direction id be grateful, just a "read this, this and this" and some links is plenty (the info may well be on here already but digging it out can be a nightmare and i havent got that far on my own yet, its a BIG forum)

so what exactly are you trying to figure out? how to fix your sd card or how to get the kernel working? your sd card may have actually just died because believe it or not those things dont last as long as you think.. thore more times you copy things on and off them the quicker they die.. but as far as the kernel problem im not sure exactly how it all works i usually get the recommended kernel for rom... usually on the post with the rom link

no the sd card is fine, its any sd card when used in beatmod with that kernel, so getting the kernel working, what i want is a rom thats a little faster than the somewhat sluggish gingeryoshi but is compatible with the farmatito kernel which solves my short battery woes
ive actually even tried cos-ds and used their recommended farmatito kernel but even then it still leaves me stuck at the g1 boot screen. infact as yet beatmod is the only rom i have got to boot at all with a different kernel than the one that comes with the rom. im not sure if its something that im doing or possibly that the g1 is on its way out, its just refused to use the backup i made before testing the greenromproject rom (which also didnt boot, again stuck at the g1 screen) as the md5 check failed and what with it being picky about which backups it will and which it wont boot anyway im beginning to suspect there may be more to it than a software complaint
and now that ive finished typing i look over at my phone to still see that big g1 glaring at me, none of my current backups now work ah well try a fresh install i guess

Need Help. PLEASE!!!!!!

I can no longer get android to run on my HD2. Here are the details to my problem. Please I really need help, will make it well worth the while of anyone that can sort this problem out for me.
First off, I had been running android on my device for about a month. Then it started just going off and freezing at the android boot logo. Nothing I did would work unless I reinstall the rom.
Then that just stopped working and even after reinstalling a rom (nand) it would never get past the android boot logo after the go go go screen. It would just stay there then restart and the restart loop continues.
I have tried
- task 29
- flashing an official stock rom
- trying different radios even though the one in my sig worked with android just fine
- reflashing HSPL 2.08, MAGLDR and recovery
- formatting my SD cards (over and over again)
- trying different roms....etc
Nothing works. And I have lost count of how many times I have gone through all this.
Please take note that I did have android running on my EU HD2 with the HSPL, radio and rom in my sig on this very phone so I at least know what I am doing.
I just dont get this issue, cause windows mobile runs just fine on my device every single time. My cards read fine too. And even when trying to run an SD rom build, after haret starts up it cuts to the HTC logo and just hangs there too. And I am assuming that if it was my battery or my battery pins it would at least affect the phone generally and not only when trying to boot android.
Please, I really need help as this phone is practically useless to me now.
Any help would be greatly appreciated.

Lorddeff07 said:
I can no longer get android to run on my HD2. Here are the details to my problem. Please I really need help, will make it well worth the while of anyone that can sort this problem out for me.
First off, I had been running android on my device for about a month. Then it started just going off and freezing at the android boot logo. Nothing I did would work unless I reinstall the rom.
Then that just stopped working and even after reinstalling a rom (nand) it would never get past the android boot logo after the go go go screen. It would just stay there then restart and the restart loop continues.
I have tried
- task 29
- flashing an official stock rom
- trying different radios even though the one in my sig worked with android just fine
- reflashing HSPL 2.08, MAGLDR and recovery
- formatting my SD cards (over and over again)
- trying different roms....etc
Nothing works. And I have lost count of how many times I have gone through all this.
Please take note that I did have android running on my EU HD2 with the HSPL, radio and rom in my sig on this very phone so I at least know what I am doing.
I just dont get this issue, cause windows mobile runs just fine on my device every single time. My cards read fine too. And even when trying to run an SD rom build, after haret starts up it cuts to the HTC logo and just hangs there too. And I am assuming that if it was my battery or my battery pins it would at least affect the phone generally and not only when trying to boot android.
Please, I really need help as this phone is practically useless to me now.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried running a CLK build or just MAGLDR or SD builds?
As far as i know (sorry if this is nonsense ) the HD2 runs natively on ppp not on rmnet, magldr (and sd?) pushes something in the radio so that rmnet can be used, maybe something in that direction went wrong with your phone?

Cheech1976 said:
Have you tried running a CLK build or just MAGLDR or SD builds?
As far as i know (sorry if this is nonsense ) the HD2 runs natively on ppp not on rmnet, magldr (and sd?) pushes something in the radio so that rmnet can be used, maybe something in that direction went wrong with your phone?
Click to expand...
Click to collapse
Well I have only been trying MAGLDR and SD roms but never CLK. Guess I can give that a shot. But assuming something weird is going on with my radio, shouldn't it have fixed itself considering the amount of radios I have used and the amount of task 29s I have done?
Thanks for the suggestion though, will give that a go today.

Lorddeff07 said:
Well I have only been trying MAGLDR and SD roms but never CLK. Guess I can give that a shot. But assuming something weird is going on with my radio, shouldn't it have fixed itself considering the amount of radios I have used and the amount of task 29s I have done?
Thanks for the suggestion though, will give that a go today.
Click to expand...
Click to collapse
Well before i get flamed by those who know better, i would ask you to look for threads covering this topic, i.e. the difference between ppp and rmnet and which one is used with which one etc.
I have read in another forum that the hd2 runs natively with ppp, but magldr pushes something "in" the radio rom while booting, so the radio looks like a desire, so the android builds can run on rmnet...
Or something like that, what i have gathered from this is, that there is a difference and since it sounded like you were running out of options, i thought i´d propose installing a clk build

Lorddeff07 said:
I have tried
- task 29
- flashing an official stock rom
- trying different radios even though the one in my sig worked with android just fine
- reflashing HSPL 2.08, MAGLDR and recovery
- formatting my SD cards (over and over again)
- trying different roms....etc
Click to expand...
Click to collapse
Can you elaborate "formatting my SD cards" a little?
As in how, which tools, were was the partitioning done if any?

Lorddeff07 said:
Well I have only been trying MAGLDR and SD roms but never CLK. Guess I can give that a shot. But assuming something weird is going on with my radio, shouldn't it have fixed itself considering the amount of radios I have used and the amount of task 29s I have done?
Thanks for the suggestion though, will give that a go today.
Click to expand...
Click to collapse
Hi,
Sometimes boot loops occur when the battery pins are out of shape.
Make sure all your battery pins are aligned and see if that helps.

Cheech1976 said:
Well before i get flamed by those who know better, i would ask you to look for threads covering this topic, i.e. the difference between ppp and rmnet and which one is used with which one etc.
I have read in another forum that the hd2 runs natively with ppp, but magldr pushes something "in" the radio rom while booting, so the radio looks like a desire, so the android builds can run on rmnet...
Or something like that, what i have gathered from this is, that there is a difference and since it sounded like you were running out of options, i thought i´d propose installing a clk build
Click to expand...
Click to collapse
Looking into trying a CLK build now. Actually just finished downloading one.
Cheech1976 said:
Can you elaborate "formatting my SD cards" a little?
Click to expand...
Click to collapse
Ok, i have a total of 3 SD cards. One 16GB, one 4GB and the last one 2GB. I have used both gParted and partition wizard. Did full 30 mins (approx) wipes on the cards and had them formatted to fat32. For the 16GB card I try that with the ext3/4 partions. Tried using both 4kB and 32KB cluster sizes.
And again, I had actually got android running on my phone before. And even tried different roms at that time so I have some idea what I am doing. I don't have any issues reading my cards either from a card reader or through the phone.
malybru said:
Hi,
Sometimes boot loops occur when the battery pins are out of shape.
Make sure all your battery pins are aligned and see if that helps.
Click to expand...
Click to collapse
Yeah read about that, I have tried straightening my pins and all that but nothing changes. And I would think that if the pins are the issue then I would at least hav some issues running windows mobile 6.5 too. I have never had such issues running WM ever. Android on the other hand just refuses to run.

Lorddeff07 said:
Yeah read about that, I have tried straightening my pins and all that but nothing changes. And I would think that if the pins are the issue then I would at least hav some issues running windows mobile 6.5 too. I have never had such issues running WM ever. Android on the other hand just refuses to run.
Click to expand...
Click to collapse
Hi,
The only thing I can think of is maybe some corrupt software along the way.
May I suggest using KSUBEDI's TOOLKIT (Don't forget to thank him).
Run through the whole process using his toolkit.
It worked for me.
Start from
HSPL 2.08 HSPL
Task 29
Radio HERE
Magldr
CWM partition for the ROM you intend to use
ROM

malybru said:
Hi,
The only thing I can think of is maybe some corrupt software along the way.
May I suggest using KSUBEDI's TOOLKIT (Don't forget to thank him).
Run through the whole process using his toolkit.
It worked for me.
Start from
HSPL 2.08 HSPL
Task 29
Radio HERE
Magldr
CWM partition for the ROM you intend to use
ROM
Click to expand...
Click to collapse
Just did all that (again). And exactly in that order. As always, it installs just fine but it always hangs on the android logo right after the go go go screen for about 20-30 secs then it restarts. Over and over again.

Lorddeff07 said:
Just did all that (again). And exactly in that order. As always, it installs just fine but it always hangs on the android logo right after the go go go screen for about 20-30 secs then it restarts. Over and over again.
Click to expand...
Click to collapse
Hi,
What ROM are you installing, and what CWM partition are you using?

Lorddeff07 said:
Ok, i have a total of 3 SD cards. One 16GB, one 4GB and the last one 2GB. I have used both gParted and partition wizard. Did full 30 mins (approx) wipes on the cards and had them formatted to fat32. For the 16GB card I try that with the ext3/4 partions. Tried using both 4kB and 32KB cluster sizes.
And again, I had actually got android running on my phone before. And even tried different roms at that time so I have some idea what I am doing. I don't have any issues reading my cards either from a card reader or through the phone.
Click to expand...
Click to collapse
Didn´t mean to let it sound like you don´t know what you´re doing, just trying to narrow it down and the sd cards can be the culprit for so many bugs, so it was worth a shot
Lorddeff07 said:
Just did all that (again). And exactly in that order. As always, it installs just fine but it always hangs on the android logo right after the go go go screen for about 20-30 secs then it restarts. Over and over again.
Click to expand...
Click to collapse
malybru said:
Hi,
What ROM are you installing, and what CWM partition are you using?
Click to expand...
Click to collapse
Especially the NAND partition used in flash.cfg would be interesting, maybe there´s something wrong with that, that would be consistent with the failure to boot, wouldn´t it?
Other than that, i have to admit, slowly but surely this leaves my area "of expertise"
I sure hope you get your phone running again! I´ll keep my fingers crossed!

malybru said:
Hi,
What ROM are you installing, and what CWM partition are you using?
Click to expand...
Click to collapse
I am installing HyperDroidGBX-v12[GRI54-2.3.3][a2sd+][TytR8.3] and using the required 150mb partition size. I had got this very rom and RAFDROID rom (though with a 400mb partition) to work on my phone previously.
I also got the a couple of SD based roms to work on my device before nand roms became available now even those dont work too.
Just tried CLK for the first time and flashed the CLK version of the aforementioned rom. Been on the white HTC screen for about 10mins now.

Cheech1976 said:
Didn´t mean to let it sound like you don´t know what you´re doing, just trying to narrow it down and the sd cards can be the culprit for so many bugs, so it was worth a shot
Especially the NAND partition used in flash.cfg would be interesting, maybe there´s something wrong with that, that would be consistent with the failure to boot, wouldn´t it?
Other than that, i have to admit, slowly but surely this leaves my area "of expertise"
I sure hope you get your phone running again! I´ll keep my fingers crossed!
Click to expand...
Click to collapse
Trust me, no offense taken what so ever .
I am aware that SD card errors could be the issue, but all three SD cards? even stranger since I have never used 2 of those 3 for any android install.
What really puzzles me though is that regardless of whatever issues i seem to be having... windows mobile runs just fine every single time. My only guess now may be that teher may be something wrong on the hardware side with how my SD card and phone syncs so something always goes wrong during the install. If that is the case the only possible solution would be if it was some how possible to install a rom directly from my PC without using an Sd card at all.

Lorddeff07 said:
Trust me, no offense taken what so ever .
I am aware that SD card errors could be the issue, but all three SD cards? even stranger since I have never used 2 of those 3 for any android install.
What really puzzles me though is that regardless of whatever issues i seem to be having... windows mobile runs just fine every single time. My only guess now may be that teher may be something wrong on the hardware side with how my SD card and phone syncs so something always goes wrong during the install. If that is the case the only possible solution would be if it was some how possible to install a rom directly from my PC without using an Sd card at all.
Click to expand...
Click to collapse
Hi,
That would mean making a DAF.exe file and install it the old fashioned way.
Sadly,beyond my level of expertise.
Good luck.

Lorddeff07 said:
Trust me, no offense taken what so ever .
I am aware that SD card errors could be the issue, but all three SD cards? even stranger since I have never used 2 of those 3 for any android install.
What really puzzles me though is that regardless of whatever issues i seem to be having... windows mobile runs just fine every single time. My only guess now may be that teher may be something wrong on the hardware side with how my SD card and phone syncs so something always goes wrong during the install. If that is the case the only possible solution would be if it was some how possible to install a rom directly from my PC without using an Sd card at all.
Click to expand...
Click to collapse
Sorry but i am at a loss for any further possible advice for you. I would propose the build i am using for you to install.
It installs with the according daf.exe and after that you can install the zip file via cwm. I never flashed another android build myself, what with all this nand partitioning (i have heard of it, but never had to set it up myself), so i don´t really know how the nand partitioning is done without daf.exe and the according flash.cfg file.

Cheech1976 said:
Sorry but i am at a loss for any further possible advice for you. I would propose the build i am using for you to install.
It installs with the according daf.exe and after that you can install the zip file via cwm. I never flashed another android build myself, what with all this nand partitioning (i have heard of it, but never had to set it up myself), so i don´t really know how the nand partitioning is done without daf.exe and the according flash.cfg file.
Click to expand...
Click to collapse
Thanks, will try. I have given up though. been working on this thing for too long. Guess its time to buy the galaxy s2. I really loved this phone. And windows mobile just doesn't cut it.

Lorddeff07 said:
Thanks, will try. I have given up though. been working on this thing for too long. Guess its time to buy the galaxy s2. I really loved this phone. And windows mobile just doesn't cut it.
Click to expand...
Click to collapse
Hi,
Just before you bin it,how have you been formatting the sd card?
Have a look at this:
"You should also properly format your sdcard with Panasonic SDFormatter (Full+Overwrite+size adjust). Then in recovery>advanced>sd partition (1GB+0MB swap) If you have a EU HD2 and need the extra data storage/rom requires it. "
Worth a shot.

Dont give up!
Might be a long shot, But have you tried turning off your antivirus software during the installation? Ive seen a few of your posts about and i hope you get it to work again. Bet your sick of the sight of task29 lol

malybru said:
Hi,
Just before you bin it,how have you been formatting the sd card?
Have a look at this:
"You should also properly format your sdcard with Panasonic SDFormatter (Full+Overwrite+size adjust). Then in recovery>advanced>sd partition (1GB+0MB swap) If you have a EU HD2 and need the extra data storage/rom requires it. "
Worth a shot.
Click to expand...
Click to collapse
yeah I have tried that too. Still leaves me hanging at the android logo right after the go go go screen. Truth is that I have come to the conclusion that nothing i am doing will actually work. Cause all these things mentioned now I have already done and didn't even need to do half of them at one point when i was actually running android on my phone.
The fact that I cant even run the SD card builds of android just goes to show that something must be very wrong with my phone now. It could be battery related or something but that doesn't make sense either cause WinMO 6.5 roms work fine every singel time.
I just dont get it really.

fuuunkdat said:
Might be a long shot, But have you tried turning off your antivirus software during the installation? Ive seen a few of your posts about and i hope you get it to work again. Bet your sick of the sight of task29 lol
Click to expand...
Click to collapse
Lol.... you have no idea lol
Its sad no doubt, but I am actually happy for the amount of help offered by a lot of ppl here in the xda community.
So at least I am taking it all in good spirits. Oh, I have probably tried that at one point too....
The only thing I can think of now is to flash my HSPL back to spl 1.66 and revert back to factory setting, then try and reflsah the 2.08 HSPL. Though I dont know what difference taht will make considering how many times i have reflsahed the very same 2.08 HSPL so at least i know I have a clean fresh one on my phone now lol.

stuck

hello all i was trying to install the android on my hd2 phone
got all the way to where i ran the rom updated utilerty and now its stuck on the htc screen ,at load up of the phone
i have read about this happening ,
and read that you hold the volum button and power and boots up ,,,which it does goes to system and the plug it in to my laptop ,,,,,
then get the USB on the screen of the phone ,,,,
but i dont have a rom to back it up with ,,could some one please point me in the right direction of where to get this fome and how to get it to work thanks

moose579 said:
hello all i was trying to install the android on my hd2 phone
got all the way to where i ran the rom updated utilerty and now its stuck on the htc screen ,at load up of the phone
Click to expand...
Click to collapse
I assume (since about ten people per day ask exactly this) that you flashed magldr but magldr didn't start as expected? This is caused by (as I type half a dozen times a day) by not having 2.08.hspl AND a compatible radio.
i have read about this happening ,
and read that you hold the volum button and power and boots up ,,,which it does goes to system and the plug it in to my laptop ,,,,,
Click to expand...
Click to collapse
bootloader
then get the USB on the screen of the phone ,,,,
but i dont have a rom to back it up with
Click to expand...
Click to collapse
not sure what that means, sorry.
,,could some one please point me in the right direction of where to get this fome and how to get it to work thanks
Click to expand...
Click to collapse
You haven't given any real details as to what you have done so far.
Details details details.
So, tell us what you did so far, please. Please be detailed, with names, filenames, versions, etc. not just 'i flashed that thing and now nothing works'

hope this helps more
ill start from the start
i first ran this file HSPL3_PKG.exe this run fine without any problems
then i ran this file rom updateutility from this rar folder ive downloaded called DFT_LEO_MAGLDR113_DAF
now this is where it all went wrong ,i ticked all the boxes and went thought the set up by following this video
got to 6;08 into the video and followed the steps
then got to 7;04 in the video and this is where the phone stayed on the htc screen for 30 mins ,,,and its done nothing
so i unplugged it
now i read that its possible to get the phone back to booting up with another offical rom from htc but carnt find the rom that ill need ,,plus the windows mobile wont reconise my phone in usb mode
hope this helps you a little more to solving my problem

and sorry i carnt post the link to the video yet as ive not done my 8 posts

ok, so its all fine so far, you just haven't yet done the next step, which is flash a compatible radio. (had you changed the radio after flashing hspl and before flashing magldr, magldr would have started straight away)
(I shall assume that you have a regular hd2, not a t mobile US model, since you haven't said, if it IS a tmous, then its a different problem)
download radio 2.15.50
enter bootloader
plug in usb
count to 5
run customruu to flash that radio
reboot
magldr should now start

thanks for your reply
ill go and find this radio now and keep you posted
thankyou

you rock dude
thank you so much for your time posting ,,
100% working andriod now
anything eles i should know please post

Lovely.
Only thing to know is that you shouldn't need to flash radio or magldr again now, if you want a different sized rom you may have to reflash cwm to change partition size, but if you ever have probs booting or whatever, nine times in ten someone will tell you to task29 and reflash stock and start over,,,, nine times in ten that's massive overkill.
Read read read is the best advice I can offer, see what issues others have and read the answer,, one day that issue might be yours, and you'll have a head start solving it. Never panic and start random flashing, that always ends badly, and means any help request posts are harder to work with.

thank for your reply
just a quick question for you
ive got a 16gb sd card in with about 300 app/games ,,and ive installed about 20 so far but now phone says memory full ,,should they be installing on sdcard instead of the phone memory
or is this normal for the phone memory to run out so fast

Depends on the rom, some leave 200+ free, some far far less. That's why most roms support an ext partition, which the phone treats as internal.
Backup your SD card (it will be wiped) start phone into cwm, then (I think its) advanced - format SD card, or something like that. Create a 1 or 2 gb ext partition, swap 0, and reflash the rom. C
The rest of the SD will be formatted to fat32 just like it is now.
It will detect the ext partition and use it as internal memory automatically. You should not choose the option to "move app to SD card", that will take the app off the ext partition and put it in the fat32 partition,, and some apps wont work from fat32.(angry birds for example)

Hoping to save an HD2...

Well this one's a doozy of sorts, I'll try to be brief but any advice or assistance is welcome. Got a TMOUS HD2 on Saturday, it "worked" for a bit of time with the stock WinMo6.5 on it (no, I didn't care to look at the version, etc) and after having it for a few minutes to verify everything from a hardware perspective was working, I set out to do the usual process to get Android on it. I just wanted to get a CM7.2 build on it, preferably the actual CM7.2 and not a more customized ROM.
I have done the following:
- HSPL 2.08 - check, successful (as noted on the bootloader screen), done using HSPL4
- Task29 - check, successful (as far as I can tell), done from bootloader (VolDown+Power, Task29 provided by doloop single exe)
- Radio installed: 2.15.50.14 TMOUS (yes, it's the TMOUS version), check, successful (as far as I can tell), done from HD2Toolkit 4.2.0.1
- MAGLDR 1.1.3, check, successful, done from bootloader (DFT_LEO_MAGLDR113_DAF installer)
Now, at that point it was basically blank, obviously, so I decided to try and get CWM installed and that's when everything seems to have gone wrong. I get the FATAL HIT1 errors, it won't get past that. I read a post in the hundreds if not thousands I've been reading over where someone suggested when that error comes up, do the VolUp+VolDown+Power and do the reset - it only takes a half second since the device is already blank but some people reported in posts that it seemed to fix the FATAL HIT1 error and got CWM to actually load.
Didn't help in my situation. So I decided to start over at that point and flash the stock TMOUS 2.13.531.1 nbh (downloaded direct from T-Mobile, extension changed to zip, RUU_signed.nbh extracted to microSD card and renamed to leoimg.nbh) and attempting to do it from the bootloader.
At this point that aspect starts to work but it gets to about 8% (the same place it gets when using the actual T-Mobile ROMUpdateUtility method in Windows) and then dies. But the difference with using the microSD card method is that it tells me the following:
RADIO_V2 - RSA FAIL
in big red letters so I'm suspecting there's something going on with the radio that's just not kosher with the installer. I'm not sure how to proceed at this point - I'd like to get the HD2 functional again, preferably getting the stable CM7.2 ROM on it (not a big huge fan of ICS and JB is simply not my choice right now on the HD).
Problem is I don't know how to proceed at this point. If I can get it back to the stock WM6.5 that's fine for the time being so the device works, then I'll see what's going on with getting Android on it later, but I figure I'd rather ask a question or two, or three, before sitting here flashing radio after radio not being sure just what's going on and how best to get this issue resolved.
As noted, any advice or suggestions is welcome. I'm still trying various things at this time, including figuring out which radio to fall back to and test but, it's not going well so far.

loads of threads about this, my name for it is 'stuck radio' but it can also affect the spl too. Basically, there is corruption somewhere in the first area of nand, where the spl and radio live. whether thats software corruption (pray that it is, you may just stand a chance) or hardware corruption, you can't tell. the fact that magldr flashed would suggest its not as critical as normal, , some people get rsa radio fail and nothing at all works, no task 29, changing spl doesnt work, nothung at all. Often something seems to work (hspl gives success, for instance) but nothing actually changes after reboot.
So, first thing to try is - phone into a baggie, baggie into freezer, 20 / 30 mins later get it out, and real quick get the sd card in there already with the tmous stock rom as leoimg.nbh on there, and straight into bootloader, , see if it flashes past the radio section (the radio is flashed at roughly 6 - 10%, thats why you;re hanging at 8%, , 8% or 9% are the main reported percentages , lower % seems to involve the spl more (as you would expect, it is the first thing to be flashed)
There have been a few successes using teh freezer trick, and also a few more where JTAG has fixed it, but as often as not it never gets fixed.
failing that, see if you can flash a custom winmo 6.5 rom, because although the radio is failing to flash, it may still be in working order, and since custom roms dont include a radio, it may well flash, giving you at least a partially working phone.

Yah, the more I dig into it the more it's obvious there's an issue with the radio (like, duh ). I'm attempting to flash that Dutty's Leo Sense 2.5 that I saw mentioned in several posts by people that said they had success getting the device working at least to some degree - I grabbed the ROM, extracted the contents, copied the nbh to the microSD card, renamed it to leoimg.nbh, and at the moment it's just crossing the 50% point so, that is some progress at least (probably because it doesn't have a radio as you stated).
Will see what happens, but it is frustrating to appear to be able to do everything but actually get the radio flashed. HSPL flashes work after the reboot, Task29 always works (or appears to), MAGLDR only gives me issues when I try to get into AD Recovery from time to time, and so on. The usual HD2 issues I suppose.
This is my 5th HD2 and I'd like to get it working just like the others I've owned - none of them had anything like this much difficulty with getting Android (or anything at all) working properly so, maybe my luck ran out when I decided to get this one, who knows.
While I normally always find the TMOUS version of the HD2 here in pawn shops in Vegas, in the past week there have been 4 or 5 international unbranded models that popped up but, I avoid 'em since I believe the TMOUS variant is the better choice. Got this one for $75 and swapped a decent battery from one of the international ones when the clerk wasn't looking.

So much for that idea, either way (from microSD card or from Custom_RUU) the Dutty's ROM just hangs at the white/pink "stick together" screen and does nothing else. I then attempted to do a regular install of the stock TMOUS ROM again, no dice.
Geez... this stuff sucks sometimes.
Still hoping, of course.

ah thats a shame. the only other thing that comes to mind is seeing one or two threads with teh same problem where the poster simply tried again and again with the various versions of the (correct!) stock rom, and suddenly it flashed, and once teh radio was replaced it all worked again. I would have thought though that if it were going to do that, the freezer trick would also have worked.
I'd definitely try the three released stock tmous roms, , 2.10, 2.13 and 3.14, anbd perhaps some of the lower ones, too, , , see the 't mobile test & stock roms' thread in the tmous section DO NOT flash the first few, since the first one will brick it, and the next two or three have manufacturing spls, which can prove dificult to remove. (Not that you have anything to lose.)
flash from sd card., no point messing with the .exe, , more likely to work from sd card.
Heres a thought, , , forget the internal nand completely, , set up an ext4 partition, and then using sd card based recovery, flash an android rom using nativeSD. So long as magldr can be succesfully pointed at an sd card folder, you needn't use teh nand at all.

Dammit, no luck with any SD or NativeSD either. It simply won't ever get past the GO GO GO! event, no matter what I do. Tried several different recoveries (accessed from MAGLDR) and every time they just stick at GO GO GO! and never do anything past that. It DOES note the SD card is there, MAGLDR can access it to load the kernel, but it always ends up stuck at GO GO GO! and that's that. I was thinking if I could just get some type of recovery loaded (TWRP, CWM, I don't care) then perhaps I could do something more but, it's just a NO GO GO GO!
I did find that leodiag.nbh thing and gave that a shot, the diagnostic portion won't start because of the radio timing out (go figure, with the bad radio flash) so that won't even run, and the reset function doesn't either as it only sees the microSD card and still won't work.
It's like I feel like I'm missing one single thing that could turn it all around but, I'm tired of messing with it. Found the suggestion to hold in the reset button (mine is white, never seen a yellow or red one so...) and then turn the power on but it never does a reboot no matter how long I wait with the reset button still depressed.
Guess it's just not gonna happen this time...

yea unfortunately that's very often the way these turn out. the radio is blocking flashes from happening, and android from loading.
Do make sure you've given the freezer trick a good chance before you give up, i've read threads where the flash suddenly took after several attempts, (however in all fairness, if the freezer trick does help, it is usually indicative of hardware overheating problems anyway)

Well, against my better judgment but having enough experience (read: decades) with consumer electronics I figure the freezer thing - since it does actually work with hard drives in some situations - couldn't hurt.
Sure enough, after only about 2 minutes in the freezer (laying on some frozen food) I gave the SD update a shot and sure enough it finished, and after taking it out of the freezer a few minutes later, it booted into Windows Mobile just fine but, of course, then comes the letdown.
It froze up (not literally in terms of temperature), rebooted, then rebooted again before it got back into Windows Mobile, then on the 3rd reboot it just stopped and was stuck at the "stick together" screen where it simply won't get past.
So, obviously this one is suffering from the overheating issue, and I don't have access to an SMD oven or a proper heat gun (not that I'm going to go that far to revive it), so it's on craigslist for sale as-is presently. Funny thing is I've had 23 people respond for it since I know and they know and we here at XDA know all about how popular the HD2 is, even one like this one with potential good parts for use in some other one.
Let's hope someone actually shows up with cash, could use it for bills.
Thanks for the information, sam.

By the way would someone have a spare volume button ?
Sent from my HTC HD2 using xda app-developers app