Database Info

[SOLVED (GUIDE)] Locking bootloader and S-OFFing

I decided I wanted to root my phone and play around with some custom roms, but as I'm a complete hacking/modding noob I decided to go the easy route and unlock my bootloader with HTC dev then flash a custom rom. Whilst this has worked perfectly for me I decided I want to go the whole hog and re-lock the bootloader then S-OFF as I am currently S-ON, as this will make it easier for me to quickly flash multiple roms etc. I understand to re-lock the bootloader you use the command
Code:
fastboot oem lock
but I read somewhere if you do this whilst using a custom rom this can brick your device? If this is true then I want to use an RUU to put my phone back into stock then re-lock it then S-OFF. This will also mean that if I ever needed to give my phone for repair my bootloader should say *locked* instead of *relocked* if I ever S-ONed again. However I have no experience or knowledge of using RUUs and I don't even know which one to use. Can someone help me?
EDIT: My HBoot remains unchanged so will I just have to run an RUU?
I looked at the DS RUU thread and there's 3 with my baseband and region (i was unbranded):
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08...
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08...
RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08...
Which one do I use? And how do I run it?
SOLUTION

take a look at my thread . this wil get you back to stock u will need to change your misc_version so you will be able top use the lowest RUU avalible. here's the link mate -----> http://forum.xda-developers.com/showthread.php?t=1609499
PLEASE USE THE RUU U WANT TO GET BACKTO STOCK THEN GO INTO FASTBOOT AND TYPE fastboot oem lock that will lock up your bootloader then you will be back to stock if u get stuck mail me on here and ill help you. another guy from india had the same problem and i helped him for 2 days straight and i got his phone back on so if u mess up in any way just mail me and dont stress about it im always here to help people mate okay in any need to speak with me give me your number and i will contact u by phone and guide u what to do and get it working 100% my friend okay take care hope u get it sorted buddy

Thanks but is it necessary to flash the hboots as I haven't touched mine? Mine is still 2.00.0002

Duke_Nuke said:
Thanks but is it necessary to flash the hboots as I haven't touched mine? Mine is still 2.00.0002[/QU
EDIT. i just read over your 1st post again so now i can help you. i will pm u exactly what to do okay
Click to expand...
Click to collapse

paul.robo said:
Duke_Nuke said:
Thanks but is it necessary to flash the hboots as I haven't touched mine? Mine is still 2.00.0002[/QU
EDIT. i just read over your 1st post again so now i can help you. i will pm u exactly what to do okay
Click to expand...
Click to collapse
XDA is a forum meant to share ideas and help openly, appreciate if we keep it that way rather than sending out instructions on PM
Click to expand...
Click to collapse

suku_patel_22 said:
paul.robo said:
XDA is a forum meant to share ideas and help openly, appreciate if we keep it that way rather than sending out instructions on PM
Click to expand...
Click to collapse
im helping a guy who is new to this sort of modding. if this is how i want to help thats my choice. its not upto u to say how i help other's. i have my guides to help the more advanced. to help noobs i help via pm. its then upto them to share how they did it. dont judge people. he is new. chucking him into other guides and helping on here will get him confused as other people would jump in and give all diff ways to do it. i have given him the very best and noob proof way to get his phone back to stock then i have provided him the files and a guide needed to get his phone downgraded ready for revolutionary. thats my way dont like it dont come onto here and messege about it
Click to expand...
Click to collapse

yeah sorry suku but paul is being really helpful, I couldn't do it without this communication, I may write a guide or a summary of what I did afterwards

may i know how this one ended up? i'm a noob and i also need some help on this. I unlocked the bootloader from htc dev and rooted using superoneclick.. i'm still s-on with hboot 2.00.0002.. i would like to go back to stock and try another method where i can have s-off..

Official unlocked devices with hboot 2.0..... can not S-OFF. Must downgrade hboot.

el_roi said:
may i know how this one ended up? i'm a noob and i also need some help on this. I unlocked the bootloader from htc dev and rooted using superoneclick.. i'm still s-on with hboot 2.00.0002.. i would like to go back to stock and try another method where i can have s-off..
Click to expand...
Click to collapse
if you still need help let me know ill add you on gtalk and ill help you get your phone s-off properly. after we finish you or me can write up a noob proof guide to help other people let me know mate im ALWAYS willing to help and im always online dont ever hesitate to send me a private message take care

that would be great.. i'll send you a pm..

I do feel that a guide should be written if other people are having the same problem... I would write one but I've forgotten most of the stuff we did

your a nice person paul.robo
its nice to know that your so helpful mate. i now know the 1st person to talk incase something goes horribly wrong with my phone
P.S. sorry for being off-topic.

paul.robo said:
if you still need help let me know ill add you on gtalk and ill help you get your phone s-off properly. after we finish you or me can write up a noob proof guide to help other people let me know mate im ALWAYS willing to help and im always online dont ever hesitate to send me a private message take care
Click to expand...
Click to collapse
Thanks a lot.. took us 2 days to solve the problem.. i'll try to review the things we did and try to make a guide when i have time.. once again, thank you so much paul...

el_roi said:
Thanks a lot.. took us 2 days to solve the problem.. I'll try to review the things we did and try to make a guide when i have time.. once again, thank you so much Paul...
Click to expand...
Click to collapse
No problem. I'm here to help all forum member's it also took me a few days to sort Duke_Nuke's problem also but we prevailed and his phones now working again this is what i am on this forum for. To help people that need help. Any time you need me send me a PM or add me on G-talk my email is [email protected] add me and give me all details of your problem so i can get to work on getting your phone back on . but i must stress. once you have got your phone back on please write up a guide on how we got your phone back on to help others

Not really a guide as such but a rough summary of what happened:
1. First, I had to get my phone back to stock. My bootloader was unlocked so I had to lock it first to run the RUU, using the command fastboot oem lock however that will show up on your bootloader as *relocked* instead of *locked*, so your warranty will still be void, but it'll be fully locked once you have run the RUU.
2. At this point I flashed stock recovery.
3. You then need to run an RUU, to make this easier you can change the misc version, the files for which is attached. This basically means you should be able to run any Desire S RUU and it will work. However the one I originally tried didn't work anyway, so I had to try a second, which worked. You may need to look around and try different ones.
4. Then I S-OFFed my ds using revolutionary.io Just follow the instructions on your screen.
5. Finally flash the hboot.img (attached) which is necessary if you want to return your phone back to stock. Then flash your rom of choice.
As I said, this is just a summary of what I did and is not a guide to be followed by the letter.

Let me also add what we did.
So before we started I was on
*UNLOCKED*
SAGA PVT S-ON RL
HBOOT-2.00.0002
With misc version: 2.10.401.8 –check by going to fastboot and on your computer open cmd and cd to your android sdk folder then type fastboot getvar all.
1. The first thing we did was to lock the bootloader (fastboot oem lock)
2. Then we tried changing the misc version with the one duke attached (or see attachment on see previous post), but it didn’t work. So we tried another one (see attached files). To see if it works, just run the .bat file with the booted device connected to the computer. make sure USB debugging is enabled and fast boot is disabled. If the screen just flashes it means it’s not working. You can double check by looking at the results of fastboot getvar all.
If the attached files don’t work, try entering the codes manually. Still, your phone should be connected with USB debugging on and fast boot off.
a. Open cmd and cd to the tools folder of the attached file.
b. Once you’re sure that your on the tools folder, enter the following codes (one code per line. So you’ll have to press enter after every code):
adb push misc_version /data/local/tmp​adb shell chmod 777 /data/local/tmp/zergRush ​adb shell chmod 777 /data/local/tmp/misc_version​c. (when everything is finished, type)
adb shell​d. (you will now be on the $, then type)
./zergRush​e. (some things will appear, wait for it to finish. It will say on the last part “[+] Killing ADB and restarting as root... enjoy!”. Then type)
adb shell /data/local/tmp/misc_version -s 1.27.405.6​f. After it’s finished, your misc version will now be 1.27.405.6. You can double check that again.
3. Now run the correct RUU for your region/brand. My phone is unbranded and it’s European so paul gave me an unbranded European RUU. You can check out his thread for the RUUs here.
4. Once the phone has booted back, turn on USB debugging and disable fast boot then go to revolutionary.io. Follow the steps on how to s-off.
5. Then flash the eng.hboot.img that duke attached (or see attached file on previous post). To do this, first you should download the file. Then copy the file on your android sdk folder. Connect your phone to your computer and go to fastboot. Open cmd and type “fastboot flash hboot eng.hboot.img” (without the “” of course ). After it’s finished, reboot to bootloader. Now your hboot will say saga pvt eng s-off.
DONE. All credits to paul.robo.. Thanks for helping

el_roi said:
Let me also add what we did.
So before we started I was on
*UNLOCKED*
SAGA PVT S-ON RL
HBOOT-2.00.0002
With misc version: 2.10.401.8 –check by going to fastboot and on your computer open cmd and cd to your android sdk folder then type fastboot getvar all.
1. The first thing we did was to lock the bootloader (fastboot oem lock)
2. Then we tried changing the misc version with the one duke attached (or see attachment on see previous post), but it didn’t work. So we tried another one (see attached files). To see if it works, just run the .bat file with the booted device connected to the computer. make sure USB debugging is enabled and fast boot is disabled. If the screen just flashes it means it’s not working. You can double check by looking at the results of fastboot getvar all.
If the attached files don’t work, try entering the codes manually. Still, your phone should be connected with USB debugging on and fast boot off.
a. Open cmd and cd to the tools folder of the attached file.
b. Once you’re sure that your on the tools folder, enter the following codes (one code per line. So you’ll have to press enter after every code):
adb push misc_version /data/local/tmp​adb shell chmod 777 /data/local/tmp/zergRush ​adb shell chmod 777 /data/local/tmp/misc_version​c. (when everything is finished, type)
adb shell​d. (you will now be on the $, then type)
./zergRush​e. (some things will appear, wait for it to finish. It will say on the last part “[+] Killing ADB and restarting as root... enjoy!”. Then type)
adb shell /data/local/tmp/misc_version -s 1.27.405.6​f. After it’s finished, your misc version will now be 1.27.405.6. You can double check that again.
3. Now run the correct RUU for your region/brand. My phone is unbranded and it’s European so paul gave me an unbranded European RUU. You can check out his thread for the RUUs here.
4. Once the phone has booted back, turn on USB debugging and disable fast boot then go to revolutionary.io. Follow the steps on how to s-off.
5. Then flash the eng.hboot.img that duke attached (or see attached file on previous post). To do this, first you should download the file. Then copy the file on your android sdk folder. Connect your phone to your computer and go to fastboot. Open cmd and type “fastboot flash hboot eng.hboot.img” (without the “” of course ). After it’s finished, reboot to bootloader. Now your hboot will say saga pvt eng s-off.
DONE. All credits to paul.robo.. Thanks for helping
Click to expand...
Click to collapse
hello im having problems with this guide i cant get the second line
the comands say that there is no such file or directory
.. pls help

It is a while ago when i did this. My problem was a file with a. .c after it. I googled for the correct file. This was somewhere to find in xda. I think you need the file without the. . c.
Sent from my Desire S using xda app-developers app

first line is missing, should be:
Code:
adb push zergRush /data/local/tmp

[how to]unlock downgrade then s-off desire s

It's the steps I took to get s-off after upgrading the phone and keeping it until the warranty wore out
1.Follow amidabuddha’s guide to abd and fast boot installation(be sure to thank him its the button on the bottom left of the post)
here:
http://forum.xda-developers.com/showthread.php?t=1272595
2.Go to http://www.htcdev.com/ and follow the instructions to unlock your phone
“note use all other supported models”
3.Install this program onto your phone http://www.4ext.net/get.php?apk
and use it download the latest stable version of recovery and transfer and unzip recovery.img file to where you installed fastboot and abd on your computer.
4.On your phone go to settings/power and make sure fastboot is turned off and then turn off.
Hold the vol down button and power button until you enter the bootloader connect the usb and select fastboot using the power button as select and vol buttons as up and down
5.Now on the computer go to where you installed fastboot and abd and right click while holding shift and select open command window here.
Type the following into the command window
fastboot getvar cid(“write this down and keep it for future knowledge”)
fastboot flash recovery recovery.img
Extrecovery should now be installed
Now type:
fastboot reboot-bootloader
And select recovery from the menu
6.In recovery go to install from sd card and then choose a zip from sd card
Should be something like this cwm-superSu-v0.94.zip
http://forum.xda-developers.com/showthread.php?t=1742522 (“you can download it from here plz thank ArcMan09”)
7.reboot the phone this time letting it boot up
connect the usb select charge only
in the command console
type
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version –s 1.27.405.6
Exit
adb reboot-bootloader
What was entered above should now actually appear in fastboot
8.now use
fastboot oem lock
Whole bunch of stuff comes up but most likely your now locked again
9.Go here
http://pastebin.com/raw.php?i=YcnM8Sr9
rember that thing I told you to write down find it in the table and take note
in fact write the corresponding one down as this is tell you the ruu you must download
Now open the required ruu on the computer
You can download from here(“plz thank football”)it’s the button on the bottom left of posts
http://forum.xda-developers.com/showthread.php?t=1002506
it should be something like this:(this may not be the right one for your phone you should have checked above)
RUU_Saga_hTC_Asia_India_1.47.720.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199605_signed
10.connnect your phone to your computer in fastboot like before
open the ruu on the computer
let it run following the instructions
now if you check the hboot it should say your have something 0.98.0000 S-ON
this means you can now use http://revolutionary.io to s-off your phone
now go back up and flash your desired recovery and rom of your choosing as well as superuser
I recommend the recovery we installed before("you will have to flash this through fast boot again")
Either
Viper Saga
or
Fallout Evolution
Both are senses roms
Recommended things to install after rooting your phone
a rom backup app:Rom manager:might come with the rom
an antivirus: avast(“you can use the root install method”)
4ext recovery control-(or updater for free but control will save you a lot of time)
Superuser but that will likely come with the rom but if it doesn’t
What ever else you want your done your phone is rooted and
I'm pretty sure this is how I did it please post questions or mistakes I've made on the board and remember to thank the creator of each of the links(it takes a lot of time to write these out) I'm really just collating them into something nice and easy to read as I jumped around forums trying to find the answer.
Hope this helps
I Would Like to thank some outstanding members that have helped me create this guide (please thank them they absolutely deserve it)
amidabuddha
n0elite
Skanob
Football
ArcMan09
if I have missed anyone im very sorry i've far too many pages up here just trying to recreate what steps I took to complete this task.

In other words I have to:
1)flash to a custom rom
2)flash to official ruu
3) s-off
4)flash to custom rom again
And why I shouldn't stay at first step? will I have a problem if I have a rooted s-on phone?

Billlis said:
In other words I have to:
1)flash to a custom ROM
2)flash to official ruu
3) s-off
4)flash to custom ROM again
And why I shouldn't stay at first step? will I have a problem if I have a rooted s-on phone?
Click to expand...
Click to collapse
well no you are flashing a recovery the first time then downgrading the ruu then s-off and then flash to custom ROM.
I don't know if there are newer methods out there im currently getting a new phone so im not much help in the experimentation side. but it should be pretty solid the tricky part i found was getting a hold of the right ruu all that saving the misc version and stuff is really important as its needed to downgrade.anyway good luck let me know if it works for you i haven't got too much feed back on this topic. oh and rooting is defiantly worth it opens up the phone completely and everything seems to work all of a sudden.:cyclops: YES YOU WILL NOT BE ABLE TO ROOT AN S-ON AKA SECURITY OR LOCKED PHONE. this of course refers to kernel which is normally locked(s-on) there is a bunch of other uses such as being able to set root to open items very handy worth buying (support the devs buy apps you like!!). you can just do a search on good play is it for root only or s-off apps wich will usually have some usefull tools anyway hope that helps.

I have just unlock my desire throught HTC-dev (still S-On) installed a recovery and a custom ROM. I suppose this is not the right procedure but I have not any problem with root-access apps now. btw its the third time that I have rooted this phone

you will be able to install and run these apps normally but the will be either not working or have limited functionality
use this to check your root and install these programs if you dont have them
root checker does what it says
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5qb2V5a3JpbS5yb290Y2hlY2siXQ.
busy box required for root
https://play.google.com/store/apps/...251bGwsMSwxLDEwMiwic3Rlcmljc29uLmJ1c3lib3giXQ..
superuser sets permissions for apps
https://play.google.com/store/apps/details?id=com.noshufou.android.su&feature=related_apps

as I said before it's the third time that I root my device so I know the required apps. Btw Root checker says that I have root access and any other root-required program works fine till now

First of all, thanks for this tutorial, it got me quite far!
There's one problem:
I can't get any further than step 9, because the thread with the RUU's doesn't exist anymore (http://forum.xda-developers.com/showthread.php?t=1002506)
I can't downgrade now, I've searched the whole internet for the version I need (HTC-Dutch HTC__E11), but I can't find it.
The only thing I found is from HTCdev, but the file I get from there is a .tar, and I don't know what to do with that.
I can unzip it, but the only thing I get from the file are a bunch of folders and files I can't open.
Can you please help me?
//WoZZerZ

WoZZerZ said:
First of all, thanks for this tutorial, it got me quite far!
There's one problem:
I can't get any further than step 9, because the thread with the RUU's doesn't exist anymore (http://forum.xda-developers.com/showthread.php?t=1002506)
I can't downgrade now, I've searched the whole internet for the version I need (HTC-Dutch HTC__E11), but I can't find it.
The only thing I found is from HTCdev, but the file I get from there is a .tar, and I don't know what to do with that.
I can unzip it, but the only thing I get from the file are a bunch of folders and files I can't open.
Can you please help me?
//WoZZerZ
Click to expand...
Click to collapse
Try this site, i think they are still up http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain

jugg1es said:
Try this site, i think they are still up [site]
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain
Click to expand...
Click to collapse
Thanks, but I couldn't find the version I need (HTC-Dutch HTC__E11) :crying:
Do I REALLY need to use that exact version?

WoZZerZ said:
Thanks, but I couldn't find the version I need (HTC-Dutch HTC__E11) :crying:
Do I REALLY need to use that exact version?
Click to expand...
Click to collapse
Now that, i don't know. Sorry.
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain

jugg1es said:
Now that, i don't know. Sorry.
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain
Click to expand...
Click to collapse
Since the TS uses a 1.47 version as an example, and I only found one European version of 1.47, I'm downloading that version.
I'll try to install it tomorrow.
edit:
I tried it today, and it doesn't work... The program crashes when getting device information
edit 2:
Wait, I can't get past step 7 either.
When using the first command, I get this message:
C:\android-tools>adb shell chmod 777 /data/local/tmp/misc_version
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
I tried it again with USB-debugging enabled, and this was the result:
C:\android-tools>adb shell chmod 777 /data/local/tmp/misc_version
Unable to chmod /data/local/tmp/misc_version: No such file or directory
Could somebody help me please?
EDIT 3:
I found out I had to push misc_version on the phone first, (not said in this tutorial), so I did that.
Then I could chmod it, and it worked fine.
I relocked the bootloader, and tried to install the RUU, but the RUU keeps crashing whenever it starts...

I found out I had to push misc_version on the phone first, (not said in this tutorial), so I did that.
Then I could chmod it, and it worked fine.
I relocked the bootloader, and tried to install the RUU, but the RUU keeps crashing whenever it starts...
(Sorry for the double-post, I couldn't find out how to delete my other post)

WoZZerZ said:
I found out I had to push misc_version on the phone first, (not said in this tutorial), so I did that.
Then I could chmod it, and it worked fine.
I relocked the bootloader, and tried to install the RUU, but the RUU keeps crashing whenever it starts...
(Sorry for the double-post, I couldn't find out how to delete my other post)
Click to expand...
Click to collapse
Make a GoldCard and your phone should eat any RUU :highfive:

VnnAmed said:
Make a GoldCard and your phone should eat any RUU :highfive:
Click to expand...
Click to collapse
I don't think the phone is the problem here, the RUU keeps crashing while the phone is ready to accept it.
The problem is that the list of RUU's on XDA-developers is gone (see step 9 in the tutorial, the link is dead), so I might not have the right version.
I've searched everywhere, but I can't find the exact RUU I need according to the tutorial.

WoZZerZ said:
I don't think the phone is the problem here, the RUU keeps crashing while the phone is ready to accept it.
The problem is that the list of RUU's on XDA-developers is gone (see step 9 in the tutorial, the link is dead), so I might not have the right version.
I've searched everywhere, but I can't find the exact RUU I need according to the tutorial.
Click to expand...
Click to collapse
Try here http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
The third-rate mind is only happy when it is thinking with the majority. The second-rate mind is only happy when it is thinking with the minority. The first-rate mind is only happy when it is thinking.
—A. A. Milne

O rly?
WoZZerZ said:
I don't think the phone is the problem here, the RUU keeps crashing while the phone is ready to accept it.
The problem is that the list of RUU's on XDA-developers is gone (see step 9 in the tutorial, the link is dead), so I might not have the right version.
I've searched everywhere, but I can't find the exact RUU I need according to the tutorial.
Click to expand...
Click to collapse
Yea, but as far as I get it that's what GoldCard is for. It fools your phone so the bastard is thinking that the software you're flashing is from nurturing bosom of mother fabrica so it swollows it whole no matter what it is and cries for dessert. I have UK vodafone Desire S and with GoldCard I have flashed official Asia Gingerbread Update

The exact same way i downgraded and achieved s-off on my Desire. I believe i have the correct RUU still somewhere on my laptop. I'm not at home at the moment but i can put up a dropbox link (if i'm not mistaking and still have it) tonight if you like?
Edit; typo
Sent from my HTC One X using xda premium

basd43 said:
The exact same way i downgraded and achieved s-off on my Desire. I believe i have the correct RUU still somewhere on my laptop. I'm not at home at the moment but i can put up a dropbox link (if i'm not mistaking and still have it) tonight if you like?
Edit; typo
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
If you could do that that would be awesome!

WoZZerZ said:
If you could do that that would be awesome!
Click to expand...
Click to collapse
Could you humor me and strat the Phone in fastboot, then open a command prompt and type; Fastboot getvar version main. Please post the version-main here. Just to be sure
---------- Post added at 03:01 PM ---------- Previous post was at 02:29 PM ----------
Here´s the db link, its still uploading so if its not there now wait a while. There are (or gonna be) 5 RUU´s in there, just check your version main and pick the one you need
https://www.dropbox.com/sh/engsv5p1xf9vy63/jOUwJUB55x

basd43 said:
Could you humor me and strat the Phone in fastboot, then open a command prompt and type; Fastboot getvar version main. Please post the version-main here. Just to be sure
---------- Post added at 03:01 PM ---------- Previous post was at 02:29 PM ----------
Here´s the db link, its still uploading so if its not there now wait a while. There are (or gonna be) 5 RUU´s in there, just check your version main and pick the one you need
https://www.dropbox.com/sh/engsv5p1xf9vy63/jOUwJUB55x
Click to expand...
Click to collapse
The bootloader THINKS the main version is 1.27.405.62, but that's the whole point: I had to do that in the tutorial when chmodding misc_version.
I'll try one of the RUU's thanks
EDIT:
It's installing now, I've got further than ever before! Hopefully it all works, I'll let you guys know in a few minutes
EDIT 2:
IT WORKED! Thanks!
I'm on HBOOT 0.98.0002 now, so I'll be able to achieve s-off, THANKS!
I can confirm that this tutorial also works to downgrade from HBOOT 2.02 to 0.98

[Q] Xfactor exploit repeatedly fails, cannot change CID

Hi everyone,
I just received a used AT&T One X in the mail and was hoping to root and install CM10. The phone came with 1.85 and I was able to get root using the manual method, but hasoon2000's all-in-one tool fails repeatedly to execute the xfactor exploit. I accepted both of the backups on my phone, and as the phone reboots into the bootloader the command line prints "[-] Failed" and returns that my CID is still CWS_001.
I've tried just about everything I can think of and I'm about to give up. I've read that updating to 2.20 with the RUU and then retrying the all-in-one tool has worked, but the RUU will not complete either (I repeatedly get a low battery or USB connection error despite a fully charged battery and correct USB drivers).
Is there anything else I'm missing, or should I just give up and return this thing?

Put the phone down and read read read. The last thing you want to do is upgrade from 1.85 to 2.2 by ota or by ruu.
Sent from my HTC One XL

954wrecker said:
Put the phone down and read read read. The last thing you want to do is upgrade from 1.85 to 2.2 by ota or by ruu.
Sent from my HTC One XL
Click to expand...
Click to collapse
I've spent hours upon hours reading and have seen nothing about that, so how about a link rather than a condescending reply?

Thank redpoint73.
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL

I used the adb method for 1.85. I didn't get any errors at the command line, until I try to get superuser access in adb and I get "/system/bin/sh: su not found."

MOD EDIT: unhelpful.
Anyway, it's getting late so I'll check in on this tomorrow. If someone has some insight, I would appreciate it.

Thread Cleaned
Thread cleaned. Keep it more helpful or move on to the next thread please.
mf2112
XDA Moderator

SuperSU says that I don't have the SU binary installed. I thought maybe the binary linked in the 1.85 rooting method post might be the problem, so I tried pushing the binary from androidsu.com and I still have the same problem - no su access at the command line, SuperSU says no binary is installed, busybox won't install. My bootloader does say TAMPERED.

Solved! For anyone who finds this later with the same problem, I tried the 2.20 RUU in fastboot for the 4th or 5th time, and it finally worked! Once I was on 2.20 I was able to easily use the all in one tool to unlock my bootloader.

oceanminded said:
Solved! For anyone who finds this later with the same problem, I tried the 2.20 RUU in fastboot for the 4th or 5th time, and it finally worked! Once I was on 2.20 I was able to easily use the all in one tool to unlock my bootloader.
Click to expand...
Click to collapse
Lol... that's why all in one tools are bad for the community. If you actually read the compilation thread, you'll find a 1 click Super CID and root script for 1.85.
Hope you don't brick your device soon.

Enjoy hboot 1.14 you definitely deserve it
Sent from my HTC One XL

954wrecker said:
Enjoy hboot 1.14 you definitely deserve it
Sent from my HTC One XL
Click to expand...
Click to collapse
He will eventually want to downgrade just like all 1.14 hboot users. He would have to search and read for the script though, oh no.
Sent from my One X using xda premium

thedauntlessone said:
Lol... that's why all in one tools are bad for the community. If you actually read the compilation thread, you'll find a 1 click Super CID and root script for 1.85.
Hope you don't brick your device soon.
Click to expand...
Click to collapse
Yeah, I tried both of those and neither worked. But again, thanks for assuming that you're the only person who reads the stickies. Jesus, this is a hostile forum. Every other device I've owned the communities have been welcoming and helpful, but here it's always LOL CAN'T ROOT? GO READ NEWB. When I posted here I was hoping to get some feedback from someone who might understand what was going on, but I guess that's not the majority of people on this forum. If someone finds this thread with the same problem in the future, I hope they can figure it out as I did.
I had hboot 1.14 when I got the phone, and I see no reason to downgrade now that I've got CM10 up and running, which is all I wanted in the first place.

No you didn't. You were on hboot 1.09. Don't claim we don't know jack when you clearly don't know what you're talking about.
It would be safe to say it's user error if you can't use the super CID script or 1.85 root others else seems to be able to use them without fail.
And this forum seems to be filled with noobs posting asking for root when there are people who take time out of their life to compile resource for noobs to read. If you followed the instructions to the tee, everything would work.

Thank you all for your help, I have learned a great deal in just a short time of reading thanks to your contributions. I have been away for a few months and last I checked, this exploit was not available. I was very pleased to find the wealth of new information and have been reading about the current exploit, and then Hasoon's GUI soon after. But then I too had the same error when attempting both methods, the command line prints "[-] Failed" and returns that my CID is still CWS_001. I am fairly certain my version is 2.20. But I see you mention HBOOT 1.14 Could someone tell me do I need to downgrade to Hboot 1.09 first? Also, point me to the information thread on this or do I just need the Jewel/Evita toolkit? Thanks again for such great support.

Nevermind I figured it out, thank you for all the good reading.

Help needed: Unlocking. Not rooted.

Hi Guys (and Gals),
I've just registered on the site, after browsing and reading posts for a few days. I'm very much an Android tech-noob but also very keen to learn more as I go along...
Here is my dilemma:
After sending my HTC Sensation XE back and forth to HTC for repair 4 times, I've now lost any faith in them helping me resolve anything. Basically, they sent me a replacement phone (supposedly unlocked) but it is locked (eight digits) to an unknown network and I don't know how to unlock it. After wasting precisely 3 months and many hours on the phone with incompetent HTC technicians, they finally informed me last week that my warranty had just run out, that day, and that they would no longer help me with any problems with the S-XE. Nice - NOT! I was furious.
So, here I am wondering what to do next. I have followed a few threads on this site and tried a couple of unlocking methods [ http://forum.xda-developers.com/showthread.php?t=1232107 ] but it appears that these methods work only on rooted phones. D'OH!
My phone isn't rooted and is currently showing S-ON. (I *think* i'm learning some lingo, lol).
I rang a couple of local traders, who said they can unlock it for a tidy sum of £15. I'm not sure what these guys do to the phone and whether it is basically the same as rooting my device?
I guess what I'm asking is, does anyone know how I can unlock this phone myself, without rooting it? Alternatively, would rooting be the only option and which method would be the best option.
I already use a HTC One, so I obviously do have a working phone but I am very keen to get this Sensation XE working.
Despite being quite clueless, I'm willing (and curious) to give rooting a go, if it's the only way to resolve my problem. My fears are that I just don't know which method would be best (and simplest), I'm worried about 'bricking it' and I don't know how to flash a ROM.
After reading some threads here, I have determined how to fastboot (?) my phone and have found the specs, as follows:
***LOCKED***
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.29.0000
eMMC-boot
Mar 2 2012
Current software info:
Android version: 4.0.3
HTC Sense version 3.6
Anyone have any sensible ideas? If anyone can help, I'd be very grateful. Oh, and apologies if I've posted this in the wrong 'section'. Many thanks in advance.
Regards: Undercrackers.

if you want to unlock your device to any network then you have to do this first
http://forum.xda-developers.com/showthread.php?t=1661631
after S-OFF in the thread you mentioned go to page 54 in see post #531 on how to unlock it

rzr86 said:
if you want to unlock your device to any network then you have to do this first
http://forum.xda-developers.com/showthread.php?t=1661631
after S-OFF in the thread you mentioned go to page 54 in see post #531 on how to unlock it
Click to expand...
Click to collapse
Hi, rzr86, thanks for the info.
I downloaded the latest controlbear, ice cream sandwich from http://unlimited.io/jb_pyramidlocked.htm
I followed the instructions from http://unlimited.io/juopunutbear.htm as far as I could.
I plugged in my USB and managed to run temp_root.bat with no problems but, I ran into problems with the ControlBear instructions and folder.
I'm guessing my phone is 'Stock RUU' but unsure what this is.
I'm not 'HTC Dev Unlocked', as the prerequisite states, but it says in the thread [http://forum.xda-developers.com/showthread.php?t=1661631] that I don't need to be so I'm now confused.
Another point of reference is that there is no ControlBear.exe file to run, in the ice cream sandwich downloaded zip folder.
It contains just a ControlBear [non exe] file, alongside adb, fastboot, MD5SUM and a jb_hboot rar/zip file.
I'm not sure if anything is missing?
Excuse my ignorance here.
The instructions say:
8. cd into the folder where you extracted and run the following cmd:
Note: This cmd returns a blank new line if you have done it correctly.
chmod 755 ControlBear adb fastboot
9. Run ControlBear from terminal - sudo ./ControlBear
Click to expand...
Click to collapse
This is where everything fails me, I have no idea how to do this - at all, so I ran temp_root_remove and set my phone back to how it was before I started.

Undercrackers said:
Hi, rzr86, thanks for the info.
I downloaded the latest controlbear, ice cream sandwich from http://unlimited.io/jb_pyramidlocked.htm
I followed the instructions from http://unlimited.io/juopunutbear.htm as far as I could.
I plugged in my USB and managed to run temp_root.bat with no problems but, I ran into problems with the ControlBear instructions and folder.
I'm guessing my phone is 'Stock RUU' but unsure what this is.
I'm not 'HTC Dev Unlocked', as the prerequisite states, but it says in the thread [http://forum.xda-developers.com/showthread.php?t=1661631] that I don't need to be so I'm now confused.
Another point of reference is that there is no ControlBear.exe file to run, in the ice cream sandwich downloaded zip folder.
It contains just a ControlBear [non exe] file, alongside adb, fastboot, MD5SUM and a jb_hboot rar/zip file.
I'm not sure if anything is missing?
Excuse my ignorance here.
The instructions say:
This is where everything fails me, I have no idea how to do this - at all, so I ran temp_root_remove and set my phone back to how it was before I started.
Click to expand...
Click to collapse
actually from the S-OFF thread request the windows version of the tool
someone will pm you

[s-off] hboot 2.15 htc one s flawless

So there are many tutorials out there for obtaining S-OFF for the HTC ONE S for all kinds of HBOOTS. But what about those of us with the newest model and HBOOT 2.15 and so on? Well it's been solved after months of trying.
1) First thing you're going to need is an appropriate RUU for your device. Mine is "RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2"
There is a thread for obtaining the proper RUU and how to distinguish which one you need. If you're here, you probably already have the appropriate RUU.
2) Second, youre going to need THE CORRECT VERSION of Moonshine. If your device is like mine, it will look like this: HTC One S T-MOB Windows 3.14.531.11 moonshine_ville_3.14.531.11.zip. If you have a different ROM version, get that one. Same goes for the carrier. Use your RUU name for a cheat sheet if you have to. Note the similarities??
3) Probably one of the most important steps is making sure that you have FASTBOOT AND ADB both installed and running AND detecting your device!!! I can not stress enough how important these are! Without them, you're gonna have a bad time. MAKE SURE USB DEBUGGING IS ON AT ALL TIMES! Snoop05 made a fantastic tool called 15 SECONDS ADB INSTALLER 1.1. Here's the link for that http://forum.xda-developers.com/showthread.php?t=2588979
Follow his instructions in the OP for a how to if you run into a problem, which you shouldn't if you can read.
Use the terminal command " adb devices " and you should get something like this
C:\Users\C***********\Desktop>adb devices
List of devices attached
HT26TW407378 device
This means your phone is being recognized as an adb device, which is fantastic! If not, try disabling and re-enabling USB DEBUGGING.
Boot into BOOTLOADER and go back to your command prompt and enter " fastboot devices ". You should get a reply that looks something like this:
C:\Users\C***********\Desktop>fastboot devices
HT26TW407378 fastboot
CONGRATULATIONS, you're almost there!
4) Once you have ADB and FASTBOOT both running properly, it is ALMOST time to run your RUU. First we have to relock our BOOTLOADER! It is very simple. Go into your Bootloader and make sure you have FASTBOOT USB on your screen. Once you see that, open a command terminal on your PC where fastboot is located, or anywhere if you used the 15 file I have above, as it makes sets fastboot machine wide! (exciting, huh?) In the command window type in " fastboot oem lock ". Now your bootloader is relocked and you are ready to run the RUU.
Run the RUU and allow it to finish. Reboot your device. HERE IS WHERE STUFF CHANGES!! Other people would have you ROOT. All you need to do is this:
-RE-ENABLE USB debugging and set your screen to NEVER TURN OFF. Trust me, you want this for now.
-Unlock your BOOTLOADER again
-DO NOT root
-DO NOT install SU or busybox
-DO NOT flash a custom recovery
-ONLY RUN MOONSHINE, follow the prompts, answer Yes twice and let it do its magic. My phone took 4 tries to get it done, but it worked!
If you followed my instruction to the T you should be moonshine S-OFF. Your device will be turned off when it finishes. Reboot your phone into Bootloader and profit, because you are S-OFF!

>My phone took 4 tries to get it done, but it worked!
What do you mean by this? You had to run the moonshine 4 times before it worked? Why would this be?

Misconception, sorry pal
808phone said:
>My phone took 4 tries to get it done, but it worked!
What do you mean by this? You had to run the moonshine 4 times before it worked? Why would this be?
Click to expand...
Click to collapse
Allow me to clarify.
When Moonshine is running it sends your phone into bootloader and restarts the phone.
After it checked to see that ADB and fastboot were working properly, it started doing that.
It went into fastboot to adb to fastboot to adb and had a running line of "moonshining<1,2,3,4>.........." after each time.
It did this four times before moonshine actually gained S-OFF.
It went something like this:
Waiting for device..........................................................................
Device found
Moonshining<1>.........................................................
Moonshining<2>..................................................
Moonshining<3>...........................................
Moonshining<4>......................................
Waiting for ADB Device
Waiting for device
Powering off device. Unplug and reboot device (or something of that nature)
Hope you enjoyed the moonshine.
Keep in mind this is off of my memory of what the terminal said. I did NOT have to restart moonshine 4 times. I ran it once, and was done.
It took about 10-15 minutes all together.

What do I need to know about RUU to use Moonshine
Thanks for this tutorial. I have had a million problems trying to get S-Off but I'm hopeful that your technique will work since it seems like we both have the One S from Tmobile.
Can you please point me to some info about RUU? I've heard of them but not sure exactly what they are. If you have a link to a good tutorial it would be much appreciated.
p.s. Here is the link to my current thread documenting my difficulties getting s-off: http://forum.xda-developers.com/showthread.php?t=2658650

fonnae said:
Thanks for this tutorial. I have had a million problems trying to get S-Off but I'm hopeful that your technique will work since it seems like we both have the One S from Tmobile.
Can you please point me to some info about RUU? I've heard of them but not sure exactly what they are. If you have a link to a good tutorial it would be much appreciated.
p.s. Here is the link to my current thread documenting my difficulties getting s-off: http://forum.xda-developers.com/showthread.php?t=2658650
Click to expand...
Click to collapse
An RUU (recovery update utility, I believe) can be used to upgrade your device OR (in our case) return your phone to stock. There is a sticky in the development area that has a page with an RUU repository. That page should tell our exactly how to match the correct RUU with your phone. I'm sorry I don't have the link handy, I'm not on my laptop right meow.
Sent from my One S using Tapatalk

Thanks. Just a couple more quick questions. After I do moonshine:
Will I be root?
Can I simply flash cwm recovery and then restore my current nandroid backup?

fonnae said:
Thanks. Just a couple more quick questions. After I do moonshine:
Will I be root?
Can I simply flash cwm recovery and then restore my current nandroid backup?
Click to expand...
Click to collapse
You should be able to! Right after I moonshined, I went right into flashing a recovery and then flashed my ROM. It was so exciting not having to boot into bootloader and the use fastboot to flash the kernel. It was instantaneous!
Flash a recovery (I've noted having trouble with old recoveries meow)
Restore your nandroid and report back here?
I'm sure there will be another user with your question. I'll add it to the OP if all goes well. And it should go perfectly. The recovery should fix root, it'll ask you before you reboot the device.
Sent from my One S using Tapatalk