Database Info

[Q] S-Off from bootloader?

So I was going to buy a new phone, and trade in my sensation for it, so I reverted to stock. Except I installed the wrong RUU for my region and only noticed after re-enabling s-on, and then I was really stupid and tried to flash the right rom.zip while it was s-on and now my phone only boots into the bootloader... how can I S-off and reinstall the right RUU from only the bootloader? Revolutionary is constantly waiting for my device and htc's token id unlocker isn't recognising it either, and when it does it always comes up with an error

chocchief said:
how can I S-off and reinstall the right RUU from only the bootloader? Revolutionary is constantly waiting for my device and htc's token id unlocker isn't recognising it either, and when it does it always comes up with an error
Click to expand...
Click to collapse
do you have htc drivers installed?
if now you have 1.17-1.18 hboot version then revolutionary.io method is the only way to S-OFF
for flashing ruu from bootloader see here
http://forum.xda-developers.com/showthread.php?t=1672425 (step 4)
but first you have to be S-OFF

[Q] A quick Q about Evita.

Hi there guys,
Not sure if any of y'all remember way-back-when, but at one point my AT&T One X went into (what seemed like) a bricked state. For 8 months, I didn't touch it, charge it, yada-yada-yada. About 2 weeks ago I decided to give it a go so I charged it for a half hour and the mo'fo' decided to work. I updated my ViperXL ROM to 4.2.0 because I enjoyed it for its features. Now I'm left to ask the question, do I have to update HBOOT to flash a JB 4.3 ROM? I'm still unsure because I feel like I remembered seeing somewhere that your HBOOT has to be a newer version to run 4.3.
Thanks and regards, worldindo1.
NOTE: My current HBOOT version is reading "1.14.002".

Yes you do need to upgrade, it's written in the install instructions for the ROMs. It isn't just the hboot you need to update though, you need to run an RUU to make sure everything gets updated.
Sent from my Evita

timmaaa said:
Yes you do need to upgrade, it's written in the install instructions for the ROMs. It isn't just the hboot you need to update though, you need to run an RUU to make sure everything gets updated.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaaa,
So just relock bootloader, RUU file, and then unlock it again? Do you know of anyone who has just the firmware upgrade files from the RUU so I can do it from my Linux laptop? Thanks a ton, now I know I wouldn't have any problems or possibly brick my device haha.
Regards, worldindo1.

You need Windows to run an RUU properly, so you'll need to hit up friend to use their PC. You don't need to relock the bootloader as long as you get s-off first so I suggest getting s-off, it's pretty important because s-on + SuperCID + jb RUU = brick.
Sent from my Evita

timmaaa said:
You need Windows to run an RUU properly, so you'll need to hit up friend to use their PC. You don't need to relock the bootloader as long as you get s-off first so I suggest getting s-off, it's pretty important because s-on + SuperCID + jb RUU = brick.
Sent from my Evita
Click to expand...
Click to collapse
Howdy,
I am S-Off thankfully haha. I used XFactor back when it was still current. But I thought the main purpose of an RUU was to execute:
Code:
fastboot oem rebootRUU
fastboot flash zip (firmware).zip
Back when I had done some work with the HTC One V, we used unruu (for Linux) or on the Windows side, explored the RUU's %temp% folder to get the firmware files. Could I still issue those commands safely or have they changed how the RUU works? As well, since I'm S-Off, do I just issue all of the usual commands (minus the "fastboot oem lock") or ? Just making sure to do all of my homework before I jump in haha.
Regards, worldindo1.

Hang on, as far as I know Xfactor was a bootloader unlock exploit, that doesn't give you s-off. There's only one s-off method for our phone and that's the Facepalm method. Having an unlocked bootloader and having s-off are completely different. Can you please post your bootloader details?
Using unruu and pulling the RUU apart and flashing the firmware files is never how an RUU was supposed to be run, nor will it ever be. That's only doing a tiny portion of the job that actually running an RUU properly does. An RUU is an exe file which is meant to be run as an exe file, there is no other way to run it properly other than that. You connect your phone in fastboot mode and run the RUU in Windows and follow the prompts. Like I said though I really need to see your bootloader details (the first four lines) because I'm concerned you have s-off and bootloader unlock confused.
Sent from my Evita

timmaaa said:
Hang on, as far as I know Xfactor was a bootloader unlock exploit, that doesn't give you s-off. There's only one s-off method for our phone and that's the Facepalm method. Having an unlocked bootloader and having s-off are completely different. Can you please post your bootloader details?
Using unruu and pulling the RUU apart and flashing the firmware files is never how an RUU was supposed to be run, nor will it ever be. That's only doing a tiny portion of the job that actually running an RUU properly does. An RUU is an exe file which is meant to be run as an exe file, there is no other way to run it properly other than that. You connect your phone in fastboot mode and run the RUU in Windows and follow the prompts. Like I said though I really need to see your bootloader details (the first four lines) because I'm concerned you have s-off and bootloader unlock confused.
Sent from my Evita
Click to expand...
Click to collapse
Sorry about that my mind just drew a blank. I mixed up xfactor with facepalm haha. Yeah I'm s-off and bootunlocked.
Sent from Marianas Trench.

[Tutorial] Update to hboot 2.15 via RUU

Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.

Have you changed your CID?

mag13 said:
Have you changed your CID?
Click to expand...
Click to collapse
Please read again.
I was Super CID (11111111) but easily changed it to match TMobile (T-MOB010) with this tool for the update.
Click to expand...
Click to collapse

yooouuri said:
Please read again.
Click to expand...
Click to collapse
I am on Super CID and it does not work

mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
You have to change your CID back to the one for your RUU.

Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4 after I flashed MaximusHD and firmware?
Now my phone is like this:
Hboot 2.16
Radio 1.20.50 (worst radio ever)
S-OFF
CID 11111111
The rom's with sense 5 (I tried just maximus because the others are not compatible with the new firmware, the sdcard mount point for multi user) are killing my battery more than twice faster compared with ViperS. 2h Display vs 5h on Viper.
Thank you!

Can we use this as rollback from h-boot 2.16 ?

mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
I didn't think it would. Glad you didn't brick your phone and I'll update the OP based on your experiment.

flow27 said:
Can we use this as rollback from h-boot 2.16 ?
Click to expand...
Click to collapse
arazvan2002 said:
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4
Click to expand...
Click to collapse
Upgrading your hboot is a one way street, as far as I know. Can't you change the radio to something else?

I flashed Viper ROM. All the things are ok, gsm, wifi, etc just I can't see the internal memory like I should. I can browse to it file es file explorer but I need a method to default mount the new (4.2.2) location of it. Where is mounted by the internal memory in 4.1 JB? I discovered a file vold.fstab. Maybe I can change something like that somewhere to be able to use 4.1 ROM's again.
Sorry for OFF topic.

Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?

yooouuri said:
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
Click to expand...
Click to collapse
Yes you can if youre s-off.
Sent from HTC One S using android 4.2.2 sense 5

Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?

yooouuri said:
Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
Click to expand...
Click to collapse
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?

tivofool said:
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
Click to expand...
Click to collapse
That's the right thing to do, yes?

kilo94 said:
That's the right thing to do, yes?
Click to expand...
Click to collapse
Yes

I have the same problem. I can't go back to stock. I haven't changed my CID yet but I see that has not worked for you.
Did you try with HTC__001 ?

dhigby said:
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Click to expand...
Click to collapse
Hey I used your instructions and everything was perfect thank you. I used to upgarde and downgrade hboot even to restore the HTC one S

I got the RUU "Error: 159" again with both RUU from first post and testet with each common cid, but at the end I only got success with super cid and the TMO_US Ruu.
Now I am back on Hboot 2.15 and can flash again the newest custom-recovery, thank you very much.
I've heard about a flashabe standalone zip for the hboot 2.15 and found this:
Only for S4!
Boot into bootloader and enable fastboot.
Code:
fastboot oem rebootRUU
Wait for the black screen with white HTC symbol. (Like when you flash a RUU)
then enter:
Code:
fastboot flash zip modded_hboot_YOUR_NEEDED_HBOOT.zip
then if you want
Code:
fastboot oem boot
(Boot into your current ROM)
modded_ = The red text is removed and "tampered" is gone in bootloader.
Download:
modded_hboot_1.06.0000.zip - (397.1 KB)
modded_hboot_1.09.0000.zip - (400.6 KB)
modded_hboot_1.13.0000.zip - (399.0 KB)
modded_hboot_1.14.0002.zip - (405.3 KB)
modded_hboot_1.14.0004.zip - (373.2 KB)
modded_hboot_1.14.0005.zip - (373.6 KB)
modded_hboot_2.15.0000.zip - (400.9 KB)
modded_hboot_2.16.0000.zip - (398.6 KB)
Thx goes to: touch of jobo XDA Post Source
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
Greetings by Idijt

[Q] Restoring phone to default

I would like to put my phone back to stock, I currently have Cyanogenmod on there, rooted, unlocked bootloader and a custom recovery. I am wanting to sell my phone so I need to know how to put it back to stock. Any help is appreciated
I am s-on
unlocked bootloader
HBOOT 2.00.0002
4ext recovery

deadphone99 said:
I would like to put my phone back to stock, I currently have Cyanogenmod on there, rooted, unlocked bootloader and a custom recovery. I am wanting to sell my phone so I need to know how to put it back to stock. Any help is appreciated
I am s-on
unlocked bootloader
HBOOT 2.00.0002
4ext recovery
Click to expand...
Click to collapse
Basically, just follow a 2.00.002 to 0.98.00000 downgrade guide involving using htcdev, such as this one, starting from the step where you push misc_version onto the device (you're already rooted and unlocked).
Obviously, if you don't want to S-OFF, you don't have to run Revolutionary.
You will need to use a RUU, you will need to re-lock your bootloader immediately before the RUU step. If you're not sure about how to choose a RUU, please see the relevant section of my guide in my signature.
If you want to sell the device as a 2.00.002 (you meanie! xD) then you can apply a newer RUU than for 0.98.0000, just don't put on ICS D:

paulie-uk said:
Basically, just follow a 2.00.002 to 0.98.00000 downgrade guide involving using htcdev, such as this one, starting from the step where you push misc_version onto the device (you're already rooted and unlocked).
Obviously, if you don't want to S-OFF, you don't have to run Revolutionary.
You will need to use a RUU, you will need to re-lock your bootloader immediately before the RUU step. If you're not sure about how to choose a RUU, please see the relevant section of my guide in my signature.
If you want to sell the device as a 2.00.002 (you meanie! xD) then you can apply a newer RUU than for 0.98.0000, just don't put on ICS D:
Click to expand...
Click to collapse
I get permission denied when trying to change the misc_version number, any ideas?
EDIT: I just sorted it

deadphone99 said:
I get permission denied when trying to change the misc_version number, any ideas?
Click to expand...
Click to collapse
You need to run misc_version as root, use su to gain root in your terminal for when you issue the command. You may need to interact with a permission request on the phone screen.
If you have an old adb on your computer and your rom is android 4.x, you might need to get a newer adb for it to work properly (some security stuff was changed).

Haven't messed with my phone since before s-off was available. Unsure how to proceed.

Current Situation(summary):
rooted
unlocked
S-on
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
CID-11111111
Lastest TWRP installed 2.7.1.0
After attempting and failing s-off with Facepalm and Rumrunner as well as trying to get newer roms installed over the 4.2.2 rom
I had the S-on way.... had to do a factory reset because I could only get to the bootloader.
Now I have no ROM installed and can only get to bootloader and recovery. Device does show up under adb sideload and fastboot in the respective modes. cannot mount as a filesystem in TWRP for some reason
Not sure where to proceed from here to acheive s-off and get up to 4.4 aosp roms.
Do I need to update the firmware for any reason? Is there an old exploitable rom and Kernal that I can install that has good success with s-off? I'm just lost and frustrated so I'm asking for help.

bathnapkin said:
Current Situation(summary):
rooted
unlocked
S-on
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
Unsure if superCID or not
Lastest TWRP installed 2.7.1.0
After attempting and failing s-off with Facepalm and Rumrunner as well as trying to get newer roms installed over the 4.2.2 rom
I had the S-on way.... had to do a factory reset because I could only get to the bootloader.
Now I have no ROM installed and can only get to bootloader and recovery. Device does show up under adb sideload and fastboot in the respective modes. cannot mount as a filesystem in TWRP for some reason
Not sure where to proceed from here to acheive s-off and get up to 4.4 aosp roms.
Do I need to update the firmware for any reason? Is there an old exploitable rom and Kernal that I can install that has good success with s-off? I'm just lost and frustrated so I'm asking for help.
Click to expand...
Click to collapse
I was in a similar situation a few days ago. In my case i couldn't boot into Android or recovery mode and the device was stuck in a reboot loop. I run RUU to reset everything to original factory settings. You have to relock your bootloader before you run RUU. It'll reset your root etc and you'll have to start from scratch. This link has the details:
http://forum.xda-developers.com/showthread.php?t=2593037
If you're on Mac or Linux use this one:
http://forum.xda-developers.com/showthread.php?t=1668156
Good luck.

Inn0vative1 said:
I was in a similar situation a few days ago. In my case i couldn't boot into Android or recovery mode and the device was stuck in a reboot loop. I run RUU to reset everything to original factory settings. You have to relock your bootloader before you run RUU. It'll reset your root etc and you'll have to start from scratch. This link has the details:
http://forum.xda-developers.com/showthread.php?t=2593037
If you're on Mac or Linux use this one:
http://forum.xda-developers.com/showthread.php?t=1668156
Good luck.
Click to expand...
Click to collapse
Thanks! this Is what I was hoping would help me. Unfortunately I've discovered I do have super CID "11111111"
currently trying to find a fastboot only script that can S-off me which i'm not sure even exists. Or just a way to revert the cid to whatever the AT&T one is

Inn0vative1 said:
I was in a similar situation a few days ago. In my case i couldn't boot into Android or recovery mode and the device was stuck in a reboot loop. I run RUU to reset everything to original factory settings. You have to relock your bootloader before you run RUU. It'll reset your root etc and you'll have to start from scratch. This link has the details:
http://forum.xda-developers.com/showthread.php?t=2593037
If you're on Mac or Linux use this one:
http://forum.xda-developers.com/showthread.php?t=1668156
Good luck.
Click to expand...
Click to collapse
bathnapkin said:
Thanks! this Is what I was hoping would help me. Unfortunately I've discovered I do have super CID "11111111"
currently trying to find a fastboot only script that can S-off me which i'm not sure even exists. Or just a way to revert the cid to whatever the AT&T one is
Click to expand...
Click to collapse
There's no need to run an RUU at this stage. Just downgrade to TWRP 2.6 and you'll be able to use the 'mount usb storage' feature again to copy a ROM zip across. Use the Kickdroid ROM and try Rumrunner s-off again.
The last thing you wanna do is change your CID back, then you'll be totally screwed. Just do what I said above and you should be fine.
Transmitted via Bacon

timmaaa said:
There's no need to run an RUU at this stage. Just downgrade to TWRP 2.6 and you'll be able to use the 'mount usb storage' feature again to copy a ROM zip across. Use the Kickdroid ROM and try Rumrunner s-off again.
The last thing you wanna do is change your CID back, then you'll be totally screwed. Just do what I said above and you should be fine.
Transmitted via Bacon
Click to expand...
Click to collapse
I managed to relock, run the 2.2 RUU, re-unlock and root again to get an unbricked stock phone. Facepalm didn't work so I'll give kickdroid and rumrunner a go.
EDIT: Kickdroid seems to require a firmware higher than the one I have to work which requires s-off for me to get without bricking. know of any older roms that are unsecure and rumrunner will work on?
Just got frustrated and did the RUU again. but this time I managed to get s-off! don't know what I did different this time but thanks to both of you!

bathnapkin said:
I managed to relock, run the 2.2 RUU, re-unlock and root again to get an unbricked stock phone. Facepalm didn't work so I'll give kickdroid and rumrunner a go.
EDIT: Kickdroid seems to require a firmware higher than the one I have to work which requires s-off for me to get without bricking. know of any older roms that are unsecure and rumrunner will work on?
Just got frustrated and did the RUU again. but this time I managed to get s-off! don't know what I did different this time but thanks to both of you!
Click to expand...
Click to collapse
Kickdroid only needs the newer firmware to stop signal loss problems and random reboots. You could have used it to get s-off. But you got it in the end!
Transmitted via Bacon