Database Info

[Q] TWRP 2.3.3.0 or lower not responding on XL

Anyone expert can advise a noob like me Recently got a One XL from a local telco in Singapore and I have the bootloader unlocked via htcdev.com.
However problem comes after I flash the latest TWRP 2.3.3.0; When I boot into TWRP recovery; the phone is not responding to any touch screen selection; thus I'm able to perform any anything such as "Backup" or whatever. Also the only way for me to get out of the recovery is to press and hold the power button.
I even tried an older version of the TWRP and it is still the same problem. Anyone can advise did I made any mistake ?
Here is my current bootloader status.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0015
eMMC-boot
Nov 26 2012, 18:37:14:9908
Current Software Info:
Android 4.1.1
Software number: 3.17.707.1

i have the same problem im looking for a fix but no luck

htcdaniel1 said:
i have the same problem im looking for a fix but no luck
Click to expand...
Click to collapse
I have the same...its because of the new hboot 2.14.....I have even tried downgrading with JET but unsuccessful.....CWM works but then any rom you flash will not respond to touch gesture.....they must have really locked this down....need the new RUU to get this back

I doubt it is a deliberate attempt at stopping custom things and more a side effect of some change to how the touchscreen works. With any luck the change was to improve something
Also it might be hboot but a whole bunch of firmware is changed beyond hboot with updates. You would need a good understanding of how the phone works before you could say if it is hboot or other related.

try running "fastboot erase cache"

Try installing goo mgr . It uses twrp and loads it directly from os
Sent from my HTC One XL using xda premium

Contact twrp developer I'm sure it's an easy fix for him to accommodate f9r you Telstra people

Im in the same boat.
Just bought this phone 2nd hand for some AOSP action and ive got as far as recovery to install a rom and no touch screen.
Someone above said that they used CWM which was an idea i had, but then the roms they flashed had no working touch screen!
Is it possible the firmware has actually changed the way the touchscreen works and therefore all roms/recoveries will no longer work?
It sounds like an H-boot downgrade may be the only way back. Someone here tried JET to downgrade and was unsuccessful.
Im starting to think there may be no way back, if something doesnt turn up soon i might just have to resell it on which is a real pity...
Any update on this?

hagenuk said:
Anyone expert can advise a noob like me Recently got a One XL from a local telco in Singapore and I have the bootloader unlocked via htcdev.com.
However problem comes after I flash the latest TWRP 2.3.3.0 When I boot into TWRP recovery; the phone is not responding to any touch screen selection; thus I'm able to perform any anything such as "Backup" or whatever. Also the only way for me to get out of the recovery is to press and hold the power button.
I even tried an older version of the TWRP and it is still the same problem. Anyone can advise did I made any mistake ?
Here is my current bootloader status.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0015
eMMC-boot
Nov 26 2012, 18:37:14:9908
Current Software Info:
Android 4.1.1
Software number: 3.17.707.1
Click to expand...
Click to collapse
up up up up up up

This is a known issue after updating by OTA to firmware 3.17 and hboot 2.14. Something in the OTA breaks TWRP.
You can use adb to run TWRP commands. The recovery works, its just the touchscreen that is not responsive within TWRP. Aside from that, you are pretty much stuck waiting for the devs to update TWRP to make it work. Might help to contact the devs, as demand from more users may prompt a quicker response.
I would not recommend CWM as a stopgap fix. CWM is known to cause some major issues on this device. And as a previous response indicates, doesn't really help in this case either.

j626914269 said:
up up up up up up
Click to expand...
Click to collapse
Dont do that, it is a well known issue.
A new update is available to support touch in twrp, but the next problem is no touch in ROM's. You have been warned!
http://forum.xda-developers.com/showthread.php?t=1677447

Danthemanz said:
Is it possible the firmware has actually changed the way the touchscreen works and therefore all roms/recoveries will no longer work?
Click to expand...
Click to collapse
Its not the firmware itself, as TWRP still works just fine with the stock rooted 3.17 ROMs posted in Development. And firmware itself shouldn't affect recovery. But it was something that deployed with the OTA, such as hboot, that broke TWRP.

I have the same problem. I cannot use TWRP and have also been unsuccessful in trying to get the OTA_EVITA_UL_JB_45_S_Telstra_WWE_3.17.841.2_0.23a.32.09.29_10.128.32.34a_release_2997538hizl4svcm80o4g1.zip properly flashed.
I was able to flash the firmware.zip component, but when I try to do the whole .zip through fastboot I get a signature error.
Can someone point me to a guide as to how to extract a flashable zip from the OTA that I can flash with the locked bootloader and fastboot? I think that the problem is that the system partition has not been flashed.
Thankx in anticipation

redpoint73 said:
Its not the firmware itself, as TWRP still works just fine with the stock rooted 3.17 ROMs posted in Development. And firmware itself shouldn't affect recovery. But it was something that deployed with the OTA, such as hboot, that broke TWRP.
Click to expand...
Click to collapse
It is almost certainly a change in the firmware itself, twrp 2.3.3.1 works because the kernel was updated to the kernel that 3.17 uses. The newer kernel supports the change in the firmware.
---------- Post added at 11:20 PM ---------- Previous post was at 11:18 PM ----------
fezzawinkle said:
I have the same problem. I cannot use TWRP and have also been unsuccessful in trying to get the OTA_EVITA_UL_JB_45_S_Telstra_WWE_3.17.841.2_0.23a.32.09.29_10.128.32.34a_release_2997538hizl4svcm80o4g1.zip properly flashed.
Click to expand...
Click to collapse
You cant just flash OTA from fastboot afaik.
You can download already prepared 3.17 ROM's here:
http://forum.xda-developers.com/showthread.php?t=2076361
http://forum.xda-developers.com/showthread.php?t=2055490
http://forum.xda-developers.com/showthread.php?t=2066023

twistedddx said:
Dont do that, it is a well known issue.
A new update is available to support touch in twrp, but the next problem is no touch in ROM's. You have been warned!
http://forum.xda-developers.com/showthread.php?t=1677447
Click to expand...
Click to collapse
Hi, i can't find the link to v2.3.3.1 Can you tell me where you found it?
Edit: found it - http://forum.xda-developers.com/showthread.php?t=1677447&page=43

Need help with getting back on stock ROM

Hello guys,
Recently I bought HTC Desire S and the ROM on it is Cyanogenmod 7.2.
Now I am trying to install on official version of android 4.0.3. I downloaded the RUU from htcdev.com
RUU_SAGA_ICS_35_S_HTC_Europe_14.01.401.2_Radio_20.76.30.0835_3831.19.00.110_release_275068_signed
Click to expand...
Click to collapse
I plug the phone in PC and start the RUU, click few next buttons... till i get to the window to the Current information about your androud phone:
It says I got a ROM verson 2.10.401.4 and it needs to be updated to 14.01.401.2 (check picture 1)
After I click the next button and the wizard starts to update my phone. (check picture 2)
After one minute of that updating process I get the following error: (check picture 3)
ERROR [155]: Unknown Error
The only thing i can do is click recovery which doesn't help at all ....
Information about bootloader:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.19.00.110
eMMC-boot
Recovery is 4EXT Recovery 2.2.7 RC5
So my question is what am I doing wrong, and how can I install official version of android on my phone.
Tnx for answers,

You want STOCK rom or is it just Sense 3.6 that interests you ?
If it's just for Sense 3.6, there are few customs roms all around here. but you're S-ON so you'll need to flash boot.img independently via adb..
Instead if you want a completly stock rom you can check this thread.

Ok, I relocked the bootloader now I am in updating process. I will tell you what will happend
Till now everything looks okay

Great, if update began then you shouldn't have any prob
XDApped from my pimped Desire S

[Q] Can't Update From Old CM Experimental: Boot Loops

I've been running Evita cm-10.1-201.0.04-experimental for some time now. Since I'm getting tired of the bugs over the past few months I've downloaded a few different roms to try them out including but not limited to:
AT&T 3.18
CM 10.1.3 RC2
CM 10.1.3 RC1
The latest CM nightly
some random AOKP build I used to use​However, I was getting install failures for each.
Finely having the necessary time to figure this out yesterday, I decided to get it this sucker updated.:fingers-crossed:
I determined that I needed to update my bootloader past 1.09.0000
I accomplished that after updating it with RegawMOD Bootload Customizer using OneXL2.14.dll.
Now only the CMs install. (AT&T still fails, but this time without reason. [there were assertion failures before the bootloader update])
On CM installs: All looks good, reset, then boot loops... 10+ I let it sit for at least 5 mins. Tried on each CM.
Wiped in TWRP cache/darivk/factory resets/system/secure/etc. each time multiple times over.
Even tried loading over fastboot the the boot.img for the respective roms... still boot loops.
Oh, and did a few side-loads... no go.
The only thing that works is reverting back to the experiential.
Red-eyed and annoyed, I defer to the more knowledgeable people of xda...
Any ideas as to how fix this?
Thanks for any help.
-Matt
S-off / supercid / TWRP

What version of TWRP are you using? Also, please provide your bootloader details. And when you say at&t 3.18 what exactly are you talking about?
Sent from my Evita

asdff issinvo
timmaaa said:
What version of TWRP are you using? Also, please provide your bootloader details. And when you say at&t 3.18 what exactly are you talking about?
Click to expand...
Click to collapse
Please forgive incomplete URLs as I don't have permission to post them yet.
TWRP: 2.3.3.0
AT&T 3.18: Extracted zip from exe found here: www [dot] htc [dot] com/us/support/news.aspx?p_id=464&p_name=htc-one-x-att
using method found here: sites [dot] google [dot] com/site/androidbyyorzua/home/tutorials/extracting-rom-files-from-htc-ruu
matthewcordaro said:
RegawMOD Bootload Customizer using OneXL2.14.dll.
Click to expand...
Click to collapse
Just in case here is my bootloader screen:
*** TAMPERED ***
CUSTOM BOOTLOADER
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Nov 26 2012, 18:37:14:-1​

I'm not sure if this is what's causing your problem, but it's never advisable to mess with the RUU exe files. I'd try running the RUU properly and see if it helps your problem.
Sent from my Evita

timmaaa said:
I'd try running the RUU properly and see if it helps your problem.
Click to expand...
Click to collapse
Ran the RUU exe...
Errors: "Make sure your phone is connected", etc.
I ran "adb devices" to make sure it was connected prior to running the exe.
I killed-server 3 times before running the exe and 3 other times I did not. Same errors for both.
It's not just the RUU. I can't load a single Evita rom that I've come across, either by side load or through recovery, except for the Cyanogenmod Experimental I have on the phone now.

What OS are you running on your pc?
Sent from my Evita

timmaaa said:
What OS are you running on your pc?
Click to expand...
Click to collapse
Win 7 x64. Drivers work fine. fastboot/adb/usb storage all work fine.
(Also run ubuntu 12.04 x64 without any adb or fastboot issues.)
FYI: Tonight I'm going to update TWRP to the latest version. 2.3.3.0 -> 2.6.3.0

Updated recovery to 2.6 without a hitch.:good:
Attempted installs. No go.
Decided to download a downgrade to test out: CM10.0
As it turns out, I can load this rom. lol???:silly:

Since my original goal was to get it back to a stock build, I decided to give it a go with a rooted stock...
[ROM][4/30/13] Stock AT&T Stock Deodexed JB 4.1.1 | Official AT&T 3.18.502.6 Update found here.
Said ROM will run as well as the CM 10.0.0 and aforementioned CM experimental.
Since I'm giving this phone to a family member when I get the Samsung Note 3, I'm not going to attempt any others installations for the foreseeable future.
Thanks for your ideas.:cyclops:

[Q] help me to update

XDA Greetings friends, I have a HTC ONE X AT & T with the following specifications:
Unloket
Avoid PVT Ship S-off rl
CID-11111111
Hboot-1.14.0002
Radio-0.19as.32.09.11.2
openDPS-v29.1.0.45.0622
eMMC-boot.
June 11, 2012, 14:36:28
My question is this:
I can? Place a cooked ROM with android 4.2.2 and Sense 5?, Having HBOOT 1.14? eye now I'm on android 4.0.4 manufactures, I have the SuperCID, Unlocked bootloader, root the phone and installed the TWRP Recovery
Or did I have to apply a RUU (3.18.502.6) to be on HBOOT 2.14??? and so to upgrade to android 4.2.2???
If I apply the RUU'll have to repeat the process bara release the bootloader, root and install the Recovery?
Thanks mates!
excuse my bad English

You can go ahead and install a custom Sense 5 Android 4.2.2 with your current setup. You'll need to install the Beastmode kernel though or you'll suffer signal loss and reboots. The other option is to upgrade to the 2.15 firmware package.
Sent from my Evita

timmaaa said:
You can go ahead and install a custom Sense 5 Android 4.2.2 with your current setup. You'll need to install the Beastmode kernel though or you'll suffer signal loss and reboots. The other option is to upgrade to the 2.15 firmware package.
Sent from my Evita
Click to expand...
Click to collapse
ok I understand correctly, if it does not work for my rom Kernel 4.2.2 Beastmode more, as I get to the 2.15 firmware upgrade package?
Very Grateful for your previous answer : Bueno:

Install the ROM and the Beastmode kernel together and you'll be fine.
Sent from my Evita

Nehomar_C said:
ok I understand correctly, if it does not work for my rom Kernel 4.2.2 Beastmode more, as I get to the 2.15 firmware upgrade package?:
Click to expand...
Click to collapse
When you flash a ROM (with S-off) both the ROM and kernel are replaced, so it doesn't actually matter what ROM and kernel you are coming from.
Sense 5 custom ROMs will install fine on any hboot. But some folks will get signal drops and random reboots. Solution is to either flash Beastmode kernel or flash the 2.15 firmware.

[Q] Unable to mount /system

So I'm very green to Rooting. 3 days into ROM world.
I purchased a used ATT HTC One X. It came rooted with Viper XL 4.0.0 installed. That ROM works fine, however, I would like to update/change it to another ROM. I installed ROM Manager and made a full backup of my current install. I tried using TWRP 2.6.0.0 to flash a new ROM. I did the Wipe and then tried to flash a new ROM. However, when the ROM install is happening (for any ROM tried) I get an error that says... unable to mount /system.
I am able to restore to the ViperXL install with no problem. That is my current backup.
Tried cm-10.2.0-evita.zip downloaded from cyanogenmod’s download site
Tried Dev-3.22.1540.1-Stock-Rooted-DE-ODEX.zip downloaded from stockroms.net
I tried this stock ROM because I thought it might be easier to load a new ROM on top of that. I also tried using the CyanogenMod Installer but it failed to recognize the device.
Bootloader:
****Unlocked****
EVITA PVT SHIP S-OFF RL
CID- 11111111
HBOOT- 2.14.0000
RADIO- 1.31a.32.45.16_2
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
Additional current phone/software info:
Android version: 4.2.2
HTC Sense Version 5.0
Software Number: ViperXL 4.0.0
HTC SDK API level: 5.41
Kernel version:
3.4.10-g08ef01e
[email protected] #1
SMP PREEMPT
Any help/guidance is appreciated.

Have you tried using the mount feature in TWRP to mount the system partition? Not sure if it's gonna work but it's worth a try. If that doesn't work I'd suggest running the 3.18 RUU. Then flash TWRP again and see if you can install ROMs ok.
Sent from my Evita

timmaaa said:
Have you tried using the mount feature in TWRP to mount the system partition? Not sure if it's gonna work but it's worth a try. If that doesn't work I'd suggest running the 3.18 RUU. Then flash TWRP again and see if you can install ROMs ok.
Sent from my Evita
Click to expand...
Click to collapse
Mount feature in TWRP didn't work. I ran the 3.18 RU and now I'm back on Android 4.1.1 with build 3.18. However, now I'm not rooted anymore. I assume I need to root the phone now? Would appreciate any suggestions on the easiest way to do so.

All you need to do now is flash TWRP again, and then you can flash Superuser or SuperSU to root the stock ROM, or flash a custom ROM.
Sent from my Evita

tup4 said:
Tried Dev-3.22.1540.1-Stock-Rooted-DE-ODEX.zip downloaded from stockroms.net
Click to expand...
Click to collapse
That is not a ROM for our device. Its for the HTC One (M7), not your One X/XL (EVITA).
You're lucky you didn't brick the phone, flashing a file for another device while you are s-off (device checks are "off" with s-off). Do yourself a big favor, and only flash things that are on XDA in this forum section, or in my Index thread:
http://forum.xda-developers.com/one-x-att
http://forum.xda-developers.com/showthread.php?t=1671237

Good catch, I didn't notice that.
Sent from my Evita

timmaaa said:
All you need to do now is flash TWRP again, and then you can flash Superuser or SuperSU to root the stock ROM, or flash a custom ROM.
Sent from my Evita
Click to expand...
Click to collapse
Timaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa!
I am officially on a stable version of CyanogenMod
Much appreciated.

Sweet
Sent from my Evita

I've been on CM 10 for a few days now. Everything seems to be running fine with one exception. I notice that my wireless connection drops occasionally. What is used to determine if I have a firmware mismatch?

A firmware mismatch doesn't usually affect aosp ROMs, but you could try flashing another radio. You're currently using a radio that was released with the 5.0x Sense 5 ROMs, I'd suggest trying out one of the 3.17/3.18 radios.
It could be an issue with the ROM itself, cm10 is pretty old. There are a few 4.4 ROMs available at the moment that I've run with zero stability issues so maybe you could try one of those. Overall I believe they're better than 4.1 ROMs like cm10.
Sent from my Evita