Database Info

Desire S Won't Boot

Yesterday my fiancée performed some updates from the market. Shortly after her phone turned off.
Now when trying to turn it on the phone gets stuck on the white screen with the green HTC logo.
I have tried booting it in to fast mode by turning it on with the volume down button held and then selecting fastboot.
This allowed me to try and flash the O2 ROM back to the phone. It find the software version on the phone (which is slightly newer than the ROM I have downloaded).
The next stage is "Rebooting in to bootloader" this is where it just comes to a stop, the fastboot menu freezes and the phone doesn't do anything.
Does anyone have any ideas? Much appreciated.

Is ur phone rooted or stock? U could try a factory reset...
Sent from my HTC Desire S using XDA Premium App

It's totally stock other than being unlocked.
If I try a Factory Reset from the HBOOT screen it just locks up. Is there another way?
If I try recovery it turns off, comes up with Green arrows in a circle, vibrates 5 or 6 thimes, then does nothing.

Hope your phone will comes up,try to flash ruu
Sent from my HTC Hero using XDA Premium App

zhaominghao said:
Hope your phone will comes up,try to flash ruu
Sent from my HTC Hero using XDA Premium App
Click to expand...
Click to collapse
I've tried to flash the RUU already haven't I? By downloading the O2 ROM.

richard_ha said:
It's totally stock other than being unlocked.
Click to expand...
Click to collapse
When you say unlocked, I'm assuming that you mean network unlocked and not S-OFF (via XTC clip)?
I'm afraid that I'd be tempted to return the device from where you bought it and attempt to get a repair/replacement unit.
Sorry that I was unable to help anymore.

ben_pyett said:
When you say unlocked, I'm assuming that you mean network unlocked and not S-OFF (via XTC clip)?
I'm afraid that I'd be tempted to return the device from where you bought it and attempt to get a repair/replacement unit.
Sorry that I was unable to help anymore.
Click to expand...
Click to collapse
Hi yes, network unlocked and not S-OFF
It seems to be like the bootloader has become corrupt some how.
I'll start making arrangments with HTC, thank you.
If anyone else has any ideas or suggestions let me know.

[Q] Phone Locked :s Help?

So I bricked my phone...
I have searched around the other threads with bricked devices but none of them had that worked for me. I am rooted and unlocked so I cant flash a RUU.
I can get into bootloader, it says fastboot but when I try fastboot oem Lock or any other command it says waiting for device and doesnt seem to do anything. (I can see the bootloader screen and the red FASTBOOT sign on my phone)
I can get into my recovery (TWRP V.2.1.8.1) but my SD seems to have disappeared, it wont mount to phone and I can not see it on file manager. Which means no backups or ROMS to reinstall. It also will not mount to my PC in recovery.
Since fastboot isnt working I cant flash new boot recovery or relock bootloader. I can completely stuck
If there is a way with adb (never used it so would need more detailed instructions).
If i try boot into ROM it just shows splash then loops.

Hadcook said:
So I bricked my phone...
I have searched around the other threads with bricked devices but none of them had that worked for me. I am rooted and unlocked so I cant flash a RUU.
I can get into bootloader, it says fastboot but when I try fastboot oem Lock or any other command it says waiting for device and doesnt seem to do anything. (I can see the bootloader screen and the red FASTBOOT sign on my phone)
I can get into my recovery (TWRP V.2.1.8.1) but my SD seems to have disappeared, it wont mount to phone and I can not see it on file manager. Which means no backups or ROMS to reinstall. It also will not mount to my PC in recovery.
Since fastboot isnt working I cant flash new boot recovery or relock bootloader. I can completely stuck
If there is a way with adb (never used it so would need more detailed instructions).
If i try boot into ROM it just shows splash then loops.
Click to expand...
Click to collapse
assuming you're using Windows. Is HTC sync running? If so kill it.
If you can get to boatloader, you should be able to see the phone in windows. It's kind of a failsafe.

gunnyman said:
assuming you're using Windows. Is HTC sync running? If so kill it.
If you can get to boatloader, you should be able to see the phone in windows. It's kind of a failsafe.
Click to expand...
Click to collapse
Your a genius...
I never shut HTC sync as soon as I did that I could OEM lock and now I am running the RUU.
Thanks for the quick reply and help.

Hadcook said:
Your a genius...
I never shut HTC sync as soon as I did that I could OEM lock and now I am running the RUU.
Thanks for the quick reply and help.
Click to expand...
Click to collapse
No problemmo.
You're only bricked (as far as I know) if you can't get to the bootloader.

gunnyman said:
No problemmo.
You're only bricked (as far as I know) if you can't get to the bootloader.
Click to expand...
Click to collapse
My other one x doesn't boot. Just stays in QHSUSB :banghead: I have warranty on the way for it. Still trying to figure out how to get boot back on it
Sent from my HTC One X using xda premium

dkirchik said:
My other one x doesn't boot. Just stays in QHSUSB :banghead: I have warranty on the way for it. Still trying to figure out how to get boot back on it
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
how did it get in QHSUSB? Is what someone said about pwr/vol UP true?

dkirchik said:
My other one x doesn't boot. Just stays in QHSUSB :banghead: I have warranty on the way for it. Still trying to figure out how to get boot back on it
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Have you tried oem refurb in fastboot. I think that's the command.
Sent from my HTC One X using xda premium

kleeman7 said:
Have you tried oem refurb in fastboot. I think that's the command.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I can't boot into fastboot.
Sent from my HTC One X using xda premium

You shouldn't need to, there was a post in s-off saying it could be ran from dload mode. From what I read.
beaups said:
I tried the pg1fs. sig check failure. As a matter of fact doing "fastboot flash aksldjflkadsfjdlsk pg1fs.img" causes the same error, so something is in the img that causes sig check or any flash attempt except recovery is sig checked. Fastbook oem refurbish puts out a lot of interesting text, then reboots into recovery and looks for something (doesn't say what).on sd card (I tried copying IMG's to internal and external sd, no luck). Interesting thing about refurb command is it seems particularly "excited" about the fact that we have super CID - run it yourself and see, no harm is done (data, etc.). one recovery boots you can screw around with volume and power keys to see the text.
Click to expand...
Click to collapse
Sent from my HTC One X using xda premium
Sent from my HTC One X using xda premium

Phone is officially dead.
RUU'ed and it completed install without problems but phone still boot loops

Which RUU did you run? Did you try running it again? Can you still boot into the bootloader? If so what does it say at the top?
Sent from my HTC One X using xda app-developers app

I relocked boot loader and ran the AT&T 1.85 ruu
Basically I now have the phone booting up, but when sense loads I can do very little on it, like text or call. As soon as I try do something more like browse the web the phone freezes and reboots. The back get warm and won't turn on immediately. I want to say the second core is shorting which is why as soon as it clicks in it freezes. Or at least what my limited knowledge would suggest.
Guessing I'm done and will be using dumb phone for 6 months

The phone has a 1 year warranty call customer service and get a new one.

Doesn't the fact that I used htc dev unlock void that warranty? And I never got my phone from AT&T so they won't help obviously.
I thought that was the whole reason some people didn't want to use htc dev unlock because it voids that warranty and they won't help because the phone was rooted and boot loader unlocked? Has anyone tried to get a replacement from htc after unlocking?

You might void it says. Hardware defects are covered. AT&T covers the phone for 1 year regardless of where you bought it. Call them.

Hadcook said:
Phone is officially dead.
RUU'ed and it completed install without problems but phone still boot loops
Click to expand...
Click to collapse
reinstall STOCK recovery (unlock BL again first if needed)
relock BL if you unlocked in step 1
factory reset
RUU
profit.

beaups said:
reinstall STOCK recovery (unlock BL again first if needed)
relock BL if you unlocked in step 1
factory reset
RUU
profit.
Click to expand...
Click to collapse
Woooooaaahhhh stock recovery? Doesn't the ruu do that? If not where could I find the stock recovery?
I thought once you have ruu you can factory reset...

gunnyman said:
You might void it says. Hardware defects are covered. AT&T covers the phone for 1 year regardless of where you bought it. Call them.
Click to expand...
Click to collapse
I doubt AT&T would help, I bought the phone out of contract from best buy they would be getting screwed. I'll try contact htc after 4th of July

They will help. They take care of phone warranty for you. You still pay for service . This warranty is part of why you pay them.

"Tampered" on HTC one x?

Hey guys. New on the forum and unfortunately a noob. I saw recently 2.20 was open to be rooted for this phone. The instructions are hard enough to follow, let alone on a macbook pro. I got as far as getting the token from htcdev.com. couldn't get any further. I decided to give up as the topic is still fresh and there isn't much Mac love regarding the new root method. So now since I got that far I am still on the stock ROM but now my phone has the "tampered" logo on the boot loader screen. Is there a way I can rid this of the phone? I don't care about rooting or unlock anymore. Just want to get rid of it because the phone is still new and I still want the warranty. Thanks a bunch guys for the help.
Sent from my Nexus 7 using xda app-developers app

RUU.

Even running a RUU it'll still say tampered I think.. the whole hboot thing isn't reversible till s-off..
For example, if you unlock your bootloader, and take any measure what so ever your hboot will even say re-locked
Sent from my One X using Tapatalk 2

InflatedTitan said:
Even running a RUU it'll still say tampered I think.. the whole hboot thing isn't reversible till s-off..
For example, if you unlock your bootloader, and take any measure what so ever your hboot will even say re-locked
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Tampered will go away after an ruu. It will always say relocked until s-off
Sent from my One X using xda app-developers app

[Q] Bricked Phone Help Please

I recently got the One X because I became to impatient for the One X+.
After flashing cm10 on it I decided to try and flash back to stock to see if i could return it to ATT because i was within 14 days.
I accidentally bricked my phone by deleting my system from the recovery and now I cant boot into recovery.
It turns on but goes as far as the "HTC quietly brilliant 'this build is for development purposes...'" screen and stops.
I can turn the phone off and on but it gets stuck at this screen.
I've tried button combos to get into recovery and I've tried adb and the one x tool kit.
I've also tried the recovery from the RUU OTA update but no dice.
Any way to fix this?

Ectosock said:
I recently got the One X because I became to impatient for the One X+.
After flashing cm10 on it I decided to try and flash back to stock to see if i could return it to ATT because i was within 14 days.
I accidentally bricked my phone by deleting my system from the recovery and now I cant boot into recovery.
It turns on but goes as far as the "HTC quietly brilliant 'this build is for development purposes...'" screen and stops.
I can turn the phone off and on but it gets stuck at this screen.
I've tried button combos to get into recovery and I've tried adb and the one x tool kit.
I've also tried the recovery from the RUU OTA update but no dice.
Any way to fix this?
Click to expand...
Click to collapse
Which ruu were you using?
Did you relock your boot loader before running ruu?
Sent from my One X using xda app-developers app

Myrder said:
Which ruu were you using?
Did you relock your boot loader before running ruu?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I used "htc_one_x_RUU_2.20.502.7_att_us_08022012" to revert back to stock because i was originally on 2.20.
I did not relock my boot loader before running RUU.

Ectosock said:
I used "htc_one_x_RUU_2.20.502.7_att_us_08022012" to revert back to stock because i was originally on 2.20.
I did not relock my boot loader before running RUU.
Click to expand...
Click to collapse
There is your problem.
Fastboot oem lock
Type that into your fastboot cmd window to ruu
Sent from my One X using xda app-developers app

Myrder said:
There is your problem.
Fastboot oem lock
Type that into your fastboot cmd window to ruu
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
still no dice
error: device not found or < waiting for device >
One thing though is the phone shows up in my device manager as Android but is an unknown and does not have the drivers.
I have the usb drivers, and android SDK installed so I dont know what drivers it is missing.

Okay I can get into the bootloader but im still getting no ADB connection
[EDIT]
from the bootloader i went into fastboot USB and relocked the bootloader
RUU is running!

Ectosock said:
Okay I can get into the bootloader but im still getting no ADB connection
[EDIT]
from the bootloader i went into fastboot USB and relocked the bootloader
RUU is running!
Click to expand...
Click to collapse
Glad you're back up and running.

I wonder if att will even take back his phone because of the relocked status, why do you want the one x + so much? You just said you couldn't wait so you tampered with it and changed your mind, but I mean the one x + is only a second faster.. you can just overclock HTC one x anyways. But I'm glad you phone is back.

Keep the Xl.
WR
Sent from my HTC One X

WhatTheAndroid? said:
I wonder if att will even take back his phone because of the relocked status, why do you want the one x + so much? You just said you couldn't wait so you tampered with it and changed your mind, but I mean the one x + is only a second faster.. you can just overclock HTC one x anyways. But I'm glad you phone is back.
Click to expand...
Click to collapse
WarRaven said:
Keep the Xl.
WR
Sent from my HTC One X
Click to expand...
Click to collapse
64gb plus better battery is enough for me to switch.
Also can the store employees actually tell if it was bootloader tampered? The last time I traded in my stock flashed Samsung Captivate for return all they did was a factory reset and took it back.

Though, better battery life is questionable.
WR
Sent from my HTC One X

They can just go into fastboot if they wanted to and just deny your return. I doubt they will do that. Although it would suck if the phone malfunctions on the next person and he returns it back to att and I guess that would be suspicious but I think your fine. I guess more space is nice on a phone but I don't think I have used that much space on my laptop haha, mabye 50 gigs of bloatware and some music and some fps games. I was just wondering why the switch. Oh and did the ruu go as planned? Oh and also if you decide to get insurance for your phone you should think about squaretrade...they protect against a lot..drops spills..and if you factory reset to stock Rom they will fix it even though you may have rooted..and they will pay you the no commitment price if they can't fix it.(drops,spills,etc)

Here in Los Angeles and surrounding cities the ATT reps are now trained to get into the boot loader to check for a tampered and unlocked device. A few months ago they were not but many devices have come back where someone screwed it up and returned it.

WhatTheAndroid? said:
They can just go into fastboot if they wanted to and just deny your return. I doubt they will do that. Although it would suck if the phone malfunctions on the next person and he returns it back to att and I guess that would be suspicious but I think your fine. I guess more space is nice on a phone but I don't think I have used that much space on my laptop haha, mabye 50 gigs of bloatware and some music and some fps games. I was just wondering why the switch. Oh and did the ruu go as planned? Oh and also if you decide to get insurance for your phone you should think about squaretrade...they protect against a lot..drops spills..and if you factory reset to stock Rom they will fix it even though you may have rooted..and they will pay you the no commitment price if they can't fix it.(drops,spills,etc)
Click to expand...
Click to collapse
The RUU worked perfectly and I returned it with no hassle; they didn't even factory reset it in front of me.
I now have the One X+ and I'm glad i switched. It runs so well I don't think I'll need a custom rom for a while.

Stuck in fastboot, can't find RUU

Hi, everyone
Yesterday I tried to root my HTC ONE X. Unfortunately, the phone got stuck in TWRP. I haven't used this recovery before but the touch didn't work and neither did the keys. When I pushed the power button appeared a screen saying swipe to unlock but it won't work either. I'm not completely sure how I got rid of TWRP screen and relocked the phone now it is stuck in fastboot mode. What's more I can't find the proper version of the RUU, my phone is 3.18.401.1 and CID is 032. And like it wasn't bad enough now my battery is low and I can't do anything neither unlock it again, nor install the proper RUU(which I can't find anyway)

funh0use said:
Hi, everyone
Yesterday I tried to root my HTC ONE X. Unfortunately, the phone got stuck in TWRP. I haven't used this recovery before but the touch didn't work and neither did the keys. When I pushed the power button appeared a screen saying swipe to unlock but it won't work either. I'm not completely sure how I got rid of TWRP screen and relocked the phone now it is stuck in fastboot mode. What's more I can't find the proper version of the RUU, my phone is 3.18.401.1 and CID is 032. And like it wasn't bad enough now my battery is low and I can't do anything neither unlock it again, nor install the proper RUU(which I can't find anyway)
Click to expand...
Click to collapse
Do you have the the Evita?
Sent from my Carbon-ize Evita using xda-developers app

No, it's the endeavour

No wonder. Wrong thread dude. At the top, type in HTC one x. And do not click on AT&T.
Sent from my Carbon-ize Evita using xda-developers app

funh0use said:
No, it's the endeavour
Click to expand...
Click to collapse
Ouch, be thankful it didn't perma brick your phone
Sent from my HTC One X using xda premium