Hi you clever people, I wonder if anyone had any ideas or pointers please. I've been on an older Eragon for some time and decided to update the other day, went to Eragon 9.9 and afterward touch screen was inoperative. Power button seems to respond with a delay also. It's complaining about anti-theft too (I had set that up a long time ago and can't get rid). Anyway I can get into recovery no problem (Philz) done every reset you can imagine and no improvement. Used the flashtool and original rom and the fault is still apparent so I'm stuck now. Is this destined for the bin?
Thanks for reading.
Regards
J
Related
Hi all
I have a strange problem in that my device started constantly rebooting with a Vodafone ROM that I have been using for the last 2 years. I left it alone for a couple of days I was then able to get it to stay on long enough for a hard reset which just made the device hang at the splash screen.
I read about this problem here and reflashed with a WM6 ROM via the bootloader method all was well for about 3hrs, great I thought feeling really pleased with my efforts.
It wasn't to last as the device has started rebooting again!!!!!!!!!!!!!
My question is would this problem be hardware or software related. Would upgrading the bootloader make any difference it currently has V1 and how do I know if the device is a G3 or G4?
Thanks for your time.
Having an issue with my HOX today. It was in my pocket all day at work, pulled it out to make a phone call and afterwards when I went to hang up, the screen would not turn back on. It is still responsive to touch input and I can still unlock while the screen is black, but it still does not turn on. I can however hard restart it and the screen comes back on and I can still enter fastboot/recovery. But if I let the phone stand-by the issue repeats itself. I was on BinDroid v2 without any kernel when this happened, I got the phone into recovery and flashed both Energy and franco.Kernel and this issue is still happening. Is my best option to try and flash the original RUU and a stock rom?
I've had this issue since flashing the bricked kernel. I think the best option would be to go back to stock.
Sent from my HTC One X using XDA
i have the same problem but in my case the phone is just suck at a black screen. am not able to do anything at all, am just sitting now waiting for my battery to die so that i may be able to reboot it. if you any suggestions to solve this, please do tell as i am in a dire situation.
Can't you restart the phone by holding the power button in?
If not then that's a strange one.
Sent from my HTC One X using XDA
IPS1989 said:
i have the same problem but in my case the phone is just suck at a black screen. am not able to do anything at all, am just sitting now waiting for my battery to die so that i may be able to reboot it. if you any suggestions to solve this, please do tell as i am in a dire situation.
Click to expand...
Click to collapse
This is what I'm doing as well. I tried using a nandroid to go back to stock and that still doesn't work. It's almost impossible to get the phone into the bootloader but it's do able. One thing I'm noticing though, is that if the screen does manage to turn on when I boot it up, it wants to send an error report to HTC about it. Also, once the screen goes off and won't come back on, it's very laggy to other inputs. Example, pressing the power like you want to wake it and then pressing to volume keys has a very noticeable delay.
Thankfully, HTC is already doing a warranty call on it for the yellow spots on my screen (now like dark orange spots now)
Update: HTC said that the screen issue I'm having is unlikely able to be fixed by a software repair and that I have to send it in for a repair. 7-10 business days.... great.
Also with an untouched phone
Guys, I am afraid this is a hardware problem. My phone is UNROOTED with the last upgrade and I am having the same issue.
Take it back to the assistance. OOPS, you rooted it ;-)
lisophorm said:
Guys, I am afraid this is a hardware problem. My phone is UNROOTED with the last upgrade and I am having the same issue.
Take it back to the assistance. OOPS, you rooted it
Click to expand...
Click to collapse
Hi.. I'm also facing the same issue ... however this didn't start till few days ago. I have had this phone for six months now and was on stock most of the times.
But since this week , I started getting issues where once the screen goes black , it doesn't come back on. Although , I can reboot the phone with long press power button and also go back to bootloader/recovery without any issues.
Can u confirm its the hardware issue ? If yes, did the techinicians told you anything about what is causing this and it can be corrected easily ? I want to try my hands on it before going to customer care as I have void my warranty and will have to pay for repairs.
Cheers !
its kernels issue.
you should flash orginal kernel or flash a rom with irginal kernel to fix this issue.
Sent from my HTC One X using Tapatalk 2
shadow fiend said:
its kernels issue.
you should flash orginal kernel or flash a rom with irginal kernel to fix this issue.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
First time I started facing the issue, I was on stock 4.0.4 rom with stock kernels unrooted and locked bootloader.
So not sure if the issue was related to kernel. Anyways I'l try to get stock kernel and use it.
Cheers
OK.. so I did tried to get the stock 4.0.4 rom with stock kerne but same issue.
Also in the meanwhile I tried all other prominent HOX roms , bot AOSP and sense.
I have found that the issue is more severe and frequent on Sense roms (confirmed on all JB roms Ondroid, Maximus and ADHD as well as VenomX) but its very much stable on AOKP ICJ and CM10 roms. However still sometimes screen doesn't come on in ICJ too.
Now I'm starting to think there might be some issue with HBoot 1.28. My CID is 001 so there shouldn't be any issue, but if I remember correctly when I installed the Hboot, there was a 'Failed' message , but the process did completed.
Should I try to again flash Hboot 1.28 as I can't apparantely go back to older ones ? anything else I should try.
I'd really like to hear from some ppl who have faced this issue and mentioned in posts above on how they managed to solve it.
Cheerio
dev997 said:
OK.. so I did tried to get the stock 4.0.4 rom with stock kerne but same issue.
Also in the meanwhile I tried all other prominent HOX roms , bot AOSP and sense.
I have found that the issue is more severe and frequent on Sense roms (confirmed on all JB roms Ondroid, Maximus and ADHD as well as VenomX) but its very much stable on AOKP ICJ and CM10 roms. However still sometimes screen doesn't come on in ICJ too.
Now I'm starting to think there might be some issue with HBoot 1.28. My CID is 001 so there shouldn't be any issue, but if I remember correctly when I installed the Hboot, there was a 'Failed' message , but the process did completed.
Should I try to again flash Hboot 1.28 as I can't apparantely go back to older ones ? anything else I should try.
I'd really like to hear from some ppl who have faced this issue and mentioned in posts above on how they managed to solve it.
Cheerio
Click to expand...
Click to collapse
have you solve this issue?
A couple of years ago i asked this forum to help me install the unbranded version of the ROM from HTC for my Desire. I created the goldcard, installed the ROM as instructed and everything worked fine. I was happy for 2 years.
Fast forward, my phone fell a couple of weeks back and now when the screen turns off the power button fails to turn it back on. The buttons at the bottom of the phone do illuminate when I press the power button, but the screen does not turn on. Even receiving a call or an alarm ringing does not turn the screen on. The only solution so far has been to remove the battery and reboot the phone: this solution works, but not on every occasion.
I have tried to reset it back to factory settings, but that has not helped. I have tried to install the ROM from scratch (I want to confirm if this is a software problem), but every time I try to install it I get the following error:
ERROR [131]: CUSTOMER ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Click to expand...
Click to collapse
The interesting thing is that the ROM is the one I used 2 years ago and, while I generated a new goldcard, I checked and can confirm that the old goldcard and the new goldcard are identical.
I have then tried rooting the phone using SuperOneClick, Unlock Root and Unrevoked - so as to try installing another ROM instead -, but all of them have failed. It seems that they all try to install some drivers and fail.
I have exhausted all my ideas on what to do.
Any ideas on how to save this phone? I really like my Desire and I do not want to buy a new one right now.
Thanks in advance for your help and support.
I think you are being a little optimistic about it being a software fault. The fact the issue developed after being dropped points to it being hardware (Proximity Sensor possibly).
I wouldn't be screwing around with roms/rooting at all.
Any ideas how to fix it?
Sorry no, the PS being at fault is just a guess as being a logical thing to start with. If you aren't comfortable in dismantling the phone and looking for obvious damage then you'd be best to consult a technician.
Ok, then let's edit the question slightly:
1. Can somebdy help root the device?
2. Can somebody help me understand why the old ROM is failing to install?
Today my device started to get a bit slow so I decided to reboot the phone in a regular way which means:
Press and maintain power button
Select reboot
Wait until phone reboot completely
After this, when the phone rebooted, the touchscreen didn't work anymore. I can use the power button and volume buttons, but the screen is not responding.
I've removed the battery, turned on the phone and nothing. I can't even use the recovery as it's a touch recovery.
Is there anything I can do to restore the touch?
I've preordered the HTC One, however, it will not be delivered until the end of the month.
I will try to take the device to service tomorrow, however, I would love to get my phone back.
Now, can this be a battery issue? (as a friend of mine had the issue with the flash rebooting the phone because of a faulted battery)
I'm searching at google and in the forum to find anything, but I can't find any information about this.
I haven't dropped the phone, I haven't touched anything or forced anything.
I hope some one can help me.
PS: Where can I find a non touch recovery??? that way, I will be able to generate a nandroid backup, flash my nandroid on the Desire HD of a friend and backup all my apps from there until I get the HTC One. Please note that I will have to flash the recovery manually through a notebook as I'm unable to do this because of the non responsive touch screen.
Thank you very much to everyone in advance.
Best Regards.
ClockworkMod has a non-touch version. Download the image and flash it from fastboot. http://www.clockworkmod.com/rommanager. It's probably not a battery problem. It's probably a hardware problem.
bananagranola said:
ClockworkMod has a non-touch version. Download the image and flash it from fastboot. http://www.clockworkmod.com/rommanager. It's probably not a battery problem. It's probably a hardware problem.
Click to expand...
Click to collapse
Dammit, I was hoping there was a way to restore the touch screen functionality. I will take the device tomorrow to a center and see if they can do anything.
Thank mate =)... Hopefully someone has an idea on what to do in the meantime. Tonight I will create a nandroid backup.
same problem here...
rebooted the DHD and after that the touchscreen was dead. no dropping the phone, no nothing.
i tried to flash a different rom... still no touchfunction. how can that be a hardware failure???
any ideas? i really like my DHD...
hi guys,
did you manage to repair your touch screens? or did you identify the problem?
thanks.
Device is fine and can be used via bluetooth mouse / keyboard - however, touchscreen went completly dead
formatted it - changed image, same result
anyone have any idea how to fix it , like a link to a video - part needed - or even a UK store
thanks
I have a similar issue.
I've had my Pixel C for around 11 Months, purchased direct from the google store in November 2017.
Last week I opened the tablet and the screen was totally unresponsive. The physical buttons were working so after several forced reboots which did not help I went for the Nuclear option and restored the device to factory defaults. This didn't work either and I was still unable to interact with the screen so logged a call with Google. I was about to invoke the warranty when suddenly the device responded again after a further reboot. I agreed with the support person that I would keep it for the time being, hoping it was just a glitch
Unfortunately the problem has recurred twice again and the only way to recover seems to be to power the device off, leave it for a "while" and power on.. not exactly scientific.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
touch screen pixel c unreliable
owens2000 said:
I have a similar issue.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
Click to expand...
Click to collapse
Same for me. The touchscreen is unresponsive, thought it would be hardware damaged, but did a couple of restarts, and all of a sudden I was able to type ten letters, then unresponsive again. Were you able to resolve this issue? Thanks!
after the last few updates the screen would respond less and less. This last update last night killed the screen completely. Zero response! I honestly think this is an error on their part but even if they fixed it in an update I cant get in to install the update!
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
tevil said:
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
Click to expand...
Click to collapse
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Im working on trying to unlock the bootloader right now. I tried the toolkit but its giving me a syntax error on trying to flash in fastboot since thats the only thing I can get to. Whats crazy is even the android recovery option is corrupt and this is a stock tablet. I really think google did this to these devices on purpose or unintentionally but has no intention on fixing them. I couldnt even run the update any since there is no way for me to get to anything.
Im looking for instructions on how to do everything from fastboot and ADB but everything is so outdated.
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Hey sorry to post twice but try these. I just tried these steps and got my tablet fully wiped (do caches first) and working. Im enabling USB debugging and bootloader unlock and doing it all now. This was proven to be a google update issue to me.
Perform a master reset
https://thedroidguy.com/2019/08/how...3-xl-touchscreen-not-responding-issue-1094388
To factory reset your Google Pixel 3 XL:
Turn off your Google Pixel 3 XL.
Press and hold the Power+Volume Down buttons until bootloader mode (image of an Android with Start above it) appears, then release.
Select Recovery mode. You can use the Volume buttons to cycle through the available options and the Power button to select. The device will flash the Google start screen momentarily and then restarts in Recovery mode.
If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
From the Android Recovery screen, select Wipe data/factory reset.
Select Yes. Wait for several minutes for the factory data reset process to complete.
Select Reboot system now. Allow several minutes for the factory data reset and reboot processes to complete.
Set the phone up again.
from there I just now used wugfreshs tool kit to unlock the bootloader and Im going to install TWRP and probably a custom rom to avoid updating again.
Update: def a software issue. I worked fine with this tablet for a few hours. Installed 1 app then it locked again. Opera browser. I've had my suspicions of the app for a while which is why I tested this app first. I'm using those same steps again to wipe and seeing if the touchscreen works again. I had trouble getting twrp and a room loaded due to encryption. There is apparently a decrypt file you need to install recovery and root. I can't seem to locate the correct one but wugs toolbox sees the device fine once the drivers are installed.
Ill keep this running and updated with results.
Full wipe and reset again and the screens not working again. What stinks is I once again can't get it into dev mode. I guess maybe it is a hardware issue. Sad, this thing has always been in a case and babied. I still think tho it's a bug with newer releases and the hardware in certain C's. It's beyond warranty though so what can we say to Google at this point. It's not even an old tablet and was pretty pricey. My Nexus 9 still runs perfectly!