Database Info

[Q] OTA Updates on rooted, 111111, s-off, custom rom devices?

I have a couple questions.
I am on the 1.16 hboot with cid111111 and s-off unlocked tampered. twrp and maximus rom.
I finally did super cid and s-off on my one-s. Shortly after I recieved a notification that ota update 3.16.401.8 (612.27 mb) was available.
I was wondering if it would even work if i attempted to update. or would i have to update manually. Or would it brick it.
The main reason i would want to update is because the JB Sense roms just dont seem to run smoothly on my phone.
I was thinking this would update everything so the custom roms run smoother.
And Should i even update my hboot. does it make a difference.
I would usually be against it(ive had to downgrade other phones before).

Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.

impostle said:
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
Click to expand...
Click to collapse
Ok. ill look into that. sounds easy enough. last time i tried to update, i couldnt because of my cid. now i guess since there is an official t-mob i can do it?
You cant flash an ruu with super cid?
Oh and also, Once i update my hboot am i able to install the older ICS roms like maximus. thats just the most stable one i have found for my particular phone.
One more. Will i be able to restore my cid with s-off

ruu update
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.

myphonesbetter said:
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
Click to expand...
Click to collapse
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.

impostle said:
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
Click to expand...
Click to collapse
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?

real187 said:
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
Click to expand...
Click to collapse
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
EDIT: Thats what I get for watching too many threads, I miss stuff.

impostle said:
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
Click to expand...
Click to collapse
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?

real187 said:
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
Click to expand...
Click to collapse
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.

impostle said:
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
Click to expand...
Click to collapse
I have seen the tread. But im scepitical, because if it really was only because of the s-off more people should have it. Might be hardware related.
Eh you do not have tot change back your Cid to original (if its a branded Cid the ruu still wont run), just a valid HTC Cid.
Verstuurd van mijn One S met Tapatalk

He could flash from recovery or fastboot flash any hboot he wants with s-off. No RUU needed for downgrade or upgrade. That's only needed to go back to stock for warranty purposes.
@myphonesbetter
If you want the red warning text overlay to be gone as well choose any of the files here and flash it within recovery. S-Off needed to do so!
To remove ***Tampered*** as well download hboot 1.140004. You will need to come from a lower hboot version so if you're already on >1.140004 flash one <1.140004 first.
--- edit ---
You can lock/unlock your phone as well by flashing. Read more in [how to] reset your lock status flag. Also it's in the Droid DNA forums it's valid for One S. Remember: You need s-off for this to work.
--- and one more ---
You can change your CID pretty simple on rootet devices. Just enter fastboot mode and type:
'fastboot oem writecid HTC__001'
Reboot bootloader then. You can find a collection of HTC ONE S CID's here

^^^^^Very helpful post. thank you. I wouldve never found that.
When you run the ruu .exe, do you have to be in fastboot or in android? The install app told me just to turn the phone on so i figured it would automatically go into bootloader. but it did nothing at all to my phone and gave me an error 115.
When i tried the ota it tells me that I am runnning an altrered OS and i will have to install it a different way.
Sorry for the easy questions. but i just cant seem to find any threads that say how to. I found the ruu and a zip of the ruu. but not how to install it.
The best sense rom has instructions on flashing a newer hboot. .but i want to install a completely stock rom.

myphonesbetter said:
^^^^^Very helpful post. thank you. I wouldve never found that.
.
Click to expand...
Click to collapse
guess you run out of thanks, no?

Never even noticed the thanks meter. I have more of a direct thank you approach.
I tried to flash the ruu .exe in fastboot. and it actually rebooted into the black htc screen, so i figure thats the way to do it.
Unfortunately I got another error. image error (159) use the correct rom and flash again.
I am attempting to flash 3.16.401.8 onto hboot 1.16 (relocked) i am s-off and i changed my cid to HTC__001 via fastboot.
Is there another way. or can i flash the zip in twrp or cwm? Again i just want an oem jelly bean with the proper hboot and radio and everything that the OTA would change. so i can be up to date before i move on to the JB roms.
Ive tried all of the custom ones, and the wifi cuts in and out. i used the wifi partition fix. and i flashed the latest radio. nothing helped for more than a few hours.

don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?

ultimul said:
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
Click to expand...
Click to collapse
Yah thats usually how it works for me. if it works for 99% of people with one step. ill have to do it manually with 20 steps. I guess its made me learn alot about adb and fastboot. I could never get adb to work untill i upgraded to windows 7 recently. until then i had to exract everything to my sdcard via terminal emulator and then drag it to my computer form the card and modify things. but ive been forced to learn quite a bit.
Its weird. I bought my phone off of craigslist from someone who had no idea how to root. But when i opened it into hboot it said Tampered and locked. with no signs of ever being unlocked. completely stock rom and no red warning text on the splash screen.
The reason i want to be stock it so i know all the correct partitions and everything are set up right. (that part i dont understand yet).
I know that a normal system wipe in twrp or cwm doesnt wipe everything. If i wipe and install the same rom i am using(just to clear it up and start over) it doesnt even wipe the app data. (at least on my phone)
Im thinking that its because i am installing a euro rom with a HTC__001 cid and mine was originally TMUS T-MOB010 .
one thing i noticed also is that windows could not verify either of the ruus i downloaded from shppied roms
How do i flash the ruu.zip that i downloaded? Do i need to rename it update.zip like the older phones? Its been a while.

Ok so i know im pretty much helping myself here but i hate when i come across threads with no conclusion.
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Any help would be appreciated.

Ahh, things go on here! Nice! :laugh:
It's not quite clear if the RUU is the right one on this phone as many people report problems... So let's go OTA.
To flash the 3.16 OTA update your hboot needs to be < 2.15, your recovery needs to be the HTC stock one , your device needs to be relocked (not totally shure as mine wasn't at that time and it worked, but please remember that) and you need to have HTC stock system/ and stock data/ (ICS) files on your phone (you'll have to unroot as well, if rootet), as the OTA seems to check if certain files are present before working.
All that is quite a pain in the ass, isn't it?! So do one the following:
- Just make shure your bootloader version is lower 2.15, else flash a lower one.
- Click here and you'll have access to one of my google drive folders.
- Download the 2.31 zip. Unpack and copy these nandroid backup files into the appropriate TWRP folder on your phone, reboot into recovery and restore. Once done, you'll be able to flash the 3.16 OTA update after reboot. Remember to change CID before if you're on 11111111.
- Or download the 3.16 zip, unpack and restore. You'll have stock htc sense JB without the OTA. You don't even need to downgrade your bootloader in case. CID doesn't matter here.
- To root simply download SU_Bbox file and flash in recovery.
Important: With the JB update HTC invented disk write protection by default. This simply means that files deleted within stock sense JB will be back after rebooting the phone, also root was granted and working (still grats to htc for this one!!!). Check out for elemental x kernel at this point, as flar2 is the one offering additional modules for the stock kernel working around this. So you can be on stock JB as close as possible with write protection disabled.
--- edit ---
I nearly forgot: If you're experiencing WiFi troubles afterwards search for flashing wifi partitions.
--- and one more ---
myphonesbetter said:
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Click to expand...
Click to collapse
Cause you're on 2.35 US. You need to be on 2.31 EU before, because 3.16 is EU and there is still no JB update to 2.35 US. 3.16 OTA will work with htc__001 (htc worldwide).

The OTA determined my OS was modified.
I could not restore the folder i took directly out of the zip.
There was a folder inside the folder that contained the same files. I was able to flash this.
My hboot is still at 1.14 my cid is not htc--001 relocked. the update was 650 mb of which i could not use wifi for becauese it just said error.
so 650 mb through tmobile. only took a few minutes but used almoast half of my months dl limit.
IDK. i found instructions on how to update the hboot in best sense roms thread. i will try that.
Edit: the restore for 3.16 worked in twrp. shouldve tried that first.
I may still update my hboot. I cant really find any instructions. Apparently the search just finds every thread and lists it.

If you are on the latest TWRP 2.4.3.0 go back to 2.4.1.0 (the latest one seems to have restore problems).
The folder contained in the zip needs to be copied to /TWRP/BACKUPS/HT23whatever/
You should be able to restore then.
--- edit
hehe, ok then.
You can flash any of these hboots from within TWRP. Up or down, it doesn't matter - you're s-off.
---------- Post added at 10:43 AM ---------- Previous post was at 10:32 AM ----------
CID should be HTC__001 not htc--001. Maybe a typo.

[HOWTO] [HTC One SV] Unbrand your phone to get the OTA updates

Bonjour everyone, here's a little guide on how to unbrand your phone in order to get the OTA updates notifications directly and be able to install them.
If you want to get S-OFF one day on your One SV, read this first. You need to change CID to SuperCID to do so, and it's not possible (for the moment) if you upgrade to JB
Basically this works as long as your phone model is sold unbranded somewhere in the world and that the people having such a phone got an OTA update.
For now, ther's no way to change CID if you're running JB and are S-ON. That means that this only work for One SV's running ICS who want to get the OTA updates.
As far as I know, it works on K2_U and K2_UL, since they both got an OTA update to JB.
The trick is simple, I didn't invent it and haven't been able to find its original founder, but thanks a lot to her or him !
I'm basically just a messenger here since I only tried out some stuff that worked with other phones, so thanks a lot to bkcokota, old.splatterhand and jmztaylor
Don't try it if you're worried, bricks happen, you'd be the only one responsible !
Here we go :
1. First you need to root your phone, here's how.
2. Change you CID using the same method than for the One S.
Personnaly, I changed it to "HTC__203", which is the CID unbranded HTC phones have in France (HTC-FRA).
For example, "HTC__001" is HTC-WWE, which stands for World Wide English.
You can change it to whatever CID you like : choose it well. I can only recommend to use HTC__203 since it's the only one I tried and that it worked, but do as you please !
3. Flash stock recovery back. You'll find it here or here. Flash it like you flashed CWM recovery (into fastboot, using fastboot flash recovery xxxxxx.img).
4. Relock your bootloader. It's possible that it's not necessary, but it can't hurt ("fastboot oem lock", when in fastboot usb)
5. Run a RUU that matches you unbranded CID to get an "unbranded" rom.
You'll find them here, for example. The "RUU_K2_UL_ICS_40_HTC_Europe_1.17.401.5_R....exe" one will work with HTC__203 and HTC__001 CIDs.
6. Go ask your phone if he can find any updates
WARNING : for the moment there's no way to change CID if you upgrade to JB since the newer HBOOT (v2.00) don't let you do it. That means that for now you won't be able to S-OFF if you upgrate to JB using this method. For now...

Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).

old.splatterhand said:
Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).
Click to expand...
Click to collapse
Done, sir.
It was only said at the bottom of the message at first, but now I put it at the beginning as well.
There's one thing that I'm trying to get though : according to a lot of people and forums, you don't get OTA when you have SuperCID... but some poeple say they do.
It probably changes depending on the type of HTC phone, but also depending on the OTA (some got the first ones, but not the latest...).

I got the ota notification with SuperCID, i think it depends on more things.
But there i'm not far enough into it.

I have had no success at all. My story:
Updated a branded phone to JB, rooted. Then I did a moonshine S-off and changed CID to HTC__001 (even tried 11111111).
I have downloaded a ICS RUU (couldn't find stock K2_UL so I thought that I would download ICS first and then do OTA to JB) but I am getting error 158. I have checked md5 sum and it matches (http://androidfiles.org/ruu/getdown...0.14_2_10.49.40.11L_release_301902_signed.exe). Any ideas?

If you're on jb and hboot 2.00, that's normal... and written in the first post.

There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?

Is there any chance to make this for the k2cl ( boost mobile ) version?

idr666 said:
Is there any chance to make this for the k2cl ( boost mobile ) version?
Click to expand...
Click to collapse
Can you be more specific, what you mean with "this".

old.splatterhand said:
Can you be more specific, what you mean with "this".
Click to expand...
Click to collapse
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB

idr666 said:
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB
Click to expand...
Click to collapse
Boost has no official jb, but i know that there is work for an custom jb rom for boost.

Oh, thank you for the info. Is there any link about this work in progress?

idr666 said:
Oh, thank you for the info. Is there any link about this work in progress?
Click to expand...
Click to collapse
Look here

szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?

szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot,...
Click to expand...
Click to collapse
This was before moonshine was available. With S-Off i think it should be possible.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
I think so.
szympro said:
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?
Click to expand...
Click to collapse
To get it a bit clearer.
At this point i'm not very up to date, thats why i didn't answer til now.
I think (but i'm not sure) you can flash the ruu, if you are on hboot 1.0.
And as you are S-Off you should be able to downgrade hboot. But this is a very risky point, you can easily brick your device. Here is, how you have to do:
rollon76 said:
To change hboot you will need a PL80IMG.zip on sdcard with android-info.txt and hboot.img inside it.
reboot to bootloader and flash.
Click to expand...
Click to collapse
The thing what makes it difficult, is to get the hboot.img (its inside ics ruu), cause the htc ruu's encrypted and i only have heard about tools for linux which can decrypt it.

Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!

szympro said:
Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!
Click to expand...
Click to collapse
Glad, it worked for you.
Yes, of course, everything is appreciated! You can use this thread, please post ruu name too. You can look at my posts there. Hboot, boot.img, recovery, radio, would be fine.

HERE have other ruu
https://www.dropbox.com/sh/1t2zswod7tc97az/5hbzEgTv80

szympro said:
I have downgraded hboot first (by extracting and encrypting ICS RUU using linux)
Click to expand...
Click to collapse
Wow, that's cool !
Did you use rollon's method and flashed PL80IMG.zip in bootloader mode ?
If yes, which android-info.txt did you use ?
If not, how did you do it ?
szympro said:
then I could run RUU and now I am stock ICS with S-off and superCID
Click to expand...
Click to collapse
Even cooler for you.
Did you get the ota update notification for JB then ?
Did you manage to apply it ?
Thanks and congratulations !

Hi everyone.
Just a quick message to confirm that rollon's method works.
To downgrade you need to be S-OFF, extract and decrypt (with ruuveal, using linux or a linux virtualbox runned in windows) hboot and androidinfo from ICS RUU, put them in a zip named PL80IMG.zip, put it on your sd card and boot into bootloader. Then you can run the ICS RUU normally and you'll be back to stock ICS, with a "*** LOCKED ***" bootloader (not relocked !), will be able to go back to S-ON using "fastboot oem writesecureflag 3" (thanks to JMZ)...
You'll then have a locked S-ON out of box phone running 100% stock ICS with original boot, recovery and all that... who'll get the 2 JB OTA's...
In case anyone's interested

[GUIDE] Root, SuperCID & S-Off for Evita Hboot 2.14 - Firmware 3.17 [Orange UK]

This is for International hTC One XL/Evita - Hboot 2.14 & firmware 3.17 (Orange UK)
If you own AT&T One X please look elsewhere, this guide is not for your phone
There is an abundance of information scattered in these forums and not all root methods/exploits work universally due to variation in firmware builds and Hboots.
I had to read a lot of threads to figure out how to S-off my Orange UK One XL with Hboot 2.14 and firmware build 3.17.
I was only interested in attaining S-off but had to start with HTCDev bootloader unlocking which I didn't really want to do but none of the known root exploits worked on my firmware.
I am sharing this hoping it would help others avoid taking pills for headaches when pursuing this noble quest
AIM:
Provide a short guide to others with similar device and configuration on where to start and simple clear steps to follow with needed links.
PREREQUISITES:
1. latest htc drivers for your Windows PC/laptop if you have one of those. Check here.
2. a working adb environment preferably from latest Android SDK, if you don't have this already set up please check here.
3. "USB debugging" must be checked under Phone settings>Developer options
4. an original htc USB cable is strongly recommended.
5. phone charged at above 50%
6. basic knowledge of using command prompt (cmd) in Windows and adb commands.
STEPS:
So in my case the steps were:
[1] Unlock bootloader through htcdev.com
[2] Flash/install TWRP recovery
This is done manually. All-In-One Toolkit didn't work for me BTW.
1. download latest TWRP recovery for One XL/Evita from here
2. you can rename file for easier command prompt typing later, like TWRP5.img
3. place file recovery file in your adb/fastboot folder
4. connect phone in fastboot mode to PC, make sure it displays fastboot USB on phone before you proceed.
5. start command prompt from within fastboot folder by right clicking inside folder and choosing "open prompt here", type following command:
Code:
C:\yourFastbootFolder> fastboot flash recovery TWRP5.img
Not a bad idea to test your recovery by making a nandroid backup before proceeding to next step.
[3] Flash a custom rom (root)
All custom roms are rooted by definition. If you chose e.g. ViperXL like I did remember to flash boot.img extracted form same rom zip afterwards, otherwise bootloop!
You can of course flash a SuperSU zip instead to gain root but I don't see the point.
[4] SuperCID
This is the simplest way that I found accidentally during my endless searches, all credit goes to @beaups for this one and @Austempest for sharing :good:
1. connect phone to PC in Android mode (mode where you can use phone)
2. Run the following command from command prompt (CMD):
Code:
C:\>adb shell
To enter adb shell, then enter following commands after each other:
Code:
# su
# echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
3. Reboot to bootloader and hopefully you'll see 11111111 as your CID ...... yes
[5] S-Off
Now that your are rooted with SuperCID you can just follow @beaups simple steps for S-Off found here Facepalm S-Off
That is it.... you broke your shackles :laugh:
I am not a dev and for sure not taking credit for other people's work, merely giving back and hoping this assists clarify stuff and save some time.
Cheers!

the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a not in your guide that this guide wont work for at&t phones.

exad said:
the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a note in your guide that this guide wont work for at&t phones.
Click to expand...
Click to collapse
Thanks for this important reminder, note added in red on top!
You mentioned one click is only for AT&T phones, I guess you mean All-In-One Toolkit by hason2000, you see even in the tool's thread it's not stated explicitly that tool works only for AT&T, while the respective threads for these exploit state that it's for AT&T One X not negating other international versions!
Most guides/tools are for North America and some Australia but very few for Europe which BTW only recently came on board with 4G/LTE.
So figuring out, especially for noobs, what is what with all these international variations for one device and huge amount of information, while searching doesn't always provide an answer is a tedious task and can end up miserably :crying:
I hope it's in order to add some info for European Evitas
guys kindly don't quote whole post(s), thanks

Only AT&T Phones are different in the case of unlocking/rooting because they can't use HTCDEV. Every other onexl is the same for unlocking/rooting.

Great guide, thanks you! it worked !
Now i'm stuck at the next step. ha :crying:

i cant get root, because my touchscreen not functional after flashed a custom rom. i had success until step 3, i cant proceed to step 4 as i cant use my touches when the rom loaded. i didnt have any back up. i already searched around to dgrade my touchscreen firmware, but it needs root. im stuck here, i can flash custom cwm recovery, install custom rom but cant touch screen. the default cm10.1 dont have android debugging enabled by default, i cant enable it cos i cant touch the screen. if i restore to stock ruu, i can touch screen n all works, but i had a problem sync google contacts.
The reason im getting my hands on custom rom is bcos my stock XL(Asian version) will neve sync google contacts properly, i tried to flash JB stock RUU, but its same. then, i started to tamper my fon with unlocking bootloader via htcdev, flash cwm(twrp mess on my sdcard storage). i had experience on older htc devices but its my 1st time on the htc one series. right now, im on evita s-on, unlocked bootloader, hboot 2.14, cwm recovery(twrp mess on my sdcard storage), not-super CID. I 'm left with a non-touchable cm10.1, i can flash any rom that supports s-on. tried to relock bootloader but i cant flash stock ICS ruu.flashing stock JB RUU is ok. my target now is to s-off n superCID.
i can :
flash RUU 3.17, running a stock RUU 3.17.
unlock bootloader
flash custom recovery(twrp mess with my internal storage)
i cant :
root my device on stock rom
touchscreen wont work on custom rom
any help will b greatly appreciated.

Do not make multiple posts about the same thing. It is strictly against XDA rules.

sorry, may i know how to delete it? i click on edit/delete but cant see any options to delete my post.

You cannot
Sent from my One X using xda app-developers app

sir how to back or normal cid help me
sir how to back or normal cid help me i have a one x its allredy super cid how get back normal cid

Fastboot oem writecid whateveryourcidwas
This will only work once with s-on after supercid but will work as many times as you want if s-off.
Sent from my One X using xda app-developers app

ignore this post. found a relevant thread

How to upgrade bootloader to 2.14
So what if you are not on HBoot 2.14?
EDIT:
Warning: It is not a good idea to upgrade only the bootloader if you intend to flash the latest CM10 builds! Avoiding RUU and unlocking again out of laziness will probably get you in trouble afterwards. RUU is definitely the safer way. You'll find a good collection of ROMs here
http://forum.xda-developers.com/showthread.php?t=2119610
and the tutorial for upgrading RUU on a previously modded phone here
http://forum.xda-developers.com/showthread.php?p=26260005
I found these threads which helped me SuperCID, S-Off and finally upgrade the HBoot of my already rooted evita.
First you need the superCID from this post:
http://forum.xda-developers.com/showthread.php?p=42351491
Next Step S-Off:
http://forum.xda-developers.com/showthread.php?t=2155069
Then RegawMOD the appropriate bootloader from this thread and flash:
http://forum.xda-developers.com/showthread.php?t=1786498
The procedure was easy once I had found the appropriate threads on XDA

You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Sent from my HTC One XL using xda app-developers app

New CM10 and derivates require HBoot 2.14
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Click to expand...
Click to collapse
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.

ernstlustig said:
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
That's exactly why you should not do it that way. You may get issues along the way as a result of the software not properly utilizing your hardware. This is why you're supposed to update hboot. What you did is more like tricking it into thinking you updated the firmware.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse

ernstlustig said:
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
As exad said, CM 10 didnt want you to update just the hboot it wanted you to flash 3.18 RUU or equal to get updated firmware.
The requirement to install 3.18 RUU is listed as a requirement for CM. The hboot is what is checked but things like radio, adsp and wcnss are what actually needed to be updated, which you have not updated.
All you have successfully done is beaten the basic check for if you flashed the 3.18 RUU without actually doing what you were told to do.

How did you get s-off? i have a rogers version

salt204 said:
How did you get s-off? i have a rogers version
Click to expand...
Click to collapse
Links to XDA threads updated. (Sorry.) Please look again.

Has anyone tried successfully to write SuperCID into hboot 2.15 S-On devices?
as the instructions is for hboot 2.14, and I would like to S-Off the device with hboot 2.15 and it is S-On.
I have tried the hex with adb method, but it doesn't work.

[Q] Installing RUU, which one to choose

Hi,
My battery has been acting up for almost half a year now and my usage time is half of what it was when i got it. I have been installing several different ROMs and kernels so I am at a lost on what's wrong. So I have decided to install a RUU to see if a total reset can fix my phone.
I found this page: http://www.androidfiles.org/ruu/?developer=Ville
Does anybody know which RUU from the link is the newest/best? Will I get updates from HTC when I do this?
Currently running trickdroid 10.3.2, bricked kernel, twrp 2.3.3, S-OFF and superCID - is there anything in particular I should know before doing this?
I have never installed a RUU before, hope somebody can help

anyone? Or perhaps just a part answer

teamet said:
anyone? Or perhaps just a part answer
Click to expand...
Click to collapse
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman

G.Rabbani said:
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman
Click to expand...
Click to collapse
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that)
2. CID & MID (CID getter from play store will tell you that)
3. Last Stock firmware you had/installed?
4. HBOOT version?
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that) -----> S4
2. CID & MID (CID getter from play store will tell you that) -----> 11111111
3. Last Stock firmware you had/installed? -----> JB 4.1.1
4. HBOOT version? -----> 2.15.0000
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the response I've responded to your queries inline.

G.Rabbani said:
Thanks for the response I've responded to your queries inline.
Click to expand...
Click to collapse
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386

G.Rabbani said:
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386
Click to expand...
Click to collapse
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
Edit 2: The CID in all cases comprises of 8 characters. i.e HTC__001 (8 chars), BM___001 (8 chars, my CID) etc. So when changing the CID, be sure to have an 8 character CID.
regards

khan.orak said:
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
regards
Click to expand...
Click to collapse
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.

G.Rabbani said:
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.
Click to expand...
Click to collapse
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
- Just need to Unlock bootloader to Root/Flash custom recovery/custom ROM

khan.orak said:
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
Click to expand...
Click to collapse
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...

G.Rabbani said:
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...
Click to expand...
Click to collapse
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.

khan.orak said:
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.
Click to expand...
Click to collapse
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:

G.Rabbani said:
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:
Click to expand...
Click to collapse
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?

G.Rabbani said:
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?
Click to expand...
Click to collapse
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?

G.Rabbani said:
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?
Click to expand...
Click to collapse
- Okay before anything, i would advise to flash TWRP 2.3.3.0 recovery and you will avoid many issues currently being faced with 2.5.0.0.
You can find 2.3.3.0 Here.
If you need help on flashing, ask away.
- now your questions:
1. No and No
2. You have to boot into bootloader and then go into FASTBOOT and write the command
fastboot oem writecid HTC__001
BTW, I assume you have adb+fastboot files on your PC?
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
fastboot oem writecid HTC__001
Click to expand...
Click to collapse
This only works if you are S-OFF
hTConeS | SoFF | ChaRmAnDrOiD | BuLLetprOOf
Inverted Sense 5 Theme Updates+Tweaks
Inverted Sense 4+

[Q] S-OFF F/W 3.14.531.17 (T-MOB) possible?

I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?

Bump
Sent from my One S using XDA Premium 4 mobile app

My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.

tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?

bump

Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.

evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.

Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.

pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app

havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.

Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.

tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!

So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.

I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise

tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )

bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!

bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks

pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755

[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.