Database Users

My touchscreen no longer works

Starting today, my touchscreen just doesn't register anything. It's not cracked or damaged at all. It just stopped responding. I can still use my dpad but my phone is extremely limited at this point.
I'm currently running Myn's Warm Eclair: http://forum.xda-developers.com/showthread.php?t=691174
I really don't want to format my phone to figure out if it's a software problem but does anyone know if this is just a problem with this android build or with android on our phone in general?

thehelios said:
Starting today, my touchscreen just doesn't register anything. It's not cracked or damaged at all. It just stopped responding. I can still use my dpad but my phone is extremely limited at this point.
I'm currently running Myn's Warm Eclair: http://forum.xda-developers.com/showthread.php?t=691174
I really don't want to format my phone to figure out if it's a software problem but does anyone know if this is just a problem with this android build or with android on our phone in general?
Click to expand...
Click to collapse
It has been a problem for me with some builds. I suggest you to make a backup with some app like Titanium Backup and reinstall Android. Try with different kernels if you still have the problem. Don't worry for the moment!

I have had this problem a few times. I still can't quite figure out exactly what makes it happen but it seems to be something to do with sleep. My solution is to restart and go into NAND then do a backup apps and then quit. something gets woken up in the screen and it starts to work again. No idea why, it just does. Good luck.

So I guess my touchscreen is just dead. I reinstalled android, reflashed my phone for the froyo rom, and I even flashed a windows rom onto my phone but nothing. I even opened my phone to see if it was connected properly to the mobo but all seems right.
On the windows rom, when it does the screen calibration, I can mash the crap out of my screen and I guess it picks up some sort of signal every now and then because the crosshair moved.
If anyone knows anything about this, please reply. I don't really want this to be the end of my vogue. It's been a good 3 years so far!

http://cgi.ebay.com/Touch-Screen-Di...749473?pt=PDA_Accessories&hash=item439b537fa1
You may just need a new Digitizer.
Can get them pretty cheap on e-bay - just have to wait since coming international mail.

I am having similar problems. Usually when the phone goes to sleep and I wake it up the touch screen is unresponsive. Only way to get touch to respond is to reboot.
I have tried it on my vogue on both the fresh froyo and experimental fat free froyo using both the 10-9 and 9-29 kernel on nand. I have also used nbh editor to change the panel types (vogue uses auto detect so I changed it to Polaris) and still the same problem. I thought perhaps there was a problem with a program but I have no programs installed right now and the problem still persists.
Does anyone have any suggestions? My phone was working fine up to a few weeks ago and I would hate to be forced to use windows again. I have reinstalled windows and it works fine there so I don't think it is hardware related. It seems something happens when it goes to sleep.

Well there might be a driver issue. Try going back to the stock rom for your device and see if the touchscreen works, if it doesn't work, then it's probably broken. Try opening the vogue and disconnecting and reconnecting and then turning your device back on and test it again. if it still doesn't work, then yea you will have to get a new digitizer.
You can also try using other releases/roms with different kernels.
good luck!! and may your vogue live on!!

Thanks, I've installed a windows rom and the touchscreen has no issue there so it leads me to believe it is not the digitizer, especially because it seems to break when it goes to sleep.
I will try even older kernels and perhaps a donut build to see if the problem still exists.

Try to figure out when things broke for you by trying the kernels that have been released over the past month. Maybe we can isolate the change that broke things for you. Maybe not, but it's worth a try.

n2rjt said:
Try to figure out when things broke for you by trying the kernels that have been released over the past month. Maybe we can isolate the change that broke things for you. Maybe not, but it's worth a try.
Click to expand...
Click to collapse
Hi! I had this problem, that was the reason why I put back WM. I experienced it using .32. I think it was from 1-Oct-2010 approximately when it started to fail.

IT'S A CONSPIRACY!!!! Last week my screen broke as well. I was running "not so super froyo" and it would work for a second then just be completely unresponsive... needless to say I now have a droid x *fap**fap*

[Q] screen unresponsive after "screen-off"

I've picked up a strange issue in the last few days ... but I'm not sure it's a hardware/software/firmware problem.
Symptoms:
A. Pull battery & restart ... everything works fine no matter how long I use the phone AS LONG as I don't allow the screen to blank (lock is disabled).
B. If Screen blanks, push power button & it lights up again ... now the phone won't detect ANY touches on the screen, the HW buttons are fine, any programmes running that display, etc are still running fine, clock updates, music/video plays ... just no touch is detected.
History:
1.) All was fine, HSPL: 2.08, Radio: 2.15.50.14, WM: EnergyROM, Android: Cope'nWarren SD AmeriCanAndroid
2.) Decided I wanted to play with NAND Android
a.) Had to install MAGLDR for that ... worked fine
b.) Installed HyperDroid-GBX-v12-signed ... problem cropped up the 1st time the screen was locked, played with various settings, no joy.
3.) conclusion ... problem with that ROM, no problem, reflash Energy ROM
4.) reflash Energy ROM ... problem still exists ... uh-oh
5.) Task 29 ... successful
6.) Flashed stock shipped ROM (RUU_Leo_HTC_WWE-AFK_1.66.421.1_Radio_15.32.50.07U_2.07.51.22_2_Signed_LEO_Ship) which I got directly from HTC here in South Africa ... problem still exists. BIG UH-OH
So obviously the problem is ROM, Radio & Bootloader independant (because the shipped ROM replaces all of that) ... which seems to indicate a Hardware issue.
The reasons I am wondering if it is NOT a hardware issue are twofold:
1.) The problem appeared so abruptly, after flashing MAGLDR & HyperDroid
2.) The problem ONLY exists after a screen-blank and not between powering on & a screen-blank.
Anyone with any ideas I can try, or advice?
Regards,
Peter

I have the same exact problem, while im in the OS i can use it for a long time, but when I hit the unlock screen I cant do anything! it makes no sense!

It is known for a while that something happens to the screen of certain devices after using NAND android. since I'm not using it I'm fine. You should search a bit before you do anything new.
I've seen plenty of milar threads before, try these keywords:
Digitizer touchscreen Unresponsive NAND Android etc.
I'm sure you'll find what you're looking for, not sure if anyone found a solution to that though.

Tx
Thanks ... suddenly a lot of old "screen locked" threads are "alive" & at the top of the forum!
You pointed me in the right direction ... now at least I can use my phone!
To anyone else who reads this ... use your OTHER hardware buttons to wake up the phone ... the END (rightmost) one is getting "worn" ... will eventually need replacing, but now it can be later ... hopefully MUCH later.
Seems MAGLDR isn't the cause, but because you use it (END button) so much when using MAGLDR, that's when the problem becomes evident ...

... Sadly ...
Sadly I have to let you know that it didn't taks so long for the problem to spread to all my hard keys!
I sent it in for repairs & was informed that they CANNOT only replace the "digitizer", but have to replace the entire screen (R2200-00 [South African Rands = ~ $300-00]).
I decided to rather get myself a Desire HD & am very happy with it.
My wife asked me to repair the phone anyway, so she could inherit it ... she's used if for a week now & the problem has reappeared ... On a brand new screen!!!! Am taking it back in.

Not Your Ordinary FREEZING Issue!

So my HD2 freezes constantly. I don't have the unlock freezing issue nor the black screen freezing issue. My phone will just freeze quite constantly. Doesn't matter if I'm just doing a message, online, or it's just sitting there doing nothing. It will freeze and will have to remove the battery and restart it. I've reinstalled MAGLDR, CWM, and tried several ROMS and it still doesn't make a difference. I remove the battery and have to let it cool for around an hour just to turn it on and be able to use it for a period of time.
Any suggestions out there? Could the battery be bad? The hardware? I constantly use Task Killer and Data Eraser to make sure there aren't unnecessary programs running. I've narrowed my app collection to just the necessary ones that I need. Still doesn't make a difference. Any programs out there that would help with this issue in any way. Would repartitioning my SD card help at all. I have pretty much everything on my SD card as well so the hardware shouldn't be overloaded at all.
Any help would be greatly appreciated.
Thanks!

check here

LOADS of people are having this problem including myself.
As long as Mobile Data and Gps are OFF, I have no freezing issues.
BUT, if I turn on Mobile date or Gps, or both, then GAME OVER.....it freezes within seconds.
It's not your battery, or SD card and don't listen to the muppets who repeat themselves by saying "do a task29" coz it doesn't work.
I've tried 5 different SD card, got 2 hd2's, task29, over 100 roms, different radios etc etc.
Never used to happen on SD builds, only Nand.
if i had the cash, i'd smash my hd2 against the wall and get a Android native phone.
this aint ever gonna be solved.
matt

freeridindirtbiker said:
So my HD2 freezes constantly. I don't have the unlock freezing issue nor the black screen freezing issue. My phone will just freeze quite constantly. Doesn't matter if I'm just doing a message, online, or it's just sitting there doing nothing. It will freeze and will have to remove the battery and restart it. I've reinstalled MAGLDR, CWM, and tried several ROMS and it still doesn't make a difference. I remove the battery and have to let it cool for around an hour just to turn it on and be able to use it for a period of time.
Any suggestions out there? Could the battery be bad? The hardware? I constantly use Task Killer and Data Eraser to make sure there aren't unnecessary programs running. I've narrowed my app collection to just the necessary ones that I need. Still doesn't make a difference. Any programs out there that would help with this issue in any way. Would repartitioning my SD card help at all. I have pretty much everything on my SD card as well so the hardware shouldn't be overloaded at all.
Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Hi,
It might be worth trying to flash an original ROM and seeing if the same thing occurs in WinMo.

Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?

TheATHEiST said:
Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?
Click to expand...
Click to collapse
I've tried all those things. I'm using the Nexus 2 Gingerbread ROM by tytung. I've tried winmo roms, android, etc. I've done task 29 several times. Different radios as well. It doesn't make a difference at all. I found a thread that might be the culmination of it all. If anyone else is having problems like I am, take a look at this thread. It's definitely the motherboard overheating and freezing/and or shutting itself off.
http://forum.xda-developers.com/showthread.php?t=982454
Luckily, I pay insurance through t-mobile so I will be picking up a new HD2 pretty soon.

I had a similar problem, but mine came about under different circumstances. I smashed my HD2 against a wall for whatever personal reasons that you shouldn't care about, anyway, so I ordered a replacement display. When I installed the display the phone would freeze just as described by OP. I found that disabling GPS and WiFi allowed me to use it for a longer time, but if I ever so much as applied any pressure to the display (rather than just lightly touching it) the screen would freeze and sometimes it would just straight shut off until it didn't turn back on at all (this was barely the first day after installation). I opened the phone and tested, found out that the LCD flex cable had a defect to it where if it was bent (the position it's supposed to be in once the phone is assembled) the display would "short out" and with the cable fully extended no problems would be present, even after applying pressure to the display or any of the other internal components.
I'm sending my LCD back for a replacement and hopefully the new one will work fine. I've read that some LCD's cause the HD2 to freeze and I think I was unlucky enough to receive one such. I need the phone to hold on long enough until I get my contract renewal May 2012. I'm surviving on my Dream right now and I'm going through Angry Birds withdrawal...

Compatible-Bad Hardware-Insurance Questions
freeridindirtbiker said:
I've tried all those things. I'm using the Nexus 2 Gingerbread ROM by tytung. I've tried winmo roms, android, etc. I've done task 29 several times. Different radios as well. It doesn't make a difference at all. I found a thread that might be the culmination of it all. If anyone else is having problems like I am, take a look at this thread. It's definitely the motherboard overheating and freezing/and or shutting itself off.
http://forum.xda-developers.com/showthread.php?t=982454
Luckily, I pay insurance through t-mobile so I will be picking up a new HD2 pretty soon.
Click to expand...
Click to collapse
I have similar issue. Could use advice. Please.
My HD2 is about a year old. Decided to try android on the sd.
Device: HTC HD2 TMOUSA
Radio: 2.10.50.26 (Original) NOW flashed to 2.15.50.14
SPL: 2.10.xxxx (Original) NOW HSLP 2.08.0000
Android Rom: SD AmeriCanAndroid AOSP HD2 GB234 CM71
WM Rom: 2.13.531.1 (Original)
ACA seemed ok but would freeze randomly. So I flashed the radio to the 50.14. Seemed a little better but still a few freezes in android. Thought I would try the partition to improve the sd card performance. can't tell if it helped or not to many freeze ups to use android during the day. NOW my winmo side it giving me random reboots. It gets hot reboots, especially bad if using gps. I know overheating is part of the issue because during the middle of the day in my car without A/C it is terrible.
I also have an OTTERBOX Defend which has kept the phone looking great but is a really pain with on all the battery removal with the freeze ups.
I have read that this can be a mainboard issue, but how can I tell if it is or not?
Could the radio and winmo rom be incompatible?
Should I flash the winmo rom to a more compatible android rom?
Should I send it in since I have TMO insurance? (Anyone know if there is a deductible if you didn't lose the phone?)
I have also noticed the on the winmo side it reboots less if I turn htc sense off.
Not sure if I should go back to a different radio or send it in?
Are the insurance replacements refurbished or new? do they have the same issue?
Thanks for any expertise you care to share.

Had similar problems with Tmous HD2. Problems were really bad in Winmo; aca worked somewhat better. Read forums, tried standard "solutions". With time the problems got to the point where the HD2 would not boot unless it had been placed in the refrigerator for 5 minutes.
Did T-Mobile warranty exchange in April. Replacement was refurb (arrives without battery or sd card, used old one), but looked fine. Had a week to test "new" phone, before sending the old one back. Replacment phone works much better. In Winmo, gps, videos, sense no longer cause reboots; aca also works great.
Hope this helps...

TheATHEiST said:
Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?
Click to expand...
Click to collapse
Exactly as my post from a few days ago predicted..."task 29"
FFS.

[HELP!] Rescue this baby! Challenge Accepted!

Ok guys, I need your help. I picked up a T-Mobile HD2 from a friend for $40 who said "it won't boot". Being the experience Android user that I am I decided to give it a try, but I am at my wits end. Here is the sitch:
1. The phone is stuck at the "Stick Together" screen.
2. The bootload WORKS, to a point. It sometimes give a black screen when connected to the computer and a flashing tool is polling the USB.
3. I can flash all different WinMO roms from the bootloader, even HSPL, but still no boot.
4. Sometimes, when the ROM and SPL info come up in the bottom left, the phone will chug at the boot logo for a second, then strange graphical glitches start to appear on the screen. Similar to flashing an i9100 kernel on captivate, but not exactly.
This phone is a hackers dream, or more specifically my dream phone. Please help me get it back to working. I am not stingy; if there person who can get this to work and has a donation link... well... you know.
I have already:
Flashed the ship rom.
Used Task29
Flashed the current TMO rom.
Installed MAGLDR -> bootloader cannot make it to MAGLDR, even holding button.
EDIT: I also can't get it to recognize or flash roms from the SD card. All I have is a 4GB SDHC.

i can't figure out for sure if it's hardware or software that's been failing you. Since i'm more experienced with hardware i'll try to figure out a cause should the problem turn out to be hardware based after all.
1. nand memory corruption. the nand memory is made out of individual memory blocks, linked in a matrix mode and controlled by a memory ...controller (pretty logical i guess ). NAND memory is organized at a logical level in a way very similar to the classical electromagnetic drives (normal hdd's). I mean, blocks, sectors etc. If a memory sector gets damaged, it will produce something called a "bad" memory block. Again, similar to HDD's. But, different to HDD's where you can remap the memory regions and isolate bad blocks, you cannot do this to a flash chip inside a phone. At least not using standard tools or software. These tests are made only once by the manufacturer when the motherboard itself is being build. So, if your nand memory get's corrupted the phone itself won't "know" it since the individual damaged blocks can't be "marked" as damaged for the software to see and avoid placing data over there.
What happens is that you flash a rom, it may complete to 100% and from the bootloader "point of view" data was written over the flash memory. But when you attempt reading data from the damaged sectors, you'll get either nothing or corrupted readings. A more worse situation is when the boadloader itself resides over the damaged memory areas. If this is the case, even bootloader operations will behave erratic - bootloader lock-ups, freezes, strange screens etc.
I've seen phones with similar behavior that will react just like that. Sometime you can flash them, sometime not and when you flash them, they will stick to some random screen or simply freeze since the OS loading process halted with some random error when the corrupted data was read. I only managed to fix this by means of JTAG, a pretty low level debugging tool that requires a direct interface between the cpu and a pc. A memory diagnostic is loaded into the RAM memory and executes from there, it's purpose being to remap the NAND memory. It cannot be done from inside the NAND memory itself just like you cannot simply format the windows drive on a pc, while still being logged in on windows.
But, it's nasty business, service center kind of business.
2. CPU I/O failure. If you look into my signature here on xda, you'll find a link about hd2's cpu and overheating. That problem can in turn cause your problems - also saw this kind of stuff happening to a hd2. In fact is easier to determine if this is the cause. While i won't repeat myself again about how heat cause dilatation in the chip's soldering and how this affects the cpu operations, you can try a simple test. Place a sd card with some rom on it in the phone then place the phone in a bag, then place the bag in the fridge for about an hour. After that (while still keeping the phone in the bag and in the fridge interior) power on the phone, go to the bootloader and try to flash the rom from the sd card. Let the phone in the fridge during flashing and after it restarts. If you can't load a rom from the sd card, try using usb, the ideea is that the phone must remain as cold as possible during the whole process. Check to see if you notice any improvements - phone booting up, different errors or something different in any way from what you noticed so far. If this is the case, that topic from my signature would describe your problem in more detail. If not, we need to look further.
These should be my main suspects. Try to check #2 and reply with some results.

First of all, thank you for the information. I am actually very experienced reflowing PS3 and Xbox 360's, so I will try the refrigerator experiment, and if that succeeds I will disassemble the phone and reflow it in my reflow station. I find (seriously, not joking) that a reflow and (after cooling) a good 10 minutes in the oven on "warm" gets everything nice and settled.
Do you know if they used lead-free solder in the HD2? I'm not sure if phones also fall under RoHS.

yep, i think it's lead free, can't say for sure. But by the way it reacts to heat.. it seems so.
If you try the fridge/freezer, try to get the hd2 as cold as possible while preventing any condensation occurring on it - those transparent zip bags can help, that's what i use for example.

I had the EXACT same problem for a version that I bought off from a NY store (jr.com), it was a t-mobile version, tried everything, just to return it after 8 hours of my purchase.
Looking again for buying another hd2.
EDIT: looking online for hours and hours in vain, I concluded that it was a hardware issue due to some versions of the hd2 as someone explained earlier here.

I reflowed the motherboard and the phone now works.
I think its official, the"Stick Together" screen is the new RROD / YLOD.

good to hear. my hd2 was broken in the same way as yours. fixed it the same way, works as good as new even now.
Well, at least you know what to do if it happens again

Bricked HD2 - White Screen(no logo) [NOT! SOLVED] !!

I just unbricked my HD2 from the white screen with no logo. I spent the whole day reading hunderts of post about the white screen- bricked HD2 - the solution was to change the mainboard (at least the official service did that) and the people mostly sold the phone as bricked, its maybe also an production problem with HD2 because it's caracteristic and usual for it.
I think the Radio ROM is the problem and that it's a hardware error caused by overheating(i will report if the problems occurs again but i think it works now).
How it began(STORY):
I went on a trip and used google maps and route66 with GPS/WIFI all the time. My OS was Android Nand ICS and it wasn't too hot. The first problems started with random white screen occurrences trought the day as i was using google maps so i took out the battery and restarted, it worket but soon after the white screen occurred again. The white screen occurrences became more often and at the end there was only the white screen. (people reported the the phone somtimes worked when they recharded the battery and left it alone for a few days, after that they flashed the new rom )
I used the ICS rom for a few months with no problems(same reported from other users).
One theory(i read it on the forum) that the ICS is constantly overheating the HD2 + route66 mabe it bricked because of it.
So there is no other way, it has to be an hardware problem but the good news is it can some kind of be fixed (because i think it caused an radio mailfunction) !
SOLUTION:
So this is the way how i solved it:
- I downloaded an old version of the stock HD2 WM rom(i found somewhere that it can fix the problem) so with radio.
- I extracted the .exe file with WinRAR(or 7z, winzp...) and renamed the RUU_Signed.nbh to LEOIMG.nbh
- I copied LEOIMG.nbh to my SD Card (they said it should max 4GB, and has to be FAT32)
- I entred the HSPL with Volume down + Power and it found the rom on the SD card i pressed Power to install it and it FAILED !!!!
- I was depresed again :|
- I keept reading and may owners had the same problem, someone suggested that the update worked for him after he left the phone in a bag in the fridge. I had no fridge in the hostel (and no SD card writer only the ROM on my SD card) so i tried it again AND IT WORKED !!!
After that i got a HTC screen that didn't boot. I flashed HSPL3 (also from the second try, flashing from HD2 tools(HSPL2) didn't work) and installed official WM from the HTC HD2 support and i think i will use it from now on (or WM7) .
After i did it once it didnt work(flashing from SD card) so i used this method:
- Entered the SPL/HSPL
- Flashed HSPL4 sometimes it does not work but you have to keep trying
- Task29
- Updated a stock WM6.5 from the PC !! (from the SD card didnt work(
- works
PS: If you see only the white screen when you turn it on you need to wait few days to get to the HTC seceen so a hardware error. Maybe try to put the battery and simcard out of the phone or put it in a plastic bag in a fridge ... maybe it will accelerate the process
So my theory:
- The overheading caused a hardware error that damaged the Radio ROM and the software(but how?).
- It's a producttion problem(may owners with the same problem)
- It mostly occurrs to android users - and mostly ICS
- As an engineer i have no idea why it works now but i like it

Ok i got a white screen with Windows Mobile 6.5 after few days (with android/W7 imidiently).
The problem occured when i was cooking almost 40 celsius.
Maybe the solution can be to put some cooling paste on the radio or similar thing
Cruonit said:
I just unbricked my HD2 from the white screen with no logo. I spent the whole day reading hunderts of post about the white screen- bricked HD2 - the solution was to change the mainboard (at least the official service did that) and the people mostly sold the phone as bricked, its maybe also an production problem with HD2 because it's caracteristic and usual for it.
I think the Radio ROM is the problem and that it's a hardware error caused by overheating(i will report if the problems occurs again but i think it works now).
How it began(STORY):
I went on a trip and used google maps and route66 with GPS/WIFI all the time. My OS was Android Nand ICS and it wasn't too hot. The first problems started with random white screen occurrences trought the day as i was using google maps so i took out the battery and restarted, it worket but soon after the white screen occurred again. The white screen occurrences became more often and at the end there was only the white screen. (people reported the the phone somtimes worked when they recharded the battery and left it alone for a few days, after that they flashed the new rom )
I used the ICS rom for a few months with no problems(same reported from other users).
One theory(i read it on the forum) that the ICS is constantly overheating the HD2 + route66 mabe it bricked because of it.
So there is no other way, it has to be an hardware problem but the good news is it can some kind of be fixed (because i think it caused an radio mailfunction) !
SOLUTION:
So this is the way how i solved it:
- I downloaded an old version of the stock HD2 WM rom(i found somewhere that it can fix the problem) so with radio.
- I extracted the .exe file with WinRAR(or 7z, winzp...) and renamed the RUU_Signed.nbh to LEOIMG.nbh
- I copied LEOIMG.nbh to my SD Card (they said it should max 4GB, and has to be FAT32)
- I entred the HSPL with Volume down + Power and it found the rom on the SD card i pressed Power to install it and it FAILED !!!!
- I was depresed again :|
- I keept reading and may owners had the same problem, someone suggested that the update worked for him after he left the phone in a bag in the fridge. I had no fridge in the hostel (and no SD card writer only the ROM on my SD card) so i tried it again AND IT WORKED !!!
After that i got a HTC screen that didn't boot. I flashed HSPL3 (also from the second try, flashing from HD2 tools(HSPL2) didn't work) and installed official WM from the HTC HD2 support and i think i will use it from now on (or WM7) .
So my theory:
- The overheading caused a hardware error that damaged the Radio ROM and the software(but how?).
- It's a producttion problem(may owners with the same problem)
- It mostly occurrs to android users - and mostly ICS
- As an engineer i have no idea why it works now but i like it
Click to expand...
Click to collapse

Hi, can u say which old WM version u used ? I dont have bricked hd2 but instead of this my lcd doesnt show anything in first stages of boot, i mean i cant see tricolor screen (but can get into this with buttons), cant see magldr or clk, cant see cwm or anything until android (hyperdroid) boots up. Then it works perfect. Of course even if I cant see anything it works fine in background, even more, i can go into cwm and by pressing buttons do everything but... cant see the menus (luckily got help on xda and i know menu structure). Anyway, I spoke to guy in mobile service point, who said that some time ago he had the same situation, his hd2 got exactly the same weird problem and he solved it my installing some old WM roms. Unfortunately it was long time ago and he didnt remembered versions. But he said it happened to him after playing with some 3rd party camera software and for him it was like lcd locked itself in specific resolution. I'm more than happy to try your solution if u can provide WM version u used, as i already tried few and... nothing. Thx

I used the newest version of WM 6.5 3.14 / 2.15.50.14 it worked for days(i have not used the phone but it was on without simcard). Afther few days i inserted the SIM card inside the phone and then after few minutes maybe half an hour the white screen appeard again
Now i will try the 1.66.405.2 version with 2.06.51.7 radio hope it works with the sim card or i will have a bad MP3 player

Problem still open
The phone works for days when i leave it in my room and don't use it (need to test it with a sim card).
But when i take it out in my pocket it just turns of and can't be turned on. I take the battery out and put it in and the famouse white screen appears and i can't flash it anymore (i can eneter the bootloader - voldown+power) but when i try to update the rom it hangs and restarts.
Had the same problem few times and the white screen disapears after a while(few days), the HTC logo appears and i can flash the phone again.
I have a feeling the phone is "more alive" when i use WM 6.5 old version (on android and WP7 the white screen appears after few minutes but i am not sure).
Next time(when the white screen goes away) i will try to flash WM6.5 and leave it with the simcard for a few days. If it does't go into white screen then it's a contact problem on the hardware (and it's triggered when i walk)
i tried to put it into the fridge but it did not work

i tried latest wm rom but it doesnt work, i can hear sound when its loaded but nothing on screen, pressing power off it just keeps black and then lights up display .... thats it. Weird but with android on board i works fine after boot sequence, just have to press power off 4times. Tried to load WM from SD card but for some reason I cant do it properly (heard thats only way to get rid of HSPL and have clean install), phone just hangs, maybe some error but my display is not showing anything at this point Starting installer from PC gives loads up WM rom succesfully, but as I mentioned before, screen just lights up, music is playing and ..... nothing. Maybe You can try this way ?
If not, you could try following :
using mtty do some task 2a and task29 then reinstall
or
try find someone who could plug JTAG into it and wipe everything
http://www.youtube.com/watch?v=XroEPU4qyuM
Mine is proably hardware, but why its fine on android and not with WM ?

It's definitely a hardware problem. When the whitescreen appears it can't be removed with flashing. i leave the phone for a few days off and than again the mobile phone boots without problems !
The phone works for days when i leave and don't touch it, but as soon as i put it in my pocket and wear it with me for about half an hour the screen gets white againt and the phone does't boot anymore(for days or more).
so definitely it's a circuit or component problem, I will try to fix it with hot air(to refresh the definitely or to break the pohone but i'ts my last solution)
Would a motherboard change help ?

Cruonit said:
It's definitely a hardware problem. When the whitescreen appears it can't be removed with flashing. i leave the phone for a few days off and than again the mobile phone boots without problems !
The phone works for days when i leave and don't touch it, but as soon as i put it in my pocket and wear it with me for about half an hour the screen gets white againt and the phone does't boot anymore(for days or more).
so definitely it's a circuit or component problem, I will try to fix it with hot air(to refresh the definitely or to break the pohone but i'ts my last solution)
Would a motherboard change help ?
Click to expand...
Click to collapse
Please help me, I have the same problem with my hd2 (white screen). I can not install anything on it. Tell me please, you solved the problem? Remove the battery when you leave a few days?

It just unfreezes at random. I found out that when installing windows mobile 6.5 and when it's winter that it works longer :|
For now it works when i install android it freezes after a day or two (in winter and almost imedietly in sommer)

Cruonit said:
It just unfreezes at random. I found out that when installing windows mobile 6.5 and when it's winter that it works longer :|
For now it works when i install android it freezes after a day or two (in winter and almost imedietly in sommer)
Click to expand...
Click to collapse
I haven't read your previous posts, but from your last post it seems that your motherboard is failing. A common issue with the HD2.

Marvlesz said:
I haven't read your previous posts, but from your last post it seems that your motherboard is failing. A common issue with the HD2.
Click to expand...
Click to collapse
i try to live with it Could "hot air" hack for short circuit help ? I will try it as soon as i find some one that has the "hot air" thing