[TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P - Drivers, Unlock, Flash Stock, Root

Search This thread

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,067
Norfolk
NEXUS 6P - SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID BUILDS.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*

NOTE: There is no insecure kernel available yet so those options have been disabled in the Toolkit. I will make some and enable the options as soon as possible.

The Unified Android Toolkit brings together all the Nexus, Google OnePlus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.

FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device

--------------------------------------------------------------
Toolkit_main_menu.png

--------------------------------------------------------------

SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*

DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)

NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.

Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.

--------------------------------------------------------------

WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.

ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).

MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.

AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv

--------------------------------------------------------------

PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.

--------------------------------------------------------------

1. INSTALLING ADB/FASTBOOT DRIVERS

The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.

THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.

If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.

Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.

On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.

--------------------------------------------------------------

2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT

When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.

Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).


--------------------------------------------------------------

USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down', 'Volume Up' and 'Power' buttons to boot the phone into FastBoot Mode

How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery

Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.

--------------------------------------------------------------

*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
 
Last edited:

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,067
Norfolk
This is the first release for the Nexus 6P module.

There is no custom recovery (TWRP should be along in a few days), insecure boot image and no root yet. As soon as TWRP becomes available then root routines can be enabled and new public device modules will be uploaded for general use.

All other functions are enabled including installing drivers, performing an adb backup, unlocking/relocking the bootloader (using fastboot flashing command), pushing/pulling files to or from the internal storage, making a logcat and countless other functions that are available.

Explore, Enjoy and as ever please leave feedback. If you think something can be improved I would like to know.

Mark.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,067
Norfolk
Can anyone flash a repacked boot image for any of the 2 available builds (MDA89D or MDB08K) that I have patched to allow root. I just want to see if my kernel rebuild tools are working for the Nexus 6P so I can make the patched images for the builds that don't have support (also for disabling encryption). If the image does not boot its an easy process to fix it, just rebooting manually back to fastboot and flashing the stock boot image back.

Would prefer someone who knows what they are doing with adb/fastboot (so they dont freak out if the image doesnt boot) but I can walk anyone through it if needed. Just let me know what build you are on so I can post the right one for testing.

Mark.
 
  • Like
Reactions: AngryDinosaur

joedeveloper

Senior Member
Jul 24, 2009
497
103
Las Vegas
Can anyone flash a repacked boot image for any of the 2 available builds (MDA89D or MDB08K) that I have patched to allow root. I just want to see if my kernel rebuild tools are working for the Nexus 6P so I can make the patched images for the builds that don't have support (also for disabling encryption). If the image does not boot its an easy process to fix it, just rebooting manually back to fastboot and flashing the stock boot image back.

Would prefer someone who knows what they are doing with adb/fastboot (so they dont freak out if the image doesnt boot) but I can walk anyone through it if needed. Just let me know what build you are on so I can post the right one for testing.

Mark.

I have a bit of experience on your tools. Thoroughly utilized your GNEX toolkit when I had my gnex. I'll see if I can test this out tonight if no one else has before then!
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,067
Norfolk
I have a bit of experience on your tools. Thoroughly utilized your GNEX toolkit when I had my gnex. I'll see if I can test this out tonight if no one else has before then!
Thanks. Try fastboot boot the image first just to see if it boots (save you having to flash the stock image back if it doesn't work). If it does then you can fastboot flash boot the image so it sticks.

I don't know what build you are on so I will post both kpatch images and stock images in case they don't work:
http://skipsoft.net/tempuploads/boot_images/Nexus6P-boot-images.zip

To anyone else please do not try flashing these unless I have talked to you and you know what you are doing. These are still test images and I dont know if they work yet.

Mark.
 
Last edited:
  • Like
Reactions: garylgray

joedeveloper

Senior Member
Jul 24, 2009
497
103
Las Vegas
Thanks. Try flashboot flash the image first just to see if it boots (save you having to flash the stock image back if it doesn't work). If it does then you can fastboot flash boot the image so it sticks.

I don't know what build you are on so I will post both kpatch images and stock images in case they don't work:
http://skipsoft.net/tempuploads/boot_images/Nexus6P-boot-images.zip

To anyone else please do not try flashing these unless I have talked to you and you know what you are doing. These are still test images and I dont know if they work yet.

Mark.

Perfect thanks! I'll let you know tonight. I'm present on the K build as I just got the OTA today.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,067
Norfolk
CUSTOM RECOVERY, DECRYPTION AND ROOT NOW AVAILABLE

I have just uploaded new Nexus6P module files for the Unified Android Toolkit to enable decryption, flashing custom recovery (thanks to TeamWin) and rooting.

Users that have already installed the toolkit you need to run ToolkitClean.exe and select the Nexus6P to clean the module files. You can then select the Nexus6P from the device selection screen to download new module files with everything updated (recovery/rooting enabled).

Mark.
 

zedlor

Senior Member
May 1, 2012
135
24
North West UK
CUSTOM RECOVERY, DECRYPTION AND ROOT NOW AVAILABLE

I have just uploaded new Nexus6P module files for the Unified Android Toolkit to enable decryption, flashing custom recovery (thanks to TeamWin) and rooting.

Users that have already installed the toolkit you need to run ToolkitClean.exe and select the Nexus6P to clean the module files. You can then select the Nexus6P from the device selection screen to download new module files with everything updated (recovery/rooting enabled).

Mark.
Do we know if decrypting will prevent us from taking OTAs?
 

evobyte

Senior Member
Oct 20, 2012
126
52
Hi im getting this error for build mda89d

You probably are in the "D" VERSION... Download Google's factory image from his app, make sure you download the one ending with "K". Flash the factory image to phone and re do the process. I had the same error. That's what I did to fix it
 

evobyte

Senior Member
Oct 20, 2012
126
52
also once i flash twrp, its just not sticking??? I can boot into it through the options, but if i hold power button + up it takes me to the android guy, also if i go through fastboot and select recovery, i still get the android guy.
 

hutzdani

Senior Member
May 9, 2010
1,222
357
London
Lol somehow TWRP wont stick and flashed the boot image and soft bricked Yay !

Can temporally boot into TWRP still

Flashed stock images again manually, but still no booting :D eek might have to relock the bootloader to get it to boot

So far not so good. . . ..

1. Temp flashed TWRP and booted to recovery to see the SD contents where gone.
2. Flashed the K build patch and the boot.img
3. This device is Corrupt message - BOOT LOOP
4. Flashed manually back to stock ( Bootloader / Recovery / Radio / System e.c.t)
5. Still bootloop
6. Relocked bootloader - still bootloop
7. Good new QFUSE is still Enabled - all that crap is utter ball****

Now not sure what to do - letting it seemingly boot for a while after flashing the stock image
 
Last edited:

opz187

Senior Member
Sep 30, 2012
1,459
480
Lol somehow TWRP wont stick and flashed the boot image and soft bricked Yay !

Can temporally boot into TWRP still

Flashed stock images again manually, but still no booting :D eek might have to relock the bootloader to get it to boot

So far not so good. . . ..

1. Temp flashed TWRP and booted to recovery to see the SD contents where gone.
2. Flashed the K build patch and the boot.img
3. This device is Corrupt message - BOOT LOOP
4. Flashed manually back to stock ( Bootloader / Recovery / Radio / System e.c.t)
5. Still bootloop
6. Relocked bootloader - still bootloop
7. Good new QFUSE is still Enabled - all that crap is utter ball****

Now not sure what to do - letting it seemingly boot for a while after flashing the stock image

qfuse is still intact after all that?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 57
    NEXUS 6P - SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID BUILDS.
    SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*

    NOTE: There is no insecure kernel available yet so those options have been disabled in the Toolkit. I will make some and enable the options as soon as possible.

    The Unified Android Toolkit brings together all the Nexus, Google OnePlus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.

    FUNCTIONS OF UNIFIED ANDROID TOOLKIT
    * Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
    * Backup/Restore a single package or all apps, user data and Internal Storage
    * Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
    * Unlock/Re-Lock your Bootloader [Nexus]
    * Root Stock builds
    * Various Root options using insecure boot image or custom recovery
    * ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
    * ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
    * [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
    * Install BusyBox on your device
    * Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
    * Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
    * Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
    * Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
    * Extras, Tips and Tricks section
    * Auto Update ToolKit to latest available version at startup (professional only feature)
    * Program up to 10 Quickpick slots and run them very quickly (professional only feature)
    * Mods section to automatically perform certain tasks on your device
    * Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
    * Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
    * Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
    * Flash Custom Recovery or Google Stock Image to Device
    * Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
    * Rename the Recovery Restore File present on some Stock Roms
    * Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
    * Flash Custom Recovery to Device
    * Boot [Nexus] or Flash .img Files directly from your PC
    * Install a single apk or multiple apk’s to your device
    * Push Files from your PC to your device
    * Pull Files from your device to your PC
    * Disable forced encryption on Nexus6 and Nexus9 devices
    * Install Root Checker app by Burrows Apps
    * Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
    * Install EFS/Partition Backup/Restore app by Wanam
    * Dump selected LogCat buffers to your PC
    * Dump BugReport to your PC
    * Set Files Permissions on your device
    * Open new Command Prompt for manual input
    * Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
    * Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
    * Display Important Information about your device

    --------------------------------------------------------------
    Toolkit_main_menu.png

    --------------------------------------------------------------

    SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*

    DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)

    NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.

    Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.

    --------------------------------------------------------------

    WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
    THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.

    ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
    THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
    THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
    PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).

    MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.

    AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv

    --------------------------------------------------------------

    PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.

    --------------------------------------------------------------

    1. INSTALLING ADB/FASTBOOT DRIVERS

    The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.

    THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.

    If drivers are not installed or there is an exclamation mark next to the device:
    Plug the device in to a usb cable directly connected to your motherboard.
    In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
    Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
    If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
    If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
    Click OK and select Google ADB Interface.

    Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.

    On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.

    --------------------------------------------------------------

    2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT

    When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.

    Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).


    --------------------------------------------------------------

    USEFUL INFORMATION
    How to get into your FastBoot Mode
    1. Turn your phone off
    2. Unplug your usb cable if you have one plugged in
    3. Keep holding the 'Volume Down', 'Volume Up' and 'Power' buttons to boot the phone into FastBoot Mode

    How to get into Recovery
    1. First boot into FastBoot Mode as described above
    2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery

    Show the Menu in the Stock Recovery Screen
    1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.

    --------------------------------------------------------------

    *DISCLAIMER*
    I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
    15
    AutoUpdates Available for Nexus 6P device module 1.2.7 !!ANDROID 7!! [ALL Users]

    Changelog:
    +Added Support [including root] for Android 7.0.0 NRD90U
    +Added Support [including root] for Android 6.0.1 MTC20L
    +Added above STOCK firmware AND OTA images to download/flash directly from Toolkit
    +Updated everything in Toolkit to work with new firmware zip files from google (checksums, unpacking)
    +Added much improved Drivers section in Startup [DR] and Toolkit Main Menu
    +Improved Root file checker/downloader at device module startup

    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.
    1. Exit the Toolkit if it is open.
    2. Run ToolkitClean.exe from the intallation folder (or the Start Menu)
    3. Select option 62 to update the Toolkit base to the latest version with root update bug fixes and improved drivers screen
    4. Select the device from the list
    5. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
    6. Restart the Toolkit, select the device and new module files will be downloaded/installed

    Please let me know if everything is working as I have done a lot of work on this version. If the Toolkit tries to detect your device and gives the message 'error: no devices/emulators found' then the installed drivers aren't workingin that mode. Follow the steps in the Drivers Section to uninstall the driver in the mode you are in and replace it with the Google adb driver. It should work then.

    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 and can update to the latest version. You can also go ULTIMATE mode now and unlock ALL device modules for the lifetime of the Toolkit. Follow me on twitter at https://twitter.com/mskipxda for posts/updates.

    Enjoy, Mark.
    13
    Sorry I haven't been around for a few weeks I have been away.

    I have added SuperSU systemless root by chainfire to the Toolkit as it works very well and I am starting to push updates for Android 6.0.1 support. I finished the Nexus 5 update last night and will definitely be doing the Nexus 6P and 5X today. I haven't had a chance to read the posts since my last one but will read them all when I get back from dropping the kids at school, respond to any outstanding ones and start working on the 6.0.1 update. Just wanted to let you guys know I haven't forgot you since you have all been soo great :)

    Mark.
    13
    I appologise that I have taken soo long with the March updates. Family emergencies and a car crash to deal with took my time away from other things. March updates are now being rolled out to all Nexus devices and April updates will be completed within 2 days of the images being released by google (usually within the first week of the month). I understand peoples frustrations after paying for pro versions but I assure those people that it's worth it. I have also spent more time testing than normal because I wanted to make sure twrp 3 was fully compatible and would not mess things up. That's all.

    ---

    AUTOUPDATE AVAILABLE FOR NEXUS 6P DEVICE MODULE 1.1.3 [PRO ONLY]

    Changelog:
    +Added Support [including root,systemless root] for Android 6.0.1 MMB29V, MHC19I
    +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.1 for standard and openrecoveryscript use
    +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.1.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.1.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.
    11
    Just caught the April Updates and downloading now. I will push an update for the Nexus 6P tomorrow FIRST as you lot have been soo great. Will put out public updates for all current builds as soon as the Samsung Galaxy 7 and 7edge have been added. I promised that to a few people before the April updates came out.

    I have also just updated the md5 check file with the new april update images which every toolkit (pro or public) will update at start up. This means if you don't want to wait for the update you can download the image from googles servers and flash via the toolkit.

    Mark.