[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY S6 EDGE - Drivers, Root, Recovery + MORE - Galaxy S6 Edge Original Android Development

SAMSUNG GALAXY S6 EDGE - SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
SUPPORTED MODELS
GLOBAL MODEL LTE [SM-G925F]
US SPRINT LTE MODEL [SM-G925P]
US TMOBILE LTE MODEL [SM-G925T]
US CELLULAR LTE MODEL [SM-G925R4]
CANADA LTE MODEL [SM-G925W8]
LATAM, SINGAPORE, INDIA, AUSTRALIA MODEL [SM-G925I]
Click to expand...
Click to collapse
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
Enable Developer options for usb debugging
Go to Settings, System section, About device and tap on 'Build number' 7 times until it says you are now a developer. You can now go to Settings, System section, Developer options and enable USB debug.
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

The latest versions of TWRP have problems with sideloading files and with openrecoveryscript which the ALLINONE procedure uses (which is why most of the devices are still using TWRP 2.7). If your module uses a 2.8 version and you have problems with the above just select the push option which will always work.
Also Chainfire updated SuperSU beta (2.49) with a fix for the deepsleep problem so select that version until the release version has been updated.
Mark.

**FAQ**

**VIDEOS**

Thanks man

any plans for G925L support?

Where are you getting your twrp recoveries from?

You sir are awesome. I will gladly donate for the pro version.

thanks man

Downloaded the toolkit, donated, converted to Pro.
Anything I'm doing I got 2.8.6.0 was unexpected at this time.
Pls Help. What's wrong ?

iigrs said:
Downloaded the toolkit, donated, converted to Pro.
Anything I'm doing I got 2.8.6.0 was unexpected at this time.
Pls Help. What's wrong ?
Click to expand...
Click to collapse
I have the same problem after donating to pro version.

Has anyone used this to put TWRP on Sprint Edge?

Thanks a lot !! ☺ ?

Any one use it and can confirme it's OK , what about deep sleep ?
Sent from my SM-G925F using XDA Free mobile app

ra_eng said:
I have the same problem after donating to pro version.
Click to expand...
Click to collapse
Is there a way to provide us some help regarding the problem we face with the Pro donated version ?\

iigrs said:
Is there a way to provide us some help regarding the problem we face with the Pro donated version ?\
Click to expand...
Click to collapse
+1

carrsteven said:
Where are you getting your twrp recoveries from?
Click to expand...
Click to collapse
http://galaxys6root.highonandroid.com/cwmtwrp-recovery/
Mark.

jarwintee said:
any plans for G925L support?
Click to expand...
Click to collapse
The lte recovery (downloaded when selecting any variant) should work fine with the LTE-A. Try it and see if it works, you can always flash the stock recovery back if it doesn't as images are avaialble to download on samsung-updates.com http://samsung-updates.com/device/?id=SM-g925l
If it works I can add support to the toolkit.
Mark.

iigrs said:
Downloaded the toolkit, donated, converted to Pro.
Anything I'm doing I got 2.8.6.0 was unexpected at this time.
Pls Help. What's wrong ?
Click to expand...
Click to collapse
Im now getting my son to sleep I will look at this as soon as I get back to my pc (less than an hour) and update the module files with the fix.
Mark.

Thanks!
Verstuurd vanaf mijn SM-G925F met Tapatalk

Related

[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GEAR V1.0.0 - Drivers, Root, Recovery + MORE

[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY GEAR - Drivers, Root, Recovery + MORE
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports a multitude of 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
* 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 modules]
* Various Root options using insecure boot image or custom recovery
* 1-Click For All to Unlock, Root, Rename the Restore Files and install busybox [Nexus modules]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung modules]
* Fix “Superuser/SuperSU has stopped” message after rooting [Samsung modules]
* 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]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Phone Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Install BusyBox on your device
* Install Samsung Knox notification disabler on your device [Samsung modules]
* Install Root checker on your device [to be added to the Nexus modules]
* Extras, Tips and Tricks section with downloadable device user guide
* Auto Update ToolKit to latest available version at startup [PRO ONLY FEATURE]
* Check for latest versions of Superuser [root] and custom Recovery images [PRO ONLY FEATURE]
* Program up to 10 Quickpick slots and run them very quickly [PRO ONLY FEATURE]
* Mods section to automatically perform certain tasks on your phone
* Download Stock Firmware Image for extracting and flashing
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus modules]
* Flash Custom Recovery or Stock Firmware Image to device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP or Stock Recovery without Flashing it [Nexus modules]
* Boot or Flash .img Files directly from your PC [Nexus modules]
* 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
* 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 various Modes automatically
* Display Important Information about your device
* Display various Help and Information screens and save a screenshot to your pc/send to default printer
* Many many more features
————————————————————–
Supported devices and latest supported builds *HERE*
————————————————————–
{
"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"
}
--------------------------------------------------------------
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE2: As the exe files are not Digitally Signed with a Microsoft Certificate they ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
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, 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 YOUR DEVICE. NO MAIN FUNCTIONS ARE RESTRICTED.
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.
IF YOU FIND THIS PROGRAM USEFUL PLEASE CONSIDER DONATING TO YOUR CHOSEN DEVICE TO GET AN ACTIVATION CODE FOR THE PRO VERSION. YOU WILL FIND THE PRO FEATURES VERY USEFUL, GET UPDATES DIRECTLY FROM THE PROGRAM AND SUPPORT FUTURE DEVELOPMENT. WITHOUT DONATIONS DEVELOPMENT WILL NOT BE ABLE TO CONTINUE.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
2. USING THE UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. The basic Toolkit files are included in the full install package but if you select a device then the working folders will be created and the device files downloaded. Once the files have been extracted the Toolkit will ask if you want to check if an Update is available (for pro users to download/install). If you type ‘no’ then you will be taken to the Model/Build selection screen where you can do a number of things:
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, ’99' will take you to the Basic Toolkit for quick use or if you do not have a supported device and want to perform general android tasks.
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 custom recovery and superuser files available (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.
The Information section which you can get to from the Model Selection screen or from the Main Menu has a wealth of help and frequently asked questions. If you need help then please look there first before asking questions in the thread.
--------------------------------------------------------------
USEFUL INFORMATION
Enable Developer options for usb debugging
Go to Settings, Gear Info, About Gear and tap on Software version 7 times until it says you are now a developer. You can now go to Settings, Gear Info and enable USB debug.
How to get into Recovery Mode
1. Open the charging case (if the device is in it) and hold the power button [on the side] in for about 10 seconds until you see a “Rebooting…” message on the screen.
2. Release the power button then press it 3 times quite fast. Wait a second then press it 3 times again and a screen should appear with 3 reboot options [continue, download and recovery].
3. Tap the power button to scroll down to recovery then hold the power button in for 5 seconds and release.
You should now boot to recovery.
How to get into Download Mode (For Odin)
1. Open the charging case (if the device is in it) and hold the power button [on the side] in for about 10 seconds until you see a “Rebooting…” message on the screen.
2. Release the power button then press it 3 times quite fast. Wait a second then press it 3 times again and a screen should appear with 3 reboot options [continue, download and recovery].
3. Tap the power button to scroll down to download then hold the power button in for 5 seconds and release.
You should now boot to download mode.
--------------------------------------------------------------
ChangeLog
Unified Android ToolKit v1.2.6 [Galaxy Gear V1.0.0] 31st March 2014
+First version of Samsung Galaxy Gear ToolKit Module released
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**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.
There is more Information/Help at http://www.skipsoft.net/?page_id=1269
**VIDEOS**
**UPDATES**
Well, there's a name I'm happy to see in Gear dev! Thanks mskip!
Thank you for the application.
Chosed option 5. Allinone. Now in Odin and starting the flashing process. How long is the process supposed to take. Or am I not just patient enough lol?
Sent from my SAMSUNG-SM-N900A using Tapatalk
darkchyldx101 said:
Chosed option 5. Allinone. Now in Odin and starting the flashing process. How long is the process supposed to take. Or am I not just patient enough lol?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Flashing twrp only takes a few seconds. What exactly have you doneand what is happening on the pc and watch? I will start making some youtube vids soon to help users.
Mark.
Installed drivers. Started toolkit. Choose my Gear section. Choosed option 5 for Allinone root, recovery, busybox, backups. Then Watch went into download mode. USB debug enabled. Odin opened. I put tar file in pda slot toolkit provided. Hit start. Then it hangs for awhile.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Hey Mskip, I have used a few of your toolkits in the past and have found all of them very useful. I have donated to upgrade to the pro version of all of them. I was just curious if you were planning on doing anything for the Samsung Galaxy Note Pro 12.2 tablet. I know there is the CF-Auto tool but I need something to root the Verizon version which is the SM-905V. Thank you in advance and keep up the excellent work!
Question
First thank you for your hard work in coming up with this process!!
Do we know if this will work with the newest galaxy gears? (gear 2, gear 2 neo and gear fit) My understanding is these devices aren't running android at all but an OS called Tizen. I know very little of this OS but I can say that the UI of my neo is nearly identical to my OG gear which makes me wonder if this method will work.
kingnarkissos said:
First thank you for your hard work in coming up with this process!!
Do we know if this will work with the newest galaxy gears? (gear 2, gear 2 neo and gear fit) My understanding is these devices aren't running android at all but an OS called Tizen. I know very little of this OS but I can say that the UI of my neo is nearly identical to my OG gear which makes me wonder if this method will work.
Click to expand...
Click to collapse
The new Gear smartphones work on Tizen as you said and the Galaxy Gear module will not work with them. I don't have a Gear 2 yet and don't know if its even rootable but if anything can be done with it in the future I will definitely look at adding it.
Mark.
Hi Op, I have used your toolkit on my nexus 5 and other samsung phones..so first thanks a lot man. Now I just bought a new gear. Whenever I select option 5 allinone and try to go to the folder in my C drive I dont see any tar file. I selected version 4.2.2 in the start. It says no extra files will be downloaded. I really want to root and install TWRP.
pro version not seeing tar.files in galaxy gear !!!!
Hi, just to say ive donated tonite to buy the pro version and when i go to root my galaxy gear , it gives me the option to enter number 3/root/unroot options/ then go to the root galaxy gear folders and select the root file for odin, but there are no files there !! can you help as i have donated but unable to root my galaxy gear. I can supply you with the pro code when i donated to prove i did buy.
---------- Post added at 09:20 PM ---------- Previous post was at 09:18 PM ----------
viny2cool said:
Hi Op, I have used your toolkit on my nexus 5 and other samsung phones..so first thanks a lot man. Now I just bought a new gear. Whenever I select option 5 allinone and try to go to the folder in my C drive I dont see any tar file. I selected version 4.2.2 in the start. It says no extra files will be downloaded. I really want to root and install TWRP.
Click to expand...
Click to collapse
Yeah im getting the same problem !!
any support please
Hi, are we getting any support please ?
has this thread been closed !!
read007 said:
Hi, are we getting any support please ?
Click to expand...
Click to collapse
Hi all, i posted last on the 27th may and have had no replys to my post, any help please
read007 said:
Hi all, i posted last on the 27th may and have had no replys to my post, any help please
Click to expand...
Click to collapse
read007 said:
Hi, just to say ive donated tonite to buy the pro version and when i go to root my galaxy gear , it gives me the option to enter number 3/root/unroot options/ then go to the root galaxy gear folders and select the root file for odin, but there are no files there !! can you help as i have donated but unable to root my galaxy gear. I can supply you with the pro code when i donated to prove i did buy.
---------- Post added at 09:20 PM ---------- Previous post was at 09:18 PM ----------
Yeah im getting the same problem !!
Click to expand...
Click to collapse
viny2cool said:
Hi Op, I have used your toolkit on my nexus 5 and other samsung phones..so first thanks a lot man. Now I just bought a new gear. Whenever I select option 5 allinone and try to go to the folder in my C drive I dont see any tar file. I selected version 4.2.2 in the start. It says no extra files will be downloaded. I really want to root and install TWRP.
Click to expand...
Click to collapse
Hi I just got a gear and am about to root... And wanted to make sure this toolkit was fully functional?
I see the most recent post were having trouble.. Was it fixed?
Sent from my Nexus 5 using Tapatalk
Its not donation, its purchasing and no i dont want to buy your product, you could have warned me before i did all of this. good day
Hey MSkip, I guess the latest updates put the Gear 1 on Tizen also. Your program ask to make the tar file and upload. I was wondering if you already have this update and are working on adding that to your program. Thanks. I also donated for the gear but have not done anything to it yet. I may root / install TWRP according to the forum threads in the mean time. Here is a link to the latest rom unrooted http://samsung-updates.com/details/30439/Galaxy_Gear/SM-V700/BTU/V700XXUCNF1.html it's the Great Britain file, but from what I understand it's the same for the US. Take it easy.
Chris
UPDATE: Tizen became really boring...so I'm back to Null rom. What was I thinking, it's nice and slick and good on battery. But even with root and setting up SDB (Sammy's ADB) and trying to customize a clock it was no longer exciting. So I came back to what I know and can use the MSkip's tool again.
Chris
Great work! Thanks!

[TOOLKIT] UNIFIED ANDROID TOOLKIT - GALAXY TAB S - Drivers, Root, Recovery + MORE

[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY TAB S - Drivers, Root, Recovery + MORE
SUPPORTED MODELS/VARIANTS
GALAXY TAB S 8.4 [KLIMT]
WIFI ONLY MODEL [SM-T700]
LTE/WIFI MODEL [SM-T705]
LTE/WIFI CANADA MODEL [SM-T705W]
LTE/WIFI S AMERICA MODEL [SM-T705M]
GALAXY TAB S 10.5 [CHAGALL]
WIFI ONLY MODEL [SM-P800]
LTE/WIFI MODEL [SM-T805]
LTE/WIFI CANADA MODEL [SM-T805W]
LTE/WIFI S AMERICA MODEL [SM-T805M]
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.
Cool thing remember you from the Hd2 Era
Thanks for porting your tookit over to support our devices. Will be very useful for many
Cheers,
UITA
JUNEBUG-1 said:
Cool thing remember you from the Hd2 Era
Click to expand...
Click to collapse
yes I recall too..great work mskip!
---------- Post added at 08:36 PM ---------- Previous post was at 08:33 PM ----------
mskip..you may want to add that the NA models of the 705 and maybe 805 too cannot make cellular calls even though have LTE data...there have been several threads on this..most recent one in the original development section posed as a question..
this was discussed here already clarified by oldblue (am sure elsewhere too)
http://forum.xda-developers.com/galaxy-tab-s/general/pre-galaxy-tab-s-att-t2881310
http://forum.xda-developers.com/showpost.php?p=56084215&postcount=44
Thanks for your work!
Thanks for the Kit,
I'm looking for a perfectly stable ROM for Tab S 8.4 SM700. The only ROM I saw that seems stable is Iron-man. Are there any other ROM stable for SM 700?
Amazing job!
Thank you very much.
Thanks for this toolkit and for replying to my email, all working ok now.:good:
Does this tool support the SM-T800NTSSXAR ? ( 16GB Wifi US Model - also know as just the SM-T800 )?
ClockerXP said:
Does this tool support the SM-T800NTSSXAR ? ( 16GB Wifi US Model - also know as just the SM-T800 )?
Click to expand...
Click to collapse
Yes. I think there is a typo in the toolkit. It should say SMT800 instead of SMP800
Donated & THANK YOU!
Hi. Thanks for the tool, I'm looking for the root access and I'm wondering if your tool can support the newer version of Tab S 10.5 based on 5433 SoC (i.e., SM-T805K)
http://pdadb.net/index.php?m=specs&...b_s_10.5-inch_broadband_lte-a_samsung_chagall
I have this 5433 model from Korea, which the shell cmd tells me this: chagall. I could not find any root tools for this.
many thanks
Howdy-
I donated so that I could use this toolkit with my Tab S. Works great.
I also made another donation so I could use the Pro version with my Galaxy S4. Unfortunately, when the Pro version loaded up I saw it doesn't support the SCHi545 Verizon version of the phone. I immediately emailed the tool author to see if he would send back my extra donation since I could not actually use the tool for the S4 and because I had already donated for the Tab S. Been over a day and no response. I got the activation code within minutes but no reply the other way around.
I have a question, this root changes Knox to "1"???
Hi guys,
what's the meaning of [KLIMT] in "GALAXY TAB S 8.4 [KLIMT]" pl?
I hate to root my GALAXY TAB S 8.4 WIFI,16G0, is it ok with your tools?
Ths for you answer, good job!
B
Bishopandme said:
Hi guys,
what's the meaning of [KLIMT] in "GALAXY TAB S 8.4 [KLIMT]" pl?
I hate to root my GALAXY TAB S 8.4 WIFI,16G0, is it ok with your tools?
Ths for you answer, good job!
B
Click to expand...
Click to collapse
klimt is the models of the tab s 8.4. Your exact model is SMT700 so Im pretty sure it should work. Hope this helps!
Just got done trying to root and install twrp recovery on the tab s 10.5 wifi and I can get into recovery that worked bu the device is not rooted. twrp installed supersu and then I started it and it preceded to to an update. So I go to start supersu and it give me this message
There is no SU binary installed and supersu cannot install it
Any ideas. I have rooted lots of devices and have never seen this.
Thanks.
kendive said:
Just got done trying to root and install twrp recovery on the tab s 10.5 wifi and I can get into recovery that worked bu the device is not rooted. twrp installed supersu and then I started it and it preceded to to an update. So I go to start supersu and it give me this message
There is no SU binary installed and supersu cannot install it
Any ideas. I have rooted lots of devices and have never seen this.
Thanks.
Click to expand...
Click to collapse
Download a zip(google it) called supersu.zip then flash it with twrp and you will have root.

[TOOL] SKIPSOFT ANDROID TOOLKIT - GOOGLE PIXEL C - Drivers,Unlock,Flash Stock,Backup

GOOGLE PIXEL C - 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 newer device you will also need to make sure "enable/allow OEM unlock" is ticked in developer options.
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 Bootloader Mode
1. Turn your device 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 Bootloader Mode
How to get into your Fastboot Mode
1. First boot into Bootloader Mode as described above
2. Select 'Switch to fastboot mode' using the volume button and press the power button. The device will say 'Waiting for fastboot command...'
How to get into Recovery
1. First boot into Bootloader 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.
** ChangeLog **
** FAQ **
Hi,
Does everything works?
We can unlock and root with that tool ?
Envoyé de mon LG-H815 en utilisant Tapatalk
misteurz said:
Hi,
Does everything works?
We can unlock and root with that tool ?
Envoyé de mon LG-H815 en utilisant Tapatalk
Click to expand...
Click to collapse
I don't want to sound like a douche, but its in the third line of the post that there's currently no root available.
tldr: no
Oh sorry, I have a piece of meat in the eyes
Envoyé de mon LG-H815 en utilisant Tapatalk
Awesome! Welcome mskip!
misteurz said:
Hi,
Does everything works?
We can unlock and root with that tool ?
Envoyé de mon LG-H815 en utilisant Tapatalk
Click to expand...
Click to collapse
Bootloader unlock should work fine (if someone can confirm this for me please).
As stated as soon as a custom recovery becomes available then I can easily enable root functions in the Toolkit.
Mark.
Can anyone who has selected this module fro mthe Toolkit please confirm that it passes the config section and proceeds to the Main Menu (where you can unlock, flash stock, etc).
I have a user who is getting an error at "Checking files are all present" stage and I cannot recreate this problem. Also I cannot see any problems in the code that would cause this error to occur.
Thanks (and Merry christmas for people who missed my messages online), MArk.
DEVICE MODULE V1.0.1 UPDATE AVAILABLE FOR ALL USERS (PRO AND PUBLIC)
Changelog:
+Fixed error at files check stage on some systems
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 the device (GooglePixelC) 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 want to donate to the Google Pixel C project please do it through the Toolkit (after selecting the device at startup) so you get the right code fast.
Enjoy, Mark.
But I can root on Google Pixel C with 6.0.1 (MXKB48J)?? ASAP
Scarfacez2007 said:
But I can root on Google Pixel C with 6.0.1 (MXKB48J)?? ASAP
Click to expand...
Click to collapse
Yes you can! ASAP
Really? Don't you mind can give me the link ?
Scarfacez2007 said:
Really? Don't you mind can give me the link ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3289357
Now I wondering if I get update Pixel C 6.0.1 (MXB48T) still on root?
Scarfacez2007 said:
Now I wondering if I get update Pixel C 6.0.1 (MXB48T) still on root?
Click to expand...
Click to collapse
No, just flash system and vendor.
Or I can downgrade?
Scarfacez2007 said:
Or I can downgrade?
Click to expand...
Click to collapse
You can flash the whole system image but can't guarantee root will work on it.
Device Module Auto Updates Available
This has been a special round of updates for the latest google monthly updates and does not affect my commitment to updating the Samsung modules with the latest builds and procedures.
Google Pixel C update [V1.0.2] 02ND FEB 2016
+Added Support for Android 6.0.1 MXB48T
+Added Android 6.0.1 MXB48T stock image to download/flash directly from Toolkit
+Updated checksum file for verifying stock image download
+Minor updates and bug fixes
If you want to donate to a device project to receive the pro updates please do it through the Toolkit (after selecting the device at startup) so you get the right code fast. Alternatively you can go to http://www.skipsoft.net/?page_id=703 and select the device you wish to activate.
On a side note I have not enabled root functions yet as it seems hit and miss and errors can lead to devices being bricked. Also im not sure about the current state of custom recovery and whether it is stable yet. If anyone can give more information about recovery/root on the Pixel C I may enable root functions and could possibly adapt the current procedure with any extra steps needed.
Enjoy, Mark.
I did buy Pro for Google Pixel C but I got unlocked and I still cant get root because of "disable" something I miss it?

[TOOL] SKIPSOFT ANDROID TOOLKIT - ONEPLUS X - Drivers, Unlock, Flash Stock, Root

ONEPLUS X - SUPPORTS ALL VERSIONS UP TO THE LATEST OXYGEN OS BUILDS.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Google, Nexus, OnePlus and Samsung Toolkits and supports many 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
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
* Root any public build automatically
* SkipRoot boot image to AutoRoot (selected builds)
* Sideload root/unroot files via Custom Recovery
* ALLINONE to Unlock, Flash Recovery, Root, Rename the restore file + install Busybox (G,N,O)
* ALLINONE to Flash Recovery, Root, Rename the recovery restore files + install Busybox (Samsung)
* Unlock/Re-Lock your Bootloader (G,N,O)
* Download Google Stock Image files directly to the ToolKit (G,N,O)
* Check md5 of google stock image before flashing
* Flash Google Stock Image (G,N,O)
* Flash any part of a stock firmware image to device [boot, system, recovery, etc.] (G,N,O)
* Download/sideload stock OTA image (G,N,O)
* Install BusyBox binarys on device
* Rename the Recovery Restore File present on Stock Roms (if stock recovery is being restored after flashing custom recovery image)
* Flash Stock Recovery, CWM touch, Philz_touch or TWRP Touch Recovery
* Pull /data and /system folders, compress to a .tar file and save to your PC
* Auto Update Toolkit at startup (PRO ONLY)
* Auto Update superuser file and custom recovery images to latest versions (PRO ONLY)
* Disable forced encryption on Nexus5X,6,6P and 9
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps
* Install EFS/Partition Backup/Restore app by Wanam
* Create tar with 1-Click for flashing via Odin
* Fix extSdCard write permissions in Android 4.4+
* Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC (selected builds)
* Useful Mods, Fixes and Tools Section
* Extras, Tips and Tricks section (includes guides)
* Backup/Restore your /efs partition (gsm only)
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC ( on builds with insecure image available)
* Mods section to automatically perform certain tasks on your device
* Boot to any recovery without Flashing it (G,N,O)
* Boot or Flash .img Files directly from your PC
* Quick Picks Professional Feature (10 slots)
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your phone
* Pull Files from your phone to your PC
* Set Files Permissions on your device
* Pull and Trim your Radio Image (gsm models only) to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Rip cache.img to zip file in CWM format
* Reboot device to Fastboot Mode or Android in fastboot mode (G,N,O)
* Reboot device to Fastboot Mode, Recovery, Android or Download Mode in adb mode
* Turn Initial Start Screen On/Off for next use
* Sideload any zip file via Custom Recovery
* Basic Toolkit for use with ANY Android device
Key: G-Google N-Nexus O-OnePlus S-Samsung
--------------------------------------------------------------
{
"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: Grarak or TWRP custom recovery on OnePlus 3, 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 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
--------------------------------------------------------------
*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**
I have finished all the work on the OnePlus modules for the 1, 2, 3 and X devices and it is ready for testing.
You can download and test the Toolkit from the link in post#1. Please remember that this IS a test version at the moment as I do not own any OnePlus devices but I have checked all the code thoroughly and don't see any problems. I am especially pleased with the unlock/lock routines and will probably implement the code for the Nexus modules if it works well.
Everything can be checked (and please do) except downloading a stock build directly from the Toolkit as I am waiting to hear back from AndroidFileHost to see if I can get direct links to use in the Toolkit. The fastboot flash routines are working though and the Toolkit will detect the storage of the device (16GB or 64GB) and flash the relevant userdata image so you do not have to do that manually anymore.
I have used the Universal USB driver pack from CWM so if anyone has not installed OnePlus drivers yet PLEASE test if this works. I did originally include the official drivers from OnePlus but they close the Toolkit when the drivers installation starts and thats not great.
The ALLINONE routine should work fine and I have sent out some pro codes to testers to check it all works.
All builds are covered and the correct version of TWRP will be downloaded depending on the build selected. Please check everything and let me know of any bugs or textual errors (as I used a lot of the Nexus code) so I can release it publicly as soon as possible.
Thanks, Mark.
hi
i have already rooted and flashed twrp on my OPX can ur tool get Me back to stock recovery and locked my boot loader
ie can i do this
1. flash back full stock rom via twrp - i have already done this so now im on stock firmware
2. use ur tool to relock my boot and get back stock recovery and im good to go
thanks in advance
haree said:
hi
i have already rooted and flashed twrp on my OPX can ur tool get Me back to stock recovery and locked my boot loader
ie can i do this
1. flash back full stock rom via twrp - i have already done this so now im on stock firmware
2. use ur tool to relock my boot and get back stock recovery and im good to go
thanks in advance
Click to expand...
Click to collapse
1. I know you said you have already done this but yes you can download a full ota image from http://downloads.oneplus.net/devices/oneplus-x/ and use option 10 to sideload it to your device. I don't kmow if there are any fastboot stock images available for the OnePlus X but if there is you can flash that using option 9.
2. The Toolkit has full automated support to unlock and relock the bootloader. Just connect, make sure usb debugging is enabled and start the process.
Mark.
Updated OnePlus X Device Module for Public (free) and Pro Users
Changelog:
+Added flash custom recovery before booting to it as per rooting guides
+Changed a lot of text to make it more relevant to the OnePlus devices
+Added text about disabling CM recovery protection in developer options to stop CM builds restoring the stock recovery
+added a bit more error control
+Fixed Toolkit going back to device selection when going to driver help screen
I’m still not sure if the Universal USB driver pack from CWM installs the recovery adb drivers. A couple of users have said when booting to recovery the device isnt being detected by the Toolkit. If someone has knowledge of adb drivers and knows their way around the device manager please look at the different modes and check drivers are installed.
Pro users can get the latest version by just selecting their device at startup and accepting the update.
Non Pro users have a few more steps.
1. Exit the Toolkit if it is open.
2. Run ToolkitClean.exe from the installation folder (or the Start Menu)
3. Select your device (OnePlus 1, 2, 3 or X) 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 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.
Updated OnePlus X Device Module for Public (free) and Pro Users to v1.0.3
Changelog:
+Added option to reboot to custom recovery after it has been flashed
+Disabled openrecovery options in custom recovery until driver issue is fixed
+Made some changes to text in Toolkit to make some things easier to understand
+OnePlus device modules are now stable
Pro users can get the latest version by just selecting their device at startup and accepting the update.
Non Pro users have a few more steps.
1. Exit the Toolkit if it is open.
2. Run ToolkitClean.exe from the installation folder (or the Start Menu)
3. Select your device (OnePlus 1, 2, 3 or X) from the list
4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
5. If you have not updated to v1.5.0 you must ALSO select option 62 to update the Toolkit.exe file
6. Restart the Toolkit, select the device and new module files will be downloaded/installed
If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast.
Enjoy, Mark.
It's not letting me download via Paypal via pro, says I need to add funds to my account. My account is verified and I have used it as a "pass through" for payments and transfers before, why would this be?
---------- Post added at 02:48 AM ---------- Previous post was at 02:27 AM ----------
Also, I'm backing up and the backup screen went away on my phone, app is still saying to unlock and confirm...nothing to confirm, is there something I need to do?
chrishickman said:
It's not letting me download via Paypal via pro, says I need to add funds to my account. My account is verified and I have used it as a "pass through" for payments and transfers before, why would this be?
---------- Post added at 02:48 AM ---------- Previous post was at 02:27 AM ----------
Also, I'm backing up and the backup screen went away on my phone, app is still saying to unlock and confirm...nothing to confirm, is there something I need to do?
Click to expand...
Click to collapse
Sorry I don't know what your problem with paypal might be. If you send paypal a message or call them they are usually very fast at responding. If it turns out to be a problem with the Toolkit in some way please let me know.
Reboot the phone to recovery (if you flashed it) and try the backup again.
Mark.
AutoUpdate Available for OnePlusX device modules [Pro Users]
Changelog:
+Test fix for booting to recovery after flashing recovery image
+Few bug fixes
+Waiting for TWRP recovery driver fix to enable ALLINONE/OPENRECOVERY scripts
Once I get the twrp drivers working properly with the Toolkit I will update the modules and upload new device modules for everyone to use.
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. Also follow me on twitter at https://twitter.com/mskipxda for posts/updates.
Enjoy, Mark
AutoUpdate Available for OnePlus X device module 1.0.7 [Pro Users]
Changelog:
+Added full support for OxygenOS 2.2.2, 2.2.3, 3.1.0 and 3.1.1 builds
+Updated stock fastboot image flash routine to better support flashing from bootloader mode
+Improvements to root method updating
+Updated drivers section to give a lot more help and more options
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.
AutoUpdates Available for OnePlus X device module 1.2.1 [Pro Users]
Changelog:
v1.2.1 – 17th May 2017
+Added instructions in OTA section [10] how to update device via OTA sideload
+Added option in OTA section to go to OnePlus download page to download ota image
+Few minor fixes to OnePlus main code
v1.2.0 – 15th May 2017
+Added full support for OxygenOS 3.1.3 and 3.1.4 builds
+Updated Toolkit base to 1.6.1. Updated app versions and improved functions
New base version adds support for OnePlus 3T device
+Toolkit will disable all server pings if they cause any trouble with downloads
+Added direct link to OnePlus download site in factory image/ota downloads section
+Improved some Main Menu functions
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.
AutoUpdate Available for OnePlus One device module [Ultimate/PRO Users Only]
Changelog:
+Updated Toolkit base to 1.6.2 for NEW Ultimate feature. After device selection the Toolkit will update the devices main module to the latest version even if an AutoUpdate is not ready yet. This is extremely useful if an AutoUpdate hasn’t been released in a while or if an AutoUpdate isn’t needed but the main module needs updating for up to minute bug fixes/new features. Minimum base version 1.6.2 needed for this to work
+Updated TWRP custom recovery to latest official version 3.1.1.1 for use with later builds
+Added VerifiedBootSigner flash to Twrp Recovery install procedure
+Updated VerifiedBootSigner zip file from Chainfire to latest V7.0
+Integrated flashing verifiedbootsigner in to root procedures if needed
+Updated some root functions and removed SuperUser by CWM from root relection
+Updated app/file versions to latest
+Fixed some bugs in the main code
If you find any of this useful PLEASE donate to a device project. You can do it through the Toolkit (after selecting the device at startup) or from the link *HERE* 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.

[TOOL] SKIPSOFT ANDROID TOOLKIT -Google Pixel- Drivers, Unlock, Firmware, Root

GOOGLE PIXEL - SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID BUILDS.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
NOTE: Verizon and ee uk models have locked the bootloaders. In this case you will not be enable the oem unlock setting to unlock the bootloader via the developer screen. You can force unlock the bootloader using dePixel8 in the Bootloader unlock section if your build is 7.1.0 NDE63X or lower. This method was patched in 7.1.1 and does no longer work. If you have a Verizon/ee uk model on 7.1.0 you MUST force unlock the bootloader before accepting the OTA update or your bootloader will be unlockable.
The Unified Android Toolkit brings together Nexus, Google, Samsung and OnePlus Toolkits and supports many 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 [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 Nexus5X, 6, 6P, 9, Google Pixel C, Google Pixel, Google Pixel XL
* 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.
YOU CAN ALSO NOW UPGRADE TO THE ULTIMATE MODE. ONCE THIS MODE HAS BEEN ACTIVATED YOU WILL BE ABLE TO UNLOCK ALL DEVICE MODULES (PRESENT AND FUTURE) AND WILL NEVER HAVE TO BUY ANOTHER PRO CODE AGAIN.
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 if you have one, 'dr' will allow you to install drivers, '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 using the Unified Android Toolkit. No warranties of any kind are given.
**FAQ**
Q: How do I enable Developer options?
– Go to Settings from the apps drawer
– Scroll Down and Tap on About Phone or About Device
– Go down to the Build number section
– Tap on the Build number option 7 times
– Go back to the Settings screen
– Scroll Down and Tap on Developer options (just above the About option)
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, on certain devices you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
– Enable Developer options (go to Settings, About and tap on Build number 7 times)
– Enable USB Debugging (Settings, Developer options)
– Look for the ‘Allow OEM Unlock’ or ‘OEM Unlock’ Option and tick it
Q: When I boot in to TWRP it asks me for a password
Android 5.0 Lollipop brings new security features like encrypted data. TWRP for Nexus 5X, 6, 6X and 9 is able to decrypt all the data using “default_password “. This allows TWRP to decrypt the information without any problems.
**Updates and Videos**
thank you so much for this!
installed adb drivers, and unlocked my pixel XL in no time!
cant wait for twrp/SuperSU for it...
Perhaps I'm missing something, but I get a "This app can't run on your PC" message. Windows 10 64bit. The Unified Drivers app works fine.
Hi there, my Pixel 5 has Android 7.1, but the tool seems to think only 7.0.1 is 'stock'. Do we need to wait for an update?
the tool works fine
works fine on win7 64bit
thank you!
Update Available for Google Pixel device module [ALL USERS]
Changelog:
+Added information in the bootloader unlock section about locked verizon devices
+Added options in build selection menu for current builds [NDE63H,NDE63L,NDE63L]
+Added above STOCK firmware AND OTA images to download/flash directly from Toolkit using option 9,1 [firmware download/flash] or 10,1 [ota download/sideload]
+Added Google Kedacom Windows 10 drivers to toolkit for better adb support
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
4. Select the device (google pixel) 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
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.
The Sunshine group have released a bootloader unlocker for Verizon/EE carrier devices that ship with a locked bootloader. This makes it possible to unlock the device and use it how you want to. I will add an automatic process in the Toolkit later to run the bootloader unlocker but I won't add the app itself to the Toolkit as they asked for it not to be redistributed.
Keep tuned.
Mark.
Im in the process of writing an automation routine to use the toolkit to unlock the verizon/ee locked bootloaders. If anyone has a locked bootloader and wants to test it please let me know in here and I will send the file to test it. Also if anyone HAS used depixel8 can you tell me how long it took from running the file to it rebooting to the bootloader. Just trying to set an approximate time for the Toolkit to wait until giving an error message to start again.
Thanks, Mark.
Update Available for Google Pixel device module 1.0.3 [ALL USERS]
I have been asked to not include any automation for dePixel8 in the Toolkit so have instead provided a link to the page so users can download the latest file and follow the instructions to force enable locked bootloaders from verizon and ee.
Changelog:
+Added link in Unlock Section to dePixel8 page to unlock carrier locked bootloader [verizon/ee]
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
4. Select the device (google pixel or google pixel xl) 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
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.
Update Available for Google Pixel device module 1.0.4 [ALL USERS]
Changelog:
+Fixed stock firmware flash routine not flashing the image.zip [flash path was not set correctly]
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
4. Select the device (google pixel or google pixel xl) 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
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.
Update Available for Google Pixel device module 1.0.5 [ALL USERS]
Changelog:
+Updated bootloader unlock procedure
+Enabled CF-Auto-Root options 1 [root] and 2 [root,busybox] in root section. To abide by CF-Auto-Root redistrubution rules the Toolkit will direct you to download file manually, then take over everything else
+Changed device name in device list to Google Pixel to avoid user confusion
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
4. Select the device (google pixel) 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
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.
thanks mark!
still gonna wait for the TWRP guys before I root this beast, but glad to see you added it!:good::good:
Update Available for Google Pixel device module v1.0.6 [ALL USERS]
Changelog:
+Added Support [including root] for November Updates, Android 7.1.0 Europe NDE63U, NDE63V and Verizon NDE63X builds
+Added above STOCK firmware AND OTA images to download/flash directly from Toolkit using option 9,1 [firmware download/flash] or 10,1 [ota download/sideload]
+Added alternative fastboot version which will download and try if there are errors flashing stock images
+Fixed Stock zip image file not showing in list if flashing using options 9,2
+Added warning against relocking bootloader in Bootloader Unlock/Re-Lock section
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
4. Select the device (google pixel) 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
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.
Before I use this and wipe my phone, will flashing stock everything decrypt my phone?
spunks3 said:
Before I use this and wipe my phone, will flashing stock everything decrypt my phone?
Click to expand...
Click to collapse
Decryption isn't available on the Pixel devices yet.
Mark.
I keep getting
load_file: could not allocate 1832020148 bytes
error: failed to load 'put_google_factory_image_here\GooglePixel\image-sailfish-nde63u.zip': Not enough space
Click to expand...
Click to collapse
when trying to flash the stock EU firmware on the Google Pixel.
Hi Mark,
keep getting error when trying to download Pixel OTA, "Stock image is not available, this option has been disabled..."
Any ideas?

Categories

Resources