Phone won't power on or charge properly - HTC One X

So last night I unlocked the bootloader for my HTC One X. I wanted to get CM10.1 Nightly builds onto my phone, and was able to get all the way to where I have CWM 5.8.4.0 and even installed CM10.1 Nightly release. The problem at the time was that when I rebooted the phone it would become stuck at the bootscreen with the "Quietly Brilliant" quote. I tried everything from there to get CM10.1 working based on what I found around other threads and forums.
At one point the battery started running low and the phone stated that the battery was too low to perform fastboot commands. I thought I was in the clear as forums stated that as long as you have CWM on your phone then you can charge it back to full. I turned off my phone and plug in the wall charger and the red indicator light turned on a solid red.
This morning when I woke up, the red indicator wasn't on so I tried turning it on and nothing happened. I held down the volume button and pressed it, held down power for a minute...nothing seemed to work. I tried plugging my phone into my pc and it made that sound where the computer recognizes a new device and then made the sound that a device has been disconnected shortly after. This time though, the red indicator turned on but was blinking. I check other forums on how to fix this and all of them say to either:
1. Let the phone charge until the red light is solid
2. Hold down the volume button and then click power to boot into recovery.
The problem with that was the first option didn't happen, at a certain point the red light will just turn off. The 2nd option yielded nothing as I can't turn my phone on...
I'm seriously hoping I didn't just brick my phone and am hoping someone out there has a solution to the problem I'm facing.
Please and thank you!
***UPDATE***::: I got it to charge just enough to power on back to the bootloader using a Duracell external battery pack. Stupid me decided to relock the phone and go for the RUU when I clearly didn't have 30% battery life. I ended up looking around forums until I found a fix for that located here: (http://forum.xda-developers.com/showthread.php?t=1658084)
Using that method my battery maxed at 3665mV and I had just enough power to unlock the phone again and then reflash cwm 5.8.4.0 just for safety measures. Now I have the phone booted into the recovery main screen and plugged it into my ac charger. However, there's no LED indicator and I'm not sure if the phone is even charging at this point. Unless someone can help assure me that it is actually charging then I will wait about 2 hours before plugging it back into my pc and checking the power variable. Hopefully this all works out...
***UPDATE 2***::: This is just leading to more frustration. I proceeded with the following tutorial http://forum.xda-developers.com/showthread.php?t=1859714 and got to where I start the RUU exe. Unfortunately for me I ran into a "155: Unknown Error" and I tried the following RUU's: (3.14.707.24), (3.14.401.31) first. My phone code is (3.14.707.24) so I wasn't sure why it wasn't working. I read another thread http://forum.xda-developers.com/showthread.php?t=1660642 that said to try either (1.29.401.11) or (1.29.401.7). Both of these RUU's gave me either a "USB connectivity error" or a "Main battery is below 30%"
Now I wasn't sure if my phone had actually lowered that much since I started working on it, but I checked the mV value and it gave me 4030 which I thought was more than 30%. I don't believe it's the USB cause I can still get to the 155 error for the former RUU's. I just went ahead and started charging the phone again and will try again soon. This is really ticking me off...
***UPDATE 3***::: NOPE! I flashed TWRP in replacement of clockwork just cause another thread said it's supported rather than just a port like CWM. Anyways, I've tried several other RUU's and they all give me the 30% Low Battery nonsense. I have tried: (1.28.728.9), (1.29.728.12), (1.29.707.11) but I didn't expect these to work since the previous thread menioned how I can't go backwards. Right now I'm completely lost on what I should do. RUU was supposed to be the last resort, but even this is failing me. FYI: My device's CID: HTC_044 and version as mentioned before: 3.14.707.24 Don't know if that will help but if someone out there can tell me my next steps then it would be much appreciated.
***FINAL UPDATE***::: Mission Accomplished!!! I'm glad to say that I got my phone running back on stock and am not holding a brick in my hands. How I fixed it? This morning I came across this thread here http://forum.xda-developers.com/wiki/HTC_One_X#Disaster_Recovery_-_what_to_do_in_the_event_of_a_bad_flash and I noticed something new in the instructions. It said to run fastboot when executing the RUU, and interestingly enough when I got to the 2nd to the last step the version said "updating from 3.14.707.24 to 3.14.707.24" Before, I ran the RUU while on the "Quietly Brilliant" splash screen since the tutorial I was following never mentioned having to run the RUU while in fastboot. This would probably also explain why, when I ran the RUU in the splash screen, it gave me the (3.14.401.31) version number instead of the correct (3.14.707.24) version.
Well, it's been a messed up roller coaster of a ride and I will try my luck with flashing another rom later this week. I hope I never have to revisit another HOX troubleshooting thread for the remainder of the time that I use this phone. Thanks to all that assisted in my endeavors.

Hey,
Try to boot into recovery when charger is plugged in hold power + vol up buttons and wait.
If that doesn't work, there is a script that charges the phone by looping ot on fastboot.
After you manage tocharge the phone boot into recovery and install cm 10.1 vendor installer :
http://d-h.st/487
Sent from my HTC One X using xda app-developers app

davidk-il said:
Hey,
Try to boot into recovery when charger is plugged in hold power + vol up buttons and wait.
If that doesn't work, there is a script that charges the phone by looping ot on fastboot.
After you manage tocharge the phone boot into recovery and install cm 10.1 vendor installer :
Click to expand...
Click to collapse
I already tried the method you mentioned and that didn't work. The problem with the script is that I assume I would need to have the phone charged somehow and then turn it on. I can't charge the phone at this point so I'm lost...

Did yoy actually try to boot into boot loader? Power + vol down
As far as i remember, charge script works whe on bootloader(please correct me if im wrong guys)
Im using twrp recovery and it charges just fine for me.
Sent from my HTC One X using xda app-developers app

The one and only solution to this is to plug it in to an AC charger and let it charge over night. It doesn't matter if the led is enabled or not.

davidk-il said:
Did yoy actually try to boot into boot loader? Power + vol down
As far as i remember, charge script works whe on bootloader(please correct me if im wrong guys)
Im using twrp recovery and it charges just fine for me.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, I have tried that too...it didn't work =(
At this point the phone just won't charge properly.

TToivanen said:
The one and only solution to this is to plug it in to an AC charger and let it charge over night. It doesn't matter if the led is enabled or not.
Click to expand...
Click to collapse
I plugged it into the AC charger last night and this morning is when the problem started. I'm starting to think I should have left the phone on in the recovery screen and charged it that way.
When I try plugging the phone into the AC charger now there's no red led indicator, but there's one when I plug it into the pc (even though the flashing light disappears after 5 minutes or so).

Hey,
Did you manage to get the phone charged?
Sent from my HTC One X using xda app-developers app

davidk-il said:
Hey,
Did you manage to get the phone charged?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
So last night I checked the millivolt of my battery after charging it through recovery for about 2 hours and it was at roughly 3810mV. I'm not sure what the max mV for HOX is but I let it charge overnight again. This morning I checked and it was at around 4180mV. I'm not very knowledgable on how to convert the 1800mah value over to how many mV it would equal to. I wasn't sure if this was the max so I left it charging and will get back to it once I get home.

~4200mV is equal to 100% charge.

TToivanen said:
~4200mV is equal to 100% charge.
Click to expand...
Click to collapse
Good to know! I'll give the RUU a try when I get the chance later today and post an update. Thanks!

I flashed TWRP in replacement of clockwork just cause another thread said it's supported rather than just a port like CWM. Anyways, I've tried several other RUU's and they all give me the 30% Low Battery nonsense. I have tried: (1.28.728.9), (1.29.728.12), (1.29.707.11) but I didn't expect these to work since the previous thread menioned how I can't go backwards. Right now I'm completely lost on what I should do. RUU was supposed to be the last resort, but even this is failing me. FYI: My device's CID: HTC_044 and version as mentioned before: 3.14.707.24 Don't know if that will help but if someone out there can tell me my next steps then it would be much appreciated.

Here is your ruu
http://bugsylawson.com/index.php/fi...24-radio-5120416229-release-296434-signedexe/
Relock the bootloader
Fastboot oem lock
Then run the ruu WITH admin rights

Mr Hofs said:
Here is your ruu
http://bugsylawson.com/index.php/fi...24-radio-5120416229-release-296434-signedexe/
Relock the bootloader
Fastboot oem lock
Then run the ruu WITH admin rights
Click to expand...
Click to collapse
If I'm not mistaken, that's the first one I used last night along with the same steps. It gave me the "155 Unknown Error" and I proceeded to trying other RUU's. I will try again when I get home, where I can only hope it works for some odd reason. Stay tuned.

Well its the only one that should work. A newer one in not out. And this one matches the main version 100%

Mr Hofs said:
Well its the only one that should work. A newer one in not out. And this one matches the main version 100%
Click to expand...
Click to collapse
I think what I forgot to mention in the updates was that I found something strange. During the RUU steps, after I clicked update, it said:
Upgrading from 3.14.401.31 to 3.14.707.24 which I thought was really strange since 401 indicates Europe version. Is this something to note?
It was the next steps that lead me to the 155 Unknown Error

The outcome of
Fastboot getvar version-main
That is the number that must match the ruu ....if its 3.14.401 then you have the wrong ruu. Do the command first and check the number/post the outcome here

Mr Hofs said:
The outcome of
Fastboot getvar version-main
That is the number that must match the ruu ....if its 3.14.401 then you have the wrong ruu. Do the command first and check the number/post the outcome here
Click to expand...
Click to collapse
Here's the thing, when I run the command to get the version I receive: (3.14.707.24)
However, when I run the 3.14.707.24 RUU it leads me to a page where it says I'm going from 3.14.401.31 to image: 3.14.707.24
That seemed very odd to me. Can you help explain why this is?

Hmm no i can't ! That's very strange.....try the 707 ruu again. Otherwise try the 401 ruu ?
http://bugsylawson.com/index.php/fi...-r-radio-5120416229-release-302015-signedexe/
Don't exactly know what to think about that

Is there a solution for Droid DNA?
I tried rooting it last night. It was successful. The last step was to reboot according to JCase's method. It hasnt restarted since then. No battery indicator as if its not at all plugged in. "YES IT WAS ON CHARGING THE WHOLE NIGHT". It wont even show me the boot screen. "YES, I PRESSED THE POWER AND VOL BUTTON FOR MORE THAN A MIN".
Any help would be appreciated.
Thank You

Related

[Q] Dead phone after update, any way to bring it back

Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Check battery pins
hedeon said:
Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Click to expand...
Click to collapse
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
whiperhack said:
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
Click to expand...
Click to collapse
That was my first idea too but, no m8, battery is placed ok....
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
if4ct0r said:
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
Click to expand...
Click to collapse
Tried that too, still dead
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
I understand I should not be worried that all of these RUU's are listed as for model: ACE?
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
if4ct0r said:
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
Click to expand...
Click to collapse
OMG! I was previously looking for stock roms and everytime I ended up on that site from your link I was annoyed that someone is giving a wrong link to roms for wrong phone. Silly me!
I am downloading right now.
if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
No it says phone not connected (error[170])
hedeon said:
No it says phone not connected (error[170])
Click to expand...
Click to collapse
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
when you connected it to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then sorry to say, its bricked.
The only way to recover it now is via jtagging or replacing the mainboard (which generally is what they do when you send it in for warranty repair)
whiperhack said:
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
Click to expand...
Click to collapse
Yes, I thought about it as phone behave like it has no power at all. But this is not the case, as I have been flipping that and another battery in every possible position. And I know which one is correct as I can see where pins are in battery pocket. I left it alone under charging and other time with no battery at all hoping that will hard reset phone. No effect at all .
JSLEnterprises said:
when connected to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then its bricked, sorry to say
Click to expand...
Click to collapse
I had drivers previously installed. But I am not entirely sure are we talking about same thing as I don't know what QLOAD is. Anyway comp doesn't see any recognised or unrecognised device that could be my phone...
I am not worrying about damn phone as if it is hard bricked tech guys in service will not probably spot that it was rooted. So they will replace, or if not I will go to insurance company. Problem is it takes to much time, I wont make it b4 Christmas.
Thank you guys,
anyone has some other ideas? Please...
desperation bump
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
if4ct0r said:
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
Click to expand...
Click to collapse
Sigh... I got "waiting for device" forever in CMD... As you said, it's dead. Gonna send it to HTC in Monday...
Thank you all, appreciate your time
Hello hedeon,
I have the same experience today, as you state in the first post in this thread.
Did you, and how solve the problem?
Is there people with the same problem? This morning I receive notification about system update for my HTC Desire HD. The rest is exactly same problem from the top of this story = death + death + death.....
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
GuyInTheCorner said:
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
Click to expand...
Click to collapse
May be, but updating started with downloading, then resetting, and then green line was growing up to 1/3 of total size, and at that size stay more then 20 min. Then I try to to push every button, and every combination of buttons, and after 10 minutes more I had pull battery out.
Was it too impatient ?
What was the Android version before you rooted if you can remember and which tool did you use to root?
From what you wrote earlier, it asked you for a 2.3 update which means you probably flashed a Froyo RUU as stock, to bring the phone back to stock ofc.
However, if your DHD came with stock Gingerbread, flashing a Froyo RUU will most definitely screw the phone. I'm not sure if it's beyond repair atm or not, but if that was the case, even if you didn't mess with the battery, chances are the phone would never boot anyway.
Look into AAHK thread, I think there is a good how to there.

Totally bricked?

Okay, I tought i just could RUU my phone using RUU file. So I downloaded RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe and booted to fastbood mode -> connected USB -> ran RUU. Anyways, all wen fine and the gray HTC logo appeared on my screen but after few seconds the RUU gave me "Bootloader version error [140]". After that my phone is just dead. It wont turn on or anything, I cant get ADB to my phone. Screen is totally black. The phone just randomly vibrates when i plug it in the charger or press the power button after taking the battery out. But its just random. The charging led indicator wont even turn on.
I Had few weeks old XJ's MIUI installed, CWM 4.X.X.X and hboot 6.93.9999 (if i remember right, 6.93.XXXX it was anyways). After failing the RUU, I googled and found out that i shuold have downgraded hboot first? I recently bought a new phone so actually just didnt give s*** Im having proximity sensor problem in my old Desire, so I would like to return it to the shop after flashing the default rom.
So folks, how do I proceed? Totally bricked?
Thanks!
jaavaa said:
Okay, I tought i just could RUU my phone using RUU file. So I downloaded RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe and booted to fastbood mode -> connected USB -> ran RUU. Anyways, all wen fine and the gray HTC logo appeared on my screen but after few seconds the RUU gave me "Bootloader version error [140]". After that my phone is just dead. It wont turn on or anything, I cant get ADB to my phone. Screen is totally black. The phone just randomly vibrates when i plug it in the charger or press the power button after taking the battery out. But its just random. The charging led indicator wont even turn on.
I Had few weeks old XJ's MIUI installed, CWM 4.X.X.X and hboot 6.93.9999 (if i remember right, 6.93.XXXX it was anyways). After failing the RUU, I googled and found out that i shuold have downgraded hboot first? I recently bought a new phone so actually just didnt give s*** Im having proximity sensor problem in my old Desire, so I would like to return it to the shop after flashing the default rom.
So folks, how do I proceed? Totally bricked?
Thanks!
Click to expand...
Click to collapse
sounds like wrong RUU file meant for SLCD/Amoled.
try the first post in Q&A which should deal with this...it's a sticky for a reason
It looks like slcd brick look for droidzone slcd brick guide
Sent from my HTC Desire using XDA Premium App
Thanks, but as I already said, the phone cant be detected by PC. The phone wont even turn on. I tried again starting the phone to fastboot mode, but the phone wont even vibrate or show any signs of life. The only thing is that when i randomly plug the phone to the charger, it might vibrate and start warming up.
And yes, I've tried charging the phone over night assuming the battery would be empty.
jaavaa said:
Thanks, but as I already said, the phone cant be detected by PC. The phone wont even turn on. I tried again starting the phone to fastboot mode, but the phone wont even vibrate or show any signs of life. The only thing is that when i randomly plug the phone to the charger, it might vibrate and start warming up.
And yes, I've tried charging the phone over night assuming the battery would be empty.
Click to expand...
Click to collapse
so holding down back and power to get straight to fastboot doesn't work at all? i'm only referencing the troubleshooting guide
droidzone's slcd brick guide is more comprehensive, if that doesn't work then i dunno unfortunately...
Whoa, got some life to my phone! Started it somehow with usb plugged and vol down and i got it to recoverymode! ADB Devices gives me following:
List of devices attached
HT07XPL06736 recovery
Dont want to boot the phone again, what do i do now? tried running a RUU for SLCD spotted in the sticky thread here, but it gives me 170 USB error.
EDIT:
So I'm in this situation now? (taken from droidzone's guide)
"IF YOU SOFT BRICKED AN SLCD BRANDED DESIRE WHICH HAD AN UPDATED VERSION OF HBOOT BY FLASHING AN INCOMPATIBLE RUU, AND IF THE DISPLAY WONT TURN ON NOW, YOU CANNOT RESTORE THE PHONE TO WORKING CONDITION UNLESS YOU HAVE A CORRECT RUU FOR THE UPDATED HBOOT, OR A GOLDCARD. "
Click to expand...
Click to collapse
Well, is there a correct RUU for me?
as you are in recovery fastboot commands will not work try adb ones:
adb reboot bootloader
download fastboot commander you can find info there
kotag82 said:
as you are in recovery fastboot commands will not work try adb ones:
adb reboot bootloader
download fastboot commander you can find info there
Click to expand...
Click to collapse
Okay entered the command and now the phone cant be recognized in any ways again. Tried running RUU right after boot but still error 170. Cant get the phone visible to ADB again..
do you have goldcard? download WWE RUU 2.29 and try do it blind google some videos as pb99200 method is shown, how to use pb99200 method see bortak guide from stickies... im off now till wednesday

[SOLVED] [Q] Can't charge, even with CWM 5.8.3.1

tl;dr: Apparently, I can't charge my phone with CWM 5.8.3.1. I need 30% to recover my HTC One X.
(I found the solution. See at the end)
So I bricked my phone.
I need to use the RUU to recover it. To use the RUU, I need at least 30% of battery.
I can boot to hboot, fastboot, recovery and HTC white screen.
I installed CWM 5.8.3.1.
On hboot and fastboot, it doesn't seem to charge.
On the HTC screen, I see the red light, but after a while, it just shuts down (empty batter I guess).
On revocery (CWM 5.8.3.1), after ~20 minutes, it shuts down (no red light while in recovery).
The max I can get is 3698mV (from fastboot getvar battery-voltage).
Then `fastboot getvar battery-status` tells me "low" (sometimes "good" for a couple of minutes).
I tried charging with the HTC charger (socket) and with my computer.
Questions:
- any alternative method to charge my phone?
- how much is 30%? I think 3690mV is 20%.
- is it a know problem that some phones can't charge even with WM 5.8.3.1?
- how can I know, for sure, that my phone is charging? Is using `fastboot getvar battery-voltage` the right way to do it?
Solution:
1) Make sure to have CWM 5.8.3.1. You don't need to be in recovery mode to charge. But you need CWM.
2) unplug the phone. switch off the phone via the fastboot menu. Do it twice if it reboots
3) plug your phone once off. Wait 3 hours. (red light). It works because your have CWM 5.8.3.1 installed.
In the meantime, run the RUU software (but don't click on any button). Find the rom.zip file somewhere in %TEMP%.. Extract boot_signed.img and recovery_signed.img (you need to use 7zip)
4) after 3 hours, your phone should be > 4000mV
5) fastboot flash boot boot_signed.img
6) fastboot flash boot recovery_signed.img
7) relock your phone: fastboot oem lock
8) Use the RUU software
9) get a beer.
Sorry to hear that.
Post the same in the official cwm thread, so someone can help you.
Sent from my HTC One X using xda premium
Hi,
I had a similar issue yesterday when I was resurrecting my phone from almost dead. have a read, I updated it with what I did to get the RUU flashed.
http://forum.xda-developers.com/showthread.php?t=1643483
i thought it charged but didn't show a light. if it isn't charged after a few hours, then i would ask in the CWM thread to let them know it isn't working.
solved
Ok, I managed to unbrick my phone (yeah!).
I have updated the original post with the solution.
Cosmicovertones, I have been reading your other messages on other threads. It helped me a lot. Thank you for that!
No problem! Glad my bad experience is of some help to others!!
amunhakon said:
Ok, I managed to unbrick my phone (yeah!).
I have updated the original post with the solution.
Cosmicovertones, I have been reading your other messages on other threads. It helped me a lot. Thank you for that!
Click to expand...
Click to collapse
Congrats mate!
Sent from my HTC One X using xda premium
HELP
i have an HTC one X+ 64g (if that matters) US version. The problem I am having is I recently dropped it and when I must have knocked something lose inside of the charging port. I know that it has the pogo pin charging option for the international version ( supposedly slightly larger than US version) and the only dock with pogo pins i can find is for that version. I need to know if there is a Pogo pin charge dock for the version I have and if not what are the 5 little connectors on back for and is there an alternate charging method? PLEASE HELP ME!
P.S Has anyone else with the HTC one x experienced the problem with noise cancelling speaker?? My phone only worked on speaker, from what I have read it was a pretty common problem with the phone.
signed
Sad HTC owner :crying::crying:

I think I just ****ed my phone

All was working fine until I installed the 3-dot removal on ODEXED rom then it will never boot again! just hanging on boot. so i ****ed my recovery aswell. All i have now is fastboot which is always telling me BATTERY TOO LOW no matter how long i keep it on charge. I can't flash anything neither use RUU. When I click "switch off" in boot menu it will just restart and bootloop. I don't know how to charge my battery so I can use RUU again. Please any help will be much appreciated!
Jack Barrett said:
All was working fine until I installed the 3-dot removal on ODEXED rom then it will never boot again! just hanging on boot. so i ****ed my recovery aswell. All i have now is fastboot which is always telling me BATTERY TOO LOW no matter how long i keep it on charge. I can't flash anything neither use RUU. When I click "switch off" in boot menu it will just restart and bootloop. I don't know how to charge my battery so I can use RUU again. Please any help will be much appreciated!
Click to expand...
Click to collapse
This may be of assistance: http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash
Once you are back up and running, this is the 3 dot removal you need for odexed 1.29.401.11 if that's what version your on
http://forum.xda-developers.com/showthread.php?p=26162691
Sent from my HTC One X using Tapatalk 2
bogfather said:
Once you are back up and running, this is the 3 dot removal you need for odexed 1.29.401.11 if that's what version your on
http://forum.xda-developers.com/showthread.php?p=26162691
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Exactly this version. But I've seen odexed later after I installed it.
I was able just to "erase cache" and unlock it. Then flash recovery. Now its in recovery and I'm waiting for it to charge. Hopefully it will.
Jack Barrett said:
Exactly this version. But I've seen odexed later after I installed it.
I was able just to "erase cache" and unlock it. Then flash recovery. Now its in recovery and I'm waiting for it to charge. Hopefully it will.
Click to expand...
Click to collapse
Once you have the latest CWM you can charge the phone whilst it's off. After that you can flash a ROM/run a RUU and get it back up and running.
rogersnm said:
Once you have the latest CWM you can charge the phone whilst it's off. After that you can flash a ROM/run a RUU and get it back up and running.
Click to expand...
Click to collapse
I was waiting till now and still nothing, ruu starts, erasing everything, sending and when its time to install it says battery low and stops.
still no luck
Jack , take a look here and report back! http://forum.xda-developers.com/showthread.php?t=1609190
Cheers~
I've tried everything. Now im at phase in bootloader - battery very low again. It's not charging from bootloader neither when I start it. Recovery is not working too + I can't unlock it because of the battery. Tried to shut down - not working. HTC made that phone crap because of the internal battery! I hope there will be solution or I have to return it to them,.
Jack Barrett said:
I've tried everything. Now im at phase in bootloader - battery very low again. It's not charging from bootloader neither when I start it. Recovery is not working too + I can't unlock it because of the battery. Tried to shut down - not working. HTC made that phone crap because of the internal battery! I hope there will be solution or I have to return it to them,.
Click to expand...
Click to collapse
To be fair its not HTC's fault, you did do something that they didn't intend.
Also don't charge from the bootloader it needs to be completely off, hold power and volume up to force it off.
Sent from my HTC One X using xda premium
I put it in bootloader to charge - it failed and switched off. Turned on bootloop to charge - same story. Tried with clockworkmod latest - same story. So I was going to send it back. Until I switched the usb port on the PC - then the battery problem was not there! I WAS ABLE TO USE RUU! That's how I fixed it.

[SOLVED] Bricked HTC One X, not charging cannot RUU less than 30% battery

Hi guys, im new here and I would like to seek help to fix my phone. I searched for similar threads but like this but my situation is different.
So I bricked my HOX last night (long story and because of the other things I did in panic some of which I cant remember a full story may not be relevant) but here is my situation
Now my battery says its too low to flash so I cant RUU flash
Its also re-locked and because battery is low, I cant flash the unlock (FAILED: battery low)
Im also not sure which CWM version I have. I do remember I flashed 5.8.4.0 at some point but Im not too sure if I overwrote with another. (So im not sure which CWM I have installed)
All these I tried today thinking I have 30% battery because I left the phone plugged to the wall last night but apparently the phone didnt charge thats why Im in this situation (battery too low to flash)
Now I managed (I think so) to turn off the phone, the screen isnt on (But there is no red light). But I will leave it plugged to the wall anyway (using HTC cable and charger)
edit: the phone screen is on, im leaving it plugged to the wall and there is this red warning saying battery level is too low to flash (so Im not sure if its charging)
Anything I can do to fix this problem?
Thanks!
Re: Bricked HTC One X, not charging cannot RUU less than 30% battery
waway625 said:
Hi guys, im new here and I would like to seek help to fix my phone. I searched for similar threads but like this but my situation is different.
So I bricked my HOX last night (long story and because of the other things I did in panic some of which I cant remember a full story may not be relevant) but here is my situation
Now my battery says its too low to flash so I cant RUU flash
Its also re-locked and because battery is low, I cant flash the unlock (FAILED: battery low)
Im also not sure which CWM version I have. I do remember I flashed 5.8.4.0 at some point but Im not too sure if I overwrote with another. (So im not sure which CWM I have installed)
All these I tried today thinking I have 30% battery because I left the phone plugged to the wall last night but apparently the phone didnt charge thats why Im in this situation (battery too low to flash)
Now I managed (I think so) to turn off the phone, the screen isnt on (But there is no red light). But I will leave it plugged to the wall anyway (using HTC cable and charger)
edit: the phone screen is on, im leaving it plugged to the wall and there is this red warning saying battery level is too low to flash (so Im not sure if its charging)
Anything I can do to fix this problem?
Thanks!
Click to expand...
Click to collapse
I had a similar issue. Although you are a silly bugger for panicking and then forgetting what you did.
The only things I can suggest, assuming you still have 5.8.4.0 I think it charges in this version? See of you can do that...
If not, I am not sure.
I assume you did a nandroid and have tried restoring it?
Did you remember to flash the boot.img before installing the ROM that I assume bricked your phone?
sent from my bladed one x
archie winnington-ingram said:
I had a similar issue. Although you are a silly bugger for panicking and then forgetting what you did.
The only things I can suggest, assuming you still have 5.8.4.0 I think it charges in this version? See of you can do that...
If not, I am not sure.
I assume you did a nandroid and have tried restoring it?
Did you remember to flash the boot.img before installing the ROM that I assume bricked your phone?
sent from my bladed one x
Click to expand...
Click to collapse
Im not sure if the current one is 5.8.4.0. I do remember flashing it last night but maybe it did'nt work coz after that I charged the phone overnight (well for about 5 hours or so) and it still "battery too low to flash"
as for nandroid, I know I pressed backup at then the CWM but that was everything got bricked. Now I dont know if its still relevant (when the phone was unlocked I did go to CWM backup and it said phone is restored but that didnt help. Nothing happened and I could not boot)
I do remember that I flashed with boot.img from the "aokp_ICJ421-V2.0" but then again Im not sure if thats relevant since I did so many flashing and unflashing and what not :crying:
So now Im in a situation where I want to do the RUU but I cant because battery is too low, and Im not sure if its charging because Im not sure what my CWM version is but I cant flash the CWM to latest anyway because 1. phone is relocked 2. phone battery is too low to flash to either unlock or update CWM version :crying:
edit:
The RED LED light is on. Is it charging? But the screen is also on =(
Re: Bricked HTC One X, not charging cannot RUU less than 30% battery
Oke do this :
Download this file
http://db.tt/aLqeTpPO
Copy it to your fastboot folder, put the phone in the bootloader and execute the file. It will continuously reboot the phone and charge it little by little. Leave it for an hour or so and check how the battery is doing
Re: Bricked HTC One X, not charging cannot RUU less than 30% battery
You can always try a universal charger.
Re: Bricked HTC One X, not charging cannot RUU less than 30% battery
jazib360 said:
You can always try a universal charger.
Click to expand...
Click to collapse
No mate don't use a universal charger, chances of draining the batt with them are even bigger ..... They often can't supply the needed power to the phone. Especially when the screen is on
Hi, how do i execute the file? is it by cmd? what is the command to type? thanks
Re: Bricked HTC One X, not charging cannot RUU less than 30% battery
Just execute the batch file by double clicking it.....from the fastboot folder
Mr Hofs said:
Just execute the batch file by double clicking it.....from the fastboot folder
Click to expand...
Click to collapse
thanks! it worked. and I only needed a couple of minutes. apparently Im just a few percentages below 30%
done RUU update also and now im in my phone..thanks thanks thanks
Nice mate ! Glad i could help
Mr Hofs said:
Nice mate ! Glad i could help
Click to expand...
Click to collapse
Always helpful, like a white knight. Kudos to you Mr. H
Sent from...... The Milky Way
waway625 said:
thanks! it worked. and I only needed a couple of minutes. apparently Im just a few percentages below 30%
done RUU update also and now im in my phone..thanks thanks thanks
Click to expand...
Click to collapse
i'm now try this and myphone is continuesly reboot and how can i determine mybattery status is enough to RUU? mybattery voltage now is 3356mv and is continuesly rising, and how much mv must i've to RUU back myphone?
Let it rise up to 3900 then run the ruu
I've done everything you said Mr. H but the cmd prompt says "waiting for device" what shall I do? :crying:
1LifeG said:
I've done everything you said Mr. H but the cmd prompt says "waiting for device" what shall I do? :crying:
Click to expand...
Click to collapse
Update the HTC drivers and uninstall HTC sync, bit leave the driver on the pc
Mr Hofs said:
Update the HTC drivers and uninstall HTC sync, bit leave the driver on the pc
Click to expand...
Click to collapse
Ok I updated the drivers and it looks like it would work. THANKS :victory:
---------- Post added at 01:16 PM ---------- Previous post was at 01:03 PM ----------
1LifeG said:
Ok I updated the drivers and it looks like it would work. THANKS :victory:
Click to expand...
Click to collapse
but it does not start in the bootloader but in the normal os
1LifeG said:
Ok I updated the drivers and it looks like it would work. THANKS :victory:
but it does not start in the bootloader but in the normal os
Click to expand...
Click to collapse
Nedded to relock now it works perfectly :victory::victory::victory:
help guys!!! HTC ONE X Bricked!!
Hey, im too darn frustrated here..
im sry abt tht but i bricked my htc one x last week an im not able to restore it to the stock recovery cos i wiped all the factory settings an i didn't have any kind off back up!
an i tried the RUU file restore techinique to restore the phone but not able do it shows some signature error..
where i had followed the tutorials as given..
please link me the page where i can find a solution to this ?
with a detailed tutorial as to how to solve this problem now.
Thxnks for ur time to read my mess..
waiting for asap for a solution....
Mr Hofs said:
Oke do this :
Download this file
http://db.tt/aLqeTpPO
Copy it to your fastboot folder, put the phone in the bootloader and execute the file. It will continuously reboot the phone and charge it little by little. Leave it for an hour or so and check how the battery is doing
Click to expand...
Click to collapse
i'm trying this but look what i found when i'm gone to flash an ruu zip file
failed <remote :12 signature verify fail>
http://dl.xda-developers.com/attach...147e491f093d2d/523d8dd1/2/2/7/2/3/9/1/cmd.JPG
Mr Hofs said:
Oke do this :
Download this file
http://db.tt/aLqeTpPO
Copy it to your fastboot folder, put the phone in the bootloader and execute the file. It will continuously reboot the phone and charge it little by little. Leave it for an hour or so and check how the battery is doing
Click to expand...
Click to collapse
it work 100 %
thanks

Categories

Resources