Related
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 ^^^^
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.
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
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.
So I did a short search for the answer to this but seems like I cant quit find the answer or it just confusing me and im getting lost. I have an HTC Sensation T-Mobile From the USA model PG58100. This phone is I assume in a bootloop as when it turns on it just stays on the HTC screen. I put it in recovery mode and tried doing just the factory reset but the phone still loops after ward. So i know assume i have to reinstall the stock rom. this phone is not and has never been rooted to my knowledge as I did not receive this new so I am not 100% sure. here is what is displayed when i go into recovery mode
*** LOCKED***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
I have downloaded Elegencia Sence 4.1 V8.0.0 zip but I will install whatever you guys feel is best for me. I just need the phone back up and running. it does not need to be rooted or have anything special completely stock would be fine. The simplest way to get it working again is all I need. Thank you in advance.
Try here:
http://forum.xda-developers.com/showthread.php?t=2094380
There you have a bunch of RUUs try with some of TMOUS but choose some newer one.