[GALAXY S3 MINI TOOLKIT V3 Drivers, Backup, Root, CWM, TWRP, Flash, + MORE

Search This thread

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,067
Norfolk
Sorry it has taken soo long to finish but im proud to release the updated Android Toolkit with added support for Samsung devices and new builds. I still have a few devices to add to the Toolkit [Samsung Galaxy Note 3, Samsung Galaxy Note 8.0, Samsung Galaxy Note 10.1, Samsung Galaxy Camera and Samsung Galaxy Gear] but the Toolkit now supports the following:

Samsung Galaxy Nexus
Nexus 4
Nexus 5
Nexus 7 [2012]
Nexus 7 [2013]
Nexus 10
Samsung Galaxy S3
Samsung Galaxy S3 Mini
Samsung Galaxy S4 [NEW SUPPORTED DEVICE]
Samsung Galaxy Note 2

Supported devices and latest supported builds *HERE*

ChangeLog
Unified Android ToolKit v1.2.4 [Galaxy S3 V8.0.0] 10th March 2014
+Added support for Samsung Galaxy S3, Samsung Galaxy S3 Mini,*Samsung Galaxy S4 and*Samsung Galaxy Note 2
+Updated support for latest builds in all device modules
+Root options support insecure boot and custom recovery methods [all rewritten]
+Added KNOX notification disabler for Samsung modules
+Added Root Checker to check the status of your root/busybox
+Added more help screens to the Information section and added ability to save screen and send to default printer
+Added philz_touch Advanced cwm recovery to Samsung modules [will be added to Nexus modules soon]
+Added option in build selection screen to disable all adb root functions [custom recovery functions available]
+Toolkit will disable insecure boot functions if insecure boot image not available
+Updated Samsung drivers to 1.5.33.0
+Re-wrote most of the code to Change the way lots of functions work [more efficient and more stable]
+Many more changes I can't think of right now

Existing activation codes will still work to update device modules in the Unified Android Toolkit to the pro version of the device you donated to. I am updating the Auto Updates for the newly supported devices but it's probably easier to download the full version and re-activate as it is such a big update.

If you have any feedback please send it to [email protected] for now as emails to [email protected] are still not coming through to me.

Hope you enjoy.

Mark.
 
J

JackoMJ

Guest
Sorry it has taken soo long to finish but im proud to release the updated Android Toolkit with added support for Samsung devices and new builds. I still have a few devices to add to the Toolkit [Samsung Galaxy Note 3, Samsung Galaxy Note 8.0, Samsung Galaxy Note 10.1, Samsung Galaxy Camera and Samsung Galaxy Gear] but the Toolkit now supports the following:

Samsung Galaxy Nexus
Nexus 4
Nexus 5
Nexus 7 [2012]
Nexus 7 [2013]
Nexus 10
Samsung Galaxy S3
Samsung Galaxy S3 Mini
Samsung Galaxy S4 [NEW SUPPORTED DEVICE]
Samsung Galaxy Note 2

Supported devices and latest supported builds *HERE*

ChangeLog
Unified Android ToolKit v1.2.4 [Galaxy S3 V8.0.0] 10th March 2014
+Added support for Samsung Galaxy S3, Samsung Galaxy S3 Mini,*Samsung Galaxy S4 and*Samsung Galaxy Note 2
+Updated support for latest builds in all device modules
+Root options support insecure boot and custom recovery methods [all rewritten]
+Added KNOX notification disabler for Samsung modules
+Added Root Checker to check the status of your root/busybox
+Added more help screens to the Information section and added ability to save screen and send to default printer
+Added philz_touch Advanced cwm recovery to Samsung modules [will be added to Nexus modules soon]
+Added option in build selection screen to disable all adb root functions [custom recovery functions available]
+Toolkit will disable insecure boot functions if insecure boot image not available
+Updated Samsung drivers to 1.5.33.0
+Re-wrote most of the code to Change the way lots of functions work [more efficient and more stable]
+Many more changes I can't think of right now

Existing activation codes will still work to update device modules in the Unified Android Toolkit to the pro version of the device you donated to. I am updating the Auto Updates for the newly supported devices but it's probably easier to download the full version and re-activate as it is such a big update.

If you have any feedback please send it to [email protected] for now as emails to [email protected] are still not coming through to me.

Hope you enjoy.

Mark.



thanks very much for your work Mark, a lot of users are waiting for it :good:
J.
 

soulkyo

Member
May 6, 2012
38
2
Lima
Question

First of all thank you for this great tool. Please, I have a question. I have this information:

GT-I8190L
Android 4.1.2

Baseband I8190LUBAMA2

Kernel Version
3.0.31-876355

Compilation number
JZO54K.I8190LUBAMA2

Which 4.1.2 option should I choose? Up to build AMB1 or Up to build ANA2? Thanks a lot! :)
 

Zakariasz

Senior Member
Jun 27, 2011
136
14
Oxford
I have used first available option and it works ok,now I am not sure what to do because this software finished all it have to do it asked me to switch ODIN off to continue,I did it and it asked me to wait a few minutes to detect my phone again,now is 67 min and it still do nothing,I am safe to disconnect my phone then ?
 

2010radams

Senior Member
Jan 29, 2013
467
197
Workington, Cumbria
Hello, on the screen shots in the opening post it says samsung galaxy s3 mini (2012) is supported. Does this mean 2013 version of galaxy s3 mini isnt supported? Or should I use the 2012 version. Thanks in advance.
 

2010radams

Senior Member
Jan 29, 2013
467
197
Workington, Cumbria
If anyone has (or will) used the Toolkit can you please post some feedback of your experience in this thread so I can tell how its working. Make sure to include your model number so any problems can be narrowed down.

Mark.

Hello, thank you for making the toolkit. It is easy to understand and follow. I have a I8190N. I decided to use the option to install cwm , root and install busybox. Everything seemed to go OK apart from a small problem at the end. I chose twrp and supersu. Everything finished and I booted into recovery fine. But when I reboot the phone it starts up OK but sometimes the 'menu' button and the 'back' button dont work at all? However, they seem to start working again if you reboot the phone 2 or 3 times. Do you know what this problem is? Can it be fixed do you think? Its just I am afraid that one time when the buttons fail, they might not start working again. I have just read your entire thread and no-one else has mentioned this problem. Is it just me who this happens to? I just thought I would let you know so that you are aware of it. Thanks again for this great tool.

Sent from my GT-I8190N using XDA Premium 4 mobile app
 

efaustino84

Senior Member
Feb 13, 2013
773
257
Harare
Hello, thank you for making the toolkit. It is easy to understand and follow. I have a I8190N. I decided to use the option to install cwm , root and install busybox. Everything seemed to go OK apart from a small problem at the end. I chose twrp and supersu. Everything finished and I booted into recovery fine. But when I reboot the phone it starts up OK but sometimes the 'menu' button and the 'back' button dont work at all? However, they seem to start working again if you reboot the phone 2 or 3 times. Do you know what this problem is? Can it be fixed do you think? Its just I am afraid that one time when the buttons fail, they might not start working again. I have just read your entire thread and no-one else has mentioned this problem. Is it just me who this happens to? I just thought I would let you know so that you are aware of it. Thanks again for this great tool.

Sent from my GT-I8190N using XDA Premium 4 mobile app

seems to be a standard problem for some users on certain firmware
the phone takes a while to allow you to use those buttons
 

bgvillones

Member
Sep 11, 2013
14
2
s3 mini MTS Manitoba Canada

Do you have a solution for s3 mini sm-g730w8 model MTS telco service in Manitoba Canada. I couldn't find one here. All I see is from fido, koodo, telus and rogers. So how can I root my s3 mini and install custom rom. Thanks a lot.
 
  • Like
Reactions: samnettt

poussinou69

Senior Member
Sep 4, 2008
361
36
France
Hi,

I followed all the instructions for rooting my GT-I8190N with the all-in-one option but when i reach the step of clicking the PDA/PA button in Odin, this button is not here. Which button do i click ? Someone to help me plz ?
 

DUnderline

Member
May 30, 2013
13
1
As explained in my original thread (http://forum.xda-developers.com/galaxy-s3-mini/help/broken-screen-rooted-lockscreened-t2867424) I'm trying to extract all internal data (mainly photos) from my friends screen-smashed S3 mini.

I'm not sure which Android version it has but I went with 4.1.2 option, aiming to have atleast "4.1" part correct.

From the main menu, I went to Backup - pull selected data - pull all data from interna storage. SkipSoft says the device must be booted into Android mode (which for me is when "adb devices" command doesn't recognize the device, but my PC recognizes it as a removable device with nothing in it). The screen is dead so you can't really know.

Anyways, when I choose "PULL ALL THE INTERNAL STORAGE FOLDER TO YOUR PC" it says "Waiting for adb Mode" and stays like that for, well, 30 mins so far. There's a screencap in the attachments. Is this okay or?

If someone could tell me the path towards the internal camera folder that'd be great - I could simply pull the data directly via adb pull command.
 

Attachments

  • skipsoft.PNG
    skipsoft.PNG
    26.2 KB · Views: 411

Top Liked Posts

  • There are no posts matching your filters.
  • 160
    IMPORTANT: THE S3 MINI MODULE SUPPORTS 4 DIFFERENT S3 MINI VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.

    SUPPORTED MODELS
    GT-I8190 INTERNATIONAL GSM MODEL
    GT-I8190N INTERNATIONAL GSM MODEL WITH NFC
    GT-8190L LATIN/USA GSM MODEL
    GT-8190T LTE MODEL

    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.
    41
    **FAQ**

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

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

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

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

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

    Q. What is ADB Shell?

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

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

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

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

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

    Q. Does flashing a custom image increase my flash counter?

    Any image that is flashed via Odin that has been modified will increase the flash counter that can be viewed in the Download Mode on your device (if booted by holding the Volume Down, Home and Power buttons). You can reset the flash counter using an app by Chainfire called Triangles Away and can find instructions on how to use that in the Downloads section in the Toolkit.

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

    Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?

    Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.

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

    Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back

    There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.

    Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.

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

    Q. My AntiVirus program says the Toolkit files may be harmful

    The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.

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

    Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work

    The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.

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

    Q. I am having trouble getting adb working with the drivers installed

    Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.

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

    Q. I want to send my device back for warranty purposes

    1. Follow the instructions to reset your flash counter with TriangleAway.
    2. Download and flash a Stock Firmware image from the download section.
    3. Boot into Stock Recovery and perform a wipe/factory reset
    .
    Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.

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

    Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit

    I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.
    8
    ***reserved if needed***
    8
    Sorry it has taken soo long to finish but im proud to release the updated Android Toolkit with added support for Samsung devices and new builds. I still have a few devices to add to the Toolkit [Samsung Galaxy Note 3, Samsung Galaxy Note 8.0, Samsung Galaxy Note 10.1, Samsung Galaxy Camera and Samsung Galaxy Gear] but the Toolkit now supports the following:

    Samsung Galaxy Nexus
    Nexus 4
    Nexus 5
    Nexus 7 [2012]
    Nexus 7 [2013]
    Nexus 10
    Samsung Galaxy S3
    Samsung Galaxy S3 Mini
    Samsung Galaxy S4 [NEW SUPPORTED DEVICE]
    Samsung Galaxy Note 2

    Supported devices and latest supported builds *HERE*

    ChangeLog
    Unified Android ToolKit v1.2.4 [Galaxy S3 V8.0.0] 10th March 2014
    +Added support for Samsung Galaxy S3, Samsung Galaxy S3 Mini,*Samsung Galaxy S4 and*Samsung Galaxy Note 2
    +Updated support for latest builds in all device modules
    +Root options support insecure boot and custom recovery methods [all rewritten]
    +Added KNOX notification disabler for Samsung modules
    +Added Root Checker to check the status of your root/busybox
    +Added more help screens to the Information section and added ability to save screen and send to default printer
    +Added philz_touch Advanced cwm recovery to Samsung modules [will be added to Nexus modules soon]
    +Added option in build selection screen to disable all adb root functions [custom recovery functions available]
    +Toolkit will disable insecure boot functions if insecure boot image not available
    +Updated Samsung drivers to 1.5.33.0
    +Re-wrote most of the code to Change the way lots of functions work [more efficient and more stable]
    +Many more changes I can't think of right now

    Existing activation codes will still work to update device modules in the Unified Android Toolkit to the pro version of the device you donated to. I am updating the Auto Updates for the newly supported devices but it's probably easier to download the full version and re-activate as it is such a big update.

    If you have any feedback please send it to [email protected] for now as emails to [email protected] are still not coming through to me.

    Hope you enjoy.

    Mark.
    7
    SAMSUNG GALAXY S3 MINI TOOLKIT RELEASED TO PUBLIC VERSION

    The Toolkit has now been tested to my satisfaction and has been released for download in the 1st post. Please remember that this is the first release and I dont own the device so there may be some textual errors or minor bugs that need ironing out. If you find any problems please post in this thread and they will be fixed as soon as possible. Do not pm me as any pm's that should be posted in a public thread will be ignored.

    Enjoy :)

    Mark.