NEXUS 9 - SUPPORTS ALL VERSIONS UP TO LATEST ANDROID BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus, Google OnePlus 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 your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Up' (the button nearest to the power button) and 'Power' buttons to boot the phone into FastBoot Mode
How to get into your HBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into HBoot Mode
How to get into Recovery
1. First boot into HBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The recovery menu screen should pop up.
--------------------------------------------------------------
*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 **
** UPDATES **
** VIDEOS **
awesome!!
so this should fix my n9 not working on my win8.1
will have to check this one out. Send me a link and I will test ?
This tool looks amazing!!!!!!! ?
Thank you very much for your HARD WORK!
Sent from my Nexus 9
Happy to help test
hi, have a 32gb white N9 and a win 8.1 and win 7 pc (both 64bit) I can test on if needed? thanks
USBhost said:
awesome!!
so this should fix my n9 not working on my win8.1
Click to expand...
Click to collapse
What isn't working on win8.1? Drivers?
If so I assume you have you looked at the device manager on your pc and made sure drivers are installed properly?
Mark.
Thank you for your effort! :highfive:
I would also love to try! :victory:
THX
I have to pop out for a bit so I will build the Toolkit installer early this afternoon and pm the link to the above users, the module will download after the Nexus 9 is selected and wait for feedback.
Mark.
I am using windows 8.1 x 64 bit and have no issues with drivers etc..
awesome! mskip Toolkit for nexus 9! thank you so much for this!
Been using your toolkit on my Note2,3 and gear!
Love your toolkit, using since galaxy nexus, nexus 7 (2012/2013) and now nexus 9.:thumbup:
Sent from my Nexus 9
USBhost said:
awesome!!
so this should fix my n9 not working on my win8.1
Click to expand...
Click to collapse
mskip said:
What isn't working on win8.1? Drivers?
If so I assume you have you looked at the device manager on your pc and made sure drivers are installed properly?
Mark.
Click to expand...
Click to collapse
These drivers work for Win8/8.1. My Win 8.1/N9 doesn't seem to find the Google Drivers but these work out the box.
http://www.koushikdutta.com/post/universal-adb-driver
prdog1 said:
These drivers work for Win8/8.1. My Win 8.1/N9 doesn't seem to find the Google Drivers but these work out the box.
http://www.koushikdutta.com/post/universal-adb-driver
Click to expand...
Click to collapse
My N9 works fine with Win8.1 too with the universal adb drivers so im not sure what the problem could be..
@USBhost if you are still having problems then I wrote a guide on getting drivers working properly. May be useful to someone: http://www.skipsoft.net/?page_id=1302
Mark.
@mskip I'm willing to be a guinea pig for your N9 toolkit if you need me.
prdog1 said:
These drivers work for Win8/8.1. My Win 8.1/N9 doesn't seem to find the Google Drivers but these work out the box.
http://www.koushikdutta.com/post/universal-adb-driver
Click to expand...
Click to collapse
mskip said:
My N9 works fine with Win8.1 too with the universal adb drivers so im not sure what the problem could be..
@USBhost if you are still having problems then I wrote a guide on getting drivers working properly. May be useful to someone: http://www.skipsoft.net/?page_id=1302
Mark.
Click to expand...
Click to collapse
Ty guys will see if it fixes my problems
USBhost said:
Ty guys will see if it fixes my problems
Click to expand...
Click to collapse
I just rebuilt my Win 8.1 and as soon as installed those drivers it hooked right up. One thing I have seen is if you show some Asus drivers as default delete them on both mtp and ptp setting.They were a Windows update bug. Then enable the Nexus drivers.
So this really includes custom recovery, or is that a feature to come when custom recovery is available?
Edit, nevermind. I overlooked it in the op, but it's as I thought. No custom recovery yet.
I will test your Tool , please send me a Link !
Related
Disclaimer: You are responsible for insuring you keep a backup of your stock recovery!
See Post 7 for the Stock Recovery if you failed to keep a copy for yourself: Click here
Steps for Backing up Stock Recovery:
Code:
fastboot boot /path/to/TWRP.img
The above command will only boot the recovery and will not overwrite your stock recovery making it possible to backup your stock from within TWRP. Now backup your recovery partition from within TWRP. It will be saved on your device and named, recovery.emmc.win. You can rename it to recovery.img to flash it back via usage of fastboot or apply restore within TWRP given the original filename, recovery.emmc.win.
Or within a terminal using dd (aka Data Destroyer);
Code:
dd if=/dev/block/mmcblk0p19 of=/sdcard/stockrecovery.img
TWRP for MT2-L03
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
Installation (PC):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- Download TWRP Recovery
- Boot to your Bootloader
- Plug your device to your PC
- Open Command Window
- Type, then Enter:
Code:
fastboot flash recovery /path/to/TWRP.img
- Also, a video to demonstrate the process of installing TWRP - Credit goes out to @superbass311:
Installation (Device)(More Experienced Users Only!):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- You MUST be rooted!
- Must have Busybox installed or a properly compiled DD binary
- Download TWRP Recovery
- Install a Terminal Emulator from the Play Store
- Type, then Enter:
Code:
su
Followed By:
Code:
dd if=/path/to/TWRP.img of=/dev/block/mmcblk0p19
Download:
- TWRP 2.8.0.0
CONTRIBUTORS
@Modding.MyMind
@xordos
@Shaky156
SOURCES
- Recovery built in a OmniRom 4.4.4 environment using device trees/kernel/dtb
- Stock Kernel
- Stock DTB
- TWRP source from Omnirom
- MT2-L03 Device Configuration Folder - My Github
VERSION INFORMATION
- Status: Stable
- Created 2014-09-22
- Last Updated 2014-09-22
Unlock Your Bootloader:
As we all know, you are not required to be rooted to install TWRP, however, you must unlock the bootloader on your device.
You must email [email protected] asking:
Hello I purchased the Ascend Mate 2 and I would like my bootloader unlock code.
SN: xxxxxxxxxxxxxxxxxxx
IMEI: xxxxxxxxxxxxxxxxxx
Thank you
Click to expand...
Click to collapse
You should get a response within 24 hours. In a situation where 24 hours has passed by than simply be patient or send another email. This is the 1st step to being able to unlock your bootloader (as of now)!
Here is a video to demonstrate to you viewers how you can go about unlocking your bootloader.
- Video credit goes out to @superbass311
*Reserved Again*
I will flash tomorrow. You just made the HAM2 the hottest phone out.
Sent from my MT2L03 using XDA Free mobile app
Thanks to all involved. Re-installed root using TWRP. Now Titanium Backup is working properly.
Flashed just now!
Backing up at the moment.
THANK YOU ALL!!!
How I did it:
Win 8 pc.
Phone booted and usb debugging allowed.
typed "adb.exe reboot bootloader" in cmd terminal
typed "fastboot flash recovery c:\adb\TWRP.img" in cmd terminal
I downloaded zip to my adb directory, also had to rename it too "TRWP.img" as download was "TWRP_MT2-L03_RECOVERY.img"
back up completed in 480 seconds!
Did have to play with TWRP settings as I hadn't used it in a while .
DID I SAY THANK YOU!!!
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is backup of stock recovery, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Thanks iammudd, I think it is confirmed the recovery image is same for all MT2L03 phone.
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Thanks for the great work!
TheGeekRedneck said:
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Click to expand...
Click to collapse
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
xordos said:
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Check your hangouts
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
xordos said:
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Interesting that backup filename is 1970-03-23 but the timestamp is 1979-12-31 23:00 on the phone.
After FTP'ing them onto Win7, their last modified times are 2013-12-31 22:00.
The device configuration folder used to build TWRP is available on my github which you can find the link in the OP under "SOURCES". If you have any knowledge on this stuff then feel free to look it over and throw some patches my way. As it stands, mtp isn't working properly however, mtp has only been known to work for a very small select list of devices. A very small list. As for the time stamp, this isn't much of a concern on my part as it is merely cosmetic. However, the problem with it would most definitely be the result of the actual TWRP source and not the configuration folder (device tree). Feel free to look further in to it if it is bothersome.
Right now, my goal is to see if I can resolve the mtp issue if it happens to be at all plausible since the mtp featured in TWRP is still fairly new and has much more work to be done with it over at TeamWin.
Currently looking in to offmode charging as well. This is merely cosmetic. But would be nice to have.
xordos said:
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is stock, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Click to expand...
Click to collapse
Yes, md5 are the same and fc on Win7 of your/my versions are the same.
4L0M said:
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
Click to expand...
Click to collapse
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
xordos said:
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Click to expand...
Click to collapse
I'd be willing to be a guinea pig for the Mt2-l05 if you need more people.
I second that
Sent from my MT2L03 using XDA Free mobile app
Gir357 said:
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
Click to expand...
Click to collapse
L should be released sometime in October I believe, alongside the new Nexus phone and tablet.
Supposedly the HAM2 is getting an EMUI 3.0 update (KK) in November. I don't know if the US version is included though.
NEXUS 6 - SUPPORTS ALL VERSIONS UP TO LATEST ANDROID BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus, Google, OnePlus 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 your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down', 'Volume Up' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The recovery menu screen should pop up.
--------------------------------------------------------------
*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 **
** Videos **
** FAQ**
Hell yeah! Been waiting for a long time.
edit: how do I upgrade to 1.3.3 from 1.3.2?
edit1: nvm, figured it out
Sent from my Nexus 5 using Tapatalk
AutoUpdate available for Nexus 6 Pro Version
+Added FULL support [including root] for Android 5.0.1 LRX22C
+Download and Flash stock 5.0.1 LRX22C stock image directly from Toolkit
Mark.
Hi Mark.
Really looking forward to trying the toolkit for the first time.
Thanks a bunch, Shaun
Is it just me or is your site down?
Any alternative links?
nexus6 drivers
I have ran the drivers page cant find them im starting to wonder if they wrote a windows 7 64 bit driver set it only connects in camera mode i got as far as unlocking the boot loader then flashing twrp but it seems twrp isnt even Installed now i went to boot loader mode and It had stock recovery it kept giving the error cannot find recovery any ideas? Ive downloaded the new sdk updated my adb.exe and fastboot.exe to no avail cf autoroot cant even find it abd the boot loaders unlocked
Would be nice to have unencrypted boot image file in the toolkit for newbies
aalupatti said:
Would be nice to have unencrypted boot image file in the toolkit for newbies
Click to expand...
Click to collapse
Disabling Forced Encryption is included in the Toolkit in the Rooting section (option 4,8 from the main menu).
Mark.
mskip said:
Disabling Forced Encryption is included in the Toolkit in the Rooting section (option 4,8 from the main menu).
Mark.
Click to expand...
Click to collapse
Great.. missed that
Also FYI : when I activated the motorola nexus 6 module , the application shows the name as HTC nexus 6 V 1.0.2
aalupatti said:
Great.. missed that
Also FYI : when I activated the motorola nexus 6 module , the application shows the name as HTC nexus 6 V 1.0.2
Click to expand...
Click to collapse
Same here, guess just a typo[emoji1]
Sent from my Nexus 6 using Tapatalk
aalupatti said:
Great.. missed that
Also FYI : when I activated the motorola nexus 6 module , the application shows the name as HTC nexus 6 V 1.0.2
Click to expand...
Click to collapse
My stupid mistake lol I made this at the same time as the HTC Nexus 9 module and must have pasted HTC in the wrong place.. Its just a bit of text at the top and nothing is affected by it. Will upload the fixed text in the next update. Thanks for pointing it out
Mark.
How would i going about reverting totally to stock?
Using the toolkit i have:
flashed the stock 5.0 ROM
re-locked the bootloader
I still cannot update to 5.0.1
How to achieve fully to stock?
i keep getting recovery not found when i try to root it.
i've tried root alone, install recovery and all-in-one.
i've never had this problem with my nexus 4 and 5
I'm getting the same thing.
Everything works until I try and root it. It boots into my twrp then just hangs and says it can't find my recovery. Any ideas
Could I have a download link?
That does not work in the home
m.ilbello said:
Could I have a download link?
That does not work in the home
Click to expand...
Click to collapse
looks like the website is down for the moment
{
"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"
}
It has LINUX/UNIX and MAC support!
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.1 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
Download links: Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations: - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here.
Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources: The official and original repository can be found here.
Bug reports/Feature requests: If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.
Licensing: Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff: Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.
Donations: Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
Disclaimer:I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
warfenix said:
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This tool has support only for 4 nexus devices, some features might work, some not, it's all down if the commands that are used by the tool are supported by the other device.
For example all fastboot flashing commands use the command:
Code:
fastboot flash <partition> <file_to_flash>
The same goes for the rest of the commads, I will try to investigate more and see if it's worth it to create a Sam Note 3 package for the tool.
The adb features should work though.
That would be awesome as i run only linux. And cant seem to get odin or heindall to work. Tried multiple times. So if there is something you could cook up. Amazing sauce. Its a att note 3. Either way. This will work great for my n6
Sent from my Nexus 6 using Tapatalk
New update with some fixes that should have been implemented a long time ago...
- Fixed Sideload flashing
- Enabled Recovery rebooting
- Fixed open folder for Stock menu
Wow - Great work on this. Love the fact that it supports mac/nix as well.
Nice! Keep up the good work.
Thank you!
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
bL33d said:
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
Click to expand...
Click to collapse
Yes, you can unlock the bootloader and flash TWRP recovery with it.
Support to Nougat?
ipan gulopuan said:
Support to Nougat?
Click to expand...
Click to collapse
Nougat should work with no problems, I personally used it to flash bootloader, radio and vendor images for Nougat update.
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 6 Recovery
CWM Advanced Edition 6.x
For Huawei Mediapad T1 10
* * * * * * * * * * * * * * * * * * * * * * * * *
{
"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"
}
Code:
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
READ THIS BEFORE DO ANYTHING:
First of all, keep in mind that this recovery is only for the Huawei Mediapad T1 10 variants (T1-A21L and T1-A21W) (codename: hwt1a21l). More details: link..
"How can i know if my device is the right one?":
If you are using EMUI 3.0., go to Settings
About tablet
Check Model number
If your device is T1-A21W (Wi-Fi variant) or T1-A21L (LTE variant) then it's the correct device
So please, if your device is not one of them then this recovery is not for your device.
Click to expand...
Click to collapse
Let me clarify some thing:
Since our device doesn't have any development support (no ROMs, no recoveries, mods, etc) i decided, many months ago, to bring it some development.
You may ask me why i'm posting a completely deprecated custom recovery for our device, and the why is simple:
Since i started trying to bring custom ROMs and recoveries, many months ago, this was one of the successfully ported recoveries i got. The other one, a twrp 2.8.6.0 recovery, it's almost unusable due to problems with the touchscreen response that i couldn't fix. I basically decided after a long time to open a thread for this recovery and share it because my main objetive was to compile a completely TWRP recovery (3.X version) but after a long and unsuccessfull battle i coudn't do it (yet).
So, i decided to share this one while i'm still trying to get the kernel source fully working to port a completely updated TWRP recovery.
Description
"PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI."
Requirements:
-Unlocked bootloader
-One of the devices mentioned before
- A PC+USB cable or compatible aplication+Root to flash the recovery
Changes between the original version
Changed Philz Touch backgound to a more modern and adapted wallpaper.
Features (Careful: Most of them untested)
touch interface:
toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate, SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keys
written from scratch full touch code
basic scroll kinetics for faster scrolling on demand
safe full touch : no wrongly validations while scrolling
when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
adjust scroll sensitivity in a huge palette
adjust menu height in a huge palette
adjust touch accuracy
30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
user custom background png can be selected in addition to 30 solid colors option
show / hide background icon
show / hide bottom virtual buttons
show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
set number of bottom log rows to show
pause on logs mode: no more miss logs during zip installs
auto dim screen after user configurable delay
auto turn off screen after user configurable delay
adjust brightness and turn off screen with a gesture action
show/hide clock and remaining battery %, even during nandroid operations
clock and battery stats now effectively refresh every 5 seconds and during nandroid operations
toggle vibrator on/off on touch
toggle key repeat for volume up/down scrolling when maintained pressed
key repeat also enabled for virtual buttons
set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
capture recovery screen shots with a gesture action (only some devices)
basic theme support
one file to save all settings
backup and restore settings file
backup and restore only GUI settings
reset to default settings option
prompt to restore your settings from a backup when they are wiped by a new ROM install
option to auto restore your settings from a backup without a prompt
all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
toggle menu options are automatically right aligned and menu text left aligned based on device display size
configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager
Note: after scroll, there is a minimal small delay (0.5 sec) to validate on next touch. This is by design and not a bug. It is there to limit erroneous validation while scrolling
true JB 4.2 migration: toggle between /data/media and /data/media/0
Secure recovery lock with passkey
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
exFAT, NTFS and Ext4 support in recovery for external storage through kernel modules for many devices for faster write speed
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
support .android_secure backup/restore from external storage
optional reboot after custom backups/restores
sd-ext support (ext4)
nandroid backups support /preload in backup and restore jobs (custom and stock modes)
nandroid backups support /misc in backup and restore jobs (custom mode)
devs: 5 extra optional partitions supported in nandroid operations by editing recovery.fstab
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore, enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
recreate md5 sum check for your cwm backups for compatibility with stock CWM if you need to revert
cancel nandroid operation with back button
create custom_rom.zip from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path auto-renamed with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo (include modem and efs)
backup/restore EFS in both tar + img formats, now with time tags for both tar and .img
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors backup/restore in stock clockworkmod or TWRP modes
advanced power options menu
detailed build info in About menu
Click to expand...
Click to collapse
What's working/not working
I have been testing it and all the basic functions (backups, instalations, partitions, brightness, touchscreen, etc) is working without problems as some extra features of the recovery, but i didn't test everything. In summary, is a completely functional recovery.
Instalation instrucctions:
By fastboot:
* You should have an unlocked bootloader and adb and fastboot set on your computer properly.
* Download the .img file on your computer and keep it in your adb folder (Windows only)
* Boot to fastboot mode and then connect your phone to the computer. Open a command window/terminal and
type this command:
To flash it to the recovery partition:
Code:
Code:
fastboot flash recovery <filename.img>
~Note: Linux users might want to add "sudo" before the respective commands.
Once finished reboot your device by pressing power and volume up to boot on the recovery.
Download link
Please do not make mirror of the download link, thanks you.
https://www.androidfilehost.com/?fid=745425885120721868
Credits
- eloygomez from HTCMania as the original recovery is from him
- @Koush for having created and maintaining cwm
- CyanogenMod
- @Tallustus from Team Skyfire for his great support over IRC
- @Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
- @Chenglu for his unpacking tools and porting i9505
- kbc-developers for the base semi-touch code and much more
- [email protected] for his great job / support
- @sk8erwitskil for his recovery source, a great place to start learning
- @shoe63 for his help from the start across many devices
- @DooMLoRD for his work and help with Sony
- @[NUT] for his ports to Sony
- @wanam for compiling sensors-free kernels for N71xx/i317M, i9500 and i9505 to fix boot delay for custom kernels, exfat support and much more
- @dougiebee for his work on fixing time on many Qualcom devices
- @ausdim for all the support in developing kernels for i9505
- @dr.ketan for his precious help in porting to the N7000 & N7100 (I don't own one) and all the support in threads
- @Chainfire for his support (stock recovery flash) and all his work for the Android community
- @Phil3759 for the great original thread which is based mine.
- @ThePhantasma for pushing me to open this thread.
Contributors
@mustang_ssc
Created: 04/04/2017
Last update: 04/04/2017
Useful topics:
- Everything Huawei Mediapad T1 10
- How to root our device: Credits to @mann1
Reserved 2
Finally, we have a working recovery for this device! I am glad you share this.
Time to share the good news! :good:
@ThePhantasma for pushing me to open this thread.
Click to expand...
Click to collapse
Thank you.
Thank you for the recovery. Any custom ROMs available??
dilipg98 said:
Thank you for the recovery. Any custom ROMs available??
Click to expand...
Click to collapse
Not yet, i will try to make the stock rom of our device flashable with custom recoveries and after that i may try to port a CM11 or MIUI.
Anyway, that's not my main purpourse, the priority for me is to fix the issues of the kernel source in order to get completely updated recoveries and roms (TWRP 3.X, LineageOS 14.1, Slim7, etc).
Huawei devices are pain in the a$$, i hardly rooted this model t1-a21l, just couple of days ago.
I've tried with most of the models that shares the same CPU and GPU chipset, but no luck till now with TWRP.
I also tried to port the stock recovery of Ascend G7, they share the same Msm8961, but i got the same problem, recovery never starts.
please could someone give me a way to root huawei T1-A21L Androird 4.4.4 ??
Mo3ta9em93 said:
please could someone give me a way to root huawei T1-A21L Androird 4.4.4 ??
Click to expand...
Click to collapse
Here i put a complete topic for it:
https://forum.xda-developers.com/huawei-mediapad/general/root-root-mediapad-t1-10-t1-a21l-t3601136
mann1 said:
Huawei devices are pain in the a$$, i hardly rooted this model t1-a21l, just couple of days ago.
I've tried with most of the models that shares the same CPU and GPU chipset, but no luck till now with TWRP.
I also tried to port the stock recovery of Ascend G7, they share the same Msm8961, but i got the same problem, recovery never starts.
Click to expand...
Click to collapse
Yeah they are quite complicated.
I have tried to port many recoveries from many devices, most of them without luck, but i ported a couple of TWRP 2.8.X recoveries but the problem is that the touchscreen response gets crazy and it's almost unusable.
This recovery and the TWRP one are from the Huawei G620s/cherry, so if you want to try to port some recoveries or roms i would recommend you to try with the ones from that devices because it's the most similar and compatible device i have found for our tablet.
By the way, thanks for the great guide to root our device, i have pinned it to my second post
mustang_ssc said:
Yeah they are quite complicated.
I have tried to port many recoveries from many devices, most of them without luck, but i ported a couple of TWRP 2.8.X recoveries but the problem is that the touchscreen response gets crazy and it's almost unusable.
This recovery and the TWRP one are from the Huawei G620s/cherry, so if you want to try to port some recoveries or roms i would recommend you to try with the ones from that devices because it's the most similar and compatible device i have found for our tablet.
By the way, thanks for the great guide to root our device, i have pinned it to my second post
Click to expand...
Click to collapse
Thank you so much , you've done great too with porting Philz :good:
I've tried a lot to port many twrps, but the most compatible ones were with
Huawei Y550
https://forum.xda-developers.com/android/help/to-root-huawei-y500-t2923318
https://forum.xda-developers.com/android/development/recovery-huawei-ascend-y550-t3294031
porting 2.8.xx gave me the same cranky touch function, but the rest of other functions work when you slowly touch them.
with 3.x.x they start w/o problems but there's no touch function.
the 2.8.xx that i ported is here
===
I guess the problem is in the (device tree blob dtb) file, by unpacking the TWRP y550 img file, i keep the kernel zImage file and i just port stock dtb from the the stock recovery.img of our device to the twrp, to get the cranky touch ported twrp.
===
you have the privilege of being able to compile the twrp from the scratch, so i suggest that you use the y550 source twrp files then readjust the "screen resolution to 800*1280, and reassign the x and y values to be adapted with our device.
===
I've tried to decompile the dtb to readable dts files of both twrp and stock with "device tree compiler" under Linux, but i got error.
===
these were the results of my tries
Ok guys look what i've just got
For now there is still some work to do to have it completely functional because for example the wifi and bluetooth are not working.
Also i finally made the stock rom of our device flashable with my recovery, and i kept it lighter and prerooted. I will open new threads of this roms when everything is ready.
mann1 said:
Thank you so much , you've done great too with porting Philz :good:
I've tried a lot to port many twrps, but the most compatible ones were with
Huawei Y550
https://forum.xda-developers.com/android/help/to-root-huawei-y500-t2923318
https://forum.xda-developers.com/android/development/recovery-huawei-ascend-y550-t3294031
porting 2.8.xx gave me the same cranky touch function, but the rest of other functions work when you slowly touch them.
with 3.x.x they start w/o problems but there's no touch function.
the 2.8.xx that i ported is here
===
I guess the problem is in the (device tree blob dtb) file, by unpacking the TWRP y550 img file, i keep the kernel zImage file and i just port stock dtb from the the stock recovery.img of our device to the twrp, to get the cranky touch ported twrp.
===
you have the privilege of being able to compile the twrp from the scratch, so i suggest that you use the y550 source twrp files then readjust the "screen resolution to 800*1280, and reassign the x and y values to be adapted with our device.
===
I've tried to decompile the dtb to readable dts files of both twrp and stock with "device tree compiler" under Linux, but i got error.
===
these were the results of my tries
Click to expand...
Click to collapse
Looks really interesting, i think i never tried to port anything from that device.
It surprise me to see you got a TWRP 3.X to boot, i never got any one to boot. I will try to port some recoveries from that device but i guess to have the same issues that you have because i think i have been doing the same porting procedure you used.
The problems with the touchscreen may be the dtb file but I'm not sure why it happens because in this recovery is working fine, but I'm sure it will be related to incompatible screen resolution and touchscreen parameters (X and Y axis).
Also I've tried to compile many times a completely updated TWRP recovery directly from the source (and also LineageOS 14.1) but the main problem is the kernel source of our device which it gave me a lot of errors. Casually i think the main problem about this is a missing dts file exclusively for our tablet which indicates the screen parameters, and should be located at arch/arm/boot/dts/qcom/huawei_t110p0_a21l of the kernel source folder. Here you have my GitHub with the device tree, vendor blobs and kernel source of our device in case you find it useful: https://github.com/Mustang-ssc
I might try what you told me about use the y550 source files to see how it goes. If you want anything feel free to contact me
mustang_ssc said:
Here you have my GitHub with the device tree, vendor blobs and kernel source of our device in case you find it useful: https://github.com/Mustang-ssc
Click to expand...
Click to collapse
Hi,
Now I've downloaded the repo and everything to compile twrp, but I'm a lil confused with the repo command
I need to download "Minimal Sources" to compile twrp 5.1, what's the right "repo init..." command to get the sources for our device?
mann1 said:
Hi,
Now I've downloaded the repo and everything to compile twrp, but I'm a lil confused with the repo command
I need to download "Minimal Sources" to compile twrp 5.1, what's the right "repo init..." command to get the sources for our device?
Click to expand...
Click to collapse
I sent you a PM :good:
mustang_ssc said:
Ok guys look what i've just got
For now there is still some work to do to have it completely functional because for example the wifi and bluetooth are not working.
Also i finally made the stock rom of our device flashable with my recovery, and i kept it lighter and prerooted. I will open new threads of this roms when everything is ready.
Click to expand...
Click to collapse
Good stuff, I was hoping that someone was working on the t10.
What's the current status on this port?
PinkOstrich said:
Good stuff, I was hoping that someone was working on the t10.
What's the current status on this port?
Click to expand...
Click to collapse
For now i have 4 different roms: CarbonROM, Pac-Man, CM11 and MIUI8. Obviously (and unfortunately) all of them based on kit kat as i cannot make the kernel source to work.
Now the main problem is that the camera and flash is not working, and a weird bug with the play store that doesn't allow to use it. This last one i don't find it logical as it shouldn't be a rom bug but i have tried many gapps and always getting the same bug (error rh-01)
The camera bug is not very relevant considering that our device is a tablet but if i can fix the play store issue i will probably upload some of the roms while i keep trying to fix the camera and flash.
wifi issues with rooted Mediapad T1 10 T1-A21L
I have access to quiet a few of these tablets (Mediapad T1 10 T1-A21L) - like more than 100 They have been used for various wifi-based demonstrations.
Recently they have begun showing an error message "Unfortunately IntegratedTest has stopped working", like every 2-5 minutes and their storage is filling up with very large logs files (which I also contribute to the IntegratedTest application). I haven't found anyone else with this issue.
The IntegratedTest application is a system app and cannot be removed without root. So I decided to try and follow the "- How to root our device" guide and root one of the devices and remove the application - which succeed. However now the wifi doesn't work.
Is there anyway to "unroot" the device, or get back to the original, while having removed that annoying application? I would very much like to get the wifi back in a working state
The device works fine and I can access recovery mode and the device both responds both via adb and fastboot.
I'm pretty new to rooting and xda in general, so sorry if this is a stupid question or i posted this in the wrong place.
jpihl_ said:
Is there anyway to "unroot" the device, or get back to the original, while having removed that annoying application? I would very much like to get the wifi back in a working state
The device works fine and I can access recovery mode and the device both responds both via adb and fastboot.
I'm pretty new to rooting and xda in general, so sorry if this is a stupid question or i posted this in the wrong place.
Click to expand...
Click to collapse
It's quite easy task, run SuperSu app, and from settings, you'll find the "Full unroot" option, after that go back to the "how to root our device" you've already downloaded 2 boot images, the rooted and the origin stock one, reflash the origin stock one again.
Finally you have to get the stock recovery back to replace the philz, download the stock one from here
Use the stock ROM to have your system back.
mann1 said:
It's quite easy task, run SuperSu app, and from settings, you'll find the "Full unroot" option, after that go back to the "how to root our device" you've already downloaded 2 boot images, the rooted and the origin stock one, reflash the origin stock one again.
Finally you have to get the stock recovery back to replace the philz, download the stock one from here
Use the stock ROM to have your system back.
Click to expand...
Click to collapse
Thanks for your response. I tried to follow your instructions - unfortunately without luck.
What I did:
1. "Full unroot" -> Removed SuperSU App (also su command no longer works - as expected) but still can't enable wifi.
2. Ran fastboot flash boot boot.img -> still can't enable wifi
3. Ran fastboot flash recovery recovery.img -> still can't enable wifi
Which leaves me with "still can't enable wifi" :/
ONEPLUS 5T - WILL SUPPORT ALL VERSIONS UP TO THE LATEST ANDROID BUILDS.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Google, Nexus, OnePlus and Samsung Toolkits and supports many 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
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
* Root any public build automatically
* SkipRoot boot image to AutoRoot (selected builds)
* Sideload root/unroot files via Custom Recovery
* ALLINONE to Unlock, Flash Recovery, Root, Rename the restore file + install Busybox (G,N,O)
* ALLINONE to Flash Recovery, Root, Rename the recovery restore files + install Busybox (Samsung)
* Unlock/Re-Lock your Bootloader (G,N,O)
* Download Google Stock Image files directly to the ToolKit (G,N,O)
* Check md5 of google stock image before flashing
* Flash Google Stock Image (G,N,O)
* Flash any part of a stock firmware image to device [boot, system, recovery, etc.] (G,N,O)
* Download/sideload stock OTA image (G,N,O)
* Install BusyBox binarys on device
* Rename the Recovery Restore File present on Stock Roms (if stock recovery is being restored after flashing custom recovery image)
* Flash Stock Recovery, CWM touch, Philz_touch or TWRP Touch Recovery
* Custom Device Builder can add build support for listed device and add device support for any Samsung device with an unlocked bootloader [included in ULTIMATE but can be added as an extra]
* Pull /data and /system folders, compress to a .tar file and save to your PC
* Auto Update Toolkit at startup (PRO ONLY)
* Auto Update superuser file and custom recovery images to latest versions (PRO ONLY)
* Disable forced encryption on Nexus5X,6,6P and 9
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps
* Install EFS/Partition Backup/Restore app by Wanam
* Create tar with 1-Click for flashing via Odin
* Fix extSdCard write permissions in Android 4.4+
* Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC (selected builds)
* Useful Mods, Fixes and Tools Section
* Extras, Tips and Tricks section (includes guides)
* Backup/Restore your /efs partition (gsm only)
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC ( on builds with insecure image available)
* Mods section to automatically perform certain tasks on your device
* Boot to any recovery without Flashing it (G,N,O)
* Boot or Flash .img Files directly from your PC
* Quick Picks Professional Feature (10 slots)
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your phone
* Pull Files from your phone to your PC
* Set Files Permissions on your device
* Pull and Trim your Radio Image (gsm models only) to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Rip cache.img to zip file in CWM format
* Reboot device to Fastboot Mode or Android in fastboot mode (G,N,O)
* Reboot device to Fastboot Mode, Recovery, Android or Download Mode in adb mode
* Turn Initial Start Screen On/Off for next use
* Sideload any zip file via Custom Recovery
* Basic Toolkit for use with ANY Android device
Key: G-Google N-Nexus O-OnePlus S-Samsung
--------------------------------------------------------------
{
"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.
--------------------------------------------------------------
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 CUSTOM 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).
THE ULTIMATE MODE UNLOCKS THE PRO FEATURES FOR ALL DEVICES WITHOUT HAVING TO BUY THEM SEPARATELY. IT ALSO INCLUDES THE CUSTOM SUPPORT BUILDER TO ADD SUPPORT FOR UNLISTED BUILDS AND CAN EVEN ADD UNLISTED SAMSUNG DEVICE SUPPORT.
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 your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Up' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
*** FAQ ***
First? ?
Have you tested restoring backups? Any "....255" issues?
This is all very interesting and convenient but it's just non-free proprietary software running a few adb and fastboot commands.
** if needed **
cubandanger05 said:
First?
Have you tested restoring backups? Any "....255" issues?
Click to expand...
Click to collapse
I dont own the device if you come across any errors please let me know.
anyone else unable to log into snapchat after rooting?
virtyx said:
anyone else unable to log into snapchat after rooting?
Click to expand...
Click to collapse
Go to majisk, select hide majisk, reboot the device them try to log in.
JD_2322 said:
Go to majisk, select hide majisk, reboot the device them try to log in.
Click to expand...
Click to collapse
im using supersu
virtyx said:
im using supersu
Click to expand...
Click to collapse
Nope snapchat will not work if u have root...hence magisk to hide root and use snapchat...
persieghini said:
Nope snapchat will not work if u have root...hence magisk to hide root and use snapchat...
Click to expand...
Click to collapse
only workaround is to un-root log into snapchat then re-root.
is there a magisk guide somewhere? i dont really know what magisk is.
virtyx said:
only workaround is to un-root log into snapchat then re-root.
is there a magisk guide somewhere? i dont really know what magisk is.
Click to expand...
Click to collapse
Magisk is just a zip file like SuperSU.... You flash it. And it's done.... Let me know if you gonna change to magisk... I'll get the links here
persieghini said:
Magisk is just a zip file like SuperSU.... You flash it. And it's done.... Let me know if you gonna change to magisk... I'll get the links here
Click to expand...
Click to collapse
what are the advantages? or is it the same?
what does magisk support that supersu doesnt?
afaik magisk is more versatile in hiding root, so i can potentially use android pay?
virtyx said:
what are the advantages? or is it the same?
what does magisk support that supersu doesnt?
afaik magisk is more versatile in hiding root, so i can potentially use android pay?
Click to expand...
Click to collapse
It's almost the same with the exception that it can hide root for some apps... And mount systemless for Android pay...
It's way more convinient than SuperSU and I've always used/preferred it over SuperSU...
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
Here u go...v15.3 works like a charm for me right now....I'm running ob stock
Ps: v15.3 also has fingerprint authentication for root access
persieghini said:
It's almost the same with the exception that it can hide root for some apps... And mount systemless for Android pay...
It's way more convinient than SuperSU and I've always used/preferred it over SuperSU...
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
Here u go...v15.3 works like a charm for me right now....I'm running ob stock
Ps: v15.3 also has fingerprint authentication for root access
Click to expand...
Click to collapse
thank you
so if i want to uninstall supersu do i do this within the supersu app then flash stock boot.img and then flash magisk?
virtyx said:
thank you
so if i want to uninstall supersu do i do this within the supersu app then flash stock boot.img and then flash magisk?
Click to expand...
Click to collapse
Yes but I donno if doing it within the app will work or not...flashing unSu zip will definitely work...it had worked for me...rest of the procedure is as u stated..
persieghini said:
Yes but I donno if doing it within the app will work or not...flashing unSu zip will definitely work...it had worked for me...rest of the procedure is as u stated..
Click to expand...
Click to collapse
thank you
where can i find the latest version of unsu.zip?
virtyx said:
thank you
where can i find the latest version of unsu.zip?
Click to expand...
Click to collapse
Take nandroid backup just incase please
All the best..
persieghini said:
Take nandroid backup just incase please
All the best..
Click to expand...
Click to collapse
ty
just one last question
does magisk only affect the boot partition? i just want to know as when i had xposed i noticed a slow down in performance (i guess its because it installs an entire framework)
virtyx said:
ty
just one last question
does magisk only affect the boot partition? i just want to know as when i had xposed i noticed a slow down in performance (i guess its because it installs an entire framework)
Click to expand...
Click to collapse
I've never felt any performance drop after magisk.... So I can vouch for that