yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Original Android Development] Mayday_XL:
How can i unroot the device/ set it back to stock ?

After i flashed the factory image, i get a message on the screen in red "developer device not for sale" ?! :(
[Nexus 9 Original Android Development] tyvar1:
Adaway and StickMount (updated for 5.0 already!) Will be the first apps to download! Thank you chainfire for this root and the great nexus StickMount app!
[Nexus 9 Original Android Development] thebrainkafka:
THX, youre a real pro!
[Nexus 9 Original Android Development] prdog1:
For those that need it. :cool:

APP -> system

CAC -> cache

LNX -> boot.img

MDA -> Unknown

MSC -> Misc (bootloader commands and other misc stuff )

PER -> usually a fat partition containing sensor calibration etc. - per device provisioned.

SOS -> recovery.img

UDA -> /data - "user data area"

USP -> bootloaderUSP -> Staging
[Nexus 9 Original Android Development] SmartGeezer:
Thanks for the great work. One thing I've noticed though on my Nexus 9. The su shell doesn't seem to have access to /storage/emulated/0 which messes with a lot of root apps, especially file managers.
[Nexus 9 Original Android Development] prdog1:
Do you have SU Pro installed. Need for shell. Had to install to get the partition table. :cool:
[Nexus 9 Original Android Development] lartomar2002:
New to Nexus, how do I unlock? Thanks
[Nexus 9 Original Android Development] jreyno10:
http://xdaforums.com/showthread.php?t=2927790

Sent from my G3
[Nexus 9 Original Android Development] WhammyDroid:
Thanks Chainfire!

One question: Does anyone know if Superuser by ClockworkMod is still being supported? If not, I will definitely be buying SuperSU.
[Nexus 9 Original Android Development] wingman_214:
You should purchase it. Support your developers.
[Nexus 9 Original Android Development] WhammyDroid:
I definitely agree with you. I just do not want to be buying something twice. That is all.
[Nexus 9 Original Android Development] Chainfire:
It's certainly not supported by me... also, that one is free. The other old paid one was also called Superuser, but that one is definitely no longer supported by anyone (for years now).
[Nexus 9 Original Android Development] zanoli99:
I had this problem and mine was due to me using lux brightness app. Had to disable it then I could install. Might want to check brightness settings. I am working fine now. Not sure this will help but is issue I had.
[Nexus 9 Original Android Development] reinert012:
dude...

I need that wallpaper on your N9
[Nexus 9 Original Android Development] Cuzz1369:
Show box works fine for me. Just install like a normal app

Spoke to soon. Installs but won't play anything
[Nexus 9 Original Android Development] jlokos:
Thanks for your great work. This is my first nexus device. I have not had root so quick on any of my other devices.
[Nexus 9 Original Android Development] uberjon:
Agreed great work! I purchased the pro version to show my support.
[Nexus 9 Original Android Development] Fransis88:
Thanks, root ok, busybox not compatible
[Nexus 9 Original Android Development] USBhost:
Busybox working just fine for me
[Nexus 9 Original Android Development] jd1639:
Should be working now

http://xdaforums.com/showthread.php?p=56552835
[Nexus 9 Original Android Development] wideopn11:
Might be the the busybox app. What are you using?

---------- Post added at 05:38 PM ---------- Previous post was at 05:34 PM ----------

Yeah I just tested a version for Stericson and it worked. Should be pushed the play store later tonight.
[Nexus 9 Original Android Development] Master05:
Can someone tell me exactly what to do to prepare my tablet for RMA without having flags set that could cause trouble?

Currently my nexus is unlocked and rooted.
[Nexus 9 Original Android Development] Gormsen:
1. Make a factory reset, just to be sure.

2. Fastboot oem lock

3. Done

Smashed down on the mighty Nexus 9
[Nexus 9 Original Android Development] venture007:
root disappeared on reboot

sorted

venture
[Nexus 9 Original Android Development] jd1639:
Did you use chainfire's image files to root?
[Nexus 9 Original Android Development] gburlingame:
Lost root

I used Chainfire's images, confirmed root with root checker and all was good.

Today I installed the Busybox Pro that just came out. It reported an SU problem.

Root checker fails.

Superuser app says there is no binary installed.

I haven't done anything I could imagine would have caused the loss of root. I did install SU Pro the other day, could that cause this?

Thanks!

Greg
[Nexus 9 Original Android Development] jd1639:
Maybe it's related to busybox. I've done everything you have except install busybox and I don't have any problems
[Nexus 9 Original Android Development] prdog1:
Used Chainfire's images, installed SuperSU Pro, and installed busybox

with Stericson's Busybox Pro and all is good. :cool:

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Nexus 9 Original Android Development] MRobbo80:
All working great here to.

Sent from my Nexus 9
[Nexus 9 Original Android Development] jamalau:
Hallo, i´ve rootet my nexus, but Titanium Backup does not work with this root, SU give the root access, but Titanium says no root access.

Have anyone the original boot.img ?
[Nexus 9 Original Android Development] thebrainkafka:
Check root with root checker APP.
[Nexus 9 Original Android Development] Mayday_XL:
http://click.xda-developers.com/api...4 - xda-developers&txt=http://t.co/PhE5wkvHkA :good:
[Nexus 9 Original Android Development] jamalau:
[MENTION=2354363]Mayday_XL[/MENTION]

Thank you, this version works perfekt !
[Nexus 9 Original Android Development] eurominican:
I did this and now in the splash screen it says in bold red letters across the top "this is a development device not intended for production use" wtf.. I had rooted it with chainfire method and obviously unlocked it.

Can some one please chime in how to fash the device back to 100% stock? TIA
[Nexus 9 Original Android Development] jd1639:
To flash back to stick see this. http://xdaforums.com/showthread.php?p=56529332
[Nexus 9 Original Android Development] eurominican:
Thank you for the fast response kind sir! I was in process of deleting this post from here and posting it in the dedicated Q&A thread but you answered here. Thanks again!
[Nexus 9 Original Android Development] 850RPM:
easy way;

adaway 2.9.2 working well after root

thanks
[Nexus 9 Original Android Development] basily:
Holy crap! I did the same thing, reset it like 3 times, oem locked it, cleaned it up and boxed it all nice to return to best buy... For some reason i hadn't noticed that "developer" message before... The returns person turned it on and that message came up... Crap! "Huh... It never said that before..." She didn't even notice and by the time the guy who knows what he's doing showed up, it was past that screen. Phew! Got my money back, and if anyone in the Toronto area wants an N7, i can only assume that there'll be an open box discounted one on the for very soon at the best buy at 7 and Weston.
[Nexus 9 Original Android Development] prdog1:
For those trying to flash the stock image and getting the not enough space error.Try removing the Vendor.img from zip. That image is the binaries and reside on their own partition. These are not touched by any root, system, rom ect. The other thread has them flashing it manually to User data. This is wrong. Should go to VNR partition Dev block 24. Not needed to flash back to stock until new binaries are released. This image is why the zip is so big. This used to be a separate flash. :cool:
[Nexus 9 Original Android Development] gleonard3:
Development message

OK, wait... so everyone that uses this root method is seeing this development message on boot? I don't think I can live with that. Or is this just for some "lucky" folks. Maybe I'll wait a while.
[Nexus 9 Original Android Development] prdog1:
Seems it most that relocked. I did it and only have seen it then and if an app crashes. May have something to do with developer mode being turned on also. Nexus is pretty much worthless locked and no root. :cool:
[Nexus 9 Original Android Development] berendspruijt:
i want to use a root app but it gives me the following error:

only position independent executables (pie) are supported

Any workaround for this?

adaway is working ^^
[Nexus 9 Original Android Development] jd1639:
This post should not be in this forum but, the app most likely does not support android 5.0
[Nexus 9 Original Android Development] berendspruijt:
O tnx. I tought it had something to do with root.
[Nexus 9 Original Android Development] jd1639:
Does flashing the stock boot.img break root?

Edit, yes it does
[Nexus 9 Original Android Development] thekenster:
So for the people like me, who did flash all the images manually including the Vendor.img did we do any damage?
[Nexus 9 Original Android Development] jd1639:
No, you didn't do any damage. Just flashed a lot of junk to the userdata partition.
[Nexus 9 Original Android Development] prdog1:
Yea. That was probably the only safe place to flash it too. :cool:
[Nexus 9 Original Android Development] Chainfire:
CF-Auto-Root has arrived: http://download.chainfire.eu/595/CF-Root/CF-Auto-Root/CF-Auto-Root-flounder-volantis-nexus9.zip
[Nexus 9 Original Android Development] jd1639:
Thanks [MENTION=631273]Chainfire[/MENTION]
[Nexus 9 Original Android Development] prdog1:
[MENTION=631273]Chainfire[/MENTION]. Thanks and keep up the good work. Looking forward to Nexus 6 root. Grab yourself a couple of pints on me. ;):cool:

Transaction ID: 71503202Y1766062T
[Nexus 9 Original Android Development] tyvar1:
What's the difference between the old version and the Auto-root?
[Nexus 9 Original Android Development] StuMcBill:
I just wondered, is there an easy way to quickly remove root if an OTA comes out and I want to go back to stock?
[Nexus 9 Original Android Development] jd1639:
Unzip it. There's a batch file inside you run
[Nexus 9 Original Android Development] prdog1:
If have SU Pro can unroot from there if it still works. May even be able to just take OTA. Comes from Google not Verizon. Not looking for bloatware and don't have custom recovery yet.. Never had Nexus so not sure.Like any other device OTA may block root exploit. Don't suggest taking it till checked by dev. :cool:
[Nexus 9 Original Android Development] jd1639:
With past nexus devices you will be able to take the ota while rooted as long as you haven't changed or deleted any system files. You will lose root with the ota.
[Nexus 9 Original Android Development] jd1639:
When you get the green robot press power + vol up. Then release the keys. That should get you into the stock recovery. Do a factory reset in that
[Nexus 9 Original Android Development] jd1639:
This is a development thread, why don't you ask your question in the q&a thread and we can take this out of this thread. There are probably more there that can help too
[Nexus 9 Original Android Development] TenderloinShadow:
ADB won't detect my tablet.

USB debugging is enabled

OEM Unlock is enabled

Device gets detected by my computer, allows me to transfer files using MTP and whatnot

Open command prompt in the platform-tools folder using the shift+rick click command to open it in the directory

type in adb devices, get no results.

Thanks in advance for any help
[Nexus 9 Original Android Development] jd1639:
Type fastboot devices. Bet that works
[Nexus 9 Original Android Development] TenderloinShadow:
Nope, didn't do anything.

Also, I don't get any message on my tablet asking me to authorize the adb connection. ADB is not reading the device. I'm sure that there's something small that I'm missing here, any yhelp would be appreciated.

Edit: Still working on this, it seems that my computer isn't detecting the ADB drivers. I should have them already installed, I use adb on my M8 all the time. Is there a way to manually install ADB drivers, or is it just the USB driver for the device?

Edit 2: Just plugged my M8 in, adb is able to detect it right away.
[Nexus 9 Original Android Development] pantmunu:
Have you tried to connect it as a camera device ?? And are u connected via a USB hub or a direct connection ?
[Nexus 9 Original Android Development] Inforc3r:
Settings > Storage then use the 3 dots on top right. Use PTP. After that u should be able to do adb devices and find it.
[Nexus 9 Original Android Development] berendspruijt:
I had the same problem.

This worked for me ^^

ADB Devices empty?

This is to help those of you folks that are running into an issue with your ADB Devices command returning blank.

This is assuming you have gone through the trouble of troubleshooting and researching yourself. If you are at this point and reading this post, then you most likely already tried stuff like a different USB port, cable, adb kill-server / start-server stuff, and ensuring you have USB debugging enabled.

If you are still stuck, then let's get to work.

Windows 8/7

1) Plug the device into a USB directly connected to MOBO or into your mobo. If you are prompted with some ping on your computer, then that is a good start.

2) Open -> Device Manager

3) Go to "Other Devices"

4) Identify the tablet. It will probably say "ADB USB blah blah". That's the one we want.

5) Right click, Update Driver Software

6) Browse my computer

7) Let me pick from a list of device drivers (bottom box)

8) In the pop up select, "SHOW ALL DEVICES" at top of list, click NEXT.

9) Click "Have Disk"

10) Browse to your path where you have:::: "android-sdk\extras\google\usb_driver"

11) Click okay

12) Select Android ADB Interface

13) Click yes -> Install -> Close

At that point you should have your tablet asking for permission. If it's not plugged in, plug it in and see the prompt.

Enjoy
[Nexus 9 Original Android Development] StuMcBill:
Chainfire - just so you know, the full unroot option in supersu doesn't work!
[Nexus 9 Original Android Development] prdog1:
May not especially since it can't reflash the boot image. Flashing the factory image will unroot it. :cool:

Sent from my Nexus 9 using Xparent Skyblue Tapatalk 2
[Nexus 9 Original Android Development] jmjm003:
Can I root LRX21Q with the files listed in the first post? I couldn't wait for the OTA so I flashed the files. Want to get my root back now.

Thanks
[Nexus 9 Original Android Development] prdog1:
Nexus 9 only. Read the OP..

Sent from my Nexus 9 using Xparent Skyblue Tapatalk 2
[Nexus 9 Original Android Development] jd1639:
Q is posted as the latest factory image. Just saw it uploaded
[Nexus 9 Original Android Development] jmjm003:
I've read it, LRX21Q is for the Nexus 9.
[Nexus 9 Original Android Development] prdog1:
I would think yes if they didn't block exploit and kernel the same. If not need to mod kernel. Let us know. ;):cool:

Sent from my Nexus 9 using Xparent Skyblue Tapatalk 2
[Nexus 9 Original Android Development] jd1639:
Most likely it'll work. Try it and let the rest of us know. Everyone is downloading 5.0 right now so it's real show our I'd try it
[Nexus 9 Original Android Development] jmjm003:
It seems to work just fine after root.

Thanks
[Nexus 9 Original Android Development] StuMcBill:
Did you just flash system.img & boot.img? Or did you flash bootloader, radio and vendor?
[Nexus 9 Original Android Development] USBhost:
ok guys

i just learned something

never do THIS!!

in /cache

rm -rf /*
[Nexus 9 Original Android Development] StuMcBill:
Why, what does it do?
[Nexus 9 Original Android Development] USBhost:
It will wipe data

And soft brick your device

I was able to use that command on my n7 and note 3 just fine

But not my nexus 9 lol

Good thing i backup my data lol
[Nexus 9 Original Android Development] tyvar1:
Lucky :)

How did you backup your data?
[Nexus 9 Original Android Development] prdog1:
Anyone that rooted the new update figure out what the new kernel patch is/does. Does it block exploit or fix something? We need to patch it for root to find out. :cool:
[Nexus 9 Original Android Development] jmjm003:
I've not had any issues with root so far on LRX21Q.
[Nexus 9 Original Android Development] USBhost:
titanium backup
[Nexus 9 Original Android Development] pantmunu:
I haven't even got an update yet ... Still on the 21L .. Why so .. Manual update it is then ..
[Nexus 9 Original Android Development] nimdae:
rm -rf /* is something you NEVER want to run. rm = remove, -r is recursive, and -f is force/no prompting. /* is everything in the root of the filesystem.

If you want to nuke /cache/* then you want rm -rf /cache/* or cd /cache and rm -rf *

---------- Post added at 11:56 AM ---------- Previous post was at 11:53 AM ----------

As I understand it, the root method modifies the initrd image. The Q update includes an update to boot.img. I don't know the contents of this image offhand, but am I correct in speculating the root tool should be updated for changes to boot.img in case google updated their kernel?
[Nexus 9 Original Android Development] USBhost:
Yep i just realize that now

Lol

It should have been /cache/*

Not /*

I was too sleepy to think straight

But it was cool seeing what happed any way
[Nexus 9 Original Android Development] prdog1:
You won't since you are using old kernel. Root needs to be updated so we have new kernel and thus full update. :cool:

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2

---------- Post added at 12:31 PM ---------- Previous post was at 12:29 PM ----------

Yes. You are correct and they did update the kernel. :cool:

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Nexus 9 Original Android Development] USBhost:
Read https://android.googlesource.com/device/htc/flounder-kernel/

the changelog
[Nexus 9 Original Android Development] prdog1:
Don't know what it is but there is a kernel patch in the OTA. :cool:
[Nexus 9 Original Android Development] jd1639:
I successfully rooted Q using chainfires manual method. I tried cf- auto but it put me into a bootloop into recovery which I could not get out of except by flashing the factory image
[Nexus 9 Original Android Development] prdog1:
But your using the original boot.img and not the one that comes in update. Thw new one is supposed to fix some of the lag and redraws. :cool:
[Nexus 9 Original Android Development] jd1639:
Haven't seen any of those
[Nexus 9 Original Android Development] prdog1:
I have had some apps lock up or open slow if moving too fast. :cool:
[Nexus 9 Original Android Development] Brian706:
Have you updated adb to release 21? Your lollipop device requires the latest version if you haven't already done that.
[Nexus 9 Original Android Development] ericplatham:
I had the same problem, updated ADB, updating drivers, switching MTP and PTP with no luck. I found this post by Koushik Dutta from ClockworkMod. I took a shot and installed his Universal ADB driver for Windows and I finally got ADB to recognize the device.
[Nexus 9 Original Android Development] mrshades812:
So, is everyone updating to the latest by just flashing the the LRX21Q factory image? I know that is a little OT, so... will the root files here work fine on the new update? (on topic) :)
[Nexus 9 Original Android Development] jd1639:
Yes to both your questions. Do the manual method to root. I had problems with cf-auto
[Nexus 9 Original Android Development] mrshades812:
PM sent. :)
[Nexus 9 Original Android Development] ombadboy:
Don't forget though that with the current manual method you will not get the Q kernel
[Nexus 9 Original Android Development] Agazoth:
Auto CF worked like a charm on LRX21Q. Excellent work!
[Nexus 9 Original Android Development] jmjm003:
. Has it been updated for Q kernel or is it still using older one?
[Nexus 9 Original Android Development] Chainfire:
CF-Auto-Root is kernel agnostic. Just run it again after upgrading to the new firmware. Yes, you will be running the new kernel afterwards.

The manual method I posted before CFAR was ready however, will put you back on the old kernel.
[Nexus 9 Original Android Development] ombadboy:
So which are the absolute min necessary files necesarry to flash Q (including the kernel) and then use CFAR to root?
[Nexus 9 Original Android Development] prdog1:
If flash-all script won't work as mine doesn't should flash all the files in the image zip. Why do a partial upgrade? :cool:
[Nexus 9 Original Android Development] jd1639:
You just extract cfar and get the current boot.img out of it. Use that
[Nexus 9 Original Android Development] prdog1:
Don't believe there is a boot image in CFAR. Believe he is patching whatever kernel you have. Would have to extract the image to see what is inside. More trouble than it is worth.As Chainfire said it is boot image agnostic. :cool:
[Nexus 9 Original Android Development] jd1639:
You're correct I spoke before I extracted it. My bad
[Nexus 9 Original Android Development] prdog1:
Lol. I was guessing but that was how I interpreted agnostic. :laugh::cool:
[Nexus 9 Original Android Development] jd1639:
Now the problem I've got, I've tried cfar twice now. Both times it's ended up with a bootloop into recovery. And there's no way to get out of it without flashing the factory image. Factory reset doesn't work. Anyone else having issues? The old image files still work to get root, but of course you end up with the old kernel.
[Nexus 9 Original Android Development] prdog1:
I'm going to try in a little while. I'm uploading my Tibu update to Dropbox. Then I'm gonna manually upgrade as I'm getting the space error and there is no fix. My guess they gonna have to repartition in another update of the bootloader. Then I'm gonna try CFAR. :cool:
[Nexus 9 Original Android Development] davy917:
For CFAR do I just need to run the root-windows.bat file in fastboot?
[Nexus 9 Original Android Development] prdog1:
That's all it should take. :cool:
[Nexus 9 Original Android Development] Chainfire:
If you used "fastboot flash" instead of "fastboot boot", I'm going to ask you to hand in your geek card.
[Nexus 9 Original Android Development] prdog1:
:eek::rolleyes::laugh::cool:
[Nexus 9 Original Android Development] PhilDX:
i'm wondering if folks here who haven't been successful in manually flashing the files included in the Q update are erasing each partition first (including the user partition)? i mention it only because i don't see many folks explicitly stating they did this erase step. note that the -w option in the flash-all.bat file included in the update will effectively do this when flashing the new image files.

so, i think you should try this, you will lose data but it works:

step #1

fastboot flash bootloader bootloader-flounder-3.43.0.0114.img

fastboot reboot-bootloader

step #2

fastboot erase system

fastboot erase recovery

fastboot erase cache

fastboot erase boot

fastboot erase userdata

fastboot erase vendor

fastboot flash system system.img

fastboot flash recovery recovery.img

fastboot flash cache cache.img

fastboot flash boot boot.img

fastboot flash vendor vendor.img

i followed this with a factory reset before leaving recovery (i don't know if that's necessary since i erased the userdata partition, but why not).

after completing these steps, i re-rooted using CF Auto Root without difficulty.
[Nexus 9 Original Android Development] jd1639:
I can say I did not erase each partition. Just flushed the images

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

No, I used boot and not flash
[Nexus 9 Original Android Development] prdog1:
CFAR worked perfectly for me also. I also erased but changed the partitions that could be formated to format instead of erase. Userdata is optional and won't erase unless you run CFAR with locked bootloader. Thanks again Chainfire. :cool:

fastboot erase recovery

fastboot format system

fastboot erase boot

fastboot format vendor

fastboot format cache

fastboot erase userdata (optional)
[Nexus 9 Original Android Development] jd1639:
Yep, that was the problem. I was lazy. Just flashed the image with fastboot -w and worked perfectly for me too.
[Nexus 9 Original Android Development] prdog1:
Kewl. I had to sweat a minute and stop and download another image zip. Even tho MD5 of zip matched the Vendor image was corrupted. :cool: