Template:Paths

"Command not found" errors

If the adb or fastboot binary file is installed on your computer, but you see a "command not found" type of error when entering your command into the terminal, the problem may be that the /platform-tools directory (or whichever directory contains the binary) is not in the "path of execution" for your terminal session. This means that your computer doesn't know where exactly the binary is located.

The solution to this is to add the directory containing the binary to your PATH.

Linux/OS X

On most Linux/OS X systems using the Bourne Again Shell (bash), you can do the following:

1. Edit the "hidden" (starting with a period) file ~/.bashrc -- If your version of Linux supports the gedit editor, simply type gedit ~/.bashrc
2. Next, add this line to the bottom: export PATH=${PATH}:<sdk>/tools:<sdk>/platform-tools (Change <sdk> to the actual path to the SDK's /platform-tools directory. For example: export PATH=${PATH}:/home/user/android-sdk-linux/platform-tools/)
3. Save the file. Then open a new Terminal. The adb command should now be available.

Windows

On Windows systems you can do the following:

1. Righ-click on My Computer and select Properties.
2. Choose Advanced, and click on the Environment Variables button.
3. Navigate to System Variables and double click on Path to edit.
4. Enter the full path to your tools folder.