yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Original Android Development] aiah:
Thanks for the quick reply.

You are right, waiting for and manual flash 5.1.1 is the way to go.

PS:

can i skip erasing / flashing recovery to ? (sinds i already have TWRP)
[Nexus 9 Original Android Development] ganGeee:
5.1.1?

New to nexus and have been out of rooting business for a while due to verizon's knox.. CURSE YOU VERIZON!!! anyways, will this rooting method work on 5.1.1 update? Thank you.
[Nexus 9 Original Android Development] fhem:
Have you unlocked bootloader and fastboot flashed twrp? If yes just install supersu 2.46 zip from twrp ------>root
[Nexus 9 Original Android Development] ganGeee:
Thank you
[Nexus 9 Original Android Development] dusko_m:
does this method work on 6.0?
[Nexus 9 Original Android Development] v12xke:
6.0

No. Go here. You need SuperSU 2.52 and either Chainfire's boot.img or a custom kernel that supports it. Flash the boot.img or kernel FIRST, then SU.

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[Nexus 9 Original Android Development] mr_magreb:
How can I know which kernels support this project?
[Nexus 9 Original Android Development] 850RPM:
Try ElementalX
[Nexus 9 Original Android Development] Debizzle:
Guys please help!! So Im currently running 6.0 when doing this and I followed all the instruction everything went fine. I got the red android it reboots. Now I get "Your device is corrupt. It can't be trusted and may not work properly." and it just set at the splash screen. I have have put the my nexu 9 in fastboot but my computer is no longer seeing it as a device when I look at "adb device". Can someone please help me getting my tablet back operational? THanks
[Nexus 9 Original Android Development] corkiejp:
Try "fastboot devices" while in that mode.
[Nexus 9 Original Android Development] EniGmA1987:
It is "Fastboot devices". Not sure if leaving off the s will work too but just thought Id put the proper command here. That works when in fastboot/bootloader. "adb devices" should work when the device is in recovery and when booted in the rom.
[Nexus 9 Original Android Development] Debizzle:
For some reason fastboot is not working . When I run any fastboot command I'm getting the "fast boot" command not found. But I have the fastboot .exe file in the folder . Doesn't the computer have to see the tablet in order for the commands to work?? Man I hope I can get this tablet recovered I just bought it . Sad I know!!
[Nexus 9 Original Android Development] dictionary:
When you get that prompt, you should still be able to boot the device. There is a link or button I think that you can press that says boot anyway, or something along those lines.

As far as fastboot, are you positive you're in the right folder? Also, have you tried to disconnect the device, and then open up a new terminal, and reconnect? Are you sure you're on the bootloader?
[Nexus 9 Original Android Development] Debizzle:
THank you guys for trying to help me. I had to put my thinking cap back on, its been a while since I have done any mods. Im all rooted and booted, and My N9 is blazing!!!
[Nexus 9 Original Android Development] prdog1:
Adb devices does not show in fastboot. Fastboot devices should if everything is right. Adb devices shows when within the OS, recovery and memory. Sounds like the fastboot setup. Maybe open the command prompt in admin mode. Sometimes a PC reboot. Could be anything. I am set up with latest full SDK and the path variables set so I just open the prompt and it all good. Win 8 and 10 were funny with the Google driver when the N9 first came out. :cool:
[Nexus 9 Original Android Development] Giants2010:
What did you do? same problem
[Nexus 9 Original Android Development] Debizzle:
Instructions

So the interesting thing is the process actually did what it said it was going to do which was unlock the bootloader, at least for me it did. The thing is Marshmallow doesnt like the state it will be in because of some inner permission issues, which cause it not boot up.

So first thing first is making sure your computer is talking to the device.

Get the tablet in the boot loader by pressing power button and holding the up volume key until u see the menu.

Next, make sure fast boot is selected.

Next run the command "fastboot device" and it should pull up some info about your device, i think it will be the serial number.

IF that is successful, now you can start flashing stuff.

You need to flash the system.img for your particular Nexus 9, in my case I have the 32g lte version make sure you find the one for your variant.

Next will be flashing a recovery which needs to be the latest TWRP for nexus. https://twrp.me/devices/htcnexus9.html

Next you need to install ElementalX kernel from TWRP. https://www.androidfilehost.com/?fid=24269982086992358 THis kernel fixes the permission issue that initially cause the tablet to not boot.

Lastly if you want to root install the lastest SuperSu Beta. http://xdaforums.com/attachment.php?attachmentid=3523851&d=1446166283.

Just post if you have any questions. Not sure what level you at when it comes to doing this stuff but we will help the best way we can.
[Nexus 9 Original Android Development] madbat99:
You actually need to flash supersu beta before elementalx.
[Nexus 9 Original Android Development] Mikeaj15:
Error but device boots/loads/works 100%

hi all. I just bought a N9 (I do NOT want to root it) with this error (This is a development device not intended for production use) showing up at charge and when shut off/rebooting stage.

The N9 has factory ROM loaded

BUT the N9 still works 100%. Nothing seems to be wrong with my ROM and any feature I've played with seems to be working perfectly well.

So since I have no intentions of rooting/loading ROMS. I just want the factory ROMs from Google Updates, should this be something I worry about, or just ignore?

I got a smoking deal on this, the keyboard cover and another silicone case with magnetic cover so I really don't want to ask seller for refund.
[Nexus 9 Original Android Development] madbat99:
Wow that is interesting. That could be an internal testing device. Mind uploading a screenshot of "about tablet"? Or maybe it says about device. You shouldn't have to worry about the message. You can always flash a clean factory image with fastboot. Or use wugs toolkit to do it for you. But hold off on that for a minute.

I can almost guarantee that there are folks who will be interested in that device. Or at least a copy of the system.

That may prove to be a very popular find you have there.
[Nexus 9 Original Android Development] Mikeaj15:
I will see what I can do for a screen shot.

I spoke with the seller, who is a computer science major about the issue and he profusely apologized and said he will take it back and fix the issue ( so he did this morning).

He rooted the device but never flashed any other ROMS. He just wanted the device rooted. So when he locked it again he figures that it what set off the "tampered flag"/error message.

So maybe since he never flashed another ROM to the device that has everything to do with why it still works 100% still, yet I'm getting the red letter message.

I spoke with HTC about this today and they said if the device is working fine and loading to the ROM no issues, then totally ignore this msg.

I just wanted to ask the seller to remove the error message if he can because if I decide I don't like the size of the device and I try to sell it I'm worried another buyer may be weary of the error message (as they should be really).

OK, so this is my solution, according to the guy who fixed my N9

"So when you unlock the bootloader it actually allows any android device to be updated easier. So it can be updated either on the tablet directly or manually updated on the computer. Unlocking the bootloader isn't the same as rooting the device.

So I have actually unlocked the bootloader. I was actually running some tests, and the red text appeared because the program I used to factory restore the tablet and lock the bootloader wasn't official. So I took Google's original software for the Nexus 9 and put it on. So everything should work fine now, you will get regular software updates over the air and everything should be fine.

I have turned on and off the tablet 7 times now and there is no text when it is booting up or shutting down. Charging seems to work perfectly fine and it is able to connect to my computer."

maybe that will help others, maybe not.
[Nexus 9 Original Android Development] madbat99:
No one would worry about that message, its a nexus, they are born to flash. You can use wugfresh nexus root toolkit to flash a fresh Google factory image. It's so easy. Point and click. Just need a pc. It downloads and flashes the whole thing. No root, factory fresh.
[Nexus 9 Original Android Development] Mikeaj15:
UPDATE: Feb 11

So Google released a Feb security patch last night and my N9 can not install it. It downloads fine and tries to run but after 1 second of installation it fails and android is on his back with the word ERROR underneath. I am not sure if this is because my factory ROM is re-installed BUT the bootloader is NOT locked again (left unlocked by the last owner). SO I downloaded Wugfresh's NRT and used the RELOCK button and after it wiped my tablet, now the red error "This is a development device not intended for production use" is back on my tablet again. ugh. I'll try using ADB and fastboot to bring back to factory spec. I do not need to have my tablet left in unlocked state as many of you may want. I just want a reliable N9 that updates the factory ROM and security patches OTA. I do not want to have to play with this.
[Nexus 9 Original Android Development] madbat99:
I would leave it unlocked. Only because if its locked, and has a critical failure or a failed update renders it unbootable, there is no saving it. You can only flash a factory image on an unlocked bootloader. You should unlock (which wipes data) then in wugs toolkit, pick the newest build available and choose the flash stock+unroot option. All it does is flash the factory image. Then leave it unlocked. Being unlocked doesn't hurt it, or leave it vulnerable. It just allows you to flash firmware. Period.

Just telling you the best and easiest way to always be able to fix it.

Flashing the factory image may solve all of your problems. Then if you want to lock your bootloader, go ahead.

Just know that locking it means you will not be able to save it from a failure that prevents it from booting into fastboot/bootloader. And no one will be able to help you.

So follow the directions I gave, or don't. Your choice.
[Nexus 9 Original Android Development] Mikeaj15:
madbat, ok thats a solid point.

I will leave the bootloader unlocked for sure then!!!

So if the Unlocked bootloader is not causing concerns, I wonder why the simple Feb security patch would not install?
[Nexus 9 Original Android Development] madbat99:
That's a good question. Did you have a clean unmodified system? Did you flash the factory image since you got the tablet?

If not, then you are relying on the previous owner gave it to you with a clean, unmodified system partition.

No way to know for sure there.

I say flash a clean factory image. Then if you don't want root, or don't care to try to "improve" the system, then just leave it be and enjoy your nexus. OTA will work fine once you've flashed stock.

Maybe after some time with it you'll want to investigate the benefits and perils of rooting (it is a nexus after all). Maybe not. Entirely up to you.

The pure joy of Android... Choice!
[Nexus 9 Original Android Development] DieselNY:
Please forgive me but what do you mean when you are in the early steps and you "copy and paste the files into the Platform Tools Folder" what is the platform folder? how do we get that/create that? Thanks.
[Nexus 9 Original Android Development] madbat99:
You download the Android SDK from Google to your computer. The platform tools folder will be in the SDK files.

You can get the SDK (software development kit) from Google's factory image page here.

It also has the factory images and all of the flashing instructions.

You don't really need the whole SDK, just adb and fastboot (platform tools).

But honestly, if your lost that early in, you will probably be better off using wugfresh nexus root toolkit from here.

It downloads all the files and tools, and does all the flashing for you.

Then it's a good idea to start learning to use adb and fastboot. Wugs kit just gives you a little head start. You can also do manual flashing with it in the advanced tools section. It has platform tools built in.
[Nexus 9 Original Android Development] larry_walker:
will this method still work on the current 6.0.1 build MMB29R?
[Nexus 9 Original Android Development] corkiejp:
Just flash the latest systemless supersu.zip in TWRP.
[Nexus 9 Original Android Development] 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.
[Nexus 9 Original Android Development] corkiejp:
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.
[Nexus 9 Original Android Development] 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?
[Nexus 9 Original Android Development] corkiejp:
Flash stock boot image from the factory image of the version your on! And try rooting again if it boots.
[Nexus 9 Original Android Development] 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.
[Nexus 9 Original Android Development] fhem:
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.
[Nexus 9 Original Android Development] 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!
[Nexus 9 Original Android Development] fazbender:
Those root files look to be over 2 years old. What android build did you first use it on?
[Nexus 9 Original Android Development] USBhost:
titanium backup

---------- Post added at 08:13 PM ---------- Previous post was at 08:04 PM ----------

Hmm busybox works when i manually put it in /bin

I manually installed it and everything is working fine
[Nexus 9 Original Android Development] Sandivisi:
too fast :XD
[Nexus 9 Original Android Development] Gormsen:
Thanks mate :D

Message has been Baconized
[Nexus 9 Original Android Development] Trekest:
Quick question regarding this method - should an OTA come by, would flashing the original boot.img revert the changes to the kernel, or would a full reflash be mandatory?
[Nexus 9 Original Android Development] drawde40599:
Funny !!
[Nexus 9 Original Android Development] Chainfire:
Regarding the boot time security - I just turned a pattern lock on for at boot, and su is still working fine for me. Going to need some more testing to fix that, as I need to reproduce the issue before I can fix it.
[Nexus 9 Original Android Development] Hogyoku:
Absoluut legend works perfectly!!
[Nexus 9 Original Android Development] :
Does anyone know which Apps currently would support filemanager items such as mounting system, copying/pasting modified APKS adn changing permissions? Tried my trusty RootExplorer but that cannot perform apk copies to mounted system
[Nexus 9 Original Android Development] tyvar1:
Omg! That was fast! Thank you so much sir!

Will I still get OTA? And will I need to reroot?
[Nexus 9 Original Android Development] :
Hello!

Can you to explain, please, what do you change in source code for rooting available? I new in kernel editing and I want change kernel for my device when it give 5.0.

Thanks!

Best regards
[Nexus 9 Original Android Development] Chainfire:
Again re: the security issue, when I reflash my Nexus9 to full stock, then set the security pattern, then boot inject and flash patched, the first boot the pattern lock doesn't work. I turn it off and boot again, then it does work, and su works fine as well. I turn the pattern off again and reboot, still fine. Turn the pattern on again, still fine.

Need a better reproducable case.
[Nexus 9 Original Android Development] frap129:
Well, I guess this makes it ROM time :cool:
[Nexus 9 Original Android Development] Vonnegut:
I've read that the system can't be mounted in Lollipop. Is that true?
[Nexus 9 Original Android Development] prdog1:
Can if you root. Root explorer working for me. :cool:

---------- Post added at 06:14 AM ---------- Previous post was at 06:03 AM ----------

Root Explorer working for me. Copied APK to system and changed permissions. Then deleted it. No problems so far. :cool:
[Nexus 9 Original Android Development] TheBiles:
Any idea why the tablet wouldn't be showing up in adb? I have the latest SDK with USB drivers installed, but nothing comes up when I type "adb devices." Yes, USB debugging is enabled on the tablet.

Edit: Had to manually install the driver. D'oh.
[Nexus 9 Original Android Development] prdog1:
I had to put mine in ptp instead of mtp. Also need environmental variables set or open command prompt from folder adb is in. :cool:
[Nexus 9 Original Android Development] steveo17:
so i did the fastboot steps...got root and it appears to be working great. however when i attempt to grant root access to an app. i can't interact with the prompt.

similar issue is now i'm trying to sideload TB test build and i can't click the install button. i can click cancel though
[Nexus 9 Original Android Development] prdog1:
Need link to TB test build so can test. Haven't had a problem interacting with any prompts yet. :cool:
[Nexus 9 Original Android Development] steveo17:
download link:

http://t.co/PhE5wkvHkA

you can accept the grant or deny supersu prompt no prob?
[Nexus 9 Original Android Development] prdog1:
Yea. So far su prompt worked on Root Explorer and TIBU although TIBU couldn't get access due to SU path. :rolleyes:
[Nexus 9 Original Android Development] JustusIV:
So.... i am never buying a none nexus again. :)

Thanks Chainfire
[Nexus 9 Original Android Development] Zilol:
Mine just arrived! It's upgrading right now but will root after that and finally give lollipop a "lick"
[Nexus 9 Original Android Development] steveo17:
this is so strange. idk why i can't accept the prompts for supersu and for install of apps that are not from the playstore.

anyone have any suggestions?
[Nexus 9 Original Android Development] Hogyoku:
Have you tried setting supersu to always grant access ?
[Nexus 9 Original Android Development] steveo17:
yes that works fine...but i can't go to my file manager, click the app i want to install and then actually hit the install button

here's the problem i'm having

[youtube]bRztFrABdWA[/youtube]
[Nexus 9 Original Android Development] USBhost:
Adaway works good
[Nexus 9 Original Android Development] prdog1:
Got MTP and TIBU test app working. If moving an apk to system use rw-r-r as permissions. :cool:

---------- Post added at 09:39 AM ---------- Previous post was at 09:24 AM ----------

Better Battery stats installed and working. Might try different file manager. :cool:
[Nexus 9 Original Android Development] steveo17:
yeah i understand that apps will install properly (moved to system and set permissions)...i can't interact with the prompt to click the actual install button...as you can see in the video. the file manager has nothing to do with it
[Nexus 9 Original Android Development] prdog1:
I did BBS with the install button from download folder. Factory reset and start over. :cool:
[Nexus 9 Original Android Development] Agazoth:
Works like a charme. Got root on Nexus 9. Now I just need adaway for 64-bit :D
[Nexus 9 Original Android Development] prdog1:
It will run 32 bit apps. Don't have 64 bit processor anyway. :cool:
[Nexus 9 Original Android Development] steveo17:
welp didnt want to have to go that route...but it worked lol factory reset cures all problems :D

thanks dude
[Nexus 9 Original Android Development] prdog1:
Yea. Gotta do what you gotta do. Something was corrupted. :cool:
[Nexus 9 Original Android Development] Agazoth:
It can not be installed from f-droid
[Nexus 9 Original Android Development] steveo17:
yep exactly. and i knew upon purchasing this that there was no way i wasnt going to have to factory reset it at least once, not including the unlock.....it is a nexus device after all. made to tinker

i got that error when trying to install show box. maybe not 5.0 compatible.?
[Nexus 9 Original Android Development] Chainfire:
Any overlay apps installed? Lux, Twilight, etc?
[Nexus 9 Original Android Development] Agazoth:
Any other apps doing the same job as adaway?
[Nexus 9 Original Android Development] steveo17:
yes i did have Lux installed. I'm waiting for playstore to reinstall all my apps. so lets see if the problem comes back when Lux is reinstalled

---------- Post added at 11:24 AM ---------- Previous post was at 11:23 AM ----------

BINGO Lux was causing the issue
[Nexus 9 Original Android Development] USBhost:
Adaway works just fine
[Nexus 9 Original Android Development] prdog1:
Yea. I just pulled apk from my S3. :cool:
[Nexus 9 Original Android Development] Agazoth:
Got Adaway here:https://f-droid.org/repository/browse/?fdid=org.adaway

Works perfectly :D
[Nexus 9 Original Android Development] tyvar1:
Omg awesome, Adaway is a most for me! To bad YouTube adaway wont work on android 5.0.. :(

Just got a mail that I can go pick up my nexus 9! Hype!
[Nexus 9 Original Android Development] qbking77:
Made a tutorial video using this root method. Hope it helps.

How to root the Nexus 9:

http://youtu.be/5jwoPx5mB7Y