yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
Turns out, flashing back with 3.0.2-0 from N to MM custom ROM works just fine, no need to piss about with flashing factory images ( I did this fine with a NON-ENCRYPTED device ), you can freely go from MM to N and back to MM with zero issues.

I don't know where this stuff came from about downgrading, just people who changed TWRP versions and then attempted to restore their back ups with the dodgy TWRP builds had this issue.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Yes that's what I'm saying. People were getting crazy with restoring MM right on top of N using v-1.

Oh I just saw your post again, you were flashing not restoring, my bad. I've done it on 3.0.2-0 multiple times and also 3.0.2-2.

The only thing that needs to be changed is the vendor.
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
No worries man, yeah I try not to rely on backups from between recovery versions, if I'm updating TWRP I usually move the old one to my PC and make a new one under the new recovery and store than on my device.

Hindsight is a wonderful thing, but I think half of this **** storm was whipped up because people where jumping versions and blindly trying several combinations.

I feel sorry for those who screwed their device because they thought that N > MM downgrade was causing the issues because they restored an old backup with a broken TWRP build, i bet flashing factory images over and over and vendors and everything under the sun just made things worse.

I guess we all now know to not jump on updates as soon as they land !
[Nexus 6P Q&A, Help & Troubleshooting] frost_nz:
7.0 factory image is finally up ;)
[Nexus 6P Q&A, Help & Troubleshooting] republicano:
Bootloader - 3.58

Baseband - 3.72

Variant - VN1

CPU - 0x20001

eMMC: 64GB Samsung

DRAM: 3072 HYNIX LPDDR4

Console - NULL

Qfuse status - Enabled

Download Mode - Disabled

Manufacture data - 10-17-2015

I had issues with the recovery.img in the latest 7.0 build, the image in recovery would flash every couple of seconds and i couldnt trigger the power+vol up commands to wipe device so i was stuck in a bootloop, i had to flash recovery.img from the last Android M build to boot into android n, then i flashed 7.0 recovery.img and now its all working
[Nexus 6P Q&A, Help & Troubleshooting] nuprotocol:
Bootloader - 3.58

Baseband - 3.72

Variant - VN2

CPU - 0x20001

eMMC: 32GB Samsung

DRAM: 3072 SAMSUNG LPDDR4

Console - NULL

Battery - OK

Device is LOCKED.

Qfuse status - Enabled

Off-mode-charge: ENABLED

Download Mode - Disabled

Phone is not locked and comptelely stock. Was running Android 7.0 for a week then the phone froze on me. I powered back on and now its stuck in a boot loop. Can't boot into Recovery. Recovery is stock. Is there any options to unbrick? I have Nexus Root Toolkit and Unified Android Toolkit. Any help would be greatly appreciated.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Can you get into stock recovery?

Either wipe data in that, or fastboot flash your device.

Otherwise you might need to RMA
[Nexus 6P Q&A, Help & Troubleshooting] cptngoju:
Still bricked after several attempts

Bootloader - 3.58

Baseband - 3.72

Variant - ANGLER-VN2

CPU - MSM8994 0x20001

EMMC - 64GB Toshiba

DRAM - 3072MB Samsung LPDDR4

Console - Null

Qfuse status - Enabled

Download Mode - Disabled

Manufacture date - 03-23-2016

Brief description of where the bootlooping started - My device has an unlocked bootloader, was stock on MTC20F, unrooted. I joined the beta program once 7.0 stable was made available & immediately received the update. Had it for several days with no issues & the following happened: I was replying to a message in Hangouts (which had been crashing considerably more after updating to Nougat than it had previously), when my phone froze for 15 seconds & rebooted. As it rebooted, it was displaying the Android boot animation in slow motion. It then went back to the unlocked bootloader warning. After that it gets stuck at the Google logo. Sometimes it will go back to the bootloader warning screen, sometimes the screen will just flash off & go straight to the Google logo.

I have not been able to fix my device

I have tried methods - #4, 5, 9, 13, 16
[Nexus 6P Q&A, Help & Troubleshooting] marc.ientilucci:
So are you past saving data at this point and just trying to get the phone on?

Take me through the steps you do when flashing the firmware please.

Have you used any 'fastboot format' commands at all?
[Nexus 6P Q&A, Help & Troubleshooting] cptngoju:
Yes, I'm not worried about saving any data. Unfortunately, I never made a nandroid backup at any point, so I wasn't able to restore.

Usually for simplicity's sake, I use Wugfresh's NRT. I attempted to flash NPD90G, which didn't work, then tried downgrading to MTC20F. I also erased the EFS partitions according to post #2's instructions & reflashed MTC20F. Once NRD90U was available, I erased the EFS partitions again & flashed it. No luck with any of it.

I haven't tried the fastboot format commands yet, I must have missed that post. I will try them next & see what happens.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Are you running the flash-all script when flashing the firmware? Are you using the full factory images?
[Nexus 6P Q&A, Help & Troubleshooting] mewmix:
Literally in the same boat as cptngoju, except I have tried TWRP 3020 and 3022 to no success, stock MM(As in first build) and N(First and Build U), ota zips, flash all and manual flashing, just used fastboot format userdata, etc (except MISC gave me a permission denied once) even though I have wiped the data before

Whats so strange is that it the only time I made any progress was flashing a custom rom (Maple AOSP) the boot cycle seemed to advance beyond google and a basic animation. In this process I've taken the time(of course due to need) to explore all the logging functions provided to try and troubleshoot this myself but I really am hoping that I am simply being lazy or stress induced carelessness in this recovery process. I've conquered many flashing fears these past few days, so am willing to try or do anything to just restore this phone only out of the pure drive if anything, considering I can flash recoverys and execute fastboot / adb / mount storage, and install through so many methods I really feel like this device can be saved.

Thank you so much everyone for your time, efforts, and knowledge!
[Nexus 6P Q&A, Help & Troubleshooting] DJBhardwaj:
A little late to catch up. But have you restored a complete Nandroid (including EFS partition) backup at any point?
[Nexus 6P Q&A, Help & Troubleshooting] mewmix:
I didn't have one, but Jammol kindly and heroically saved my Nexus6p by illuminating my ignorance of what the EFS Partition was, why I needed to wipe and pointed me to (oh irony...) the second post of this thread!

Downloaded factory image from google, Android N BuildU, Booted into TWRP 3020 - ran the two commands in adb shell, reboot.

THANK YOU SO MUCH Jammol! OP! XDA!
[Nexus 6P Q&A, Help & Troubleshooting] cptngoju:
Yes to both of those questions. I used the full images directly from Google.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Try this....

Load the latest twrp.

Do full wipe of everything(backup what you need first)

Format Data (type in Yes)

Reboot to bootloader

Run flash-all script from latest N factory image

Let it try to boot

If it fails(probably will), follow the efs erasing fix in post 2

Now see if it boots

---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------

Glad you got it working now!!! We are all here to help.
[Nexus 6P Q&A, Help & Troubleshooting] cptngoju:
It finally booted (sort of)! I had done all of those steps, just not in exactly the order you specified. Once I was done, it finally went to the loading animation, although it was in extreme slow motion. I left it alone for about 10 minutes & it finally loaded into the welcome screen! Now the bad news. I stepped away for a few minutes leaving it plugged into my computer on the welcome screen. When I came back, it was in a boot loop again. As I type this, it is going through the loading animation again, so we shall see if it ends up going back to the welcome screen.

---------- Post added at 05:43 PM ---------- Previous post was at 05:31 PM ----------

No luck, back to bootlooping. It made it back to the welcome screen one more time, but as soon as I hit get started, it rebooted again.
[Nexus 6P Q&A, Help & Troubleshooting] marc.ientilucci:
Try the following via fastboot for erasing everything and starting from scratch.

NOTE: THE FOLLOWING COMMANDS WILL ERASE EVERYTHING ON YOUR PHONE.

fastboot erase boot

fastboot erase cache

fastboot erase recovery

fastboot erase system

fastboot erase userdata

fastboot flash bootloader [name of your file].img

fastboot reboot-bootloader

fastboot flash radio [name of your file].img

fastboot reboot-bootloader

fastboot flash recovery [name of recovery file].img

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash userdata userdata.img

fastboot flash vendor vendor.img

fastboot flash cache cache.img

fastboot format userdata

fastboot format cache
[Nexus 6P Q&A, Help & Troubleshooting] tyea:
My Nexus 6p behaves the same as yours. I'm thinking of begging Google to replace it since Huawei told me my attempts to fix the phone with factory images is tampering with firmware, which negates their warranty.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
I did it also, called them back said the phone was not flashed and that I side loaded. Then I flashed the factory image and locked it and sent it back. They got a new phone back to me in under 3 weeks.
[Nexus 6P Q&A, Help & Troubleshooting] sirhugh15:
Bricked...Am I doomed?

Hello, I have bricked my Nexus 6P and hope you guys can help me figure this out. I have been searching and reading and trying many things but have had no success. I was running 7.0 and trying to install a custom boot animation. Everything was working splendidly for two weeks prior to that. :eek:

I only have access to Fastboot. I am unable to boot into any recovery, even after successfully flashing various versions of TWRP and stock images. I get an infinite boot loop for 40+ minutes if I try booting the recovery via the bootloader or just rebooting the system.

Things I have tried:

Heisenberg's Factory Image Flash guide for NRD90U, NRD90T, MTC20L

Executing the flash-all.bat for each factory image

Wug's Nexus Toolkit 2.1.9 for each factory image listed above

fastboot erasing boot, cache, recovery, system, and userdata and then trying to flash the above three factory images utilizing each flashing method.

manually flashing twrp-3.0.2-2-angler

manually flashing twrp-3.0.2-3-angler

manually flashing No-Force-Encrypt Boot Image

manually flashing the MTC20L vendor image with the two 7.0 factory images.

Current:

BL: angler-03.54

Baseband: angler-03.61

Product Variant: Angler-VN2

Device is Unlocked

Qfuse Satus: Enabled

Download Mode: Disabled

Again, I believe I only have access to Fastboot. Any suggestions?
[Nexus 6P Q&A, Help & Troubleshooting] silvan g:
Thanks you man! you saved my day big time!
[Nexus 6P Q&A, Help & Troubleshooting] oussamalabbize:
Bootloop

Hello, my Nexus 6P is bricked, here what happend before :

-I was running [Stock+][Nougat-NBD90X]Debloated-Prerooted-Odex-Busybox-Fast & Stable rom, worked like a charm.

-I made a full backup (everything)

-PureNexus nougat was out, so I flashed it, worked well.

-Then, I wanted to try Miui 8 Beta, workerd, not stable enough.

-Boot into Twrp 3.0.2-1, wiped everything except internal storage, restaured my backup === bootloop

-Back to Twrp, wiped everything, copy purenexus rom from my pc, re-flashed === bootloop

-Downloaded latest factory image, followed heisenberg's instruction via fastboot, no error while flashing, === bootloop

-Tried to go to stock recovery, juste the dead android guy, no commands

-Flashed twrp 3.0.2-0 === SURPRISE MOTHA****** only 32go memory!!!! my N6P is the a 64go variant, figured out that I did a wrong command "fastboot format userdata" and I didn't read that "I should never flash userdata" my fault, okay I'm so desesperate that I can leave 32go memory...

-Tried to wipe everything via TWRP === ERROR : couldn't wipe anything...

I can't even send it to repair, I bought it in montreal but I live in algeria.

[MENTION=3745842]tr4nqui1i7y[/MENTION] plz help :) I'm at my office now, I'll send every information once I got home. thx in advance.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
You'll have to use the fastboot erase command for userdata. There's a guide from Heisenberg.

http://xdaforums.com/showpost.php?p=63049067&postcount=4

You may also need to wipe efs. That's done via adb. Follow the unbrick method first.
[Nexus 6P Q&A, Help & Troubleshooting] oussamalabbize:
Thx for your reactivity, I'll try to do that, I'll tell you if it worked or not.
[Nexus 6P Q&A, Help & Troubleshooting] oussamalabbize:
I reflashed latest Twrp 3.0.2-2, the storage got back to 64go.

What do I do now? I flash via fastboot? Stock nougat or stock MM?

Edit : I just made the :

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

Reflashed stock MM, and it's working like a charm again, I love my nexus :D

Thx a lot [MENTION=3745842]tr4nqui1i7y[/MENTION]
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
No problem!
[Nexus 6P Q&A, Help & Troubleshooting] RicardoSul:
Same here in my device.

Occasionally I can bootup the phone in bootloader and tried:

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

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

but nothing happens.

Any suggestions???

---------- Post added at 08:17 PM ---------- Previous post was at 07:56 PM ----------

I also try that... but nothing happens, the phone don't bootup. Any suggestions?
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
We need to know the history of your device. Meaning, what was flashed, how it crashed and what type of crash it is. We also need to know what you have tried.
[Nexus 6P Q&A, Help & Troubleshooting] StarShoot97:
Bootloader - angler-03.54

Baseband - angler-03.61

Variant - ANGLER-ROW-VN1

CPU - MSM8994 0x20001

EMMC - 32GB Toshiba

DRAM - 3072MB HYNIX LPDDR4

Console - NULL

Qfuse status - ENABLED

Download Mode - DISABLED

Manufacture date - 11-12-2015

The phone randomly rebooted while I was using it and since then I am stuck in a bootloop. I can acces the bootloader, but neither fastboot nor ADB are working, I just get errors. Tried many drivers already. Cannot access recovery mode either, it just jumps into a regular reboot when trying to access it. I would just like to somehow pull my App data and Sdcard data, if the phone is dead I can RMA it.

*I have not been able to fix my device*

I have tried methods - none of them are working, as the device is not accepting the fastboot commands

target didn't report max-download-size

sending 'recovery' (13133 KB)...

FAILED (command write failed (Unknown error))

finished. total time: 0.000s

The problem should be the drivers, but I can't figure out what's wrong. Everything is working fine on my N7
[Nexus 6P Q&A, Help & Troubleshooting] RicardoSul:
My device is:

Bootloader - angler-03.61

Baseband - angler-03.72

Variant - ANGLER-VN2

CPU - MSM8994 0x20001

EMMC - 32GB Samsung

DRAM - 3072MB Samsung LPDDR4

Console - NULL

Device is UNLOCKED

Qfuse status - ENABLED

Download Mode - DISABLED

Manufacture date - 10-31-2015

I was running NBD90X but my phone was slow in some apps, then I’ve flashed the factory image NBD90X, twrp-3.0.2-2, and then SuperSU-v2.78 and Franco Kernel r-32, and during the installation of this apps the phone randomly rebooted and I can't access the recovery mode anymore.

Then I tried to do a new factory reset by flashing these factory images: NDB90X, NRD90U, MTC20L, MTC20F, MMB29M, MDA89D, still no success. The method I used was flash-all, they return “OKAYS”, but without success.

The phone randomly reboots and I try to enter in recovery mode. It takes me approximately 20 reboot attempts so that I can get in recovery mode once. Once I'm in recovery mode, I tried to flash ota-nbd90x, ota-nrd90t, recovery nandflash, but everything without success. When I try to recover nandflash in twrp (twrp-3.0.2-0/twrp-3.0.2-2/twrp-3.0.2-3), the phone randomly rebooted and I can't flash it entirely.

I also tried to flash the 6.0.1 vendor.img in 7.0 factory rom, and flash in twrp adb:

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

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

but the phone doesn't boot up.

I bought the phone in the USA, but I'm living in Rio de Janeiro - Brazil and I can’t send the phone to RMA.
[Nexus 6P Q&A, Help & Troubleshooting] istperson:
adb shell is not working in Bootloader mode. For Bootloader mode use fastboot. adb works in booted mode, and in recovery.
[Nexus 6P Q&A, Help & Troubleshooting] RicardoSul:
oops I wrote wrong, I did it in the TWRP.
[Nexus 6P Q&A, Help & Troubleshooting] RicardoSul:
When I ran the commands above, I received the following response:

C:\Users\ricardosul\Desktop\angler\_arquivos>adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
dd: writing '/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1': No space left on device
257+0 records in
256+0 records out
4194304 bytes (4.0MB) copied, 0.007216 seconds, 554.3MB/s

C:\Users\ricardosul\Desktop\angler\_arquivos>adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
dd: writing '/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2': No space left on device
257+0 records in
256+0 records out
4194304 bytes (4.0MB) copied, 0.006987 seconds, 572.5MB/s

Was it correct?
[Nexus 6P Q&A, Help & Troubleshooting] MoistPicklez:
Bricked 6P

Bootloader - angler-03.54

Baseband - angler-03.61

Variant - ANGLER-VN2

CPU - MSM8994 0x20001

EMMC - 32GB Samsung

DRAM - 3072MB SAMSUNG LPDDR4

Console - NULL

Qfuse status - ENABLED.

Download Mode - DISABLED.

Manufacture date - Oct, 31st, 2015 (Ooooo spooky.)

Brief description of where the bootlooping started - After updating to NBD90X, I flashed PureNexus 7.0 and had an enjoyable time with Nougat till last Thursday. I got home from work and noticed my battery was close to dead, plugged 'er in for maybe an hour -- powered down. Then tried to boot back up with no success.

Recovery does not work either

... ( I was last on the unofficial TWRP 3.0.2-3. )

*I have not been able to fix my device*

I have tried methods - Literally every method that didn't involve getting into Recovery or using ADB to sideload an OTA. Every time I attempt flashing a stock image, it is successful, but my 6P still hasn't booted properly, or into Recovery mode since Thursday. I can still get into Bootloader just fine, and flashed about every damn N and MM stock image available, as well as all TWRP versions from 3.0.2-0 to the unofficial 3.0.2-3.

[MENTION=3745842]tr4nqui1i7y[/MENTION] by the way great thread, I appreciate all the methods and the documentation on these issues, as Google and Huawei have both said there's nothing left they can do to help since my bootloader is unlocked and my device was purchased at a Best Buy. Definitely willing to try anything to get this 6P revived. I ended up getting an LG G5 as a replacement, but damn I miss my Nexus... :'(
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Does your device just not react to the power button, or does it boot to a certain point?

If it seems like it isn't reacting to the power button, leave it plugged in for 10 min, then hold the power button down for like 30 seconds.
[Nexus 6P Q&A, Help & Troubleshooting] MoistPicklez:
I guess I should have mentioned the power button works fine and my battery is somewhat charged. (Not sure the exact %.) I had it charging in bootloader mode last night so it would have enough battery to troubleshoot today.

My device only boots to the Google Logo, then hangs shortly, and goes back to the "Your device maybe corrupt" screen, and continues that loop consistently. Same happens with Recovery.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Try out this one.

If you use 6.0.1 use TWRP 3.02-0

for nougat use TWRP 3.0.2-2

Boot phone into TWRP, run these commands. If you can't connect to adb in recovery then toggle mtp. To flash everything I use Wugfresh's tool. Saves a lot of stress when you're looping. So you don't have to type commands a million times.

Enter adb shell then copy and paste these two lines, separately.

adb shell

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

and

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

fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img

fastboot reboot-bootloader

fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img

fastboot reboot-bootloader

fastboot flash boot C:\angler\images\boot.img

fastboot erase cache

fastboot flash cache C:\angler\images\cache.img

fastboot flash recovery C:\angler\images\recovery.img fastboot flash system C:\angler\images\system.img fastboot flash vendor C:\angler\images\vendor.img

fastboot reboot system
[Nexus 6P Q&A, Help & Troubleshooting] MoistPicklez:
Well, no dice.

I was already on MTC20F, tried flashing TWRP 3.0.2-0, ended up in the same bootloop. Then I tried flashing stock MTC20F fresh again in the format you posted above, same TWRP version, same bootloop. I feel like this poor thing is on it's last little bit of life..
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
It's important that you run those adb commands as well
[Nexus 6P Q&A, Help & Troubleshooting] MoistPicklez:
I tried but I cannot issue those commands in my command window it just states "No device found", and because I can't get into Recovery at all, I can't use ADB there...
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Use wugs tool to boot your device into twrp
[Nexus 6P Q&A, Help & Troubleshooting] MoistPicklez:
I can't, Wug's tool just sends me back into a direct bootloop between the warning screen and the Google Logo again. I literally have tried every option in Wug's tool that I can find, but no such luck even reaching Recovery..
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
On the right hand side, under flash stock. Check soft bricked.

Now launch the andvanced tools on the bottom right.

In the center column there is fastboot flash options, on the right there is fastboot boot options.

Fastboot boot into custom recovery.

Then you can run those adb commands. Stay in recovery and report back before moving on.
[Nexus 6P Q&A, Help & Troubleshooting] MoistPicklez:
After following your instructions to a T. I go directly into yet another bootloop. I feel as though my Recovery partition is somehow messed up, but I was also in the beta DP5. ( Beforehand ( Also rooted. )) Not sure if that is to blame or my own actions, but I'm seriously baffled here. I rarely install kernels and other such tweaks and just enjoy a clean well built custom ROM. If you have any other suggestions my kind sir I am more than welcome to test them out since my device is pretty much a door stop at this point anyways.. Thank you though, I really appreciate the help.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
[MENTION=4613660]Jammol[/MENTION] plz. I can't even
[Nexus 6P Q&A, Help & Troubleshooting] MoistPicklez:
Nvm Ill attempt to get this working, again appreciate the insight. Cheers.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
You're good. There's just got to be something miniscule we're over looking. [MENTION=4613660]Jammol[/MENTION] will be able to figure it out.