Database Users

MAGLDR NOT causes Touch Screen issues Confirmed

Update: According to info from Cotulla, MAGLDR does not initialize the touch screen since it doesn't have touch input. WinMo or Android (linux kernel) initializes the touch screen. The failures I'm seeing in Android NAND builds must be due to bug in those builds. I've just downloaded 14 different NAND builds (clockwork and not) to test out again. I'll report results later.
See Cotulla's post on the matter here. Thanks for all the help on the matter to everyone.
Update 2: Here is the link to my post testing a handful of builds and what I found.
Note: Please take the insults elsewhere. I'm trying to actually get some help and offer it. I never said MAGLDR caused any damage to my device. It's a simple bug which once pointed out can be researched and fixed.
The work the DarkForcesTeam has done is amazing! We're talking thousands of hours of work collectively. Some commercially available products don't receive such dedication. I just want to try to help out as best as possible to make it an even better product.
When I use MAGLDR, my touch screen becomes over-sensative. It'll randomly select parts of the screen as having been touched when they're not, like a "ghost hand" was using the device..
It is not a bad digitizer. It is not a hardware defect. It is a problem with MAGLDR. I've confirmed this existing with versions 1.11 to 1.13. The problem only exists when using MAGLDR. If WinMo is used, problem goes away.
Here's what I did:
1) Task 29
2) WinMo 6.5
3) Ran an Android ROM from SD (Copes AOSP SD HD2 GB232/CM7 A2SD at
http://forum.xda-developers.com/showthread.php?t=898831
Everything is fine. Screen is incredibly precise.
4) Task 29
5) MAGLDR 1.13
6) Change SD build to boot from MAGLDR instead of HARET
7) Boot up, everything comes up fine.
8) Screen goes crazy.
Since I didn't change the build I was booting, and only changed MAGLDR, there should have not been any touch screen issues.
9) Task 29
10) WinMo 6.5 reinstalled
11) Change SD build back to boot from HARET
12) Boot the Android SD build
13) Screen is very precise once again.
Does anyone know if the DarkForcesTeam (DFT) has commented on this issue before? Are they working on it? Are they even aware of it?
Has anyone else had any issue like this?
I'm using one of the first HD2s to come out for T-Mobile in the US.

FreakyFerret said:
When I use MAGLDR, my touch screen becomes over-sensative. It'll randomly select parts of the screen as having been touched when they're not, like a "ghost hand" was using the device..
It is not a bad digitizer. It is not a hardware defect. It is a problem with MAGLDR. I've confirmed this existing with versions 1.11 to 1.13. The problem only exists when using MAGLDR. If WinMo is used, problem goes away.
Here's what I did:
1) Task 29
2) WinMo 6.5
3) Ran an Android ROM from SD (Copes AOSP SD HD2 GB232/CM7 A2SD at
http://forum.xda-developers.com/showthread.php?t=898831
Everything is fine. Screen is incredibly precise.
4) Task 29
5) MAGLDR 1.13
6) Change SD build to boot from MAGLDR instead of HARET
7) Boot up, everything comes up fine.
8) Screen goes crazy.
Since I didn't change the build I was booting, and only changed MAGLDR, there should have not been any touch screen issues.
9) Task 29
10) WinMo 6.5 reinstalled
11) Change SD build back to boot from HARET
12) Boot the Android SD build
13) Screen is very precise once again.
Does anyone know if the DarkForcesTeam (DFT) has commented on this issue before? Are they working on it? Are they even aware of it?
Has anyone else had any issue like this?
I'm using one of the first HD2s to come out for T-Mobile in the US.
Click to expand...
Click to collapse
I do not know whether this will work or not. But try a NAND build with SENSE in it. Sense has a function of "Calibrate your Screen". Try and recalibrate your screen.
I know for sure the build "imilka's Vision Sense v3.0 (HD2Z)" has this feature. The link for this build is http://forum.xda-developers.com/showthread.php?t=898708
I hope that resolves your issue.

My touch screen stopped working during windows phone 7 and i cant figure out a reason why. Im running magldr 1.12

It might be a mgldr booting SD build issue, I've been using cyanogenmod 7 android 2.3 nand for a month without a single issue..
Sent from my HTC HD2 using XDA App

roloracer said:
It might be a mgldr booting SD build issue, I've been using cyanogenmod 7 android 2.3 nand for a month without a single issue..
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Same here
Sent from my HTC HD2 using XDA App

When I use a pure NAND build, the problem is there too.
Anytime I use MAGLDR, it happens.
I don't like Sense, but I'll give the one you recommended a try later tonight.

havent had the issue either.. BUT!!! cause its winter here whenever i come from outside and i use my phone i get random presses on the screen cause its wet, when i wipe it off it just behaves..

Alright... my phone just died
Had the setup that you can see on my signature, and touchscreen just stopped responding randomly. First it was once or twice a day, now its like every other time that the screen is sleeping and I try to wake it up.
I did Task29, flashed official WinMo radio, and now the problem still exists. Every other time that the phone goes to sleep - i press any button, the screen lights up, but like the touchscreen function just wont work.
I know for sure that I am not the first, second or even tenth person that has this problem after running NAND-android. Maybe this should be put on the android development thread, so people wont break their phones.
I have no idea why is this happening, but I know that its time for a new phone. Hopefully T-Mobile will give me a new phone, which I can sell and get a native android phone. I hate windows, the reason that I got this phone was the screen size, which no other android phone had on t-mobile back when I got it.
So, one more time
PEOPLE, MAGLDR WILL CORRUPT YOUR TOUCHSCREEN IF YOU USE IT
With that said - I would like to thank everyone that made android on HD2 possible, and specially cotulla, his team, mdj and hastarin, I had a blast using it You guys ROCK!!
Edit: After flashing winmo - I kept getting problems for the first 1hr.
Now it seems that freezing is gone on Win Mo.
Will update later.

t0ny0 said:
Alright... my phone just died
Had the setup that you can see on my signature, and touchscreen just stopped responding randomly. First it was once or twice a day, now its like every other time that the screen is sleeping and I try to wake it up.
I did Task29, flashed official WinMo radio, and now the problem still exists. Every other time that the phone goes to sleep - i press any button, the screen lights up, but like the touchscreen function just wont work.
I know for sure that I am not the first, second or even tenth person that has this problem after running NAND-android. Maybe this should be put on the android development thread, so people wont break their phones.
I have no idea why is this happening, but I know that its time for a new phone. Hopefully T-Mobile will give me a new phone, which I can sell and get a native android phone. I hate windows, the reason that I got this phone was the screen size, which no other android phone had on t-mobile back when I got it.
So, one more time
PEOPLE, MAGLDR WILL CORRUPT YOUR TOUCHSCREEN IF YOU USE IT
With that said - I would like to thank everyone that made android on HD2 possible, and specially cotulla, his team, mdj and hastarin, I had a blast using it You guys ROCK!!
Click to expand...
Click to collapse
I had my touchscreen do that and just stop working BEFORE magldr even came out. A person I know who never hacked or did anything to his phone had this problem. It's a hardware defect and it's just coincidence that it broke while you had magldr on your phone.

not again...
if MAGLDR makes those weird things to your phone then DON'T USE IT!!!
I have been using MAGLDR since it came out. EVen flashing a lot of builds everyday to test but never had any issues with the touchscreen.

jose makalolot said:
not again...
if MAGLDR makes those weird things to your phone then DON'T USE IT!!!
I have been using MAGLDR since it came out. EVen flashing a lot of builds everyday to test but never had any issues with the touchscreen.
Click to expand...
Click to collapse
Same, I've flashed well over 25 times and my Touchscreen hasn't had any problems.
MAGLDR is safe, end of story.

Confirmed? Really? Because you think it happened to you?
This is anecdotal, and it is definitely not concrete in any way. This is pure FUD, nothing more. You should consider thinking before you post ridiculous claims that something has been "confirmed."
This has happened to ONE person on ONE phone, and pretty much everybody else is telling you that you are wrong. Does that sound confirmed to you?
It annoys me that you would smear somebody else's fantastic work because your phone had a freak accident. Go blame the government or something, just stop blaming magldr. Thanks.

Buy a WinMO 6.5 phone stick to WinMO6.5 if you want it to work as intended by manufacturer.
If you want to tinker, then be prepared to tinker it to its death.
If you can't afford a new phone, don't mess with it.
If you can't be without a phone for even 1 day, don't mess with it.
If you want to blame, then blame yourself. You are just messed up.

Danation and hd2k10, I'm not smearing anyone. My phone is fine. There is a bug in MAGLDR. One I'm sure the DarkForces Team can fix if someone can provide some good feedback. Read what I posted again. I'm asking to help DFT solve this software bug. Not saying it's bad.
And I did confirm the problem only exists when using MAGLDR. It runs fine on most of the phones, but there are others aside from myself who have had problems with it. We would love to see MAGLDR working perfectly and I personally encourage anyone who it works for to continue using it. I wish I could use it and want to do everything I can to make that a reality.
psykick5, did you try flashing a WinMo ROM or Android SD build to see if your screen returns to normal?

Danation said:
Confirmed? Really? Because you think it happened to you?
This is anecdotal, and it is definitely not concrete in any way. This is pure FUD, nothing more. You should consider thinking before you post ridiculous claims that something has been "confirmed."
This has happened to ONE person on ONE phone, and pretty much everybody else is telling you that you are wrong. Does that sound confirmed to you?
It annoys me that you would smear somebody else's fantastic work because your phone had a freak accident. Go blame the government or something, just stop blaming magldr. Thanks.
Click to expand...
Click to collapse
Maybe you should read around and see that its not ONE person on ONE phone?
Also, I have flashed many many times, on HD2 and other devices, the fact of the matter is that it happened. Its not just the OP, its not just me, there are plenty of posts in here, saying that exactly the same thing happened to them /just search and you will see/.
Also, I would hate if someone is talking bad about someone elses fantastic work, and this is why I thanked everyone that helped getting android on our HD2s. There is no disrespect, I was just trying to warn other people that this has happened, and not once or twice. The fact that it didnt happen to you - means nothing It wasn't happening to me either, and I even wrote an angry comment to one of the people that was complaining a while back, and ha, guess what happened today
I agree, that probably "confirmed" is not the write word in here, but what we are trying to do, is just warn other users, AND DEVELOPERS so they can look into it, what if the problem is with MAGLDR? Hopefully its not, but thats a big coincidence. What if by some way its overheating a chip or something? You never know, since you are not a developer, I'm don't think that you can be 100% sure about something that is not open source, and you can't see how its made or what it does to the device.
So cool down, and if you can't help - there is absolutely no need to post negative comments.
Thank you,
Tony.
Edit: This is not for you only, its for all the other negative comments that are before yours. And after yours Y'all need to chill out, we are here asking for help. I have donated to a good amount of developers in here, and I am not trying to disrespect any of them, as I said in my previous post. I appreciate their work, but as far as I'm concerned, and the few other guys before me - there is a bug in MAGLDR, and it would be nice if Cotullas team can take a look at it.

Must be a T-Mobile problem. I don't have it. Sorry for you tho, wish I could help.

I have EU HD2 and noticed same problems. Not all time and can say that i think its not MAGLDR problem. More NAND roms side. You ask why.
Tested many roms, not one. No, i dont go say these are bad. just tryed find wich works best for me.
With win 6.5 and win 7 roms i dont seen this problem but with android nand roms yes. Tested custom win 6.5 + android sd too. With that siutation dont had these problems.
Why i try here too is that i think its clued with another problem too, described on this hd2 forum on diffrent places. One is this thread.
Also i have read on some NAND roms thread that rom cooker are increased screen sensitivy or smth. Cant find right now it but if i remember it then i go back and post link.

Not all this sh1t again.
IF there was a "bug" in magldr for TS then it would affect the MAJORITY not the MINORITY.
Also the title of this thread is retarded, you havent "confirmed" a bloody thing other then your ability to presume something and then jump to a wrong conclusion.
EVEN if there is a bug would be a very small one and not one that DFT should waste their time on atm.

your understanding of a bug is that it shows up on the majority of a system? that's utter bull****! sorry.

HectiQ said:
Must be a T-Mobile problem. I don't have it. Sorry for you tho, wish I could help.
Click to expand...
Click to collapse
I have a tmous HD2 and don't experience that crap at all!
Sent from my HD2 Droid HD using XDA App

[Q]Htc hd 2 stuck on boot.

Hello,
I recently bought a HTC HD 2 Tmobile from ebay .
The phone will not boot up.
When i start up the phone it leads me to the windows start up to the tmobile start up then back to the windows start up and stays there and i cannot do anything except take out the battery.
Any ideas? Thanks in advance.

Sounds like you are stuck in a boot loop. There is a few things you can try.
First check the battery pins and make sure you do not have any that are bent out of alignment with the others or that is being hindered in anyway.
Next you can download the official Windows Mobile ROM from T-Mobile. You will have to enter the IMEI number, look under the battery for it. Once downloaded you can try to flash it via USB. Just put your HD2 into the bootloader by holding down the volume down button while powering on your HD2 and then connect it to your computer via USB cable. You will have to have Windows Mobile Device Center or Active Sync installed on your computer so you can get the USB Sync connection you need. Go to here to find a link to both, just choose the one you need for the type of windows you use. Anyway once you have your HD2 in bootloader and connected the serial in the bottom white bar of bootloader should change to USB, this means you have the USB Sync connection. When you see the USB you can right click on the ROM you downloaded from T-Mobile and run it as administrator. I do suggest you let your HD2 stay off and charge for a little while first though to make sure you have more than a 50% charge.
If that does not work you can try running a Task 29 and then repeating the above mentioned steps to flash the ROM again.
If this does not fix your problem you probably have hardware issues causing the boot loop.

Thank you so much for the reply. I will try the things you have listed. Even though i am a bit lost haha. If these steps dont work , what are some of the hardware issues that may be the cause of this? And i know this is random but can you help me load android onto my hd2? I have 2 2gb micro sd cards do i have to get a bigger card? Which android os would you recommend? Thats quick and smooth? Thx!

H0n3yb43 said:
Thank you so much for the reply. I will try the things you have listed. Even though i am a bit lost haha. If these steps dont work , what are some of the hardware issues that may be the cause of this? And i know this is random but can you help me load android onto my hd2? I have 2 2gb micro sd cards do i have to get a bigger card? Which android os would you recommend? Thats quick and smooth? Thx!
Click to expand...
Click to collapse
the hardware issue would be overheating cpu, have to get a new main board via HTC warranty (if it is not voided due to water damage or dropped).
Android is easy to load. Fast/smooth you want a CyanogenMod7 ROM, you can find versions for SD or versions that you flash on the phone itself. You can either run Windows Mobile 6.5 then laucnch Android from SD (dual-boot), launch Android from SD with no Windows Mobile, launch Android flashed from internal storage, or flash Windows Phone 7 to internal storage and run Android from SD (dual-boot).
The tutorials are all in the HD2 Android forums and HD2 WP7 forums.

initially I would try a hard reset before getting too technical.
hold down volume up and down and switch on. keep holding volume buttons, when prompted press volume up. this will restore to out of he box settings ie remove all previous data on the phone.
G

H0n3yb43 said:
Thank you so much for the reply. I will try the things you have listed. Even though i am a bit lost haha. If these steps dont work , what are some of the hardware issues that may be the cause of this? And i know this is random but can you help me load android onto my hd2? I have 2 2gb micro sd cards do i have to get a bigger card? Which android os would you recommend? Thats quick and smooth? Thx!
Click to expand...
Click to collapse
As far as hardware issues go it is like XDA member orangekid said overheating is the predominant reason that comes to mind. Another thing is degraded prossesor connection or degradated flash/NAND chip connections. All of witch can only be fixed by main board replacement.
Yes I can help you "load" Android onto your HD2, just click the guide link ed in my Sig. I think everything you need to know is there. well except how to run Android fro SD card, hmmm maybe I should add that. Also you can go here for more links to very useful threads in the Android General Stickie Roll up thread.
Again I have to agree with XDA member orangekid, the CyanogenMod7 ROMs are pretty creaking awesome. But I do recomend the Hyperdroid ROM I have linked in my Sig. I have used it for my daily driver for months and the only real problem I have had is the latest update to the ROM the new updated market would not work properly I would have to go to Settings/Applications/Manage Applications. Then find the market selerct it and then select Uninstall Updates. Oh and make sure you do not have the check box checked to aromatic update the market or you will have to do this everytime you use the market. I am currently testing the [17 Aug][SENSE3.0] Pyramid HTC WWE 1.35.401.1 - Real 3D [V2.1][RAF 1.9GB] ROM to sort of test the HTC Sensation's ROM and to check out HTC Sense 3.0.
As for your 2gig SD card no it will work but I do recomend you consider getting a 4 gig SD card. I have heard mixed results from 2 gig SD cards that people use to dual boot with. I personally have never used under a 4 gig SD card and have never had any trouble.

Thank you all for your replies.
I will Try out all the steps to fix my phone first. then i will try to load up android onto it and i will get back to you guys. i thanked all that have helped thank you so much. i will be back around sunday or monday with an update. wish me luck! oh one more question. would a 8gb be a good size micro sd card? or should i get a 16gb?

It really depends on how much space you'll think you'll need like, are you a person who takes a lot of pics or video, do you keep a lot of music on your phone? If you do then yes I would go with an 8gb. If not then you could really just use a 4gb sd card. I use a 8gb class 10 sd card myself and store a lot of pics, roms and backups and I haven't had the need to go back to a 16gb. Also you dont have to get a high speed card either, a class 4-6 is plenty.
If you decide to go the dual boot for Android I would look up a program found here on XDA called Rundroid. It will allow you to run many different Android builds from your sd card and is very simple to use. I would give the link but I'm not by a computer right now, sorry about that.
Sent from my Desire HD using XDA App

Hiii just an update . i did try to hard reset and it does reset but after i reset when it reboots it stays on the tmobile stick together logo.
and i just noticed if i leave it on like this and leave the battery the phone starts to get warm a bit on the back bottom side of the phone.
i will try the steps you gave me and see if it works. thanks.

I tried to restore by volume down+up and power and it reset but no boot. Pleasse help any one. i tried to do the bootloader ( my computer doesnt reconize my phone) it shows me all these codes. any help?

Heres a vid of my phone if it helps.
http://www.youtube.com/watch?v=a2qQsSXPx-s

I dont want to comment on something and be wrong so with that I would take it to t-mobile and see if you can have it switched out under your warranty. I had a very similiar problem that it was stuck on the HTC/T-mobile splash screen and I sent mine in for repair through HTC. They fixed the issue and sent it back (for free), all I had to pay was shipping there. They do say that if they find something thats not covered under warranty like water damage/not the proper software they'll call and let you know if there will be a charge to fix it.
I will say that my bootloader and probabaly everyone elses dont look like yours. Just above the spl-2.08 mine says pb81120..also mine says Cotullahspl where yours does not. If you dont find what your looking for here on the site best bet is to send it in for repair. Even if T-mobile says you didn't buy the warranty or what ever you still may be covered through HTC. This also will apply even if you bought the phone used.
HTC repair can be found here.

were you not holding the volume down button when you turned on the phone?
I would just download/flash stock from that bootloader screen.

I was holdin the vol down and power and i bought it on ebay so.. idk if i have warenty.

Even if you bought the phone on ebay you still could have a warranty. In post 12 I linked HTC repair. If you call them you could find out if you do have a warranty on it or not. They'll ask if for the imei# and run it. Im not sure if its a two year or one year on the warranty but they'll be able to tell you that.
I bought a used HD2 on ebay as well. Mine was listed as broke and was stuck on the T-mobile splash screen. I asked for the imei# from the seller and then called HTC to find out if it still had a warranty which it did, so i bought it. I lucked out that my phone was covered under warranty, you may or may not have the same luck as i had.

Thank i did what you told me and they gave me a new motherboard on mine. Thanks alot

HD2 Always freezing on any android build

Ive had 2 HD2's and its been the same problem for both.
No matter what rom i use on my hd2 it ALWAYS freezes(I was having the same issues with my first hd2 but eventually the screen on it stopped working and i sent it back for warranty and got a new one)
Ive flashed 2 other hd2's that belong to some friends and i did the exact same thing to their phones that i did to mine and they dont have any issue.
I dont know what to do and why am i the unlucky one
Please XDA Community i come to you for Guidance! I know this phone can be amazing but why is it being so stubborn!
Can it be SD related?

Does the area beneath the battery shell, behind the phone, feel particularly hot? If so, it's likely overheating (HTC calls it a current leakage... something?) and if you're under warranty you may wish to send it back.
Otherwise, there are fixes (suck as devising your own extra heatsink, reflowing the solder).... but it's non-trivial.

Does it freezes while using any particular applications, and what happens when it freezes???? I mean does it get to normal by itself or you have to pull the battery out and restart your HD2.
I am asking this because I was also having the same issue with my previous HD2, and then I came across this post
http://forum.xda-developers.com/showthread.php?t=1189544
which explains a lot about bad blocks which affect the android build.

DutchMaster117 said:
Ive had 2 HD2's and its been the same problem for both.
No matter what rom i use on my hd2 it ALWAYS freezes(I was having the same issues with my first hd2 but eventually the screen on it stopped working and i sent it back for warranty and got a new one)
Ive flashed 2 other hd2's that belong to some friends and i did the exact same thing to their phones that i did to mine and they dont have any issue.
I dont know what to do and why am i the unlucky one
Please XDA Community i come to you for Guidance! I know this phone can be amazing but why is it being so stubborn!
Can it be SD related?
Click to expand...
Click to collapse
dude, u need to give the detail of your problem, when and how it freezes. Cuz there are lot of problems by which a phone can be freezed up.

hstr said:
dude, u need to give the detail of your problem, when and how it freezes. Cuz there are lot of problems by which a phone can be freezed up.
Click to expand...
Click to collapse
yea sorry im just at the point where idk what else to do.
Lemme be more specific about this.
Theres times where it would actually boot up to where i can make a call but only for less than a couple minutes most of the time. There are times where i get lucky and it stays on for a good while ( couple hours ) and it'll stay that way as long as i dont use it. It freezes up starting up just about any app so i have this odd feeling it might be my sd card. But then i dont understand why the next thing happens. After i remove the battery and put it back in and boot either 1 of the 3 happens.
1) 1EFATAL HIT 1
2) Gets stuck on Go go go
3) gets stuck after go go go when rom tries to boot up.
Only thing i can do to get it to boot up again is take the battery out and leave it out for a good 10-15 minutes.
I tried Task29 and reinstalling magldr, cwr, and Rafdroid Rom and i still get the same crap
The Phone gets a little warm under the cover sometimes but its right were the micro sd is located

I'm having the same problem. My HD2 will freeze if I play games on it causing me to pull out the battery and when I boot it up, sometimes it will freeze at the MAGLDR screen, will freeze as soon as the rom boots. Right now my phone seems stable and I'm only using it for texting and making calls and nothing else for the fear of damaging the phone any further. I have a TMOUS phone btw.

DutchMaster117 said:
yea sorry im just at the point where idk what else to do.
Lemme be more specific about this.
Theres times where it would actually boot up to where i can make a call but only for less than a couple minutes most of the time. There are times where i get lucky and it stays on for a good while ( couple hours ) and it'll stay that way as long as i dont use it. It freezes up starting up just about any app so i have this odd feeling it might be my sd card. But then i dont understand why the next thing happens. After i remove the battery and put it back in and boot either 1 of the 3 happens.
1) 1EFATAL HIT 1
2) Gets stuck on Go go go
3) gets stuck after go go go when rom tries to boot up.
Only thing i can do to get it to boot up again is take the battery out and leave it out for a good 10-15 minutes.
I tried Task29 and reinstalling magldr, cwr, and Rafdroid Rom and i still get the same crap
The Phone gets a little warm under the cover sometimes but its right were the micro sd is located
Click to expand...
Click to collapse
Last question to u, that when u had ur stock windows rom in ur mobile , does any thing happened like this.
if not, then the problem is not in your mobile or sdcard, the problem is in the method u are intalling by.
1)try to get back to windows mobile.
2)install hardspl4 - 2.08 (not Hardspl3 - 2.08)
3)install magldr 1.13 (not magldr 1.11)
4)install clockworldmod recovery 3.0.0.5 (if ur rom is a cwm rom.)
5)Now flash the rom.
6)give it a try, if not any issue, then
7)push the thanks button. .. lol

hstr said:
Last question to u, that when u had ur stock windows rom in ur mobile , does any thing happened like this.
if not, then the problem is not in your mobile or sdcard, the problem is in the method u are intalling by.
1)try to get back to windows mobile.
2)install hardspl4 - 2.08 (not Hardspl3 - 2.08)
3)install magldr 1.13 (not magldr 1.11)
4)install clockworldmod recovery 3.0.0.5 (if ur rom is a cwm rom.)
5)Now flash the rom.
6)give it a try, if not any issue, then
7)push the thanks button. .. lol
Click to expand...
Click to collapse
That's actually the same thing I do.
Alright I know this might sound ridiculous but it seemed to work ( so far ). After 6 hours of trying to get this phone to work I decided to try something I saw on another thread. I got an icepack and did a complete install while having the phone on the icepack to keep it from getting warm. To my suprise it worked... I'm using my phone now with no issues yet and its been about 12 hours and it hasn't frozen yet. Although it did do a random reboot once ( I have a few bad blocks so I'm guessing that might be the reason). But Yea this worked for me some how. I'll update on any issues I get as soon as I can.
Sent from my HD2 using XDA Premium App

Same problem for me. My hd2 always freezes with any sense ui android build. MIUI and Nexus HD rom works fine.

My simple advise is... reinstal windows. And try again.
This worked for me when i started with the HD2.
Sent from my mercury using XDA App

Hi I had the same problem, but I sent my phone for repairs and it never froze again. According to HTC they just replaced the main board. But before I did that I actually flashed the official RUU (windows 6.5), and it continued to freeze, so I was quite sure it was a hardware problem. Indeed after repairs my phone didn't freeze anymore.
Sent from my HD2 using XDA App

DutchMaster117 said:
Ive had 2 HD2's and its been the same problem for both.
No matter what rom i use on my hd2 it ALWAYS freezes(I was having the same issues with my first hd2 but eventually the screen on it stopped working and i sent it back for warranty and got a new one)
Ive flashed 2 other hd2's that belong to some friends and i did the exact same thing to their phones that i did to mine and they dont have any issue.
I dont know what to do and why am i the unlucky one
Please XDA Community i come to you for Guidance! I know this phone can be amazing but why is it being so stubborn!
Can it be SD related?
Click to expand...
Click to collapse
I also had 2 x HD2 which did this.
Froze when got to hot, or if using gps or mobile data.
Sold it 2 weeks ago, now own Desire HD and it's BRILLIANT!!

So now ive been running rafdroid on the phone without an sd and it runs.. but laggy since theres almost no space left in phone and it isnt getting hot. It only gets hot when it operates with the SD inside.
anyone know anything about that?

same problem
i have the exact same issues. the phone freezes every time it boots, be it magdlr nand, sd, wm 6.5 anything. however my old hd2 had no problems at allbut i broke it changing the screen digitizer and lcd.
(the white plastic on the connector that connects the lcd and digitizer to the main board broke.)
im pretty sure the reboots are mother board related but i don't know if telling tmobile or htc that will do anything because the phone is old. (i got this other hd2 from a guy on craigslist.)

I had the same freezing problem with my HD2. After all the research I've done, none of them worked. Then i put the phone into the freezer for a minute and took an ice pack, placed it on the back of the phone where CPU is located. While holding the ice pack, I re installed the ROM and at the and freezing issues were solved. It never froze again.
I hope this solves your problem too.

oztorque said:
I had the same freezing problem with my HD2. After all the research I've done, none of them worked. Then i put the phone into the freezer for a minute and took an ice pack, placed it on the back of the phone where CPU is located. While holding the ice pack, I re installed the ROM and at the and freezing issues were solved. It never froze again.
I hope this solves your problem too.
Click to expand...
Click to collapse
I want to ask whether this cooling trial fixed freezing problem forever? suppose if u use your set for more than for hour streaming over wifi? never it got freeze again?

The best solution that you can flash back to WinMo 6.5 and run Android from SD Card.

I have the same issue... but...
Make a complete instalation with an ice pack?? Are u joking me?? It works??
well... i have not to lose... i will report if i try it...

I flashed stock rom and run android from sdcard. but when i press Haret.exe is going to HTC green logo and after restarting. some solution?

Similar problem
I have a similar problem. But with two different phones.
I bought LG Optimus One about two years ago. After a few months, some freezes appeared... I've sent it to manufacturer three times and every time they changed some parts... but nothing have helped. I've made some experiments (another battery, SIM card, MicroSD card, custom ROMs) and than I realized, that the problem occurs only while the mobile internet is ON.
This summer, my friend offered me used HTC HD2 and I bought it. He used to have Android there with no problems. After a few weeks, the freezes occured again. And again: I can surf internet all day by wifi with no problems, but when I tunr on the mobile internet (MI), the phone freezes. The back cover of battery is a bit hot, but this appears while long using the phone too without MI (without freezes).
I've tried almost everything to solve this problem: changed SIM card, changed SD card, everytime with flash of the newest ROM... nothing helped.
I'm not sure if the problems with LG OO and HTC HD2 have the same reason, but I can't believe I can buy two phones with similar problems without transfering them.
What aboutthat crazy plan of flashing with ice cooling? Does it work afret a few months too?
PS: Sorry for my English

HD2 Bricked?

Last night, I noticed that ROM Manager had an update in the Android market
(512mb LEO with Typhoon Cyanogenmod). I hit the update button, and walked away for a while while my phone did its thing, as usual.
I returned about 15 minutes after and noticed that my HD2 was off. I could not, however, turn it back on.
Removing and replacing the battery did not help. The phone wouldn't charge via the wall socket.
My linux PC will not detect it (I checked my dmesg log when plugging in and turning on)
I left the battery out overnight, plugged the phone into the wall, put the battery inside. No luck.
I checked the battery voltage with a multimeter, and it reads about 3.9v.
I don't think it's the battery. I think my HD2 is somehow bricked! Is there anything I can do?
It's not under warranty any more, but if I send it for repair, do you think they will deny it (because it has Android on it)?
Enlighten me with your wisdom, XDA! I don't want to say goodbye to this amazing device!

xebozone said:
Last night, I noticed that ROM Manager had an update in the Android market
(512mb LEO with Typhoon Cyanogenmod). I hit the update button, and walked away for a while while my phone did its thing, as usual.
I returned about 15 minutes after and noticed that my HD2 was off. I could not, however, turn it back on.
Removing and replacing the battery did not help. The phone wouldn't charge via the wall socket.
My linux PC will not detect it (I checked my dmesg log when plugging in and turning on)
I left the battery out overnight, plugged the phone into the wall, put the battery inside. No luck.
I checked the battery voltage with a multimeter, and it reads about 3.9v.
I don't think it's the battery. I think my HD2 is somehow bricked! Is there anything I can do?
It's not under warranty any more, but if I send it for repair, do you think they will deny it (because it has Android on it).
Enlighten me with your wisdom, XDA! I don't want to say goodbye to this amazing device!
Click to expand...
Click to collapse
Did you try holding the volume down button and turning on the phone....
It should take you to the tri colored screen...
If you get there the phone is not bricked

casemandan said:
Did you try holding the volume down button and turning on the phone....
It should take you to the tri colored screen...
If you get there the phone is not bricked
Click to expand...
Click to collapse
Yes I have tried that. Alas, nothing...
Do you recon they will fix it even if Android was on it?

xebozone said:
Yes I have tried that. Alas, nothing...
Do you recon they will fix it even if Android was on it?
Click to expand...
Click to collapse
It is a little late for me to mention this, seeing as you have sent your HD2 in for repairs all ready. But your power/end button may have stopped working, if you still had the your HD2 you could try pressing the reset button by the SD card slot and see if the device booted up then. But that is not an option now.
If all you did was update ROM Manager via the Android Market. Then it should not have bricked your HD2 in any shape form or fashion. Further more it should not have caused your HD2 to turn off either. I mean when you are running NAND Android on the HD2 you are pretty safe from bricking your HD2 because both MAGLDR, cLK, and the actual Android ROM is flashed to the ROM partition of the NAND memory and never touches the real SPL bootloader partition of the HD2.
Plus did you check your battery pins before sending it in? One might have been bent slightly. Or it could have been dirty battery terminals not allowing a good connection.
Point is I very much highly doubt your HD2 was bricked. You probably just missed judged your situation is all. As far as will they fix it? If you are willing to pay the fee they charge then yes.

T-Macgnolia said:
It is a little late for me to mention this, seeing as you have sent your HD2 in for repairs all ready. But your power/end button may have stopped working, if you still had the your HD2 you could try pressing the reset button by the SD card slot and see if the device booted up then. But that is not an option now.
If all you did was update ROM Manager via the Android Market. Then it should not have bricked your HD2 in any shape form or fashion. Further more it should not have caused your HD2 to turn off either. I mean when you are running NAND Android on the HD2 you are pretty safe from bricking your HD2 because both MAGLDR, cLK, and the actual Android ROM is flashed to the ROM partition of the NAND memory and never touches the real SPL bootloader partition of the HD2.
Plus did you check your battery pins before sending it in? One might have been bent slightly. Or it could have been dirty battery terminals not allowing a good connection.
Point is I very much highly doubt your HD2 was bricked. You probably just missed judged your situation is all. As far as will they fix it? If you are willing to pay the fee they charge then yes.
Click to expand...
Click to collapse
Hah. I don't know where you assumed that I have already sent it in. I'm the kind of person who tried to fix it myself first
Pressing the reset button doesn't do anything. I tried holding it down while inserting the battery too, and nothing,
The battery pins do not appear to be bent or dirty. I gently pushed them upright, and down, and scraped the surface gently in case there was any layers of dirt, still nothing.
I have a sibling with an HD2. I can test the batteries later.
Do you think somehow, the NAND can be worn from multiple reads/writes until it dies? It is flash memory after all, and that last write from the update could have pushed it...

xebozone said:
Hah. I don't know where you assumed that I have already sent it in. I'm the kind of person who tried to fix it myself first
Pressing the reset button doesn't do anything. I tried holding it down while inserting the battery too, and nothing,
The battery pins do not appear to be bent or dirty. I gently pushed them upright, and down, and scraped the surface gently in case there was any layers of dirt, still nothing.
I have a sibling with an HD2. I can test the batteries later.
Do you think somehow, the NAND can be worn from multiple reads/writes until it dies? It is flash memory after all, and that last write from the update could have pushed it...
Click to expand...
Click to collapse
Hmmm sorry I thought you had sent it in for repair already. Guess I miss read that, my bad man.
Yes NAND chips are rated for only a number of flashes. But that number is very high. I can not remember the exact numbers right now but hey that is what google is for right? But you did not flash a ROM you just uninstalled a app and then installed the updated version of that app. But then again I guess when you install or uninstall a app it is performing a some what similar action. Still though flashing a ROM is flashing a ROM, and installing a app is installing a app. One is a a lot different than the other.
My money is with your battery being bad. I mean like I said updating your ROM Manager should not have caused your HD2 to turn off at all. Try your sibling's battery and report back, I really hope that fixes it for you.

I haven't actually installed any Android ROM myself. But I did lots of WinMo ROM updates. What strikes me is that you installed a new ROM through the Android Market. Is that a normal procedure to upgrade an Android ROM on the HD2?

T-Macgnolia said:
Hmmm sorry I thought you had sent it in for repair already. Guess I miss read that, my bad man.
Yes NAND chips are rated for only a number of flashes. But that number is very high. I can not remember the exact numbers right now but hey that is what google is for right? But you did not flash a ROM you just uninstalled a app and then installed the updated version of that app. But then again I guess when you install or uninstall a app it is performing a some what similar action. Still though flashing a ROM is flashing a ROM, and installing a app is installing a app. One is a a lot different than the other.
My money is with your battery being bad. I mean like I said updating your ROM Manager should not have caused your HD2 to turn off at all. Try your sibling's battery and report back, I really hope that fixes it for you.
Click to expand...
Click to collapse
Hmm... I have an interesting development.
I tried my sibling's battery, and it didn't help, but what I did notice is that the phone vibrates slightly when I turn it on (as it should), but it does so very weakly. So weakly that I need to put my ear against the phone to hear it.
I don't think it's the LCD, because the charging light still doesn't work.
It probably needs a new mobo.
Any suggestions before I take it in for repair?

Cenobite_ said:
I haven't actually installed any Android ROM myself. But I did lots of WinMo ROM updates. What strikes me is that you installed a new ROM through the Android Market. Is that a normal procedure to upgrade an Android ROM on the HD2?
Click to expand...
Click to collapse
No, I didn't install a ROM on the market. It's an app called ROM Manager

xebozone said:
Hmm... I have an interesting development.
I tried my sibling's battery, and it didn't help, but what I did notice is that the phone vibrates slightly when I turn it on (as it should), but it does so very weakly. So weakly that I need to put my ear against the phone to hear it.
I don't think it's the LCD, because the charging light still doesn't work.
It probably needs a new mobo.
Any suggestions before I take it in for repair?
Click to expand...
Click to collapse
Yeah I agree with you it sort of sounds like something in the main board has malfunctioned. My guess is the processor or the NAND chip one. I would just send it in for repair if I was you. Maybe your HD2 just finally died, I know it sucks. But if you are willing to pay for the repair then you should be back up and running in no time. I am assuming you plan to send it to HTC for repair right? If for some reason they do give you a hassle about Android being on your HD2 and will not repair it. Then contact me I might know somewhere you can get a new main board put in it.

I got my HD2 back today.
Apparently it's not worth fixing...
I also got robbed today... Just my luck.
I cannot afford any other phones atm, but what do u think would make a good candidate replacement for the future? I don't think any other phone has the same kind of mod-ability and support here at XDA, but I would be delighted if you could prove me wrong.
My friend has a Galaxy S2, which is cool, but it doesn't have notification LED :/
Is there much hacking/dev on the GS2?

Touchscreen not working

Installed IceCreamTosti HD2 ROM 0.9 worked well for a day or two then all of a sudden my screen would stop working when it went to sleep. I researched and found that there is an undervoltage script that could be causing this problem. So i deleted the script. Then it started happening again. Task29'ed, installed HyperDroid Gingerbread Xtreme to see if that would fix my problem, nope still happening. It works when it wants but the funny thing that if I get it to work, I can use it until I have to go back to the previous screen, then I would have to hit the power button to put it to sleep, unlock it for the screen to become responsive. I know it sound like a Digitizer problem but I was wondering if anyone has any other suggestions before I buy it.
Thanks!

read here http://forum.xda-developers.com/showthread.php?t=993787

I've already read that. Thanks
Im just seeing if it could be a Kernel problem or something of that sort.

I've had this problem on one of the ROMs i used, not sure which one since i didn't stay on it for to long.
After i flashed a different ROM it fixed it. This might seem like a lot of work but why not reinstall MAGLDR,
CWM & a new ROM. Maybe try RAFDROID HD. Yes i know its a really old ROM but its a goodie and this
would be for test purposes anyway. You can always switch back.
I read the mentioned thread before too and im sure it does sound like it happens but since it happened so
soon after you installed a new ROM it makes me think its the ROM, eventhough you tried to reinstall a
different one. Maybe you can make a backup of your SD card and repartition both your phone and SD.

PC10DaTruth said:
Installed IceCreamTosti HD2 ROM 0.9 worked well for a day or two then all of a sudden my screen would stop working when it went to sleep. I researched and found that there is an undervoltage script that could be causing this problem. So i deleted the script. Then it started happening again. Task29'ed, installed HyperDroid Gingerbread Xtreme to see if that would fix my problem, nope still happening. It works when it wants but the funny thing that if I get it to work, I can use it until I have to go back to the previous screen, then I would have to hit the power button to put it to sleep, unlock it for the screen to become responsive. I know it sound like a Digitizer problem but I was wondering if anyone has any other suggestions before I buy it.
Thanks!
Click to expand...
Click to collapse
After reading the other guys thread about the end key it does seem like a bad digitizer . i read other threads explaining your exact same issue . the only way to figure out if its ROM related is to flash the stock winmo 6.5 ROM . yes , i said it , winmo but thats the last resort before deeming something hardware related . if you tried the end key option , pressing really hard on the key , then i guess i would change tto winmo and try to see if it still happens then

I do have to admit it could just be coincidence and the digitizer went up but considering this happened
only a few short days after he installed a new ROM makes me feel that there is a possibility its the ROM,
or maybe even the partition he changed (if it applies) when flashing that ROM over. I still suggest to start
over from MAGLDR on, including repartitioning your phone to the proper needs of the new ROM to see
if it helps before doing something drastic like reverting back to winmo.

Thanks for the help everyone, opened the phone up. Was hard as hell! But I cleaned the dust on the contacts under the end button, still no luck. I bought a new phone. Going to get a digitizer down the road and fix this one, If anyone want to buy it just let me know.

You will get a lot more people to see your interested in selling the phone if you post it in the xda marketplace found here.
Just open a new thread there and post how much you would want for the phone. I'm sure people would be interested
especially when you can get a new digitizer off ebay for so cheap.

change an other rom,if the problem still exist,i am sorry to tell u that u should send it to fix the touch screen..