Database Info

HELP! Desire S won't boot!

My friend asked me to have a go at fixing his Desire S...
I'm in Australia, it's a Telstra branded HTC Desire S.
The details of the phone are (from bootloader screen):
SAGA PVT SHIP S-ON RL
HBOOT - 0.98.0002
RADIO - 3805.04.02.01_M
eMMC - boot
What happens is I turn the phone on, and it gets stuck at the Telstra splashscreen. It stays on this screen until the battery goes flat.
I've tried accessing the phone through adb, but adb can't find the phone. I think this is because USB debugging is not enabled, but I can't get the phone to turn on to enable it
I've also downloaded this RUU:
RUU_Saga_Telstra_WWE_1.36.841.3_Radio_20.28d.30.0805U_3805.04.02.01_M_release_184558_signed
When I run the RUU, it is unable to connect to the phone (even though the phone is connected to the computer, and I can see the phone in the device manager).
Any suggestions are welcome

Do you have any idea what caused this?
Looks like you may still be stock?
which means you're at least covered by warranty
Swyped from my Desire S using XDA Premium

@themalenurse
FIRST try a factory reset. Boot into hboot, go to recovery, once in recovery go vol up + power to get the menu then try wipe cache partition if that fails(doesn't help) then do a factory reset.
As for the RUU route...
Boot your phone into fastboot *get into hboot, then press the power button after 30s) and then run the RUU again from the PC.
If that fails....... Extract the rom.zip from the RUU, rename it to PG88IMG.zip, place on SDcard root, then boot your phone into hboot and follow the screen.

@ben_pyett:
I don't know what caused this.
I'd say that it's highly likely that the phone is still stock, however, my friend bought the phone privately over the internet, so couldn't be 100% certain. Due to this, the phone is no longer under warranty, because my friend doesn't know where the phone was purchased originally.
@foX2delta:
I tried to do the wipe cache partition and the factory reset, and I could get neither of them to work.
I also tried the RUU route, and the RUU program still didn't connect to the phone.
So I'm at the final step that you suggested, but I don't know what you mean by extracting the ROM.zip from the RUU, as the RUU is an exe. Can you please explain that?
Also, once I am able to do that, how do I place the the PG88IMG.zip onto the SDcard root? I ask this because my computer doesn't recognise the phone as a removable disk.

So, to clarify, I should rename RUU_Saga_Telstra_WWE_1.36.841.3_Radio_20.28d.30.0805U_3805.04.02.01_M_release_184558_signed.zip to PG88IMG.zip?
Then I put PG88IMG.zip on the SD card and then boot the phone into hboot?
If I am incorrect, please provide clear instructions
I'm new to doing this stuff on the Desire S, my own phone is a Samsung Galaxy S (which I find much easier to do things with).

I've successfully extracted ROM.zip from the RUU and have renamed it to PG88IMG.zip.
I've put the PG88IMG.zip on a SD card, and loaded into hboot on the Desire S.
The phone goes through it's checking, and I press the volume up key to start the update.
The phone then freezes (See attached pic)...
How long should the update process take?
If the phone is frozen, any suggestions/options?

A good place to start is ensuring you have the appropriate drivers installed on your system. Do you have HTC Sync? Or the Android SDK? We'll take it from there ...

@Saipro:
I have installed the drivers that are linked to from this page:
unrevoked[dot]com/rootwiki/doku.php/public/revolutionary
Sorry I had to put the link like that because I'm not yet allowed to put links in my posts.

themalenurse said:
If the phone is frozen, any suggestions/options?
Click to expand...
Click to collapse
Are you sure you pressed VolUp?
As I remember, it must be something like "Updating in progress, please wait".
Sry for my bad English

[Q] Cannot Flash Back To Stock, Boot, or Mount

First of all I apologize if this has been covered, I have been trying to find a solution for 3 days straight. I have a Rogers Wireless HTC One X I managed to unlock bootloader and root as well as having access to TWRP 2.1.8. recovery.
My problem is when I tried to apply the 3 dot removal mod my phone suddenly would not boot past the first screen, and a message would appear for developers use do not distribute but just stay on that screen. I have tried numerous things to no avail. I can boot in recovery and mount sd card from there (but have not found a successful way to restore from within recovery mode) otherwise in fastboot etc. the computer does mount the phone at all. it will not mount as a device properly so I cannot run the RUU and flash to stock.
So I am left with a unmountable and unbootable phone (brick) and have no other ideas on how to fix it if possible. BTW the device does show in device mgr and the computer gives the connect and disconnect alert, but it will not mount. Also, I have read the bootloader has to be relocked to flash back to stock if I relock the phone I cannot access recovery therefore an endless nightmare. Also, within TWRP recovery I try to reboot and it gives an error saying no Android OS found, install a rom or restore from backup (which I have neither) so I have to hold the power and dwn volume button to reboot each time to switch from recovery to fastboot. I think its toast.
Thank you in advance for any responses, I have been up almost 36 hours straight trying to figure this out and the phone is not even a week old. :crying:

There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.

Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.

gunnyman said:
There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.
Click to expand...
Click to collapse
Thank you very much I will look into that today. Fingers crossed!

i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.

stnguyen09 said:
Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.
Click to expand...
Click to collapse
Yes, thank you I have HTC Sync installed and it does not recognize the phone when it is connected either. I will keep searching. Thanks.

ethantarheels123 said:
i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.
Click to expand...
Click to collapse
Yes, I have tried relocking bootloader, it did not help with the phone being recognized by the computer also when I oem lock I cannot access recovery and such. I will have some more time to poke around with it, I have downloaded the RUU utility although it sends back error with device not found. Thanks for your reply, I will keep at it I know the phone can not be bricked, well I am hoping not!

[Q] I'm in lockdown and can't get out.

I bought a HTC One S for T-Mobile USA. Has been working flawlessly. Today I got an OTA and my world is now upside down. I have spent 5 hours trying countless things to get my phone back up to no avail.
my phone stats:
hboot 1.09.0000
radio 0.16.31501s.16_2
open dsp-v28.1.0.32.0504
emmc-boot apr 2 2012,21:08:24
UNLOCKED
TAMPERED
How do I get back to square one and turn this phone back into something usable?
It has something called TWRP 2.1.7 installed on it and I have tried fastboot and a host of other things to remove it. I have even tried the thread on sending your phone back to stock but I can't access RUU because it won't load the driver. I have never rooted this phone nor do I believe USB Debugging was turned on before I accepted the OTA. I can communicate via fastboot in the command shell via a usb cable. The PC wont mound the SD card so I can't copy a new image and reboot this thing on a different rom and then send it back to stock.
I am about ready to throw it away because i can't seem to get a .zip file to it so it will run again (for putting a working build on it). There are no images to boot to. Somehow that got wiped and no backup was done. I don't give a poop if the data is whiped. Its all backed up via dropbox and exchange. I just want it up and running so i can use RUU and send it back to stock.
Any help would be appreciated.

Scuba_Luv said:
I bought a HTC One S for T-Mobile USA. Has been working flawlessly. Today I got an OTA and my world is now upside down. I have spent 5 hours trying countless things to get my phone back up to no avail.
my phone stats:
hboot 1.09.0000
radio 0.16.31501s.16_2
open dsp-v28.1.0.32.0504
emmc-boot apr 2 2012,21:08:24
UNLOCKED
TAMPERED
How do I get back to square one and turn this phone back into something usable?
It has something called TWRP 2.1.7 installed on it and I have tried fastboot and a host of other things to remove it. I have even tried the thread on sending your phone back to stock but I can't access RUU because it won't load the driver. I have never rooted this phone nor do I believe USB Debugging was turned on before I accepted the OTA. I can communicate via fastboot in the command shell via a usb cable. The PC wont mound the SD card so I can't copy a new image and reboot this thing on a different rom and then send it back to stock.
I am about ready to throw it away because i can't seem to get a .zip file to it so it will run again (for putting a working build on it). There are no images to boot to. Somehow that got wiped and no backup was done. I don't give a poop if the data is whiped. Its all backed up via dropbox and exchange. I just want it up and running so i can use RUU and send it back to stock.
Any help would be appreciated.
Click to expand...
Click to collapse
I hate to tell you this but if you never unlocked or rooted your phone, somebody did. Your device is unlocked and running a custom recovery therefore you cannot accept over the air updates and that is your problem. You did not buy your phone that way from T-Mobile so what did you really do to get to this point?

Behold_this said:
I hate to tell you this but if you never unlocked and rooted your phone, somebody did. Your device is unlocked and running a custom recovery therefore you cannot accept over the air updates and that is your problem. You did not buy your phone that way from T-Mobile so what did you really do to get to this point?
Click to expand...
Click to collapse
I never said I bought it as OEM. I also never thought to ask the guy I got it from if he rooted it or unlocked it.

Relocking the boot loader then running an RUU should fix the issue. Once you do that enter the recovery and wipe everything/factory reset.
Then if you are trying to run a custom ROM you should be able to mount your SD card and push one to the phone.
Sent from my HTC One S using xda premium

beats4x said:
Relocking the boot loader then running an RUU should fix the issue. Once you do that enter the recovery and wipe everything/factory reset.
Then if you are trying to run a custom ROM you should be able to mount your SD card and push one to the phone.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Great reply however I am short on knowledge on how to do what you have recommended. I don't know how to relock the boot loader nor can I run RUU because I can't get the driver installed. Any help would be awesome. Thank in advance. Sorry I'm a noob at this.

In the dev section there is an all in one toolkit that will execute the correct scripts for you. Download it, then run it. You may also need the HTC sync drivers installed on your computer.
Once you see that the bootloader is locked run the ruu.
And don't apologize for being a noob, I am too lol. We all need help to get started.
Sent from my HTC One S using xda premium

If you install HTC sync to your pc it should install the driver's you need. Then install the one s tool kit in developers section to relock. Then run ruu.

Also, anything you see in blue text is what you'll need to type, or copy/paste, to avoid any quote confusion.
Files You Need:
T-Mobile USA RUU file (mirror) - it's about 563 mb, and worth saving once you download it.
Extremely Important: If you're on another carrier you'll need a different RUU file - DO NOT try and run this RUU file, it could really screw you up. Go to this link to find the right RUU file.
HTC Drivers (mirror) - You probably already have the drivers installed if you're needing this thread, but just in case...
ADB / Fastboot (mirror) - same as the drivers, but again, just in case...
Initial Setup:
Again, some of this might be redundant as you might already have this setup if you rooted/unlocked.
Install the HTC drivers if you haven't already
Unzip the adbfastboot.zip file to your desktop (anywhere, but I find it easiest to get to it on the desktop for my habits)
Getting into the bootloader (hboot):
If you're stuck in a boot loop, pull the batt... oh wait, we can't do that here. To perform a hard reset, hold down the power button for 10 seconds - in the process you'll see the softkeys start blinking, then it should reset. As soon as it starts to reset, release power, and hold down the volume-down button - hold it until hboot pops up (white screen, colored text).
If you're phone is fully powered off (make sure "fastboot" is disabled - settings > power), hold the volume-down key and while holding it, press and hold power for a few seconds. You can probably release the power button, just make sure you keep holding volume-down - after probably 3-5 seconds (maybe a bit more), hboot should come up.
If the phone is on and you're plugged in to your computer, make sure "usb debugging is enabled" (settings > developer options), shift+right-click the adbfastboot directory on your desktop (or wherever you put it), choose "open command window here", and in the prompt that comes up, input adb reboot bootloader.
Restoring:
Once you're in hboot, make sure you select Fastboot (if you don't see it, you're in Fastboot already). In the command prompt referenced above, input fastboot oem lock. This will relock your bootloader in order to allow the RUU to run. Historically this has been necessary for an RUU to run, but I haven't actually tested it without relocking on the One S, and assumed based on previous HTC devices that this would continue to be the case. Edit: thanks rbrookstx for confirming that re-locking is necessary
Your phone will reboot when it relocks - follow the steps above to get back into hboot.
Once you're back in hboot, make sure you're in Fastboot, and open / run the RUU file. It'll go through some initial prompts, then it should start. It takes about 10-15 minutes, maybe less, depending on your computer.
Once it's done, it'll simply go back into hboot - reboot, and you're good to go.
A couple of notes:
When you unlocked and flashed a custom recovery (if you did that), hboot probably said "tampered with" and when it booted up, it probably had a red message under the "HTC" logo about being a developer only device. That should be gone now. It should boot up clean, and hboot should simply say "relocked", with no tampered message.
Until a better solution comes out, once you unlock the bootloader with HTC's official method, it can never be locked the way it was from the factory. "Relocked" is the best you can do.
Click to expand...
Click to collapse
This is what worked. I had to search the internet for this stuff but the HTC driver, the fast boot and the RUU with a matching or higher radio number all made it work out.

HTC Desire Z stuck at htc screen

I just bought this phone used and the seller said it was stuck on htc screen.
If i power it on it stays on the htc screen. But if i press the vol down button and then power it on i come to a menu:
Vision PVT Ship - S-on
HBOOT 0.85 ....it says some more stuff but i dont think all of it is needed you guys are pros so you understand.
Then i get the options :
FastBoot
Recovery
Factory Reset
Simlock
Image CRC
OK so i want to get the phone working by installing a custom rom on it or by getting it back to factory specs. I have very little idea about this stuff but if you guys tell me what to do i can try to pull it off.
Please give some suggestions

First download HTC Sync that has all the drivers that you need included.
Then browse for the desire z RUU ( its originally firmware ) and download it.
After downloading connect it to the computer with usb and let it at bootloader option ( maybe its fastboot to but its a long time ago i done so on my EVO )
Then run the RUU as adminstrator follow the steps and you will se the ruu will flash it.
Voila it should reboot and you will have a working phone
ATTENTION: Be sure to download the RUU thats for your device because there are more of them!
For more help pm me i will help you more if you run into trouble
Sent from my HTC EVO 3D X515m using Tapatalk 2

just get the custom ROm from the internet and copy that file into sd card and dnt forgot that you should not make any folder , just paste in root folder of sd card
then turn on the phone in this hboot mode and it will automatically find the image and boot it

htc one x at&t boot loop

Hi everyone, i got an issue with my cel phone, i update it with the RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34 and after that my phone starts in a boot loop , the AT&T logo appears but then restarts again ,and again ,etc.-
I tried to conect it to the Pc so i can put another RUU Rom ,but computer cant install the drivers so is not recognize .-
The phone is not unlock
Please i dont know what to do , i tried a lot of thing like fastboot rebot,recovery,etc but nothing seems to work , if anyone can help me i will be gratefull
thanks

try a factory reset from recovery hold the power button and volume down till the lights at the bottom start blinking when the phone shuts off keep holding the volume button and let go of the power button this should get you into bootloader then select recovery from there

So the phone is stock (not rooted, never bootloader unlocked)?
If the drivers aren't correctly installed, the RUU is never going to run. I think that is the main problem. Find the latest drivers (HTC Sync), reboot the computer, make sure you have admin rights, etc. Also try a different USB port, or try another computer, if possible.

redpoint73 said:
So the phone is stock (not rooted, never bootloader unlocked)?
If the drivers aren't correctly installed, the RUU is never going to run. I think that is the main problem. Find the latest drivers (HTC Sync), reboot the computer, make sure you have admin rights, etc. Also try a different USB port, or try another computer, if possible.
Click to expand...
Click to collapse
Yes you are right , te phone is stock , also y tried reseting the recovery and nothing happend, the problem is what you said i think , i will try with the laptop and tell you what happend

gomussi said:
also y tried reseting the recovery and nothing happend
Click to expand...
Click to collapse
RUU doesn't care about recovery, it re-installs stock recovery automatically.

Well i made what you told me , first i tried to put the same RUU and it flashed it but issue remains , so i tried to put an older RUU ( downgrade it ) process starts but suddenly stopt with 140 error : bootloader version error .-
I don´t know wich version i can istall if process show me that error .-Or which RUU version can put on it
my cel phone
EVITA PVT SHIP´S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
oPEN dsp-V34.1.0.45.1219
Emmc-boot

You can't use a previous RUU if the hboot is older. So that error is normal and expected.
You will need to run the 3.18 RUU. Try to download it again. Might just be a bad download.

redpoint73 said:
You can't use a previous RUU if the hboot is older. So that error is normal and expected.
You will need to run the 3.18 RUU. Try to download it again. Might just be a bad download.
Click to expand...
Click to collapse
i already download from htc site and the same happend

Well i finally solve the problem ,after updating with the same RUU many times ,what i do ( don´t know how it works) i flash recovery, when the screen show the red triangle with the exclamation sign , i push power button for about 10 sec ,and the cel phone restarts ok.-
Now i want to know what can ido with this RUU,im afraid if i restar the cel againg the same thing is going to happend .-
I tried to rooted but no succes
I got a doubt what should i do first ?? unlock bootloder or root the phone first ??
thanks

First thing you need to do is read the stickies in this q&a section. Then read stickies in android development section. Then if you have questions, ask. If you just ran the 3.18 ruu though, you're sol, no root/bootloader unlocking possible.
Sent from my HTC One X using xda app-developers app

gomussi said:
I got a doubt what should i do first ?? unlock bootloder or root the phone first ??
Click to expand...
Click to collapse
Its not clear from your posts whether the phone was actually updated to 3.18 firmware or not. But the hboot has at least been updated to 2.14.
If the phone is on 3.18 firmware, you can't unlock the bootloader and you can't root.

Well thanks for all the answers , but sorry to say, i continue with the loops anda suddenly the phone starst fine, but when in rebbot it for some reason keep on with the loop issue.-
Instead of that i notice a strange thing happend , as i told , got wifi problems on this model , but as shown in the picture above , i pull out the micro sim,so no mobile data, data conection or network operator set and im connect to my wifi network , thats is strange ,if i put the sim ,the cel phone automatically set the network operator ,and if i set the APN , wifi signal desapears and beggin the known issue for this model on wifi signal and connections .-
Any idea of wath can be ??
Thanks

if you can get your phone to boot and stay booted for atleast 30 minutes. could you install and run this app. eMMC Brickbug Check it will check if the phones memory is good. i havent heard of any bad emmc on evita but maybe you have one, since you seem to be having a similar problem to what i had on an htc ace. also you could reboot into stock recovery and do a factory reset or clear cache, see if you get any errors i got emmc errors on my ace before the partitions finally decided to crap out. you could go through the unbrick thread to repair partitions before the die completely, my theory was doing a similar thing to this ace to repair it.

big problem
I just unlocked my bootloader and rooted my phone, everything went fine. i then tried to flash a custom ROM. Thats where it went really bad. It went into a bootloop. I was able to get it back to bootloader mode and then recovery, so i tried to flash the ROM again, same result. I now have no way to transfer a new ROM over to my SD card and attempts to flash this ROM i downloaded through fastboot have all failed. I dont know what to do at this point, please help.

You haven't given enough information. What are your bootloader details? What recovery and version are you using? Which ROM did you flash? Did you do a factory reset from bootloader?
Sent from my Evita

brickwallwb17 said:
I just unlocked my bootloader and rooted my phone, everything went fine. i then tried to flash a custom ROM. Thats where it went really bad. It went into a bootloop. I was able to get it back to bootloader mode and then recovery, so i tried to flash the ROM again, same result. I now have no way to transfer a new ROM over to my SD card and attempts to flash this ROM i downloaded through fastboot have all failed. I dont know what to do at this point, please help.
Click to expand...
Click to collapse
If s-on, do you realize that you need to flash boot.img seperately using fastboot (for any hboot 1.14 or higher)? This is the most common reason for bootloops when flashing a ROM on this device.