yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] Funkwheat:
Oh, I'm totally not disagreeing with you on that one. I honestly wasn't even expecting it to work, I knew exactly what I was doing and why I shouldn't do it. I figured if it doesn't work I'd just revert to backup or reflash the factory image; no harm no foul. The point is, though, like you said earlier, anything on a Nexus should be fixable by properly reflashing a factory image. I had never heard of something like this happening where it just plain can't be restored. The mind boggling part here is that this not only resulted in a soft brick, but an unrecoverable one.
[Nexus 6P Q&A, Help & Troubleshooting] akumalol:
FYI. I managed to finally boot again on Android 7 using the OTA update from here. https://www.reddit.com/r/Nexus6P/comments/4z4ru1/android_n_ota_link_for_nexus_6p_from_601_to_70/

The problem is i cant get back to MM and i guess i have to wait somehow for the updated apps to work with Nougat.
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
Have you tried flashing MTC20F factory images, then booting into stock recovery and downloading the OTA zip?
[Nexus 6P Q&A, Help & Troubleshooting] Funkwheat:
yep. Just tried again just for fun. Reflashed factory MTC20F, sideloaded ota.zip through factory recovery... boot loop city.
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
At this stage I'd be contacting Google and organising a warranty exchange.
[Nexus 6P Q&A, Help & Troubleshooting] Funkwheat:
Yeah, waiting for my office to clear out so I can call them from work. (since I don't have a cell phone). Thanks for the help! So much for the idea of Nexus phones being invincible. :x
[Nexus 6P Q&A, Help & Troubleshooting] :
Did you you guys reflash rom and then vendor image? That user in pic that I posted had same problem. I personally would never update while still Rooted or Rom'ed, and would flash stock image before updating or taking ota. I had a Samsung S5 stock rooted no rom, it updated because I didnt freeze DM Service, lost root on that phone. It happens..better hope you have insurance, Its android 101....by no means am I a pro, but there is a code we androdians must live by. Good luck to you guys. Patience is a virtue.

---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------

This happened on my Note 4, I couldnt go back to Kit-Kat for some reason on lolli I could go back and forth between that and MM. Its weird....its like they blew a qfuse or sometin.
[Nexus 6P Q&A, Help & Troubleshooting] Funkwheat:
Yeah, I tried what that user said as well. Several times. And yeah, I am aware of the dos and don'ts of Android, I always have been. But I also live by the code of "anything you screw up on a Nexus can be fixed with a factory image restore" sooo my confidence in that led me to get ballsy.
[Nexus 6P Q&A, Help & Troubleshooting] itspritts:
I am in the same boat. I've been flashing since Cupcake. I have never ever seen an issue I couldn't get around on Android. I took the OTA from NP5 beta. Decided I wanted to go back to 6.01. Boot loop. Flashed multiple stock images, used wuggs, I have done everything. Unbelievable.
[Nexus 6P Q&A, Help & Troubleshooting] Ericarthurc:
Sorry your dealing with this! There just seems to be a huge problem going from 7 back to 6. The actual Nexus 6p factory image isn't out yet but when that does come out (hopefully soon) you could give that a shot. If your phone is under warranty still I recommend getting a replacement phone. That's the route I ended up taking; and I am stay far away from 7 until this issue is resolved and custom rom developers get a hold of it. There seems to be no explanation to why this is happening either... People from stock and custom roms are experiencing this issue; it just seems that going back to 6 from 7 is causing the problem. Good luck mate!
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Last one.

Never mind
[Nexus 6P Q&A, Help & Troubleshooting] BakedTator:
My efforts to restore my other 6p have failed...no stock firmware will get it to boot
[Nexus 6P Q&A, Help & Troubleshooting] :
Maybe if someone flashes a stock Gingerbread ROM
[Nexus 6P Q&A, Help & Troubleshooting] BakedTator:
You're a smart ass and you just about made me spit my food out reading this... That was great! Lol
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
I just tried cupcake from the Droid X and it worked. I can't touch anything though :/ and the resolution is way off.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
That's why I erased my posts. I never said I knew more than any of you, yet the ideas I came up with have now become a laughing matter. That's why I erased my posts, I saw it coming down to this! Good job!

BakedTator, did you get any errors while running the flash-all script?
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Your idea isn't a laughing matter. It's even included in my 20+ methods list on the other thread.

EDIT: It was just stated back on like, page 1-2.
[Nexus 6P Q&A, Help & Troubleshooting] BakedTator:
No errors at all...everything went through as expected...but right into the bootloop
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Can you get into stock recovery?

If yes or no, flash twrp (latest) and do a factory reset, flash the vendor image for the firmware you flashed and reboot.

---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------

No explanation needed. Your post and the others are there, pretty sure it became a laughing matter but it's okay. I am here to sort out the same issue anyways.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Everyone interested in troubleshooting, please check out this thread.

Also, if you are looking for all the fix methods/attempts, I have a compiled list as the 2nd post.
[Nexus 6P Q&A, Help & Troubleshooting] be_vigilant:
I doubt you can fix it if you cannot even flash access\flash twrp. I will try to clear things up.

What caused my bootloop

I was on latest stock image, rooted. I side loaded the OTA using TWRP 3.0.2.1. 2 errors came when flashing system and also vendor. Device rebooted to the google logo, then gets no further. There is no boot animation.

I tried flashing many stock images from bootloader using flash-all.bat They all completed without error yet also would not boot past the google logo.

Exact steps I used to fix my bootloop

1) Flashed full stock image MTC19T in bootloader using flash-all.bat

2) Flashed twrp 3.0.2.0 recovery from bootloader. fasboot flash recovery twrp-3.0.2.0.img

3) Loaded into TWRP recovery

4) Went into wipe , advanced clicked on each partition and selected repair

5) Restored a stock MTC19T backup I had from May including ALL partitions. EFS , vendor ETC

6) Rebooted phone. At this point it would boot past the google logo and show boot animation.

7) Rebooted into bootloader and flashed latest stock image MTC20F

8) Phone is alive and everything works.
[Nexus 6P Q&A, Help & Troubleshooting] Juzman:
I checked the recovery.log from my PN backup when I did the EFS backup, and noticed something interesting:

ro.build.id=MOB30M

ro.build.date=Mon Aug 22 17:17:54 EDT 2016

ro.build.description=omni_angler-eng 6.0.1 MOB30M 5 test-keys

ro.build.fingerprint=Huawei/omni_angler/angler:6.0.1/MOB30M/5:eng/test-keys

There was no MOB30M for Nexus 6P (only Nexus 6). So I am going to try and flash the MTC19V factory image, TWRP 3.0.2-1 and restore EFS.

Flashed MTC19V and could restore EFS in recovery. Then flashed MTC20F but bootloop.
[Nexus 6P Q&A, Help & Troubleshooting] jesssiii:
I flashed the OTA update over DP5. I've since restored PureNexus MOD rom backup, flashed Digitalhigh's Nougat rom, restored again my PureNexus MOD rom backup. All successfully, all with twrp 302-1 latest.

I'm decrypted. Just curious if that makes any difference? For instance, are the looping people encrypted when it started and ones who were able to fix decrypted from the start?

Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] rbouza1:
I'm decrypted and I looped too, but restored a backup after a factory image and manual fastboot of bootloader, radio and vendor .
[Nexus 6P Q&A, Help & Troubleshooting] CallMeAldy:
Devices here (India) new/old are still being sold for at least 80-90% of the launch price.
[Nexus 6P Q&A, Help & Troubleshooting] Juzman:
Took the phone into the phone store today. They're organising a replacement. Should arrive within 5 business days.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Just to clear up a few things.

The system error and vendor errors will always happen when side loading the OTA. It's doesn't matter if you're using twrp or stock recovery.

I do think you guys should stop restoring backups though. Restoring the vendor image or partition from any backup can cause looping. The best thing is to just flash the correct vendor.

Here's another thing, I saw a few people post about the Nougat vendor, where the heck did you get that at? Please share it as I would like to do some testing. The OTA only has a patcher for the Vendor as far as I can see.

---------- Post added at 08:30 PM ---------- Previous post was at 08:27 PM ----------

Do you still have the bootlooping 6P? If you do I would like to do some testing with you.

Please add me to hangouts: xdahelper@gmail.com

If anyone else is interested and has the time and patience to do some testing with me, feel free to add as well.

We can report our findings when we are done.
[Nexus 6P Q&A, Help & Troubleshooting] tyea:
I'm game for testing on my bootlooping N6p.
[Nexus 6P Q&A, Help & Troubleshooting] Juzman:
Nope. They took it to send away, and organised a new one to be shipped.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
I have a broken device still. I'm down to do more tests. Note: mine bootlooped from something different than everyone else's.
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
Ok I'm encrypted and my phone is bootlooping, could this be a factor? So far I've seen reports of decrypted phones successfully fixed.

How about those on encrypted phones?
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Please add me to hangouts: xdahelper@gmail.com

Just want to do it in a more controlled space. It's late here so I'm going to bed, I'll talk tomorrow
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
I even decrypted and installed a no-encrypt kernel and still bootlooped
[Nexus 6P Q&A, Help & Troubleshooting] Train88:
I flashed the full ota in TWRP 3.0.2-1 and everything was fine... But I only wanted to get a quick look at what kinda work we had to do once source drops. So I backed up, then tried restoring my DU backup. That was my mistake. I tried everything from a normal wipe and reflashing the ota, to wiping my entire device and flashing latest factory image. Nothing I tried did anything other than loop between the Google logo and "can't verify" screen. Then I saw be_vigilant's post and remembered I had a backup of MMB29P, so I downloaded the corresponding factory image, and followed his steps exactly. It booted up, and I was then able to flash/update everything accordingly to restore the nandroid I made & pulled to my PC before flashing the ota.

Possibly noteworthy: I was able to stay decrypted through the entire fiasco (Including factory reset through stock recovery, etc), and I still am now. Another factor could be that the MMB29P backup was from when I initially decrypted my device, so I was able to easily pull all my pictures, backups, etc from my PC through adb
[Nexus 6P Q&A, Help & Troubleshooting] opz187:
almost exact same process I did. I was hopelessly bricked. I think a mistake I made and that others have made is freaking out and formatting the devices too soon.. I think adb woulda been helpful in stock recovery but once you format, forget it. I know twrp will still recognize adb but I didn't have any success with any adb commands in twrp. anyway I even got ahold of the NRD90M factory image and fastboot flashed all of the. imgs correctly, STILL no luck. finally I got desperate and had a nandroid on my CPU of ubermellow back from like December, backed up everything from boot to efs, I restored it, it booted to the Android animation and for a few tense seconds i watched as those circles spun and changed color.. it booted to the lock screen and I think I yelled "I am god!" at the top of my lungs. now I'm on weta 7.1. it might not have been a factor, but at some point in my journey I removed my sim to see if that helped anything. but don't give up, I was certain I mine was bricked for life, but am ecstatic it's alive
[Nexus 6P Q&A, Help & Troubleshooting] SlimSnoopOS:
Where did you get the NRD90M factory image from?
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
Well I'm giving up trying. Sideloading OTAs, full flashing factory images all don't work.

I'm just going to wait for Nougat Factory Image to be out as my last resort and if that doesn't work, off to service center.

I think many of those who managed to fix the bootloop, they have a copy of an old backup nandroid that has all partitions backed up, including EFS, vendor partitions. I accidentally deleted my old copies of nandroids and the only backup I have is one that only has boot, system and data backed up, so using that did not work.

I did make a full nandroid of MTC20F rom, but I used TWRP 3.0.2-1 to back up and that doesn't work as well.
[Nexus 6P Q&A, Help & Troubleshooting] akshaysalunke13:
Factory image.!???? From where bro?
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
There is a 1.1GB image floating around that's from MM > N not the smaller update from DP5 > N

there is a guy with his own thread of it, but i con't find it anymore but the link to the file is here - https://android.googleapis.com/pack.../47ceb0f81a49e6866428f9996f8212aba8c29fbe.zip

ADB sideload this and apply as normal
[Nexus 6P Q&A, Help & Troubleshooting] indian84:
I tried this a couple of days back. No luck..
[Nexus 6P Q&A, Help & Troubleshooting] roan.util:
I have the same problems here. I flashed my own AOSP build. Didn't work. Flashed back to factory stock M, let it upgrade to N, did a nandroid, tried a new AOSP build, worked but wasn't happy, tried restoring from that factory N nandroid. That's when everything went south. Haven't been able to recover no matter what I try flashing.

Just called Google. I explained it all and they didn't even have my try anything. They said it sounded like I tried everything they would have me do. So a replacement is on the way.
[Nexus 6P Q&A, Help & Troubleshooting] fezzy102:
who did you call at google? got a number?

---------- Post added at 04:32 PM ---------- Previous post was at 04:19 PM ----------

who did you call at google? got a number?
[Nexus 6P Q&A, Help & Troubleshooting] roan.util:
Correction: I had them call me. Just googled "nexus technical support". First link is for Google support and I requested they call me.
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
User [MENTION=4905158]bogomil4e[/MENTION] posted this in another thread.
[Nexus 6P Q&A, Help & Troubleshooting] bogomil4e:
Yep :D. I posted it everywhere including here. our goal was to obviously alert as much people and fix as many devices at once as possible so Spread the word!
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
Did you already post it in this thread? I didn't see it.
[Nexus 6P Q&A, Help & Troubleshooting] roan.util:
Yea, that fixed mine. Thanks for posting that, [MENTION=5357445]defcondev[/MENTION]. Also, thanks [MENTION=4905158]bogomil4e[/MENTION] for the fix.
[Nexus 6P Q&A, Help & Troubleshooting] halocorn:
This worked for me. Thanks didn't have to RMA my phone :good:
[Nexus 6P Q&A, Help & Troubleshooting] rbouza1:
I posted last Friday to restore efs with earlier backup with with older twrp and like one person tried
[Nexus 6P Q&A, Help & Troubleshooting] Galrash:
Did you buy your phone directly from the google play store? I'm worried that if I am not able to fix it myself I'll be out of luck since I bought mine from Best Buy,
[Nexus 6P Q&A, Help & Troubleshooting] toadths:
My method to fix was as follows (prior phone state was bootlooping on a factory image of DP5):

1. Follow these instructions http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/

Assuming you have adb/fastboot set up start from step 8 and include the command

$ fastboot erase vendor

Then follow the instructions down to the end of step 11 (don't forget to flash your vendor)

2. Open up a command prompt and execute the adb commands specified in previous posts to rewrite EFS

3. Restored factory image previously used one more time for the hell of it using batch file

4. PROFIT?!

I don't think it's necessary to use DP5 guys that's just the one I had handy at the time.
[Nexus 6P Q&A, Help & Troubleshooting] SlimSnoopOS:
What does that tell you? A lot of people don't even HAVE a backup to restore to. From the sound of it, this dd method is zeroing the EFS location for them and generating on boot?
[Nexus 6P Q&A, Help & Troubleshooting] Polgi21:
This work for me, Thank you very much this is a life saver :D hahahaha
[Nexus 6P Q&A, Help & Troubleshooting] rbouza1:
Rule of Android flashing , make backups for backup
[Nexus 6P Q&A, Help & Troubleshooting] Nowak4G:
She's alive again!!!!! Nice, so happy!!!
[Nexus 6P Q&A, Help & Troubleshooting] Train88:
I don't believe that really has to do with it, as I gave a friend the nandroid I had from MMB29P and he was still stuck. He tried the adb commands and got it to boot. I think this comes down to people just flashing the different parts of the factory image, instead of using the flash-all script that wipes the entire device.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
There were a few users that only needed backups to get their device running. Whether it was their own, or another's. Mine for example got screwy from trying to fix a system bug in miui 8. I had a full backup, efs included. I needed to run the adb commands though. Flashing over wouldn't cut it.
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
It was clarified that TWRP caused the issue due to a missing file name set bug during the restoration process;

From [MENTION=5672995]jcadduono[/MENTION] in the announcement thread:

..It would restore the EFS data for modemst1 to both modemst1 & modemst2.

"Snapdragon modem firmware is usually smart enough to regenerate from scratch ex. zeros, but panics on random data"
[Nexus 6P Q&A, Help & Troubleshooting] chevycam94:
When I got my replacement 6P, I immediately made a FULL backup using TWRP 3.0.2-0 (EVERY option selected, and NOT compressed). MMB29Q was what it had when it arrived on my desk. I took that backup, and burned it to a DVD, as well as made a copy on two external hard drives. Im NOT going to lose it! That is my safety net. Made with the proper (known working TWRP), and BEFORE I had changed ANYTHING (besides flashing TWRP of course).

If your planning on flashing up to N, be sure to make a backup THAT way, BEFORE you move forward. Dont expect a second chance to just jump in your lap. Prepare yourself....
[Nexus 6P Q&A, Help & Troubleshooting] Train88:
After rereading what he said, I realize I misunderstood at first - multitasking problems ha.

My nandroid of stock MMB29P is from January, so it makes sense why I was able to boot up again. But at the same time my nandroid was not enough to save my friend's 6P; he did the adb commands in addition to restoring my nandroid after flashing the MMB29P factory image to get his revived.
[Nexus 6P Q&A, Help & Troubleshooting] godzulu:
When I run the following adb commands that were posted, i get - error: device not found

ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384

and

ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384

I have no idea what to do???? I even tried loading stock from wug, that seems to go alright but t still bootloops. Went directly rebooting into bootloader and running adb commands and i get the error. And for what its worth, i know my 6p was not in developer mode when this all started last week - reverting from nougat to MM.

Help is appreciated, thanks. Using a spare OnePlus 2 at the moment and I dont dig it :)
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
Run the adb commands while booted into TWRP
[Nexus 6P Q&A, Help & Troubleshooting] godzulu:
OMG, back flip, high five!!!! That worked! woohoo Thank you all!!!!
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
Haha glad to hear.

Quick question, did Huawei refuse to fix your phone because you shipped it to them with an unlocked bootloader? Did they mention?

Thanks
[Nexus 6P Q&A, Help & Troubleshooting] Tomv5314:
I would like to know also cause Mine got to the service center today flashed stock and relocked it. I
[Nexus 6P Q&A, Help & Troubleshooting] godzulu:
They didnt fix it, just shipped it back
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
Did they say why?

I think they have to give a reason for denying warranty service.

And they have to prove it was the fault of the user, which leads me to believe it was the fact you sent it in with an unlocked bootloader.
[Nexus 6P Q&A, Help & Troubleshooting] godzulu:
No reason, no nothing, nada
[Nexus 6P Q&A, Help & Troubleshooting] Tomv5314:
This is not a good sign for those of us who sent our phones back to Huawei right before the fix came out. They received mine today. I also relocked mine so I am also concerned that I get mine back unfixed and will not be able to unlock it again to do the fix.
[Nexus 6P Q&A, Help & Troubleshooting] godzulu:
I dont think I'd be worried. I just forgot to re-lock it. Understandable for as many times I flashed and reflashed, adb'd my a$* off trying trying to fix it. Im sure they will fix it and send it back, mate. Again, Im grateful to those who came up with a fix!!
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
I read that another user was able to unlock the bootloader again, since the device wasn't able to boot and catch/register the "enable OEM unlock" flag.
[Nexus 6P Q&A, Help & Troubleshooting] roan.util:
I don't understand why re-locking the bootloader would be an issue. You can just re-unlock in bootloader. Which this bug doesn't effect access to the bootloader.
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
Yes but when you flash back stock, "enable OEM unlock" isn't activated in dev options, as required to unlock the bootloader.

And you have to be able to boot into the ROM to activate it.
[Nexus 6P Q&A, Help & Troubleshooting] roan.util:
I guess it's been a while, but I don't remember allowing unlock from Android before doing it in recovery. If that's the case, yea that could really mess you up.
[Nexus 6P Q&A, Help & Troubleshooting] :
Permanently kill device
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
It was only introduced in android 5.0, and even then not all devices have it.
[Nexus 6P Q&A, Help & Troubleshooting] roan.util:
I see. So that's only on my Nexus 6 and 6P. And I only would have done it once the day I got them. That's definitely pushing the abilities of my memory.
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
Haha right on.

Even if I get a bricked phone back, I'll probably buy another 6p.

I had given my wife my Moto X Style, so I'm typing this from me second backup Moto X 2014 PE.

This tiny screen is driving me insane now.
[Nexus 6P Q&A, Help & Troubleshooting] henrybravo:
Just a heads up for those that have been monitoring this thread like me, and ready for the impending disaster when flashing from N back to M. I've been running WETA ROM (Nougat) with the N bootloader/radio for the last several days. I decided today to flash back to Pure Nexus (Marshmallow). I was prepared for the worst and was ready to fix the impending bootloop via the most recent methods listed in this thread. But all I did was flash the MTC20F stock image (using flash-all.bat) and my phone booted right up into M with no problems. Then I flashed TWRP and the latest Pure Nexus and it booted up with no issues.
[Nexus 6P Q&A, Help & Troubleshooting] roan.util:
It's my understanding (and experience) that the issues are related to restoring from backup with the latest twrp for angler. Flashing back and forth between M and N shouldn't result in the issues described here.