Develop Bugs

Need Battery Help

Okay... i've tried a bunch of stuff now and i'm stuck. I was doing the 2.3.2 to root to 2.3.3/4 flash upgrade process. my battery was charged to 100%, but now (as typically happens with this process) it says 0% and closes the phone.
I've tried pulling the battery as described in the walkthrough, but it doesn't solve it.
I can't charge it because the battery is at 100%. does anyone know how to manually discharge the battery, or have any other suggestions?

I have the same problem

further information - the battery calibration app changes nothing. i (while plugged in) rooted and downloaded the battery calibration app (this one https://market.android.com/details?id=com.nema.batterycalibration&feature=search_result), turned off the wait til 100% and hit calibrate. nothing changed.
Any tips on manually wiping the battery stats? my phone has been plugged in for 2 hours and still says 0%.
---------- Post added at 05:25 PM ---------- Previous post was at 05:05 PM ----------
Further, after the above thing where i did the battery calibration, then left the battery out of the phone for 15 minutes, put it back in, still says 0% and shuts off (not plugged in).
I need some suggestions here.

and further further, i went in with root explorer and deleted the batterystats.bin file manually from data/system. this hasn't worked either.
I'm about to try to drain the battery by letting it sit for a couple days, but as there's no load i'm not sure how successful this will be. again, any suggestions would be great.

i have the same issue when flashing 2.3.4 then back to 2.3.2,after gingerbreak reboot the battery is 0%

flash back to 2.3.2, root it with gingerbreak. instal root explorer or something likewise, go to Data-> System -> Batterybins.bin and delte batterybins.bin. after reboot it should be fixed again

flashed 2.3.2. installed explorer. went to my sd card, installed gingerbreak. rooted. reboot. installed root explorer. deleted batterystats.bin. shut down phone. pulled battery for 5 minutes. replaced battery.
boots to 0% and dies.
---------- Post added at 11:03 PM ---------- Previous post was at 10:58 PM ----------
of note, it *always* boots, so it definitely a software file issue. i'm trying to charge it with my sim pulled. whenever it boots without being plugged in, or when i pull the plug, it always announces that there's no sim card first, so i'm trying anything.
can someone point me to a rogers branded firmware in case i have to return this?
---------- Post added at 11:58 PM ---------- Previous post was at 11:03 PM ----------
okay, flashed 2.3.4 and still no luck. battery just sits there at zero.
this f*cking sucks.

im in the same vote as you im trying to do a phone repair to see if that will work. not fun at all

zombiej79 said:
im in the same vote as you im trying to do a phone repair to see if that will work. not fun at all
Click to expand...
Click to collapse
Just tried. It tells me there is no software for my phone.
Next up, install one of these two: http://forum.xda-developers.com/showthread.php?t=1042963&highlight=lt15a and see. i'm basically going to stop f*cking with it as soon as i get my battery back. screw root and updates, i've been without a phone for less than 24 hours but this is stressing me the hell out.

yeah tried the repair tried a few diffrent firmwares the orignal rogers firmware still 0% deleted battery.bin file still 0% not super happy thats for sure
---------- Post added at 02:27 AM ---------- Previous post was at 01:46 AM ----------
went back to 2.3.4 still 0% wow soo annoying im pretty choked about it. dont know what else i can do.

zombiej79 said:
yeah tried the repair tried a few diffrent firmwares the orignal rogers firmware still 0% deleted battery.bin file still 0% not super happy thats for sure
---------- Post added at 02:27 AM ---------- Previous post was at 01:46 AM ----------
went back to 2.3.4 still 0% wow soo annoying im pretty choked about it. dont know what else i can do.
Click to expand...
Click to collapse
i'm trying the last thing we have left - attempting to drain the battery over time to see if that sorts it. otherwise i've got a POS that i have to return to Rogers.

mine shuts down as soon as i unplug it so i dont know what the issue is im with rogers too so maybe its something to do with their phone. or what they have done to it. annoying though. hoping it will fix itself cause ive tried everythign else i can think of. dosent even feel like the battery is getting warm when plugged in. the repair option on the pc software didnt seem to do much either.

can we just confirm symptoms? here's mine:
1) turn it on
2) get SE screen
3) get swirly animation
4) boots to 0%
5) says mounting sd card - network is rogers
6) then it says no sd card, no sim card, no service
7) and craps out seconds later.
at this point, like i said, i'm gonna turn it on every time i think to until it won't boot anymore, then try charging it again. if that doesn't work i'm going to flash back to stock (hopefully rogers) and tell them "it broke"
its still bootloader and simlocked, so they should swap it before they notice i tinkered with it (cross your fingers).

yep thats exactly what happens to me even when i flash back to the stock rogers firmware i still get 0% and it dies as soon as it starts. mine is boot and sim locked too
my girlfriend has the same phone so i tried her battery that was charged still the same thing 0% and it shuts down.

dude, i tried the same thing
flashed 2.3.4... dont like it and want to go back
battery 0%...
Sony f* us good..
Man, I'm so choked..
Can anyone help me?

battery problem is also happening for me... (
but that was not on first boot when i flash the rom
it was after i gain root access...
now i dont know what to do...

There must be a way to fix this.
It's definitely a software problem.
I believe sony did this on purpose so root cannot be accessed.

guyz if any one come up with a solution please share for other....
(

meeaaoon said:
guyz if any one come up with a solution please share for other....
(
Click to expand...
Click to collapse
O， I get the same problem like you guys .And my phone isn't by ROGER or ant other carriers,I'll wait here for a solution with you guys.

So you guys got this problem after you tried to went back to the 2.3.2 from the 2.3.4?

[Q] Need help may have bricked my one X

So I am totally lost. Have exhausted all my knowledge on these issues, but i will take u guys through my process step by step.
Right now my problem is that i am unable to charge my one x in any way. it will only respond to being connected through my pc and obviously that wont charge very well. My phone will boot to the home screen but will go from being 35% charged to 0% and just reboot. what lead up to this was my installing android revolution 1.2.2 along with the interim clockwork mod. Upon reboot is where all the problems began. I accidently forgot to wipe before installing and now this is where im at. Cant boot into recovery. cant load default recovery because battery is too low. nothing except this impossible battery screw up is all i get. and now oncve i unplug my phone from pc, its shuts down after a few moments with no charge. Im at my wits end guys. anyone know what i can do?

These threads may help:
http://forum.xda-developers.com/showthread.php?t=1596155
http://forum.xda-developers.com/showthread.php?t=1599748

chukwu77 said:
So I am totally lost. Have exhausted all my knowledge on these issues, but i will take u guys through my process step by step.
Right now my problem is that i am unable to charge my one x in any way. it will only respond to being connected through my pc and obviously that wont charge very well. My phone will boot to the home screen but will go from being 35% charged to 0% and just reboot. what lead up to this was my installing android revolution 1.2.2 along with the interim clockwork mod. Upon reboot is where all the problems began. I accidently forgot to wipe before installing and now this is where im at. Cant boot into recovery. cant load default recovery because battery is too low. nothing except this impossible battery screw up is all i get. and now oncve i unplug my phone from pc, its shuts down after a few moments with no charge. Im at my wits end guys. anyone know what i can do?
Click to expand...
Click to collapse
I assume you were on 1.19 software? This happened to a friend yesterday. He ended up fastboot erase cache. Fast boot reboot bootloader. Get into recovery and plug up to ac power. The light comes on for a min. Or so then goes off. When it goes off unplugg it then plug it back in. Keep this up till you have some juice. Then fastboot flash the stock recovery relock bootloader, then get ruu 1.26.707. Run that ruu and it should boot. After that you can flash all the roms you want.
Sent from my HTC One X using XDA

Thanks so much, I will try and let u guys know what is going on. FYI i dont see a fastboot erase cache on my screen so how would i go about doing that?

So i locked my oem back before i could boot stock revocery and stock ruu. anyone know how i would ebable to unlock my oem. ADB doesnt appear to re open it with the unlock command. i get a command error message. And yes the bin file from htc is in the fastboot folder. smh

I cant get a charge and the fastboot wont let me unlock oem or load a new recovery.... what now?

cmon guys, i spent 10 hours trying to fix this yesterday, im close to just chucking this thing into the garbage and going back to my nexus. someone please give a little help. i cant charge the phone so i cant load any stock RUU. fastboot is pretty much useless right now. nothing seems to do anything other than show a list of commands when i try to unlock oem again. im desperate so someone please help

chukwu77 said:
cmon guys, i spent 10 hours trying to fix this yesterday, im close to just chucking this thing into the garbage and going back to my nexus. someone please give a little help. i cant charge the phone so i cant load any stock RUU. fastboot is pretty much useless right now. nothing seems to do anything other than show a list of commands when i try to unlock oem again. im desperate so someone please help
Click to expand...
Click to collapse
I don't know what to tell you bro. If you locked the bootloader before putting stock recovery back on the phone. An ruu won't work anyway. Have you tried fastbooting a system.IMG and a boot.IMG. to see if it might boot? If you have your bin file from when you first unlocked. Try sending that again to unlock. Hopefully someone will pop in and give you a hand.
Sent from my HTC One X using XDA

what commands should i use to try to get it back to normal? everything is saying my battery is too low, which really thats what is keeping me from doing anything to help the situation. I need to charge but none of the threads i have read with steps for charging have worked

chukwu77 said:
what commands should i use to try to get it back to normal? everything is saying my battery is too low, which really thats what is keeping me from doing anything to help the situation. I need to charge but none of the threads i have read with steps for charging have worked
Click to expand...
Click to collapse
Did you do a backup after brick?
I have a copy of the main files... (data.img, system.img and boot.img).
i Use this commands:
Examples
Manual Nandroid restore
Make a Nandroid backup, and copy the folder off your SD card to your desktop.
cd ~/Desktop/path/to/backup/
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
MORE INFO HERE.
For the battery... try a charger with little more volts or amperes... you can buy some usb chargers on any electronic store.

thanks i will get on it and let u know what happens. Much appreciated! I did not do a backup after brick but before brick i did. I am using the transformer prime charger its a quad core tablet and it reads as having higher volts/amp than all my others.

your one x stills bricked?
No solution?

[TUT] How to really get battery when you brick your HOX.

Well, i discover it because i brick my phone haha now i share it to you.
IF YOU HAVE ANY UNSIGNED RECOVERY:
1.- GO TO RECOVERY
2.- FORMAT SYSTEM
3.- RESTART NORMALLY
4.- YOUR PHONE WILL STOPS IN "HTC QUIETLY BRILLIANT" SCREEN (or any other custom roms screens, like villain for example).
5.- PUT YOUR PHONE TO CHARGE (no light notification appears)
6.- LET IT CHARGE FOR A COUPLE HOURS (i put mine to charge for a complete night)
7.- Now restore your RUU, Flash, etc...
IF YOU HAVE SIGNED RECOVERY:
1.- GO TO FASTBOOT
2.- HIT "SHUT DOWN"
3.- WITH THE POWER OFF PUT IT TO CHARGE
4.- RED LIGHT NOTIFICATION SHOWS THE CHARGING PROGRESS.
5.- NEXT DAY YOU WILL SEE A SOLID GREEN LIGHT NOTIFICATIONS FOR A COMPLETE CHARGE.
PD: Sorry for ortography, im from Chile, my native speaking is spanish but i want to share my knowledge with XDA COMMUNITY !
PD2: The charging process is slower than the normal charging process, remember that you have the splash screen with full bright.

this one is the completely yes for me, been through this process and successfully get my one-x back by the way mentioned.
highly recommended!!

Onepagebook said:
this one is the completely yes for me, been through this process and successfully get my one-x back by the way mentioned.
highly recommended!!
Click to expand...
Click to collapse
Which one of the two method did you use ?
---------- Post added at 01:06 PM ---------- Previous post was at 01:01 PM ----------
wolfraim said:
Well, i discover it because i brick my phone haha now i share it to you.
IF YOU HAVE ANY UNSIGNED RECOVERY:
1.- GO TO RECOVERY
2.- FORMAT SYSTEM
3.- RESTART NORMALLY
4.- YOUR PHONE WILL STOPS IN "HTC QUIETLY BRILLIANT" SCREEN
5.- PUT YOUR PHONE TO CHARGE (no light notification appears)
6.- LET IT CHARGE FOR A COUPLE HOURS (i put mine to charge for a complete night)
7.- Now restore your RUU, Flash, etc...
IF YOU HAVE SIGNED RECOVERY:
1.- GO TO FASTBOOT
2.- HIT "SHUT DOWN"
3.- WITH THE POWER OFF PUT IT TO CHARGE
4.- RED LIGHT NOTIFICATION SHOWS THE CHARGING PROGRESS.
5.- NEXT DAY YOU WILL SEE A SOLID GREEN LIGHT NOTIFICATIONS FOR A COMPLETE CHARGE.
PD: Sorry for ortography, im from Chile, my native speaking is spanish but i want to share my knowledge with XDA COMMUNITY !
Click to expand...
Click to collapse
Thanks for sharing, added to my disaster recovery thread

well at very first moment I have paul's 5818 recovery and I have not tried ,
so I asked PG101 and he told me the second way so I tried with 2nd one there.
cuz first one still not let you feel secure I think.Mostly the 2nd one is the one everyone need to go if you encounter that low battery state

Onepagebook said:
well at very first moment I have paul's 5818 recovery and I have not tried ,
so I asked PG101 and he told me the second way so I tried with 2nd one there.
cuz first one still not let you feel secure I think.Mostly the 2nd one is the one everyone need to go if you encounter that low battery state
Click to expand...
Click to collapse
If you have CUSTOM RECOVERY like 5.8.2.7 or any other, you cant charge in any bootloader screen, or fastboot, the only way to charge when you DON'T HAVE the signed recovery, is in the HTC QUIETLY BRILLIANT SCREEN or IN ANY SPLASH SCREEN (IF YOU HAVE INSTALLED VILLAIN ROM OR ANY OTHER).

wolfraim said:
Well, i discover it because i brick my phone haha now i share it to you.
IF YOU HAVE ANY UNSIGNED RECOVERY:
1.- GO TO RECOVERY
2.- FORMAT SYSTEM
3.- RESTART NORMALLY
4.- YOUR PHONE WILL STOPS IN "HTC QUIETLY BRILLIANT" SCREEN (or any other custom roms screens, like villain for example).
5.- PUT YOUR PHONE TO CHARGE (no light notification appears)
6.- LET IT CHARGE FOR A COUPLE HOURS (i put mine to charge for a complete night)
7.- Now restore your RUU, Flash, etc...
IF YOU HAVE SIGNED RECOVERY:
1.- GO TO FASTBOOT
2.- HIT "SHUT DOWN"
3.- WITH THE POWER OFF PUT IT TO CHARGE
4.- RED LIGHT NOTIFICATION SHOWS THE CHARGING PROGRESS.
5.- NEXT DAY YOU WILL SEE A SOLID GREEN LIGHT NOTIFICATIONS FOR A COMPLETE CHARGE.
PD: Sorry for ortography, im from Chile, my native speaking is spanish but i want to share my knowledge with XDA COMMUNITY !
PD2: The charging process is slower than the normal charging process, remember that you have the splash screen with full bright.
Click to expand...
Click to collapse
can you help me my one x (evita, north american version) is completely dead i lash a rom (a wrong one to be exact) at a 25% charge and now my one x is dead cant get to recovery bootloader wont charge nothing can you help me fix this i appreciate it

mr.5106411 said:
can you help me my one x (evita, north american version) is completely dead i lash a rom (a wrong one to be exact) at a 25% charge and now my one x is dead cant get to recovery bootloader wont charge nothing can you help me fix this i appreciate it
Click to expand...
Click to collapse
I read a way in tutorial, the thing is that when you get the splash screen ...like a bootloop, the phones charges, and then you go back to bootloader, do that severals time, with new recovery, if u manage to get there, phone start charging.
If u dont have new recovery and u can put phone to "fastboot" mode, try to flash it using " fastboot recovery recoveryNAME.img" then...stay in recovery all Night so phone will get full charge...
Then do whatever you want.
Firma....firme aqui xxxxxxxx

I left my phone plugged into USB all night in bootloader (I read that was the best way to get initial charge) but this morning it had just powered down, I'm guessing due to no charge?
Got it back on today and plugged it into the mains adapter whilst it was in bootloader, the red (constant) light stayed on and nothing seems to be changing. I'm going out now so I did fastboot>power down and left it in the wall. There is no light displayed at all, I'm just going to leave it and hope the charge comes back over the next few hours? Or do I need to do something else? My recovery is corrupt, I cant boot into it.

[★] said:
I left my phone plugged into USB all night in bootloader (I read that was the best way to get initial charge) but this morning it had just powered down, I'm guessing due to no charge?
Got it back on today and plugged it into the mains adapter whilst it was in bootloader, the red (constant) light stayed on and nothing seems to be changing. I'm going out now so I did fastboot>power down and left it in the wall. There is no light displayed at all, I'm just going to leave it and hope the charge comes back over the next few hours? Or do I need to do something else? My recovery is corrupt, I cant boot into it.
Click to expand...
Click to collapse
If you still don't manage to come right, try this

ClydeB1 said:
If you still don't manage to come right, try this
Click to expand...
Click to collapse
Cheers mate, gonna try this in a min. I got home and I think it had run flat again, I hooked it up to USB and now its sitting in Fastboot usb and the orange light is flashing! (charging?) Should I just leave it for a while now or give this power cycle a go? Also is there a way to check my battery level using an adb command or something? Cheers

[★] said:
Cheers mate, gonna try this in a min. I got home and I think it had run flat again, I hooked it up to USB and now its sitting in Fastboot usb and the orange light is flashing! (charging?) Should I just leave it for a while now or give this power cycle a go? Also is there a way to check my battery level using an adb command or something? Cheers
Click to expand...
Click to collapse
If you are going to use this method, perhaps try using a wall charger as it will push more juice. For the batch file method, I know it has worked for a few users.
The only command I know to check battery capacity is adb shell cat /sys/class/power_supply/battery/capacity, but I guess it won't help if you are in fastboot.

ClydeB1 said:
If you still don't manage to come right, try this
Click to expand...
Click to collapse
Didnt realise it displays the charge on the cmd, just a matter of time now Im hoping
---------- Post added at 05:38 PM ---------- Previous post was at 05:30 PM ----------
ClydeB1 said:
If you are going to use this method, perhaps try using a wall charger as it will push more juice. For the batch file method, I know it has worked for a few users.
The only command I know to check battery capacity is adb shell cat /sys/class/power_supply/battery/capacity, but I guess it won't help if you are in fastboot.
Click to expand...
Click to collapse
The batch file is in full swing and i'm getting about 3mV every time, so looks like its working. I need to go out for a bit so I think i'll leave it to get a bit over 3.8V. Then when I come back, unlock the bootloader, then flash http://forum.xda-developers.com/showthread.php?t=1594819 cwm recovery and get it charging from mains yeah?

[★] said:
Didnt realise it displays the charge on the cmd, just a matter of time now Im hoping
---------- Post added at 05:38 PM ---------- Previous post was at 05:30 PM ----------
The batch file is in full swing and i'm getting about 3mV every time, so looks like its working. I need to go out for a bit so I think i'll leave it to get a bit over 3.8V. Then when I come back, unlock the bootloader, then flash http://forum.xda-developers.com/showthread.php?t=1594819 cwm recovery and get it charging from mains yeah?
Click to expand...
Click to collapse
Yeah

ClydeB1 said:
Yeah
Click to expand...
Click to collapse
Slight problem, its now going between 3686 and 3687, :S its gets higher occasionally but then drops again. Maybe I should shove it into the wall

[★] said:
Slight problem, its now going between 3686 and 3687, :S its gets higher occasionally but then drops again. Maybe I should shove it into the wall
Click to expand...
Click to collapse
How much is needed to be able to unlock bootloader and flash recovery? I see this corresponds to about 10% according to the thread and they state that you can unlock between 10% and 30%, so perhaps give that a try.
I also saw a thread somewhere where it was suggested to run command fastboot oem rebootRUU and then plug the device into the wall charger like that, but have not had anyone confirm to me if this works.

ClydeB1 said:
How much is needed to be able to unlock bootloader and flash recovery? I see this corresponds to about 10% according to the thread and they state that you can unlock between 10% and 30%, so perhaps give that a try.
I also saw a thread somewhere where it was suggested to run command fastboot oem rebootRUU and then plug the device into the wall charger like that, but have not had anyone confirm to me if this works.
Click to expand...
Click to collapse
Ahah yes you're right, I was reading it at 3.8 not 3.68, bootloader unlocked! Now to try and flash recovery
---------- Post added at 06:50 PM ---------- Previous post was at 06:43 PM ----------
[★] said:
Ahah yes you're right, I was reading it at 3.8 not 3.68, bootloader unlocked! Now to try and flash recovery
Click to expand...
Click to collapse
Went to boot into recovery and just got stuck in the same bootloop!
cmd read
C:\fastboot>fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.i
mg
sending 'recovery' (5742 KB)...
OKAY [ 0.778s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.559s]
finished. total time: 1.337s
Click to expand...
Click to collapse
so it looked successful, but apparently not?

[★] said:
Ahah yes you're right, I was reading it at 3.8 not 3.68, bootloader unlocked! Now to try and flash recovery
---------- Post added at 06:50 PM ---------- Previous post was at 06:43 PM ----------
Went to boot into recovery and just got stuck in the same bootloop!
cmd read
so it looked successful, but apparently not?
Click to expand...
Click to collapse
Run command - fastboot erase cache and then try to boot to recovery again.

ClydeB1 said:
Run command - fastboot erase cache and then try to boot to recovery again.
Click to expand...
Click to collapse
You sir, are a gentleman, thankyou. I'm in CWM but no orange light indicating charging

[★] said:
You sir, are a gentleman, thankyou. I'm in CWM but no orange light indicating charging
Click to expand...
Click to collapse
Pleasure, glad it worked . I don't think the led light works in recovery, but if you are on the latest CWM version 5.8.4.0 then it should charge.

ClydeB1 said:
Pleasure, glad it worked . I don't think the led light works in recovery, but if you are on the latest CWM version 5.8.4.0 then it should charge.
Click to expand...
Click to collapse
I factory reset,wiped cache and dalvik cache and rebooted so I can leave it in htc quietly brilliant screen I hope its charging, currently I just have a constant orange/red light aha

[Q] One X Stuck at bootloader

Hi all. I hope some kind person here can help me get to the bottom of this.
I unlocked my bootloader earlier from htcdev. I then installed super user.
I wanted to install Leedroid ROM so downloaded the files and used fasboot to install the version of boot.img that comes with it. Problem is that I forgot to transfer over the rom zip file to the device before doing it so now I'm stuck. I know, I just got distracted. My fault I know. I just feel totally sick at the thought of just having bought a £450 to have broken it less than a week later.
(I have successfully rooted my old desire and a wildfire in the past without bother so I do have experience of rooting....just looking like and feeling like an idiot now!)
I had a nandriod backup done from before flashing boot.img and tried to restore.. It says restore was successful but it got stuck on the HTC splash screen. Some help would be mighty appreciated.
The bootloader is now locked again but I think I still have CWM recovery installed however I can't access it any more. The phone boots directly into the bootloader and doesn't attempt to boot.
I've tried unlocking the bootloader again but now it says the battery is too low. I keep trying to turn the phone off in fastboot to let it charge but it just starts up again? Any Ideas?As I said I can't get it to charge so I can't unlock the boot loader again. I've tried running stock 1.29 RUU but again not enough juice.
Just to confirm: My HBOOT is 0.94.0000; The bootloader is relocked.
Any help would be very appreciated, I am at my wits end. Thanks in advance

http://forum.xda-developers.com/showthread.php?t=1546970
Try that. download and extract boot.img and then flash the boot.img that should then work. If not try looking for stock roms that are flashable through clock work mod and get hold of that boot.img. hope this helps
Sent from my HTC One X using XDA Premium HD app

Also if you got cwm you can go into it and charge the phone from there
Sent from my HTC One X using XDA Premium HD app

This is just a thought, maybe when the battery dies the phone will switch off on its own, and then u can charge it.

malcovitch said:
Also if you got cwm you can go into it and charge the phone from there
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for all the replies. Unfortunately, I can no longer access CWM. When I go to recovery it shows the "Quietly Brilliant" Screen then goes to fastboot menu, no CWM?

UPDATE: Ok, I have managed to unlock my bootloader again. In another thread mevorach advised running a batch script that displays the voltage and reboots the phone. Id created this script and waited until the phone charged up enough, then I ran the unlock command again.
I now have access to CWM again. Feels like I'm starting to get somewhere.
mevorach said:
Hi
I have a solution for you
make a batch file :
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
put this file in the directory where you have fastboot.exe adb.exe and all other
files , also put the unlock.bin file that you have from htcdev
put your phone to bootfsatusb , and run the batch file , you will see the voltage
off the battry each time it loop , after an hour or two you will have enough power(~3.68mv) to unlock it , then charge it and do what ever you want
Click to expand...
Click to collapse

cosmicovertones said:
Thanks for all the replies. Unfortunately, I can no longer access CWM. When I go to recovery it shows the "Quietly Brilliant" Screen then goes to fastboot menu, no CWM?
Click to expand...
Click to collapse
That's because of low battery.
have you read this : http://forum.xda-developers.com/showthread.php?t=1609190
which recovery version that you have ? If it is 5.8.3.1, what you can try is:
attach the charger to it's usb.
the phone will boot to bootloader
scroll to power down
it will shut down
don't take out the usb cable/charger from the phone.
if the phone starts again to bootloader
scroll again to power down
(normally it will stay shut down when doing this power down the second time)
let it charge for an hour.
on PC get ready the fastboot command to unlock the bootloader
fastboot flash unlocktoken Unlock_code.bin and enter
status will show waiting for device
connect your phone and power on
and see whether the "low battery" warning still there.
if successful, unlock the phone (choose yes)
when it reboot - hold power + volume down to force it to bootloader
fastboot flash boot boot.img for the nandroid backup that you restore earlier
once done reboot the phone.
---------- Post added at 02:45 PM ---------- Previous post was at 02:43 PM ----------
cosmicovertones said:
UPDATE: Ok, I have managed to unlock my bootloader again. In another thread mevorach advised running a batch script that displays the voltage and reboots the phone. Id created this script and waited until the phone charged up enough, then I ran the unlock command again.
I now have access to CWM again. Feels like I'm starting to get somewhere.
Click to expand...
Click to collapse
that's good.
what you need now is to flash the boot.img for the nandroid backup that you have which you mentioned you restored earlier. without a correct boot.img for your nandroid backup, you will stuck on "quietly brilliant"

Thanks for your reply,
ckpv5 said:
That's because of low battery.
have you read this : http://forum.xda-developers.com/showthread.php?t=1609190
Click to expand...
Click to collapse
Yes, I've gone through all the pages.
ckpv5 said:
which recovery version that you have ? If it is 5.8.3.1, what you can try is:
Click to expand...
Click to collapse
When I managed to get into CWM I realised I was not on the latest, I have now managed to flash 5.8.3.1
ckpv5 said:
attach the charger to it's usb.
the phone will boot to bootloader
scroll to power down
it will shut down
don't take out the usb cable/charger from the phone.
if the phone starts again to bootloader
scroll again to power down
(normally it will stay shut down when doing this power down the second time)
let it charge for an hour.
on PC get ready the fastboot command to unlock the bootloader
fastboot flash unlocktoken Unlock_code.bin and enter
status will show waiting for device
connect your phone and power on
and see whether the "low battery" warning still there.
if successful, unlock the phone (choose yes)
Click to expand...
Click to collapse
I have managed to get to this step.
ckpv5 said:
when it reboot - hold power + volume down to force it to bootloader
fastboot flash boot boot.img for the nandroid backup that you restore earlier
once done reboot the phone.
that's good.
what you need now is to flash the boot.img for the nandroid backup that you have which you mentioned you restored earlier. without a correct boot.img for your nandroid backup, you will stuck on "quietly brilliant"
Click to expand...
Click to collapse
I tried to restore the boot.img that backed up earlier but it is getting stuck at the "quietly brilliant" screen.
I also tried to restore all of the nandroid backup without success.
Any ideas how I can get a working boot.img to flash?
I am currently leaving the phone on the "quietly brilliant" screen (the charge LED is on) to see if I can get enough charge to restore the stock recovery, lock the bootloader and flash the 1.29 europe RUU. Is this a good plan or should I be trying something else?

Based on my experience, when you're not sure which boot.img belongs to which nandroid, a stock boot.img will work.
But if that also fail then the next best thing to do is flash RUU and make sure you have the right official RUU for your phone. Wrong RUU will not work.

Ok, will do. Thanks for the help
I'm trying to leave the phone on charge for a couple of hours, I'll then try flash the boot_signed.img file from the RUU.zip andfailing that I'll try the whole RUU.

Same situation here...
cosmicovertones said:
I'm trying to leave the phone on charge for a couple of hours, I'll then try flash the boot_signed.img file from the RUU.zip andfailing that I'll try the whole RUU.
Click to expand...
Click to collapse
I'm having the exact same problems, and have pretty much done the same steps in my attempts to get the phone back to life. Current status is that it's locked and can't unlock it due to low battery, but that .bat file seems to be helping - battery voltage is going up, so eventually I should be able to do something.
My plan however is to try RUU (tried everything else already, when I had battery and the phone was unlocked and had clockworkmod).
Anyway please keep this thread up to date with your progress.
If you broke your phone in the first week...well, I opened the box of mine 15 minutes before bricking it, hadn't even installed the SIM card (I bought it from an amazon seller and he sent me the Asian version, Thai keyboard and all - that's what started all this).

Ok... so I flashed the boot_signed.img file from the official 1.29 ruu. The phone then rebooted and again froze on the "quietly brilliant" screen. I then locked the bootloader again and rebooted. This time it booted fine
Once booted I left it to charge fully, I then was able to run the 1.29 RUU for my phone.
Next step I unlocked the bootloader again and flashed CWM 5.8.3.1. Performed a nandroid backup and flashed the super user zip file.
It is fully functioning up to this point now.
My next step is to follow ALL the steps (this time lol) to get leedroid one xtreme v5 rom installed again.
I'm getting the phone back to 100% charge before doing the next steps, just incase I need to undo anything I REALLY don't want to run into the low battery issue again.

cfsmp3 said:
I'm having the exact same problems, and have pretty much done the same steps in my attempts to get the phone back to life. Current status is that it's locked and can't unlock it due to low battery, but that .bat file seems to be helping - battery voltage is going up, so eventually I should be able to do something.
My plan however is to try RUU (tried everything else already, when I had battery and the phone was unlocked and had clockworkmod).
Anyway please keep this thread up to date with your progress.
If you broke your phone in the first week...well, I opened the box of mine 15 minutes before bricking it, hadn't even installed the SIM card (I bought it from an amazon seller and he sent me the Asian version, Thai keyboard and all - that's what started all this).
Click to expand...
Click to collapse
As the earlier quote regadring the bat file, you will have enough power(~3.68mv) to unlock it. Once it gets to ~3.689mV you will be able to unlock the phone.
Did you have it unlocked at one point? If so you can use the same unlock file HTC sent you to unlock again.
Once you have it unlocked run the bat script again until the power is around the same level again, then flash cwm 5.8.3.1 through fastboot.
Once you have this you can turn the phone off and plug it into your charger. I had mine plugged in for over an hour. The charge was then enough to flash the boot_signed.img file from the RUU for my phone, and as I said it booted fine.
Hope this all helps, I know exactly how you feel.
My killer mistake was forgetting to transfer the leedroid rom zip to the phone and I wrongly assumed CWM could mount the internal storage as USB to transfer the rom to the phone; like earlier versions.

cosmicovertones said:
Ok... so I flashed the boot_signed.img file from the official 1.29 ruu.
Click to expand...
Click to collapse
Where did you get that file? Digging into %TEMP% or is there an official repository or something?
Why not install the full RUU, by the way, to start over?
Anyway your post gives me hope I'm currently letting the .bat file run - but the plan was to do RUU if at all possible, rather than unlock, add clockworkmod, etc...

I couldn't get it to charge much higher than was required to unlock etc.. so I needed to get CWM installed to get it to charge properly.
Also, I couldnt get the boot_signed.img to flash I assume cause the bootloader is locked.
I got the boot_signed.img by opening the RUU installer but not clicking next just having it open.
Then I got the temp folder on my pc and searched in it for zip files. Only 2 appeared. The rom was called "rom.zip"
I then copied this to my desktop and opened the zip. Then I was able to extract the boot_signed.img file to the fastboot folder on my pc and got it flashed across.
I think you're probably gonna have to unlock the bootloader to fix your problem.

cosmicovertones said:
I couldn't get it to charge much higher than was required to unlock etc.. so I needed to get CWM installed to get it to charge properly.
Click to expand...
Click to collapse
I got some help in IRC on the charge front. Indeed powering off the phone from the FASTBOOT menu *without* having a cable plugged in (otherwise the damn thing won't stay off) puts it in a chargeable state. What I did was plug it in the wall charger for a bit. Then they suggested that when the phone is off you can plug it to the PC and get battery status with adb, which I did - like this:
adb shell cat /sys/class/power_supply/battery/status
adb server is out of date. killing...
* daemon started successfully *
Charging
adb shell cat /sys/class/power_supply/battery/capacity
30
[plugged again to wall charger for a while]
adb shell cat /sys/class/power_supply/battery/capacity
42
So it's looking good. I'll let it charge for a while and once it's done, relock (I just installed cwm again), and try RUU.
cosmicovertones said:
I got the boot_signed.img by opening the RUU installer but not clicking next just having it open.
Then I got the temp folder on my pc and searched in it for zip files. Only 2 appeared. The rom was called "rom.zip"
Click to expand...
Click to collapse
OK, I just did and saved the file somewhere in case it's needed.
We'll see

for the RUU to run successfully you need to flash the stock recovery (to get rid of CWM) and lock the bootloader AFTER you've flashed the boot_signed.img file. This is to get the RUU to run on an unmodified phone.
Once you get that run you can re unlock, flash CWM and super user binaries if you want.
After this experience, I'll be checking and double checking the steps provided in future. What an ass I am!!! ha just goes to prove just cause I was successful on my old htc desire and the gf's wildfire it's no guarantee I know what I'm doing
Also, I've now successfully installed Leedroid One Xtremem V5.1. Just after restoring my apps using titanium backup.
Let me know how you get on
EDIT: I think the reason I had to flash the boot_signed.img file is because I flashed the leedroid boot.img then realised my mistake of not having the rom to flash and to compound the issue relocked the bootloader and the low battery. You might be able to get away with charging and running your RUU. If that fails I would restore stock recovery, lock the bootloader and retry the RUU

cosmicovertones said:
for the RUU to run successfully you need to flash the stock recovery
Click to expand...
Click to collapse
Nope It just needs to be locked, but it was happy to run with cwm installed.
So I got it to work (back to square one, because I still need to change the ROM). I actually did more stuff than needed (because I was trying two approaches as the same time), but in summary:
- That glorious 5 line .bat file works, and allows the battery to charge, so reach a state where you can at least lock/unlock and flash. For me the battery changes from 'low charge' to 'good' at 3615mV.
- You can also turn the phone off from the service menu, but you have to be sure no cable is plugged, or it will turn itself back on in a couple seconds.
- The battery charges if the phone is off, using a wall charger.
- With the phone off, you can still plug in on a PC and find battery status (whether it's charging or not) and current charge (in %) with adb (another command line tool, like fastboot).
- With 30% or more of load, you can run RUU and get the phone back to factory state.
- You can't use a RUU for a different model, if your model is from Asia you need the Asian RUU, you can't just install a European one. You don't like a Vietnamise keyboard? Tough ****.
Anyway, since I know have all the tools and more confidence I'll just go ahead and try again. Starting will a full charge of course

Awesome!! I'm glad you got it to work, and I hope this thread serves as some help for others.
The damn battery charge issue had me worried. That bat file is really a lifesaver!

Thanks for all the info. Hope not to need it but mistakes can be made.

[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