[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

Status
Not open for further replies.

mauronofrio

Recognized Developer
Jun 29, 2012
4,358
13,446
263
24
Castellana Grotte
toolaio.tk
Hello everyone, today I present my new creation: we are talking about a tool that allows you to do many things , from the bootloader to flash the factory image , comfortably. Now you're probably asking: but there are already other tools available , why use it? I 'll explain it: this tool currently supports 13 devices of different companies and all the controls have been tailored to each device .

TOOL ALL IN ONE



ADVANCED OPTIONS



FUNCTIONS

Install Drivers
Unlock Bootloader
Lock Bootloader
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Reboot Phone
Update the Tool to last version
Delete downloaded files

DEVICE LIST

Oneplus 3T (Stock firmware not found for now)
Oneplus 3
Oneplus Two
Oneplus One
Oneplus X (Stock Firmware not found for now)
ZUK Z2 PRO (Stock firmware and recoveries not found for now)
ZUK Z2 (Stock firmware and recoveries not found for now)
ZUK Z1
Nexus 4
Nexus 5
Nexus 5X
Nexus 6
Nexus 6P

NOTE
I could not test all the controls, because they are really a lot, I did some tests and everything seems to work. I added a button "Delete File " in the case when downloading some files you have problems, you can delete the corrupted files directly from the tool instead of going to look for it manually.

Before using the tool, make sure that you have turned the oem unlocking, usb debugging and you reboot your device in Fastboot-Bootloader mode.

If you flash a Factory Image, all your data will be erased.

Use "Lock" only when you're certain that the Stock ROM functions properly.

If you have any problems during installation then first try to update the Microsoft Net freamwork to latest version:
https://www.microsoft.com/it-it/download/details.aspx?id=30653

HOW TO INSTALL

Download .zip file;
Extract all its contents into a folder;
Click on setup.exe;
Click on "Install";
Waiting for the end of the process;
Enjoy your tool :D

UPDATE
There will be no need to re-download the new tool, but just look for new updates directly from the tool.
In all cases I'll update the link in this thread and report it when there are new updates with its changelog. (If you have some problem during the update, press continue)

CHANGELOG
#1.0.0.7
Added official OPT recovery;
Added official ZZ1 recovery;
Solved some bug.

#1.0.0.9
Solved OPT bug on stock firmware;

#1.0.1.2
Add some download links

#1.0.1.3
Add new rom;
Solved some bugfix.

#1.0.1.5
Add OnePlus 3 support;

#1.0.1.6
Add new download links;
Add some new stock roms;
Add restore stock boot logo for ZUK Z1 ( you find it on "Flash stock fimrware").

#1.0.1.9
Add new "Advanced Options", i add a screen with all possible fuctions above;
I have changed some protocol (TWRP and Stock Recovery);
Add Oneplus 3 stock recovery.

#1.0.2.0
Add new "Generic" option to advanced settings (if you want to install a custom recovery or some else on an unsupported device you can try);
I have changed some protocol (Factory image and drivers);
Add Oneplus 3 Stock Faactory Image ( i have not tested it, if you test it please make me a fedback).

#1.0.2.1
Added official OnePlus 3 TWRp recovery;
Added last OnePlus One Factory Image;
Generic Bufix.

#1.0.2.2
Added Zuk z2 and zuk z2 pro.

#1.0.2.3
Added Zuk z2 and zuk z2 pro TWRP recovery;
Added new universal drivers;
General Bugfix.

#1.0.2.4
Added new Fastboot and Adb app (If zuk users have some problem try to unistall the tool and install the last through download link);
New UI;
General Bugfix.

#1.0.2.5
Added OnePlus 3T support;
Added OnePlus 3T TWRP;
General Bugfix.

#1.0.2.6
Added last ZUK Drivers;
Fixed Nexus Factory Image;
Fixed OnePlus Factory Image;
Fixed ZUK Z1 Factory Image;
Added newest Nexus Factory Image;
Added last OnePlus One Factory Image;
Added OnePlus 3 TWRP 3.0.2-1.28 recovery;
Added OnePlus 3T TWRP 3.0.2-0 recovery;
Added OnePlus 3T stock recovery;
General BugFix.

CONTACTS
If you think it necessary to add new features or other recovery or other Factory Image or you want to add a new device support please comments or send me a private message or send me an email to [email protected] (If you want to add support for additional device, please send me the link to download important files (recovery,factory image, ... ) or links to guides on the device(unlock bootloader) or anything that may serve me).

DOWNLOAD

TOOL ALL IN ONE
( Alternative Link )

DONATE LINK

If you want to support the project please consider making a donation, thanks.



DONATORS
- Alberto Petten�: 2.00 �
- Oliver E. : 3.50 �
- Tunde Alabi: 10.00 $
- Giovanni MacCelli: 5.00 �
- Cristian Godnik: 5.00 �
- Luca Milkovitsch: 5.00 �
- Nicol� Rossini: 2.00 �
- Luigi Pedrini: 1.00 �
- Oscar Davi: 5.00 �
- Claudio Orititi: 2.50 �
- James Goldsbury: 3.00 $
- Abel Varela Carou: 2.00 �
- Juan Carlos Cuevas Barreira: 5.00 �
- scooterofficina: 1.00 �
- Paul Moore: 3.00 GPB
- Mattia Colle: 1.00 �
- Maryan Komar: 2.00 �
- Luigi Ardizzone: 1.00 �
- Maximo76: 10.00 �
- Lo�c Payol: 13.37 �
- Antonio Rateni: 2.00 �
- Matteo Verzella: 0.50 �
- Lukas Heddendorp: 2.00 �
- Scott Dare: 5.00 �
- Leonardo F. : 3.00 �
- Andrea Tassotti: 5.00 �
- Stefano Franceschini: 1.00 �
- ??????? ???????: 1.00 �
- Stian Domben Bardsen: 20.00 �
- Kevin Dang: 2.00 $
- David Lebrun: 5.00 �
- James Hise: 15.00 �
- Daniele Barbana: 0.40 �
- Christophe Van B. : 2.50 �
- Robert M�ller: 10.00 �
- Johannes Fleischmann: 5.00 �
- Marco Rigoni: 10.00 �
- Pasquale Rivieccio: 2.00 �
- Jorge Toledo: 5.00 �
- ionel firuti: 10.00 �
- Argel Thulin: 2.00 �
- Tim Altmann: 1.00 �
- Christoph Hackl: 2.00 �
- Joel Vazquez: 10.00 $
- Tommaso Tautonico: 1.00 �
- Fabio Vannoni: 4.50 �
- Willy Andresen: 10.00 $
- Antonino Muscarella: 1.00 �
- ??????? ??????: 1.00 ?
- Pietro Brasile: 2.00 �
- Giorgio Frasca: 5.00 �
- Andrea Della Verde: 1.00 �
- RAFAL SZALKA: 2.00 GPB
- marco da silva: 2.00 �
- Jose Rodriguez Martinez Z: 1.00 �
- Francesco Rizzo: 1.00 �
- Lorenzo Stronati: 2.50 �
- Brian Salerno: 15.00 $
- Alois Seelwische: 4.50 �
- K & J Cooper Proper: 5.00 �
- Janis Jemeljanovs: 5.00 �

Really thanks to donators
 
Last edited:

UnnamedFile

Member
Jul 19, 2015
22
4
0
When you have unlocked your bootloader you can may be boot the twrp recovery by fastboot boot twrp_recovery.img and make a backup?
Sorry, this doesn't work - after sending the command to the phone like this:
Code:
# fastboot boot twrp-recovery.img 
downloading 'boot.img'...
OKAY [  0.664s]
booting...
OKAY [  0.368s]
finished. total time: 1.032s
It's just stuck at the fastboot screen. Also, I get a message of a failed MTP mount on my PC, and fastboot devices shows nothing. The phone only reacts to long-pressing the power button and reboots.
 

mauronofrio

Recognized Developer
Jun 29, 2012
4,358
13,446
263
24
Castellana Grotte
toolaio.tk
Sorry, this doesn't work - after sending the command to the phone like this:
Code:
# fastboot boot twrp-recovery.img 
downloading 'boot.img'...
OKAY [  0.664s]
booting...
OKAY [  0.368s]
finished. total time: 1.032s
It's just stuck at the fastboot screen. Also, I get a message of a failed MTP mount on my PC, and fastboot devices shows nothing. The phone only reacts to long-pressing the power button and reboots.
there are another way, via adb, do you want to try?
 

mauronofrio

Recognized Developer
Jun 29, 2012
4,358
13,446
263
24
Castellana Grotte
toolaio.tk
If you tell me how, I'll try.
OK, enable debug usb and oem unlocking on your op3, then connect your phone (the phone must be switched on, not in fastboot-mode) to pc, you open a terminal on the adb-fastboot folder (if you are using linux open a normal terminal), write "adb shell" on windows or "sudo su" in linux and then write "cat proc/mtd" e launch de command. Please report what you see on terminal, then i can give you the right command to extract the recovery
 

UnnamedFile

Member
Jul 19, 2015
22
4
0
OK, enable debug usb and oem unlocking on your op3, then connect your phone (the phone must be switched on, not in fastboot-mode) to pc, you open a terminal on the adb-fastboot folder (if you are using linux open a normal terminal), write "adb shell" on windows or "sudo su" in linux and then write "cat proc/mtd" e launch de command. Please report what you see on terminal, then i can give you the right command to extract the recovery
So you say, I should tell you what the file /proc/mtd on my local PC contains? Somehow I don't understand how this would make sense (besides the fact that I have no such file in my /proc). So I guess that this command should be executed on the phone. However, when I set it up like you described (with USB debugging and OEM unlocking activated, and the phone fully booted up), 'adb devices' shows me nothing, just "List of devices attached" and then no device.

I am by no means a newbie on Linux or computers in general, but not a programmer either. This makes me wonder: Shouldn't the command 'cat /proc/mtd' be executed on the phone itself? I don't know much about adb, but shouldn't "adb shell" do the trick in that case? However, only if adb recognizes my phone, which mine doesn't (despite usb debugging and oem unlocking activated). I'd still like to help, but I'm stuck here, don't know what else to do. Does the phone need to have an unlocked bootloader for simple adb functionality? Because I did relock mine after the last try...

The phone itself mounts a second MTP device called OnePlus Drivers, which contains a file 'adb_config_linux_OSX.sh' with the following content:
Code:
#!/bin/sh
# adb configuration script
PATH=$PATH:/bin:/sbin:/usr/sbin
ANDROID_HOME=~/.android
ANDROID_CONFIG=~/.android/adb_usb.ini
CUST_VID="0x2a70"
if [ -e $ANDROID_HOME ] ; then
   echo "android home is exist!"
else
   echo "creat android home!"
   mkdir $ANDROID_HOME
fi
grep $CUST_VID $ANDROID_CONFIG 2>/dev/null
if [ $? -eq 0 ] ; then
   echo VID $CUST_VID is already configured.. 
   echo "adb should be OK!"
   exit 0
else
   echo config adb ...
   echo $CUST_VID >> $ANDROID_CONFIG
fi
adb kill-server
if [ $? -eq 0 ] ; then
  echo "OK! You can use adb now!"
  exit 0   
else
   echo "try sudo exec adb.."
   sudo adb kill-server
   if [ $? -eq 0 ] ; then
       echo "OK! You can use adb now!"
       exit 0
   else
       echo "Please do command \"adb kill-server\""
   fi
fi
exit 0
I executed it, but that changed nothing.
 

mauronofrio

Recognized Developer
Jun 29, 2012
4,358
13,446
263
24
Castellana Grotte
toolaio.tk
So you say, I should tell you what the file /proc/mtd on my local PC contains? Somehow I don't understand how this would make sense (besides the fact that I have no such file in my /proc). So I guess that this command should be executed on the phone. However, when I set it up like you described (with USB debugging and OEM unlocking activated, and the phone fully booted up), 'adb devices' shows me nothing, just "List of devices attached" and then no device.

I am by no means a newbie on Linux or computers in general, but not a programmer either. This makes me wonder: Shouldn't the command 'cat /proc/mtd' be executed on the phone itself? I don't know much about adb, but shouldn't "adb shell" do the trick in that case? However, only if adb recognizes my phone, which mine doesn't (despite usb debugging and oem unlocking activated). I'd still like to help, but I'm stuck here, don't know what else to do. Does the phone need to have an unlocked bootloader for simple adb functionality? Because I did relock mine after the last try...

The phone itself mounts a second MTP device called OnePlus Drivers, which contains a file 'adb_config_linux_OSX.sh' with the following content:
Code:
#!/bin/sh
# adb configuration script
PATH=$PATH:/bin:/sbin:/usr/sbin
ANDROID_HOME=~/.android
ANDROID_CONFIG=~/.android/adb_usb.ini
CUST_VID="0x2a70"
if [ -e $ANDROID_HOME ] ; then
   echo "android home is exist!"
else
   echo "creat android home!"
   mkdir $ANDROID_HOME
fi
grep $CUST_VID $ANDROID_CONFIG 2>/dev/null
if [ $? -eq 0 ] ; then
   echo VID $CUST_VID is already configured.. 
   echo "adb should be OK!"
   exit 0
else
   echo config adb ...
   echo $CUST_VID >> $ANDROID_CONFIG
fi
adb kill-server
if [ $? -eq 0 ] ; then
  echo "OK! You can use adb now!"
  exit 0   
else
   echo "try sudo exec adb.."
   sudo adb kill-server
   if [ $? -eq 0 ] ; then
       echo "OK! You can use adb now!"
       exit 0
   else
       echo "Please do command \"adb kill-server\""
   fi
fi
exit 0
I executed it, but that changed nothing.
Where can we talk? You have telegram? or Hanoguts? i explain you better
 
Status
Not open for further replies.