Related
Is there an S-OFF available for HBOOT 1.20? Saw "locked" after flashing 1.20 and S-ONed phone. Finally unlocked using htcdev but nothing I found could help me downgrade HBOOT and do S-OFF again. Do not have SuperCID atm.
there is a thread on this your still rooted even though it says s on
Yeah, I am still rooted and can get into recovery and flash ROMs. But I am having issues with signal and I cannot flash anything because 1.20 does not support fastboot commands. I would like to downgrade but cannot. I tried flashing the customized p85img.zip with my CID T-MOB010 and it would just return to menu w/o any messages.
Make sure it's p85img in the file name.
Don't INSERT .zip at the end. It should automatically be a .zip file.
The file is named correctly.
There is a thread here ima try and find it were you can revert back to hboot 1.17.0000
Sent from my HTC Sensation using xda premium
silverion said:
Is there an S-OFF available for HBOOT 1.20? Saw "locked" after flashing 1.20 and S-ONed phone. Finally unlocked using htcdev but nothing I found could help me downgrade HBOOT and do S-OFF again. Do not have SuperCID atm.
Click to expand...
Click to collapse
i m facinf d same problm wit my sensation with bootloader unlocked thro htc dev. i m unable 2 flash any radios. Even i m unable to flash any custom firmware also. I need ur help if u found any solution.
either downgrade your hboot to 1.17 or update to ics 3.24 which has hboot 1.27 (unlocked) and you will have advance fastboot commands
Same exact problem here, semi-bricked my phone before I went over to Htcdev.... attempting to flash a p85img for HBOOT 1.17 or any p85img does nothing but parse it. Searched all day today couldn't find a thing to help...Others have suggested just waiting until Revolution comes out with an Unlock for 1.20 but I'm determined to find a solution for us.
Hi,
I have sensation with hboot 1.23 s-on, unlocked with official htcdev and custom rom installed.
I can't flash any RUU, even it's original orange UK RUU, I can't s-off with revolutionary because max hboot version is 1.18 and can't unlock network!!
any ideas?
pls help...
Flash previous Firmware, see if work .
Same problem here but I am stuck on 1.20. No firmware can be flashed, neither through RUU or PG58IMG.zip. RUU flashing ends with message security failed, update failed. PG58IMG.zip simply returns to menu after parsing. Fastboot returns with "remote, not allowed".
Please help !
silverion said:
Same problem here but I am stuck on 1.20. No firmware can be flashed, neither through RUU or PG58IMG.zip. RUU flashing ends with message security failed, update failed. PG58IMG.zip simply returns to menu after parsing. Fastboot returns with "remote, not allowed".
Please help !
Click to expand...
Click to collapse
When I tried an ICS rom, I flashed the 1.20 hboot and firmware. All I had to do to get rid of 1.20 hboot was flash the PG58IMG.zip of the eng hboot.
Sent from my HTC Pyramid using xda premium
tigrnaz said:
Hi,
I have sensation with hboot 1.23 s-on, unlocked with official htcdev and custom rom installed.
I can't flash any RUU, even it's original orange UK RUU, I can't s-off with revolutionary because max hboot version is 1.18 and can't unlock network!!
any ideas?
pls help...
Click to expand...
Click to collapse
If you are s-on you can't flash anything. You have to wait until revolutionary updates to 1.23
Sent from my Kindle Fire using Tapatalk
How did you guys end up with S-On?
Were you S-On before flashing hboot 1.23 or you just flashed an old official RUU over 1.23?
---------- Post added at 02:11 AM ---------- Previous post was at 02:09 AM ----------
ar4l said:
If you are s-on you can't flash anything. You have to wait until revolutionary updates to 1.23
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Revolutionary won't S-off for 1.23 in near future...:-/
Pure stupidity for me. I usually pay more attention to what's going on. When I flashed firmware that contained HBOOT 1.20 it did flash 1.20 but got stuck in bootloader mode and did not update radio.
I followed with attempt to downgrade to 1.17 and restore S-On so I could repeat revolutionary. When it simply returned to the menu w/o any error (but in fact stayed on 1.20) I did writesecureflag 3.
So the best I did was unlock bootloader through HTCDEV. I am still however stuck at 1.20, old radio and while I can flash roms, I cannot flash radio or hboot or RUU. normally I would just wait it out but wi-fi does not work in new roms for me, prob because of old radio.
I have the same problem, and there are many people have the same problem. Hope revolutionary would support hboot 1.23. But previous revolutionary s-off the bootloader when phone is on.
silverion said:
Pure stupidity for me. I usually pay more attention to what's going on. When I flashed firmware that contained HBOOT 1.20 it did flash 1.20 but got stuck in bootloader mode and did not update radio.
I followed with attempt to downgrade to 1.17 and restore S-On so I could repeat revolutionary. When it simply returned to the menu w/o any error (but in fact stayed on 1.20) I did writesecureflag 3.
So the best I did was unlock bootloader through HTCDEV. I am still however stuck at 1.20, old radio and while I can flash roms, I cannot flash radio or hboot or RUU. normally I would just wait it out but wi-fi does not work in new roms for me, prob because of old radio.
Click to expand...
Click to collapse
Well what's done is done... Wait for ICS official RUU... Probably it will flash...
Atleast thug can flash a Rom...
For wifi issue, i suggest you reset the router...I have doubts that will solve your issue..
ar4l said:
If you are s-on you can't flash anything. You have to wait until revolutionary updates to 1.23
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Seems to be the only solution at this point. Based on revolutions history, how long would you say that might be?
RUU_PYRAMID_ICS_HTC_Europe_3.12.401.2_Radio_11.65.3504.00U_11.19.3504.29_2_test_233440
HBOOT 1.23.000 S-ON / unlock or relock ( secureflag 3) without firmware
now i have HyperSensation_v1.8_R
4ext recovery touch
Does anyone know how to upgrade or downgrade hboot?
This guide will help
http://forum.xda-developers.com/showthread.php?p=23222794
Sent from my Pyramid-T
i cant flash PG58IMG.ZIP with S-ON
and cant use revolutionary on 1.23.000 hboot
[email protected] said:
i cant flash PG58IMG.ZIP with S-ON
and cant use revolutionary on 1.23.000 hboot
Click to expand...
Click to collapse
wait for revolutionary to get updated... thats the only way. you are stuck with your setup
[email protected] said:
i cant flash PG58IMG.ZIP with S-ON
and cant use revolutionary on 1.23.000 hboot
Click to expand...
Click to collapse
Use adb as alternative to pg58img to flash recovery as per the guide.
Flashing the boot.img part of the ruu then gives you downgraded bootloader enabling you to s-off.
Sent from my Pyramid-T
1) i can use revo only for 1.18.xx or lower (i have 1.23.000)
2) with S-ON i cant change hboot
"wait for revolutionary to get updated... thats the only way. you are stuck with your setup" how long? if it ever will
[email protected] said:
1) i can use revo only for 1.18.xx or lower (i have 1.23.000)
2) with S-ON i cant change hboot
"wait for revolutionary to get updated... thats the only way. you are stuck with your setup" how long? if it ever will
Click to expand...
Click to collapse
Nobody knows... Maybe you could pay a visit on the revolutionary irc channel #revolutionary on server irc.freenode.net and ask them
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
Hi, I have same problem, hboot 1.23 and S ON. How to solve problem? Need help.....
konzul said:
Hi, I have same problem, hboot 1.23 and S ON. How to solve problem? Need help.....
Click to expand...
Click to collapse
I was in the same situation, used the Juopunutbear S-OFF method and it worked. Don't forget to thank the developer.
So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2.
If you have S Off, this doesn't matter, but you should always try to flash the oldest RUU, so that it is easier to S Off later, unless you don't intend to perform S Off again.
Click to expand...
Click to collapse
I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get
error: -5001. Please make sure you have finished any previous setup and closed other applications.
Click to expand...
Click to collapse
Is the problem with compatibility or something else?
Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?
SsBloodY said:
So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2. I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get Is the problem with compatibility or something else?
Click to expand...
Click to collapse
SsBloodY said:
Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?
Click to expand...
Click to collapse
1. RUU naming convention
RUU_Pyramid_<an extra LE in the name if XE>_HTC_<country/cariier>_<rom main version>_Radio_<radio version>_release_<release version>_signed.exe
dont bother about release version ..we dont need that
the only concerns are ..
country/carrier -> which determines the cid
rom main version ->explains whether youy are on GB or ICS (lesser the version ..older it is ...only between same country/carrier RUU's)
radio version -> tells the radio
2.oldest RUU ..ive explained earlier ..the main version should be least ..but this comparison is only valid if the country/carrier matches
eg:
in case of
RUU_pyramid_tmous_1.52.xx
and
RUU_pyramid_europe_1.27.xx (you cant say which one is oldest)
3.no firmware questions when we are talking about RUU (firmware arises when you talk about custom roms)
RUU has everything ...it wipes everything and converts it to stock (RUU cant touch the SOFF and CID though ..they can be changed only manually ..i.e. by we doing it manually by commands)
4.which RUU ..is you decide by CID ...
if you are supercid ..and dont know the original cid
you need to select the RUU based on your country and carrier
there is an excellent guide on RUU and it explains everything
here is the link to it ...do read it
(it helps you in finding right RUU too )
RUU RELEATED INFO AND FLASHING GUIDE
also remember by flashing RUU ..you wont lose SOFF ...unless you change it manually ..to know how to change it please refer the above guide
also i believe this answer ..answers your second post questions too
Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app
SsBloodY said:
Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
im confused
did you mean you solved it ? or are you asking me how to bypass that error ?
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe
I can't solve the problem. I connect it in bootloader/fastboot and try to run the RUU.exe. And I did revolutionary S-OFF.
Hey no idea that
error: -5001. Please make sure you have finished any previous setup and closed other applications.
is pretty annoying.
What is the CID currently on the phone ?
The RUU with xxx.401.xxxx IRC will require SuperCID (11111111) or a CID of HTC__001.
1.27... will end up installing HBOOT 1.17.0008 (just gone through the process on my replacement replacement phone.
As mentioned earlier you'll keep S-OFF and your existing CID after installing the RUU.
As far as the comms are concerned have you got the latest HTC drivers on the PC ?
---------------snip-------------
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe
---------------snip-------------
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.
I am super CID.
gol_n_dal said:
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.
Click to expand...
Click to collapse
regarding RUU running normally ..you should have usb debugging enabled ..and need to have proper drivers too to recognize the device ..
running from fastboot no hassle there.. (most 155 errors can be prevented from running from fastboot)
couple of people were thrown error 99 when they ran RUU with unlocked bootloader ..so relock is a safer bet to prevent that error too
Hi,
I'm trying to go to the stock rom because I have to return my phone because I have battery problems and dust behind my screen.
But when I try to flash a stock rom it doesn't work. It says that I using the wrong image update.
Current image is 1.11.401.110 and I want to go to the lastest stock rom 3.32.401.105
What do I have to do?
Thanks
What was the original CID ? What CID do you now have ?
1.11.401....... wow that seems really old.
x.xx.401.... will need CID "HTC__001" or SuperCID "11111111".
What exactly does it say when you run the RUU ? Does it connect OK to the Sensation, does it say what the existing version is on the phone ?
gol_n_dal said:
What was the original CID ? What CID do you now have ?
1.11.401....... wow that seems really old.
x.xx.401.... will need CID "HTC__001" or SuperCID "11111111".
What exactly does it say when you run the RUU ? Does it connect OK to the Sensation, does it say what the existing version is on the phone ?
Click to expand...
Click to collapse
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
tommeke19 said:
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
Click to expand...
Click to collapse
OK I don't understand where 1.11.401.110.... figures in the situation. If I understand correctly that is a custom ROM based off a different platform with Sense 4.0. Probably wrong though..
Are you fully S-OFF (clutching at straws here). Assuming you are you should be able to install an RUU easily. I recently went from 3.32.161.... to 3.32.401.. then back to 1.27.161... with no issues at all.
I'm sure someone more able than me can help you here.
GL
tommeke19 said:
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
Click to expand...
Click to collapse
ok you are SOFF seeing that you have revolutionary HBOOT ..
so when returning stock ...its better to flash the correct stock...which can be found using CID
but as you have supercid now ...you need to know your original cid or the carrier/country the phone is linked to ..for finding the proper stock RUU
this guide helps you in fiding the proper stock RUU and it has flashing instructions too
Hi,
I followed the link and tried to get my CID but I only get 11111111 so i don't know what I have to download now
Install "cid getter" from the market.
AFAIK the entry for "ro.cid" should tell you your original CID.
e.g. It says VODAP001 for me while "fastboot getvar cid" gives "11111111".
tommeke19 said:
Hi,
I followed the link and tried to get my CID but I only get 11111111 so i don't know what I have to download now
Click to expand...
Click to collapse
from which country you bought the phone from and to which carrier it is linked to ?
Thanks everyone for helping me, but after using google I've found a site and found the solution.
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