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

[mskip]

SAMSUNG GALAXY NOTE 5 - SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*

SUPPORTED MODELS/VARIANTS
INTERNATIONAL MODEL [SM-N920C] [Supported up to 7.0]
LATAN, INDIA MODEL [SM-N920G] [Supported up to 7.0]
SINGAPORE, NEW ZEALAND, AUS MODEL [SM-N920I] [Supported up to 7.0]
US SPRINT MODEL [SM-N920P] [Supported up to 6.0.1]
US TMOBILE MODEL [SM-N920T] [Supported up to 7.0]
US CELLULAR MODEL [SM-N920R4] [Supported up to 6.0.1]
CANADA MODEL [SM-N920W8] [Supported up to 7.0]
KOREAN KT [SM-N920K] [Supported up to 7.0]
KOREAN LG U+ [SM-N920L] [Supported up to 7.0]
KOREAN SK TELECOM [SM-N920S] [Supported up to 7.0]

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

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

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

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

SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*

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

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

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

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

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

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

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

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

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

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

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

1. INSTALLING ADB/FASTBOOT DRIVERS

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

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

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

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

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

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

2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT

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

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

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

USEFUL INFORMATION
How to Hard Reboot the device
1. Unplug the USB cable.
2. Hold down the 'VOLUME DOWN' + 'POWER' buttons for about 5-15 seconds until the device reboots

How to get into Recovery Mode
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME UP' + 'POWER' buttons for about 5-15 seconds until you see the Samsung logo on the screen.
3. Release all buttons straight away to enter Recovery Mode.

How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME DOWN' + 'POWER' buttons for about 2-15 seconds until a WARNING! Screen appears.
3. Press the 'VOLUME UP' button to enter Download Mode.

--------------------------------------------------------------
*DISCLAIMER*

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

 

[mskip]

**UPDATES**

 

[mskip]

**VIDEOS**

 

[mskip]

**FAQ**

Q. Help me I can't find my build in the Model Selection Screen

The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).

The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.

If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.

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

Q. What is ADB Shell?

Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.

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

Q. Why do I need to back up my IMEI/EFS and how do I do it?

There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry).

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

Q. 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. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit

I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.

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

Q. "Superuser/SuperSU has stopped" message after rooting

After updating Samsung device to newer builds of Android [4.3 and later] which contains the new security from Samsung "Samaung KNOX", you might face a problem if you tried to root your device.

This might happen because of KNOX security, it blocks/disables the Superuser app and you will see this notification after the first boot:
"Unfortunately, SuperSU has stopped" or "Unfortunately, Superuser has stopped" depending on the root method you used.

The easiest way to fix this problem is by installing the superuser apk file. Select option 6 from the Rooting Section and the Toolkit will attempt to extract the superuser.apk file from the root zip file in the Root folder and if successful it will then be installed. You can then run the app [Superuser or SuperSU] from the apps list. A warning message will pop up saying Samsung KNOX has been detected and ask if you want to try and disable it. Click OK, KNOX should be disabled and your device should now be properly rooted.

 

[mash4077fan]

First off thank you for this toolkit. I was running a custom rom on my sprint note 5. The developer came out with an update and I tried to install and had all sorts of problems. I honestly believe it is not the rom as everyone seemed to take ok. Anyways I had to odin back to stock and I tried to install TWRP several different ways and kept getting an error message and the phone would not boot down and I had to odin back to stock. Well after going back to stock I was able to root with odin and I was able to flash stuff with FlashFire. So I was fine but now out of the blue I got this error about super su binary not updated and my root was gone. Now all the changes I made before I got this message still work and the phone seems fine but a few apps I use require root permission but since I lost root I cant use them.

Well anyways I saw this site and I am hoping it will work for me. I am stock MM and I have super su installed but dont have root. My question is do I put my phone in dl mode before I start toolkit or do I made all my selections and then at the end I plug it in.

 

[mskip]

First off thank you for this toolkit. I was running a custom rom on my sprint note 5. The developer came out with an update and I tried to install and had all sorts of problems. I honestly believe it is not the rom as everyone seemed to take ok. Anyways I had to odin back to stock and I tried to install TWRP several different ways and kept getting an error message and the phone would not boot down and I had to odin back to stock. Well after going back to stock I was able to root with odin and I was able to flash stuff with FlashFire. So I was fine but now out of the blue I got this error about super su binary not updated and my root was gone. Now all the changes I made before I got this message still work and the phone seems fine but a few apps I use require root permission but since I lost root I cant use them.

Well anyways I saw this site and I am hoping it will work for me. I am stock MM and I have super su installed but dont have root. My question is do I put my phone in dl mode before I start toolkit or do I made all my selections and then at the end I plug it in.

Just leave the phone booted to Android. I assume you have adb drivers installed so you can plug the device in before starting the Toolkit so it can detect your build. The Toolkit will boot you to whatever mode you need to be in and there is loads (maybe too much) text to tell you whats happening.

I would welcome some feedback of your experience with the Note 5 module especially since you haven't used the Toolkit before.

Mark.

 

[mash4077fan]

Well I was able to root and install TWRP with this tool box. I am running the Sprint Note 5 running MM. Thank you

 

[Mediatech1]

@mskip sorry for the N00b question here, but if I'm understanding correctly skipsoft is a more controlled ecosystem for dealing with a ROM upgrade. I'm fine with paying for a service that eases the process a bit. Is there a "how to" area on skipsoft on say how you go from stock to custom Marshmallow? Better yet how you go from existing Custom ROM to a skipsoft environment? Thanks

Sent from my SM-N920P using XDA-Developers mobile app

 

[mskip]

@mskip sorry for the N00b question here, but if I'm understanding correctly skipsoft is a more controlled ecosystem for dealing with a ROM upgrade. I'm fine with paying for a service that eases the process a bit. Is there a "how to" area on skipsoft on say how you go from stock to custom Marshmallow? Better yet how you go from existing Custom ROM to a skipsoft environment? Thanks

Sent from my SM-N920P using XDA-Developers mobile app

Skipsoft is not a custom rom and I do not make any custom roms for any supported devices. The Unified Android Toolkit is a communication tool between your pc and device. You can use it to install correct drivers, backup your data/installed apps to your pc, flash a custom recovery to your device, root your device, boot to different modes and lots and lots more. You can also use the Toolkit to flash a custom rom that you have downloaded but I do not provide links to custom roms, they are quite easy to find.

Mark.

 

[stormrain]

I have been using your ToolKits in many of my previous phones mate, cheers

Pardon my ignorance, but this one should theoretically also support the SM-N920CD variant, right? I mean it's practically the same hardware plus an extra Sim Card slot..

Thanks

 

[mskip]

I have been using your ToolKits in many of my previous phones mate, cheers

Pardon my ignorance, but this one should theoretically also support the SM-N920CD variant, right? I mean it's practically the same hardware plus an extra Sim Card slot..

Thanks

Yes the custom recovery for the SM-N920C is exactly the same as the CD.

If you go to the Settings, About screen what is the model number of your device? There is no firmware available for the SM-N920CD which is why I did not add it straight away but some research has revealed that the dual sim model and single sim model use exactly the same firmware so if the model number of your dual sim model is SM-N920C then you can use that option in the Toolkit.

If thats the case I will add SM-N920CD to the SM-N920C option so there is no confusion for people who own the dual sim model.

Mark.

 

[stormrain]

Yes the custom recovery for the SM-N920C is exactly the same as the CD.

If you go to the Settings, About screen what is the model number of your device? There is no firmware available for the SM-N920CD which is why I did not add it straight away but some research has revealed that the dual sim model and single sim model use exactly the same firmware so if the model number of your dual sim model is SM-N920C then you can use that option in the Toolkit.

If thats the case I will add SM-N920CD to the SM-N920C option so there is no confusion for people who own the dual sim model.

Mark.

Yup, just like you said, in my About screen it's the SM-N920C model number. I did a bit of research as well and turns out that indeed, both models run the same firmware.
I guess that's why in sammobile there is no option for the CD device but only for the C.

Thanks

 

[mskip]

Yup, just like you said, in my About screen it's the SM-N920C model number. I did a bit of research as well and turns out that indeed, both models run the same firmware.
I guess that's why in sammobile there is no option for the CD device but only for the C.

Thanks

I will add the SM-N920CD model number to the SM-N920C selection after device selection so those users know what to select but you can use that one. I will also add a little info at the top to explain why.

Thanks for helping, Mark.

 

[mskip]

Update Available for Galaxy Note 5 device module [All Users]

Changelog:
+Added Dual Sim Model SM-N920CD with support up to the latest Android 6.0.1 builds

Pro Users can just select the Note 5 device at startup and the update will be available for auto download. Public users can grab the update by closing the Toolkit and running ToolkitClean.exe from the Toolkit folder, then selecting the Galaxy Note 5 from the list to delete device module files. You can then restart the Toolkit and select the Galaxy Note 5 to download new module files.

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast. Also follow me on twitter at https://twitter.com/mskipxda for posts/updates.

Enjoy, Mark

 

[adelistiawan]

No hopes for n9208 devices sir?

 

[mskip]

No hopes for n9208 devices sir?

Yes I can add the SM-N9200 and SM-N9208 support.

Mark.

 

[adelistiawan]

Yes I can add the SM-N9200 and SM-N9208 support.

Mark.

Thanks for your amazing work!

 

[mskip]

AutoUpdate Available for Galaxy Note 5 device module [Pro Users]

Changelog:
+Added China Model SM-N9200 with support up to the latest Android 6.0.1 builds
+Added China Dual Sim Model SM-N9208 with support to latest Android 6.0.1 builds

I will update the public device module to the latest version at the weekend after I finish working on adding OnePlus support for the 1, 2 and 3 devices.

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast. Also follow me on twitter at https://twitter.com/mskipxda for posts/updates.

Enjoy, Mark

 

[0xFFFF]

Upgraded SM-N9208 to 6.0.1 with no trouble at all.
Thanks mskip!

 

[mskip]

Upgraded SM-N9208 to 6.0.1 with no trouble at all.
Thanks mskip!

Thanks for the feedback. Glad everything is working as it should.

Mark.