Android ADB Fastboot


Latest SDK version: 26.0.2
Custom Installer updated: 2017.11.21


After always having to search for the latest versions of  Android’s ADB and Fastboot tools instead of downloading the whole Android SDK for just 1 mb in a few files, I decided to make my own MSI installer using the latest versions of ADB and Fastboot.

Starting in 2017, Google decided to release the platform-tools binaries as a separate download. This means you no longer need to install the complete Android SDK to get the latest ADB and Fastboot versions.

You can install it wherever you want and it will work from any path in the command prompt. The installer will append the installation folder location to the system PATH variable, allowing you to run ADB or Fastboot without you having to change the command prompt path to where they are installed.

This installer is 32-bit and 64-bit compatible.

Android ADB Screenshot


The default installation path is C:\ADB so you can easily add your flashable files in there. There are no shortcuts because they are not needed.

After installing Android ADB Fastboot you can open a command prompt and type adb or fastboot commands right away, you don’t need to change paths. Keep in mind that you need admin privileges, though.

To open a command prompt with administrator rights on Windows 10, right click on the bottom left corner of the screen or use the Win+X shortcut and then click on Windows PowerShell (Admin). Windows 10 Creators Update changed the command prompt to PowerShell.

Windows 10 Win-X Menu

If you have Windows 7 or Vista, the quickest way to do it is to type CMD on the Start Menu search box and press Ctrl+Shift+Enter instead of just pressing Enter.


You need to have ADB Debugging under Developer Options on your device. You also need the drivers for every device you want to use with ADB installed and working.

You can type adb devices on a command prompt. If your device is listed, the drivers are working and good to go for ADB and Fastboot use.


I will always check the ADB version whenever a new Android SDK is released and I will update my installer when needed.



  • Paulinus

    Thanks for this.

  • Matias Nino

    Thank you for this! Helped bigtime!

  • MH


  • Fdawg

    Thanks I had real old version from 2012 😛

    • There’s no shame in that, but now you can always have the latest version 😉

      • autoparts321

        what did you mean by “now you can always have the latest version”??? does your installer have automatic updates feature?

        • No, it doesn’t. What I meant was that by using my release, you will always have the latest version of ADB as I update the installer whenever a new ADB version is available.

  • Abhishek

    with ‘adb devices’ command, I get
    ADB server didn’t ACK
    * failed to start daemon *
    error: protocol fault (no status) adb version is out of date,

    ‘adb version’ command gives
    ‘Android Debug Bridge Version 1.0.32’

    where’s the problem, drivers or the file? I’m not getting it

    • It could be your drivers or a security software like a firewall. I would try to uninstall and install the drivers again and see if it solves it. Look for up to date drivers for your device. Let me know how it goes.

  • James Stone

    I’m having issues trying to get Fastboot to find my device. Interestingly ADB finds it. My specs are below:

    Computer: Ubuntu 14.04

    Phone: One Plus Two Oxygen OS 2.1.1

    james@james-Aspire-3830TG:~$ adb devices
    List of devices attached
    3778baee device

    james@james-Aspire-3830TG:~$ fastboot devices

    Any help would be great – Thanks !

  • Foolios

    Waiting For Device Error





    • Normally that’s a problem with your device drivers. Uninstall any drivers you may have installed and see if reinstalling them solves it. Also, look over at XDA for new drivers for your device.

  • Foolios

    plz help NOWNOW

  • David B

    I am sorry I am totally computer illiterate. Where do I download this?

  • blipton

    Any suggestions for installing adb on linux? I’m running Debian 8.4 on a BeagleBone Black, so resources are limited for an android sdk install.

    My ultimate goal is to use the android’s camera over usb for face recognition using the beaglebone.

    • Hi, you can try to search the XDA forum. I’m sure there are ways to get ADB on your installation in an easy way.

  • UrWifesBoyfriend

    I probly sound dumb but….
    How do I delete all my older drivers before doing this?
    Ive read that the fastboot drivers Google drivers need to be manually trashed
    For me: adb devices. (it shows my serial #)
    But :::: fastboot devices *waiting for device*
    All day I was stuck
    So, thnx in advance

    • It’s not dumb at all. This could be obvious but are you trying the fastboot command while your device is in fastboot mode? Fastboot won’t work in “normal” mode, which is having the device booted up with the operating system.

      • UrWifesBoyfriend

        neYup, And It Remains As Fastboot Not Fastboot USB
        I went ahead and installed this here and i still have the same issue. I’m thinking about installing ubontu or something like that. argh…. my phones out dated and I’m really upset with the lag. but I’m a dad and my money can’t keep going to new phones all the time. i have the htc evo 4g lte. no mods of course

  • Nightmare-Rex

    ABD not rconized as an internal or external command :/ what do you have to do to get it to launch? i dled this, anoither and the whole stinking sdk ass well as set the path varables. what else do you have to do!? yes running cmd prompt as admin.

  • solepublic

    I haven’t been able to get any drivers for my 2012 Kindle fire 7″ HD (D025) to install on my windows 10 64-bit system. I have driver verification disabled and JAVA installed. I’ve tried the Amazon drivers you linked to in your “How to Root the Kindle Fire HD to Install a Custom ROM” post, the latest google usb driver, and Jayce Ooi’s kindle fire driver. I haven’t been able to find a win10 64bit compatible driver on XDA. Any suggestions? I’ve got ADB, fastboot and a rooted kindle, but I need a driver to install a custom ROM. Also, do you recommend CM11 now that it is abandoned?