yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] Nebul0us:
Yes. I did a nandroid restore on a replacement device. After that I would get a message when the system would start saying the device is damaged. I also could not get the fingerprint sensor to work. So I flashed the latest factory images but kept TWRP. It got stuck on animation screen and would not boot. Tried several times. So I flashed the stock recovery along with the rest 7.1.1 factory images. Now it just flickers the dead Android then black screen the loop again...
[Nexus 6P General] jhs39:
Did you try flashing the complete factory image using flash-all.bat command?
[Nexus 6P General] Nebul0us:
Wow. I don't usually to preserve my data but didn't mind in this case. Worked. Thank you!
[Nexus 6P General] brasewel:
So I tried updating my phone using the adb commands from N4F26U (7.1.1) to N2G47O (7.1.2) and it seems like my phone is stuck in the animation step after rebooting the phone. Phone was unlocked and rooted before I updated.

Update:

I installed TWRP, and got a "Failed to Mount Cache (Invalid Argument)" error. I had to mount the cache partition again and wipe it to fix the issue.
[Nexus 6P General] 5.1:
Hello,

Latest 7.1.2 broke TWRP and Root.

Some people on Pixel device flashed April 7.1.1 bootloader and got out of bootloop, then reflash TWRP and reinstall Root.

Or flash April 7.1.1 bootloader, backup data and flash N2G47O factory image which will wipe everything (except if you remove the -w from the script)

Keep in mind, if you choose the latest solution, you won't have TWRP and Root until Chainfire updates SuperSU or topjohnwu Magisk...

Good luck...
[Nexus 6P General] brasewel:
Thanks, I just updated my comment with what I did to fix this. I'm able to have root and TWRP at this point.
[Nexus 6P General] 5.1:
Hey,

Ah, so the issue is not present on Nexus. Good to know :)

Cheers...
[Nexus 6P General] mobileman88:
It's because there is no cache image in the new factory images
[Nexus 6P General] dratsablive:
There was a cache file in the image I downloaded.
[Nexus 6P General] mobileman88:
Odd. I just checked. No cache.img file
[Nexus 6P General] zer0se7en:
Mine has no cache image too. I used cache.img from 7.1.1. so far so good. Flashed latest TWRP and SR3 SuperSU. Now fully rooted.
[Nexus 6P General] Dr.Tautology:
So I am rooted and have missed a few update patches recently. Can I just flash the most recent factory image, or do I need to do the ones I missed in order?
[Nexus 6P General] SlimSnoopOS:
Flash the most recent factory image. Each factory image contains all the commits, security changes, etc. that have been merged as of their respective release date.
[Nexus 6P General] 5.1:
Hey,

Don't forget to backup important datas. It will wipe the userdata partition.

Cheers...
[Nexus 6P General] dratsablive:
Do you have a file called:

image-angler-n2g47o.zip

If so, the cache image is stored in there.
[Nexus 6P General] mobileman88:
no cache.img file in there. Last I saw it was in 7.1.1
[Nexus 6P General] vil-2:
Hello

I have to RMA my N6P. Wanted to lock the bootloader, did it, but now I have the infamous message that the device is corrupt. But it works fine though. Should I be worried considering the RMA?

How can I remove this annoying message? i think it happened because although I was in stock before locking the BL again, I forgot to unroot the device. I tried to flash factory recovery/vendor etc., but it didn't work. Any idea?
[Nexus 6P General] 5.1:
Hello,

Go in developer option and enable own unlocking again. Reboot to bootloader and unlock the bootloader again.

Download a factory image and extract it in your platform-tools folder where you have ADB/fastboot. Then run flash-all script. There's "normally" no reason it would fail.

Let me know if you have issues yet...

Good luck...
[Nexus 6P General] vil-2:
OK I just did it, phone rebooted as normal. Should I relock the bootloader now?

edit: well, it did the trick perfectly. Thank you so much!
[Nexus 6P General] 5.1:
Hey,

You're welcome. :)

You installed stock firmware, the phone is clean. Relock the bootloader and disable "OEM unlocking" in developer options if enabled. Done...

Cheers...
[Nexus 6P General] mobileman88:
My bootloader is unlocked, but I have not checked the setting in Developer options for many months, noticed that the "allow bootloader to be unlocked" is set to "No". Strange.
[Nexus 6P General] 5.1:
Hey,

Better keep it that way. Otherwise FRP is inactive. :)

Cheers...
[Nexus 6P General] mobileman88:
What's FRP?
[Nexus 6P General] 5.1:
Hello,

Factory reset protection.

Cheers...
[Nexus 6P General] dratsablive:
I stand corrected, I don't have a new cache file. I must have been looking at an older one.
[Nexus 6P General] arty93:
I want to upgrade from 6.0.1 to this. Other than flashing the latest vendor, rom and gapp, is there anything else i need to flash?
[Nexus 6P General] 5.1:
Hello,

What means "to this"

Do you want to update stock firmware? Custom ROM? There are several possible scenarios depending your goal.

Cheers...
[Nexus 6P General] arty93:
I want to upgrade to the latest ressurection remix rom.
[Nexus 6P General] 5.1:
Hello,

I'd flash bootloader, since 6.0.1 is really old with fastboot. And appropriate vendor with either fastboot or TWRP.. Radio is optional.

Use a recent/latest TWRP as well. Older versions are incompatible with Android 7.x

And just follow the ROM thread for install instructions in the first post :good:

https://xdaforums.com/nexus-6p/development/rom-resurrection-remix-t3507061

Good luck...
[Nexus 6P General] Rashad83:
[MENTION=4153349]Heisenberg[/MENTION], please adjust Guide No.11. Clearly erasing the cache step without even flashing cache causes issues too.

I have followed the steps to the letter and avoided flashing the cache but i did the step before it which is erasing the cache still even with that i was stuck on the first boot up animation(I have tried this 2 times now, and have waited for > 10min but still was stuck). The way i overcome this is by installing TWRP and wiping cache and dalvik. I got a red notification when i tried to wipe clearly the cache was corrupted.

What i haven't tried is following the guide but without erasing the cache, someone needs to confirm whether if we have to overlook the erase and flash cache all together in future updates.

Thank you again for your work. Best of luck to all.
[Nexus 6P General] 5.1:
Hey,

Next time you update, simply don't erase cache and see if it works. And report back... :good:

If it fails, boot TWRP and wipe it.

Cheers...
[Nexus 6P General] Rashad83:
Hi, hehe maybe someone else will find out soon i had an enough dose of flashing for today:crying:. By the way i came from march update 7.1.1 and just wanted to share my experience so no one goes through the trouble.
[Nexus 6P General] g_oral:
hi guys i wanted to return to stock so i did it everything like in first hisenberg post. i got bootloop and i couldn't go to rrcovery mode. i fastboot twrp and now i have lstest stock android, twrp and no root.

i want my google pay working so i need to lovk bootloader. propably i need to remove twrp. how to do it and get stock bootloader

or there is another way to use android pay and snapchat
[Nexus 6P General] 5.1:
Hello,

Just:

fastboot flash recovery recovery.img

From your factory image.

Lock your bootloader only if you are 100% sure everything is fine.

Or you could try installing a custom Kernel. It will kind of hide your unlocked bootloader.. Most of them are patched and shouldn't trigger AP or safety net.

Good luck...
[Nexus 6P General] g_oral:
tkank you mate, there is one problem in the zip package with original android there is recovery.img and i was fastbooting when i was going back to stock and then i got that boot loop, so i fastbootet twrp then

is it posible that recovery.img from google is corupted?
[Nexus 6P General] 5.1:
Hey,

When you got into bootloop, you did fastboot flash TWRP right?

And it booted right away? Or did you wipe cache, data (without internal storage) and dalvik/art cache? And then booted with TWRP installed?

Seems strange that TWRP flash is the only step that allowed you to boot...

Good luck..
[Nexus 6P General] g_oral:
so i was everything like in first post to go back to stock (newest angler for may)

i got bootloop, there was android loading animation, and when i tried to go to recovery mode, the lying android screen flashed and i coudnt do anything

so then i downloaded twrp, fastbooted it and recovery started to work. i wiped everything via twrp and then android booted
[Nexus 6P General] 5.1:
Hey,

Ok. Just flash stock recovery and you should be good to go.

Most likely old data made your device looping. Since you wiped, I don't see any reason it wouldn't boot with stock recovery... :good:

Cheers...
[Nexus 6P General] g_oral:
thank you i will do it later :)
[Nexus 6P General] nahuelarg86:
Ok, so I had the exact same issue as g_oral, and I found where the problem lies.

What happened to me was I was following the steps from Heisenberg to the letter to flash a stock image, go back to factory, and lock the bootloader. However, when I was done flashing everything, I would try to boot into recovery and it would "bootloop" with the "resting android" icon blinking. That would be, the phone would not boot into recovery. I could go back to fastboot, I reflashed everything again and nothing... Then, I flashed TWRP again (as did g_oral) and I was able to enter into that recovery. I then rebooted the phone without doing anything else, and it would get stuck in the little colorful dots of google and not boot. I then booted back into TWRP and wiped the cache/dalvik partitions and rebooted. BINGO! I was able to boot into the system again. So then I went back and re-flashed stock recovery and FINALLY I was able to get into stock recovery, lock bootleader and be done.

The problem is in the step of "fastboot erase cache". That somehow currupts the cache or something. IT SHOULD BE DELETED FROM THE STEP-BY-STEP GUIDE.

Tl;dr

Do not follow the erase cache command in the guide!!
[Nexus 6P General] Heisenberg:
Did you not read the this very clear line under that command?

Above command unnecessary on 7.1.2 and above

The erase cache command

does not

need to be removed from the guide, it is still relevant to every build before 7.1.2. What

does need to happen

is people (read: you) actually reading what I've written and following the instructions properly.
[Nexus 6P General] nahuelarg86:
Hey man, no need to get all fussy, I was just trying to help other that might have accidentally misinterpreted the instructions. I did read up and down the guide about 10 times before doing anything (because I am that type of person that needs to be sure what I'm doing). I guess I interpreted the "unnecessary" as "not necessary", as if "you don't have to do it, but it's not bad if you do it." Perhaps if you change the wording, or make a note that it will kinda break the process if you do it on 7.1.2 would be better. Anyways man, just trying to help here. This confusion may happen again in the future with other people. Have a good one :good:
[Nexus 6P General] Alcor1us:
This whole erase cache or not topic is kind of pointless. I was and am flashing stock and custom roms on a regular basis (at least 20x over the past few weeks if not more and i always revert back to stock before flashing another custom rom) and no matter if 7.1.1 or 7.1.2, erasing cache never resulted in any kind of issue on my device. (But i admit, i have never tried booting into stock recovery as i do not see any reason to do so; if you want to mess around in recovery, twrp is better anyway) It boots fine, so either my device is somehow special or the issue lies in something else.
[Nexus 6P General] ftarules:
What kernel should be flashed to hide unlocked boot loader?
[Nexus 6P General] Einwod:
Nothing hides the message if bootloader unlocked. Only relock in ON COMPLETE STOCK is recommended.
[Nexus 6P General] Debuffer:
My nexus 6p doesn't receive any cellular network signal.

I tried all the software fixes over XDA:

Flashing factory image

Hard reseting

Installing a February factory image

flashing 6.0.1 PureNexus to get automatic band selection

Put a tape on the SIM card (the device wasn't recognizing it before, now it only won't get any cellular signal)

Flashing baseband, radio and vendor again

Etc...

The device recognizes my SIM. The mobile network keeps at "No Service | Vivo" (vivo is my carrier).

Someone please have a fix for it?
[Nexus 6P General] amith007:
I am also facing the exact same issue. I also did wipe the cache and I was in 7.1.2(thinking that it will do no harm). But the major problem that I have is that my device is not detected in Fastboot. I can boot into bootloader, but when I fire fastboot devices, I don't see my device there. Hence I am not able to re-flash TWRP or any other images. Any help?

Edit: my device showed up in fastboot after I kept it switched off for a while. Then I was able to flash TWRP and wipe the caches. Now am happily running Android O beta.
[Nexus 6P General] Stbrightman:
i could really use some help; I was on a January build of PureNexus (7.1.1) and I went to update tonight and i am stuck at Google logo after trying to install latest 7.2. First mistake i made was not updating my vendor image first because I didn't think it was necessary, but upon reboot after install of zip i got vendor img messages. I made a backup AFTER i disabled lockscreen security, and when i flashed the backup, i am prompted for pin- which of course doesn't work. I can boot into TWRP as well as Bootloader and ADB is working.. My question is am i fcuked and if not, how do i sideload the latest PureNexus, vendor img, etc to get back to good?

Edit- ok i got it back. was able to get latest vendor img and rom onto root, re-installed and it took it. love that rush.
[Nexus 6P General] Homeboy76:
Cheat Sheet for Flashing Android 7.1.2 (based on #9 of [GUIDE] Unlock/Root/Flash for Nexus 6P by Heisenberg)

Boot into TWRP recovery and enter the wipe menu, select advanced wipe, check only the

data box

and swipe to wipe.

Put device/phone in Bootloader mode, connect it to PC, open Command Prompt (see Guide).

Cut and Paste the following to Command Prompt and Press Enter:

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

fastboot reboot-bootloader

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

fastboot reboot-bootloader

fastboot erase cache

(above command is unnecessary on Android 7.1.2 and above)

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

(above command is unnecessary on Android 7.1.2 and above)

fastboot flash boot C:\path\boot.img

fastboot flash recovery C:\path\recovery.img

fastboot flash system C:\path\system.img

fastboot flash vendor C:\path\vendor.img

flash recovery C:\path\twrp-3.1.1-0-angler.img

Disconnect device/phone from PC.

Use the volume keys to scroll, select Recovery Mode and the press the power key.

When the phone has booted into Recovery/TWRP install SuperSu/Magisk for root.

SuperSU-v2.79-SR3.

Press Install and navigate to the folder where SuperSU-v2.79-SR3.zip is located

Select it

Swipe to install

After, SuperSU-v2.79-SR3.zip is installed Select Wipe Caches. On 7.1.2 and above you'll also need to boot into TWRP recovery and

wipe cache and dalvik cache.

Swipe to Wipe

Reboot System

Magisk - Note: Some hiccups with Titanium Backup.

Press Install and navigate to the folder where Magisk-v12.0.zip is located

Select it

Swipe to install

After, Magisk is installed Select Wipe Caches. On 7.1.2 and above you'll also need to boot into TWRP recovery and

wipe cache and dalvik cache.

Swipe to Wipe

Reboot System

After, reboot go here - (Get Magisk Manager through XDA LABS - near the bottom after article ) and get the Magisk Manager App and install it.

Open Magisk click Menu (Top left corner), click Settings, Turn on Hide and Turn off BusyBox.

Reboot System

Done
[Nexus 6P General] cmousseau:
I have myself in a bit of a jam here. I followed the guide, as far as I know correctly, but my phone is stuck with the "Google" logo in white and will not turn on past that point. I can access the bootloader.

I never actually achieved root, I unlocked my phone, got to TWRP, and installed SuperSU through TWRP. After that my phone did fully boot, but there was no root. I decided to try the process again, same thing no root. So I decided to use TWRP to recover back to my backup. From this point forward I have been stuck at the Google logo. I have tried factory reset, using TWRP to wipe, reset, anything I can think of. Nothing is fixing this.

Edit: After a few failed attempts I was able to flash to a factory image successfully. I am going to try rooting again later.
[Nexus 6P General] Homeboy76:
You followed the instructions in the guide for #1,2, and 6?

What version of TWRP and SuperSU did you use?

Marshmallow or Nougat?

Nougat 7.1.1 or 7.1.2?
[Nexus 6P General] cmousseau:
Yes I followed 1, 2, and 6 and as far as I can tell I did it all exactly. I am on 7.1.2 and used TWRP angler 3.1.1 and SuperSU 2.81.

As I do it everything looks like it should, and SuperSU seems to install correctly through TWRP, but when the phone comes back on and I check to see if I have root I do not.
[Nexus 6P General] dwh2o13:
Try using SuperSu v2.79 SR3 instead of 2.81. Start over with a clean install
[Nexus 6P General] Spannaa:
Try flashing SuperSU v2.79 - v2.81 had been reported as buggy on some devices.
[Nexus 6P General] Franglestine:
So I tried following the instructions on this but using the newest version of TWRP and now it only sits on the boot screen. I've gone back in after the root/TWRP flash and cleared the cache but it still sits here. Any ideas?

-RESOLVED-
[Nexus 6P General] FreeRusMan:
hi! I want to ask about bootlooped N6P when there is no access to recovery, did someone find solution for this?

Thanks!
[Nexus 6P General] tjg_marantz:
So I had gone from O to PN and had the rotation issues. Reading through, problem was obvious. I flashed the stock 6.0 image. Booted up fine. Opened youtube to be safe and sure enough, video will go full screen on rotation etc... Everything fine.

Followed the instructions to install PN once again (same steps I did last time from O) but now I am stuck at the google logo for about 30 minutes. I'm thinking this is not normal. Any thoughts as to next steps I could try? Do I go back into twrp and erase dalvich/cache/data/etc... and resintall pn, gapps, vendor and su? Or is this timeframe still within norms?

Thanks!
[Nexus 6P General] Spannaa:
Why the stock 6.0 image? The bootloader & vendor won't be compatible with the latest PN

Use the latest 7.1.2 (N2G47O, May 2017) images and do a full factory reset via the phone > settings (this will wipe your internal storage too, so backup anything you want to keep first).
[Nexus 6P General] cooperkid:
Ok All, i need help....

My phone was stock and began to give me a bootloop issue.

Randomly switching off, followed by bootloop and eventually loading up for a short time before crashing and going into bootloop....

I went to the bootloader and thought I could reset via recovery. However everytime i choose recovery the phone would reboot back to the “Google” screen and the same issue would repeat…..no recovery?

OK I bid my time and waited for it to boot up properly, I went into the settings, enabled usb debugging and unlock bootloader.

I used fastboot to unlock the bootloader and flash a recovery…

Nada still the same issue “choose recovery the phone would reboot back to the “Google” screen….”

In Fastboot the phone seems to be writing new recoverys but regardless of using TWRP or stock recovery I cannot bot into recovery….

Any help on this one?

I haven’t had to do this in a while so I may be missing a trick but even following the guides on here don seem to be helping me…
[Nexus 6P General] MichPRich:
Ok, I've used this guide multiple times now since I got my 6p rooted more than a year ago. It's definitely THE essential guide for 6P users. So, that is my sincere thank you to [MENTION=4153349]Heisenberg[/MENTION] for your hard work and continued support itt.

Now, my question is a simple one I just want to make sure it's clear enough to get relevant answer(s)

I am currently on 7.1.2., rooted, superSU, custom rom (aokp), twrp 3.1.0.0

I am still running with the 3.64 bootloader, and 3.78 radio, both of which, I believe, are a bit overdue to be updated (to 3.68 and 3.81 respectively).

If all I really want to do is flash the newer radio and boot loader,

(A) do I need to use fastboot (it's not a case of lazy, i'm sitting at my pc as i write this with my SDK updated and everything set, but lately flashing stuff gives me pause with all googles updates changing things etc..) or can I use TWRP (or flashify, or other)?

(B) If fastboot is the only way, am i able to use the guide as written but with the non-applicable commands omitted?

(C) TWRP 3.1 has been smooth for me, any reason I need to update to 3.1.1.0? I was one of the casualties of the pin-code-restore-brick bug, which is basically why I'm here, asking questions first..
[Nexus 6P General] Heisenberg:
A) Yes, fastboot is the only way.

B) Yes, you can issue only the relevant commands and omit all the others (do a "fastboot reboot-bootloader" between each one though).

C) I can't fully answer this one as I am yet to update to the latest version myself. However, as far as I know there isn't anything new around that makes the latest version absolutely necessary.
[Nexus 6P General] Badger50:
You can also flash the bootloader and radio with TWRP if they are in .zip format. Flipz makes theses for our 6P's. While I have always used fastboot tl flash these as Mr. Heisenberg has said, I've also never read any negative effects from flashing the .zip format ones. You can find them here if you'd like to try :good:

https://www.androidfilehost.com/?fid=889764386195905636
[Nexus 6P General] byproxy:
so the latest update of windows 10 sort of jacked up adb commands. instead of the normal (old style) command prompt a shift+right click opens some dumb "windows powershell". now instead of being able to simply type adb commands you have to put a .\ in front of everything. so like ".\fastboot reboot"

the commands still work... you just have to add that stupid .\ in front of everything. super annoying.

if there's a fix or work around i'd love to know. otherwise, be advised if you have issues.
[Nexus 6P General] CyberZeus1977:
Yes, you have to change settings of the Start Menu turning off "show powershell instead of command prompt" (I don't know the exact words, my Windows 10 is in Italian). This way you will have your command prompt back all-over Windows 10.

Tell me if you sorted it out.

Sent from Enterprise bridge
[Nexus 6P General] dwh2o13:
I think you can just open the directory containing your SDK files, then type cmd in the address bar of the directory to open a command prompt window as usual. I've been able to test adb and fastboot connections successfully at that point.
[Nexus 6P General] MichPRich:
Thank you both for these prompt responses. Both were very helpful to me and much appreciated.
[Nexus 6P General] archibold23:
Hey guys

Sorry if this has already been addressed, there an awful number of comments to search through here :p

I followed this guid some time ago to root my nexus, and it worked perfectly. However i found having to manually install OTA updates annoying, and I wasn't really using root features so I removed it using this basic guide (androidexplained.com/nexus-6p-unroot)

SuperSu no longer detects a root, but I'm still currently unable to install OTA updates. The patch will dowload but when installing on the bios screen i get 'Error!' with the android logo.

Does anyone know what I might have missed that could be causing this?

many thanks in advance
[Nexus 6P General] Einwod:
Do you have a custom recovery installed or the standard Nexus android recovery?
[Nexus 6P General] archibold23:
Well I installed TWRP as part of the initial root, but I dont believe its there/accessable because if i enter recovery mode I get "No Command" with the android logo