Database Info

[Q] Issues with Rogers HTC One X

First off here's what I'm working with:
Rogers HTC One X
Cyanogenmod from http://forum.xda-developers.com/showthread.php?t=2205183
Recovery - TWRP 2.5
Hboot - 2.14
radio - 0.23a.32.09.29
Rooted - I don't think so
SuperCID - 22222222
S-OFF - No
Lock status - Unlocked with HTCDev after SuperCID
Story time:
After deciding to install cyanogenmod on the weekend I've run in to a myriad of issues. I was able to unlock, flash CWM recovery, and install Cyanogen fairly easily, but I ran into the issue where the touch screen doesn't work.
What I've done:
I've found the fix detailed here: http://forum.xda-developers.com/showthread.php?t=2159863, but have been unable to get all the prerequisites going. From the screen fix thread linked above I need to be rooted, s-offed, and superCIDed.
I believe I got the superCID working by following the steps in this post: http://forum.xda-developers.com/showpost.php?p=41482419&postcount=2 and fastboot oem readcid returns 22222222
After that I was unlocked before but locked and relocked with a new unlockcode from htcdev
For rooting, I've looked at the methods listed under Root on http://forum.xda-developers.com/showthread.php?t=1671237, but I'm not too sure where to find which firmware I'm on. That would be the version of cyanogen would it not. I've tried the x-factor method using All-In-One Toolkit from http://forum.xda-developers.com/showthread.php?t=1952426 to no avail, as well as SuperSU from http://forum.xda-developers.com/showthread.php?t=1673935 and this one: http://forum.xda-developers.com/showthread.php?t=1644167, but I don't think any method has worked so far.
In order to use S-Off I'm pretty sure you need to be rooted, so it of course it didn't work, what made me think I wasn't rooted was when I was going through the Facepalm S-Off guide here: http://forum.xda-developers.com/showthread.php?t=2155071 when I ran "adb shell su -c "/data/local/tmp/soffbin3" it would just me the error su: not found, which means your not in as root according to: http://forum.xda-developers.com/showthread.php?p=38278577#post38278577
I've also tried going back to stock using the RUU RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe from http://ruu.androidfiles.org/getdown...9.28L_10.103.32.24L_release_268972_signed.exe, but when I run it I get error 99: Unknown Error, and I if I look in the log it creates it says error 44 HBOOT mismatch. I'm running after relocking, and I've tried just grabbing the rom.zip from %temp%, extracting it and flashing the boot and system imgs, but it says the system.img is too big.
At this point I'd just like to get my phone to work. If I can get it with CM that'd be cool, but stock would be good too. Any help would be appreciated.
Thanks!

In cyanogenmod you have to allow adb root access in developer options.
To ruu without s-off you need to change your cid back to the default but you will brick if you update to 3.18 after. Best to s-off since you changed your cid.
Sent from my Sony Tablet S using xda app-developers app

exad said:
In cyanogenmod you have to allow adb root access in developer options.
Click to expand...
Click to collapse
The touchpad doesn't work in cyanogenmod though, that's the root of the issue
exad said:
To ruu without s-off you need to change your cid back to the default but you will brick if you update to 3.18 after. Best to s-off since you changed your cid.
Click to expand...
Click to collapse
I was trying to RUU before changing CID, but was running in to "FAILED (remote: 44 hboot version check fail)", when running the RUU mentioned in the OP

Ah I see the ruu must have had an older hboot version than the one on your phone. You cant downgrade firmware without s-off.
To fix your issue you will need to flash a sense rom and then s-off and then downgrade your touchscreen firmware. Then you can flash whatever evita rom you like.
Sent from my Sony Tablet S using xda app-developers app

exad said:
Ah I see the ruu must have had an older hboot version than the one on your phone. You cant downgrade firmware without s-off.
To fix your issue you will need to flash a sense rom and then s-off and then downgrade your touchscreen firmware. Then you can flash whatever evita rom you like.
Click to expand...
Click to collapse
Thank you very much!
I flashed the Sense build from http://forum.xda-developers.com/showthread.php?t=2293032 and was then able to S-Off. After that I was able to down grade the touchpad firmware and install cyanogenmod.
Thanks again for pointing me in the right direction
:victory:

[Q] Problem with Custom ICS Rom Installation in My HTC Sensation

I have two HTC Sensation Device ---
1) Locked hboot1.27.XXXX, ICS (From Official OTA), S-ON, Non-rooted
2) Locked hboot1.18.XXXX, GB (As no Official OTA Received for ICS), S-ON, Non-rooted, Orange-United Kingdom
I have successfully unlocked and rooted both the devices with 4EXT Touch Recovery Installed in both the mobiles (Still S-ON for both devices).
Now my Device status are as below:
1) Unlocked hboot1.27.XXXX, ICS (Custom ROM), S-ON, Rooted
2) Unlocked hboot1.18.XXXX, GB (Slightly Customed ROM), S-ON, Rooted
I have tried to install different ICS based custom roms using Smart Flash of 4EXT Recovery with S-ON.
In first device, ROM installation was successful in every try
But in second device, ROM installation failed and boot-loop problem occurred (tried with 5~6 custom ROMS but failed all the time with similar problem). Then I have flashed GB ROM on second device with hboot 1.18.XXXX.
Can anyone answer my following queries, Please--
1) I think, as the custom ROMS requires hboot version 1.27.XXXX+, it failed to flash. Please confirm whether my assumption is ok or not. Please be noted that custom ROMS are flashing my first device with S-ON with ease.
2) Can I upgrade to 1.27.XXXX hboot version without S-OFF?
3) Can I flash/push by hboot.img through (fastboot flash hboot hboot.img) command with version 1.27.XXXX? If yes, can anyone provide me a proper link to download that hboot.img file?
4) Can anyone provide me download link for RUU so that I can update my hboot version by official ICS ROM (Orange, United Kingdom)
5) Can anyone suggest any better method to install custom ROMS with S-ON?
6) Can anyone suggest me how to S-OFF easily (I have tried Revolutionary.exe, but this program never opens in my PC although I have the beta Key)?
7) With S-OFF, will the problem will be solved with hboot version 1.18.XXXX? If not, please suggest...
I would be really happy if my problem is solved by any of yours' help

in the first device you completely fine:good:
in the second one indeed you need to S-OFF in order to upgrade firmware to ics(will upgrade also your hboot version)
that's why the device is bootlooping(not running in gb firmware)
you mentioned that you tried revolutionary method and it didn't work
so try this guide
http://forum.xda-developers.com/showthread.php?t=1672425
search for the correct ruu.exe
by the way what kind of problem do you face with revolutionary method?

RE:
rzr86 said:
in the first device you completely fine:good:
in the second one indeed you need to S-OFF in order to upgrade firmware to ics(will upgrade also your hboot version)
that's why the device is bootlooping(not running in gb firmware)
you mentioned that you tried revolutionary method and it didn't work
so try this guide
http://forum.xda-developers.com/showthread.php?t=1672425
search for the correct ruu.exe
by the way what kind of problem do you face with revolutionary method?
Click to expand...
Click to collapse
In fact revolutionary.exe is being crashed whenever I tried to open it either in Windows XP (Office Laptop) or in Windows 7 (Home PC). So, I have failed to use this tool. Can u suggest any idea?

If you can't use revolutionary for s-off, then your only hope is RUU.EXE on your PC.
Sent from my HTC Sensation

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.

I'm seriously stuck!!!

Hi all I need help!!!
My HTC OneXL is unlocked bootloader
Android Version ICS
I dont know which firmware I am running (Rogers One X)
PVT SHIP S-ON RL
HBOOT 1.09
I installed TWRP successfully but I can not install roms!
Please help!

bobyum said:
Hi all I need help!!!
My HTC OneXL is unlocked bootloader
Android Version ICS
I dont know which firmware I am running (Rogers One X)
PVT SHIP S-ON RL
HBOOT 1.09
I installed TWRP successfully but I can not install roms!
Please help!
Click to expand...
Click to collapse
you have to flash the boot.img of a rom if you are s-on
must also be rooted.
1. plug phone into pc
2. mount sdcard in twrp
3. copy rom to your computer
4. extract boot.img
5. reboot to bootloader (also done in twrp)
6. highlight "fastboot" and press power and the phone should say "Fastboot USB"
7. open a command promt (type cmd into search box on windows7) and cd to your adb/fastboot folder
8. type
Code:
fastboot flash boot boot.img
9. reboot to recovery and install your rom
10. reboot system when done
if you arent rooted, use the toolkit in the development area and root.

What ROM are you trying to install? If it's any recent aosp your current hboot version is the problem. All current aosp ROMs require the 2.14 hboot which you can get by running the 3.18 RUU. S-off is highly recommended, if you run a jb RUU with SuperCID and s-on your phone will brick.
Sent from my Evita

I am trying to get cm10.2. so should my first step right now be getting the 3.18 RUU or getting s-off?

Ok, first, please read the instructions of any ROM you're going to flash, it's stated very clearly in the cm10.2 thread that an update is needed before flashing the ROM. One of the most important rules of XDA is to search before posting, proper searching limits the amount of unnecessary threads.
Get s-off first, if you don't already have SuperCID you will need that in order to get s-off. Use the hex edit method to get SuperCID, then you can get s-off in the Facepalm S-off thread. Your best bet to go through this process is to temporarily flash a Sense ROM, any Sense 4 Android 4.1 ROM should be fine. Once all that's done you can run the 3.18 RUU, then flash TWRP recovery again and flash CM.
Sent from my Evita

S Off dude. Read what @timmaaa said.
Sent from my One X using XDA Premium 4 mobile app

thanks timmaaa!!! I need to head out right now but will try it asap! I apologize for not searching before asking but my phone was stuck on ICS and I thought it would be hopeless to install a custom rom.

got super cid and soff!
ok i got both super cid and soff. so my next step is to flash a sense 4.1 rom correct? any suggestions?
edit: i downloaded RageXL so do i just flash in twrp?

No you don't need to do that, I meant you should try a 4.1 ROM in order to get s-off. If you have SuperCID and s-off now you can go ahead and run the RUU.
Sent from my Evita

bobyum said:
I apologize for not searching before asking but my phone was stuck on ICS and I thought it would be hopeless to install a custom rom.
Click to expand...
Click to collapse
Not sure how you got that notion. Its actually a bit easier to mod older firmware versions, due to the fact that HTC keeps plugging the various exploits with successive (newer) firmware builds.
There is currently no firmware version for this device that would leave you "stuck" not being able to flash custom ROMs.

from maximus hd to cyanogenmod 11

hi guys, i was undecided about the rom. im on maximus hd now but i want also kitkat, and so install the last snapshot (the monthly cyanogenmod release). what do you think? and what i have to do now for install it? i wnat to go back to 2.15 hboot, please help me

Anyone?
Sent from my HTC One S using XDA Premium 4 mobile app

no one can help me?

Maybe this can help you to go back to hboot 2.15.
For CM follow the instructions in the first post of this thread.
The latest snapshot can be found here. GAPPS can be found e.g. here or here.

I'm a bit confused.
Currently on Hboot 2.16 , S-Off, TWRP 2.8.0.1 and maxumiusHD.
Can I install official CM 10.2?

CaptainMaki said:
I'm a bit confused.
Currently on Hboot 2.16 , S-Off, TWRP 2.8.0.1 and maxumiusHD.
Can I install official CM 10.2?
Click to expand...
Click to collapse
CM 10.2 doesn't support hboot 2.16. BTW using the search function doesn't hurt.

Flippy498 said:
CM 10.2 doesn't support hboot 2.16. BTW using the search function doesn't hurt.
Click to expand...
Click to collapse
We want to go back to 2.15
Sent from my HTC One S using XDA Premium 4 mobile app

Yeah, I understood that. All you got to do is following the instructions in the first link I posted in my first answer. ?

in an italian forum i have see that i can flash the hboot for downgrade, without installing the RUU.. here the link if you understand something http://www.androidiani.com/forum/ht.../354323-guida-s4-upgrade-downgrade-hboot.html
so what i have to do?

djinn0 said:
in an italian forum i have see that i can flash the hboot for downgrade, without installing the RUU.. here the link if you understand something http://www.androidiani.com/forum/ht.../354323-guida-s4-upgrade-downgrade-hboot.html
so what i have to do?
Click to expand...
Click to collapse
Well, I've always been using a RUU if I wanted to downgrade so I don't know which way is the best. All I can say is that I never had any problems with downgrading by using RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe and the CID HTC__102. Maybe it's not the fastest way (you need to upgrade by official OTA's afterwards to get hboot 2.15) but it works.

I have to change the cid for return to 2.15?
Sent from my HTC One S using XDA Premium 4 mobile app

djinn0 said:
I have to change the cid for return to 2.15?
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you use RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1 .06es.50.02.31_10.09a.50.04L_release_275655_signed.exe for downgrading then yes. Otherwise you'll brick your phone by installing the official OTA's while you are on CID 11111111.

So first installing the RUU then return to my cid? And then i can install cm?
Sent from my HTC One S using XDA Premium 4 mobile app

1. Return to your CID (in my case HTC__102)
2. Use the corresponding RUU (in my case RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1 .06es.50.02.31_10.09a.50.04L_release_275655_signed.exe; your Phone has to be in fastboot USB mode; maybe you have to relock your bootloader)
3. Install official OTA's to get from ICS to JB with hboot 2.15 (with CID 11111111 this step will brick your phone)
4. Unlock bootloader if needed
5. Return to Super CID if you want (actually not needed since you only need it for facepalm s-off as far as I know)
6. Flash TWRP/CWM (I prefer TWRP)
7. Flash latest CM snapshot
8. Flash GAPPS
9. Enjoy
It's not the fastest way but I never had problems as the 3G loss that is mentioned in some threads. More or less these are the same steps that are mentioned in the link I posted in my first answer.

And If i install the jb ruu?
Sent from my HTC One S using XDA Premium 4 mobile app

I've never used any other RUU than the one I mentioned above. So I don't know whether a JB RUU can brick your phone while you are on Super CID. Nevertheless the steps you need to do are the same with a JB RUU except that you can leave out the installation of the original OTA's.

Flippy498 said:
I've never used any other RUU than the one I mentioned above. So I don't know whether a JB RUU can brick your phone while you are on Super CID. Nevertheless the steps you need to do are the same with a JB RUU except that you can leave out the installation of the original OTA's.
Click to expand...
Click to collapse
i have sucessfully installed the ICS RUU but now my bootloader is 1.14 not 2.15... it automatically get updated with the jb OTA?

Flippy498 said:
1. Return to your CID (in my case HTC__102)
2. Use the corresponding RUU (in my case RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1 .06es.50.02.31_10.09a.50.04L_release_275655_signed.exe; your Phone has to be in fastboot USB mode; maybe you have to relock your bootloader)
3. Install official OTA's to get from ICS to JB with hboot 2.15 (with CID 11111111 this step will brick your phone)
4. Unlock bootloader if needed
5. Return to Super CID if you want (actually not needed since you only need it for facepalm s-off as far as I know)
6. Flash TWRP/CWM (I prefer TWRP)
7. Flash latest CM snapshot
8. Flash GAPPS
9. Enjoy
Click to expand...
Click to collapse
See step 3. Just download them via "About" -> "Software updates" in the system menu.