Develop Bugs

HTC One X Suddenly won't turn on!

Hi guys!
I bought my new HTC One X on contract with three UK about 10 days ago. Been working great and I've flashed several different roms on it, the latest being the AOKP jelly bean.
I was in the middle of setting up my Go Launcher last night, when the phone suddenly died. I thought it must have just crashed following some rom/kernel issue, so I tried to turn it back on, no luck. Also tried holding the power button down but to no avail.
I supposed that it might have run out of battery, as it was fairly low at the time, so I left it charging on USB (with the indicator light flashing) all through the night (around 9 hours) and this morning it still won't turn on.
The screen won't come up at all, and the phone doesn't vibrate or make any noise but if I connect it to my computer it will sometimes be detected and I can see the device in ADB.
"adb devices" first shows the device as offline, then if I run "adb kill-server" and try again then it shows the device as "HT23YW105462 recovery".
I've then tried running commands such as "adb reboot", "adb reboot-bootloader", "adb reboot -p" but no luck. The phone seems to recognize the command as it disconnects, but it doesn't turn back on.
Any theories guys? I hope my new toy hasn't been bricked somehow! If this happened to my Desire HD I'd just take the battery out to make sure it was fully off and try again... is this a good idea here?
Thanks in advance for any help you can give! Many cookies will be given as reward. (sorry for the long post )
- P.s. This is pretty urgent as I use this number for work!

:victory:
Ok, it seems to have been resolved at last... just for anybody who gets the same issue, here's what worked for me.
After doing some more searching I found someone mentioning this method: Leave the phone plugged in to your USB port for a while until the orange LED flashes. Leave it flashing for a few minutes, then quickly swap the lead from your USB port to a wall charger. If you leave it unplugged too long then it seems the LED stops flashing and it won't work, so do it quickly.
If successful the LED will keep flashing while plugged into the wall, and it will start to charge up. Give it a while (I left mine for about 25 minutes) then try and turn it on. This worked for me, but even after this period of time it had only charged up to 2%!
:S This is an odd phone indeed.

Very strange resolution IMHO.
This problems must be caused by discharging the battery more than it should (which I guess custom ROMs can cause)
/Croaton

Croaton said:
Very strange resolution IMHO.
This problems must be caused by discharging the battery more than it should (which I guess custom ROMs can cause)
/Croaton
Click to expand...
Click to collapse
Very strange indeed... I tried pretty much everything I could before this, but this was the only thing to get the phone to boot. Charging and working fine now :S. I'll have to make sure to never run it flat if I can help it, this would be a right pain if it it happened while I was out

Just saved from similar issue
My battery run out last night when I had the phone connected to the tv through USB>HDMI when i put it on the charger the charging light would not switch on. Phone wouldnt switch on either it was really dead!. Left it all night hooked up to charger and this morning still nothing, wouldnt switch on.
So I Hooked it up to the PC and after 10 minutes or so the light started to flash and I quickly inserted the usb charging cable and it started to charge.
Pretty sure I either discharged the battery to much (did update to 7.2.2 yesterday with 30% bat), OR something to do with having the USB>HDMI cable inserted when the battery run out.
Odd but brought it back to life (phew!)

silenttalker said:
My battery run out last night when I had the phone connected to the tv through USB>HDMI when i put it on the charger the charging light would not switch on. Phone wouldnt switch on either it was really dead!. Left it all night hooked up to charger and this morning still nothing, wouldnt switch on.
So I Hooked it up to the PC and after 10 minutes or so the light started to flash and I quickly inserted the usb charging cable and it started to charge.
Pretty sure I either discharged the battery to much (did update to 7.2.2 yesterday with 30% bat), OR something to do with having the USB>HDMI cable inserted when the battery run out.
Odd but brought it back to life (phew!)
Click to expand...
Click to collapse
Hmm, seems like a pretty common fault. Maybe an app that cuts power to the phone when it reaches a critical limit might be a good idea... I noticed that most phones seem to turn themselves off before fully dead, whereas ours now seem to completely flatten themselves. At least if it shut down at 1% you could still turn it back on when you found a charger, and it could tell you why your screen was about to go black rather than "poof, gone".
Anybody know such an app? Or should I make one (been wanting to get my hands dirty)

wont turn on
chrisoverson said:
Hmm, seems like a pretty common fault. Maybe an app that cuts power to the phone when it reaches a critical limit might be a good idea... I noticed that most phones seem to turn themselves off before fully dead, whereas ours now seem to completely flatten themselves. At least if it shut down at 1% you could still turn it back on when you found a charger, and it could tell you why your screen was about to go black rather than "poof, gone".
Anybody know such an app? Or should I make one (been wanting to get my hands dirty)
Click to expand...
Click to collapse
im unable to see led light i believe unsupported kernel fryed phone

Red light flashing.. phone won't boot.

Hello! let's just cut to the chase. I need help..
Couple of days ago I got tired of waiting for the new ota for my phone so I decided to root.. unlocking bootloader went well, installed newest cwm, made a backup of my rom and chose renovate 3.0 as my first rom to try... everything works normal and I update the faux kernel on the rom to version 5b01.. all works normally at this point.. I play games, listen to music, surf the web.. yesterday I then updated the kernel to 5b03.. I went playing dark knigt rises (btw a very good game) and the phone heats up pretty much (which I think is normal as the game is quite heavy and I use wilkyys game booster app). I play about 15minutes and I get the message that the battery is running low, I plug the charger in and continue.. five minutes go and the phone freezes and the screen goes black.. the phone is connected to the charger and the charging light blinks red.. the phone won't start, even when pressing the power key for 10seconds. I can get to the bootloader and recovery _when_ the phone is connected to the charger thou.. if I unplug the charger the phone won't do anything. I search the problem on xda and find some threads about similar problems.. eventually after changing from the wallcharger to the usb charger on my pc (did this many times..) the red light goes solid and I press power and the phone boots normally.. weehee I made it!! or so I thought..
Next day: I woke up and the phone was in charger all night. Battery reads 100%. I load "system tuner" and experiment with undervolting my phone (only -50mv) and run some benchmarks and everything seems working.. I start to download an app from the play store.. the phone freezes and again the same flashing red light is to be seen, I thought it could be because of the undervolt but I'm not sure anymore.. and now I haven't got the phone in working condition.. I have now got the phone in recovery for about three hours and there should be enough juice for it to start but it wont..
I also restored my backup but that didin't help.. with the getvar battery-voltage command it reads about 2500mv which should be enough to atleast power it on?

Hi
elmonen said:
Hello! let's just cut to the chase. I need help..
Couple of days ago I got tired of waiting for the new ota for my phone so I decided to root.. unlocking bootloader went well, installed newest cwm, made a backup of my rom and chose renovate 3.0 as my first rom to try... everything works normal and I update the faux kernel on the rom to version 5b01.. all works normally at this point.. I play games, listen to music, surf the web.. yesterday I then updated the kernel to 5b03.. I went playing dark knigt rises (btw a very good game) and the phone heats up pretty much (which I think is normal as the game is quite heavy and I use wilkyys game booster app). I play about 15minutes and I get the message that the battery is running low, I plug the charger in and continue.. five minutes go and the phone freezes and the screen goes black.. the phone is connected to the charger and the charging light blinks red.. the phone won't start, even when pressing the power key for 10seconds. I can get to the bootloader and recovery _when_ the phone is connected to the charger thou.. if I unplug the charger the phone won't do anything. I search the problem on xda and find some threads about similar problems.. eventually after changing from the wallcharger to the usb charger on my pc (did this many times..) the red light goes solid and I press power and the phone boots normally.. weehee I made it!! or so I thought..
Next day: I woke up and the phone was in charger all night. Battery reads 100%. I load "system tuner" and experiment with undervolting my phone (only -50mv) and run some benchmarks and everything seems working.. I start to download an app from the play store.. the phone freezes and again the same flashing red light is to be seen, I thought it could be because of the undervolt but I'm not sure anymore.. and now I haven't got the phone in working condition.. I have now got the phone in recovery for about three hours and there should be enough juice for it to start but it wont..
I also restored my backup but that didin't help.. with the getvar battery-voltage command it reads about 2500mv which should be enough to atleast power it on?
Click to expand...
Click to collapse
2500mv is far too low for lithium ion batteries. There are protection mechanisms in most lithium ion batteries that will trigger at 2.7volts or lower putting the battery and its protection circuitry into deep sleep.
From the battery university: http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries/
Li-ion should never be discharged too low, and there are several safeguards to prevent this from happening. The equipment cuts off when the battery discharges to about 3.0V/cell, stopping the current flow. If the discharge continues to about 2.70V/cell or lower, the battery’s protection circuit puts the battery into a sleep mode. This renders the pack unserviceable and a recharge with most chargers is not possible. To prevent a battery from falling asleep, apply a partial charge before a long storage period.
If this is the case you may not be able to recover easily. We can only assume something went wrong with the phones firmware that caused it to deeply discharge and now protection measures have kicked in.
Regards
Phil

hmm.. thanks for the answer.. last night I got the charging light to stay solid when I plugged the phone in and I was so happy.. but I was so stupid and tried immediatly to turn it on.. it even started and got to the quietly brilliant screen, but died pretty soon and the red light started blinking again.. then I realised I should have kept it charging for a while before trying to turn it on... god damn it..

Hi
elmonen said:
hmm.. thanks for the answer.. last night I got the charging light to stay solid when I plugged the phone in and I was so happy.. but I was so stupid and tried immediatly to turn it on.. it even started and got to the quietly brilliant screen, but died pretty soon and the red light started blinking again.. then I realised I should have kept it charging for a while before trying to turn it on... god damn it..
Click to expand...
Click to collapse
When lithium batteries are deep discharge (below 2.7volt) changes take place which can cause short circuits in the battery, recharging then becomes dangerous, hence the battery goes into a form of safety mode, it's like a fuse blowing. It may never take a charge again, or if it does, the battery life will be less than before.
Hope it recovers okay however if it really did hit 2.5volt it could be permanently damaged now.
Regards
Phil

mine was doing that for a while. Keep it plugged in, if the wall charger doesnt work hook it up to a computer. it will turn on again...

simple keep the phone on charge for few hours and dont touch it.

Ok back to the problem.. the phone was in charger yesterday for about 12hours.. and still won't show any signs of recovery.. blinking red light continues... I might just have to accept that I have to send it in to repair... sigh.. and I think I have to pay for it..
As I said in my first post I have restored a nandroid backup of which I made as soon as I installed cwm.. so I should be at stock firmware? allthou I can't confirm it as I can't get the phone to boot but cwm said restore was succesful.. next step is to install original recovery and relock the phone, am I correct? so next question is.. is there anyway to do this as everytime I try to flash something with flasboot I end up with "failed: low battery"...?

elmonen said:
Ok back to the problem.. the phone was in charger yesterday for about 12hours.. and still won't show any signs of recovery.. blinking red light continues... I might just have to accept that I have to send it in to repair... sigh.. and I think I have to pay for it..
As I said in my first post I have restored a nandroid backup of which I made as soon as I installed cwm.. so I should be at stock firmware? allthou I can't confirm it as I can't get the phone to boot but cwm said restore was succesful.. next step is to install original recovery and relock the phone, am I correct? so next question is.. is there anyway to do this as everytime I try to flash something with flasboot I end up with "failed: low battery"...?
Click to expand...
Click to collapse
I've experienced this kind of problem when I drain the battery flat; naturally, I crapped myself like everyone else since there's no easy way to remove the battery like you would for any other phone.
All I did (and still do) when this happens is hold the power button until the main buttons flash white a few times, let go and it should reboot the phone..

two minutes pressing power button, nothing happens

elmonen said:
two minutes pressing power button, nothing happens
Click to expand...
Click to collapse
did the buttons even flash??
Try holding vol down + power until you get a response, then try holding the power button again ..
for me the key was to get the buttons to flash white, thats when i knew things were gonna be ok! :highfive:

kennylovesyou said:
did the buttons even flash??
Try holding vol down + power until you get a response, then try holding the power button again ..
for me the key was to get the buttons to flash white, thats when i knew things were gonna be ok! :highfive:
Click to expand...
Click to collapse
no response! only response is that when it's in charger I can get to to blootlader and recovery with the vol- power combination..

If it won't charge read this thread. http://forum.xda-developers.com/showthread.php?t=1658084
Helped me out with similar problem.
Hope this helps.
Sent from my HTC One X using XDA Premium HD app

Amicushia said:
If it won't charge read this thread. http://forum.xda-developers.com/showthread.php?t=1658084
Helped me out with similar problem.
Hope this helps.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Tried that :/ won't work.. as my phone doesnt restart with the script.. only way to get a response from it is to press power and vol down when in charger...
Thanks for the suggestion thou.

all right.. quick update.. I have sent the phone in for repair.. so just waiting for the repair bill

Ok... update (don't know if anyones interested..) Today I got at txt message from my carrier that the phone is now ready.. and what do you know.. it was covered by warranty. They changed the motherboard and the screen module (I had one dead pixel) needless to say Im pretty happy now.

elmonen said:
Ok... update (don't know if anyones interested..) Today I got at txt message from my carrier that the phone is now ready.. and what do you know.. it was covered by warranty. They changed the motherboard and the screen module (I had one dead pixel) needless to say Im pretty happy now.
Click to expand...
Click to collapse
Don't you just love it when that happens.
I had a rooted phone and my warranty was probably void. A week ago I dropped the phone screen first onto a concrete floor and I expected the worst. Picked it up and turned it on and to my surprise, the screen hadn't cracked. Used it for 5 minutes and it worked as it normally would. When I got back home and wanted to make a call, the screen wouldn't turn on. The lights for the buttons would light up but the screen would remain blank. Calls and texts would come through so the phone worked, just without the screen. After about 10 minutes of tinkering, the screen turned on and I heaved a sigh of relief thinking all was normal again. But when I locked it and tried unlocking it, the screen refused to turn on again. At this point I assumed there would be a loose connection between the MB and screen.
I took the phone to a few repair shops around here to find out how much they would charge and I got quotes around $200. So I decided to try taking it to the vodafone store to see how much it would cost to get HTC to repair the phone. The guy over the counter inspects the phone and finds no physical damage to the screen and says that they'd be glad to replace the phone right then and there at the price of me losing all my data as that would be unrecoverable. I told him I'd be glad to have a replacement on the spot. So in the end, I guess I got a good deal.

Lucky you !
Sent from my HTC One X using XDA Premium HD app

I had the same problem last night:
phone charging with the HTC wallcharger, alarm set.
the device did not ring: it died during the night.
At first, impossible to boot (rom or hboot) or to charge it. I plugged it on my PC and the red light started to flash. One hour later, it was still flashing, so I tried to turn it ON
It turned ON but repported 2% battery only. (ok, that's why it was refusing to boot)
4 hours later, ON and plugged to the HTC wallcharger (that I verified of course), it was still 2%
After three reboots, plug/unplug several times, suddenly battery displayed 44% instead of 2%
Battery monitor repports that indeed, the device charged for the 1st part of the night, then suddenly and very quickly discharged to 0 while plugged, with no particular app to drain the battery.
During the 4 hours it was plugged and ON, it remained 2%, then a sudden 44% after a reboot.....
What the hell is that???? I've now cleaned cache and battery stats in recovery and I'm letting it charging to see if it goes above these 44%
Weird, I really thought my battery had just died....
EDIT: 2 minutes later, it now repports 46%, so seems to charge correctly. But I need to know what happened, I usually relay on my phone alarm to wake up, and if it happens again, it could be a real problem. Maybe I should flash an other recovery, even if I never had a single problem with it?

kennylovesyou said:
did the buttons even flash??
Try holding vol down + power until you get a response, then try holding the power button again ..
for me the key was to get the buttons to flash white, thats when i knew things were gonna be ok! :highfive:
Click to expand...
Click to collapse
I have drained battery, been charging all night with a flashing red LED. No response. Now when I plug it in it still flashes red. When I hold the power button (also power+volume down) the main buttons start flashing white, but no response from the phone whatsoever.
When I let go the power button during the flashing, the lights either go out or stay on..
Any ideas? Thank you!

[Q] Defect or just coincidence?

I am on my 3rd Fire in less then 60 days, the first two died from the same thing. Powered off but when I went to power it on the next morning the light would briefly turn green then turn off. The screen would not come on, and when I plugged the charger in the light would turn green then change to a bright orange then immediately dim to a pale orange. Like I said the first two did the same thing, they were both flashed with the latest gedeROM and OC to 1200Mhz, I have shied away from flashing the third one until I can find a common denominator , either that or my luck is just that poor. I have googled this issue for the last few days and haven't found anybody with the same issue. Any help would be awesome thanks.

sarsius said:
I am on my 3rd Fire in less then 60 days, the first two died from the same thing. Powered off but when I went to power it on the next morning the light would briefly turn green then turn off. The screen would not come on, and when I plugged the charger in the light would turn green then change to a bright orange then immediately dim to a pale orange. Like I said the first two did the same thing, they were both flashed with the latest gedeROM and OC to 1200Mhz, I have shied away from flashing the third one until I can find a common denominator , either that or my luck is just that poor. I have googled this issue for the last few days and haven't found anybody with the same issue. Any help would be awesome thanks.
Click to expand...
Click to collapse
Well it sounds like its not charged. When u plug it in, do you have enough time to hold the power down for the 20 seconds required to force it off. If you can do that then you could let it charge while its forced off. But it sounds to me it wont stay on long enough. This might require a factory cable, not sure though. This same thing happened to me, ad with me being stupid I made a charger that is more voltage than default charger and I fried my kindle. I suggest not to do what I did

powerpoint45 said:
Well it sounds like its not charged. When u plug it in, do you have enough time to hold the power down for the 20 seconds required to force it off. If you can do that then you could let it charge while its forced off. But it sounds to me it wont stay on long enough. This might require a factory cable, not sure though. This same thing happened to me, ad with me being stupid I made a charger that is more voltage than default charger and I fried my kindle. I suggest not to do what I did
Click to expand...
Click to collapse
Yes I attempted a reset but it wouldn't respond and I tried to let it charge, but after about an hour it got extremely hot and I didn't feel I could leave it plugged in safely. When I contacted amazon for support I did all this for the tech on the phone and when I plugged it in and told him about the light, he said something about the usb port had come off the board which I know is possible but to happen twice in 60 days with two different devices is just ridiculous. I'm not sure what I am doing wrong if anything both devices were fully charged when the errors occurred. I just don't want to have to get a fourth before the month is out, the only positive is the fast turn around from amazon.

[Q] HTC One X won't turn on at all

Hello, I asked this question yesterday and fixed it but it appears to have gotten worse.
Pretty much my phone turned off randomly last night and now all I get is a red flashing light, I'm on Cyanogenmod 10. I managed to turn my phone on once and it turned off again, I think it may be stuck on 2% battery or something. I also did the plug into pc then switch to mains and left it to charge but nothing happened, I'm trying to go back to stock ROM too and completely format my phone and start again.
Can someone help me with this? I can't turn my phone on enough to get it into USB mode so I can change the stuff around and I think it may actually be broken, I have no idea how to fix it.
- Alerion

Leave it charging for a couple of hours.

robchongke said:
Leave it charging for a couple of hours.
Click to expand...
Click to collapse
I left it charging all day, nothing has happened

In case of low battery did you try this to get it charged
http://forum.xda-developers.com/showthread.php?t=1957442
Check the batt script post .....
Hope this helps a bit

MarcelHofs said:
In case of low battery did you try this to get it charged
http://forum.xda-developers.com/showthread.php?t=1957442
Check the batt script post .....
Hope this helps a bit
Click to expand...
Click to collapse
I think it may actually be down to having to change power cable as I lost my original HTC One X the other day, its probably not charging fast enough

I had it happen just now for the first time, the battery monitor indicated 89% so it didn't need charging, and plugging it in didn't turn on the amber LED. I held down the power button for a good 30 seconds and a few seconds later it started up.
How odd and I hope it doesn't happen again, considering I just switched from the lemon problem ridden LG Optimus LTE (Nitro HD).

[Q] Problems charging/holding a charge/can't boot

Having massive issues right now. Last night I left my phone plugged in AC to charge and ran a sleep tracker app. Woke up this morning and found the phone dead. I tried unplugging and plugging again multiple times and managed to get the Red LED blinking then it went steady indicating it was charging. Turned the phone on but as if it wasn't charging anymore, it powered off within minutes. I managed to get recovery running and factory reset (running CM10). Same issue still there. I even tried leaving the phone in hboot and recovery to charge but after 10 mins the battery went flat again. Now I've just left the phone off and plugged into AC. The blinking LED came on again then went steady - but after 15 mins the LED light disappears. I just left it like that, now the phone tries to boot up but gets stuck at HTC logo. Also it is incredibly hot.
Any ideas? Really need help here.
Additional info, installed NFS: Most Wanted yesterday, tried playing but phone really overheated big time. Could that have cause the motherboard to fry? Just seems odd though cause it boots up fine, just won't stay on - can't even get past the initial setup wizard.
Also I would take it back to Vodafone AU but since I can't get the phone up long enough to restore to stock, they might find out I've rooted and thus voiding my warranty.

I had the same problem. I installed NFS MW and it drained my battery like help and when i tried recharging it it wouldnt charge
at all. Even when i pluged the phone on it wouldnt charge. Tried a different cable. For all it could be a adapter/cable problem.
That was what it was for me. I tried a different charger and it worked. If you are using a different charger, use something with 1A output.

If the led is blinking, it means that the battery is verryy low.
once your phone turns on, turn the airplane mode ON and display OFF and wait a few minutes before using the phone.

no luck
xzallent said:
I had the same problem. I installed NFS MW and it drained my battery like help and when i tried recharging it it wouldnt charge
at all. Even when i pluged the phone on it wouldnt charge. Tried a different cable. For all it could be a adapter/cable problem.
That was what it was for me. I tried a different charger and it worked. If you are using a different charger, use something with 1A output.
Click to expand...
Click to collapse
Yea, I tried using a different cable, even tried using my old iPod USB to wall adapter. No luck there, but I think I'm on to something now. Thanks anyway

getting there
Vcek said:
If the led is blinking, it means that the battery is verryy low.
once your phone turns on, turn the airplane mode ON and display OFF and wait a few minutes before using the phone.
Click to expand...
Click to collapse
Hey, yea I figured that much from searching around. Too bad it's such a big flaw. I couldn't sustain a charge at all when I was still on CM10. Couldn't even finish booting up and it would just die. Voltage was super low was my guess. Tried using the fastboot charging script (http://forum.xda-developers.com/showthread.php?t=1658084&page=5) and managed to get battery up enough to flash stock boot.img, did a nandroid restore to Stock ROM then flashed stock recovery. Seems to be stable now, in airplane mode and display off. Started up phone at 4% and now it's at 6% so fingers crossed :fingers-crossed: Thanks for the reply though - needing all the tips I can get!