Why are you trying to run “./adb”? That skips the path variable entirely and only looks for “adb” in the current directory. Try running “adb” instead.

Edit: your path looks wrong. You say you get

/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/Libs/android-sdk-mac_x86/tools:/Libs/android-sdk-mac_x86/platform-tools

You’re missing the /Users/simon part.

Also note that if you have both .profile and .bash_profile files, only the latter gets executed.

Add to PATH for every login

Total control version:

in your terminal, navigate to home directory

cd

create file .bash_profile

touch .bash_profile

open file with TextEdit

open -e .bash_profile

insert line into TextEdit

export
PATH=$PATH:/Users/username/Library/Android/sdk/platform-tools/

save file and reload file

source ~/.bash_profile

check if adb was set into path

adb version

One liner version

Echo your export command and redirect the output to be appended to .bash_profile file and restart terminal. (have not verified this but should work)

echo “export PATH=$PATH:/Users/username/Library/Android/sdk/platform-tools/
sdk/platform-tools/” >> ~/.bash_profile

Alternative: Install adb the easy way

If you don’t want to have to worry about your path or updating adb manually, you can use homebrew instead.

brew cask install android-platform-tools

On my Macbook Pro, I’ve added the export lines to ~/.bash_profile, not .profile.

e.g.

export PATH=/Users/me/android-sdk-mac_86/platform-tools:/Users/me/android-sdk-mac_86/tools:$PATH

Just encase anyone finds this SO post when using Android Studio which includes the SDK has part of the App package (on Mac OSX).

So as @davecaunt and @user1281750 noted but insert the following line to .bash_profile

export PATH=/Applications/Android\ Studio.app/sdk/tools:/Applications/Android\ Studio.app/sdk/platform-tools:$PATH

The answer for MAC should be:

1. Open your bash_profile with the following commands: open ~/.bash_profile

2. In case base profile file doesn’t exist, create a new one with the following command: touch .bash_profile then repeat phase 1.

3. Add the following line: export PATH=/Users/"YOURUSER"/Library/Android/sdk/platform-tools:$PATH

4. Restart your bash window and test by typing adb shell

Good luck! 🙂

In your terminal, navigate to home directory

cd
create file .bash_profile

touch .bash_profile
open file with TextEdit

open -e .bash_profile
insert line into TextEdit

export PATH=$PATH:/Users/username/Library/Android/sdk/platform-tools/
save file and reload file

source ~/.bash_profile is very important
check if adb was set into path

adb version

It should be fine now.

Android Studio v1.2 installs the adb tool in this path:

~/Library/Android/sdk/platform-tools/adb

So it goes like this:

1. Run Terminal
2. run adb version and expect an error output
3. touch ~/.bash_profile
4. open ~/.bash_profile
5. add the above path before the ‘closing’ :$PATH
6. source ~/.bash_profile
7. run adb version and expect an output

Good luck!

I use zsh and Android Studio. I use a variable for my Android SDK path and configure in the file ~/.zshrc:

export ANDROID_HOME=/Applications/Android\ Studio.app/sdk
export PATH="$ANDROID_HOME/platform-tools:$ANDROID_HOME/tools:$PATH"

Note: Make sure not to include single or double quotes around the specified path. If you do, it won’t work.

It appears that you’re still trying to execute adb with ./adb. That asks the shell to run the program named adb in the current working directory.

Try just adb without ./.

In order to make the terminal always have the file ~/.bashrc and there put the path you wish to use, by adding:

export PATH=$PATH:/XXX

where XXX is the path that you wish to use.

for adb, here’s what i use:

export PATH=$PATH:/home/user/Android/android-sdk-linux_x86/platform-tools/

(where “user” is my user name).

I added export PATH=${PATH}:/Users/mishrapranjal/android-sdks/platform-tools/ into both places .bash_profile and .profile to make sure it works. Still it wasn’t working and then I looked at sarnold’s tip about restarting terminal and it worked like a charm.
It saved my time of adding every time this into the PATH whenever I had to run adb.
Thank you guys.

If anyone can’t seem to get there .bash_profile file to take any new Paths AND you have other commands in that file (like alias commands) then try moving the PATH statements to the top of the file.

That is the only thing that worked for me. The reason it worked was because I had some typos in my alias commands and apparently this file throws an error and exits if it runs into a problem. So that is why my PATH statements weren’t being run. Moving it to the top just let it run first.