Database Info

HTC Desire S hangs on carrier logo :-(

Dear forum,
I kind of hesitated to start a thread for my problem, but after a long time I still haven't found a solution. I have contacted HTC (no answer yet), but hope to resolve my problem in meanwhile instead of waiting 1 month+ for a replacement.
I got the -by now familiar- freeze, and after rebooting it would go beyond the HTC logo, then stay stuck in a backlit black screen mode. Tried removing the battery, sim card, sd card etc. Then decided to boot into recovery (vol down + power) which worked, but any option would freeze the phone, like factory reset which I tried first.
Right now, the phone already freezes at the carrier logo, and I can't even get into recovery again (vol down + power). The phone won't respond to the key presses, and eventially boot and freeze at the carrier logo. The weird thing is that before, after a lot of trying and re-inserting the battery, it would eventually boot and work just fine for about 1 in 10 tries.
Does anyone have any ideas what I could try? Any help would be greatly appreciated!
edit: Okay, after a while I finally managed to get into HBoot again! Now what should I do to get my phone resetted/fixed? I guess it's not possible for me to flash another ROM or something as i'm not rooted. Details shown are: S-OFF, HBOOT 98.0002

can you get into recovery from bootloader?

Seems like I now consistently can boot into HBOOT. When I choose recovery, it will reboot, show the carrier logo, show the green logo with circular arrows, and then switch to the phone logo with a red exclamation mark for two seconds. Then, it shuts off. Also, when I tried that just now, it buzzed for like 6 times very fast after turning off.
On the second try, exactly the same happened: red exclamation mark, screen off, +- 6 fast buzzes.
After doing that, it doesn't respond to vol down+power or power at all. After reinserting the battery, I can get back into HBOOT

edit: it didn't want to boot into HBOOT, but now it does again. Anyhow, chosing recovery is still green logo, red logo, screen off and some buzzes. The phone doesn't show up in "adb devices" neither.

Whatever you are going to do; do not root your device as it will void your warrenty.

Is there anything else i can try doing? The situation so far:
-normal boot just stays stuck into carrier logo
-hboot->recovery gives a reboot, green logo, switch to red logo, screen off and +- 6 fast buzzes, then nothing. Needs battery reinsertion to be able to respond to vol down + power again
-hboot->factory reset just freezes on the same screen, no response, needs battery removal
-noshow in adb devices (update: show in fastboot!)

Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely

maxxur said:
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
Click to expand...
Click to collapse
Slow down maxxur, wait for this quesstion to be out there for long enough for someone to answer it.
Dont go on a battery pulling spree, coz that is the first and most tempting response on a frozen phone. But i hope you know what that can do to this phone...
Give the xda community some time to figure this out. Hold your ground till then. Need to go in to the theatre now. Will get back in the evening and try to figure this out.

Try running the RUU while in the fastboot menu (usb mode). Also my suggestion is not to make the process more complicated by downgrading - just reflash 1.47...

Thanks for the response guys
The RUU I found was 1.37. Could you point me to a 1.47 RUU for the 3UK network?
Also, running that RUU when in Fastboot USB mode is what I tried. The info on the RUU shows that it hangs indefinitely at "rebooting bootloader". That is expected, as when I try to manually reboot bootloader in my fastboot menu, my phone will also freeze.
I'm wondering if running a different recovery image could be of any help? Last night I tried running CWM recovery to see my options, by entering "fastboot boot recovery.img" but i'd get a "remote: not allow" error.

Have not noticed that you are not rooted!
Why don't you try the revolutionary tool? If you have luck it will restore your bootloader if it is broken (keep in mind that is not the best option because it will break you warranty). Then you will just need to flash an eng hboot and run the RUU, or better try some custom ROM
But in my opinion the best option for you is to go for a replacement rather to try yourself, since you dont have any custom software on it it has to be covered by your warranty (probably it is a faulty device to go like this from nothing).

Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.

maxxur said:
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
Click to expand...
Click to collapse
Of course you can if you are eager to try this. When you run the RUU, even when there is no phone connected there is a folder in your C: drive created (I assume that you are using Windows). Open your Windows Explorer and search for the rom.zip. When you have it copy it somewhere and close the RUU screen. Then if you open the RUU all the *.img files are there. You can try flashing the stock recovery or hboot or whatewer using the fastboot command. But I have to say again the best option for you is to bring the phone for a repair before you end up with something irreversible and void your warranty.

Thanks for keeping me sane on what to do with my problem Mentally, I came to the point where I'd go flash CWM recovery on my phone and try to flash that RUU rom from there, but you helped me get around that thought and now I made arrangements for HTC to come and pick it up. I'll keep you guys posted!
PS: you've got to love our desire s community, it's the best.

Cheered too early
Now HTC suddenly responds that while entering my phone in their warranty service thingy and the phone seemed to be 3G UK branded, they told me they "can't" do repairs for those.

Seriously, HTC is trying to troll me saying the inner hardware could differ between a UK and a Belgian Desire S?? Could this be true in any way?? :/

Maybe some parts are cheaper but with the same parameters...but I thought that when you have a branded phone you should seek your warrancy support from the carrier's office?!?
Sent from my HTC Desire S

Options for solution!
Option 1: Copy rom.zip (from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed) to your sd rename it to PG88IMG.zip and let m boot into hboot.
If option 1 is not ok try option 2.
Option 2: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU then after that run ruu RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.
If option 2 not OK then there is option 3.
Option 3: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU after that run in dos/terminal fastboot flash zip rom.zip (extracted from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed)
Let me know if one of these option worked for you if not I can help you with reflashing your hboot again.

NikMel,
Thank you so much for the tips. Currently I'm trying the first HBOOT + .ZIP method. It detected it, asked me to update and is now showing a pink "Updating" sign. How long should this normally take? I have a strong feeling it simply froze again, and it really turns out to be a hardware problem.

Is that updating next to radio?
If yes it will take realy long so wait!!

[Q] Phone won't boot into recovery, please help

Hi. This is the first time I've tried to install custom rom's on my phone so bear with me. I followed a post (since I can't post links yet just google: CyanogenMod 9 (CM9) for HTC One X is Here. It's the first link) detailing how to install CM9 on the OneX. Everything worked up until step 16 where you have to boot into recovery mode. When I select recovery mode from the bootloader, the phone just tries to restart and gets stuck at the HTC loading screen with a message underneath saying that this ROM is not official etc.
Is there an easy way to try and fix this and make it work properly? I've tried erasing the fastboot cache and that didn't make a difference. At this point I don't really care if I have to erase everything and just go back to what I had before. The phone doesn't show up as a drive on the PC when I plug it in.
Any help would be great!
SOLUTION: Ok this is what I did to get it working again. My phone is on Rogers so I had to download this RUU and then follow these steps to flash the RUU onto the phone. Pretty simple actually.

Well, I can tell you that the ROM you were trying to flash was not for the S4 variant of the HTC One X, the ROM you saw was for the international Tegra 3 chip which is VERY different. I would attempt to flash an RUU from the At&T HOX thread if that is possible. Sorry if I can't be of any more help, that's all I've got.

I just had this exact same problem on mine. Well I didn't try to install a full rom, but accidently tried to apply the mod where you remove the menu bar and remap the keys that was for the HTC One X (Internation/Tegra3) to my HTC One X (AT&T) and what happened was it would freeze at the HTC One Beats Audio screen and not do anything. Tried going to Recovery as well and nothing. So I thought. What I had to do was unplug my phone from USB, hold down power for about 7 seconds until screen goes black, immediately after screen goes black, release power button and start to hold down volume down button, this should get you to the Recovery menu. From here what you will need to do is go into FlashBoot, and then from ur PC (or mac... hopefully PC though) you need to relock your BootLoader, and get stock recovery (if you changed it). After this reboot and then go back into Recovery, FastBoot, and connect to PC. Now download the AT&T RUU (i used the newest, 1.85) and run through those steps. After this is finished phone should boot fine and your expensive device is saved.
Oh by the way, I'm an evolving Noob. Just started to do anything ...interesting... with my phone today, crap went down, and using these steps I was able to fix it, so if I am off on some of my steps or unclear, just comment please and I'll try and correct myself or giver farther details on what I did.
-Good Luck

Thanks for the replies but I think my situation is further complicated by the fact that my phone is a Rogers phone. I know the RUU is 1.73.631.1 but I don't know if a stock recovery is available for Rogers yet. It sounds like all I have to do is find the correct RUU and flash it to the phone.
TrueLandon, you said after you held the power button down for 7 seconds you could put the phone into recovery mode. Would that be the same thing as the bootloader menu (where you can select fastboot, factory reset etc)?

achoj said:
Thanks for the replies but I think my situation is further complicated by the fact that my phone is a Rogers phone. I know the RUU is 1.73.631.1 but I don't know if a stock recovery is available for Rogers yet. It sounds like all I have to do is find the correct RUU and flash it to the phone.
TrueLandon, you said after you held the power button down for 7 seconds you could put the phone into recovery mode. Would that be the same thing as the bootloader menu (where you can select fastboot, factory reset etc)?
Click to expand...
Click to collapse
Yes, sorry if I were unclear, still trying to learn the lingo and technical terms , and yea, that's what you would need then is the RUU for Rogers, but I think the other steps should work for you.
I'll PM you a link to 1.73 RUU for Rogers

achoj said:
Hi. This is the first time I've tried to install custom rom's on my phone so bear with me. I followed a post (since I can't post links yet just google: CyanogenMod 9 (CM9) for HTC One X is Here. It's the first link) detailing how to install CM9 on the OneX. Everything worked up until step 16 where you have to boot into recovery mode. When I select recovery mode from the bootloader, the phone just tries to restart and gets stuck at the HTC loading screen with a message underneath saying that this ROM is not official etc.
Is there an easy way to try and fix this and make it work properly? I've tried erasing the fastboot cache and that didn't make a difference. At this point I don't really care if I have to erase everything and just go back to what I had before. The phone doesn't show up as a drive on the PC when I plug it in.
Any help would be great!
EDIT: Is it even possible to do a factory reset at this point?
Click to expand...
Click to collapse
The facepalm is significant and this makes me wish HTC forced carriers to label the S4 One X as the One XL.
If your bootloader was unlocked, lock the bootloader and run the RUU from fastboot.

Thanks for the replies guys. Truelandon sent me the RUU that I need for my phone but there's no .exe file in it. I was just wondering if I can somehow use these files and flash my phone with this RUU. Most of the files that I ended up downloading are disk image files.

Addition to the issue
I flashed a cm9 rom on my hox (international version). Its working fine but the only issue is that i want to install black and cyan theme to it and when i try to flash it and the moment i hit recovery in boot loader my phone restarts and comes back normal.so i can't enter cwm to flash the theme.

manmeets said:
I flashed a cm9 rom on my hox (international version). Its working fine but the only issue is that i want to install black and cyan theme to it and when i try to flash it and the moment i hit recovery in boot loader my phone restarts and comes back normal.so i can't enter cwm to flash the theme.
Click to expand...
Click to collapse
Wrong forum you have the international one x the is the one xl forum so we can't really help your phone has completely different partitions.
The only thing I would suggest is to reflash your cwm and see if it helps.
Sent from my HTC One XL using Forum Runner

[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.

[Q] S-off HTC One M7 with boot issue

Just as a quick intro, hello everyone. I'm new to the forum, but I've been reading from this site for a couple years now. Now that that's out of the way...to the real question.
So, my DNA committed suicide the other day and I received an HTC One M7 from a friend of mine who switched to apple. Yeah...he's stupid. But it's my gain. ANYHOW! It's a sprint HTC One m7 with the 1.57 hboot. I've come across an issue with trying to break this system open. Unlock went great along with TWRP recovery flash and superSU. No issues with any of that. HOWEVER! Somewhere down the line I believe my baseband and IMEI has been lost internally. I only come to this conclusion through research and finding a somewhat similar situation.
Currently, this is what's happening. I can enter bootloader and recovery just fine. The phone boots up just fine. But, once the phone is booted and I unlock the screen, all I get is a white screen with an HTC logo. Touch works, vibration works, it registers everything I do including the pull down (just to display header. it never actually pulls down), usb debugging icon, sounds, screenshot, PC recognizes device and everything. But it stays like this for about a minute or two and then restarts. It does this over and over.
I've been trying to s-off using rumrunner just to see if by chance it'd have success, but the phone won't recognize ADB. It will recognize fastboot commands perfectly, but not ADB. And yes...I use ADB commands in recovery I've tried every driver I could think of and every version of recovery and adb.exe I could find compatible. Because the computer won't recognize the phone in ADB, I can't get anywhere in rumrunner and because I can't access the main screen after unlocking the screen, I can't even use sunshine.
I'm at a total loss and I don't have any money for another phone. I really need some advice to get this fixed so I can flash a baseband and/or RUU and get this thing working with ViperONE. Please halp!
- Charles

You need to flash a stock ruu with fastboot and the imei will restore .
To see if the imei is still in the partition but the software doesn´t recognize it go in fastboot mode and type fastboot getvar all and the imei should be there.

Please Help !. HTC One Mini stuck in BOOTLOADER Menu

My HTC One mini swtiched off a couple of days ago and since then only load to bootloader menu no matter what I click or do. It goes also automatically to this screen as soon as I plug it with the charger even if did not press the on/off key.
I tried to unlock the bootloader according to the instructions on HTCDev.com site. Everythings work till the last step, as no menu appear on my phone asking me if I want to unlock the bootloader or not.
I also tried to use RUU to install a new Firmware. The phone showes a black screen for a couple of seconds and then restart again to bootloader screen. I got an error afterwards.
The phone was running on a stock firmware, no root, no custom recovery, or any other thing.
Can anyone help me to solve this problem. It seems my phone has no OS or something like that.
PLEASE HELP

Hi guys n gals
it appears ive inadvertantly deleted my rom i successfully unlocked bootloader installed recovery but over killed me wiping. Sso ive got an unlocked bootloader, have access to fasboot and recovery but fone is stuck at bootlader screen. How do I flash a rom now? as when hooked to a pc its no longer recognised. any help much appreciated!!!

moh19814 said:
My HTC One mini swtiched off a couple of days ago and since then only load to bootloader menu no matter what I click or do. It goes also automatically to this screen as soon as I plug it with the charger even if did not press the on/off key.
I tried to unlock the bootloader according to the instructions on HTCDev.com site. Everythings work till the last step, as no menu appear on my phone asking me if I want to unlock the bootloader or not.
I also tried to use RUU to install a new Firmware. The phone showes a black screen for a couple of seconds and then restart again to bootloader screen. I got an error afterwards.
The phone was running on a stock firmware, no root, no custom recovery, or any other thing.
Can anyone help me to solve this problem. It seems my phone has no OS or something like that.
PLEASE HELP
Click to expand...
Click to collapse
I seem to be in the same situations... although I got to it in a different way. Where did you download the RUU from? is it version-main: 4.14.401.2 or higher?
Try: rootwiki dot net and search for htc one mini bootlocker unlock....this helped me to UNLOCK and put TWRP recovery on it... maybe it gets you a step closer.