hardware issue? - One (M8) Q&A, Help & Troubleshooting

My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?

yakultski said:
My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?
Click to expand...
Click to collapse
I have same problem!

Bump. I have the same problem too. Seems to have come out of the blue for an otherwise functional phone. Can't figure it out.
I'll add that I can get into twrp and it seems to function without the charger plugged.. But otherwise, if the charger is removed, phone dies like OP.
Anyone can help?

Hey, this happened to me too while I was using the camera too! What's the linkage?
@yakultski, have you figured this out yet?

Try to flash a RUU and if you got the same it should be an hardware problem...

yakultski said:
My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?
Click to expand...
Click to collapse
Did you resolve the issue. I heard it could be the battery failing, but i'm not so sure anymore, because when i run antutu benchmark my phone shuts down when using fisheye image processing or 3D, it turns off even when it's plugged in.
I suspect it's the GPU failing or something similar. That is weird since i wasn't using any intense 3D games. I'm sure this is my last HTC.

yakultski said:
My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?
Click to expand...
Click to collapse
I don't know if you managed to solve your problem, but in my case I replaced the battery and now the problem is gone. So defective battery is the reason in my case. I replaced it my self which is quite a task but not so hard, you just need patience and time. So if you have time to reply me, please do, as i would like to help.:good:

Gunman84 said:
I don't know if you managed to solve your problem, but in my case I replaced the battery and now the problem is gone. So defective battery is the reason in my case. I replaced it my self which is quite a task but not so hard, you just need patience and time. So if you have time to reply me, please do, as i would like to help.:good:
Click to expand...
Click to collapse
Hey Gunman84, my phone is behaving in a similar fashion as the OP. I have an AT&T phone converted to a GPE. So everything is stock in that sense. If plugged in, phone operates normally. As soon as I unplug it, a couple of seconds later it will power off. If I boot into hboot, the phone will stay on for a long time (its been an hour+ already and its still on).
I watched a youtube video showing how to replace the battery and that was pretty intimidating - haha. Where did you get your battery replacement? and how much did it cost?
thanks

clemdaddy said:
Hey Gunman84, my phone is behaving in a similar fashion as the OP. I have an AT&T phone converted to a GPE. So everything is stock in that sense. If plugged in, phone operates normally. As soon as I unplug it, a couple of seconds later it will power off. If I boot into hboot, the phone will stay on for a long time (its been an hour+ already and its still on).
I watched a youtube video showing how to replace the battery and that was pretty intimidating - haha. Where did you get your battery replacement? and how much did it cost?
thanks
Click to expand...
Click to collapse
Hi, it's not so intimidating . Well you just need to be careful and patient, there are lots of small resistors, connectors and so on. Check the iFixit site for proper instructions here is the link https://www.ifixit.com/Teardown/HTC+One+%28M8%29+Teardown/23615 this is full teardown, and here is 2nd link where they focus mainly on replacing the battery https://www.ifixit.com/Guide/HTC+One+M8+Battery+Replacement/41650. I'm from Slovenia, and the battery cost me 20€, which is around 25US dollars, the battery was original one. I bought it from local supplier. It took me around 2-3 hours to replace it, or something like that, that's because i wanted to be careful.

Gunman84 said:
Hi, it's not so intimidating . Well you just need to be careful and patient, there are lots of small resistors, connectors and so on. Check the iFixit site for proper instructions here is the link https://www.ifixit.com/Teardown/HTC+One+%28M8%29+Teardown/23615 this is full teardown, and here is 2nd link where they focus mainly on replacing the battery https://www.ifixit.com/Guide/HTC+One+M8+Battery+Replacement/41650. I'm from Slovenia, and the battery cost me 20€, which is around 25US dollars, the battery was original one. I bought it from local supplier. It took me around 2-3 hours to replace it, or something like that, that's because i wanted to be careful.
Click to expand...
Click to collapse
Thanks so much for the links.
The phones behavior really makes me question if its the battery. For example, it stayed on in the hboot/recovery screen for 10+ hours (without being plugged in). So the battery can definitely hold a charge.
I'm afraid to open up the phone (and potentially break it), when there is potentially something else going on (maybe a software issue). I guess if I run out of ideas, I'll have no choice but to attempt the battery replacement.
thanks again!

clemdaddy said:
Thanks so much for the links.
The phones behavior really makes me question if its the battery. For example, it stayed on in the hboot/recovery screen for 10+ hours (without being plugged in). So the battery can definitely hold a charge.
I'm afraid to open up the phone (and potentially break it), when there is potentially something else going on (maybe a software issue). I guess if I run out of ideas, I'll have no choice but to attempt the battery replacement.
thanks again!
Click to expand...
Click to collapse
Well in my case i could also stay in recovery mode(TWRP) indefinitely also in bootloader mode, that's because you are not in the operating system. The graphics are not running at that point and so on, it doesn't drain that much power at that point either.. It's a different story if you try to flash a rom in aroma, at that point the phone shuts of if not plugged in. It is the battery, trust me.

Gunman84 said:
Well in my case i could also stay in recovery mode(TWRP) indefinitely also in bootloader mode, that's because you are not in the operating system. The graphics are not running at that point and so on, it doesn't drain that much power at that point either.. It's a different story if you try to flash a rom in aroma, at that point the phone shuts of if not plugged in. It is the battery, trust me.
Click to expand...
Click to collapse
Really appreciate your responses. Makes sense what you say. I'm going to attempt the battery swap. Got no other option!
For the adhesive parts of the phone. When putting it back together, did you need to reapply more adhesive?
Thanks

clemdaddy said:
Really appreciate your responses. Makes sense what you say. I'm going to attempt the battery swap. Got no other option!
For the adhesive parts of the phone. When putting it back together, did you need to reapply more adhesive?
Thanks
Click to expand...
Click to collapse
Nope, no additional adhesive was needed in my case. I used the hair dryer to soften the original adhesive. The speaker grills were difficult to remove as they are glued quite well, but eventually they came off. The toughest part was separating the back casing, as you do need quite a few prying picks or guitar picks.
Just be careful with the motherboard, slowly remove the tape that covers the connectors, you don't want to rip apart any flat cables. And don't throw away that tape, you will need it.

Ohh i have the same issue.i used phone normally before and battery worked fine.but then i flashed ICE rom and when i was using the camera this happend.is this really a battery issue?
Sent from my HTC Desire EYE using XDA-Developers mobile app

Kasun72 said:
Ohh i have the same issue.i used phone normally before and battery worked fine.but then i flashed ICE rom and when i was using the camera this happend.is this really a battery issue?
Sent from my HTC Desire EYE using XDA-Developers mobile app
Click to expand...
Click to collapse
Well if yours symptoms are the same as clemdaddy has, then yes. Sorry, but at least now you know what the problem is.

Got the new battery today and performed the phone surgery. All the connections looked good. Pieced it all back together and everything works BUT the new battery won't charge. The phone is running off the battery, so the connections I made must be correct. Running off the battery the phone no longer exhibits the symptoms I described above (so this most likely confirms my previous battery was the culprit). I tried the hold all buttons for 2 minutes to re-calibrate the new battery. All that did was made the phone now display a full battery (instead of the empty battery it initially showed).
On the weekend I'll open it up again and see if I missed something.

Got the replacement battery. Re-opened up the phone. This time I over heated the upper and lower panels which caused them both to warp a bit, and one of them to have its paint bubble :crying: :crying: :crying: :crying:
I replaced the new defective battery with the most recent one. Put the phone back together and it is back to normal again! Also probably because of the over heating, there is now a little bit of a rainbow effect on the lower part of the LCD screen!
A real pity the first battery was defective, causing me to have to re-open it and carelessly overheat it. Otherwise the 1st attempt would have been a flawless repair!
With the warped panels, the bubbling paint and now the rainbow effect on the screen, I wonder how long I'll keep the phone. These little things are definitely bugging me... If I get rid of it, I'll really miss my google edition htc one m8! Nothing like a nexus like experience with a remove-able microSD card. Such a thing no longer exists

Related

android:battery empty: can't recharge

Is there a way to solve this (I've got a spare battery)? Any chance of getting an updated NBH?
robuser007 said:
Is there a way to solve this (I've got a spare battery)? Any chance of getting an updated NBH?
Click to expand...
Click to collapse
if your phone truly isn't charging the battery you can always hotwire it to the positive and negative wires from a clipped usb cord.
holding the wire to the terminals of the battery for a few minutes can get you running again.
however...
I have found that often if you just unplug the phone,remove the battery from the phone and then discharge the phone (pressing power button) then reinstall battery, you can then plug in the phone to get a charge...
let it charge for 15-20 minutes and then turn it on without the powercord.
resume charging once running.
I'd advise against the hotwiring method, since unless you have a lot of experience in wiring you run a risk of damaging something due to shorting wires, put it this way, I am experienced in electronics assembly, and wouldn't try this unless there was no other way.
However my method is similar to the one mnjm suggests, I have run out of battery once or twice on android, and I pull the battery, replace it, plug in the charger, wait until the light goes out, disconnect charger, pull and reinsert battery again, power on the phone, wait until it starts the second stage of booting, ( bootanimation), then plug in the charger. Usually works fine.
Or try this:
Pull the battery, replace it, plug in the charger, don't wait wait until the light goes out, power on the phone while light is ON.
I have run out of battery many times while testing battery patch an this always worked for me.
My battery meter was acting up lately and I decided to let my phone die. Let it run out of power to correct the battery meter. It was either 100% charged or less then 1% charge.
Now it won't boot. I see the X animation and nothing happens. I just keep watching the animation. The animation keeps resetting. I hate to think that my Android installation corrupted just by letting the battery run dry?
Will it even charge if I plug it in? I wanna try reinstalling Android to get it working again.
**EDIT**
Yep, corrupt installation.
I have no idea why draining the battery would do that, but it did. I reinstalled Android and it booted again.
My phone lost charge overnight the other day and I found plugging in usb power and using the hard reset button made it boot and then it would charge up OK.
Steve
zenity said:
I'd advise against the hotwiring method, .
Click to expand...
Click to collapse
yeah...I was regretting typing that.
obviously if you are not confident in your understanding of what you are doing then AVOID playing with bare wires.
you don't have to fear electricity...
but you do need to respect it.
I know you are confident, just making sure people knew that there were potential dangers, it's not that a cut down usb lead is dangerous as far as shock hazards go, more the remote possibility that a shorted lead could perhaps cause major battery problems, since hotwiring them, while it does charge the battery, provides no short-circuit protection, it is remotely possible, (but unlikely), that this could cause fire hazards.
If I was really desperate I might do this with a zener diode rather than just bare wires.
I know we like messing with our phones, but also remember that the Darwin Awards exist because people sometimes let enthusiasm get ahead of their capabilities
Dukenukemx said:
**EDIT**
Yep, corrupt installation.
Click to expand...
Click to collapse
One of the dangers, that's why it should be fixed in the NBH, any chances for a fix, anyone working on this at the moment ?
I'm thinking of buying the motorola milestone, but it's still expensive (350 euro's).
robuser007 said:
One of the dangers, that's why it should be fixed in the NBH, any chances for a fix, anyone working on this at the moment ?
I'm thinking of buying the motorola milestone, but it's still expensive (350 euro's).
Click to expand...
Click to collapse
I can actually buy a phone with my upgrade discount, but I love my Kaiser too much to let it go. Plus it's a better learning experience when dealing with Android.
If I bought a new Android phone, I wouldn't do much of anything with it, besides use it as a smart phone.
zenity said:
I know we like messing with our phones, but also remember that the Darwin Awards exist because people sometimes let enthusiasm get ahead of their capabilities
Click to expand...
Click to collapse
I know what you mean. When I use my hammer to smash aerosol cans, I'm always careful enough to cover my face with my hand. Can't be too careful.
I kid, I kid.
Dukenukemx said:
I can actually buy a phone with my upgrade discount, but I love my Kaiser too much to let it go. Plus it's a better learning experience when dealing with Android.
If I bought a new Android phone, I wouldn't do much of anything with it, besides use it as a smart phone.
Click to expand...
Click to collapse
I've seen that the milestone is still locked, no hardspl etc.
robuser007 said:
I've seen that the milestone is still locked, no hardspl etc.
Click to expand...
Click to collapse
Seriously? By the time they unlock it, there will be a new phone to buy.
Meh, besides, I never lose my old phones. They turn into "hand me downs". My sister has my old HTC Wizard right now. If things get really bad, I still have my old Nokia NGage. Yes, I own one of those.
Same thing has just happened to me, except I can't turn the phone back on at all now.
Was running the latest Kaiser NBH from DZO whilst using Myn's rom, I had a number of issues with battery life using android with it going from 75% charge to 0% and soft resetting by itself.
Anyways this time it hasn't woken up after doing just that, it was working fine then it turned off and I can't get it back on.
It just won't power on, there is no charging light but then again that only came on once android was booted never on startup with the android NBH, it was fine with Windows Mobile.
I have removed the battery, put it back in but nothing.
Swapped out for another working battery that I have spare, but nothing.
Tried a hard reset, still nothing.
It's just not starting at all now.
The phone was working and was on the side not charging and all of sudden it turned off and hasn't come back on since.
Bit annoyed.
ST1Cl<^^aN
Stickman89 said:
Same thing has just happened to me, except I can't turn the phone back on at all now.
Was running the latest Kaiser NBH from DZO whilst using Myn's rom, I had a number of issues with battery life using android with it going from 75% charge to 0% and soft resetting by itself.
Anyways this time it hasn't woken up after doing just that, it was working fine then it turned off and I can't get it back on.
It just won't power on, there is no charging light but then again that only came on once android was booted never on startup with the android NBH, it was fine with Windows Mobile.
I have removed the battery, put it back in but nothing.
Swapped out for another working battery that I have spare, but nothing.
Tried a hard reset, still nothing.
It's just not starting at all now.
The phone was working and was on the side not charging and all of sudden it turned off and hasn't come back on since.
Bit annoyed.
ST1Cl<^^aN
Click to expand...
Click to collapse
Sorted it now, note to self and anyone else who has done this.
Usually what occurs is when the phone powers off when the battery has not been calibrated properly it requires you to do a hard reset using the stylus.
Anyway's I did that in the dark and accidentally pushed the stylus into the charger port on the phone and pushed a pin into another so It was short circuiting. Luckily I didn't damage the pins or the phone and was able to straighten it so it wasn't making contact with the other pins.
I'm happy again, its only really a test phone tbh, I have had a HTC Hero for some time now...
Best Regards,
ST1Cl<^^aN
Like most problems, it's due to the kernel. Even if the bugs get sorted out, there's still plenty of room for improvement.
Lets say the following is working 100%.
phone
GPS
3D
power management
wifi
bluetooth
USB
camera
etc
There's always a need for something. Like upgrading 3D to OpenGL ES 2.0, or getting support for ext3/ext4. That's a long way to go and very few people are willing to do it on their spare time.
In the most severe cases, people had to pool together a reward for someone to include support for something.
Considering how similar the Kaiser/Polaris/Vogue is, you could combine this group of people to get something done. There's a lot of talent, but it's spread far apart.

Phone died?

Hello everyone.
I have been using Tasks ROM for a while now. Last night my phone had a random reboot and other than that, no troubles.
Well about 20 minutes ago, my phone just turned off and will NOT come back on at all. I have done nothing different, cant get in to get a logcat or lastkmsg. It will not even boot up to the samsung screen.
It will vibrate when I plug it in or take out the battery and reput it in.
The only response I am getting is taking everything out (batter/sim/sd) and plugging it into my comp. The response is a Red light in the notification LED and a short vibrate, then nothing.
I get a Samsung logo if I just pull battery and reinsert.
Any help would be greatly appreciated.
Thanks
So you can't get into CWM or TWRP? And what Galaxy S3 Variant are you using?
axel4401 said:
Hello everyone.
I have been using Tasks ROM for a while now. Last night my phone had a random reboot and other than that, no troubles.
Well about 20 minutes ago, my phone just turned off and will NOT come back on at all. I have done nothing different, cant get in to get a logcat or lastkmsg. It will not even boot up to the samsung screen.
It will vibrate when I plug it in or take out the battery and reput it in.
The only response I am getting is taking everything out (batter/sim/sd) and plugging it into my comp. The response is a Red light in the notification LED and a short vibrate, then nothing.
I get a Samsung logo if I just pull battery and reinsert.
Any help would be greatly appreciated.
Thanks[/QUOTE
Ii it possible you may have a bad battery? How new is it?(not that age of it matters) Also, do you have a case on the phone? Check to make sure the power button is not stuck. If you can get to boot logo, then its not dead-dead. If you've had your phone for awhile, double check the battery terminals are not oxidized. Unlikley, but worth checking and maybe check battery wih voltage meter if you have access to one. Then charge it overnight and check it again. One last thing to try is plug it in with the battery out and see if that does anything. Have you flashed anything lately? Modem? Scripts?
Click to expand...
Click to collapse
I have taken the battery out and plugged the phone straight into the computer and all that i get is a red light where the notification light is and then it disappears.
As for age, its a little over a year old.
I wasnt doing any flashing at the time, it just went kaput right after a phone call.
I had a mophie case on it, but not right now. I guess ill take it a part when i can and throw som alcohol on the battery button to see if it loosens it up. But other than that, I'm at a loss.
Not trying to pay $80 for a craigslister either.
Bubba Fett said:
axel4401 said:
Hello everyone.
I have been using Tasks ROM for a while now. Last night my phone had a random reboot and other than that, no troubles.
Well about 20 minutes ago, my phone just turned off and will NOT come back on at all. I have done nothing different, cant get in to get a logcat or lastkmsg. It will not even boot up to the samsung screen.
It will vibrate when I plug it in or take out the battery and reput it in.
The only response I am getting is taking everything out (batter/sim/sd) and plugging it into my comp. The response is a Red light in the notification LED and a short vibrate, then nothing.
I get a Samsung logo if I just pull battery and reinsert.
Any help would be greatly appreciated.
Thanks[/QUOTE
Ii it possible you may have a bad battery? How new is it?(not that age of it matters) Also, do you have a case on the phone? Check to make sure the power button is not stuck. If you can get to boot logo, then its not dead-dead. If you've had your phone for awhile, double check the battery terminals are not oxidized. Unlikley, but worth checking and maybe check battery wih voltage meter if you have access to one. Then charge it overnight and check it again. One last thing to try is plug it in with the battery out and see if that does anything. Have you flashed anything lately? Modem? Scripts?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Man, I don't know. Sounded like a charging issue at first, but looking I'm not so sure now. Anything stuck in your power slot? Maybe try leaving battery out overnight and see if it clears anything. If it starts to boot I would go right to recovery and try flashing something. I would be concernedabout going straight to download mode and using oOdin cause of it does during the flash that is really bad...
Can you get into download mode? Pull battery plug in USB and hold volume down and home buttons I think... when you plug USB in to computer does Odin recognize it at all?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I just started having the same issue. I have a an ATT S3 running the newest Hyperdrive. Mine wasnt doing a random reset, but it seemed like it has been turning itself off. Totally intermittent, i couldnt pinpoint the cause.
Then just today when i went to see if i had any messages and the phone was off again (i had about a 60-75% charge) I hit the power button a few times and now i am getting the symptoms described above.
When i try to go into TWRP, i get the blue text at the top left of the screen, sometimes i make it to the first hyperdrive screen, then it goes black.
When I go to download I can get to the hit up or down screen, i hit up to go into download, i get to the next screen then it goes black again.
I did leave the battery out for about 15minutes and no dice. I even tried to leave it on the charger thinking i lost all charge or something.
I am just a mere user, but i have always been able to tinker around enough not to bother the devs and get my way out of these situations, but I think i am stuck. Anyone have any ideas?
Thank you!
nightwulfss said:
I just started having the same issue. I have a an ATT S3 running the newest Hyperdrive. Mine wasnt doing a random reset, but it seemed like it has been turning itself off. Totally intermittent, i couldnt pinpoint the cause.
Then just today when i went to see if i had any messages and the phone was off again (i had about a 60-75% charge) I hit the power button a few times and now i am getting the symptoms described above.
When i try to go into TWRP, i get the blue text at the top left of the screen, sometimes i make it to the first hyperdrive screen, then it goes black.
When I go to download I can get to the hit up or down screen, i hit up to go into download, i get to the next screen then it goes black again.
I did leave the battery out for about 15minutes and no dice. I even tried to leave it on the charger thinking i lost all charge or something.
I am just a mere user, but i have always been able to tinker around enough not to bother the devs and get my way out of these situations, but I think i am stuck. Anyone have any ideas?
Thank you!
Click to expand...
Click to collapse
Maybe a stuck power button? Try cleaning it out a little. .. sounds like it's rebooting itself.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
Maybe a stuck power button? Try cleaning it out a little. .. sounds like it's rebooting itself.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I am trying that, it doesn't seem like there is anything in there, but you never know.
If the power button was stuck on, wouldn't the phone keep trying to restart? Or no?
nightwulfss said:
I am trying that, it doesn't seem like there is anything in there, but you never know.
If the power button was stuck on, wouldn't the phone keep trying to restart? Or no?
Click to expand...
Click to collapse
I believe so, unless you pull the battery. In fact pull battery plug into usb and go into down load mode and see if it restarts. Or go into recovery without holding power button, and if you can then that means the power button is stuck on.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
I believe so, unless you pull the battery. In fact pull battery plug into usb and go into down load mode and see if it restarts. Or go into recovery without holding power button, and if you can then that means the power button is stuck on.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have tried that as well. Whenever it goes into download mode the screen goes black after a couple of seconds. And it doesn't boot into recovery as well since it seems to go dead too quick.
I mainly just want to recover my pictures at this point. I am leaving the battery out of the phone for the day and see if that makes a difference this evening.
I am out of ideas, lol
nightwulfss said:
I have tried that as well. Whenever it goes into download mode the screen goes black after a couple of seconds. And it doesn't boot into recovery as well since it seems to go dead too quick.
I mainly just want to recover my pictures at this point. I am leaving the battery out of the phone for the day and see if that makes a difference this evening.
I am out of ideas, lol
Click to expand...
Click to collapse
Take the six acres it and open her up, Take out button off and clean it and where it goes.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
Take the six acres it and open her up, Take out button off and clean it and where it goes.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Pretty sure the flex cable on you're power button is not working as intended, could be a short from a rain drop or just everyday wear and tear another issue could be that the battery is fried and can't hold a charge, but this seems unlikely given you're circumstance.
I always tell people to utilize pie controls to save you're everyday use from wearing out our precious hardware buttons, My power and home only get pressed to wake the device, everything else is pie control via LMT launcher
That happened to me a few months ago. I was at work when it happened. The phone would just continually restart, vibrate, restart, back and forth. I ended up taking the battery out so it wouldn't get drained. Had it out for about four hours. Once I got home, I put it back in and never had any more problems. It was just a random thing, so try keeping the battery out for a while.
I'll keep my fingers crossed. I took the phone apart last night to clean it out and it was pretty spotless. But It keeps shutting off after trying to boot after a few seconds. I just hope I can get to a point where I can get my pictures off of it now.
nightwulfss said:
I'll keep my fingers crossed. I took the phone apart last night to clean it out and it was pretty spotless. But It keeps shutting off after trying to boot after a few seconds. I just hope I can get to a point where I can get my pictures off of it now.
Click to expand...
Click to collapse
Hello all, as an update, I did nothing to my S3 over the weekend haping something magical could happen.
Today I went through all the normal steps again, and still a dead soldier. Now it wont ever SHow the Samsung logo however - just a short vibrate then nothing..
Still get a red light and a short vibrate when plugging into the comp without battery in though.
I have NOT taken it apart yet, but I will tonight most likely.
Thanks for all the suggestions and Ill keep this updated.
axel4401 said:
Hello all, as an update, I did nothing to my S3 over the weekend haping something magical could happen.
Today I went through all the normal steps again, and still a dead soldier. Now it wont ever SHow the Samsung logo however - just a short vibrate then nothing..
Still get a red light and a short vibrate when plugging into the comp without battery in though.
I have NOT taken it apart yet, but I will tonight most likely.
Thanks for all the suggestions and Ill keep this updated.
Click to expand...
Click to collapse
Hello again,
Some news, I am able to get it into download mode for about 1 second then the phone shuts off - just like the other person in this thread with the same issue.
I took the phone apart and used a Qtip with 91% isopropyl Alcohol to try and clean the power button (which looks surprisingly clean). Still the same thing happening.
I'm running out of ideas here, so please chime in if you have any.
Thanks
axel4401 said:
Hello again,
Some news, I am able to get it into download mode for about 1 second then the phone shuts off - just like the other person in this thread with the same issue.
I took the phone apart and used a Qtip with 91% isopropyl Alcohol to try and clean the power button (which looks surprisingly clean). Still the same thing happening.
I'm running out of ideas here, so please chime in if you have any.
Thanks
Click to expand...
Click to collapse
I was going to try the alcohol tonight, but I am afraid that I will have same results. I am going to try a new battery from another s3 tomorrow. I will post the results.
nightwulfss said:
I was going to try the alcohol tonight, but I am afraid that I will have same results. I am going to try a new battery from another s3 tomorrow. I will post the results.
Click to expand...
Click to collapse
Final update (hopefully)
I got the qtip and scrubbed anything to do with the battery, pressed the power button, got more alcohol in by the button (not a lot) scrubbed some more terminals, and the battery terminals, etc. waited about ten minutes and put the battery in...
Low and behold, something worked and now the phone comes on.
I dont know which part of the scrubbing actually did it, but something worked.
All in all I have no idea what actually fixed it, but the point is that it works.
Thank you for who those that insisted that it was a power button issue - you were most likely right.
So here are my results as of today, and what I have tried to get to this point:
After my S3 died and wouldn't boot up into recovery i tried cleaning all the internals with alcohol. I cleaned thoroughly, and focused on the charging port, the power switch and battery terminals. The phone acted exactly the same.
I then tried putting it in a bowl of rice for about 24 hours. I was thinking that it might have been caused by some condensation. No success.
I was thinking since the power would turn on whenever i plugged the battery in, that maybe the switch was stuck. I took it apart again and tested the switch with a multi-meter. The switch seemed fine. It was responding when i pushed it, so i figured that wasn't the problem.
I kept reading that apparently this is an issue with the mother board. I tried the broken PS3 method of heating up the motherboard with a heat gun in hopes to re-seat something that may be loose. This did not work either. After this, I figured i was SOL since I was out of ideas and out of warranty (which didn't really matter anyway since I am running Hyperdrive).
Earlier today I figured the best tool in your toolbox sometimes is a hammer. I started tapping the phone on the side of my table, especially around the power button, while trying to turn it on. It didn't seem like it was doing anything either. I then plugged the phone into the charger since i thought the battery was totally dead.
A few minutes after i walked away from the phone, I came back into room and the red charging light was on. I tried turning it on, and holy cow it works...wtf...
I have no idea what made this work. It could be a complete coincidence. But, this phone has not worked since last Saturday. I just kept messing with it and may have just gotten lucky. I don't think banging your phone will fix this, but if truly was a hardware issue, maybe something in the phones mother board is becoming loose from the extreme heat they endure at times. I know my S3 has gotten pretty hot when I use it to navigate and leave it in the case.
I don't know if any of this will help anyone, but this is my experience so far of my S3 having what I think is the sudden death failure. I will followup with any updates if it decides to act up again.

[Q] ZL shutting down during boot, stays on with usb power

Hi guys, I'm experiencing some power issue with my ZL. I have recently updated via Seus to .283 firmware....once I reboot, it gets to the Sony screen and then it shuts down. If the phone is plugged in it boots fine and remains on. The battery charge shows 80%. Afterwards I unlocked the bootloader and flashed the KK advanced kernel to see the battery percentage in recovery and it also shows 80%. Is there anyway to check if its the battery without replacing it?
Aphex33 said:
Is there anyway to check if its the battery without replacing it?
Click to expand...
Click to collapse
There is a battery testing app for Sony devices (you can find it here), but, obviously, it requires your phone to be able to stay on battery power for the time of the testing...
What happens with your phone if you unplug the charger once fully booted? Does it immediately shut down, or is only happening during startup?
The phone shuts down immediately after I remove the usb cord. Offline charging looks as though it's working. I'll see what the app says, thank you.
* btw the phone stays on when in recovery which is odd
* the battery app requires you to remove power which I cannot do
* help me!..using a Z Ultra at the moment...things huge!
Aphex33 said:
The phone shuts down immediately after I remove the usb cord. Offline charging looks as though it's working. I'll see what the app says, thank you.
* btw the phone stays on when in recovery which is odd
* the battery app requires you to remove power which I cannot do
Click to expand...
Click to collapse
Well, yeah, that's what I meant saying the phone has to be able to stay on battery...
I think (just an uneducated guess ) that the recovery doesn't have a mechanism to analyze battery health/status, but the Android OS does (and so does the bootloader). That's why it stays on in recovery, but when booted (or in the process of booting) into the OS, the system somehow thinks that the battery level is too low, and shuts down as a safety measure. I have seen multiple times that the battery levels shown in recovery and in Android are drastically different, which kinda confirms my thoughts...
All in all, it looks to me like your battery is acting up. Just to save you an effort and expense of getting a new battery, at least until you know for sure the battery is the problem, I can suggest something to you... I am expecting a replacement for my battery in a day or two. My old (current) battery still works, it's just old and doesn't last very long, that's why I am replacing it. I could send the old one to you (Vancouver to Winnipeg is not a big deal), so you can try it out to pinpoint the problem. If it works, then you know it's the battery, and you can either buy a new one, or keep my old one for the time being. If you are OK with the idea, just send me a PM with the address to send it to.
I think I'm just going to buy a battery of ebay. I really appreciate your offer to send me your old battery, but its probably best I go new since I don't want this issue arising again. Thanks again for all your help.
Aphex33 said:
I think I'm just going to buy a battery of ebay. I really appreciate your offer to send me your old battery, but its probably best I go new since I don't want this issue arising again. Thanks again for all your help.
Click to expand...
Click to collapse
No problem! I was just thinking you could use my battery to confirm the problem before buying the new one, not to keep it for the long term, of course (that would be silly). But I am pretty sure it's the battery, anyway... Good luck!
I was wondering if the battery ever fixed the problem, I am having the same issue
really mad, I'm going on a business trip and this started happening. this week I updated the firmware to 293.
I didn't know you could replace the ZL battery.
After 2 years of use, my phone suddenly just died when I was playing a game. It won't boot without the charger ever since. I'm so sad because I expected this phone to last longer

[Q] Flashed ROM, worked perfectly, won't turn on now

So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
NotRankin said:
So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
Click to expand...
Click to collapse
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
FoxyDrew said:
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
Click to expand...
Click to collapse
ok, I'll continue waiting, thanks for the info. I'll go ahead and flash CM11 and use that for awhile until HTC pushes their 5.0 out or if problems are fixed. Hopefully it won't take too much longer for the device to die...
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
NotRankin said:
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
Click to expand...
Click to collapse
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
FoxyDrew said:
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
Click to expand...
Click to collapse
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
If theres still no charging lite? Possibly. You could try to charge the battery with a split charger. However thats last resort and can break your battery if it doesn't work.
NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
Or you could use your manufacturers warranty and send that baby back in for a fresh one. Claim a defect... Why? Because it is a defect. If you can't get it to boot with adb / rooted methods then their stock methods won't work nor detect anything. Besides, the worse they'll do is send your phone back the same way it got to them.
Also, if the others who ran into this issue could give feedback on if they modified screen resolution before the device kicked on CM12 that would be most informative.
Sent from my 710C using XDA Free mobile app
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
NotRankin said:
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
Click to expand...
Click to collapse
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
FoxyDrew said:
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
Click to expand...
Click to collapse
So either I screwed something up or it was a screwed up phone in the first place (I'm inclined to believe this as it was frequently getting into a locked state where I'd have to force reboot it via the vol/power buttons). Guess I'll go for it, thanks!

Bad Battery?

I know. I've seen the threads for battery drain and such, but I don't think there's a problem with "drain" so much, as perhaps a bad battery altogether.
I'm using my old M8 for my daughter, but after RUU, and setting up latest TWRP and all, then trying to install a custom ROM whether Stock or AOSP, when I boot into recovery, it goes from 100% within the ROM, to show 80% in recovery.
If off the charger, there does appear to have some battery drain, but I chalk that up to normal first usage.
However, it then shuts off @ 30%, but when I put it on the charger, it says @ 60%.
I've done the calibration method (hold all buttons for 2 minutes) trick, but there appears to be no help for the erratic battery readings.
Does anyone know if my suspicion is correct?
I'm on Sprint's last RUU.
mcwups1 said:
Does anyone know if my suspicion is correct?
Click to expand...
Click to collapse
Ive seen so many posts now that refer to the exact thing you mention. Phones turning off at 20-30%. Its claimed that this is due to a faulty battery and a replacement has fixed it. I do not have this problem, however, I did get a replacement 12 months ago.
That's what I'm afraid of.
Did you replace it yourself, or have a tech do it?
mcwups1 said:
That's what I'm afraid of.
Did you replace it yourself, or have a tech do it?
Click to expand...
Click to collapse
I replaced mine just Yesterday, with both speakers, chraging portero AND buttons, its not that hard AND not easy, you Will nerd a razor blade, AND see a few videos first, one thing to have in mind Is that i put a m9 battery on my m8, AND the phone works, but the phone doesnt recognize the aditional 240mamps,. AND the battery temp always shows 25C, but besides that everything is ok, waiting for the battery yo settle.

Categories

Resources