Develop Bugs

[GNEX TOOLKIT V11.1.0] Drivers, Backup, Unlock, Root, Recovery, Flash + MORE [GSM]

Frequently Asked Questions:
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. What is FASTBOOT?
Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.
It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
OR you can use the ToolKit to rename the files (root access needed).
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download, install and run the Unified Android Toolkit.
2. Install adb/fastboot drivers (if you havent already done so)
3. Option 9 to download a Google Factory Image.
4. After it finishes downloading you will be given the option to flash the image to your device. Do this.
4. Let the device reboot, then shut it down and re-enter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
5. Option3, 2 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped. Your device will now be back to an out-of-the-box FULLY STOCK state and ready to send back.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton) will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. The ToolKit recognises my device in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.
You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.
----------------------------------------------------------------------------
Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?
Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.
This option will NOT require your bootloader to be unlocked first.
You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.
You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.
The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I cannot find Developer options to Enable USB Debugging
With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:
Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
You can now go into Developer options and enable usb debugging.
----------------------------------------------------------------------------
Q. How do I Update to the latest Google Stock Rom (manually)?
THE FOLLOWING PROCESS WILL ERASE YOUR INTERNAL STORAGE BACKUP ANYTHING YOU NEED.
You can use the Android ToolKit which will do everything automatically.
Or you can follow the instructions and do it manually:
These steps assume that you have set up your adb/fastboot drivers correctly.
1. Download it from https://developers.google.com/android/nexus/images
2. Unzip the .tar file to a folder on your pc
3. Unzip the needed files from the .tar file to the same folder on your pc
4. Copy the file fastboot-windows.exe to this folder (you can find the fastboot file in many places including my ToolKit download on post#1) and rename the file to fastboot.exe
5. Boot the phone into Fastboot Mode (KEEP holding the 'Volume up' and 'Volume down' buttons while pressing the 'Power' button)
6. Connect your device via the usb cable
7. Browse to this folder on your pc and run the flash-all.bat file to flash the stock images
----------------------------------------------------------------------------
Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect
Make sure the code entered is for the correct device being used in the Unified Android Toolkit.
You need to make sure you start the Toolkit with the toolkit.exe file when activating so the settings can be initialised or the code will not be accepted.
Also make sure you enter the code correctly as the characters are case sensitive.

UPDATES:

[TOOLKIT] SKIPSOFT ANDROID TOOLKIT -GNEX - GSM- Drivers, Root, Recovery + MORE
SPRINT MODEL SUPPORTED *HERE*
VERIZON MODEL SUPPORTED *HERE*
GALAXY NEXUS - SUPPORTS ALL AVAILABLE VERSIONS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus 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
--------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
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, 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' 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 any procedures within this guide. No warranties of any kind are given.

Manual Rooting Instructions for Galaxy Nexus
VIDEOS:

Amazing thread! This thread would probably be really helpful for newbies
Just a few suggestions:
1.)You might want to include how to flash custom kernels
and also that you can
2.)Clockwork Recovery can be instealled through Rom Manager
Nonetheless, great thread

mohitrocks said:
Amazing thread! This thread would probably be really helpful for newbies
Just a few suggestions:
1.)You might want to include how to flash custom kernels
and also that you can
2.)Clockwork Recovery can be instealled through Rom Manager
Nonetheless, great thread
Click to expand...
Click to collapse
Thanks
1. Added Step 7, how to flash kernels and Radios via CWM.
2. Added a Note at the end of the CWM flashing step for the Rom Manager method.
Mark.

mskip said:
Thanks
1. Added Step 7, how to flash kernels and Radios via CWM.
2. Added a Note at the end of the CWM flashing step for the Rom Manager method.
Mark.
Click to expand...
Click to collapse
No problem, and thanks for the additions
EDIT: Nevermind, didn't read the thread properly, sorry

Are you completely sure this will work with the LTE version? Being that it comes out tomorrow, I have yet to get mine. I also think it may be a christmas present.....nonetheless, I don't know if Verizon has made any changes to the bootloader or not. Have I anything to worry about or am I just being paranoid?

_AI_ said:
Are you completely sure this will work with the LTE version? Being that it comes out tomorrow, I have yet to get mine. I also think it may be a christmas present.....nonetheless, I don't know if Verizon has made any changes to the bootloader or not. Have I anything to worry about or am I just being paranoid?
Click to expand...
Click to collapse
The bootoader and root steps will definitely work paul has confirmed in his thread that superboot will work on LTE devices. Im not sure if CWM has been tested on an LTE device but if it doesnt work the stock Recovery image can easily be flashed via fastboot. Once you have CWM then you just need to find a Rom that will work on LTE devices as im not sure if the Roms are different.
No need to be paranoid as the GN is close to unbrickable as long as you can enter fastboot
Mark.

Very much appreciated! Thank you for the time and effort you put in to help out others. Coming from my G1, I am not up to date with the newer methods and this certainly gave me confidence to go forth with my GNEX.

I've flashed CWM through ROM Manager but still get the stock recovery in recovery mode - isn't that a fake flash anyways? Does anybody know if you can restore a nandroid via the stock recovery?
Sent from my GN

Hey thanks you alot, made me more comfortable messing with me "GN".
Much appreciated
Regards
Schmee

Thank you sir for taking the time to write this. Just went through the process successfully to flash a stock Google rom to remove the Samsung one from my phone as I want to get the rom updates quicker via Google vs waiting for the Samsung port. However, to ensure I get the updates via OTA, do I have to unroot/ relock bootloader? Does it hurt anything leaving it as is or do we need to button down again.
Thanks in advance.

Awesome thread!
Quick Q though, if im currently using a custom ROM, when i use the advanced restore option in CWM, can someone quickly describe what each option will do to my phone?
ie.
Whats will happen if im running custom ROM and i select restore boot? restore system? restore data? restore cache? restore sd-ext?
Thanks in advance!

I have unlocked the bootloader, and flashed cwm. When I try to install from sdcard, I get this error: E:Can't mount /sdcard/
Any suggestions?

tristan202 said:
I have unlocked the bootloader, and flashed cwm. When I try to install from sdcard, I get this error: E:Can't mount /sdcard/
Any suggestions?
Click to expand...
Click to collapse
To copy the rom to your Internal Storage you need to reboot your phone into Android, then connect the usb cable and copy it across using your file manager. Then you can reboot into CWM and flash the Rom.
Mark.

ahqball said:
Awesome thread!
Quick Q though, if im currently using a custom ROM, when i use the advanced restore option in CWM, can someone quickly describe what each option will do to my phone?
ie.
Whats will happen if im running custom ROM and i select restore boot? restore system? restore data? restore cache? restore sd-ext?
Thanks in advance!
Click to expand...
Click to collapse
I will add this to the FAQ as I build it up:
> Restoring boot will restore your boot image which contains the kernel. Useful if you try custom kernels and something goes wrong with it.
> Restoring system will restore your system files (Rom).
> Restoring data will restore your installed apps. Good if you install a new rom and do a wipe before flashing (which will format the data partition). If you flash a new Rom without wiping the data partition isnt usually touched.
> Not exactly sure about cache..
> Galaxy Nexus doesnt have sd-ext so no need to worry about that.
Mark.

TorontoR said:
Thank you sir for taking the time to write this. Just went through the process successfully to flash a stock Google rom to remove the Samsung one from my phone as I want to get the rom updates quicker via Google vs waiting for the Samsung port. However, to ensure I get the updates via OTA, do I have to unroot/ relock bootloader? Does it hurt anything leaving it as is or do we need to button down again.
Thanks in advance.
Click to expand...
Click to collapse
Not so sure how a stock image is affected. At worst case you will still get the update notification but the install will fail. As long as you have the latest build on your phone then you wont get any notification so you could easily flash the latest CWM Stock image as it is made available.
You just cant hurt this monster
Mark.

DJ "suMo* said:
I've flashed CWM through ROM Manager but still get the stock recovery in recovery mode - isn't that a fake flash anyways? Does anybody know if you can restore a nandroid via the stock recovery?
Sent from my GN
Click to expand...
Click to collapse
There is an auto recovery restore system on stock android builds so when the phone is rebooted it restores the stock recovery image.
Remove 'recovery-from-boot.p' from /system and it wont restore the stock recovery after you flash CWM.
Mark.

Thanks for this. Do you have to delete or can you just rename that file?

[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE

SAMSUNG GALAXY NOTE 4 - SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
SUPPORTED MODELS/VARIANTS
ASIA, EUROPE EXYNOS LTE [SM-N910C] [Supported up to 6.0.1]
EUROPE MODEL QCOMM LTE [SM-N910F] [Supported up to 6.0.1]
SINGAPORE,INDIA,AUS QCOMM LTE [SM-N910G] [Supported up to 6.0.1]
US SPRINT QCOMM LTE [SM-N910P] [Supported up to 6.0.1]
US TMOBILE QCOMM LTE [SM-N910T] [Supported up to 6.0.1]
CANADA QCOMM LTE [SM-N910W8] [Supported up to 6.0.1]
The Unified Android Toolkit brings together all the Nexus 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
--------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
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 Hard Reboot the device
1. Unplug the USB cable.
2. Hold down the 'VOLUME DOWN' + 'POWER' buttons for about 5-15 seconds until the device reboots
How to get into Recovery Mode
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME UP' + 'POWER' buttons for about 5-15 seconds until you see the Samsung logo on the screen.
3. Release all buttons straight away to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME DOWN' + 'POWER' buttons for about 2-15 seconds until a WARNING! Screen appears.
3. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.

**UPDATES**

**VIDEOS**

**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry).
----------------------------------------------------------------------------
Q. Does flashing a custom image increase my flash counter?
Any image that is flashed via Odin that has been modified will increase the flash counter that can be viewed in the Download Mode on your device (if booted by holding the Volume Down, Home and Power buttons). You can reset the flash counter using an app by Chainfire called Triangles Away and can find instructions on how to use that in the Downloads section in the Toolkit.
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.
----------------------------------------------------------------------------
Q. "Superuser/SuperSU has stopped" message after rooting
After updating Samsung device to newer builds of Android [4.3 and later] which contains the new security from Samsung "Samaung KNOX", you might face a problem if you tried to root your device.
This might happen because of KNOX security, it blocks/disables the Superuser app and you will see this notification after the first boot:
"Unfortunately, SuperSU has stopped" or "Unfortunately, Superuser has stopped" depending on the root method you used.
The easiest way to fix this problem is by installing the superuser apk file. Select option 6 from the Rooting Section and the Toolkit will attempt to extract the superuser.apk file from the root zip file in the Root folder and if successful it will then be installed. You can then run the app [Superuser or SuperSU] from the apps list. A warning message will pop up saying Samsung KNOX has been detected and ask if you want to try and disable it. Click OK, KNOX should be disabled and your device should now be properly rooted.

Thanks for this great software

Any chance of getting this working for n910u?...
...
...please? :fingers-crossed:

eternal-intent said:
Any chance of getting this working for n910u?...
...
...please? :fingers-crossed:
Click to expand...
Click to collapse
The n910u is a exynos based device so if you select the n910c at the model selection screen(option 01) then it should work. If it does please let me know and I will add it to the list (with supported stock images).
Mark.

Thanks for your great efforts.
I'm a Nexus user, and totally new to Samsung. I wanna ask if internal storage contents will be erased after rooting like Nexus devices? (I guess not, because it's erased during unlocking Nexus bootloader, but I'm not very sure)

GialanG said:
Thanks for your great efforts.
I'm a Nexus user, and totally new to Samsung. I wanna ask if internal storage contents will be erased after rooting like Nexus devices? (I guess not, because it's erased during unlocking Nexus bootloader, but I'm not very sure)
Click to expand...
Click to collapse
Internal storage is not erased during rooting or by flashing stock firmware images on samsung devices. The only thing that will affect Internal Storage is a factory reset/wipe.
Mark.

Always used your toolkits, thanks man.

thanks for this.
loved it. will explore more. :good::good:

Confirmed working on the Bell Canada version of the SM-N910W8 Note 4. Only issue of note was the fact that on first boot after flashing customer recovery, the stock recovery reinstalled itself. Simple matter of following the easy-to-use instructions with the toolkit. As soon as the flash is complete, manually boot into recovery and re-flash the recovery from TWRP. This will allow recovery to stick after booting up.
Excellent job as always.

Does root through this tool increase Knox counter?
Sent from my SM-N910T using XDA Free mobile app

Does root through this tool increase Knox counter?
Click to expand...
Click to collapse
I'm fairly sure it does.
Also, this part needs a little editing:
You can reset the flash counter using an app by Chainfire called Triangles Away and can find instructions on how to use that in the Downloads section in the Toolkit.
Click to expand...
Click to collapse

Also, of note, a lot of people ask if they will be able to update their device OTA after following the root procedure. Right after I successfully acquired root with MSkip's toolkit, I checked the status of my device and it showed "CUSTOM." This is to be expected. Checked for an update and got the expected "your device has been modified" message. But I installed the xPosed framework and installed theWanam module - it includes a feature to change the device status from "CUSTOM" to "OFFICIAL." Did this and rebooted and sure enough, device status now shows "official" and checking for an update only returned the message "the latest updates have already been installed." So now just wondering if I can apply the 5.0 update when it comes out over the next couple weeks and if we can re-root using the toolkit, but I doubt we'll know for sure until the update comes out.

Hi Mark,
many thanks for the new toolkit, it works great as allother and i get the pro key now for the Note 4 too.
many regards
EDIT
TWRP recover 2.8.4.0 for N910F is available now > http://www.techerrata.com/browse/twrp2/trltexx

N910G here!
i have always liked using the toolkits for rooting my devices. It's easier than manual flahsing. So I was wondering if this will work on my N910G?

Just a heads up... TWRP 2.8.5.0 is on the SM-N910F now PS Great Toolkit

acmilan77051 said:
i have always liked using the toolkits for rooting my devices. It's easier than manual flahsing. So I was wondering if this will work on my N910G?
Click to expand...
Click to collapse
Select the N910F from the model selection and try the root procedure. It should work fine. If it does then I will add support for that variant.
Mark.

Update
I have updated the module files (that are downloaded after the Note4 is selected at startup) to fix several config settings, update some Toolkit functions and update TWRP for all variants to 2.8.5.0. The unroot zip file has also been fixed/updated.
Supported models/builds list: http://www.skipsoft.net/?page_id=1203
Download from: http://www.skipsoft.net/?page_id=1069 if you don' already have the Toolkit
If you have already downloaded the new Toolkit and have the v1 module for the Note 4 then delete the ConfigGalaxyNote4.exe and the _currentrecoveryversionGalaxyNote4.ini from the tools folder and the Unroot-UninstallBusybox-CwmManager.zip from the root folder. Download the new unroot zip file from http://skipsoft.net/download/fileupdates/Unroot-UninstallBusybox-CwmManager.zip and move it to the root folder, start the Toolkit and select the Galaxy Note 4 from the list. The Toolkit will then download new module files.
I will also push an AutoUpdate with the same updates/fixes for Pro users to automate the whole above procedure.
Mark.

[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - NEXUS PLAYER - Drivers,Unlock,Root,Flash Stock

NEXUS PLAYER - SUPPORTS ALL VERSIONS UP TO LATEST ANDROID 7 BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
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
--------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
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. Flip your device over so you can see the button on the bottom.
2. Unplug the power connector, hold in the button on the bottom of the device and plug the power connector back in. You will see the power light come on.
3. Keep holding the button until it starts pulsing [and the Google logo appears on the screen] then release the button immediately to enter Fastboot Mode.
How to get into Recovery Mode
1. Boot to Fastboot Mode as above.
2. Select 'Recovery' by Short Pressing [less than a second] the button on the bottom of the device until 'Recovery' is displayed.
3. Long Press [3 seconds] to enter Recovery Mode.
4. In Stock Recovery Long Press the device button to show the Recovery Menu.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.

** UPDATES **

** VIDEOS **

I'm proud to add support for the Asus Nexus Player to the SkipSoft Unified Android Toolkit
As there is no custom recovery yet for the Nexus Player I have built a self rooting boot image which is extremely easy and fully tested to be safe. The SkipRoot boot image will fully remove any previous root and also install the busybox binaries and remove the recovery restore file. It is built on Chainfires SuperSU v2.46. There is also a working insecure boot image which can be booted/flashed to the device to give full adb root access.
Enjoy (and please give feedback).
Mark.

I just realised that the download link from post#1 was still downloading 1.3.4.
This has now been fixed and downloads the new version 1.3.5 with Nexus Player support from the link.
Mark.

Hi,
question:
i've got my nexus player into fastboot but my linux pc does not recognze it, at the screen i can see "fastboot offline" , is my fastboot outdated or coul be something i've forgot to do?
im updating my fastboot now but i would like to have some help.
thaks

ErikMunoz said:
Hi,
question:
i've got my nexus player into fastboot but my linux pc does not recognze it, at the screen i can see "fastboot offline" , is my fastboot outdated or coul be something i've forgot to do?
im updating my fastboot now but i would like to have some help.
thaks
Click to expand...
Click to collapse
There are a few things that can cause trouble with fastboot commands on linux. If you have installed adb and fastboot then sometimes just rebooting your device and pc can fix it but if not google is your best bet for some fixes.
Mark.

Update
I have remade the skiproot boot image to be much more efficient installing root and busybox. If you delete the boot*fugu.img files from the tools menu and restart the Toolkit then the new files will be downloaded after you select your build.
Please let me know how it goes.
Mark.

UPDATE - FULL SUPPORT ADDED FOR ANDROID 5.1.1 LMY47V
The public module files have been updated to include full support for Android 5.1.1 LMY47V.
I have also added a Superuser fix if the SuperSU app doesn't show in the apps bar after rooting (App fixes, section 19)
To make it easier to get the updated files I have made a small program to clean all the files related to a specific Android Toolkit device.
Download and copy the ToolkitClean.exe to the Toolkit installation folder (same as toolkit.exe).
Make sure the Toolkit is closed and run ToolkitClean.exe.
Select the Nexus Player from the list (option 09), type y or yes and all module files will be cleaned.
When asked if you want to Exit and restart the Toolkit type y or yes.
Select the Nexus Player from the device list (09) and new module files will be downloaded including firmware/root support for Android 5.1.1 LMY47V.
Download link: HERE
Mark.

Will this toolkit update bootloaders? I am currently running the 5.0.x bootloader and would like to update to 5.1. Thanks

ecsnead69 said:
Will this toolkit update bootloaders? I am currently running the 5.0.x bootloader and would like to update to 5.1. Thanks
Click to expand...
Click to collapse
It doesn't flash the single bootloader image but if you download/flash the 5.1.1 image from the Toolkit then the bootloader will be updated during the process.
If you want to JUST flash the bootloader then you can download the latest bootloader from skipsoft *HERE* then move it to the Unified Android Toolkit folder (same location as Toolkit.exe) and do the following:
Open a command prompt (option 25 from the Main Menu)
Boot to fastboot mode (adb-toolkit reboot bootloader)
Flash the bootloader image (fastboot-toolkit flash bootloader bootloader-fugu-fugu-02.09.img)
Reboot to fastboot to check its changed (fastboot-toolkit reboot-bootloader)
Reboot back to Android (fastboot-toolkit reboot)
I will add an automated process to the Toolkit in the next few days to download a stock image for the selected device, then extract whatever part they need (bootloader, boot, system, recovery) and flash it directly. May be useful to some people who are having problems.
Mark.

Thanks

I am at this screen now . what option should i choose so that i can update my player to 5.2 ? I have a unlocked boot loader with root.

Select 30. Magic
because 5.2 doesn't exist and it would take some sort of magic to get it.
However it you actually meant 5.1.1 you can select 9. Download ... Google Factory Stock Rom.

TWRP is available for NP now

Can't unlock the bootloader on 5.1.1 with this tool. It keeps stating that the bootloader is already unlocked.

i love this program and donated to it and would love to recommend a donator feature if possable.
could it be possable to use this idea http://forum.xda-developers.com/nex...ent/data2usb-boot-image-nexus-player-t3115752 but was for noobs like myself so do this for use.
The idea being i could plug in the ssd via otg to the player and it would download the firmware i wanted and auto modify the image and then install it so it was just ready to go from the box. i understand a iy twould need to use the multi usb port block which are cheap

slonn said:
Can't unlock the bootloader on 5.1.1 with this tool. It keeps stating that the bootloader is already unlocked.
Click to expand...
Click to collapse
I am also having this issue. OP is there something we can do about this? The tool is nice but i can't get it to work
Edit: rooted with chainfires root, not autoroot. SuperSU never got installed so I used this program to reinject the apk and verified root easily. Programs very nice just some flaws with the newest update on the nexus players comparability.

hello I have my nexusplayer with android toolkit with the application of pro donation, but I can not install root, app superurser not install applications, I have installed and also for recovery mode either,
I can do ???
thanks

Only way I could get busybox installed was to get the pro version and
Sideload it. Other than that, this tool was totally worth the money.

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

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
--------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
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.

**FAQ**

**VIDEOS**

**UPDATES**

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.

Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P

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.

Hi, have already bought the PRO !!(but no Np6 yet ) :good:

mskip said:
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.
Click to expand...
Click to collapse
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!

joedeveloper said:
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!
Click to expand...
Click to collapse
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.

mskip said:
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.
Click to expand...
Click to collapse
Perfect thanks! I'll let you know tonight. I'm present on the K build as I just got the OTA today.

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.

mskip said:
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.
Click to expand...
Click to collapse
Do we know if decrypting will prevent us from taking OTAs?

Hi im getting this error for build mda89d

pro4ever said:
Hi im getting this error for build mda89d
Click to expand...
Click to collapse
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

pro4ever said:
Hi im getting this error for build mda89d
Click to expand...
Click to collapse
I must have set something wrong I will look at it when I get home.
Mark.

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.

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

hutzdani said:
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 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
Click to expand...
Click to collapse
qfuse is still intact after all that?

opz187 said:
qfuse is still intact after all that?
Click to expand...
Click to collapse
Sure is still enabled - but i can't boot into android it just bootloops forever
i can't get the system image to work from the servers - flashing everything manually and then re locking ends up in a boot loop aswel.
i'll keep trying

Question [CLOSED] Root, and get Custom Bootanimation and Custom Font OnePlus 9 Pro includes T-Mobil variant

Hi All,
First of all, I am not responsible for the final outcome of your device. This is a choice you have made. This is what I did to get the phone I have want for years now. Follow these steps to “unlock bootloader, install root, and make certain partitions R/W”. By doing so you can install a custom bootanimation and custom fonts with apps from the Google Play Store. Make a full backup of device storage because you will be wiping your phone. Backup phone by connecting to PC and copy all necessary folders from phone storage to a temp folder on PC desktop (documents, downloads, pictures, dcim, music, videos etc). My device apps were auto backuped by Google Account. I copied and pasted the device storage to my laptop. This is all down on a windows 10 laptop. Using the ADB and Fastbbot tools from the android platform tools. Caution, if you are not use to rooting devices, don't do this!
Requirements: Use good quality USB cable when connecting to PC Phone must be fully unlocked (check settings/about phone and scroll all the way to bottom for unlock status) Download and install the latest Android Platform Tools to preferable to C:\adb (https://rb.gy/8yeouu) . Disable driver signing on your PC (https://rb.gy/8iva24) Download and install OnePlus USB drivers (https://rb.gy/awepqe). Download and install Qualcomm USB drivers (https://www.gadgetsdr.com/qualcomm-usb-driver/). Must be on Android 11 (not Android 12 there is a special step included to downgrade)
1) phone must be fully unlocked from T-Mobile.
2) Device needs to be on Android 11! Mandatory
If on Android 12, downgrade to 11 with this link and update once!!!!!
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
3) do not restore or setup phone at this time but connect to WIFI, go into settings/about phone and tap several time to enable developer settings. then in system/developer settings enable OEM Unlock and enable USB Debugging and disable Auto Update!
4) Unlock the bootloader with this link.....https://rb.gy/8f0psw (the phone will factory reset and then boot to system
5) Use this link to gain root... https://rb.gy/dtsb2n
6) download flashable Magisk from here and copy to internal storage on device....https://www.rootingsteps.com/magisk-zip/
7) install TWRP from this link https://twrp.me/oneplus/oneplus9pro.html and while in TWRP flash the Magisk zip file.
Boot to system and open the Magisk Manager and click the upper install to direct path.
8) download this script and move it to phone internal storage.....https://rb.gy/pcdquz then boot to TWRP recovery and flash the zip. the phone will boot to system....enjoy
9) install from Goole Play Store Bootanimation changer by jimmy rum and Fontfix.
Now you can install a custom bootanimation and custom font.
Questions, just ask......
TheGhost

MOD ACTION:
Thread closed as duplicate of https://forum.xda-developers.com/t/...eplus-9-pro-includes-t-mobil-variant.4467317/