[ROOT - ZS570KL] ZenUtil + everything you need to root the Z016D quickly and easily! - Asus ZenFone 3 Deluxe Questions & Answers

ZenUtil was created for use with the Zenfone 3 Deluxe Special Edition ONLY.
Hello everyone my name is Sandman45654. I would like to share a little root utility I put together in my free time over the last couple of weeks. After not having much luck with the root packages/images I found here on XDA and the internet in general I decided to create my own solution! ZenUtil was created specifically for the Zenfone 3 Deluxe Special Edition (SD821) and has been tested on seven different computers. Four physical and three virtual machines. Operating systems from Windows 7 through the latest Windows 10 build have all been tested. Two machines even had fresh Windows installations with no prior ADB driver installations and Wi-Fi set to disabled to ensure drivers were in fact installing and not downloading! This package includes EVERYTHING to get the job done quickly and easily!
Screenshots:
View attachment 4270854 View attachment 4270855 View attachment 4270856
View attachment 4270857 View attachment 4270859 View attachment 4270860
Features:
1. Completely menu driven CMD file! Typing or remembering commands is not required.
2. ZenUtil is able to create a support files (help/uninstaller/log files) dynamically.
3. Install Asus ADB Drivers. Fastboot drivers are also installed but not enabled by default. Instructions below.
4. Install the Asus UnlockTool v1.1 onto your phone.
5. Push the SuperSU 2.82 zip file into \sdcard\ in preparation for rooting.
6. Push just about any file or folder, even over network shares into \sdcard\. Supports drag & drop too!
7. Able to boot TWRP 3.1.1-0 without flashing.
8. Able to boot included stock Asus recovery image (v5.15.44.2562) without flashing. Boots upside down for some reason but works.
9. Reboot into the recovery that is currently installed.
10. Reboot into Fastboot mode.
11. Exit out of Fastboot mode. No more holding for power button for days!
12. Able to flash TWRP 3.1.1-0
13. Flash/restore stock Asus recovery image. It does not boot upside down when flashed.
14. Remove any lock screen PIN/Password/Pattern. Useful after restoring a Nandroid and getting "Incorrect PIN" error.
15. ADB transfers are check and verified as either successful or failed.
16. ADB transfers are also logged with date/timestamps and shown automatically on error.
17. The ADB log file is deleted on each launch to keep it small, clean, and simple.
18. Confirms before any "permanent" actions are completed. (Flash / Pin Removal / Uninstall)
19. Maybe more to come...
ZenUtil will be updated with the latest image files for the foreseeable future regardless.
Included files and versions with notes.
ADB Files = 1.4.2 Minimal (Preferred for logging)
Asus Stock Recovery = Z016_1-WW-5.15.44.2562_recovery.img
Asus UnlockTool v1.1 = UnlockTool-9.0.0.29_ZS570KL_PRO.apk
TWRP = twrp-3.1.1-0-Z016-20170826.img
NO LAG ON BOOT with this version of TWRP!!! I was also able to create, wipe, and restore without the issues of previous versions. Might this be the one?!
Finishing Fastboot driver installation.
Your phone must be connected and in fastboot mode before you are able to install the drivers.
1. Right click on the start button and select "Device Manager" or WinKey+R>devmgmt.msc>enter
2. Right click on "Android" with a yellow ! next to it and select "Update driver".
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of available drivers on my computer"
5. Select "ASUS Android Device" and click next.
6. Select "ASUS Android Bootloader Interface Version: 8.0.0.3 [3/16/2015]" and click next.
7. Click "Yes"
8. Click "Close"
A HUGE thank you goes out to Judago for creating CmdMenuSel!
Downloads:
Download ZenUtil v1.0
Fastboot Help Files (with pics)

hello
I have the ASUS Zenfone 3 Deluxe ZS570KL (Z016S)
but I can not do it ROOT
if it does HELP

alkis68 said:
hello
I have the ASUS Zenfone 3 Deluxe ZS570KL (Z016S)
but I can not do it ROOT
if it does HELP
Click to expand...
Click to collapse
According to the page below that phone has the Snapdragon 820 and not the 821. So there is high likelihood that this would fail. If the included Twrp is compatible across both phones you could install the bootloader unlock tool from Asus website and then finish rooting with Zenutil. I cannot however say for certain that Twrp would be compatible.
https://www.mobosdata.com/asus-zenfone-3-deluxe-z016s#

Any chance of getting this uploaded again, it's no longer available

Related

[Script][Root] Lord AIO Tool - v2.1 - 21/01/14 - The Tool You've Been Searching

This is my first work on xda, I created a tool that can make lots of thing with just a click !
Download Links
Linux
Windows
WARNING!!!
I'm not responsible if you brick your device!!! Do at your own risk!!!
Bootloader Unlocker and Root Tool will VOIDS YOUR WARRANTY!!!
Click to expand...
Click to collapse
Feel free to buy me a coffee, it will be appreciated , click the donate button over there (coffee) http://forum.xda-developers.com/donatetome.php?u=4169130
XDA portal link
Here it is : http://www.xda-developers.com/android/all-in-one-tool-for-motorola-xoom-brings-dual-recovery/
Thanks for the help
How to use
Windows --> Download the ZIP from here: http://sourceforge.net/projects/laiot/files/LAIOT.zip/download. Extract it in any folder you want. Then read the README_FIRST.txt file, it contains further information about what you need to do! Here's the content if you prefer reading in your browser:
PLEASE RUN (as administrator) The "Set_Up.bat" First To make sure all dll's and files are distributed where they need to be in order to launch LAIOTools
The reason for this is because this utility does not require the Android SDK to run and has "several key files" that need to be added to multiple directories within LAIOTools for certain Utilities, commands, and features to work properly! This was setup like this to avoid having to manually copy and past the files as well as to keep the download of this utility as light as possible...
Once Set_Up.bat has completed you will see LordAIOTool.bat in the LAIOT root directory. To use the utility, just double click the LordAIOTools.bat to begin...
(Note: There is a version 2 of the same file slightly modified, that file is mainly the same with a slight difference, it does not check to make sure necessary files are installed in the Tools directory for use with this utility - so please do not start with the LordAIOTool2.bat file. It's purpose is used throughout the utility for navigation purposes as a way to bypass the initial file check in the main LordAIOTool.bat file to keep things moving once you have launched the utility.) ..no harm should come if you accidentally used the 2.bat just that some commands may fail while trying to use it!
If you need to install the Motorola Device drivers install the appropriate windows version 32 bit or 64 bit depending on your system, they are located in the folder labeled Moto_Drivers
Click to expand...
Click to collapse
Linux --> Extract on your ~/ (If you didn't understand - /home/youruserhere), open LAIOT folder, double click "RunThisOnce.sh" select run in terminal, now it's installed, to run it, open a terminal and write LAIOT, it's opened! Please report here the bugs! The Linux version link is here https://downloads.sourceforge.net/project/laiot/LAIOT.tar.gz?r=&ts=1335123218&use_mirror=master , everything from Windows version is included except Boot in Ubuntu, but I will add later, sorry for the long wait for the new update, but it's here!
Click to expand...
Click to collapse
Features
1.Complete Backup Tool
2.Bootloader Unlocker Tool
3.Bootloader Locker Tool
4.Install Recovery
5.Restore Tool
6.Root Tool
7.Unroot Tool
8.App Install
9.Unbrick Xoom Tool
10.Dual Recovery Tool (Only on Linux version)
11.Ubuntu Boot (Based here Thank him as well!!!)
12.ROM Install (Under Development)
13.Stock Install
Click to expand...
Click to collapse
To use Unroot Tool on Xoom and Unbrick Xoom Tool download the official image (for your device) from the following link :
http://developer.motorola.com/products/software/
Click to expand...
Click to collapse
History/Changelog
1st posted as a tool that can backup /sdcard/Android and /sdcard/Gameloft folders on Motorola Xoom, then added Bootloader Unlocker and Root, then added more features
Beta 1
First Release
No script yet
Beta 2
Added a script on zip that can backup your data and unlock bootloader
Fixed Bootloader Unlocker Tool Bug and added some new options
Beta 3
Added root option
Fixed some more bugs
Put some more things and better writing
Beta 4
Added option to Lock Bootloader
Fixed some words wrong
Tried to fix some bugs
Beta 5
Added App Install feature
Added Check Root Feature
Fixed some gramatic errors
Fixed some bugs in Bootloader Unlocker
Fixed some bugs in Root
Fixed some bugs on Lock Bootloader
Beta 6
Renamed to Lord AIO Tool (on Script)
Added new Root option (Super One Click for some devices)
Added DooMLoRD root (For Xperia 2011 devices)
Fixed "Install app" bug
Fixed "Restore folders" bug
Added more compatibility
Fixed more bugs
Arranged better the folder
Beta 7
Added User Data Backup
Improved Backup Tool
Improved Restore Tool
Created an User Data Restore Tool
Moved to Development section
Beta 7.1
Just fixed some minor errors... Sorry didn't notice them
Beta 8
Added Unroot option
Fixed some other minor errors that I didn't notice
Beta 9
Added Unbrick Xoom Feature (Testers needed)
Organized better the folder of the tool (sorry still need to extract on C:/)
Beta 10
Added to X10 Mini Pro forum
Added X10 Mini/Pro and X8 Bootloader Unlocker
Beta 11
Added Dual Recovery Xoom (still developing, not working for now ) (Maybe until Wednesday it's done )
Added X10 Mini/Pro CWM Install
Fixed some problems when trying to use some tools
Beta 11.1
Testing phase of Dual Recovery on Xoom!!!
Reuploaded, must work now
Fixed some minor things...
Beta 12
Fixed some bugs
Really added CWM Install option (working fine)
Messed up with dual recovery... NOT WORKING FOR NOW! DO NOT TRY USING IT!!!
Beta 13
Added Ubuntu Boot
Fixed some things...
Added VNC Install
Added Ubuntu Download
Version 1
Linux Version is out!
Dual-Recovery on Linux version!
Started ROM Install development!
Stock Install on Linux version!
Version 2
Fixed little bug on Dual-Recovery.sh and LordAIOTool.sh scripts
Added BacktrackInstall/Uninstall/Boot script
Started new project... First two scripts are on update, now back to work
Version 2.1
Big Windows Update!
No changes in Linux yet, next version may come with Linux update
Code completely rewritten
Tools description clearer
Better Start-up check
Many thanks to @sidgrafix, my dear friend, who made this Windows update possible.
Click to expand...
Click to collapse
Warning regarding last update!
There are some untested features! Also there are some tools missing! A FAQ was added to the code, and it will be created with users information!
Thanks.
My Special Thanks to:
BPaul (paul-xxx) ---> He was my inspiration since I started thinking about developing... He is my favorite developer ever!
zone23 ---> For helping me when I needed some help
solarnz ---> For making the CWM and root I used here for Xoom
DoomLoRD --->For making the root option I used here for Xperia 2011 devices
shortfuse --->For creating the SuperOneClick I used here too
unrandomsam --->For giving me the idea to backup userdata
My Dad --->For helping me in fixing some problems
unchainedrssr --->For giving Dual Recovery tip
D4 --->For porting CWM to x10 mini pro
tehgeekguy --->For giving me some files
zacthespack --->For modding ubuntu.img to Xoom and creating the ubuntu.sh
faiyyaz --->For fixing a little thing on Ubuntu Script
Backtrack --->For making this amazing Distro and arm compatible!
sidgrafix ---> For rewriting the whole Windows script
undergroundandroid ---> For giving support to my projects
Click to expand...
Click to collapse
Thanks for choosing Lord AIO Tool!!!​
Manual Root Way
STEP 1: Obtaining Required Files
a.) Download the latest version LAIOT for Windows (http://forum.xda-developers.com/showthread.php?t=1468298)
b.) Download and Install the latest version of Motorola USB Drivers from HERE.
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
c. Download http://dl.atftas.us/OEM/Motorola/XOOM/Xoom-Universal-Root.zip2.
STEP 2. Connect the Xoom, Install SD Card, and setup PC
Make sure your Xoom is turned on. Go to settings and click on [developer options]; turn USB debugging ON; turn stay awake ON
Connect it to your PC via USB.
Make sure you have the Xoom drivers installed and that the Xoom mounts on the computer
Place the following files on the root of your SD Card:
Xoom-Universal-Root.zip (downloaded earlier)
Update.zip (from LAIOT Tools Folder)
Install the LAIOT tools folder on c:/LAIOT
Run the LordAIOTool.bat file
STEP 3: Unlock the Bootloader
Copy update.zip from tools folder and Xoom-Universal-Root.zip to external sdcard
Open cmd window on your PC and type the following commands:
cd C:/
cd LAIOT
cd LAIOT
cd CWMInstall
adb reboot bootloader
Your XOOM will reboot into the bootloader (fastboot mode) showing "Starting Fastboot Support Protocol".
Type the following command into the Command Prompt to unlock your bootloader:
fastboot oem unlock
Read the warning and follow the instructions on the Xoom Tablet itself from this point onwards. On the tablet, accept the terms using [VOL -] and [VOL +] keys
[VOL -] then [VOL +] to select
repeat [VOL -] then [VOL +] to select
Once selected, your Xoom will now unlock and format itself, meaning, all data will be cleared and you will go back to a factory reset. and will reboot on its own bringing you to the setup wizard (skip it). (You do want to let it complete the full reboot process this time)
STEP 4: INSTALL ClockworkMod Recovery (CWM)
Make sure you have the SD card installed in the Tablet.
Bring your Xoom back to the fastboot screen by:
hold [POWER] + [VOL +] until it reboots
Place in Fastboot Mode: During the first 2 seconds after the Dual Core screen appears, press [VOL +]
On the computer, type:
fastboot flash recovery CWMTiamat.img
You will get a confirmation message indicating that the flashing is done on both computer and Xoom. Then:
fastboot reboot
Do not let it boot to completion (normal boot) or you will need to repeat this process.
Now on Xoom, apply update.zip and Xoom-Universal-Root.zip from SD Card:
While booting press [VOL -] 3 sec after Motorola Dual-Core screen appears (Android Recovery Screen should appear)
Then press [VOL +] (CWM screen should appear now)
use the [VOL -] & [VOL +] keys to navigate and [POWER]button to select
Select "Apply sdcard update.zip" and then
- select “choose zip from sdcard”
-select “Xoom-Universal-Root.zip”
- Select "Yes"
Select “Install zip from sdcard”
Now Select “+++++Go Back+++++” and then “Reboot system now”
Note: if you are restoring from a rooted image, you should be able to skip these last two installs (update.zip and Xoom-Universal-Root.zip) and go straight to the restore procedure (step 6)
You should be done, but you now need to confirm your root status by:
Download and install “Root Checker Basic” from Google Play and then run the checker. You should get a prompt to “allow superuser”. Click “Allow” and you should get a confirmation that you have root access.
You are complete and now have a rooted Xoom with Nandroid ClockWords Mod installed
STEP 5: Backup image to SD card
Make sure you have the SD card installed in the Tablet.
On your Xoom:
Hold [POWER] + [VOL +] until it reboots
While booting press [VOL -] 3 sec after Motorola Dual-Core screen appears (Android Recovery Screen should appear)
Then press [VOL +] (CWM screen should appear now)
use the [VOL -] & [VOL +] keys to navigate and [POWER]button to select
Select "backup and restore" and then
- select “backup”
-select “Xoom-Universal-Root.zip”
- Select "Yes" and wait while it completes your backup
Now Select “+++++Go Back+++++” and then “Reboot system now”
STEP 6: Restore image from SD card
Make sure you have the SD card with your backup installed in the Tablet.
On your Xoom:
Hold [POWER] + [VOL +] until it reboots
While booting press [VOL -] 3 sec after Motorola Dual-Core screen appears (Android Recovery Screen should appear)
Then press [VOL +] (CWM screen should appear now)
use the [VOL -] & [VOL +] keys to navigate and [POWER]button to select
Select "backup and restore" and then
- select “restore”
-select your desired backup
- Select "Yes" and wait while it completes your restore
Now Select “Reboot system now”
I'm thinking about changing the name, does anyone know another name?
XxLordxX said:
I'm thinking about changing the name, does anyone know another name?
Click to expand...
Click to collapse
You could just call it Xoom Back-up, Unlock & Root (if a root tool is added).
I think that it's great that young people like you are doing work like this. Good luck!
Cool name
Sent from my MZ605 using XDA App
Is this script applicable for Xoom Wifi US model?
is there unroot option?
Hi, I think it is applicable on Wifi US, as it features doesn't have any thing that prevent you... I liked your unroot a good idea , will put on it on next release, the unique problem of the unroot is that it isn't universal, I'm using Tiamat Universal root, so I don't face this incompanility problem there...
Sent from my MZ605 using XDA App
Don't get how this is a full backup.
What about the stuff in userdata ?
(All the script does is adb pull /sdcard/)
Reading everything like that seems unlikely and if it did include everything don't get how the permissions would work. (For the stuff usually in userdata on phones.)
Or does userdata on honeycomb not matter with regards to either permissions or file ownership ?
---------- Post added at 09:47 PM ---------- Previous post was at 09:34 PM ----------
XxLordxX said:
Hi, I think it is applicable on Wifi US, as it features doesn't have any thing that prevent you... I liked your unroot a good idea , will put on it on next release, the unique problem of the unroot is that it isn't universal, I'm using Tiamat Universal root, so I don't face this incompanility problem there...
Sent from my MZ605 using XDA App
Click to expand...
Click to collapse
There is no reason you couldn't do the process in reverse (Splitting the boot.img - doing the opposite to build.prop reflash)
Wouldn't be signed though.
Does the original stay signed if it is backed up with dump_image ?
I didn't put backup for anyother than /sdcard/ because to backup anyother you need root... and I think I maybe add in beta 7 this option... BTW the new thread is on Android Hacking General you can find the link on the start of the post...
Sent from my MZ605 using XDA App
---------- Post added at 09:47 PM ---------- Previous post was at 09:34 PM ----------
[/COLOR]
There is no reason you couldn't do the process in reverse (Splitting the boot.img - doing the opposite to build.prop reflash)
Wouldn't be signed though.
Does the original stay signed if it is backed up with dump_image ?[/QUOTE]
I don't think so, to restore the unroot (as I know) you need a CWM backup before the install of update.zip and/or the official image (including the system)
Sent from my MZ605 using XDA App
Bump
10 chars
Beta 9 coming!!! Now with Unbrick feature!!!
Sent from my MZ605 using XDA App
Beta 9 is up and with Unbrick feature!
Keep up the good work nick!
And also, hope you make this tool works perfectly on our x10mp too.
Or, make it for all devices! FTW!
Goodluck!
leimrey said:
Keep up the good work nick!
And also, hope you make this tool works perfectly on our x10mp too.
Or, make it for all devices! FTW!
Goodluck!
Click to expand...
Click to collapse
Thanks , I'm working on x10 mini pro, but if you knows anyone can help me on testing please ask him/her to help too ... I only have x10 mini pro and xoom, my brother has a Play, but he don't let me test as it will void him warranty
For user mjamocha66 I wasn't able to send you an email and a PM so the answer is here, after unpacking just double click LordAIOTool.bat on LAIOT folder, no more thing is needed
BUMP, thinking about a new feature, someone can help?
Sent from my MZ605 using XDA App
Repart (BlackRose type) Bootloader. Might as well get started on it because it will come to be needed.
Recovery Switch/Flash Script. There will be alternate recoveries that will all have their pros and cons (stability vs. WIP). Likely to be various stages of touch recoveries with multiple beta testing stages for themes, tools, etc. They may not prove to be trustworthy at first but we will all test them anyway.
Since ADB can now be used over wifi, you can look into adding this functionality as well (wireless).
These are just off the top of my head. My friends and wife know I can do this all day. I'll check in on occasion to see how this tool develops.
Keep up the good work.
Ok thanks for the tip
Sent from my MZ605 using XDA App
Beta 10 is coming, with x10 mini pro Unlock Bootloader Unlocker

[TOOLKIT] SKIPSOFT ANDROID TOOLKIT -GNEX SPR- Drivers, Root, Recovery + MORE

GALAXY NEXUS - SUPPORTS ALL AVAILABLE VERSIONS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.4.1 [05th Oct 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]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU, 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).
--------------------------------------------------------------
ChangeLog:
ToolKit v1.4.1 (05th Oct 2015)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)
--------------------------------------------------------------
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' 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 blue 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.
Manual Rooting Instructions for Galaxy Nexus
UPDATES:
VIDEOS:
Frequently Asked Questions:
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. What is FASTBOOT?
Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.
It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.
----------------------------------------------------------------------------
Q. I flashed CWM 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. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
OR you can use the ToolKit to rename the files (root access needed).
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download, install and run the Google Nexus 4 Toolkit.
2. Install adb/fastboot drivers (if you havent already done so)
3. Option 9 to download a Google Factory Image.
4. After it finishes downloading you will be given the option to flash the image to your tablet. Do this.
4. Let the phone reboot, then shut the device down and reenter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
5. Option3, 2 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped. Your tablet will now be back to an out-of-the-box FULLY STOCK state and ready to send back.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton) will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. The ToolKit recognises my tablet in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.
You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.
----------------------------------------------------------------------------
Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?
Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.
This option will NOT require your bootloader to be unlocked first.
You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.
You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.
The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I cannot find Developer options to Enable USB Debugging
With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:
Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
You can now go into Developer options and enable usb debugging.
----------------------------------------------------------------------------
Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect
Make sure the code entered is for the correct Toolkit being used.
You need to make sure you start the Toolkit with the toolkit.exe file when activating and not the tkmain.exe file so the settings can be initialised or the code will not be accepted.
Also make sure you enter the code correctly as the characters are case sensitive.
thnx man!
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Much recomended for all users. Easy and all the options and extras you'll need. Then just flash away..............
dangambino said:
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Click to expand...
Click to collapse
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
mskip said:
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
Click to expand...
Click to collapse
Works for me. Flashed it perm and the first thing i did was do a backup. No issues thus far. About to flash Team Win's to see what its all about. But yeah, its working.
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
Anon9mouz said:
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
Click to expand...
Click to collapse
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
adb-toolkit shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh-old
Click to expand...
Click to collapse
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.
Skip I just sent you a message regarding the radio pull CMD
mskip said:
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.
Click to expand...
Click to collapse
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Anon9mouz said:
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Click to expand...
Click to collapse
I think people just prefer using fastboot I know I certainly do.
Mark.
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
LAYGO said:
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
Click to expand...
Click to collapse
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
mskip said:
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
Click to expand...
Click to collapse
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
LAYGO said:
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
Click to expand...
Click to collapse
Plus one on no sd
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Will be doing this when I get home from work! I was glad I picked my GNex up yesterday...it was the only one my store received! So I was quite happy...can't wait for more support on the sprint side.
I couldn't wait, I rooted after lunch. Getting Swype installed, first thing, EVERY time. I needs my Swype!
Then to get some apps on there. Connection sucks at work though.
Can someone please pull the radio for the sprint galaxy nexus
I did a n00b mistake and restored a google factory image for VZW on my Sprint Galaxy Nexus...
Any help would be greatly appreciated!!!
I may have spoke so soon. I'm getting error 7 assert fail when flashing a twrp recovery zip. Is that an issue with the recovery on the toolkit or the zip. I flashed a teerom and kernel with no issues though.....

[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - NEXUS 10 - Drivers, Root, Recovery + MORE

NEXUS 10 - 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 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
* 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, 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).
--------------------------------------------------------------
ChangeLog:
ToolKit v1.4.1 (05th Oct 2015)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)
--------------------------------------------------------------
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' 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 blue 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.
Google Nexus 10 Frequently Asked Questions
UPDATES:
Frequently Asked Questions:
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. What is FASTBOOT?
Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.
It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.
----------------------------------------------------------------------------
Q. I flashed CWM 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. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
OR you can use the ToolKit to rename the files (root access needed).
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download, install and run the Google Nexus 4 Toolkit.
2. Install adb/fastboot drivers (if you havent already done so)
3. Option 9 to download a Google Factory Image.
4. After it finishes downloading you will be given the option to flash the image to your tablet. Do this.
4. Let the phone reboot, then shut the device down and reenter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
5. Option3, 2 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped. Your tablet will now be back to an out-of-the-box FULLY STOCK state and ready to send back.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton) will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. The ToolKit recognises my tablet in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.
You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.
----------------------------------------------------------------------------
Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?
Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.
This option will NOT require your bootloader to be unlocked first.
You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.
You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.
The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I cannot find Developer options to Enable USB Debugging
With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:
Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
You can now go into Developer options and enable usb debugging.
----------------------------------------------------------------------------
Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect
Make sure the code entered is for the correct Toolkit being used.
You need to make sure you start the Toolkit with the toolkit.exe file when activating and not the tkmain.exe file so the settings can be initialised or the code will not be accepted.
Also make sure you enter the code correctly as the characters are case sensitive.
Like a BOSS!
Can someone with a Nexus 10 tell me if it has a download mode since it is by Samsung, similar to the Galaxy Nexus?
If it has one you would get to it by shutting down the device, then holding volume down and long pressing the power button.
Just need to know if Odin support needs adding to the Toolkit.
Mark.
mskip said:
Can someone with a Nexus 10 tell me if it has a download mode since it is by Samsung, similar to the Galaxy Nexus?
If it has one you would get to it by shutting down the device, then holding volume down and long pressing the power button.
Just need to know if Odin support needs adding to the Toolkit.
Mark.
Click to expand...
Click to collapse
Yes it does have it. Says "Downloading. Do Not Remove Target"
Hope that helps! If you need help testing it I'm available to test it for a few hours.
My N10 device is:
- Unlocked
- Rooted
- Stock ROM/Kernel
If that makes a difference.
Happy to help test as well if you still need any testers.
Will it be possible to root using this utility without unlocking the bootloader?
rpz3.14 said:
Will it be possible to root using this utility without unlocking the bootloader?
Click to expand...
Click to collapse
No it wont. Its not possible to unlock the Nexus 10 without unlocking the bootloader as you can only boot/flash images with the boobloader unlocked. You can quite easily relock the bootloader though so its not really a big deal.
Mark.
mskip said:
No it wont. Its not possible to unlock the Nexus 10 without unlocking the bootloader as you can only boot/flash images with the boobloader unlocked. You can quite easily relock the bootloader though so its not really a big deal.
Mark.
Click to expand...
Click to collapse
Okay. I know that flashing unsigned images is a way to get root. With other devices I've used, there are other methods to get root, typically through an exploit. I wasn't sure how this method achieved it, so I appreciate the clarification.
rpz3.14 said:
Okay. I know that flashing unsigned images is a way to get root. With other devices I've used, there are other methods to get root, typically through an exploit. I wasn't sure how this method achieved it, so I appreciate the clarification.
Click to expand...
Click to collapse
I think the last known exploit was patched by google with 4.0.2. The 2 easiest methods of rooting are adb root by booting an insecure boot image and pushing the files or by flashing/booting custom recovery and flashing a root zip file. Both methods are included in the Toolkit.
Mark.
Happy to help you test if you are still needing help. Mine is still fresh out of the box a few hours ago.
rsohne said:
Happy to help you test if you are still needing help. Mine is still fresh out of the box a few hours ago.
Click to expand...
Click to collapse
Do you know how to install the adb/fastboot drivers manually via the device manager on your pc? I need to know the driver ids so I can enter them in the toolkit. I have the driver pack from 1wayjonny but dont have the device and dont know which ids to add.
Mark.
mskip said:
Do you know how to install the adb/fastboot drivers manually via the device manager on your pc? I need to know the driver ids so I can enter them in the toolkit. I have the driver pack from 1wayjonny but dont have the device and dont know which ids to add.
Mark.
Click to expand...
Click to collapse
Is this what you need or would it be something else?
Atmazzz said:
Is this what you need or would it be something else?
Click to expand...
Click to collapse
Thanks for confirming, I have OCD and would to separate this in my driver as well. had it as generic and it works perfect but would like to change the name that is reported to Windows.
mskip let me know about your confirmation to this.
Thank you mskip! Been looking for a toolkit like this thats supported by Windows for 3 days now. Was just about the try the Linux toolkit but im not familiar with linux. Will be gladly awaiting the release of this toolkit. Is it still expected to be released tonight? Would really like to get my N10 unlocked and rooted as soon as possible, but don't really want to use the manual way. I love your toolkits, been using them for my S3 and N7.
Ahhhhhhh.. I was crossing every extremity hoping that you'd be putting out an N10 toolkit mskip, but didn't want to harass you and ask in case it delayed it
Cheers!
Love the Galaxy Nexus toolkit, can't wait to use this one on my N10.
Sent from my Nexus 10 using xda app-developers app
awesome, just got my nexus 10 so just gona wait for this to root it
Finishing off this morning and adding custom recovery choice to the root routines. As soon as its ready I will send a message here to see if anyone can give it a test so if someone is available in about 2 hours that will be great. Sorry it wasnt finished last night I think I fell asleep at the desk while sorting the driver installer out lol.
Mark.

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

NEXUS 5 - SUPPORTS ALL VERSIONS UP TO LATEST ANDROID 6.0.1 BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into 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' 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 blue 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:
Frequently Asked Questions:
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. What is FASTBOOT?
Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.
It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.
----------------------------------------------------------------------------
Q. I flashed CWM 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. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
OR you can use the ToolKit to rename the files (root access needed).
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download, install and run the Google Nexus 4 Toolkit.
2. Install adb/fastboot drivers (if you havent already done so)
3. Option 9 to download a Google Factory Image.
4. After it finishes downloading you will be given the option to flash the image to your tablet. Do this.
4. Let the phone reboot, then shut the device down and reenter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
5. Option3, 2 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped. Your tablet will now be back to an out-of-the-box FULLY STOCK state and ready to send back.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton) will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. The ToolKit recognises my tablet in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.
You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.
----------------------------------------------------------------------------
Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?
Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.
This option will NOT require your bootloader to be unlocked first.
You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.
You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.
The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I cannot find Developer options to Enable USB Debugging
With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:
Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
You can now go into Developer options and enable usb debugging.
----------------------------------------------------------------------------
Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect
Make sure the code entered is for the correct Toolkit being used.
You need to make sure you start the Toolkit with the toolkit.exe file when activating and not the tkmain.exe file so the settings can be initialised or the code will not be accepted.
Also make sure you enter the code correctly as the characters are case sensitive.
finally, I was waiting for this.
Sent from my Nexus 5
Yup!! Best toolkit is here! Got donated versions for N4; N7 and SG3mini!!!
Enviado desde mi Nexus 5 mediante Tapatalk
oh yes! the toolkit of all toolkits
Great news. The best toolkit out there. No offense to others.
Sent from my Nexus 5 using Tapatalk
Oh nice, i'm waiting for your toolkit
me too waiting for your toolkit
About time. (Joking) best toolkit for the nexus 5.
Sent from my Nexus 5 using XDA Premium 4 mobile app
ballaz said:
About time. (Joking) best toolkit for the nexus 5.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry ... download ? hello
pialletti said:
sorry ... download ? hello
Click to expand...
Click to collapse
From 1st post
"Being released today. Needed to create thread to add for Toolkit support.
Mark."
so we'll have to wait for Mark
mskip. No nexus forum is complete without his toolkit!
Sent from my Nexus 5 using xda app-developers app
Perfect!!
Can't wait...
Toolkit packed up just doing some final tests to make sure device specific files are correct and procedures work. Should be ready for release in an hour.
This Unified Android Toolkit is phase 1 and will replace ALL my other Nexus Toolkits to support 6 Nexus devices as well as a basic Android Toolkit which can be used by ANY Android device.
Phase 2 is to add my Samsung device Toolkits so all 12 devices (so far) are supported in a modular format.
More explanation on release
Thanks for your patience.
Mark.
Cant wait used this for my Gnex. Makes life so much easier.
Awesome to see. I was a fan of these on my galaxy nexus and Nexus 7 (2012)
Sorry to double post here but I was wondering, if I donate, do I need to donate for every device or if I donate with the all in one I get one donation code that works on all of them?
Great job Mark.
Sent from my Nexus 10 using Tapatalk

[Root] Junsun Android 5.1 Rear View Mirror (A930/A931) Tutorial

Hello all XDA Developers and site visitors,
I recently picked up a Junsun A931 Rear View Mirror on AliExpress and didn't see any forums on it. So, I decided to write my own about how I managed to gain root and install Magisk. Links to all the files will be included.
This works for Junsun's A930/A931 with Android 5.1. The process will probably work for other Rear view Mirrors with MTK chips, you will need to have access to the boot.img and scatter file for your device.
**Disclaimer: Proceed at your own risk! Although this worked for me without issues, there is always a chance of bricking your devices/making your device unusable. I am not responsible for your device(s).
Instructions:
1. Install MTK Drivers provided.
**I only have the ones for Windows. Mac/Linux, I couldn't find any MTK drivers for you.
**If you have trouble installing drivers, try turning off "signed drivers" in Windows Recovery.
2. Attach device to computer via USB cable.
3. If computer doesn't recognize device when it's fully booted:
-Go to "Set Up"
-Slide over to "Other" tab
-Scroll down to "Version"
-Click on "Version" until it brings up a menu (Same principle as Developer Mode, except it pop's up a menu)
-Click on "USB Host"
-Select "USB Device" (the one that has "adb" in the description)
**If this doesn't work, then try switching USB ports on your computer. It only ever works on my USB 3.0 ports.
4. Install Kingoroot on PC.
5. Launch Kingoroot and let it recognize your device, then click "Root."
** This is only a temporary root. It will reset every time you shutdown/restart. If that's what you want, stop here. Otherwise, continue on.
PERMANENT ROOT:
6. Open your choice of ADB on your PC. (I used Minimal ADB and Fastboot)
-Type "adb devices" to see if your devices is recognized and listed.
-Type "adb install [location of magisk.apk on computer]"
**replace "[location of magisk.apk on computer]" with location of magisk.apk (provided in RootPack.zip). This can be done by just dragging the file into adb or you can type the address from Windows Explorer.
-Type "adb push [location of boot.img for device] /sdcard/download"
**replace "[location of boot.img for device]" with location of boot.img for YOUR DEVICE. USING A BOOT.IMG FOR A DIFFERENT DEVICE WILL MOST LIKELY RESULT IN YOUR DEVICE BEING BRICKED!!! That being said, I have provided the software for Junsun A930/A931 for Android 5.1. If you have a different device, you will need the boot.img for it.
-Type "adb install [location of file explorer apk]" or install an file explorer from the Playstore, etc.
**replace "[location of file explorer apk]" with file explorer of your choice. I used ES Explorer.
7. Now open Magisk on the Rear View Mirror. (Make sure you're either connected to WiFi or Data)
**Be sure to grant it SuperUser Permission from Kingo SuperUser.
- Click "Install" next to "Magisk is not installed"
- Click "Install" on propt that pops up
- Choose "Select and patch a file" option.
- Scroll down and click on Es Explorer (or the file explorer you chose)
- Now go into the "download" folder and click the "boot.img"
- Click the option "File way"
**The "Normal Android Way" option kept failing for me.
- Let this complete.
8. Go back into ADB on the PC
- Type 'adb pull "sdcard/download/magisk_patched.img" C:/Downloads'
**You can replace "C:/Downloads" with whatever location you want to pull the file to on your computer.
9. Launch SP Flash Tool on your PC (provided in RootPack.zip)
-Load Scatter File by clicking the "Scatter-loading" button next to "Scatter-loading File" in the "Download" tab.
**This can be found in the firmware that I've provided, IF you have the Junsun A930/A931. If you have a different device, load the scatter file for it, instead.
-Now unclick all the boxes.
-Now click the box for "location" on the "boot" aisle.
-Select the "magisk_patched.img" that we just made from C:/Downloads or wherever you saved yours. Click "Open."
-It should have now have put the location of your "magisk_patched.img" file in the "location" box and the box next to the "boot" aisle should now be selected again (If not, make sure it is. Also, that it is the only one selected)
-Now click on the "Download" button (with the Green Arrow) at the top.
-Hold the home button the Rear View Mirror and click "Restart" (be sure to keep the mirror connect to the computer via USB)
-Now let the bar at the bottom finish.
-When it's done, there will be a pop-up that says "Download OK"
-Your device will restart
10. In your Mirror, launch Magisk Manager.
-Congratulations! The Magisk Installed option should now be green and you should have permaroot! Enjoy!
**You can now uninstall Kingo SuperUser.
Links:
Root Pack: https://drive.google.com/open?id=11poc-Pr30J_aPmhVJktuqZx1H9fkX371
Firmware: https://drive.google.com/open?id=19zUz_piQ6aiO_uGCQTmKpC9ErAR5-4xZ
A BIG THANK YOU TO THE DEVELOPERS AT MAGISK, KINGOROOT, MINIMAL ADB AND FASTBOOT, MTK DRIVERS, SP FLASH TOOL, XDA, AND EVERYONE ElSE WHO ATTRIBUTED TO THIS THROUGH DEVELOPMENT OF PROGRAMS USED! IF THIS WAS HELPFUL, BE SURE TO THANK ALL OF THEM!
great tutorial, really appreciate it
locale?
Thanks
seeing the A930P mt6735 root here, reboot after root language becomes us and timezone becomes China
I think I'm back to the default, but if you change the language, time zone to Japan and then restart it, it will go back to the default again 
Do you need to change settings with build props etc?
otan032 said:
Thanks
seeing the A930P mt6735 root here, reboot after root language becomes us and timezone becomes China
I think I'm back to the default, but if you change the language, time zone to Japan and then restart it, it will go back to the default again
Do you need to change settings with build props etc?
Click to expand...
Click to collapse
Hmm.. could you give me some more information? Did you install Magisk or just use the temporary root with KingoRoot?
You could probably edit the build.prop to get the correct results by changing the "en" to "jp" for Japanese (or the whatever region). However, I'm not sure why yours is resetting to default after reboot? Mine always retains the settings after restarting. So if you could give me a little more information, I'll see if I can figure out what's the problem.
Great write up! Thank you.
I ended up picking a diff model Junsun /w 2gb RAM and am having issues with the USB port:
aliexpress : /item/32844242296.html
It won't recognize any USB devices, so assuming the drivers are missing or it's disabled permanently somehow. This unit is not powered thru USB port, there are separate 12v +/- to hardwire in. I've tried multiple USB cables as well.
I tried USB sticks for storage, but my actual intent is to hook up a USB DAB+ antenna like I'm using on another vehicle's Android
HeadUnit:
aliexpress: item/33003465623.html?spm=a2g0s.9042311.0.0.5ad74c4dUcy6j9
I just need basic USB drivers and 5V output on the USB port, any ideas on how to get this working or add drivers onto the existing ROM etc.?
Thanks!
iamrance.asa said:
Hello all XDA Developers and site visitors,
I recently picked up a Junsun A931 Rear View Mirror on AliExpress and didn't see any forums on it. So, I decided to write my own about how I managed to gain root and install Magisk. Links to all the files will be included.
This works for Junsun's A930/A931 with Android 5.1. The process will probably work for other Rear view Mirrors with MTK chips, you will need to have access to the boot.img and scatter file for your device.
**Disclaimer: Proceed at your own risk! Although this worked for me without issues, there is always a chance of bricking your devices/making your device unusable. I am not responsible for your device(s).
Instructions:
1. Install MTK Drivers provided.
**I only have the ones for Windows. Mac/Linux, I couldn't find any MTK drivers for you.
**If you have trouble installing drivers, try turning off "signed drivers" in Windows Recovery.
2. Attach device to computer via USB cable.
3. If computer doesn't recognize device when it's fully booted:
-Go to "Set Up"
-Slide over to "Other" tab
-Scroll down to "Version"
-Click on "Version" until it brings up a menu (Same principle as Developer Mode, except it pop's up a menu)
-Click on "USB Host"
-Select "USB Device" (the one that has "adb" in the description)
**If this doesn't work, then try switching USB ports on your computer. It only ever works on my USB 3.0 ports.
4. Install Kingoroot on PC.
5. Launch Kingoroot and let it recognize your device, then click "Root."
** This is only a temporary root. It will reset every time you shutdown/restart. If that's what you want, stop here. Otherwise, continue on.
PERMANENT ROOT:
6. Open your choice of ADB on your PC. (I used Minimal ADB and Fastboot)
-Type "adb devices" to see if your devices is recognized and listed.
-Type "adb install [location of magisk.apk on computer]"
**replace "[location of magisk.apk on computer]" with location of magisk.apk (provided in RootPack.zip). This can be done by just dragging the file into adb or you can type the address from Windows Explorer.
-Type "adb push [location of boot.img for device] /sdcard/download"
**replace "[location of boot.img for device]" with location of boot.img for YOUR DEVICE. USING A BOOT.IMG FOR A DIFFERENT DEVICE WILL MOST LIKELY RESULT IN YOUR DEVICE BEING BRICKED!!! That being said, I have provided the software for Junsun A930/A931 for Android 5.1. If you have a different device, you will need the boot.img for it.
-Type "adb install [location of file explorer apk]" or install an file explorer from the Playstore, etc.
**replace "[location of file explorer apk]" with file explorer of your choice. I used ES Explorer.
7. Now open Magisk on the Rear View Mirror. (Make sure you're either connected to WiFi or Data)
**Be sure to grant it SuperUser Permission from Kingo SuperUser.
- Click "Install" next to "Magisk is not installed"
- Click "Install" on propt that pops up
- Choose "Select and patch a file" option.
- Scroll down and click on Es Explorer (or the file explorer you chose)
- Now go into the "download" folder and click the "boot.img"
- Click the option "File way"
**The "Normal Android Way" option kept failing for me.
- Let this complete.
8. Go back into ADB on the PC
- Type 'adb pull "sdcard/download/magisk_patched.img" C:/Downloads'
**You can replace "C:/Downloads" with whatever location you want to pull the file to on your computer.
9. Launch SP Flash Tool on your PC (provided in RootPack.zip)
-Load Scatter File by clicking the "Scatter-loading" button next to "Scatter-loading File" in the "Download" tab.
**This can be found in the firmware that I've provided, IF you have the Junsun A930/A931. If you have a different device, load the scatter file for it, instead.
-Now unclick all the boxes.
-Now click the box for "location" on the "boot" aisle.
-Select the "magisk_patched.img" that we just made from C:/Downloads or wherever you saved yours. Click "Open."
-It should have now have put the location of your "magisk_patched.img" file in the "location" box and the box next to the "boot" aisle should now be selected again (If not, make sure it is. Also, that it is the only one selected)
-Now click on the "Download" button (with the Green Arrow) at the top.
-Hold the home button the Rear View Mirror and click "Restart" (be sure to keep the mirror connect to the computer via USB)
-Now let the bar at the bottom finish.
-When it's done, there will be a pop-up that says "Download OK"
-Your device will restart
10. In your Mirror, launch Magisk Manager.
-Congratulations! The Magisk Installed option should now be green and you should have permaroot! Enjoy!
**You can now uninstall Kingo SuperUser.
Links:
**I am unable to add links due to how new my account is. For the files as of now, search "[Root] Junsun Android 5.1 Rear View Mirror A930/A931 " on YouTube and all the links are in the description. I will update here as soon as time allows.
A BIG THANK YOU TO THE DEVELOPERS AT MAGISK, KINGOROOT, MINIMAL ADB AND FASTBOOT, MTK DRIVERS, SP FLASH TOOL, XDA, AND EVERYONE ElSE WHO ATTRIBUTED TO THIS THROUGH DEVELOPMENT OF PROGRAMS USED! IF THIS WAS HELPFUL, BE SURE TO THANK ALL OF THEM!
Click to expand...
Click to collapse
Also, just adding more info to my post above.
I've tried contacting Junsun directly and thru AliExpress, they weren't helpful and just advised this feature isn't supported.
Apparently the USB port can be used for flashing firmware, but no other information.
rochbaz said:
Great write up! Thank you.
I ended up picking a diff model Junsun /w 2gb RAM and am having issues with the USB port:
aliexpress : /item/32844242296.html
It won't recognize any USB devices, so assuming the drivers are missing or it's disabled permanently somehow. This unit is not powered thru USB port, there are separate 12v +/- to hardwire in. I've tried multiple USB cables as well.
I tried USB sticks for storage, but my actual intent is to hook up a USB DAB+ antenna like I'm using on another vehicle's Android
HeadUnit:
aliexpress: item/33003465623.html?spm=a2g0s.9042311.0.0.5ad74c4dUcy6j9
I just need basic USB drivers and 5V output on the USB port, any ideas on how to get this working or add drivers onto the existing ROM etc.?
Thanks!
Click to expand...
Click to collapse
So MTK usually doesn't recognize in Windows the traditional way. You'll need a MTK program or the ADB/Fastboot. Since I don't have this model, I have no way to test it but I would look around the settings to see if there are some extra settings menus like developer mode. In the A930, they have extra menu by clicking the "version" and tapping it multiple times (not Android's but Junsun's custom one).
The driver's that I provide here: https://drive.google.com/file/d/11poc-Pr30J_aPmhVJktuqZx1H9fkX371/view?usp=drivesdk
Should work for your model since it uses the same processor. It should be able to recognize it on start but if it doesn't recognize it when it boots up then there's probably something in settings that will enable it to. It will probably be hidden since it's most likely only for developers who were working on the rom.
Hello I've just rooted my junsun A930 alps-1.6.91 with Dr. Fone root, it showed device as ASUS A10 but rooted no problem and so far seems permanent..
Monkandi said:
Hello I've just rooted my junsun A930 alps-1.6.91 with Dr. Fone root, it showed device as ASUS A10 but rooted no problem and so far seems permanent..
Click to expand...
Click to collapse
Thanks ! It works! I try many times with Kingoroot, but allways fail. My mirror is recognized as MediaTek FX. It is android 5 . Is there any options to upgrade it to newest Android version?
Hello I'm looking for upgrade or custom rom myself, if I find anything I will let you know, but we're already in the best place XDA for it to happen... Good luck
I ask on Junsun Official Store and their answer: "Our equipment cannot upgrade the system. The system is fixed in the device..." So , no solution from official.
Monkandi said:
Hello I'm looking for upgrade or custom rom myself, if I find anything I will let you know, but we're already in the best place XDA for it to happen... Good luck
Click to expand...
Click to collapse
It depends on if anyone will spend the time to build an update rom or port for that device. If you send your device info, someone might end up working on it for you
nejcov said:
I ask on Junsun Official Store and their answer: "Our equipment cannot upgrade the system. The system is fixed in the device..." So , no solution from official.
Click to expand...
Click to collapse
I doubt it will ever have the support for the most current Android version. Most devices like this don't receive updates from official channels and the product isn't popular enough for most developers to have it.
updating fail due to power failed
I am using 4G Junsun A930 model DVR (1GB RAM) I have lost my framework "alps.l1.mp3.v2.95_t98_v2.1.10" I try to flash "full_E08_KM_4G_9.35_WJ_EN_1.6.91" but failed. any possibility to flash my dvr or get "alps.l1.mp3.v2.95_t98_v2.1.10" framework
ajish110 said:
I am using 4G Junsun A930 model DVR (1GB RAM) I have lost my framework "alps.l1.mp3.v2.95_t98_v2.1.10" I try to flash "full_E08_KM_4G_9.35_WJ_EN_1.6.91" but failed. any possibility to flash my dvr or get "alps.l1.mp3.v2.95_t98_v2.1.10" framework
Click to expand...
Click to collapse
Contact them and ask for the firmware for your device. They will most likely send you it. Flash it instead.
Then follow the steps I outlined but using the firmware they sent you instead. That is if you want root.
I requested but they are not respond
---------- Post added at 10:22 AM ---------- Previous post was at 10:10 AM ----------
Orginal firmware ony we can flash in mtk mt6753 chipset? No other solution? I try miracle tool it shows mt 6753 then try to read boot8 after tool auto shutdown
Do you have a picture of the back of your device?
I don't know of any other tools/methods. There's some other programs for MTK development but they won't be much help in this case. You'll need to get the stock firmware back before anything. There's no programs to find suitable software nor is there a cross-reference. There is also no custom roms for these devices. Thus, why root and Magisk integration is such a positive.
drive.google.com/file/d/1Q9v9S_F3OXGp5h-ekh_yAdtJAk246ukY/view?usp=drivesdk
---------- Post added at 11:34 AM ---------- Previous post was at 11:33 AM ----------
drive.google.com/file/d/1Q0Jsw5QbNm2NRsE9vPAr1nXd8_7s_dja/view?usp=drivesdk
There was no access so I requested it
Ok now added

Categories

Resources