Related
Would appreciate your help on the following issue (amoled display):
- phone doesnt boot up, it is stuck to a screen showing htc in the middle and 4 small triangles in the corners; if I unplug the pc cable it goes to a RUU menu
- no access to recovery or bootloader menus (by holding power + vol down/back)
- installing stock RUUs dont work; there is a 110 error saying that the RUU is not complete (tried 5-6 RUUs, both 2.1 and 2.2). there is a progress bar on the phone's screen that is normally green, but turns red when the radio is being written (as per the install wizard on the pc) and there is another triangle showing up at the end of the progress bar
- fastboot oem boot restarts the phone, but then it gets stuck to the white screen having htc in the middle (like when you start up the phone and after this quietly brilliant shows under htc, for me it doesnt go beyond this initial point)
- fastboot reboot-bootloader restarts the phone into the same 4triangles screen with htc in the middle
- adb doesnt work as it doesnt show my device
- any power + vol down/back combination brings the phone to the 4triangles screen
- if I run the stock RUU after fastboot oem boot (white screen with htc in the middle) there is a menu showing up on top of the white screen showing up the progress (1-bootloader, 2-radio_v2, 3-radio, then system, recovery, user data, etc.); bootloader is updated ok but then it gets stuck when updating radio_v2 and doesnt move further from that point)
- after the RUU install fails, I plug out the pc cable and see the RUU menu; depending on the RUU that I try to flash the hboot version changes up and even goes down after, but the firmware (what the RUU installer "sees" on the phone) and radio (seen on the RUU menu) remains the same: 1.21.405.1 and 4.06xx; the date on the RUU menu also changes depending on the RUU that I try to flash
Any suggestions to get my desire unbricked?
Bit of a background to the problem:
- rooted (unlockr) and was having Paul's r3 rom (2.1)
- updated the radio to 5.10xx
- got into silly restarts when using gps and thought to reflash a new rom and went for Paul's r8
- restarts were there also when using the phone normally
- thought to re-do all the rooting, wiping out everything from the phone, etc; so having r8 as the rom (pre-baked version) I started the rooting process with creating again the goldcard, etc etc
- error message at some point saying partition update fail (following the steps from theunlockr as I did the first time when rooting) and then the phone got to this triangles screen with htc in the middle
- strange though that this screen is different than the one when I first rooted when there was just one big triangle in the middle
Thanks a ton guys!
I've seen a few posts about this screen with the 4 triangles, but never seen the result of any potential fixes, or if it was ever actually fixed.
Just an idea, but it was maybe a bad radio flash if you are saying it started playing up after that? Unfortunately a bad radio flash is fairly terminal so I hope that's not your problem.
Good luck with this one and if you get it fixed then post the result here if you don't mind!
Will definitely post the solution when found; so far though nobody has any thoughts around what might be the reason behind this problem and how to get around it. I dropped a few PMs to the people that had this problem in the past and contacted Paul at Modaco, but so far no replies...
You can fix this with an RUU, I've had the same issue when I unplugged too early after flashing, but you are asking for help in the wrong section.
thought that the dev's section is where the best knowledge exists...
about the RUU process, I am trying to flash stock RUU.exe files, but there is a problem when the radio is being written and then I get a 110 error from the RUU install wizard saying that the RUU is incomplete.
for you the RUU install worked smoothly?
If you get a write error during an RUU flash (i.e. while the flashing is taking place, not before) it probably means there's a hardware fault.
Could be hardware, but I find it hard to believe as the phone is new and it is network locked, hence I didnt even use it for real, apart from some wifi and gps activities. Besides, the phone worked very well when I first rooted with Paul's r3 and the whole mess with restarts when using gps started after I upgraded the radio to 5.10xx having a 2.1 OS.
I feel that the problem started when I tried to root the phone being on Paul's r8 2.2 OS (tried to root with a 2.1 system and then it got messed up in the process).
I am not saying that it is not hardware as it is a possibility, but still think that it might be a messy software aspect, as if the radio is messed up from a hardware perspective, then at least the system should boot up and then wifi, gps, gsm and the things that are controlled by the radio shouldnt work...but somehow the OS should start-up.
Basically I dont get a write error, it's just that the error comes up when the radio is being written, hence I think that there is something wrong with the radio set-up that I have now on the phone...
Maybe somebody knows how to flash the system from scratch using only fastboot in cmd (having the right zip or img files properly signed), or maybe just the radio to start with.
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
acolwill said:
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
Click to expand...
Click to collapse
Well, I thought that as various solutions to root the phone, to get past different restrictions in the OS, etc. were discussed here, it might be a good thing to develop a way to bring back to life a OS being in this situation like mine...come on...
mariosraptor said:
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
Click to expand...
Click to collapse
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
but to get adb you need to download and install android sdk. look here http://developer.android.com/sdk/index.html system dependands download.
install it here are instructions on how to use if you aren't familiar with.
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
for anything else just use google.
i'm pretty sure that your device is fixable and you can fix it without any service center. cheers and post what ever happens.
popepope said:
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
Click to expand...
Click to collapse
I know how to use adb commands...pretty new to android and everything, but lately I roamed a lot through various things about it and learned a lot.
The problem is that adb doesnt list my phone when I run adb devices, it shows only when I run fastboot devices, I am sure you know what I mean...hence I cannot push any files to the phone, etc., at least not using adb in cmd.
That's actually the problem, that I cannot get adb to work, I only have fastboot commands. At least the way I see it now the question is how can I work with the phone to fix it just by having fastboot access in cmd.
I searched quite a lot various forums, etc, but I never came across a solution that will get things going just by having fastboot in cmd (without adb working). Maybe somebody here will come up with some magic trick...
Nerten said:
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
Click to expand...
Click to collapse
How did you end up having this problem, just like that or after some update, flash, etc?
Thanks!
have a look here mate http://forum.androidcentral.com/htc...9-bricked-my-evo-but-there-away-un-brick.html
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
sorry idf i don't underdstand, but if you have fastboot working in your device and sdcard also then you should be able to push files to device via fastboot making as clean installs as possible.so if your device is picked up by command line type fastboot to see command list. i'am a bit comfused. pretty sure you should fix it through fastboot though.
popepope said:
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
Click to expand...
Click to collapse
right, I can run 2 things with fastboot in cmd: (name of the files just an example)
1. fastboot update update.zip
here I get that the archive doesnt contain android-info.txt or android-product.txt
2. fastboot flash update.img
here i get signature verify fail
for example, fastboot erase radio says FAILED, remote: not allowed
there are some fastboot commands related to the kernel and some others, but dont know how to make use of them for my problem.
sd card is accesible for sure and it is a goldcard.
I saw some linux/ubuntu methods to simulate adb usage in cmd, but I dont think it will work...will try to find an ubuntu image and mount it under windows, but dont have time now...
anyways, thanks to everybody for the suggestions and interest, maybe we'll crack it some day
You need to use an official RUU zip image - i.e. a PB99IMG.zip. Not an update.zip.
Hi all. I have a HTC Desire rooted with unrevoked3. Phone runs sweet as except bluetooth. I can enable bluetooth graphically (the checkbox ticks and after some time the bluetooth logo appears on the status bar). However, if I cannot chance the device name, make the device discoverable or scan for devices. Nothing happens.
The kernel gives errors such as:
Code:
<3>[ 71.632263] hci_cmd_task: hci0 command tx timeout
I am currently running CyanogenMod 7.1 RC1, but this problem exists if I run other ROMs too. I've gone back to the HTC RUU to verify it's not hardware and bluetooth works fine there. So I dug about some more.
There are many posts relating to bluetooth problems on rooted Desires, but none appear to be line mine - Still, I tried some recommended solutions anyway. The issue of a 'USB brick' sounded a possible cause, but I followed through the solution (http://forum.xda-developers.com/showthread.php?t=691639) and got no further. I am sceptical as to if I modified the misc.img file correctly, as I don't know how to find my current ROM version (it's not under About The Phone).
I would really appreciate any help. I've been nosing about looking in '/sys/devices/virtual/bluetooth/hci0/' were the bluetooth stuff resides. See here: http://forum.cyanogenmod.com/topic/23500-bluetooth-lack-of-functionality/#entry217041 But this isn't just a Cyanogen problem. The only way I can restore bluetooth functionality is by letting HBOOT re-flash from PB99IMG.
I am not an expert in this, but I have read quite a lot and have a good idea of what's going on, but this has stumped me. I am very fluent in Linux. Any help you can give would be greatly received.
EDIT:
I notice that from the stock HTC ROM, I can root the device with unrevoked3 and Bluetooth still works. Then as soon as I do anything with ClockworkMod (version 2.5.0.7) it appears to break Bluetooth.
I dumped the misc partition from the stock HTC ROM while Bluetooth was working, and tried to reflash that to the misc partition once Bluetooth broke in Cyanogen - It didn't work: using flash_image on the rooted phone, it appears to work... it doesn't actively fail... it doesn't say anything, just returns (exit 0). Using fastboot flash misc mtd0.img results in checksum errors, etc and does actively fail.
Any advice would be greatly received please?!
Kind Regards,
George Smart.
so i sucessfully rooted my DZ but i have a problem with my computer now after i rooted, i have a fair idea of what caused the problem but dont know how to fix it.
CMD commands dont work on my computer (like ipconfig and ping etc) giving an error that "ip config" isnt a recognized as an internal or external command.
i think the issue is due to changing the "Enviroment Variables > Path" on my computer as it was in the guide i was following to make things easier, i removed the default path and replaced it with what i have now being
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\PROGRAMS\Other\HTC\SDK\platform-tools;C:\PROGRAMS\Other\HTC\SDK\tools;C:\Program Files\Windows Live\Shared
however i think there may be a command i deleted that i need.
if anyone has any suggestions please post your advice
thanks in advanced Penfold
Add this to it:
%SystemRoot%\system32;%SystemRoot%;
-Nipqer
Ouch, yeah ... what Nipqer said will fix the cmd problem but if there were any other paths set up by other applications you might run into more problems down the line. The guide wasn't stating to replace the paths but to add to them by adding '; c:\new_path\'.
You might just want to roll back with System Restore if there's a very recent one and then readd the adb path properly.
Sent from my HTC Vision using XDA App
Good Idea with system restore.
Looking at my Path the only other ones neccesary are possibly nvidia drivers.
-Nipqer
ok will do, so i dont have to make a new topic ill ask here...
does any1 know of any app that can give me notifications via the LED light.
ive tried LED me know but i dont think that works (the notification is always the same no matter what option you try)
I tried LED me know without any success on my G2. I currently use MIUI and LED notifications work for all apps.
Sent from my HTC Desire Z using XDA App
I have searched through many microphone issue threads and none seem to help. I have a T-mobile htc g2 which has been unlocked and using my AT&T SIM Card. The phone works perfectly, except no one can hear me during phone calls. The voice search app works perfectly -text,navigation, etc. (so it should not be a hardware problem) which leads to a software problem. I have factory reset the phone several times, but it doesn't fix the problem. I have tried to flash ROM the phone, but I cannot get the phone to ROOT. I have tried Visonary (which failed since I have Android 2.3.4) and the xda wiki page, but my phone is not recognized by HTC Sync or adb.
Either way, I need help figuring out if I can ever fix the microphone issue this phone has. If there is another way to install a ROM, please let me know. I have been trying for days to get my phone rooted.
For more information:
I have tried both versions 3.2.20 and 3.0.5551 of HTC Sync (and neither worked). I've restarted my computer and the phone, turned off antivirus, followed HTC instructions; but nothing worked.
When trying adb, in the command prompt after typing "adb devices" I received this message: " 'adb' is not recognized as a internal or external command, operable program or batch file " To my knowledge I followed all the previous steps correctly, although I have windows 7 and not vista (but I still got to the same properties).
Anyway, please help me with any information.
UPDATE:
I finally rooted and downgraded the phone to 2.2 Android and then flashed a sense 2.0 ROM (although it was force closing applications), but it did not fix the microphone issue. People still cannot hear me during phone calls. So it seems that this must be a hardware problem, but if the mic works for some applications, is it the microphone that is broken? Or could it be something else?
Right now my phone is still in 2.2 Android since I may be flashing the Sense 3.0 ROM soon. But does anyone know what the problem could be and how to fix it?
if adb is not recognized then you are not pointed to it. you need to either
change directories in cmd and point it to the folder adb is in
or
change the path in system variables so when you type "adb" into cmd it will always find the path no matter where you are directing it
or if these steps are above your head,
open the folder adb.exe is located, hold shift and right click in the folder - then choose open command here
once in cmd, type
adb devices
if your phone is plugged in, debugging turned on, proper drivers installed you will see a serial number, that's good - continue
if you see waiting for device, then adb.exe is now working but your phone isn't being detected
if you get the same error as before you need to one of the other ways I mentioned
Sent from my HTC Vision using xda premium
demkantor said:
if adb is not recognized then you are not pointed to it. you need to either
change directories in cmd and point it to the folder adb is in
or
change the path in system variables so when you type "adb" into cmd it will always find the path no matter where you are directing it
or if these steps are above your head,
open the folder adb.exe is located, hold shift and right click in the folder - then choose open command here
once in cmd, type
adb devices
if your phone is plugged in, debugging turned on, proper drivers installed you will see a serial number, that's good - continue
if you see waiting for device, then adb.exe is now working but your phone isn't being detected
if you get the same error as before you need to one of the other ways I mentioned
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
That worked perfectly and I guess my phone is seen by adb. However, I realized the link of the xda wiki for the clockwork recovery is not working. I am trying to find another download link, but does anyone know where else you can download the clockwork recovery for htc g2?
go to the cyanogen wiki (just google it)
but I would recommend 4ext recovery, (you can google this too) it far nicer than clockwork for the vision
on a side note, find strawmetal's guide to rooting, its in pdf format and also has all the downloads needed
Sent from my HTC Vision using xda premium
demkantor said:
go to the cyanogen wiki (just google it)
but I would recommend 4ext recovery, (you can google this too) it far nicer than clockwork for the vision
on a side note, find strawmetal's guide to rooting, its in pdf format and also has all the downloads needed
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank you. I will try to strawmetal's guide first since the xda isn't working for me right now.
That Strawmetal's guide worked wonderfully! I finally rooted and downgraded the phone to 2.2 Android and then flashed a sense 2.0 ROM (although it was force closing applications), but it did not fix the microphone issue. People still cannot hear me during phone calls. So it seems that this must be a hardware problem, but if the mic works for some applications, is it the microphone that is broken? Or could it be something else?
the mic is part of the main flex cable, it is possible it cuts in and out because the flex is going bad and the mic is fine.
either way sounds like the only fix will be to replace your flex about 35~40 on ebay and 30~60min depending on how novice/pro you are
Sent from my HTC Vision using xda premium
demkantor said:
the mic is part of the main flex cable, it is possible it cuts in and out because the flex is going bad and the mic is fine.
either way sounds like the only fix will be to replace your flex about 35~40 on ebay and 30~60min depending on how novice/pro you are
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank you for your advice. I flashed the Virtuous Unity ROM and it fixed the microphone, somehow. However, if it shuts off (I pray it wont) I will try to see if replacing that will make a difference.
Mic Not Working in Calls Only
nds623 said:
Thank you for your advice. I flashed the Virtuous Unity ROM and it fixed the microphone, somehow. However, if it shuts off (I pray it wont) I will try to see if replacing that will make a difference.
Click to expand...
Click to collapse
I have qmobile noir a10 which is same as micromax a110.. From few days i have got this mic problem in voice calls. I can hear voice of ppl calling me but they cant hear me.. while microphone is working quite fine in sound recorder application.. i flashed custom ROMS but no success yet.. Plz help me!!
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse
nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).