yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] effraie:
I guess you're using a case covering buttons?I've got the same issue. Does it work without the case?

Try to push the very high end of the power button. A bit tricky, but work for me
[Nexus 6P General] johnhazelwood:
How did you try taking a screenshot? Should hold power button + volume down for a few seconds.
[Nexus 6P General] Kameechewa:
Wow! You're right, it's the case, I feel like such an idiot now. It is very difficult to take one properly with the case. Thank you!

---------- Post added at 11:48 PM ---------- Previous post was at 11:42 PM ----------

I was doing power and volume down. But it appears this case mashes all the side buttons together?
[Nexus 6P General] Heisenberg:
Not really, sorry.
[Nexus 6P General] Slartibartfast_:
Thanks a lot for the detailed guide! The only thing I wish it had is some explanation on what we can do after each step and what we might miss. For example, I was thinking about doing steps 1-4 so I can install a decent ad blocker and enjoy a few other tweaks that require rooting. I know that by doing that I'll be giving up on Android Pay, but what about OTA updates (without manually flashing them / wiping data?)

Is there any other downside to doing that?

TIA.
[Nexus 6P General] :
This... Times a million saved headaches.

I may have missed it but is there seriously not a FAQ about all the questions we noobs ask? It would help me tremendously to understand the process of twrp, root, root apps, and firmware updates without having to ask, search, or possibly get confused.

Great community but an FAQ would us a lot. ☺
[Nexus 6P General] AriStar:
This may be a dumb question BUT, Ive rooted and stuff, how do I install the updates?

It keeps telling me i have an 8mb update but when i install it it doesnt work.
[Nexus 6P General] Heisenberg:
You need to remove root and flash the stock recovery. Flash the system.img and recovery.img from the factory images and then you can take the update.

Sent from my Nexus 6P
[Nexus 6P General] AriStar:
will this remove all my saved data?
[Nexus 6P General] Heisenberg:
I'm planning on adding an FAQ section guys, it's in the works. I don't know when it'll be added as I'm a bit pressed for time at the moment but it's coming.

Sent from my Nexus 6P
[Nexus 6P General] AriStar:
Also is there any step by step guide on getting updates?
[Nexus 6P General] efrant:
Try this:

fastboot - S 512M flash system system.img
[Nexus 6P General] Heisenberg:
It's in the works. I gave you basic instructions on the last page though, the commands that you need to use can be found in the last section of the guide (how to flash factory images).
[Nexus 6P General] AriStar:
I don't want to risk anything after I failed following the steps to root once before getting it down.

I'll just wait for your guide haha.
[Nexus 6P General] adrman:
Make sure your sdk is up to date. The system file is too large to flash all at once now.
[Nexus 6P General] effraie:
I have an issue on N6Pangler rom, with MMS, and i may go back to stock for checking if the issue is rom related. I was wondering what was the easiest way, if I want to keep all my user data, root, and TWRP?
[Nexus 6P General] Slartibartfast_:
Your work is much appreciated. Thanks!
[Nexus 6P General] sirxdroid:
One correction to the guide if you could make it, in #2 you do *not* need the modified boot.img for TWRP. It's only needed for SuperSU if you root. Technically you can install TWRP and not root (which is how I've been running for a couple of days now).
[Nexus 6P General] Heisenberg:
You can't keep root or userdata if you want to go back to stock, especially if you're trying to troubleshoot something. Go back to stock by flashing everything from the factory images except for recovery and userdata, but you should format userdata otherwise you risk reintroducing the cause of your issues.

Thankyou for confirming this, I'll edit the guide appropriately.
[Nexus 6P General] Heisenberg:
[Size=+1]

Update!

[/size]

An FAQ section has been added to post #2, so far it only contains one question but I figure it's the one question that's being asked the most so it's a good start. Please feel free to make suggestions for more questions to be added.
[Nexus 6P General] :
Perhaps expand on it to include the steps to flashing updates manually through adb. It's the only thing I have left to understand and probably the most daunting part yet. Unlocking, twrp, and rooting were easy.

Thanks for this guide BTW. It helped out a ton.
[Nexus 6P General] Heisenberg:
There's already a section (#8) detailing how to flash factory images with fastboot. You don't use adb to flash anything, it's fastboot that you use.
[Nexus 6P General] :
Right lol.

Do you recommend nexus root toolkit to speed things up since Google's putting out firmware updates every month now?

On average how long does it take you to manually update firmware and set all root mods back the way they were?

Do I have to deactivate root mods before flashing firmware upgrades?
[Nexus 6P General] Heisenberg:
Absolutely not, I'll never recommend anyone use a toolkit, I've seen them cause too many problems, plus they take experience away from the user. You'd need to deactivate things like Adaway by restoring the stock host files, but most root apps you wouldn't need to worry about. All up it'd take maybe a few minutes to flash the system and recovery images, no time at all.
[Nexus 6P General] :
Thank you heis.

So If I don't deactivate the adaway host files before updating firmware (and among any other extreme case) what could happen?
[Nexus 6P General] Heisenberg:
The updater will detect a modified /system and will refuse to install the update.

Sent from my Nexus 6P
[Nexus 6P General] efrant:
If you have root, flashing the system and recovery images is not enough to be able to install an OTA update. You also need to revert your modified boot image back to stock (in most cases).

I think maybe he initially meant "how to sideload an OTA update".

Sometimes the OTA update comes out before the factory image, so in order to update (assuming you haven't received the update OTA), you have to update by sideloading the update via ADB because there are no factory images to flash.
[Nexus 6P General] :
That's innocent enough. You said most mods won't interfere with updates but I assume the ones that will are the ones that are installed in /system?
[Nexus 6P General] Heisenberg:
Can't believe I skipped that, thanks, I'll add that information into the FAQ.

Ah yeah, I hadn't thought of that, I'll need to add that info to the guide as well.

What I meant was most apps that use root don't interfere with the /system partition, thinks like Titanium Backup, Greenify, etc. Most mods do reside in the /system partition so anything like that needs to be cleaned up.
[Nexus 6P General] sidhaarthm:
Hi all,

Quick query, and apologies in advance if already answered somewhere, though I could not find any info on the first page.

Can I use the Modified Boot Image from MDB08K for Root purposes even if I am running the latest build MDB08M for the 6P?

Thanks!
[Nexus 6P General] Heisenberg:
Yes you can, I'll add this information to the FAQ section.
[Nexus 6P General] Si73:
Thank you. There were clear, understandable and straight forward instructions.
[Nexus 6P General] Candylicks:
I used your guide for my first time unlocking my 6P and was easy to follow. Thanks for the clear guide!
[Nexus 6P General] dangerdan:
So I installed the custom TWRP recovery before updating to the newer build, so I need to update to the latest build and then install TWRP again right? Thanks.
[Nexus 6P General] sirxdroid:
I had D build out of the box so I unlocked the bootloader and flashed latest TWRP. All good. Then I manually moved to the M build as I was not getting any OTA updates. Here's what I flashed by hand:

- bootloader

- radio

- system

- vendor

- modified boot img from K build (so I can root with /system SuperSU)

I did *not* flash recovery as I already had the latest TWRP version. I tried booting into recovery right away and to my surprise I ended up in the stock recovery, TWRP was gone.

Not a big deal, I flashed TWRP quickly but I'm curious what flash from above could have wiped recovery and restored it to the stock one?
[Nexus 6P General] efrant:
The factory images from Google now include a script that essentially flashes the stock recovery on every boot. If you get root, then it disables this (or you can disable it manually, but it requires a change to a file in /system). Even if you flash TWRP again, it will get wiped out by the stock recovery when you boot into Android unless you disable it.
[Nexus 6P General] sirxdroid:
But I didn't flash the entire factory image, I only picked certain partitions to flash as listed above. And I did not boot after I was done flashing, I tried to go straight to recovery.

I know about stock system trying to restore recovery, that's why I always boot TWRP first to let it fix it.

Again, not a huge deal, just trying to understand where things went wrong.
[Nexus 6P General] efrant:
You flashed the system partition (the script is in the system partition). But in your case, I would assume that it's because you didn't get root after flashing TWRP the first time you flashed TWRP, so it flashed the stock recovery when you booted Android on the D build.
[Nexus 6P General] belloni:
NVM.
[Nexus 6P General] sirxdroid:
Ah so you need to get root in order for TWRP to fix it so that recovery is not replaced? Is it TWRP that fixes it or installing SuperSU?
[Nexus 6P General] efrant:
Root, not TWRP. Or you can make the edit yourself if you don't want root. Just delete or rename /system/etc/install-recovery.sh

The reason why getting root disables it, is because the way that SuperSU is implemented, it uses /system/etc/install-recovery.sh, so it replaces that file with its own version (essentially).
[Nexus 6P General] wirelezzz:
I thought with root u get no update notifications. 8 mb securtity update prob will ruin the root and mods i did .

Question I'm all rooted and I now have a message system update is downloaded but I did not install. How do I get rid of this message and the file that's downloaded. Don't want to destroy my mods and root lol

OK figured out how stop the msg but where does the update down load file go.
[Nexus 6P General] dipole:
I followed steps below and now on first boot I get "Android System. There's an internal problem with your device. Contact your manuf for details. " Any clue as to what I did wrong?

- Flash mdb08m factory image

- Flash modified angler-mdb08k-boot

- Flash TWRP 2.7.2

- Flash SuperSU Beta 2.52

edit, also erased data and dalvik/cache, still error message

edit2, found this, the error is likely from setting a fingerprint. This fix worked.

http://xdaforums.com/nexus-9/development/zip-universal-build-fingerprint-fix-t3173557/post62229347#post62229347
[Nexus 6P General] ghudgins:
did you also have to reflash the modified boot.img from the original instructions?
[Nexus 6P General] dipole:
Was because I had a fingerprint on file I think, see above for fix for anyone else who gets this error.
[Nexus 6P General] efrant:
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
[Nexus 6P General] JSouthern:
Thanks for the thread Heisenberg. I almost jacked myself and installed SuperSU before the boot.img. Luckily I'm so compulsive I check everything I'm doing 10 times before committing to it and realized what I was about to do.

This is only my 3rd smartphone. My first premium phone (my droid razr was better than galaxy s5). And my first root.

Thanks for making it a cake walk. I had no idea what I was missing these last 4 years.
[Nexus 6P General] wirelezzz:
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?
[Nexus 6P General] efrant:
It won't install. You need a clean system (i.e., no mods) and most likely the stock boot image and stock recovery.
[Nexus 6P General] Kiribbs:
USB Continuously Not Working

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?
[Nexus 6P General] wirelezzz:
Thanks. Don't have to worry then.
[Nexus 6P General] JSouthern:
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!
[Nexus 6P General] 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 [MENTION=4153349]Heisenberg[/MENTION]

Angler MDB08M Modified Boot Img - requires SuperSu 2.50+ (re-uploaded, tested, 11/11)

Angler MDB08M Modified Systemless Boot Img - requires SuperSu 2.56
[Nexus 6P General] 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!
[Nexus 6P General] 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.
[Nexus 6P General] msick:
solved
[Nexus 6P General] Heisenberg:
I see you've also posted this in another thread, where you're receiving help. Please don't double-post, it isn't allowed.
[Nexus 6P General] Heisenberg:
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.
[Nexus 6P General] 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
[Nexus 6P General] sirxdroid:
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
[Nexus 6P General] 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?
[Nexus 6P General] ckc90745:
thanks for that fast response I will try doing it tomorrow, and let you know how it went, thanks again
[Nexus 6P General] sirxdroid:
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.
[Nexus 6P General] Heisenberg:
Thanks for your effort, I've included a link to this post in the guide.

:good:
[Nexus 6P General] :
This should be on the front page as a warning. Remove secure pins and fingerprints before making a backup in TWRP.

http://xdaforums.com/showthread.php?t=3245070
[Nexus 6P General] Heisenberg:
Thanks, I ran into this problem earlier today, very frustrating! I'm going to add a warning to section 4 very soon.
[Nexus 6P General] :
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?
[Nexus 6P General] mrRobinson:
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).
[Nexus 6P General] The_android_Modder:
Ok lol i wrote works great because i needed to post one more time b4 i could post a link sorry guys lmao it did make me seem dumb after a actually read the thread lmaoo
[Nexus 6P General] tpthatsme:
Just follow the non-steps

lol
[Nexus 6P General] Heisenberg:
Wow, yeah, that's hilarious. I made an error in what I said obviously, I'm glad you found it necessary to make an off-topic post just to point that out.
[Nexus 6P General] wonsanim:
Hi guys i follow the guide complete till hold shift + right click, select open command prompt here, after do this s no command prompt option, Just open or run as administrator, some help please!
[Nexus 6P General] StupidIdea:
I understand this is a placeholder thread and still I find it misleading. You cannot simply root Android 6 beta so there is no reason to think that final will be different. The only working solution currently is flashing custom kernel with permissive SeLinux. Someone will get their device soon, follow this guide and end up in bootloop.
[Nexus 6P General] Heisenberg:
Sounds like you're clicking on a file, you're meant to just click on blank space within the folder.

I'll edit the guide to remove the root section, and reimplement that section as more information comes to hand.
[Nexus 6P General] wonsanim:
Yes, exactly Heisenberg, now open but I test abd version but don't recognize abd
[Nexus 6P General] Heisenberg:
You need to be more specific, that doesn't make much sense. Plus, do you actually have the Nexus 6P already?
[Nexus 6P General] wonsanim:
Sorry I don't have the device, i just pre-order, I just testing using this method because I never use before
[Nexus 6P General] Heisenberg:
Ok, but if you don't have the phone connected then what is adb meant to be communicating with? It can't recognise anything if there's no device connected.
[Nexus 6P General] wonsanim:
I just make the question because the tutorial explain that you need to enter the code adb version to see the results and after connect your device
[Nexus 6P General] Heisenberg:
Ok, but you're still not being specific enough. If you expect anybody to be able to help you, you need to explain exactly what is or isn't happening.
[Nexus 6P General] wonsanim:
I installed the SDK inside C:\ and go to a new folders called platform-tools and follow your instructions, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide.

To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:

Code: adb version

If it returns a version number for Android Debug Bridge then you're good to go.

but said don't recognized abd for me means something is wrong
[Nexus 6P General] Heisenberg:
What version of Windows are you using? Can you show me a screenshot of the folder please?
[Nexus 6P General] wonsanim:
i'm running Windows 10
[Nexus 6P General] Captain381:
thanks mate

it worked for me. thanks for the contribution
[Nexus 6P General] Heisenberg:
How'd you get the phone already?
[Nexus 6P General] Born<ICs:
edited
[Nexus 6P General] Heisenberg:
Only the root section was problematic, and that section has been altered.
[Nexus 6P General] Born<ICs:
OK got it, thank you much.

for a newbie which has less risk, SDK or Multi Tool ?

Here is link to download Huawei USB Drivers (HiSuiteSetup)

.

https://www.androidfilehost.com/?fid=24052804347825738
[Nexus 6P General] nowy57:
hello

I cannot UNLOCK my nexus6P by using command "fastboot flashing unlock"

I have old adb files when I am using it to find 7a

what am I doing wrong ?
[Nexus 6P General] efrant:
You need to go here, and download the driver (direct link here).

Plug your phone into your PC, and open Device Manager on Windows. Then find the device (not on the device under Portable devices, but the other one, probably under Other devices -- should say something like Android device or Nexus 6P or something), right click on it and select Update driver.

THEN, select the second option, i.e., Install from a list or specific location, NOT the first option (Let Windows search for best driver blah blah...).

THEN click on Have disk and point it to where you extracted the USB driver you downloaded.
[Nexus 6P General] AriStar:
my question would be, does taking OTA update remove all personal data on the phone?
[Nexus 6P General] sirxdroid:
No, that would be a disaster.
[Nexus 6P General] Ketawa:
I ran into some issues using this modified boot image for MDB08M with SuperSu 2.52. AdAway couldn't write to /system. I also received a red warning when booting into system that said "your device is corrupt" rather than the orange warning that said "your device can't be checked for corruption". It was still the orange warning when I booted into TWRP. I checked my history and I downloaded the correct one.

I reverted back to the MDB08K modified boot image from the first post in the [WIP][2015.10.30] Android 6.0 Marshmallow thread and AdAway is working again. No red warning either.
[Nexus 6P General] ckc90745:
hi sixxdroid thanks for your help, when I use twrp I chose the option of not rooting the phone, the only thing I did was unlock the bootloader, turn on oem unlock and usb debugging on the phone settings, then rebooted the phone and install twrp, the first time it did not working it just took me to android with a red square on the center, then I reflashed twrp and it worked the phone rebooted and told me there was an update to my software but I did not take it, reboot it the phone and made a nandroid back up, then try to reboot phone but it is stock on the google boot screen it shows a lock image on the botton and its unlock