Android Basics: How to Install ADB & Fastboot on Mac, Linux & Windows

How to Install ADB & Fastboot on Mac, Linux & Windows

ADB and Fastboot are probably the most important tools for any Android aficionado. They can do everything from backing up your device and changing your screen resolution to rooting your phone and opening it up to hundreds of tweaks and customizations. What's even better is that they can be downloaded and installed on any of the three major computer operating systems in just a few clicks.

Method 1: Install Android SDK Tools (Windows, Mac, or Linux)

Your first (and probably best) option is to install Android SDK Tools, which comes with ADB and Fastboot bundled. It's also updated regularly by Google. (Note: see update link above for a way to download just the tools without the SDK, or continue with these instructions if you want the full SDK.) To use this option, start by downloading the installer file for your particular operating system:

The installation process will vary depending on your operating system, so we've outlined it in three separate sections. When you're done, make sure to hit up the "All Operating Systems" section below to finalize your work.

Windows Installation Instructions

Windows users can simply launch the EXE file and follow the provided instructions to install the Android SDK. When installation has finished, you'll be prompted to update the SDK Tools. When you see this menu, make sure that the "Android SDK Platform-tools" option in selected, then click "Install."

Once installation is completely finished, Android SDK Tools will be saved in the C:\Program Files (x86)\Android\android-sdk\ folder. Remember this location, as you'll need to open a command window in the "platform-tools" folder inside of it when you want to run ADB or Fastboot commands.

After that, you'll need to download the ADB drivers so that the new software can interact with your device. You can download the drivers at this link—just run the file, then follow the prompts, and you'll be good to go.

Mac Installation Instructions

If you're using a Mac, extract the ZIP to a folder you can access easily, and take note of this folder's location, as this is where you'll need to open a command window whenever you want to send ADB or Fastboot commands.

From there, open the android-sdk-macosx folder, then head to the tools folder inside of that. Next, double-click the "android" file to launch the SDK installer.

From here, make sure that the "Android SDK Platform-tools" option in selected, then click "Install." After that, just follow the prompts for installation, and click "Accept" when prompted about license agreements.

Note that as a Mac user, you'll need to add a period and a slash (./) to the front of any ADB or Fastboot commands you see listed on most sites. In other words, when a guide tells you to type "adb devices" or something similar, type "./adb devices" instead.

Linux Installation Instructions

If you're running Linux, extract the android-sdk_r24.4.1-linux.tgz file, then open a terminal window and change directories to the /android-sdk-linux/tools/ folder that you just extracted. Next up, type android sdk to launch the SDK Manager, then make sure the "Android SDK Platform-tools" option is selected and click "Install."

When that's finished, you'll need to install the drivers. To do that, download and extract this ZIP file, then run the script with Terminal, and you'll be all set to go.

Note that as a Linux user, you'll need to add a slash (/) to the front of any ADB or Fastboot commands you see listed on most sites. In other words, when a guide tells you to type "adb devices" or something similar, type "/adb devices" instead.

All Operating Systems

Once you've installed Android SDK Tools, you'll be ready to send ADB and Fastboot commands. But to make sure you don't have any troubles in the future, there's one last step you should take.

First, make sure you have "USB debugging" enabled on your Android device. This setting can be found in the Developer options menu, which can be activated using these instructions. From there, simply connect your phone or tablet to your computer with a USB cable, then you should see the following prompt on your Android device:

To finalize things, tick the box next to "Always allow," then press "OK" on the popup. When you're done there, you should have no trouble sending ADB or Fastboot commands in the future.

Method 2: Install a Standalone ADB Program (Windows)

Thanks to shimp208's Minimal ADB and Fastboot utility, there's a quick and painless way to install ADB and Fastboot on Windows. However, note that this tool isn't updated as frequently as the official Android SDK Tools from Google, so it may be missing a feature here and there.

All you have to do is download his ADB installer (.exe), then run the file and follow the prompts. When you're done there, download the drivers from this link, and again, run the file and follow the prompts.

After that, you'll be all set to use ADB and Fastboot commands. To do that, just head to the C:\Program Files (x86)\Minimal ADB and Fastboot\ folder, then hold down the shift button on your keyboard, right-click any empty space, and choose "Open command window here."

Method 3: Install a Standalone ADB Program (Mac & Linux)

If you are using a Mac or Linux computer, you won't have the luxury of using a program to install ADB and Fastboot. Instead, you will have to use a Terminal command.

However, this will install ADB and Fastboot in a way that allows you to use them from any directory so you don't have to worry about entering a "cd" command to get ADB or Fastboot commands to run properly.

To get ADB and Fastboot to install, you'll need to run a script created by corbin052198. There is no actual file to download since Terminal will handle the downloading and installation. So to get down to business, just execute the following command in Terminal. You will need an active internet connection to get this to run properly, and will need to type in your password to continue.

bash <(curl -s

If you get an error, you can try this alternative command instead.

cd ~ && curl -s -o ./ "" -LOk && chmod +x ./ && ./ && rm ./

Now you should have a fully functional and up-to-date copy of ADB and Fastboot on your computer, but if you continue to get errors like "device not found," be sure to drop us a comment below.

Cover image and screenshots by Dallas Thomas/Gadget Hacks


tenia un problema de compatibilidad con adb, asi que use las urls que proporciona este blog y me descargo los archivos en la ruta usr/bin/adt y usr/bin/fastboot, y remplace en "folder personal"/Library/Android/sdk/platform-tools

¿Que pasa cuando pones una clave de adb?

I installed adb/fastboot for windows, but it still will not be recognized. i'm trying to get the GPe, and i was linked here from your other article on unlocking the bootloader

Did you install it system wide? Are you using a USB 2.0 port to connect your device?

The commands for Linux are needlessly complex. On Ubuntu, here's how you get ADB in one command line step. Better yet, it is kept up to date indefinitely, unlike the method shown above.

$ sudo apt-get install android-tools-adb

Boom. Done.


thank you much for a great article. I have a new Moto X Pure, and have tried installation w method 3 /mac. The script installed both adb and fastboot fine. But when I connected my phone, I initially got a "command not found" when I entered "oem...." . Then -- "device not found" error. I am a NOOB! Do I need to CD change directories? I have Yosemite, but also Avira Antivirus (why you ask? well, I actually WAS infected...)- I'll turn that off and see. Do I need to enter any other commands in fastboot? And I should preface everything w "fastboot..." , true?

What text should show on the phone? I have "device locked" which I am not sure what it refers to. The bootloader has not yet been unlocked; I'm installing adb etc. to unlock the bootloader etc. Is that what the text refers to? Do I need to be in any other mode than download mode? (my Moto X P) has several modes, it seems)

thanks much!


oops, addendum. I have a Moto X Pure. turns out under developer options, I had to turn off "verify apps over USB". Then it worked fine; I used fastboot to get my unlock code for my phone. Thank you much!

have done all the above but when I run the command line in comes back with "device not detected"

could anybody help

dony know if usb debugging has been activated on Sony Experia

I attempted method 3 but terminal is asking me for a sudo password but there is no mention in this post in regards to a password. I cannot type or paste anything.

Please assist.

If it's asking for a password, it will be your admin password on the computer. When you type it in, it will look like nothing is happening, but it is. Just type it out carefully and press enter.

Can't open command window someone please help what am I doing wrong?

The OEM unlock has to be ticked on in developer mode to use fast boot if it's disabled you'll never be able to get root on said device

I honestly don't know if anyone will read this but I am hoping so. I am trying to update my HTC Desire 530 from Verizon but I can;t get it to unlock!! Please help.

HT67R0002270 fastboot

oem unlock
FAILED (remote: 'unknown command')
Finished. Total time: 0.009s

flashing unlock
FAILED (remote: 'unknown command')
Finished. Total time: 0.007s

I'm sorry, but it looks like your phone's bootloader can't be unlocked. Verizon double-locks the bootloader on their devices and there's no way around it.

The errors you're getting seem to back that up. The "remote: 'unknown command'" part is saying the other end of the connection (your phone, not your computer) is receiving the command, but saying "I don't have a command like that."

Under "Linux Installation Instructions", the link for the driver zip file appears to be broken - I get a not found error.

Share Your Thoughts

  • Hot
  • Latest