My Nexus 6P went in a bootloop recently.
It was shortly after I unlocked the bootloader and rooted the phone.
I tried everything I could (stock firmware 7.1, 7.0 and the oldest that was available) but nothing worked.
I still had warranty so I sent it back to webshop where I bought it.
Now I got my phone back and the note says 'Mainboard replaced'.
What I want to know:
- Can it be my fault the phone broke, I know the Nexus 6P has some issues concerning bootloops.
- Can I safely root again? Or would you not recommend it?
Thanks for your answers.
I have a backup phone, but I don't want to f*** my 6P up again.
Search for BLOD. You will answer your own question in no time. Lol No you are not to blame. It had or is happening to probably hundreds of phones by now. You will also see there are many different roms, 6&7, root or stock that have the problem.
Sent from my Nexus 6P using XDA-Developers Legacy app
Rooting doesn't cause the boot loop of death. Flashing something sometimes triggers it (including flashing a normal OTA on pure stock) but it is almost certainly a hardware issue.
Related
I've had this phone almost 2 years now and never had an issue. Since I installed the OTA for 5.0.1 last week I've now had 3 random reboots. This is bringing back the nightmare of my G2X days. Anyone ideas?
Have you done a factory wipe? That's where I'd be starting. I never trust updates without a wipe. My sisters galaxy s 1 and 3 always got messed up every time she did an ota update.
I've never done many ota updates since I've always run custom roms.
Right now I'm running stock 5.0.1 on the n4 I just bought used and no issues at all but it got wiped as soon as I got it and updated it.
Sent from my Nexus 4 using XDA Free mobile app
I would wipe everything and reflash 5.0.1. I have been running it on the N4 since it came out and have not had a single issue.
If that does not work, get a logcat of the issue if you can.
I got a G2 from Ebay a few months ago (4 to be exact) and from then and now I've not done much but than install a few custom ROMs (2) and restore to KDZ (3). All that time I've been getting Overheating issues. I am almost 96% sure that it is not a frankenphone but I feel something is up with this phone.
When I first got it. I used the phone for a few weeks on stock (it was on Jellybean shipped). Then KDZ upgraded to KitKat (no sim, full wipe). Still nothing, no overheating.
Then I finally decided to get a ROM going. I rooted with TowelRoot and installed recovery with AutoRec. Then upgraded TWRP to support lollipop ROMs (Blastagator's Thermal TWRP).
Now after all of that I successfully installed my first ROM of choice - Blisspop. It ran like a dream. But this is where the overheating started.
I constantly got 40C+ and above. I did nothing about it. Got sick of it, and installed another ROM (Cloudy 2.2). Of course it installed successfully. Nothing wrong. Still overheated like mad.
Used Cloudy for a few weeks and finally decided to back everything up and restore via KDZ (back to KK). After that. Overheating still occured although it was a little better than I expected... I wondered what was going on. By then it was a month and the Ebay seller said I was Out of Luck. Now I decided to install Resurrection Remix 5.1. It seemed to fix some overheating issues but they were still severe-ish.
Decided to restore via KDZ again (KK again) still nothing. After that I installed everything I needed and installed a Stock Lollipop Stripped Down ROM, I've heard bad things about LG's Stock Lollipop (including overheating) so I'm not surprised that this thing is overheating in this state. I am now stuck here. Wondering what the hell I need to do to get this thing back to it's former glory.
Look at my location. I live in Nevada. I know that High Temps here aren't good for this phone and that might be the problem. But this phone is hardly used anywhere without AC (Car, Home, Job, Banks, Buildings, ect) and both are really cool compared to outside's 100+F/37C heat. So that can't be a factor.
I'm wondering if I can return this thing back to LG/AT&T if they still allow them to be repaired. My seller gave some info like S/N and original purchase date. But I'd rather not do that. Also, if I'm Out of Luck on warranty. How much would it cost to pay LG for it to be fixed? Just wondering. But I would rather fix it on my own that to wait a few weeks without a phone.
TL;DR: Bought phone, upgraded from JB to KK. Rooted and installed recovery, flashed a ROM. Overheated. KDZ'd back, overheated. more rom installing ect, ect. still overheating. Wondering what I need to do to restore this thing.
Well if its is under warranty i would suggest going through lg however if you are not, there is a thermal mod on xda for the g3 which is also applicable for the g2 and it requires opening the phone up and applying thermal compound on the cpu chip. Google lg g3 thermal mod and there is an xda forum for it.
Sent from my LG-D800 using Tapatalk
xmayhemreturnsx said:
Well if its is under warranty i would suggest going through lg however if you are not, there is a thermal mod on xda for the g3 which is also applicable for the g2 and it requires opening the phone up and applying thermal compound on the cpu chip. Google lg g3 thermal mod and there is an xda forum for it.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
I've checked the threads and I've seen nothing about it working for the G2. Have you tried it?
It is compatible with almost all phones. Honestly, all it requires you to do put thermal compound on the cpu. It does work for the g2.
Sent from my LG-D800 using Tapatalk
Hi,
My Nexus 6p has 32GB Samsung emmc.
I upgraded it to 7.11 several days ago and used it for 2 days before I knew many Nexus 6p has a boot loop problem(luckily I didn't have it when I was using 7.0). So I flashed back to 6.0.
My question is, since I had tried 7.11, downgraded it, and good with 6.0 since then. Does it prove that I don't have a hardware problem and I can use 7.1.1 safely?
The reason I'm using Nexus 6p is I really want the latest updates.
p.s it's my first thread on XDA.
Thanks for any thoughts and comments.
Real1minshen said:
Hi,
My Nexus 6p has 32GB Samsung emmc.
I upgraded it to 7.11 several days ago and used it for 2 days before I knew many Nexus 6p has a boot loop problem(luckily I didn't have it when I was using 7.0). So I flashed back to 6.0.
My question is, since I had tried 7.11, downgraded it, and good with 6.0 since then. Does it prove that I don't have a hardware problem and I can use 7.1.1 safely?
The reason I'm using Nexus 6p is I really want the latest updates.
p.s it's my first thread on XDA.
Thanks for any thoughts and comments.
Click to expand...
Click to collapse
Nobody knows for sure what causes the boot loop of death, which is what I assume you are concerned about, but multiple people who stayed on Marshmallow and never updated to Nougat reported that they got it anyway. If you want to run Nougat you should do a clean install of the full factory image and see if you still have the problem. As long as your bootloader is unlocked and USB debugging is enabled in developer options you should be relatively safe should you encounter problems again. I have been running 7.11 or roms based on 7.1.1 for as long as I have had this phone and have never encountered any serious issues. The vast majority of 6P owners don't have serious issues with Nougat. I personally wouldn't go back to Marshmallow because I got the 6P to be up to date as well.
jhs39 said:
Nobody knows for sure what causes the boot loop of death, which is what I assume you are concerned about, but multiple people who stayed on Marshmallow and never updated to Nougat reported that they got it anyway. If you want to run Nougat you should do a clean install of the full factory image and see if you still have the problem. As long as your bootloader is unlocked and USB debugging is enabled in developer options you should be relatively safe should you encounter problems again. I have been running 7.11 or roms based on 7.1.1 for as long as I have had this phone and have never encountered any serious issues. The vast majority of 6P owners don't have serious issues with Nougat. I personally wouldn't go back to Marshmallow because I got the 6P to be up to date as well.
Click to expand...
Click to collapse
Thank you~
Hi,
My Nexus 6P is on android 6.0.1 and after reading all the problems with Nougat, I would better stay on marshmallow.
However, my security patch is from April 2016.
I am rooted with stock 6.0.1 MHC19Q.
Would like to know if I can update only the security update and if so, how to do this ?
Sent from my Nexus 6P using xda premium
Lior84 said:
Hi,
My Nexus 6P is on android 6.0.1 and after reading all the problems with Nougat, I would better stay on marshmallow. However, my security patch is from April 2016. I am rooted with stock 6.0.1 MHC19Q.
Would like to know if I can update only the security update and if so, how to do this ?
Click to expand...
Click to collapse
I respect your decision to stay with MM, but I think it is misguided. There are many improvements that come with installing N, including the security updates. Security updates are part of the OS update and are not available separately. If you want the benefits of the latest security updates, you have to install 7.1.2.
Right now I'm on latest stock rooted with franco kernel and there are no issues. Except there's no xposed support.
But updating to nougat comes with no issues, so u should try, make a backup and flash.
I'm afraid to update because of brick possibility. From what I read, many users that updated, had a brick.
Sent from my Nexus 6P using xda premium
Lior84 said:
I'm afraid to update because of brick possibility. From what I read, many users that updated, had a brick.
Sent from my Nexus 6P using xda premium
Click to expand...
Click to collapse
Nah, don't be afraid, I'm flashing everything with twrp, factory images too. No issues.
If by brick issue you are talking about the boot loop of death that's a hardware issue and it happens while you are on Marshmallow, Nougat or a custom Rom. If you are talking about something else as long as your bootloader is unlocked and OEM Unlock is enabled in developer options you should be able to recover in the unlikely event of a flash going bad. Whether to flash or not is a tradeoff. You get the latest features and security updates on Nougat but you can't use Xposed (if that's actually important to you) and you will almost certainly get worse battery life on the latest versions of Nougat than you are getting on Marshmallow. Google has goosed the stock kernel settings lately resulting in worse battery life and the operating system and screen using more battery than previously. The only way to avoid that and stay up to date is to flash a custom kernel or flash a custom Rom.
I have bootloader unlocked from the first day of the phone. I really like this model (except for the camera that responds slower than the nexus 5 one) and would like to use it at least one more year. Really worry about the hard brick and because of its, staying till now on stock 6.0.1.
With N5, I flashed many roms, but in this one, I stayed one year on a single rom that came on it.
Sent from my Nexus 6P using xda premium
Lior84 said:
I have bootloader unlocked from the first day of the phone. I really like this model (except for the camera that responds slower than the nexus 5 one) and would like to use it at least one more year. Really worry about the hard brick and because of its, staying till now on stock 6.0.1.
With N5, I flashed many roms, but in this one, I stayed one year on a single rom that came on it.
Click to expand...
Click to collapse
The bootloop issue has nothing to do with the os update. It is because of dodgy hardware. It can happen from a damaged and degraded battery. Updating to nougat doesn't cause the issue.
Hey guys, my Nexus 6P got the BLOD 2 months ago so i sent it into warranty. They sent me back a new one a few days back. First thing i did is I enabled OEM unlocking and USB debugging. Is that enough to save my 6P in case I get a bootloop again? Should i unlock bootloader and install custom recovery? Stock oreo is working pretty good, any of you guys recommending any custom roms?
I would think that no mater how talented are the mods in here, who came up with a solution for a crippled 6P, in a case of a BLOD I would simply get it fixed if I can get Huawei to do it or simply get a new device.
having a crippled 6p with only four cores active , little cluster, that's not a real smartphone.
But as a whole, yes, unlocking your bootloader is what you need to use that mod.
flopix1337 said:
Hey guys, my Nexus 6P got the BLOD 2 months ago so i sent it into warranty. They sent me back a new one a few days back. First thing i did is I enabled OEM unlocking and USB debugging. Is that enough to save my 6P in case I get a bootloop again? Should i unlock bootloader and install custom recovery? Stock oreo is working pretty good, any of you guys recommending any custom roms?
Click to expand...
Click to collapse
I don't know about the 6P boot loop causes (they are not so popular like the 5X with this problem). Just in case I recommend you to do this.
In the 5X, 90% of the bootloops happen in less than 2 weeks after a mayor OTA update (like from M to N or N to O).
So what I do is to put the phone in the fridge for 5 minutes, once is cold I press the update button and let it update inside the fridge. This way the phone remains COLD during the update process, and one of the 5X chipset doesn't get unsoldered. Note that It shouldn't be more than 10 minutes inside the fridge.
flopix1337 said:
Hey guys, my Nexus 6P got the BLOD 2 months ago so i sent it into warranty. They sent me back a new one a few days back. First thing i did is I enabled OEM unlocking and USB debugging. Is that enough to save my 6P in case I get a bootloop again? Should i unlock bootloader and install custom recovery? Stock oreo is working pretty good, any of you guys recommending any custom roms?
Click to expand...
Click to collapse
Stock ROM, unlocked bootloader, USB debugging enabled, TWRP recovery, rooted, custom kernel. Nothing you can really do to prepare for a defective motherboard.