[GUIDE] Install official ICS update using GoldCard - HTC Desire S

Very Strange that by using this method, my device remains S-OFF and UNLOCKED (!!)
And here is the guide:
A- Preparation:
- Download RUU.exe file from htcdev.com. Run it (without connecting your Desire S to the PC), proceed to Next, Next... but do not exit this app. Open folder %TMP%, search for rom.zip file, copy it to another location and rename to PG88IMG.ZIP. Now you can exit RUU app.
- GoldCardTool, download it here.
- An SD card (>1GB recommended)
B- Step-by-step:
- Insert SD card to the phone, format it.
- Connect phone to PC in Disk drive mode, don't forget to enable USB Debugging = ON.
- Run GoldCardTool.exe, press Get CID button to get CID.
- Go to http://psas.revskills.de/?q=goldcard and enter CID, press Download Goldcard to get goldcard.img file.
- Get back to GoldCardTool.exe, press Load Goldcard.img to load the file goldcard.img.
- Press Patch MMC, your SD card is now ready for goldcard.
- Copy PG88IMG.ZIP file to SD card.
- Shutdown phone and boot it into bootloader.
- Phone will start update process automatically. Don't touch it unless you see "Press Power to restart".
After this step, mine is S-OFF and UNLOCKED. So I can flash custom recovery and root easily.

Leaving you device S-OFF and unlocked after RUU has nothing to do with Goldcard.
It happaned probably because you have Alpharev hboot. RUU is bypassing flashing the hboot because Alpharev hboot has bigger version, but it flashes the rest of the RUU.
It happened to one of my friends also and we didn't use Goldcard.
Sent from my HTC Desire S using xda premium

I have hboot 2.00.0002 SHIP S-OFF

Flashing an RUU doesn't change the S-OFF, never has (not on the Desire/Sensation anyway)
Sent from my HTC One X using xda premium

EddyOS said:
Flashing an RUU doesn't change the S-OFF, never has (not on the Desire/Sensation anyway)
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It means ICS update by using Goldcard is a good way to keep the hboot unchanged.

EddyOS said:
Flashing an RUU doesn't change the S-OFF, never has (not on the Desire/Sensation anyway)
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is not true, unless you have XTC-clip S-OFFed device.
My old Desire was S-ON when I bought it. I made it S-OFF using Alpharev's tool and every time I flashed any RUU (with Goldcard) it made it S-ON again.
My current Desire S is S-OFF with XTC-clip which means permanent S-OFF, now even after RUU I am still S-OFF, but with newer hboot.
When I flashed the RUU (without any Goldcard) on my friends Desire S, which has Alpharev hboot 7.0... all the images flashed successfully except BOOT which was "Bypassed", so the Alpharev's hboot was not overridden by RUU, and the rom booted successfully.
My guess it is because it has bigger version then the on in the RUU.

dmatik said:
This is not true, unless you have XTC-clip S-OFFed device.
My old Desire was S-ON when I bought it. I made it S-OFF using Alpharev's tool and every time I flashed any RUU (with Goldcard) it made it S-ON again.
My current Desire S is S-OFF with XTC-clip which means permanent S-OFF, now even after RUU I am still S-OFF, but with newer hboot.
When I flashed the RUU (without any Goldcard) on my friends Desire S, which has Alpharev hboot 7.0... all the images flashed successfully except BOOT which was "Bypassed", so the Alpharev's hboot was not overridden by RUU, and the rom booted successfully.
My guess it is because it has bigger version then the on in the RUU.
Click to expand...
Click to collapse
I have hboot 2.00.0002 SHIP S-OFF before and after goldcard, so it is not Alpharev hboot.
I have sent my phone to repair once, so I'm not sure if it was XTC-clip S-OFF or not.

vndnguyen said:
I have hboot 2.00.0002 SHIP S-OFF before and after goldcard, so it is not Alpharev hboot.
I have sent my phone to repair once, so I'm not sure if it was XTC-clip S-OFF or not.
Click to expand...
Click to collapse
Please, get your facts straight. This guide is wrong on so many levels. You are furtherly confusing people.

mirok said:
Please, get your facts straight. This guide is wrong on so many levels. You are furtherly confusing people.
Click to expand...
Click to collapse
hi mirok, i have said that it's very strange that my device remains s-off and unlocked after updating by goldcard.
however everyone can use this guide to update ICS beside other guides.

Related

[Tutorial] [Discontinued] How to restore stock ROM and S-On after AlphaRevX S-Off

I am sorry to announce, but I am pulling this tutorial. Tutorial is not meant for branded phones and recently I am getting few of those asking for help!
Sorry unbranded device owners, but my intention is to have brick free world!
Have a nice day! And safe flashing.
P.s. FYI, new boot loader can be unlocked using htcdev.com and locked again using the same.
/Edzz
good to know if somthing goes wrong and must be done in warranty time
can I use your guide for my thread ? I will give you credit.. thanks.
Why not do it the easy way since you're already S-OFF?
Take the ENG HBOOT found here and put the PG88IMG.zip in the root of your SD card
Boot into the bootloader (Volume Down + POWER)
Go into FASTBOOT mode
The bootloader will automagically detect your new HBOOT and install it
After rebooting your phone you can install any RUU you want. That will bring HBOOT back to the installed original
Make sure you make a good backup up front and be carefull what RUU to flash. The newer ones will overwrite HBOOT with version 0.98.0002, which, up to this date, can't be put to S-OFF yet by Alpharevx. I recommand you install the oldest RUU version you can find. A list of original ROMS can be found here
Good luck!
@nodeffect
Feel free.
@jorgen2009
such approach won't work with Alpharev hboot. They appear to have kinda locked it by making it appear ar 6.x Hboot version. That means, that bootloader will bypass upgrade. Been there, tried that, didn't work
chiekurz said:
@nodeffect
Feel free.
@jorgen2009
such approach won't work with Alpharev hboot. They appear to have kinda locked it by making it appear ar 6.x Hboot version. That means, that bootloader will bypass upgrade. Been there, tried that, didn't work
Click to expand...
Click to collapse
The original ENG HBOOT didn't work if i recall correctly. Redownload the ENG-HBOOT and you'll notice the version has changed to a number higher than Alpharev's. It DOES work now, in fact, my phone is S-ON again as we speak
Will have to try that again.
jorgen2009 said:
Why not do it the easy way since you're already S-OFF?
Take the ENG HBOOT found here and put the PG88IMG.zip in the root of your SD card
Boot into the bootloader (Volume Down + POWER)
Go into FASTBOOT mode
The bootloader will automagically detect your new HBOOT and install it
After rebooting your phone you can install any RUU you want. That will bring HBOOT back to the installed original
Make sure you make a good backup up front and be carefull what RUU to flash. The newer ones will overwrite HBOOT with version 0.98.0002, which, up to this date, can't be put to S-OFF yet by Alpharevx. I recommand you install the oldest RUU version you can find. A list of original ROMS can be found here
Good luck!
Click to expand...
Click to collapse
So i downloaded 2 files:
The PG88IMG.zip and eng_hboot
what do i put on my sd card, only PG88IMG.zip or both of them?
.sh4d0w. said:
So i downloaded 2 files:
The PG88IMG.zip and eng_hboot
what do i put on my sd card, only PG88IMG.zip or both of them?
Click to expand...
Click to collapse
Only the PG88IMG.zip, don't rename or extract it or it won't work, just put the file in the root of your SD card
So what is the use of Eng S-Off.rar?
And another question the RUU is an .exe?
And is this old enough RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed ?
Thanks.
LE: i flashed the pg88img.zip and i am still Alpharevx hboot 6.xxxxx etc (but the update was successful)
Maybe... if i flash a RUU? I just wanted to get eng s-off.. don't want to get s-on now
.sh4d0w. said:
So what is the use of Eng S-Off.rar? [/QUOTE
Look at this thread
And another question the RUU is an .exe?
Click to expand...
Click to collapse
yes, it's direct from HTC and unfortunately can only be run from within Windows
And is this old enough RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed ?
Click to expand...
Click to collapse
yes, that comes with the HBOOT 0.98.0000
Thanks.
Click to expand...
Click to collapse
your welcome
LE: i flashed the pg88img.zip and i am still Alpharevx hboot 6.xxxxx etc (but the update was successful)
Maybe... if i flash a RUU? I just wanted to get eng s-off.. don't want to get s-on now
Click to expand...
Click to collapse
just check again in fastboot, ENG HBOOT version has changed to 6.98.2000 iirc. After running the RUU it should be 0.98.0000 again as ENG HBOOT can be overwritten in contrast to the AlphaRevX HBOOT. If you only want ENG HBOOT don't flash the RUU obviously
Click to expand...
Click to collapse
Ok i just checked.
I have like this
--- AlphaRev ---
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
So nothing changed.... and i did the update like... 5 times
It asks vol + to install update
And after it's finished
Power down to reboot.
Maybe i got the wrong file? The PG88IMG.zip attached here http://forum.xda-developers.com/showthread.php?t=1113820
.sh4d0w. said:
Ok i just checked.
I have like this
--- AlphaRev ---
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
So nothing changed.... and i did the update like... 5 times
It asks vol + to install update
And after it's finished
Power down to reboot.
Maybe i got the wrong file? The PG88IMG.zip attached here http://forum.xda-developers.com/showthread.php?t=1113820
Click to expand...
Click to collapse
You can try with this modified ENG Hboot for devices with AlpharevX
Please, report if works
heavyhms said:
You can try with this modified ENG Hboot for devices with AlpharevX
Please, report if works
Click to expand...
Click to collapse
Nope.... doesn't work at all. Not even loading.
.sh4d0w. said:
Nope.... doesn't work at all. Not even loading.
Click to expand...
Click to collapse
Try to re-download Eng Hboot (normal and modified) after deleting browser cache. Disable antivirus software during download and transfer to microsd.
Do not download file directly with desire S browser: use a pc
You can try also with a different microsd card
.sh4d0w. said:
Nope.... doesn't work at all. Not even loading.
Click to expand...
Click to collapse
Should be the right version...
BTW I changed the link in my first post here to this one. I accidently posted the wrong version
BTW...... the original eng hboot is 1 mb and this modified one is only 260 kb ???
Maybe that's why it doesn't work.
In winrar i have like this
Name__________________Size________Packed
engHBOOToverARX.img___1.048.576____262.273
Added your guide to my thread. Thanks for this one, it's very useful.
p.s. you got a typo for the title of this thread. "Tutorial", not totutial... please correct it, thanks
I did it.. using the adb comands in first page..
LE: Great! Alpharev beta site doesn't work.....stuck with stock lol ))
LE2: New alphareve+unrevoked site http://revolutionary.io/ Back to S-OFF
chiekurz said:
(Windows only? Not sure if RUU works on other platforms)
With thanks to user Murchelago for providing adb method to restore stock boot and HTC for providing RUU's here is step by step, how to return to stock after Alpharevx S-Off.
Prerequisites:
Debugging mode on
Root access
Hboot.img (attached)
RUU for stock restore. Can be downloaded here: http://forum.xda-developers.com/showthread.php?t=1002506
How to:
1. Put the hboot.img you want to flash in the root of the sdcard.
2. In cmd run the following commands (after each command press enter):
adb devices
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
reboot bootloader
3. RUN Downloaded RUU
4. You are on stock again!
After running ADB commands and rebooting into bootloader, you will get security warning. This is normal, just continue with flashing RUU.
Worked for me perfectly 3 times without any issues. However issues might occur and I can not take any responsibility for them. Use this tutorial on your own responsibility
Click to expand...
Click to collapse
I can confirm that you CANNOT just RUU a device. As the name implies, ROM Update Utility.
I followed everything on the first page and can confirm that I've successfully reverted back to HBOOT 0.98.0000.
AFAIK my phone was flashed with the hTC_Asia_WWE_1.31.707.2 on stock.
I tried to RUU using the oldest firmware that I can find, HTC_Europe_1.28.401.1. But it gave me the error 131 (AFAIK) customer ID error. About language and stuffs. Model ID, etc.
So I tried to RUU with the oldest hTC_Asia_WWE_1.31.707.2 (the oldest that I can find that is an ASIA one.). Then it gave me the error 140 (bootloader error). The readme doesn't have any information on this one, even on the net for HTC Saga.
So I tried to RUU with the "LATEST" hTC_Asia_WWE_1.48.707.1 that I found and everything works well. I really am not quite sure why I was not able to "downgrade", just "upgrade".
AFAIK i just updated my radio to the latest 20.28I.30.085AU_3805.06.02.03_M found on the hTC_Asia_WWE_1.48.707.1 when I was S-OFFed. It may have something to do with it.
Just an additional info. I'm now S-ON and on-stock hTC_Asia_WWE_1.48.707.1_20.28I.30.085AU_3805.06.02.03_M

Need help unrooting and turning s-on

Got to return phone yet again to be repaired.
I usually use the RUU but it wont work this time.
Any help what else i can do?
What do you men won't work...
Provide more information
Swyped from my Desire S using XDA Premium
Hi,
i have revolutionary S-OFF
hboot 6.98.1002. and stock 1.47.401.4 rom
at the same time i do not have root access and my recovery mode shows me the red triangle with !
i want to be S-ON again. I have tried this method http://forum.xda-developers.com/showthread.php?t=1187231&page=13 but it's not working for me.
could you please help me?
OK so you have reverted to a stock ROM, which has worked - but the Revolutionary S-OFF has a kind of protection to stop RUUs rewriting the bootloader etc
Recovery appears like that because the RUU has changed something meaning ClockworkRecovery isn't working anymore (not too sure of the specifics). You should still be able to get past the red triangle by pressing power + vol up (or + vol down, I forgot).
You can reinstall Clockwork again using the S-OFF utility if you need to.
You need to follow this guide http://forum.xda-developers.com/showpost.php?p=16031365&postcount=4
The first part is vital as it removes the Revolutionary boot lock (or whatever its called).
it did not worked.
when i flash PG88IMG.zip it says "hboot bypassed" and i'm still S-OFF with hboot 6.98.1002
Just checking but it's not a suspect emmc is it?
Sent from my HTC Desire
I would flash the hboot with the 0.98 hboot then redo the ruu process which will then be also able to overwrite the hboot
Sent from my HTC Desire S using xda premium

[Q] hboot 1.23 & s-on problem

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.

[Q] How to choose RUU?

Hi guys!
I have some problem with HTC Sensation. It boots only till HTC logo. And nothing more! On this device isn't OS.
Some guys said that I need to install RUU exe file through computer. I did it but received error 130 (need other version of RUU, I think).
So can you recommend something?
S-ON, hboot 1.18.000, radio 10.14.9035.02_02
Thank you!
Flexaitis said:
Hi guys!
I have some problem with HTC Sensation. It boots only till HTC logo. And nothing more! On this device isn't OS.
Some guys said that I need to install RUU exe file through computer. I did it but received error 130 (need other version of RUU, I think).
So can you recommend something?
S-ON, hboot 1.18.000, radio 10.14.9035.02_02
Thank you!
Click to expand...
Click to collapse
What exactly do you mean by "On this device isn't OS".Do you mean you haven't install some custom OS on your device or it has no OS at all.If you have erase the OS the bootloop is something natural.
I did a google search for your radio version and according to this I found answers only on some german forums.So your cid (as long as you are s-on) should be possibly a German or a European one.
You can download the latest Europe version from here and give it a try.
You can find your cid number using fastboot.Just get into fastboot mode of your hboot and give the command fastboot getvar cid.
If your bootloader is HTCDEV unlocked give the commands:
Code:
fastboot oem lock
fastboot reboot-bootloader
After that your hboot should say Relocked instead of Unlocked.Then install the RUU.
You could also give it S-OFF using this guide (Does not require HTCDEV unlock method):
[GUIDE] Juopunutbear S-OFF NO HTCDEV UNLOCK | ROOT (1.2x HBOOTS)
If you are S-ON you can use a RUU only with hboot 1.18 in your case
Read this topic to know all about RUU
claudianolo said:
If you are S-ON you can use a RUU only with hboot 1.18 in your case
Read this topic to know all about RUU
Click to expand...
Click to collapse
Why exactly he should use an RUU with hboot 1.18?!
I know that the version of hboot can be upgraded normally but cannot be downgraded as long as you are S-ON.If you are S-OFF you can downgrade everything.Also if you want to install an older RUU and you are S-ON you have to use a gold card and you patch the version of the misc partition to an equal or lower one for the RUU you are going to use.
Flexaitis said:
Hi guys!
I have some problem with HTC Sensation. It boots only till HTC logo. And nothing more! On this device isn't OS.
Some guys said that I need to install RUU exe file through computer. I did it but received error 130 (need other version of RUU, I think).
So can you recommend something?
S-ON, hboot 1.18.000, radio 10.14.9035.02_02
Thank you!
Click to expand...
Click to collapse
Hi,
Try THIS ONE
Did you unlock your phone with HTC DEV?
If not, then , DO NOT.

[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

Categories

Resources