Root

[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

 

[corkiejp]

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

Try "fastboot devices" while in that mode.

 

[EniGmA1987]

Try "fastboot device" while in that mode.

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.

 

[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!!

 

[dictionary]

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!!

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?

 

[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!!!

 

[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.

 

[Giants2010]

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!!!

What did you do? same problem

 

[Debizzle]

Instructions

What did you do? same problem

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://forum.xda-developers.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.

 

[madbat99]

You actually need to flash supersu beta before elementalx.

 

[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.

 

[madbat99]

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.

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.

 

[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.

 

[madbat99]

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).

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.

 

[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.

 

[madbat99]

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.

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.

 

[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?

 

[madbat99]

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?

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!

 

[DieselNY]

A quick video guide for those of you that prefer visual aids.

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.

 

[madbat99]

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.

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.