Database Develop

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

[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY NOTE 8.0 [2012 MODEL] - Drivers, Root, Recovery + MORE
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports a multitude of Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
SUPPORTED MODELS
GT-N5100 3G/WIFI MODEL
GT-N5110 WIFI ONLY MODEL
GT-N5120 LTE MODEL
Click to expand...
Click to collapse
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
Enable Developer options for usb debugging
Go to Settings, System section, About device and tap on 'Build number' 7 times until it says you are now a developer. You can now go to Settings, System section, Developer options and enable USB debug.
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the device.
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 device.
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*

Mskip
thanks for this
is your version of cwm working properly?
thanks

jocko6872 said:
Mskip
thanks for this
is your version of cwm working properly?
thanks
Click to expand...
Click to collapse
I think that's for us us to test and tell him

sefrcoko said:
I think that's for us us to test and tell him
Click to expand...
Click to collapse
It's the same version as provided in the development thread.

i flashed the cwm
but cant do anything
cant even reboot

jocko6872 said:
Mskip
thanks for this
is your version of cwm working properly?
thanks
Click to expand...
Click to collapse
CWM is the experimental port from emwno in *THIS* thread.
I need people to test if the insecure boot image flashes and whether the root process works.
Mark.

madsatan said:
i flashed the cwm
but cant do anything
cant even reboot
Click to expand...
Click to collapse
Flashing custom recovery shouldnt affect the boot process have you tried just holding the power button for about 15 seconds to force a hard reboot?
Are there any lights or anything on the screen?
Mark.

Sorry that i didnt make myself clear
What i was saying is that i boot into cwm
Cant press any fuctions (cant back up or reboot etc)
I had to use power buttom to restar the tablet
Sent from my GT-N5110 using XDA Premium HD app

madsatan said:
Sorry that i didnt make myself clear
What i was saying is that i boot into cwm
Cant press any fuctions (cant back up or reboot etc)
I had to use power buttom to restar the tablet
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
As stated the cwm port is still experimental but it is being worked on by emwno and im sure he will get there.
Has anyone tried the root procedure yet with the insecure boot image? I really need some feedback here.
Mark.

Hey mskip,i just downloaded the toolkit and went through the insecure kernel process with no problems,tho i had already rooted using the Framaroot app. I also installed cwm and booted into it,although it's a little buggy it's useable ,just need something to flash in it now

ktmman said:
Hey mskip,i just downloaded the toolkit and went through the insecure kernel process with no problems,tho i had already rooted using the Framaroot app. I also installed cwm and booted into it,although it's a little buggy it's useable ,just need something to flash in it now
Click to expand...
Click to collapse
Glad its all working ok. Did you go through the ALL-IN-ONE process? Just wondering if you had installed busybox as I need someone to make a NAND backup from the backups section. If you can do that and then post a screenshot of the files (filenames and file sizes) then I can update it to a public version
Mark.

mskip said:
Glad its all working ok. Did you go through the ALL-IN-ONE process? Just wondering if you had installed busybox as I need someone to make a NAND backup from the backups section. If you can do that and then post a screenshot of the files (filenames and file sizes) then I can update it to a public version
Mark.
Click to expand...
Click to collapse
ok,i downloaded Busybox from the market,it looks like its going well,here's the data.

ktmman said:
ok,i downloaded Busybox from the market,it looks like its going well,here's the data.
Click to expand...
Click to collapse
Looks good
Now I just need someone with a full stock firmware flashed that can test the ALL IN ONE process and perform a NAND backup to make sure it works from scratch. Any takers?
Mark.

I will try once I'm home
Sent from my GT-N5110 using Tapatalk HD

n5120
got n5120, lte. can I use tools or I have to wait for n5120 version?
thanx in advance for answer.

goo.im seems to be down. Got a mirror?

thanks mskip
i use your nexus 4 tool kit a lot and was excited to see this one
i had already rooted via the framaroot app. was able to successfully load up CWM recovery (although it needs some help but i see in the other thread its being worked on).
also ran a backup successfully.

Sardo Numspa said:
thanks mskip
i use your nexus 4 tool kit a lot and was excited to see this one
i had already rooted via the framaroot app. was able to successfully load up CWM recovery (although it needs some help but i see in the other thread its being worked on).
also ran a backup successfully.
Click to expand...
Click to collapse
Flash Experimental #4 for your specific device (from my thread). Its working properly now.

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

[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY TAB S - Drivers, Root, Recovery + MORE
SUPPORTED MODELS/VARIANTS
GALAXY TAB S 8.4 [KLIMT]
WIFI ONLY MODEL [SM-T700]
LTE/WIFI MODEL [SM-T705]
LTE/WIFI CANADA MODEL [SM-T705W]
LTE/WIFI S AMERICA MODEL [SM-T705M]
GALAXY TAB S 10.5 [CHAGALL]
WIFI ONLY MODEL [SM-P800]
LTE/WIFI MODEL [SM-T805]
LTE/WIFI CANADA MODEL [SM-T805W]
LTE/WIFI S AMERICA MODEL [SM-T805M]
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to Hard Reboot the device
1. Unplug the USB cable.
2. Hold down the 'VOLUME DOWN' + 'POWER' buttons for about 5-15 seconds until the device reboots
How to get into Recovery Mode
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME UP' + 'POWER' buttons for about 5-15 seconds until you see the Samsung logo on the screen.
3. Release all buttons straight away to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME DOWN' + 'POWER' buttons for about 2-15 seconds until a WARNING! Screen appears.
3. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.

**UPDATES**

**VIDEOS**

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

Cool thing remember you from the Hd2 Era

Thanks for porting your tookit over to support our devices. Will be very useful for many
Cheers,
UITA

JUNEBUG-1 said:
Cool thing remember you from the Hd2 Era
Click to expand...
Click to collapse
yes I recall too..great work mskip!
---------- Post added at 08:36 PM ---------- Previous post was at 08:33 PM ----------
mskip..you may want to add that the NA models of the 705 and maybe 805 too cannot make cellular calls even though have LTE data...there have been several threads on this..most recent one in the original development section posed as a question..
this was discussed here already clarified by oldblue (am sure elsewhere too)
http://forum.xda-developers.com/galaxy-tab-s/general/pre-galaxy-tab-s-att-t2881310
http://forum.xda-developers.com/showpost.php?p=56084215&postcount=44
Thanks for your work!

Thanks for the Kit,
I'm looking for a perfectly stable ROM for Tab S 8.4 SM700. The only ROM I saw that seems stable is Iron-man. Are there any other ROM stable for SM 700?

Amazing job!
Thank you very much.

Thanks for this toolkit and for replying to my email, all working ok now.:good:

Does this tool support the SM-T800NTSSXAR ? ( 16GB Wifi US Model - also know as just the SM-T800 )?

ClockerXP said:
Does this tool support the SM-T800NTSSXAR ? ( 16GB Wifi US Model - also know as just the SM-T800 )?
Click to expand...
Click to collapse
Yes. I think there is a typo in the toolkit. It should say SMT800 instead of SMP800

Donated & THANK YOU!

Hi. Thanks for the tool, I'm looking for the root access and I'm wondering if your tool can support the newer version of Tab S 10.5 based on 5433 SoC (i.e., SM-T805K)
http://pdadb.net/index.php?m=specs&...b_s_10.5-inch_broadband_lte-a_samsung_chagall
I have this 5433 model from Korea, which the shell cmd tells me this: chagall. I could not find any root tools for this.
many thanks

Howdy-
I donated so that I could use this toolkit with my Tab S. Works great.
I also made another donation so I could use the Pro version with my Galaxy S4. Unfortunately, when the Pro version loaded up I saw it doesn't support the SCHi545 Verizon version of the phone. I immediately emailed the tool author to see if he would send back my extra donation since I could not actually use the tool for the S4 and because I had already donated for the Tab S. Been over a day and no response. I got the activation code within minutes but no reply the other way around.

I have a question, this root changes Knox to "1"???

Hi guys,
what's the meaning of [KLIMT] in "GALAXY TAB S 8.4 [KLIMT]" pl?
I hate to root my GALAXY TAB S 8.4 WIFI,16G0, is it ok with your tools?
Ths for you answer, good job!
B

Bishopandme said:
Hi guys,
what's the meaning of [KLIMT] in "GALAXY TAB S 8.4 [KLIMT]" pl?
I hate to root my GALAXY TAB S 8.4 WIFI,16G0, is it ok with your tools?
Ths for you answer, good job!
B
Click to expand...
Click to collapse
klimt is the models of the tab s 8.4. Your exact model is SMT700 so Im pretty sure it should work. Hope this helps!

Just got done trying to root and install twrp recovery on the tab s 10.5 wifi and I can get into recovery that worked bu the device is not rooted. twrp installed supersu and then I started it and it preceded to to an update. So I go to start supersu and it give me this message
There is no SU binary installed and supersu cannot install it
Any ideas. I have rooted lots of devices and have never seen this.
Thanks.

kendive said:
Just got done trying to root and install twrp recovery on the tab s 10.5 wifi and I can get into recovery that worked bu the device is not rooted. twrp installed supersu and then I started it and it preceded to to an update. So I go to start supersu and it give me this message
There is no SU binary installed and supersu cannot install it
Any ideas. I have rooted lots of devices and have never seen this.
Thanks.
Click to expand...
Click to collapse
Download a zip(google it) called supersu.zip then flash it with twrp and you will have root.

[Rom] [Ufirm_Flat_QE2_Hybrid_Nougat_Rom_FlashFire_Install][Status Official For All]

Latest Ufirm QE2 Nougat Firmware For The S7 Flat Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up​
Files To Download
Odin.zip
ADB_Root_G930U_QE2Files.zip
UFIRM_G930_Odin_Firmware.zip
FlashFire_Flashable_G930UFirmware.zip
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G930_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Goto Step 3 Below
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G930_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G930U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. Im not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
6. Unzip FlashFire_Flashable_G930UFirmware.zip
7. Copy AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 to your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip to your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source

In the OP I had the ADB_Root_G930U_QE2Files.zip linked to the ADB_Root_G935U_QE2Files.zip zip so please make sure you have the ADB_Root_G930U_QE2Files.zip when downloading. Its fixed in the OP now so just double check
I recommend everyone put the Flashfire AP zip and Rom Zip on your internal storage as the AP file is so large that it may not be read properly do too limitations of some SD Cards. When you select AP file in Firmware there should be 4 partitions that are selected. If not then you have a bad download or need to have AP file on internal storage

Thanks for all your hard work . I just installed this so far so good but I am missing Wi-Fi calling. Is that normal or am I just not looking in the correct place? Thanks

ledezma2003 said:
Thanks for all your hard work . I just installed this so far so good but I am missing Wi-Fi calling. Is that normal or am I just not looking in the correct place? Thanks
Click to expand...
Click to collapse
You may have to flash the TMO version of this rom

jrkruse said:
You may have to flash the TMO version of this rom
Click to expand...
Click to collapse
Ok will try that when I get a chance. Thanks again.

Thx for an awesome rom.
Sorry if this question is asked before but couldn't find a solution (checked Verizon thread as well).
I am running Playstore version ROM and everything is working fine except Video Recording.
Photo is fine but when I record a video with included Camera NX, it only plays sound and the screen is either still or black.

I have been taking a needed break. I will update all my s7 roms including this one in the next few days

Nice

That rom can flash for g930p? tks your work!!

@jrkruse
Thanks for all your contributions to this device. I just bought this device and I've been diving through the forums trying to gather as much info on this locked down device.
Could you provide me with just the boot images that don't check the system image and from what model/rom are they from?
Oh and could you provide the partitions locations? The latest roms have an updated Knox that blocks SU from doing it's thing and I have to perform everything via adb (eng boot).

Blank screen
Hello,
I am on your custom rom and the phone was working fine for a day. After I restarted the phone I am not able to see the lockscreen. Its just blank. I do hear the sound of taking a screenshot when I press the buttons and I also can see the " shut down, restart, emg mode" buttons when I hold the power button but no lockscreen. I tried running the recovery boot img but nothing changed.
There is some kind of issue at the locksceen after a restart.

I'm Stuck
jrkruse said:
Latest Ufirm QE2 Nougat Firmware For The S7 Flat Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up​
Files To Download
Odin.zip
ADB_Root_G930U_QE2Files.zip
UFIRM_G930_Odin_Firmware.zip
FlashFire_Flashable_G930UFirmware.zip
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G930_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Goto Step 3 Below
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G930_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G930U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. Im not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
6. Unzip FlashFire_Flashable_G930UFirmware.zip
7. Copy AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 to your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip to your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source
Click to expand...
Click to collapse
I followed the directions up to Step 7.
For the life of me I can not get the AP file to copy to my SD card. Yes I have enough space on it and I can get the ROM copied.
I tried copying the AP file with a file explorer, on my PC, external card reader. Every time I try, it gets to about 95-99% and says "copy failed".
I know it says flashfire only, but is that my only option?

Reegs said:
I followed the directions up to Step 7.
For the life of me I can not get the AP file to copy to my SD card. Yes I have enough space on it and I can get the ROM copied.
I tried copying the AP file with a file explorer, on my PC, external card reader. Every time I try, it gets to about 95-99% and says "copy failed".
I know it says flashfire only, but is that my only option?
Click to expand...
Click to collapse
In my case I created a folder named Download in Internal Storage and copied Zip and AP files there. I didn't have trouble coping files there.
From my experience & guess, you may still have old files & settings even though you flashed U-firm files Step 1-2.
Try to access recovery mode and do factory reset and see if this helps. Make sure you backup all important files to External SD because it will factory reset.

So I rooted my phone using Araltd's guide in this forum. I've got a couple of questions about this rom...
1. If I were to flash this rom to my device, would it remove my root access?
2. What's device performance like? After rooting, my device is very slow and buggy. Will this fix that?
3. Will my device still be full of T-Mobile's bloatware?
Thanks!

wolfpls254 said:
So I rooted my phone using Araltd's guide in this forum. I've got a couple of questions about this rom...
1. If I were to flash this rom to my device, would it remove my root access?
2. What's device performance like? After rooting, my device is very slow and buggy. Will this fix that?
3. Will my device still be full of T-Mobile's bloatware?
Thanks!
Click to expand...
Click to collapse
1. Yes, it will remove Root Access but you can still use ADB to do root stuff like push / pull files.
2. Since it will use stock boot instead of ENG boot, it will fix the lag issue.
3. This is U (universal) firmware so it won't have Tmobile bloat but it will have Samsung bloat/apps. During the install you can also choose de-bloat level too. From my experience BS-Free (2nd one), is both lightweight and stable. If you go with Playstore level (most lightweight, replace Samsung Apps with Google ones), you will have trouble with camera.

kyungone said:
1. Yes, it will remove Root Access but you can still use ADB to do root stuff like push / pull files.
2. Since it will use stock boot instead of ENG boot, it will fix the lag issue.
3. This is U (universal) firmware so it won't have Tmobile bloat but it will have Samsung bloat/apps. During the install you can also choose de-bloat level too. From my experience BS-Free (2nd one), is both lightweight and stable. If you go with Playstore level (most lightweight, replace Samsung Apps with Google ones), you will have trouble with camera.
Click to expand...
Click to collapse
Do you know how this rom compares to the QF6 one which seems to be a bit more popular?

wolfpls254 said:
Do you know how this rom compares to the QF6 one which seems to be a bit more popular?
Click to expand...
Click to collapse
The QF6 ROM you mentioned is T-mobile firmware so it will have Tmobile apps. Most of them can be removed from ROM install or disabled after.
Other than that there's no performance difference.
If you want Tmobile like environment with Tmobile update schedule, go with T-mobile one. If you want less carrier apps, go with U-Firmware one.

I will no longer be updating my s7 threads until the time Oreo is released with root method. For now I have worked with @stang5litre to bring my non-root method to his amazing rom. He currently has a nougat release found here http://stang5litre-roms.proboards.com/

I keep getting samsung pay connection error. any fixes? i tried factory reset and reset settings, but the app still doesnt work. do i have to reflash the rom?

amdeng said:
I keep getting samsung pay connection error. any fixes? i tried factory reset and reset settings, but the app still doesnt work. do i have to reflash the rom?
Click to expand...
Click to collapse
If you at any point tried to root it or flashed the modified boot image then you are no longer passing the safteynet checks, my suggestion is to do a clean install and see if it works then try it again making sure you don't root after you are done installing this rom.

(Guide)Root +Busybox + OEM Fix + EFS backup Note 9 N960F/FD/N Exynos only

How to ROOT Samsung Note 9 N960F/FD/N
Before trying make sure that flashing said file,
- Warranty will be void
- You won't be able to use Secure Folder/Samsung Pay forever (or may be more)
- May lose OEM unlock option
- Backup important stuff as you need to full wipe device (including internal storage)
DO IT ON YOUR OWN RISK
What is OEM fix?
Since Note8 samsung have introduced OEM unlock control remotely and flashing any custom binary removes OEM unlock option and rebooting in this state it ends with custom binary error and have to flash stock firmware. OEM patch will retain OEM unlock option in spite of having custom recovery. If you are not sure your device have OEM issue then there is nothing wrong to use 'OEM patch' option.
If you don't have OEM unlock option out of box then it may appear after 7 days, before this nothing can be done. Also this suggest, you have OEM affected device.
Click to expand...
Click to collapse
METHOD 1 : Root with TWRP Also works on Android Q (RECOMMENDED)
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card
4.Download TWRP for N9
5.Switch Off device
6.Press Vol down + Bixby and connect to PC to reboot to download mode, press volume up when asked to continue to download mode
7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14A (If you are on Pie)
.Now select Install and navigate path to Ext SD card - N960_root_OEM_issue_devices_V*.zip, you have copied earlier, select desired root method and select 'OEM Patch' option if your device have OEM issue. If you are not sure about this then better select 'OEM Patch', this will prevent losing OEM unlock option and so prevent 'custom binary error'
OR
14B (If you are on Android Q)
Flash Latest magisk & then DM-VERITY, FORCED ENCRYPTION, AND DISC QUOTA DISABLER
15.Once flash successfully finish, Reboot to System
Magisk app may appear in drawer after one reboot.
Important Note for Pie - There will be OEM unlock option there in developer setting but it will be disabled and can not enabled, this is because of it is hacked. Just ignore it. You can not boot device with TWRP if it is really disabled. Also If magisk app may not appear then simply download Magisk_for_Pie.apk from below attachement and install as regular app.
Open settings - Developer option - Look for OEM Unlock option. If it is there, it is safe to reboot device.
Credits and Thanks goes to BlackMesa123 for OEM fix
Click to expand...
Click to collapse
METHOD 2: Root with Stock Recovery (NOT SAFE ON OEM ISSUE DEVICES)
1.Download Magisk.apk attached below
2.Download Prerooted_N960_Exynos.zip (For Oreo Only)
3. Keep stock ROM file ready in case this doesn't work
4.Download De-Knox tool attached below (optional)
Installation :
- Enable OEM unlock
- Reboot to Download mode
(Here method changed - Switch off device - connect top PC - Press Vol down + Bixby)
- Extract (Unzip) Patched kernel - you will get N960F_kernel_PreRoot_RH5_DrKetan.tar.md5
Flash it using latest Odin with AP tab
- Once file successfully flashed, device will reboot and ask to reset device.
- Reset device, keep patience, device may take 5-7 minutes to boot.
- Once device reboot - Install Magisk manager apk manually
- install De-Knox tool apk and click icon, this will remove all knox app (no more useful on rooted device). This will also remove security messages
YOU MUST BACKUP EFS AS SOON AS ROOT DEVICE, and copy it to safer place,
Click to expand...
Click to collapse
14.01.2019 - Added support for Pie
Credit and Thanks to breakersvd for ril patch (defex fix) and @topjohnwu for magisk
EFS Backup Tool
As soon as you root device, you must make backup of EFS and must store a copy of backup to safer place like on cloud and on a PC
XDA version - Free version, complimentary tools for XDA users attached below.
Play Store version - You can buy from Play store to support us.
Both version make same form of backup and have no difference, Paid version have additional function to make Auto Backup when you change the ROM

So if we do lose OEM unlock, this means we will never be able to unlock the bootloader later on down the road, right?
I love your work and look forward to it every time I get a phone.

chrispyutec said:
So if we do lose OEM unlock, this means we will never be able to unlock the bootloader later on down the road, right?
I love your work and look forward to it every time I get a phone.
Click to expand...
Click to collapse
No, on previous device you get oem unlock option back again after 7 days
Though this is csc related and not all users will lose this option. Usually if your device have unlock option out of box then mostly you won't lose it. Though if we get root working we may need move forward to fix this

When its a kernel parched with normal magisk it will break ril because samsung added defex to the galaxy n9. I have only a semi working root on mine with ril

Here you see the half working root with ril. Normal magisk will break ril like i said

geiti94 said:
Here you see the half working root with ril. Normal magisk will break ril like i said
Click to expand...
Click to collapse
Have you tried hex patch similar issue reported on A series? Tried TWRP? Or you are waiting for kernel source. We badly needed it now.

dr.ketan said:
Have you tried hex patch similar issue reported on A series? Tried TWRP? Or you are waiting for kernel source. We badly needed it now.
Click to expand...
Click to collapse
Twrp with stock zimage dont boots and with compiled img from s9+ source same thats why i am waiting soueces. Twrp tree is allready finished and defconfig too. Only source is missing but sammy dont released it today. And n9 defex is different from a8 one

geiti94 said:
When its a kernel parched with normal magisk it will break ril because samsung added defex to the galaxy n9. I have only a semi working root on mine with ril
Click to expand...
Click to collapse
Wow! Wtf Samsung!!!??

How did you manage that half working root ?

siriom said:
How did you manage that half working root ?
Click to expand...
Click to collapse
Its a modded magisk where magisk hide and magisk manager gives fc. That means root is all time enabled and i dont need to press confirm and works only with some apps. For example es file explorer cant get root and titanium backup same

geiti94 said:
Its a modded magisk where magisk hide and magisk manager gives fc. That means root is all time enabled and i dont need to press confirm and works only with some apps. For example es file explorer cant get root and titanium backup same
Click to expand...
Click to collapse
If you to open a prompt and su ? would that work ?
I would like to mount or chgroot ....
This obviously blows up the whole knox deal right ?

geiti94 said:
Twrp with stock zimage dont boots and with compiled img from s9+ source same thats why i am waiting soueces. Twrp tree is allready finished and defconfig too. Only source is missing but sammy dont released it today. And n9 defex is different from a8 one
Click to expand...
Click to collapse
It's up now

FINALLY ROOTED NOTE9
May be Worlds first fully rooted Note9
Big thanks goes to @breakersvd for his special hex fix for recent samsung devices.

I will re-write first post with new files soo

Amazing @dr.ketan ??

Amazing @dr.ketan ??

Really appreciate this! Just to confirm, by rooting we will lose Secure Folder and Samsung Pay only (for now)?
If I unroot, will I receive ota?

Plzz let us know how to fully root note 9 dr.ketan
Plzz update file and root process .. i am very excited to root my note 9 .. dr. Ketan u r the best.. love ur work????

Nasty_z said:
Really appreciate this! Just to confirm, by rooting we will lose Secure Folder and Samsung Pay only (for now)?
If I unroot, will I receive ota?
Click to expand...
Click to collapse
You will lose secure folder and Samsung pay forever even if you unroot. You cannot undo this once done

pankajgavri said:
You will lose secure folder and Samsung pay forever even if you unroot. You cannot undo this once done
Click to expand...
Click to collapse
Yes, I know. I asked about ota after unrooting. I can still get ota if I unroot?

Alternative method magisk root [stock android 9][NO TWRP][Samsung A70 FN/DS]

purpose of this post is to share an alternative method for those who fail to root using @topjohnwu recommended method or the method posted by @Grarak here on A70 forum that involves patching recovery.img in magisk and then flashing that in twrp>install to boot.
failing to root means either bootloops or unstable magisk root or magisk root disappearing randomly or after a module installation.
this is not my original guide , i was told this method by @raeumler via PM and i am sharing it on A70 forums incase other methods dont work.Some of the steps may not be neccesary , but i did them ritually anyway
my phone model is SM-A705FN /DS and firmware version is A705FNXXU5ASL4( with 1st jan 2020 updates) . country is PAK
do this at your own risk! i will not be responsible for any negative consequences
appropiate links and files will be posted as attachments
rooting procedure( read each step twice)
1- UNLOCKING BOOTLOODER= this will factory reset device . backup your data
read step 02 of this linked guide https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
DOWNLOAD FIRMWARE AND ATTACHMENTS= now i am assuming you have stock samsung android 9. if not, download your firmware via SamFirm windows program and flash in odin to go to stock[ program available in attachements]. Download other attachements too
2-Find vbmeta.tar in downloaded attachments and unpack it. you will get vbmeta.img file.
3. unzip stock Samfirm downloaded firmware. you will get 5 files in it (BL,AP,CP,CSC and CSC_HOME).open the AP File from the factory rom with 7zip
4. remove userdata.img, vendor.img and system.img from the AP file
5. replace vbmeta.img with the one you have downloaded in step 2.
6. repack AP as AP.tar [ use 7zip or peazip. i used peazip windows program, ensure file type is TAR]. transfer this AP.tar to your phone
7. install magisk manager 7.5.1 on your phone and open it. connect your phone to internet.
8. hit the upper install button and choose "patch a file"
9. choose the repacked AP file and patch it[ this requires active internet as magisk needs to download its zip file]
10. copy the AP file which magisk creates in internal storage/download/magisk_patched.tar back to your pc (better keep it named as such for differentiation, its irrelevant how the file is named as long its a tar file)
11. download,unzip and open Odin 3.1.3.1[available in attachements]. i used Odin3+v3.13.1_3B_PatcheD.exe , there is a simple version too inside the zip
12. go into download mode on your phone (shut down completely then hold vol+ vol- togather and plug in cable connected to PC ). Odins should show Com port X as blue
13. in odin: put the BL, CP and HOME_CSC in its place (the files from the factory firmware you downloaded in step 1 from SamFirm windows program) and place the magisk patched AP on AP
16. check if you want autoreboot or not, its your own taste (some feel safer with autoreboot unchecked, both works)[ i kept autoreboot checked]
15. hit start and let it finish (when it stucks on something try another cable and install latest samsung adb driver.)
16. let the system reboot
17. if you get stuck in bootloop or freeze >10 min on samsung logo, try to force reboot.press volume down + power till screen turns blank then press volume + and power till bootloader unlock screen appears and then let go of all keys.
if still it doesnt boot, then press volume down and power togather to force shutdown and then press volume up and power till stock recovery boots up. Mine at this stage said firmware is corrupt ,factory reset needed so thats what i did in stock recovery. power off system in stock recovery and then press volume+ and power till bootloader warning screen , let go of all buttons, it should now boot up fine with magisk manager app in app drawer. DONT OPEN IT YET
download this app from play store https://play.google.com/store/apps/details?id=fr.petrus.tools.reboot&hl=en_US. open app and press reboot. No need to press any keys
on reboot complete ,connect to internet,open magisk, let it check for updates, it should say installed in both portions. magisk will do additional enviromental steps and then reboot. on booted up, use the linked reboot app to reboot again.
now magisk should be installed all fine
for viper4android>open magisk>swipe left and tap downloads> installed 2.7.1.6> reboot with linked app
on reboot check if app is installed, if not > install and login on xda labs and download viper4android 2.7.1.6> open app> give it root accesss> let it reboot device on installtion> on bootied up reboot again with linked app and then check drivers on viper4android[ make sure master switch is on and then play some music ,tap the chip icon to see driver status and processing status
from here onward, always use the linked reboot app to reboot device. if an app or module reboot device automatically( like viper4android does ) then on boot complete,reboot again with the linked app
Credits to @Grarak for his original work and files
 @raeumler for his guide.

Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.

kac222 said:
Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.
Click to expand...
Click to collapse
This is for stock android 9 as the title says.
Follow @MarvinMod guide to root android 10

Yes i know but i tried for yourself. I know how rooted on Android 10. Regards.
Wysłane z mojego SM-A705FN przy użyciu Tapatalka

Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?

DelphisDoofer said:
Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?
Click to expand...
Click to collapse
Download phone info app and note pda, csc and phone codes.
Use these codes to Google your exact firmware and download that ( you may have to visit various websites that offer better speed)
The samfirm, frija only allows latest firmware to be download, not the currently installed one.
One you have the stick firmware file, then you can proceed with rooting.
If you are on android 9 use this guide
If you are on Android 10 use MarvinMod guide.
This reboot app is what I currently use. Haven't experimented with other apps.
The root is permanent as long as your reboot with the mentioned key combination or the reboot app.
The reboot app simple allows you to reboot without the key combination. If you don't want to use this app then you must reboot with the mentioned key combination to retain root. Otherswise you wouldn't have root unless you reboot again with correct combination.
To make this easy I suggested that reboot app
Yes I feel you bro, I had Samsung note 2 then note 4 phone and they were easier to root.
But with Google changing things the best way to root is to use magisk and this complicated methods

i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....

raeumler said:
i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....
Click to expand...
Click to collapse
I didn't messed with boot or recuvery files like the way you DM me.
But I have been noticing strange behavior with petrus app.
Reboot option in petrus app is kinda of like fast reboot or reboot UI. Because all apps opened and present in task manager remain so after reboot with petrus app.
Also once you power off with petrus app,
1= booting up with root key combination results in phone getting freeze Or bootlooping
2=. Force shutting phone again bootloop phone.
3= Going to stock recovery and rebooting system bootloop.
4= going to stock recuvery and shutting off phone from there and then simply pressing power button without key combination, successfully bootup phone with root intact.
This is such a bizzare behaviour
Oh and i am still on Android 9 pie.