yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Original Android Development] 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
[Nexus 9 Original Android Development] mskip:
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.
[Nexus 9 Original Android Development] Cam2:
Yeah, going back and reading that info is what helped me figure it out. Totally my fault for trying to rush the process.
[Nexus 9 Original Android Development] 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?
[Nexus 9 Original Android Development] 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 toolkit.support@skipsoft.net so it can be fixed. I do test as much as I can on most devices but i'm not perfect :)

Mark.
[Nexus 9 Original Android Development] 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.
[Nexus 9 Original Android Development] cobyman7035:
this tool kit works with nexus 9 LTE 5.1 android? thx
[Nexus 9 Original Android Development] madbat99:
Look at the post directly above yours.
[Nexus 9 Original Android Development] 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.
[Nexus 9 Original Android Development] 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.
[Nexus 9 Original Android Development] 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.
[Nexus 9 Original Android Development] chesterchen:
Hi there,

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

Thanks,

Chester
[Nexus 9 Original Android Development] mskip:
Yes, please read the following post.

Mark.
[Nexus 9 Original Android Development] 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.
[Nexus 9 Original Android Development] 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﻿
[Nexus 9 Original Android Development] mskip:
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.
[Nexus 9 Original Android Development] 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.
[Nexus 9 Original Android Development] guinnes.s:
Yes decrypting the device effect the OTA'S , cannot install security update?
[Nexus 9 Original Android Development] scoobydu:
I unlocked my bootloader with the tool and then proceeded to remove encyption.

The tool falshed something to bypass the forced encryption piece and said it would reboot.

It didn't and I cannot get out of flashboot.

I have tried flashing a stock image and it fails, as well as trying to flash individual parts of the 6.01 stock immage.

Is there a way I can get back to stock 6.01 in order that I can root and instal TWRP please?
[Nexus 9 Original Android Development] scoobydu:
Flashed back to stock with the stock cable (rather than my xperia one) on my laptop; seemed to work and I am now back at 5.01 :)
[Nexus 9 Original Android Development] bluesharp:
Bootloop after 6.0.1 OTA update

Dear Mr. Skippen,

2 weeks ago I did a 6.0.0 to 6.0.1 OTA update and my device went into I a so called bootloop.

I tried everything on http://www.skipsoft.net/?page_id=1647 - without success.

The factory reset and the options in the recovery menu of the Nexus 9 did not help.

I cannot load a new image because I did not Enable the developer options nor the USB debugging via the menu when the device was OK.

I installed the SKIPSOFT UNIFIED ANDROID TOOLKIT and connected to my Nexus 9 (WiFi).

I connected successfully to the device and tried the UNLOCK BOOTLOADER part of the app.

It didn't work - it gives "ERROR - you have to enable debugging mode in order to unlock".

So, the question is: Can you unlock the bootloader with the SKIPSOFT UNIFIED ANDROID TOOLKIT if one did not Enable the enable developer options nor the usb debugging via the android menu?

If not, can you suggest to me what may be my options as I am stuck. Warranty of the device has just passed.

Thank you in advance,

S.
[Nexus 9 Original Android Development] mskip:
Device Module Auto Update Available

This has been a special round of updates for the latest google monthly updates and does not affect my commitment to updating the Samsung modules with the latest builds and procedures.

02ND FEB 2016

+Added Support [including root] for Volantis[wifi] 6.0.1 MMB29R

+Added Support [including root] for Volantisg[lte] 6.0.1 MMB29R

+Added above stock images to download/flash directly from Toolkit

+Updated checksum file for verifying stock image download

29TH JAN 2016

+Reconfigured root routines for a more logical [easier to follow] flow

+Added alternative locations to push file to if root/push file fails [automatic]

+Fixed some bugs when booting to various modes

+Updated/Added some more text to root routines to make it easier to understand

+Added a refresh screen option on build selection screen for plugging in device

+Updated the Any Build option to work correctly with any Android version/Build

If you want to donate to a device project to receive the pro updates please do it through the Toolkit (after selecting the device at startup) so you get the right code fast. Alternatively you can go to http://www.skipsoft.net/?page_id=703 and select the device you wish to activate.

Enjoy, Mark.
[Nexus 9 Original Android Development] DowntownRDB:
Good morning all. I just noticed that a device module auto-update is now available. Has latest factory images as well as TWRP 3.0.0.1. Thanks Mark for the update. :good: :good:
[Nexus 9 Original Android Development] mskip:
AUTOUPDATE AVAILABLE FOR NEXUS 9 DEVICE MODULE 1.2.3 [PRO ONLY]

Changelog:

+Added Support [including root,systemless root] for Volantis[WIFI] 6.0.1 MMB29V

+Added Support [including root,systemless root] for Volantisg[LTE] 6.0.1 MMB29V

+Added above stock images to download/flash directly from Toolkit

+Updated checksum file for verifying stock image download

+Updated TWRP custom recovery to 3.0.0.2 for standard and openrecoveryscript use

+Enabled ALLINONE and openrecoveryscript options for public testing [work fine]

+Made some changes to root procedures and reboot procedures

I updated public (free) versions a few weeks ago. Someone was supposed to post that in here but they didn't, sorry. It is 1.2.2 for now but I will update it to the latest once I have completed some more updates and added the Samsung Galaxy S7 modules to the Toolkit.

To update to 1.2.2, Non Pro users have a few steps (if you have already downloaded previous versions).

1. Exit the Toolkit if it is open.

2. Run ToolkitClean.exe from the installation folder (or the Start Menu)

3. Select your 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

If you download the new module files without installing the updated Toolkit then you will be prompted to update to the latest version after selecting your device.

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast.

Enjoy, Mark.
[Nexus 9 Original Android Development] mskip:
AUTOUPDATE AVAILABLE FOR NEXUS 9 DEVICE MODULE [V1.2.4] 22ND APR 2016 [PRO ONLY]

These are available for PRO users. I will try to update the Public (free) modules next week if I can as I now have to work on adding the Galaxy S7/S7 Edge and Note 5 to the Toolkit. I can then continue updating the Samsung device modules for the latest support.

Changelog:

+Added Support [including root] for Android 6.0.1 MOB30D [WIFI ONLY MODEL]

+Added Support [including root] for Android 6.0.1 MMB29X and MOB30D [LTE MODEL]

+Added above stock images to download/flash directly from Toolkit

+Updated checksum file for verifying stock image download

+Added option to keep existing recovery when flashing stock image to device

+Updated TWRP custom recovery to 3.0.2.0 for booting to/flashing to device

+Minor updates and bug fixes

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast.

Mark.
[Nexus 9 Original Android Development] mskip:
AUTOUPDATE AVAILABLE FOR NEXUS 9 DEVICE MODULE 1.2.6 [PRO ONLY]

Changelog:

+Added Support [including root] for Android 6.0.1 MOB30G [WIFI ONLY MODEL]

+Added Support [including root] for Android 6.0.1 MOB30G [LTE MODEL]

+Added above stock images to download/flash directly from Toolkit

+Updated checksum file for verifying stock image download

Public modules will be updated to current in 7-10 days approx. Some new devices are in the process of being added and once that is done I can look in to updating the public device modules.

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast.

Enjoy, Mark.
[Nexus 9 Original Android Development] broggyr:
Hiya Mark, tried to send you a small donation but PayPal keeps giving me an error...
[Nexus 9 Original Android Development] mskip:
Try again and thank you :)

Mark.
[Nexus 9 Original Android Development] mskip:
AUTOUPDATE AVAILABLE FOR NEXUS 9 DEVICE MODULE

Changelog:

+NEW FUNCTION [OPTION 10] Download Google OTA image, verify and sideload to device

Will download chosen OTA image from google servers and sideload in stock recovery

+Added info about who can apply ota updates and what will break it in the OTA Menu

+Tweaked a few procedures and updated information in root selection screen

+Minor updates and bug fixes

The public device modules will be updated to the latest version at the end of this month which will include the new google ota sideload function. If the Toolkit helps you please consider a donation. The Toolkit will not be able to run much longer without your support.

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast.

Enjoy, Mark.
[Nexus 9 Original Android Development] broggyr:
Just tried, still failed.
[Nexus 9 Original Android Development] nartan:
When the program gives me auto-update, I answer "yes" and apparently installed and then reoffered me and again I say "yes" and again asked me again and so on. I still in 1.2.6. I have PRO.
[Nexus 9 Original Android Development] mrcgp:
love this toolkit and have been using it for years now!

Started on N7 original wifi version then nexus 4, nexus 10 and now nexus 9. I have also used it for friends samsung devices to save there phones when the worst has happened!

would be nice if you have paid for a certain amount of devices that you get everything fully unlocked....just a thought to repay your returning customers!
[Nexus 9 Original Android Development] radialblur:
Me too, I too have pro, 1.2.6 says update available, press y, looks like it downloads, then restarts as 1.2.6 again asking if I want to update to 1.2.7 gave up after 6 attempts.

Update: Used Wireshark to grab the update URL, downloaded and applied manually, made no difference, stayed on 1.2.6 and tells me 1.2.7 is available, same loop.

Cheers.

R.
[Nexus 9 Original Android Development] mskip:
AUTOUPDATE AVAILABLE FOR NEXUS 9 DEVICE MODULE [PRO ONLY]

Changelog:

+Fixed update bug [device modules not updating to latest version]

+Updated Toolkit.exe base version to 1.4.6 with new code ready for next release version

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast.

Enjoy, Mark.
[Nexus 9 Original Android Development] mskip:
Sorry about that it should all work now.

Now working on the public updates and autoupdates for the new google June builds.

Mark.
[Nexus 9 Original Android Development] radialblur:
Cheers Mark, will give it a try later.
[Nexus 9 Original Android Development] radialblur:
Forgot to check back.. works great now, cheers Mark.