yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
My device is

Bootloader - 3.58

Baseband - 3.72

Variant - VN2

CPU - 0x20001

eMMC: 32GB Samsung

DRAM: 3072 Samsung LPDDR4

Console - NULL

Qfuse status - Enabled

Download Mode - Disabled

Manufacture data - 12-24-2015

Did not have a bootloop issue. Flashed to Stock MTC20F and then side loaded N OTA zip via stock recovery. Used N for a full day and then ran flash-all script inside MTC20F factory package to successfully get back to MM.

Have you tried side loading the N OTA zip from Stock Recovery?

Try this...

Twrp->full wipe including formatting data. Flash MTC20F Vendor.

Reboot to bootloader and run Flash-all script in MTC20F factory image.

See if it boots. If it does yay, if not, fastboot twrp and boot into recovery and flash MTC20F Vendor and reboot. Let me know what happens.

Edit: I keep seeing people post about N Vendor, where is this Vendor you guys speak of?
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
LOL I fixed my phone in 2 hours. My phone is working with no issues. The problem was the EFS partition. Read through the post, I'm here helping ppl not looking for help. OP tagged me for this thread cause i was helping ppl in the Botched update thread. I had a bootloop issue on Saturday but I fixed mine restoring my OG firmware that came with phone in FEB and the EFS backup i made at the same time.

Also Sideloading the N Update is the worst advice. That's what cause most of these issues, sideloading the update over things like a custom ROM. If you're bootlooping as well best thing is to go back to MM with restoring EFS and vendor from MM
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
My apologies, I thought your device was still looping.
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
Ok so add me to the list of unfortunate accidents.

My Device:

Bootloader - angler 3.54

Baseband - angler 3.61

Variant - Angler-row-vn1

CPU - MSM8994 0x200001

EMMC - 128GB Samsung

DRAM - 3072MB Micron LPDDR4

Console - NULL

Qfuse status - Enabled

Download Mode - Disabled

This is found in bootloader - barcodes

Manufacture date - 11-17-2015

So I was on latest Pure Nexus Rom (8-21), I decided to try 7.0 and I flashed tupac4u's Stock+ Debloated rom and his bootloader+radio zip. Tried 7.0 for a while and decided to switch back because some of my important apps are crashing on 7.0.

Did a wipe in TWRP 3.0.2-1 and restored nandroid of my Purenexus, no go. Bootloop hell. Did many things like reflash TWRP 3.0.2-0, reflash the stock+ 7.0 rom, flashed stock MTC20F using Heisenberg's method (did not wipe userdata though), reflash MTC20F vendor, bootloader and radio images, still in bootloop hell.

So the only thing I haven't tried is to wipe out all internal storage by formatting userdata partition. Did anyone still face bootloop even after formatting userdata and wiping out internal storage?

Also I realized not everyone here has mentioned whether they were decrypted or encrypted prior to flashing 7.0 for the first time. I was on encrypted Purenexus rom and I read of successful cases of decrypted phones. So I'm hoping that a format of userdata might do something. Otherwise I'm out of options here.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
As long as you haven't written over that data, I'd back it up. Then move it to a PC. Then you can try any method you haven't.

Thanks for the thorough reply.
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
Alright, so after some more testing, I somehow managed to boot into Android 7.0 again... but did not fix the issue at all. It's like someone else in this thread or the other botched thread.

Anyway, what I did was:

- flashed TWRP 3.0.2-1

- wiped factory reset

- flashed the stock+ debloated 7.0 rom

- tried to reboot, no go

- went back to TWRP and flashed MTC20F vendor

- reboot, and somehow the boot animation is showing for a while, then it reboot again and this time it finished loading into Android

- unfortunately because its the wrong vendor, I can't use the rom and the "something wrong with your internal" pop up

Anyway tried to reflash the Android 7.0 rom didn't work, and tried to reflash MM rom didn't work. Bummer.
[Nexus 6P Q&A, Help & Troubleshooting] indian84:
I am in similar boat. I fastbooted N DP5 and installed MTC20F vendor with TWRP. the bootloops stopped. Bus as mentioned earlier, no baseband and camera doesn't work.

I am trying to get my phone RMAd and waiting for final Nougat factory images. I am still hoping when we have Nougat factory Images, we should be able to get the devices back and running.
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
Nah man, it's all good ;)
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
Just to chime in here, I see people have managed to flash the MTC20F vendor and DP5 and get their devices to boot but unfortunately have several driver issues that are not correct due to incorrect drivers in the vendor image.

What about getting one of the previews to boot and then using the TWRP 3.0.2-0 build that had no problems with the Preview builds and factory resetting and flashing back the correct vendor a custom rom based on MM.

i don't recall any issues with the preview builds and flashing back to MM
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
mine is sent out also, I tried flashing both vendors and copying the contents to a diff folder. What i did was flash an N vendor mount in twrp copied the contents off then flashed the MM vendor and mounted it and copied it off, then flash the N vendor again since its a bigger partition adb shell while booted into twrp rm -rf /vendor/* and then copying the MM contents to it = no boot. I then flashed the MM vendor again rm -rf and tried copying the contents from the N vendor image over but it misses a few files since that partition is 2 meg smaller , BUT it boots up and the same 2 things don't work sim/camera. I think that partition size of the vendor image has something to do with it.

---------- Post added at 08:26 AM ---------- Previous post was at 08:23 AM ----------

if you copy the build.prop from the N vendor image and copy over the one from the MM vendor that msg will go away but you will still not have a working radio/camera
[Nexus 6P Q&A, Help & Troubleshooting] vestaviajag:
Maybe different situation?

FORM:This info is found in the bootloader

Bootloader - angler-03.54

Baseband - angler-03.61

Variant - ANGLER-VN2

CPU - MSM8994 0x20001

EMMC - 32gb Toshiba

DRAM - 3072mb HYNIX LPDDR4

Console - NULL

Qfuse status - ENABLED

Download Mode - DISABLED

This is found in bootloader - barcodes

Manufacture date - 05-08-2016

Brief description of where the bootlooping started - Phone has always worked well; ran stock the day I got it, unlocked & rooted the next day flashing Dirty Unicorns. Except for a few tries on their nightlies which didn't work, I've only ever flashed their latest MM weeklie or official (last one I flashed was 8/28). Never flashed kernels. Yesterday afternoon at home, noticed I couldn't make calls, which I was on a call not but an hour before on the way home from work. Tried clearing the phone app cache, force closing it, rebooting; all to no avail. Tried wiping cache in TWRP (3.0.2-1) also did not work. Tried flashing the ROM again to overwrite see if that helped, it didn't. Tried flashing a backup, the bootloops started. Tried flashing an older version of Dirty Unicorn w/ corresponding vendor image, didn't help. Still in bootloops... I have not been able to fix my device

I have tried methods - #3 & #9. When I get time at work, I will start down the list w/ #1.

Any help or advice would be greatly appreciated. It appears (from last few pages) this is mainly for ppl who've gone to 7.0 then tried to get back to MM. Unfortunetly (I guess) that doesn't describe my situation. Hopefully someone can at least point me in a direction to try.

Also, slightly off-topic, what are my options to return phone (warranty, etc.?). This is my first Nexus, and ironically, my first bootloop/brick? that I couldn't get out of.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
leaning towards TWRP (3.0.2-1) is the culprit here regardless if you were on N or not when it happened.
[Nexus 6P Q&A, Help & Troubleshooting] vestaviajag:
That was my thinking too, so I did fastboot flash back to 3.0.2-0. Still same results though.

While I believe TWRP to be somehow connected, I'm still confused how the status of this phone went from fine 12 hours ago on a MM ROM -> no calls (but data?!?) -> no calls w/ previous MM versions of the ROM -> not booting.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
I think once you do a back up and restore with the -1 version its too late.
[Nexus 6P Q&A, Help & Troubleshooting] vestaviajag:
I did (apparently) flash 3.0.2-0, but maybe you're right, downgrading isn't that simple. FML. Any other suggestions? Haha.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
well my 6p is arriving at the service center today....
[Nexus 6P Q&A, Help & Troubleshooting] pahlerc1:
That's what I was also thinking.. Everything was running fine until I updated TWRP to 3.0.2-1.. not sure how or why, but that's what I am telling myself was the culprit.. I tried every combination I could for about an entire day, got tired of f**** with it so I fastboot flashed stock MTC20F, locked the bootloader, and sent to Huawei.. patiently waiting for the 14 business days to get my phone back.. but probably won't root it this time, wait out the next month sell it and get the Google Marlin. Kind of upset the first Nexus I ever purchased was able to be bricked smh but that's the risk we take.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
did the same.
[Nexus 6P Q&A, Help & Troubleshooting] tmar89:
So I'm not in a boot loop issue, but I don't know if I have a hardware or software issue. I got this device Used-Like New on Amazon and it has stock 6.0.1 MMB29M installed, unlocked and with TWRP 2.8.7.2. When connected to a PC in bootloader mode, it will not be detected as an ADB device or USB device. Windows doesn't see any device at all. The device does charge. I tried 3 different cables, 4 different PCs, all USB ports. Is there a way that the software could be faulty where the USB drivers on the phone aren't working? And if so, can it be updated through TWRP alone? I see many of you have different bootloaders, baseband and even TWRP. Again, I cannot connect to a PC to update but I could get files onto this device through Google Drive. Thanks.

Bootloader - angler-02.45

Baseband - angler-02.50

Variant - ANGLER-VN2

CPU - MSM8994 0x20001

EMMC - 32gb Samsung

DRAM - 3072mb HYNIX LPDDR4

Console - NULL

Qfuse status - ENABLED

Off-mode-charge: ENABLED

Download Mode - DISABLED

Manufacture date - 10-06-2015
[Nexus 6P Q&A, Help & Troubleshooting] vestaviajag:
So in y'alls opinion, there is not coming back for this phone w/out sending it to Huawei?
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
I believe the twrp people need to see this issue in order for that to happen.

or if someone can DD their phones whole file system while on MM install the latest twrp make a backup flash bit back and if brick DD the image back
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
There's still the last hope of flashing the nougat factory image once it comes out. I've already wiped my phone clean to the bone. But nothing works.
[Nexus 6P Q&A, Help & Troubleshooting] psychemisha:
Ihave been able to boot after itook full recovery from my feiend with efs through twrp 3020

---------- Post added at 04:34 PM ---------- Previous post was at 04:33 PM ----------

Iam sorry from my friend u need full back up and then u rwstore it with efs
[Nexus 6P Q&A, Help & Troubleshooting] downslayer:
I think you hit the nail on the head there with the recommendation. My phone is currently in bootloop city and I am waiting on a replacement for the same thing. I had a similar issue trying to restore my phone by flashing N again (of course with the N vendor). I will try flashing tonight with the latest MM vendor over N, but I also noticed the google logo started to change for a second and then jumped back to a boot loop, which is the most I've gotten out of my phone in terms of booting since this started.

I did try to restore a MM backup with every option selected in the latest TWRP (including vendor) just before the bootlooping started. I am really hoping that a new version of TWRP or a factory image drops soon that might fix this, as I am without a phone at the moment. I haven't gotten the email back from google but I am on the 128GB version at the moment and I have heard the version you get back is refurb. I'm really hoping I can fix this phone and not have to deal with potentially getting a smaller version. I don't understand what could mess up that would cause fastboot restoration of stock images to fail to boot. Shouldn't that always fix it?

---------- Post added at 01:09 PM ---------- Previous post was at 01:04 PM ----------

Is an EFS backup something that can be shared without revealing personal information and/or is it unique to your exact phone? I had an EFS backup but in my wiping frenzy I accidentally formatted my internal storage and lost it. If it is not unique to you/your phone, could you share it? I have not been able to boot my phone in 2 days as it has been stuck in bootloops and I think it may be some change in EFS that is not fixed either by wiping and fastboot restoring a stock image or by wiping and installing a ROM in TWRP.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
When you restored in TWRP, did you restore Vendor?
[Nexus 6P Q&A, Help & Troubleshooting] vestaviajag:
Restored my backup? I don't remember, but I don't think so. I was under the impression (possibly wrong) that if I wasn't going from one ROM to another that was on the same vendor image, it wasn't required to flash the vendor image every time.
[Nexus 6P Q&A, Help & Troubleshooting] pahlerc1:
IMO yeah, i just didn't have a back-up to use, and having Project Fi as my service provider, it kind of put me in a bad situation.. so i am going to tmobile after work to pay for a month of service to hold me over until i get my 6P back.. I mean i tried everything I could, got completely fed up with it and figured I should go ahead and get the ball rolling on a RMA.. it's all up to you, maybe the 6P Android N factory image will help, maybe not... who knows, something is completely borked in the phone though, that's for sure

---------- Post added at 01:31 PM ---------- Previous post was at 01:23 PM ----------

yeah i called Huawei several times to discuss details of this.. they do state that I will be getting back a refurb, which is okay with me.. I dont care, I just want a working phone, they also state they will send back the exact same color and size. So I should be getting back a 128gb graphite 6P.. not sure why or how this happened, but all i have read for years is that a nexus shouldn't brick, and factory images fix everything.. apparently not with the issue we are all dealing with. but regardless, i sent my phone in, i need a phone, no backup device to use with project fi.. and with the fact that most nexus devices have a factory 7.0 image, i wonder if it is something to do with internal hardware for out 6p that is causing an issue with this.. i don't know, just speculation, but i also think the new twrp 3.0.2-1 had something to do with this issue
[Nexus 6P Q&A, Help & Troubleshooting] Gytole:
Method 22

Let me know if you have more![/QUOTE]

My method, post 69, looks like nobody tried a manual format/erase and manual flash. FULL erase and FLASH! Good luck!
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
I believe the EFS is unique to each phone and one will not work the other. Unless someone knows for certain that is not the case. That's why the instant you flash TWRP you MUST do a backup for your EFS partition and then make a duplicate somewhere on you PC. Also, I recommend doing an EFS backup with every major update your phone gets
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Do you not have another device you can just throw the Project Fi sim in?

---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------

I asked because most people restore everything they backed up. Vendor is normally something that is selected to backup automatically unless you deselect it. Restoring the Vendor image or partition can cause bootloops to occur.
[Nexus 6P Q&A, Help & Troubleshooting] Gytole:
Someone try my method and see if you get anywhere.

Post #69
[Nexus 6P Q&A, Help & Troubleshooting] gruppert246:
Hey guys,

I am perplexed.... I have read through all of the posts here and 98 percent of them are pretty similar to the issue that I am experiencing. The only difference is that my recovery is wiped out clean as well. I can not boot into it...I have tried flashing TWRP and also stock recovery and I get the boot loop. A little back history

So I was using 7.0 final release and I received it OTA. I have had no issues at all. However, yesterday I was using my device and I received a phone call. I dismissed it because I was not able to answer the call at that moment. As soon as I dismissed it, the phone restarted. And that is when the boot loop city happened. Now, my phone was not rooted, however, my boot loader was unlocked. I have tried everything imaginable and nothing works. I have tried flashing earlier versions of 6.01 with no luck and flashed 7.0 with no luck. I have tried restoring 7.0 and flash the 6.0.1 MM vendor file but did not work. Flashing the stock rom has always fixed my issues but I don't think it's going to save me this time.

I do not understand why my recovery does not work at all. I can't flash twrp or anything at all. I do not get an error message when flashing twrp or stock recovery. My computer says it was a success and I get no error on the phone. However, when I go to reboot into recovery...I get BOOTLOOP. Any thoughts? Thanks guys for all your help
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
Did you relock the bootloader? If so and you had TWRP installed, you hard bricked the phone.
[Nexus 6P Q&A, Help & Troubleshooting] vestaviajag:
[/COLOR]

No, typically I do not backup vendor in TWRP, as I always save the latest two vendor images on my /sdcard. My fault, I didn't understand what you meant.

Tried your post, did not work for me. Only thing it did that was noticable was wipe my recovery.
[Nexus 6P Q&A, Help & Troubleshooting] psychemisha:
Iam uploading full backup with efs to mega its from 64 gb version no metter flash twrp 3020 flash mtc20f bootloader restore back up and your phone live and kicking

---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------

Oh wipe data sustem art and cache

---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------

When it be loaded ill share link
[Nexus 6P Q&A, Help & Troubleshooting] pahlerc1:
Nope, this is my first Nexus device, and only three devices work on Project Fi so far --> Nexus 6, 5X and 6P

I went all in on the 6P getting the 128gb.. oh well it's all good.. phone is sent to Huawei, I'll get my new one in about 3 weeks and leaving work soon to get some TMobile coverage for the time period.. luckily my dad has an extra Nexus 5, so I am going to throw my SIM in it this weekend when I go and visit the family.. Project Fi is taking care of me, gave me a nice credit since I can't use their service for the time period.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Any phone that can use T-Mobile service will work on Project Fi. The only issue is it won't switch to Sprint towers. If you have a phone that can run on T-Mobile or US Cellular, all you have to do is insert the sim card as long as it'll fit the slot.
[Nexus 6P Q&A, Help & Troubleshooting] pahlerc1:
Hmm okay I didn't think about that.. Thanks for the heads up.
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
I think google know about this issue hence the lack of factory images, I think we will see an OTA update and images sometime next week
[Nexus 6P Q&A, Help & Troubleshooting] gruppert246:
No, I did not relock the bootloader and I did not have TWRP installed at all. I tried after the bootloop had already started but by that time...TWRP would not install nor would a stock recovery.

As of right now I do not have any recovery installed. When I select recovery mode...I do not get any green alien with an exclamation point...I just get reboot.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Yeah no problem, wanted to keep you from having to pay them "extra" for service you already have. I used to think that I HAD to have one of the 3 Nexus devices until I accidentally Google'd what devices people have tried.
[Nexus 6P Q&A, Help & Troubleshooting] vacaloca:
Maybe slightly off topic, but can anyone (whether borked or not) check if there are any files on their persist partition? It gets mounted on /persist

I remembered that when attempting to un-brick from the 7.0.0 -> 6.0.1 fiasco, I actually formatted that partition, thinking that it was actually the EFS partition (it is not -- those are actually named modemst1 and modemst2 -- which is what gets backed up by TWRP as ef1 and efs2), so I don't know if there was actually anything in it to begin with or what it holds on the Nexus 6P. I haven't had any problems with any of the phone sensors that I've noticed, and my bluetooth/wifi mac addresses seem correct, so maybe no ill effects, but still curious. Feel free to send a PM to not clutter this thread.
[Nexus 6P Q&A, Help & Troubleshooting] Ulver:
So if I wanted to go back to Marshmallow, is there any problems with just flashing the factory image with a full wipe?

Sent from my Huawei P9
[Nexus 6P Q&A, Help & Troubleshooting] mbutandola01:
Long story short, don't do it

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P Q&A, Help & Troubleshooting] chevycam94:
You're correct, at least in my case. Mine was noted as a refub on the bill. Just to be on the safe side. Im going to stick to a Marshmallow ROM, since I know all of them are safe. Something with Nougat doesnt allow downgrading (or at least in specific circumstances). I'll wait until there is an OFFICIAL factory image available from Google for Nougat, and wait until I hear that others can confirm that the issue has been fixed (or found a way to fix it unofficially).

Im going to say its either TWRP or the Nougat vendor image that is causing this headache. The evidence doesn't point anywhere else.
[Nexus 6P Q&A, Help & Troubleshooting] SlimSnoopOS:
Yes, I have several files there on my 5X. So there should be some on your 6P.
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
Correct. I came to the conclusion about TWRP last Saturday. Also EFS has something to do with it as well as i tried to make a backup of Nougat in TWRP and decided to restore the backup and constant Bootloop. Only thing that saved me was restoring my EFS and Stock backup Rom from when I got the phone in Feb (was on 29Q) and presto, phone booted perfectly.

So it is certainly 1 of 3 things. TWRP, Vendor, EFS or a combination of 2 or all 3 of them.