[TUT] Return official S-ON HBOOT 1.02 - HTC Aria Android Development

Restoring S-ON and HBOOT 1.02 firmware with the restoration of the American
Liberty_downgrade.img in the fastboot.zip
Install the driver fastboot
Liberty_downgrade.img image is complete, and nothing more needs to be done!
1) Copy of the archive folder fastboot, such as the root of drive C: \
2) Run cmd and type:
Code:
cd C:\fastboot
3) After the return to the default firmware from backup, or in case of emergency swing RUU from HTC Aria and install (Warning: This information will be deleted!)
4) Enter the hboot and switch mode fastboot, before connecting to your PC via USB cable.
5) Enter:
Code:
fastboot flash hboot liberty_downgrade.img
and press Enter
With the device, do not do anything! Do not reboot, not disconnected from the PC!
6) Run the RUU again from HTC Aria. At the end of the installer will complain about the error device ID, you can now go in and admire HBOOT labeled S-ON and release HBOOT 1.02
Thank you very much team member Alpharev - kmdm
Sorry for my bad english!
Md5 for liberty hboot fb9a82200b14508cb40be69f43937fc7
Coming soon this manual for europe version!

It's finally here (although I don't need it). Have you tested it yourself?

Yes, i'm tested on myself devices! Working!

very nice!! thanks for sharing. good to know there is a way back if needed

Works PERFECTLY!
I admit that I was skeptical, but this process worked perfectly on the first try on my Aria that I have to return for warranty replacement to AT&T. Entire process took a little more than 10 minutes!
Thanks so much for posting this method!
dimon2242 said:
Restoring S-ON and HBOOT 1.02 firmware with the restoration of the American
Install the driver fastboot
Liberty_downgrade.img image is complete, and nothing more needs to be done!
1) Copy of the archive folder fastboot, such as the root of drive C: \
2) Run cmd and type:
Code:
cd C:\fastboot
3) After the return to the default firmware from backup, or in case of emergency swing RUU from HTC Aria and install (Warning: This information will be deleted!)
4) Enter the hboot and switch mode fastboot, before connecting to your PC via USB cable.
5) Enter:
Code:
fastboot flash hboot liberty_downgrade.img
and press Enter
With the device, do not do anything! Do not reboot, not disconnected from the PC!
6) Run the RUU again from HTC Aria. At the end of the installer will complain about the error device ID, you can now go in and admire HBOOT labeled S-ON and release HBOOT 1.02
Thank you very much team member Alpharev - kmdm
Sorry for my bad english!
Click to expand...
Click to collapse

Once the phone has been restored to S-ON w/ HBOOT 1.02 using this method, can Revolutionary be used to S-OFF again?

drumist said:
Once the phone has been restored to S-ON w/ HBOOT 1.02 using this method, can Revolutionary be used to S-OFF again?
Click to expand...
Click to collapse
Yes) can used revolutionary)

It would be nice if people who post hboots would post the md5sums as well. It is irresponsible not to.

Md5 has been posted) thanks!

Does anyone know if this works on htc gratia,hboot 1.03,bootloader unlocked (htcdev.com)

s19r83g said:
Does anyone know if this works on htc gratia,hboot 1.03,bootloader unlocked (htcdev.com)
Click to expand...
Click to collapse
The new HBOOT 1.03 is already S-ON. You can change it's state from LOCKED to UNLOCKED and back to RELOCKED using fastboot commands.

i not tested with this hboot 1.03, unlikely...

You cannot downgrade from HBOOT 1.03 to HBOOT 1.02 (or earlier).

s19r83g said:
Does anyone know if this works on htc gratia,hboot 1.03,bootloader unlocked (htcdev.com)
Click to expand...
Click to collapse
No, but I know how to remove those.
High level, not for noobs, and certainly not step by step noobs will look for:
install cwm
update the mainver in the misc partition to 1.11.111.1 from cwm (dump/hex edit, reflash required)
back up the current ROM with cwm
relock the bootloader
make a goldcard
flash an aria RUU with a 1.02.1002 hboot.
run revolutionary
restore your gratia rom from cwm backups.

Please attach hboot 1.03 I will try to patch it for Gratia, thanks!

munjeni said:
Please attach hboot 1.03 I will try to patch it for Gratia, thanks!
Click to expand...
Click to collapse
HBOOT 1.03 is attached.
hboot_liberty_7227_1.03.0000_111215.zip
MD5: b1d549c2b602a26740305014bc2de6fd

Hi there,
I have a HTC Aria with Hboot 0.57 and S-ON. I rooted this a while ago and I've been running the Liberated Aria ROMS 2.1 and 2.2.
I want to take S-OFF, but it seems like the only way available is for me to install the official ROM update from AT&T and then use Revolutionary to re-root it and take S-OFF.
Can I use this method for going to Hboot 1.02 and the AT&T official update? and then use revolutionary?
If not, what should I do? (also I have difficulties accessing a windows computer, I primarily use GNU/Linux. If there are instructions for it, that would be swell... I know revolutionary has a linux version, so all is good there).
Thanks
Andres

acimmarusti said:
Hi there,
I have a HTC Aria with Hboot 0.57 and S-ON. I rooted this a while ago and I've been running the Liberated Aria ROMS 2.1 and 2.2.
I want to take S-OFF, but it seems like the only way available is for me to install the official ROM update from AT&T and then use Revolutionary to re-root it and take S-OFF.
Can I use this method for going to Hboot 1.02 and the AT&T official update? and then use revolutionary?
If not, what should I do? (also I have difficulties accessing a windows computer, I primarily use GNU/Linux. If there are instructions for it, that would be swell... I know revolutionary has a linux version, so all is good there).
Thanks
Andres
Click to expand...
Click to collapse
No, you should not use the method described in this thread. Unrevoked does not modify the HBOOT or give you S-OFF, so the instructions in this thread do not apply to you.
To update to HBOOT 1.02, the only thing you need to do is run the RUU to update your phone. Since the RUU is only available as a Windows executable, you can use this alternative method to install it: http://forum.xda-developers.com/showpost.php?p=18541475&postcount=145 . This will erase all your settings from the device, so make a Nandroid backup first if you want to save them.
Once you have completed those steps, you can then use Revolutionary on your device. If you made a backup, you can restore it after Clockworkmod is reinstalled.

No, if fails with hboot 1.03. Is possible to revert to hboot 1.02? Any idea?
Code:
C:\fastboot>fastboot flash hboot liberty_downgrade.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\fastboot>
s19r83g said:
Does anyone know if this works on htc gratia,hboot 1.03,bootloader unlocked (htcdev.com)
Click to expand...
Click to collapse

It fails when you try to flash patched misc partition.
Code:
#fastboot flash misc misc.img
sending 'misc' (640 KB)...
OKAY [ 0.243s]
writing 'misc'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
Edit:
It WORKS!!!, using flash_image misc misc.img
attn1 said:
No, but I know how to remove those.
High level, not for noobs, and certainly not step by step noobs will look for:
install cwm
update the mainver in the misc partition to 1.11.111.1 from cwm (dump/hex edit, reflash required)
back up the current ROM with cwm
relock the bootloader
make a goldcard
flash an aria RUU with a 1.02.1002 hboot.
run revolutionary
restore your gratia rom from cwm backups.
Click to expand...
Click to collapse

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

[RESOLVED] Did I kill my phone ? catch-22

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.

[MISC] Flashing ENG HBOOT | Rolling back to S-ON - The Noob Way

Hi all
I noticed that many of us while trying to flash HBOOT's brick our devices as there is no single thread and no single unified noob proof solution for flashing Revolutionary's S-Off 'ed+ Rooted Desire S all the way from HBOOT version 6.98.1xxx to 0.98.2000 (PG8810000).
Hope this helps..
Ok, less talking; more work
This Thread will help you if:
- if you want to change your HBOOT version to 0.98.2000 (PG8810000)
- if you want to S-On your previously S-Off 'ed Desire S as to make use of warranty (as there is no way of making a S-Off device having Revolutionary's HBOOT v.6.98.1002 -to- S-on again without flashing the HBOOT again).
- AFAIK, if you want to flash an RUU (read ROM Update Utility AKA the stock ROM installer) you won't be able to do it you are S-off 'ed using revolutionary method. So for doing that again you need to have the HBOOT version as something like 0.98.xxxx or 6.98.2000 (experts need your comments on this one)
This guide won't be telling you of how to make it S-on again (though theres a link to youtube step-by-step video tutorial of how to do it in the update section below; Do NOT ignore the video's ending ) but just of how you can go ahead with changing your Revolutionary's default flashed HBOOT version 6.98.10xx -to- v.6.98.2000 and then -to- v.0.98.2000 (PG8810000).
For more updated info please refer to "UPDATE" section below:
UPDATE:
Regarding the "Returning to Stock/making your phone S-ON" issue:
ok..I have not tried this but this right here guides you of how to S-ON and return your phone to total* factory like condition by installing an RUU thereby removing just everything..revolutionary, CWM..u name it; just like a real stock phone
But pls note that using an RUU (read ROM Update Utility AKA the stock ROM installer) will erase all your data! as you are flashing a stock RUU
And for this you need to change your HBOOT to 6.98.2000 (PG8810000) (as in the video linked above) OR to 0.98.2000 (PG8810000); so thats one of the other advantages of my guide..
Hope this helps..
Also, a lot of good folks here have been asking/suggesting me over why this method..? and why not the "dd commands method" / adb command(s) method? (all manually )
ok here's my take on this
Click to expand...
Click to collapse
Prerequisites:
- you need an HTC Desire S phone
- HBOOT version 6.98.1xxx (how to check HBOOT version? just read step#4 & step#5 to find out your HBOOT version)
- S-OFF and Root 'ed using Revolutionary (also known as AlphaRevX; its the old name 'duh)
- your data cable and a working PC with HTC Fastboot Drivers installed (get them here)
- make sure you don't have HTC Sync software installed (check it in Add/Remove Programs found in Control panel of your PC); if it is then please remove it before starting with the following process!!!
WARNING:
DO NOT..I REPEAT AGAIN..DO NOT DISCONNECT IN-BETWEEN THE FLASHING PROCESS(Step#6 onwards) OR YOU MAY DAMAGE (READ "BRICK") YOUR PHONE IN A VERY BAD WAY!
Instructions:
1- download and extract the attached zip file in a empty folder (make sure NOT to touch/merge any of its contents)
2- make sure USB debugging is switched "ON" in your phone's: application settings menu >> development settings
3- also make sure that fastboot mode is switched "OFF" in your phone's: Power settings menu and by default your phone is configured to switch to charging mode when the cable is connected (JUST DO NOT CONNECT IT YET)
4- Now, reboot your phone into bootloader mode by first switching off your phone and then press the Power button and the volume down key simultaneously.
5- you should be able to see white screen with things like Revolutionary on top, S-OFF, HBOOT ... 6.98.10xx etc.
6- now go into the fastboot mode and then just connect you phone until the "fastboot" turns into "usb fastboot" OR "fastboot usb" either of these
7- now go inside the extracted folder named "FlashENGHBOOT698"
8- click on bat file named "Click This" and sit back
9- a black screen should popup as soon as you click on the bat [email protected] step#8 and you should see "OKAY" at the end of successful flash but it would be too quick so keep on lookout
10- select reboot on the bootloader's menu
11- reboot back to bootloader's menu to check if HBOOT's version has been changed to 6.98.2000
12- repeat the process from step 8 BUT make sure this time you go inside the other folder named "FlashENGHBOOT098" (notice the ZERO before 98)
13- follow the steps upto step#11 to check if the HBOOT's version has been changed to 0.98.2000 (PG8810000)
Voila!
Note:
This is just a compilation and a slightly edit of the batch file code to flash the second flash Image for the 0.98.2000 HBOOT All credits goes to the following people:
Credits: (Yay!! time for beer)
Would like to thank Maarten for his post and tool here
lgl0 for all his valuable info here
DesireFanatics for his step-by-step tutorial video here
Last but not the least anchemis for sticking and guiding me all the way
And to all those who have helped me here and here.
Disclaimer:
I won't be responsible for any damages done to your phone. Please attempt/flash with caution. though this method has been tested personally by me and is working fine; have also tested rebooting my phone so as to make sure bootloader does not give up on me.
MODS pls sticky this thread as newbie/newcomers really won't get it the first time they look at the [index] @ XDA
And this right here is the solution for Flashing their HBOOTs almost painlessly
Regards,
sky770
- Reserved for future use -
great guide, just have one question, currently I am using reengineered 2.00.002 hboot - 7.00.1002, my phone was s offed by revolutionary, will it work as well?
esideboi said:
great guide, just have one question, currently I am using reengineered 2.00.002 hboot - 7.00.1002, my phone was s offed by revolutionary, will it work as well?
Click to expand...
Click to collapse
:|..*gulp*
ok..as am a newbie so I would be needing experts in here
btw..have you gone through the Index/threads? coz thats what i did
esideboi said:
great guide, just have one question, currently I am using reengineered 2.00.002 hboot - 7.00.1002, my phone was s offed by revolutionary, will it work as well?
Click to expand...
Click to collapse
You have the latest hboot. If you don't want to s-on and unroot your phone again there is no need for you to downgrade the hboot (afaik )
Edit: accidentally pressed thanks.. never mind
sky770 said:
Hi all
I noticed that many of us while trying to flash HBOOT's brick our devices as there is no single thread for flashing Revolutionary's S-Off 'ed+ Rooted Desire S to 0.98.2000 (PG8810000).
Hope this helps..
Ok, less talking; more work
This Thread will help you if:
- if you want to change your HBOOT version to 0.98.2000 (PG8810000)
- if you want to S-On your previously S-Off 'ed Desire S as to make use of warranty (as there is no way of making a S-Off device having Revolutionary's HBOOT v.6.98.1002 -to- S-on again without flashing the HBOOT again).
- AFAIK, if you want to flash an RUU (umm noob translation for this would be original stock ROM?) you won't be able to do it you are S-off 'ed using revolutionary method. So for doing that again you need to have the HBOOT version as something like 0.98.xxxx or 6.98.2000 (experts need your comments on this one)
This guide won't be telling you of how to make it S-on again but just of how you can go ahead with changing your Revolutionary's default flashed HBOOT version 6.98.10xx -to- v.6.98.2000 and then -to- v.0.98.2000 (PG8810000)
Prerequisites:
- you need an HTC Desire S phone
- HBOOT version 6.98.1xxx (how to check HBOOT version? just read step#4 & step#5 to find out your HBOOT version)
- S-OFF and Root 'ed using Revolutionary (also known as AlphaRevX; its the old name 'duh)
- your data cable and a working PC with HTC Fastboot Drivers installed (get them here)
- make sure you don't have HTC Sync software installed (check it in Add/Remove Programs found in Control panel of your PC); if it is then please remove it before starting with the following process!!!
WARNING:
DO NOT..I REPEAT AGAIN..DO NOT DISCONNECT IN-BETWEEN THE FLASHING PROCESS(Step#6 onwards) OR YOU MAY DAMAGE (READ "BRICK") YOUR PHONE IN A VERY BAD WAY!
Instructions:
1- download and extract the attached zip file in a empty folder (make sure NOT to touch/merge any of its contents)
2- make sure USB debugging is switched "ON" in your phone's: application settings menu >> development settings
3- also make sure that fastboot mode is switched "OFF" in your phone's: Power settings menu and by default your phone is configured to switch to charging mode when the cable is connected (JUST DO NOT CONNECT IT YET)
4- Now, reboot your phone into bootloader mode by first switching off your phone and then press the Power button and the volume down key simultaneously.
5- you should be able to see white screen with things like Revolutionary on top, S-OFF, HBOOT ... 6.98.10xx etc.
6- now go into the fastboot mode and then just connect you phone until the "fastboot" turns into "usb fastboot" OR "fastboot usb" either of these
7- now go inside the extracted folder named "FlashENGHBOOT698"
8- click on bat file named "Click This" and sit back
9- a black screen should popup as soon as you click on the bat [email protected] step#8 and you should see "OKAY" at the end of successful flash but it would be too quick so keep on lookout
10- select reboot on the bootloader's menu
11- reboot back to bootloader's menu to check if HBOOT's version has been changed to 6.98.2000
12- repeat the process from step 8 BUT make sure this time you go inside the other folder named "FlashENGHBOOT098" (notice the ZERO before 98)
13- follow the steps upto step#11 to check if the HBOOT's version has been changed to 0.98.2000 (PG8810000)
Voila!
Note:
This is just a compilation and a slightly edit of the batch file code to flash the second flash Image for the 0.98.2000 HBOOT All credits goes to the following people:
Credits: (Yay!! time for beer)
Would like to thank Maarten for his post and tool here
lgl0 for all his valuable info here
Last but not the least anchemis for sticking and guiding me all the way
And to all those who have helped me here and here.
Disclaimer:
I won't be responsible for any damages done to your phone. Please attempt/flash with caution. though this method has been tested personally by me and is working fine; have also tested rebooting my phone so as to make sure bootloader does not give up on me.
Click to expand...
Click to collapse
you have not mentiond the dd commands tut. this is used because of the re engineerd hboot 7.00.1002 upgrade people are doing, u cannot use any other method to get another hboot to your device after using 7.00.1002 hboot. as no fastboot and using the PG88IMG method just gets bypassed. so the only way is the dd commands. please add this to your guide thanks
If i pass your guide, will my phone be s-on or s-off?
Is it possible to apply this hboot version after? Or can i apply this hboot version right now?
Currently im on hboot-6.98.1002.
Hope someone will guide me real quick. Thanks!
@muselmann88 : 1. The bootloader is Eng S-off!
2. You're now with the Revolutionary Hboot and there is no reason to change. As long as you're using the dd commands to directly write the bootloader partition every bootloader can be uploaded. I haven't had any problems with this method.
marioemp2k7 said:
@muselmann88 : 1. The bootloader is Eng S-off!
2. You're now with the Revolutionary Hboot and there is no reason to change. As long as you're using the dd commands to directly write the bootloader partition every bootloader can be uploaded. I haven't had any problems with this method.
Click to expand...
Click to collapse
I read that i'll have boot problems with sense 4 roms, isn't that correct?
Could you please list the dd commands that i'll succeed in writing the bootloader to the partition.
How about other eng hboot?
Sent from my HTC Desire S using XDA
muselmann88 said:
I read that i'll have boot problems with sense 4 roms, isn't that correct?
Could you please list the dd commands that i'll succeed in writing the bootloader to the partition.
Click to expand...
Click to collapse
I have PM you mate i have sent u everything u need to get yourself on the new eng hboot with that new eng hboot u can use ANY Rom without any problems
The hboot version that should be overwritten by "dd" command is 6.98.1002.
All the others are perfectly rewritten by a RUU or PG88IMG with a higher version.
Only Revolutionary (not AlpharevX) hboot has write protection. There is not only version check in that process
Thanks to the OP!
Just got a Desire S and so far done this little lot:
I've downgraded the ROM to 1.28 to get HBOOT 0.98
S-OFF'ed using Revolutionary.
Installed 4EXT Recovery 1.0.0.5 Touch RC3
Flashed VanillaICE ROM
and just followed this guide to get off the Revolutionary HBOOT and to the ENG HBOOT 0.98.2000.
And it worked flawlessly!
Thanks again!
EDIT: and somewhere in that lot I have also updated the radio to the latest one from the Radio thread!
htc-phones said:
you have not mentiond the dd commands tut. this is used because of the re engineerd hboot 7.00.1002 upgrade people are doing, u cannot use any other method to get another hboot to your device after using 7.00.1002 hboot. as no fastboot and using the PG88IMG method just gets bypassed. so the only way is the dd commands. please add this to your guide thanks
Click to expand...
Click to collapse
Hi,
The fastboot method gets bypassed if we try to flash it by directly picking up the *.zip file from SD Card's root (that good 'ol PG88IMG.zip method).
Using the above method (my method at post#1) we are just literally pushing it through fastboot>>adb>>phone to get it flashed.. no questions asked from phone's side
srry abt the newbie/layman terms answer but this is how it actually works
Also regarding, the "dd commands" are never meant to be used for "noobs" as they are quite dangerous...more..more dangerous than to use fastboot instead of directly using adb commands.
Just because dd commands method exist doesn't mean we should go to that extent to brick our phone (a noob can easily do that while sipping beer and typing some command as bik instead of blk)
And hence I would not like newbie(s) coming in here, bricking their phones and stalking me
UPDATE:
Excerpt taken from here
There are actually two levels of S-OFF. The Bootloader (HBoot) and the Radio. Getting S-Off on the HBoot gives us everything we need, but doesn't actually turn off the @secuflag which is set in the radio. What it is possible to do is to flash a HBoot that believes the Radio is set to S-OFF, as the HBoot is responsible for setting that flag. Once the HBoot on the phone is S-OFF, we can write to all the partitions and basically do whatever we want, but it is possible to go one step further. Flashing a radio that is S-OFF and actually setting the @secuflag off gives 100% total access to every part of the phone and it's software, as it becomes network unlocked allowing to you to use any SIM and also allows you to flash a ROM from any carrier (known as Super CID). It also makes it nigh on impossible to permanently loose root no matter what you flash. Once you have radio S-OFF, it makes it much easier to flash new HBoots and ROMs even if you flash something that is locked down tight.
Setting the Radio to S-Off is not necessary, and gaining S-OFF on the HBoot is more than most people will ever need. Radio S-Off is just the last step of the puzzle, but it is worth noting the only points you can permanently brick your phone is flashing a radio or a HBoot, if either of these go wrong you will end up with a shiny expensive paper weight so there is risk involved.
Click to expand...
Click to collapse
So pls pls suggest newbie(s) to flash with caution :|
muselmann88 said:
If i pass your guide, will my phone be s-on or s-off?
Is it possible to apply this hboot version after? Or can i apply this hboot version right now?
Currently im on hboot-6.98.1002.
Hope someone will guide me real quick. Thanks!
Click to expand...
Click to collapse
As it looks to me, if you're running hboot-6.98.1002 already then you must have used revolutionary's tool to S-off your phone.
Therefore you are eligible to use the above guide to re-flash your hboot.
Infact you're having the same hboot version as I had after using revolutionary.
changing your hboot version to 0.98.2000 (PGI880000) will make sure that you can flash any RUU (official stock ROM) so that you could be s-off again
Though I am still getting working on it to have a simple 1-click solution for this too for ya noobs
Also, make sure you're rooted (though I would like some expert to comment on this; but AFAIK root is needed to flash the *.img file over fastboot; just search around forum as to be sure.)
Do it now! and you won't regret..
Regards,
sky770
marioemp2k7 said:
@muselmann88 : 1. The bootloader is Eng S-off!
2. You're now with the Revolutionary Hboot and there is no reason to change. As long as you're using the dd commands to directly write the bootloader partition every bootloader can be uploaded. I haven't had any problems with this method.
Click to expand...
Click to collapse
I would not really recommend using "dd commands" please see my reply over here
Regards,
sky770
muselmann88 said:
I read that i'll have boot problems with sense 4 roms, isn't that correct?
Could you please list the dd commands that i'll succeed in writing the bootloader to the partition.
Click to expand...
Click to collapse
Sense 4 requires you to have umm... HBOOT version 2.xxx and above? (experts?) anyways.. that cannot be categorized as "problem" its just another "prerequisite" for sense 4 based ROMs though am not sure if its an "official prerequisite" or a non official non
Also, please read my post abt dd commands here.
Regards,
sky770
Dreamtheater2003 said:
How about other eng hboot?
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
Can take some time here to try some custom(s) ROMs first
Anyways, now that am here on XDA lets get started..
Regards,
sky770
htc-phones said:
I have PM you mate i have sent u everything u need to get yourself on the new eng hboot with that new eng hboot u can use ANY Rom without any problems
Click to expand...
Click to collapse
any ROM?
you sure about RUU (stocks) ??
if yes then plz forward tht PM to me too pls
Regards,
sky770
amidabuddha said:
The hboot version that should be overwritten by "dd" command is 6.98.1002.
All the others are perfectly rewritten by a RUU or PG88IMG with a higher version.
Only Revolutionary (not AlpharevX) hboot has write protection. There is not only version check in that process
Click to expand...
Click to collapse
aha! Right on point
And thats one more reason I won't really..really recommend using dd commands to a noob/newcomers just for flashing from 6.98.10xx -over to-0.98.2000 (PGI880000).
Regards,
sky770

Can't revert to stock --> T-mob101 (DE), hboot 2.16, S-ON

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

[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