yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] BeerFuelledDude:
I use systemless root (don't use Android Pay so can't say about that) - and have had no problems with any root required items, yet. XPosed is fine and I use GravityBox on it along with adblocks etc.
[Nexus 6P General] itsmejson:
Question on nandroid backup. Based on the instructions it says to check system/data/boot/vendor boxes. I see there are also system image, data image, boot image, vendor image boxes. Should those be checked as well?
[Nexus 6P General] xucardsfan08:
Noob question Alert!

I cannot seem to get the "fastboot devices" command to recognize my phone after booting into the bootloader. When the phone is turned on, it shows a serial number after the "adb devices" command. I reinstalled all the Android SDK tools, reinstalled/updated Java, restarted my PC, have debudding enabled in the phone, OEM unlock is turned on, nothing seems to work.

I do notice that in the bootloader, it says "Download Mode: Off" and "Connect USB Cable" does not change after plugging in a USB cable.

There were no issues installing the USB drivers, but it can't seem to recognize the phone when it's in the bootloader??? :confused:
[Nexus 6P General] greyhd:
Did you make sure to check "trust this computer" message on your phone's screen?
[Nexus 6P General] xucardsfan08:
I have not seen that pop up (phone on, or in bootloader). When the phone is on, just the "USB Debugging" enabled and "Use USB For" pops up. It is able to connect to my PC, as I have been able to transfer files to and from.
[Nexus 6P General] greyhd:
Next time you do it, unplug and plug it back to the computer and it should pop up.
[Nexus 6P General] xucardsfan08:
Nothing :(

I've tried all 3 USB ports on my computer. I'm on Windows 10, and using the cable that came with the phone. I'm out of ideas as to what's causing this. I can transfer files fine & dandy, but that "Trust this computer" doesn't pop up, and "Fastboot devices" does not work. Damnit. :confused:
[Nexus 6P General] elsworth1983:
Have a look in android sdk and find google drivers download them & reboot and see if that works.
[Nexus 6P General] Pain-N-Panic:
Yup, probably a driver issue. I know others who have had similar issues used some sort of "universal driver" and got it to work. Not sure where they downloaded it though.
[Nexus 6P General] omametsnor:
Yday I got the new P version update and i know I couldn't get it OTA since i customized my system ( rooted custom recovery ) so I did the way u described in section 10.

everything worked out BUT i kept getting a messaged IN the rom itself '' your software is corrupted '' not the orange warning but in android itself

so imma wipe evrything out and perform a clean install with fastboot, after that I flash the systemless root again and I restore my apps and settings

I dont know why i got this message probly because I upgraded from a customized system thats why im performing a clean install.

any tips what I can do better next time to prevent a clean install??

EDIT: I just rechecked my steps but could it be that i forgot to flash '' vendor.img"' and that made the pop up happen?
[Nexus 6P General] treasureking:
Need a new boot.img after January security update MMB29P

I followed Heisenberg's How-To, got the update MMB29P, reflashed TWRP. Now I need to choose systemless root, or traditional root. I want to modify build.prop. So I should go with traditional root, right? Where can I get a modified boot.img?

Can I go with systemless root, but still modify /system? Why is it said /system should be read-only?
[Nexus 6P General] SlimSnoopOS:
Yes.
[Nexus 6P General] AngelxCasas:
I did this tutorial several times, but this time, when im trying to put the lines to go back to stock, it stuck on waiting for any device, and i don't know what to do.

Debuging is on, the other option is on, re installed sdk tools, etc, and same problem, someone know what i have to do?
[Nexus 6P General] BeerFuelledDude:
I use systemless and can modify what I like, including build.prop

I also used the xposed framework. No need for a modified boot.img either.
[Nexus 6P General] treasureking:
Thanks for the info.

Which version of SuperSu are you using?

I had a weird problem. I used traditional root method last time and I had SuperSu 2.52. I don't remember if it gets updated later.

After this P update, I tried systemless root and used SuperSu 2.66. It works but I keep getting a message in SuperSu regarding binary needs to be updated. I let it update, but it always fails. When I tried to disable/enable su, it also complains failure. But actually "su" works. I thought it could be related to switching from traditional root to systemless root.

I have since uninstalled SuperSu. Will try systemless root again tomorrow.
[Nexus 6P General] Surfinette:
Thank you for your great guide.

I have a question regarding the process below

I need this command to run the Secure Settings plugin for Tasker...

But I presume that applying this code will destroy the ability to do OTA updates while rooted, right?

Can you provide the reverse command to go back to systemless root?​
[Nexus 6P General] anjelika:
Does your device appear in the list when you type

or

? If not...it could be a driver problem. Make sure that the drivers for your phone are properly installed.
[Nexus 6P General] BeerFuelledDude:
I'm on the same version SU 2.66. I'm not sure what that issue is, though. It was as simple as flashing the .zip within TWRP and that was it. When you say P update - you mean MMB29P? I'm on that build so shouldn't be any issues. Listed my versions, just in case it helps.

TWRP - v2.8.4

SU - v2.66

Android - MMB29P
[Nexus 6P General] NPOA556:
Even if you undo all changes made to /system, you will still not be able to receive OTAs unless you flash stock system, boot, and recovery images. Once /system is modified in any way, OTAs are no longer possible without reflashing stock.

---------- Post added at 12:46 PM ---------- Previous post was at 12:39 PM ----------

You didn't flash a modified boot image before installing SuperSU, did you? That requirement for the older root methods is not required for the newer systemless root. Also, did you decline TWRP's offer to install SuperSU?
[Nexus 6P General] AngelxCasas:
Im suing the google driver of the SDK installer, and everyting was ok before, but yes it doesn't appear there.

What driver should i install?
[Nexus 6P General] treasureking:
No, I didn't flash a modified boot image this time, after upgrading to MM29BP. I would if I could find the modified boot.img though.

I also declined TWRP's offer of SuperSu.

Thanks for the reminder.
[Nexus 6P General] :
Layers

I want to know if anyone has the modified boot image for MMB29P. I'm trying to get layers to work but they don't stick which did not happen before on traditional root. I'm using systemless and tried the terminal commands but all I get is read-only system file.
[Nexus 6P General] treasureking:
I redo all the steps with MM29BP image, installed TWRP 2.8.7.2 and systemless root with SuperSu 2.66.

After rooting, I tested Android Pay. I cannot add a new credit any more. I could with traditional root method before after disabling root in SuperSu.

Now when I tried to disable and re-enable su in SuperSu, it says failed. Soon a message pops saying "The SU binary needs to be updated. Continue?". Surely installing failed as well.

After both failure, I am still able to "su" in a terminal, or under adb shell. I then rebooted the phone, and ignore the SuperSu binary needs update. Another problem comes after I disabled root under SuperSu. I cannot use SuperSu again. It says "There is no SU binary installed, and SuperSu cannot installed it." I guess that's the result of my turning off root. What's the point of turning it off, if I cannot turn it back on again?

The conclusion of my limited tests is,

I could use Android Pay (at least adding CC) using traditional root method on MM29BM as far as root is disabled under SuperSu.

I cannot use Android Pay the same way using systemless root method on MM29BP, right after the first boot. Disabling root under SuperSu doesn't help and prevents itself from running again.

For now, I stay unrooted and modify /system with TWRP. Hopefully, someone better than me will figure out a solution, or what I did wrong.
[Nexus 6P General] anjelika:
You should install the Google USB drivers. Can be found here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
[Nexus 6P General] Kriptini:
Hi all. Thanks for maintaining this thread. Trying to root my new Nexus 6P today and I'm having an issue.

When installing TWRP, I chose to not let it read-only, as I wanted to do a traditional root. I've found a boot image for my build version (MMB29P), but I get an error when I attempt to flash it. Here's what my cmd prompt looks like:

C:\adb>fastboot flash boot boot.img
target reported max download size of 494927872 bytes
sending 'boot' (3526 KB) . . .
OKAY [ 0.153s]
writing 'boot' . . .
FAILED (remote: metadata: partition name doesn't exist)
finished. total time: 0.185s

Does anyone have a fix for me? Is there any additional information I can provide that would be helpful?
[Nexus 6P General] Heisenberg:
Where did you find the boot.img?
[Nexus 6P General] Kriptini:
Got it from the first post in this thread:

http://xdaforums.com/nexus-6p/general/mmb29p-images-roms-t3286024
[Nexus 6P General] Heisenberg:
Ok, the first problem here is that that boot.img won't allow you to do traditional root, it's stock, not modified. As for why it won't flash I'm not sure, had you flashed anything previous to this?
[Nexus 6P General] Kriptini:
Yes, I've both unlocked the bootloader and I flashed TWRP, but I did not select "read-only" for TWRP. Can I still attempt a systemless root? What do you think would be the best thing for me to do in this case if I want to unlock and root my phone in preparation for installing a custom ROM?
[Nexus 6P General] Heisenberg:
Well there's no point in rooting before you flash a ROM because it'll be overwritten. Best thing to do is just make sure you're on the correct firmware (bootloader, radio, etc), and then just flash the ROM.

And no, allowing modifications to system with TWRP will mean you don't have systemless root.
[Nexus 6P General] slixzen:
So gathering what I have read, I would like have TWRP on a recovery partition permanently, keep system unmodified, and have systemless root. But this is not possible, is that correct?

If so, what is causing the recovery partition to constantly be overwritten? I don't recall this ever being an issue on Nexus 5. I have systemless root, with write-enabled on TWRP.
[Nexus 6P General] Kriptini:
Thanks, it works great now!
[Nexus 6P General] Heisenberg:
TWRP needs to write to the system partition in order to retain its position in the recovery partition.
[Nexus 6P General] slixzen:
So then there is no way to use Android Pay (due to the unlocked bootloader I assume, as of right now my systemless root is complaining it doesn't meet the requirements) with root like can on the Nexus 5?

EDIT: To clarify, this is using stock firmware (the january patched version), the only thing I have done is installed SuperSU via a system-less install (and double checked that it is system-less in SuperSU app), and downloaded the Safetynet Playground app to test if I meet the minimum requirements, which it says I don't. My bootloader is unlocked still, because if I lock it, I wipe the phone, which removes root.

EDIT 2: I also tried adding a card in Android Pay and it tells me my system is not compatible.
[Nexus 6P General] Heisenberg:
Your bootloader state has no effect on Android Pay. It'll be the fact that you allowed TWRP to modified the system that's stopping it.
[Nexus 6P General] slixzen:
Alright, but I didn't do that. If I remove full un-root the system-less root app, Safetynet Playground tells me that I pass the requirements on the Nexus 6P. While I still have root available on 2.61 SU for Nexus 5.
[Nexus 6P General] Heisenberg:
I must have misread your previous post. I'm not sure what's going on, others have Android Pay working with systemless root on this device.
[Nexus 6P General] slixzen:
I tried again, using V2.61 and I obtain a pass on the safetynet app. Maybe it is something that is wrong with the 2.66 that gives away the safetynet verification. Maybe not, I don't know, but going to stick with this until then. EDIT: I also used Windows instead of OS X, but that shouldn't make a difference.

So my last question is, is there any way to lock the bootloader with a custom recovery intact then?
[Nexus 6P General] Heisenberg:
You can't lock the bootloader with any modifications. I wouldn't suggest it anyway, unless you're super concerned about someone getting their hands on your phone. If you ever have problems and your bootloader is locked you could end up with a device that you can't revive.
[Nexus 6P General] SlimSnoopOS:
With SuperSu 2.66 installed, delete or add ".bak" to the end of this folder su/xbin_bind" and reboot. Check your SafetyNet App and you should be set with Android Pay.
[Nexus 6P General] AngelxCasas:
So guys, when I use systemless root, my android pay app don't let me enter to te PLUS button, where I gotta put my card, what im droing wrong, if other people can use it normally with systemless root?

---------- Post added at 07:32 AM ---------- Previous post was at 06:51 AM ----------

Why when Im trying to ad a card with systemless root, it say's that I can't ?

What should I do to fix the problem?
[Nexus 6P General] Heisenberg:
Do you have any other modifications or a non-stock DPI?
[Nexus 6P General] tbv2005:
Hi, I have a small issue.

original state of phone:

- latest firmare, systemless root, xposed installed with some modules

what I did before problem occur

- froze Google app and Google launcher in Titanium

- edit build.prop to get multiwindow and reboot (ro.build.type=userdebug) --> rebooted device

What happened then is that I was in a bootloop. Android was showing Optimising Apps..... --> reboote to the circles --> optimising apps...... an so on

OK, I changed the build.prob back to the original file but still same behavior (Optimising Apps --> circles --> Optimising Apps.

OK, then just let's reflash the system --> followed step 10 from OP (by the way 3 times already to make sure I didn't do any mistake) --> behaviour now is Android starts, it's shortly showing the clock on top rigth and the menu buttons on bottom but that's it. It just stays there for a while with screen off or on and then reboot itself.

Is there anything I can do to keep the installed apps and my SDcard, or at least the SD Card? I want avoid starting everything from scratch. Thanks in advanced!

PS: right now TWRP is not installed but can be installed if it would help.

---------- Post added at 02:31 PM ---------- Previous post was at 01:32 PM ----------

OK, problem solved (also I'm not sure if it was the right way to do) - I just restored the Data partition from an old nandroid backup, Starting was fine, I shortly got the red warning device can't be trusted but ignored it, installed Su and Xposed from recovery and everything is fine.
[Nexus 6P General] Danieliko:
When I try to do nandroid backup, it fails and says I dont have enough space on my device. The TWRP says I have 0mb on my device.

I read online that I need to set a password for my device to solve it, but the main thread says not to have any passwords when backing up.

What should I do?
[Nexus 6P General] janjan881:
Build MMB29P

I have to say, this is one of the best rooting guides I have ever seen. When I am going to root my Nexus 6p in the future, I will definitely use this guide. Nevertheless I do have a question. I have Android 6.0.1 (build MMB29P). This particular build is not mentioned in the guide. Does this affect the rooting process? I assume the systemless root will still be possible, but how about the traditional root with a modified boot.img? Does it even matter if I use the systemless root or traditional root for flashing custom ROM's? I am not sure If I can flash ROM's without root.

Anyway, many thanks for this guide! :good:;)
[Nexus 6P General] Mesmurized:
Root is not required to flash [?? all, many, some ??] ROMs. For example, Pure Nexus ROM includes system root and provides instructions to change it to system-less root if desired.

I agree about this guide ... it is the best :)
[Nexus 6P General] AngelxCasas:
Nothing, but I read here in a random comment (I lost it) i have to check a "systemless root" option on SuperSU? I gotta do that to make it work? or what?

I just went stock again, systemless rooting (with all the steps before root obviously) and tried to use android pay, and when I wanna add a card and I press the + button, it sends me a message, and don't let me put my information.

Im getting this message "Android Pay cannot be used" "Google is unable to verify that your device or the software running on it is Android compatible"
[Nexus 6P General] dlads:
Thank you :)

worked well.

Just for anyone else who's had the SDK on their computer for a while, it does need to be either updated or the new version :)

First Nexus :D onto my first nexus ROM

Cheers.
[Nexus 6P General] LeftHandedWave:
Holycow! That worked. Thanks!
[Nexus 6P General] kenfly:
Encryption

So having an encrypted device is fine with the new twrp and it will function as normal?
[Nexus 6P General] Heisenberg:
Yep.
[Nexus 6P General] AngelxCasas:
What should I do if I can't add cards to Android pay?

I didn't modify nothing, just systemless root, and anything more.
[Nexus 6P General] Heisenberg:
Which version of SuperSU are you using?
[Nexus 6P General] AngelxCasas:
2.66, and Im using Ex kernel now, but is the same, I saw someone saying that if I "completly unroot" on supersu, add cards, and then root again it will work properly, but i don't know if that option will work, because the Ex kernel.

Nothing edited, everything stock but systemless root metod with supersu 2.66 and ex kernel.
[Nexus 6P General] Heisenberg:
I'm not sure about EX kernel, but I think I recall someone else describing issues with 2.66 and Android Pay, they unrooted and flashed 2.61 instead and that fixed the issue.
[Nexus 6P General] syintiphic:
I've been able to get Android Pay to work on my initial setups with these two ROMs.

1) Stock 6.0.1 w/systemless root using SuperSU 2.60.

2) Pure Nexus ROM w/systemless root using SuperSU 2.66.

When I installed SuperSU 2.66 there were some steps I had to take to make sure SuperSU installed as systemless. This was not the case with version 2.60 as it has a different install script.

"In TWRP Go into Advanced > Terminal Command > Select current folder via button in right hand corner and type the two lines below, one at a time:

Code:

echo SYSTEMLESS=true>>/data/.supersu echo BINDSYSTEMXBIN=false>>/data/.supersu"

Note that I didn't discover the instructions in quotes on my own but used the guide by [MENTION=6842057]nathanchance[/MENTION] that was put together in the Pure Nexus thread.

Also, there is a bit more detail in Chainfire's SuperSU release thread, which provides details on the different versions and methods for obtaining root. I suggest you check it out.

http://xdaforums.com/showthread.php?p=64161125

I hope this helps.
[Nexus 6P General] Danieliko:
Anyone?:confused:
[Nexus 6P General] Heisenberg:
Have you tried the password you previously used? That is what's used for deception.
[Nexus 6P General] garny68:
can someone advise here please . ive just unlocked bootloader and not trying to flash twrp but when i type fastboot flash recovery twrp.img all i get is waiting on device and nothing happens
[Nexus 6P General] hexinn:
I just get this error (The program cant start because AdbWinApi.dll is missing) following (10. How To Update To A New Build Of The Stock ROM) Anyone know how to fix that?

Also is ok to do that with stock rom and custom kernel?

Edit: all fixed. Thanks for great tut.
[Nexus 6P General] SlimSnoopOS:
Type the exact file name of the TWRP file that you have downloaded, every single letter or number.
[Nexus 6P General] garny68:
the original file was called twrp-2.8.7.2-angler.img i renamed it to twrp.img are you saying rename it back to twrp-2.8.7.2-angler.img then input fastboot flash recovery twrp-2.8.7.2-angler.img

tried fastboot flash recovery twrp-2.8.7.2-angler.img

still same answer waiting on devices
[Nexus 6P General] Yamakasinge:
Problem

Hello, thanks you for you post. I have a problem : accidentaly, I did the swipe for root with TWRP and now my phone won't start. Fortunately, I did the Nandroid and EFS backup before the TWRP root, what should I do now ?

Thank you for your time,

Léo
[Nexus 6P General] SlimSnoopOS:
No, that shouldn't be necessary although you could try that. I was making sure you weren't typing TWRP.img when the file had not been renamed to that. Did type the file directory as well? fastboot flash recovery C:\path\to\file.img
[Nexus 6P General] garny68:
hi ive nit typed anypath the path is already ther in command promt as im opening the comand promt in correct folder

im just following the instructions in secton 2 of first post in this thread 2. How To Install A Custom Recovery On Your Device

5 hours i been trying to do this
[Nexus 6P General] SlimSnoopOS:
Hmm, ok. That should not be the case. Let's start from the beginning then. Are you a new 6P user? If so, have you updated the SDK? It needs to be updated if you are coming from an older device.

If you have used fastboot to flash on your 6P before, have you downloaded any drivers that may cause issues?
[Nexus 6P General] srqrob:
Seems kind of basic, but with the phone in bootloader mode connected to your PC does typing fastboot devices in a command prompt return the serial number of your phone?
[Nexus 6P General] garny68:
hi

yes im a new 6p user

just downloaded android sdk this morning

if i enter adb devices it shows devicce

only other drivers that may be on pc are for android tablet universal usb drivers

should i be turning my phone of first then pressing power on + volume down then issuing the command

fastboot flash recovery twrp.img
[Nexus 6P General] Badger50:
Yes. You need to be in the bootloader for fastboot to work.
[Nexus 6P General] AngelxCasas:
SuperSU 2.61 runs great, and it fixed my android pay problem, thank you :)
[Nexus 6P General] Yamakasinge:
Anyone ?
[Nexus 6P General] Badger50:
Go back into fastboot and flash TWRP again.
[Nexus 6P General] Beamen:
Thanks

Just wanted to say thanks, this thread was really helpful in getting my new Nexus 6P bootloader unlocked, rooted, and fixing android pay.

Loving this phone so far!
[Nexus 6P General] Salval:
I followed a different guide but did everything like what is stated in this tutorial except I allowed twrp to install supersu and the phone stays on the boot animation now. Any tips?
[Nexus 6P General] Mesmurized:
I believe the post #1 tutorial states to not allow twrp to install supersu.

Edit: Section 2: "Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems"
[Nexus 6P General] Heisenberg:
You'll need to flash the system image for your current build to remove the incompatible version of SuperSU that you've installed. Do you have a link for the guigive you followed please?
[Nexus 6P General] Salval:
I followed your directions to restore the phone and have flashed twrp 2.8.7.0. I also flashed the MMB29M boot image and copied supersu over to the phone but I can't find it in twrp to install it.

Here's the guide I followed the first time : http://wccftech.com/update-and-root-mmb29p-android-6-0-1/

---------- Post added at 03:46 AM ---------- Previous post was at 03:21 AM ----------

I got it worked out. Thanks!
[Nexus 6P General] Heisenberg:
That's why people should only follow guides they find here on XDA, that guide directs users to download an outdated version of TWRP, which can't access the data partition if it's encrypted. I'm glad you worked it out though.
[Nexus 6P General] MegaHz:
yeah it seems that there's no modified boot yet? [MENTION=4153349]Heisenberg[/MENTION] can you confirm?

thanks
[Nexus 6P General] Heisenberg:
Indeed, there is no modified boot.img for MMB29P.