yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] Ketawa:
Quick Reboot didn't work for me on systemless SuperSU 2.61. Chainfire posted that there is a workaround for this and other apps not working with systemless root since they look for su binary in a hardcoded location. http://xdaforums.com/showpost.php?p=64204285&postcount=3358

I booted into TWRP, mounted system, opened a terminal, navigated to /system/bin/, and used the command "touch su" to create a file called su. Booted back into system and now Quick Reboot works again.
[Nexus 6P General] 09eric09:
Edit: nvm.
[Nexus 6P General] justmpm:
I think you will have to provide a little bit more information here...what exactly is failing for you and what are we supposed to notice?

If you are having trouble with English...maybe try Google translate, it should do a pretty good job translating between English and Spanish.
[Nexus 6P General] adrman:
There's a great workaround for Quick Reboot, use Franco's Simple Reboot. :) It's been working nicely since I updated, well actually since before. It's a good alternative to QR.
[Nexus 6P General] Nexicovx:
Cataclysm steps:

Excuse my ignorance, I am new to Nexus and Android. I want to install the cataclysm rom into my phone. Do I do the following steps in order to have a rooted device with cataclysm?

How To Unlock Your Bootloader

How To Install A Custom Recovery On Your Device

How To Decrypt Your Data Partition

How To Make A Nandroid Backup With TWRP Recovery

How To Make An EFS Backup With TWRP Recovery

How To Root Your Stock Rom

How To Install A ROM with TWRP Recovery (This is where I would install Cataclysm)

How To Install A Custom Kernel With TWRP Recovery

How To Flash The Factory Images (And Return To Stock)

I would like to be able to keep up with the security updates without having to erasing my phone and starting from scratch. Is this the correct procedure?
[Nexus 6P General] Heisenberg:
You don't need to follow all of the sections. Just these:

How To Unlock Your Bootloader

How To Flash The Factory Images (flash the MMB29M build)

How To Install A Custom Recovery On Your Device (use TWRP 2.8.7.2)

How To Make A Nandroid Backup With TWRP Recovery

How To Make An EFS Backup With TWRP Recovery

How To Install A ROM with TWRP Recovery

No gapps are necessary with cataclysm, and you can flash SuperSU 2.61 directly after flashing the ROM. You also don't need to worry about flashing any modified boot.img as SuperSU 2.61 will patch the existing boot.img for you. One thing you need to be mindful of is to be on the correct build (MMB29M) before flashing Cataclysm. So you'll see I've added that step between unlocking the bootloader and flashing the recovery (just don't flash/format userdata).

PS. You won't be able to take any official OTA updates while you have a modified system partition. When a new update comes out you'd need to flash the factory images again to receive it, and then flash Cataclysm and root again.
[Nexus 6P General] Heisenberg:
Updated 2015/12/09!

I've split the "How To Root" instructions into two sections; systemless and traditional.
[Nexus 6P General] Nexicovx:
Thank you for this detailed response. I should be getting my Nexus in a week. I'm excited to try Android out. I've been waiting for the right phone to turn me over and the 6P seems to do it for me (not to mention Project Fi's price).
[Nexus 6P General] Heisenberg:
No problems, don't be afraid to ask if you have any further questions.
[Nexus 6P General] logonaniket:
Can someone provide me stock recovery (for MDB08M) link?
[Nexus 6P General] snachez:
[MENTION=4153349]Heisenberg[/MENTION] [MENTION=3355398]mrRobinson[/MENTION] Any chance of getting the 6.0.1 / MMB29M boot.img patched to allow traditional root rather than this systemless option. Many many thanks chaps :)
[Nexus 6P General] Heisenberg:
https://drive.google.com/open?id=0B98G0KTJwnBFWEFrdmF5WnBWN2c

I'm unable to, sorry.
[Nexus 6P General] mrRobinson:
Even if you use the systemless you can still chose to touch/modify system. You'll have full root. What is the point of sticking with system?
[Nexus 6P General] drothenberger:
If you're having problems with root apps not working correctly with systemless root (SuperSU 2.61), you can touch or manually create an empty file at /system/bin/su and/or /system/xbin/su and SuperSU will replace it with the real su binary on every boot. Essentially system root.

SuperSU 2.61 automatically patches the boot.img on install, so nobody has to create special boot.img files for each kernel, release, and device. Definitely an improvement. Try it out.
[Nexus 6P General] mrRobinson:
Yes, that's why I wondering why there are still requests for a modified boot.img on the latest version? Either I'm missing a reason or people think systemless can't modify their system? The apps that are broken on systemless the owner/maintainers should fix soon, and otherwise its easy for the user to address for now as you pointed out.

Edit: For those who feel they need it I guess: angler-mmb29m-boot.zip

Use with SuperSu 2.5.2

This should be the last one needed, I'll assume by the next update systemless will be even more mature and those broken apps will have updated.
[Nexus 6P General] GatorsUF:
I just updated my phone with the latest 6.0.1 system image files following the instructions provided. All I am getting is a bootloop. I've had similar problems in the past with updates and typically I have 2 options:

1. Loooong press power so the phone reboots and try again (this works sometimes)

2. If the reboot doesn't work I have to go into TWRP and wipe cache/dalvik (however the instructions told me to install stock recovery for now so I did)

As I typed this the reboot worked just fine, I let the boot screen run for about 10 minutes and the phone never booted so I long pressed the power button and restarted the phone. It booted right up and is not running through the "update process". In the future is there anything I can do in fastboot to increase the chances it will boot up the first time?
[Nexus 6P General] 89titanium:
I have SuperSU 2.56. That is systemless, right? Will it automatically patch the non-modified boot.img? Do I have to update SuperSU? I didn't see 2.61 when I did it only a few days ago...

When updating SuperSU, do I have to wipe cache/dalvik? What will this erase exactly?
[Nexus 6P General] cturbos:
I took the plunge and updated my phone to 6.01 manually,now I need root,any ideas?

Thank you
[Nexus 6P General] drothenberger:
2.56 doesn't automatically patch boot.img. You need 2.60 or 2.61 for that.

I'm not sure about wiping cache/dalvik, but it can't hurt. Erasing those two won't cause you to lose any data, but your phone will need to "optimize apps" during the next boot, which can take some time.

---------- Post added at 09:16 AM ---------- Previous post was at 09:15 AM ----------

Flash SuperSU 2.61 in TWRP. That's it.
[Nexus 6P General] jaidev.s:
How to create an empty file? Sorry for the noob question
[Nexus 6P General] drothenberger:
Personally, I used Root Explorer. I navigated to /system/xbin, then clicked the button at the top to remount /system as R/W. Then I clicked the + icon to create a new file.

You can also do it this way from a terminal window or adb:

su
mount -o remount,rw /system
touch /system/bin/su /system/xbin/su
mount -o remount,ro /system

After you create the files, you have to reboot so SuperSU replaces them with the correct su binary.

Chainfire (SuperSU dev) mentioned that 2.62 will be released today and it sounds like the new version may have options to do this with the application.
[Nexus 6P General] Smuvaan:
My N6p dosent ask confirm any action, it dosent ask anything. fastboot devices work*​
[Nexus 6P General] arrrgh:
Sweet, too bad google added the annoying warning after bootloader unlock
[Nexus 6P General] Smuvaan:
Thats i mean:

C:\SDK>adb devices
List of devices attached
CVH7N15B12003472 device

C:\SDK>adb reboot bootloader

C:\SDK>fastboot devices
CVH7N15B12003472 fastboot

C:\SDK>fastboot flashing unlock
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable

C:\SDK>
[Nexus 6P General] Heisenberg:
This means your adb/fastboot is out of date. I'm assuming by the C:\SDK in your command prompt that you installed adb/fastboot via the SDK? Open the SDK Manager program and update the platform-tools package.
[Nexus 6P General] Heisenberg:
You can't maintain root during an update. Just go to section 10 and flash the factory images to update, don't flash/format userdata. Then "fastboot reboot-bootloader" and flash TWRP again, then "fastboot reboot-bootloader" again and enter TWRP and flash SuperSU 2.61 for systemless root. Your camera will still work, I'm pretty sure the people whose camera stopped working were using traditional root and had flashed an outdated modified boot.img.
[Nexus 6P General] ycats:
Worked, however, my camera isn't working. I'm still on stock kernel.
[Nexus 6P General] Heisenberg:
Which images did you flash? Which SuperSU did you flash?
[Nexus 6P General] galaxy s4 nutjob:
Dumb question here when i download the factory image from Google it's a .tgz file how do i extract that. Windows doesn't give me an option to extract the files
[Nexus 6P General] ycats:
I used the images in step 10, from image-angler-mmb29m.zip..............flashed SU 2.61
[Nexus 6P General] Heisenberg:
I believe winrar can unzip them.

Try wiping data in TWRP.

PS. Please quote the post you're replying to when replying on XDA.
[Nexus 6P General] jimmyjohnIII:
Most folks are using 7zip these days.
[Nexus 6P General] ycats:
Was hoping to avoid wiping data.
[Nexus 6P General] cturbos:
Heisenberg

Since you're the BOSS here,and I/we love you for the work you're doing,please tell me if I flash the latest twrp-2.8.7.2-angler.img on 6.0.1,then flash the systemless root,will it be OK?Will I gain root? I'm root less now,stock 6.0.1.

Thank you
[Nexus 6P General] Heisenberg:
Yep, A-Ok.
[Nexus 6P General] cturbos:
Thank you.....
[Nexus 6P General] mobileman88:
Hi. Thanks for providing the commands. I think the last line should read

mount -o remount,ro /system

Just in case someone encounters any error.

su
mount -o remount,rw /system
touch /system/sbin/su /system/sbin/su
mount -o remount,ro /system
[Nexus 6P General] sirxdroid:
And the touch is wrong also, it should be:

touch /system/bin/su /system/xbin/su
[Nexus 6P General] DrSeussFreak:
I've said it before and I will say it again, you rock, thanks!
[Nexus 6P General] VanGolfer:
Hi: can you install the TWRP recovery only on locked & unrooted stock phone?
[Nexus 6P General] Heisenberg:
No, and yes. It must have an unlocked bootloader in order to flash anything to the device. You don't need root though, root has nothing to do with being able to flash, or with recovery.
[Nexus 6P General] drothenberger:
Thanks. I updated my original post. I also fixed the touch command.
[Nexus 6P General] VanGolfer:
I have Red Exclamation in Stock Recovery.. Every Time, see details:

http://xdaforums.com/nexus-6p/help/red-exclamation-stock-recovery-time-t3267539

How can I fix it?

---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------

Do I lost my date if I unlocked bootloader?
[Nexus 6P General] Heisenberg:
Yes, unlocking the bootloader wipes all userdata from the device. Are you holding power + volume up when you open stock recovery to bring up the menu?
[Nexus 6P General] tpthatsme:
Problem here. I was rooted with 6.0.0 with this wonderful guide and wanted to upgrade to 6.0.1. I followed the old 9 (that is the new 10) with the 6.0.1 factory image and didn't flash recovery or do anything with the userdata, but now I have the start up circles for about 25 minutes. Did I miss a step?
[Nexus 6P General] Heisenberg:
Were you decrypted before?
[Nexus 6P General] tpthatsme:
I am going to say yes because I followed part 3 originally to decrypt.
[Nexus 6P General] Heisenberg:
Your phone is encrypting your data, it'll take a while.
[Nexus 6P General] tpthatsme:
Dang it... Did I just screw it up? I rebooted a few times. It is still working on the circles, so if you say it will take a while, then I will leave it all night. Thanks for your help!
[Nexus 6P General] AndroidPurity:
Hi Heisenberg or whomever can point me in the right direction.

This is my first time going into stock recovery on my 6P, all of my experience before was with my Nexus 5. So forgive me if this is an obvious answer.

When I go into the bootloader, then go to recovery it just shows the little android guy with "no command." If I remember correctly the Nexus 5 went straight into several options of how to apply an update. From ADB or from storage and so on. Without having to do anything else before getting to those options after selecting recovery, right? I could be not remembering correctly.

Anyways from this point after selecting recovery for the 6P, what do I need to do to get to the 'sideload from adb' option? I tried clicking the volume and power buttons a couple different combinations to enter into a list of options to sideload but nothing happens except boating up eventually. Also yes I tried searching, and also no Heisenberg's awesome guide seems to imply stock recover should go striaght to those options? A little point in the right direction would be awesome. Thanks!
[Nexus 6P General] Heisenberg:
I'm only guessing but encryption seems like the obvious answer. If you're going to leave it overnight make sure you plug it in, interruption can cause data loss.

I think you need to hold power + volume up to enter the menu. Either that or hold power and click volume up repeatedly.
[Nexus 6P General] VanGolfer:
Yes I am able to bring up the recovery Android ICON with Red ! on top and stuck, NOT able to get to the recovery manu :(
[Nexus 6P General] imex99:
Flashed images, modified build prop for wifi tether, everything went good until 2nd boot and got this.... Anyone see this before?
[Nexus 6P General] ycats:
Try wiping data in TWRP.

I wiped data, camera still isn't working.
[Nexus 6P General] Heisenberg:
Sorry, but I have no idea.

You need to provide more info. Which images? Which boot.img?

You only flashed the MMB29M factory images and SuperSU 2.61? Nothing else?
[Nexus 6P General] imex99:
B29m but no root.... Reading that u need to flash vendor image? Some kind of new check with 6.0+
[Nexus 6P General] ycats:
You only flashed the MMB29M factory images and SuperSU 2.61? Nothing else?

That's it, and the latest TWRP as instructed. Any suggestions to get the camera working?
[Nexus 6P General] AndroidPurity:
Thanks! The tap of the volume up button did it!

But now I am getting "error: device '(null)' not found" when trying to side load. So clearly the stupid Google USB driver is having issues.

When the phone is started device manager shows "Android Composite ADB Interface." I have tried uninstalling and reinstalling the Google Driver using Android SDK but still no luck. It is version 11.0.0 driver, that is the most up to date right?

When I did "adb devices" command when phone was turned on it showed the serial number. Also fastboot devices shows serial number when in bootloader. However adb devices does not work in bootloader and fastboot devices does not work with phone on (not in bootloader). Not sure if that is intended but if I remember correctly my Nexus 5 showed the serial number for both commands regardless of whether phone was on or in bootloader. Which leads me to believe the driver is working at least partly. I have also tried unplugging and killing adb.exe process but still no luck. Any ideas?

I can sideload without ADB but I still need the driver to function properly of course because I need to unlock and root soon. Thanks!
[Nexus 6P General] tpthatsme:
Thanks for your continued support! I reflashed the whole process again and now I am back up and running on 6.0.1. Just to be clear, for root I would need to only follow sections 2,3, and 6. Thanks again!
[Nexus 6P General] Heisenberg:
You shouldn't need to if you're running the stock ROM, it's worth a try though.

I'm not sure, there's a thread discussing this in the q&a section though, have a look there.

Try booting into recovery with the cable connected, then disconnect and connect again, that might prompt your PC to get the drivers going.

Personally, I don't worry about decrypting anymore, there isn't really any benefit. But if you want to decrypt, yes, those steps are right.
[Nexus 6P General] ycats:
I'm not sure, there's a thread discussing this in the q&a section though, have a look there.

I noticed that I don't have root either. Should I reflash SU?
[Nexus 6P General] mobileman88:
Did you flash the modified boot? Flash the stock boot over it and it should work
[Nexus 6P General] GloriousGlory:
There's a bunch of threads, but I figure I'll post here. At first Camera didn't work but I was using an older version of SuperSU. Reflashed everything and now I seem to be losing root on 6.0.1 after every reboot (Used SuperSU2 2.6.1)
[Nexus 6P General] ycats:
Did you flash the modified boot? Flash the stock boot over it and it should work

point to the stock one, if you don't mind..............btw, what if I do a TWRP restore of a backup from 6.0?
[Nexus 6P General] imex99:
Vendor flashed, rebooted, pushed build prop edits and now no error....

The vendor file fixed this error and camera wasn't working but is now working!
[Nexus 6P General] Heisenberg:
I noticed that I lost root after one reboot, I rebooted again and it's been fine since then.

It's the one that you flashed from the factory images. So are you saying that you did flash a modified boot.img?
[Nexus 6P General] AndroidPurity:
Nope that did not work either.

Although I think I found the problem....

Just to summarize Device Manager displays the following when...

1.) Phone is on with USB debugging on = Android Composite ADB Interface

2.) Phone is on bootloader = Android Bootloader Interface

3.) Phone is in Recovery = Displays no device at all

4.) Phone has been selected to 'side load from ADB' = Displays under 'Other Devices' as Nexus 6p with yellow explanation mark.

I thought finally when I saw number 4. However trying to automatically install or install by browsing to file path C:\Users\Matthew\AppData\Local\Android\sdk\extras\google\usb_driver says the driver can not be found for this device. Despite the drive clearly being there. Looking at properties of the Nexus 6P device under Other Devices displays a Hardware ID for this state of the device as USB\VID_18D1&PID_D001\8XV5T15A20010668

Editing the android_winusb.inf file in there shows that the file does not contain USB\VID_18D1&PID_D001. So I added a line of the following to both sections for ;Google Nexus (generic)...

%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001

After doing that and trying to manually install the driver it finds the driver, attempts to install it but then errors with the attached screen shot.

I found this thread right here where adding that line resolved it for them, but seems this has not resolved it for me. Can someone please send me the exact android_winusb.inf file you have on your windows computer?

I have version 11.0.0 of Google USB driver from SDK, after uninstalling and reinstalling. There are no updates for it in Android Studio. So if I can get someone else's then hopefully that should resolve it. I just do not understand why only some people are having this issue. Google needs to update their damn driver, it is really ridiculous there is no updates in that file since 08/28/2014
[Nexus 6P General] GloriousGlory:
Not for me, it stays unrooted until I flash supersu again.
[Nexus 6P General] ycats:
It's the one that you flashed from the factory images. So are you saying that you did flash a modified boot.img?

I guess I'm confused as to which boot.img I need to flash, are you talking about the one I used for the initial rooting of 6.0? Are you referring to Step 7, if so, which of those do I use? And which SU?
[Nexus 6P General] Badger50:
The modified boot.img is needed if you want traditional system root using Su 2.52. If you want systemless root using Su 2.61, then you'll want the stock 6.0.1 boot.img.
[Nexus 6P General] ycats:
Still confused.
[Nexus 6P General] Ketawa:
Check the SuperSU WIP thread. If you are on any version of SuperSU before v2.60, you need to flash stock system and boot. Then, flash the SuperSU 2.62 zip (just released) in TWRP. It will patch the boot image for you.
[Nexus 6P General] 89titanium:
The earlier versions of the guide had a systemless version with 2.52. It needed special systemless boot images. Just saying...
[Nexus 6P General] kbapk:
Hi. I have a question. I want to flash custom ROM. I have root and custom recovery. For example I save ROM to device. When I will make full wipe it will be deleted or not from device?

And if I want flash 6.01 original. Now I have 6.00. Can I flash directly. Will my bootloader abdv recovery changed?
[Nexus 6P General] Wim!!:
What steps do I need to take to go from Traditional root 6.0 to systemless root 6.0.1?
[Nexus 6P General] 89titanium:
Since newest SuperSU uses stock images, does that mean it can take OTA updates?

Also, I currently have SuperSU 2.52 and systemless modified boot.img. If I want to update to 6.0.1, would I simply flash stock boot.img, then install SuperSU 2.61? Or the other way around....? Or are there other steps...
[Nexus 6P General] Ketawa:
I literally just wrote this a few posts before you.

"Check the SuperSU WIP thread. If you are on any version of SuperSU before v2.60, you need to flash stock system and boot. Then, flash the SuperSU 2.62 zip (just released) in TWRP. It will patch the boot image for you."

Also, there's no way you have systemless root with SuperSU 2.52.
[Nexus 6P General] 89titanium:
It's true man. Systemless root was around before 2.62.

Any news on if OTAs will be doable in the future?
[Nexus 6P General] Heisenberg:
That's true but what he's saying is that 2.52 isn't a systemless version of SuperSU.
[Nexus 6P General] tpthatsme:
I can not flash TWRP for some reason. My bootloader is unlocked and last night I flashed stock 6.0.1. I follow the direction in section 2, but when I reboot the bootloader, it is still Android and not TWRP. Any ideas what I am doing wrong?
[Nexus 6P General] ^tyrant^:
If i follow the instructions to take the OTA 6.0.1 update, will flashing the system.img wipe out all my apps ?
[Nexus 6P General] Heisenberg:
What version of TWRP are you flashing?

No, apps reside in the data partition.
[Nexus 6P General] tpthatsme:
I'm a big dummy... recovery mode... duh.
[Nexus 6P General] ^tyrant^:
Thanks for the quick answer, just want to cover all my bases here.. since I am debating whether to take the OTA or not, I still need to install the newest SU also.. so im thinking of knocking both out at the same time.

Prep for OTA.

Take OTA

Flash TWRP

Flash SuperSU 2.62

I also have xposed installed anyone know if there is any problems with it and 6.0.1? or putting it back on after the OTA?