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

[Q] HTC one X 4.1.1 Hboot 2.14.000

Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S

tookie69 said:
Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S
Click to expand...
Click to collapse
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2

Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.

OK i have unlocked again and re pushed recovery TWRP 2.4.1.0
But I still cant boot into the recovery option..
PLease tell me what im doing wrong..
iElvis said:
Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.
Click to expand...
Click to collapse

I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Kole_Ackerson said:
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse

tookie69 said:
I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Click to expand...
Click to collapse
I believe through adv but is way simpler to do it through recovery. Try a earlier version of twrp
Sent from my HTC One X using Tapatalk 2

did you verify you are unlocked now, or did you just assume since you pushed the token again?

Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?

I pushed the same token and rebooted the device at the top its now says unlocked
DvineLord said:
did you verify you are unlocked now, or did you just assume since you pushed the token again?
Click to expand...
Click to collapse

make sure to run "fastboot erase cache" after changing recovery

IM pretty sure.. I also tried and older TWRP still same issue would you happen to have a link ? I have been using the all in one for HTC one X Tool
iElvis said:
Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?
Click to expand...
Click to collapse

bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita

ok i loaded that last night before i went to bed I went this morning to look at the phone and now it just goes to a black screen no madder what I do i put it in the computer the computer goes beep now when its plugged in my computer only the red light at the top flashes and then it disconnects from my computer because i can here the beep of adding and removing hard ware.
is my phone now bricked ?
DvineLord said:
bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita
Click to expand...
Click to collapse

Just relock and boot into boot loader the tampered screen then run a ruu am you should be back to stock
Although I had a EVO before that I flashed the wroung bootloader an bricked it an it wouldn't go anywhere but the bootloader
Sent from my HTC One X using xda premium

If I were you I'd reinstall drivers and manually push the recovery via adb. Use this command- fastboot flash recovery (filename).img
Sent from my HTC One X using Tapatalk 2

Thanks
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one

Rom installation fails on Rogers HTC One X, S-ON, EVITA, HBOOT 2.14.0000
tookie69 said:
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one
Click to expand...
Click to collapse
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.

iccrcmember said:
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.
Click to expand...
Click to collapse
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.

I'll just clarify that when Redpoint said you need to update TWRP you should update it to TWRP 2.6, your current version (2.5) is very buggy. Also, he means since you are s-on you need to flash the boot.img, when you get s-off this will no longer be required.
Sent from my Evita

Thank you redpoint73
redpoint73 said:
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.
Click to expand...
Click to collapse
I made an error. my bootloader was already unlocked. Any how flashing the boot.img of the Rom before installing the Rom worked. Thank you for your insight. My phone is up and running.
For others: below is the rom i flashed:
[ROM] 10/10 Team Venom ViperX 4.0.4 - Sense 5 JellyBean | orig. OTA | Tweaks
http://forum.xda-developers.com/showthread.php?t=2087443

[Q] hboot 2.15.0000 -- Can't get rom to flash and work!

UPDATE:
Keeping the top here current for the tldr problem:
- My setup -- T-mo HTC one S with original hboot 2.15.0000 picked from that link, S-On, no SuperCID, and I can unlock the bootloader. I have TWRP 2.3.3.0 installed.
- I can run the T-Mo release_309489 RUU and get a working OS, *except* that my USB port keeps connecting/disconnecting
- Flashing the latest CM10 nightly results in spinning CM logo but no successful boot. It seems as if flashing boot.img did not take, although I got no errors
- I cannot do SuperCID anymore, it seems as though the modified partition is not writable anymore (due to hboot?)
--- Old stuff ---
So I noticed the latest nightly and decided to flash it, and then an error occurred telling me I needed a newer hboot. I installed 2.15.0000 and then the rom and boot.img extracted from rom, but all I got was a bootloop, no CM logo at all. Tried different roms to no avail. Grappled with sdcard unreadable so I have flashed stock recovery to fix that a few times now. I'm kind of at a dead end and feel like I tried everything I could think of. Any help is appreciated!
I can fastboot fine but adb is very spotty, as my computer keeps connecting/disconnecting to my phone, preventing any real use of adb. It seems that when I write to the sdcard, I get immediately disconnected from the phone almost as if the sdcard write is crashing the connection somehow.
I have tried using CWM recovery as well as TWRP 2.6 and 2.4.4.

Try TWRP 2.3.3.0
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Try TWRP 2.3.3.0
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks, I will try that. Magical version or something?
I did burn some midnight oil last night and got the latest tmo RUU that I could find to install (RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe). By the way, there is an OTA update available, any reason I should take it?
I un-superCID'd, relocked bootloader etc and I am guessing that this one installed because the hboot is 2.15.0000? Anyway, I am wondering what I might have done wrong to cause this in the first place. I still have very odd behavior when USB is hooked up, the connection continuously connects and then drops when in the stock ROM. Could that be an hboot issue?

crakarjax said:
Thanks, I will try that. Magical version or something?
I did burn some midnight oil last night and got the latest tmo RUU that I could find to install (RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe). By the way, there is an OTA update available, any reason I should take it?
I un-superCID'd, relocked bootloader etc and I am guessing that this one installed because the hboot is 2.15.0000? Anyway, I am wondering what I might have done wrong to cause this in the first place. I still have very odd behavior when USB is hooked up, the connection continuously connects and then drops when in the stock ROM. Could that be an hboot issue?
Click to expand...
Click to collapse
Ok that's great.
-RUU is a one step solution to many problems so that's why it worked.
- the OTA available is for T-Mob only. You may install it if you don't have SuperCID; it contains some sort of battery fix.
- Odd USB behavior could be due to a variety of reasons. For instance:
1. Faulty Cable. Check other cables.
2. Incomplete driver installation. Might try with with HTC Sync Manager.
3. Try enabling USB debugging.
- I can't really seem to establish a relation between HBOOT and USB not working, but then I might be having insufficient knowledge.
Best of luck!
Sent from my HTC One S using Tapatalk 4 Beta
---------- Post added at 03:14 AM ---------- Previous post was at 03:10 AM ----------
And yes, 2.3.3.0 indeed is magical for it has shown wonders where other versions have failed.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
Ok that's great.
-RUU is a one step solution to many problems so that's why it worked.
- the OTA available is for T-Mob only. You may install it if you don't have SuperCID; it contains some sort of battery fix.
- Odd USB behavior could be due to a variety of reasons. For instance:
1. Faulty Cable. Check other cables.
2. Incomplete driver installation. Might try with with HTC Sync Manager.
3. Try enabling USB debugging.
- I can't really seem to establish a relation between HBOOT and USB not working, but then I might be having insufficient knowledge.
Best of luck!
Sent from my HTC One S using Tapatalk 4 Beta
---------- Post added at 03:14 AM ---------- Previous post was at 03:10 AM ----------
And yes, 2.3.3.0 indeed is magical for it has shown wonders where other versions have failed.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
I have tried TWRP 2.3.3.0 but that did not seem to help. My cable is good, I connected my wife's One S to my computer and it had no issues. iirc, I do not have USB issues in TWRP anymore though... so perhaps 2.3.3.0 did help in that regard. The connection works fine with fastboot so I am pretty sure that there is no hardware issue here.
I was going to try to get S-Off but couldn't get SuperCID to stick; it seems that the RUU I installed write protected that partition because I could do SuperCID before I applied the factory RUU.
I am still able to go back to stock with the factory RUU if I apply the factory recovery and relock.
My hboot now says " Tampered / Relocked / Security Warning " if that means anything.
And finally, I am able to flash CM10 (nightly 8-04) but when I did that I got a boot hang at the spinning CM logo. I did fastboot flash the boot.img from that ROM, but it seems to behave as if the boot.img is still incorrect. I suspect that as with SuperCID, something is locking down my ability to write the correct boot.img. Is there any way to pull the boot.img off after flashing to verify that it was correctly written?
Since I have not been able to get a custom ROM working since I updated to hboot 2.15.0000, I have to think that the hboot is the culprit. At the same time, I don't see why a version of CM10 would have been released that required 2.15.0000 if it had not been tested. It is possible I suppose that I have installed a bogus hboot, as I grabbed it from someone's post (http://forum.xda-developers.com/showthread.php?p=39216236#post39216236).

crakarjax said:
I have tried TWRP 2.3.3.0 but that did not seem to help. My cable is good, I connected my wife's One S to my computer and it had no issues. iirc, I do not have USB issues in TWRP anymore though... so perhaps 2.3.3.0 did help in that regard. The connection works fine with fastboot so I am pretty sure that there is no hardware issue here.
I was going to try to get S-Off but couldn't get SuperCID to stick; it seems that the RUU I installed write protected that partition because I could do SuperCID before I applied the factory RUU.
I am still able to go back to stock with the factory RUU if I apply the factory recovery and relock.
My hboot now says " Tampered / Relocked / Security Warning " if that means anything.
And finally, I am able to flash CM10 (nightly 8-04) but when I did that I got a boot hang at the spinning CM logo. I did fastboot flash the boot.img from that ROM, but it seems to behave as if the boot.img is still incorrect. I suspect that as with SuperCID, something is locking down my ability to write the correct boot.img. Is there any way to pull the boot.img off after flashing to verify that it was correctly written?
Since I have not been able to get a custom ROM working since I updated to hboot 2.15.0000, I have to think that the hboot is the culprit. At the same time, I don't see why a version of CM10 would have been released that required 2.15.0000 if it had not been tested. It is possible I suppose that I have installed a bogus hboot, as I grabbed it from someone's post (http://forum.xda-developers.com/showthread.php?p=39216236#post39216236).
Click to expand...
Click to collapse
That's a modded HBOOT. Maybe that is the cause of the problems.
You should flash the original HBOOT and reflash OS etc.

khan.orak said:
That's a modded HBOOT. Maybe that is the cause of the problems.
You should flash the original HBOOT and reflash OS etc.
Click to expand...
Click to collapse
The link has both modded and original hboots -- I flashed the original 2.15.0000 version. I'm going to look into downgrading my hboot, but then I won't be able to run the latest kernel so that isn't exactly ideal. It might allow me to run the latest RUU though and get a fresh hboot on there to see if the one I downloaded was borked.

crakarjax said:
The link has both modded and original hboots -- I flashed the original 2.15.0000 version. I'm going to look into downgrading my hboot, but then I won't be able to run the latest kernel so that isn't exactly ideal. It might allow me to run the latest RUU though and get a fresh hboot on there to see if the one I downloaded was borked.
Click to expand...
Click to collapse
That's a fine remedy.
Sent from my HTC One S using Tapatalk 4 Beta

Hmm, so I plugged my phone into USB on my work laptop and the connection dropping doesn't happen. The drivers aren't installed though, so I will have to try this out at home with my other computers.

I finally got S-Off using moonshine for linux -- Unlocked my bootloader, installed android-tools for Centos 6 (I was using x64 but installed the 32 bit package), and ran moonshine. I guess moonshine installed a modded hboot in the process. Installed TWRP 2.3.3.0 afterwards, and then the latest CM10.
*hopefully* since I am S-Off I won't have any sdcard corruption issues or otherwise after future updates. Thanks for the advice and hopefully if someone runs into this situation, they can jump straight to moonshine on linux as a solution.
HOWEVER, CM10 nightly still gets stuck at the cm spinning logo. I'll try an older version (the one I was using prior to this fiasco) and see if it works.
EDIT: the nightly I was using (20130312) isn't available?!? So I guess I will try another.... ok 3-04 nightly works fine, and the boot.img appears to have been correctly installed.

Ok, installed a 3.0 kernel nightly and it does work! So, for some reason the 3.4 kernel versions aren't booting. Not sure where to go from here, as moonshine installed a different hboot in the process and still no love.

Installed a different 3.4 kernel ROM (Illusion) and it works! I guess the problem lies with CM10.1.

Stuck at boot loop???

Hi, i had a S4 which got a broken screen and costs too much to fix a the moment so i brought a Telstra HTC ONE XL off a friend for $100.
I do like the phone but was over the 4.2.1 software as used to the 4.3 on the S4 which i rooted and put on CM10.
I tried with this phone to put on the nightly cm 10.3 but i hit a problem ,when install the nightlies it boot loops and when i try install the stable 10.1 it fails with an error which i do belive is to do with my V2 hboot.
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial
I have unlocked through htcdev and rooted it ok.
Im stuck now though as i pressed backup current original rom which turns out its not.
The phone details are
CID TELST001
Model: HTC ONE XL TELSTRA
If someone can tell where to either find the newest telstra rru for my phone or how to update my hboot so i can use cm10?
My phone is pretty useless at the moment

stueee said:
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
Click to expand...
Click to collapse
Where are you getting CM from (link it) and what is the file named? CM will typically have the phone's code name (EVITA) in the file name. If the code name ENDEAVORU is in the file name, it is in fact for the wrong device, as the ENDEAVORU is for the quad core Tegra3 (non-LTE) version, which is completely different hardware.
Also, I don't know if 10.3 is even released yet for our device, or for the ENDEAVORU for that matter. I think you might be confused about what you are flashing. So again, link what you are trying to install.

The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have. Getting s-off disables the security check which would let you run any Evita RUU but you need to get a ROM to boot first before you try that. You also need SuperCID.
Your best bet is probably to flash an older Sense ROM (4.0 or 4.1), then you can at least boot, and get SuperCID and s-off so you can run the 3.18 RUU to meet the requirements for the latest cm ROMs.
Sent from my Evita

timmaaa said:
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have.
Click to expand...
Click to collapse
For some reason, I got confused and thought the OP was saying that the ROM install was failing. But it clearly says the RUU (or "rru" anyway) failed.
But yes, you can only run an RUU for your carrier version. So you will need s-off to run the AT&T RUU (the RUU referenced in the OP).
But still confused about the mention of CM10.3. From what I can see, it doesn't exist for either our EVITA, or the ENDEAVORU.

Maybe he meant cm10.2 and it was a typo?
Sent from my Evita

timmaaa said:
Maybe he meant cm10.2 and it was a typo?
Click to expand...
Click to collapse
Could be. Although if so, its a type that appears twice.
It seems fairly common for folks to try to install the wrong CM (wrong device). So I want to make sure the OP isn't doing that.

redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.

stueee said:
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
Click to expand...
Click to collapse
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.

Hi Red,
Sorry i typed out that post at almost 1am after pulling my hair out over a few hours and got a little confused.
My hboot is 2.15 and twrp is 2.6.3.0 which I believe is the latest.
What sense rom would work on mine as i really need this working now as i cant find a rom to suit anywhere with my lesser expertees.
I tried changing the cid using the super cid Telstra bat file but it won't recognize the phone as its not loaded, i tried in off state, bootloader, fastboot and twrp but is just keeps saying cant find phone.
I also tried the hex editor method but it didnt seem to update the CID after i completed it without errors.
thanks for you help.
redpoint73 said:
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Click to expand...
Click to collapse

With 2.15 hboot, you cannot modify the files required for supercid.
You can try the ever so risky jet tool. But this tool deliberately bricks to downgrade your hboot.
Sent from my HTC One XL using xda app-developers app

Any recent Sense ROM will suit your current setup, have a look here and you'll find a whole bunch. Unfortunately for you the 2.15 hboot has write protection enabled so there's no way you can get SuperCID (abd therefore can't get s-off), at least not until an exploit is released.
When you tried to flash CM did you also flash the boot.img via fastboot afterwards? You're s-on so that's necessary to get it to boot. Phones on a higher hboot like yours are unable to flash the boot.img through recovery so it must be done manually.
All you do is retrieve the boot.img from the root of the ROM zip, put it in your fastboot folder on your PC, and after you've flashed the ROM in recovery you reboot to bootloader, connect the phone to the PC, open a command prompt from within your fastboot folder (shift + right click anywhere in the folder then select open command prompt here), then give the following command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the ROM.
Sent from my Evita

stueee said:
My hboot is 2.15
Click to expand...
Click to collapse
That's pretty important. This is the reason why the older CM10.1 failed to install. CM was having issues with older hboots, so a script was added to require hboot 2.14.
Once hboot 2.15 came along, folks found that CM failed to install since the install script explicitly requires 2.14. Later versions include hboot 2.15 in the install script.
As exad and timmaaa mention, SuperCID (and therefore s-off) are not possible on hboot 2.15. So you are stuck with s-on (assuming that is what you are on now). It also means you can't currently run any RUU. Reason being, with s-on you can't run older RUUs, RUUs from another carrier, and there are no RUUs based on hboot 2.15. No "current" RUU exists (for your hboot), you can't run "previous" RUUs with the S-on restriction. So therefore you can't currently run any RUU.
But hboot 2.15 will work with newer versions of CM (and other AOSP ROMs which have been recently updated) as well as any Sense ROMs. But with s-on, you need to extract boot.img and flash manually with fastboot every time you install a ROM (as timmaaa points out). If you did not do this, this is why flashing the recent CM10.2 nightly resulted in a bootloop. Failure to falsh boot.img is the most common reason for bootloop after flashing a ROM.

stuck in bootloop
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..

martin-m7 said:
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
Click to expand...
Click to collapse
You're in the wrong forum, buddy. This is the HTC One XL forum.

[Q] Question about HBOOT update with CyanogenMod installed

Recently I had to have my phone JTAGed, because I wanted to update the bootloader. I failed to read about S-ON/S-OFF, and ended up with a brick. When I sent my phone in, I requested that they do the update and install CyanogenMod for me, so that I wouldn't end up with a paperweight again, because obviously I am too impatient.
So after I got my phone back, I noticed that the installed version was a nightly build. No biggie. I went about with this for a little while, until the other day I noticed that a few of my apps were crashing, and I got the idea to update the phone.
Well, already long story short, when I tried to run the update I got the assert failed getprop( ro.bootloader ) error. Someone else said this is because HBOOT isn't the correct version, and lo, it was not.
Ok, now we're to the issue. When the people who JTAGed my phone sent it back, they relocked the bootloader. Can I unlock the bootloader through traditional means, and then attempt the HBOOT update with the RUU? I also asked them to make the phone S-OFF, so hopefully when I unlock the bootloader it will show me that information.
I'm just trying to be sure that I don't brick my phone again. I wouldn't even be bothering with all of this if the OS was on a stable version, but it isn't.
Any help?

You haven't provided your bootloader details. Post them please.
Sent from my Evita

timmaaa said:
You haven't provided your bootloader details. Post them please.
Click to expand...
Click to collapse
Sorry about that.
***LOCKED***
EVITA PVT SHIP S-OFF RL (Guess that answers one question, didn't notice that before)
CID-22222222
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
That's what it says in the bootloader window. Is any more information required?

Just go to htcdev and unlock your bootloader. Then run the 3.18 RUU, that will upgrade your firmware as required by CM. Then just flash TWRP recovery and you're good to go.
Sent from my Evita

Just finished running the 3.18 RUU and I now have the stock ROM running with the updated HBOOT. I also just finished installing the latest TWRP and am downloading the CM ROM now. Thank you so much for your help!

No problems.
Sent from my Evita