Root for S7580 Galaxy Trend Plus - Upgrading, Modifying and Unlocking

Root for S7580 Galaxy Trend Plus - Upgrading, Modifying and Unlocking

Regarding the root procedure for the S7580 found in
http://forum.xda-developers.com/showthread.php?t=2621087
where I'm not allowed to write, i would like to add an important but not mentioned note: USB debug MUST be enabled.
I strictly followed the procedure, ending just with the stock recovery, and using Root Browser to rename install-recover.sh won't help because the device it's not rooted yet and write option will fail.
After having enabled the USB Debug, the procedure worked and at last CWM appeared, allowing SuperSU to install.
To enable USB Debug on 4.2.2:

Related

[TOOLKIT] SKIPSOFT ANDROID TOOLKIT -GNEX SPR- Drivers, Root, Recovery + MORE

GALAXY NEXUS - SUPPORTS ALL AVAILABLE VERSIONS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.4.1 [05th Oct 2015]
* 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]
* 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
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
ChangeLog:
ToolKit v1.4.1 (05th Oct 2015)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

Manual Rooting Instructions for Galaxy Nexus
UPDATES:

VIDEOS:

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

thnx man!
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Much recomended for all users. Easy and all the options and extras you'll need. Then just flash away..............

dangambino said:
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Click to expand...
Click to collapse
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.

mskip said:
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
Click to expand...
Click to collapse
Works for me. Flashed it perm and the first thing i did was do a backup. No issues thus far. About to flash Team Win's to see what its all about. But yeah, its working.

whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.

Anon9mouz said:
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
Click to expand...
Click to collapse
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
adb-toolkit shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh-old
Click to expand...
Click to collapse
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.

Skip I just sent you a message regarding the radio pull CMD

mskip said:
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.
Click to expand...
Click to collapse
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2

Anon9mouz said:
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Click to expand...
Click to collapse
I think people just prefer using fastboot I know I certainly do.
Mark.

Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.

LAYGO said:
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
Click to expand...
Click to collapse
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.

mskip said:
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
Click to expand...
Click to collapse
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!

LAYGO said:
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
Click to expand...
Click to collapse
Plus one on no sd
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2

Will be doing this when I get home from work! I was glad I picked my GNex up yesterday...it was the only one my store received! So I was quite happy...can't wait for more support on the sprint side.

I couldn't wait, I rooted after lunch. Getting Swype installed, first thing, EVERY time. I needs my Swype!
Then to get some apps on there. Connection sucks at work though.

Can someone please pull the radio for the sprint galaxy nexus
I did a n00b mistake and restored a google factory image for VZW on my Sprint Galaxy Nexus...
Any help would be greatly appreciated!!!

I may have spoke so soon. I'm getting error 7 assert fail when flashing a twrp recovery zip. Is that an issue with the recovery on the toolkit or the zip. I flashed a teerom and kernel with no issues though.....

[SAMSUNG GALAXY S3 UNIFIED TOOLKIT V9] Drivers, Backup, Root, Recovery + MORE [ATT]

INTRODUCING THE SAMSUNG GALAXY S3 UNIFIED TOOLKIT
SUPPORTED MODELS
INTERNATIONAL [GT-I9300] SUPPORT THREAD HERE
AUSTRALIAN MODEL GSM [GT-I9300T]
INTERNATIONAL [GT-I9305/GT-I9305N] SUPPORT THREAD HERE
AUSTRALIAN MODEL LTE [GT-I9305T]
C SPIRE MODEL LTE [SCH-L710]
AT&T US [SGH-I747] SUPPORT THREAD HERE
BELL, ROGERS, SASKTEL, TELUS [SGH-I747M] [SGH-I747M] USE AT&T SUPPORT THREAD
US CELLULAR MODEL LTE [SCH-R530] USE AT&T SUPPORT THREAD
METRO PCS MODEL LTE [SCH-R530M] USE AT&T SUPPORT THREAD
SPRINT US [SPH-L710] SUPPORT THREAD HERE
TMOBILE US [SGH-T999] SUPPORT THREAD HERE
MOBILICITY, VIDEOTRON, WIND [SGH-T999V] USE TMOBILE SUPPORT THREAD
VERIZON US [SCH-I535] SUPPORT THREAD HERE
CHINA ANYCALL CDMA MODEL [SCH-I939] USE GT-I9300 SUPPORT THREAD
Click to expand...
Click to collapse
The Unified Android Toolkit supports a multitude of Nexus and Samsung devices with more devices being added all the time. 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 V1.3.4 [9TH JAN 2015]
* 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]
* 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]
* 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
* 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
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: 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: 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.
--------------------------------------------------------------
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. NOTHING IS 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.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
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 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.

**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). If you have a GT-I9300 GSM Model then you can do this from the Toolkit but if you have an LTE device then it isn't soo easy to do. If you have an LTE device you should go to *THIS* thread by lyriquidperfection and follow the information to save your IMEI/NV Data so that you are covered if anything should happen.
----------------------------------------------------------------------------
Q. Is there currently no way to root the Samsung Galaxy S3 without voiding the warranty?
All methods of rooting will void your warranty in some way as you will have superuser files on your phone that arent supposed to be there. There is a method of rooting your phone without increasing the flash counter which involves flashing a complete rom with root files already added but if anything happens and you need to send it back under warranty you will need to flash a 'proper' Stock Rom back before returning it or your warranty will be void. Flashing a custom kernel or recovery to root will increase the flash counter and also void any warranty. There is currently no method of resetting the flash counter on Snapdragon models but im pretty sure there will be some support for it soon. If you dont want to risk it or you aren't sure then you shouldnt really be flashing your phone and should just leave it alone. Its your choice .
----------------------------------------------------------------------------
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.

*reserved if needed*

Wow! Even the tech challenged girlfriend should be able to use this. No time to test but will be back.

Faaaaantastic! I'll be getting my phone this afternoon so should be able to report back tonight.

Worked Great on My Rogers Samsung Galaxy S3 , thank you so much

Worked great on my Rogers. Finally decided to root

trublu said:
Wow! Even the tech challenged girlfriend should be able to use this. No time to test but will be back.
Click to expand...
Click to collapse
Jirv311 said:
Faaaaantastic! I'll be getting my phone this afternoon so should be able to report back tonight.
Click to expand...
Click to collapse
Please do report back as I want to know if anything doesnt work as expected.
Mark.

I selected all in one for Rogers but it looks like it never installed CWM app touch.

Awesome, I'll be trying this out when I get home from work tonight!

Wow nice job!! gonna check this out after work!!

Nice, but didn't work on my AT&T. Odin got to RESET and rebooted phone, but did not get to PASS. Closing Odin by X, returned to toolkit, but could not get ACK, install su or set root.

Dx9 said:
I selected all in one for Rogers but it looks like it never installed CWM app touch.
Click to expand...
Click to collapse
Yeah that happened with me too, stock CWM is fine for me ahha
---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------
alkiter said:
Nice, but didn't work on my AT&T. Odin got to RESET and rebooted phone, but did not get to PASS. Closing Odin by X, returned to toolkit, but could not get ACK, install su or set root.
Click to expand...
Click to collapse
Mine took about 3-5 minutes for it to stay PASS and rebooted before pass.

I ran the #3 root option and everything worked fine. i have att version. I'm making a nandroid right now not issues.

When Im tried this method:
http://forum.xda-developers.com/showthread.php?t=1725395
from noobnl, I had force close everywhere. I unrooted it with the steps provided in the same thread and reseted my phone. When it rebooted, screen rotation was the oposite of normal, the screen was always upside down. I could change it from Rogers, Do you think this method would do the same?
Thanks

xhead said:
Yeah that happened with me too, stock CWM is fine for me ahha
---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------
Mine took about 3-5 minutes for it to stay PASS and rebooted before pass.
Click to expand...
Click to collapse
So how do I get the actual app? Should I redo it again and select a different option or is there a way to actually install from CWM? Thanks

Looks amazing!
Quick question does the root function trigger the modify counter?
Sent from my SAMSUNG-SGH-I747 using xda premium

skalatsky said:
Looks amazing!
Quick question does the root function trigger the modify counter?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Yes

What root option do I have to go for? (in the root folder) I am with Rogers, i747m -

Does this trigger flash counter?

[SAMSUNG GALAXY S3 UNIFIED TOOLKIT V9] Drivers, Backup, Root, Recovery + MORE [TMO]

*reserved if needed*

thanx op for all your work and helping us tmo peeps.
EDIt: works as advertised, no issues.

Hey, congrats on finding everything you were looking for and getting the Toolkit up and running for the US variants!
Thanks for the great tool.

Thanks!
Awesome and thanks! I used the GNEX Toolkit you put together and I assume this is very much like that one - I do apprecaite the effort and time you put into this - thanks a lot!

well done mate! everything seems to work perfectly. thanks Mark

Donation sent.
Thanks, Mark! :good:

overground said:
Donation sent.
Thanks, Mark! :good:
Click to expand...
Click to collapse
Thanks mate hope everything works as it should. If you spot anything that needs fixing please let me know. The Snapdragon Edition benefited from a few script upgades over the International version
Mark.

mskip said:
Thanks mate hope everything works as it should. If you spot anything that needs fixing please let me know. The Snapdragon Edition benefited from a few script upgades over the International version
Mark.
Click to expand...
Click to collapse
Well, there's a problem with build.prop push/pulls, at least on this ROM: http://forum.xda-developers.com/showthread.php?t=1728255
Any changes fail to boot...even after restoring backup in recovery.
Seems to be a permissions problem as indicated in this thread (towards the end): http://forum.xda-developers.com/showthread.php?t=1735128

overground said:
Well, there's a problem with build.prop push/pulls, at least on this ROM: http://forum.xda-developers.com/showthread.php?t=1728255
Any changes fail to boot...even after restoring backup in recovery.
Seems to be a permissions problem as indicated in this thread (towards the end): http://forum.xda-developers.com/showthread.php?t=1735128
Click to expand...
Click to collapse
Is that s problem with the ToolKit or with the build.prop changes from the thread you linked to. Its never a good idea to edit too much in the build.prop as it can soft brick your device.
Mark.

mskip said:
Is that s problem with the ToolKit or with the build.prop changes from the thread you linked to. Its never a good idea to edit too much in the build.prop as it can soft brick your device.
Mark.
Click to expand...
Click to collapse
I'm not sure at this point. All I did was use your tool to disable boot ani.
But it's not inherently the tool's fault because it happens if manually done also.

Use the toolkit to restore back to stock for some odd reason my Internet isn't working any ideas
Edit problem solved had to pull some and reboot thanks for this wonderful tool
Sent from my SGH-T999 using xda premium

Just upgraded to an SIII from a G2 and boy, when did rooting get so easy? Thank you for this fantastic tool; your work saves everyone a ton of headaches.

Recovery
Does this recovery support external sd card and if it does do the backup and restore work? I know there was one posted, but restores did not work. The recovery in the root tutorial woks with backup/restore but it's internal storage support only.

Just used This toolkit to root my device. Worked flawlessly. Thanks, bro!

anthonykash said:
Does this recovery support external sd card and if it does do the backup and restore work? I know there was one posted, but restores did not work. The recovery in the root tutorial woks with backup/restore but it's internal storage support only.
Click to expand...
Click to collapse
I would also like to verify this?

I got everything to work except installing superuser. I passed ODIN and then when I try to flash superuser, it flashes but when I restart my phone I don't have superuser.

kharnage said:
I got everything to work except installing superuser. I passed ODIN and then when I try to flash superuser, it flashes but when I restart my phone I don't have superuser.
Click to expand...
Click to collapse
go to the market and download superuser, and busybox.

anthonykash said:
Does this recovery support external sd card and if it does do the backup and restore work? I know there was one posted, but restores did not work. The recovery in the root tutorial woks with backup/restore but it's internal storage support only.
Click to expand...
Click to collapse
The ToolKit uses Team Epic's v4 cwm Recovery which from their changelog supports external sd cards and has no mention of restores not working so I would think its safe.
You can see Team Epic's Changelog *HERE*.
Mark.

[Q] Errors trying to root with the MSkip Toolkit

I tried posting to the relevant thread on xda but I don't have enough posts. Anyway, I uninstalled the default drivers and installed the drivers from the toolkit but Windows keeps trying to reinstall the default drivers. I end up with the phone showing up under "Portable Devices" as "SAMSUNG-SGH-I747" and under a new section "SAMSUNG Android Phone" as "SAMSUNG Android ADB Interface". Not sure if that's how it should be or not, but the toolkit does show a code and "device" at the top of the main menu...
The first time I ran the ALLINONE rooting option I got some errors during the verification steps related to "su" not being found (it went away before I could get a screenshot). I rebooted the pc and the phone and tried again and got a java IllegalStateException saying "Cannot broadcast before boot is completed"
I tried it a third time and got a couple errors saying that it failed to restore the recovery files ("No such file or directory"). The next step failed when trying to push Busybox to my phone ("error: device not found").
USB Debugging was enabled. Any idea what on Earth I'm doing wrong?!
Edit: It appears CWM was installed and I can get into it but there's no SuperUser app in my app drawer...

I guess my first question would be what version of the SG3 do you have, as the very first line of his post says "IMPORTANT: DO NOT USE THIS TOOLKIT TO ROOT OR FLASH CUSTOM RECOVERY ON A SNAPDRAGON MODEL SGS3 AS THE INCLUDED IMAGES WILL NOT WORK ON IT". If you go to you settings>about phone>hardware it will tell you if you have the qualcomm snapdragon CPU.

dntesinfrno said:
I guess my first question would be what version of the SG3 do you have, as the very first line of his post says "IMPORTANT: DO NOT USE THIS TOOLKIT TO ROOT OR FLASH CUSTOM RECOVERY ON A SNAPDRAGON MODEL SGS3 AS THE INCLUDED IMAGES WILL NOT WORK ON IT". If you go to you settings>about phone>hardware it will tell you if you have the qualcomm snapdragon CPU.
Click to expand...
Click to collapse
I have the Snapdragon version of the toolkit referenced here: http://forum.xda-developers.com/showthread.php?t=1746665

I see, i'm downloading the file's now to take a look but just reading the post i can tell you the recoveries in this package are outdated, not to say they wont work but there are significant changes between those and the current versions.
*Edit* - You said CWM did install but the SU app did not, do you by chance have root access as well? Just shooting in the dark here but if so you can simply download the SU app from the market and go about your merry way. If not I would suggest just using odin to flash the approtiate stock rooted rom from THIS THREAD which also includes the SU app (if i recall from when i last used it). After looking through the packaged files the toolkit includes odin which is used to flash a root inject stock rom based on your selection as to which device you select. Not knowing how this executable handles unexpected errors i would simply run odin manually from the toolkit folder and make sure it is recognizing your device properly using this guide which also includes a link to the samsung usb drivers. I don't know how these drivers in the toolkit compare to the linked drivers on the odin thread but would install those just to be sure its not a driver issue. Also another thing to check would be to make sure you are using the usb micro cable that came with your GS3 as many people have had flashing issues using other cables.

[TOOLKIT] GALAXY NOTE 10.1, Drivers, Backup, Root, Recovery, Flash + MORE

INTRODUCING THE SAMSUNG GALAXY NOTE 10.1 TOOLKIT
IMPORTANT: THIS TOOLKIT DEVICE MODULE SUPPORTS 5 DIFFERENT VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.
SUPPORTED MODELS
GT-N8000 3G/WIFI MODEL
GT-N8005 3G/WIFI MODEL
GT-N8010 WIFI ONLY MODEL
GT-N8013 WIFI ONLY MODEL
GT-N8020 LTE/WIFI MODEL
Click to expand...
Click to collapse
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 V1.3.3 [8TH DEC 2014]
* 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]
* 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]
* 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
* 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
--------------------------------------------------------------
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: 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.
--------------------------------------------------------------
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. NOTHING IS 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.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
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 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 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.
Note: If you cannot get into Recovery by using the buttons then you can reboot to it from the Toolkit 'reboot device' section.
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.

**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.2).
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).
This feature will be added to the Toolkit after testing has been completed.
----------------------------------------------------------------------------
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.

**Reserved if needed**

Loved your work for nexus 7 . Great to see you here.
Thanks

thanks so much
what a great tool. Thanks so much for creating it. I will download and explore

aalupatti said:
Loved your work for nexus 7 . Great to see you here.
Thanks
Click to expand...
Click to collapse
justauser said:
what a great tool. Thanks so much for creating it. I will download and explore
Click to expand...
Click to collapse
I need it tested before I can release it. If either of you or anyone else can test, busybox and make a nand backup then I can release it publicly.
Mark.

mskip said:
I need it tested before I can release it. If either of you or anyone else can test, busybox and make a nand backup then I can release it publicly.
Mark.
Click to expand...
Click to collapse
I will let you know this weekend. I am currently on ASOP based rom and will need sometime before I can go back to stock.

On ARHD8.0!
Hmmm...I'm on ARHD8.0 + with KALAGAS Theme.
I'm ready to Test.
Is it OK??
Edit : Back to ARHD 8.0 + STOCK Theme.

just received my N8010 yesterday and was looking for a toolbox, like í did with my N7.
it's completely Stock (see attached screenshot)
I'm willing to test.
Sent from my GT-N8010 using xda app-developers app

Hi,
I Have samsung galaxy note 10.1 GT-N8000. OFFICIAL ROM , ROOT ACCESS , STOCK RECOVERY. BINARY COUNTER ZERO
I AM READY TO TEST
PM me

william84 said:
just received my N8010 yesterday and was looking for a toolbox, like í did with my N7.
it's completely Stock (see attached screenshot)
I'm willing to test.
Sent from my GT-N8010 using xda app-developers app
Click to expand...
Click to collapse
Jaspreet.master7 said:
Hi,
I Have samsung galaxy note 10.1 GT-N8000. OFFICIAL ROM , ROOT ACCESS , STOCK RECOVERY. BINARY COUNTER ZERO
I AM READY TO TEST
PM me
Click to expand...
Click to collapse
Great thanks I will finish building the installation file now and send you both pm's with the link to test ASAP
EDIT: DOWNLOAD LINKS AND INSTRUCTIONS SENT TO YOUR INBOX. PLEASE TEST AS SOON AS POSSIBLE.
Mark.

Excellent! Im very happy to see Mscip working on a tool for galaxy note 10.1 like the for Gnex. I hope we get a release soon.....much much thanks
Sent from my GT-N8000 using xda app-developers app

Hi Mark,
I used your toolbox for the Galaxy Note 2.
My Galaxy Note 10.1 is arriving this evening and I'm willing to test your toolbox!

@mskip: i'm using your Toolkit on my Galaxy Nexus, Galaxy S3 and Galaxy Note 2.
Would be happy to use and test it also on my Galaxy Note 10.1 (N8000)
Greetings
king.larry
Sent from my GT-N8000 using xda premium

king.larry said:
@mskip: i'm using your Toolkit on my Galaxy Nexus, Galaxy S3 and Galaxy Note 2.
Would be happy to use and test it also on my Galaxy Note 10.1 (N8000)
Greetings
king.larry
Sent from my GT-N8000 using xda premium
Click to expand...
Click to collapse
You have too many devices lol. If you (or the above user) can test and give me feedback tonight then please let me know as soon as possible so I can release the Toolkit soon.
Also can someone with a GT-N8010 or N8013 device please install voodoo report (free from google play store) and email the results to [email protected] so I can make sure the partition points are set right. I have the points for the N8000 so do not need it for that.
Mark.

mskip said:
You have too many devices lol. If you (or the above user) can test and give me feedback tonight then please let me know as soon as possible so I can release the Toolkit soon.
Also can someone with a GT-N8010 or N8013 device please install voodoo report (free from google play store) and email the results to [email protected] so I can make sure the partition points are set right. I have the points for the N8000 so do not need it for that.
Mark.
Click to expand...
Click to collapse
Sent u the report from N8013 running Revolt rom - Asop based.

I sent a voodoo report running stock JZO54K.N8013UEUCMB3.
I can test the toolkit on my device if needed.
Sent from my GT-N8013 using XDA Premium HD app

djmasoda said:
I sent a voodoo report running stock JZO54K.N8013UEUCMB3.
I can test the toolkit on my device if needed.
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
When is the soonest you can test? I was expecting feedback from testers by now but nothing so I may just have to take it out of beta testing, post the installer and wait for public feedback.
Mark.

TOOLKIT ANNOUNCEMENT!!
TOOLKIT OPENED FOR PUBLIC RELEASE. PLEASE REMEMBER THIS IS THE INITIAL VERSION SO PLEASE GIVE FEEDBACK IF ANYTHING IS TEXTUALLY INCORRECT OR NEEDS FIXING.
DOWNLOAD LINKS AND INFO IN POST#1
MARK.

Can anyone who has used the Toolkit give some feedback pleased. Just if its working as it should or if anything needs fixing.
Mark.

Develop Bugs

welcome