Howdy, guys.
I've got my One rooted, unlocked, and was running a CM10.2 nightly build. Everything was working fine until yesterday, when my battery started to rapidly discharge. I woke up with 100% battery, and after about 15 minutes of playing music it was down to 30%. I recharged it and started noticing rapid battery loss, about 10% per 15 minutes when the phone was idle.
Worried that this had to do with my ROM, I flashed the Eclipse Google Play Edition v1.2 ROM. However, the drain issue continued. I decided to let the phone fully discharge, then try powering it up again.
When it was fully discharged, I tried plugging in the phone. No LED came on and I couldn't turn the phone on. I've let it sit for over 2 hours now with the same result.
Some posts with similar symptoms have mentioned plugging the phone into a Windows PC and experiencing the "USB device plugged in" sound alert. I am not having any such luck, and what I currently have is a very aesthetically pleasing paperweight with no function whatsoever.
Has anyone else experienced a similar issue, or found a fix?
none
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Last Sunday, listening to music with HTC One (bought on Sep 11) on the charger, it suddenly went dark. Would not reboot, no charge light either. Went to a VZW store, they're shipping me a warranty replacement.
I wonder whether my habit of leaving it charger-connected whenever it's sitting on my desk (i.e., way beyond the fully-charged point) somehow stressed the battery (or the charging circuitry) -- though that habit never impacted my two previous HTC models.
When you hold Vol+Down and Power do your home and back arrows blink? If so, point the phone sensors (the two on the front on the left hand side) into a bright light. Then hold down Vol+Down and Power. It should boot. I'm not sure why. But it worked for me today after installing a custom recovery. -shrugs-
musicman625 said:
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Click to expand...
Click to collapse
I've got a replacement being shipped to me, and I'll send them the old one when it comes in. Currently using an old Samsung Stratosphere as a replacement, I was just hoping there'd be an easier fix or something simple. Thanks, though!
Related
I searched here and google and found various charging issues but none quite like what I am seeing. The night before last, I plugged my A100 in before bed like I normally do and saw the power light turn orange. In the morning, I unplugged it without even looking at the LED because I just expected it to have charged completely. When I got to my car and turned it on, it was at 32%. I thought maybe I had something running that was eating battery or I didn't plug it in all the way overnight so it didn't charge. I plugged it into the car charger and went to work. When I got to work it was still at 32% but I didn't use it the whole time so I thought that was odd. I pretty much didn't use it the whole day since I knew it was low on power and I didn't have a charger at work. I got home and saw that it was at 28% so I plugged it in. About an hour later, I checked and it was still at 28%. Thinking that was odd, I turned it off and left it charging with it off for an hour. Turned it back on an hour later and still at 28%. I spent a little time using it while plugged in trying to kill off apps and things but it drained to 18% even though it was plugged in, the power LED showed orange, and the battery icon on screen showed charging (lighting bolt). At this point I started to worry that something was seriously wrong. I turned it *off* and left it plugged in all night after checking to make sure the LED was orange. In the morning, the LED had turned off completely (not blue or orange). I turned it on and saw that it was still at 18% even after charging all night turned off. I unplugged and replugged and the LED came on orange again.
So here is where it gets really strange.. I decide to go through RMA process since I'm still under warranty. I don't want my private data on it when sending it to them so I do a wipe. On a whim, I plug it back in after the wipe and guess what? It's charging! What the heck?!?! I had thought maybe I installed something that was causing problems but since it wasn't charging even when turned off, I figured it couldn't be an app. Can an application cause the device not to charge even in the off state? I thought maybe my battery stats had gotten corrupted so the percentage readout wasn't accurate but right after wiping the data, the battery was reading 18% just as before the wipe.
Any thoughts? Anyone ever see anything similar? My gut says to RMA it still.
Reboot the device.
It's a bug that happened to me on Honeycomb all the time with A100. (No longer happens on ICS)
Did you actually read the OP?
Sent from my Acer Iconia Tab A100 using Tapatalk
Yes, multiple reboots didn't help. No charging even when off. Started charging after wipe. Very odd.
So, after my wipe, I set out to see if I could get it to fail again. I loaded a couple of apps that I had loaded a couple of days before this happened and it stopped charging again. Unloaded each of those apps and still no charging. Did another wipe and still no charging. Conclusion is it's busted and just randomly charges on occasion. Sending it in for RMA today. Still very odd that it was reliably charging after that first wipe.
I myself am experiencing exactally the same problem. Any fix found?
Sent from my A100 using xda premium
Similar thing happened to me. The only thing is I didn't realize it wasn't charging until it was too late and the battery was at 5%. After it shut off, the only way i could get it to turn on was by holding down the power button and plugging in the charger. It didn't get to try a data wipe (didn't have enough time lol). I sent it back and they replaced the system board. Said it was not recognizing the battery properly.
I own two tabs, and one had this issue, the fix is actually quite simple. Let the tab die. No battery life at all. Then, when your sure its dead, plug it back in, and let it charge to full. I haven't had the issue on the tab since.
Sent from my Bad-Ass Acer Iconia Tab a100
Ciao. Same problem: my a100 only power on when plugged on charger.
i'm using a cooked ics with ulocked bootloader and i tried wipe, new installation, varius reboot, etc... and nothing heeelp!
thnx
flskio said:
Ciao. Same problem: my a100 only power on when plugged on charger.
i'm using a cooked ics with ulocked bootloader and i tried wipe, new installation, varius reboot, etc... and nothing heeelp!
thnx
Click to expand...
Click to collapse
Blow in the charge hole (in the tab) and try again, i had a similar problem, my charge was stuck into 3%, i tried that and worked for me : )
Enviado desde mi A500 usando XDA Premium HD app
luisxd said:
Blow in the charge hole (in the tab) and try again, i had a similar problem, my charge was stuck into 3%, i tried that and worked for me : )
Click to expand...
Click to collapse
my charge is on 3% too, but no good luck for me. seems a most serius problem
thanks.
any news guys? I bought a old ACER A100 and only power on while it plug in, so I went ahead and changed the battary, it still does not get charge.
Is the happening on complete stock? Or a custom ROM, if so, which one.
Also, reflash said ROM if applicable, and make sure the data is wiped.
I like the drain the battery idea, although its risky, these tabs can brick if it gets below 10%, current/voltage act weird when its low and blow a breaker inside and keep it from turning on.
Sent from my A100 using Tapatalk 2
What percent does it show the battery at while it's on?
Sent via Acer Iconia A100 on CM10_Build090212; godmachine v2.0 kernel, Smooth, Stable, Fast
My tab has the charging issue, but it is self inflicted. It was dropped, which cracked the lcd screen. I ordered one after a week or so and replaced it. At this point is when the charging issue cropped up. It powers on only if plugged in, and will get to 3% charge no matter how long it is plugged in. It will also only show the 3% if the charger is unplugged. It will then run for a few minutes until the battery dies. Also, the orange charge blinks about one minute after the charger is plugged in.
I found a reference on the web that if the battery charge gets too low the A100 can't charge it. I also found references that people had this problem, and Acer replaced the mb. I took a shot on the battery since it was a lot cheaper. Still the same. That doesn't the battery was not the issue since it was an ebay battery. So for now I just use it in the living room, plugged into outlet. Works good for that.
Jim
Ha! Found my own post by doing google query. Wow, didn't know this thread was still somewhat alive. So, I sent mine back as I mentioned in my last post back in February and they took a week and sent it back to me completely untouched. Basically said it was fixed but the same problem existed. I sent it in after a wipe but I did configure my wifi access point before I sent. When I got it back, my access point connected immediately and it still would not charge. I called them right back furious and demanded they provide shipping back to them because they clearly did nothing. They finally agreed and I shipped it back. After another two weeks of transit and repair time, I got my tablet back and this time it appeared to be fixed.
So, flash forward to 3 weeks ago. One morning I woke up and the tablet wouldn't power on. Black screen but the home "button" would light up when touched and power button would light up when plugged in and such. After several attempts to reset by holding down power button and using the recessed reset button, it was still not responsive. Tried up volume (and down volume) while powering pressing power button.. tried holding down reset button while pressing power button.. all with no result. Submitted rma request and was immediately granted without review. Sent it in and after about two weeks, got it back and it appeared to be working fine. Just this past weekend (about a week after I got the tablet back), I noticed that it was 3% after sitting on the charger for 2 days straight over thanksgiving. ARG!! Looks like another round of RMA here. I have not tried wiping but last time the charging issue happened, it was intermittent for about 2-3 weeks getting worse and worse before finally never charging. I am now near the end of my warranty period and I worry that if I send it back now, they will just turn it around and say it started charging after a wipe. What a piece of ... this is? This will be the 4th times in one year of ownership. I've almost spent the difference in cost between this tablet and other more expensive options in time and shipping alone.
I will try wiping it and then running it all the way down. Although I almost want it to fail hard right now so I can get it RMA'd before my warranty is up.
Hi all,
For the last two to three months, I've been running a Universe ROM on my E4GT. Other than an occasional quirk, the phone has been working very well. I noticed that my phone didn't seem to be connecting to my home WiFi, so I put it into Airplane mode, and then took it out of Airplane mode. Instantly, it connected to my WiFi with a MUCH better signal After checking emails on the phone, I set an alarm and went to sleep. I woke up without the alarm since it did not go off. My phone appeared to be off. Holding the power button resulted in the blue LED charge light flashing, but the screen did not come on. I pulled the battery and put it back, thinking that the phone had some odd-ball software glitch that made it turn off in the middle of the night. When I hit power, the blue LED turns on, blinks, and that is all that happens. Once and only once since this started, my screen showed the boot animation, but did not get past that.
Because my screen turned on ONCE, I'm really hoping that I am soft bricked and not hard bricked. It does seem VERY odd for the phone to become bricked after working fine on this ROM for at least a couple months. The only change I made in recent time is to change a governor in ExTweaks from Hyper to Ondemand. I suppose that could have somehow caused this.
I stopped by a Sprint store, but they would not help as I do not have insurance and the phone is out of warranty.
Do you think making a USB jig or buying one may help? There is a Radio Shack close to where I live. And I have an extra USB cable I can take apart.
If that fails, should I send the phone to mobiletechvideos.com for their JTAG repair? It costs $50 plus shipping to them, but that is still cheaper than buying a new phone. If it came to that, I'd certainly hope they could fix it.
The fact that the blue LED light comes on seems like a decent sign of some life. While the battery animation does not come on, the light does.
Thanks for reading and offering any advice/suggestions.
Can you get into recovery or odin mode?
bigdaddy619 said:
Can you get into recovery or odin mode?
Click to expand...
Click to collapse
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
anindrew said:
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
Click to expand...
Click to collapse
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
bigdaddy619 said:
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
Click to expand...
Click to collapse
Thank you! I'll post here if I get that to work or have an alternate solution.
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Brick
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
Thank you very much for the reply. My phone was having a strange issue with connecting to my home WiFi before I put it on the charger for the last time. I wonder if that was a tell-tale sign that something was up.
I went to the Sprint store closer to where I live and explained what happened. They didn't give me any argument at all. Their tech checked out my phone, but couldn't get it to power up at all. They ordered a replacement E4GT (might be new; might be refurbished) for me for $35. I should have it by Friday. I was surprised by how helpful they were. Apparently, they have see this issue occur on some other Android phones as well.
What is the Chainfires app? Does it identify if you have the "older" chipset which can cause the brick issue? That must be what you mean by "GotBrickBug," right?
Since I'm eligible for an upgrade in June, I think I'll just use the stock ROM to avoid any possible issues. I wonder if the GS4 will be out then. It's always interesting to see what the hot new phone is going to be when you're ready for an upgrade.
Again, thank you to everyone for the helpful replies!
Surprised they even had you pay but I'd have paid $35 also if they'd asked me too.
You should get either new or new board at least.
Here's Chainfire's thread and app in OP. By the looks of it, my chips firmware is updated and as much as I've tested and flashed in the last couple weeks, it's holding up great. http://forum.xda-developers.com/showthread.php?t=1693704
My first clue was that my phone was having problems being read by my PC. Couldn't see either the onboard usb or my external usb. It was intermittent and within a week it was gone.
Sprint has been seeing this problem for sure and in Chainfire's thread, Samsung is well aware.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew said:
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Click to expand...
Click to collapse
Sounds like the h/w took a dump on you - the phone replacement was probably the only route left. By any chance did you leave it charging and/or in a location that allowed it to store heat? (Like a blanket, foam cushion, etc)
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Update the next day: I found this thread, which is essentially a match for what I was experiencing. That one ended with a wait-it-out approach, and I basically did the same. I left it plugged in overnight, even though it appeared not to be charging at all (stone cold, no red light). In the morning, it was still all but dead, but I popped out the battery again (I had done this many times before), replugged it into power, and then it charged normally and completely for the first time since the incident. Moral: don't let the phone go below 15%, and if you do, plug it in ASAP. Don't ignore it overnight, even if it's powered off (maybe especially).
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
You're right - folks, this is not the eMMC bug. Let's just clear that up. If you need further information on that you can refer to the discussion thread on that bug and all the research that several folks have put into it.
When I first got my E4GT there was talk of a BLOD or "sleep of death" where the phone would not come back on. Wasn't the eMMC bug. Most people had a low battery so it was thought the batteries were too low and that it booted and messed up the bootloader. Others thought they overheated. Problem is without any way to diagnose the problem it's hard to come up with a "true" answer.
Perhaps a JTAG could revive the phones. Odd that even if plugged in that nothing is happening. But sometimes h/w really can just go south and trash a phone.
I highly suggest backing up your internal usb drive as frequently as possible because I lost a lot of photos that I never transfered, thanks to Samsung and my hardware taking a crap. Emmc blue light bug really sucks, believe me...
---------- Post added at 03:39 AM ---------- Previous post was at 03:29 AM ----------
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
Doesn't sound like emmc at all. All you will have is a blue light and that's it. If you saw ANY display, it's probably a battery and charging issue. You'll know the bug when you don't see anything but blue and no display at all.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew, how did it all turn out?
Please look into this guys;
Last night, I charged my HOX from 18%-28%, used it for a few minutes and then turned it off (it was still at 28%). I then plugged it into the HTC "black box" usb charger (I've been using the same one since I got the phone like six months ago) but turned on charging after 2 hours - and left it charging for like 6½ hours.
EDIT: My brother actually switched on charging two hours after I switched the phone off. [IT WAS TURNED OFF FOR 2 HOURS]
In the morning, the red LED wasn't on, so I disconnected it and tried turning it on - it didn't work.
I tried holding all three buttons for minutes and all of that, but it still didn't work.
I googled the issue and went through a bunch of threads where the exact same thing happened, and most people said the battery either died permanently or something similar. This one person said he fixed his HOX by using a different charger, apparently the chargers themselves can die.
I plugged my HOX into my mom's Samsung charger, and booted it into bootloader, and selected RECOVERY. After a few minutes and to my orgasmic relief, my phone turned on.
I'm still confused as to what happened.
1) Is there something terribly wrong with my phone's battery now? (When it turned on it was at 1%, whereas I turned it off 6½ hours prior at 28%)
2) My HTC black box charger is obviously not to be used now, right?
3) Is there any problem with using a samsung charger on my HOX from now on? Or should I search for another HTC Black Box Charger?
I'll leave it on charge until it reaches around 60-70% and test it out, and let you know if it's fine. But until then, could you please try answering my questions?
THANKS!
On a side note:
I recently had my HOX repaired at the UK service center under warranty. The phone actually had a bunch of issues; yellow spots on the screen, the ruined wifi antennae thing.. Well, they replaced the screen and display, and replaced the Wifi wiring. When I got it back, it turned out that they forgot to remove a plastic cover from the in-call speaker. Thus I cannot use the phone for phone calls outside of extremely quiet places, unless I use earphones with a mic. I let HTC know this, and they said, "Oh, no problem, just send it back to center"
I reside outside of the UK. I had to send it there with my own money and bring it back with my own money. So now I have to choose between spending another $90 or being able to use my phone for phone calls.
Thanks again, whoever bothers to read this and helps me
I posted this in the noob thread and I'm not sure how posting a new thread will help but hopefully someone may be able to sort me out.
I was using my phone in the car about an hour ago, listening to music (3.5mm jack). At this point my battery was at 3%. I opened Snapchat and the camera was being weird; it had purple noise(?) lines all over the screen every time I pressed the screen to focus it which tells me the camera is stuffed for whatever reason.
Anyway, the phone died on me. I assume the battery died as it was already low. However, it then starts to bootloop about 4-5 times and only manages to reach the encryption screen once, at which point it just switches off. Again, I thought the battery died! So I walk in to my flat, plug the charger in and expect it to boot but nothing happens. At this moment, there is no LED light on the front to indicate charge despite having been on charge for over half an hour, there is no vibration or any form of life from the phone. It just seems to have flat out died on me.
Now I know people will say I dropped it or its water damage so right off the bat, it is neither of those. It was dropped around 3 months ago, once, on carpet, from about 1.5ft if that. Never seen liquid and never been pulled out in the rain or anything like that. Last night it charged fine and today it worked fine too. Now it's dead!
Is there anything I can do/try? The USB cable/charger are fine, I tested them with a volt meter. Other things I have done include trying to boot the phone in any way possible through a number of button combinations, with and without SIM/SD card and even tried to plug the cable into my laptop. It's simply dead. Finally, if this helps: the phone is stock apart from an unlocked bootloader. It is rooted and has xposed installed with 3-4 mods, none of which do a lot (Snappreffs, xnotifications, dpi manager etc). It is running old firmware (like from last May when I bought it. Just never got around to updating I guess!) but this has never caused a problem.
Thanks in advance for any help.
Edit: Phone now responsive after 45 mins+ of being plugged in. Charging and working fine. Weird af..Mods feel free to delete this thread.
So, I bought my HTC 10 sometime last week and I love it, I got the red 2PS6500 version. I have been excited to see people like Leedroid and Faygi working to make this phone so amazing. But I always had a rough battery experience.
At first, symptom was fast draining. It rarely got 3-4hrs SoT, but some days I had good battery life. More recently, I noticed that when using my camera around the 20-30% range, the phone would shut down, and I'd see that it was at 0%-1% and not booting.....
From my research here, this seems like I could try to re-calibrate my battery. I had it charge (powered off) for 2 minutes, then I held both volume buttons + power while still charging. I then let it go up to 100%. When I turned it on, the percent showed 70%. So while it was on, I let it go to 100%. After that, I unplugged it, and rebooted it. It went down to 70% again. I repeated the full charge to reboot. This time, I was 99%. I wanted to reboot once more, just to close the gap from 99% and 100%. USB connection is clean and good, cable works on other phones.
Then the phone just stopped working. It no longer boots up, no LED's, no vibration, buttons don't function no matter the combination. I tried connecting it to my PC and I get nothing recognized. Cannot get the screen on at all.
So I am guessing two things:
(1) Battery might have fired and the connection to the board is gone. I might have bought one that already had issues and this was the last leg of it.
(2) Motherboard damage from the battery? This is something I'm afraid of if I go and replace the battery and I still have issues with it not turning on.
I was hoping anyone with experience might be able to confirm anything I mentioned with the battery issue, and if replacing it solved that.
TL;DR, HTC 10 no longer powers on, shows no sign of life. Battery previously had calibration issues. Should I replace the battery, and then it will turn on, or could there be further damage. Most situations I found were from users that were still able to turn on their HTC 10.
I've replaced my battery recently. I had the same deal. I had to use the actual charger plugged in for a while and it eventually came on
Yayodroid said:
I've replaced my battery recently. I had the same deal. I had to use the actual charger plugged in for a while and it eventually came on
Click to expand...
Click to collapse
Thank you for responding. My issue/question was more about "if" i replace the battery, will it solve my issue. I have not replaced it yet, and I ordered an OEM battery in hopes that should fix my issue. So hopefully a new battery will allow me to boot up my HTC 10 again.
At least I still have my HTC m8, and I'm replacing it's battery too (swelling and making the screen bulge). The community around the M8 is still strong and there is even the latest RR pie available too.
I gotcha. Sorry I have a terrible habit of skimming and then assuming. Mine was similar but not exact. I was always able to get it to show life after it was on charge for a while.
When I replaced the screen once, i forgot to unplug the battery from the board before I started. I got it all back together and it wouldn't turn on. It wouldn't show that it was charging. So I went in and unplugged the battery and plugged it back in. It acted after like it never happened.
Yayodroid said:
I gotcha. Sorry I have a terrible habit of skimming and then assuming. Mine was similar but not exact. I was always able to get it to show life after it was on charge for a while.
When I replaced the screen once, i forgot to unplug the battery from the board before I started. I got it all back together and it wouldn't turn on. It wouldn't show that it was charging. So I went in and unplugged the battery and plugged it back in. It acted after like it never happened.
Click to expand...
Click to collapse
I hope after I replace the battery, it finally boots up. I had to order a new heat blower because mine broke. I'm surprised after I charged it to 100%, it hard bricked and died. I have a feeling th battery was the culprit, since it was always bad at holding a charge....and even more oddly enough, using RR pie on my HTC M8 is FASTER than it was using RR pie on the HTC 10. That battery was very likely affecting my overall experience.
Please do update us with your progress and conclusion. It might help the next person
Yayodroid said:
Please do update us with your progress and conclusion. It might help the next person
Click to expand...
Click to collapse
DEFINITELY. I hope nobody has the issue I am facing at the moment.
UPDATE
So I replaced the battery, was very easy to do with patience and the right tools.
AND, it did not fix my issue. As I opened the phone, I noticed stickers on the chips from a company that apparently did work on it prior to me buying it, and the work they did was bad. I think it is safe to say that the motherboard has suffered severe EDP damage, and it would not be worth the cost to fix it. Burnt pins near almost every chip.... It was so happy being a part of this awesome group, working on the HTC 10 and having Fagyi making the amazing Pie roms. I will be selling my HTC 10 for parts on Ebay if anyone is interested (1 new battery, 1 lcd screen in excellent condition, both cameras, charging ports. . . basically everything but the motherboard that is dead)
So, I am torn between three options. Since my HTC m8 is fixed (top third inch of touchscreen no longer works with tough), I can keep the HTC m8 until it dies and replace it's digitizer/LCD. I can buy another HTC 10 and hope it will not be a crappy one, or I can save and get the HTC u11 (that red color looks so nice!) or go for a Samsung Note 4. I've had the M8 for about 5 years now and it's running RR-P like a brand new phone. I am so sad my 10 just died like that. I was so spoiled with the HTC 10, it was the best phone I ever had. I'd love to have a new device with tons of potential for modding in the future.
Any recommendations then: any device will be modded like crazy, especially with RR or LOS
- keep M8 / replace LCD+Digitizer
- buy HTC 10
- buy HTC U11
- buy Note 4