Related
Hello people
A couple of hours ago, my phone shut down due to empty battery. I came home, plugged it in and booted it, all was fine. At about 60% I shut it off and went to have lunch, when I came back and tried to turn it on, I couldn't.
Led was orange at the time, I unplugged the power cord but the led stayed on! I removed the battery to be able to reboot it, but when I re-inserted it I still wouldn't boot.
Now no matter how I try to charge it, led stays off like it's not charging. Tried various different cables/chargers, the same. Tried to plug it to the charger without battery but no led flashed. Tried to boot without sim/sd card, still the same.
Any ideas?
My battery has never been changed (for a year now) and has had a bunch of full drains. Could this be a dead battery? :/
Well seems the phone is fried... I tried two more official batteries and no go...
Sorry to hear it. I thought that at first when I read your thread but I thought because I am not the most experienced person here, there might be some kind of fix.
HTC will most likely if not certainly replace this handset for you, seeing as it just happened out of the blue.
Well I certainly hope so, problem is I suspect it's an import (from another European country) and local HTC service generally does not do well with European imports.
Anyway I'll give it a try, meanwhile I'm getting a sensation soon
I have a similar problem.
I'm lucky that my girlfriend has the same handset as I do, the I could compare the phone abnormal behavior tho that of her properly working phone.
The first thing I've noticed, after a while when the charger was attached, was that the phone is very hot and that the battery keeps draining out in a surprisingly high rate.
After a while I've noticed that even when the phone is turned off it wont recharge. Sometimes the Orange LED is on when recharging while it is off, and the LED stays on for a few seconds after removing the charger, as if it was still charging. Note that the affects of connecting the charger to the phone, are mainly the ones listed below (not necessarily altogether)
* The phone indicates as if it recharges.
* Going to an infinite loop of rebooting and crashing.
* Getting hot when power supply is plugged, or at any time when the phone is turned on.
Ultimately the battery was empty, and the only way I had to keep using the phone (mostly to diagnose the symptoms listed here) was to swap the battery with the one of my girlfriend's device, and charge my battery in her device while using her's. That's the place to mention that the battery works just fine and that the phone is draining any battery, no matter what.
I took it apart to have a closer look at the source of all of the heat emitted while the phone is turned on, and it seem to come from the motherboard itself.
That's all I have.
The worst thing is that a friend of mine who helped me opening it up broke the pcb of the volume keys. Now I checked and It turns out that that pcb is actually part of the flex cable, which sort of extension of the motherboard and is mainly the second most important piece of hardware of all the phone parts (not that there are so many). If I would be able to expose the conductors inside the flat cable I might be able to solder an alternative volume pad I'll make out of old some miniature switches I have. The cable is very thin. any Ideas of how to expose the relevant conductors without ripping the cable apart?
Just a (late) update:
It's been almost two years, I had given the phone to a close friend of mine after a couple of weeks since writing the first post, just in case he could resurrect it, nothing.
Then, a couple of months down the road, the phone suddenly woke up! He tried to connect it with the charger, after months of not being able to charge or boot it up and somehow it worked. And it has been working flawlessly ever since.
I just got it back to give to my girlfriend until her sensation is fixed, flashing Viper now
In case something like this happens to any of you, don't give up!
BACKGROUND:
At first, it just started turning off for no reason (probably a month and a half ago).
Then this week, it would start to randomly turn off, and start vibrating constantly when charging. After fiddling with the buttons, it would eventually find itself into download mode and then later turn itself on.
NOW:
Monday morning, after several days of draining the battery to 0% (due to me solely charging it for an hour a day), the phone went dead. Then, that night, upon trying to charge it and turn it on, it remained stuck on a black screen. After taking out the battery, it would continuously beep while still connected to the charger. As soon as I put in the battery, it would become COMPLETELY unresponsive, with and without the charger. After fiddling with it for over an hour, I put it down and slept, leaving the battery and charge in the phone.
Tuesday morning, I clicked the power button, and the phone flashed to the lock screen. It displayed it was at 0% battery, but I think it showed a charging sign. I used the phone for almost 2 minutes, checking my texts, before it again went completely black. The phone became completely unresponsive (no beeping or anything, regardless of anything I did). I connected it to a wall charger again, and left it there for the entire afternoon.
Then when I picked it up at around 6 o clock, I discovered that the continuous beeping stopped, and it would only beep after holding the power button for around 5 seconds. It could beep regardless of whether the battery was out or not.
After charging it all that night, I found I could make it flash the Samsung logo for a fraction of a second after holding down both volume buttons and the power button. I looked it up, and supposedly it brings you to recovery mode, but I believe my phone is switching off immediately after bringing up the logo.
At around 12, Tuesday night, I again decided to hold down the power button (just to reassure myself of it still somewhat functioning), and it powered on for around ten seconds (!!!) . It got all the way to the end of the pink loading bar screen, but then beeped and restarted. The second time, it lasted only around three seconds, without even getting to the loading bar screen, before powering off. It became completely unresponsive afterwards, no beeping, regardless of where it was charging and whether the battery was in or not.
Wednesday morning (today), after having left it charge all night, the phone still was completely unresponsive. I then left it to charge the entire afternoon (until now), and it was still completely unresponsive. I took it apart and played around with the power button, but it didn't seem to be stuck. I've now put it back together and leaving it connected to the wall charger once again.
What I've Tried:
Tried connecting it to Kies (computer doesn't even recognize it)
Tried putting into Recovery Mode (unresponsive)
Tried putting into Download Mode (unresponsive)
Switched chargers (unresponsive)
Held power button (beeps, now doesn't do anything)
Held both volume buttons and power button (beeps then quickly flashes samsung logo)
Cleaned off some of the micro usb lint with a tooth pick (coincided with the stopping of continuous beeping, not sure if it caused it)
What I think it could be:
Faulty power button (this is what I thought it was, but now it's not vibrating)
Faulty battery (I kept draining to 0%, but if this is the problem, it doesn't explain the phone not displaying anything when it's connected to a charger w/o battery inside)
Faulty usb charging port (I've heard it sometimes causes vibration problems. wouldnt explain the restarting).
Fried motherboard (phone has had some water damage, but I'm not sure if it's the MOBO, considering its symptoms)
HELP WOULD BE GREATLY APPRECIATED.
Not Alone
hey, this isnt really an answer, but maybe something to bump this up. Mine went last night.... won't boot, won't charge... goes into download mode but no matter how many times i switch cables, install Samsung drivers, install Keis, or anything imaginable- i cannot get it to communicate with my PC. if i could i would be able to fix this problem.
i really hope that someone will take a look at these issues and give some input. my call to Samsung was useless, i wasted hours with redundancy. I bought the phone used off Ebay in mint condition... have taken it apart and cleaned it with no avail. i fear that soon the battery will be dead and there's no way to charge it. sucks. Samsung really should recall/replace this because so many people have similar issues. whether it's the USB Flex or the battery or the motherboard they should be responsible. looks like ill be getting a nexus 4 afterall.
please let me know if you figure anything out.
sluchy523 said:
BACKGROUND:
At first, it just started turning off for no reason (probably a month and a half ago).
Then this week, it would start to randomly turn off, and start vibrating constantly when charging. After fiddling with the buttons, it would eventually find itself into download mode and then later turn itself on.
NOW:
Monday morning, after several days of draining the battery to 0% (due to me solely charging it for an hour a day), the phone went dead. Then, that night, upon trying to charge it and turn it on, it remained stuck on a black screen. After taking out the battery, it would continuously beep while still connected to the charger. As soon as I put in the battery, it would become COMPLETELY unresponsive, with and without the charger. After fiddling with it for over an hour, I put it down and slept, leaving the battery and charge in the phone.
Tuesday morning, I clicked the power button, and the phone flashed to the lock screen. It displayed it was at 0% battery, but I think it showed a charging sign. I used the phone for almost 2 minutes, checking my texts, before it again went completely black. The phone became completely unresponsive (no beeping or anything, regardless of anything I did). I connected it to a wall charger again, and left it there for the entire afternoon.
Then when I picked it up at around 6 o clock, I discovered that the continuous beeping stopped, and it would only beep after holding the power button for around 5 seconds. It could beep regardless of whether the battery was out or not.
After charging it all that night, I found I could make it flash the Samsung logo for a fraction of a second after holding down both volume buttons and the power button. I looked it up, and supposedly it brings you to recovery mode, but I believe my phone is switching off immediately after bringing up the logo.
At around 12, Tuesday night, I again decided to hold down the power button (just to reassure myself of it still somewhat functioning), and it powered on for around ten seconds (!!!) . It got all the way to the end of the pink loading bar screen, but then beeped and restarted. The second time, it lasted only around three seconds, without even getting to the loading bar screen, before powering off. It became completely unresponsive afterwards, no beeping, regardless of where it was charging and whether the battery was in or not.
Wednesday morning (today), after having left it charge all night, the phone still was completely unresponsive. I then left it to charge the entire afternoon (until now), and it was still completely unresponsive. I took it apart and played around with the power button, but it didn't seem to be stuck. I've now put it back together and leaving it connected to the wall charger once again.
What I've Tried:
Tried connecting it to Kies (computer doesn't even recognize it)
Tried putting into Recovery Mode (unresponsive)
Tried putting into Download Mode (unresponsive)
Switched chargers (unresponsive)
Held power button (beeps, now doesn't do anything)
Held both volume buttons and power button (beeps then quickly flashes samsung logo)
Cleaned off some of the micro usb lint with a tooth pick (coincided with the stopping of continuous beeping, not sure if it caused it)
What I think it could be:
Faulty power button (this is what I thought it was, but now it's not vibrating)
Faulty battery (I kept draining to 0%, but if this is the problem, it doesn't explain the phone not displaying anything when it's connected to a charger w/o battery inside)
Faulty usb charging port (I've heard it sometimes causes vibration problems. wouldnt explain the restarting).
Fried motherboard (phone has had some water damage, but I'm not sure if it's the MOBO, considering its symptoms)
HELP WOULD BE GREATLY APPRECIATED.
Click to expand...
Click to collapse
It may be your battery, u need to remember why they tell u not to run the phone that way, the batteries our phones run need to maintain a certain charge in order to work correctly, if like u said u only charged it an hr or so a fah for over a week and drained completely more than once u may have rendered ur battery unable to hold a charge, in effect not allowing the phone to run its boot process, I would try a new battery, because beyond that the only other logical explanation is a hardware failure, stuck power button wouldn't render the device unresponsive only when the battery was put in like that, it would bootloop, have u ever just held ur power button in? The phone vib an shuts down a. Vib again n shut down, not become unresponsive, I would try a new battery, and if it works, respect the charge lol
Sent from my SGH-T989 using xda premium
I would agree, seems to be the battery. I bought 2 batteries and a 110V charger on eBay for $30. They don't have the NFC antenna in them but I've never missed it. Not only that but charging that way saves the wear and tear on the USB port.
T989D
latest CM 10.1 nightly
latest Uber nightly
My Idea
Follow the procedure on this website
galaxys2root.com/t-mobile-galaxy-s2/how-to-unroot-t-mobile-galaxy-s2-jelly-bean/
Hello all. I recently made this thread where I described the phone, the LG G3 d851 t-mobile variant. randomly rebooting and not turning on without pulling the battery. (http://forum.xda-developers.com/lg-g3/help/d851-randomly-shuts-off-wont-power-t3424458). I deduced it to the replacement battery (supposedly genuine) that I purchased from a seller on ebay. I put my old battery in and everything is fine again, and the seller shipped me another replacement battery (big mistake, i know).
I put in the replacement battery, and a day later the phone shuts down again in the same manner as stated in the previous thread. I pull out the battery and put it back in and.. nothing happens on screen. The LEDS just flash green and blue. I tried plugging it into a charger, just a red LED, no display. If I plug in the phone to a charger without the battery inserted, the backlight activates but nothing whatsoever appears on the screen. I cannot get into the recovery either.
If I let the phone sit for a while, and try to power it on, I see the LG boot screen appear for about 5 seconds. Then the image flickers and fades away to black, and the LED just flashes blue/green.
Am I screwed or is there any way to salvage this phone? I'm desperate for any assistance and I'm totally open to any component level repair you guys recommend (I'm pretty broke :/)
Thanks all!
Current behavior:
Attempt to turn phone on: Blank display, no backlight, blue/green LEDs
Plug phone in with battery in: Blank display, no backlight, red LED
Plug phone without battery in: Blank display, backlight active, red LED
Do any of the above after leaving phone off for a while with battery unplugged: display begins to display the expected image for 5 seconds, then the screen flickers and the image fades until the screen turns black.
I tried the old (working) battery, and no luck either.
[edit] Hopefully solved. please read my latest post for my idiotic but somehow functional solution
amaskedman said:
Hello all. I recently made this thread where I described the phone randomly rebooting and not turning on without pulling the battery. (http://forum.xda-developers.com/lg-g3/help/d851-randomly-shuts-off-wont-power-t3424458). I deduced it to the replacement battery (supposedly genuine) that I purchased from a seller on ebay. I put my old battery in and everything is fine again, and the seller shipped me another replacement battery (big mistake, i know).
I put in the replacement battery, and a day later the phone shuts down again in the same manner as stated in the previous thread. I pull out the battery and put it back in and.. nothing happens on screen. The LEDS just flash green and blue. I tried plugging it into a charger, just a red LED, no display. If I plug in the phone to a charger without the battery inserted, the backlight activates but nothing whatsoever appears on the screen.
I tried the old (working) battery, and no luck either.
If I let the phone sit for a while, and try to power it on, I see the LG boot screen appear for about 5 seconds. Then the image flickers and fades away to black, and the LED just flashes blue/green.
Am I screwed or is there any way to salvage this phone? I'm desperate for any assistance and I'm totally open to any component level repair you guys recommend (I'm pretty broke :/)
Thanks all!
Click to expand...
Click to collapse
It would help if you would say what variant you have (at&t, verizon, sprint). Can you boot into TWRP? If your able to get into bootloader kdz or tot back to stock.
netookska05 said:
It would help if you would say what variant you have (at&t, verizon, sprint). Can you boot into TWRP? If your able to get into bootloader kdz or tot back to stock.
Click to expand...
Click to collapse
Sorry! I am using the d851 T-mobile model. I can't boot into recovery or anything. the LED just flashes some color but nothing appears on the screen.
Behavior:
Attempt to turn phone on: Blank display, no backlight, blue/green LEDs
Plug phone in with battery in: Blank display, no backlight, red LED
Plug phone without battery in: Blank display, backlight active, red LED
Do any of the above after leaving phone off for a while with battery unplugged: display begins to display the expected image for 5 seconds, then the screen flickers and the image fades until the screen turns black.
Will update the OP
Thank you for the reply.
amaskedman said:
Sorry! I am using the d851 T-mobile model. I can't boot into recovery or anything. the LED just flashes some color but nothing appears on the screen.
Behavior:
Attempt to turn phone on: Blank display, no backlight, blue/green LEDs
Plug phone in with battery in: Blank display, no backlight, red LED
Plug phone without battery in: Blank display, backlight active, red LED
Do any of the above after leaving phone off for a while with battery unplugged: display begins to display the expected image for 5 seconds, then the screen flickers and the image fades until the screen turns black.
Will update the OP
Thank you for the reply.
Click to expand...
Click to collapse
Possibly bricked plug it into your computer and see what it comes up as.
So strangely enough, I tried heating my phone using the most idiotic method possible by letting it heat in my blanket (I don't have immediate access to a heat gun). The screen began displaying some funky artifacts when attempting to boot with the LG logo but would otherwise revert to the behavior described in the OP (only LED working, no LCD display.).
I let the phone cool for a few hours and I'm actually able to get as far as the dialog box where it asks you whether or not you really want to format, in other words the factory data reset dialog box (when holding vol down + power to get into the recovery) with minimal to no hardware artififacts., and only when I confirm that I do does it crap out and revert to the previously described behavior. But it actually lets me use the vol keys to select an option, so I'm getting a lot further than before.
So this absolutely seems to be a hardware problem. Anywhere you guys suggest I examine before I take a heat gun to the motherboard? Any specific component I should look at?
Thank you guys so much
Take it to certified technician he will fix ur device these phones are dirt cheap nowadays so u will not be charged heavily no more than 50$ worthl
So,
after reading into this more and suspecting loose solder joints (see the various threads about screen flickering problem), I decided to pursue this route and continue trying to heat the logic board.
I'm completely broke and don't have access to a heat gun, and with no other working phone I decided to take some desperate measures. For those of you having a similar problem and reading this, PLEASE DON'T ATTEMPT WHAT I'M ABOUT TO DESCRIBE. THIS IS A HORRIBLE IDEA.
I turned on the phone to get the blue/green LEDs , plugged it into the wall, and wrapped the phone with blankets. I let the phone cook itself for 2 hours.
Yes, just like the infamous xbox 360 "towel trick".
When I went to remove the phone from my makeshift blanket oven, the phone was brutally hot and felt like a stovetop (was painful to touch for the first 30 seconds). The screen was filled with artifacts due to the intense heat.
I carefully removed the battery, let the heat dissipate slowly for a couple minutes, let the phone cool on an AC unit for a another few minutes and turned the phone on.
It worked. Phone boots and haven't had a single problem for over a day.
I guess the problem was cold solder joints after all, and the intense heat was enough to reflow the solder and form a stable enough connection to allow the display to function again.
Even ran a stress test program for an hour with no issues.
Hoping this fix lasts (knock on wood), will report back if I have any issues.
Again, anyone having a similar problem, please don't emulate me. I shouldn't even have to say why this is a bad idea. Get a heat gun, remove the motherboard and heat it that way.
I'm sure applying the proper repair procedure described in this thread http://forum.xda-developers.com/lg-g3/help/screen-flickering-fix-successful-t3397411 would have fixed my problem as well.
So, why did this problem happen in the first place? I'm guessing it has to do with the overheating issues this model of phone has (at least my particular unit). I've been playing a lot of pokemon go, so the phone is running a lot hotter than it used to. The constant high temps (reading upwards of 75c frequently from my cpu) were enough to weaken the solder joints. I also recall dropping the phone a couple times while playing the game, and I guess this was enough to knock the joints out of wack.
I'm currently capping the CPU at 1500mhz and the GPU at 300mhz and the phone is running a lot cooler now. I'm probably going to set the resolution to 1080p, cap the framerate and possibly undervolt, though this might not be necessary.
Thanks for reading and hope this helps someone in the future.
So, the other day I accidentally dropped my Zenfone. When I picked it up, it had been shut down. I couldn't boot it up anymore after the drop. After like maybe 1 hour I opened the phone up and reattached the battery wire. Then I got it working. But then the problem was that the phone got really hot, even when I wasn't using it.
I waited until the battery was completely dead and then tried to recharge. And now the problem is that the phone won't charge at all. It still gets really hot. When I plug the charging cable in, it just vibrates, shows that it is charging, but then just after 20seconds it stops.
And now I'm asking, what should I do? I also tried to disassemble everything and then assemble everything back again, but with no luck.
ranetnjuud said:
So, the other day I accidentally dropped my Zenfone. When I picked it up, it had been shut down. I couldn't boot it up anymore after the drop. After like maybe 1 hour I opened the phone up and reattached the battery wire. Then I got it working. But then the problem was that the phone got really hot, even when I wasn't using it.
I waited until the battery was completely dead and then tried to recharge. And now the problem is that the phone won't charge at all. It still gets really hot. When I plug the charging cable in, it just vibrates, shows that it is charging, but then just after 20seconds it stops.
And now I'm asking, what should I do? I also tried to disassemble everything and then assemble everything back again, but with no luck.
Click to expand...
Click to collapse
inspect motherboard for physical damage with a magnifying glass. go for reflow if no physical damage.
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