[TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 9 - Backup, Root, Recovery, Flash Stock

[mskip]

Yes all drivers are installed. It detects and reboots my device into Fastboot, but once the tablet loads into TWRP I get the message saying it can't detect

Once it boots into fastboot then into TWRP, I get this msg...

Open up the computers task manager, find adb process and kill it, then try again. If that doesn't work reboot your pc and try again.

Mark.

 

[brushrop03]

Open up the computers task manager, find adb process and kill it, then try again. If that doesn't work reboot your pc and try again.

Mark.

Yeah, that's what I did and got it working.

 

[Cam2]

Trouble unlocking bootloader

EDIT: I figured it out. I didn't have the OEM unlock box checked in Developer settings. I'll leave this post here just in case someone else goofs up the same way I did. I don't remember having to do that with previous devices.

Mark or anyone who can offer a suggestion:

I've read the entire thread and browsed the Help and FAQ sections on the Skipsoft website, all to no avail. I'm in the process of searching through Android Toolkit threads for other devices to see if my issue has come up before for other devices/users (no luck yet).

I'm having trouble unlocking the bootloader.

I'm using Toolkit version 1.3.3. on a Windows 8.1 PC. I installed ADB drivers using the Toolkit option 1, and installed the recommended Clockworkmod package.

The drivers appear to have installed successfully. Device is recognized in ADB mode with no errors noted in Device Manager. The device serial number shows up under list of devices attached in the Toolkit.

USB debugging is enabled on the device, PTP mode is checked under USB options, and my Windows PC is authorized for USB debugging ("Always allow for this computer" is checked).

When I try to unlock the device using Toolkit option 3, it detects the device and reboots it to Fastboot, and detects the device in Fastboot mode.

After the Toolkit says to press the "volume up" button when prompted to unlock the bootloader, it says:
(bootloader) ability is 0
(bootloader) Permission is denied for this command!

The Toolkit then finishes its script and reboots the device into Android without unlocking the bootloader.

I attached three screen captures from my computer in case those will help troubleshoot. Anyone know what I'm doing wrong?

Thanks!
Cam

 

[mskip]

EDIT: I figured it out. I didn't have the OEM unlock box checked in Developer settings. I'll leave this post here just in case someone else goofs up the same way I did. I don't remember having to do that with previous devices.

Mark or anyone who can offer a suggestion:

I've read the entire thread and browsed the Help and FAQ sections on the Skipsoft website, all to no avail. I'm in the process of searching through Android Toolkit threads for other devices to see if my issue has come up before for other devices/users (no luck yet).

I'm having trouble unlocking the bootloader.

I'm using Toolkit version 1.3.3. on a Windows 8.1 PC. I installed ADB drivers using the Toolkit option 1, and installed the recommended Clockworkmod package.

The drivers appear to have installed successfully. Device is recognized in ADB mode with no errors noted in Device Manager. The device serial number shows up under list of devices attached in the Toolkit.

USB debugging is enabled on the device, PTP mode is checked under USB options, and my Windows PC is authorized for USB debugging ("Always allow for this computer" is checked).

When I try to unlock the device using Toolkit option 3, it detects the device and reboots it to Fastboot, and detects the device in Fastboot mode.

After the Toolkit says to press the "volume up" button when prompted to unlock the bootloader, it says:
(bootloader) ability is 0
(bootloader) Permission is denied for this command!

The Toolkit then finishes its script and reboots the device into Android without unlocking the bootloader.

I attached three screen captures from my computer in case those will help troubleshoot. Anyone know what I'm doing wrong?

Thanks!
Cam

I'm guessing you didn't read the information at the start of the boot loader unlock process screen

Glad you managed to figure it out though.

Mark.

 

[Cam2]

I'm guessing you didn't read the information at the start of the boot loader unlock process screen

Glad you managed to figure it out though.

Mark.

Yeah, going back and reading that info is what helped me figure it out. Totally my fault for trying to rush the process.

Sent from my Nexus 5 using Tapatalk

 

[Dunc001]

Help required if anyone has time. My device is currently running the LRX21R build, stock but is unlocked, with TWRP and ElementalX kernel. It has downloaded the 5.0.1 OTA (26mb) but obviously can't install it. What do I need to do to be able to get the OTA installed? Just flash stock kernel and recovery or do I need to do a full return to stock/wipe?

 

[mskip]

TOOLKIT UPDATE
New functions added to the root section [new rooting options for root and unroot],
More text added to various sections,
Text added to the Factory Image Download/Flash section to help recovery from a bootloop/device not booting properly,
Fixed push/pull and sdcard backup routines for Lollipop as Android 5 has problems communicating with the sdcard without root,
Fixed apps backup routine not starting when selected,
Updated TWRP recovery to latest version 2.8.4.0,
Fixed the unroot zip file and added stock recovery to the routine to make the device fully compatible with OTA updates,
OTA Updates can be sideloaded via stock recovery using the Toolkit (unroot first though),
Toolkit always updates to latest SuperSU version from Chainfire.

I will push AutoUpdates for all Nexus devices within the next day to make it easier to update but for users without the Pro Version (I urge you to donate if you use it/like my work as I won't be able to keep it going much longer without your support) you can do the following:
In the Tools folder delete the tkmainNexus9.exe file (this will trigger new device files to be downloaded at startup)
Download the attached Unroot-UninstallBusybox-CwmManager.zip from this post and move it to the root folder (overwriting the original)
Start the Toolkit, select your device and enjoy.

I am currently working on adding a OnePlus One Toolkit device module. Once that is finished I will build a new Toolkit and you will be notified on startup that a new version is ready to download directly via the Toolkit (if using UAT base 1.3.3 or later).

If anything doesn't work properly please let me know in the thread or at [email protected] so it can be fixed. I do test as much as I can on most devices but i'm not perfect

Mark.

 

[mskip]

AutoUpdate available for Nexus 9 device module

+Added LTE model (volantisg) to the support list
+Added FULL support [including root/recovery] for Android 5.0.1 LRX22C
+Download and Flash stock 5.0.1 LRX22C stock image directly from Toolkit

I will update the public device module when the next full version is released (with OnePlus One support).

Mark.

 

[cobyman7035]

this tool kit works with nexus 9 LTE 5.1 android? thx

 

[madbat99]

this tool kit works with nexus 9 LTE 5.1 android? thx

Look at the post directly above yours.

 

[mskip]

UAT 1.4.1 RELEASED AND AUTOUPDATE and PUBLIC VERSIONS UPDATED

Changelog for device module:
+Added FULL support [including root,skiproot] for Android 5.1.1 LMY48M [WIFI]
+Added FULL support [including root,skiproot] for Android 5.1.1 LMY48M [LTE]
+Added Android M Preview [MPA44I] to build selection for downloading/flashing
+Added 5.1.1 LMY48M,LMY48M,MPA44I stock images to download/flash from Toolkit
+Added more stability to certain routines [root, flashing]
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added new upcoming devices to device selection screen
+Added driver installation option at startup for new installs

Changelog for UAT 1.4.1:
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)

The AutoUpdate for pro users has all the above included (update via the toolkit).
You can also download the Unified Android Toolkit 1.4.1 from http://www.skipsoft.net/?p=1660. You can select Fresh Install to delete all device modules and related files (recovery, root) so when you select your device at startup it will download the latest module with all the above included. If you have several device modules downloaded (e.g. for samsung and nexus) then you can select 'upgrade' when installing the toolkit, then run ToolKitClean.exe to delete just the modules you want to update.

Android 6.0.0 images have now been released and I am working on adding support. Support will be pushed as an AutoUpdate as soon as possible.

Enjoy, Mark.

 

[mskip]

AutoUpdate for Nexus 9 Toolkit module

+UPDATE FOR ANDROID 6.0.0 MARSHMALLOW
+Added FULL support [including root] for Android 5.1.1 LMY48T [WIFI ONLY]
+Added FULL support [including root] for Android 6.0.0 MRA58K [WIFI ONLY]
+Added FULL support [including root] for Android 5.1.1 LMY48T [LTE]
+Added FULL support [including root] for Android 6.0.0 MRA58K [LTE]
+Updated all stock images up to 6.0.0 MRA58K to download/flash from Toolkit
+Updated several root routines for kernel patch if needed for Android 6
+Updated many parts of the Toolkit for Android 6 support [changes from 5.1.1]
+Added message on Main Menu start for usb mode switching to charging after reboot
+Updated busybox free, root checker and easy backup/restore apps to latest
+Disabled openrecoveryscripts as TWRP for Nexus9 doesn’t work properly with it
+Insecure kernel and skiproot images will be added soon

If you don’t have the pro version you can download the Toolkit from http://www.skipsoft.net/?page_id=1069 and donate to the Nexus 9 module at http://skipsoft.net/donate/?toolkit=Nexus9, enter your activation code when received and autoupdate to the latest version.

I will update the public device module as soon as I can.

Mark.

 

[mskip]

Updated Device module v1.1.8 available for ALL users (Pro and Public) to support all builds up to Android 6 MRA58N

Changelog:
+Added FULL support [including root] for Android 6.0.0 MRA58N [VALANTIS/WIFI ONLY]
+Added FULL support [including root] for Android 5.1.1 LMY48X [VALANTISG/LTE]
+Added FULL support [including root] for Android 6.0.0 MRA58N [VALANTISG/LTE]
+Updated all above stock images for WIFI/LTE to download/flash from Toolkit
+Fixed root routine going wrong when a certain set of options is selected
+Added more information to users in root, recovery, unlock, decryption routines
+Added detection in unlock routine for oem unlock option not being enabled
+Added Bootloop fix when rooting Android 6 by twrp message at exit [option 22,2]

I WOULD RECOMMEND ALL USERS UPDATE TO THIS MODULE TO FIX MANY SMALL BUGS AND IMPROVE THE TOOLKIT EXPERIENCE.

Pro users can just start the Toolkit as normal. After you have selected your device you will be notified there is an update available and can auto update. SIMPLE.

Non Pro users have a few extra steps.
FIRSTLY DOWNLOAD THE LATEST TOOLKIT FROM *HERE* (I UPDATED IT LAST WEEK BUT KEPT IT AT THE SAME VERSION) SO THAT YOU CAN UPDATE THE FIRMWARE CHECK FILE FROM TOOLKITCLEAN.EXE (IF THIS IS ALREADY AVAILABLE WHEN YOU RUN TOOLKITCLEAN.EXE OPTION 63 THEN NO NEED TO UPDATE THE TOOLKIT).
1. Exit the Toolkit if it is open.
2. Run ToolkitClean.exe from the intallation folder (or the Start Menu)
3. Select the device from the list
4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
5. Select option 63 to update to the latest md5 firmware check file (if you are downloading new firmware)
6. Restart the Toolkit, select the device and new module files will be downloaded/installed

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) so you get the right code fast.

If someone could give it a thorough testing (root, unlock, disable encryption, recovery) and let me know if there are any bugs or if its all good then I can update the modules for all the other nexus devices.

Enjoy, Mark.

 

[chesterchen]

Hi there,

Do you support 6.0.1 for the Nexus 9 in your Toolkit?

Thanks,

Chester

 

[mskip]

Hi there,

Do you support 6.0.1 for the Nexus 9 in your Toolkit?

Thanks,

Chester

Yes, please read the following post.

Mark.

 

[mskip]

Updated Device module v1.1.9 available for ALL users (Pro and Public) to support all latest builds up to 6.0.1

Changelog:
+Added Support [including root] for Volantis[wifi] Android 6.0.1 MMB29K
+Added Support [including root] for Volantisg[lte] 5.1.1 LMY48Z and 6.0.1 MMB29K
+Added above stock images to download/flash directly from Toolkit
+Added SuperSU systemless root method for root without flashing patched boot image
+Added check for latest stock image md5 checksum file after device selection
+Made some changes and improvements to the config module code

Pro users can just start the Toolkit as normal. After you have selected your device you will be notified there is an update available and can auto update. SIMPLE.

Non Pro users have a few extra steps.
IF YOU DON’T HAVE THE 1.4.4 VERSION INSTALLED FROM 15TH DEC 2015 – FIRSTLY DOWNLOAD THE LATEST TOOLKIT FROM http://www.skipsoft.net/?p=1660 TO ENABLE THE SUPERSU SYSTEMLESS ROOT METHOD TO WORK PROPERLY AND AUTO UPDATE THE GOOGLE FIRMWARE CHECK FILE. IF THIS IS NOT DONE YOU WILL BE PROMPTED AFTER SELECTING A DEVICE.
1. Exit the Toolkit if it is open.
2. Run ToolkitClean.exe from the intallation folder (or the Start Menu)
3. Select the device from the list
4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
5. Restart the Toolkit, select the device and new module files will be downloaded/installed
Note: Steps 1-5 are not needed if you have not selected the device before and not downloaded module files

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) so you get the right code fast.

Enjoy, Mark.

 

[guinnes.s]

I reset and flashed stock 6.0.1 on N9 ,at the time of installation I did choose the decrypt feature ,will this effect future OTA ??Thanx

Sent from my Nexus 5X using Tapatalk

 

[mskip]

I reset and flashed stock 6.0.1 on N9 ,at the time of installation I did choose the decrypt feature ,will this effect future OTA ??Thanx

Sent from my Nexus 5X using Tapatalk

Im not sure if decrypting the device affects OTA updates. The modification is made to the kernel so the system blob is unaffected. I will try testing it on my Nexus 9 tomorrow.

Mark.

 

[mskip]

Device Module Auto Update Available for Pro version

Changelog:
Nexus 9 update [V1.2.0] 06TH JAN 2016
+Added Support [including root] for Volantis[wifi] 6.0.1 MMB29S build
+Added Support [including root] for Volantisg[lte] Android 5.1.1 LMY49F, Android 6.0.1 MMB29S
+Added above stock images to download/flash directly from Toolkit
+Updated checksum file for verifying stock image download
+Updated TWRP Recovery to 2.8.7.1 for both models

If you don’t have the pro version you can download the Toolkit from http://www.skipsoft.net/?page_id=1069 and donate to the device module at http://www.skipsoft.net/?page_id=703 or directly through the Toolkit. Enter your activation code when received and autoupdate to the latest version.

Public updates will be made available soon. I am in the middle of updating the Samsung device modules (long overdue) and had to stop to update the Nexus modules for the latest builds.

Mark.

 

[guinnes.s]

Yes decrypting the device effect the OTA'S , cannot install security update?

Sent from my Nexus 9 using Tapatalk