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.
Here's my "little" story on how I ended up on xda forums asking for help on wifi. TL;DR is at the bottom.
I've owned the sensation for about a year now, or so it seems. Always remained stock everything. Loved it because it felt so smooth, faster than any other phone i have owned previously with Tmo. Updated every OTA update they threw at me, had no plans to root, flash roms of the sort.
UNTIL the latest ICS update, i was a little late on receiving it. I'd say its been about a few weeks since i got ICS OTA on my STOCK sensation. Downloaded it and thought WOW awesome, didn't even expect this. Everything was good until i noticed my wifi wasn't working. This really dampened my spirits as i am a HEAVY user of wifi, weather i'm at work or at home.
I then did my research and found out i wasn't the only one with this wifi problem. Of course Tmo forums had troubleshooting tips for the blind, deaf ,and armless.
"have you tried turning it off?"
"resetting it?"
Tips that you know aren't going to help. Anyways i resorted to checking out this flashing, rom, rooting, s-offing business. Got to say i spent a whole day just going from thread to thread just to be able to grasp the idea of what i was getting myself into. After countless boxes of cheez-its and hours spent on reading up on this, i conjured up enough courage to believe i was ready.
From what i read since i had updated to ics i was not able to "s-off" using the revolutionary website because i was hboot 1.27.... yada yada
so i used i believe it was called "asskickers guide for flashing roms with s-on, 1.27 hboot.
To make this long story shorter, i followed his guide to the T.
And that abled me to have root, and flashed my first rom while S-on using smartflash with 4EXT.
I even used the rom he suggested in the guide, revolutionary HD 6.7.0 4G-XE
Everything went smooth, and the rom booted up and everything.
To my discovery my wifi still wasn't working. This really had me bouncing off the wall.
Luckily in the guide it explained that wifi would be an issue, and had a small guide on how to fix it. Flashing boot.img with the matching kernal you selected in the rom. GREAT i thought. but still, that didn't work.
I don't know if i did it wrong, i really don't think i did because i follow instuctions to the T. Or so i think.
Anyways.
Did more research and found out that most S-On users had the wifi problem beacuse of the Dev unlock only unlocking certain. Sorry for my bad wording, lets not forget I'm a first timer.
Anyways after reading about that i assumed i had to go S-off now. SO i used Juopunutbear S-OFF (HBOOT 1.27.0000 with 3.32 ICS Firmware) method.
I used this method and how challenging it was with that paper clip wire trick it was to get it. I swear it took me at least 20 tries, but finally got it and succesfully got S-off to show on the white screen, bootloader i believe its called.
So after i got s-off i reinstalled the rom, whiped everything and re-flashed it.
Still no luck on wifi. So now this has me crawling at my knees begging what more could i do to fix this wifi nightmare of mine. PLEASE if anyone could help, i'd be forever thankful.
AS of right now i am...
Unlocked Dev
S-off
Hboot - 1.27.0000
Android version - 4.0.3
Htc sense - 3.6
ROM - Android Revolution HD 6.7.0 4G-XE
Kernel - 3.0.16-v1.30.2 Sebastion FM#1
Baseband version - 11.69A.3504.00P_11.23.3504.07_M2
Build number - 3.32.531.14 CL356011
TL;DR My wifi is still not working after I feel that i've done all that i can. ANY suggestions would help. Please and thanks you.
Thanks to anyone that actually reads all of this sort of rant of mine.
Question: what do you mean wifi is broken? Do you mean it doesn't turn on or it doesn't find any networks or what?
Sent from my commodore 64 running android 4.1
Hmm simple.. Solution is there.. Let's see
You have unlocked the bootloader after soff.. You should not do that.. After soff you can flash engineering hboot.. Which comes with soff method.. (juopunutbear/revolutionary) which are much much better than the unlocked hboot
Ok
Now to the point
Try the tmous ruu..
Ruu = rom update utility.. The official one of HTC
Search for pyramid shipped rom collections.. Thread in sensation development section.. And get the pyramid ics.. Ruu of tmobile
And run it...
It's an exe file so.. Just double click on it
But remember.. As you have done unlock of bootloader.. You need to re lock it first (fastboot oem lock)
Also you need to connect the phone to pc... From bootloader/fastboot ( phone reads fastboot usb after this)
Then run the ruu.. It should solve your wifi issue
Sent from my pyramid.. Through blazing fast sonic waves
@sy22
it does that whole "turning on wifi..." then it goes to error after a while.
@ganeshp
Thanks thanks thanks a bunch, i'll be doing this today and see if it solves my long and twisted journey. :fingers-crossed:
If that doesnt work then it could be a hardware fault. I used to have wifi issues and after flashing a whole bunch of roms and seeing it still failing to turn on, I gave up and S-ON'd my sensation and sent in to repairs and have had no problems since
IT could be hardware problems but the thing that gets me is that my wifi has always worked.
Like i said i've owned it for about a year now or so it feels, and i've never had problems with it until that OTA update to ICS.
but if all fails then i'll throw in the towel and undo all this mess and send it in i suppose.
ganeshp said:
Hmm simple.. Solution is there.. Let's see
You have unlocked the bootloader after soff.. You should not do that.. After soff you can flash engineering hboot.. Which comes with soff method.. (juopunutbear/revolutionary) which are much much better than the unlocked hboot
Ok
Now to the point
Try the tmous ruu..
Ruu = rom update utility.. The official one of HTC
Search for pyramid shipped rom collections.. Thread in sensation development section.. And get the pyramid ics.. Ruu of tmobile
And run it...
It's an exe file so.. Just double click on it
But remember.. As you have done unlock of bootloader.. You need to re lock it first (fastboot oem lock)
Also you need to connect the phone to pc... From bootloader/fastboot ( phone reads fastboot usb after this)
Then run the ruu.. It should solve your wifi issue
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Alrighty I did just this exactly.
Ran RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed
let it complete to the last step. phone rebooted and still no wifi
i hate to be such trouble, but if anyone has anymore suggestions, i'd appreciate it.
Thanks again to anyone who reads,replies with suggestions.
Am now showing in the white screen-
***relocked***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.23.3504.07_M2
openADSP-v02.6.0.2226.00.0131
eMMC-boot
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!
I examined most if not all Boot Loop related items in XDA-Developers, as well as other sources. Although there are lots of suggestions, I cannot find one that relates to my specific situation. The last thing I want to do is make it worse. So, here's my story. I'll keep it brief, but concise.
I've had my Sensation 4G for a little over two years. Soon after purchase, I rooted it via the Revolutionary mechanism. Unfortunately (I think), I also opted for the Clockwork Mod. Unfortunately, I have not been able to do OTA updates, and find I'm still running 2.3.4.
I recently desired to purchase the HTC One for T-Mobile, and did so. I wanted to pass on my Sensation 4G to my sister. Therefore I needed to unroot it. I did weeks of reading about all the ways to do this. Early last week I attempted doing so by following the directions found here (http://kgs1992.com/ruu-guide/). I used the PG58IMG file found here (http://forum.xda-developers.com/showthread.php?t=1459767#2). The file selected was Firmware 3.33 Universal: (http://d-h.st/SuC). I followed the directions precisely. All appeared to run properly, and appeared to end with successful messages. At the end of the instructions it states "If you experience a boot loop, repeat 4.4.2 again." I did that several times. I still have the boot loop.
I started the process with this...
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMCC-boot
Jun 2 2011.22:31:39
HBOOT
(VOL UP) to previous item
(VOL DOWN to next item
(POWER) to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Following afore-mentioned process it says...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
That brings me to my big question. What do I do now? I had hoped to retain my contacts and applications. I'd like to first attempt ways to fix it and still salvage what's on the phone, but ultimately I just need the phone to work. I should also mention that I've downloaded the following two files. My next attempt was going to execute the top one, but I don't know the status of the phone after doing so. Can anyone help me? Are there other things I should try first?
RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed.exe
Micalee said:
I examined most if not all Boot Loop related items in XDA-Developers, as well as other sources. Although there are lots of suggestions, I cannot find one that relates to my specific situation. The last thing I want to do is make it worse. So, here's my story. I'll keep it brief, but concise.
I've had my Sensation 4G for a little over two years. Soon after purchase, I rooted it via the Revolutionary mechanism. Unfortunately (I think), I also opted for the Clockwork Mod. Unfortunately, I have not been able to do OTA updates, and find I'm still running 2.3.4.
I recently desired to purchase the HTC One for T-Mobile, and did so. I wanted to pass on my Sensation 4G to my sister. Therefore I needed to unroot it. I did weeks of reading about all the ways to do this. Early last week I attempted doing so by following the directions found here (http://kgs1992.com/ruu-guide/). I used the PG58IMG file found here (http://forum.xda-developers.com/showthread.php?t=1459767#2). The file selected was Firmware 3.33 Universal: (http://d-h.st/SuC). I followed the directions precisely. All appeared to run properly, and appeared to end with successful messages. At the end of the instructions it states "If you experience a boot loop, repeat 4.4.2 again." I did that several times. I still have the boot loop.
I started the process with this...
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMCC-boot
Jun 2 2011.22:31:39
HBOOT
(VOL UP) to previous item
(VOL DOWN to next item
(POWER) to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Following afore-mentioned process it says...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
That brings me to my big question. What do I do now? I had hoped to retain my contacts and applications. I'd like to first attempt ways to fix it and still salvage what's on the phone, but ultimately I just need the phone to work. I should also mention that I've downloaded the following two files. My next attempt was going to execute the top one, but I don't know the status of the phone after doing so. Can anyone help me? Are there other things I should try first?
RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed.exe
Click to expand...
Click to collapse
You will probably have to wipe the data partition, and therefore delete your contacts and apps (but if your contacts are saved on your google account they will be restored).
:
Do you have access to the recovery? from there you can flash a ROM and do a fresh install. I got that problem when I upgraded to the newer firmware, and I just flashed the ROM, and then everything worked fine.
astar26 said:
You will probably have to wipe the data partition, and therefore delete your contacts and apps (but if your contacts are saved on your google account they will be restored).
:
Do you have access to the recovery? from there you can flash a ROM and do a fresh install. I got that problem when I upgraded to the newer firmware, and I just flashed the ROM, and then everything worked fine.
Click to expand...
Click to collapse
I'm not sure I know what the data partition is. I can get to all my apps via play.google.com. I took full Titanium Backups, so maybe that'll be an option. Those backups were copied to my laptop.
As to Recovery, I can access it, but cannot put anything on the sd card as I do not have access to it. Apparently I can only do things via ADB.
I was just reading "A must read for those noobs who want to enjoy ICS". Perhaps there is a solution. There are apparently conflicts with Hboot versions and ICS or something. I just found that, so I'm still looking into that. I don't know how to deal with only Hboot.
Micalee said:
I'm not sure I know what the data partition is. I can get to all my apps via play.google.com. I took full Titanium Backups, so maybe that'll be an option. Those backups were copied to my laptop.
As to Recovery, I can access it, but cannot put anything on the sd card as I do not have access to it. Apparently I can only do things via ADB.
I was just reading "A must read for those noobs who want to enjoy ICS". Perhaps there is a solution. There are apparently conflicts with Hboot versions and ICS or something. I just found that, so I'm still looking into that. I don't know how to deal with only Hboot.
Click to expand...
Click to collapse
You can connect your MicroSD card via another phone to the PC, and also use the "adb push" command to push the ROM files to the root of the microSD card. Also, some recoveries allow mounting the SD card to the PC like doing it when the phone is booted, as an external drive, check for it in the recovery.
To move the ROM files to the SD card:
put the files in the folder where ADB is located
On command line type: "adb push rom.zip /sdcard/rom.zip"
Where rom.zip is the name of the rom file you are going to flash. this should work, here is a full guide to help you pushing the file via ADB: http://forum.xda-developers.com/showthread.php?t=1667929
Good luck
astar26 said:
You can connect your MicroSD card via another phone to the PC, and also use the "adb push" command to push the ROM files to the root of the microSD card. Also, some recoveries allow mounting the SD card to the PC like doing it when the phone is booted, as an external drive, check for it in the recovery.
To move the ROM files to the SD card:
put the files in the folder where ADB is located
On command line type: "adb push rom.zip /sdcard/rom.zip"
Where rom.zip is the name of the rom file you are going to flash. this should work, here is a full guide to help you pushing the file via ADB: http://forum.xda-developers.com/showthread.php?t=1667929
Good luck
Click to expand...
Click to collapse
That certainly sounds doable. I went to the link you provided. I'm not sure how pushing the rom.zip to the sdcard and doing the recovery via the phone's recovery is different than via the adb command as done earlier. The adb command process seemed to work correctly, except for the resulting boot loop. Apparently I still need to determine which rom.zip will leave me with a function phone. The only other difference in what I read at the link you provided was to do the various ["Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache]" commands, which I have not done. I need to determine whether those commands are necessary in my case. Thank you for your contribution.
What's happens here is that you have placed ice cream sandwich firmware with a gingerbread Rom. Gingerbread doesn't support it and as such won't boot. If you want to regain access to everything again the reflash 1.17 firmware from the thread. Then your Rom should boot up. Then jump to recovery and make a full nandroid back up. Then re-flash the ics 3.33 universal firmware and then run one of the ics ruu's you downloaded. That will make the phone have a fresh install of ics and stock HTC sense unrooted
don't try to s-on again as their is no real point to it. It's not going back for warrenty so what's the concern eh?
Good luck pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Micalee said:
That certainly sounds doable. I went to the link you provided. I'm not sure how pushing the rom.zip to the sdcard and doing the recovery via the phone's recovery is different than via the adb command as done earlier. The adb command process seemed to work correctly, except for the resulting boot loop. Apparently I still need to determine which rom.zip will leave me with a function phone. The only other difference in what I read at the link you provided was to do the various ["Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache]" commands, which I have not done. I need to determine whether those commands are necessary in my case. Thank you for your contribution.
Click to expand...
Click to collapse
If you want you should backup via recovery, but wiping the phone after is necessary. if you managed to push the ROM to the SD-card, you can normally flash. but use a ICS (or newer) ROM, that supports the firmware.
In contrast to what heavy_metal_man said, you can do a nandroid backup as it is, as the files are still there. but you don't have much to do with it.
Edit - If you need any help doing it step by step - I'm here to help, just say where you are stuck on the guide (or just explain)
heavy_metal_man said:
What's happens here is that you have placed ice cream sandwich firmware with a gingerbread Rom. Gingerbread doesn't support it and as such won't boot. If you want to regain access to everything again the reflash 1.17 firmware from the thread. Then your Rom should boot up. Then jump to recovery and make a full nandroid back up. Then re-flash the ics 3.33 universal firmware and then run one of the ics ruu's you downloaded. That will make the phone have a fresh install of ics and stock HTC sense unrooted
don't try to s-on again as their is no real point to it. It's not going back for warrenty so what's the concern eh?
Good luck pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
Thanks heavy_metal_man for that information. In the mean time, while waiting for another suggestion, I decided to try a different rom. That was due to the comments I'd seen about conflicts between Hboot and ICS. So, just for the heck of it I went through whole routine, using ROM V3.12. After doing so (twice), the phone booted! Amazingly, other than thinking it's 1970, it appears to be identical to what it was before I ever did anything. It's still running V2.3.4 of Android, and Sense V3.0. I don't recall which version of Sense was there before. After it booted, I shut it down again and put it in Recovery mode. There have been a number of changes there. Now it says...
*** 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
Does any of this information affect or change your suggestion in any way? I'd still like to get ICS on this thing so the latest is available for when I give it to my sister. I wonder what will happen if I attempt OTA? By the way, it still has Revolutionary CWM V4.0.1.4 on it.
Micalee said:
Thanks heavy_metal_man for that information. In the mean time, while waiting for another suggestion, I decided to try a different rom. That was due to the comments I'd seen about conflicts between Hboot and ICS. So, just for the heck of it I went through whole routine, using ROM V3.12. After doing so (twice), the phone booted! Amazingly, other than thinking it's 1970, it appears to be identical to what it was before I ever did anything. It's still running V2.3.4 of Android, and Sense V3.0. I don't recall which version of Sense was there before. After it booted, I shut it down again and put it in Recovery mode. There have been a number of changes there. Now it says...
*** 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
Does any of this information affect or change your suggestion in any way? I'd still like to get ICS on this thing so the latest is available for when I give it to my sister. I wonder what will happen if I attempt OTA? By the way, it still has Revolutionary CWM V4.0.1.4 on it.
Click to expand...
Click to collapse
you just used a ruu.exe from pc and restored everything to stock condition
but how you were able to keep custom recovery(cwm V4.0.1.4)
when you flashed the 3.33 firmware you could just install a custom ics rom
because with 3.33 firmware the gb rom you had it would never booted
about OTA i assume nothing will happen as long as you have cwm recovery installed
you must have the stock recovery
Well, since you flashed a new rom you can disregard my first suggestion and go straight for running the ics ruu you have. Ota updates will not work if you dont have the stock recovery. But the ruu will give you it so ota will work, but the updates will be for the cid of the rom you flashed. So flash a WWE rom to make sure you get any updates, but at this point their will be few if any.
Aside from that you will be all sorted pal
Sent from my Nexus 7 using Tapatalk 4
Thanks again heavy_metal_man. It wasn't that I ignored your suggestion, I tried the second (V3.12) Rom before I had seen it. As for your last entry, I was following it until you hit me with the WWE reference. As for the V3.12 Rom I used, there was a direct MIB match, and the CID used was cid******, so a direct match was not necessary as far as I can determine. I could have edited the txt file and inserted my actual CID however. Also, was your comment about "the ics ruu I have", in reference to the two RUU_PYRAMID_ICS_TMOUS...etc. files I mentioned that I had already downloaded? Running one of those will be a new experience. I'll run the latest. If that works, I'll be a happy camper. I've learned a lot, but I have a long way to go.
Micalee said:
Thanks again heavy_metal_man. It wasn't that I ignored your suggestion, I tried the second (V3.12) Rom before I had seen it. As for your last entry, I was following it until you hit me with the WWE reference. As for the V3.12 Rom I used, there was a direct MIB match, and the CID used was cid******, so a direct match was not necessary as far as I can determine. I could have edited the txt file and inserted my actual CID however. Also, was your comment about "the ics ruu I have", in reference to the two RUU_PYRAMID_ICS_TMOUS...etc. files I mentioned that I had already downloaded? Running one of those will be a new experience. I'll run the latest. If that works, I'll be a happy camper. I've learned a lot, but I have a long way to go.
Click to expand...
Click to collapse
ah sorry, getting ahead of myself with terminology here WWE stand for world wide English. most unbranded phones run on world wide English roms, and if people are downgrading/upgrading they tend to want unbranded as they will get official htc updates faster
as far as cid`s are concerned they dont really matter as you are s-off and the phone will accept any ruu (rom update utility) you give it. one note of caution though is you have select a t-mobileus ruu and they are ment to be for the tmobile sensation 4g. if you dont have the tmobus 4g it may give you some issues with the radio, meaning you may lose phone signal. ( im not 100% sure but caution is advised )
if you dont have a sensation 4g then download and run this one here. im pretty confident that its a stock ice cream sandwich unbranded rom
Running the RUU is simple enough, just boot the phone into your stock 2.3.4 rom and turn on usb debugging from settings for good measure. Then connect the phone to the pc via the usb cable and then run the RUU. it will connnect to the phone and confirm the phone is the correct model i believe, then it will confirm this is what you want to do. select yes and let it work its magic. its pretty straight forward they phone may reboot several times, this is normal. just dont disconnect the battery or the usb cable and you will be fine. should be done in ten minutes tops
good luck pal
I made it through the RUU process, but not without some difficulty. When I ran the RUU_PYRAMID_ICS_TMOUS_3.32.531.14 version, it died with an Error 155. Fortunately it left everything intact. Then I ran the older RUU_Pyramid_TMOUS_1.50.531.1 non-ICS version. It got the same error. I think these errors must somehow be due to the peculiar results from flashing the PG58IMG file earlier. Once again, it left everything intact. I tried the RUU ICS 3.32 version one more time, except this time I put the phone in flashboot mode first. Curiously, the RUU screen that came up thought it was updating a later version than what was actually on the phone, but IT RAN... all the way through to a successful finish. I was stunned. Now the phone reports...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
The entire process left my SD card intact as well. Amazing. It still says S-OFF as you expected. I may or may not attempt turning S-On again.
One comment I'd like to make about xda-developers. There is an amazing amount of information here. The biggest problem I've encountered is trying to figure out if I'm looking at, or have found, the latest information. Some times I'll find something that looks pertinent, only to find that I'm on page 2 of a 114 page thread, and the information I'm looking at is completely obsolete. It's tough for a noob to decipher it all. Anyway, thanks again for everyone's assistance. I think this is a proper place to terminate this particular thread. Now I'll start looking for the latest information on rooting my new HTC ONE. At least I have a fall back phone in my newly restored Sensation 4G. I'm not sure I'm in love the ONE yet, so perhaps I'll take it back. I'm within my 14 day return window.
I'm glad your sorted pal the threads can be a bit out of date, maintenance of information is not really regulated but as always if people are unsure just ask, quoting the info you have and what you think is the case
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Micalee said:
I made it through the RUU process, but not without some difficulty. When I ran the RUU_PYRAMID_ICS_TMOUS_3.32.531.14 version, it died with an Error 155. Fortunately it left everything intact. Then I ran the older RUU_Pyramid_TMOUS_1.50.531.1 non-ICS version. It got the same error. I think these errors must somehow be due to the peculiar results from flashing the PG58IMG file earlier. Once again, it left everything intact. I tried the RUU ICS 3.32 version one more time, except this time I put the phone in flashboot mode first. Curiously, the RUU screen that came up thought it was updating a later version than what was actually on the phone, but IT RAN... all the way through to a successful finish. I was stunned. Now the phone reports...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
The entire process left my SD card intact as well. Amazing. It still says S-OFF as you expected. I may or may not attempt turning S-On again.
One comment I'd like to make about xda-developers. There is an amazing amount of information here. The biggest problem I've encountered is trying to figure out if I'm looking at, or have found, the latest information. Some times I'll find something that looks pertinent, only to find that I'm on page 2 of a 114 page thread, and the information I'm looking at is completely obsolete. It's tough for a noob to decipher it all. Anyway, thanks again for everyone's assistance. I think this is a proper place to terminate this particular thread. Now I'll start looking for the latest information on rooting my new HTC ONE. At least I have a fall back phone in my newly restored Sensation 4G. I'm not sure I'm in love the ONE yet, so perhaps I'll take it back. I'm within my 14 day return window.
Click to expand...
Click to collapse
actually are you sure that you flashed the ruu.exe correctly?
you still have the patched hboot and on top of the screen it still says firmware 3.33 which is the patched one
don't attempt to S-ON.probably you will brick the device
after ruu installation your bootloader should say relocked or locked on top of the screen
edit:if i remember well error 155 means a connection issue
rzr86 said:
actually are you sure that you flashed the ruu.exe correctly?
you still have the patched hboot and on top of the screen it still says firmware 3.33 which is the patched one
don't attempt to S-ON.probably you will brick the device
after ruu installation your bootloader should say relocked or locked on top of the screen
edit:if i remember well error 155 means a connection issue
Click to expand...
Click to collapse
Flashed? All I did was run the program. It did whatever it did. I think the 3.33 was somehow left over from flashing a PG58IMG I'd gotten from here>http://forum.xda-developers.com/showthread.php?t=1459767#2. That failed as explained earlier in this thread. I figured that running the RUU would overwrite that failure, and I'm surprised it didn't. All I care is that I'm now getting OTA updates correctly. Yeah, I won't be trying to S-ON. I've thought about rerunning the RUU (3.32) again, but for now I'm going to just leave well enough alone.
I forgot to mention. This information was in the documentation for the RUU
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
One last note. I returned the HTC ONE, and have reactivated the Sensation 4g which this thread is about. The HTC ONE hardware is wonderful, but I didn't like all the HTC ONE software "features" you can't turn off. Maybe I'll jump ship and go with the Samsung Galaxy S4. In the mean time, this Sensation 4G is okay.
Micalee said:
Flashed? All I did was run the program. It did whatever it did. I think the 3.33 was somehow left over from flashing a PG58IMG I'd gotten from here>http://forum.xda-developers.com/showthread.php?t=1459767#2. That failed as explained earlier in this thread. I figured that running the RUU would overwrite that failure, and I'm surprised it didn't. All I care is that I'm now getting OTA updates correctly. Yeah, I won't be trying to S-ON. I've thought about rerunning the RUU (3.32) again, but for now I'm going to just leave well enough alone.
I forgot to mention. This information was in the documentation for the RUU
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
One last note. I returned the HTC ONE, and have reactivated the Sensation 4g which this thread is about. The HTC ONE hardware is wonderful, but I didn't like all the HTC ONE software "features" you can't turn off. Maybe I'll jump ship and go with the Samsung Galaxy S4. In the mean time, this Sensation 4G is okay.
Click to expand...
Click to collapse
exactly the firmware 3.33 and the 1.27.1100 hboot version are from 3.33 universal firmware zip(from the thread you mentioned)
but as long as you are on S-OFF you can use any ruu.exe if you are also supercid
When the PG58IMG flash failed, I assumed at that time that it failed completely, and that no part of it actually worked. I'm too much of a noob to understand the pieces, or elements of the phone's software vs. firmware. I know the difference of course, but not as they relate to this phone, and certainly not as they relate to all the various flashes or other 'fixes' or other such mechanisms I see here on xda-developers.
If I get the nerve to attempt it, is there a way to get everything to a fully legitimate 'stock' situation? That is, just in case I upgrade to another phone again and want to sell this Sensation 4G? For example, I wonder what would be the result of a factory reset at this point? I realize it'll wipe everything out of course, but I wouldn't care.
Micalee said:
When the PG58IMG flash failed, I assumed at that time that it failed completely, and that no part of it actually worked. I'm too much of a noob to understand the pieces, or elements of the phone's software vs. firmware. I know the difference of course, but not as they relate to this phone, and certainly not as they relate to all the various flashes or other 'fixes' or other such mechanisms I see here on xda-developers.
If I get the nerve to attempt it, is there a way to get everything to a fully legitimate 'stock' situation? That is, just in case I upgrade to another phone again and want to sell this Sensation 4G? For example, I wonder what would be the result of a factory reset at this point? I realize it'll wipe everything out of course, but I wouldn't care.
Click to expand...
Click to collapse
A factory reset only deletes the data partition and cache, not any other partition. There are ROMs that are based on stock (and even stock). By fully legitimate 'stock' situation I believe you mean S-On and every thing stock. There are guies for that in the general and development forums.
I'm using CM10 and I've been wanting to update my S4 to a KitKat rom for some time and now that some stable builds are starting to come out I decided it was a good time.
On my first try flashing a new rom I got an error message asking for a newer version of hboot (mine is 1.14.0002 and it wanted 2.15.0000), so I looked around and found out I needed a RUU to update that, but since finding one for my phone is pretty difficult I decided to S-Off it, because apparently you can use any RUU that way.
Obviously it's not working, that's why I'm posting this. I did the htcdev method to unlock the phone back when I installed CM10 and to get S-Off I followed the rumrunner method. No problems whatsoever so far. They start appearing as soon as I try to update the 2.15.0000 RUU I downloaded from this other tutorial (the HTC Europe one, since I live here).
Following all the steps in that page I read about needing to change the phone's SuperCID to make it compatible with the RUU. First I tried with the default SCID that my phone had (VODAP304) with no luck. Then after a bit of searching I tried changing it to HTC__001 which seemed to be the correct one for the european RUU, but the same thing happened: it gives an incompatibility error, the process stops, the phone bootloops and I have to do a TWRP restore (the back up is from this morning and I made it just before attempting this, so no data loss of any kind)
These are the numbers bootloader gives me, if they're of any help:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-VODAP304
HBOOT-1.14.0002
RADIO-1.08es.50.02.21
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
What exactly am I missing here to update the hboot?
You don't need to install RUU, you need to flash a new firmware. Take a look at [URL="http://forum.xda-developers.com/showthread.php?t=2322755" ]this [/URL] thread.
Sent from my HTC One S
ka_55 said:
You don't need to install RUU, you need to flash a new firmware. Take a look at [URL="http://forum.xda-developers.com/showthread.php?t=2322755" ]this [/URL] thread.
Sent from my HTC One S
Click to expand...
Click to collapse
But isn't that for kernels? In several hours of research I haven't found one post about kernels for my issue
It does look similar to another method I've found recently that flashes the hboot through fastboot/recovery but users say it's much more risky
Rodrows said:
But isn't that for kernels? In several hours of research I haven't found one post about kernels for my issue
It does look similar to another method I've found recently that flashes the hboot through fastboot/recovery but users say it's much more risky
Click to expand...
Click to collapse
Yes it's about kernels and the problem with the new roms is nothing but the kernel. So firmware update is enough as a solution. I don't think it's dangerous if you follow the instructions correctly. But you should follow them word to word with your own risk
Sent from my HTC One S