Minimaladbfastboot1.4.3portable: Update Version. What is Minimum of ADB and Fastboot. ADB stands for Android Debug Bridge and is a tool that allows you to transfer unique commands from Fastboot to your device. Allowing many possibilities such as unlocking your bootloader, rooting the device, updating the standard firmware or even installing.
If you want to root your Android device, install a custom ROM or many other advanced-level techniques then you need to learn how to install ADB and Fastboot on Windows. Here is a guide for getting going on getting the most out of your Android experience as well as a list of the most common mistakes.
Jump to a section
- ADB commands: the most important commands and functions
- ADB errors: common errors and solution
What you should know before you start
What is ADB?
ADB (Android Debug Bridge) consists of a client and server part each communicating with the other. In laymen's terms, it's a communication tool between your smartphone and PC. It is accessed via the command prompt on Windows and is used to send commands to Android from a PC. In other words, ADB is very helpful to the Android community for rooting, flashing new ROMs or simply troubleshooting smartphones.
What is fastboot?
Fastboot is basically a diagnostic tool used to modify the Android file system from a computer when the smartphone is in bootloader mode. The commands are basic, and include, for example, to 'flash' (install) a boot image or a bootloader.
What are drivers?
A driver is a small program that allows an operating system – Windows in this case – to recognize a device and interact with or use it. Each deveice has its own driver, hard drive, mouse, etc. For our smartphones, the system itself uses a driver, the ADB mode and fastboot mode also because the interface is not the same. To summarize, Windows needs a driver for the smartphone, for fastboot and ADB. They are common for all smartphones.
Install ADB drivers on Windows
In our test with a Windows 10 system, we didn’t have to install any additional drivers and could, with any Android smartphone, immediately access the ADB interface. On Windows 7 and earlier OS versions, connecting your smartphone and PC via ADB was somewhat more complex.
On Windows 7, the ADB interface will rarely be recognized. If the appropriate ADB driver is missing, your smartphone and PC will not be able to communicate. Thankfully, the ADB Driver Installer offers a universal solution to the problem. Make your way to this site and click on ADB Driver Installer (9:22 MB). Open the zip file and start the .EXE file contained therein. Confirm the warning regarding user access controls when it appears.
Enable USB debugging
Make your way to Settings, then tap on About phone and press seven times in quick succession on Build number. Go back to the main Settings menu, and you will now see an option for Developer options above About phone. In here, activate USB debugging.
Now click again on Refresh in the ADB Driver Installer, and your device should appear. If it still doesn’t work, you need to change the USB connection mode. Many smartphones are set to use the USB cable only for charging by default. This is intentional, so your files are invisible to the user of the connected computer.
Pull down the notification from the top of the screen of the smartphone while it is connected to your computer. From here, press on the USB connection type. Then select either MTP or PTP. (We found success with both options).
Now, when you click on Refresh, you should see your device in the list of ADB Driver Installers. Click on the line displaying your device, and then click Install. This should install the appropriate ADB drivers for your smartphone.
If you have problems, you need to open the Device Manager, delete existing entries with your smartphone and repeat the installation.
Install ADB Tools on Windows
Now we want to make use of the ADB drivers. To ensure everything is as recent as possible, first, head to this website and download the android sdk_ [release number] -windows.zip file from down the page.
Unpack the archive and open the SDK Manager.exe file. Wait ten seconds, until the right window (see above) opens. Since we’re not looking to program an app, we can remove a lot of the checkmarks. In fact, only Android SDK Platform Tools needs to be left checked. Note: repeat this procedure if ADB Tools begins to misbehave at any point.
Next, open up the new platform-tools folder in the previously extracted folder. Hold shift and right click anywhere in the white space of this folder and click Open a command window here. With your smartphone connected via USB to your computer, type in the command window adb devices. On your smartphone, you will see a warning message (bottom-right image).
Once you have enabled USB debugging on your device and allowed it from the computer (pictured above), you device should appear in the device list within the command window.
Install ADB on Mac or Linux
The Unix-based systems of Mac OS and Linux make things much easier. Firstly, they eliminate the hassle of drivers. Secondly, the ADB tools keep themselves up to date thanks to simple package management systems. Mac users install the package manager Homebrew and then run brew install android platform-tools. Linux users need to look in the package system for android-platform-tools and install it. Subsequently, the ADB tools should be defined globally, so you are able to use the following ADB commands in the command line.
ADB commands
adb backup -f FullBackup.ab -apk -all: The idea here is that you make a full backup of your app data. In practice, the results are unreliable. Not all apps allow for an ADB backup, meaning you might need to find an alternative method.
adb devices: With this command you will receive an overview of all devices connected to the computer device with ADB support. Here you can see the device identifier and the status. If the word Unauthorized appears, it means you need to allow the computer permission to communicate with your smartphone.
adb reboot: reboots your smartphone
adb reboot recovery: reboots your device into recovery mode
adb reboot bootloader: reboots into the bootloader. Once it is in this mode, you can communicate with the device via the fastboot command.
adb push[directory on the computer / dateiname.endung] [Directory in the smartphone]: this command moves a file from the stated folder on your computer to the stated folder on your smartphone.
adb pull [Directory in the smartphone / dateiname.endung] [directory on the computer]: if you run this command, it will save a file from your smartphone or tablet to your PC. Without specifying the computer directory, the file will land in the path of the ADB executable or /home directory.
adb shell screencap -p /sdcard/screenshot.png
adb pull /sdcard/screenshot.png
adb shell rm /sdcard/screenshot.png:To take a screenshot, saved to your computer.
adb help: overview of all ADB commands, syntax and help.
ADB to flash apps and updates
adb sideload update.zip: this command is used to install files, such as official device updates, on your smartphone. More complex installations, such as those of Custom ROMs, however, are done through the fastboot interface.
adb install [android app].apk: this can be used to install an Android app (APK) on your smartphone / tablet.
ADB errors: common error messages and solutions
Command Not Found: you have made a mistake, or the command is not yet available in your ADB version. Check the command via adb help or update to a newer version ADB.
No Device: Your USB cable is not connected properly, the ADB interface on your phone is not running or your computer does not recognize your smartphone. Try using a different USB port, another cable, enable USB debugging, check the drivers, the computer, and restart your device.
Server is out of date: The version of ADB Tools on your computer and the version of Android on your smartphone must be compatible. If they are not, this error occurs. Update your version of ADB Tools.
Waiting for device: This error is largely the same as the No Device error. Your computer does not recognize your smartphone. See above for the solutions.
What now?
Now you are aware of all the ways you can go about modifying your smartphone. Be it sideloading an update, rooting, or whether it is the installation of different firmware, you now have full control over your smartphone.
Need any further help? Put your questions in the comments section below.
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The first step is to unlock bootloader. I stack on step 8, fastboot oem get_identifier_token shows info < waiting to device >. adb sees my device but fastboot can't. An idea?
My phone is HTC Wildfire S and these are steps which I am following:
- I restarted phone and entered into
FASTBOOT USBmode - I tried to run
fastboot oem get_identifier_tokencommand but without success.
I use Windows 7 Professional and my phone is recognized as HT1CSTR05155.
9 Answers
Linux/OSX
Run fastboot as root or with sudo.
Other OS: credits
Are you rebooting the device into the bootloader and entering fastboot USB on the bootloader menu?
Try:
adb reboot bootloader
Then, look for on-screen instructions to enter fastboot mode.
geffchangProblem solved. At the end I saw that drivers for android were not installed. I installed drivers from this site http://forum.xda-developers.com/showthread.php?t=2126036 and device is visible by fastboot. One thing I don't understand is why adb saw device and fastboot not.
ADB and fastboot require different USB drivers.
Whilst you may see your device under adb when your phone is on it will not be detected by fastboot until you install the driver for it and hence will show 'waiting for device'.
You can follow the steps below to do so:
- Open your device manager and reboot your device into fast boot by pressing volume up, down and power button simultaneously
- You will notice that device manager refreshes and now your phone has a yellow icon
- Download the Google USB driver, it is a zip file so go ahead and unzip it in your local directory
- Right click on the yellow triangle for your device and update driver, select the option update from local storage and select the folder 'usb_driver' under extracted files in previous step
- You are good to go now, fastboot oem unlock will detect the device now
I didn't realize it right away, but there are different ADB drivers and Fastboot drivers. I had installed the google usb drivers with the SDK extras and ADB worked great but I got the 'waiting for device' trying to flash in fastboot mode.
I went to device manager from the control panel and saw the 'Android 1.0' device with the yellow icon showing it wasn't working right. I had to update the driver and pick from the list of existing drivers which had a fastboot entry.
Minimal Adb And Fastboot Xiaomi
I had the same problem described by 'pepuch' on my HTC Desire S. I tried different drivers on relatively new computers running Windows 8 and Windows 10. In the end I found a link suggesting that I should try the (same) procedure on an older (desktop) computer which I did and the computer managed to detect my Desire S in fastboot USB mode and I managed to read the ID token. The link which steered me to the solution follows:http://forums.androidcentral.com/htc-one-rooting-roms-hacks/345350-htc-one-pc-doesn-t-recognize-bootloader.html
The only thing I did before starting in fastboot USB was to install the HTC drivers for the phone on the Windows 7 box and verify that the phone is detected when Android is up and running.
Issue: adb and fastboot modes for the same Android device are recognized as separate devices under Windows
Scenario: the device is visible with adb devices but is not detected with fastboot devices and the other suggestions here don't work; you still end up with 'waiting for device' on Windows and aren't able to choose a driver to install via rahul pandey's answer using the Google USB driver.
Possible Solution: manually update the driver for your device in Device Manager while it's connected in fastboot mode
Steps:
- Download and install the Android USB drivers for your device. For example, Samsung drivers for Samsung phones or the (venerable) Google Galaxy Nexus
- Reboot device into fastboot mode using
adb reboot bootloaderor by pressingVolume Up+Volume Down+Powerbuttons simultaneously - Open Device Manager
- Unplug/plug in your Android device so you can easily find your unrecognized device in the list
- Under Other Devices find your Android phone with a yellow triangle
- Right-click on it and select:
Update driver>Browse my computer for driver software>Let me pick from a list of available drivers on my computer - Look for the driver you just installed and select it. For my Google Galaxy Nexus it was
Samsung Android ADB Interface.
With any luck that will solve your problem. Now you can use the bootloader unlock method for your device (or, in my case, flash an OEM ROM).
Thanks to: https://android.stackexchange.com/a/106468/52235 for pointing me in the right direction.
try reinstalling fastboot driver
while in fastboot
- open device manager
- expand android
- there should be one device
- right click
- uninstall
- uncheck 'delete driver software'
- click on pc with magnifying glass (in toolbar)
- if not fixed, repeat, but check delete driver (you may need to download it)
If no drivers work on Windows 10 or 8.1/8 and your goal is to just use fastboot to flash boot.img (Probably because you have S-ON), there's the way of the Linux:Get a USB stick ready and use Live Linux Creator and install a Live Linux like Ubuntu or Lubuntu onto the stick. Boot to the Live version (maybe you can use VirtualBox VM on Windows, not sure). Open Terminal with Ctrl+Alt+T.Type (without comments with // ofc):
protected by Community♦Sep 15 '16 at 21:14
Minimal Adb And Fastboot Zip
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?