Yesterday the touchscreen on my HD2 began to stop working correctly. It is a T Mobile US version. It wasnt dropped or exposed to water. If I play with it for awhile it will start to work again but only for a few minutes. This started when I had a NAND version of Android installed, I thought it may be something with the Android build so I flashed a different build and it still was not working. I then performed a task 29, reflashed HSPL, and the latest official stock rom from T mobile and the screen was still not working correctly. Is there any easy fix for this? If not what parts will I need to fix this correctly?
If you search around, this is a hardware issue - a faulty "digitizer" (connected to the LCD) - is known to the HD2 and other HTC devices. Fix = replace the digitizer. Repair by HTC is a good solution, if your HD2 is in warranty (which it very well may be in). I have this issue and have sent mine for repair.
yeah mine is on its way to me , becouse of the faulty digitizer
I am having the same issue.. I installed an android nand rom yesterday, everything was working perfect, then i used mass storage to copy games and as soon as i unplugged it, the touchscreen stopped working!! I thought some files got corrupt and tried reinstalling android, then stock win mo rom, and still the problem persists... any solution???
Related
Hey guys,
So my touchscreen totally died yesterday, wouldn't respond to any touches at all, hardware buttons still worked however.
Assuming this was a hardware fault I was just going through the motions to book the phone in for a repair, first step was to restore a stock ROM from the SD card, i was previously running hspl 2.08 with one of dutty's recent ROM's.
To my surprise the stock rom has fixed the screen so this was obviously some serious rom or spl error (I tried a hard reset yesterday before coming to the conclusion it was hardware related)
I thought I would post my findings in case it helps anyone else, and would be interested to know if anyone has come across this before, do you guys think this must have been an spl issue if a hard reset didn't fix???
lancemate.
thank you
this just happened to me its after 7pm pacific time htc is closed and im going to try it now
it did not work my touchscreen has still failed and if its because i should remove the spl then i havent done it yet and how do i do it if the touschreen is gone
ok i did remove the spl and put back the stock telstra rom still touch screen failure, so tired of working with winmo crashing hardware and software, i went to android twice and came back to winmo because its what i know, i just keep getting let down, before this the latest let down was winmosquare, i dont know how much longer i can hold out for windows phone 7, i just may go evo 4g
Hello All,
I have an HTC HD2 (TMOUS) that hangs once it gets warm. I got it a couple of days ago. The first thing I tried to do was to update the rom (there was an old stock rom) to the latest version from t-mobile. But when I tried to do that the update process failed at 8% with "error[262] update error". I tried to flash it again, but got the same result.
I tried both the approaches: to flash via usb and via SD card, but the results were the same. Flashing via SD card gave me "RSA fail" error. I have found some related info, but that is not the case since I could flash the radio later. Also I've noticed that after a couple of iterations the phone were vibrating 7 times during the rom update process. Some guys are telling that it could be a motherboard issue (http://forum.xda-developers.com/showthread.php?t=797179 and http://forum.xda-developers.com/showthread.php?t=826119).
Today I tried to update rom again and got it successfull. But the phone has hanged on botting. Taking into account that the phone has been turned off for the whole night I decided to try to put it into a cool place. I put it to the balcony for 5 minutes and the turned it on again. It has loaded successfully and I was able to test wifi and to make a couple of calls. But after some time when it has got warm it hanged.
I have found that some guys had the same problem but couldn't fix it (http://forum.xda-developers.com/showthread.php?t=701349).
It seems to me now that this is a hardware issue (maybe with the internal flash memory module).
Was anybody able to fix the isssue?
Could this problem be caused by my attempts to flash?
Thanks in advance.
Guys,
I'm kindly asking to share your thoughs on any of the questions. It is very important for me since I don't know whether it is my fault or the phone was already damaged.
The rom I tried to flash was a stock rom and the flashing process hasn't been interrupted.
Thank you!
had this issue and indeed it was the motherboard so i had to send it back to htc.
good luck.
az_registration said:
Hello All,
I have an HTC HD2 (TMOUS) that hangs once it gets warm. I got it a couple of days ago. The first thing I tried to do was to update the rom (there was an old stock rom) to the latest version from t-mobile. But when I tried to do that the update process failed at 8% with "error[262] update error". I tried to flash it again, but got the same result.
I tried both the approaches: to flash via usb and via SD card, but the results were the same. Flashing via SD card gave me "RSA fail" error. I have found some related info, but that is not the case since I could flash the radio later. Also I've noticed that after a couple of iterations the phone were vibrating 7 times during the rom update process. Some guys are telling that it could be a motherboard issue (http://forum.xda-developers.com/showthread.php?t=797179 and http://forum.xda-developers.com/showthread.php?t=826119).
Today I tried to update rom again and got it successfull. But the phone has hanged on botting. Taking into account that the phone has been turned off for the whole night I decided to try to put it into a cool place. I put it to the balcony for 5 minutes and the turned it on again. It has loaded successfully and I was able to test wifi and to make a couple of calls. But after some time when it has got warm it hanged.
I have found that some guys had the same problem but couldn't fix it (http://forum.xda-developers.com/showthread.php?t=701349).
It seems to me now that this is a hardware issue (maybe with the internal flash memory module).
Was anybody able to fix the isssue?
Could this problem be caused by my attempts to flash?
Thanks in advance.
Click to expand...
Click to collapse
Before you go trying to replace the mother board or any hardware such as that. I suggest you run a task 29 on your HD2 and reflash the stock ROM. A task 29 totally wipes the current ROM on the HD2 so if it is a problem from you trying so many timez to flash the ROM this will clear that up. Here is a link to the task 29 thread so you can learn more and decide if you want to do it or not.
Thank you for your replies!
T-Macgnolia said:
Before you go trying to replace the mother board or any hardware such as that. I suggest you run a task 29 on your HD2 and reflash the stock ROM. A task 29 totally wipes the current ROM on the HD2 so if it is a problem from you trying so many timez to flash the ROM this will clear that up. Here is a link to the task 29 thread so you can learn more and decide if you want to do it or not.
Click to expand...
Click to collapse
Yes, that's a useful tool, but I'm afraid that I might damage the existing rom and will not be able to flash it agian. Also it requires to flash HSPL before which also potentially might brick the device ( I mean the flashing process).
sike222 said:
had this issue and indeed it was the motherboard so i had to send it back to htc.
good luck.
Click to expand...
Click to collapse
So it was a factory defect, wasn't it?
If I did something wrong during the stock rom flashing process, could be the reason of the problem?
Thank you.
After reading forums it seems to me that the issue appears mostly for T-Mobile US version..
If it is a hardware problem, does anybody know what part of hardware is damaged?
Thanks!
I'm not a NOOB, I do it all possibilities for FIX the G-Sensor, but I'm very impresive with this problem....
If the G-Sensor of my HD2 doesn't work and I do it a Reset, Flashed a official update by T-Mobile, I installed android all correctly and it worked before because I have the phone from sealed box NEW NEW, What part of the HD2 I need to buy for repair?
Is your G Sensor working on WM or is it haywire on both Android and WM?. And is the G Sensor totally spolit or is it working and you are getting wrong outputs? If it is only on Android, you should try installing terminal emulator. Launch it, type su (return) bma150_usr( lay phone flat on back and hit return ) exit(return), exit(return and close). You should lay phone on its back. This might not work and after trying about 5 times, if it sill doesnt work, you should try reinstalling Android, or try a different build to see if that fixes a problem. But, i think you have already done that, so you might want to try a completely fresh installation. For WM, if calibration still didnt work, flashing a stock ROM is not enough. If the problem is still there, you should first flash HSPL,Task 29, Radio and the stock ROM. Then, perform a hard reset. If the G Sensor does not work like it is supposed to, then you should send it for repairs. Hope this helps.
I has Windows mobile 6.5 Stock from T-Mobile it doesn't work :/
Thanks for your help!
I flashed tytung Beta 9 of Android 4 and whole nightmare started.
Touchscreen aren working sometimes (most times)
In Windows Phone 7, android....I got this weird display acting (cant unlock, pick-up phone call...only sometimes when im lucky)
In Windows Mobile 6.5 no problem, nothing. (Multi touch, everything working fine)
I reflashed HSPL, do Task29, Reflashed rom like 100x times (winmo back to droid to wp7 back to winmo)...nothing helps.
Im out of warranty like a month. (Still i cant use that even if i have, because everything is OK when using original winmo rom :/)
Is there any way ? Or its time to grab a new phone ? :/
Ok first and foremost...I have tried searching
I have been a lurker most of the time here on xda seeing as if I just search and read I'll get most of my answers, but not this time.
Ok some background info first:
TMOUS US HD2 1024Leo
Radio: I'm not 100% sure but I did a task29 that supposedly flashed 2.15.50.14
HSPL: 2.08
MAGLDR 1.13
I bought this phone about a year ago, flashed tytung's Nexus HD2 Gingerbread rom which worked flawlessly for about 10 months or so. One day the phone froze up, pulled battery then inserted and the rom reset to the point where it was like new. Around that time tytung's ICS AOSP thread came alive and I followed it closely watching the updates and what not.
I never installed it until Beta 10. Followed his instructions, set up the partition to 200MBs with a cache of 45MB...45MB for cache because I suspect I may have some bad NAND blocks. Anyways install went flawlessly, everything that was supposed to work, worked...ect ect
Used it for about 24hrs then all of a sudden it froze, when I rebooted I started getting all these random apps crashing(gapps[google apps?], Email, Google Login Services ect), needless to say I task29'd the HD2 and reinstalled everything, worked fine for a day then everything started crashing again.
So after all that info I'm just wondering if someone is experiencing the same problems and/or can maybe lead me in the right direction to figure out this problem.
I know its only a beta but I havent read many posts containing my problems. So Im just left wondering if my NAND is going bad completely and I need a new phone or if theres just something I'm doing wrong.
Before i begin - I have no experience with that Rom, these are just common general ideas.
1) as the rom starts well and then only after a day it breaks, maybe it is because of something (update) getting installed on your device. Have you tried fixing permissions after you encounter the problem?
Or try figuring out which update of which app does it.
2)It also might be the problem of the nand bad blocks, if you suspect it, but if thats the case, there is not really a lot you can do...
No offense, but that's the reason its beta. It doesn't have all the bugs worked out yet.
If you're looking for a daily driver, you should try something more stable.
Hi,
Not sure if you still have this problem..
Have you tried re-installing the ROM again or a different ROM to confirm if the issue is with your phone (hardware) or with the ROM (beta version)?