Related
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.
Hello. I'm trying to run various ICS roms that require firmware 3.24 or more(Android Revolution HD for example and numerous others). For a while I was running Virtuous Inquisition on 3.12 firmware but wanted to try some others out so I downloaded the 3.30 firmware found on the firmware for beginners topic page.
I am using the correct firmware because I know what my CID/MID are:
cid:T-MOB010
mid: PG5810000
However, no matter what ROM i use, I tried VI, Revolution HD, Blitz, on either 3.24 or 3.30 or 3.32, I always get stuck in a bootloop. VI gets stuck on a bootloop on any firmware besides 3.12. What do I need to do to get the higher firmwares to work?
This is what my bootloader screen shows on the top when on firmware 3.12. If you guys need more information just ask and I'll post it when I can.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011, 12:14:25(clock seems to be super wrong idk why lol)
Thank you!
pr0adam said:
Hello. I'm trying to run various ICS roms that require firmware 3.24 or more(Android Revolution HD for example and numerous others). For a while I was running Virtuous Inquisition on 3.12 firmware but wanted to try some others out so I downloaded the 3.30 firmware found on the firmware for beginners topic page.
I am using the correct firmware because I know what my CID/MID are:
cid:T-MOB010
mid: PG5810000
However, no matter what ROM i use, I tried VI, Revolution HD, Blitz, on either 3.24 or 3.30 or 3.32, I always get stuck in a bootloop. VI gets stuck on a bootloop on any firmware besides 3.12. What do I need to do to get the higher firmwares to work?
This is what my bootloader screen shows on the top when on firmware 3.12. If you guys need more information just ask and I'll post it when I can.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011, 12:14:25(clock seems to be super wrong idk why lol)
Thank you!
Click to expand...
Click to collapse
Hi,
Have you had a look at THIS THREAD ?
Yes I have. Using this thread I found the firmware that is supposed to work with my phone using the CID I found using the information in that thread. However, the firmwares listed for my thread that are 3.24 onward do not work for any of the ROMs I have tried. Only 3.12 and 1.17 work for me. I'm not sure why this is.
I'm quite noob but probably you need to be supercid to flash some roms. You can follow the guide (in development forum 2nd sticky thread). Good luck
Strange you have locked bootloader btw.
Follow guide for superCID to see if that helps?
Sent from my Pyramid-T
Well, looks like I have a similar problem...
I'm SuperCID, and till this morning, I was running VI 3.5.1b.
Seeing on the VI thread that the latest firmware could be run with it, I upgraded to 3.32... and since then, I'm stuck in an bootloop.
I tried everything : rolling back to 3.24 and to 3.12 ; changing roms ; wiping everything I could ; but i won't help.
Most of the times, I'm stuck at the HTC Splashscreen ; VI and Tripnice (yeah, even tried that one) go to the boot animation, then reboot. So I'm at a loss here as to what to do to fix it. Any help would be very welcome and appreciated !
pr0adam said:
Hello. I'm trying to run various ICS roms that require firmware 3.24 or more(Android Revolution HD for example and numerous others). For a while I was running Virtuous Inquisition on 3.12 firmware but wanted to try some others out so I downloaded the 3.30 firmware found on the firmware for beginners topic page.
I am using the correct firmware because I know what my CID/MID are:
cid:T-MOB010
mid: PG5810000
However, no matter what ROM i use, I tried VI, Revolution HD, Blitz, on either 3.24 or 3.30 or 3.32, I always get stuck in a bootloop. VI gets stuck on a bootloop on any firmware besides 3.12. What do I need to do to get the higher firmwares to work?
This is what my bootloader screen shows on the top when on firmware 3.12. If you guys need more information just ask and I'll post it when I can.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011, 12:14:25(clock seems to be super wrong idk why lol)
Thank you!
Click to expand...
Click to collapse
Hi there. There are a lot of people here who will help you but you need to work through a procedure such as this Thread and identify what you have done and where you get stuck.
Mercvtio said:
Well, looks like I have a similar problem...
I'm SuperCID, and till this morning, I was running VI 3.5.1b.
Seeing on the VI thread that the latest firmware could be run with it, I upgraded to 3.32... and since then, I'm stuck in an bootloop.
I tried everything : rolling back to 3.24 and to 3.12 ; changing roms ; wiping everything I could ; but i won't help.
Most of the times, I'm stuck at the HTC Splashscreen ; VI and Tripnice (yeah, even tried that one) go to the boot animation, then reboot. So I'm at a loss here as to what to do to fix it. Any help would be very welcome and appreciated !
Click to expand...
Click to collapse
Well in such case I would extract the rom.zip from the official RUU (I hope you know how to do) and flash it as PG58IMG. Then start again the whole procedure.
Go to [ROM]Shipped Pyramid ROM Collection thread and dowload the RUU_PYRAMID_ICS_HTC_Europe_3.30.401.1_Radio_11.69.3504.00U_
Sorry but I cannot post links right now.
You won't lose superCID and S-OFF so it worths trying.
I have made my phone superCID and will now try to run the higher firmwares and see if that works this time around. I'll let you guys know if anything changes thanks for the help thus far
pr0adam said:
I have made my phone superCID and will now try to run the higher firmwares and see if that works this time around. I'll let you guys know if anything changes thanks for the help thus far
Click to expand...
Click to collapse
Waiting for good news
Mercvtio said:
Well, looks like I have a similar problem...
I'm SuperCID, and till this morning, I was running VI 3.5.1b.
Seeing on the VI thread that the latest firmware could be run with it, I upgraded to 3.32... and since then, I'm stuck in an bootloop.
I tried everything : rolling back to 3.24 and to 3.12 ; changing roms ; wiping everything I could ; but i won't help.
Most of the times, I'm stuck at the HTC Splashscreen ; VI and Tripnice (yeah, even tried that one) go to the boot animation, then reboot. So I'm at a loss here as to what to do to fix it. Any help would be very welcome and appreciated !
Click to expand...
Click to collapse
Can you reach recovery or bootloader?
Sent from my Pyramid-T
Nope still doesnt work. 3.32 still bootloops on various ICS roms i tested(ARHD and Blitz) even with superCID
stringer7 said:
Can you reach recovery or bootloader?
Sent from my Pyramid-T
Click to expand...
Click to collapse
Yup, still got access to both of them. I resolved my problem by flashing both the firmware and the latest rom from He Who Must No Be Named... For a reason I still don't grasp, it seems that the firmwares I flashed previously didn't downgrade the bootloader, or something like that. Trip's one, however, is a waaaay bigger file and seems to rewrite a huge amount of things.
Don't know yet if I could switch back to VI harmlessly, though...
Sorry- of course you can reach bootloader, you listed it in your OP! Tired...
Something strikes me, you have hboot 1.23, I know this version causes issues with s-on users that have accepted OTA updates.
Have you run s-off via revolutionary in the past? Unlocked via htc.dev (which I think gives hboot 1.23)?
Does recovery work?
Sent from my Pyramid-T
Mercvtio said:
Yup, still got access to both of them. I resolved my problem by flashing both the firmware and the latest rom from He Who Must No Be Named... For a reason I still don't grasp, it seems that the firmwares I flashed previously didn't downgrade the bootloader, or something like that. Trip's one, however, is a waaaay bigger file and seems to rewrite a huge amount of things.
Don't know yet if I could switch back to VI harmlessly, though...
Click to expand...
Click to collapse
Great!
Might still be worth checking out what I posted above to see if something in that causes the problem?
Sent from my Pyramid-T
After reading more around the forums I'm pretty sure I need a custom firmware. One with the HBOOT of 3.12 but the rest of the files of a 3.32 firmware. How would I go about doing this?
I wouldn't mess things more than this.
I would go back to GB first.
Download the appropriate official RUU for your device and run it on the pc until appears the picture of a phone and "show readme file). Leave this window open.
then go to "My computer"-disk C (or wathever)- Documents and settings-name of computer (or your name)- local settings - Temp.
There you will find a folder or more folders with a weird name ie: {040EEDE2-371A-4BF6-8D25-1B12121F8D9E}.
Inside one of this folder you will find a file "rom.zip". do not extract, just drag and drop somehere in your pc.
Now close the RUU windows by clicking cancel.
Now rename "rom.zip" in PG58IMG and put in the root of your SD card.
Reboot your phone by pressing vol down+power.
At this point the file PG58IMG will be detected you will be asked to update. Say yes by pressing volume up.
Be patient as it will take a lot of time, don't touch or do anything until it has finished. a lot of files will be flashed and screen may goes black a couple times.
Dont worry and wait until it will say "press power to reboot".
Now you should be back to stock GB and start all procedures to upgrade once more if you like.
Remember then to delete the PG58IMG on the SD card.
When you will set your phone again, remember to untick fastboot for future use.
Hope it helps
PS: Forgot to say that by doing this you will lose root (not S-OFF and superCID) but you can easly re-root your device by following the guides in the forum.
So I managed to flash back to 3.32 and VI 4.0 after 2 days of mercyless bootlopping.
What I did was :
1- superwipe everything, flash latest TripOS rom
2 - reboot to bootloader and flash Trip's latest firmware (this way, I knew I woul have both a matching rom and matching firmware, avoiding incompatibility issue). Trip's firmware rewrites a huge amount of things, and that seems to put an end to what was causing my bootloops.
3 - reboot and let the phone alone for 10 minutes, just to let everything settle right.
4 - reboot to recovery
5 - Superwipe again
6 - flash my rom (in my case, VI 4.0)
7 - power off, and boot to bootloader
8 - flash 3.32 firmware
9 - reboot and let the phone still for 10 minutes
So far everything runs perfectly (I just have a splash screen saying "Trip'n Nice" on it) and it saved me from going into the process of flashing a RUU, rooting the RUU, installing recovery and so on. Give it a try, it might work for you to.
Looks like He has HBOOT 1.23, so I suspect He's using HTC-Dev method to unlock the boot loader or running FOTA that maybe gives him HBOOT 1.23.
Since Revolutionary could only S-OFF up to HBOOT 1.18, so maybe He just need to wait till Revolutionary support HBOOT 1.23 (the only options, maybe next year )
BTW, what are You doing that causing You to have HBOOT 1.23?
problem is that his bootloader shows ***Locked***.
If you go through htc-dev it would have shown ***Unlocked***.
This is why I would start from the beginning flashing a GB RUU and then start again the upgrade process.
My humble opinion, of course
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!
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
Hey all. I posted this in the wrong forum by accident, so reposting here. Also, this may have been asked before but I did a search and couldn't find a thread quite like it!
I am currently running Android 2.3.3 and HTC Sense 2.1 on my HTC Desire S. I have used the Revolutionary method to S-OFF and root the phone, which allowed me to uninstall branded bloatware and add some interesting apps.
I have not been able to update the phone as quite frankly I have no idea what I'm doing, and the OTA update will brick the phone. Can anyone please tell me what I need to do to get the latest version of Android and HTC Sense?
I'm in the UK on the Three network. After doing an extensive search for the specific RUU matching that, I can't seem to find it unfortunately.
Many thanks for your time.
I'd suggest you just flash a custom sense rom from dev section, which is very easy to do. and a lot of those are better than the HTC ICS rom
If you really want to go back to stock HTC, follow this video guide, check video description for links
http://www.youtube.com/watch?v=X71RtQQjbqk
You can find 3 branded RUU here, at the bottom of the list
http://www.shipped-roms.com/index.php?category=android&model=Saga
Ahhh thanks so much for that list! There was a forum post I found with details on how to unroot, but all the links to the RUUs were dead. Does it matter which RUU I use so long as it's meant for the UK? I can't seem to find the one for Three network, unless it's under "H3G_UK"...
xTheLostProphetx said:
Ahhh thanks so much for that list! There was a forum post I found with details on how to unroot, but all the links to the RUUs were dead. Does it matter which RUU I use so long as it's meant for the UK? I can't seem to find the one for Three network, unless it's under "H3G_UK"...
Click to expand...
Click to collapse
Is your phone branded? If not, just use the Europe ruu
thwbyan mon
Well it has a Three network splash screen and sadly it's still locked to the network, but other than that I don't think so
xTheLostProphetx said:
Ahhh thanks so much for that list! There was a forum post I found with details on how to unroot, but all the links to the RUUs were dead. Does it matter which RUU I use so long as it's meant for the UK? I can't seem to find the one for Three network, unless it's under "H3G_UK"...
Click to expand...
Click to collapse
Yes that's the one
I'm very sorry to have to bump this, but I followed the instructions that I was given and ended up with the infamous Error [140].
While fastbooting, I now have:
***Security Warning***
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.14_M
eMMC-boot
Mar 10 2011,14:58:38
And when I try to use the OTA update, it goes straight into this Fastboot screen. I literally have no idea what's going on now.
xTheLostProphetx said:
I'm very sorry to have to bump this, but I followed the instructions that I was given and ended up with the infamous Error [140].
While fastbooting, I now have:
***Security Warning***
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.14_M
eMMC-boot
Mar 10 2011,14:58:38
And when I try to use the OTA update, it goes straight into this Fastboot screen. I literally have no idea what's going on now.
Click to expand...
Click to collapse
you must install the original RUU, which will remove all your data and install original ROM Android 2.3.3, recovery, hboot and radio
i suggest RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed-ORIGINAL.exe from here http://www.androidfiles.org/ruu/?developer=Saga
or you can put this zip on your sd card, and install it from bootloader: http://dfiles.eu/files/bh4avk6uz (easier method)
Thank you for your link and RUU file. I tried running the Europe RUU.exe, but came up with "Error 131: Customer ID error". Still the same information in the bootloader as before though.
Sorry to bump this again, does anyone have a fix?
Or would it be easier to root and s-off once more then flash a rom that was similar to stock?
xTheLostProphetx said:
Sorry to bump this again, does anyone have a fix?
Or would it be easier to root and s-off once more then flash a rom that was similar to stock?
Click to expand...
Click to collapse
probably be easier to s-off and flash ice cold, it's the closest to stock with none of the bugs of stock
Never interrupt me when I'm eating a banana.
Ryan Stiles