Related
Running Myns Warm TPT and the Netarchy NoHAVS kernel with Caulkins battery tweak.
Today my screen is possessed. I can't select the "T" on my swype keyboard, and random letters and buttons are being pressed all over the screen when I'm not touching it. I've performed two battery pulls, one reboot, and the problem persists. Is this a rogue app, something in the ROM, or a screen going bad?
Even though it is not the same phone. I just had this problem with my Hero. I had to take it in. It was the screen going bad, at least on my phone. I thought it was a custom Rom but I have went through three different ones and sprint is just giving me a new one. Hope this helps.
Thanks - I'm really afraid that's what it is. Just had trouble with the "V" which is in a straight line down from the T, which indicates some sort of problem with the screen to me. Just in case, I'm doing a data, cache, and dalvik wipe and reverting back to another nandroid backup.
ran a nandroid backup, cleared data, cache, and dalvik, and everything seems to be working now. This is positive!
Apparently I spoke way too soon. It happened again last night, but not as bad (no reboot required.)
This morning, I woke up to a battery with 5% and the phone was unusable because of the screen issues. I put my regular battery in and everything is fine...which leads me to a question...
I purchased two aftermarket batteries and a wall charger from Ebay. Is it possible that they are causing the problem? Undervolted, maybe? The wall charger is doing a great job with my original battery (I've never seen 100% on my Evo until now...) but the others drop pretty quickly (and even plug in at less than 90%.) Any thoughts? I want to try all day on my regular battery and see if the problem happens again, and then I'm dumping the aftermarket one if it doesn't.
No ideas at all? This thing is quickly becoming unusable...
Hello,
I have a problem, I think. My phone is one Revolution 1.2.1 and today I've been gaming all day on my couch plugged in to an old charger. So when I unplugged the device I had 0% battery. So far no worries, I thought.
I tried to plug the device back in to the original charger and then it booted, and I can see the HTC "quietly brilliant" screen. This screen is on for a few seconds and after that there's another screen that I don't recognice, it's got the HTC logo and in the bottom there's a "beats audio" logo. After that nothing happens. So for now I've decided to try to charge it fully and see what happens. I have backups and I can access fastboot so I think it should be ok to just reflash the backup. But still, I'm really curious as to what caused this, and is there a fix without reflashing?
//Joel
Usually the screen with the beats logo is part of the booting procedure. I think it will just work fine when fully charged, but you should also wipe your battery stats, because having 0% battery is:
- technically not really possible, because phones have a safe shutdown thingie
- not good for the battery
- unlikely if it has been plugged in all the time, unless the old charger only provides 500 mAh. could you check that, please?
Solved it, I'm too much of a noob to know why it worked but it did.
I wiped chache and dalvik, then I rebuilt the permissions. Now it booted like normal
Yeah it's an old charger, it says 750 on it. Not gonna use that one again . Do you think I should wipe batterystats as well?
the stock charger provides 1000mAh, which is most likely why your phone went down to 0%. I think it's not actually neccessary to wipe battery stats, but it doesn't hurt either. Just do it
Glad to be of help,
dobbi10k
I can't seem to find any information on this issue.
I charge the battery fully on my external charger and then when I put it in my Inspire it shows red with no battery charge then shuts down. When I power it on with the usb plugged in then the battery shows full and I can unplug it. If I power it off then back on it then shows empty again, even if I quick plug in the usb. I have 3 backup batteries and this happens with 2 of them. All of the batteries worked fine until this started happening. I just rebooted with the usb plugged in and when I check the battery info on my ICS rom it shows 0%, charging (AC), 21s on battery. When I unplugged the usb and refreshed the battery info it now shows 99%, not charging, 3s on battery.
Any help would be greatly appreciated, my son's Inspire does not have this issue with the same batteries that i use so it has to be related to my phone.
This happens on my phone rom, Melcheizedek v2.1 and on one of my Boot Manager roms, Lords ICS v 7.4.
Thanks!
I dont know if this will help.
Try using a different stable Gb rom. If problem persists, power off, pull the battery out, put back the same battery, power on. If it still happens, try cleaning the battery connectors. In the past week or so in either this section or the inspire 4g (either the general or Q&A) someone explained how to clean them.
Edit: does the same problem happen in recovery? My guess is yes, regardless if it's software or a hardware prob.
Sent from a dream.
Teichopsia said:
I dont know if this will help.
Try using a different stable Gb rom. If problem persists, power off, pull the battery out, put back the same battery, power on. If it still happens, try cleaning the battery connectors. In the past week or so in either this section or the inspire 4g (either the general or Q&A) someone explained how to clean them.
Edit: does the same problem happen in recovery? My guess is yes, regardless if it's software or a hardware prob.
Sent from a dream.
Click to expand...
Click to collapse
I will try a GB rom today. I just completely reformatted and re-installed Melchizedek - AOSP ICS booted my phone and battery shows red, no charge. Reboot with usb connected to AC and full charge shows then when i unplug still full charge. When i am in recovery it shows battery --% for a few seconds then it changes to full.
Coffee still hasn't kicked in
In recovery it shows 100%. If you stay in recovery what happens?
Same problem? It discharges and then shuts down?
Can you use the battery cover from your sons cellphone?
Do you remember what you did when you first noticed the problem?
Insight to something that happened to me a few weeks back.
I was running a Gb miui rom, I installed a mod or something the device bootlooped. Erased everything, used my backup, but then the battery would discharge insanely fast. 3-5% per minute. From 80% it went down to 65%, rebooted, then it would show 76%. Wipped everything, installed a different stable rom, no apps whatsoever, same problem. I went into recovery, same issue in recovery, erased, (this part I'm a bit foggy) I believe the same thing happened in recovery with a formatted system.
Can't remember if I installed another rom or just went back to my backup.
Powered off the cell, swapped batteries with another phone, the issue was gone.
My assumption is that by pulling out the battery it solved the problem.
In your case, you already pulled out and tried several batteries. But they work in your sons cell. However, with several batteries it is unlickly (the spelling for that just seems wrong for some reason) to be a battery (just ranting to see where my mind goes).
Still waiting to know what happens in recovery.
If it happens with different roms, Im assuming you full wiped. Especially if you are running one from the collective and lord. You probably know more than I do
Try using a different battery cover if you can, and also try booting your cell without the sd card.
Try them seperately to see if either one works.
Hope something I said works, or at least gives you ideas to try something else.
Edit: I just re-read your initial post. It happens with two out of your three batteries. That's a tough one.
Whats the difference between the batteries? Does your sons battery work on your cell?
You can disregard cleaning the connectors - probably.
Or clean the connectors on the bats and the cover. Or try your sons bat connector with those batteries.
Could you re-phrase your initial post along with everything that has happened and what you have tried?
Sent from a dream.
Teichopsia said:
Coffee still hasn't kicked in
In recovery it shows 100%. If you stay in recovery what happens?
Same problem? It discharges and then shuts down?
Can you use the battery cover from your sons cellphone?
Do you remember what you did when you first noticed the problem?
Insight to something that happened to me a few weeks back.
I was running a Gb miui rom, I installed a mod or something the device bootlooped. Erased everything, used my backup, but then the battery would discharge insanely fast. 3-5% per minute. From 80% it went down to 65%, rebooted, then it would show 76%. Wipped everything, installed a different stable rom, no apps whatsoever, same problem. I went into recovery, same issue in recovery, erased, (this part I'm a bit foggy) I believe the same thing happened in recovery with a formatted system.
Can't remember if I installed another rom or just went back to my backup.
Powered off the cell, swapped batteries with another phone, the issue was gone.
My assumption is that by pulling out the battery it solved the problem.
In your case, you already pulled out and tried several batteries. But they work in your sons cell. However, with several batteries it is unlickly (the spelling for that just seems wrong for some reason) to be a battery (just ranting to see where my mind goes).
Still waiting to know what happens in recovery.
If it happens with different roms, Im assuming you full wiped. Especially if you are running one from the collective and lord. You probably know more than I do
Try using a different battery cover if you can, and also try booting your cell without the sd card.
Try them seperately to see if either one works.
Hope something I said works, or at least gives you ideas to try something else.
Edit: I just re-read your initial post. It happens with two out of your three batteries. That's a tough one.
Whats the difference between the batteries? Does your sons battery work on your cell?
You can disregard cleaning the connectors - probably.
Or clean the connectors on the bats and the cover. Or try your sons bat connector with those batteries.
Could you re-phrase your initial post along with everything that has happened and what you have tried?
Sent from a dream.
Click to expand...
Click to collapse
When I boot into recovery it initially shows no charge for maybe 20 - 30 seconds and then shows full (or whatever level the battery really is). The battery level stays normal then and works perfectly fine all the while I am in recovery.
I just rebooted with the battery I was using all day, it was plugged into a usb ac at work until about 3.5 hours ago, and it rebooted with a normal battery level, I rebooted again and it was normal again. I booted this same battery in the morning and it showed no charge but now it works fine. I then rebooted with a second battery and again it booted fine with full charge. I put in a third battery, this was the one it first happened on, and it booted with no charge. I put back in the battery I had in all day and it booted with normal charge again. I checked the bad battery and the good battery and both have about 4.2 volts.
When it happened the first time it was only with 1 battery, that was about a week ago. I just got 2 new batteries in the mail and one worked fine and the second booted up showing no charge like the other one. That was 2 days ago, since then every battery seemed to do it until now, I just checked 5 batteries and only the first bad one and the one new one that was bad don't work, weird.
It seems like the bad battery screwed up something in my phone but it's hard to believe that whatever it was would survive a system format. Now it seems to be working fine...I don't like things that fix themselves...
Well, if you have the time let's try troubleshooting the issue with only the bad batteries (as long as if you believe it to be software related only).
Keep in mind that I'm trying to help figure this out, and to keep bumping this thread until someone more knowledgeable joins in.
If its software, remove the sd card, format everything. Power off, remove the battery, while the battery is out press and hold the power button (hoping the cell works something like a pc) for 30s. Then install - I don't know - any rom? Load a few basic apps you use/need. See what happens with the bad battery.
You did say the bad battery does work in another cell?
Sent from a dream.
Teichopsia said:
Well, if you have the time let's try troubleshooting the issue with only the bad batteries (as long as if you believe it to be software related only).
Keep in mind that I'm trying to help figure this out, and to keep bumping this thread until someone more knowledgeable joins in.
If its software, remove the sd card, format everything. Power off, remove the battery, while the battery is out press and hold the power button (hoping the cell works something like a pc) for 30s. Then install - I don't know - any rom? Load a few basic apps you use/need. See what happens with the bad battery.
You did say the bad battery does work in another cell?
Sent from a dream.
Click to expand...
Click to collapse
I don't believe it's software related, I reformatted and re-installed the rom I was using and still had the issue. I have been using the same rom for a while with no issues. I'll check the 'bad' batteries on my son's phone tomorrow.
Edit: Booted normal this morning again, I think I can close this issue for now. I am a bit uncomfortable with not finding the root cause but at least it ended in my favor. Thanks for your input!
You are welcome. My next step was going to be to link your issue in another thread. Good luck.
Sent from a dream.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Try full wipe and reinstall ROM, if doesn't work flash another ROM. If doesn't work again, maybe it's problem whith battery controller, you would have to go to service centre
DHD
I had a similiar problem and it happened after i started playing with ICS DHD Roms. I downloaded a stock WWE sense 2 rom and flashed that. I then flashes the latest Stock WWE 2.5 Sense rom and all is still ok. Dunno if the stock flashing (through exe from PC) it was unrooted though. Fixed it but its fine now. So maybe try that.
Perhaps this may help.
http://forum.xda-developers.com/showthread.php?p=26010421
Sent from my Inspire 4G using XDA
Thanks for sharing my post on the Inspire forums, Teichopsia.
I'm convinced that there's something in the non-sense ROMS that doesn't get the battery charge % correctly immediately after booting. I'm having the same symptoms as the original poster is having. Two of my batteries are after market and two are HTC. The generic ones have the problem of registering 0% on reboot after swapping the batteries in. If you have them on the charger they work fine and show 100% after about 30 seconds. If you reboot with the same battery it's fine until you change to a different one. The latest ICS Rom I'm using has the problem with any reboot, even if the same battery is in. If I'm using real HTC batteries this problem doesn't manifest itself on Cyanogenmod or AOSP ROMs.
EDIT: I should clarify that the after market batteries fail on any reboot without the charger with the latest ICS ROM I'm trying, but the HTC batteries are fine.
I've had success with booting into recovery mode and wiping battery stats. This is not a permanent fix but is useful when you don't have access to a charger and need to swap batteries.
The full procedure is this: with phone off hold power and vol down, select recovery, advanced, wipe battery stats, yes, go back, reboot system now.
Bad battery I think. Ik had the same problem with a brand new, original battery.
Charged it fully with external charger, booted phone with it but showed 0% juice....
I had to boot with the charger plugged in, and then after booting it went to 100%
Send the battery back because this was not normal, recieved a new one and didn't have the problem.
btw I was on IceColdSandwich rom...
Im running ICS 4.0.4 aospX 1.0.0-MR1 on my HTC Inspire 4g with a Anker® 1600mAh Li-ion Battery For HTC Desire HD, Inspire 4G - White and had this problem initially.
The only way my phone would boot up was if it was plugged in, otherwise it would show a dead battery warning when the homescreen loaded, and then it would shutdown. If I booted it while plugged in, then disconnected the cable, then it would run off the battery just fine.
What I did to fix it was to shutdown the phone, take off the battery cover, removed the battery ( the Anker one), blew into the compartment to make sure there was nothing interfering with the connectors, wiped the battery's connectors with my finger, and then i replaced the Anker battery, pushed hard on it to make sure the connection was good, and booted the phone.
To my surprise, this actually seemed to fix the problem. Whatsmore, after I put the battery cover back in place, the phone continued to boot with no issue, meaning I did not have to push on the battery to make sure the nodes were connecting. I even shook the phone in my hand to see if this would loosen the battery connection, but it still booted fine.
I then took out the battery and replaced it to make sure it would still boot, and it did. Hope my solution works for you! Cheers!
CM is having issues on the One X with reported battery levels as well.
Sent from my HTC One X using xda app-developers app
Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?
Bootloops/shutdowns are going to corrupt your data. I would RUU the thing before looking for hardware trouble, which you've likely sorted out by replacing the battery (of course, we're assuming the new battery is good).
BUT before that, is there a memory test in the bootloader or recovery? If so, I would run that very first thing.
bluedimensional123 said:
Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?
Click to expand...
Click to collapse
Whatever happened to your phone? I have the exact same problem. Infinite boot loop, no illuminated LED, and no way of getting into recovery or anything else with it bootlooping. It occurred after I made the mistake of trying to restart it at 25%. I have the new battery and screen. i'm going to attempt to open this Pandora's box. Seriously going to have to turn my back on HTC. The 10 is so full of software issue problems regarding the batteries that they never bothered to address.
I did the exact same thing a few days ago and my phone won't charge or boot, but I do think the problem is with the button strip, that's what i think, because i tried turning it on before re assembling it and it did turn on successfully and was charging normally but when i re Assemble it, the phone got this problem, now i think when i turned it on before assembling i pressed the power button with a screw driver because i couldn't press it with my fingers, I think there i messed it up, any advice how to fix the button strip and remove a slip nut would be very much appreciated
I had the exact same issue as you(shutting down at 50%), have you found any solution to it?
edit: I THINK clean flashing oreo firmware then latest RUU then twrp then lineage fixed my issue, charging to full rn will drain it over the next day and report back if its gone for good
Early on this year i had an idea of installing nethunter on my old Nexus5X well everything was smooth untill i forgot about phone being in middle of installation and where it prompted me if i want to keep this system read only, I havent noticed that prompt and it automatically selected it as default. As nexus booted into nethunter everything seemed okay untill i launched app, phone froze started to heatup and drained whole battery. After that i charged it for few hours and still no powerup there was only red flashing light as indicator of drained battery. Pressing buttons in any order did nothing didn't even got charging up icon on screen. So i thought that i hard bricked this phone. Put it aside and few months later had an idea of taking it to scraps and mybe sell individual parts as screen, battery and body for few moneys. I unplugged battery and said to myself "its gonna power up rn, i can feel it" and it actually did. So my question here is did it fry the battery or connector on mb or just some messed up corrupted bloat preventing battery to charge up(didnt flashed it to stock yet so everything is set to read-only)
So I tried to install stock rom and realised that because i have to unplug battery it wont boot just loops endlessly.
If you don't mind you could order a cheap battery replacement and try with that one. Sounds like it fired the battery, but it could also have damaged the device (BLODed).