Root

[larry_walker]

will this method still work on the current 6.0.1 build MMB29R?

 

[corkiejp]

will this method still work on the current 6.0.1 build MMB29R?

Just flash the latest systemless supersu.zip in TWRP.

 

[PieceKeepr]

I just got a used, but really nice, Nexus 9 and I'm getting ready to root it and flash a custom rom. From what I've read the process for the Nexus 9 looks like...

Activate developer mode
Turn on Enable OEM unlock
Turn on USB debugging
Flash the "NEW: CF-Auto-Root flashable" at the top of the OP (I'm assuming you flash this as a zip and not just the img file?)
Flash BETA-SuperSU-v2.72-20160510112018.zip
Flash TWRP
Flash ROM

Have I got this right or am I missing something? I'm new to the Nexus 9 and the process is different from the HTC devices I've owned and I want to make sure I'm right so I don't screw it up.

Thanks.

 

[corkiejp]

I just got a used, but really nice, Nexus 9 and I'm getting ready to root it and flash a custom rom. From what I've read the process for the Nexus 9 looks like...

Activate developer mode
Turn on Enable OEM unlock
Turn on USB debugging
Flash the "NEW: CF-Auto-Root flashable" at the top of the OP (I'm assuming you flash this as a zip and not just the img file?)
Flash BETA-SuperSU-v2.72-20160510112018.zip
Flash TWRP
Flash ROM

Have I got this right or am I missing something? I'm new to the Nexus 9 and the process is different from the HTC devices I've owned and I want to make sure I'm right so I don't screw it up.

Thanks.

CFAR linked at the star of the thread is an old version. Plus you don't need it. If you are using it, you extract the zip on a computer and run the script while in fastboot with your device attached to your computer. Get the most recent from here

Flashing SuperSU in TWRP does the exact same as the above. So you need to flash/boot TWRP to flash supersu.

 

[jagruk]

Stuck on bootloop after rooting

I just rooted my Nexus 9 using this method
Now it's stuck on the boot animation.
I had previously flashed the Android 7.0 ota image. Is that what's causing it?
How can I fix this?

 

[corkiejp]

I just rooted my Nexus 9 using this method
Now it's stuck on the boot animation.
I had previously flashed the Android 7.0 ota image. Is that what's causing it?
How can I fix this?

Flash stock boot image from the factory image of the version your on! And try rooting again if it boots.

 

[Topazzar]

I have the same problem as above.
I have unlocked the bootloader using ADB and flashed the Nexus 9 SuperSU (inject.img & patched.img) and now my Nexus 9 won't boot to the OS.
I then tried a Factory Reset and it never gets passed the 4 dots animation.
ADB doesn't recognise the device anymore either.

How do I put an image onto it now?

EDIT: I sorta figured it out. I got into recovery (I haven't got a custom recovery installed!) and selected 'apply an update from ADB' now 'adb devices' recognises the tablet in 'sideload mode'.. Every time I push an image though, it fails with 'E: signature verification failed' on the tablet. I ran the Test Mode command on my Windows 10 machine and rebooted. Sure enough, it now says Test Mode in the bottom right hand corner of the desktop wallpaper, but I still get the E: signature verification failed message on the tablet.

I have no OS so I can only flash and image or custom ROM using ADB at the moment. I can't run it up an install Flashify. Wipe and factory reset doesn't work.

 

[fhem]

I have the same problem as above.
I have unlocked the bootloader using ADB and flashed the Nexus 9 SuperSU (inject.img & patched.img) and now my Nexus 9 won't boot to the OS.
I then tried a Factory Reset and it never gets passed the 4 dots animation.
ADB doesn't recognise the device anymore either.

How do I put an image onto it now?

EDIT: I sorta figured it out. I got into recovery (I haven't got a custom recovery installed!) and selected 'apply an update from ADB' now 'adb devices' recognises the tablet in 'sideload mode'.. Every time I push an image though, it fails with 'E: signature verification failed' on the tablet. I ran the Test Mode command on my Windows 10 machine and rebooted. Sure enough, it now says Test Mode in the bottom right hand corner of the desktop wallpaper, but I still get the E: signature verification failed message on the tablet.

I have no OS so I can only flash and image or custom ROM using ADB at the moment. I can't run it up an install Flashify. Wipe and factory reset doesn't work.

When you go into bootloader using power and vol dn buttons you are in NOT in fastboot mode. HBOOT and FASBOOT are both highlighted blue.
At this point you need press the power button. This will put you into fastboot mode. FASTBOOT should now be hi-lighted red. At this point I would fastboot erase/format all and flash back to all factory and start over.
Good luck. Hope this helps.

 

[Topazzar]

I have done that. When connected to the PC it says FASTBOOT USB, That's how's how I did the fastboot oem unlock to unlock it with ADB

I did a factory wipe just over an hour ago and it's still on the 4 dots animation, but I've downloaded the Google Factory 7.1.1 (December 2016) image - NMF26F (previously on NRD90R)

EDIT: Stock ROM installed, cheers

EDIT2: Still having issues rooting this thing. The bootloader is unlocked but after flashing the rooting images (actually, I used rootjunkys batch file method) it just never boots into the OS again!

 

[fazbender]

I have done that. When connected to the PC it says FASTBOOT USB, That's how's how I did the fastboot oem unlock to unlock it with ADB

I did a factory wipe just over an hour ago and it's still on the 4 dots animation, but I've downloaded the Google Factory 7.1.1 (December 2016) image - NMF26F (previously on NRD90R)

EDIT: Stock ROM installed, cheers

EDIT2: Still having issues rooting this thing. The bootloader is unlocked but after flashing the rooting images (actually, I used rootjunkys batch file method) it just never boots into the OS again!

Those root files look to be over 2 years old. What android build did you first use it on?