Database Info

How to unroot HTC Magic

Hi there
i'm really stuck at the moment and i've been reading threads after threads on this forum and i still couldn't find any solution and no luck with search as well.
my current problem is that i flashed a hero rom (i believe it's called myhero) about half a year ago when i first got it, but now i want to go back to the original Roger rom so that i can update to the new RUU. But i have no luck going back to the original rom at all. Anyone here would like to help?? i dun want to see my data plan go to waste just because of this
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT - 1.33.0009 (SAPP50000)
CPLD-12
RADIO - 3.22.20.17
PS: i tried many different ways, including unlockr's unrooting method, someone's nandroid wiped roger rom etc, but either htc sync said usb error or my fastboot screen said update failed. please help~

Should work using this method, just apply the update while the phone is in fastboot mode.

i tried that but i never knew i need to go into fastboot mode, i will give that a try, thank you very much

~dimdim~ said:
i tried that but i never knew i need to go into fastboot mode, i will give that a try, thank you very much
Click to expand...
Click to collapse
You don't usually need it. But if HTC Sync can't find the phone, you can apply the update trough fastboot. Let me hear your result.

yes same as before i get an error 170: usb error, is there any other way :S??

fastboot errors on mine also.

[Q] Requesting help with Desire S - Posting this after much research

Hi Everyone,
Apologies for this post, I've spent the last week and a half trawling through forum posts for my problem with limited success.
My Desire S had been experiencing random freezes, which would require a battery pull to reboot. I had tried a factory reset from HBOOT, but the phone would still freeze after that.
After the 5th or 6th battery pull, my phone would no longer boot successfully - It would get stuck on the white screen with green 'HTC' Text.
I can still successfully boot into HBOOT. If i select RECOVERY, it shows a black screen with a green triangle, then the screen goes black and the phone vibrates seven times.
If i select FACTORY RESET, the phone freezes and is not responsive.
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
I've tried connecting the phone to the PC and running some of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=1002506
specifically: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
If I connect in HBOOT and run the RUU, I get a less than 30% battery power error, but if i connect through FASTBOOT, the RUU will run but gets stuck on a 'rebooting to bootloader' message.
The phone cannot be seen in a devices search in ADB either. Also, In an effort to remove S-ON to load PG88IMG.zip from my SD CARD, i tried the revolutionary and HTC provided methods, both were unsuccessful.
with Revolutionary, it would show "Waiting on device" and then nothing, and with the HTC method, the fastboot command to get the device token wouldn't work due to a command error. I know that the HTC method doesnt officially support the Desire S, but another XDA poster said that worked for his (or hers).
So, I'm asking for help. There are a lot of posts that relate to my issue, but none match 100%. I wanted to figure this out myself, but I defer to your greater knowledge.
Thanks very much, any help would be great.

sorry, as an addendum, I've also successfully created a gold card, if that helps.

Blindshot888 said:
Hi Everyone,
Apologies for this post, I've spent the last week and a half trawling through forum posts for my problem with limited success.
My Desire S had been experiencing random freezes, which would require a battery pull to reboot. I had tried a factory reset from HBOOT, but the phone would still freeze after that.
After the 5th or 6th battery pull, my phone would no longer boot successfully - It would get stuck on the white screen with green 'HTC' Text.
I can still successfully boot into HBOOT. If i select RECOVERY, it shows a black screen with a green triangle, then the screen goes black and the phone vibrates seven times.
If i select FACTORY RESET, the phone freezes and is not responsive.
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
I've tried connecting the phone to the PC and running some of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=1002506
specifically: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
If I connect in HBOOT and run the RUU, I get a less than 30% battery power error, but if i connect through FASTBOOT, the RUU will run but gets stuck on a 'rebooting to bootloader' message.
The phone cannot be seen in a devices search in ADB either. Also, In an effort to remove S-ON to load PG88IMG.zip from my SD CARD, i tried the revolutionary and HTC provided methods, both were unsuccessful.
with Revolutionary, it would show "Waiting on device" and then nothing, and with the HTC method, the fastboot command to get the device token wouldn't work due to a command error. I know that the HTC method doesnt officially support the Desire S, but another XDA poster said that worked for his (or hers).
So, I'm asking for help. There are a lot of posts that relate to my issue, but none match 100%. I wanted to figure this out myself, but I defer to your greater knowledge.
Thanks very much, any help would be great.
Click to expand...
Click to collapse
A very rare problem, and since you've done a lot on your phone that were'nt successful, hope for the best that you haven't fried your eMMC. (Check forum for reference)
I would strongly suggest to remove the battery out for atleast 30secs to 1min. Then place it back in.
don't turn on the phone and charge it until full.
Once full, disconnect from power.
Go to bootloader, post your hboot version.
If hboot is still the same, go to fastboot and RUU with the one that your phone came with when you bought it.
It's great that you have a GoldCard, if the step above don't work, try RUU to the latest one.
Now regarding the freezes, I haven't received any freezes from my phone when it was still on stock. It might be a software problem and RUU might fix it. But if its a hardware, you might need to send for repair or maybe replacement.

Thanks very much for the reply Skanob,
Unfortunately, I didn't receive a RUU with my phone when it bought it. I checked through the SC card that was in the phone, but there's nothing that resembles an RUU. If you could please direct me to the latest version you mention, I would appreciate it.
when you say to post my HBOOT version, do you mean for me to post it here on the forums?
Apologies for the questions, I'm still getting used to the lingo.

Blindshot888 said:
Thanks very much for the reply Skanob,
Unfortunately, I didn't receive a RUU with my phone when it bought it. I checked through the SC card that was in the phone, but there's nothing that resembles an RUU. If you could please direct me to the latest version you mention, I would appreciate it.
when you say to post my HBOOT version, do you mean for me to post it here on the forums?
Apologies for the questions, I'm still getting used to the lingo.
Click to expand...
Click to collapse
The phone really didn't came with an RUU file. What I meant is that try to remember the Software Version of the phone when it came when you bought it. That means that software version is the RUU that was installed with it. Also the region.
My phone was installed with the one prior to RUU_Saga_hTC_Asia_WWE_1.48.707.1......
Try to get the RUU of your phone.
Post your HBOOT means post here or atleast tell me what is the version of your bootloader.
Example:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011, 14:58:38
the latest as of now is RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed.

Thanks again Skanob,
I'll try what you said to do and post the results.
from my initial post, I stated my HBOOT version as 0.98.0002. From what you've told me, should I expect my HBOOT version to change?
Also, I've checked the Europe RUU I attempted to use initially, i can confirm that it was the same version number as my phone. However, it got stuck on the status of "Rebooting to Bootloader" for hours.

Hi Skabob,
Just an update, after performing the steps you told me, my Desire S is still the same, with HBOOT version as 0.98.0002.
The rest of the details are the same as my original post.

Blindshot888 said:
Hi Skabob,
Just an update, after performing the steps you told me, my Desire S is still the same, with HBOOT version as 0.98.0002.
The rest of the details are the same as my original post.
Click to expand...
Click to collapse
I was expecting that your HBOOT would've been changed to the new one, it was an honest error on my end. I thought you've RUUed on the latest one. Sorry about that.
Seeing that you already have a GoldCard, I strongly suggest to RUU to the latest Europe version first.
If it still doesn't work, prepare for a long instruction, read on:
If you cannot use any RUU, the only thing you can do is update your HBOOT to the latest official S-ON.
Seeing that you are still currently S-ON. you wont be able to flash anything on your phone properly.
I myself don't have a proper guide on how you can update it as stock as possible, but maybe you can try what I've done before.
Skanob said:
amidabuddha said:
Ok taking my words back And how do you did this? You flashed the Stock 2.10.401.4 ROM over you bricked phone and it worked? (overwritted the revolutionary hboot or which version was it before?).
Click to expand...
Click to collapse
To make the long story short:
I stupidly get the firmware.zip file inside the ota file. That file had the latest hboot, recovery, and others. I renamed it to the correct pgxxximg.zip (cant remember the correct filename, currently drinking ) to flash it from bootloader.
Everything went well. Everything inside the file updated the corresponding file/partition/image to my phone. Hence letting me be stuck to the "locked" hboot 2.xx.xx s-on. ROM wouldn't boot as I said.
Being on the "locked" state wouldn't allow me to flash anything on the phone as far as i can remember. While writing, it will say has its unsuccessful.
But "unlocking" the hboot let me flash the recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
The OTA file that I've mentioned here is the recently released OTA file for Sense 3.0. Use search on where to get the download link.
Once you have the OTA file, just extract it and gather the firmware.zip file. copy it to your phones SD Card and rename it to PG88IMG.zip (.zip should be the extension of the file, not included in the name of the file).
Boot your phone into bootloader and agree to the phone if it asks you to update. AFAIK it should automatically do its thing.
Also, I remembered that it should be stuck in the middle of its update, just past the HBOOT and RADIO procedure. Once you are on that stuck state, maybe wait for about 10-15mins and see if it doesn't move. That is when I've removed the battery and waited for 30secs to 1min then re-plug it in. So you should pay close attention to what it is doing. Then check your HBOOT and see if it is updated.
If it is successful on updating your HBOOT, you would now need to UNLOCK your bootloader. The HTC unlock method supports the new HBOOT, seeing that you are still on the OLD one, thats one reason it wasn't successful.
What we're trying to do here is to get your phone to a state where you should be able to flash a custom recovery (check partitions if they are corrupted, most especially cache), full wipe partitions, flash a custom rom (pre-rooted stock recommended), then RUU back if you still want stock roms.
Goodluck!
P.S.
These instructions that I've given you are the methods that I would've used and thought of if I was in your situation. I am no expert in ADB nor on how to fix the phone properly. I assume that you already know the world-wide disclaimer: "not held responsible, know what you are doing" blah blah blah...
Also, full charge your phone first prior to doing it.
---------- Post added at 02:51 AM ---------- Previous post was at 02:32 AM ----------
And it's Skanob...

oh! my apologies Skanob! the B and N keys are right next to each other..but still I should have double checked.
Okay, I've tried running the RUU exe file for the RUU you referred me to. unfortunately it didnt move past "rebooting to bootloader".
I also grabbed the OTA file from this link. http://forum.xda-developers.com/showthread.php?t=1282019&page=65
Post number 643 had the link
I renamed the file to PG88IMG, put it on my sd card and loaded the Bootloader on the phone. It scanned the file, but did not give me am option to update.

Blindshot888 said:
oh! my apologies Skanob! the B and N keys are right next to each other..but still I should have double checked.
Okay, I've tried running the RUU exe file for the RUU you referred me to. unfortunately it didnt move past "rebooting to bootloader".
I also grabbed the OTA file from this link. http://forum.xda-developers.com/showthread.php?t=1282019&page=65
Post number 643 had the link
I renamed the file to PG88IMG, put it on my sd card and loaded the Bootloader on the phone. It scanned the file, but did not give me am option to update.
Click to expand...
Click to collapse
it should be PG88IMG.zip (.zip is the file extension). But have you double checked if the HBOOT was updated?

I can confirm that the file I used was indeed a .zip file.
From looking at the HBOOT version, its still sitting at 0.98.0002.

Blindshot888 said:
I can confirm that the file I used was indeed a .zip file.
From looking at the HBOOT version, its still sitting at 0.98.0002.
Click to expand...
Click to collapse
you might want to try to re-create your GoldCard. You might have a bad one.
Does the phone detects the file? There should be a check of .zip files once you boot on bootloader. The screen will take you there within 3-5 seconds after boot and will stay on checking the files for 1-2 seconds.

Blindshot888 said:
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
Click to expand...
Click to collapse
Hey man this says it all. You do not need to change hboots, flash RUU or other stuff. Just go to the service center and they will repair it for free. Like this guy did. If you have warranty of course

amidabuddha said:
Hey man this says it all. You do not need to change hboots, flash RUU or other stuff. Just go to the service center and they will repair it for free. Like this guy did. If you have warranty of course
Click to expand...
Click to collapse
or that ^^^^

How to S-ON the HTC Desire S, Unroot, remove Revolutionary and Clockwork Mod recovery

Hi folks, just thought I'd post my newly created video on here for anyone who wants to S-ON their HTC Desire S and revert it to a factory 'fresh' state.
*Please only follow these steps at your own risk etc etc as I cannot be held responsible if anything goes wrong!*
I searched for ages for the best way to do it and I think I've managed to portray it here in the video. A noticed an old thread which someone did on here (in the sticky section) has now been 'taken off' so thought I'd create a new one.
Let me know if you have any questions/comments and I hope this helps some of you out!
I've also done some quick instructions which should help out along with the video:
Today I will be showing you how to get your HTC Desire S to be “S-ON”. You only need to follow this video if you want to revert your phone back from a S-OFF state.
Why would I possibly want to do this?
There are several reasons:
1) If you need to send your phone back to HTC for repair it’s probably a good idea to remove any software you’ve put on the phone — they may no like it
2) If you want to revert to how your phone was when you first purchased it this is the best way to do it (some people call it factory defaults)
3) You’re bored and have 18 minutes and 5 seconds to spare.
What you will need:
1 x HTC Desire S (with at least 50% battery)
1 x USB Sync cable
1 x half-cup of tea
1 x de-stressing device
Firstly, you will want to download an RUU file. RUU stands for “ROM Update Utility” and this file contains the original software/firmware for your phone.
Go to here: http://forum.xda-developers.com/showthread.php?t=1002506 and then click the link to FileFactory which will bring up the list of ROM files. Find the one that matches your phone. If you are in the UK like me you’ll see “UK” in the file name. You also need to select the correct file depending on the phone operator/network you are on. I’m on T-Mobile so went for the “TMO” version.
Whilst that downloads, on XDA Developers again, search for “Revert back to stock (remove revolutionary)” http://forum.xda-developers.com/showthread.php?t=1387484 and you can download a lovely package from “giby21″ which contains Android Flasher and the HBOOT file you need.
********
**PLEASE NOTE** The RUU file for your phone is quite possibly different to the one mine uses so you may need to use a different HBOOT version. If you don't have the correct HBOOT version you will get an error messagee from the RUU setup/installer saying "error [140] bootloader version error".
********
Extract the files and then load Android Flasher. Please note you must have HTC Sync UNINSTALLED, USB Debugging mode enabled (in your phone’s settings) and you also need HTC’s Fastboot drivers installed for your phone to be picked up later. You can get the fastboot drivers from here: http://unrevoked.com/rootwiki/doku.php/public/revolutionary
Now select your device in Android Flasher and the select the Browse button under where it says “Bootloader”. Browse to where you extracted the “Revert to stock” .rar file and then the folder called “FlashENGHBOOT”. Select the .img file in there (named engHBOOToverARX.img) and press OK.
Now power off your Desire S and power back on whilst holding the Vol Down button. Click to select FASTBOOT and then plug it in via USB. Now back to the Android Flasher program and select “I’m already in fastboot” checkbox and press the “Flash!” button. You should now notice the REVOLUTIONARY title at the top has gone — great — it’s been removed.
Once flashed, reboot your phone and leave it plugged into the USB. Now you can right-click the RUU file you downloaded and “Run as Administrator”. This process will take about 10 minutes but after this you will be back with S-ON and to your original T-Mobile (or other operator) software.
Phew! Time for a drink!

Interesting guide, but there is a lot missing which you haven't evaluated on, which can cause users to get stuck.
Especially in the misc_version area side of things, eg. CID, Model ID etc.

Agreed with above, you should add a lot more detail. Cause people are going to fall flat with te RUU, also add changing your misc version.

Hi both, thanks for your feedback. The notes I wrote up were done whilst the video was being uploaded and I didn't have time to write in any more detail. I will however try and make it more 'user friendly' when I have a moment
Cheers.

jonjuk said:
Hi both, thanks for your feedback. The notes I wrote up were done whilst the video was being uploaded and I didn't have time to write in any more detail. I will however try and make it more 'user friendly' when I have a moment
Cheers.
Click to expand...
Click to collapse
Super OK

Doubt
Hi jonjuk
I first rooted my Desire S using one of the DesireFanatics Video. Now after OTS Upgrade HBOOT got upgraded as well, so no SOFF + root using revolutionary. I chose doing root (with S-ON) using alternate method.
This video will revert both the cases? or just the original HTC Desire S (before OTS upgrade)

xAutobot said:
Hi jonjuk
I first rooted my Desire S using one of the DesireFanatics Video. Now after OTS Upgrade HBOOT got upgraded as well, so no SOFF + root using revolutionary. I chose doing root (with S-ON) using alternate method.
This video will revert both the cases? or just the original HTC Desire S (before OTS upgrade)
Click to expand...
Click to collapse
Have you tried following the video system from jonjuk

luky4 said:
Have you tried following the video system from jonjuk
Click to expand...
Click to collapse
Yup and it simply uses android flasher. My doubt was if it will work on a root + s-on device hboot version 2.x (in my signature) that is after the OTS upgrade

Worked a treat. Followed this and now have a factory fresh phone

Mine still says:
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0002
WHAT DO I DO?

yajnibor said:
Mine still says:
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0002
WHAT DO I DO?
Click to expand...
Click to collapse
Go through the video again. I've also updated the written instructions slightly so have a read through them

jonjuk me wonder if the RUU rom contain Hboot 0.98.0000 or 0.98.0002 may also have, when ga installation.
Suppose rom RUU Saga Europe ver. 1.28.401.1 contains Hboot 0.98.0000.
Rom RUU Saga Europe ver. 1.47.401.4 gives Hboot 0.98.0002.
The question I asked, which RUU download.
You can this be tested?
I think this problem is occurring at yajnibor.
I ask for your opinion.
http://shrani.si/f/e/Tz/jQvpGJ3/hboot.jpg (RUU 1.28.401.1 )
http://shrani.si/f/3p/L2/10DkqOmg/hboot1.jpg (RUU 1.47.401.4 )

Help with RUU installation
I followed all your instructions but cannot seem to get the RUU to install. Whenever I run it I recieve error 140 asking me to get the correct RUU. I am using the RUU for virgin mobile which was on the link for RUU's that you provided.
My bootloader is as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
I have no ROM currently on there at the point I am at in your guide so every time I boot, I go straight into bootloader,
Any help on what I'm doing wrong or what I can do to get the RUU onto my phone.
Thanks.

luky4 said:
jonjuk me wonder if the RUU rom contain Hboot 0.98.0000 or 0.98.0002 may also have, when ga installation.
Suppose rom RUU Saga Europe ver. 1.28.401.1 contains Hboot 0.98.0000.
Rom RUU Saga Europe ver. 1.47.401.4 gives Hboot 0.98.0002.
The question I asked, which RUU download.
You can this be tested?
Click to expand...
Click to collapse
I'm not an expert on RUU files but yes, I think it does contain a new HBOOT which it installs. The reason you need to revert your HBOOT back, I think, is so the RUU file will recognise your phone correctly.

As I went through this by very hard path on my own and forum research, also I can confirm, that this guide is well presented, but it's missing a lot very significant information.

Forwox said:
As I went through this by very hard path on my own and forum research, also I can confirm, that this guide is well presented, but it's missing a lot very significant information.
Click to expand...
Click to collapse
Hi there, please let me know what I've missed and I'll add it into the video and the first post

I had HBoot 0.98.0002 and used Revolutionary to get S-off then loaded su file for root.
I now have...
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.04.02.01_M
eMMC-boot
I tried running Android Flasher to flash the EngHboot file but it is not doing anything.
It changes the phone to fastboot so I know it is communicating but after that the phone stays on the fastboot screen and Android Flasher stays on the "please wait while flashing your phone" screen. This has been unchanged for over an hour.
Can anyone advise what might be the problem ?

You can have a look here androidforums.com/desire-s-all-things-root/438830-guide-how-root-desire-s.html under section 2, it shows you other ways to flash the hboot.

Ive been messing with custom ROMS, but i miss that stock feeling Ill have to give this a go, hopefully not mess anything up... Cheers mate

Does anyone have a guide for returning to a stock ROM when you unlocked using htcdev.com? I tried (re)locking my device, but I can't get a RUU to install.
Edit: I unlocked and installed ClockworkMod after previously having upgraded to Android 2.3.5/Sense 3.0.

[Q] Error 155 Such a case has not yet gone.

I have RUU which I used a few times, this time one pops me "error 155" and check the CID still gives me H3G-UK H3G__001 but as I check the version does not show any information. Already changed the cables, I have uploaded the drivers, I downloaded the new files from the RUU.
TEMPERED
RELOCKED
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-1.08es 50.02.16
PpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
If anyone can solve this riddle?

Ironic this happened to you because I was just trying to go back to ( which I have successfully have done several times before ) my stock RUU file. I am also getting the ERROR 155. Maybe our issues are the same.
I have :
- Gone back to a stock rom
- Relocked Bootloader
- tried to run RUU from within Fastboot ( and every other way I could imagine )
Still get the ERROR 155! The only difference now is that I am coming back off a Jelly Bean ROM ( every other time I was on a Sense 4.04 based ROM)
Could that be the issue? Did it update my HBOOT to one that my stock RUU won't recognize? That seems to be were the RUU fails everytime. It blinks fast but I do beleive the RUU installer says something about HBOOT before it craps out.
Any suggestions or help would be appreciated by us both I presume!
Thanks! :fingers-crossed:

Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Sent from rooted awesomeness using xda premium

TheArtiszan said:
Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Click to expand...
Click to collapse
Thanks for the reply! I didn't even think to look for a log file for the RUU. Sure enough it was right on the root of my hard drive! The log confirms my suspicion :
<T230213><DEBUG><OUT>INFOchecking hboot version...</OUT>
</DEBUG></T230213>
<T230213><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
Somehow my HBOOT has been updated from the last time I have went back to stock. I don't remember doing an update last time I was STOCK and RELOCKED ( i might of though, can't remember! ). Is it possible that the Jelly Bean ROM I had installed after my last RELOCK, updated the HBOOT?
Sooooo.....I went ahead and I have extracted the HBOOT NB0 file from the ROM.ZIP that the RUU creates in a temp folder. Is there a way to push that onto my phone, then run the RUU?

Hope this helps!
So first off, to the OP Kobi71, sorry if I hijacked your thread! I was going to post about my issue and came across yours first which sounded pretty much identical! So hopefully my experience can help you!
So I got it to work! I have successfully flashed my RUU. What I found out from reading other threads and poking around was that my HBOOT was to new for the RUU file I had. There isn't an update RUU for my phone out there so I decided to give the HBOOT downgrade to 1.06 a shot.
[TUT] Downgrade/Unbrick Ville S4
http://forum.xda-developers.com/showthread.php?t=1990043&page=16
I followed the instructions and it all worked out just fine. READ through the instructions twice if you have too!
Understand them if you decide to try this because your essentially bricking your phone (at first). All being said, worked like a charm. Downgraded to HBOOT 1.06 from 1.13. The only "troubles" I had during the process, was that when I did step 9 and 12 the phone would hang on Sending Reset randomly throughout the process. Probably about ten times. So I did this each time :
absolutelygrim said:
" If it stalls at "Waiting for /dev/sdc12, hold the power button down on your phone about 10 seconds, or until your see "Qualcomm. Inc. Gobi Wireless Modem (QDL mode) disappear from your terminal window, then release it. 10 seconds or less after you do this, emmc_recovery will see your phone and proceed "
Click to expand...
Click to collapse
It also hung at the very end of the process too, so again hold the power button down if that happens to you.
After all that was done, I flashed the stock recovery from the ROM.ZIP that i got from the RUU ( don't know if I needed to do this ). Wiped everything/Factory reset. Then i relocked the bootloader. I then ran the RUU file, and it worked perfectly. Just like before. HBOOT was also "upgraded" to 1.08
Hope this helps your situation!

[Q] Issue going back to stock

Hi Guys, I've tried to do this myself reading other posts and not creating a thread but I have failed miserably so I am in need of some advice now. I need to try and get back to stock due to a warranty issue so I was following this guide here: http://forum.xda-developers.com/showthread.php?t=1460713
It seemed to be going well and I flashed the hboot which removed the revolutionary version, the RUU I used was the only Tmobile version I could find RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed and it started running through, it updated the hboot which is now S-On version 0.98.0000 but after that point it failed with error 140.
I don't understand why this has happened though as surely the version 0.98.0000 HBoot version is what is installed by the RUU itself so how can this be the wrong version? Is there something else I'm missing here.
At this point the phone is connected by USB to my laptop still and sat in HBoot, I'm not even sure if I can safely reboot at the moment so need some advice on what to do next?

I did that, had the same problem (around 3 weeks before you). I just ran it a gazillion times and then, I ended up flashing RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068 anyway. That worked. T-Mobile/HTC never said a word, fixed it and then sent my phone back.
But beware, the phone sent back will return on:
Android 4.0.4
Sense 3.6
Hboot 2.02.0002
Radio 20.76.30.0835U_3831.19.00.110
rlzzzz said:
Hi Guys, I've tried to do this myself reading other posts and not creating a thread but I have failed miserably so I am in need of some advice now. I need to try and get back to stock due to a warranty issue so I was following this guide here: http://forum.xda-developers.com/showthread.php?t=1460713
It seemed to be going well and I flashed the hboot which removed the revolutionary version, the RUU I used was the only Tmobile version I could find RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed and it started running through, it updated the hboot which is now S-On version 0.98.0000 but after that point it failed with error 140.
I don't understand why this has happened though as surely the version 0.98.0000 HBoot version is what is installed by the RUU itself so how can this be the wrong version? Is there something else I'm missing here.
At this point the phone is connected by USB to my laptop still and sat in HBoot, I'm not even sure if I can safely reboot at the moment so need some advice on what to do next?
Click to expand...
Click to collapse

So your problem is solved ? I want go back to S-ON and would get some feedbacks before doing this