Database Info

Installing RUU for HTC One XL (Telstra Branded)

Hi Guys.
I wanted to confrim if I can install any RUU on my HTC One XL with out unlocking the Bootloader or rooting or supercid.
Because in most forums i have had a look at they dont mention if its needed.
In this case i wanted to install the RUU EVITA hTC Asia WWE 2.23.707.2 and wanted to know if its required to perform the above to install the RUU.
Regards

Ruus have 3 simple rules.
1. Bootloader must be locked.
2. Cid must match. Eg WWE is not the same cid as Telstra. You need to supercid or atleast change to Telstra cid.
3. You can not downgrade hboot. The ruu must be equal or newer than your current version.
Point 2 is where you will need root.

gondwn said:
Hi Guys.
I wanted to confrim if I can install any RUU on my HTC One XL with out unlocking the Bootloader or rooting or supercid.
Because in most forums i have had a look at they dont mention if its needed.
In this case i wanted to install the RUU EVITA hTC Asia WWE 2.23.707.2 and wanted to know if its required to perform the above to install the RUU.
Regards
Click to expand...
Click to collapse
The Telstra One XL is currently Bootloader unlockable through htcdev unlike the AT&T One X. This means that we don't have to mess around to get a ROM onto our device. Why you would go to all the trouble of rooting and changing your cid (Which sometimes I've read can wipe out your IMEI and Serial Number?) when you just just unlock your bootloader, flash a recovery and then install any ROM you want.

Thanks guys for your help

I am stuck in a cm10 boot loop. Never got çm sucessufulky flashed. Was on stock deodexed rom prior to attempting cm.
I can get to twrp 2.2.0 recovery and to recovery as well but don't have a backup to flash from twrp.
I was thinking of going back to ruu 1.8.5 but my bootloader is unlocked using HTC Dev.
Any suggestions?
[QUOTE=twistedddx;30840704]Ruus have 3 simple rules.
1. Bootloader must be locked.
2. Cid must match. Eg WWE is not the same cid as Telstra. You need to supercid or atleast change to Telstra cid.
3. You can not downgrade hboot. The ruu must be equal or newer than your current version.
Point 2 is where you will need root.[/QUOTE]

Grab another rom and flash it. Try nocturnals telstra rom and see what you think.
It will be a lot easier than heading back to stock via ruu
Sent from my HTC One XL using xda app-developers app

w0tha said:
Grab another rom and flash it. Try nocturnals telstra rom and see what you think.
It will be a lot easier than heading back to stock via ruu
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
how do you flash another rom though without being able to put it on your sd card first? is there a command you can put in command prompt so that the zip shows up in recovery?

from twrp recovery, you can connect the USB and mount SDCard
then connect to computer and copy over the rom
otherwise, you could use adb commands
adb devices (make sure device exists)
adb shell
mount sdcard
Then either
adb push ROM.zip \sdcard\
or copy

AT&T ONE X
Hi,
I have an AT&T one X and i see that i cant use tethered WiFi, I dont use the phone in the USA but here in NZL, is there some way to get around this ? I cant stand the ATT rubbish they put on the phone so im looking for a unbraded rom, but Id prefer a rom which is factory rather than a custom built.
Could someone please point me in the right direction
Thanks in advance
G

gymmy said:
Hi,
I have an AT&T one X and i see that i cant use tethered WiFi, I dont use the phone in the USA but here in NZL, is there some way to get around this ? I cant stand the ATT rubbish they put on the phone so im looking for a unbraded rom, but Id prefer a rom which is factory rather than a custom built.
Could someone please point me in the right direction
Thanks in advance
G
Click to expand...
Click to collapse
Any of the stock rooted ROMs in Development except AT&T ones have WiFi tethering enabled. You of course need to be bootloader unlocked and custom recovery.

redpoint73 said:
Any of the stock rooted ROMs in Development except AT&T ones have WiFi tethering enabled. You of course need to be bootloader unlocked and custom recovery.
Click to expand...
Click to collapse
I was trying to avoid loading a custom recovery, its not that i dont trust the kind folk on here, but lets face it , it wouldnt take much to have my phone upload its contents to a dev, just call me paranoid hahahaa, so do i have to use an ATT rom ? i really would like to unbrand it also
G

[Q] HBOOT 2.14.0000 Softbrick & no stock RUU

Hey Guys,
So yesterday I decided I wanted to root my HTC One X (Rogers Canada Unlocked) so I followed the tutorials and unlocked the bootloader and went to install CWM recovery. I flashed it via fastboot, then when I restarted into recovery I was in a bootloop saying that this is for development purposes only, and it just kept restarting. So I booted back in to fastboot mode and installed TWRP 3.0.0.0 but the touch controls didnt work, so I reflashed TWRP 3.0.0.1 and the recovery was accessible. I tried to flash a rom and it said it succeeded but it just keeps going into that bootloop and there is no sign of the old stock ROM on the device at all. So I decided today to relock the bootloader, clear the cache and find a Rogers RUU to flash back on the phone with ARUwizard. It fails to install because of a conflict with my bootloader (obviously because mine is 2.14.000) but there is nowhere on the world wide web that has an updated Rogers RUU to flash to my phone. The only good thing that came out of it, is it just stays on the HTC splash screen and doesn't have the red development purposes only writing. I need some help, thanks in advance. If there is anything I missed please let me know.
Phone: HTC One X (Rogers Canada Unlocked) Evita
Bootloader Relocked, S-ON, Hboot 2.14.000
Secondary: HTC Incredible S (Vigin Mobile Canada)
Bootloader Unlocked, S-OFF, C10 ROM

RUU I have found in the past to be more difficult than the root process. make sure drivers installed and usb plugged into the back of pc.
CMW probably corrupt your SD card btw.
Use twrp. And looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1

The problem is that there is no Rogers RUU for the latest hboot (2.14) that the OP is on. For some reason (that I've never completely understood) Rogers firmwares often don't have corresponding RUUs ever released. And he can't use an old RUU, as it fails version check (you can't run an RUU for a firmware version and/or hboot older than what is on the phone). Maybe they will release a Rogers RUU for the firmware that goes with 2.14. But it wouldn't surprise me if they never do.
The TWRP versions mentioned in the OP look wrong. The newest TWRP version is 2.3.3.1, and is supposed to be compatible with 2.14 (although I think some are still having some troubles). I'd start there, by re-unlocking and installing the latest TWRP:
http://forum.xda-developers.com/showthread.php?t=1677447
DvineLord posted the recovery img in Post 432.

If the OTA file is a complete zip, with hboot, sbl images, etc. It can be used as an RUU, but it isn't an automated process. as long as you install TWRP, and then install a ROM/kernel, your phone will work again
jjswain, if you need to RUU, find the complete zip OTA package, and follow the steps here http://forum.xda-developers.com/showthread.php?t=1974272
The same can be done in windows, start at step 9

subarudroid said:
looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.

veemodz823 said:
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.
Click to expand...
Click to collapse
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now

jjswain said:
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now
Click to expand...
Click to collapse
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.

This sounds very similar to the situation I'm in. People have said the reason why there is no touch is because of 3.17 blah blah blah. If you want to read up on where I'm at, here's the link. We're pretty much in the same boat bro.
http://forum.xda-developers.com/showthread.php?t=2102729

absolutelygrim said:
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.
Click to expand...
Click to collapse
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue

jjswain said:
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue
Click to expand...
Click to collapse
You have to downgrade your hboot to ruu downgrade to get the old firmware

absolutelygrim said:
You have to downgrade your hboot to ruu downgrade to get the old firmware
Click to expand...
Click to collapse
I could use this rom correct? Its based on 3.17
http://forum.xda-developers.com/showthread.php?t=2075783

Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte

Search for TWRP for the HTC One X Evita (the north American model of the HTC one x) and make sure that the version is 2.3.3.1.
Then install Viper XL by Team Venom.
When installing the rom wipe everything that TWRP will let you wipe, then mount the phone as USB storage put the ZIP file on the phone, and then flash it.
If that doesn't work I dunno what will.
---------- Post added at 06:28 PM ---------- Previous post was at 06:17 PM ----------
So first you need to flash TWRP for HTC One X evita, you are going to need version 2.3.3.1.
Boot into the new recovery and wipe everything, SD Card, System everything.
Then download Viper XL by Team Venom, go to the mount menu, make sure everything is unchecked, and mount the phone as USB storage and put the rom on the phone.
Flash the rom and you now have a working phone.

jjswain said:
Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte
Click to expand...
Click to collapse
This depends on the network icon set that was flashed with the rom you chose. For some roms, the values are as follows:
E - Extended network
3G - 3G
H - 4G
4G - LTE
On other icon sets, the last one is replaced by LTE - LTE. Some roms will actually let you install/use different network icons, so you could always take a look into something like that.

^what he said ^ also you can go to dialer and *#*#info#*#* go to phone info and see what network your connected to.
Sent from my HOX w/CM10.1

I'm somewhat in the same position as the OP, but every RUU or rom I try fails at signature check (although the latest one posted above seemed to work but then nothing at bootup). Being that I have stock CID ROGER001, and the same HBOOT 2.14 Evita, Radio .23a.32.09.29 and S-ON, is hoping a Rogers RUU is released my only option?
Well given my specs above I can confirm that the Hatka rom works (insofar as it has booted up and I have a phone again!!) Thank you so much for the link jjswain!!

you will only be able to downgrade if you s-off. i assume you are unlocked with twrp or the new cwm flashed if so as long as you wipe first you should be able to flash roms fine unless you are trying to flash non-evita roms for some reason. which roms have you tried flashing and what version of recovery are you using?

So... I had an awkward moment where I began looking at all the roms and seeing that they were all for a OneX not OneXL...:silly: Thanks for asking me to go through those as I probably would not have realized my mistake! Just flashed Viper3.2.6XL and I'm much happier with the look and feel.

I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?

mcnaught82 said:
I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?
Click to expand...
Click to collapse
You can't root now. There is no root method for jelly bean yet.
Sent from my Nexus 7 using Tapatalk HD

[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] Can not get any Rom or Ruu to flash my soft bricked device

New to HTC One S.
Device Sim unlocked but branded Bell Mobility, was running 4.1.1 hboot 2.15 Dev Unlocked and I am able to use fastboot to push boot images and recovery images. I am able to mount the internal SD to my computer and copy zips. However nothing will flash. Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
P.S. when I flashed the boot images for the rom it honestly wiped my internal SD and I lost my nandroid... wishing I had copied it to my computer.
Open to advice! thanks!
WiL

citats said:
New to HTC One S.
Device Sim unlocked but branded Bell Mobility, was running 4.1.1 hboot 2.15 Dev Unlocked and I am able to use fastboot to push boot images and recovery images. I am able to mount the internal SD to my computer and copy zips. However nothing will flash. Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
P.S. when I flashed the boot images for the rom it honestly wiped my internal SD and I lost my nandroid... wishing I had copied it to my computer.
Open to advice! thanks!
WiL
Click to expand...
Click to collapse
Have you tried flashing with an older version of twrp
Verstuurd van mijn HTC One S met Tapatalk

citats said:
New to HTC One S.
Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
Click to expand...
Click to collapse
Use 2.3.3.0 instead...

Thanks guys, I have actually tried 2.3.3.0 due to reading that in another thread. What I see is I can get various aroma installers to start, but at the actual install they seem to fail gaining access to areas on the phone. It's worth mentioning that I have reflashed stock boot img and stock recovery, relocked and attempted various RUU's but I understand that the hboot at 2.15 is most likely why that method fails.
I'm unlocked again but I think I'm going to try reflash stock recovery relock clear and reset all storage etc. then unlock use twrp and re-attempt a flash.
Any suggestions on a rom that should'nt have issues with hboot 2.15?

To flash RUUs you need to be on stock recovery, not custom.
2.15 came with JB. Trickdroid or ViperOneS would be sense roms, else you could flash CM 10.1 or derivates (AOSP/AOKP).
As long as you flash the according kernels in fastboot mode you can also use ICS roms. That doesn't matter.
--- edit
as with 2.15 you could only flash the 3.16 RUU which still isn't available (the one here is for ONE S SE and exits with errors. To flash earlier RUUs you will need an earlier bootloader version. There are two ways: To downgrade bootloader or s-off. As downgrading is a pain you should think about s-off.

Thank You
Yes I was on stock recovery and stock boot img and relocked during that attempt.
does the hboot version matter?
(based upon what I have read it won't flash if my hboot is newer)

Ok, just answered this as edit while you posted. lol

Thank You again!
I have looked into downgrading and a pain might be an understatement I'm looking into the One S toolkit to see what i can do for me... Here's hoping the RUU with hboot 2.15 gets leaked soon.

Let me pm you with a few useful links for a s-off device this evening (Germany, UTC +1) as it's 5:45 in the morning here and I've got to go to work now... :laugh:

rootrider said:
Let me pm you with a few useful links for a s-off device this evening (Germany, UTC +1) as it's 5:45 in the morning here and I've got to go to work now... :laugh:
Click to expand...
Click to collapse
OK that would be great thanks!
WiL

Holy crap that was painful...
I once again have a rom running! I did so many things but in the end I pushed Energy Rom to the device and it's boot.img after wiping multiple times reformating. Energy Rom is the only one that would complete install without write errors. Very strange stuff but for now i am happy.
Thanks again man!

Damn, I searched this thread for 20 minutes... :cyclops:
Which recovery are you using?
Anyway you should better use TWRP <= 2.3.3.0 for flashing roms.
(gonna write your pm now, will take some time and sorry for the delay!)

I'm all good now. Running Venom and very happy. I appreciate your efforts.
The recovery question tho I had to swap back and forth between twrp 2.3.3.0 and the most recent cwm. Mainly because of I could only send adb via twrp and I could only use adb shell with cwm, the nightmare is over!
Sent from my HTC One S using xda app-developers app

At&t Htc One X 4.2.2 Root

Help im new!
Soo i recently got my htc one x on android jelly bean 4.2.2 from at&t and is there a method or easy root method for this version? 4.2.2, with 5.18? I really want to try and root my phone but i know nothing about messing with all these types of files, and i dont want to risk destroying my phone.
Im not sure if there is already a post or something about this and if it is im sorry, these forums are a bit overwhelming and i am new.
I would very much appeircate any help or info on being able to easily root my htc one x 4.2.2, 5.18 at&t white.

The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita

timmaaa said:
The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita
Click to expand...
Click to collapse
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.

There is a perfectly easy way to unlock your bootloader on the 3.18 software, it isn't a stupid phone, nor is the exploit hard to achieve, hundreds if not thousands of people have done it. It's as simple as entering a few adb/fastboot commands.
You can't root on 5.18 because the update patched the weakness that was exploited in the 3.18 software/firmware. It takes time for devs to crack these things and the update has only just been released. It's not even sure whether the devs will want to spend any time finding a crack for a phone that's relatively old now. This is why you never take an update without first unlocking/rooting, unless you're comfortable with the fact that you won't be able to (it is a well established fact that updates patch exploits).
Sent from my Evita

5.18!to 3.18 ruu
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?

brenntard said:
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?
Click to expand...
Click to collapse
Bootloader details please.
Sent from my Evita

timmaaa said:
Bootloader details please.
Sent from my Evita
Click to expand...
Click to collapse
Tampered
Relocked
Evita put ship s-on rl
Hboot-2.18.0000
Radio-1.35a.32.45.27
Opendsp-v33.1.0.45.1128
Emmc-boot
It's weird, I tried using the all in one toolkit and was able to unlock the boot loader, get twrp recovery working and flash supersu. The only problem I ran into was when I opened supersu it said the binaries need to update. The first time I updated them and it was fine then the phone shut off and supersu would always need updated when opened...I downloaded titanium backup and was able to get root access before my phone restarted and I had to update supersu again... It is now relocked, obviously, but easy enough to unlock again using the toolkit

You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita

timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Yes it says me CID is 11111111. Why would supersu be acting so funny and constantly telling me to update the binaries...supersu seems relatively useless at this point. do i need supersu to flash a custom ROM?

Forever95 said:
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.
Click to expand...
Click to collapse
Lack of research. A working root method exists for 3.18, both a "manual" method and two "Toolkits" for those that can't handle the manual method.
Also, you should never never never install an OTA update unless you know what has been patched, changed, etc. Updates frequently will patch existing root exploits, and therefore leaving you in the spot you find yourself in.
Other devices (such as the One) can be rooted with later firmware, simply because that device has more developer interest. It requires the right talented developer(s) putting in the time and effort to find the exploit method. Its still possible on this device with 5.18. All it takes is the right guy and the proper amount of motivation. But as the device is getting older, and devs are moving to other phones, those chances do get more unlikely.

UPDATE!
timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for the help. i know officially have an s-off device that is unlocked and rooted ready to run custom ROMS.
My next question would be how do i flash a kernel and why would i flash a kernel?

cant flash ROM
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?

brenntard said:
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?
Click to expand...
Click to collapse
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.

timmaaa said:
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.
Click to expand...
Click to collapse
That sounds easy enough.. I was able to gain s-off through the face palm method earlier today so now i just need to flash the 2.15 firmware. in the thread it says to "make sure you flash your current ROM's boot.img after" is this necessary if i am using the stock 4.2.2 sense 5 ROM already, does the download include the radio? do i need a different radio?

The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita

timmaaa said:
The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita
Click to expand...
Click to collapse
awesome! im gonna try that tonight.

Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita

timmaaa said:
Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for your help! i succesfully flashed the firmware and amnow running CM10.2.1. If i want to flash a 4.4 ROM do i need a different recovery? im currently using 2.5.0.0

Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita

timmaaa said:
Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
Click to expand...
Click to collapse
I guess the all in one toolkit hasn't had an update in a while...
thanks again for all the help, really appreciated
i have been working to get a custom rom on my device for roughly a month now and today was the day it finally happened
glad to say i learned a lot thanks to help from people like you in this great forum