[GUIDE] Unlock/Root/Flash for Nexus 6P

[efrant]

Perfect ? found it there and deleted it.
This root works to good and moded some files.
What would happen if I did install this 8 mb security update?

It won't install. You need a clean system (i.e., no mods) and most likely the stock boot image and stock recovery.

 

[Kiribbs]

USB Continuously Not Working

[size=+1]Frequently Asked Questions[/size]

1. How do I take an OTA update if I have root or other system modifications on the stock ROM?

The first thing you need to do is remove root and any other system modifications you might have as these will cause an OTA to fail. You also need to revert to the stock recovery if you have TWRP or another custom recovery installed, and the stock boot.img too. To break it down you need to do the following:

• Download factory images for current build (check this by looking at Build Number in Settings>About Phone).
• Extract and flash the system.img, recovery.img, and boot.img.
• Apply the update.

See section 8 of this guide for full details on how to extract and flash components of the factory images.

2. Can I use the modified MDB08K boot.img on other builds?

Yes, the modified MDB08K boot.img can be used with the MDB08K build and all later builds (MDB08L, MDB08M). It cannot be used with the MDA89D build.

So, I keep trying this on multiple computers, and my device will connect to Windows Explorer, but neither adb or fastboot recognizes it. This also occurs with my Nexus 9. What else can I do to check the drivers?

 

[wirelezzz]

Having root doesn't affect whether or not you receive the update notification.

Probably /data/data/com.google.android.gms/app_download/ and its probably called update.zip

It won't install. You need a clean system (i.e., no mods) and most likely the stock boot image and stock recovery.

Thanks. Don't have to worry then.

 

[JSouthern]

So, I keep trying this on multiple computers, and my device will connect to Windows Explorer, but neither adb or fastboot recognizes it. This also occurs with my Nexus 9. What else can I do to check the drivers?

I had trouble with the connectivity even after ensuring usb/adb debugging were enabled in developer options (I also had to google how to enable developer options, lol). I used the above link to manually update the driver and it corrected my issue. Perhaps it will work for you as well.

**EDIT** I'm not allowed to post links. So the best I can tell you is to Google how to manually update your nexus 6p/android usb drivers. There's a site near the top with step-by-step instructions (it's not quite as straightforward as just going to device manager, imo).

Hope this is helpful enough. GL!

 

[mrRobinson]

I know the older kernel boot img's work but that wasn't good enough for me and my nexus finally arrived. so i went ahead and made ones (systemless and normal) from the mdb08m kernel. Most people are requesting this in the supersu thread (and i'm pretty sure others have provided these as well) but I feel those requests and those willing to provide are better served in the device specific forum. This seems like a great thread to provide such images for the nexus6p, of course ultimate decision up to @Heisenberg
Angler MDB08M Modified Boot Img - requires SuperSu 2.50+ (re-uploaded, tested, 11/11)
Angler MDB08M Modified Systemless Boot Img - requires SuperSu 2.56

 

[cruiz1022]

I have a question. This is my first time in these forums but I'm in desperate need of help. I tried rooting using Wugfresh, as I've done this in the past with my N6.

But it didn't work, so I went to flash stock again. And I've been stuck in the Google boot logo for 3 hours now. I tried flashing stock, factory reset on the phone... And I have NO idea what to do. If any one has any input whatsoever and would like to help me out please do so.

Thank you!

 

[zervic]

Okay here's the real question...how can I disable the notifications for the OTA update? If I have to completely start over (i.e. flash back to stock, just to install the update, then re-root and all of that) just for an 8 MB update, I'm not interested...but I'm also not interested in a persistent "system update downloaded" notification.

 

[msick]

solved

 

[Heisenberg]

I have a question. This is my first time in these forums but I'm in desperate need of help. I tried rooting using Wugfresh, as I've done this in the past with my N6.

But it didn't work, so I went to flash stock again. And I've been stuck in the Google boot logo for 3 hours now. I tried flashing stock, factory reset on the phone... And I have NO idea what to do. If any one has any input whatsoever and would like to help me out please do so.

Thank you!

I see you've also posted this in another thread, where you're receiving help. Please don't double-post, it isn't allowed.

 

[Heisenberg]

solved

Instead of editing your post to just say "solved", you should have kept your original post but added what you did to solve the issue. That way if someone else has the same problem the information is there when they search for it.

 

[ckc90745]

need help please

hello everyone, I need help, I just got a 6p as soon as I got it, I boot the phone up and did not take the upgrade, unlock the bootloader and installed twrp 2.8.7.2 I also did a nandroid backup, everything went ok till them, the problem that now my phone wont boot its just stock on the android screen, what did I do wrong, the phone is not even rooted I just installed the recovery, did I brick my phone. I try to restore the back up and it does not work, please help, also I would like to know how can i reinstall the original recovery and lock the oem so I could send the phone back to google

 

[sirxdroid]

hello everyone, I need help, I just got a 6p as soon as I got it, I boot the phone up and did not take the upgrade, unlock the bootloader and installed twrp 2.8.7.2 I also did a nandroid backup, everything went ok till them, the problem that now my phone wont boot its just stock on the android screen, what did I do wrong, the phone is not even rooted I just installed the recovery, did I brick my phone. I try to restore the back up and it does not work, please help, also I would like to know how can i reinstall the original recovery and lock the oem so I could send the phone back to google

I doubt your phone is bricked. Download the MDB08M stock image from Google and flash it using the flash-all script in the file:
https://developers.google.com/android/nexus/images?hl=en#angler

 

[grizzlebizzle]

I unlocked the bootloader, flashed recovery, and manually upgraded to mdb08m. That all worked just fine.

Now if I flash the mdb08k boot image to gain root it wipes out my recovery (?). I reflashed recovery and installed the SuperSU zip using recovery - but I do not have root. I went back and checked and the modified boot.img was flashed to boot, not recovery. Not sure where I went wrong. You can use the modified mdb08k boot.img on mdb08m, correct?

 

[ckc90745]

I doubt your phone is bricked. Download the MDB08M stock image from Google and flash it using the flash-all script in the file:
https://developers.google.com/android/nexus/images?hl=en#angler

thanks for that fast response I will try doing it tomorrow, and let you know how it went, thanks again

 

[sirxdroid]

thanks for that fast response I will try doing it tomorrow, and let you know how it went, thanks again

Most likely what I think happened is that you swiped in TWRP when it prompted you if you wanted to root so it did but you don't have the modified boot img, hence the boot loop. I've done it too even though I was aware of it, I just didn't pay enough attention.
To recover, you can try flashing just the system.img from the correct factory image if you recall which version your phone has. If it's out of the box and you didn't apply any OTA updates it's most likely MDA89D.

 

[Heisenberg]

I know the older kernel boot img's work but that wasn't good enough for me and my nexus finally arrived. so i went ahead and made ones (systemless and normal) from the mdb08m kernel. Most people are requesting this in the supersu thread (and i'm pretty sure others have provided these as well) but I feel those requests and those willing to provide are better served in the device specific forum. This seems like a great thread to provide such images for the nexus6p, of course ultimate decision up to @Heisenberg
Angler MDB08M Modified Boot Img - requires SuperSu 2.50+
Angler MDB08M Modified Systemless Boot Img - requires SuperSu 2.56

Thanks for your effort, I've included a link to this post in the guide.
:good:

 

[JustRootDontCustomRomIt]

This should be on the front page as a warning. Remove secure pins and fingerprints before making a backup in TWRP.
http://forum.xda-developers.com/showthread.php?t=3245070

 

[Heisenberg]

This should be on the front page as a warning. Remove secure pins and fingerprints before making a backup in TWRP.
http://forum.xda-developers.com/showthread.php?t=3245070

Thanks, I ran into this problem earlier today, very frustrating! I'm going to add a warning to section 4 very soon.

 

[JustRootDontCustomRomIt]

I know the older kernel boot img's work but that wasn't good enough for me and my nexus finally arrived. so i went ahead and made ones (systemless and normal) from the mdb08m kernel. Most people are requesting this in the supersu thread (and i'm pretty sure others have provided these as well) but I feel those requests and those willing to provide are better served in the device specific forum. This seems like a great thread to provide such images for the nexus6p, of course ultimate decision up to @Heisenberg
Angler MDB08M Modified Boot Img - requires SuperSu 2.50+
Angler MDB08M Modified Systemless Boot Img - requires SuperSu 2.56

You seem like the perfect guy to ask then... What is the difference between this newer boot img and the k img? Is it important to always have the right and up to date boot image? Could I mess things up if I flash the latest boot img onto a future update that might not be compatible?

 

[mrRobinson]

You seem like the perfect guy to ask then... What is the difference between this newer boot img and the k img? Is it important to always have the right and up to date boot image? Could I mess things up if I flash the latest boot img onto a future update that might not be compatible?

don't know the difference. Not sure anyone does except they are different, ie the two binary kernels don't have same md5. Not sure anyone found a changelog though.
The only thing you can mess up is the phone won't boot. Just as the K boots fine in M, there could be some minor differences yet its booting fine. If Q comes out, M could still boot it fine or it could not. You'll know if your phone start bootlooping. Then just flash back to M and wait for someone to post a Q kernel.
Since we don't know what changed, if anything, I just wanted to run on the one shipped with M to ensure not running into any issue that running on the K kernel with M image may bring to the table (again, if any).