Recently I tried out a custom rom on my T-mobile branded One S, but I want to revert back to stock in order to do a S-OFF.
Before flashing the custom rom I ran the latest official t-mobile firmware, non rooted, original recovery, h-boot 2.16 and radio 1.15, S-ON. I unlocked the phone with an HTC-dev unlock token, flashed TWRP recovery and flashed a custom rom but left the phone S-ON.
Now I want to revert back to stock so I can do a S-OFF (which is needed for certain roms). I picked a RUU corresponding my CID t-mob101, in this case the only one I could find was:
Code:
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
I wanted to try this one, but the download link is dead:
Code:
RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09 es.50.02.07_2_10.09d.50.04L_ver2_release_287723_si gned.exe
I flashed back the original recovery, relocked the phone and tried to run the RUU. However when running the RUU I get an 155 error, which means the RUU isn't corresponding to my CID?
Does this mean i'm out of any options reverting to stock? I don't have a nandroid backup..
Thanks in advance!
Try Magio Rom and do S-off > then flash RUU. It works for me with hboot 2.16
First: S-off using facepalm follow this:
1) update your android sdk by clicking android sdk manager and then update from there.
2) after the update finished, shut down your computer and then turn it on again.
3) turn off your phone, just leave it off for like 5 minutes then go to recovery, wipe cache and dalvik cache, then fix permissions then reboot to system.
4) using ONLY the oem htc usb cable, plug in your phone to a usb 2.0 port.
5) just before doing anything else, first check if your phone is recognized by typing "adb devices", there you should see your devices' serial number if it's recognized correctly.
6) then proceed to the steps of facepalm.
Just remember to NOT do the fastboot flash firmware again after error 92. Then after finishing "fastboot oem boot", your computer should then recognize again your phone, then you could proceed to the last three commands.
This is how i managed to have s-off using facepalm. At first i was really frustrated of that error 99, but a little reading and searching won't hurt you.
Take note that the steps i just said may or may not be required to do so, and i don't know if all these steps are really necessary but i just want to share to you guys that have had the same problem as mine. Good luck guys. Hope this helps.
Click to expand...
Click to collapse
hongha_222 said:
Try Magio Rom and do S-off > then flash RUU. It works for me with hboot 2.16
Click to expand...
Click to collapse
Do I need superCID?
And what RUU is needed in step 5 of the facepalm S-OFF
mk13139 said:
Do I need superCID?
And what RUU is needed in step 5 of the facepalm S-OFF
Click to expand...
Click to collapse
not RUU / PJ4010000-OneS.zip
I think you don't need Supercid. Just try Magio first
hongha_222 said:
not RUU / PJ4010000-OneS.zip
I think you don't need Supercid. Just try Magio first
Click to expand...
Click to collapse
Ok thank you for your help, I will try it out soon!
However in the facepalm thread it says you do need supercid... And for supercid you do need to be S-OFF? That's strange..
When I have S-OFF, I can flash any ROM without boot.img and any RUU right?
mk13139 said:
Ok thank you for your help, I will try it out soon!
However in the facepalm thread it says you do need supercid... And for supercid you do need to be S-OFF? That's strange..
When I have S-OFF, I can flash any ROM without boot.img and any RUU right?
Click to expand...
Click to collapse
Magio rom don't need s-off. You might be stuck at supercid and s-off with hboot 2.16 !!! Try it first to do supercid and s-off
When you have s-off, you can flash any Rom with boot.img and RUU.
hongha_222 said:
Magio rom don't need s-off. You might be stuck at supercid and s-off with hboot 2.16 !!! Try it first to do supercid and s-off
When you have s-off, you can flash any Rom with boot.img and RUU.
Click to expand...
Click to collapse
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
m4te said:
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
Click to expand...
Click to collapse
Wait all of this would work on hboot 2.16? I have the same problem im s-on but super cid.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: I have an htc one s by rogers so would it matter if i use the nandroid i dont have a tmo htc one s
cyberusman said:
Wait all of this would work on hboot 2.16? I have the same problem im s-on but super cid.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: I have an htc one s by rogers so would it matter if i use the nandroid i dont have a tmo htc one s
Click to expand...
Click to collapse
I was on HBOOT 2.15 (from JB OTA). With that hboot, you can not get SuperCID only by altering it in mmcblk0p4, so I had to do s-off first. If you have SuperCID, why dont you try facepalm s-off method? http://forum.xda-developers.com/showthread.php?t=2155135
Please help. I'm confused. I have HBOOT 2.15
I'm S-ON.
I can't get supercid, because mmcblk0p4 is write protected or something. (I followed exactly the steps but it just doesn't stick)
And I can't S-OFF because for that I need Supercid. But you say you can S-OFF without having supercid?
Sent from my One S using xda app-developers app
rolo143 said:
Please help. I'm confused. I have HBOOT 2.15
I'm S-ON.
I can't get supercid, because mmcblk0p4 is write protected or something. (I followed exactly the steps but it just doesn't stick)
And I can't S-OFF because for that I need Supercid. But you say you can S-OFF without having supercid?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Have you tried my instructions that are on this page? http://forum.xda-developers.com/showpost.php?p=46939498&postcount=7
I haven't. Can I use that method and install the backup doesn't matter which firmware version I have?
Sent from my One S using xda app-developers app
m4te said:
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
Click to expand...
Click to collapse
When you had this problem were you on hboot 2.16? I have super cid but when i try to flash the zip file for face palm s-off it gives me error 99 unkown fail
Related
Hi,
After running with revolutionary and my rooted stock rom 1.47.401.4, I got yesterday a new OTA with 2.10.401.4 (2.3.5 and sense 3).
When trying to install it, it failed (blue android with big "!" on my screen)
First I downgraded my hboot back to 0.98.0000, but than I did something stupid .
I flash my hboot to the one provided with the OTA 2.00.0002, incl radio and all other stuff from the firmware.zip.
Now I ended up with a *** LOCKED *** HBOOT 2.00.0002, but also a 1.47.401.4 rom with android.
I tried to use the RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed.exe from windows, but that fails as the hboot has the incorrect version.
THe other thing I could do is go back to a 0.98 HBOOT, but that doesn't work either. the rom is ***LOCKED***, I have no root and it's S-ON.
I also searched for an RUU_Sage_HTC_Europe_*2.10.401.4*.exe as that might work because the HBOOT has the right version, but I could not find anything like that
Does anyone have an idea how I can go forward or how to go back ??
My phone is alive again as used the recovery.img procedure below and installed Saga3D 3.0. After that, I tried also the RUU installation to fully go back to stock, but that doesn't work. It complains about a security failure in hboot screen. I locked it back with 'fastboot oem lock', but that doesn't make the RUU work either.
lessimp said:
THe other thing I could do is go back to a 0.98 HBOOT, but that doesn't work either. the rom is ***LOCKED***, I have no root and it's S-ON.
Click to expand...
Click to collapse
did u try that or u think that wont work?
Before I updated to 2.00.0002, I created a dd-backup on the sdcard for the 0.98.000
when I however use adb to connect, I don't see how I can restore that back without root. I also didn't see the sdcard mounted
I was also thinking ....
Would it maybe also be possible to create a PG88IMG.zip with all the right software for 1.47.401.4 ? and restore that via recovery ? would the current hboot allow a downgrade ?
Today I was able to get the **LOCKED*** off to UNLOCKED via htcdev.com
In the thread http://forum.xda-developers.com/showthread.php?t=1299438
I found this (identical to my problem)
If anyone has the same problem and has hboot-2.00.0002 & S-ON you have to unlock the bootloader via htcdev.com site following all the steps and flash the EXT4 Recovery via FASTBOOT and NOT ADB.!!
Then go to recovery and flash any custom rom.
I don't unserstand what I have to do next. ADB does not work anymore, and only fastboot is available. I downloaded an EXT4 recovery (4EXTRecovery_v2.1.0_saga.zip) which have me an recovery.img and a META-INF folder.
When I name the zip image update.zip, and run
C:\android>fastboot.exe update update.zip
it fails with ...
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
How to I proceed to get it working ?
BTW, HBOOT is UNLOCKED but still S-ON
Please help
you already update hboot right. try this
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed
from here.
budingyun said:
you already update hboot right. try this
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed
from here.
Click to expand...
Click to collapse
You can RUU with that correct version or follow my instructions to achieve custom recovery/rom since you are already "unlocked":
Skanob said:
You should be able to change your recovery without any problem if your s-off or unlocked 2.xx.xx hboot s-on.
1. Get 4ext recovery.img
2. connect phone on fastboot
3. In cmd use these command to push the recovery image:
fastboot flash recovery D:\recovery.img (<- should be directory of 4ext recovery image)
fastboot reboot-bootloader
Now you should have 4ext recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
From here on you can now flash custom ROMs that you would like that is compatible to Desire S.
Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!
LSGio said:
Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!
Click to expand...
Click to collapse
1. No, if you have S-ON you can't create a NAND backup as you don't have a custom recovery.
2. ***TAMPERED*** means that an app or apps have gone into your /system/ partition, thereby triggering the tampered flag. You can remove this message by running a HTC RUU.
3. No, you first flash the zip file with the boot.img inside, then flash the boot.img in the bootloader. fastboot flash boot boot.img
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
Then yes you can make a backup and restore later. Just always full wipe, cache and dalvik cache wipe.
As far as flashing kernels/boot.img, if you are < hboot 1.13 then just flash via recovery. If your hboot is > or = to hboot 1.13tjen flash via fastboot or flash img GUI (available in the play store and in various threads).
And as of right now there is no s-off for the one s.
Sent from a baked One S
If I've helped hit the thanks button
LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.
KACE321 said:
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.
Click to expand...
Click to collapse
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?
LSGio said:
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?
Click to expand...
Click to collapse
fastboot oem writecid 11111111
usaff22 said:
fastboot oem writecid 11111111
i have 2 questions:
1.how many 1's do i have to write
2.can i get back to my cid and how?
Click to expand...
Click to collapse
Yes, you can make nand backups and restore them if you have a custom recovery. You don't need to have s-off for that but you do need to have your bootloader unlocked. Depending on your hboot version, restoring a nand backup will not restore your boot image. (1.09 and below will, 1.13 and up won't.) We do now have the means to downgrade hboot tho.
You get the *tampered* line if your recovery is unsigned. When you use a custom rom, you will most likely also get a red warning text over your boot splash. It's normal.
You have to extract the boot image from the rom zip and flash it in fastboot before you boot the new rom. This may even be before you flash the new rom. You can leave the rom zip unchanged and flash it in recovery.
-Jobo
if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Sent from my HTC One S using xda app-developers app
LSGio said:
if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Click to expand...
Click to collapse
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
LSGio said:
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Click to expand...
Click to collapse
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.
touch of jobo said:
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.
Click to expand...
Click to collapse
can you please tell me how can i download an ruu that matches my stock rom. cause when i get to the filefactory server it tells me that i need to buy premium because the file is larger than 500MB.
and the link to the ruu downloads is from this thread:
http://forum.xda-developers.com/showthread.php?t=1543588
if youll go to the first page and click the (ville S4) link you will see a list of ruu's but i can't download them because the size of them is larger han 500mb and i need premium.
Hi guys, recently my Desire S got some problems with sending/receivng sms and calls (tried 2 sim, different roms) so I decide to revert it back to stock rom and send it to RMA.
First i tried to install a RUU (ok, now I know it has'nt been a good idea), but installation failed with an error like "can't install, wrong bootloader".
Now I have a phone without recovery, with HBOOT 2.00.0002 and says:
***LOCKED***
***Security Warning***
SAGA PVT SHIP S-ON RL
HBOOT 2.00.0002
etc.
Could anyone tell me what to do now? Thank you all!
I would try and run the official ics ruu and then unlock via htcdev then flash custom recovery and then gain root and then change the misc version and then lock bootloader then finally run your region ruu to get back to stock but have a search about coz there is plenty of guides out there.
good luck
DuTY09 said:
I would try and run the official ics ruu and then unlock via htcdev then flash custom recovery and then gain root and then change the misc version and then lock bootloader then finally run your region ruu to get back to stock but have a search about coz there is plenty of guides out there.
good luck
Click to expand...
Click to collapse
Thank you, I will try!
I succefully installed ICS RUU and then unlocked with HTC dev. Then I flashed clockwork mod via fastboot. Now I'm still on S-ON and my question is: if I restore an old nandroid backup that I made when I was on old 0.98 hboot, will this overwrite my hboot? I don't know if it works since I'm still S-ON.
stavoltafunzia said:
I succefully installed ICS RUU and then unlocked with HTC dev. Then I flashed clockwork mod via fastboot. Now I'm still on S-ON and my question is: if I restore an old nandroid backup that I made when I was on old 0.98 hboot, will this overwrite my hboot? I don't know if it works since I'm still S-ON.
Click to expand...
Click to collapse
No, it won't change your hboot. But you will have to flash the boot.img from the backup in fastboot.
stavoltafunzia said:
I succefully installed ICS RUU and then unlocked with HTC dev. Then I flashed clockwork mod via fastboot. Now I'm still on S-ON and my question is: if I restore an old nandroid backup that I made when I was on old 0.98 hboot, will this overwrite my hboot? I don't know if it works since I'm still S-ON.
Click to expand...
Click to collapse
change your misc version then run the region ruu for your phone and you should be back as stock p.s once you have changed your misc version make sure your in fastboot mode when you run your region ruu
DuTY09 said:
I would try and run the official ics ruu and then unlock via htcdev then flash custom recovery and then gain root and then change the misc version and then lock bootloader then finally run your region ruu to get back to stock but have a search about coz there is plenty of guides out there.
good luck
Click to expand...
Click to collapse
DuTY09 said:
change your misc version then run the region ruu for your phone and you should be back as stock p.s once you have changed your misc version make sure your in fastboot mode when you run your region ruu
Click to expand...
Click to collapse
That worked fine, thank you!!
stavoltafunzia said:
That worked fine, thank you!!
Click to expand...
Click to collapse
no worries glad to help :highfive:
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
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