My Desire S was unlocked but still S-ON.
I want to change back to stock ROM and stock recovery.
I've try
- RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed
- RUU_Saga_HTC_Thailand_1.35.1113.2_Radio_20.28d.30.0805U_3805.04.02.01_M_release_183327_signed
but it doesn't work.
What method should I use to restore my phone without rooting (hboot 2.00.002).
Thank you.
P.S. Sorry for poor English.
You need to relock your bootloader before installing RUU.
Code:
fastboot oem lock
chninkel said:
You need to relock your bootloader before installing RUU.
Code:
fastboot oem lock
Click to expand...
Click to collapse
It's working but still got an error [140] bootloader version error (different from the first error before relocked).
I bought in Thailand so I think I should use this one
RUU_Saga_HTC_Thailand_1.35.1113.2_Radio_20.28d.30.0805U_3805.04.02.01_M_release_183327_signed
It has only one version of Thailand's RUU.
What should I do now?
Goldcard
Sent from my HTC Desire S
Hello,
I updated my HTC Sensation to stock ROM based on Android 4.0.3 ICS (build 3.33.401.6) now I want root it.
In bootloader mode I see that it result S-OFF and Bootloader LOCKED, following htcdev.com I try to unlock bootloader, in fastboot send file (Unlock-code.bin) but doesn't flash.
Can I root without unlocked bootloader?
see this thread,it might help you
but first read
http://forum.xda-developers.com/showthread.php?t=1661631
max299 said:
Hello,
I updated my HTC Sensation to stock ROM based on Android 4.0.3 ICS (build 3.33.401.6) now I want root it.
In bootloader mode I see that it result S-OFF and Bootloader LOCKED, following htcdev.com I try to unlock bootloader, in fastboot send file (Unlock-code.bin) but doesn't flash.
Can I root without unlocked bootloader?
Click to expand...
Click to collapse
I've recently up and downgraded from 3.32 to 3.33 and back.
I've S-OFF'd my device with Revolutionary.
So on 3.32 my device showed HBOOT 1.27.XXXX (dunno right now), S-OFF and REVOLUTIONARY on top.
On 3.33 it said S-OFF and LOCKED... This is quite annoying because I like fastboot
This and a "slowdown issue" on Viper Rom made me to go back to 3.32 - just go to the Firmwares thread and download the PG58IMG.zip and put it on your SDCard - now boot to bootloader and flash the PG58IMG
By the way, normally you can flash any rom with S-OFF on, you just need to get root by something like zergRush (dunno right now which tool).
S-ON meant at least on my previous phone that you can change the content of /system only within recovery. You weren't able to change your stock recovery to CWM, so you had to use "fake-flash" - you actually apply an update.zip that contained your CWM Recovery...
S-OFF meant you can change /system on a running android and change your recovery and don't have to use FakeFlash (like 3 seconds faster )
My phone was working flawlessly with CM9. Decided to try CM10/10.1 and AOKP. After RUU'ing 3.18, re-root, s-off, it wasn't worth the hassle. Constant reboots, wake locks, and other nonsense... after full wipes and flashes.
So now I'm trying to RUU 3.18 again to rule out something in this process fried some hardware.
Relocked BL
hboot 2.14
S-Off
Tried CID 11111111 and CWS_001
RUU error 170 unless I reboot to fastboot usb in BL
Re-downloaded the RUU (from dl3.htc.com/application/RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe)
And no matter what I do it just hangs on Sending. Same for fastboot oem rebootRUU -> fastboot flash zip OTA.zip
Any ideas? I'm ready to put this POS through the sheetrock.
Not sure if it matters or not but if you are s-off you don't have to relock the bootloader. I've ran multiple RUUs on phones that were s-off and had an unlocked bootloader. Not sure if that is the problem or not though. I would think that since you are s-off the state of the bootloader shouldn't matter but it may be worth a shot.
I agree with pside 15 if you are s-off you are suppose to be able to flash any RUU without having to lock the bootloader. And if u are having problems with CM 10.1 rom I recommend download again the rom or change the recovery I believe twrp 2.3.1.0 is one of the best and the last version 2.6.0.0 I even use clockwork mod recovery to flash aosp roms maybe that can help u after u flash the RUU
Good Luck .
Sent from my HTC One XL using xda premium
Also tried the 2.20 RUU, no dice.
Unlocked BL, no dice.
Formatted the entire sdcard, dropped directly to bootloader -> fastboot usb, and it seems to be taking the RUU now. Must not have liked something in the AOKP flash?
Hey,
I decided to make S-Off with the JuopunutBear methode but I have some problmes.
1. I unlocked my HTC Sensation by HTCDev and flashed the Inspiration rom. If I want to use the JuopunutBear methode I have to flash the Stock RUU (1.50.401.1), isn't it?
2. When I want to flash the Stock RUU I have to relock / lock my bootloader again and what I'm doing after relocking? I know how to relock but I want to unlock my Bootloader after the process again, is this possible?
I think that was all Sorry for the issues in the text.
StormUltimate said:
Hey,
I decided to make S-Off with the JuopunutBear methode but I have some problmes.
1. I unlocked my HTC Sensation by HTCDev and flashed the Inspiration rom. If I want to use the JuopunutBear methode I have to flash the Stock RUU (1.50.401.1), isn't it?
2. When I want to flash the Stock RUU I have to relock / lock my bootloader again and what I'm doing after relocking? I know how to relock but I want to unlock my Bootloader after the process again, is this possible?
I think that was all Sorry for the issues in the text.
Click to expand...
Click to collapse
it is possible to unlock it again
just use this time the unlock code.bin to flash it via fastboot command
done
but actually you can flash the stock rom from recovery and then follow the juopunutbear method.i think it will work
link in my signature(rooted stock ics)
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