Database Info

[Q] Unlocked, S-ON want to restore to stock ROM but can't use RUU

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

CID

Quick questions!!
My CID is BM__001 (Bell Mobility Canada). It is rooted, unlocked bootloader and CWRM recovery
I want the latest update (4,1 sense and not the 4.0 I'm stuck with and down the line the latest jellybean) WITHOUT a custom rom!
If I change Cid to HTC__001 I have read I can apply the international unbranded RUU and I will get them.
1. Will I have to flash radios or anything of the sort in order to make it work with my network in Canada?
2. What are the advantages of keeping my Bell CID?
3. What are the advantages of CHANGING to the HTC__001 CID?
4. Is it possible without s-off?
Sorry for the noobish questions put couldnt find simple answers to these questions!

nicolas0189 said:
I want the latest update (4,1 sense and jellybean) WITHOUT a custom rom!
Click to expand...
Click to collapse
The update you seek hasn't been released yet so it's impossible at this time.

I meant sense 4.1 OR the later jelly bean update my bad!
Sent from my HTC One S using xda app-developers app

nicolas0189 said:
Quick questions!!
My CID is BM__001 (Bell Mobility Canada). It is rooted, unlocked bootloader and CWRM recovery
1. Will I have to flash radios or anything of the sort in order to make it work with my network in Canada? - No.
2. What are the advantages of keeping my Bell CID? - You don't have a chance of messing anything up.
3. What are the advantages of CHANGING to the HTC__001 CID? - Faster updates, Less bloat.
4. Is it possible without s-off? - Yes.
Click to expand...
Click to collapse
If your phone already has the bootloader unlocked and a custom recovery why not just flash a rom?

Thanks for the answer!
Because I want to be able to OTA update without loosing all my data and settings..
With a custom ROM it will be a bit more of a hassle.
1. If I change my CID will I have to flash the RUU or will it do it by itself?

nicolas0189 said:
1. If I change my CID will I have to flash the RUU or will it do it by itself?
Click to expand...
Click to collapse
You would have to run a RUU with the one you would like to receive future updates from. This will relock your bootloader so you would have to unlock it again through htcdev.

Unlocked Unlocked bootloader S-ON, rooted, can I put custom ROM or pre-rooted ROM

Hello, I have Unlocked bootloader, S-ON and rooted telephone , can I put custom ROM, or pre-rooted RUU-ICS, Version HBOOT is 2.00.02.
I Know that must downgrade on 09.000.02 hboot-a, that I have S-off.
Can I put custom ROM, or RUU, or pre-rooted ROM, I want ICS-RUU. on phone with this caracteristics.
I really confused because S-ON, did I can do this.
Thanks advanced.

dejanxxxx said:
Hello, I have Unlocked bootloader, S-ON and rooted telephone , can I put custom ROM, or pre-rooted RUU-ICS, Version HBOOT is 2.00.02.
I Know that must downgrade on 09.000.02 hboot-a, that I have S-off.
Can I put custom ROM, or RUU, or pre-rooted ROM, I want ICS-RUU. on phone with this caracteristics.
I really confused because S-ON, did I can do this.
Thanks advanced.
Click to expand...
Click to collapse
Yes you can. You don't need to achieve S-OFF to install custom ROM. I don't recommend you to install Official RUU ICS because it has been reported many times to be buggy and laggy. If you want a better feeling of that, you should install IceDS or IceCreamSaga ROMs.

I have another problem. I wanted put RUU-ICS, but always get message ERROR 155. Every time, I dont know why. I am from Serbia, and people from HTC send me a link for RUU - ICS, and when I start with proces- eject ERROR 155-every time, after I tried another RUU-ICS again error 155, I tried 4 RUU- ics, and always error 155.
Why I get always this message, and what I do?. S-ON, bootloader-relocked, rooted phone.

i tried this and i flashed a custom rom with s-on and it just keeps booting into recovery mode

dejanxxxx said:
I have another problem. I wanted put RUU-ICS, but always get message ERROR 155. Every time, I dont know why. I am from Serbia, and people from HTC send me a link for RUU - ICS, and when I start with proces- eject ERROR 155-every time, after I tried another RUU-ICS again error 155, I tried 4 RUU- ics, and always error 155.
Why I get always this message, and what I do?. S-ON, bootloader-relocked, rooted phone.
Click to expand...
Click to collapse
Is your phone branded to any mobile carrier- by any chance?
Because if it was, to override the branded version by WWE 4.0.4
( world wide english )
you should use < gold card >
http://forum.xda-developers.com/showthread.php?t=1248095
If i remember correctly, error 155 refers to CID mismatch- wrong RUU version
But in your best interest is to double check what others say
Edit: unles something has changed,
there was only one ics ruu version for desire s
to be found on htcdev website..
How come you found four of them?

seagheart89 said:
i tried this and i flashed a custom rom with s-on and it just keeps booting into recovery mode
Click to expand...
Click to collapse
Did you flash the boot.img?
"If I were two-faced, would I be wearing this one?"
- Abraham Lincoln (1809-1865)

jugg1es said:
Did you flash the boot.img?
"If I were two-faced, would I be wearing this one?"
- Abraham Lincoln (1809-1865)
Click to expand...
Click to collapse
it didnt give me an option for boot.img it used the aroma installer

message ERROR 155 for original RUU ICS - means that you have unlocked bootlocker.
You must relock bootlocker with fastboot and start installation again - it will work.
Commant: "fastboot oem lock"
BR.

continiven said:
message ERROR 155 for original RUU ICS - means that you have unlocked bootlocker.
You must relock bootlocker with fastboot and start installation again - it will work.
Commant: "fastboot oem lock"
BR.
Click to expand...
Click to collapse
I have this problem. Because my girl friend dont want custom ROM, I install RUU-ICS. But always when start flashing,eject 155 error, bootloader first unlocked, after before process I locked again bootloader,and in HBOOT writing RELOCKED-you say this is mistake because bootloader is unlocked, it not true- on my case.
After I use HTC SYNC- register phone and recognized, everything pass easy,and ROM is installed.

seagheart89 said:
it didnt give me an option for boot.img it used the aroma installer
Click to expand...
Click to collapse
Since your device is still s-on you need flash the boot.img manually.
Extract the boot.img from the rom, boot your device into fastboot and enter
Code:
fastboot flash boot boot.img

Flashing pacman into my friend's desire s , after unlocking it, i tried every recovery, formatting every partition manually, and flashing the boot.img using fast boot, but could not get beyond the white HTC screen. I wonder why it was being so... I own a one s, and have used multiple sense and aosp based ROMs on it without a hiccup (am s-on).
Any help would be really appreciated
Thanks a lot
Sent from my One S using xda premium

syed.shoaib said:
Flashing pacman into my friend's desire s , after unlocking it, i tried every recovery, formatting every partition manually, and flashing the boot.img using fast boot, but could not get beyond the white HTC screen. I wonder why it was being so... I own a one s, and have used multiple sense and aosp based ROMs on it without a hiccup (am s-on).
Any help would be really appreciated
Thanks a lot
Sent from my One S using xda premium
Click to expand...
Click to collapse
This might be the reason http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge
"Happiness is good health and a bad memory."
- Ingrid Bergman (1917-1982)

[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

Is it ok to flash an unbranded stock ROM to carrier ROM?

as above.
I just want to avoid the carrier boot animation and whatever apps they have installed on the phone. Thanks!

You need to unlock bootloader via htc dev, root, s-off, change cid and mid then flash the unbranded firmware.