• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Root

Search This thread

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,442
87,712
www.chainfire.eu
NEW: CF-Auto-Root flashable: http://download.chainfire.eu/595/CF-Root/CF-Auto-Root/CF-Auto-Root-flounder-volantis-nexus9.zip

Will update this post soon-ish!

--- old post follows ---

This took a few hours more than I had hoped, because it's both the first firmware on a new Android version as well as 64-bit. While there have been 64-bit builds of the SuperSU binary for a while now, they were untested until now, and unsurprisingly there were a few (minor) issues to fix before it worked properly.

As such, this root includes SuperSU v2.18, which is a special build for the Nexus 9, which you should definitely not try to put on any other device, nor should you put an older version of SuperSU on the Nexus 9.

I have not yet updated the CF-Auto-Root framework to be able to patch the kernels live (needed on 5.0) or support 64-bit, so this is a more manual root than usual.

It pretty much comes down do:
- enable oem unlocking in Android's developer options
- fastboot oem unlock
- fastboot boot inject.img
- fastboot flash boot patched.img

The included README.TXT is a little bit more extensive, but not by much, and if you don't know what the above does then maybe you shouldn't bother (yet).

Please note that many root apps will have issues with both Android 5.0 as well as 64-bit. There may also be more issues with SuperSU on 64-bit that I have not found yet.

Guess it's time to fix up CFAR and update the new How-To SU with all the 5.0 specifics. That'll all take some time, though.

^^^ from my G+

Download:
http://download.chainfire.eu/592/CF-Root1/Nexus9-root-SuperSU-v2.18.zip
 
Last edited:

leviwhite9

Senior Member
Nov 11, 2011
158
11
Buckhannon
Can't get it to work...

Booted both images just as instructed. Then first full boot after booting the images, it won't accept touch at the encryption screen. Hold the power button then it reboots and boots fine. Open SuperSU app and it says no root binary... I'm still fidgeting with it.
 

renzyyy

Member
Aug 6, 2010
38
28
Milwaukee, WI
renzy.land
Booted both images just as instructed. Then first full boot after booting the images, it won't accept touch at the encryption screen. Hold the power button then it reboots and boots fine. Open SuperSU app and it says no root binary... I'm still fidgeting with it.

had the same issue. went back to the stock boot.img, disabled security and set to swipe, reflashed inject.img & patched.img. worked good, turned security back on but didnt choose to enforce on start up. guessing might be an issue with that..? havent tried with that re-enabled.
 

leviwhite9

Senior Member
Nov 11, 2011
158
11
Buckhannon
had the same issue. went back to the stock boot.img, disabled security and set to swipe, reflashed inject.img & patched.img. worked good, turned security back on but didnt choose to enforce on start up. guessing might be an issue with that..? havent tried with that re-enabled.
That was the issue! Turned off security and rebooted the two images and I had SU access. Turned pattern lock with boot enforcement and it broke SU. It is the boot time security that breaks this.
 

eurominican

Senior Member
Apr 25, 2008
647
228
That was the issue! Turned off security and rebooted the two images and I had SU access. Turned pattern lock with boot enforcement and it broke SU. It is the boot time security that breaks this.

Also, for anyone that missed this or didnt know about it (like me), you have to tick off "Enable OEM unlock"

Screenshot_2014-11-04-21-27-50.png
 
  • Like
Reactions: raakaysh

Sean09

Senior Member
May 6, 2008
795
195
Nice work! Seems to work well so far - now as others stated I just need busybox - seems Titanium Backup is not detecting root and needs it? Or TB could be incompatible.
 

Top Liked Posts