My Nexus 5X has just decided to die.
It isnt bootlooping, it just will not come on. It wont even open the bootloader. So i cant flash it or anything; anywayy, i purchased a Nexus 6p today because i wanted something similar to what i had been using, blah blah. So, i got home with it, and im looking at reviews and just come across the fact that its only bloody got the same bootloop issue that *might* crop up. Ffs. haha.
So my question is; am i to understand that the 6P will infact bootloop? Its just a matter of time? Or is it that it might not? I was afraid of the bootloop of my 5X and it lasted just over a year before its untimely death.
Should i flash it premeturely so it prevents it? Idk. Please can someone enlighten me?
Thanks Guys
K
It is not guaranteed but it is probable that it will happen at some point. I have had a Nexus 6P and Nexus 5X both bootloop.
I would suggest selling the 6P while you can and purchase a used Pixel if you want the same experience. You can skip Pixel 2 to reduce cost.
Sent from my Pixel XL using XDA-Developers Legacy app
Kushina_1337 said:
My Nexus 5X has just decided to die.
It isnt bootlooping, it just will not come on. It wont even open the bootloader. So i cant flash it or anything; anywayy, i purchased a Nexus 6p today because i wanted something similar to what i had been using, blah blah. So, i got home with it, and im looking at reviews and just come across the fact that its only bloody got the same bootloop issue that *might* crop up. Ffs. haha.
So my question is; am i to understand that the 6P will infact bootloop? Its just a matter of time? Or is it that it might not? I was afraid of the bootloop of my 5X and it lasted just over a year before its untimely death.
Should i flash it premeturely so it prevents it? Idk. Please can someone enlighten me?
Thanks Guys
K
Click to expand...
Click to collapse
The 5X was prone to circuit board failure. It would do various things from deactivate the fingerprint sensor to make the screen go off and give the appearance that it wasn't turning on but in fact it just wasn't displaying anything. Not I don't know what truly happened to you but the 5x was pretty unusable at this point and the manufacturers didn't seem to want to do anything about it.
The 6p which is what I am using right now is victim to a CPU Hardware defect which can throw it into a bootloop. Not everybody will have it. Some people will take a long time to have it. I used mine for a year-and-a-half and I am still using it now even after it went through the bootloop issue. My recommendation to you would be to unlock the bootloader and to make sure that you have USB debugging turned on so you can be prepared to flash a fix if you have to. I was able to flash the boot loop fix without losing any of my data and although the phone is a little bit slower than when it was out of the box it is still a perfectly good and usable phone for day-to-day tasks and to do things like watch movies take pictures Etc. I do not know if my phone will decline to an even worse state but for now 2 years after getting it it's still running fine
Sent from my Nexus 6P using Tapatalk
We have two of them, my wife and I, and have for quite some time. Both were bought used. I keep them updated. So far no boot loops or any other issues. Been over a year for both of them.
I bought 2 Nexus 5Xs to my parents and both died after about a year and a half. Sent them both to LG, they fixed them for free. I think they replaced the motherboards, but not sure.
I bought mine in Sept 2015 - the week the device was released.
During that time I was horrible with charging patterns - sometimes leaving it on the charger for days at a time.
I've had to replace my battery once due to early shutdown happening at 50-60%, however at no point did I ever see signs and symptoms of BLOD.
My mom also has a 6P, and she's much better at the charging issues, usually leaving it dead for days lol. She's beginning to show battery issues, with early shutdown happening around 10-15%, however she got hers in April of 2016.
Have a 128gb Nexus 6p and it's still going without any issues.
No such problems with either of the ones I have had. Battery degradation I have had but never bootloops.
Kushina_1337 said:
My Nexus 5X has just decided to die.
It isnt bootlooping, it just will not come on. It wont even open the bootloader. So i cant flash it or anything; anywayy, i purchased a Nexus 6p today because i wanted something similar to what i had been using, blah blah. So, i got home with it, and im looking at reviews and just come across the fact that its only bloody got the same bootloop issue that *might* crop up. Ffs. haha.
So my question is; am i to understand that the 6P will infact bootloop? Its just a matter of time? Or is it that it might not? I was afraid of the bootloop of my 5X and it lasted just over a year before its untimely death.
Should i flash it premeturely so it prevents it? Idk. Please can someone enlighten me?
Thanks Guys
K
Click to expand...
Click to collapse
My wife replaced hers with a Pixel because of premature shutdown last year. The other day I put in a new battery and now it's like a new phone. I put my Moto Z in the drawer and use the 6P as my daily driver. I think it's on its final update so might as well unlock the bootloader and try out some roms. It runs well on Los14.1 and AICP13. Currently trying out SuperXE 8.1 with ElementalX 8.1 kernel
Related
Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
S.H.A.D.E said:
Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
Click to expand...
Click to collapse
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
propably you could check the rev of those n4's (asking them in pm's). i can't imagine rev11+ have this problem anymore. I still won't believe this happened without a reason
S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
These many people you speak of? That's not even half possible for it to RLOD on pure stock without any mods it's just to save the hardware its the phones built in safety net...unless you plan on OCing to 1.98ghz and set it to performance and run antutu that will most likely do it for you
Sent from my Nexus 4 using xda app-developers app
Hi,
It happened wih or without running an Antutu bench. Yes some users have reported the red light on stock with rev 10 or with rev 11.
Antutu is not directly the culprit, it's due to a bad read of battery stuff (in a stress condition even at 50% battery the phone think you are out of battery then shutdown + heat, there is an issue with some phone about the battery contact inside the phone). If it's happen you can try to let your phone in charging for hours, sometimes it's enough. But the better thing is to open your phone then disconnect / reconnect the battery.
It happened also while flashing something in recovery mod, 40% battery, flash then reboot and bam red light...
Also on a French forum it happened during a download while browsing...
I agree we not know all the conditions together when it happened but it seems this is slightly random. Maybe a combination of circumstances...
It's "just" related to some weird battery reading issue.
For example I ran a bunch of Antutu bench with / without overclocking at different battery % (even at 11% battery ) without any issues, at least until today...
Take a look here: http://forum.xda-developers.com/showthread.php?p=36304348
So does this problem happen to everybody or is only a minority of nexus 4 users affected? Do you think google would've fixed this problem by now??
Re,
It seems it's a minority phones who are concerned...
I don't know if Lg / Google have worked on the problem. As I read maybe the rev 11 are less concerned? But I'm not sure...
Don't be afraid, use your phone and if that happens rma or open your phone, there is always a solution
Alright, read a lot of threads and it looks like removing the battery and starting it again works perfectly. I also read somewhere that its due to too much pressure being applied on the thing the connects the battery to the phone.. - http://forum.xda-developers.com/showthread.php?t=2128392&highlight=red+light+of+death&page=2
Yes, it's what I said, ah I forgot this link.
When you search, you find
Happened to me a few days after I got it (100%stock, not rooted); I left it charging for some time and it turned on again like nothing happened. Didn't happened since.
Only time I had it was when I first rooted.
It got stuck in a boot loop on the "X" screen and when I rebooted to clear the cache the red light flashed and I had to hold the power button in to turn it off.
Booted into recover fine after that.
No issues since.
Alright that's good to hear. When did you guys get your nexus?? Maybe google resolved this issue.
I got mine very recently ordered in late February. It did red light because I flashed a mod which was for the nexus 7 but i flashed it on my nexus 4. I just went into recovery and flashed stock, phone was fine.
Sent from my Nexus 4 using xda app-developers app
Alright. Sounds good.
Got mine last week but it's a Rev 10 not an 11.
indoh said:
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Click to expand...
Click to collapse
That is not true.. Red light appears due to some small chip next to the battery which is hardly put in there, you just need to release some pressure and it will be fine.. (there's a youtube video)
Loosen the screws?? Do you have a link to the YT video?
Ordered mine when they were first available, got it 2-3 weeks later (end of November).
Got a bricked rev11 301k here. Tried everything untill I get my replacement (takes a bit longer since I live in holland). Check out http://forum.xda-developers.com/showthread.php?t=2177787&highlight=nexus+4+bricked for more info. Now I try to drain the battery and let it charge (put it in a cold enviroment for a full 24 hrs. Got past the google logo for half a second and saw the stock recovery before it went dead again
Hi guys, I have bought a nexus 6P secondhand but I'm dealing with the problem of random shutdowns. After that it won't boot unless it is hooked to a charger. Some facts that I think might be of some influence or what I have tried:
- I bought it with Cyanogenmod 14.1, first day flashed back to stock 7.0 but kept my bootloader unlocked;
- Today I flashed an OTA update to 7.1.1;
- It happens random while using the phone, but I manage to reproduce the failure when using Google Camera and take pictures very rapidly (don't really know what the phone activity is at that moment)
- I've got a new battery on the way, might that be the issue?
- Battery status (percentage etc) doesn't make a difference. Might as well happen at 100%
- It doesn't happen while on the charger;
- It didn't happen in safe mode (didn't test this for too long though, but the fast camera action didn't kill the phone;
Does these descriptions make any bells rinkle? For me it looks like a defective battery but I'm happy to hear some expert about this
Thank you all for reading!
Yup, mine does the same thing. I believe it is supposed to be fixed with the new 7.1 release. Its the most inconvenient thing ever. I rarely takes pics now because nobody has a usb-c charger to get my phone turned back on. I'm running stock 7.0. It's not your battery.
Well that would kinda suck, I just updated to 7.1.1 and the problem is still there. Do you have a source for this thing?
I had the same random reboots.
I too suffered from random reboots in 7.1.1 dp2. They increased in frequency gradually. One night, it stuck in bootloop. Couldn't even boot into recovery. Browsed through threads here and reddit posts. All said the only solution was to RMA as without recovery nothing is possible. Huawei is replacing the motherboard as it's under warranty.
I just updated to 7.1.1 and I also can still confirm it's happen. I called huawei and they told me it was a software issue and it's not resolved and there is no fix other than to load 6.x on the phone. So basically, I we have a turd of a phone and nobody seems to want to fix it. Google told me it was a hardware issue and now Hauwei tells me it's a software issue. Maybe it's time for a new phone.
Just curious but have any of you flashed the official release images directly from Google through ADP with the FlashAll.bat command that it includes? Keeping your bootloader unlocked, but flashing everything to make sure your device is 100% stock and as fresh as it can be?
Messing with OTA's and other stuff like CM, I would definitely flash it this way and test it bone stock before venturing back into the Custom Rom land as major OS changes (from 6.0 to 7.0, etc) always seem to have residual glitches just like this.
IM0001 said:
Just curious but have any of you flashed the official release images directly from Google through ADP with the FlashAll.bat command that it includes? Keeping your bootloader unlocked, but flashing everything to make sure your device is 100% stock and as fresh as it can be?
Messing with OTA's and other stuff like CM, I would definitely flash it this way and test it bone stock before venturing back into the Custom Rom land as major OS changes (from 6.0 to 7.0, etc) always seem to have residual glitches just like this.
Click to expand...
Click to collapse
I loaded the image directly from google. I've never rooted or loaded a rom on this phone. I've only run factory images. I don't have the time to tinker like I used to.
Well that is downright strange then. There really doesn't seem to be any device that doesn't at least have a small share of mystery in some of it's problems is there? Lol.
Well that was how I reverted from CM to stock 7.0, by using the flash-all function (even though the flash all didn't work, had to flash the seperate files, but result was the same). The 7.1.1 upgrade was with a OTA flash using ADB sideload because I was rooted and TWRP recovery was active, so the OTA update didn't work for me. To be honest, I don't think my problem is a software issue. Is there any 'deeper' software than the complete rom? Is the kernel flashed seperately?
IM0001 said:
Well that is downright strange then. There really doesn't seem to be any device that doesn't at least have a small share of mystery in some of it's problems is there? Lol.
Click to expand...
Click to collapse
This fiasco has been happening for tons of people for weeks now, including me. Mine was just 2 weeks out of warranty, both google and huawei are pointing fingers at each other and nobody cares. I have tried all the methods possible, to flash different versions of pure factory image, nothing worked.
What charger did everyone use to get it backup a running?
Mine just shutdown this morning and using the USB A-to-C cable on a computer/car/wall outlet it didn't even recognize it was plugged. Google wants to RMA it (third one in 14 months of ownership) and I'm fighting over their 5 days delivery time for a new one.
also face this problem previously and Huawei replace battery. just 1 week before the warranty run out
Sent from my Nexus 6P using Tapatalk
rmoney said:
What charger did everyone use to get it backup a running?
Mine just shutdown this morning and using the USB A-to-C cable on a computer/car/wall outlet it didn't even recognize it was plugged. Google wants to RMA it (third one in 14 months of ownership) and I'm fighting over their 5 days delivery time for a new one.
Click to expand...
Click to collapse
Every charger worked for me. Now even carry a powerbank with me for when it lets me down outdoors I can get it powered on again. Plugging it in the PC also works just fine. Even a standard samsung charger (with micro-usb -> usb C adapter) works.
hah! Mine just started doing this!
I got the phone back from huawei for the 15% battery issue.. and it came back with this issue after going to 7.1.1
Strange! Mine doesn't seem to be related to any firmware state. It had this with CM14.1, stock 7.0 (factory image), and 7.1.1 (OTA flash). The only thing that is in common is that the bootloader is unlocked. Can this have any influence?
Hafidel36 said:
Strange! Mine doesn't seem to be related to any firmware state. It had this with CM14.1, stock 7.0 (factory image), and 7.1.1 (OTA flash). The only thing that is in common is that the bootloader is unlocked. Can this have any influence?
Click to expand...
Click to collapse
Mine is locked, on 7.0 I didn't have this issue.. on 7.1.1 It started.
on developer previews for it wasn't an issue either..
This is the absolute worst. Phones dying consistently at 15%. Sometimes it'll even shut down at like 30-40%. Absolutely ridiculous. I'm getting a new phone.
andrewnelson23 said:
This is the absolute worst. Phones dying consistently at 15%. Sometimes it'll even shut down at like 30-40%. Absolutely ridiculous. I'm getting a new phone.
Click to expand...
Click to collapse
That seems to be another know defect, you should look it up on here. Plenty of people are having that problem, but it is different from this thread.
I am having the same problem too! I was trying to raise this for two times on both XDA and reddit and no body seemed to care until you came up with this!
Mine randomly happens when taking photos with HDR+ and with the battery less than 50% (based on my observation). I replaced the battery by myself not long ago though.
Huawei says going back to 6.0.1 will fix the issue... and is blaming google, saying their pixel devices have this issue on 7.1.1 too.
Hey all,
I'd like to get a better view on how much 6p's are affected by this issue. I really have no clue what % we're talking about. So.. Is your 6p affected by the early shutdown issue? If not, could you tell us when you've bought your phone and, if you have accubattery installed, the capacity (health) of your battery?
Thanks in advance!
Sure am, and it's died at as high as 45% and as low as 15%. Accubattery pegs the health at about 60% and I've only had the phone about 15 months. Wanted this to be the first one I kept for two years.... Not looking likely with my 2 hours of SOT.
Lulzmaster said:
Sure am, and it's died at as high as 45% and as low as 15%. Accubattery pegs the health at about 60% and I've only had the phone about 15 months. Wanted this to be the first one I kept for two years.... Not looking likely with my 2 hours of SOT.
Click to expand...
Click to collapse
Yeah this is really bad. Fortunately, I've got a new battery in it thanks to warranty. But now I'm really afraid to use the phone. I'm waiting on a response from Google on all this before using my phone again. I've used it after repair for a couple of days to see if the problem was fixed: it was.
Can't wait for the oneplus 5 to be released.
swa100 said:
Yeah this is really bad. Fortunately, I've got a new battery in it thanks to warranty. But now I'm really afraid to use the phone. I'm waiting on a response from Google on all this before using my phone again. I've used it after repair for a couple of days to see if the problem was fixed: it was.
Can't wait for the oneplus 5 to be released.
Click to expand...
Click to collapse
It infuriates me because I love the phone and don't want to buy a new one.... But I can't have something that is going to die on me. I'm pretty pissed off with the state of Google hardware in general right now. Both the 5x and 6P are bootlooping and dying for no discernible reason, the Pixel and 6P have battery issues, although the Pixel, so far at least, doesn't seem to have them nearly as widespread. I feel like my phone is a ticking time bomb and that's really, really not cool.
Plus the supply issues with the Pixel all but rule that out as a replacement anyway.
I've owned three of the last four generations of Nexus phones, and while I was elated with the 6P when I got it, that glow has faded significantly. .
Lulzmaster said:
It infuriates me because I love the phone and don't want to buy a new one.... But I can't have something that is going to die on me. I'm pretty pissed off with the state of Google hardware in general right now. Both the 5x and 6P are bootlooping and dying for no discernible reason, the Pixel and 6P have battery issues, although the Pixel, so far at least, doesn't seem to have them nearly as widespread. I feel like my phone is a ticking time bomb and that's really, really not cool.
Plus the supply issues with the Pixel all but rule that out as a replacement anyway.
I've owned three of the last four generations of Nexus phones, and while I was elated with the 6P when I got it, that glow has faded significantly. .
Click to expand...
Click to collapse
Yeah that ticking timebomb feeling is really annoying. I don't even dare to use the phone now it actually works, because I'm afraid that I'll f*ck up my new battery. I'm trying to wait for an official response from Google, but it's hard. I really want to know if some software f*ckup is causing these batteries to degrade faster.
I had the issue also. I bought mine in October 2015. Accubattery was showing the battery at 60% and was shutting down at random once it got below 40%. Google sent me a refurbished phone even though it was out of warranty. So far this one hasn't shut down early and accubattery shows 95%.
I got my phone mid February (Best Buy) last year and do not have the problem. Accubattery shows my battery health at 93% (3220mah). But I also protect my battery as much as possible with when to charge and never let my phone stay plugged in when topped off either.
Never had early shutdown. Had my 6p for a few months. Accubattery shows 99%.
Sent from my Nexus 6P using Tapatalk
murphyjasonc said:
I had the issue also. I bought mine in October 2015. Accubattery was showing the battery at 60% and was shutting down at random once it got below 40%. Google sent me a refurbished phone even though it was out of warranty. So far this one hasn't shut down early and accubattery shows 95%.
Click to expand...
Click to collapse
Does the battery life itself seem to be better as well? Part of my problem is that with the screen on I'm looking at an obscene drain. According to accubattery my average drain with screen on is 1100ma/h. Hell it dropped two percent in the time it took me to type this.
Lulzmaster said:
Does the battery life itself seem to be better as well? Part of my problem is that with the screen on I'm looking at an obscene drain. According to accubattery my average drain with screen on is 1100ma/h. Hell it dropped two percent in the time it took me to type this.
Click to expand...
Click to collapse
Yeah the battery life is a lot better. I was doing good to get 2 hours SOT on my old phone. Same setup on this one is getting 4 to 4.5 hours SOT. I don't recall what my average drain was before but now it's about 450 ma/h. Here is a screenshot.
murphyjasonc said:
Yeah the battery life is a lot better. I was doing good to get 2 hours SOT on my old phone. Same setup on this one is getting 4 to 4.5 hours SOT. I don't recall what my average drain was before but now it's about 450 ma/h. Here is a screenshot.
Click to expand...
Click to collapse
I may have to give that a shot then. Buying a new one really isn't in the budget right now. Did you flash back to stock or relock the bootloader before you sent it in?
Never had early shutdown, and have had my 6P since launch.... Mostly custom AOSP roms....
Lulzmaster said:
I may have to give that a shot then. Buying a new one really isn't in the budget right now. Did you flash back to stock or relock the bootloader before you sent it in?
Click to expand...
Click to collapse
I'm not sure it was necessary but I flashed back to stock and relocked bootloader. I didn't want to take any chances especially since they were replacing it out of warranty. Worst case I could have used Nexus protect either way. They tried to get me to do that when I called. I refused and once I mentioned the Reddit thread they agreed to replace. Saved me the $79.00 deductible.
Nope
:good::good:We have two in our family and neither one is affected. One was purchased Late 2015 and another early 2016. Both show over 95% capacity in Accubattery (mine is 97%) and I can run the battery down to 1%. Both are stock 7.1.1 one is unlocked and rooted, and the other has never been unlocked. Although I could not vote for each phone, it will be interesting to check poll results a few months down the road.
swa100 said:
Yeah that ticking timebomb feeling is really annoying. I don't even dare to use the phone now it actually works, because I'm afraid that I'll f*ck up my new battery. I'm trying to wait for an official response from Google, but it's hard. I really want to know if some software f*ckup is causing these batteries to degrade faster.
Click to expand...
Click to collapse
Google's official position is that the early shutdown problem and boot loop of death are both hardware issues. People are experiencing both problems on stock Marshmallow and Nougat as well as on custom ROMs.
murphyjasonc said:
I'm not sure it was necessary but I flashed back to stock and relocked bootloader. I didn't want to take any chances especially since they were replacing it out of warranty. Worst case I could have used Nexus protect either way. They tried to get me to do that when I called. I refused and once I mentioned the Reddit thread they agreed to replace. Saved me the $79.00 deductible.
Click to expand...
Click to collapse
Guess I'm making a call tomorrow then. Hope this straightens things up. Thanks!
Just as an update, I got my RMA last week and it has behaved flawlessly since. Accubattery is actually reporting 101% battery health, and It's taking a little getting used to having a phone that the battery doesn't die in two hours.
affected
Lulzmaster said:
Sure am, and it's died at as high as 45% and as low as 15%. Accubattery pegs the health at about 60% and I've only had the phone about 15 months. Wanted this to be the first one I kept for two years.... Not looking likely with my 2 hours of SOT.
Click to expand...
Click to collapse
Same story.. getting a new battery install totally solves this? https://www.youtube.com/watch?v=2fCDOfljoQY
It's annoying not to be able to easily swap in a new battery but manufacturers could prefer people feel desperate for a yearly upgrade: https://forum.xda-developers.com/nexus-6p/help/nexus-6p-battery-replacement-options-t3628932
SMARTPHONEPC said:
Same story.. getting a new battery install totally solves this? https://www.youtube.com/watch?v=2fCDOfljoQY
It's annoying not to be able to easily swap in a new battery but manufacturers could prefer people feel desperate for a yearly upgrade: https://forum.xda-developers.com/nexus-6p/help/nexus-6p-battery-replacement-options-t3628932
Click to expand...
Click to collapse
I haven't had an issue since I got my RMAd device, so yeah. I even have all the same apps installed and everything and I'm still getting ten hours of mixed usage. Performance is getting a little pokey but the phone is coming up two years old soooooooooooo I'm not surprised.
Sent from my Nexus 6P using Tapatalk
I am looking for any info from anyone that has experienced the infamous bootloop. Not sure if it has happened on the V20 but we all know about the others. I have a theory I am testing out and need as much info as possible. I experienced this twice on the V10, my son on the G4, and now my brother on the V10. The one thing we all had in common is the use of two lg batteries. If you notice when you reboot your phone with it unplugged you will always drop at least 2%. I had multiple times on the V10 where I would put in a full battery after draining the previous and it registered as a much much lower percent(in the red). It got to where I would have to wait a minute or two before booting and plug the phone in for it to register at 100. It wasn't too long after this that I experienced my first bootloop on the V10. The way android started changing battery stats on Lollipop, I feel didn't and doesn't play nice with swapping batteries. This is why I am looking for more info. I know what Lg and others claim about a contact pin, but I am starting to think bs.. I really would like to get more info because this could just be a crazy coincidence.
As a v10 user who has experienced the boot issue I didnt have any problems with the phone reading my factory batteries correctly, I did have problems with the phone reading aftermarket battery packs. What would happen is the phone would claim it was out of juice but turning it off, unplugging then plugging the battery back in would give me 40% of the battery back.
When my phone boot looped it was after it was on the charger and not being used when i took it off the charger and started to use it that's when it hard locked and i had to pull the battery to reboot it...At this point it never stopped rebooting.
I used the freezer method to just see if its the same issue, putting it in the freezer for 10 minutes made the phone work for a little bit after.
The issue is a poor solder connection aggravated by the fact the snapdragon 808 getting excessively hot. Its not a coincidence that all these phones that have the boot issue (v10, g4 and nexus 5x) are running the same processor. I think these are the only phones that really have the boot loop issue.
Essentially I think it's LGs poor construction and the snapdragon 808 excessive heat that causes it. If neither issue existed I don't think the problem would exist.
I don't think the g5 and v20 boot loop issues are related to hardware failures I think it's more people screwing up their own phones by rooting or modding (which happens all the time) but since the g4 bootloop issue is so prolific its easy to assume the boot loops on the g5/v20 are the same.
Sent from my LG-H918 using XDA-Developers Legacy app
My Gflex 2 bootloop with a 810
Sent from my LG-LS997 using Tapatalk
I had a V10 it went into the boot loop. I did use multiple OEM LG batteries. I sent it in and they repaired it. I also think it has something to do with heat and something on the main board failing After Time. The ticket said RF and main boards replaced when I got it back from LG
My V20 bootloops if I use a stock ROM of any kind. But if I put an AOSP ROM like AICP or the sort it has no problems. I'll probably fix it temporarily and see what T-Mobile can do about it.
EROMITLAB said:
My Gflex 2 bootloop with a 810
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
The 810 has even more issues with heat in fact in some reviews the 808 performed better because the 810 consistently throttles in response to overheating.
Sent from my LG-H918 using XDA-Developers Legacy app
I guess there's two kind of root-cause for the LG's infamous bootloop issues. One issue that many G4 users has faced is the bad soldiering on the SoC. When the SoC is hot enough, the soldering connection get loose and put the phone into infinite bootloop. This one can be helped only by replacing the whole mainboard, or by re-flowing process (either try ur luck or go to professionals).
Another type of bootloop (I've faced with my G Flex 2) is the battery issue. The battery control chip inside the battery died (maybe a fuse has been blown). That cause the phone to receive incorrect battery information and eventually make it shut-down. I've replaced the battery of my G Flex 2 and after that, it has been working so far.
For V20, so far, I've never heard from anyone about any bootloop issue yet. Maybe it's a bit early as the phone is fairly new.
spiderx_mm said:
I guess there's two kind of root-cause for the LG's infamous bootloop issues. One issue that many G4 users has faced is the bad soldiering on the SoC. When the SoC is hot enough, the soldering connection get loose and put the phone into infinite bootloop. This one can be helped only by replacing the whole mainboard, or by re-flowing process (either try ur luck or go to professionals).
Another type of bootloop (I've faced with my G Flex 2) is the battery issue. The battery control chip inside the battery died (maybe a fuse has been blown). That cause the phone to receive incorrect battery information and eventually make it shut-down. I've replaced the battery of my G Flex 2 and after that, it has been working so far.
For V20, so far, I've never heard from anyone about any bootloop issue yet. Maybe it's a bit early as the phone is fairly new.
Click to expand...
Click to collapse
I have had no issues with the V20 so far, except for the massive drop in battery after a reboot. I added it in case others have experienced it.
"Bootloop of death" finally hit V10.
It turned off itself and only shows LG on the screen.
I am curious with v10 owners on what month your phones were manufactured, mine was Nov 2015 and it crapped out in January 2017 (naturally).
What I am curious about is if phones made post jan 2016 have this issue. Why this date? This is when LG announced this issue. I am curious if they just ignored it and sent out defective units anyway or if they actually fixed it.
The V20 shouldn't be affected since it's a different chipset while the v10/g4 have the same chipset. The 820 (g5/v20) also doesn't get nearly as hot as the 808 did.
One thing's for sure with the lawsuit against them and all the negative publicity (almost every facebook post the company makes someone comments about the boot loop) of this problem I am sure they learned a lesson.
Sent from my LG-H918 using XDA-Developers Legacy app
I thought I read on Android central LG is now honoring the V10 up to 24 months of warranty. I have a V10 at home so I guess good to know. It was made in Nov 2015. Hasn't bootlooped yet, but I only use one it as a portable hifi music player and it just sits in airplane mode.
Sent from my LG-H918 using Tapatalk
I have very high demands when coming to a camera on a mobile and after analyzing the latest mobiles pictures I am as a photographer most impressed with Nexus 6P.
I have found a brand new copy of it for 350 euro.
But what makes me still not sure is the bootloop thing.
1) Does the bootloop problem comes after the phones age, is it caused by worn or is it caused by after an update?
2) I have root a few mobiles and always the camera has got a bit worse after installing CM/LOS/AOSP, is it the same with Nexus 6P? Is the camera best with the stock rom?
3) Are there any other problems with Nexus 6P that is very common?
AFAIK the bootloop is totally random - I have a 6P and never had it, but I was affected by the battery early death.
I'd look for newer phones.
Grushteniak said:
AFAIK the bootloop is totally random - I have a 6P and never had it, but I was affected by the battery early death.
I'd look for newer phones.
Click to expand...
Click to collapse
LG V20 is cheap these days.
Moto Z.
If I didn't have a Nexus 6P, I would not buy one today.
There are too many alternatives.
Grushteniak said:
AFAIK the bootloop is totally random - I have a 6P and never had it, but I was affected by the battery early death.
I'd look for newer phones.
Click to expand...
Click to collapse
tech_head said:
LG V20 is cheap these days.
Moto Z.
If I didn't have a Nexus 6P, I would not buy one today.
There are too many alternatives.
Click to expand...
Click to collapse
The only two new phones that have better or same camera quality is Pixel and HTC U11, but their way too expensive.
V20 is like all other LG and Samsung camera, to much oversharp and unnatural colors.
There arent too many alternatives if you looking for a camera as good as Nexus 6P and with at least 5,5" display
Brand new? Not refurbished?
If it is actually brand new for 350 euro I would buy it. Yes there are alternatives but not at that price.
Basic stuff:
1) take care of the battery, don't let it go to zero (many of us had our phones replaced due to early battery death)
2) put a decent case on it, screen will crack if you drop it on a corner on a hard surface
I'm on my second 6p and I've not experienced the bootloop issue, but I did get early battery death on the first one.
cheesiepoof said:
Brand new? Not refurbished?
If it is actually brand new for 350 euro I would buy it. Yes there are alternatives but not at that price.
Basic stuff:
1) take care of the battery, don't let it go to zero (many of us had our phones replaced due to early battery death)
2) put a decent case on it, screen will crack if you drop it on a corner on a hard surface
I'm on my second 6p and I've not experienced the bootloop issue, but I did get early battery death on the first one.
Click to expand...
Click to collapse
Agreed. No better camera at this price and take care of battery. I have accubattery and battery repair app. After nearly a year, still 96% health. Don't charge over 90% and don't go below 20% if possible.
Grushteniak said:
AFAIK the bootloop is totally random - I have a 6P and never had it, but I was affected by the battery early death.
I'd look for newer phones.
Click to expand...
Click to collapse
tech_head said:
LG V20 is cheap these days.
Moto Z.
If I didn't have a Nexus 6P, I would not buy one today.
There are too many alternatives.
Click to expand...
Click to collapse
cheesiepoof said:
Brand new? Not refurbished?
If it is actually brand new for 350 euro I would buy it. Yes there are alternatives but not at that price.
Basic stuff:
1) take care of the battery, don't let it go to zero (many of us had our phones replaced due to early battery death)
2) put a decent case on it, screen will crack if you drop it on a corner on a hard surface
I'm on my second 6p and I've not experienced the bootloop issue, but I did get early battery death on the first one.
Click to expand...
Click to collapse
Brand new
I'd say go for it great phone just recently picked up one and couldn't be happier.
I was wondering the same thing since I'm thinking about dropping Sprint for T-Mobile, but the Bootloop issue that we've all heard about has me extremely worried. Anyone recommending this phone (in the US specifically) in 2017?
tropical cactus said:
Agreed. No better camera at this price and take care of battery. I have accubattery and battery repair app. After nearly a year, still 96% health. Don't charge over 90% and don't go below 20% if possible.
Click to expand...
Click to collapse
What? You're joking? I never heard of any of these issues. Especially the bootloop which I JUST HAD on my LG G4! I got this phone as a replacement by a friend and it got the same issue? That's hilarious.
What's the battery thing? I can't let it go under 20%? That's rather annoying since this phone (as well as my LG G4) doesn't seem to have stellar battery life so I will as a hard user drop under 20% easily in a day. Is it really that serious?
BrotherZero said:
What? You're joking? I never heard of any of these issues. Especially the bootloop which I JUST HAD on my LG G4! I got this phone as a replacement by a friend and it got the same issue? That's hilarious.
What's the battery thing? I can't let it go under 20%? That's rather annoying since this phone (as well as my LG G4) doesn't seem to have stellar battery life so I will as a hard user drop under 20% easily in a day. Is it really that serious?
Click to expand...
Click to collapse
Just telling it as it is. No boot loop and no battery problems.
tropical cactus said:
Just telling it as it is. No boot loop and no battery problems.
Click to expand...
Click to collapse
Oh, I'm not questioning you. Just venting my frustration as well appreciating the humour coming from a device that had the exact same problems, and then got this device as a temporary replacement. Wonder if it's related to the Snapdragon 808/810, those SoC's weren't the best.
Could you tell me anything more about the battery issue? What is it exactly and is it common?
BrotherZero said:
Oh, I'm not questioning you. Just venting my frustration as well appreciating the humour coming from a device that had the exact same problems, and then got this device as a temporary replacement. Wonder if it's related to the Snapdragon 808/810, those SoC's weren't the best.
Could you tell me anything more about the battery issue? What is it exactly and is it common?
Click to expand...
Click to collapse
Well, I've only had the device since October last year and reading about the battery problems others have had on older devices, such as shutting down at 50% has got me a bit concerned. Just following xda charging advice. I've been on nougat, dp4 and now back on last stock marshmallow build because I miss Xposed. Battery life seems better and wakelock isn't showing any apps misbehaving. Just an average user willing to take whatever advice I come across.
tropical cactus said:
Well, I've only had the device since October last year and reading about the battery problems others have had on older devices, such as shutting down at 50% has got me a bit concerned. Just following xda charging advice. I've been on nougat, dp4 and now back on last stock marshmallow build because I miss Xposed. Battery life seems better and wakelock isn't showing any apps misbehaving. Just an average user willing to take whatever advice I come across.
Click to expand...
Click to collapse
Not sure how old this device I got is, but I'd guess at least one year. I'll guess I'll just have to see.
Where can I find the XDA charging advice, or is that just the one you posted, not above 96% and not below 20%. The last one is going to be tough since I suspect this device doesn't have stellar battery life so I'll easily dip below 20% in a day.
Which one is DP4? I'm on CarbonROM now (love the selection of ROMs for this device) because of it's excellent support for MicroG. About to try out Pure Nexus and LineageOS.
Isn't Xposed ready for Nougat now? Although I don't miss Xposed that much anymore after Magisk.
BrotherZero said:
Not sure how old this device I got is, but I'd guess at least one year. I'll guess I'll just have to see.
Where can I find the XDA charging advice, or is that just the one you posted, not above 96% and not below 20%. The last one is going to be tough since I suspect this device doesn't have stellar battery life so I'll easily dip below 20% in a day.
Which one is DP4? I'm on CarbonROM now (love the selection of ROMs for this device) because of it's excellent support for MicroG. About to try out Pure Nexus and LineageOS.
Isn't Xposed ready for Nougat now? Although I don't miss Xposed that much anymore after Magisk.
Click to expand...
Click to collapse
http://www.techadvisor.co.uk/how-to/mobile-phone/how-properly-charge-phone-battery-3619623/
Not above 90%. Once in a while should be alright. Dp4 is the last beta of stock Android o. I usually stick to stock so I don't know much about custom roms. I use ex kernel for color profiles - can't stand stock yellowish tint. Xposed for nougat I tried. Before attempting to install any modules, other apps begin to crash. I don't know how much progress has been made since then but only a few modules work anyway. Only tried magisk to install system wide sound module once before but haven't used it since.