yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Reflashed again with Windows Phone 7 and it works. Weird. It's a software issue for sure.
[HD2 Android Q&A, Help & Troubleshooting and Genera] deweylima:
Glad to hear it worked for you and that I am not the only one. Does seem to complicate the whole cause/effect issue however.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Yeah it's just really weird, there's obviously an issue here.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Blake001001:
Thus thread needs to be melted just like ur screen. Send it back to HTC they'll fix it if u return to factory settings
[HD2 Android Q&A, Help & Troubleshooting and Genera] nedevg:
While I don't believe for a second this could be a software issue, I think that, at least in my case, it's somehow linked to Android (my touchscreen died under Android SD). And it's the hardware buttons, much more used under Android. After 72h or so of tests with my screen being almost totally irresponsive under both WM and Android I noticed that it went dead much faster if I was using a lot the buttons. Now, this is of course a hardware problem and HTC replaced my old (and scratched plus white spotted!) screen with a brand new one.

On the other side, I have one question if it was to happen again. Is it always possible to go back to factory settings without using the touchsreen?
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Well I reflashed last night, and it worked until shortly after I woke up this morning. Argh!!!
[HD2 Android Q&A, Help & Troubleshooting and Genera] sguler:
and I tried a few time flashing my phone before sending it for repair, it didnt work for me...

interesting...
[HD2 Android Q&A, Help & Troubleshooting and Genera] Sentinel196:
I have a software and hardware engineering background and am struggling to see how this could be a software issue based upon the evidence in this thread.

More specifically, I can not understand how it could be related to flashing ROMS to NAND.

All things being equal, if you flash a rom and the touchscreen stops working, then you hash blast it (Task29), Reinstall HSPL and flash a stock ROM, EVERYTHING has been overwritten, so there cant be some corrupted code somewhere that is causing it if it still doesn't work..

A quick search on the intertubes reveals many many people running stock roms with exactly the same issues.

It is certainly possible that a bad flash could cause the touchscreen not to work, but erasing all of the NAND memory and then re flashing it would absolutely, unequivocally fix it every single time if this were the case.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
So why does reflashing WP7 (haven't tested Android yet) fix the problem? I have an engineering background as well, that doesn't mean anything.
[HD2 Android Q&A, Help & Troubleshooting and Genera] mickfarr:
Reflashing doesn't fix the problem, you've just proved that in your previous post.

It's a bit like how my dad used to fix the tv. A couple of bangs with his hand and the reception would be fine, till the next morning. A couple more bangs and it was working again. Eventually we had to get a new TV! :D
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Well I reflashed again and it still works...
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
Read my posts to see it is software related (at least for me).

Flash MAGLDR, and screen goes crazy.

Flash anything, and screen is stable and precise again.

The MAGLDR problem can take an hour to really show up, but it's present at least slightly immediately.

Flashing to anything other than MAGLDR and it instantly fixes the problem.

Seems to me, that proves it's a software issue.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Yup. Agreed.
[HD2 Android Q&A, Help & Troubleshooting and Genera] mickfarr:
That's what my dad used to say, "give the tv another bang" and it worked. Unfortunatly the tv died. RIP TV. :(

It's already on its way out and it will need replacing.

Why don't you record the problems you have and show your solution, then post it up on youtube. A video is worth a thousand words, thats what my dad used to say :D
[HD2 Android Q&A, Help & Troubleshooting and Genera] adibis:
Unfortunately I have been on the receiving end of this a lot by HP. A lot of things failed in my nx6110 laptop. DVD drive, Hard drive, motherboard. A lot of times (no lemon laws in India).

HP said it's Linux and could never explain how. Finally they released a new version of BIOS that fixed issues.

If the companies themselves believe - try to make us believe that it's the software - times are bad.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Why do I need to make a video of me reflashing? There's tons of those videos already posted.
[HD2 Android Q&A, Help & Troubleshooting and Genera] mickfarr:
I said to record the problem you are having including proof that reflashing fixes your problem. It should be very easy to do, yes?
[HD2 Android Q&A, Help & Troubleshooting and Genera] xs11e:
Most likely a hardware issue.

If I can weigh in on this.... I don't know about the OP but when I flash I use the USB cable to do so and using the USB cable can cause an overheating problem with the battery which DOES affect the touch screen.

I suspect the overheating is caused by the USB ports allowing a higher initial current than the standard wall charger allows and it's particularly noticeable with a very low battery. I've noticed my phone getting pretty hot when connected to the USB ports and I actually caused a couple of smaller batteries to swell up and die in the past.

To avoid problems I'd use the supplied wall charger to charge my battery to 50% or better before connecting the phone to a USB port.

NOTE: The above is with multiple phones and several different computers so it's not a phone or a USB fault, it's apparently the design of the current limiting regulation in USB vs wall charger or at least that's my best guess?
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Don't believe me? Oh well, I shared a success story. If people need video proof, they're obviously too lazy to reflash.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
I don't think heat has anything to do with this. Think about how hot tablets get...
[HD2 Android Q&A, Help & Troubleshooting and Genera] trill12:
Well, I got my HD2 back with the new screen and flashed an SD build. Not a single issue. Not going back to NAND until this issue is looked over.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Good thinking.
[HD2 Android Q&A, Help & Troubleshooting and Genera] StephanV:
How is that? Wall charger has an output of 1000mA, USB ports typically have a (I believe hardware) limited output of somewhere between 500 and 700mA. I suppose there are exceptions, but more than 1000mA seems highly unlikely to me - assuming no one here already has USB3.0 ports.

Question for everyone having this problem: have you flashed a lot of ROMs before having the defect, or was it after one of the first? I really do mean flashing, SD builds don't count, WinMo and Android NAND Roms do.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
I've flashed a number of times. At least 6-10. Windows Phone 7 seems to be the most stable to be honest.
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
I had flashed a few WinMo builds. Then I flashed a basic one to run Android SD. I didn't flash for months. Flashed MAGLDR and noticed problem. Flashed back WinMo and problem gone. Flash MAGLDR, and it's back. Flash WinMo, and it's gone.

The only way I can get the problem to occur is if I use MAGLDR.
[HD2 Android Q&A, Help & Troubleshooting and Genera] xs11e:
Nothing to do with total current output, it's how the current output is limited with a badly discharged battery.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Essenar:
I don't understand how so many people here can claim to work in IT and not live by this saying:

"If it's broken after you do something, whatever you did broke it."

If I open up a PC and install a new ram stick and it won't post, obviously installing the ram stick broke it.

Now, what is causing it to not like the new ram stick is an entirely different question to answer that has many different responses. But did installing the ram prevent the computer from posting? Absolutely.

Does flashing Android to NAND cause an HD2 screen to go wonky? Yes. That's been proven here by everyone.

Is it the Android rom causing the problem? That's a different question to answer. It could be that the screen is already defective and Android NAND triggers the stress required to show the screen as being defective. That's one possibility. It could be that the screen operates fine with 65k color versus th emuch larger color spectrum of an Android build. Could be that the phone was plugged into the charger while flashing to NAND.

But at the end of the day, flashing Android to NAND was what led to the screen not working and something else is the reason WHY the screen isn't working.
[HD2 Android Q&A, Help & Troubleshooting and Genera] StephanV:
I'm trying my best but I'm really not following you. What do you mean with that limitation?
[HD2 Android Q&A, Help & Troubleshooting and Genera] StephanV:
I agree with everything you said except for this. It's not the screen which is broken, but the digitizer, so I don't see the color depth being relevant.

My thoughts exactly!
[HD2 Android Q&A, Help & Troubleshooting and Genera] mickfarr:
It could help Cottulla and the DFT to find and fix the problem but if you wont help them why would they bother helping you?

I don't understand why you would refuse to do this? :confused:
[HD2 Android Q&A, Help & Troubleshooting and Genera] deweylima:
I agree with your entire post but especially with the part above.

That is exactly what happened to me on two separate occasions. I flashed dozens of times before and even a couple of times afterward.

Something in this process triggered this effect. Clearly, it happens very rarely and in my case, only twice.

Maybe it is an indication that my screen is on the way out. Maybe not.

My touchscreen worked flawlessly before it happened and it has worked flawlessly once it came back to life on both occasions.

I am not blaming anyone or anything for this. In fact, I will continue to flash. It is a risk we all take. But hopefully, this discussion will help pinpoint the reason so that others can benefit.
[HD2 Android Q&A, Help & Troubleshooting and Genera] tally_pj:
I flashed a kumar rom a few months back, and right after flashing the screen would keep waking up randomly killing my battery. I asked about it and everyone said it was a hardware problem to do with the pins where you plug in the usb cord. I could see it looked like a hardware problem, but strange it started right after messing with the software. So i played with it for a few weeks, task 29, new rom, stock rom, ect. Then one of the new roms i flashed on the phone , it just stoped, and phone was back to normal. So if it was a hardware problem how could it just fix itself? I was thinking maybe some software is causing problems with how the hardware runs, but then why didnt it fix the problem right after i changed the first rom? Hardware, software, hardware, software. I just dont know lol. But Im running android nand with no problems now :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] saap:
hi guys

How many people have this problem?
[HD2 Android Q&A, Help & Troubleshooting and Genera] hd2life:
Mine just died today,maybe there is something in here. She was the best phone I ever had i will miss you my love:(. I say chaps we should do something about this NAND guy, am geting ma gun are ya with me :mad::mad:.
[HD2 Android Q&A, Help & Troubleshooting and Genera] double_ofour:
So what's the symptoms? also the touchscreen inacurate also? or the whole device just died?..
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Started with inaccuracy.

But for all you bandwagoners who think it's a hardware issue, I just had the unresponsive touch screen again...reflashed, and it's fixed. IT IS A SOFTWARE ISSUE!!!
[HD2 Android Q&A, Help & Troubleshooting and Genera] double_ofour:
Can you tell us what OS/firmware/SPL/HSPL/Radio are you at before you flashed a ROM that started an inacuracy? also what ROM did it broko? and lastly what ROM did you flashed to make it fixed?
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
The issue started with the Pure Gingerbread v6 NAND Android ROM. Using Radio 2.15, 2.08 HSPL and 1.11 MAGLDR. Flashing Windows Phone 7 fixes it for 12-24 hours until it seems to stop again. Reflashing almost always fixes it on the first try. If the first try fails, the second one works.
[HD2 Android Q&A, Help & Troubleshooting and Genera] double_ofour:
hhmm.. flashing back to WM6.5 or any Android NAND or SD can't solve the problem which is I already did, but didnt even tried the WM7 yet.. Somewhere in this thread said that flashing WM7 did restored the accuracy of their screen, but it would'nt take long to snap again..

so bro, as you said that it fixes it for 12-24 hours, does that 12-24 hours you flashed android? or you stay in WM7 and it snaps the screen again?..
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Haven't tried Android yet, like I said... I'm kind of hesitant to at this point.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Metastable:
Here to debunk that NAND flashing is the reason your screen dies. I had the same issue back when Android only ran off your SD and there was a post in the old T-Mobile specific forums along with many others saying they had issues and never touched Android.

The issue isn't related to NAND builds. FYI I only breezed through this thread.

-Metastable
[HD2 Android Q&A, Help & Troubleshooting and Genera] double_ofour:
so what you're saying is, the screen broke again while you're in WM7?.. how sad..

Im planning to put my HD2 under repair, as far as i know they will just replace my digitizer. If that happens and it fixes the inacuracy, i too would be hesitant to install another ROM again as it would may happen again..
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
K, so this is one case of the touch screen dying. No one else thus far has had this happen as far as I know.

Have you read anything I've posted? I said I haven't tried Android since the screen stopped working right. Go back a few posts, and re-read what I said.
[HD2 Android Q&A, Help & Troubleshooting and Genera] double_ofour:
i didnt ask you again if you flashed android again and it did broke your screen, re read my post again
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
I said nothing near to "my screen broke the first time while in WP7." The issue is unrelated to WP7.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Just flashed Android 2.3 (Gingerbread). On the default launcher, the two bottom left circles are highlighted orange as if someone was pressing/holding them. When I hold the end button to power off, the first option is highlighted.

Dunno...
[HD2 Android Q&A, Help & Troubleshooting and Genera] deweylima:
Agentfazexx,

that is exactly the issue I had. The two bottom left circles were highlighted orange just as if someone was pressing them just like you describe.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Yep. Weird issue.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Unconn:
Just the opposite. The wall chargers are normally 1amp or 1000ma. Almost all USB ports only do .5amp or 500ma.
[HD2 Android Q&A, Help & Troubleshooting and Genera] saap:
AngelDeath

+1 :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] mickfarr:
AngelDeath

+2 :D

The HTC HD2 has been having touch screen problems long before NAND as have other HTC models.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RayHeath:
Now my turn. I´ve taken time and read this whole thread. I do definately agree with AngelDeath. I´ve had a HD2 since it first came out. Then in October after flashing a Win6.5.x ROM I started having problems. Before then my screen would also hesitate and the calibration wasn´t always exact. I then sent it in for repair and ended up receiving a completly new HD2. Since then I´ve probably flashed 50x Win6.5.x, Android, and several time WP7. Never a problem. I do have a European HD2.

Now, sometimes if flashing a Nand and using a SD-card, the HD2 might need time to settle down, a couple of re-boots. That´s the process when flashing a nand or any ROM. Give it time to install all apps and it should work pretty well.

It is definately not just an Android nand that causes problems. I´ve tried every single Nand-ROM on this sight untill I found my favorite one "Droid Core". Now after using it for several days, it very smooth and fast.

As far as overheating, try not to use it when you´re charging it. If you do have it hooked to USB to flash, when it´s finished flashing disconnect it from USB and let it boot normally.

By the way, I am also IT, been so for over 20+ yrs. Hard- and Software. I think that when we do all work together, we can solve any problems.

Thanks DEVS.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Seems like if reflashing doesn't fix it, rebooting until it works fixes it, temporarily of course.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RayHeath:
Which ROM are you trying to flash?
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
WP7 has been the only working one so far, and that doesn't work 100% of the time.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RayHeath:
I did try WP7, but ended up going back to Android-Nand. What exactly happens with your HD2? Is it just the screen, hesitation, calibration, boot?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Johev:
Did you try the flashaholic tool? It will do a task29 to your phone before you flash something.

I use it even before I flash Android NAND or WP7 on the phone, just to be sure it is clean and ready.

If you try it with lets say NAND Android, just do this:

1) Ensure that you have HSPL on your phone

2) Run the flashaholic tool and format the phone (after the format (aka Task29) is done you can quit the program as you no longer need it).

3) Boot the phone in bootloader and install magldr 1.12 (or the newest release when it comes out)

4) Boot into Magldr and run the Android flasher.

5) Good luck and lots of pacience.

Tell me if this worked?
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
The screen is either working, or not. No calibration issues.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RayHeath:
When does this happen? During unlock?
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Yup, or bootup, right when it boots into the OS.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RayHeath:
Are you using SD-Card?
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
No, I said I was using NAND a few posts back, and plus WP7 doesn't run off SD.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RayHeath:
If you have a SD-Card in your phone then it will be formatted by WP7. Even if you have a card in your phone, it is still a nand. Just like the nand Android. It uses the system and card. Did you try a Task 29 before you flashed WP7? Each time I flashed a new Nand (WP7 or Android) I made sure that everything was formatted with Task 29 and my card completely formatted.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Never did task 29. Does this overwrite MAGLDR?
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Nevermind, did task 29 and put back on the stock ROM, and it isn't fixed.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Scratch that, now it works...

So does task 29 drop me back to 2.08 radio, and remove HSPL?
[HD2 Android Q&A, Help & Troubleshooting and Genera] RayHeath:
It will overwrite everything. You don´t need to worry about that, you can install everything once again, but I think that your HD2 will work a lot smoother when you do the Task 29, then install everything from scratch. I know it´s a pain, but that´s why we experiment with all of the ROMs. You will have to unlock you WP7 with the Chevron7 again and do all of the steps that are described, but it´s well worth it.

I went back to Android because it´s a lot easier if you want apps or anything else, plus with "HD2 CoreDroid DHD V1" Rom I have the eye candy and everthing else I need. The WP7 is for me too new to use it everyday, where as with this Android I have a nice screen and more tweaking possibilities. If you do decide to install CoreDroid, please read his thread in detail. You can always ask me anything that you need to know.:D
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
See above post, seems to have fixed it...I'll keep testing it on stock ROM before going to WP7...
[HD2 Android Q&A, Help & Troubleshooting and Genera] RayHeath:
Task 29 does not change your Radio or HSPL.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Oh, those are more on the firmware side, right?
[HD2 Android Q&A, Help & Troubleshooting and Genera] RayHeath:
Yep, I also use the same radio. Never had a problem. Hope I was able to help.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Thanks. So far so good on task 29/stock ROM...
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Well, guess I spoke too soon. Screen is doing the same thing...already. Not as bad, but still...it's unresponsive here and there.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RayHeath:
Feel free to try a Nand. You see that everything will work out fine.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
I've been using that...
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Flashed WP7 NAND again, issue is back in full force...NAND does seem to be the problem.
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
That's what I keep telling people, but no one is listening. They keep thinking it's the screen being faulty no matter what.

The problem only exists for me when using MAGLDR (ie, a NAND build). In all other builds, the screen works perfectly.

:mad:
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Maybe it's MAGLDR 1.12...

Too bad 1.11 doesn't work with WP7... Argh!
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Blah, nevermind. Flashed magldr 1.11 and Android, same issue...
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Dammit, back to stock and it's still hosed...
[HD2 Android Q&A, Help & Troubleshooting and Genera] hd2life:
Just out of curiosity did this ever happened to someone using stock roms only? Maybe its HSPL issue, has anyone tried reverting to stock spl?
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
It's not HSPL related. It never caused issues before...this is kind of out of the blue.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
I'm also trying to flash different radio's to see if that fixes it. So far, 2.14 hasn't fixed it. I have 2.12 installing, and 2.10 downloading. Here's to hoping...
[HD2 Android Q&A, Help & Troubleshooting and Genera] AngelDeath:
Just an fyi for anyone that doesnt know, if you want to put the phone back to "True" factory default, take the nbh file from an official rom, and place it on your sd cards root, then turn the phone on, the phone will be erased and also HSPL will be removed, and the stock rom will be back in place along with the radio that comes with that rom, then you can HSPL after again if you want, but this way you'll be back to stock.
[HD2 Android Q&A, Help & Troubleshooting and Genera] hd2life:
To what do you need to rename nbh file? I cant get it to work.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
You know...the forum does have a search feature...