[Q] Touch in TWRP not working after Lollipop - Nexus 5 Q&A, Help & Troubleshooting

I updated yesterday, everything went smooth even the flashing of the recovery which I see some people are having trouble with.
Only problem: The touch screen doesn't work while I'm in TWRP.
Only way i got it to work:
Enter TWRP
Wait till screen locks
Open screen - Then the touch works (If I manually lock it then wake it up the touch screen still doesn't work).
I've looked around and I don't think its Lollipop related as people encountered this problem before.
Any suggestions?
Thanks in advance to everyone who helps~

Related

G1(Dream) Touchscreen HELP!

I was flashing a rom the other day (that i had flashed in the past and worked fine) and then i noticed that the touchscreen did not work. (everything else worked)
i flashed back to the cyanogen rom and my touchscreen still did not work.
(when i say my touchscreen doesnt work i mean that i cant touch anything, not even the android to set up my phone)
the trackball works but i am FORCED to touch the android and i cant
ive been flashing and still no luck, any ideas on what happened to my touchscreen or any ideas on how to fix it?
please help!

[Q] Please help CM 10.1 on HTC EVO 4G LTE

This is my first time rooting or doing any modifying to my phone. Can someone please help??!
I have installed the CM 10.1, but whenever I reboot, it takes me to the main screen (language screen), but I am unable to do anything. The touch screen and interactive buttons do not work. The only buttons that work are the power and volume buttons. I can only go back to the bootloader and/or twrp, what do I do???!
hmmmm
lbharris2008 said:
This is my first time rooting or doing any modifying to my phone. Can someone please help??!
I have installed the CM 10.1, but whenever I reboot, it takes me to the main screen (language screen), but I am unable to do anything. The touch screen and interactive buttons do not work. The only buttons that work are the power and volume buttons. I can only go back to the bootloader and/or twrp, what do I do???!
Click to expand...
Click to collapse
Not really sure what you mean, but are you s-on? because then you have have to flash the kernel manually.
I know with my HTC One X I have to flash the boot.img manually before installing CM10 otherwise it just won't work.
Download adb / fastboot
Reboot into bootloader
Connect USB
command is "fastboot flash boot boot.img" - obviously the boot.img is the kernel.
reboot and all should be working
Screen nonresponsive
I flashed my HTC EVO 4G LTE to Cyanogen 10.1. Stupid me didn't make a backup. I have the same issue as OP - the phone boots ok, but screen and keys at the bottom of the screen are non-responsive. I tried flashing 10.0, that didn't work. The Cyanogen splash screen hung. Tried going back to RUU (stock) but I have the new bootloader with Jellybean, and that wouldn't work either. I tried manually flashing the kernel from the latest nightly and got no errors. But same issue. The phone loads, but screen doesn't work.
Found my own answer. This is a typical issue with CM10.1 - the screen drivers have changed. For anyone else who stumbles across this with the same issue...
http://forum.xda-developers.com/showthread.php?t=2151727
Quick Question
Hi guys,
I just have a quick question. I'm on MeanBean 3.09. Its great, but I'm getting the urge to switch roms. I loved cm 10.1, but I missed the voice mail function- which i found an apk to a modded voice mail. I was also having the problem of not getting certain notifications. Facebook, Messenger, and other social apps weren't showing notifications, I would have to manually check. This was a major inconvenience. I was wondering if that has been resolved? Or is there a fix for it?
Thanks,
Nick M.
wwjoshdew....You Tube. He'll know!

*resolved* Touch screen & recovery issues with new install of slimkat

**** resolved *****
(left the battery out for 30 min then tried rebooting into recovery - worked. immediate face palm)
Coming from CM 10 to SlimKat 4.4 build 4 - clean install. Installed the .zips and when I rebooted, the touch screen was not responding. Hard buttons working fine, but can't unlock the screen (somehow a pattern unlock is now on my phone when I had that turned off previously...?!). Tried to reboot into recovery but it takes me to the splash screen and back to the unlock screen. I'm about ready to pull my hair out! Any other suggestions to at least get back to recovery? I was running the latest version of CWM.
Thanks in advance!

Touchscreen issues

Bootloader unlocked
s-off
supercid
hboot: 2.18
Have recently been running CM12.1 nightly from April 26th.
Phone has been working fine until today the touchscreen became completely unresponsive while I was using the phone, would not register touch anywhere on the screen. However when in recovery (TWRP-evita-F2FS-2.8.5.0-unofficial) the touchscreen was entirely functional. I did a full wipe and flashed the newest CM12.1 to see if it would fix the issue. Again when in the ROM touch was not working at all, but in recovery it was completely fine. I decided to run the 5.18 RUU.(Filename: HTC_One_X_RUU_5.18.502.1.exe) to see if it would fix the issue. After successfully running the RUU touch no longer works in the ROM or in TWRP recovery.
Seems very odd to me. Is there anything else I can do to try fixing this?
Update: just flashed CWM recovery so i could flash a rom using the hardware buttons, had candykat 4.4.4 on my computer. Rom booted up and the capacitive buttons started flickering all crazy when i pressed one then stopped after a second and touch is now fully working again....odd. Perhaps hardware failure is imminent lol, but for the time being things are working.
edit: spoke too soon, appears touch is still a bit wonky. I can get it to work but it stutters a bit and usually the capacitive button lights will be flickering when touch starts performing poorly. Could this be a loose connection? dying digitizer? Any help is appreciated.

Need help after failed rom install

I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.

Categories

Resources