I have my HOX for a couple of months now. It's has been on stock rom for about 2 minutes. I flashed a custom rom as soon as i had it. Everything was working fine until a couple of weeks ago. I think it started after flashing hboot 1.39, or after a couple of times of wiping battery stats (but i'm not sure).
My phone randomly turns off completely. No shutdown or whatever, just off if it was disconnected from the battery. The battery wasn't even close to empty so this was very strange behavior. I tried to start the phone again but it keeps turning off while booting or just after booting. I have tried booting the phone over and over but it won't work. Not until i plug a charger in it. While charging or just after charging the phone works fine. When i'm not charging it keeps working for a couple of hours until it turns off again.
I have tried several roms. None of them changed anything. I have reflashed hboot but it didn't help. Wiping battery stats won't help. That said, wiping battery stats or rebooting the phone changes the battery level almost every time. Battery level could be 71% just before it turns off. Then after a reboot it says 45% (and it turns off again). Next reboot it says 59%, etc... My phone is absolutely useless now. I can't have it plugged in a charger all day.
Is anyone else having these problems?
What's wrong with my phone and how do i fix this? I think HTC won't fix this free of charge (because of flashing) so that's not really an option.
Fetch a last_kmsg for examination. (google)
Sent from my IceCold One X
TToivanen said:
Fetch a last_kmsg for examination. (google)
Sent from my IceCold One X
Click to expand...
Click to collapse
I can't find the file. I tried finding it using the Terminal Emulator app (root access).
Maybe there wasn't any last_kmsg written? I can see the /proc/kmsg log.
[edit]
Tried adb too, but no luck. There is no last_kmsg file. My problem probably doesn't generate that file.
3raser said:
I can't find the file. I tried finding it using the Terminal Emulator app (root access).
Maybe there wasn't any last_kmsg written? I can see the /proc/kmsg log.
[edit]
Tried adb too, but no luck. There is no last_kmsg file. My problem probably doesn't generate that file.
Click to expand...
Click to collapse
via Terminal Emulators:
su {enter]
cat /proc/last_kmsg(space)>(space)/sdcard/last_kmsg.txt {enter}
should be on your SDcard as last_kmsg.txt
treebill said:
via Terminal Emulators:
su {enter]
cat /proc/last_kmsg(space)>(space)/sdcard/last_kmsg.txt {enter}
should be on your SDcard as last_kmsg.txt
Click to expand...
Click to collapse
No, it's really not there.
/proc/last_kmsg: No such file or directory
3raser said:
No, it's really not there.
/proc/last_kmsg: No such file or directory
Click to expand...
Click to collapse
There is. I have attached a screenshot.
Sent from my HTC ViperX
Could it be that you have disabled debugging in your kernel?
I doubt it would disable kmsg though....
Sent from my IceCold One X
I actaully have the same exact problem as you... Turns out its due to Mobile Data. It was fine up until i installed a rom with 3.18 base.
TToivanen said:
Could it be that you have disabled debugging in your kernel?
I doubt it would disable kmsg though....
Sent from my IceCold One X
Click to expand...
Click to collapse
How would i do that? And why is kmsg still working?
Dizy801 said:
I actaully have the same exact problem as you... Turns out its due to Mobile Data. It was fine up until i installed a rom with 3.18 base.
Click to expand...
Click to collapse
So there is no solution? (since you didn't post it)
I formatted everything (even /sdcard) flashed a 3.19 based rom and it seems to be stable now. I have been using it for 3 days now and it did not shutdown. Battery level looks a lot better too. So this could be a solution for others too.
Back again. Phone randomly turns off again.
This time, i have a last kernel log. I actually have 2 (because the phone keeps rebooting).
http://pastebin.com/JS3EUyJB
http://pastebin.com/t7RMBZfh
Another thing is that fastboot tells me my battery is too low to flash anything (at what battery level is that?). When i boot, android tells me that i have a battery level of at least 50%. Everybody keeps telling me that the battery level in android cannot be wrong. I think this battery reading is very wrong and it's one of the causes of the random shutdowns.
I don't know anything about kernel logs. Can anybody tell me if the logs in those links say anything useful?
[edit]
More info about the battery
adb shell cat /sys/class/power_supply/battery/capacity
69
Click to expand...
Click to collapse
C:\fastboot>fastboot getvar battery-voltage
battery-voltage: 3942mV
finished. total time: 0.106s
Click to expand...
Click to collapse
Is this battery-voltage the same as a 69% load?
Is there anyone who can help me with the kernel logs?
Battery to low means under 30%. Can you wipe the batt stats in recovery and reboot the phone into the bootloader ?
A full battery is around 4200 btw
Mr Hofs said:
Battery to low means under 30%. Can you wipe the batt stats in recovery and reboot the phone into the bootloader ?
A full battery is around 4200 btw
Click to expand...
Click to collapse
I charged the phone, so it's not in the same state as yesterday any more. Wiping battery stats never helped me in any way.
My battery stats are messed up any way. I unplugged my phone this morning at 100%. In 4 hours it dropped to 69% and it stayed there for the next 4 hours. It will probably shutdown somewhere in the next couple of hours while it still says 69%.
Related
Yeah, it was my fault when I decided to reflash my One X in a hurry and even didn't pay any attention to the low battery status.
I tried to flash it using ClockworkMod Recovery, as I have already done before.
I had ARHD 6.1.0 and was about to flash the latest 7.1.0 when my device suddenly shut down. The only think I have done before the battery became empty (it would be better if I haven't done it ) - ran the Super_Wipe script.
So, now once I try to charge my One X, it charges for ~1-2 minutes and then turns on showing infinite white screen with HTC logo (as the ROM has been wiped). That 1-2 minutes are not enough to charge the battery to "flashable" status, but once the device starts to boot, the charge process stops. And there is no way to prevent the boot and white screen when the battery does not charge. The battery is also not charging in the boot menu. The CWM even does not boot (I see CWM screen for about half a second and then it immediately reboots due to the low battery level).
In other words - HTC One X with ~1% charged battery, wiped ROM, CWM installed and ARHD image on the internal flash drive ( /flash ).
Is there any way to flash it during the USB charging process (maybe via fastboot)? Or charge it (blocking the boot process when the battery charge stops) to flash after? Please help.
Try this: http://forum.xda-developers.com/showthread.php?t=1658084
sardor said:
Try this: http://forum.xda-developers.com/showthread.php?t=1658084
Click to expand...
Click to collapse
Thank you! I have tried the "charging" script, the voltage is ~3672mV now and it was enough to start the RUU, which failed on the middle of the process due to the "low battery" issue. But I have a night ahead (hope it will be enough to have at least ~3900mV) and I believe that it will work for me.
Thank you again! I luv XDA
Just flashed the latest CWM (5.8.4.0, I had 5.8.3.1 before) and it was actually able to start. The sdcard has been formatted (maybe by RUU), so I had to upload the ARHD image using the USB mount CWM feature again.
Due to the CWM thread (http://forum.xda-developers.com/showthread.php?t=1594819), "Led light might be off in recovery but device charges" in the latest version, and that's awesome! You may charge the device once you are able to boot to CWM.
I may see the device booting in normal mode, and it means that the de-bricking quest has been completed :laugh:
Do always check the battery level before flashing
It's good to see when someone can revive their device flashing a ROM with no battery. It happens all the time lol but its reassuring to know its not game over. Good job man
knclub said:
Just flashed the latest CWM (5.8.4.0, I had 5.8.3.1 before) and it was actually able to start. The sdcard has been formatted (maybe by RUU), so I had to upload the ARHD image using the USB mount CWM feature again.
Due to the CWM thread (http://forum.xda-developers.com/showthread.php?t=1594819), "Led light might be off in recovery but device charges" in the latest version, and that's awesome! You may charge the device once you are able to boot to CWM.
I may see the device booting in normal mode, and it means that the de-bricking quest has been completed :laugh:
Do always check the battery level before flashing
Click to expand...
Click to collapse
I had a similar problem and charging in recovery helped to get enough juice to boot. It did take nearly 12 hours to get to 20% but it was worth it.
Sent from my Venom powered Htc One X quad core
I hope you have solved this case
Hi,
Yesterday i flashed the wrong ROM on my Onex and now i've got some issues i can't seem to resolve.
The Rom i installed was for the Tegra3 Onex and i've got the international version, so yeah, kinda stupid i know.
Some facts:
-Hboot 1.12.0000
-Bootloader is unlocked
-Clockworkmod is installed
-Made a nandroid backup
-Got a fastboot folder
-The ROM i installed was Cyanogenmod 10
At first i didn't notice it was the wrong ROM but it drained my battery pretty fast and WiFi/SD-card/Network/etc. isn't working.
The phone hardly charges (only up to 3% or something) and when i go in recovery and restore the backup i made, it's going into bootloop.
I can't find a way to install another custom or stock ROM on the SD-card since my pc isn't recognizing the device as a storage.
I can however communicate via cmd, but when i try to flash another boot.img on it, it says power too low.
Any idea on how i can get it charged?
Any idea on how to get it working again? (w or w/o stock rom)
Thnx a lot in advance
Switch off the phone and charge it for 1hr
Allready tried that but it won't go beyond 2/3%
Tried charging it while plugged in to the laptop and while plugged into the net.
Yesterday i left it charing for a few hours while it was turned on, but when i got back to it, it was turned off.
The tegra3 one x IS the international one x.
Sent from my HTC One X using xda app-developers app
What XX said. The international One X is the Tegra 3. Did you flash the boot.img prior to flashing CM10?
@XxVcVxX Hmm, my bad about the International version... had a short night, thought i figured it out...
@dr9722 Yes, i flashed the boot.img and followed the guide exactly. The ROM does work, but somehow it doesn't recognize the SD-card, WiFi doesn't work and network doesn't work either. And on top of that, it still doesn't really charge and stays at about 3% when i charge it on standby for an hour.
Any suggestions on how i can get another ROM (zip-file) on the SD-card (perhaps somewhere in the settings?) so i can replace the current one?
Does the Rom actually boot into a usable user interface?
PHP:
XxVcVxX said:
The tegra3 one x IS the international one x.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thats what I thought.
Yes, the ROM does actually work, it's got apps installed and everything else seems to run pretty smooth. Developer options can be enabled and everything works.
Except the most important parts don't work... unfortunately exactly the parts that make it a phone!
the phone doesn't charge right?
matt95 said:
the phone doesn't charge right?
Click to expand...
Click to collapse
It charges up to 3% but drains in 2 minutes when i turn on the phone.
marcobeinema said:
It charges up to 3% but drains in 2 minutes when i turn on the phone.
Click to expand...
Click to collapse
well, this is probably an HW problem... if your phone boots up and can't charge, well that's weird... try erasing battery stat in recovery
marcobeinema said:
It charges up to 3% but drains in 2 minutes when i turn on the phone.
Click to expand...
Click to collapse
Ok, it's charged up to 13% now after being turned off for about 45 minutes. I had it still plugged into the laptop but as soon as i turned it on (screen on minimum brightness) it drains the battery extremely fast.
matt95 said:
well, this is probably an HW problem... if your phone boots up and can't charge, well that's weird... try erasing battery stat in recovery
Click to expand...
Click to collapse
Yeah, allready tried to erase that. But this happened after i installed the new ROM.
Other problem is that when it is on, it doesn't recognize the SD-card so i can't put any other ROM on it, stock or custom.
marcobeinema said:
Ok, it's charged up to 13% now after being turned off for about 45 minutes. I had it still plugged into the laptop but as soon as i turned it on (screen on minimum brightness) it drains the battery extremely fast.
Click to expand...
Click to collapse
did you try what i wrote above?
Ok, it went down from 13% to 2% when i powered it down. Figured if i turned it off, it wouldn't consume any energy, but appearantly that isn't the case.
marcobeinema said:
Ok, it went down from 13% to 2% when i powered it down. Figured if i turned it off, it wouldn't consume any energy, but appearantly that isn't the case.
Click to expand...
Click to collapse
how can it drain battery with power off? Try to leave it charged for a whole day. You can mount your sd card from recovery fyi.
Sent from my HTC One X
Everlasting said:
how can it drain battery with power off? Try to leave it charged for a whole day. You can mount your sd card from recovery fyi.
Sent from my HTC One X
Click to expand...
Click to collapse
I tried to mount the SDcard, but it still isn't recognized when i run the ROM.
I can't seem to install USB Mass Storage, which might be the problem.
marcobeinema said:
I tried to mount the SDcard, but it still isn't recognized when i run the ROM.
I can't seem to install USB Mass Storage, which might be the problem.
Click to expand...
Click to collapse
if you're on JB there's no more USB mass storage
matt95 said:
if you're on JB there's no more USB mass storage
Click to expand...
Click to collapse
Now you mention it, you're right. So how am i gonna get another ROM on the SDcard?
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
Ok so i have searched a lot about the problem so dont ask me to use search..
i flashed 4.2.2. jellybean update on my rooted one x but formatted the system so in order to get back my apps and features, i downgraded my hboot and relocked the bootloader
now my battery got low and i am stuck at fastboot.... it cant flash/unlock bootloader...
phone now wont charge... when i connect it to charger in off state, red led starts blinking and a "charging" symbol appears... ie a battery symbol with a lightning symbol on it... left it like that for hours but phone didnt charge at all... red led still blinked and fastboot said low battery cant flash..
then i searched and FOUND THE .BAT file.... after hours of charging, the voltage fluctuated between 2700 mv and 3000 mv... did the process several times but it wont go any higher... the max voltage achieved was around 3090mv... after that the voltage decreases instead of increasing... i am stuck in fastboot from 2 days... i NEED to revive my phone.. PLEASE tell me if there is any solution to my problem..
Khizar Amin said:
Ok so i have searched a lot about the problem so dont ask me to use search..
i flashed 4.2.2. jellybean update on my rooted one x but formatted the system so in order to get back my apps and features, i downgraded my hboot and relocked the bootloader
now my battery got low and i am stuck at fastboot.... it cant flash/unlock bootloader...
phone now wont charge... when i connect it to charger in off state, red led starts blinking and a "charging" symbol appears... ie a battery symbol with a lightning symbol on it... left it like that for hours but phone didnt charge at all... red led still blinked and fastboot said low battery cant flash..
then i searched and FOUND THE .BAT file.... after hours of charging, the voltage fluctuated between 2700 mv and 3000 mv... did the process several times but it wont go any higher... the max voltage achieved was around 3090mv... after that the voltage decreases instead of increasing... i am stuck in fastboot from 2 days... i NEED to revive my phone.. PLEASE tell me if there is any solution to my problem..
Click to expand...
Click to collapse
download this extract the file ChargeONEX.bat plase in your fastboot folder run CMD go in bootloader with volume down + power buton connect the phone to computer and run the bat file the phone will start to restart a lot of times wait until you see 3700mV and you will be able to unlock flash recovery and rom. The process is slow.
And one more thing this solution is writen on many thread by me and other people you not surch so good
Thant said:
download this extract the file ChargeONEX.bat plase in your fastboot folder run CMD go in bootloader with volume down + power buton connect the phone to computer and run the bat file the phone will start to restart a lot of times wait until you see 3700mV and you will be able to unlock flash recovery and rom. The process is slow.
And one more thing this solution is writen on many thread by me and other people you not surch so good
Click to expand...
Click to collapse
well already tried it but trying once again with your script... will report back
Thant said:
download this extract the file ChargeONEX.bat plase in your fastboot folder run CMD go in bootloader with volume down + power buton connect the phone to computer and run the bat file the phone will start to restart a lot of times wait until you see 3700mV and you will be able to unlock flash recovery and rom. The process is slow.
And one more thing this solution is writen on many thread by me and other people you not surch so good
Click to expand...
Click to collapse
voltage still fluctuating between 2700 and 2900mv :/
Khizar Amin said:
voltage still fluctuating between 2700 and 2900mv :/
Click to expand...
Click to collapse
Yes but wait the gharge in this way is slow. You maybe need 7-8 hours. The voltige will increase after some time and you will see this on the computer. But the script is working or not? Are your phone start to restart and again an again?
Thant said:
Yes but wait the gharge in this way is slow. You maybe need 7-8 hours. The voltige will increase after some time and you will see this on the computer. But the script is working or not? Are your phone start to restart and again an again?
Click to expand...
Click to collapse
yes it is rebooting again and again...
but the problem is it is still stuck between 2700-2900 mv.... if i disconnect it and reconnect after it cools down, it shows voltage around 3000mv... but once the loop starts, voltage drops continuously upto around 2750mv... after the next reboot , voltage is around 2850 mv and starts dropping again.. :/
Khizar Amin said:
yes it is rebooting again and again...
but the problem is it is still stuck between 2700-2900 mv.... if i disconnect it and reconnect after it cools down, it shows voltage around 3000mv... but once the loop starts, voltage drops continuously upto around 2750mv... after the next reboot , voltage is around 2850 mv and starts dropping again.. :/
Click to expand...
Click to collapse
I think your battery is dead repleace the battery with new one if not charge in this way and go only to 2900 and drops down so fast I think faulty battery. I can't suggest anything else because this script work on many people and they charge there phone normal.
Thant said:
I think your battery is dead repleace the battery with new one if not charge in this way and go only to 2900 and drops down so fast I think faulty battery. I can't suggest anything else because this script work on many people and they charge there phone normal.
Click to expand...
Click to collapse
hmm... well i guess i should get the battery replaced... thanks anyway
Khizar Amin said:
hmm... well i guess i should get the battery replaced... thanks anyway
Click to expand...
Click to collapse
No problem. Please give feedback when you change the battery to know I and other users if resolve your problem maybe in future will have other problems like this.
Try it on different computers or laptops! On my pc it didn't work, but on my laptop it did. You could also try different cables. Some Chinese copies did not reach the same voltage as the official cables.
Sent from my HTC One X using xda app-developers app
Khizar Amin said:
hmm... well i guess i should get the battery replaced... thanks anyway
Click to expand...
Click to collapse
Try and this where suggest the @Maart84
Thant said:
No problem. Please give feedback when you change the battery to know I and other users if resolve your problem maybe in future will have other problems like this.
Click to expand...
Click to collapse
well the problem fixed without changing battery... i juct changed the cable... got a new cable and connected phone to the wall charger. after a few minutes the blinking led became solid red... after about 30 minutes the phone booted in fastboot... checked voltage.. it was around 3400+ mv...
then i used the script and in a few hours battery went to around 3620 mv and the battery too low to flash warning disappeared... at this point i unlocked bootloader and formatted /system and connected the phone to wall charger in off state... meanwhile i downloaded android revolution hd rom... waited for aroud 2-3 hours (actually the phone WAS on as the soft keys vibrated when i touched them). after that i flashed the rom and i was good to go..
PS i had downgraded my hboot so phone would not boot anyway so i had to format the system to charge it... otherwise it just booted in fastboot
Khizar Amin said:
well the problem fixed without changing battery... i juct changed the cable... got a new cable and connected phone to the wall charger. after a few minutes the blinking led became solid red... after about 30 minutes the phone booted in fastboot... checked voltage.. it was around 3400+ mv...
then i used the script and in a few hours battery went to around 3620 mv and the battery too low to flash warning disappeared... at this point i unlocked bootloader and formatted /system and connected the phone to wall charger in off state... meanwhile i downloaded android revolution hd rom... waited for aroud 2-3 hours (actually the phone WAS on as the soft keys vibrated when i touched them). after that i flashed the rom and i was good to go..
PS i had downgraded my hboot so phone would not boot anyway so i had to format the system to charge it... otherwise it just booted in fastboot
Click to expand...
Click to collapse
good to hear you fixed your phone if you go in fastboot connect the charger and choice option power off and you will charge yor phone
Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.
dead battery
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found
jhakjhuk1853 said:
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found
Click to expand...
Click to collapse
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.
try changing battery
try changing battery by buying new battery and connecting
or remove battery and charge it with external source i guess u must have heard of jump starting battery
kartikeym309 said:
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.
Click to expand...
Click to collapse
kartikeym309 said:
Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.
Click to expand...
Click to collapse
After the phone updated did u extract and flash boot.img from M5.zip?
convict_moody said:
After the phone updated did u extract and flash boot.img from M5.zip?
Click to expand...
Click to collapse
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.
kartikeym309 said:
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.
Click to expand...
Click to collapse
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.
convict_moody said:
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.
Click to expand...
Click to collapse
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.
kartikeym309 said:
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.
Click to expand...
Click to collapse
Check the guides in here:
HTC One X Reference
convict_moody said:
Check the guides in here:
HTC One X Reference
Click to expand...
Click to collapse
Nah, nothing is suitable. There are guides on how not to brick your device but nothing to unbrick it. :|
Thanks anyways. It's appreciated.
Another bricked HOX apparently. There seem to be loads of these on the internet. In my case, it can't have to do with custom roms or rooting since I never messed around with stuff like that. I even opened the HOX and checked all cables etc. There is no part that looks damaged or otherwise suspicious.
What can we do? How can we at least get access to the data in the internal memory?
Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Click to expand...
Click to collapse
Then run the Batch File
Credit to Floepie for writing the .bat
Wilks3y said:
Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
Then run the Batch File
Credit to Floepie for writing the .bat
Click to expand...
Click to collapse
Unfortunately, there's no way this could help. because the HOX is literally dead. There is not even a charging indication when plugged into a PC or the wall charger. And thus it's not recognised by the PC and fastboot won't find it.