att htc one x
carrier unlocked (straight talk now)
perma root
super cid
TWRP Recovery 2.4.1.0
custom rom: viperxl 3.2.6
EVITA PVT SHIP S_OFF RL
Hboot ver 1.14.0002
radio ver 0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
eMMc-boot
jun 11 2012, 14:36:28
1) carrier unlocked for straight talk.
2) unlocked bootloader with att all in one tool kit.
2.a) this tool will get identifier token, change cid, unlock bootloader,
2.b) [TOOL] HTC One X (Evita) All-In-One Toolkit V2.1.1 [2-1-2013] [PERM ROOT][Noob-Proof]
http://forum.xda-developers.com/showthread.php?t=1952426
3) installed TWRP 2.4.1.0 via tool kit
4) installed Superuser via tool kit
5) nandriod backup via TWRP
6) gained S-Off using Facepalm
6.a) [S-Off] Facepalm S-Off for HTC One XL
http://forum.xda-developers.com/showthread.php?t=2155071
anyone else have issues unlocking S-ON?
I have the solution. HTC says it cant be done by them. At&t says it cant be done by them. both say unless it came S-OFF it is not possible. I beg to differ but it was not an easy task.I could not get the S-OFF by using facepalm, untill i had installed viperxl rom. it would not work on stock rom, only after viperxl install. I tried like 12 times, suprisingly enough my phone never bricked. but to get viperxl installed i had to flash the boot.img file via adb command line (extracted from rom, or avail on thread above) then go immediately to recovery and install the rom without reboot, wiping the cache and delvik once install is complete. then reboot. once viperxl stabilizes and setup is complete, reboot to recovery, nandriod BU, then follow the facepalm instructions.
In no way is this thread to be misconstrewed as taking any credit for any development of any references here, they are solely references that i used to achieve the desired effect on my device. this is an instructional on how i performed these functions on my phone. I would like to thank all the developers that have made this possible.
I have no idea what you're asking
Sent from my VENOMized HoxL
area51avenger said:
I have no idea what you're asking
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
was not asking anything. Simply providing information.
Just a heads up you don't need to sim unlock a AT&T phone to use it on Straight talk if you're using there AT&T network sim. If you're using AT&T phone on ST with Tmobile network sim then you do need to Sim unlock it.
bpear96 said:
Just a heads up you don't need to sim unlock a AT&T phone do use it on Straight talk if your using there AT&T network sim. If you using AT&T phone on ST with Tmobile network sim then you do.
Click to expand...
Click to collapse
Had lots of issues changing carrier, including blacklisted imei. as far as that part goes I followed ST support instructions.
Later come to find out that ST is a devision of att. Same network and all. Just different apn's. a ST sim will not prompt for unlock pin to change carriers. I had to borrow one from Verizon. only to find out later that I didn't need to c_unlock the device at all. Yaay. Me.
delete
delete this post please, not the thread just this post. thank you
sphynx.0029 said:
att htc one x
carrier unlocked (straight talk now)
perma root
super cid
TWRP Recovery 2.4.1.0
custom rom: viperxl 3.2.6
EVITA PVT SHIP S_OFF RL
Hboot ver 1.14.0002
radio ver 0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
eMMc-boot
jun 11 2012, 14:36:28
1) carrier unlocked for straight talk.
2) unlocked bootloader with att all in one tool kit.
2.a) this tool will get identifier token, change cid, unlock bootloader,
2.b) [TOOL] HTC One X (Evita) All-In-One Toolkit V2.1.1 [2-1-2013] [PERM ROOT][Noob-Proof]
http://forum.xda-developers.com/showthread.php?t=1952426
3) installed TWRP 2.4.1.0 via tool kit
4) installed Superuser via tool kit
5) nandriod backup via TWRP
6) gained S-Off using Facepalm
6.a) [S-Off] Facepalm S-Off for HTC One XL
http://forum.xda-developers.com/showthread.php?t=2155071
anyone else have issues unlocking S-ON?
I have the solution. HTC says it cant be done by them. At&t says it cant be done by them. both say unless it came S-OFF it is not possible. I beg to differ but it was not an easy task.I could not get the S-OFF by using facepalm, untill i had installed viperxl rom. it would not work on stock rom, only after viperxl install. I tried like 12 times, suprisingly enough my phone never bricked. but to get viperxl installed i had to flash the boot.img file via adb command line (extracted from rom, or avail on thread above) then go immediately to recovery and install the rom without reboot, wiping the cache and delvik once install is complete. then reboot. once viperxl stabilizes and setup is complete, reboot to recovery, nandriod BU, then follow the facepalm instructions.
In no way is this thread to be misconstrewed as taking any credit for any development of any references here, they are solely references that i used to achieve the desired effect on my device. this is an instructional on how i performed these functions on my phone. I would like to thank all the developers that have made this possible.
Click to expand...
Click to collapse
Can you help me by telling which Viper Rom you have used for this. I am having problems in S-OFF . Running same as ur version
harismahesh said:
Can you help me by telling which Viper Rom you have used for this. I am having problems in S-OFF . Running same as ur version
Click to expand...
Click to collapse
Which part of the s-off process are you having problems with? Are you able to post the text from the command prompt on a failed attempt? That will make diagnosing the problem a lot easier.
Sent from my Evita
Sure,
While running - fastboot flash zip PJ8312000-OneX.zip
I am getting 99 unknown fail.
sending 'zip' (36064 KB)...
OKAY [ 2.873s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.126s
Ok, when you get error 99 force a reboot back into bootloader by holding volume down and power together. When it reaches bootloader start again from the beginning, you should now get error 92. You do have SuperCID right?
Sent from my Evita
Related
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
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:
I have a phone that I got which was locked to Telus, the root was messed up. I want to flash a RUU so I can update to the latest OS. I get that "developer red text" with the HTC logo in recovery.
- RUU_Evita_UL_TELUS_WWE_1.91.661.4_Radio_0.18a.32.09.01_2_10.94.32.20L_release_266645_signed.exe
is that the correct file?
What it says on my phone:
***TAMPERED***
***RELOCKED***
***Security Warning***
Evita PVT SHIP S-ON RL
HBOOT-1.11.0000
RADIO-0.18a 32.09.01_2
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7 2012,13:10:34
fastboot getvar version-main
version-main: 1.91.661.4
finished. total time: 0.000s
Also since my phone is on Fido(I got a sim unlock) I get no data. Could I flash to a Rogers RUU? Because Rogers and Fido are literally the same company, I got Rogers connection all the time on my iPhone. Would this work or would it mess everything up?
- RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe
Thanks
Those "tampered"and "unlocked" messages in bootloader are completely normal. That means you can now flash a custom recovery, and then from that recovery you can flash a custom ROM.
If you want to RUU for some reason, you'll probably want to s-off first. If you have SuperCID and are s-on, running an RUU could brick your phone.
Sent from my Evita
My phone isn't rooted, I tried to flash a recovery file but that's when it messed up. I get the HTC logo and red text that says "This build is for development purposes only do not distribute outside of HTC without HTC's permission".
I cant get to the CWM from recovery. I also cant upgrade my OS from the phone itself I get that red text error and its just frozen there until I reboot the phone.
I relocked the bootloader and it now has a security warning thing.
***TAMPERED***
***RELOCKED***
***Security Warning***
Evita PVT SHIP S-ON RL
HBOOT-1.11.0000
RADIO-0.18a 32.09.01_2
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7 2012,13:10:34
edit.
The security warning thing went away now but I ran:
fastboot getvar cid
and got cid: TELUS001
Could I flash the Telus RUU now? Also if I got SuperCID and S-Off could I flash the Rogers RUU? Would that even give me data back?
Your CID is fine, and because you have relocked your bootloader you should be ok to run the RUU.
Have you triple checked that your apn settings are correct? That's usually the cause of a loss of data.
Sent from my Evita
No I didn't set that up yet haha that would be the reason why. Just did and it works now!
I'm going to wait for my phone to charge up some more before it run the RUU. Hopefully all goes well, and I can actually get my device properly rooted..
Thank you for your help
Running the RUU won't really help the rooting process. You could just unlock your bootloader again and flash a recovery. Just make sure it's a recovery for this device (Evita) because that may be where you went wrong in the first place.
Sent from my Evita
Alright I downloaded the HTC One X(evita) All-In-One Toolkit
I will follow the steps on there
Do I have to do the Xfactor and MotoChopper steps?
Do you still have the unlock.bin from when you unlocked your phone the first time? It should still work.
Sent from my Evita
Yes I still have the email from HTC and I made a backup of the file as well
I just used that toolkit and went right to the unlock bootloader.
In the bootloader it is now
***Tampered***
***Unlocked***
I flashed TWRP 2.5.0.0 and put the SU files in my main directory
Worked!! Flashed the SU file and phone booted up properly now
You should be able to use it again to unlock your bootloader. Just go back to htcdev and do the last part where you enter the unlock.bin.
Then I recommend flashing TWRP 2.6 recovery from here.
Sent from my Evita
Should I just reflash 2.6 instead then? Do I have to remove anything or can I just flash over top?
Also I'm on 4.0.3 should I update the OS and then flash 2.6?
You can't flash TWRP until you've unlocked your bootloader, so do that first. Then flash TWRP by using the following fastboot commands:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
fastboot erase cache
fastboot reboot-bootloader
Now you can either flash a superuser zip to have root on the stock ROM. Or you can flash a custom ROM.
Sent from my Evita
I got it all to work using the toolkit. I have superuser on my phone now. But I used the 2.5.0.0 file instead.
Do you think its wiser to update my OS and then reflash to 2.6.0.0?
You don't need to update the os, you can flash any ROM you like once you have the correct recovery installed. Just make sure you flash TWRP 2.6, because 2.5 has major bugs.
Sent from my Evita
Alright I flashed 2.6.0.0 now. Is there any custom ROM you would recommend?
Should I run the S-off commands in the toolkit before I flash the custom ROM?
It's against the rules to ask which ROM is best/most stable etc, so it's against the rules for me to answer something like that.
But...
If you're looking for a Sense based rom, look in Android Development section, there you'll find MagioRom (Sense 5), or if you want Sense 4 there's ViperXL, RageXL, and others.
If you're looking for a stock android/aosp ROM, look in Original Android Development. There's a whole bunch of great ROMs in that section, like Cyanogenmod, AOKP, Carbon, Rootbox, Slimbean, etc.
Have a look in the OP (first post) for each ROM, that'll tell you if there are any bugs and a basic rundown of the features, and any requirements you may have to fulfill for the ROM to work. Just find one that suits you best, and if it doesn't, you can just flash another.
Sent from my Evita
I guess I will give this one a shot.
http://forum.xda-developers.com/showthread.php?t=2061881
I need to update my HBoot, SuperCID and S-off before I attempt?
Yes I believe that's right. First SuperCID, then s-off, then RUU. Once you've done the RUU, you'll need to reflash TWRP again.
Sent from my Evita
Could you point me in the direction of the RUU file?
You'll find a list of RUU's on this thread:
http://forum.xda-developers.com/showthread.php?t=
Keep in mind you need to upgrade to at least 3.17 or 3.18.
Sent from my Evita
---------- Post added at 11:15 PM ---------- Previous post was at 11:14 PM ----------
Also, this thread is an awesome list of resources:
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my Evita
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Have you changed your CID?
mag13 said:
Have you changed your CID?
Click to expand...
Click to collapse
Please read again.
I was Super CID (11111111) but easily changed it to match TMobile (T-MOB010) with this tool for the update.
Click to expand...
Click to collapse
yooouuri said:
Please read again.
Click to expand...
Click to collapse
I am on Super CID and it does not work
mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
You have to change your CID back to the one for your RUU.
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4 after I flashed MaximusHD and firmware?
Now my phone is like this:
Hboot 2.16
Radio 1.20.50 (worst radio ever)
S-OFF
CID 11111111
The rom's with sense 5 (I tried just maximus because the others are not compatible with the new firmware, the sdcard mount point for multi user) are killing my battery more than twice faster compared with ViperS. 2h Display vs 5h on Viper.
Thank you!
Can we use this as rollback from h-boot 2.16 ?
mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
I didn't think it would. Glad you didn't brick your phone and I'll update the OP based on your experiment.
flow27 said:
Can we use this as rollback from h-boot 2.16 ?
Click to expand...
Click to collapse
arazvan2002 said:
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4
Click to expand...
Click to collapse
Upgrading your hboot is a one way street, as far as I know. Can't you change the radio to something else?
I flashed Viper ROM. All the things are ok, gsm, wifi, etc just I can't see the internal memory like I should. I can browse to it file es file explorer but I need a method to default mount the new (4.2.2) location of it. Where is mounted by the internal memory in 4.1 JB? I discovered a file vold.fstab. Maybe I can change something like that somewhere to be able to use 4.1 ROM's again.
Sorry for OFF topic.
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
yooouuri said:
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
Click to expand...
Click to collapse
Yes you can if youre s-off.
Sent from HTC One S using android 4.2.2 sense 5
Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
yooouuri said:
Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
Click to expand...
Click to collapse
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
tivofool said:
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
Click to expand...
Click to collapse
That's the right thing to do, yes?
kilo94 said:
That's the right thing to do, yes?
Click to expand...
Click to collapse
Yes
I have the same problem. I can't go back to stock. I haven't changed my CID yet but I see that has not worked for you.
Did you try with HTC__001 ?
dhigby said:
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Click to expand...
Click to collapse
Hey I used your instructions and everything was perfect thank you. I used to upgarde and downgrade hboot even to restore the HTC one S
I got the RUU "Error: 159" again with both RUU from first post and testet with each common cid, but at the end I only got success with super cid and the TMO_US Ruu.
Now I am back on Hboot 2.15 and can flash again the newest custom-recovery, thank you very much.
I've heard about a flashabe standalone zip for the hboot 2.15 and found this:
Only for S4!
Boot into bootloader and enable fastboot.
Code:
fastboot oem rebootRUU
Wait for the black screen with white HTC symbol. (Like when you flash a RUU)
then enter:
Code:
fastboot flash zip modded_hboot_YOUR_NEEDED_HBOOT.zip
then if you want
Code:
fastboot oem boot
(Boot into your current ROM)
modded_ = The red text is removed and "tampered" is gone in bootloader.
Download:
modded_hboot_1.06.0000.zip - (397.1 KB)
modded_hboot_1.09.0000.zip - (400.6 KB)
modded_hboot_1.13.0000.zip - (399.0 KB)
modded_hboot_1.14.0002.zip - (405.3 KB)
modded_hboot_1.14.0004.zip - (373.2 KB)
modded_hboot_1.14.0005.zip - (373.6 KB)
modded_hboot_2.15.0000.zip - (400.9 KB)
modded_hboot_2.16.0000.zip - (398.6 KB)
Thx goes to: touch of jobo XDA Post Source
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
Greetings by Idijt
Hello ,
i have just install a new rom , AICP , .
Everything is fine till when i shut down my phone or reboot , i am not able to boot my phone. MY phone will only show till HTC WITH THE RED TEXT then it will go into black screen and not boot up , and i cant get into the boot animation of AICP ROM. the only way i can get boot up my phone sucessfully is to flash my boot.img again. is there anyway to fix this problem ? sorry for my bad english and thanks in advance
cheers
More info required. What are your bootloader details? What recovery are you using? Did you clean flash?
Sent from my Evita
HBOOT- 2.14
S-0N (I tried S-off alot of times but i cant get SupeCID )
I did a factory reset when i flash the rom .
You didn't answer my questions.
Sent from my Evita
So sorry ,
recovery penrecovery-twrp-2.6.3.0-evita-4.4-selinux
i have done factory reset/data wipe + wiping davlik
Bootloader :
TAMPERED
UNLOCKED
EVITA PUT SHIP S-ON RL
H BOOT 2.14
RADIO 0.23a.32.09.29
OpenDSP - v 3.1.1.0.45.0015
eMMC-boot
It seems like you might have a corrupted boot partition. What is your CID? What methods have you tried to use to get SuperCID?
Sent from my Evita
hi
i have only tried this method [ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit ( http://forum.xda-developers.com/showthread.php?t=1952038 ) and it fail,
Affixation said:
hi
i have only tried this method [ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit ( http://forum.xda-developers.com/showthread.php?t=1952038 ) and it fail,
Click to expand...
Click to collapse
Is there any reason in particular you're using that method? It won't work, it states pretty clearly that it is used to gain SuperCID on at&t devices with the 2.20 firmware installed (which you don't have). You can try the hex edit method to get SuperCID. Or you can try the Rumrunner S-off method to get s-off.
You failed to answer one of my questions. I ask these questions for a reason, I'm trying to help you, and in order to help you I need information. I don't like having to repeat myself because it's a waste of my time. What is your CID?
Sent from my Evita
my cid is htc_044
Ok. Try the methods I listed above. You need s-off so you can run an RUU.
Sent from my Evita
i am really sorry for the trouble cause . And thanks alot for your help .