[Nexus 6P General] m1xmstr:
How to:Manual OFFICIAL Android Update(s) WITHOUT losing data with custom recovery, and/or root {Works with TWRP, root#, etc}

### Below is the procedure I use monthly, it works perfectly, and is running 100% as of 01/25/2017 ###

### I make no warranties regarding your choice of using these instructions. If you lose data, BRICK or break your phone, it is YOUR fault... ###

### You are responsible for what you do/don't do ###

Current Setup:

Nexus 6P 128GB

Android 7.1.1

Build NMF26F (December 2016 update/security update) https://developers.google.com/android/images

TWRP recovery 3.0.3-0 https://dl.twrp.me/angler/

root access (SuperSU v2.79) http://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

If you're like me, you get the monthly security update (26MB on average) to download/install. The problem is if you are running TWRP to have the ability to flash SuperSu (root access) this security update fails...

*As of 12/20/2016 even my paid Flashify app cannot perform this update successfully... :(

First (Assuming you already have the Bootloader unlocked "Google/XDA is your friend", and USB debugging enabled in developer options):

*Download the latest TWRP recovery from the link above... (At the time of writing this 3.0.3-0 was current 12/20/2016)

*Download the latest SuperSU version from the link above... (At the time of writing this v2.79 was current 12/20/2016)

*Download the latest Official Google Android Build (It's large usually 1.3GB) https://developers.google.com/android/images

Unzip the latest Build to a folder on your Windows machine(Use WinZip, 7z, or whatever)

Right Click and choose 'edit' on the "flash-all.bat" file inside that folder...

Edit the line that reads:

fastboot -w update image-angler-nbd90x.zip <---- This is the build# it will change each time a new version is released, used as reference...

to

fastboot update image-angler-nbd90x.zip <---- This is the build# it will change each time a new version is released, used as reference...

click 'save' on this file...

#Once saved it's a good idea to edit it again to double check the "-w" has been removed (or else it will wipe all user data on your phone...)

Now on a (Windows PC "WinBlows")

Connect your Nexus 6P to your machine and select File Transfer from the drop down (If it currently says charge only...)

Copy/Paste the latest SuperSU.zip file you downloaded to the root (main) directory of your phone...

In the folder that you saved the flash-all.bat hold down the 'right' "Shift" key, and Right Click your mouse...

Select "open command window here"

Test that you have adb and fastboot installed correctly... (Google is your friend)

Run the following....

adb devices

#Should return output showing your Nexus 6p

adb reboot bootloader

#Should reboot your Nexus 6p into Bootloader mode.

fastboot devices

#Should return output showing your Nexus 6p

flash-all.bat

#Should install the latest build (That you just downloaded, and NOT wipe all your data...)

#This takes some time, once the phone reboots do the following....

### If you just want to be stock you are done... If you'd like TWRP recovery and root access on your device proceed below ###

#Assuming the latest TWRP recovery img is in the same folder/directory that you opened your command prompt in from previous steps...

adb devices

adb reboot bootloader

fastboot devices

fastboot flash recovery twrp-3.0.3-0-angler.img

#Once it says success.

on the phone use the vol keys to select 'recovery' and hit the power button...

#The phone should now be booting into TWRP recovery (Takes a little while 1-2 mins first time...)

#Select modify system files (first time...) say 'yes' by sliding...

Now your Windows computer should show your Nexus 6p again...

Place the SuperSU zip file in the root directory of your Nexus 6p (If you haven't already...)

On the main TWRP Install/Wipe/etc screen...

Click 'install'

Choose the SuperSU zip file

Once finished click "Reboot"

#You may be prompted to 'install TWRP' I would just click don't install since it already is...

The first boot takes longer (duh) and might boot loop 2X

Once the phone boots up, test out the following:

Settings > about device

verify you are on the latest Build and Security Update date...

Verify SuperSU installed correctly...

Root Checker or App that requires root.

All of your files, texts, calls, game settings, should still be perfect.

#UPDATE 01/24/2017#

I experienced a "Bluetooth Audio streaming issue" recently with the current available BUILD N4F26J

#WORK_AROUND#

Unfortunately I had to factory rest, fully wipe {TWRP > Delete Cache, Dalivik Cache, Data, Internal} to make the media play out of my connected device. The problem was that the audio would continuously play out of the phone. Even though the Bluetooth settings were set to play Media, and Phone (both were checked)... This occurred in my car (Honda Link), and with my Sony Bluetooth Headphones [Both of which played perfectly for the last 3+ months.]

I spoke to 'Chaz' at 'Google Android Support' who informed me that they would like my logs. I have yet to receive the email he was going to send.

Chaz also seemed to think that a factory reset was the only solution with this issue. I personally do not believe that to be true, and I am certain that the February Security Patch update will correct the line(s) of code that are wrong.

I am currently still using stock Recovery, BUILD N4F26J, and without root access and for 72+ hours without an issue related to Bluetooth.

I will be switching back to TWRP recovery and then SuperSU to try and recreate the problem.

#UPDATE 01/30/2017#

#Below was sent to my Google/Android contact Ken...#

Attached is a picture of the "lint" that was found in my Nexus 6P headphone jack. While I don't send everyone a picture of this, :) this could have been what was causing the following issue(s).

My phone (Nexus 6P on build N4F26J latest) had the following issue with Bluetooth Audio:

-My phone had previously been working fine, and already paired with the devices I encountered the following issue on my way to work.

2015 Honda Civic EX-L "Honda Link"

-Nexus 6P has been connected since day 1.

-Honda Link said "Connected to Nexus 6P"

-Touch screen (in Honda) said the song I was listening to in PLEX.

-I hit the "play" button and music started playing, but out of my phone speakers.

Hmmmm I thought, that is weird. I am a Linux Systems Administrator for PRIVATE and have a very lax schedule (basically get the work done, and either work on something else or Work From Home WFH). Anyhoo, I pulled over and tried the following:

-Shut off the Honda, and opened the drivers door, this killed the power to the radio completely.

-Power Cycled my Nexus 6P (I know it's Linux based, but ya'know...)

-"Forgot" the Bluetooth connection for 'Honda Link'

-Power Cycled my Nexus 6P (Yup just to be sure...)

-Deleted the known connection on the Honda Link screen...

-Shut off the Honda, and opened the drivers door

-Restarted the car, and clicked "Add a phone"

-Accepted the connection request on my Nexus and entered the correct PIN.

-Phone now said connected to Honda Link (Yay!!!)

-Brought back up Plex and connected to my home server.

-Found a song and clicked play...

*Guess where the audio came out of... THE PHONE! exploit deleted... ;)

Ok, hooked up my USB flash drive and jammed out to it on the way to work...

I get to work, and pick up my 'already paired' Sony Bluetooth Headphones. I've used these flawlessly with all Android builds I have tested... I hit the 'play' button and can you guess where Mozart started playing?

That's right out the phone speakers again...

Now I am pulling my hair out (I'm bald so that's a joke).... I decide maybe it's because of one of the following:

-Unlocked Boot-loader (Panic Panic lol )

-TWRP 3.0.0.2 recovery (not stock Android) *#Meant to say 3.0.3-0

-SuperSU beta (Ahhhhh! not a SysAdmin wanting root access~! NO!!! :) )

-Or insert a magnitude of other odd ball things I do to my device(s)...

So, I do the following (at work mind you...):

-Reboot into recovery (TWRP)

-Back-up (full 'Nandroid' backup saved to internal storage. *#No MicroSD card slot DUH!)

-I hit 'Wipe' in TWRP

-I wipe the following:

-Cache

-Dalvik Cache

-Data

-System

(3 X just to make sure)

-I install Cyanogenmod's new release 14.X which I believe is Android 7.1.1

-I fail; due to the fact there is not an official Gapps for 7.1.1

-I perform the wipe again (3 X again)

On my Windows box I do the following from the official build of N4F26J I just downloaded 'flash-all.bat' when my phone is at it's fastboot point...

10-20 mins later and "Bob's your uncle..." my phone works again.

Yay!!! As I try to contain myself at a quiet place of work. I begin the restore process and setting all my user/pass info on my apps that are restoring (I really wish it remembered them, but I could see how that could be a security concern too.)

I Bluetooth connect to my Sony Headphones, and hallelujah my headphones are outputting the music!

I run to my car, and YES it works there too!

*I am thrilled (I fixed something *Yay I know...Not really, but it's all working again.)

So, I decide to tell Android about this in the new support tab on my phone.

Chat? Really? OK...

I basically type in that tiny chat window this email...

hit connect and "Unfortunately Chat has closed"

Now I swear...

I hit Phone in the support tab and in less than a minute Chaz I believe is his name calls my back.

I explain this exhausting thing to him, and he is very very good on the phone. He places me on a brief 12 minute hold. I told Chaz that I would be happy to send my logs if they think it could help other Android users by allowing the developers at Google or Android to find the bug that caused this...

Chaz says "I am sending you the email..." (Never got it, because Google had the wrong email for me... 'JC')

So, I request another call back the next day...

The person called me back (her name escapes me sorry) and again in less than a minute (AWESOME!).

Alright, fast forward to tonight and guess what same issue different Bluetooth (known) device... Music plays out of my phone (Huh, maybe I have a faulty headphone jack I think).

I talk my endoscope out and I can see lint or something in the headphone jack... I use a very small screw driver and a can of compressed air and blow out the headphone jack...

Attached is the picture of the lint. I do NOT know if this was the root cause of my playback issues, but I thought I would still share with you guys that I did this. The music started playing out of the connected Bluetooth device. I am happy to share this as this helped me resolve my issue.

I hope someone finds this useful and can pass it along to others that might be experiencing a similar issue. For fun I hit the 'Phone' support and spoke to 'Kath' (pronounced CAT) tonight she was not super duper excited to hear this whole story. I told her that the reason she couldn't find history of my 2 recent calls was due to the fact that ya'll had the wrong email address on file for me.

If this helps, or needs revision please reach out to me.

Thanks,

M1xMstr

Please 'hit' THANKS if this helped at all...

{My email address was here... Removed for spam issues...}.

Below is the link to the picture I attached to the Google Support email (The image is also an attachment here too...):

https://goo.gl/photos/L3WQLB7vFUXpFdZCA