TWRP Touch Screen Won't Work
- Thread starter mr_krunchi
- Start date
-
- Tags
- question
I doubt anything is wrong from their side as it was working perfectly well in the morning today.
No No NO!
ClockWorkMod DOES NOT WORK properly on this device. TWRP is the ONLY fully working recovery that will not bork important device partitions.
Please do not give bad advice.
P.S. Why bump this month old thread? I'm sure this issue has been resolved.
Last edited:
+1
Not to mention that the guide from the link he provided appears to be for a different device.
Sent from my EVO 4G LTE using xda premium
Last edited:
Ohh okay, I had the same issue on my htc one and thought that it could fix the problem. So I take the Words back!
Same here. My HTC One TWRP is not responding to touch. Did you figure it out for your device yet?
Why? I tried using CWM Recovery (regular, not touch) as well and that works with the volume keys but aroma does not.
Aroma has to be updated to 2.70B for the screen to work properly but you can still use the vol buttons to navigate and the home button to select
It still isn't working. If it helps, I'm have a USA DEV Edition HTC One that I rooted and ROMMED to be a Google Play Edition. The build number is 2.14.1700.15 CL211149 and kernel version is 3.4.10-g7edee3c [email protected] #1. Someone please help me out. Thanks.
Not to be rude but we are going Off Topic in this thread maybe you should move you question to Q&A for your device
Just did. Thanks for the help.
http://forum.xda-developers.com/showthread.php?p=44107099#post44107099
TWRP DOES NOT WORK with Sprint HTC EVO 4G LTE with kernel 3.17xxxORD
This my experience, not opinion.
CWM is the ONLY thing that works at all. If TWRP had keypress controls too it would be fine. I have a Sprint HTC EVO/Jewel 4G LTE, that had a 3.17xxxORD kernel and jb4.12. I tried several versions of TWRP from 2.8.1.0 on back, none worked, No touch. I fastbooted an img of CWM (recovery-clockwork-6.0.4.8-jewel.img) and all was golden. Couldn't get MeanBean or BeanStalk to work, but after several tries EOS (EOS-full_jewel-20140724.103928.zip) is now running fine. I used CWM 6.0.4.8 to flash CWM-SuperSU-v0.87.zip and gapps-kk-20140606-signed.zip after Rom install. I have kk4.4.4 now, I guess the latest versions of EOS have it.
How specifically does CWM damage partitions? When every other solution has been eliminated, whatever is left, appears to be the only answer.
I unlocked hboot with HTCDev option. Then fastbooted TWRP, it looked awesome, but was useless. Couldn't get root until I fastbooted CWM. Phone appeared to be a brick after flashing ROM, but HTC Sync would open after holding power and volume keys, telling me there was some life in the phone. After CWM, then SU, then reflashing EOS with fastboot phone rebooted within a couple minutes, right as I was getting ready to order another phone.
WinDroid also works, if the phone appears to be a brick only the fastboot tab works, but a cmd window and DOS commands work better. How hard would it be to insert key commands into TWRP for redundancy? TWRP may the ONLY fully working recovery that will not bork important device partitions, but it did not work at all on this unit with this kernel, and CWM worked.
---As of today it is Not resolved.
This my experience, not opinion.
CWM is the ONLY thing that works at all. If TWRP had keypress controls too it would be fine. I have a Sprint HTC EVO/Jewel 4G LTE, that had a 3.17xxxORD kernel and jb4.12. I tried several versions of TWRP from 2.8.1.0 on back, none worked, No touch. I fastbooted an img of CWM (recovery-clockwork-6.0.4.8-jewel.img) and all was golden. Couldn't get MeanBean or BeanStalk to work, but after several tries EOS (EOS-full_jewel-20140724.103928.zip) is now running fine. I used CWM 6.0.4.8 to flash CWM-SuperSU-v0.87.zip and gapps-kk-20140606-signed.zip after Rom install. I have kk4.4.4 now, I guess the latest versions of EOS have it.
How specifically does CWM damage partitions? When every other solution has been eliminated, whatever is left, appears to be the only answer.
I unlocked hboot with HTCDev option. Then fastbooted TWRP, it looked awesome, but was useless. Couldn't get root until I fastbooted CWM. Phone appeared to be a brick after flashing ROM, but HTC Sync would open after holding power and volume keys, telling me there was some life in the phone. After CWM, then SU, then reflashing EOS with fastboot phone rebooted within a couple minutes, right as I was getting ready to order another phone.
WinDroid also works, if the phone appears to be a brick only the fastboot tab works, but a cmd window and DOS commands work better. How hard would it be to insert key commands into TWRP for redundancy? TWRP may the ONLY fully working recovery that will not bork important device partitions, but it did not work at all on this unit with this kernel, and CWM worked.
Had the same problem on my Asus Slider SL101 - Fortuantely it has an USB Port so i put a mouse to it and that worked.
Can you unlock that screen lock in twrp recovery mode ?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone