Database Info

[ROM][ICS][STOCK][GT-P5100] ICS 4.0.3 Stock Safe / Recovery / Root (P5100XWALD7)

=========================================================================================
=== Device: GT-P5100 (Galaxy Tab 2, 10.1", 3G model)
=== Description: Safe stock ODIN image, recovery and root
=== Packaged by: cheatman ( xda - http://forum.xda-developers.com/member.php?u=490310 )
=== Stock ROM version: P5100XWALD7
=== Build date: 07 June 2012
=========================================================================================
Disclaimer: I am not responsible and assume no liability on how this information is used. This package is provided "as is" without any warranty and does not guarantee any fitness for any purpose.
ONLY FOR GT-P5100 (3G model)!!! Do not flash on any other Galaxy Tab 2!!!
Download the ZIP (large, about 600MB) from here:
=> DOWNLOAD FROM HERE (HotFile)
How to use: Read the readme.txt file or this post here.
On to the safe stock restore process:
1. Make sure you have the Samsung device drivers installed before you begin. If you don't, install them from here:
- 64bit: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
- 32bit: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
2. Make sure your tablet's battery is at least 30% charged up before you begin.
3. Make sure you have an external microSD inserted in the device, if you also plan on rooting afterwards. Nothing will be erased from the microSD, there is no need to worry about that.
4. Run procedure to flash back the stock ROM from Samsung (Ice Cream Sandwitch 4.0.3 - P5100XWALD7) from the folder "Step1-Stock". STOP HERE FOR PURE STOCK!!!
5. Run procedure to enable ClockworkMod recovery from the folder "Step2-Recovery". This step is OPTIONAL (only if you want a custom recovery). STOP HERE IF YOU DON'T WANT ROOT!!!
6. Run procedure to enable "root" access from the folder "Step3-Root".
7. Done! Enjoy! Profit!
===============================================================
========== Step 1 - Flashing Stock P5100XWALD7 ================
===============================================================
1. Download the file from the link above.
2. Shut down your tab.
3. Disconnect tab from USB and/or power cables.
4. Hold "Power+Volume UP" physical buttons on your tablet to initiate download mode.
5. Press "Volume DOWN" physical button on your tablet to confirm and enter ODIN mode.
6. On your PC, open "Odin3 v1.85.exe"
7. Press "PDA" button in ODIN and select the "PLATFORM_P5100XWALD7_482645_REV02_user_low_ship.tar.md5" file.
8. Press "PHONE" button and select the "MODEM_P5100XXLD7_REV_01_CL1128355.tar.md5" file.
9. Connect your tablet using a USB cable. In ODIN you should see the device "<added>" message appear. If you do not, there is a problem with the Samsung drivers installation.
10. Confirm that only the following options are checked in ODIN: "Auto Reboot", "F. Reset Time", "PDA", "PHONE". DO NOT CHECK RE-PARTITION!!! NEVER!!!
11. Click the big "Start" button and WAIT. Be patient!!! The process takes about 3-4 minutes but can take longer.
12. Do not power down the tablet while this takes place. Do not shut down your PC. Do not touch anything! Just wait! Get a coffee or something...
13. After full flash the tablet will reset automatically.
14. Congratulations you are now safely back to stock P5100XXALD6.
15. There is no need to flash the bootloader and CSC. Do so at your own risk.
===================================================================
========== Step 2 - Flashing ClockworkMod Recovery ================
===================================================================
1. Download the attached recovery file "p5100-recovery.tar.md5.zip" and extract it.
2. Shut down your tab.
3. Disconnect tab from USB and/or power cables.
4. Hold "Power+Volume UP" physical buttons on your tablet to initiate download mode.
5. Press "Volume DOWN" physical button on your tablet to confirm and enter ODIN mode.
6. On your PC, open "Odin3 v1.85.exe"
7. Press "PDA" button in ODIN and select the "p5100-recovery.tar.md5" file.
8. Connect your tablet using a USB cable. In ODIN you should see the device "<added>" message appear. If you do not, there is a problem with the Samsung drivers installation.
9. Confirm that only the following options are checked in ODIN: "Auto Reboot", "F. Reset Time", "PDA". DO NOT CHECK RE-PARTITION!!! NEVER!!!
10. Click the big "Start" button and wait a few seconds. Flashing recovery.img is super-fast!
11. After recovery flash, the tablet will reset automatically.
12. Congratulations you are now running recovery for your tablet.
13. Note: Internal SD is not working with this recovery, you must use external microSD cards to load up ZIPs.
14. You can also download and extract the kernel and flash it also on "PDA" if you want a rooted Kernel
=========================================================
========== Step 3 - Enabling root access ================
=========================================================
1. Download the attached file "CWM-root-P5100-v1.zip".
2. Copy the "CWM-root-P5100-v1.zip" file to the external microSD card.
3. Shut down your tab.
4. Insert the microSD in the tablet.
5. Hold "Power+Volume DOWN" physical buttons on your tablet to initiate recovery mode. It takes a while to start up recovery (10-15 seconds) so be patient. Try not to press too hard on the buttons as it does not help at all (takes same amount of time :-D)
6. Use the "Volume UP" and "Volume DOWN" buttons to navigate (select options) and the "Power" button to select. Don't HOLD the buttons, just press them (like a click or something).
7. Select the option to install ZIP from sdcard.
8. Navigate to where you copied the "CWM-root-P5100-v1.zip" file and select it.
9. Wait for the operation to complete.
10. Navigate back and select option to "Reboot system"
11. Congratulations you have a fresh stock ROM with CWM and root ready to go!
12. Enjoy
=======================================================================================
Thanks and greetings go to:
- Galaxian-Soup
- nycbjr
- All others who help and bring value to the XDA comunity!
Peace and have fun!
C.

Reserved!
Looking for mirrors. This is a very large file!
Thanks.

Ah damnit lol this was almost what i was looking for. I need the one for the wifi version.
Do you think the recovery would be the same? Thats the only part i really need lol.
Nvmind i see its all in one file lol

Recovery is in an independent folder, you don't flash the initial zip lol.
Anyway, the recovery and root steps should apply to p5110 as well.
Cheers,
C.

Thank you for all the hard work. I'm sure my Willy nilly ways will require me to use this
Sent from a note on fire in the middle of the sea

Hi,
I see that in your instructions for flashin stock do not use file "BOOTLOADER_P5100XXALD6_365113_REV02_user_low_ship. tar.md5" which is otherwise included in the package, does that mean that it did not necessarily use one?
When it is necessary to use that file?
Thanks.

Updating the bootloader is not required.
Playing with bootloaders is very risky and dangerous in general (can permanently brick tab).
Bootloader is responsible for the download mode. If you can access it and flash using odin, there is no need to mess with it. Upgrading it may result in a locked boot mode, meaning you can't flash custom stuff anymore.
I included only the required files and steps so you guys don't have to look for the right combination.
Peace,
C.

Thank you for the file sir oh sir.
Rapidshare mirror
Sized at 492.65MB, i recompressed the file using 7-zip to cut off the size a bit. It is below 500MB, meaning it's Dev Host friendly.
Code:
stock-safe-p5100-4.0.3-v1.zip 2E5566F2311BAD666A8CFD9674AEE0A5
stock-safe-p5100-4.0.3-v1.7z 946AAC1EDE408FFCA48BAF592AC3F92C
Step1-Stock
MODEM_P5100XXLD6_REV_01_CL1128355.tar.md5 07EFC235DC6989D50C9321076EDCDFC1
PLATFORM_P5100XXALD6_365113_REV02_user_low_ship.tar.md5 8186B1660ED2D4C1752336014ED047FD
Step2-Recovery
recovery.tar.md5 16AFDD2FEDBD8476521D9C144C823023
Step3-Root
CWM-root-P5100-v1 4D2E472F0C0A640F4170B9500F39FCAC
Can someone please confirm the hashs?

I rooted my Galaxy Tab 2 10.1 WiFi GT-P5110 using the manual and it works fine!
Thanks for the manual
Sent from my r00t3d GT- P5110 using XDA Premium App

Updated new version of the stock image.
Thanks for this find go to our friend "zi0m3k" (cheers, mate!)
C.

How did you capture the stock recovery from the device? I would like to do the same from my GT-P5113, but (of course) one has to flash CWM first to get access, and that overwrites the recovery.

Stock recovery comes with the stock ROM, so you need to overwrite it, not capture it.
But, to clarify the issue, you can root your device without a custom recovery. After you root, you can dump system images using the "dd" command.
Rooting using CWM zips is just more convenient and easier for everyone, it's not the only option, though. There was root before recovery...
C.

cheatman said:
Stock recovery comes with the stock ROM, so you need to overwrite it, not capture it.
But, to clarify the issue, you can root your device without a custom recovery. After you root, you can dump system images using the "dd" command.
Rooting using CWM zips is just more convenient and easier for everyone, it's not the only option, though. There was root before recovery...
C.
Click to expand...
Click to collapse
I know that the final goal is to overwrite the recovery to get the benefits of CWM (e.g.). But if you want to save the *stock* recovery first, you need to capture/dump it from the device somehow before flashing (correct me if my logic here is incorrect).
Also, yes, I know a good way to dump it is with "dd", but one needs root to do that (I tried for the hell of it, to see if there was non-root read access, but alas, no).
I think you have hit upon my question regarding root: did you root the tab without flashing CWM? If so that will allow "dd" to capture the stock recovery, yes. If you used CWM, that you overwrote the recovery, and you would not have been able to save the stock recovery in that case.
I have not found a rooting method for the GT-P5113 that does not involve flashing CWM, so I cannot figure out how to same my stock recovery, which I would like to do before flashing CWM (and thereby losing the stock recovery forever).

I obviously dumped the recovery before I flashed CWM, otherwise it wouldn't be stock.
If I get you right, you want to know the root exploit I used to root my p5100 to get suid and be able to copy the "su" binary. In fact, getting elevated rights on a linux system if you have direct access to it is not rocket science. However, because that's a lot to write, here is a more simple solution you can apply to get a stock recovery that I didn't have at the time:
1. Go to samfirmware.com and download a stock rom for your device.
2. Extract the .tar.md5 files and get the "recovery.img" out of them. Usually the "boot" and "platform" files have one inside.
I reckon all p51xx devices have the same recovery anyway, but it might not be the case.
C.

cheatman said:
I obviously dumped the recovery before I flashed CWM, otherwise it wouldn't be stock.
If I get you right, you want to know the root exploit I used to root my p5100 to get suid and be able to copy the "su" binary. In fact, getting elevated rights on a linux system if you have direct access to it is not rocket science. However, because that's a lot to write, here is a more simple solution you can apply to get a stock recovery that I didn't have at the time:
1. Go to samfirmware.com and download a stock rom for your device.
2. Extract the .tar.md5 files and get the "recovery.img" out of them. Usually the "boot" and "platform" files have one inside.
I reckon all p51xx devices have the same recovery anyway, but it might not be the case.
C.
Click to expand...
Click to collapse
Hi, yes, that's exactly right - I wanted to know how you got elevated rights in order to use dd for this.
I really want the recovery image from *my* stock tablet - not one off the net.
Could you private message me, if you are uncomfortable talking about it here. I am well-versed in Linux (I've done kernel development, I'm part of the Gentoo Linux dev team, etc.), so I am no stranger to Linux. I know there are exploits now and then, but they are not usually trivial. If you found a new one for the current kernel, then I'm impressed, and please do tell. If you found the exploit somewhere on the net, can you send me a link?
Thanks, Joe

Well, I must admit I actually took my time thinking whether I should actually write a reply :-D
However, my main concern is having to write a lot to explain stuff, but considering you are a kernel dev, this should be easy peasy. In short, I didn't force my way in, I just *convinced* the system to let me in. It's an inherent problem of Android, in fact:
1. Extracted the boot.img and unpacked it.
2. Replaced the adbd binary in the ramdisk with an unsecure one.
3. Repackaged and flashed using ODIN.
4. Used adb root to get into the system, the *regular* way. Once adbd lets
5. Installed su and superuser.apk.
There is no need to exploit the kernel if the system is inherently flawed when it comes to direct access (adb root exists). Any and all Android devices that use this layout (boot.img) can be rooted this way. Sorry to disappoint you about the exploit, but I am no *real* dev. I just know my way around :-D
PS: You can get the latest boot.img I did for this purpose here
Hope it helps with your recovery dump,
C.

cheatman said:
There is no need to exploit the kernel if the system is inherently flawed when it comes to direct access (adb root exists).
Click to expand...
Click to collapse
Very interesting - that was my missing piece of the puzzle - I had not realized one could replace the adbd. Makes sense. I will certainly give this all a try! I may be experienced with Linux, but I have a lot less background in android internals; learning quickly, though. In fact, my next project (when I get some time) is to try building the GT-P5113 ROM from source (and also some delving into AOSP). Being able to customize at the source level would be very cool.

LavaJoe said:
Very interesting - that was my missing piece of the puzzle - I had not realized one could replace the adbd. Makes sense. I will certainly give this all a try! I may be experienced with Linux, but I have a lot less background in android internals; learning quickly, though. In fact, my next project (when I get some time) is to try building the GT-P5113 ROM from source (and also some delving into AOSP). Being able to customize at the source level would be very cool.
Click to expand...
Click to collapse
I would be eternally grateful if you could post the stock rom for the 5113 (including stock recovery) if you can. I would settle for just the stock recovery in flashable form via odin etc.

A read through Samsung's kernel source reveals that the governors are already coded into the kernel (install voltage control and you can switch between governors and schedulers at will).
It looks like the set stock speed on the 10.1 5113 is 1008MHz.
Does anyone know how/where in the kernel overclocking is programmed?
The source also looks pretty comprehensive for the tablet and apparently is very similar to that of the 7" tab. I imagine it wouldn't be too hard for a veteran coder to fix this up for the 10" users.
I haven't coded in years and I'm not familiar enough with Android to do anything but attempt to compile the source from Samsung.

Hi,
Does this work on P5100XXLD6 ?
Android version 4.0.3
Thanks

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

INTRODUCING THE SAMSUNG GALAXY S3 UNIFIED TOOLKIT
SUPPORTED MODELS
INTERNATIONAL [GT-I9300] SUPPORT THREAD HERE
AUSTRALIAN MODEL GSM [GT-I9300T]
INTERNATIONAL [GT-I9305/GT-I9305N] SUPPORT THREAD HERE
AUSTRALIAN MODEL LTE [GT-I9305T]
C SPIRE MODEL LTE [SCH-L710]
AT&T US [SGH-I747] SUPPORT THREAD HERE
BELL, ROGERS, SASKTEL, TELUS [SGH-I747M] [SGH-I747M] USE AT&T SUPPORT THREAD
US CELLULAR MODEL LTE [SCH-R530] USE AT&T SUPPORT THREAD
METRO PCS MODEL LTE [SCH-R530M] USE AT&T SUPPORT THREAD
SPRINT US [SPH-L710] SUPPORT THREAD HERE
TMOBILE US [SGH-T999] SUPPORT THREAD HERE
MOBILICITY, VIDEOTRON, WIND [SGH-T999V] USE TMOBILE SUPPORT THREAD
VERIZON US [SCH-I535] SUPPORT THREAD HERE
CHINA ANYCALL CDMA MODEL [SCH-I939] USE GT-I9300 SUPPORT THREAD
Click to expand...
Click to collapse
The Unified Android Toolkit supports a multitude of Nexus and Samsung devices with more devices being added all the time. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.4 [9TH JAN 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

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

**VIDEOS**

excellent

great

great share!

Will this work for rooting the XXALI9?

this is great,

lithium86 said:
Will this work for rooting the XXALI9?
Click to expand...
Click to collapse
It will work on everything upto ALJ7 and beyond.
Final checks and uploading now.
Mark.

The Toolkit will be finished uploading in less than 10 minutes but before I release it publicly I need someone with a GT-I9305 to download and test the root and nand backup features. Please message back in here if you can test it right away as I can't post the link until I know it works properly.
Theres absolutely no risk of any damage as Stock Firmware images exist for your device so if anything doesnt work a simple flash will fix anything.
Mark.

Download link posted in OP.
Thread officially open
If anyone spots any bugs or errors in V6.0.0 please let me know right away as this was a major major rewrite to be able to incorporate I9305 and while I think everything looks fine I may have missed something.
Enjoy.
Mark.

Thanks Mark!
I know it is not your bag but any idea when CWM-Touch may be available for the I9305?
Thanks!

ALI9 ??
The welcome screen does not show the xxxali9 version of the i9305 model.. I surpose that means we have to wait for support for this one as well ??
Edit... didn't see before after posting that this q already has been answered....

[email protected] said:
The welcome screen does not show the xxxali9 version of the i9305 model.. I surpose that means we have to wait for support for this one as well ??
Click to expand...
Click to collapse
Did you read the text on the Model Selection Screen?
FOR ROOTING AND PERFORMING ADB TASKS ON YOUR DEVICE, IF YOU CANNOT FIND THE BUILD
IN YOUR DEVICES SECTION THEN YOU CAN SELECT THE CLOSEST BUILD IN THE LIST (AS LONG
AS IT IS THE SAME ANDROID NUMBER IE. 4.0.4 or 4.1.1).
Click to expand...
Click to collapse
For xxali9 you can choose the ALI5 or the ALJ4 model it doesnt matter they will both work perfectly.
Mark.

mskip said:
Did you read the text on the Model Selection Screen?
For xxali9 you can choose the ALI5 or the ALJ4 model it doesnt matter they will both work perfectly.
Mark.
Click to expand...
Click to collapse
Thanks a lot.. . .Wasn´t sure..
and one thing is for sure.. Rather ask you one time to much, than brick my phone.:angel:

[email protected] said:
Thanks a lot.. . .Wasn´t sure..
and one thing is for sure.. Rather ask you one time to much, than brick my phone.:angel:
Click to expand...
Click to collapse
Correct
Mark.

Just to clarify for I9305 users this toolkit states full support for our device but just be aware it cannot communicate in Qualcomm Diag Mode so backing up EFS on its own is not amicable. Please still use the QPST method to backup NV Items and EFS area of the device.
For anything else then this toolkit is the biz although I write my own tools!
Sent from my GT-I9305 using Tapatalk 2

Thanks for your hard work. I love the Nexus toolkit.
Do you have any plans to expand this G3 toolkit for verizon? It is the d2vzw.

lyriquidperfection said:
Just to clarify for I9305 users this toolkit states full support for our device but just be aware it cannot communicate in Qualcomm Diag Mode so backing up EFS on its own is not amicable. Please still use the QPST method to backup NV Items and EFS area of the device.
For anything else then this toolkit is the biz although I write my own tools!
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Do you mean we should use the steps provided in this guide - http://forum.xda-developers.com/showthread.php?t=1946915 before using the Samsung Toolkit?

lithium86 said:
Do you mean we should use the steps provided in this guide - http://forum.xda-developers.com/showthread.php?t=1946915 before using the Samsung Toolkit?
Click to expand...
Click to collapse
Yes and I'm also updating my application to support Qualcomm NV item backup and restore.
Sent from my GT-I9305 using Tapatalk 2

[TOOLKIT] GALAXY S4 GSM Drivers, Backup, Root, Recovery, Flash, + MORE

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

**Updates**

**FREQUENTLY ASKED QUESTIONS**
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to
send commands to your android device. For S-ON devices, this is crucial for
modifying files in the /system partition (where the rom sits) as you cannot modify
anything in /system when the rom is running without S-OFF like removing system apps.
------------------------------------------------------------------------------------
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. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery
partitions so you can restore a complete rom and all data and settings.
Titanium Backup is mainly used to backup apps and associated user data. These
could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb
backup which is in the ToolKit and can do the same job as Titanium Backup but will
store the data on your PC rather than on the phone (which takes up space).
Q. I cannot find Developer options
With Android 4.2 google have thought it would be funny to hide the Developer options
screen in the Settings. This means you cannot enable usb debugging to communicate
with your device. To show the Developers options screen do the following:
1. Goto Settings, About and tap the Build number text 7 times.
2. When you have tapped 3 times you will be given a countdown of taps until you
become a developer.
3. Once you are told you are now a developer you can go back to the Settings
Screen and can see Developer options.
4. You can now go into Developer options and enable usb debugging.
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera (P2P) mode.
To do this open the notification area [top left] with the device connected via usb,
click where it says 'connected as' and change from MTP to PTP.
------------------------------------------------------------------------------------
Q. How to get into your Download Mode
1. Unplug your usb cable if you have one plugged in
2. Keep holding the Volume Down, Home and Power buttons until you see a warning
screen [about 10 seconds]
3. Press the Volume Up button to boot the phone into Download Mode
------------------------------------------------------------------------------------
Q. How to get into Recovery
1. Unplug your usb cable if you have one plugged in
2. Keep holding the Volume Up, Home and Power buttons until you see a green android
man on the scree [about 15-20 seconds]
Q. I tried to enter the code for the pro version but it says the code is incorrect
1. Make sure the code entered is for the correct Toolkit being used.
2. You need to start the Toolkit with the toolkit.exe file when activating so the
settings can be initialised or the code will not be accepted.
3. Make sure you enter the code correctly as the characters are case sensitive.

**if needed*

GREAT. Thank you for providing your tools to our device mskip
powered by Fingerbite Chocolate™

mskip said:
**if needed*
Click to expand...
Click to collapse
I think most of your pics are damaged...can they be repaired?
Sent from my GT-I9500

anu.cool said:
I think most of your pics are damaged...can they be repaired?
Sent from my GT-I9500
Click to expand...
Click to collapse
Sorry im not sure what you mean.
Mark.

mskip said:
Sorry im not sure what you mean.
Mark.
Click to expand...
Click to collapse
tapatalk shows images in first post are damaged ie can't be seen,broken links maybe.
Can they be fixed?
Sent from my GT-I9500

Thanks mskip, yours utilities are the best.
Enviado do meu GT-I9500

knox
if you do root the S4 with this process, active knox?

kraiioL said:
if you do root the S4 with this process, active knox?
Click to expand...
Click to collapse
bump bump:highfive:

kraiioL said:
if you do root the S4 with this process, active knox?
Click to expand...
Click to collapse
If you flash any custom image on a device with KNOX present then yes you will trip the knox flag.
Mark.

mskip said:
If you flash any custom image on a device with KNOX present then yes you will trip the knox flag.
Mark.
Click to expand...
Click to collapse
Works to root 4.4.2 official?
I need the phone in download mode? Recovery mode?
[SGS4]

KNOX S4
whether this method changes the root flag knox with 0x0 to 0x1

by far the best application i have used for a long time... whether rooting the phone or reverting to stock firmware. great piece of work.

i keep getting error when i try to install custom recovery ive tried both my wifes phone and mineim on 4.4.2

I installed the toolkit to do an ADB backup of Samsung Galaxy S4 M919 with Android 4.2.2 (already rooted)
PC system in Win7/32
After installing the Samsung USB drivers, and plugging in the USB cable, I can see that the ADB drivers are loaded. In Device Manager, The "SAMSUNG Android ADB Interface" is shown under Android Phone. Running "adb device" from the command line shows that the SGS4 is recognized.
However, the prompt about pairing with the PC never occurs. I thought maybe I had done it before, so I didn't worry about it since ADB was working. I selected ADB Backup in the toolkit using the -all -apk -system -noshared options.
The Full Backup function appeared on the phone, and I selected "Back Up My Data". The phone had not rebooted - the backup app is on top of the regular phone function and the status bar is still showing at the top. I did not enter a password.
Below the password field various apps are displayed one by one.
However the progress is unbelievably slow. After 30 minutes, only at 200 MB file is present in the backup folder. It hasn't increased in size for over 10 minutes.
This is the first time I've tried an ADB backup with the SGS4, but my previous phone would back up several Gbytes in about 15 minutes.
Is this process just very slow on the SGS4, or is something wrong?

so the Att SGH 1337 model is not supported by this toolkit?

thank you for this wonderful tool, makes things easier

HI Mark,
I just want to say THANK YOU for all of your toolkits!
I bought the OG N7 AND N7 2013 versions, and I (finally) have a SGS4 on the way and will be buying this toolkit as well when my i9500 arrives.
You have saved me a ton of time of trouble, and I plan on following your work down the road as well.
Thank you for making these available to us, and please keep up the great work... :highfive:

(Tutorial) Root SM-903VL By Downgrading to 4.4 (Simplified, No Converting Needed)

hello i have put together a bunch of information about getting root on the S5 (SM-S903VL) though i cannot take all the credit.
I simply pulled info from different threads into one to make things less confusing and more simplified. so be sure to thank @parrotgeek1 on how to convert and @mortj19 for providing the link to the "testing" firmware. The downside to this is you will be downgraded to 4.4 kitkat from 6.0 marshmallow. Also your phone might read it as SM-G900V instead of SM-903VL in "About Phone" This will enable people to root the S5 that some want so badly and to have a pretty stable system (im still checking everything over myself) so lets begin...
NOTE: I am not responsible for any damage or data loss that may occur. proceed at your own risk.
I have swapped the system.img and cache.img that was originally in this thread to the G900V for better compatibility and most importantly to allow WIFI TETHER
WARNING: YOU WILL BE ABLE TO USE WIFI TETHER BUT IN STRAIGHT TALKS POLICIES, IT STATES THAT TETHERING IS PROHIBITED AND IF CAUGHT, STRAIGHT TALK CAN TERMINATE YOUR ACCOUNT WITHOUT NOTICE OR WARNING. YOU'VE BEEN WARNED. TETHER AT YOUR OWN RISK.
Known Issues (So Far)
-SHealth crashing consistently (disable it to fix or remove after rooting)
-After reboot, Wifi password is forgotten and needs to be re-entered - since swapping over to G900V, im not sure if this is an issue anymore. need someone to confirm if it does or doesnt since im on a custom rom now and cant.
-mobile data does NOT work until the system and cache are transferred to the device
Fingerprint sensor- has something to do with incorrect test keys. i do not have enough understanding on how to patch this to get it working again. so sorry. if anyone is able to get it working, please post and ill update the thread with the correct changes.
LINKS UPDATED!
Things needed are:
A PC with phones drivers installed
Odin 3.12.3 - https://mega.nz/#F!Ugh2CaRa!YcYsAQy-OG6hW3PPNA9TuQ
System Img. built from G900V - https://mega.nz/#!EkonBKAR!Xp_CCqMKgijpEFA_h0id6yn9NttPwTgArlLTU82rKWs
Cache Img. built from G900V - https://mega.nz/#!glAHmJgS!L4gHDv6y8M4_feSz1cDHqWtsMoeO7wvAj9HwWOzxAVk
sdk-tools - move this folder to the root of your C:/ drive - https://mega.nz/#F!gswwxSiY!Qx2dm6GlfL5vLwD2oQaV7A
4.4 Test firmware - https://forum.xda-developers.com/galaxy-s5/general/downgrade-to-4-4-2-factory-test-t3530449
Towelroot Apk - towelroot.com
kingroot Apk - kingroot.net
external SDCard (make things easier)
NOTE: download everything on a PC to make instructions easier to follow
Step 0: Move system.img and cache.img to the ROOT of your internal storage of your phone and kingroot,towelroot to your SDcard
Step 1: Put phone in download mode by shutting the phone off then turning it back on by holding the volume key up + Home button + power button
Step 2: NOTE:THIS STEP WILL WIPE EVERYTHING ON YOUR PHONE SO BE SURE TO BACKUP! Run Odin.exe and click AP in the program and select the 4.4 test firmware and click start. let it finish and the phone boot into system
step 3: Install kingroot and run it and let it root the device. If it fails just try again (You get a network error if you try to use towelroot at this point.
step 4: open up command prompt on your PC and type the following:
CD C:/sdk-tools
adb shell
su (grant permissons on prompt on your phone)
stop
dd if=/sdcard/cache.img of=/dev/block/platform/msm_sdcc.1/by-name/cache bs=10485760
(give it a minute or two to say its transferred)
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system bs=10485760
(give a minute or two to say its tranferred)
reboot recovery (if it says an error like not found like mine did. just pull the battery out after disconnecting phone from your PC and manually reboot into recovery and it will load some stuff in the backround. after that it will reboot again but BEFORE it does be sure to hold the buttons again to get into recovery)
step 5: go down to factory reset and perform the reset to prevent a bootloop
step 6: reboot into system
step 7: install towelroot and tap "make it rain"
step 8: login to google play store and install supersu
step 9: open supersu and install the binary.
step 10: install root checker from the play store to verify root
its bit of a long process but if you want root bad enough on the SM-903VL like i did. i would say its well worth it. so far i have installed safestrap for the G900V (verizon) and it works.(if you install safestrap, dont forget it requires to have busybox installed) ive tested two roms so far. MOAR rom doesnt boot. only get a black screen. acherom works just fine though. (dont try to install twrp recovery or you will get the "take to verizon store error" and have to odin back to stock 903VL and start all over. i assume its from it having a locked bootloader. this is pretty much word for word on how to do this correctly thats why its so long but its quite simple. I have just took a few steps out so you dont have to worry or bother about doing any converting.
any problems give a post and see if we can resolve it to make this a more stable system
NOTE: IF YOU GET A RANDOM KERNEL PANIC DURING THE PROGRESS OF THIS, JUST DO OVER AGAIN.. SOMETIMES IT WILL GO UNDER PANIC ON THE FIRST TRY AND WILL NEED ODIN BACK TO STOCK.

@bjf189
To fix first 2 issues
In build.prop
ro.securestorage.support=false
Oh and while you're at it
ro.tether.denied=false
You should make a build.prop with those changes already applied and upload it for easier instructions

bjf189 said:
hello i have put together a bunch of information about getting root on the S5 (SM-S903VL) though i cannot take all the credit.
I simply pulled info from different threads into one to make things less confusing and more simplified. so be sure to thank @parrotgeek1 on how to convert and @mortj19 for providing the link to the "testing" firmware....
Click to expand...
Click to collapse
Awesome stuff! Thanks for the credit for the testing firmware, that took awhile to find.

parrotgeek1 said:
@bjf189
To fix first 2 issues
In build.prop
ro.securestorage.support=false
Oh and while you're at it
ro.tether.denied=false
You should make a build.prop with those changes already applied and upload it for easier instructions
Click to expand...
Click to collapse
i will update the build.prop and reupload in a matter of days. its been a busy week for me so i have very little time. one other issue i have found is i cant get the fingerprint sensor/scanner to work. any idea how to fix that? im not sure what files the sensor requires to use it.
right now im seeing if i can find a bypass to use to keep root but be back on marshmallow

bjf189 said:
i will update the build.prop and reupload in a matter of days. its been a busy week for me so i have very little time. one other issue i have found is i cant get the fingerprint sensor/scanner to work. any idea how to fix that? im not sure what files the sensor requires to use it.
right now im seeing if i can find a bypass to use to keep root but be back on marshmallow
Click to expand...
Click to collapse
1) unfortunately I don't think that's possible, mismatched rom fails security check
2) 100% impossible due to dm verity

parrotgeek1 said:
1) unfortunately I don't think that's possible, mismatched rom fails security check
2) 100% impossible due to dm verity
Click to expand...
Click to collapse
well your right that i cant bring it back to marshmallow. its even being a pain to extract correctly. so your saying that the fingerprint sensor cant be fixed?

I'm having trouble pulling apart the build prop. I have it extracted so I have it to edit and it has been corrected for tethering and that Wi-Fi error but I can't get it to inject back into the file or firmware of the downgrade. 7zip says error

================================================== =================
The Steps I used to go from SM-903VL MM 6.01 to ROOTED SM-S902L KK 4.4.2
================================================== =================
download the official stable version of ODIN 3.12.3 here:http://samsungodin.com/
download the SM-903vl 6.01 stock image ( in case you need to recover / de-brick ) from page 1
Download & downgrade to the factory test 4.4.2 SM-903vl Firmware from page 1 ( Using ODIN , use "AP" button for the .MD5 file )
root using KINGROOT PC version (windows) - INTERNET REQUIRED for KR to work! here:https://kingroot.net/thank-you-for-d...t-for-windows/
*** NOTE: May take a couple or few attempts to root phone. Exit & run KR again if no root.
(Also, try restoring 6.01 firmware, then try to downgrade again & root)
after ROOT successful, manually install stericson version of busybox: here:*https://www.apk4fun.com/apk/6139/
( copy apk to internal SD via PC mtp & install it from MY FILES )
download the s902L 4.4.2 TFN firmware here:https://samsung-firmware.org/model/SM-S902L/*( FREE, but have to register to DL )
(Windows use simg2imghttps://github.com/KinglyWayne/simg2img_win)
(Linux use a package manager to install simg2img)
Unzip the S902L KitKat Files to a folder, and then
use simg2img on cache.img.ext4 also ( *** temporarily rename it to system.ext4.img)
put the ext4 files in the same folder as simg2img.exe
open terminal or CMD prompt, then type:
simg2img system.img.ext4 system.img
simg2img cache.img.ext4 cache.img*
then copy the system.img & cache.img to your INTERNAL SD card
next run these commands from linux terminal ( or Windows CMD prompt ):
adb shell
su
stop
dd if=/sdcard/cache.img of=/dev/block/platform/msm_sdcc.1/by-name/cache bs=10485760
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system bs=10485760
**** Then exit the adb shell by typing exit (enter) 2 times to get back to command prompt, then
adb reboot recovery
let recovery do its thing, then when it reboots and is on the samsung boot screen
quickly do another
adb reboot recovery
then do a wipe data (Factory reset), then reboot
( I downloaded these APKS manually on PC, & copied to SD. WIFI will work on phone, but not DATA until you fix APN! )
install TR.APK ( Towelroot 3.0 ) and ROOT your phonehttps://towelroot.com/tr.apk
install stericson busybox-free ( found it here:https://www.apk4fun.com/apk/6139/*)
install PhoneInfo.apk and FIX the APN for LTE data to work ( menu, secret codes, lte stealth mode )
install XPOSED INSTALLER 2.6.1 ( KITKAT ) if you want xposed - google it
install SElinuxToggle.apk from XDA to be able to change SElinux to Permissive - google it
install SuperSu from playstore, upgrade binary & disable knox - Normal Mode ( as theres no custom recovery )
install ViperFX & ViperXHifi ( The BEST AUDIO MOD by far! Nothing can touch this! ) - google it
install a file manager with root capabilites: Rename the ContextProvider.apk in /system/priv-app/ folder to ContextProvider.apk.old
you should have ROOTED s902L normal KK 4.4.2 rom with XPOSED & Viper4Android Audio
Everything should work, EXCEPT for the WIFI TETHER & FINGERPRINT SCANNER
*** I DO NOT TAKE CREDIT FOR THIS... I PUT ALL THE PIECES TOGETHER FROM DIFFERENT SOURCES ***
But, did want to share the steps used in more detail to do this! Thanks XDA Members!!!!
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
Fix APN with PhoneInfo.apk
http://apk.center/down_Phone-INFO-Samsung_apkcenter.html
Source of info was found here: http://www.reddit.com/r/galaxys5/comments/3uniq8/looking_for_lollipop_firmware_files_for_model/
Open Phone Info app Click on Secret Codes Click launch STEALTHMODE Click LTE APN SETTINGS Hit the + to add APN
Enter the follow information;
Name=Verizon Internet APN=TRACFONE.VZWENTP Proxy=(LEAVE BLANK) Port=(LEAVE BLANK) Username=(LEAVE BLANK) Password=(LEAVE BLANK) Server=(LEAVE BLANK) MMSC=(LEAVE BLANK) Multimedia message proxy=(LEAVE BLANK) Multimedia message port=(LEAVE BLANK) MCC=311 MNC=480 Authorization type=None Click menu in right hand corner and save Select new APN APN type=default,dun Bearer=Unspecified Mobile virtual network operator type=None
Click menu in right corner save. Select new APN reboot phone.
---------- Post added at 02:46 PM ---------- Previous post was at 02:41 PM ----------
Questions:
(1) could we use the sm-g900v 4.4.2 fw instead of the sm-902l? https://samsung-firmware.org/model/SM-G900V/
build G900VVRU1ANE9 can be rooted with TR
(2) would lineage 14.x work via safestrap?
---------- Post added at 02:55 PM ---------- Previous post was at 02:46 PM ----------
bjf189 said:
I'm having trouble pulling apart the build prop. I have it extracted so I have it to edit and it has been corrected for tethering and that Wi-Fi error but I can't get it to inject back into the file or firmware of the downgrade. 7zip says error
Click to expand...
Click to collapse
i used es note editor as root. set the tether block to false. also did the sql thing to global database with the ",dun" thing.
i always get "hotspot not supported".
did you actislly get it to work???? how?
you could also from playstore download "root essentials". you can edit build.prop & csc data.
another tool in playstore, CSC FEATURES, not only allows editing of csc, but you can add missing features too. it has a huge categorized list built in!
please let me know if your mobile hotspot works and you can connect to it. i really need this!!!! thanks.
oh, if your trying to flash the csc via odin, and getting 7zip errors. assuming you are windows user (i am linux), try IZARC and use it to make your .tar file. http://izarc.org

fingerprint scanner.
*#0*#dialer code , sensors test , fingerprint version: null
build.prop shows:
samsung/kltetfnvzw/kltetfnvzw:4.4.2/KOT49H/S902LUDUAOD3:user/release-keys
maybe we need release-keys from 903vl factory test? can anyone help figure out the FP scanner issue?

DeepPurple72 said:
================================================== =================
The Steps I used to go from SM-903VL MM 6.01 to ROOTED SM-S902L KK 4.4.2
================================================== =================
download the official stable version of ODIN 3.12.3 here:http://samsungodin.com/
download the SM-903vl 6.01 stock image ( in case you need to recover / de-brick ) from page 1
Download & downgrade to the factory test 4.4.2 SM-903vl Firmware from page 1 ( Using ODIN , use "AP" button for the .MD5 file )
root using KINGROOT PC version (windows) - INTERNET REQUIRED for KR to work! here:https://kingroot.net/thank-you-for-d...t-for-windows/
*** NOTE: May take a couple or few attempts to root phone. Exit & run KR again if no root.
(Also, try restoring 6.01 firmware, then try to downgrade again & root)
after ROOT successful, manually install stericson version of busybox: here:*https://www.apk4fun.com/apk/6139/
( copy apk to internal SD via PC mtp & install it from MY FILES )
download the s902L 4.4.2 TFN firmware here:https://samsung-firmware.org/model/SM-S902L/*( FREE, but have to register to DL )
(Windows use simg2imghttps://github.com/KinglyWayne/simg2img_win)
(Linux use a package manager to install simg2img)
Unzip the S902L KitKat Files to a folder, and then
use simg2img on cache.img.ext4 also ( *** temporarily rename it to system.ext4.img)
put the ext4 files in the same folder as simg2img.exe
open terminal or CMD prompt, then type:
simg2img system.img.ext4 system.img
simg2img cache.img.ext4 cache.img*
then copy the system.img & cache.img to your INTERNAL SD card
next run these commands from linux terminal ( or Windows CMD prompt ):
adb shell
su
stop
dd if=/sdcard/cache.img of=/dev/block/platform/msm_sdcc.1/by-name/cache bs=10485760
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system bs=10485760
**** Then exit the adb shell by typing exit (enter) 2 times to get back to command prompt, then
adb reboot recovery
let recovery do its thing, then when it reboots and is on the samsung boot screen
quickly do another
adb reboot recovery
then do a wipe data (Factory reset), then reboot
( I downloaded these APKS manually on PC, & copied to SD. WIFI will work on phone, but not DATA until you fix APN! )
install TR.APK ( Towelroot 3.0 ) and ROOT your phonehttps://towelroot.com/tr.apk
install stericson busybox-free ( found it here:https://www.apk4fun.com/apk/6139/*)
install PhoneInfo.apk and FIX the APN for LTE data to work ( menu, secret codes, lte stealth mode )
install XPOSED INSTALLER 2.6.1 ( KITKAT ) if you want xposed - google it
install SElinuxToggle.apk from XDA to be able to change SElinux to Permissive - google it
install SuperSu from playstore, upgrade binary & disable knox - Normal Mode ( as theres no custom recovery )
install ViperFX & ViperXHifi ( The BEST AUDIO MOD by far! Nothing can touch this! ) - google it
install a file manager with root capabilites: Rename the ContextProvider.apk in /system/priv-app/ folder to ContextProvider.apk.old
you should have ROOTED s902L normal KK 4.4.2 rom with XPOSED & Viper4Android Audio
Everything should work, EXCEPT for the WIFI TETHER & FINGERPRINT SCANNER
*** I DO NOT TAKE CREDIT FOR THIS... I PUT ALL THE PIECES TOGETHER FROM DIFFERENT SOURCES ***
But, did want to share the steps used in more detail to do this! Thanks XDA Members!!!!
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
Fix APN with PhoneInfo.apk
http://apk.center/down_Phone-INFO-Samsung_apkcenter.html
Source of info was found here: http://www.reddit.com/r/galaxys5/comments/3uniq8/looking_for_lollipop_firmware_files_for_model/
Open Phone Info app Click on Secret Codes Click launch STEALTHMODE Click LTE APN SETTINGS Hit the + to add APN
Enter the follow information;
Name=Verizon Internet APN=TRACFONE.VZWENTP Proxy=(LEAVE BLANK) Port=(LEAVE BLANK) Username=(LEAVE BLANK) Password=(LEAVE BLANK) Server=(LEAVE BLANK) MMSC=(LEAVE BLANK) Multimedia message proxy=(LEAVE BLANK) Multimedia message port=(LEAVE BLANK) MCC=311 MNC=480 Authorization type=None Click menu in right hand corner and save Select new APN APN type=default,dun Bearer=Unspecified Mobile virtual network operator type=None
Click menu in right corner save. Select new APN reboot phone.
---------- Post added at 02:46 PM ---------- Previous post was at 02:41 PM ----------
Questions:
(1) could we use the sm-g900v 4.4.2 fw instead of the sm-902l? https://samsung-firmware.org/model/SM-G900V/
build G900VVRU1ANE9 can be rooted with TR
(2) would lineage 14.x work via safestrap?
---------- Post added at 02:55 PM ---------- Previous post was at 02:46 PM ----------
i used es note editor as root. set the tether block to false. also did the sql thing to global database with the ",dun" thing.
i always get "hotspot not supported".
did you actislly get it to work???? how?
you could also from playstore download "root essentials". you can edit build.prop & csc data.
another tool in playstore, CSC FEATURES, not only allows editing of csc, but you can add missing features too. it has a huge categorized list built in!
please let me know if your mobile hotspot works and you can connect to it. i really need this!!!! thanks.
oh, if your trying to flash the csc via odin, and getting 7zip errors. assuming you are windows user (i am linux), try IZARC and use it to make your .tar file. http://izarc.org
Click to expand...
Click to collapse
I kind of gave up on it being I've been real busy lately. If anyone can upload the new system img with the build prop corrections injected to it. I'll gladly upload it to the thread so it's all in one.
As for tethering and such. I just installed safestrap made for the G900V. Then installed acheron rom on slot one but that caused some errors. So I undid that and put it on stock slot after deleting the rom 1 slot. It got rid of the errors and enabled Wi-Fi tether. So that's an option to look into if you'd like. Still can't get finger print sensor to work though. I too think it might be something to do with the test keys but even on the test firmware I believe the finger print sensor didn't work. So I'm not sure if we can use the 6.0 marshmallow keys on 4.4 to fix the sensor or not. I have my doubts on it though

I am very busy also.
I think on the "downgrading to factory test 4.4.2" thread, someone posted the system.img & cache.img for 902l kk. Just use "root essentials" to edit the build.prop file and change the net.tether.block to false. Build.prop does not need to be injected. Its a quick edit using root, and can be edited directly.
As for the G900v kk 4.4.2, i will try and DL it, and make the system/cache img files.
will let you know when they are ready - but someone else will need to test them!
It took so long to get the 902L KK ver setup and all, and its working very good with root / xposed and all. But i am thinking the g900v kk should be more compatible to the 903vl than 902L, given that fcc id says 903vl is a g900v.

900
DeepPurple72 said:
I am very busy also.
I think on the "downgrading to factory test 4.4.2" thread, someone posted the system.img & cache.img for 902l kk. Just use "root essentials" to edit the build.prop file and change the net.tether.block to false. Build.prop does not need to be injected. Its a quick edit using root, and can be edited directly.
As for the G900v kk 4.4.2, i will try and DL it, and make the system/cache img files.
will let you know when they are ready - but someone else will need to test them!
It took so long to get the 902L KK ver setup and all, and its working very good with root / xposed and all. But i am thinking the g900v kk should be more compatible to the 903vl than 902L, given that fcc id says 903vl is a g900v.
Click to expand...
Click to collapse
i still cant get the fingerprint scanner to work even when i pull keys over from the factory test. i did however find a way to be able to get wifi tethering on stock after doing the system and cache switch. its simple. just use the G900V system.img and cache.img files in the G900V firmware and youll have wifi tether.
dont use the G900V firmware on the 903VL using odin. you will get a fail at aboot and with the aboot removed, it fails at the pit file. so thats out the window but you can still merge the system and cache over using your method to have tether though

Running G900V (Verizon) KitKat 4.4.4 STOCK ROM on SM-903VL !!!
Download G900V 4.4.4 Stock Rom HERE: https://www.androidfilehost.com/?fid=23991606952607146
Follow SAME directions as the SM-S902 4.4.2, only use the system/cache IMGs from this ROM instead!
( Yes, TowelRoot Works on this ROM! )
Debloat using a "System App Remover" app from playstore to delete the Verizon crap that you dont need/want.
Working for me on SMART-TALK (Verizon Carrier). Mobile Hotspot Works! (I'm using it now to post this)
I have already used the "PHONEINFO.APK" to do the LTE STEALTH MODE to add the APN for STRAIGHT TALK from previously using the 902L 4.4.2 rom.
I noticed that it does not seem to work on the G900V 4.4.4 - I'd suggest that while you have the SM-903VL FACTORY TEST flashed, trying the PHONEINFO LTE STEALTH MODE in that ROM if you have NO MOBILE DATA.
I also extracted the modem.bin file from the original SM-903VL MM 6.01 ROM's "AP" archive ( after extracting the MD5 files ), created a "tar" of just the modem.bin, and flashed the modem.bin.tar using ODIN AP mode to update the modem (baseband) back to MM 6.01 PH3 , for optimum performance as LTE seemed to be slower using the baseband that the FACTORY TEST flashed. I did not test PHONEINFO in the Factory Test rom - If it does not work and you have no mobile data, then you would have to install the 902L KK 4.4.2 first, root it with TR, then install PHONEINFO to be able to use the LTE STEALTH MODE in order to ADD the proper APN ( tracfone ) for STRAIGHT-TALK 4G/LTE mobile data to work. Then you can simply "dd" the system/cache img's from the G900V KK 4.4.4, reboot, let recovery do its thing and then when it reboots itself, go into recovery again and do the wipe data thing. The APN will not be affected. ENJOY!
FIngerPrint Scanner DOES NOT WORK ( maybe due to being ROOTed / ContextProvider errors - disabled that package )
*** I Believe the FIngerPrint Scanner will not work if the BOOT.IMG ( Kernel ) mismatches the SYSTEM image version, based on alot of googling. Since with a locked bootloader ( Toshiba Emmc ) we cannot flash the G900V boot image as ODIN fails ( due to bootloader locked ).
Also, I am using the modem from original SM-903VL MM 6.01
Performance is EXCELLENT! Running VERY FAST!
Xposed, ViperFX & ViperXifi, Lucky Patcher,etc ALL working. Phone/LTE/MOBILE HOTSPOT too!
Using Nova Launcher for Desktop ( love the 3D cube effects! )
I'm very HAPPY now that this SM-903VL has ROOT, and converted to G900V KitKAt 4.4.4
ITS SO EVIL HOW COMPANIES ARE LOCKING DOWN BOOTLOADERS / HINDERING ROOT!
If this where a PC, and they said you can ONLY install Windows 10 & You CANNOT be an ADMIN, but just a LIMITED USER, either their would be LAWSUITS or END-USERS say "FU" and NOT BUY the product.
Why should smart phones be any different from a PC in that respect?
Removed ALL Verizon apps EXCEPT VZ-NAVIGATOR ( which appears to work using STRAIGHT-TALK )
Also DISABLED/REMOVED the KNOX crap & SECURITY UPDATER too.
This can be done using SYSTEM APP REMOVER/UNINSTALLER, LUCKY PATCHER, etc.
Also using FDROID ( FOSS Software, kinda like the PlayStore app ), I use a nifty app called "autostarts"
to disable alot of apps from starting up at/after boot to save ram and battery.
Also, KNOX WARRANTY bit is still GOOD, doing all this stuff did NOT trip the KNOX WARRANTY!
THANK YOU SO MUCH XDA MEMBERS!!!! Your Posting of information has been extremely helpful!
---------- Post added at 02:37 PM ---------- Previous post was at 01:40 PM ----------
Getting XPOSED SECURITY ALERT CODE 2 errors with some Games/Apps ?
Oh, if you are ROOTED + XPOSED and play games, some games ( like NetMarble games ) detect XPOSED , pop up an error, and wont allow you to play them.
See my post here on how to defeat this ( without uninstalling xposed and without any reboot! )
https://forum.xda-developers.com/xposed/xposed-security-alert-code-2-netmarble-t3400258

Hello, I followed the instructions from the first post which booted, but i had an overlay on my main screen with yellow letters that would only go away if a menu or app was open. i eventually got a modem error of some sort on boot after the dd commands. so i found a zip with four files, AP BL, CP, CSC. This got me back to 6.0.1 and working but back to square one. and it must've updated the recovery part too because now the text colors are different and it has an extra option or two. when i tried to start over again, it failed in odin then i got a blue screen wanting me to connect the phone to quick connect app or something like that. eventually got that worked out and back running again, but any ideas on how i can go about trying this again? also this last post i've been reading, if i'm understanding correctly, i should be able to follow the same directions from the first post, but using the dd commands for the cache and system from the 4.4.4 download in the last post? also the CP file from the stock 903 6.0.1 zip folder i have is the modem file. if i want to use that modem file with 4.4.4 to possibly avoid the boot screen with the modem error do i load it in the AP or CP line in odin?
Sorry, i've rooted a tablet recently which was way less steps, and it's been a couple of years since i've rooted a phone so i'm rusty and still fairly noobish to this lol

GilFPV said:
Hello, I followed the instructions from the first post which booted, but i had an overlay on my main screen with yellow letters that would only go away if a menu or app was open. i eventually got a modem error of some sort on boot after the dd commands. so i found a zip with four files, AP BL, CP, CSC. This got me back to 6.0.1 and working but back to square one. and it must've updated the recovery part too because now the text colors are different and it has an extra option or two. when i tried to start over again, it failed in odin then i got a blue screen wanting me to connect the phone to quick connect app or something like that. eventually got that worked out and back running again, but any ideas on how i can go about trying this again? also this last post i've been reading, if i'm understanding correctly, i should be able to follow the same directions from the first post, but using the dd commands for the cache and system from the 4.4.4 download in the last post? also the CP file from the stock 903 6.0.1 zip folder i have is the modem file. if i want to use that modem file with 4.4.4 to possibly avoid the boot screen with the modem error do i load it in the AP or CP line in odin?
Sorry, i've rooted a tablet recently which was way less steps, and it's been a couple of years since i've rooted a phone so i'm rusty and still fairly noobish to this lol
Click to expand...
Click to collapse
Can you provide your Android version and model number and your baseband version under settings and about device? I will be updating this thread later today with the new fixes in place for those who want WiFi tether fixed. However I Still can't get fingerprint sensor to work correctly.

bjf189 said:
Can you provide your Android version and model number and your baseband version under settings and about device? I will be updating this thread later today with the new fixes in place for those who want WiFi tether fixed. However I Still can't get fingerprint sensor to work correctly.
Click to expand...
Click to collapse
Thank you!! Being able to have wifi tethering would be amazing! Currently using foxfi and pdanet to connect through usb and I get random connection drops.
Version 6.0.1
Model SM-S903VL (Straight talk)
Baseband S903VLUDU5AQA1

GilFPV said:
Hello, I followed the instructions from the first post which booted, but i had an overlay on my main screen with yellow letters that would only go away if a menu or app was open. i eventually got a modem error of some sort on boot after the dd commands. so i found a zip with four files, AP BL, CP, CSC. This got me back to 6.0.1 and working but back to square one. and it must've updated the recovery part too because now the text colors are different and it has an extra option or two. when i tried to start over again, it failed in odin then i got a blue screen wanting me to connect the phone to quick connect app or something like that. eventually got that worked out and back running again, but any ideas on how i can go about trying this again? also this last post i've been reading, if i'm understanding correctly, i should be able to follow the same directions from the first post, but using the dd commands for the cache and system from the 4.4.4 download in the last post? also the CP file from the stock 903 6.0.1 zip folder i have is the modem file. if i want to use that modem file with 4.4.4 to possibly avoid the boot screen with the modem error do i load it in the AP or CP line in odin?
Sorry, i've rooted a tablet recently which was way less steps, and it's been a couple of years since i've rooted a phone so i'm rusty and still fairly noobish to this lol
Click to expand...
Click to collapse
GilFPV said:
Thank you!! Being able to have wifi tethering would be amazing! Currently using foxfi and pdanet to connect through usb and I get random connection drops.
Version 6.0.1
Model SM-S903VL (Straight talk)
Baseband S903VLUDU5AQA1
Click to expand...
Click to collapse
The links have been updated and swapped to the G900V instead of the 902L for better compatibility and enable of WiFi tether. Just follow the guide and you'll have a rooted tetherable device.
As for your situation, your baseband I don't recognize. Where exactly did you pull that basrband from? When you go back to stock 6.0. You should have an ending of PH3 as your baseband. Then after using Odin it'll change to PH1.
Try starting over. Be sure the stock firmware you flash back to stock with has an ending of PH3. If you have trouble finding it. I'll upload the firmware here. After your back to stock. Just follow the guide word for word. Also the yellow wording on your home screen is the testing firmware that you flash that shows you downgraded from 6.0 to 4.4. After you see that yellow letters you are on 4.4. After that you go to the command prompt like in the guide and type in the commands on your pc to push the system and cache images to your phone and it will push out all that testing stuff. When using command prompt and type a command. Be sure to be patient and be sure that it says on your computer screen that it says "transferred in xx.xxx seconds" this means it got pushed to your phone successfully. If you pull the cord or cancel out before that reads on both the system and cache pushing. It won't be fully done and could end up stuck at start up or nothing changes which then you'd need to start all over. So he Patient. Hope this helps

bjf189 said:
The links have been updated and swapped to the G900V instead of the 902L for better compatibility and enable of WiFi tether. Just follow the guide and you'll have a rooted tetherable device.
As for your situation, your baseband I don't recognize. Where exactly did you pull that basrband from? When you go back to stock 6.0. You should have an ending of PH3 as your baseband. Then after using Odin it'll change to PH1.
Try starting over. Be sure the stock firmware you flash back to stock with has an ending of PH3. If you have trouble finding it. I'll upload the firmware here. After your back to stock. Just follow the guide word for word. Also the yellow wording on your home screen is the testing firmware that you flash that shows you downgraded from 6.0 to 4.4. After you see that yellow letters you are on 4.4. After that you go to the command prompt like in the guide and type in the commands on your pc to push the system and cache images to your phone and it will push out all that testing stuff. When using command prompt and type a command. Be sure to be patient and be sure that it says on your computer screen that it says "transferred in xx.xxx seconds" this means it got pushed to your phone successfully. If you pull the cord or cancel out before that reads on both the system and cache pushing. It won't be fully done and could end up stuck at start up or nothing changes which then you'd need to start all over. So he Patient. Hope this helps
Click to expand...
Click to collapse
QA1 was an update.

charliepop said:
QA1 was an update.
Click to expand...
Click to collapse
Well I've always had updates frozen and have been on a custom rom pretty much the whole time I had the s5. Does that updated version root with king root? I doubt it does and probably wasn't a good idea to update if you wanted root.
So new plan. Download the PH3 firmware and try using Odin to downgrade back the PH3 instead of what you have now. If it fails, I fear that Verizon/straight talk might have blocked downgrading. Be sure to let me know your result

I can't remember where i found the "back to stock" folder at, but it included these files which i loaded in odin but it did update once the phone was back up and running and i've yet to be able to get odin to flash anything since.
AP_S903VLUDU4APH3_CL8867563_QB10607737_REV00_user_low_ship_MULTI_CERT.tar
BL_S903VLUDU4APH3_CL8867563_QB10607737_REV00_user_low_ship_MULTI_CERT.tar
CP_S903VLUDU4APH3_CL8867563_QB10607737_REV00_user_low_ship_MULTI_CERT.tar
CSC_TFN_S903VLTFN4APH3_CL8867563_QB10607737_REV00_user_low_ship_MULTI_CERT.tar
also I didn't realize straight talk could shut my service off if they found out i am tethering. not sure if anything is different from the wifi hotspot than pdanet/foxfi which is what i've been using for the past couple of years. it's my only source of internet.

[Stock ROM][Combination][RMM state solution][GUIDE AIO] and many more for M30s

What's currently included in this thread :-
TWRP (With/without magisk)
Installing EdXposed
Root with magisk (not recommended due to bootloops, use twrp with magisk)
RMM state Prenormal solution
Stock and combination firmware and Kernal source Gdrive links
Tools for flashing and downloading latest firmware
Post 2
Hide bootloader unlocked warning message
DeGoogle & debloat M30s and install MicroG
Enable Haptic feedback on m30s (or any other samsung phone)
BACKUP YOUR EFS PARTITION BEFORE DOING ANYTHING​If EFSpartition is corrupted or lost, you would not be able to get calls and wifi and your IMEI will be permanently lost.
There is currently no way of restoring corrupted EFS partition since it is device specific, so flashing stock firmware will also be useless
Here is one guide. follow this or any other that works for you.
Here is another (droid view.com/restore-efs-imei-galaxy-s7/)
OR You can Backup all partitions using twrp (nandroid backup) and store in someplace safe (make sure to tick all partitions including EFS)
This is an excellent guide regarding EFS (thanks to @PlayingPoise). I HIGHLY RECOMMEND READING IT BEFORE PROCEEDING.
TWRP (With/without magisk) (huge thanks to @santhoosh)
Thread
there are two .tar files, flash the one you need
Pro Tip: I would recommend Smalipatcher module to reboot directly into magisk system.
Installing EdXposed
See This for installation video OR This Or This for installation guide.
This, for official website
And This for github!
NOTE: v0.4.6.0_beta from github requires custom magisk otherwise the system wont boot since github hosts alpha versions, so i advice to follow the video tutorial since it has installed the most stable EdXposed
Rooting with Magisk (Currently causing random bootloops since custom Kernal is req., i recommend flashing twrp with magisk)
From magisk official repo and This Link, Both are same, but i just wanted to make AIO thread)
thanks to @santhoosh and @topjohnwu
Unlocking Bootloader
Normally I wouldn’t provide instructions for this, but since things had changed drastically from previous Samsung devices, and there are some caveats, I figure this would be helpful.
* Allow bootloader unlocking in Developer options → OEM unlocking
* Reboot your device to download mode. Either use adb reboot download, or use turn off m30s, press vol+ and vol- simultaneously (while powered off) and connect to pc.
* Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Just when you think the bootloader is unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
* Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
* Enable developer options, and confirm that the OEM unlocking option exists and grayed out! The VaultKeeper service will unleash the bootloader after it confirms that the user has the OEM unlocking option enabled.
* if there is no OEM unlock option, set phone's date to 7+ days and back and now see.
* Your bootloader now accepts unofficial images in download mode.
Instructions
* Download the firmware for your device.
* Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
* Install the latest Magisk Manager
* In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
* Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
* Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
* Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
* Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
* We now want to boot into the stock recovery to factory reset our device.
* Full data wipe is mandatory! Do not skip this step.
* Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the Vol up and power to boot to recovery . Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
* Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
* This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
* The device will automatically reboot for the first time it boots. This is completely normal and done by design.
* After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
* You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded in step 3 and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
* Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
Additional Info
* Magisk actually patches 3 partitions on your device:
vbmeta: replace with empty vbmeta image to disable partition verification
boot: remove the signature of the image to prevent soft bricks
recovery: this is where Magisk is actually installed
* Never, ever try to restore either of the 3 images mentioned back to stock! You can easily brick your device by doing so, and the only way out is to do full Odin restore following with factory reset. Just don’t do it.
* If you want to upgrade your device, never flash the stock AP tar file with the reasons mentioned above. Always pre-patch the firmware before flashing in Odin.
* If you don’t need to patch the full firmware, you can manually create a tar file with at least vbmeta.img, boot.img, and recovery.img to let Magisk Manager patch your images in the proper way.
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery
I would recommend Smalipatcher module to reboot directly into magisk system.
Updates: For each and every updates, either magisk or system update always patch the firmware with magisk and flash using odin(data will not be wiped if HOME_CSC
used instead of CSC)
RMM state Prenormal solution
Flash stock firmware
Boot up WITH sim inserted, CONNECT to internet during setup (or you can connect after setting up, but perform below operations only when connected to internet).
Enable developer options and go to them.
Now connect to internet and go to dev options, now set date 8 days back and check dev options for OEM unlocking
if it's still not there set date to today and again 8 days back and again check.
This worked for me and OEM unlocking was there and RMM state was changed to checking.
(what we are doing is fooling phone to believe that sim was inserted for more than 7 days)
Stock and combination firmware and Kernal source
Below are Gdrive links for Combination firmware for (M307FXXU1ASH9) and (M307FXXU2ASK2) and ROM M307FXXU1ASHI, M307FXXU2ASL2, M307FXXS2ATB3 (FOR INS ONLY, for other regions, use frija or samfirm).
I have also uploaded Kernal source for M307FXXU2ASL2 on gdrive for faster download.
Tools included
The following tools are also included in the shared folder, they are up to date as of FEB 2020, but i have attached links to original threads of xda to give credits and in case they are updated, you can download them from there. (As i said, this is AIO thread to find tools, none of them are my creation)
Frija, Samfirm continued and Samfirm are Tools for downloading Official firmware from samsung servers with high speed (so no to sammobile and other ****ty premium websites)
Frija thanks to @invmini, Github
SamFirm thanks to @zxz0O0, Github
SamFirm_continued, Github
Odin
Patched Odin by @realbbb
Frija not working ? install both vcredist_x00 for your device !
(check your windows settings to know which version to install)
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-m307f) and your CSC : (mine is INS).
(All models on samfrew: https://samfrew.com/model/SM-M307F/).
Thanks to @BK
Other Tools
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer
Samsung firmware naming convention and explanation (Outdated)
SM-M307F - Galaxy M30s Samfrew
Extract Samsung PIT File from Samsung Firmware -> www.droid views.com/extract-samsung-pit-file-from-firmware (remove space b/w "droid" and "views")
NAND Erase Samsung Devices in Odin -> www.droid views.com/nand-erase-odin-samsung-firmware (remove space b/w "droid" and "views")
Latest Odin Downloader: https://odindownloader.com/category/download
Samsung USB Driver: https://samsungusbdriver.com/category/download
Samsung Firmware: https://firmwarefile.com/category/samsung
Links​LINK (Pm me if link is dead. If there is error like "try after some time", make a copy of file to your drive and then download)

Hide bootloader unlocked warning message
See Here
DeGoogle & debloat M30s and install MicroG
Here
Enable Haptic feedback on m30s (or any other samsung phone) (thanks to ak****)
1- download "Settings database Editor" from playstore.
2- scroll to bottom and find "haptic_feedback_enabled" and change it to 1

Just in case

great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )

BK said:
great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )
Click to expand...
Click to collapse
Are you talking about the frija and samfirm part?
I think i took it from some other thread which i cant find now. (maybe s10 or note10 ones)
Edit: Gave credits to you

How to flash Combination firmware?
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.

nobody_nowhere said:
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.
Click to expand...
Click to collapse
it's currently impossible to install a test/debugging firmware without a samsung dev account that work as an authorization to flash combination files.

Sm-m307f/ds
Hi i got OTG update and my phone didnt restart after that, i have been trying to find the right Stock firmware for my Samsung M30S SM-m307F/DS but i couldnt find the right one, can you please help me out with the link of the right firmware for my phone.
Thanks

Watch this video broo...you will get to know how to download all latest updated frimware