Related
GReetings,
So I have searched for a lot of forums to see if there is an answer to this.
So the story goes. I got myself a new phone and put the TP2 in a drawer. After moving, I have a reason to pull it out and get it ready to be used again. However, it wont turn on.
So I figure the battery went dead. I plug it into the charger, the LED lights up, and got to wait a few minutes. After a minute or so, the white HTC screen suddenly comes on the screen, it vibrates one quick, and shuts off again.
I cant power it up, I can get it to boot loader. Really not sure what the problem is here.
Any ideas suggestions would be welcome as I want to put this one back to stock so I can send it to my step-kid for use.
Try charging it for a few hours, while it is closed. If the phone regularly reboots and then switches off, leave it that way.
The idea is to charge the battery enough, so as the phone boots.
had the same prob the other day
what helped here was:
remove the battery and let it out of the phone for a couple of hours (i did it at night). had the battery removed for about 8 hours. put it back in and it worked for me again.
give it a try and let me know!
Ok will try that tonight when I'm heading for bed. Ill leave it to charge while I'm at work because I get tired of hbearing it vibrate every 20 seconds while its charging
kilmarac said:
Ok will try that tonight when I'm heading for bed. Ill leave it to charge while I'm at work because I get tired of hbearing it vibrate every 20 seconds while its charging
Click to expand...
Click to collapse
Did you get it to work? I'm having the same problem. I posted in another thread that had the same problem as you.
Maybe HTC really is pushing an auto kill program.
Sent from my PG86100 using Tapatalk
Unfortunately, it didnt work. I think the phone was probably dropped one too many times and is broken. I cant get it to boot, cant even get into the bootloader. So I have no idea.
Steefje said:
had the same prob the other day
what helped here was:
remove the battery and let it out of the phone for a couple of hours (i did it at night). had the battery removed for about 8 hours. put it back in and it worked for me again.
give it a try and let me know!
Click to expand...
Click to collapse
I also had the same problem I took out the battery and blew on it to get it to cool down and had it sit out of the phone for 10-15mins then put it in the phone and plugged into charger and left it for 30mins then hit the power button.
This reboot cycle happens when my phone dies in android and it works every time for me.
Hope that helps
for future reference, the phone died with a Sim card in it, revived when a Sim card was replaced.
Sent from my cm_tenderloin using Tapatalk
yesterday I had the same problem, boot loader doesn't work. But.... I charged my battery, replaced it, pushed Vol. down + EndCall btn. + Power btn and inserted battery. As a result my boot loader is working now. But after running task 29 and flashing custom firmware my phone doesn't came back alive. I'm looking for solution now. Did anybody have the same problem?
When I'm flashing original firmware the process stops on checking my phone.
Please, give me advice how to solve my problem. Thx.
RHOD*** 32M SS-BC
SPL-0.88.000
MircoP(LED) Wrong Plat(0x0)
MicroP(KEY) Wrong Plat(0x0)
Turbo HW/Turbo SW
TP MFG DATA
501,526 793,854
810,209 211,200
211,855 Calibrated
First off it looks like you are not Hard SPLed so custom ROMs will be a problem for you. Second you have a major error with your keyboard and touch screen. I have a TP2 that took a dip into some water that has the same error - MircoP(LED) Wrong Plat(0x0) and MicroP(KEY) Wrong Plat(0x0). When I first got the phone it would not turn on but would make a noise that sounded like it was crying. I got another TP2 that works fine and swapped the top halfs of the phones because the new one looked like a dog chewed on it. It still worked but in real bad shape. The touch screen that got wet works fine so it is on the TP2 that I use all the time. The wet TP2 will now start up but the keyboard, all of the front buttons but the end key, and touch screen don't work. The touch screen will only register getting touch in one spot. So if you have a software keyboard up only the t will be hit. I Hard SPLed it, ran task 29, and installed a custom rom on it. I have to use My Mobiler to do anything with it. It also will take a battery that has a full charge and drain it to about 50% in about 20 minutes and then claim the battery is dead even on a charger. Something to play with.
With the error you have unless you got it wet you might have a bad flex cable. I would try to fix the error first before trying to change roms.
Thank you for answer.
My phone was HardSPLed and flashed by custom firmware and works fine for half a year. The reason for my situation was broken charger... I think that problem in hardware when I put it on charge, my phone lightly flashed by orange lamp and became can't turn on
You are told that it is looks like it doesn't hacked because I tried to roll it back to original.
Are you sure the phone did not get wet? Everything you describe makes it sound like the phone took a dip. If not, try plugging it into a computer and see if it will charge and turn on.
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
AlexeYM007 said:
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
Click to expand...
Click to collapse
You can only HSPL once. If they (or you) relocked the device, you won't be able to unlock it again unless you can get Olipro/cmonex to take pity on you.
Glad I could help. Here is a small warning. Once a phone gets wet it's days are numbered. You might have a week, a month, or a year but the phone will die. I would plan ahead for the phone to die and keep an real close eye on it.
Sent from my HTC Touch Pro 2 running FRX07.1 using the XDA mobile application powered by Tapatalk
AlexeYM007 said:
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
Click to expand...
Click to collapse
If you need to HardSPL a second time, PM me.
Hello!
A few months back I rooted my Verizon LG G3 without any issue. Worked great, went smoothly.
Last night I was watching Netflix when the phone suddenly shut off without warning. I haven't recently installed anything out of the ordinary. When I tried to reboot, I got the green screen with a HW reset warning. Pressing Vol down to reboot gave me a blue screen. I'm able to reboot using Power + Vol down, but if I try any of the options [including factory reset] it suddenly goes to the blue screen.
I also tried getting into download mode without any luck - you guessed it: Blue screen. If I connect the phone to a PC, it doesn't recognize it. I've tried downloading and running the LG PC Suite, but it can't connect to the phone.
Any thoughts on what's going on and how I might be able to repair it? I've looked through various threads here and anything similar seems to revolve around flashing gone awry...and I'm not flashing anything (nor do I really have the know-how to do so).
Thanks, in advance, for any assistance.
Andrew
rewkim said:
Hello!
A few months back I rooted my Verizon LG G3 without any issue. Worked great, went smoothly.
Last night I was watching Netflix when the phone suddenly shut off without warning. I haven't recently installed anything out of the ordinary. When I tried to reboot, I got the green screen with a HW reset warning. Pressing Vol down to reboot gave me a blue screen. I'm able to reboot using Power + Vol down, but if I try any of the options [including factory reset] it suddenly goes to the blue screen.
I also tried getting into download mode without any luck - you guessed it: Blue screen. If I connect the phone to a PC, it doesn't recognize it. I've tried downloading and running the LG PC Suite, but it can't connect to the phone.
Any thoughts on what's going on and how I might be able to repair it? I've looked through various threads here and anything similar seems to revolve around flashing gone awry...and I'm not flashing anything (nor do I really have the know-how to do so).
Thanks, in advance, for any assistance.
Andrew
Click to expand...
Click to collapse
Do you get the blue screen when attempting both recovery and download mode?
Blue screen no matter what I do - recovery, download or normal mode. As a matter of fact, now the phone won't attempt to boot at all.
Really strange.
rewkim said:
Blue screen no matter what I do - recovery, download or normal mode. As a matter of fact, now the phone won't attempt to boot at all.
Really strange.
Click to expand...
Click to collapse
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Bastienhere said:
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Click to expand...
Click to collapse
I appreciate your help - thank you. For what it's worth, no - there was never any text on my blue screen, and I couldn't ever get it to get into Download Mode. Plugging it in to a computer did nothing except give me a blue screen, and the computer never recognized it as a device.
I ended up getting a replacement G3, so [for now] my troubles are over. Thanks, again, for your help.
(I guess this thread can be closed now.)
Bastienhere said:
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Click to expand...
Click to collapse
Quick update: I just learned today that a co-worker who also has a G3 (T-Mobile) also got a blue screen last week. He was told that this was a "known issue" with this phone...but they wouldn't provide him with a replacement, which also seemed strange.
rewkim said:
Quick update: I just learned today that a co-worker who also has a G3 (T-Mobile) also got a blue screen last week. He was told that this was a "known issue" with this phone...but they wouldn't provide him with a replacement, which also seemed strange.
Click to expand...
Click to collapse
Glad you got it replaced!!
And a shame for your friend :/
In my case, it was practically hopeless, nothing seemed to work, eventually i had to have the motherboard replaced. It was clearly a damaged bootloader, yet, they repaired it under warranty! funny
I doubt you can damage a bootloader without root or stuff.
I wonder what would suddenly mess with the bootloader after months of no issues?
I'm having the same issue. Or rather I had the same issue but I was able to get it back to stock through all the various .tot methods and using download mode and everything. I had no issues so I rooted it again, installed the 35B firmware from xdabbeb, as well as his 46A so everything is still stock, and running the latest android update, but the phone is still rooted. In any case it has been working fine for almost a week. Today it shut itself off again and now only blue screen when I turn it on. It barely gets past the LG logo before it blue screens again. I can't enter download mode because while installing the device on the PC it blue screens and crashes in download mode.
So I'm not sure what the deal is. I have the extended insurance and warranty but if you pull the battery for a couple hours and put it back in it will boot past the LG screen and start the OS, but the boot loading screen shows "Android" instead of "Verizon" so they'll know it's a custom firmware and do nothing for me. If anyone has any ideas I'm open to them! I would love to revert back to stock but with it crashing in download mode I can't even do that.
try these things but g3 is crap phone
you can try these things: use stock charger and try to boot then, i think its a 2amp charger. if it boots then swapping out battery with good one will likely cure it. its hard to find good new oem batteries though. usually that only works if you see a blue screen with a number on it. if its just a flat blue screen and connected to stock charger wont improve anything then its likely corrupted bootloader (hard brick). i currently am trying to resurrect one that is acting the same, it will only randomly turn on to blue screen, sometimes after days left with battery in while turned off. all the tricks like taking battery out, connecting to charger or computer without battery or holding power button to drain capacitors with batt out dont seem to help really. i am trying to get it to turn on into download mode at which point i will flash stock kitkat but seems like it wont happen. seems like lollipop 5.0 has something to do with this issue. there is an outfit on ebay that fixes it for 29bucks in texas. you will find them on youtube. g3 is crap. g2 was excellent except for touch screen issues.
can you explain what outfit in you are talking about? i am facing the same problem,
Simaramis said:
you can try these things: use stock charger and try to boot then, i think its a 2amp charger. if it boots then swapping out battery with good one will likely cure it. its hard to find good new oem batteries though. usually that only works if you see a blue screen with a number on it. if its just a flat blue screen and connected to stock charger wont improve anything then its likely corrupted bootloader (hard brick). i currently am trying to resurrect one that is acting the same, it will only randomly turn on to blue screen, sometimes after days left with battery in while turned off. all the tricks like taking battery out, connecting to charger or computer without battery or holding power button to drain capacitors with batt out dont seem to help really. i am trying to get it to turn on into download mode at which point i will flash stock kitkat but seems like it wont happen. seems like lollipop 5.0 has something to do with this issue. there is an outfit on ebay that fixes it for 29bucks in texas. you will find them on youtube. g3 is crap. g2 was excellent except for touch screen issues.
Click to expand...
Click to collapse
..
ARYA3 said:
..
Click to expand...
Click to collapse
Sorry "outfit on ebay" means seller on ebay. Don't remember what their name was. With the g3 it's like this: bootloop is usually fixable with a new battery. If it loads with charger connected, then definitely try new battery. If blue screen without a number, it's likely faulty motherboard. It may still boot occasionally, after leaving batt out or putting in freezer (yes freezer). If it does boot then do a backup immediately but phone is likely in need of new motherboard.
http://forum.xda-developers.com/showpost.php?p=70264535&postcount=9
BSOD is not so BSOD as you might think. This is actually the default view of the screen controller. It just means.... well... basicly... you're ****ed....
Something in the hardware doesn't fire up as it should and it's usually the SoC.... or the so called processor. Heating and baking might help if the problem is with low temperature welding but again it might not. And even if it does... it will be totally temporary (most cases weeks) because of the rapid increase/decrease of the processor temperature and thus welding joints... I'm basically in the same situation right now with the same phone... he fought well as it is 2014 phone after all but in the end it died heroically.... ;(
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
I have a G4 with Verizon and on Sunday I powered it down to swap my battery. I had about 30% left on the battery in the phone and a fully charged spare. I put the second battery in and since then it will not power on. I have tried both batteries and connected it to the power adapter... nothing happens (no lights, sounds, or vibrations). I called Verizon and they are sending me a refurb replacement but I'll need to send this one back once that device is up and running. I want to see if anyone has ideas on how to eliminate my data. I do have a SD card with my pictures so that's fine. I just want to erase everything else.
I have been playing with the phone for the past day and a half and I have gotten it to power on for a brief moment here or there. It is very random and sometimes it will show the LG splash screen and then it goes back out. I also have had it vibrate like it is turning on only not to show anything. A couple of times it has vibrated for over a minute straight before cutting back out. And while it was sitting on my desk it was rebooting itself several times earlier today until giving up. Also, when I plug it into my PC I do hear the Windows sound that you get when connecting a drive. But no drive letters appear. I am hopeful that I can get it to turn on long enough to erase everything. The phone is not rooted and is using the latest Android OS (I believe it was 5.1.1) that Verizon sent out in November.
I did not notice any other issues recently and I have swapped batteries dozens of times and never had this problem. It was powered off properly prior to this all happening. If anyone has any ideas of ways I can try to get it back on that would be great. Thank you!
Edit: Also, pressing the volume down and power together does nothing. Only way I have ever got the phone to respond in the past 24 hours is holding power for 20+ seconds and maybe it will work. But then it turns back off.
same here. dunno what to do since i bought mine used on swappa!
Sound like the hardware problem other users have had, including myself just about 2 weeks ago. If this is the case try putting the phone in the freezer for 10 to 20 minutes (I know it sounds crazy) but it worked for me and some others. I was able to power the phone up long enough to get it into recover (pressing the power button + volume down) long enough for me to wipe my data before sending it back. When I put the phone in the freezer I left the batter in and the back cover on.
jfriend33 said:
same here. dunno what to do since i bought mine used on swappa!
Click to expand...
Click to collapse
The phone is still not quite a year old. Contact LG as they have a 1 year warranty. You are running out of time though. They never asked me for a receipt as they knew within a year if it died the fix was on them.
LG G4 is a very vulnerable phone and LG’s Head of US Marketing has accepted that the LG g 4s manufactured before september 2015 had its own set of problems. Follow this guide https://appuals.com/fix-lg-g4-wont-turn/ in order to resolve your phone issues. If this doesn't help, you can send the phone for repair or replacement.
Hello everyone.
I have a 100% stock nexus 5X, never did any modification to it. One or two weeks ago I installed the official Android 8 OTA. Some hours ago while I was looking at some options of the google assistant (the one about enabling geolocalization-based tabs) my device froze and then shut down but didn't rebooted automatically. I wasn't able to boot it again since after nor I was able to boot in fastboot mode. When this happened the battery should have been at least at 50% of charge. If I connect it to the wall plug adapter it doesn't show the usual charging animation. The only result I was able to accomplish is that, while it was plugged in, I tried to boot in fastboot mode and it displayed the charging icon. I then unplugged it and tried to boot it but I failed and I wasn't able to reproduce that. Currently it's plugged in the wall-plug adapter and I can tell by the noise that it makes that is probably charging, but it doesn't display the usual charging animation. Any suggestion about what I could do?
That is what my phone did before it eventually bootlooped. It died while in use and did not bootloop until after recovery efforts. When it wouldn't start at all, I tried freezing/ice bath, and it would then actually boot into recovery and even got to where I could use adb to reinstall the OS. But it never would boot until I used a heat gun on it. After I recovered my data, it did eventually finally bootloop. But the dying and not turning on was due to the same cause as the boot loop.
This was back in June on 7.1.2, so perhaps your phone is doing something related to the OS update, but it really is acting just like mine did when it was dying.
Voicebox said:
That is what my phone did before it eventually bootlooped. It died while in use and did not bootloop until after recovery efforts. When it wouldn't start at all, I tried freezing/ice bath, and it would then actually boot into recovery and even got to where I could use adb to reinstall the OS. But it never would boot until I used a heat gun on it. After I recovered my data, it did eventually finally bootloop. But the dying and not turning on was due to the same cause as the boot loop.
This was back in June on 7.1.2, so perhaps your phone is doing something related to the OS update, but it really is acting just like mine did when it was dying.
Click to expand...
Click to collapse
Could you please give me more info about the freezing/ice bath process? You just put it in a freezer for some time? For how long?
Update: I was able to boot into fastboot mode, then I selected recovery mode and it displayed "GOOGLE" for a while, then powered off
Update 2: keeping the power button pressed for longer than usual it displayed "GOOLGE" for a while as usual during boot, but then powered off.
My Nexus 5x has the exact same problem.
Installed new App-Updates, for example the Facebook Beta, and after browsing on FB my phone died.
Android 8 September Patch, Locked Bootloader, 100% Stock
GTP95 said:
Could you please give me more info about the freezing/ice bath process? You just put it in a freezer for some time? For how long?
Click to expand...
Click to collapse
Some background. If this is the infamous boot loop issue, it is hardware based where possibly some solder is cracked around the CPU or some joints came apart, or something similar. The idea behind cooling (or heating the motherboard in say an oven), is that the contraction or expansion closes the crack for a limited amount of time. You then may have a chance to backup photos or data, reinstall the OS, etc. However, it does not fix the underlying problem, and will go back to dead when it warms up. However, if you are able to unlock the bootloader, you could try to install the fix that disables the big cores. If that works for your phone, then you would have a usable phone, but at reduced performance.
That fix in this thread below, though there is also a thread about doing it with a locked bootloader. Though I have never looked through that one so don't know about it.
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
About the freezing: Some people have just put it into the freezer for some period and then turned it on while inside the freezer. Then waited to see if it would boot. I tried this inside a ziploc bag because otherwise it got condensation when I pulled it out. I ended up just freezing first, then putting it inside a ziploc bag in an ice bath since that kept it cold and then I could bring it to the laptop and plug it in and re-installed the OS. Just freezing didn't get mine to boot, but other people have claimed to have gotten their phone to boot and yank data off after just freezing it.
You put it into the freezer until you think it has cooled down the motherboard since that's where the cracks would be. So that's maybe half an hour in the freezer or more depending how cold the freezer is. About half an hour worked for me since the refrigerator is only 2 years old and the freezer is really cold.
I did manage to reinstall the OS after freezing/ice bath, but the phone didn't actually fully boot until I used a hair dryer on the motherboard. But it then instantly died after unlocking the phone. Only using a heat gun on the motherboard got it to where I could boot and take data off of it. I even got it to work normally for 9 hours by using a heat gun since they are hot enough to actually melt solder.
The method to disable the big cores wasn't around back then, but I think I might have been able to get it on there if it had been.
Voicebox said:
Some background. If this is the infamous boot loop issue, it is hardware based where possibly some solder is cracked around the CPU or some joints came apart, or something similar. The idea behind cooling (or heating the motherboard in say an oven), is that the contraction or expansion closes the crack for a limited amount of time. You then may have a chance to backup photos or data, reinstall the OS, etc. However, it does not fix the underlying problem, and will go back to dead when it warms up. However, if you are able to unlock the bootloader, you could try to install the fix that disables the big cores. If that works for your phone, then you would have a usable phone, but at reduced performance.
That fix in this thread below, though there is also a thread about doing it with a locked bootloader. Though I have never looked through that one so don't know about it.
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
About the freezing: Some people have just put it into the freezer for some period and then turned it on while inside the freezer. Then waited to see if it would boot. I tried this inside a ziploc bag because otherwise it got condensation when I pulled it out. I ended up just freezing first, then putting it inside a ziploc bag in an ice bath since that kept it cold and then I could bring it to the laptop and plug it in and re-installed the OS. Just freezing didn't get mine to boot, but other people have claimed to have gotten their phone to boot and yank data off after just freezing it.
You put it into the freezer until you think it has cooled down the motherboard since that's where the cracks would be. So that's maybe half an hour in the freezer or more depending how cold the freezer is. About half an hour worked for me since the refrigerator is only 2 years old and the freezer is really cold.
I did manage to reinstall the OS after freezing/ice bath, but the phone didn't actually fully boot until I used a hair dryer on the motherboard. But it then instantly died after unlocking the phone. Only using a heat gun on the motherboard got it to where I could boot and take data off of it. I even got it to work normally for 9 hours by using a heat gun since they are hot enough to actually melt solder.
The method to disable the big cores wasn't around back then, but I think I might have been able to get it on there if it had been.
Click to expand...
Click to collapse
Thanks for your detailed answer, I would never have thought about disabling big cores. Anyway I checked and found out that my phone is still under the warranty protection (less than two months left, I was lucky!) so I decided to take the "official way" and bring it to LG's assistance. I've been told I would have to wait about 20 days, in the meantime I'm using my old Galaxy S3. I hope they will fix it so I don't loose anything but I will be happy anyway if they replace it because I have a backup of most things. I wonder though if with so powerful processors with so many cores this is an issue other phones are facing too and how much this is common.
GTP95 said:
Thanks for your detailed answer, I would never have thought about disabling big cores. Anyway I checked and found out that my phone is still under the warranty protection (less than two months left, I was lucky!) so I decided to take the "official way" and bring it to LG's assistance. I've been told I would have to wait about 20 days, in the meantime I'm using my old Galaxy S3. I hope they will fix it so I don't loose anything but I will be happy anyway if they replace it because I have a backup of most things. I wonder though if with so powerful processors with so many cores this is an issue other phones are facing too and how much this is common.
Click to expand...
Click to collapse
That is the best way to deal with it. They replace the motherboard and I'm guessing it is done as a complete unit, so I think you will lose all your info that isn't already saved. Though I'm not sure since I received a replacement from Google when mine died.
This same issue came up on the LG G4 and another LG phone that came out at the same time as the Nexus 5X. So hopefully LG figured out what the underlying issue is and will not make the same mistake again. But I will not be buying another LG phone for a long time. As an example, I would have considered the large version of the Pixel 2. But that phone is made by LG, so I just went with the Moto X4 and I'll decide next year if I stay with Fi or switch back to a regular provider.