yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Q&A, Help & Troubleshooting] madbat99:
You need a permissive kernel.

---------- Post added at 07:16 AM ---------- Previous post was at 07:14 AM ----------

And you can stop calling it m now. It's marshmallow. "M" was the name of a developer preview of an unnamed version of Android. Is that what you're trying to root? Lol. Not likely. Marshmallow it is!
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Edited!

The good news is Chainfire(+New Team) or working on another method to root!

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 Which no longer has the possibility of causing a factory reset on encrypted devices!
[Nexus 9 Q&A, Help & Troubleshooting] VermontKindBud:
Link to new method is a 404 error
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Thanks, just put the correct link in!
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Stickmount has now been updated to work with MarshMallow!
[Nexus 9 Q&A, Help & Troubleshooting] jib@rmi.ge:
Not **quite** working. Have installed TWRP 2.8.7.0, Supersu beta 2.51 and ElementalX 4.01 kernel; was able to install adbd insecure, so adb goes root and I can su from shell there.

Still when booting into recovery, TWRP asks for password, and if I cancel cannot mount anything but cache. Supersu seems to grant SOME permissions but for example I cannot modify default.prop (neither from the device nor via adb - the latter says about read only file system).
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Use chainfire's method to root!

TWRP needs to be update. or follow these instructions to no-forceencrypt your device.
[Nexus 9 Q&A, Help & Troubleshooting] flar2:
I use Chainfire's method in EX 4.01

EX always rooted "properly"

There was no system write on the initial release. But encryption was always handled properly. Please dont spread misinformation
[Nexus 9 Q&A, Help & Troubleshooting] jib@rmi.ge:
The latter instructions helped - Chainfire's did not mention that I should wipe data after booting into twrp. Now it seems ok - at least twrp does not ask for passwords anymore. Btw I looked into default.prop and there one still has

...
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
...
ro.adb.secure=1
...
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Edited: Sorry! I used an old version of the kernel and now have updated my posts to reflect this and also provide a link to the updated kernel! Its a pity that the online guide i linked still points to the old version!
[Nexus 9 Q&A, Help & Troubleshooting] Taomyn:
I have an LTE N9, but I cannot get Chainfire's method to work - TWRP keeps asking for a password which when I enter correctly says is not valid. If I boot normally I can enter my password for the encryption and the tablet continues ok so I know the password is good.

I installed the volantisg boot image, TWRP 2.8.7.0 then restarted in recovery. This is exactly the same thing I did for my Nexus 6 and it went fine.

Any ideas?
[Nexus 9 Q&A, Help & Troubleshooting] madbat99:
Format data in twrp. You're still encrypted.
[Nexus 9 Q&A, Help & Troubleshooting] Taomyn:
Yes, I just found out that TWRP is not working with encryption on the N9, even though it works with the N6. Will have to hope they fix it soon.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Nexus 9 twrp-2.8.7.1-flounder now available and works on encrypted device!

See XDA thread!
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Nexus 9 wifi (MRA58N) boot file (system root) now available.
[Nexus 9 Q&A, Help & Troubleshooting] cancertoast05:
TWRP can't proceed because SU zip files aren't present (NRT says there should be files and folders for /sdcard/!readytoflash/Root_files) Neither that folder path, nor any SU files exist.

I have Marshmallow 6.0 installed on a Nexus 9 that is unlocked.

Any help? Im rusty in regards to rooting Android devices so I am quite confused.....

ed:

NRT is using TWRP -2.8.6.0-flounder.img. Tomorrow I will dl 2.8.7.1 via my tablet, then attempt again.

ed 2: That likely wont work because I still dont have the SuperSU files it is asking for.... smh...
[Nexus 9 Q&A, Help & Troubleshooting] madbat99:
You have to flash chainfires modified boot image, then supersu beta 2.52. That is the only way to root marshmallow.
[Nexus 9 Q&A, Help & Troubleshooting] cancertoast05:
Care to walk me through the steps using wugfresh nrt? I'm wary of bricking myself. I've already unlocked so I'm almost there!
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
There is two methods to root.

First method: -

Use a modified boot kernel available from here for MRA58K and MRA58N

Also get Nexus 9 twrp-2.8.7.1-flounder img and the latest SuperSu Beta

Put Supersu on your device somewhere you can find it latter in TWRP.

With the advanced utilities of NRT "Fastboot Flash" both the Boot (Kernel) and Recovery in turn.

Once that is done boot your device in recovery mode and use that to install SuperSu from the location you put it earlier!

Hopefully enjoy a rooted device!

Second Method

Using ElementalX kernel. Flash TWRP as above and then from Recovery Flash ElementalX kernel (linked in op) first and then supersu
[Nexus 9 Q&A, Help & Troubleshooting] v12xke:
Anyone have the N9 LTE (Volantisg) modified boot.img for MRA58N? Because I am stock, unencrypted and wish to stay that way, this file is always seems to be the hold up for me. Could I just:

a) use the existing CF modified boot.img from MRA58K or

b) d/l a custom MRA58N ROM and extract their boot.img and then flash it with the other Google image files? (bootloader, system, vendor, modified boot, SU v2.52)

Edit:

Coming from MRA58K rooted, I flashed individually the following: bootloader, system, vendor, ElementalX 4.03, Super SU v2.52. Up and running MRA58N, still rooted, no issues. I would still like to know how to modify the stock boot.img to disable forced encryption every time.
[Nexus 9 Q&A, Help & Troubleshooting] cancertoast05:
System and vendor are? Sorry for the noobishness.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
I don't know how to modify the boot.img either, but chainfire usually provides them soon after the release of the factory image, going by his post's in supersu thread he is currently away(or on holidays for a while).

The ElementalX kernel also disables the force encryption. (I believe since it also modifies the boot image).

System is the partition of you device where the majority of the operating system is stored!

Vendor is another partition (introduced with Nexus 9, the newer nexus 5X and 6P also have it.)

Full list of partitions when flashing a factory image are: - Boot [Kernel], Bootloader, Radio (for devices with LTE/4G, phones etc), Recovery, System, Userdata (don't flash if you want to keep data and apps) and finally vendor (for devices that have it)

When I was updating MRA58K to MRA58N, I only flashed system and vendor.
[Nexus 9 Q&A, Help & Troubleshooting] v12xke:
Thanks for your reply. I'm looking at Fed Patcher now over here. For (already encrypted users) it looks like you just put the zipfile in the root before fastboot flashing the appropriate .IMG files, then reboot to recovery (before booting) and now flash FED Patcher which modifies the factory boot.img , and then Super SU. Looks like I/we now have a way to quickly update the N9 (LTE or Wi-Fi) every time a new security update comes out. Also works with the N6 (Shamu).
[Nexus 9 Q&A, Help & Troubleshooting] jamesalfred:
Did you succeed with that? As I recalled, the author says that FED Patcher won't work with SuperSU 2.50+. It's a problem with the SELinux working on "enforced" mode or something. Basically, if you're using the patch alongside with SuperSU, you'll end up with infinite boot loop, because current version of SuperSU requires SELinux to work properly, and the patcher basically removed it from the boot.img.

EDIT: link to the post http://xdaforums.com/showpost.php?p=63601246&postcount=9
[Nexus 9 Q&A, Help & Troubleshooting] cancertoast05:
So my nexus 9 refuses to boot into recovery. I hold volume up + volume down + power and it loops the google logo ever 6 or so seconds until I let go, then it boots the os. One time it booted the os with the words SAFE MODE in the bottom left corner. Any ideas as to what the hell is going on? I have tried this while the tablet is plugged into the pc, and while the tablet is unplugged. I get the same result every time. I know it is not an issue with the volume +/- buttons, as they work just fine in Android.
[Nexus 9 Q&A, Help & Troubleshooting] v12xke:
No, I did read that but I had already updated mine to RMA58N using EX kernel so I have not tested FED Patcher yet but I will next update. He is working on it pretty actively. I also did not try CF's boot.img for RMA58K which would probably have worked. The most important thing for me about the FED Patcher is that my data not accidentally become encrypted on first boot. Once the ROM is installed I can always go back and fix root, even if I have to flash a custom no-force encrypt kernel. In the past I have been dependent on others for the latest modified boot.img which usually comes out a week or two after the official Google images. Now I can modify the factory boot.img to not encrypt and flash as soon as the Google images are out.... or just revert to what worked this time. Fastboot flash bootloader, vendor, system, EX Kernel, SU v2.52.

I would first try wiping cache and erase/flash recovery.img. If you aren't comfortable with Fastboot you can use Wugfresh's toolkit. Start the toolkit then reboot phone to bootloader. There you can wipe cache, temp boot TWRP or perm flash any recovery or kernel including stock. I would also strongly recommend USBhost's modded version of TWRP as your recovery. It is much faster and has a super GUI. You can find it here.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
The correct combination for Nexus 9 is Power + Volume Down.

Which will bring you to the bootloader and from that you can select to boot recovery.

Also in the advance utilities of NRT in quick tools you have the option to boot recovery.

If the above doesn't work, try re-flashing the recovery image.
[Nexus 9 Q&A, Help & Troubleshooting] cancertoast05:
edit: ^^ Thank you.

Thank you all for your help. Now all I have to do is install ElementalX kernel (which I will do through the app.) Then wait for DU to officially support 6.0.

Question though. Once I install the ElementalX kernel, that will permanently be there, no matter which roms i am flashing? Or will I have to reinstall the kernel everytime I try a different rom, whether that be stock or some other variety?
[Nexus 9 Q&A, Help & Troubleshooting] v12xke:
No, the kernel will not be there permanently. ROMS will over-write the existing boot partition with their own kernel (boot.img). You can flash a kernel even before you boot. Lots of people flash a ROM, then GAPPs if needed, then kernel of choice, then SU sequentially before booting for the first time (queued in TWRP). Once you can boot into a working custom recovery, you can flash any kernel you want. In fact the NRT toolkit will allow you to "temp" flash a kernel or recovery and try it out, and when you reboot it will be gone. There is a very recent version of NRT v2.06 that was just released by the dev Wugfresh. Be aware that in general you should not flash ROMS over custom kernels. You may end up in a boot loop. It's easy to flash back to the stock kernel, especially if you have an app like Flashify or Rashr.
[Nexus 9 Q&A, Help & Troubleshooting] sirxdroid:
For MRA58N and systemless root, which modified boot.img do we use? And is SuperSU-v2.56-20151030013730 OK to use?
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
If you checked the SuperSu Thread it is available here

Plus you need to use version 2.56 of supersu for it to work.

Haven't tried it myself as it is still very experimental and don't see the need for it yet (Useful for people with android pay, but on nexus 9 don't think so.)

Re-flashing boot just to take an OTA, when factory images are available?
[Nexus 9 Q&A, Help & Troubleshooting] sirxdroid:
Thanks. I did check but only found the one for system root, missed this one for systemless.

---------- Post added at 01:16 PM ---------- Previous post was at 12:54 PM ----------

If you go the /system way for root, it is OK to let TWRP install SuperSU when it prompts? Does it install the correct version and does it fix the ramdisk too? Or TWRP hasn't been updates to support root install on Android M?
[Nexus 9 Q&A, Help & Troubleshooting] v12xke:
Sorry, I don't use systemless. I use SuperSU v2.52. I believe since I fastboot flash select partitions, then a kernel that supports root and no-force-encryption, then Super SU, I don't see that message... maybe once but I do not allow TWRP to write to /system, and no TWRP doesn't do anything to ramdisk. Once I fully boot the first time I am already rooted and don't see that message anymore. Since TWRP was recently updated you should make sure you are using the latest version especially if you are encrypted), or the modded version I linked to earlier.
[Nexus 9 Q&A, Help & Troubleshooting] sirxdroid:
OK, switched to the /system version because ES File Explorer doesn't work with the systemless one. No good reason to have systemless anyway as you need to make more modification to /system, things like hosts file for ad blocking, busybox, other apps that need to be installed in /system, etc.

And yes, I have the latest TWRP and SuperSU 2.52, just got the N9 yesterday so going through all the setup, upgrade to M, rooting, etc. Things have changed as it is usually the case with a new Android version, I have some catching up to do.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Added a link to system-less boot file in OP for others probably looking for it!
[Nexus 9 Q&A, Help & Troubleshooting] cancertoast05:
I have noticed that my 16gb Nexus 9, after rooting shows a storage size of 10.75 GB, it used to say 11.05 GB of storage. Any clues?

I
[Nexus 9 Q&A, Help & Troubleshooting] Taomyn:
Not true. On systemless you put BusyBox in /su/bin and create a bind mount for hosts in /su/etc then neither will be in /system. How to do this can be found in the SuperSU beta thread.
[Nexus 9 Q&A, Help & Troubleshooting] Taomyn:
Has one for the LTE version been created?
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Haven't seen them posted yet on SuperSu thread.
[Nexus 9 Q&A, Help & Troubleshooting] sirxdroid:
Yes but if you simply install various apps they don't yet work like that, or even work at all, ES File Explorer for example. Once all apps are fixed to support systemless root, sure it makes sense, but until then it's a pain to fix them all by hand, then a pain to upgrade them, etc.

Maybe some day we will get overlay/union fs for /system which I think is a nicer solution.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Updated ElementalX kernel - no longer needs modified CF boot images

For people using ElementalX

Updated ElementalX 4.04 kernel - no longer needs modified CF boot images.

See the flar2's post here

For people with LTE model, you can root without needing boot images as the kernel will have the changes required!
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Modified Boot Images available here for the LTE model.

Thanks to topjohnwu.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
6.0.1 (MMB29K) Factory Image Now Available.

I successfully update my Nexus 9 and flashed ElementalX Kernel and Systemless SuperSU v2.61
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
SuperSU v2.62 now available.

Update: SuperSU 2.62 now available with more support for root apps. Example "ES File Explorer's Root Explorer" now works.

If you flashed 2.62 over 2.61 you may need to reflash(or update) ElemetalX kernel again if you use the app to update it.
[Nexus 9 Q&A, Help & Troubleshooting] jib@rmi.ge:
Just could not resist

Result:
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
SuperSU v2.64 Beta now available.

If your using ElementalX, you will probably have to reflash that again after SuperSU.
[Nexus 9 Q&A, Help & Troubleshooting] waffleb051:
Anyone else getting a bootloop or is it just me?

Flashed the TWRP, latest beta SuperUser, Flashed ElementX but I am still bootlooping.... Im confused about what could be doing this. Could it be that I didnt flash the modded boot image?
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
You don't need a modified boot image with latest SuperSU V 2.64 beta (and/or ElementalX) because these will modify the boot.img when been installed.

Few things to consider are:

Had you previously been rooted with a system root? - Make sure to flash stock boot.img, system.img and vendor.img first.

Did you allowed TWRP to attempt to install it's SuperSU? - This has been strongly advised against in Chainfires linked post.

Was there any errors reported while flashing SuperSU?
[Nexus 9 Q&A, Help & Troubleshooting] waffleb051:
No errors reported while installing. I got it to work by flashing the modded boot image. Right now I am working on fixing the fact that it thinks it is wireless charging and the fact that the radio stack crashes. I think the radio stack problem is from xposed though so that is an easy fix.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Where did you get a modded boot image for 6.0.1 [mmb29k], I did not see anyone releasing them.

If your using a modded boot image for an earlier factory image, that may cause you problems.

Radio Stack I assume you have the LTE model?

If you cannot resolve your problems, I would consider flashing back to the stock factory image (can be done without wiping data) and follow the steps again to root etc.

Maybe doing it in stages, only do this if your device is still encrypted

Flash Stock and Boot up the device.

Flash SuperSU and Boot up the device.

Then ElementalX.

If it causes a boot loop, you will know when.
[Nexus 9 Q&A, Help & Troubleshooting] waffleb051:
That is something I didnt do. I went back to stock so this is a clean image. I'll reflash the whole lot and start over.

---------- Post added at 03:27 PM ---------- Previous post was at 02:38 PM ----------

It fails at the super user flash. And yes I do have the LTE version.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Maybe try an earlier BETA-SuperSU-v2.62-3 for example.

Also post this in Chainfires SuperSU Beta thread for possible more assistance.

Posting as much detail as possible (eg device, lte and android versions etc)
[Nexus 9 Q&A, Help & Troubleshooting] waffleb051:
I'm going to try wiping the whole device again this time starting over from 0 as if it where a new tablet then build from there. I went back to stock but it didn't erase everything like usual so I'm thinking that could be part of it.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
SuperSU v2.65 Beta now available.

Thanks to Chainfire posting over the Xmas Period!

Did you resolve your Boot-loop?
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
SuperSU v2.66 Beta Now Available.

SuperSU v2.66 Beta Now Available.

Chainfire's Post.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Nexus 9 6.0.1 (MMB29S) successfully rooted with 2.66.

Nexus 9 6.0.1 (MMB29S) successfully rooted with 2.66.

Hopefully kept my system untouched by using AdAway Systemless Host, Busy Box installed into /su/xbin/ using this app and only booted TWRP instead of flashing it.
[Nexus 9 Q&A, Help & Troubleshooting] sejmand:
Am I right?

coming from nexus 9 wifi volantis_6.0.1 MMB29K, SuperSU-v2.62-3-20151211162651, ElementalX-N9-4.05 und twrp-2.8.7.1-flounder

to get MMB29S had to:

- flash boot.img, vendor.img and system.imgfrom MMB29S

- Reboot to recovery flash BETA-SuperSU-v2.66-20160103015024

- cache- andd dalvik-WIPE

- boot system

- install ElementalX-N9-4.05 from recovery or with ElementalX-app
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Sounds fine. You could flash ElementalX Kernel zip after you flash supersu, since your already in recovery.

Although Flar recommends booting the system before flashing the kernel.
[Nexus 9 Q&A, Help & Troubleshooting] sejmand:
I did it and it works without problems

MMB29S with twrp, superuser2.66/root and ElementalX
[Nexus 9 Q&A, Help & Troubleshooting] searingxheretic:
No Command?

Greetings, could use a bit of advice. I was attempting to install TWRP for the first time using adb/fastboot. It seemed like twrp flashed fine using fastboot, I got an "Okay" message at the end of the flash. When restarting and choosing recovery in the bootloader, it takes me to a dead android guy and says "no Command". I have tried re-flashing twrp a few times, with the same result. Any help is appreciated.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
If you see the above, you still have stock recovery.

Once you flash TWRP, you need to boot into it first before booting up the system or it will be overwritten with stock recovery.
[Nexus 9 Q&A, Help & Troubleshooting] searingxheretic:
Ha, that did it. What a stupid oversight on my part, although i didn't see that step listed in any tutorials, everything just said reboot. Thank you for your quick reply, it saved me just a few grey hairs.

---------- Post added at 09:43 PM ---------- Previous post was at 09:21 PM ----------

So, as a follow up question... I booted into twrp fine, completed a nandroid backup, booted into system, then tried to reboot back into recovery and it was gone. Does the system wipe it out every time you boot into system? So you have to continually reinstall twrp every time you want to use it?
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Once you flash it and boot into the flashed versions. It should stick and not need to be flashed again.

How did you boot TWRP? If you used "fastboot boot <twrp.img or whatever it is called> " you weren't using the flashed version on your device.

Steps to follow.

Flash TWRP.

Shutdown.

Boot up the bootloader and from there boot recovery (hopefully TWRP this time).

Alternatively after flashing twrp, use this comand "adb reboot recovery" and you should boot into the flashed TWRP.

NRT provides a "PERMrecovery.zip" that can be flashed if you use that method to install twrp.

I can not verify on my own device at this time, because I'm testing systemless root. And to remain stock, I have only temporarily booted twrp when needed instead of flashing it. Hopefully to accept the February OTA.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
SuperSU v2.67 Beta now available.

SuperSU v2.67 Beta now available.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Suggestion: Try out Chainfire's app Flashfire.

If you have a completely stock system image, which hasn't been touched by a root file manager/TWRP.

Chainfire's Flashfire app should be able to apply the OTA even with a modified kernel, as it restores the stock boot and recovery images.

v0.50 released

Keep your system untouched by using AdAway Systemless Host, Busy Box installed into /su/xbin/ using this app and only booted TWRP instead of flashing it.

Stericson's Busybox app can now install to /su/xbin as well, but not by default.

Although Flashfire will restore stock recovery before flashing OTA's so twrp can be flashed as well now.
[Nexus 9 Q&A, Help & Troubleshooting] SanjesvhYogesan:
Hey guys,

If I were to update my Nexus 9 using Chainfire's Flashfire app, would I be able to do so if I was completely stock with some Xposed modules installed like Gravity Box, Greenify, etc? Or does Xposed modules consider as modifying the system????
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Xposed modifies the system, so OTA's updates by Flashfire will fail.

You could use Flashfire to Flash Factory Images.
[Nexus 9 Q&A, Help & Troubleshooting] SanjesvhYogesan:
Thank you very much for your help.:D:D
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
6.0.1 (MOB30D) - April Security Factory Images are up.

Attention: They just removed the images for: Nexus Player, Nexus 9 wifi, Nexus 7 (2013 WiFi), not sure what's up

As of 11 April, the above images have now been restored to the page.

Successfully used FlashFire to update my Nexus 9 with 6.0.1 (MOB30D) Factory Image.

Only flashed Boot, Vendor and System.

First Boot stalled at Black Screen

Manually rebooted and all was okay.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
6.0.1 (MOB30D) - Is back up for Nexus 9 Wifi.

It has the same MD5 Checksum as last weeks version, so don't know why they where removed!