[SOLVED] Unroot & roll back S-ON with HBoot 7.00.1002 - HTC Desire S

I've been experiencing poor battery life on my DS since I bought it and have tried customizing settings as much as possible (lower brightness, undervolting, etc) and flashing different roms but the battery life never seems to improve. I know the battery life on the Desire S isn't the best but I've never been able to get near the amount of hours of usage that people have reported. So I need to take my phone in to get the battery replaced and hence need to unroot and roll back to S-ON because of warranty issues.
I have found the following threads http://forum.xda-developers.com/showthread.php?t=1460713 and http://forum.xda-developers.com/showthread.php?t=1701137 but it seems both use HBoot 6.98.xxxx whereas I'm on HBoot ENG 7.00.1002
If necessary, I have a nanroid backup of the stock rom. Can anyone help me unroot and S-ON or link me to a thread that can assist me?
Apologies if this has been asked before.

Follow the threads you've found. Absolutely the same sequence, and since the first step in this sequence is reflashing HBOOT with another one - it wasn't hard to assume that the HBOOT doesn't matter as long as it's an engineering one.

So I can use the attachment from this thread http://forum.xda-developers.com/showthread.php?t=1387484 to downgrade my hboot?
Do I have to use an RUU or can I simply restore to stock rom and then downgrade my hboot?

Bump

You can flash stock ROM in recovery and then fastboot flash the bootloader.
You can also first flash the bootloader and then use RUU.
Your phone, your choices.

Thanks - had to be sure.

I restored the phone to my stock rom, did a factory reset and used Unroot from SuperOneClick tom remove Superuser. I then used Android Flasher to flash the 0.98.0002 hboot from this thread http://forum.xda-developers.com/showthread.php?t=1387484 and it restored the phone back to S-ON.
Everything seems to be factory fresh, but when I select recovery or factory reset it enters a menu with fastboot above the options and the message "security warning" appears in pink (in place of -revolutionary-). The message is removed after rebooting the bootloader.
Is this normal? Why does this warning appear and how can I fix it?

The reason I didn't use a RUU is because I couldn't find one compatible. In any case, I flashed the ENG hboot 0.98.2000 from here http://forum.xda-developers.com/showthread.php?t=1113820, created a gold card, and used an RUU.
Phone is factory fresh with S-ON. Perhaps this may help someone else with a similar issue in the future.

Related

[Q] Very strange issue with hboot

Hi all,
I'm having a strange issue with the hboot downgrade process. I S-OFFed my DS using revolutionary, but wanted to go back to a stock ROM using one of the shipped RUUs. I realised I cannot flash the RUU over the revolutionary hboot, so I looked around the forum for a recipe how to downgrade to a stock 0.98.0000 or anything that would not render my DS unusable after using RUU.
I tried most hboot.img files on this forum and none of them managed to overwrite the current file. I don't know what to do, when I use the zip file method I get "Bootloader bypassed" message and nothing changes. I tried android flasher as well, and even though it reports that phone has been flashed successfully it sill comes up with the revolutionary hboot version and running a RUU makes my phone stuck on the HTC logo.
There was one tutorial topic on how to go back to the original hboot, but it was pulled by the author due to people bricking their phones caused by not following the instructions properly etc.
I would appreciate any help, as I really want to go back to S-ON and stock ROM. At the moment I'm rocking CM7 as thankfully I made a nandroid backup before playing with the hboot stuff.
Kris
You first need to flash a hboot that can be over written by a RUU. The one you need is Eng 0.98.2000, once you've flashed that you can install the RUU.
I think u need to flash it using adb or fastboot whilst the phone is in bootloader or maybe recovery
Sent from my HTC Desire S using xda premium

[Q] Stuck in bootloop after 6 months of smooth sailing, can't access recovery

Hi everyone!
I've been searching and reading around trying to solve a bootloop problem on my HTC Desire S/Saga (or at least I think it is a bootloop problem) but, so far, I've had no luck.
Here's what has happened and what's going on:
1) S-off and got hboot 6.98.1002 through revolutionary
2) phone worked normally for six months and suddenly, without any changes or flashes, it rebooted and started a boot loop, ie, I can't get into any in-OS menus.
3) Choosing recovery of factory settings from hboot menu just reboots the phone and restarts the loop.
4) I've tried flashing (both through fastboot and android flasher) the eng hboot 0.98.0000 and clockworkmod recovery images but neither had any effect.
Phone was vodafone-locked, running a vanilla Android 2.3.4.
hboot menu data:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
I don't have any backup data from pre-revolutionary, either :|
I'm knocking my head against the walls, hoping that the phone's only temporarily bricked... any ideas?
Thanks in advance for helping a n00b...
Doesn't sound like a hboot problem you me, but that could just be me. And I don't think flashing the stock hboot will help.
Are you sure you are flashing the ENG hboot? It's 0.98.2000. 0.98.0000 is most likely your stock hboot and can't be flashed over revolutionary hboot in most cases.
So to get back to stock stock..... You will need to run your RUU after the new hboot has been flashed.
Another option is for you to install a custom ROM and avoiding the RUU. I still suggest you flash the ENG hboot though.
Head for this thread for help
http://forum.xda-developers.com/showthread.php?t=1488672
Thanks everybody!
I've been away for the last few days so I haven't been able to test anything, but tomorrow evening I'll test both suggestions and post feedback.
Thanks again!
So, I've trying out your suggestions and...
foX2delta said:
Doesn't sound like a hboot problem you me, but that could just be me. And I don't think flashing the stock hboot will help.
Are you sure you are flashing the ENG hboot? It's 0.98.2000. 0.98.0000 is most likely your stock hboot and can't be flashed over revolutionary hboot in most cases.
So to get back to stock stock..... You will need to run your RUU after the new hboot has been flashed.
Another option is for you to install a custom ROM and avoiding the RUU. I still suggest you flash the ENG hboot though.
Click to expand...
Click to collapse
So I tried to flash the ENG hboot from this thread, using android flasher and later using this method, but adb never lists my Saga.
Fastboot lists it correctly, though. I *think* I had USB debugging on, if I recall correctly.
Using androidflasher I get a flash ok notice and then the bootloop just restarts...
Any ideas?
mOh19973 said:
Head for this thread for help
http://forum.xda-developers.com/showthread.php?t=1488672
Click to expand...
Click to collapse
Thanks moh19973, I'll leave feedback at your thread (no luck, though..)
thanks again to everybody
Opalid said:
Hi everyone!
I've been searching and reading around trying to solve a bootloop problem on my HTC Desire S/Saga (or at least I think it is a bootloop problem) but, so far, I've had no luck.
Here's what has happened and what's going on:
1) S-off and got hboot 6.98.1002 through revolutionary
2) phone worked normally for six months and suddenly, without any changes or flashes, it rebooted and started a boot loop, ie, I can't get into any in-OS menus.
3) Choosing recovery of factory settings from hboot menu just reboots the phone and restarts the loop.
4) I've tried flashing (both through fastboot and android flasher) the eng hboot 0.98.0000 and clockworkmod recovery images but neither had any effect.
Phone was vodafone-locked, running a vanilla Android 2.3.4.
hboot menu data:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
I don't have any backup data from pre-revolutionary, either :|
I'm knocking my head against the walls, hoping that the phone's only temporarily bricked... any ideas?
Thanks in advance for helping a n00b...
Click to expand...
Click to collapse
Your problem sounds exactly like the one on the thread linked below.... in which case, if you just try the steps from the concerned thread, and are still unable to fix your device, it can be written off as another dead eMMC...
Just follow the instructions on this thread...maybe you will have better luck than the OP?
http://forum.xda-developers.com/showthread.php?t=1507106
So did your hboot change or not? If hboot and recovery won't flash then I have to agree with above, fried emmc :-(
yeah it could be an emmc problem, you may want to check the sticky in the development forum, if this is the real problem there is a possibility for a fix, not necessarily emmc replacement
enigmaamit said:
Your problem sounds exactly like the one on the thread linked below.... in which case, if you just try the steps from the concerned thread, and are still unable to fix your device, it can be written off as another dead eMMC...
Just follow the instructions on this thread...maybe you will have better luck than the OP?
http://forum.xda-developers.com/showthread.php?t=1507106
Click to expand...
Click to collapse
Thanks, tried everything and had the exact same results. Fried eMMC, I guess..
This is really wierd, I got a phonecall, turned the call off, the phone rebooted and entered the bootloop.
Nothing fishy or wierd, no flashing erros, just a regular phonecall from my boss. Damn :|
If only I could get the normal hboot on I could repair it under warranty
Well, thanks everybody
Try going for warranty repair, for a few guys over here at xda no one checked (or din not care) whether the phone was rooted or s-off when they went to service their phone. Maybe you'll get lucky too. Good luck!

[Q] locked HBOOT v2.00.0002 with S-OFF! Is it possible to turn S-ON??

Hi,
I'm very familiar with flashing ROMs on phones and have flashed a fair few in my time. I flashed my sisters Desire S a while ago but recently the phone has stopped detecting the SIM card and subsequently has to go back for warranty.
I've flashed a Stock rom over it - trouble is, I now have the locked HBOOT v 2.00.0002 with S-OFF!
Could someone verify if these steps are correct? I'm not too familiar with the Desire S.
1. Downgrade HBOOT to earlier version - 0.98 i think it is.... or 0.68
2. Turn S-ON
3. Flash RUU Stock ROM
I cannot for the life of me downgrade the HBOOT version - I've tried every method out there!
I am very familiar with working in command line on Windows and Linux so don't be afraid to get technical!
Any help is very much appreciated!
Daft question, but have you tried a different Sim?
Does she still have the box?
Swyped from my Desire S using XDA Premium
Haha I spent hours debugging the sim card issue and finally came to the conclusion it's a hardware fault!
Yes - tried several different sim cards from two different carriers (this household only uses 2 carriers!)
Also tried several different ROMs/Radios - she was happily using MIUI for months then she just told me it stopped detecting her SIM card - she certainly hasn't been playing with ROMs so I know it's nothing she has done.
Update: Box is long gone
I've flashed a Stock rom over it - trouble is, I now have the locked bootloader v 2.00.0002 with S-OFF!
Could someone verify if these steps are correct? I'm not too familiar with the Desire S.
1. Downgrade bootloader to earlier version - 0.98 i think it is.... or 0.68
2. Turn S-ON
3. Flash RUU Stock ROM
Can I skip the first step? I guess not.
What has me confused is that you flashed the 0.98 hboot and you said it was s on, now you ran the RUU, and its s off....
Did you use revolutionary to get s off or was it s off to start with?
The correct steps would be.. (if you use revolutionary)
1. Use fastboot to flash 0.98.2000 over the revolutionary one.
2. Run correct RUU.
Problem you could run into are cid's of the RUU (make a goldcard to avoid error) and two misc version being higher than RUU.
Thanks for the reply. I never said it was S-on, the phone was running a custom MIUI ROM with S-Off, I flashed a stock rom straight over the top of it by running the RUU (pretty sure I shouldn't have done!) now I have stock ROM with S-Off and locked HBOOT v2.00.0002
I cannot remember if I used revolutionary to get s off originally - it was many months ago, more than likely though. I remember the phone came with S-On and I had to make it S-Off.
I just want to get S-On again with stock rom but it's proving impossible!
So just to clarify, it is currently running stock rom with LOCKED HBOOT v2.00.0002 and S-Off.
I've tried manually overwriting the version with miscinfo, I've also tried the zerg method - all to no avail.
I have NEVER heard of a stock hboot that is s-off, only when the phone was s-off to start with (early models), or if you used a clip.
Flashing the RUU would bring the phone back to completely stock. (if it flashed correctly)
foX2delta said:
I have NEVER heard of a stock hboot that is s-off, only when the phone was s-off to start with (early models), or if you used a clip.
Flashing the RUU would bring the phone back to completely stock. (if it flashed correctly)
Click to expand...
Click to collapse
Haha want screenshots? I assure you that's what I've got.
Ran an older RUU which has downgraded my HBOOT to 0.98 or 0.68 (can't remember off top of my head) and am running stock rom, HBOOT says ***locked*** at top and also says S-OFF.
I think I'm getting there now.

[Q] No internet after flashing ARHD / on bootloader recovery went to ~locked~

Hello to everyone..
I will give you the longer story just so you get as much detail as possible, and i hope we can come up with easy solution.
Yes, I am new to all rooting, ROMS, recovery etc, and I consider my self noob, because I can follow guides, but dont understand actually what am I doing...
Ive had ARHD for a while when decided to put everything back to stock for warranty purposes. I cant remember the order of things, but i removed recovery, put back SON, and flashed stock RUU...In bootloader it said: LOCKED; PYRAMID SHIPPED and SON.
Since I didnt take phone to get repairs (I found out that my HTC sensation was turning off cause of extra space between casing and battery, and repaired it myself) I wanted to go back to ARHD.
The problems started when I realised i have 1.27 HBOOT and methods will be different. However i made it. First I unlocked bootloader with HTCdev, than installed 4ext recovery, put superSU on, rooted, put new firmware, superscripted and flashed ARDH. Everything worked fine except I didint have internet connection, and I mean no H, 3G, 4G ...nothing. Ive checked setting but nothing was wrong.
I have realised that my firmware was 3,2 and not 3,33, so i flashed it again (made sure i downloaded newest one), and It still says 3.2 so that is problem 1.
I did SUPER CID thinking that might be the problem and flashed again, but no luck. Than I flashed new firmware again (from different source) but still 3.2. After that in my bootloader the top ~revolutionary~ changed into ~locked~, while i still had SOFF and everthing else.
So to sum up: 1. Why dont I have any internet(what step did i mess up)
2. Why did my recovery went to locked (even though I can enter in 4ext from bootloader)
3. What are my steps to make this all work again.
Hope you can help me, and thank you all for being a great community so far !
Sisak said:
Hello to everyone..
I will give you the longer story just so you get as much detail as possible, and i hope we can come up with easy solution.
Yes, I am new to all rooting, ROMS, recovery etc, and I consider my self noob, because I can follow guides, but dont understand actually what am I doing...
Ive had ARHD for a while when decided to put everything back to stock for warranty purposes. I cant remember the order of things, but i removed recovery, put back SON, and flashed stock RUU...In bootloader it said: LOCKED; PYRAMID SHIPPED and SON.
Since I didnt take phone to get repairs (I found out that my HTC sensation was turning off cause of extra space between casing and battery, and repaired it myself) I wanted to go back to ARHD.
The problems started when I realised i have 1.27 HBOOT and methods will be different. However i made it. First I unlocked bootloader with HTCdev, than installed 4ext recovery, put superSU on, rooted, put new firmware, superscripted and flashed ARDH. Everything worked fine except I didint have internet connection, and I mean no H, 3G, 4G ...nothing. Ive checked setting but nothing was wrong.
I have realised that my firmware was 3,2 and not 3,33, so i flashed it again (made sure i downloaded newest one), and It still says 3.2 so that is problem 1.
I did SUPER CID thinking that might be the problem and flashed again, but no luck. Than I flashed new firmware again (from different source) but still 3.2. After that in my bootloader the top ~revolutionary~ changed into ~locked~, while i still had SOFF and everthing else.
So to sum up: 1. Why dont I have any internet(what step did i mess up)
2. Why did my recovery went to locked (even though I can enter in 4ext from bootloader)
3. What are my steps to make this all work again.
Hope you can help me, and thank you all for being a great community so far !
Click to expand...
Click to collapse
now are you S-ON or S-OFF?
if you are S-ON flash the boot.img of the rom manually
or enable smartflash from recovery(only if you are S-ON) and flash the rom again
other way is to use the wifix manager app
also update fw it can only be done if you are S-OFF
if you are S-OFF it can be done only from bootloader and renamed as pg58img.zip
did you do that in this way?
edit:first do something else
connect your device into pc.navigate to the folder where adb and fastboot files are located
open a command window there and do these commands:
1)adb reboot bootloader
2)fastboot getvar version-main
it will show you your exact fw version
Sisak said:
Hello to everyone..
I will give you the longer story just so you get as much detail as possible, and i hope we can come up with easy solution.
Yes, I am new to all rooting, ROMS, recovery etc, and I consider my self noob, because I can follow guides, but dont understand actually what am I doing...
Ive had ARHD for a while when decided to put everything back to stock for warranty purposes. I cant remember the order of things, but i removed recovery, put back SON, and flashed stock RUU...In bootloader it said: LOCKED; PYRAMID SHIPPED and SON.
Since I didnt take phone to get repairs (I found out that my HTC sensation was turning off cause of extra space between casing and battery, and repaired it myself) I wanted to go back to ARHD.
The problems started when I realised i have 1.27 HBOOT and methods will be different. However i made it. First I unlocked bootloader with HTCdev, than installed 4ext recovery, put superSU on, rooted, put new firmware, superscripted and flashed ARDH. Everything worked fine except I didint have internet connection, and I mean no H, 3G, 4G ...nothing. Ive checked setting but nothing was wrong.
I have realised that my firmware was 3,2 and not 3,33, so i flashed it again (made sure i downloaded newest one), and It still says 3.2 so that is problem 1.
I did SUPER CID thinking that might be the problem and flashed again, but no luck. Than I flashed new firmware again (from different source) but still 3.2. After that in my bootloader the top ~revolutionary~ changed into ~locked~, while i still had SOFF and everthing else.
So to sum up: 1. Why dont I have any internet(what step did i mess up)
2. Why did my recovery went to locked (even though I can enter in 4ext from bootloader)
3. What are my steps to make this all work again.
Hope you can help me, and thank you all for being a great community so far !
Click to expand...
Click to collapse
Hi,
What is your radio?(Settings>about phone>software information>more>baseband version)
Recovery is locked because you probably flashed 3.33 firmware from ARHD thread.
It will not show 3.33
This is because 3.33 is only a radio update.
Locked only means you are restricted in certain fastboot commands.
To unlock,flash THIS
There is nothing in what you said that would remove your internet connection.
Take off the back cover of the phone ,and GENTLY lift the 2 gold pins at the bottom of the phone,and see if that helps...
rzr86 said:
now are you S-ON or S-OFF?
if you are S-ON flash the boot.img of the rom manually
or enable smartflash from recovery(only if you are S-ON) and flash the rom again
other way is to use the wifix manager app
also update fw it can only be done if you are S-OFF
if you are S-OFF it can be done only from bootloader and renamed as pg58img.zip
did you do that in this way?
edit:first do something else
connect your device into pc.navigate to the folder where adb and fastboot files are located
open a command window there and do these commands:
1)adb reboot bootloader
2)fastboot getvar version-main
it will show you your exact fw version
Click to expand...
Click to collapse
I have checked and yes, fastboot shows my fw is 3.32.401.3
and i still have SOFF
when i flashed fw so far, i put zip to sd root and turned phone with power + down
malybru said:
Hi,
What is your radio?(Settings>about phone>software information>more>baseband version)
Recovery is locked because you probably flashed 3.33 firmware from ARHD thread.
It will not show 3.33
This is because 3.33 is only a radio update.
Locked only means you are restricted in certain fastboot commands.
To unlock,flash
There is nothing in what you said that would remove your internet connection.
Take off the back cover of the phone ,and GENTLY lift the 2 gold pins at the bottom of the phone,and see if that helps...
Click to expand...
Click to collapse
i have flashed your recovery, and it helped. Now it says revolutionary again.
and baseband is : 11.76A.3504.00P_11.24A.3504.31_M
Still no internet though.. (it seems to me that when i remove back case of the phone, my signal drops drastically, sometimes even connection breaks)

return to stock

My device is S-OFF and I'm running unlocked bootloader, custom recovery, and custom ROM.
I'm going to be returning it so I want to restore to completely stock (including S-ON). Any guides for this?
RedBullet said:
My device is S-OFF and I'm running unlocked bootloader, custom recovery, and custom ROM.
I'm going to be returning it so I want to restore to completely stock (including S-ON). Any guides for this?
Click to expand...
Click to collapse
Not exactly an all in one. Start here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
The method for turning S-On and relocking can be found here: http://forum.xda-developers.com/showthread.php?t=2745257 near the bottom of the first post
Dottat's pre-rooted RUUs can be found here: http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
My advice would be to flash a pre rooted RUU, Lock the bootloader, turn s-on then flash the stock RUU that matches the pre-rooted RUU. Don't forget to do a factory reset at the end as the RUUs are no-wipe.
I would say that turning s-on should be the last thing you do. Get the phone the way you want it. Flashed back to stock, locked bootloader and whatever else you want to do. Then make sure it's all the way you want it. Once you know for sure, then turn s-on. If you turn it on before you flash back to stock and you should somehow end up with it rooted or the have the tampered flag set, whatever the case may be (I've seen plenty of posts where something like this has happened), you'll be out of luck and not be able to fix it. Do it all and then turn s-on. That's my thinking anyway.
robocuff said:
I would say that turning s-on should be the last thing you do. Get the phone the way you want it. Flashed back to stock, locked bootloader and whatever else you want to do. Then make sure it's all the way you want it. Once you know for sure, then turn s-on. If you turn it on before you flash back to stock and you should somehow end up with it rooted or the have the tampered flag set, whatever the case may be (I've seen plenty of posts where something like this has happened), you'll be out of luck and not be able to fix it. Do it all and then turn s-on. That's my thinking anyway.
Click to expand...
Click to collapse
flashing the Stock RUU is the LAST thing you do, to remove root. You need root to turn s-on
edit: you need root to lock the bootloader, but not go S-on. In any event The steps Dottat outlines in his thread says to go S-on first then ruu the stock image

Categories

Resources