WARNING: This might be redundantly long. But at least it's clear. I believe it to be a matter of wp7 and android. So it'd be inappropriate to paste it in either one of those. Enjoy reading!
I've scrolled around the forums for a possible answer, but I couldn't find any threads with exactly my problem. I'll organize the situation:
Problem: HD2 Won't turn on.
(That's about as helpful as saying 'I put gas in my car, put a key in it, and it won't turn on. Help?' right?)
What happened: I was following the thread http://forum.xda-developers.com/showthread.php?p=11097380 (Not slandering them, just using it as a reference to help the trouble shooting of what's going on.) And I followed it as it went. I tried flashing the radio leo rom 2.15.50.14. And it completed. But then my phone turned off, and hasn't come back on yet. It makes the "ba-dum" noise when I plug it into my PC though. Although, there is no faint vibration like I've read with other's problems.
Background info: I've stumbled through about 3 or 4 flashings of wp7 roms and such. As I've broken them all. This one managed to survive since July. And I wanted to try an android os, it's been a while since I've touched any android phones. Anyways, I had wp7 and all the appropriate downloadings/flashings onto it. I thought maybe I should start over, and just follow the guide's steps. Although! There's the problem that I can't use .xaps to my phone. I can sync with my zune library, but I can't xap anything to it. Essentially I'm saying it works, but it doesn't.
And finally, the reason why I did this: The screen progressively became unresponsive. It started as what seemed as if I had oil on my fingers, and it fixed itself within a few seconds. As the days went on, it became minutes, then it finally stopped working. I'd go on to take out the battery, then have to restart it. Also, like a past hd2 of mine, it's moved onto restarting itself at random times. Sometimes one boot up after the next, or just randomly. It was perfectly fine. Perfect.
P.S. Sorry for the length, I wanted to be completely clear to prevent questions like, "Need more info. What's exactly wrong?".
Thanks for anyone helping me! I really do appreciate it. I don't want to have to get ANOTHER one.
P.S.S I'm really terrified of it being bricked. Although, it didn't work at the moment anyways. But I was hoping to attempt to fix it. OH, and I called t-mobile about the screen being unresponsive. (Don't worry, they don't know what I've flashed to it ) They told me to hard reset it with vol up/down + red button. I tried that. The screen worked again. For a short while. And every now, and a thousand random reboots, the screen will proceed to work. But it doesn't show a history of texts during the duration it works. And it usually freezes, then boots down. Boots up, and stops working.
sorry to be the bearer but it sounds as though you're yet another victim of the digitizer hardware issue. its one of those things that simply cant be helped and seemingly comes out of nowhere!
you might, however, go back to basics. start by flashing a stock winmo 6.x rom. if that cures your screen troubles you will have a fresh base to start over (and more carefully) ... if it doesnt fix screen troubles and it stays unresponsive you will have it already ready to be shipped off to be replaced ( this way tmo or wherever you're sending it to wont be able to say YOU caused the screen issue)
in any case i wish you luck!
Related
Thanks for reading.
I'm currently using WM6.1 on the phone, and loving everything about it.
Since day 1, I've used a phone lock code, along with PIN1 code.
When unlocking the phone for after say an hours inactivity, the keypad will show, then the screen will go blank only showing the top bar of the phone.
Any press of buttons and screen will just make a beeping sound, and so far nothing I've done will restore the keypad to unlock the phone.
Is there anything wrong with the ROM i have, and is there anyone who can suggest how to correct this?
Please remember, the top bar still shows, and a reset allows the phone to work as normal (once logging back into it of course).
Thank you,
Hi guys,
Sorry to bring this back up, but this problem is still going on.
Not sure how to resolve it, so hoping someone would know how to solve this.
Thanks,
Posted twice for some reason.
Maybe is a sw failure,(50%) try to reflash with this fw: RUU_Hermes_CINGULAR_WWE_3625023_6275_1540700_108_UOOS_SVN05_Ship.exe
if your hermes its from att/cingular. after flash open and close the tap of hermes, if the blank screen continues or return this, the failure is hw (the flex component broken,bus, pcb) in this case you need to buy the spare part or send to sat.
good luck
other possible solution
http://forum.xda-developers.com/showthread.php?t=321163
Hi there,
Its not white screening, or anything else, I think the next time it does this, I'm going to have to take a picture, to make sure it can be understood clearly.
Basically, when bringing the phone out of standby (from pressing off/on button) and attempting to enter my pin into the phone the phone will allow me usually to press at least one number of my pin, and then it'll black screen, where the start bar still displays, but no response.
The handset isn't problematic when being opened for use, or anything else, its just annoying to have to reset to load the phone back up again.
I hope this helps?
Further to the above, here is what i've been talking about...
Happened last night, typically as I was bored, and had to wait till morning to take the photo...
Still no movement on this post...
Would it be suggestable to upgrade the install of WM?
If it is, how easy (will read guides beforehand) is it to do (reasonably, hard etc).
Just this is now my only phone, so don't fancy my chances bricking it.
Thanks!
Sorry to be posting yet again, but this has now happened 3 times a in row since last night. I wouldn't mind knowing if a rom fix would sort this, and if so whats the best rom to go for...
Just keen to get this sorted now...
Thanks.
If it helps, I've nothing running when this happens. The exception of last night, where I was using Audio Manager when walking home, and had to soft reset once in the door.
Hi
I am almost certain you have a software fault here and need to reload a new ROM - take your pick - my preference is schnaps - it isnt that hard to do and should solve your problem
Just go to the Windows upgrading section on here and follow the process - you will be happy
John
I had a strange issue recently with my build (below). I had a 'normal' data freeze and rebooted, but when I did, apparently a message was waiting and some appointment on my calendar was due. This seemed to really slow down WM and HaRET ran very slowly before booting Android. However, after Android booted, the touchscreen was locked and wouldn't slide out of the way. In fact, the screen darkened and shut off just as if I wasn't touching the screen at all. I did receive a phone call, which worked, but touchscreen was still unresponsive.
So I tried rebooting again. This seemed to lock up JMZ Dual Boot and not allow me to boot up Android. Moreover, it locked my touchscreen in WM! I have pocketshield installed, and after cover screen showed up, I couldn't move it away. I tried rebooting, taking the battery out for 5 minutes, etc. and no luck.
Ultimately, I resolved this by a HARD RESET of the phone. Lost my windows setup which will take some time to repair, but since I use Android most of the time, maybe it doesn't matter?
Anyway, posted this in case others are having this problem, maybe there's a theme.
editted: ok, touchscreen stopped responding again, in WM and Android, while the unit was just sitting on my desk. I'm now thinking hardware problem...
yes i have the same problem since a ~week. NO TOUCHSCREEN... i have flashed maybe 100 different roms, but no luck... even when i install the original vodafone rom with radio and downgrade to spl 1.48 it doesnt work... this must be an android issue i think.
yesterday i was in the vodafone shop and they give me an NEW HD2 ))))).
now im waiting for an solution about that problem and hope someone will fix it. untill that i will stay on WM6.x. i dont think, i will get another new HD2^^
sorry about my bad english! im german...
ps: when i started the hd2 there was an picture of an WORLD MAP for ~one second. maybe this helps. i think there is something in the front of the orange screen. something with "yes" or "no" option. but i cant see it.
Ok, so here's the full story;
I dropped my phone a month or so back, and the LCD broke, so I bought a new LCD/digitizer on eBay. I've replaced screens on heaps of phones/cameras before, and this wasn't that challenging (HTC actually provide a video tutorial on disassembly/assembly), but now that it's all back together it has some serious problems.
The first time I turned it on it was fine - I went through WM6.5, booted into android no probs, made a call and turned WiFi on to test connections, but after about 15 mins it froze and I had to pull the battery. Now I cannot turn it on. most of the time, I turn it on and it brings up the very first splash screen for the ChuckyDroid ROM I have on it, but stays there. Occasionally it will load further, and VERY occasionally it will get all the way into WM6.5, but 90% of the time, it will turn on, load the first splash screen, then vibrate 7 times before freezing completely.
I've read about this problem on other phones, but haven't seen anyone provide a working solution. I am positive that all the assembly has been done correctly (especially seeing as people are getting it on their stock phones, HD2 included), and would really like any help.
Thanks in advance,
Jason
I think the motherboard has problem when you drop it. The device will vibrate 7 times if NAND error. Usually when the device gets hotter or warmer, NAND become unreadable. This is the error that many users have even myself.
To temporarily solve this, you can take out the battery, and put your phone in the freezer for 5 minutes, then take it out. Put the battery on. Then turn the phone on. It will work normally if the bottom part stay cold. So make sure you have a bag of ice to cool the bottom down while using.
Another way is send the phone to HTC and request a fix... cause this is motherboard problem.
bobuchacha said:
I think the motherboard has problem when you drop it. The device will vibrate 7 times if NAND error. Usually when the device gets hotter or warmer, NAND become unreadable. This is the error that many users have even myself.
To temporarily solve this, you can take out the battery, and put your phone in the freezer for 5 minutes, then take it out. Put the battery on. Then turn the phone on. It will work normally if the bottom part stay cold. So make sure you have a bag of ice to cool the bottom down while using.
Another way is send the phone to HTC and request a fix... cause this is motherboard problem.
Click to expand...
Click to collapse
Like BOBUCHACHA said ... thats nand problems... i also have same problem too... you can try doing some modification ... follow this thread to do so
http://forum.xda-developers.com/showthread.php?t=971783
ok, I have a strange issue that I can not seem to find the answer to. Whenever my phone locks after not being used etc. When I wake it up, the touchscreen will not let me unlock. It takes me close to 50 attempts to do so. However once I actually am successful in getting it unlocked. The touchscreen works flawlessly. I have tried several different builds, all of them I have the same issue. I have done Task29 and started fresh on that front each time. I tried a couple different radios. Any suggestions?
**** man i got the same problem! i tried hard reset, rom updates, other buils but it wont go away!
plz someone help us!
Hi,I'm using BOYPPC-SHIFTPDA GINGER 2.3.3 RAM_V5 works great so far the best that I tried.After u flash android it's recommended to wait few mins until it loads everything then do a shut down - not a restart.then again u wait few mins and u do a second shut down. after that the os should work fine ,at least for me works great. if that doesn't help ,try to reinstall everything from the start..hspl radio etc.
You could just turn off the lockscreen? Get 'NoLock' from the market. That should do the business if you want.
I've got the same problem since 5 days, It started when I started using WIFI and turning off my 3G ..
you have the same problem my hd2 has....it is a hardware issue. the screen becomes unresponsive. if you still have warranty send it in for a repair. if not... repair it yourself. it's not that hard. the screen wire is probably just loose.
follow this video to take apart your hd2.
http://www.youtube.com/watch?v=cL-jnUKufC4
Sounds like a similar problem that I'm experiencing. If I wake the lockscreen with the send key instead, it works. When I boot I get exactly one shot with the end key then it locks up again. I'm able to use it with the send key, but concerned it might get worse. If anyone finds the solution please post.
I actually for the first time had this, and I know this is going to get flamed but its not the Screen thats the problem. And I think (BIG IF) that the dreaded unresponsive screen issue that we keep reading about Majority of them I think is not the screen.
I have 2 HD2s and both have worked flawlessly without any problems, but today I was playing with my test phone that doesnt get used that much and I noticed after installing a new rom that my screen after I played with it for a bit went black (sleep) and when I woke it up it wouldnt respond, first thing that crossed my mind is I just lost my digitizier, and started wondering okay why, I went as far to re-flash WinMo stock HD2 rom, same issue, so I decided its time to find out exactly whats causing this, and I found it. I wasnt going to make a post again cause I figured people would be "Not another thread about this" but I know whats causing the screen issue, at least this is my suspicision and I have temporarily fixed mine.
The problem is HARDWARE, The Culprit: THE END KEY (Red Button)! The Answer to "How or Why": The "End" key is used to turn the phone on and off or to put it in sleep mode, it is the most used key out of all 5 keys, it is used probably 7x more then all the rest, Its used for just about everything, now how does this cause the unresponsive screen? Easy, the phone lock or sleep is associated with this key, Its the only way to make the screen go off other then waiting for the time out period. Because by habit we mostly hit the end key to turn the screen off the phone automatically associates this with locking the phone, once that happens the screen becomes unresponsive because of several reasons: 1) The contact under the actual key has dirt which causes the button to stick in the down position, 2) the contact is bent which the "end" key is pressing down on the contact which is making contact with the board and causing it to be unresponsive, 3) The contact is worn. This is the reason why if you press the end key a few times (anywhere between 2-10) and then try the screen responds, this is cause your "unsticking" the key which then lets the screen respond.
Most of us when we hit the end key press to the far right to avoid hitting the back key (The button with the left arrow) which causes the end button to lean toward the right. But you can wake the phone up with the other 4 keys to the lock screen which will allow you to unlock the phone. As a temporary fix for myself, on my test phone I now make sure to press on the left side of the key to prevent this from happening, since its a test phone I'm not worried, but the real solution is to take the phone apart and clean the underside of the end button, and the actual contact with alcohol to remove the build up of dirt and whatever else. And also if the contact frame is bent to GENTLY bend the right side back up alittle to stop it from happening, or sending it to htc and letting them fix it.
We have to RE-TRAIN ourselves to start using the other keys to wake the phone up and not rely on the end key so much.
Hope this helps anyone finally why we have this problem. And if it works for you then hit the Thanks button
I think here might be something wrong with the htc sense, but the thing is, that my hd2 touchscreen wont respond to my touch. When i'm at the unlock screen, i cant slide it to open up. This wont change after reboot either.
So eventually i set a hard-reset on the phone, but it didn't work after that either. I tried three times, no respond. Without the sim and with it in.
I cant recive calls or text messages, because i cant tap my PIN in, neither i could open or answer. I'm f***ed.
Okay, the next day i do my fourth hard-reset, and it starts working again, but after a time of use, it will start getting slow with the touch again, and then it will stop responding again. So I don't now what to do. There is now warranty time left, so i want to see what i can do my self before taking it to a repairing place and pay 100 € for it.
This is my everyday phone, and i would like to get it back to normal state as soon as possible, so many many many thanks to all who try to help me out of this
Cheers,
Nother
notherman10 said:
I think here might be something wrong with the htc sense, but the thing is, that my hd2 touchscreen wont respond to my touch. When i'm at the unlock screen, i cant slide it to open up. This wont change after reboot either.
So eventually i set a hard-reset on the phone, but it didn't work after that either. I tried three times, no respond. Without the sim and with it in.
I cant recive calls or text messages, because i cant tap my PIN in, neither i could open or answer. I'm f***ed.
Okay, the next day i do my fourth hard-reset, and it starts working again, but after a time of use, it will start getting slow with the touch again, and then it will stop responding again. So I don't now what to do. There is now warranty time left, so i want to see what i can do my self before taking it to a repairing place and pay 100 € for it.
This is my everyday phone, and i would like to get it back to normal state as soon as possible, so many many many thanks to all who try to help me out of this
Cheers,
Nother
Click to expand...
Click to collapse
Have you flashed HSPL on it or this is all stock ROM?
honestly it looks like a hardware issue to me.
well i looked at the stats, and seems like i have HSPL on it, but it's not bought from a reseller, it was bought second-hand. it has worked perfectly until a few days ago, then the freezing started.
notherman10 said:
well i looked at the stats, and seems like i have HSPL on it, but it's not bought from a reseller, it was bought second-hand. it has worked perfectly until a few days ago, then the freezing started.
Click to expand...
Click to collapse
ok if it has HSPL on there that means someone flashed something on there.
I would flash task29, then flash the ROM of your choice and see if it still does it.
If the ROM is the problem a hard-reset won't fix it, so let's try this and see what happens.
Okay thanks for the help
the only problem is that i'm running on a mac, and i cant find any software to flash the hd2 on a mac..? Do you now any?
and could you link me a thread or a tutorial to how to flash 'cause i'm quite new with this anyway.
Thanks!
notherman10 said:
Okay thanks for the help
the only problem is that i'm running on a mac, and i cant find any software to flash the hd2 on a mac..? Do you now any?
and could you link me a thread or a tutorial to how to flash 'cause i'm quite new with this anyway.
Thanks!
Click to expand...
Click to collapse
There is no way to do this on a mac, find a PC.
ok, here's the quick version.
1) download the attached file from this post:
http://forum.xda-developers.com/showpost.php?p=5848003&postcount=19
2) turn your phone off, then turn it back on while holding the vol-down arrow, this will bring you to a tri color screen. Make sure you are plugged in via USB.
(you could do this via activesync, but I want to avoid the freeze so this gets you right into bootloader)
3) unzip the file and run it, follow the on-screen instructions, it will flash task 29, which is basically a good reformat.
4) if you are fast, hold the vol down arrow when it reaches 100% and don't let go till you're back at the tri-color screen. If it goes to the splash screen it will stay there forever (because there is nothing flashed on your phone now). You have to do a battery pull or press the reset button. In this case hold the vol-down arrow again and power on the device to get you into the tri-color screen again.
5) Download the ROM of your choice from this forum:
http://forum.xda-developers.com/forumdisplay.php?f=534
They are all custom ROMs, my favorite is the this one currently:
http://hotfile.com/dl/117879873/9b01b43/Energy.Leo.29020.Sense2.5.Cookie.2.0.sencity.May.14.7z.html
It was taken from this thread:
http://forum.xda-developers.com/showthread.php?t=591784
and is the awesome one with big finger friendly buttons as well as that awesome blackish theme (Sencity)
If you don't want a custom ROM then go to the HTC support site and find your stock ROM, download and flash that via SD card (I am assuming you have an international HD2 and not a TMOUS one).
If for some reason you have a TMOUS one DO NOT GO THRU HTC BUT USE TMOBILE'S SUPPORT SITE.
Let's get you rocking and rolling!
Thank you very much for your help, i'm very grateful
I'm going to run W7 virtually, just to be quick.
And I was thinking to flash straight to Android, is that possible? Like android 2.3 or something.
Cheers!
sorry if I made you unhappy, but my phone is now in a technic service due to same problem, it never fixed with a rom update, day by day your problem will appear more frequently, this is a hardware issue, maybe digitizer maybe hardware buttons block your touch screen.. I will see what will happen after my phone come to my hands again..
Okay thanks.
I will see what the reflashing will do. Then if it doesn't work, i will take it to repairing.
Thanks!
notherman10 said:
Then if it doesn't work, i will take it to repairing
Click to expand...
Click to collapse
definitely send to repairing and dont try any thing by you self ... you will end doing more damage - except Software solution...
anyway i wish all the best and i hope you fixit
best regards from me