yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Just run the flash-all.bat file(back up your stuff, it will wipe the device) in the mm factory image you want and you'll be good. If you're on twrp 3.0.2-1 do not restore anything. It needs to be updated first.

These boot loops are either from bad efs from restore in twrp 3.0.2-1 or something to do with a faulty nand/emmc/official kernel fault like a user posted just above. This is rather sad on Google/Huawei's part if it is because of a crappy nand.
[Nexus 6P Q&A, Help & Troubleshooting] out of my element:
After having tried numerous reflashes of my phone to the previous unrooted versions of android, both 7.0 and 6.0, I never could get past the boot loop. I couldn't boot into TWRP either using Wug's tool.

I left the phone on and let it boot loop itself to complete battery drain over the weekend. I had called google to return it this AM and they wanted me to go through some troubleshooting steps and although I had already done all of these I obliged and charged the phone and turned it back on. To my absolute surprise it went from the google logo to the spinning colors and to a new user login. It froze here and then went through a bootloop cycle all morning again. When I just got back home it fully booted up and now lets me log back in.

I have know idea what led to this righting itself. All I can say was I downgraded to NRD90T During my 4 days of bootloop I could only get to the stock recovery but never TWRP.

Now I have a refurb on the way from Google and have to decide whether to keep my original or swap for the refurb...

Good luck to others with the boot loop issues. Maybe try completely draining your battery, only thing I can think of I did differently in the last 24 hours. If you have any questions to elucidate other possible resolutions let me know.
[Nexus 6P Q&A, Help & Troubleshooting] DaGr81:
This is exactly how I got into the boot loop mayhem. Instead of watching a YouTube video, I was using a camera to take pictures. Phone had twrp3.0.2-2 installed, got an nbd90x ota, flashed it via flashfire.

It all started after few days of upgrade.

:crying:
[Nexus 6P Q&A, Help & Troubleshooting] BIGSAMDA1ST:
I'm curious to know if anyone that may have received their replacement devices or know of anyone that have, had any problems with them? Meaning, has anyone try any updates or flashing anything on their replacements? I'm still waiting on mine to get here but a lil weary on flashing anything or even updating for that matter.
[Nexus 6P Q&A, Help & Troubleshooting] 808computers:
I got my replacement from Google 10/21. Upon setting it up, it immediately began downloading monthly OTA/security updates. I let each install and when it was up to date, it began downloading 7.0. NBD90X. After that installed without issue, I unlocked the bootloader. But I'm hesitant to do anything more lest it boot loops too. I'm hoping the actual cause for the boot loops can be determined so that it can be averted. I wouldn't wish this problem on anyone yet, at the same time, if it did affect more 6p owners (tinkerers or not) maybe Google will issue an update that corrects this.

So, to answer your question, I have not yet run into any problems. But it's been less than a week and I haven't done anything except unlock the bootloader and let it self-update to NBD90X.
[Nexus 6P Q&A, Help & Troubleshooting] BIGSAMDA1ST:
That was exactly my plan when my replacement got here. Unlock the bootloader and just run it as is until the problem is resolved. Don't want to risk another boot loop fiasco.
[Nexus 6P Q&A, Help & Troubleshooting] RedInuYasha:
I just got my phone back from my carrier. They gave me a replacement instead of fixing whatever was wrong with the other one. So I guess I'll wait for all official updates before I root again. I am kind of scared to unlock anything after this last issue.
[Nexus 6P Q&A, Help & Troubleshooting] rchtk:
So... Can we see a common pattern in the affected users? To me that looks like hardware failures that just exhibit when it's being used (flashing). ?
[Nexus 6P Q&A, Help & Troubleshooting] playaz33:
What is causing this?

I have been trying different things for the past few days while waiting for Google to RMA this. Here's what I've experienced.

Out of 100 tries to boot into recovery, I can get into it maybe 3 times. It's hit and miss, but it SEEMS more likely to go into recovery when:

1) it is plugged into the original charger

2) when I cover the proximity/ambient light sensor

3) when I drain the battery and try to boot into recovery while it is charging up

The second one doesn't seem to make much sense. Maybe the other two can give a hint as to the cause of the problem. One thing I did notice prior to this bootloop issue is that my phone would shut off with more than 15% left. That was a new issue that occurred a day or two before the bootloop. Is it possible that the phone is rebooting because it somehow thinks the battery is low even if it's not? Maybe it is heat related because keeping the phone on while charging creates some internal heat, not a ton though. If I want to drain the battery, I just go to the "barcodes" mode in the bootloader and I let it sit there since the screen is mostly white and will likely drain the battery faster.

I have tried pretty much every combination of different things to flash, from Marshmallow, different versions of Nougat, locking and unlocking the bootloader, encrypted and unencrypted boot, to different versions of TWRP, to stock recovery, erasing partitions, formatting partitions, holding vol up and vol down, hidden fastboot commands, flashing the dd codes when it finally does get into recovery. Still bootloops.
[Nexus 6P Q&A, Help & Troubleshooting] afdhalzaed:
I actually got out from this freaking BOOTLOOP!

I actually did it! oh my god i actually did it! i got out from the freaking bootloop! and trust me i tried EVERYHTING else. Only this method, for me at least, helped. I will described exactly what i did.

1. You need a nandroid backup. Any nandroid backup for your phone is good i think. You NEED to know what version of nandroid backup you are having, and what version of ROM.

2. Wiped, erased everything on my phone.

3. Reverted my phone to stock version of the nandroid. (Google Factory) (For me i reverted to MTC20F full stock because my nandroid backup was on PureNexus MTC20F, used flash all.bat)

4. Tried booting to system but failed, still bootlooped.

5. Flashed TWRP, for me, TWRP 3.0.2.0 works. My suggestion, don't go above this version of TWRP, lots of problems!

5. Flashed the custom ROM the nandroid you had (for me, the nandroid backup was PureNexus MTC20F 6.0.1, so i flashed the PureNexus ROM running MTC20F vendor)

6. I tried rebooting to system, but not to avail.

7. I restored the nandroid backup i had earlier.

8. Progress, the boot animation appeared. Before, only Google logo poped out and then it restarts again.

9. Flash back to full stock MTC20F. (flash all.bat without wiping anything)

10. The phone fully boots!

Goodluck guys! it took me an all nighter. I tried everything people and the internet guides me but nothing helped. This is the only one that actually worked for me. Thank God!
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Glad you got it running. Either your efs or emmc was corrupted.
[Nexus 6P Q&A, Help & Troubleshooting] MoistPicklez:
Just thought I'd give other Canadians with a bootlooped / bricked 6P a heads up. FutureTel is where the device is sent to in Canada. The company itself has a horrible reputation and reviews on Google. Apparently lots of people have had issues with FutureTel, if you're in Canada and sent your phone into them, definitely check out the startling reviews.

I sent the company an email and it literally took them 3 business days to get back to me so while I waited for a response I called them several times and only got through once. They had no idea what the status was on my device they only knew that it had been delivered to them and was in their inventory. It's been about 6 days now and I hope to whatever y'all believe in that the device is sent back in tip top shape. Gotta call them tomorrow for some hopefully good news.

Has anyone else dealt with FutureTel in Canada? Curious to see if anyone here has got their device fixed properly as I am extremely worried after reading their reviews...
[Nexus 6P Q&A, Help & Troubleshooting] seco2004:
Well, mine just died. Out of the blue started to get bootloops last friday. Phone was running latest beta release, locked bootloader and unrooted. Since then the phone would eventually boot up after 30 minutes if I let it bootlooping. One weird thing I noticed is that if I let the battery run out, after I plug it in the device would boot after 2 or 3 attempts, and then die again when the battery reaches around 10 or 11% (I'm gonna try this again to see if it's actually a pattern). Anyway, tried pretty much everything: downgrade to MM, flash latest stable build, flashed Pure Nexus with ElementalX kernel (device ran quite well for about 7 or 8 hours), Nexus Toolkit.... I can get to bootloader and recovery just fine and the phone is fully responsive in those modes, but I pretty much guess this one is a goner :( Worst thing is that I live in Brazil, so no support for me. No stores here works with this phone, so I'm stuck with a very expensive paperweight (which I financed and there's still 8 payments to go). Here's the info:

Bootloader: 03.62

Baseband: 03.75

Variant: Angler-VN2

CPU: 0x2001

eMMC: 32GB Toshiba

DRAM: 3072MB HYNIX LPDDR4

Console: NULL

Qfuse Status: ENABLED

Download Mode: DISABLED

Manufacture date: 03-08-2016
[Nexus 6P Q&A, Help & Troubleshooting] BIGSAMDA1ST:
Any good news from anyone regarding this horrible situation?
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
No problem. Currently updating to N again as I type via adb OTA in stock recovery from MTC20F.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
You should brick it so you can join in on the shenanigans!

*don't do that"
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Lol. That's actually what I'm trying to do.

I might have success this time as I was greeted with two errors after the System patching and two more after Vendor patching.

Appears to have booted into N and setting up just for the heck of it. Will be using device for at least an hour to see if I get the random reboot others have reported here.

Update: Didn't get a random reboot but setup was stalled because of Project Fi setup not continuing, so I rebooted and got past it, ran a factory reset from inside device and back up and running after setup smoothly. It's getting late, so I'll go back to MM tomorrow morning.
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
Just to clarify, I've never has a random reboot on N. Only the bootloop after trying to restore stock N ROM from a backup made in TWRP 3.0.2-1
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Wait, when you restored, you didn't try restoring the vendor image did you?
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
No why would I have to if I'm already on the ROM?
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
There are so many people trying to restore backups from recovery, WHY ? it's a totally different version / boot loader and likely has other changes due to the implementation of the dual ROM memory of soon the be released nexus devices.

TWRP has not been built and tested for the new version of N yet there has been no update since N OTA was pushed ! Don't make any backups ! Don't try and Restore ! FLASH BACK TO STOCK your jumping versions ! ( This a common theme oh I tried to restor an image I made on a recovery that's not been updated to the new file structure)

I have downgraded 3 times now, I Originally flashed an OTA that was converted to a flashable ZIP found on these forums that was specifically from MM -> N

Each time I have made a full wipe and backed up my internal storage.

Wipe Absolutely everything !

Flash the Image from its parts as explained by Heisenberg in his thread :

you NEED to wipe /system, /data, /cache, and dalvik cache and you need the Vendor.img & bootloader for your stock image you are flashing to be installed before you flash the system ! ( you can mess about with modified bootloaders once you have got the system to boot !

Bootloader / Radio -> reboot bootloader -> Flash the rest via ADB/Fastboot including your correct Vendor image ! and then boot as normal

If your going to need TWRP always use the latest version don't, if your on N build flash the new version before attempting the role back !

I have had zero issues each time and has booted as expected, people are making this so complicated because they are not taking proper steps, if you had N on your device and are flashing back you NEED all the original files for the MM version you are flashing !

If you can't be arsed to make a full wipe and do everything correctly step by step file by file then expect dragons ahead !

i think the message we need is : stop using TWRP to make backups of N or use it on N to restore lesser android builds ! flash back to stock as if returning your device to the OEM
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
we have tried this and it still is broken, myself I upgraded to the latest twrp and made a backup of MM and restored it, my phone was never on N when this happened to me. I tried flashing stock images from all the way back to 6.0.0 wiping EVERYTHING in fastboot first. I think the latest twrp is whats causing it, I noticed a few things the vendor image is 2 megs bigger for N than it is for MM I think the latest twrp messes with the vendor partition somehow.
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
That's weird then i'm using the latest version of TWRP that stable and not beta or anything V3.0.2-0 and it restores MM stuff fine when i'm running MM and has done ever since I flashed that build back in April.

I have gone from a stock rooted debloated 6.0.1 build and pure nexus afew times and had zero issues, people are doing something they should not be for there to be an issue with restoring MM backups then.

Sure the vendor image might be different than that of MM for N because the vendor image contains specific drivers for that build and that device, flashing an incorrect vendor image for you build is just asking for issues as other have highlighted months back.

And this current build of TWRP for MM / N previews has been working fine since they fixed the issues with encryption, so there is a common denominator thats causing these issues and if your saying its happened to you going from MM to MM backups then clearly its not specific to rolling back from N, however you are the first person i have seen myself that has said they had issues with going between MM builds.

Everyone has already attempted to restore backups they already had, and nobody i can see has said oh yeah what i did was "Totally wipe everything and flash absolutely everything need for a fresh MM image and then attempted to recover with a backup" its always after they have done something else !

Every ROM thread worth its salt always states to flash fresh when swapping builds and has done for along time, you dont go flashing a phone that's running 5.X.X directly over to 6.X.X builds, like wise for those with issues with roling back from N why restore a MM build that's clearly different from the OTA build of 7 that will have changes that are likely not addressed in your recovery ?! ( I agree this does not work in your case ) its akin to trying to use a windows restore tool from windows XP on a windows 10 machine its just not going to cut the mustard.

Full wiping and Flashing a full fresh factory image before attempting a restore should be a no brainier, and from the three times i have done exactly this to test I fail to see why many people have this issue.

Clearly TWRP is not updated for this build of N and their page says nothing to suggest it is so why assume ? follow known good practice that has been preached on XDA for the last few years and it works fine. . .

If your doing something that's unknown and then attempt to rectify it by going for the default safe option is always going to have a chance to not solve the issue because well people = stubborn and ultimately stupid because they are in a rush for the newest shiny thing as fast as possible.

Again absolutely no issues here three times over flashing back.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
ok here is how i bootlooped and never came back... NEVER EVER FLASHED A VERSION OF N OF ANY KIND. Upgraded twrp to TWRP 3.0.2-1 and like i do with every release of twrp I go in make a backup and restore and now my phone is on its way to rma. It was running the latest version of purenexus... that was all.
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
Well the common denominator is this TWRP 3.0.2-1 build clearly, its working with decryption of the latest N build as the change log says, did you attempt to use 3.0.2-0 ?

I wonder if someone with the issue can Flash the 3.0.2-0 build and attempt to flash an image that way from N to MM, as for your MM to MM i'd guess that the 3.0.2-1 build has its own set of issues when flashing backups for MM.
[Nexus 6P Q&A, Help & Troubleshooting] psychemisha:
Yes man same here the new twrp coused this to me
[Nexus 6P Q&A, Help & Troubleshooting] ciocu:
I find it interesting that I was running a stock MM (unlocked bootloader, no root, no custom recovery), then I sideloaded the OTA in stock recovery.

N was working great for couple of days, until I was browsing some webpage with chrome, when the phone rebooted and the already famous bootloop started.

First thing for me was to try and go into stock recovery, to wipe cache ..with no luck, since any option from the bootloader led to bootloop (except for power off).

Then, I have downloaded the latest MM factory image on my laptop, and I ran the flash-all script. Completed with no errors, however bootloop was still happening :(

I downloaded TWRP, tried flashing several versions, all without luck (bootloop).

I tried older factory images, still with no success.

Then, I contacted Google, and they offered to RMA the phone (6P was purchased from Play Store and still covered by warranty).

Now I'm patiently waiting for the replacement to come, and I'm reading XDA, hoping that someone will find the cure for this weird brick.
[Nexus 6P Q&A, Help & Troubleshooting] BakedTator:
Just by reading this it seems it is twrp that is causing the issue (99.9% of the time).

I had used twrp 3.0.2-1 to backup my nougat OTA, and flash the AOSP build of 7.0. after I had some crazy issue with open Gapps causing Google play services to crash on that ROM, I went to restore my backup and that started my bootloop and was unable to recover from it.

My finger points to the newest twrp restoring backups as the issue (though is possible I am completely wrong)

Upon the bootloop happening, I was still able to get into the bootloader and recovery. Adb and fastboot both seen my phone as I tried to flash stock images and OTA's to recover my phone from the brick
[Nexus 6P Q&A, Help & Troubleshooting] tsuttie99:
I agree with this EFS statement. I have not had this issue but been reading up on this throughout XDA. There are multiple reports of people being able to boot into 7.0 after bootlooping but then they have no SIM/Service/Camera. Which would support issues with EFS.... Unfortunately I am not advanced enough to diagnose EFS issues. I just know to back the $hit out of it before doing anything.
[Nexus 6P Q&A, Help & Troubleshooting] BakedTator:
This is because the only way to boot the phone after this issue is to flash the nougat OTA and the latest MM vendor.

In doing this, it screws you camera, sim slot, and sensors up...it was the only way I could boot my phone! It pretty much makes it a nexus pod
[Nexus 6P Q&A, Help & Troubleshooting] tsuttie99:
That's exactly what I've been reading thank you for clarifying.
[Nexus 6P Q&A, Help & Troubleshooting] ciocu:
so, then, I'm one of those lucky 0.1% bastards, whose 6P died while using a stock recovery, no root, and an unlocked bootloader :confused:

from my experience with my 6P, I still have no idea what happened there.. one moment everything was fine, than the next moment bootloop :confused::confused::confused::confused::confused::confused:

once again, I did not try flashing anything BEFORE the bootloop
[Nexus 6P Q&A, Help & Troubleshooting] busbeepbeep:
I'm with you, part of the 0.1%.
[Nexus 6P Q&A, Help & Troubleshooting] BakedTator:
Did either of you get an OTA right before it died?

And please don't forget the part where I said I could be completely wrong...lol. It's just what I have observed
[Nexus 6P Q&A, Help & Troubleshooting] rchtk:
Sorry for you.

For how long have you been having the device?

Not sure if it's emmc or battery related, looks like battery.

Could you try this command (in twrp term or adb shell) to have your phone read mmc0:

dd if=/dev/block/mmcblk0 of=/dev/null

At 230MBps it should last around 130 seconds. What speed and size does it give? Any error?
[Nexus 6P Q&A, Help & Troubleshooting] seco2004:
So my theory is confirmed: the phone actually works when battery level is at 10% or below (see screenshots). Left the phone running through the night and noticed from the uptime that it didn't reboot. This is the weirdest thing I've seen, I mean I heard about 6Ps turning off when getting down to 20%, but never heard of one that only works below 10% :confused: Do you guys think a battery replacement could fix this thing?

[MENTION=4533695]rchtk[/MENTION] I have the device for 4 months now. This is the output of the command:

~ # ←[6n dd if=/dev/block/mmcblk0 of=/dev/null

61071360+0 records in

61071360+0 records out

31268536320 bytes (29.1GB) copied, 143.919210 seconds, 207.2MB/s
[Nexus 6P Q&A, Help & Troubleshooting] BIGSAMDA1ST:
Ok. So I don't know what the deal really is because I haven't seen Google say anything about it, but I just received my replacement device and it was on 6.0.1 ,now just be on the safe side I called Huawei which is whom I got my replacement from and I told them that I had an update on my phone. The tech asked me which version was the phone currently on and I told him 6.0.1, so he basically told me "Do Not update" because that 7.0 has a serious issue that bricks the 6P's and 5X's and that Google was aware of it. He said that Google was already working on an update to rectify numerous devices being bricked. But damn Google if you know that the updates are working phones, why not pull the factory images from your website until then? Anyone else heard different?
[Nexus 6P Q&A, Help & Troubleshooting] playaz33:
Same thing as what I experienced.

It seems to work:

"3) when I drain the battery and try to boot into recovery while it is charging up"
[Nexus 6P Q&A, Help & Troubleshooting] MoistPicklez:
Update: Finally got my Nexus 6P back from Huawei's sister company FutureTel. It works 100% thankfully and they returned it in perfect condition after about 12 days.

It is on one of the oldest MM builds and I'm seriously freaked right out, on whether or not I should update it to a more recent factory image or leave it on MM.

May I ask some opinions from some great XDA minds on what to do? Im well seasoned in flashing factory images and ROMs, but when it was fatally bootlooping I was last on PureNexus Nougat and I really don't want to go through this again, as my warranty is now gone..
[Nexus 6P Q&A, Help & Troubleshooting] jamaniek:
But it's the same phone, not a replacement? I'm curious on what exactly's been done.

I'm sending mine next week. Hopefully it'll come back quickly :fingers-crossed:
[Nexus 6P Q&A, Help & Troubleshooting] MoistPicklez:
Same phone different insides. Before my 6P had a Samsung eMMC and now its a Toshiba. My guess is they just replace the insides of the phone and left the shell
[Nexus 6P Q&A, Help & Troubleshooting] chrispy_212:
I really wanted to unlock and root my 6P (no ROM flashing) that has been stock (plus dev preview) since day 1, mostly for the Pixel goodies (especially Assistant), but this thread has me really concerned that I could be a fortnight without my phone if I do, and the benefit doesn't really outweigh the risk. Are we any closer to finding the culprit that's causing this?