TWRP Touch Screen Won't Work

mr_krunchi

Member
Feb 3, 2011
18
1
0
Anaheim
I'll pull the boot.img from the OTA. That *should* get the touch screen working properly. If it doesn't, I'll S-ON my device, unlock again, take the OTA, and see what I can come up with as a solution.

EDIT: boot.img attached (it's in the zip). If you're unlocked, you should be able to either fastboot the img in the zip file, or rename the entire zip to just PJ75IMG.zip and flash through HBOOT.

EDIT 2: Also, if you need a different 3.16 ROM to flash, that'll work with TWRP 2.4.1.0, you can try mine from here: http://d-h.st/users/Captain_Throwback/?fld_id=10308#files

EDIT 3: Ok, well I can confirm that with TWRP 2.4.1.0, after flashing the new touch panel image, I'm unable to flash either of my ROMs either. Now to try a ROM based on the 3.15 (Viper4G), and see if I can use that along with the signed boot.img :rolleyes:.

EDIT 4: The AROMA installer does show up in a weird color in this latest TWRP, but the ROM does appear to have flashed successfully (I assume restoring a nandroid would work too). Touch screen unresponsive on initial boot, but after fastbooting the boot.img from my stock rooted ROM, I can navigate (the one from this post should work also).
Well I tried to install the 3.16 you posted, but neither of them worked for me. It failed for both. I'm looking for the Viper4G ROM you're talking about, but only came across one that was really old. Mind posting the link please? I'd really like to use my new phone lol.
 

Captain_Throwback

Recognized Developer
Aug 22, 2008
20,080
22,348
203
The Nothing

tonyevo52

Senior Member
Feb 1, 2013
794
445
0
Captain

Captain, so for the 3.16 Stock ROM you posted, I am assuming it will take the phone back to 3.16 stock, but does it matter if you are s-on or off, i am rooted using the 2.4.1 and SU 1.04, from reading everything, the way i understand there is no way to flash ROMS right now, so to me, if i screw something up, your 3.16 should be my saving grace from bricking the phone?
 

Captain_Throwback

Recognized Developer
Aug 22, 2008
20,080
22,348
203
The Nothing
I've been trying to install the viper rom for 15 minutes now and it's stuck at 4%, executing full wipe, formatting/system partition.
It does that on full wipe sometimes. Do a battery pull/reboot back into recovery and wipe manually. Then choose the no wipe option in AROMA.

Captain, so for the 3.16 Stock ROM you posted, I am assuming it will take the phone back to 3.16 stock, but does it matter if you are s-on or off, i am rooted using the 2.4.1 and SU 1.04, from reading everything, the way i understand there is no way to flash ROMS right now, so to me, if i screw something up, your 3.16 should be my saving grace from bricking the phone?
You won't be able to flash my ROM with TWRP 2.4.1.0.
 

mr_krunchi

Member
Feb 3, 2011
18
1
0
Anaheim
So Viper4G didn't work out. I flashed the ROM using TWRP 2.4.1. It did install all the way and finished, but I'm stuck on the boot animation and just continues to stay on that screen. I was never able to get it to boot up completely. I then flashed the boot.img from your ROM, and that didn't change anything. So I'm still stuck with a brick :(

EDIT: So I looked at the previous post about the full wipe thing and decided to try it out again, without the AROMA wiping everything. I got it to boot up completely! I just flashed the boot.img from your Stock 3.16 ROM, booted it up, and now it works (so far)! :] Happy camper right here. Thanks so much!
 
Last edited:
  • Like
Reactions: scrambler7

scrambler7

Member
Nov 1, 2008
31
2
0
It does that on full wipe sometimes. Do a battery pull/reboot back into recovery and wipe manually. Then choose the no wipe option in AROMA.
Ended up doing that and got the same results as krunchi below

So Viper4G didn't work out. I flashed the ROM using TWRP 2.4.1. It did install all the way and finished, but I'm stuck on the boot animation and just continues to stay on that screen. I was never able to get it to boot up completely. I then flashed the boot.img from your ROM, and that didn't change anything. So I'm still stuck with a brick :(
Yeah, this sucks. Had it stick on the animated viper. Even after it looks like it installs, if you boot back into recovery, twrp doesn't show an os installed.

Tried installing CM10 stable and it stuck on the animated boot as well.

It looks like trying a rom with aroma installer gets you the farthest, but still won't boot. frustrating.
 

Captain_Throwback

Recognized Developer
Aug 22, 2008
20,080
22,348
203
The Nothing
Ended up doing that and got the same results as krunchi below



Yeah, this sucks. Had it stick on the animated viper. Even after it looks like it installs, if you boot back into recovery, twrp doesn't show an os installed.

Tried installing CM10 stable and it stuck on the animated boot as well.

It looks like trying a rom with aroma installer gets you the farthest, but still won't boot. frustrating.
Look at the edit above your post ;).
 
  • Like
Reactions: scrambler7

michaeldm

Member
Sep 8, 2010
12
0
0
Good news!

TWRP has been updated to version 2.4.1.0 that fixes the touchscreen issue in recovery. Please thank Dees_Troy for the fix at your earliest convenience :).
So are we able to use the official 3.16.651 OTA and used the new tp.img that comes with it when using 2.4.1.

Also, do I need to relock my boot loader when doing an RUU or receiving an official OTA

Unlocked
S-OFF
Recovery: TWRP 2.3.3
Device: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003
Baseband: 1.12.11.1119 | PRI: 2.87_003 | PRL: 25012
HBOOT: 2.09.2222
 

fearstealth

Member
Feb 6, 2013
13
0
0
So are we able to use the official 3.16.651 OTA and used the new tp.img that comes with it when using 2.4.1.

Also, do I need to relock my boot loader when doing an RUU or receiving an official OTA

Unlocked
S-OFF
Recovery: TWRP 2.3.3
Device: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003
Baseband: 1.12.11.1119 | PRI: 2.87_003 | PRL: 25012
HBOOT: 2.09.2222
I just got my evo lte yesterday at sprint :D and the person that was activating my phone updated my phone to 3.16 I'm dying to root it and install recovery on it and flash CM10, but all i been reading that the update 3.16 messes everything up, so does that mean i can't flash nor root my evo using S-ON with recovery version 2.4.1?
 

Captain_Throwback

Recognized Developer
Aug 22, 2008
20,080
22,348
203
The Nothing
I just got my evo lte yesterday at sprint :D and the person that was activating my phone updated my phone to 3.16 I'm dying to root it and install recovery on it and flash CM10, but all i been reading that the update 3.16 messes everything up, so does that mean i can't flash nor root my evo using S-ON with recovery version 2.4.1?
You can still do all those things. There are just additional steps that need to be taken. If you read through the thread, I explained what needs to be done.

For starters, you'll have to unlock with HTCDev. Then you'll have to install TWRP 2.4.1.0. Then, you'll only be able to install JellyBean Sense ROMs based on the 3.15.651.13 base, like Viper4G, which you'll have to follow up by flashing the boot.img from the 3.16.651.3 ROM update through fastboot or via HBOOT.

I'm not going to explain how to do all that; the information is all here. But that's how we got quite a few others going.
 
  • Like
Reactions: volk9029

BigMosley

Senior Member
Aug 19, 2011
4,327
1,204
0
I can't seem to find a TWRP thread on here. Where can I go to talk about the update to fix it screen driver issue as well as to where I can download this fix and thank the creator?

Sent from my EVO using xda premium
 

Captain_Throwback

Recognized Developer
Aug 22, 2008
20,080
22,348
203
The Nothing
I can't seem to find a TWRP thread on here. Where can I go to talk about the update to fix it screen driver issue as well as to where I can download this fix and thank the creator?

Sent from my EVO using xda premium
TWRP thread: http://forum.xda-developers.com/showthread.php?p=37717588

That's also the fix to the TWRP rebooting while flashing issue. Maybe I'll update my stock rooted ROM with the fix so that people have one to flash.
 

viennk07

New member
Feb 6, 2013
2
0
0
batus ymextr

I'll pull the boot.img from the OTA. That *should* get the touch screen working properly. If it doesn't, I'll S-ON my device, unlock again, take the OTA, and see what I can come up with as a solution.

EDIT: boot.img attached (it's in the zip). If you're unlocked, you should be able to either fastboot the img in the zip file, or rename the entire zip to just PJ75IMG.zip and flash through HBOOT.

EDIT 2: Also, if you need a different 3.16 ROM to flash, that'll work with TWRP 2.4.1.0, you can try mine from here: ]

EDIT 3: Ok, well I can confirm that with TWRP 2.4.1.0, after flashing the new touch panel image, I'm unable to flash either of my ROMs either. Now to try a ROM based on the 3.15 (Viper4G), and see if I can use that along with the signed boot.img :rolleyes:.

EDIT 4: The AROMA installer does show up in a weird color in this latest TWRP, but the ROM does appear to have flashed successfully (I assume restoring a nandroid would work too). Touch screen unresponsive on initial boot, but after fastbooting the boot.img from my stock rooted ROM, I can navigate (the one from this post should work also).

So, I've done everything. I've installed TWRP 2.4 1. 0 and I've installed the newest Viper4g ROM and in aroma it basically stops at 90% and restarts and it doesnt look like anything gets accomplished. In fact with every ROM--MEanbean, odex, deodex, viper4g-- the installation just freezes and starts over, except for SuperLTE. What can I do about this.
 

Captain_Throwback

Recognized Developer
Aug 22, 2008
20,080
22,348
203
The Nothing
So, I've done everything. I've installed TWRP 2.4 1. 0 and I've installed the newest Viper4g ROM and in aroma it basically stops at 90% and restarts and it doesnt look like anything gets accomplished. In fact with every ROM--MEanbean, odex, deodex, viper4g-- the installation just freezes and starts over, except for SuperLTE. What can I do about this.
Tomorrow I'll update my stock rooted 3.16 ROMs so that TWRP will flash them successfully. Then you can flash one of those.

EDIT: When you flashed Viper, did you make sure you chose the option to NOT wipe?
 
Last edited:
  • Like
Reactions: BigMosley

viennk07

New member
Feb 6, 2013
2
0
0
Tomorrow I'll update my stock rooted 3.16 ROMs so that TWRP will flash them successfully. Then you can flash one of those.

EDIT: When you flashed Viper, did you make sure you chose the option to NOT wipe?
yes i chose the option not to wipe. Also i just found the Viper Kernel flasher that's supposed to help with bootloops but that really didn't help me much either. now the rom isn't even loading.

and cool i'll look forward to it
 

Captain_Throwback

Recognized Developer
Aug 22, 2008
20,080
22,348
203
The Nothing
Tomorrow I'll update my stock rooted 3.16 ROMs so that TWRP will flash them successfully. Then you can flash one of those.

EDIT: When you flashed Viper, did you make sure you chose the option to NOT wipe?
yes i chose the option not to wipe. Also i just found the Viper Kernel flasher that's supposed to help with bootloops but that really didn't help me much either. now the rom isn't even loading.

and cool i'll look forward to it
As promised: http://d-h.st/users/Captain_Throwback/?fld_id=10308#files

TWRP 2.4.1.0 will flash either of those no problem. I tested myself ;).
 
  • Like
Reactions: volk9029