Database Users

How do I know if I can flash my HTC HD2? (touchscreen not working)

Hi!
The touchscreen of my phone almost doesn't work. I've read many topics about this in different forums and maybe a solution would be to reinstall all from 0 (resetting the phone with that yellow button when you revome the back doesn't work anymore).
So, I want to try to install android hoping this will solve the problem. If not, my phone will be a thin brick in a drawer.
Since the touchscreen is not working correctly, I can't go to see the details in the menu.
The phone was flashed once and currently has a rom called BSB beast 6 and when I turn it on, this red numbers appears:
2.10.50.26
15.39.50.07u
2.11.86834 8g
Current OS is Windows Mobile 6.5
I believe android will work with the current rom without the need of installing another one before, right?
Would recommend me one rom (android NAND) to put? because I saw a lot in thread here and I don't really understand what the differences would be. I just want the phone to work
I hope this is enough information
Thanks a lot!

If you want to flash Android what you need to do is...
Make sure you have 2.08.HSPL (I'm assuming you do as you have a custom ROM).
Then flash the newest radio (2.15.50.14)
Flash MAGLDR
Flash a NAND ROM of your choice.
Though I doubt that will fix the problem. Your digitizer is probably gradually dieing. You can easily get it fixed for about $80.

alc112 said:
Hi!
The touchscreen of my phone almost doesn't work. I've read many topics about this in different forums and maybe a solution would be to reinstall all from 0 (resetting the phone with that yellow button when you revome the back doesn't work anymore).
So, I want to try to install android hoping this will solve the problem. If not, my phone will be a thin brick in a drawer.
Since the touchscreen is not working correctly, I can't go to see the details in the menu.
The phone was flashed once and currently has a rom called BSB beast 6 and when I turn it on, this red numbers appears:
2.10.50.26
15.39.50.07u
2.11.86834 8g
Current OS is Windows Mobile 6.5
I believe android will work with the current rom without the need of installing another one before, right?
Would recommend me one rom (android NAND) to put? because I saw a lot in thread here and I don't really understand what the differences would be. I just want the phone to work
I hope this is enough information
Thanks a lot!
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showpost.php?p=12105680&postcount=1

[Q] - Touch Screen stopped working/Help

All of a sudden my touch screen stopped responding to me, so I thought it was a rom error and went into clockwork from boot and reflashed it 4 times now and I still can't get it to see the touch screen. It was working just fine and mid message it just stopped working.
Can anyone help me with this? I tried a reset holding down the yellow button on the back too.

Mine just did the same thing. If it's in warranty.. Just send it in.
It's the digitizer, usually.. The connections for the digitizer are right under the Call End button (the physical red one) I believe.. I've just been repeatedly pressing that button multiple times and eventually the screen will work.. until I lock it or it decides to stop, which is rarely does if the screen never goes off.

Xura08 said:
Mine just did the same thing. If it's in warranty.. Just send it in.
It's the digitizer, usually.. The connections for the digitizer are right under the Call End button (the physical red one) I believe.. I've just been repeatedly pressing that button multiple times and eventually the screen will work.. until I lock it or it decides to stop, which is rarely does if the screen never goes off.
Click to expand...
Click to collapse
SOB! Really? my end call button always felt weird for months now. I got the extended one you pay for each month on your bill, does that cover it? Also do I need to reflash it back to windows to send it back?

RiffyDivine said:
SOB! Really? my end call button always felt weird for months now. I got the extended one you pay for each month on your bill, does that cover it? Also do I need to reflash it back to windows to send it back?
Click to expand...
Click to collapse
yes flash your stock windows rom..from sd card method...download your stock rom from the tmobile site or htc site which ever suits your phone ..extract the file and then search for the largest .nbh file ...rename it to LEOIMG.nbh ..place it on you sd card and follow instructions.. after complete you should now send it in for warranty

I got the same problem. Is there some video how to change the touch screen? Are there some different models on the market or should I buy the first that ebay gives me?
I have the TMOUS version
thanks

RiffyDivine said:
SOB! Really? my end call button always felt weird for months now. I got the extended one you pay for each month on your bill, does that cover it? Also do I need to reflash it back to windows to send it back?
Click to expand...
Click to collapse
I believe any warranty will cover a defect like that granted there's no physical damage or water damage (the little water strip on the inside).
Before you send it in.. MAKE SURE that you flash everything back to stock. They would LOVE a reason to not have to fix it for you..

i have a touch screen problem i was using the hyperdroid rom.. i woke up the next day and the screen wouldnt wake up so when i restarted the phone it stuck on the go go go screen.. then i flashed a winmo stock rom and the screen stopped responding... i also did a task 29 then installed magldr then when i tried to flash CWM it didnt enter it.. i dont know is it possible that since i have the CWM problem so my problem is software related? is there a way to fix it?? please help me..
i have no warranty so if im fixing it it'll be on my expense

guess.whoo said:
I got the same problem. Is there some video how to change the touch screen? Are there some different models on the market or should I buy the first that ebay gives me?
I have the TMOUS version
thanks
Click to expand...
Click to collapse
yours is a tmobile hd2 ... you have to buy a specific tmobile hd2's digitizer/touch screen (since it is a bit larger than the eu hd2s) and then fix it .. click on the thanks button if i helpedd

yma900 said:
i have a touch screen problem i was using the hyperdroid rom.. i woke up the next day and the screen wouldnt wake up so when i restarted the phone it stuck on the go go go screen.. then i flashed a winmo stock rom and the screen stopped responding... i also did a task 29 then installed magldr then when i tried to flash CWM it didnt enter it.. i dont know is it possible that since i have the CWM problem so my problem is software related? is there a way to fix it?? please help me..
i have no warranty so if im fixing it it'll be on my expense
Click to expand...
Click to collapse
yours is a hardware problem ... i had the same problem once upon a time.. i had to send it for repar ...they changed the touch screen for INR 5000 i.e. about $100
.mind it it is not a software related issue probably your screen conector might have become llose or disconected..try pressing the call end key hard 2 or 3 time then it should work temporarily i.e. 10 to 15 seconds

Weird, left it upside down all night when I was sleeping and it's working again. So still going to send it in, I will flash it back to stock when the new one shows up
Never mind crapped out for good this time, having tmob replace it.

yours is a hardware problem ... i had the same problem once upon a time.. i had to send it for repar ...they changed the touch screen for INR 5000 i.e. about $100
.mind it it is not a software related issue probably your screen conector might have become llose or disconected..try pressing the call end key hard 2 or 3 time then it should work temporarily i.e. 10 to 15 seconds
Click to expand...
Click to collapse
so do u think that if i fix the touch screen issue i'll be able to enter CWM?? i mean isnt there some problem that needs a JTAG? i really am confused and i am willing to go to a repair center to fix it today but if i fix the screen and still cant use android so i wont benifit anything..
i tried to press the call end botton hard for more than 3 times and nothing worked... so do u still think that its the connector that is broken?

Okay they are sending me a new phone, so what all should I do to the old one before it goes back? I can't use the touch screen at all but I can still get into clockwork and such.

Yup your screen connector is probably broken ..so send it in for a fix ...when you get it back just flash clk or magldr ..and then flash cwm partition it will work ..I think u are making a mistake while installing the clock work recovery mod. The cwm problem is not at all hardware related probalby you did something wrong. good luck. But flash official stock Windows Rom using SD care method.
Edit :the jtag has to be done only when you Brick your device I.e you device doesn't turn on due to flashing a wrong Windows Rom (flashing Android doesn't pose any threat )
Sent from my HTC HD2 using XDA App

siddharth singh said:
Yup your screen connector is probably broken ..so send it in for a fix ...when you get it back just flash clk or magldr ..and then flash cwm partition it will work ..I think u are making a mistake while installing the clock work recovery mod. The cwm problem is not at all hardware related probalby you did something wrong. good luck. But flash official stock Windows Rom using SD care method.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
What cwm problem? It works fine, I just wanted to know if I should go grab the newest offical rom off tmobs website and flash it before I send it back to them is all. Since I am not sure they will take it back with android on it.

Yup your screen connector is probably broken ..so send it in for a fix ...when you get it back just flash clk or magldr ..and then flash cwm partition it will work ..I think u are making a mistake while installing the clock work recovery mod. The cwm problem is not at all hardware related probalby you did something wrong. good luck. But flash official stock Windows Rom using SD care method.
Edit :the jtag has to be done only when you Brick your device I.e you device doesn't turn on due to flashing a wrong Windows Rom (flashing Android doesn't pose any threat )
Click to expand...
Click to collapse
thank you alot brother for helping me... well im sorry if i seem naggy but im gonna tell u how i installed the cwm so you can tell me whats wrong...
first of all i had a stock windows mobile rom from HTC website so the things i did were
1- task 29 and it was done perfectly
2- i installed the radio 2.15.50.14
3- i installed magldr v1.13, when i open it it gives me a fail to open an android nand but i havent install it yet so i think its not a problem.. i mentioned this because it never used to appear to me when i used to flash android roms before.
4- i go to usb in the magldr to install cwm and when its connected i install magldr by pressing on daf on the computer as an administrator and it gets installed perfectly.
then when i open AD recovery it stucks on the go go go screen and nothing opens..
i tried to install CLK one time and did the instructions but also cwm never opened.. so do u still think if i fix the screen issue then cwm will work?
i was thinking that the defect in openning cwm is because of a bios problem.. (( well i dont know if its called bios in the mobile but i mean what like the bios in the computer)) so thats why i thought about the JTAG.. but if u think that i will not benifit it then i wont do it and i'll only fix the screen issue..
btw i did a hard reset before i did the installation of the cwm...
sorry for making my reply long but i really would like u to know everything happenning because u seem as an expert that would be able to help me.. plus i really cant live without the android and i need to fix it
thank you again brother

yma900 said:
thank you alot brother for helping me... well im sorry if i seem naggy but im gonna tell u how i installed the cwm so you can tell me whats wrong...
first of all i had a stock windows mobile rom from HTC website so the things i did were
1- task 29 and it was done perfectly
2- i installed the radio 2.15.50.14
3- i installed magldr v1.13, when i open it it gives me a fail to open an android nand but i havent install it yet so i think its not a problem.. i mentioned this because it never used to appear to me when i used to flash android roms before.
4- i go to usb in the magldr to install cwm and when its connected i install magldr by pressing on daf on the computer as an administrator and it gets installed perfectly.
then when i open AD recovery it stucks on the go go go screen and nothing opens..
i tried to install CLK one time and did the instructions but also cwm never opened.. so do u still think if i fix the screen issue then cwm will work?
i was thinking that the defect in openning cwm is because of a bios problem.. (( well i dont know if its called bios in the mobile but i mean what like the bios in the computer)) so thats why i thought about the JTAG.. but if u think that i will not benifit it then i wont do it and i'll only fix the screen issue..
btw i did a hard reset before i did the installation of the cwm...
sorry for making my reply long but i really would like u to know everything happenning because u seem as an expert that would be able to help me.. plus i really cant live without the android and i need to fix it
thank you again brother
Click to expand...
Click to collapse
just get your screen fixed... i will guide you rhrough cwm installation

Having the same problem. Read some older post and even common sense all says It's hardware so gonna need to send it off.
Sent from my HTC Flyer P510e using XDA App

I sold mine for 110€ because I didn´t have warranty and the repair costs about 80€ and more.
Now I bought samsung galaxy s and it cost me additional 130€.
So at the end of the day, I´m satisfied with my decision because I have a new phone right away, I have no worries about the repair and I don´t have to use old Nokia from the middle ages

[Q]A Leo unit won't flash

Hey guys!
I'm having a rather strange problem with an HD2 unit. It belongs to a friend of mine and since I used to own one he turned to me for help, but as it appears I am helpless in the matter as well.
He claims he hadn't experienced any problems ever since he got it. He was using a custom WM6.5 ROM flashed by me no less than a year ago. Suddenly phone just rebooted showed a splash-screen, then 7 vibrates then nothing. I did a google search etc. and I found out this points to a MB hardware problems.
The thing is this:
I AM able to re-flash HSPL and OSPL properly.
I AM able to flash MAGLDR 1.13, but it won' boot. I just see the title, but no menu after that. PC installation states install finishes correctly.
I am NOT able to flash any radio custom or stock, nor am I able to flash any stock or custom ROM.
So I was just wondering - before I decide to give my friend advice to pay money for MB replacement should I try anything else?
Note: I DID try putting the phone (battery out) in the freezer for a few mins in a plastic bag. No change in any proccess whatsoever.
P.S. I believe I forgot to mention it is a EU HD2 unit.

Bad news
IMO it's a faulty MB, I doubt anyone could revive it, if freezer trick is not working, this is final verdict: dead!!!

I am still considering the option of the oven though... I just might take it apart and put the MB in the oven... or use a hot-air station... I'd be really thankful if someone shares experience and conclusions about similar activities

[Q] Trouble installing WP7 or Android

Hey guys.
I have been struggling with ROM flashing lately and was wondering if anyone could help. Sorry for wall of text but going to explain as much as I can.
Short version:
• Can’t get WP7 or Android working.
• CWM gets stuck on 123456 GO GO GO.
• Can flash WP7 ROMs successfully but touch screen won’t work.
Long version:
Have had an HD2 for about two years. Have previously installed some Android NAND but have mostly been running WP7. About 6 months ago touchscreen hardware failed and it went for repair at HTC. Re-flashed WP7 when it came back. A little while ago touchscreen hardware failed again and I had it repaired again under insurance (warranty had run out). The phone was returned again with touch screen working perfectly on stock ROM. I am now really struggling to get any custom ROMS working.
I have succeeded in installing three builds of WP7 (most recent versions of Yuki’s Back to the Future, HD2O, and Ultrafruit). Yuki’s Back to the Future is what I was running before most recent repair. In all cases the touch screen is entirely unresponsive. If I flash back to stock, it works perfectly again. So I gave up on WP7 and tried Android.
I am less experienced in flashing Android NAND, so this might be a silly mistake on my part, but I have flashed Android before both on my HD2 and on my friends’. I find I can’t get into CWM Recovery from MAGLDR. It stops after 123456 GOGOGO. I have tried the 250MB recovery from here (1) and the 200MB 5.200.5 recovery from the fourth post in this thread (2).
I am on HSPL 2.0.8. I have followed the following process for both WP7 and Android using mainly ksubedi’s HD2 Android Toolkit:
• Task 29
• Radio 2.15
• MAGLDR 1.13
• Enable last 24 NAND (WP) or Install recovery (Android)
Has anyone got any ideas? I have never had any problems before. I’ve noticed that my problem seems similar to the ones here (3) and, particularly, here (4). I have tried most of what was suggested in these threads. It seems unlikely but I’m wondering if the new screen from the most recent repair is causing this problem. The OP in the second thread seems to have exactly the same situation: new screen, touch screen doesn’t work in WP7 but does in WM6.5, can’t boot recovery.
Sorry for massive post, was trying to give as much information as possible. Apologies if I have missed something really obvious.
(1) http://www.addictivetips.com/mobile...kmod-recovery-on-android-htc-hd2-with-magldr/
(2) http://forum.xda-developers.com/showthread.php?t=1507792
(3) http://forum.xda-developers.com/showthread.php?t=1472556
(4) http://forum.xda-developers.com/showthread.php?t=1603428
Edit: Messed up the links so have just put them at the bottom. Sorry!

Your guess is correct. Recently read about it, but the link to can not.
The problem is that there are several revisions touchscreen. In the new right, works only on WM6.5. So it's best to find a screen with a broken system, so to say the donor. Other options can not help you.

try the links below, you can even triple boot now

d_3ger said:
Your guess is correct. Recently read about it, but the link to can not.
The problem is that there are several revisions touchscreen. In the new right, works only on WM6.5. So it's best to find a screen with a broken system, so to say the donor. Other options can not help you.
Click to expand...
Click to collapse
Hmmm.
Damnit. If that's true then this is the worst repair ever! A repair which makes it unflashable!
Is it definitely the screen that is causing the problem and not a new mainboard (they may have replaced more than just the screen)?
Is there any way to confirm for certain that this is the problem? I saw some guys talking about something similar and suggesting editing the bootloader with JTAG. Could this work?
http://forum.xda-developers.com/showthread.php?t=881912
http://forum.xda-developers.com/showthread.php?t=887337
mengfei said:
try the links below, you can even triple boot now
Click to expand...
Click to collapse
Thanks for the link. I'll give it another go using your guides and see if I had been making a mistake somewhere.

I've now also tried booting into Recovery from cLK and booting into an Android SD build.
Both have which have also failed.
Recovery from cLK crashes at what appears to be the same point as from MAGLDR.
Android SD build stops at "Jumping to kernel (custom). I used Nexus HD2-ICS-HWA-SD_v2.7.
It really does look as though it is now unflashable, as d_3ger said.
Bah.
I am wondering if maybe they may have used parts from a TMOUS HD2 in repairing my HD2.
Is this plausible and might it have caused the problem?

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