[17.12.2011][CF-Root v5.1] ICL53F - su+bb

[17.12.2011][CF-Root v5.1] ICL53F - su+bb - Samsung Galaxy Nexus

This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original firmware, and just adds root and busybox.
THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THE ENTIRE FIRST FEW POSTS!
Donate
There have now been nearly 1.000.000 downloads of CF-Root for various devices (see for example Galaxy S1, Galaxy Tab 7", and Galaxy S2), and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user had donated me $1...
Main features
- The kernel is fully stock and taken from the original firmware, with just the following added:
- Superuser v3
- Busybox v1.19
- Custom boot / init scripts
- Insecure
Installation instructions
Please see the next post !
Recovery
Unlike CF-Root for various other devices, CF-Root for the Galaxy Nexus does not include any recovery, due to kernel and recovery being separate partitions on the device. This means you don't need to flash a recovery with your kernel.
Custom boot / init scripts
CF-Root will execute the following scripts if present, in the order listed:
- /system/etc/init.d/* (there can be many files here, no extensions! use "#!/system/bin/sh")
- /system/bin/customboot.sh
- /system/xbin/customboot.sh
- /data/local/customboot.sh
Please make sure you chown / chmod the scripts correctly so they can be executed. Pretty much root:root / 755.
Busybox
Busybox by default creates symlinks in /sbin. You can turn this off by executing the following:
adb shell setprop persist.busybox.nosymlink 1
And reboot your device.
Installing busybox over the included version
It is possible to install a custom busybox over CF-Root. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. It is now used to make CF-Root for many devices!
Help! Which file do I use ?
Check Settings -> About phone -> Build number and find the matching download. YAKJU downloads are for GSM, MYSID downloads are for LTE.
Download
These are general-purpose downloads. See the posts following this one for the kernels.

Instructions
IMPORTANT: If your device is not yet OEM unlocked, both methods WILL WIPE your data ! If you are already OEM unlocked, this does not happen.
Flashing with ODIN
ODIN: Short
- Flash CF-Root-xxx-vX.X.tar (from the attached zip) as PDA in ODIN, without repartition. Done.
ODIN: Long
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-xxx-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-xxx-vX.X.tar
- Put your phone in download mode (turn off phone, then hold volume-down + power to boot)
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Flashing with FASTBOOT
Fastboot: Short
- Flash boot.img (inside the tar inside the attached zip) as boot. Done.
Fastboot: Long
- Unzip the attached CF-Root-xxx-vX.X.zip
- Untar the CF-Root-xxx-vX.X.tar (found inside the zip)
- Find the boot.img file that you extracted
- (USB) Disconnect your phone from your computer
- Put your phone in fastboot mode (turn off phone, then hold volume-up + volume-down + power to boot)
- (USB) Connect the phone to your computer
- If your device is not yet OEM unlocked - NOTE: This wipes your data!
fastboot oem unlock
- (1) Flash the kernel (permanent):
fastboot flash boot boot.img
- Press the power button to boot
- or (2) Flash the kernel (temporary, applies root only):
fastboot boot boot.img

Downloads
Remember: I only have the GSM version, so the LTE versions are not tested by me !
CF-Root-GGN_YAKJU_ICL53F-v5.1.zip
CF-Root-GGN_MYSID_ICL53F-v5.1.zip

-- reserving yet another post --

I have the LTE SGN and my build number is ICL53F, not MYSID

theboo7 said:
I have the LTE SGN and my build number is ICL53F, not MYSID
Click to expand...
Click to collapse
And thus you should use:
CF-Root-GGN_MYSID_ICL53F-v5.1
and specifically not:
CF-Root-GGN_YAKJU_ICL53F-v5.1

omanomanom, tastes like bacon.
*installs*

finally the greatness has arrived on the galaxy nexus

So this changes/modifies the kernal to add root? What about OTA updates?
Sent from my Galaxy Nexus using XDA App

@chainfire
if my device is ITL41F and what can i do?
can i flash your other thread ICL53F rom via odin
and then flash cf-root kernel via odin again?

kangxi said:
So this changes/modifies the kernal to add root? What about OTA updates?
Click to expand...
Click to collapse
It should not interfere with OTA updates ...
leamoor said:
@chainfire
if my device is ITL41F and what can i do?
Click to expand...
Click to collapse
There's no ITL41F version yet, not sure if I'm making one. 53F is out already ...

Chainfire said:
It should not interfere with OTA updates ...
There's no ITL41F version yet, not sure if I'm making one. 53F is out already ...
Click to expand...
Click to collapse
Thanks for the quick response. Gonna try it when I get home.
Sent from my Galaxy Nexus using XDA App

Thanks for the quick response，but i'm not get the ITL53F yet
if my version is ICL53F,how can i made oem unlock？

leamoor said:
Thanks for the quick response，but i'm not get the ITL53F yet
if my version is ICL53F,how can i made oem unlock？
Click to expand...
Click to collapse
Use this command :
fastboot oem unlock
Also, @Chainfire, you should add a warning stating that "fastboot oem unlock" wipes data

Chainfire i knew you would come with a cr-root kernel...thanks!!!
Sent from my Galaxy Nexus using xda premium

Okay i did this, but my phone is now stuck on the Google Screen with a lock on the bottom that is unlocked.
When i go back to the bootloader and select Recovery Mode.
I get an Android with a "!"
Reboots back to the Google and nothing happens =(
The only way to start my Device is in CMD and using Superboot =S
Help!

Glad to see Odin works. I like having that safety net for when ROMs attack.

chainfire, je bent een baas! grtz uit haarlem.
pitje

cdesai said:
Use this command :
fastboot oem unlock
Also, @Chainfire, you should add a warning stating that "fastboot oem unlock" wipes data
Click to expand...
Click to collapse
get out noob this thread is sacred

Will this work with buildnumber ITL41F?
If not what should I do to make use of this kernel?
Many THanks in advance

Related

[KERNEL] 24 Nov r2: MoDaCo Custom Kernel (+CIFS +USB drives / keyboard / mouse)

This is now included in my MoDaCo Custom ROM for the Galaxy Nexus - details.
I have created a custom kernel for those that would like CIFS support or USB drive / keyboard / mouse support. This is a temporary download until such time as MCR is released. This is based on the stock kernel source with purely config tweaks at this time.
This should be flashed via ClockworkMod Recovery.
This is designed for devices running the I9250XXKK1 / ITL41D ROM.
DOWNLOAD - MD5: 4eb172c3222126ceb3eed340f51c7b28
P
Note: Source is now available in my bitbucket repository.

Thanks Paul.
Just two things:
1. You say try using 'fastboot boot' rather than 'fastboot boot' in your post. Just a heads up so you can fix that.
2. So the Galaxy Nexus does not support USB storage out of the box? It needs kernel modifications to make it work?
Thanks for all your hard work.

Stigy said:
Thanks Paul.
Just two things:
1. You say try using 'fastboot boot' rather than 'fastboot boot' in your post. Just a heads up so you can fix that.
2. So the Galaxy Nexus does not support USB storage out of the box? It needs kernel modifications to make it work?
Thanks for all your hard work.
Click to expand...
Click to collapse
1. I think he wanted to say [use 'fastboot boot' rather than 'fastboot flash' to try before flashing].
2. I think he added HID support to the kernel.

Guys any tut on how to flash those md5 files of paul?

DJTaurus said:
Guys any tut on how to flash those md5 files of paul?
Click to expand...
Click to collapse
md5 is not a file, it's a checksum. You flash modified boot.img with custom kernel using fastboot flash boot boot.mck.img (as mentioned in the first post). You need to boot your device in fastboot mode on device with unlocked bootloader. Or maybe I didn't understand the question?

mike1986. said:
md5 is not a file, it's a checksum. You flash modified boot.img with custom kernel using fastboot flash boot boot.mck.img (as mentioned in the first post). You need to boot your device in fastboot mode on device with unlocked bootloader. Or maybe I didn't understand the question?
Click to expand...
Click to collapse
Ok so how do we flash those img's?
1.Boot into fastboot
2.Then connect GN with PC
3..?

DJTaurus said:
Ok so how do we flash those img's?
1.Boot into fastboot
2.Then connect GN with PC
3..?
Click to expand...
Click to collapse
then open terminal and type the command

mike1986. said:
then open terminal and type the command
Click to expand...
Click to collapse
I ll have to wait for the online kitchen then.
I never got the android sdk properly installed on the pc

questions
Sorry, REALLY a newbie here
1. What is CISF and MCR?
2. So, the GN doesn't have HID support at first? I thought that's one of their features
3. Can u make a more detailed tutorial? It's really my first time using boot/flash or whatever it is

xinn3r said:
Sorry, REALLY a newbie here
1. What is CISF and MCR?
2. So, the GN doesn't have HID support at first? I thought that's one of their features
3. Can u make a more detailed tutorial? It's really my first time using boot/flash or whatever it is
Click to expand...
Click to collapse
1. CIFS - http://searchcio-midmarket.techtarget.com/definition/Common-Internet-File-System
MCR - Modaco Custom ROM
2. Not sure about that.
3. If you don't know what CIFS is then why you want to flash this? I mean no disrespect to anyone but if you don't know what something is and you don't know how to flash it then don't flash it. Better wait for ready ROMs (mine is ready but still waiting for working recovery) with custom kernels. Shouldn't take long

mike1986. said:
1. CIFS - http://searchcio-midmarket.techtarget.com/definition/Common-Internet-File-System
MCR - Modaco Custom ROM
2. Not sure about that.
3. If you don't know what CIFS is then why you want to flash this? I mean no disrespect to anyone but if you don't know what something is and you don't know how to flash it then don't flash it. Better wait for ready ROMs (mine is ready but still waiting for working recovery) with custom kernels. Shouldn't take long
Click to expand...
Click to collapse
OK, let me start from the beginning
I was really interested with the Galaxy Nexus
Then when I found out that it didn't have SD card slot, I was really bummed
I was planning on using the GN for watching alot of movies, but without a external storage, it's hard to store alot of files at once (particularly HD videos)
Then I learned that GN was able to use USB OTG
So, I thought of using a flash drive to store my movies, then just plug it into the GN if I wanted to watch something
That's why I was really interested in this costum kernel
I wanted to use the Vanilla Android, if I use modded ROMs, will the themes change?

Having trouble using CifsManager, phone crashes and reboots when I attempt to mount.

xinn3r said:
OK, let me start from the beginning
I was really interested with the Galaxy Nexus
Then when I found out that it didn't have SD card slot, I was really bummed
I was planning on using the GN for watching alot of movies, but without a external storage, it's hard to store alot of files at once (particularly HD videos)
Then I learned that GN was able to use USB OTG
So, I thought of using a flash drive to store my movies, then just plug it into the GN if I wanted to watch something
That's why I was really interested in this costum kernel
I wanted to use the Vanilla Android, if I use modded ROMs, will the themes change?
Click to expand...
Click to collapse
A "custom" kernel is not the same as a ROM, this "custom" kernel will only change the kernel and nothing else.
I put quotes around "custom" as this is just the same kernel but with a few flags enabled.
Also for whatever it's worth, USB-OTG is supposed to be supported by the GN, so it may just be an oversight that they didn't enable module support for it already, so it may come in a future update.

FISKER_Q said:
A "custom" kernel is not the same as a ROM, this "custom" kernel will only change the kernel and nothing else.
I put quotes around "custom" as this is just the same kernel but with a few flags enabled.
Also for whatever it's worth, USB-OTG is supposed to be supported by the GN, so it may just be an oversight that they didn't enable module support for it already, so it may come in a future update.
Click to expand...
Click to collapse
Yes, that's my point, I just want the kernel to be modified, I don't want a costum ROM, that's why I was asking for a tutorial how to do this

suppose that I want to use this kernel,
what will happen when an ota update will be released?
should I reflash this kernel to have the usb host feature?
---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------
If you want the usb host enabled via official firmware/kernel please write here and ask it to google.
http://code.google.com/p/android/issues/detail?id=22038&thanks=22038&ts=1321813429#makechanges

xinn3r said:
Yes, that's my point, I just want the kernel to be modified, I don't want a costum ROM, that's why I was asking for a tutorial how to do this
Click to expand...
Click to collapse
Obtain Fastboot, if you don't know where to get it, just download this package from Modaco: http://android.modaco.com/topic/348161-18-nov-r2-superboot-rooting-the-galaxy-nexus/
You'll only need "Fastboot-windows.exe" provided you use windows.
Extract it to say c:\android\
Rename it to fastboot.exe (it's not nessecary, but since most guides assume you have "fastboot.exe" it would eliminate some confusion)
Download the kernel from the post
Copy that to c:\android\
Open a command prompt (cmd)
Navigate to c:\android\
Enter Fastboot mode (Shutdown the phone, and then hold down both volume buttons while powering up) you can confirm it's presence by entering "fastboot devices"
If your device is not already unlocked (There's an opened lock icon when you boot up) you will have to execute the following command: (This will void your warranty)
fastboot oem unlock
After that you simply do this to install the new kernel:
fastboot flash boot boot.mck.img

FISKER_Q said:
Obtain Fastboot, if you don't know where to get it, just download this package from Modaco: http://android.modaco.com/topic/348161-18-nov-r2-superboot-rooting-the-galaxy-nexus/
You'll only need "Fastboot-windows.exe" provided you use windows.
Extract it to say c:\android\
Rename it to fastboot.exe (it's not nessecary, but since most guides assume you have "fastboot.exe" it would eliminate some confusion)
Download the kernel from the post
Copy that to c:\android\
Open a command prompt (cmd)
Navigate to c:\android\
Enter Fastboot mode (Shutdown the phone, and then hold down both volume buttons while powering up) you can confirm it's presence by entering "fastboot devices"
If your device is not already unlocked (There's an opened lock icon when you boot up) you will have to execute the following command: (This will void your warranty)
fastboot oem unlock
After that you simply do this to install the new kernel:
fastboot flash boot boot.mck.img
Click to expand...
Click to collapse
Thx alot for the tutorial!

mike1986. said:
1. CIFS - http://searchcio-midmarket.techtarget.com/definition/Common-Internet-File-System
MCR - Modaco Custom ROM
2. Not sure about that.
3. If you don't know what CIFS is then why you want to flash this? I mean no disrespect to anyone but if you don't know what something is and you don't know how to flash it then don't flash it. Better wait for ready ROMs (mine is ready but still waiting for working recovery) with custom kernels. Shouldn't take long
Click to expand...
Click to collapse
How do you use cifs? I'm not quite understanding if it enables the use of server/client type apps such as printershare, idisplay, and splashtop, or if its simply a seperate client. If so, where do you download its companion program in windows? Or is it some kind of cmd prompt only deal?

Since this just resets several flags in the stock ROM will this kernel work with the VZW LTE version of GN when we finally get it, or will a different kernel be needed, or don't know yet?

Wow, do you mean we're getting Revolution for GN?
Since Clockwordmod has been updated, everything is ready.
My GN is on the plane, can't wait!!
Sent from my Nexus S using xda premium

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

[Galaxy Note2 TOOLKIT V4.1.0 TMOBILE] Drivers, Backup, Root, Recovery, Flash Stock

INTRODUCING THE SAMSUNG GALAXY NOTE2 TOOLKIT
GSM (GT-N7100) and LTE (GT-N7105) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1923956
AUSTRALIAN GSM (GT-N7100T) and LTE (GT-N7105T) SUPPORTED. USE GSM THREAD
SPRINT (SPH-L900) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957155
TMOBILE (SGH-T889) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957720
MOBILICITY, VIDEOTRON, WIND [SGH-T889V] SUPPORTED. NO THREAD YET. USE TMOBILE THREAD
AT&T (SGH-L317) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052779
BELL, ROGERS, SASKTEL, TELUS [SGH-I317M] SUPPORTED. NO THREAD YET. USE AT&T THREAD
VERIZON ([SCH-I605]) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052788
US CELLULAR (SCH-R950) SUPPORTED. NO THREAD YET. USE ANY
KOREAN SK TELECOM [SHV-E250S] SUPPORTED. NO THREAD YET. USE ANY
NOTE: If you want a new build added to the Toolkit then download and install, Type 'A' in the Model Selection screen and follow the instructions.
HOW TO VIDEOS ARE ON POST#4 (THANKS TO WWJOSHDEW) MAKE SURE YOU HAVE A LOOK AT THEM AS A VIDEO IS WORTH A THOUSAND WORDS
FUNCTIONS OF SAMSUNG GALAXY NOTE2 TOOLKIT V4.1.0 [9TH APRIL 2013]
Install 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 (different options)
Root with Superuser (ChainsDD) or SuperSU (Chainfire) via CWM (works on ANY build)
[*]Root+busybox+rename recovery restore files via Custom Recovery
[*]Unroot (delete root files and busybox)
[*]Many root/unroot options including adb, recovery and sideload via custom recovery
[*]Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC
[*]Pull /data and /system folders, compress to a .tar file and save to your PC
[*]Auto Update ToolKit to latest push version on startup (donator feature)
[*]Dump selected Phone Partitions, compress to a .zip file with md5 and save to your PC
[*]Install BusyBox binary on phone
[*]Flash Stock Recovery
[*]Flash CWM Recovery (thanks to Clockworkmod Team) or TWRP Recovery (thanks to Team Win)
[*]Rename Recovery Restore files if present
[*]Flash Insecure Boot Image for adb mode
[*]Flash Stock Boot Image back to your phone
[*]Create tar file to flash via Odin (from upto 10 image files) with 1-click process
[*]Download, Extract and Flash Stock Rom (full DETAILED steps) ESSENTIAL FOR WARRANTY RETURNS
[*]Rip cache.img to zip file in CWM format for editing and flashing (thanks to Adam Lange)
[*]Install a single apk or multiple apk's to your phone (being worked on)
[*]Push Files from your PC to your phone
[*]Pull Files from your phone to your PC
[*]Set Files Permissions on your phone
[*]Dump selected LogCat buffers to your PC
[*]Dump BugReport to your PC (if installed)
[*]Help, Information Screen for various tasks
[*]Mods Section to Modify your phone (being worked on)
[*]Reboot Phone options in adb mode
[*]Change background, text colour in ToolKit
[*]Device Information screen which pulls info directly from device
[*]Activate Professional features from within the ToolKit
--------------------------------------------------------------
Mod edit: Download link removed
MD5 Sum for V4.1.0: 37360aabdf3869aad55d12dd2c2b0b07
NOTE: As the ToolKit.exe and ModsSection.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.
IMPORTANT: ONLY FLASH ROMS THAT ARE SPECIFICALLY MADE FOR YOUR PHONES MODEL NUMBER AS FLASHING AN INCORRECT ROM CAN SOFT BRICK YOUR DEVICE!
Credits: ChainsDD for Superuser, Chainfire for SuperSU, Chenglu for modded cwm.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN FREE (PUBLIC) AND DONATE (PROFESSIONAL) VERSIONS?
THE FREE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD POSSIBLY NEED TO MANIPULATE YOUR PHONE. NOTHING IS RESTRICTED. ACTIVATING THE DONATE VERSION WILL ADD THE ABILITY TO CHECK FOR UPDATES VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED TO MY SERVER WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. THIS ALSO MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE VARIANT OR CARRIER SO DONATOR VERSIONS WILL BE UPDATED SOONER. IF YOU ARE NOT ABLE TO, OR DO NOT WANT THE AUTO UPDATE FEATURE THEN ALL UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL DOWNLOAD VERSION AS SOON AS TIME ALLOWS AND THERE ARE ENOUGH UPDATES TO WARRANT IT. DONATORS WILL ALSO HAVE THE QUICK PICKS AND EXTRAS SECTIONS UNLOCKED AND THE 'NAG' SCREEN ON EXIT WILL BE DISABLED. NEW DONATOR FEATURES WILL ALSO BE ADDED TO THE TOOLKIT IN THE FUTURE.
AUTO REPLY LINKS FOR PAYPAL AND GOOGLE CHECKOUT TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
AUTO UPDATES ARE BY FAR THE EASIEST WAY TO KEEP THE TOOLKITS UP TO DATE AS I HAVE LOTS OF OTHER TOOLKITS TO LOOK AFTER. IF ANYONE HAS ANY VIEWS ON THIS PLEASE PM ME OR CONTACT ME AT [email protected]. PLEASE DO NOT POST YOUR VIEWS IN THIS THREAD AS I WANT TO KEEP IT CLEAN FOR USER SUPPORT.
{
"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"
}
(Changelog at the Bottom of Post#1)
--------------------------------------------------------------
PLEASE READ THE *FAQ* IN POST#2 BEFORE ASKING QUESTIONS
--------------------------------------------------------------
1. INSTALLING GALAXY NOTE2 DRIVERS
The first thing you need to do is to install the drivers. These are needed so that you can communicate with the phone via the PC and perform the tasks that the ToolKit offers.
NOTE: If you have Kies installed then it is advisable to uninstall it first to avoid conflicts.
a. Make sure your phone is booted into Android and the USB cable is unplugged.
b. Select Option 1 in the ToolKit to install the Samsung USB Driver pack. This should install all the neccessary drivers you need.
C. While the drivers are installing make sure that USB Debugging is enabled on your phone via the Settings, Developer options Screen.
d. After the drivers have been installed connect the USB cable and the PC should detect the phone and install the correct drivers. This will also happen when you enter Download Mode and Recovery Mode for the first time.
e. If you want to check the drivers then go to your Control Panel on your PC and open the Device Manager. With the USB cable connected you should see a device listed as 'Samsung Android Phone' or something similar and a driver attached to it.
NOTE: If you are having trouble with your device being detected or the drivers installing correctly then you could try rebooting your phone, using a different usb port and making sure no other drivers are installed on your pc.
--------------------------------------------------------------
2. USING MSKIPS' SAMSUNG GALAXY NOTE2 TOOLKIT
a. Download the Samsung Galaxy Note2 ToolKit package and run to install the ToolKit to your PC. The installation will also create a Shortcut on your desktop for easy access. You have the option to include or exclude the drivers files at installation so if you already have your drivers set up and are just updating the ToolKit then you can untick the drivers if you wish.
b. Once the ToolKit is installed make sure your phone is booted and plugged in via USB cable and double click on the shortcut on your desktop to run it.
c. You will be asked if you want to check for an Update. If you type 'yes' this will download and check the latest version numbers against the versions in the ToolKit. If there is an update available then you will have the option to download and install it (professional feature).
d. You will now be presented with a Model Selection Screen to choose the Model/Build that you are currently on. Type the number that corresponds to your desired selection. For example type '12' for INTERNATIONAL GSM MODEL [GT-N7100] 4.1.1 [Build ALJ1-ALJ3]. If you cannot find the build your device is using then type 'h' to select the HELP option to get more info.
NOTE: If you have a new build that isnt covered by the Toolkit you can also type 'a' in the Model Selection screen to see instructions on how to pull your stock image and send it to [email protected] so support can be added.
e. The Toolkit will now locate and download the boot image pack for your chosen Model. This is a new feature so the Toolkit is not limited to how many Models can be added and it cuts down ALOT on the download size. After the zip file has finished downloading it will be extracted to the correct folders and the files checked to make sure everything is ok.
f. When you enter the Main Menu you will see 'Adb Mode' at the top. If you have installed your drivers correctly then you will see your devices serial number under the text with 'device' next to it. If you see this then your device is connected and you can carry on.
NOTE: If you haven't installed the drivers and don't see a serial number at the top then this is the FIRST thing you want to do so the Toolkit can operate properly.
g. Each option in the ToolKit has full information on what it is and how to use it.
--------------------------------------------------------------
3. FLASHING A ROM, RADIO OR KERNEL VIA CWM RECOVERY
a. Download your chosen Rom, Radio or Kernel from the Development Forum, then make sure your phone is booted up as normal and connect your usb cable so it goes into MTP Mode. Copy the .zip file (DO NOT UNZIP IT FIRST) to the 'Internal Storage' part on your phone. Do not copy it to a Sub Directory as it will be harder to find when flashing it.
b. Enter CWM Recovery (shut down the phone then hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds).
c. Select 'Install zip from sdcard' and select 'choose zip from sdcard' if the file is on Internal Memory.
d. Scroll to your zip file and select. Then select 'Yes' in the list to start flashing.
e. When flashing is finished press the BACK Button to go back until you get to the Main Menu and then select 'reboot system now' to reboot your phone into Android.
--------------------------------------------------------------
4. FLASHING A ROM, RADIO OR KERNEL VIA DOWNLOAD MODE USING ODIN
Odin can be used to flash image files or parts of your phone. You can flash something as simple as a boot image or a complete system. Everything is packed in a tar or tar.md5 file on your PC and flashed via Odin which is a Windows OS program.
a. Make sure you have your tar file stored on your PC.
b. Reboot your phone to Download Mode [shut down your phone, then hold down the Home + Volume DOWN Buttons and press the Power Button for about 2 seconds until a Warning screen appears. Press Volume UP to continue to Download Mode.
c. Connect your phone via usb and the first box at the top under ID:COM should turn blue and have some text in it. If you are using Download Mode on your phone for the first time then you will notice drivers being installed to use it.
d. The site or page you downloaded the file from will usually give you instructions to set Odin but if not you want to load boot/recovery/system files to the PDA location and have 'Auto Reboot' and 'F.Reset Time' ticked and nothing else.
e. Click on 'Start' to start the flash. You can see what is happening in the text box in the lower left.
--------------------------------------------------------------
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.
--------------------------------------------------------------
ChangeLog
ToolKit v4.1.0 (9th April 2013)
+Updated complete Toolkit structure for easier support and faster updates
+Added GT-N7100T and GT-N7105T models to the support list
+Added 4.1.2 support for many models. See screenshot for full list
+Updated CWM and TWRP Recovery to the latest model specific version
+Added TWRP NAND backup/restore procedure to backups section
+Updated SuperSU Root procedure to V1.25
+Updated Samsung usb drivers to 1.5.18.0
+Added more error detection and updated many parts of the Toolkit procedures
+Added Activation option and support procedure for new builds to Model Screen
+Updated Stock firmware download section with new Samsung images
+Adb server is now shut down if you exit from Model Selection screen
+Added more error control Toolkit processes
+Updated mods section
ToolKit v3.0.0 (18th December 2012)
+Rewrote soo many parts its hard to list them all
+Changed the Model Selection screen
+Split up images for all supported models to make them easier to distinguish
+Added support for Verizon, GT-N7105 (lte), AT&T and Korean SK Telecom
+Added new options to Root/Unroot Screen
+Added root+busybox+rename recovery restore files via Custom Recovery
+Added Root/Unroot via Sideload feature in Recovery
+Updated CWM Recovery to 6.0.1.9
+Updated TWRP Recovery to 2.3.2.3 for all available Models
+Updated SuperSU to 0.99
+Added Device Information Screen
+Added instant reply donate link to Toolkit
+Soo many more behind the scene changes
ToolKit v2.0.0 (27th October 2012)
+Added FULL support for Sprint (SPH-L900)
+Added FULL support for TMobile (SGH-T889)
+Added FULL support for US Cellular (SCH-R950)
+Updated SuperSU Root zip file to V0.96
+Updated CWM Recovery to V6.0.1.5
+Added TWRP Recovery V2.3.1.1
+Added option on all Root procedures to root with Superuser (ChainsDD) or SuperSU (Chainfire)
+Added option in ALLINONE Root routine to flash cwm or twrp Recovery
+Improved Root procedure on all builds
+Made some edits for Toolkit stability
+More tweaks
ToolKit v1.0 (7th Oct 2012)
+First version of Samsung Galaxy Note2 ToolKit 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. 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. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android 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 the Market). Delete the file recovery-from-boot.p from /system. Now when you flash CWM Recovery it will NOT be overwritten after a reboot. You can also use the Toolkit to rename the files if you wish.
----------------------------------------------------------------------------
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 would i perform a nandroid vs a titanium backup?
You would perform a nandroid backup to back up your entire system including boot image and data and system partitions so you can restore your entire system back to that particular point in the future.
You would use Titanium Backup mainly to back up your installed apps and settings so they could be reinstalled easily and quickly on any future roms. You can also choose individual apps to backup or restore on Titanium Backup whereas if you restore your boot partition via CWM Recovery you are stuck with the whole lot.
----------------------------------------------------------------------------
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 and AVG Free) will pick it up as potentially harmful when it is not. They 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. 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 flashed the Stock Firmware Image. Odin flashes the file successfully and the phone reboots but it stays stuck on the samsung logo
If the firmware tar file does not include a userdata image (which most Samsung firmware do not) then your userdata partition will be left from your previous setup. If this is incompatible with the new firmware because of build or something else then your system will freeze on boot up.
This is easily fixable by holding the Volume UP, Home and Power buttons all at the same time for about 10 seconds until the device reboots to the Stock Recovery screen. Use the Volume Down button to scroll down to 'wipe data/factory reset' and press the Home button to select it. Go down to yes to confirm and your userdata partition will be wiped. Your device should now boot fine.

**RESERVED FOR MANUAL INSTRUCTIONS**

Reserved for how to videos on this incredible toolkit!
http://www.youtube.com/playlist?list=PLwCVKEYxr_z7FBQYT32dbYw_kdSJmSDH2
How To Root
http://www.youtube.com/watch?v=M9zF6x1MURM
How To Flash Stock Recovery
http://www.youtube.com/watch?v=9CL5x84Tu_U
How To Manually Boot to Custom (or Stock) Recovery
http://www.youtube.com/watch?v=9m6Uugh8ps8&hd=1
Sent from my SPH-L710 using Tapatalk 2

Can i unroot with toolkit?.Many thank for awesome work..:good:

thank you! worked like a charm!!!

simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
Yes you can.
Mark.

So does this add to the flash counter?

Tiffany84 said:
So does this add to the flash counter?
Click to expand...
Click to collapse
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Mark.

simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
mskip said:
Yes you can.
Mark.
Click to expand...
Click to collapse
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.

GREAT work and thank you for getting this into an easy toolkit form, as many people will be helped out by this!! I was already rooted, as some others were too, but you created a tool that needs a BIG :good:

teshxx said:
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.
Click to expand...
Click to collapse
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.

Is TWRP supported on the TMo Note II?

mskip said:
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Click to expand...
Click to collapse
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number

mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Oh ok. I would, but I haven't rooted mine yet. Still deciding if I want to keep my grey one or exchange it for the white lolol. Hopefully, someone who is already rooted will be kind enough to do it for you.
Thanks for your effort and time.

Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
PM sent w/ link for stock T889 kernel.img. build number is the file name. sorry i can't help with stock recovery.img since i already rooted and flashed CWM recovery.
---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
hey mark, if u wanna post or PM me instructions i'll get u the mount points.

Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
So nice to see you here. Thanks for all u do!!
Sent from my SGH-T889 using Tapatalk 2

I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?

LvDisturbed1 said:
I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?
Click to expand...
Click to collapse
I can use my extSD with CWM so it's something on your end. I used the toolkit for the N7100 but same stuff...

Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
I just sent you a pm with the stock recovery.img from my device(T-Mobile Galaxy Note 2). My build number is JRO03C.T889UVALJ1. Hopefully this gives you what you need. Thanks again.
---------- Post added at 03:53 AM ---------- Previous post was at 03:43 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Just sent you a pm with the mount points for the T-Mobile Galaxy Note 2. Thanks for this tool. It's incredible.

[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