Today on my way to work I was playing music through my bluetooth and the music stopped. I went to reset bluetooth and it took almost 3 mintues to turn off. When I went to turn it back on, it wouldn't. I powered off and reset the phone. After, it got stuck in a bootloop. LG logo for about 7-8 secs and restarts.
Before the bootloop, I was noticing a few weird things: A notification of USB Options was always up, was saying I was using my phone as a USB Power Supply. If I changed the options it would revert back to USB PwrSply. I noticed the battery life was getting a lot worse. Also, when plugged into Quick Charge it would not say "Quick Charging" anymore.
I can get into the Recovery menu, but all options revert to the bootloop.
I can get to the Download menu. After about a few seconds of sitting on the Download menu, it starts the LG logo bootloop.
I have not tried to flash another stock ROM. I have downloaded the LGUp program, Uppercut, LG Mobile Support Tool, and LG Mobile Driver. I also downloaded the previous 1BA firmware kdz file.
I believe I have the knowledge to reflash properly, but I do not want to make the phone worse or lose my data. Plus, I don't want to void the warranty.
TL;DR I have bootloop and want to save my data!
Any suggestions would be very much appreciated! Thank you!
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Either way, LG will definitely take care of it under warranty since those morons can't seem to make a decent heat sink that lasts. Every LG flagship phone since the G4 has had this problem. I am sure the V30 and G7 will be no different -- they just haven't been out long enough yet.
-- Brian
runningnak3d said:
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Either way, LG will definitely take care of it under warranty since those morons can't seem to make a decent heat sink that lasts. Every LG flagship phone since the G4 has had this problem. I am sure the V30 and G7 will be no different -- they just haven't been out long enough yet.
-- Brian
Click to expand...
Click to collapse
I was hoping that this wasn't the issue. I was hoping that it was from the 1CA update, because the other random problems seemed to have started when it updated. Should I at least try to reflash? Would reflashing to a stock/OEM ROM (the one i mentioned above) void the warranty?
Also, when I restarted the phone today, that was the first restart that I have done since the update. Not sure if that means anything, but maybe??? lol
No, flashing a KDZ does not void the warranty even by LGs terms.
In the US rooting your phone doesn't void the warranty either .. no matter what OEMs will have you believe.
-- Brian
runningnak3d said:
No, flashing a KDZ does not void the warranty even by LGs terms.
In the US rooting your phone doesn't void the warranty either .. no matter what OEMs will have you believe.
-- Brian
Click to expand...
Click to collapse
Awesome! That's definitely good to know. Thanks.
I'm going to attempt to downgrade flash it. If it doesn't work, I'll contact LG. I dont really care about buying a new phone. My data on it is worth WAY more to me than the phone. (Guess I really should start backing up my stuff XD )
If you have any suggestions as to recovering my data, even if it kills the phone, I'm all ears!
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Dart_Fur said:
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Click to expand...
Click to collapse
I'm not sure to be honest, your situation seems strange
Was it hot and was your phone in the sun during your trip to work? Overheating can make weird things happen.
lakingslayer said:
Was it hot and was your phone in the sun during your trip to work? Overheating can make weird things happen.
Click to expand...
Click to collapse
It wasn't hot at all, I had the A/C in my car on and it sets on a car mount that mounts to the air vent. It gets direct A/C. I didn't have it charging either.
All I did was connect my phone to Bluetooth, play a mix, and drive 15mins to work at 6am in the morning. It was still dark and cool out. The music stopped and I tried to reset bluetooth. It took forever to turn off and wouldnt turn back on. I reset phone and BOOTLOOP. ???
There is no damage to the phone physically. I don't think I've ever dropped it ever. It's gotten hot a couple times, but that was months and months ago.
I've never had a problem with this phone since I got it almost 2 years ago, since the 1CA update, I had a couple bugs, now this bootloop.
Dart_Fur said:
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Click to expand...
Click to collapse
I hope you got your data off before you started messing with it.. your phone is dead.. Runningnak3d gave you a clear warning
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Click to expand...
Click to collapse
Related
I'm pretty lost on this one and after hours of searching, have not the slightly clue how (or if) to fix it...if it can even be fixed.
Past few days I've noticed the phone randomly rebooting, some of the times it says my battery is 0% when it's almost full. Today I went to go wipe it and reflash Pure Nexus. While wiping and flashing it, it ended up in a boot loop. I've tried everything to get the phone back up and running. I've tried attempting to flash different ROMs, the stock images (tried T and Q), doing a hard reset, factory reset. Literally everything under the sun that I know to do or have looked up.
Right now the most my phone will do is turn on, shows the Google screen, the reboots and repeats. Sometimes when the phone is off, I have to hold the power button for a minute or 2 to get it to turn on. Still, can only get in the bootloader, but can't get it to boot further than that.
Any help is appreciated, I'm at a loss on this one....and phoneless. :crying:
Pretty weird, if nothing works you should flash stock images, lock bootloader and RMA.
Techno Peter said:
Pretty weird, if nothing works you should flash stock images, lock bootloader and RMA.
Click to expand...
Click to collapse
I also tried to lock the bootloader and re-unlock it, with no luck. Called Google and they weren't any help, least outside of what I've already tried. I'll be calling Huawei tomorrow when they open.
As of now, it seems when I unplug my phone, it just turns off. I plug it back in, it goes into bootloop (without me hitting power button). Sort of wondering now if the battery just took a dump?
The phone started acting funny every since I tried to Android N. I'm going to attempt to try flashing N again, just for kicks.
I found a USB charger at work. While not a fast charging one, it was enough to allow my phone to boot up. Apparently there is something wrong with the battery some how. When it booted up, it showed I still have 48% of battery left so I took it off the charger. About 5min after booting it shut down again. Now that it's on the charger again, it'll boot back up and now shows 1% of battery.
I can't figure out for the life of me what the deal is. Looking like I'll need to lock the bootloader and RMA it back for warranty and get a properly operating phone. I'm curious how quick this will happen to get a working phone? I'm up for an upgrade through Sprint, think at this point it's best to go get a new phone to use in the meantime since I have no old phones to use in the meantime. If Huawei gets me a new phone within 14 days I can take the new one back and rock on with Nexus. Kind of sucks, but just my luck.
InfiniteReality said:
I found a USB charger at work. While not a fast charging one, it was enough to allow my phone to boot up. Apparently there is something wrong with the battery some how. When it booted up, it showed I still have 48% of battery left so I took it off the charger. About 5min after booting it shut down again. Now that it's on the charger again, it'll boot back up and now shows 1% of battery.
I can't figure out for the life of me what the deal is. Looking like I'll need to lock the bootloader and RMA it back for warranty and get a properly operating phone. I'm curious how quick this will happen to get a working phone? I'm up for an upgrade through Sprint, think at this point it's best to go get a new phone to use in the meantime since I have no old phones to use in the meantime. If Huawei gets me a new phone within 14 days I can take the new one back and rock on with Nexus. Kind of sucks, but just my luck.
Click to expand...
Click to collapse
That's exactly what you should do. Most probably the battery is dead or malfunctioning. Charge it with that spare charger for a few hours, then restore stock and lock the bootloader. Finally, turn it up for RMA.
I never had a single out-of-the-box issue with any of my 5 Nexus devices. I hope the replacement that you receive will be up to the satisfaction.
Techno Peter said:
Pretty weird, if nothing works you should flash stock images, lock bootloader and RMA.
Click to expand...
Click to collapse
DJBhardwaj said:
That's exactly what you should do. Most probably the battery is dead or malfunctioning. Charge it with that spare charger for a few hours, then restore stock and lock the bootloader. Finally, turn it up for RMA.
I never had a single out-of-the-box issue with any of my 5 Nexus devices. I hope the replacement that you receive will be up to the satisfaction.
Click to expand...
Click to collapse
Thanks for the confidence. I'll do just as suggested and return it.
I'm up for an upgrade, although I have to do online so I don't have to pay an extra $30/month for a phone I'll sell after getting my 6P back. I hate sprint not letting me do it in the store, such a PITA. If I do online I can just get the discount and sign a 2yr contract which is fine with me. Any idea if they will ship a new phone so I'm not without a phone for week(s)?
InfiniteReality said:
Thanks for the confidence. I'll do just as suggested and return it.
I'm up for an upgrade, although I have to do online so I don't have to pay an extra $30/month for a phone I'll sell after getting my 6P back. I hate sprint not letting me do it in the store, such a PITA. If I do online I can just get the discount and sign a 2yr contract which is fine with me. Any idea if they will ship a new phone so I'm not without a phone for week(s)?
Click to expand...
Click to collapse
Sorry, but I never had any experience with an international carrier like Sprint, so can't say. Someone here would be able to answer this better than me. :highfive:
Thanks for the quick reply. I'll call Huawei here in a few and start the process and find out. Fingers crossed they will ship a new phone, even with a temp hold on the money while I send this broken one back. I'll post what I find out, just in case anyone else is curious and searching for the answer.
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
hurricane flow said:
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
Click to expand...
Click to collapse
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
eidairaman1 said:
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
Click to expand...
Click to collapse
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
I will follow up on the battery swap when mine arrives.
hurricane flow said:
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
Click to expand...
Click to collapse
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
eidairaman1 said:
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
Click to expand...
Click to collapse
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
hurricane flow said:
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
Click to expand...
Click to collapse
I thought it was a bad rom flash as well or SuperSU causing it, well I found another article stating they replaced the battery and the issue went away. I think the phone was stating a bad POST so it would restart
My nexus 6p suddenly won't start, I've had my phone since May 2016 so more than a year now.
I've flashed a custom ROM onto it, I'm sure this isn't a software issue because it's been running fine since I bought it (and flashed it) and I followed all the instructions correctly.
I've read through this thread and tried the solutions there, hold the power button for longer than usual (a few minutes), hold the volume down button and power together, hold the volume down button then charge it, now hold the power button. I tried all 3 solutions which worked for many in that thread, but not me.
This all started 2 days ago, with no changes software-wise and using the same configuration as when I first flashed it, I opened the app HERE Maps and then my phone froze, totally stuck and unresponsive, restarting was no good, I had to go into TWRP and wipe the cache and dalvik cache, and it booted fine.
Today, same thing, I opened up HERE Maps and it got stuck again, I now notice that it takes longer than usual to start up via the power button, and wiping the cache and dalvik cache does not work anymore, it stucks on boot.
Now, my phone is not able to start at all. I think this is a hardware-related issue.
So quick recap:
1. Opened HERE Maps and gets frozen
2. Wiping cache and dalvik cache no longer works, stuck on boot.
3. Phone not able to start at all.
I am out of warranty period-wise, but I also custom it, so obviously my warranty is out the window. I need some insight from you guys here at XDA before I buy another costly phone.
someRandomSamaritan said:
...Now, my phone is not able to start at all. I think this is a hardware-related issue...
Click to expand...
Click to collapse
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
v12xke said:
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
Click to expand...
Click to collapse
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Can you access recovery or bootloader mode?
If within warranty, contact google/Huawei depending on where you purchased the phone from.
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Is it recognized at all when you plug a data cable to your PC? Your phone may be stuck in Qualcomm's EDL mode. Search.
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
Click to expand...
Click to collapse
This is a possible option..I'll try that tomorrow when it's morning
Anything else I could try? I think the most obvious methods are not available for me with this kinda situation
someRandomSamaritan said:
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
Click to expand...
Click to collapse
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
v12xke said:
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
Click to expand...
Click to collapse
Okay, this is helpful, you guys seems to think it is in EDL mode (which I haven't heard of until now), I'll try this and hopefully a driver loads or something
EDIT: nope, no drivers are loading, doesn't seem to be anything new in device manager, no device plug in sound, how sure are you that I'm in EDL mode?
It did work a few times yesterday (being able to boot into TWRP and wiping cache and dalvik cache), but now I'm not so lucky, it doesn't work anymore. I don't believe my phone is completely dead for some reason, I still do believe it can be saved. Hopefully I'm right :|
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
someRandomSamaritan said:
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
Click to expand...
Click to collapse
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2. They have project treble.
Your issue is different than most others. Most n6p with issues are bootlooping devices.
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
BadBoy2K7 said:
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
Click to expand...
Click to collapse
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2.
Click to expand...
Click to collapse
Pixel 2 is some expensive thing, out of my budget
someRandomSamaritan said:
Pixel 2 is some expensive thing, out of my budget
Click to expand...
Click to collapse
Then you should look for alternatives. Perhaps OnePlus 5T, etc.
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
someRandomSamaritan said:
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
Click to expand...
Click to collapse
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
I was facing bootlooping problem with my Nexus 6P and bootloader was locked so was unable to flash ROM by any mean.
So I tried following few threads and did "fastboot continue" and my device is not showing any sign of power since then. When connected to PC then no USB connection is there.
Is there any suggestions that can solve issue?
someRandomSamaritan said:
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
Click to expand...
Click to collapse
No. Unfortunately this happened to me last month and ive had the phone for almost 2 years now. Its sad because others are having the same issue and I think the hardware is faulty
I just called up a local phone repair and they said from their experience of repairing nexus 6p phones, most (if not all) of them had dead motherboards. The technician told me to get a new model of a phone and skip the 6p as it is a poorly built phone.
I consider saving up for a pixel..
NoobInToto said:
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
Click to expand...
Click to collapse
Ive heard of people baking motherboard on Nexus 5x and many other phones to reflow the solder.
I have an LG G6, international version (H870DS) that has been having bootloop issues for a while now. For the first few months it would come and go -- sometimes it would be a week between issues, sometimes just a few minutes. I tried many things, multiple factory resets, removed the SD card, deleted possible troubles apps, basically anything I could find online to try. But, for a while the phone would work pretty much normally until it decided to restart and loop.
But... about two weeks ago the phone got into its bootloop and never came out -- I can't get past the LG logo screen anymore. If I let the phone go for a while eventually it gets to a green screen talking about a RAM dump. One time I managed to get it to a screen talking about unlocking the bootloader but that part got a bit over my head. Basically, I can let the batter die but as soon as I plug it in, the phone starts lopping again for 15 minutes or so, eventually ending at that green screen.
Over the last few days I have tried downloading a stock KDZ file to try to flash stock ROM back onto the phone. The problem is, I can't get the phone to communicate with my computer no matter what I do. I've downloaded LGUP, installed all the drivers, tried the LG Flash Tool and pretty much anything else I could find -- but I just can't get anything to recognize the phone, even when I get it into download mode. I know the problem isn't with drivers because when I try my wife's identical G6 on my computer it gets recognized right away.
I should mention that I never tried to tweak anything with the phone -- the issue has been occurring since it was basically brand new. I am by no means an idiot when it comes to tech but also far from an expert, but I have done my research and tried everything I could.
So -- basically I am out of options and appealing to anyone who can help. I currently live in Africa and have no access to LG service centers. I have spent upwards of 10 hours trying to figure this out now and I just don't know what else to try. Any tips or advice would be incredibly appreciated. Thank you!
This looks like a hardware failure. if you have warranty, you should send it back to them. The seller can't take care of the warranty ?
Well, it happened... I was browsing XDA on my beautiful V20 when suddenly I'm looking a the boot logo.. and then a black screen. I tried to turn it on a million and one times, various battery pulls, plugging into every PC in the house (and it wasn't detected... at all). The only thing it would do is vibrate one time after holding the power button. I was at a loss.. If my computer couldn't recognize it, I couldn't fix it.
Thankfully, it was still under manufacturer warranty. I sent it in holding my breath, hoping they wouldn't be able to tell that I had Dirty Santa'd the hell out of the bootloader. As luck would have it, not even 24 hours later I received an email saying my phone had been repaired. And what did they do to fix my V20?
... they replaced the flash memory.
LG's track record with memory hasn't been the greatest the past couple of years, so I'm wondering if the memory bug is going to happen to us.
FYI: My V20 was a US Cellular US996 running WETA ROM with barely any tweaks other than what came with the ROM.
I have 2 v20s that I have bricked 3 times for various reasons. When I sent them off for repair, LG replaced the NAND twice, and the entire logic board once.
At the time I thought maybe it was just easier for them to replace the NAND than to re-flash it, but I think you may be on to something. Maybe they know that the NAND they used is flaky, so they don't even try and flash it.
-- Brian