When I write in cmd adb devices I got from windows this:
'adb' is not recognized as an internal or external command,
operable program or batch file.
but in my 2nd pc when I write this same adb devices i got list of my devices and i see my phone with android.
What is wrong with 1st PC ? How to repair it ?
It seems windows can't find adb in your computer. adb is located at this folder if you have installed android sdk
%USERPROFILE%\AppData\Local\Android\sdk\platform-tools
You can add this folder to PATH environment variable and then adb will be available globally. Here are steps
1. Click 'Start'.
2. Type 'Edit environment variables for your account', and click it.
3. Double click PATH.
4. Click 'New'.
5. Paste that path in.
6. Click 'OK', click 'OK', and restart any command prompts you have open.
I'm having an issue running the android key word on Git bash, installed on Windows 7, 64 bit.
The error I get is as below:
sh.exe": android: command not found
Any one know why this is so?
You need to set Android SDK path in your system path.I am assuming you have your sdk at this path:C:\android-sdk-windows
Can be done in below ways:-
Using command prompt :
set path=%path%;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;
Another way is to add in your environment variable:-
My Computer->Property->Advanced->Environment Variables->Edit Path Variable and add “C:\ android-sdk-windows\tools” & “C:\ android-sdk-windows\platform-tools”into the Path Variables.
It is a good practice to do so, because you will be irritated if need to go SDK folder in command prompt always when their is need for it.
I am trying to run google map v2 on emulator, I am following this tutorial.
When I was trying to install required apk file on emulator, I am getting below error.
I tried to solve this using this tutorial.Followed all steps, added the path to paltform-tools to environment path. Also after modifying the PATH variable started a new CommandPrompt window.
But getting the same error. I need to check my google map application on emulator.
Kindly suggest me.
'adb' is not recognized as an internal or external command,
operable program or batch file.
Set the path of adb into System Variables. You can find adb in "ADT Bundle/sdk/platform-tools" Set the path and restart the cmd n then try again.
Or
You can also goto the dir where adb.exe is located and do the same thing if you don't wanna set the PATH.
If you wanna see all the paths, just do
echo %PATH%
From Android Studio 1.3, the ADB location is at:
C:\Users\USERNAME\AppData\Local\Android\sdk\platform-tools.
Now add this location to the end of PATH of environment variables. Eg:
;C:\Users\USERNAME\AppData\Local\Android\sdk\platform-tools
If you want to use it every time add the path of adb to your system variables:
enter to cmd (command prompt) and write the following:
echo %PATH%
this command will show you what it was before you will add adb path
setx PATH "%PATH%;C:\Program Files\android-sdk-windows\platform-tools"
be careful the path that you want to add if it contains double quote
after you restart your cmd rewrite:
echo %PATH%
you will find that the path is added
PS: if you just want to add the path to cmd just to this session you can use:
set PATH=%PATH%;C:\Program Files\android-sdk-windows\platform-tools
I did this on Windows 7, by going to:
Start > Control Panel > System > Advanced System Settings > Environment Variables...
In this Environment Variables window, in the User variables for (your-username) highlight Path and click Edit...
You then need to append a ; if there isn't already one at the end of the Variable value field, and then append C:\Users\<your-username>\AppData\Local\Android\sdk\platform-tools; to that same field.
Then click the three OK buttons to get out.
If you already have a Command Prompt window open, close it then re-open and the adb devices command should then work.
In Windows 10,
Add User Variable PATH: %USERPROFILE%\AppData\Local\Android\sdk\platform-tools.
Restart cmd (if any open).
adb devices, it should list, if it does, you are all set.
That's it!
On Window, sometimes I feel hard to click through many steps to find platform-tools and open Environment Variables Prompt, so the below steps maybe help
Step 1. Open cmd as Administrator
Step 2. File platform-tools path
cd C:\
dir /s adb.exe
Step 3: Edit Path in Edit Enviroment Variables Prompt
rundll32 sysdm.cpl,EditEnvironmentVariables
more, the command to open environment variables can not remember, so I often make an alias for it (eg: editenv), if you need to work with environment variables multiple time, you can use a permanent doskey to make alias
Step 4: Restart cmd
Add your path into environment variable "PATH" where you installed your sdk with below:
\Sdk\platform-tools
You can in image below for example:
and reopen your command prompt to see changes.
Follow path of you platform tools folder in android setup folder where you will found adb.exe
D:\Software\Android\Android\android-sdk\platform-tools
Check the screenshot for details
If your OS is Windows, then it is very simple.
When you install Android Studio, adb.exe is located in the following folder:
C:\Users\**your-user-name**\AppData\Local\Android\Sdk\platform-tools
Copy the path and paste in your environment variables.
Open your terminal and type: adb it's done!
adb command can be under the new path below-
C:\Users\USERNAME\AppData\Local\Android\sdk\platform-tools
for new versions of Android studio.
I found in this location for me.
For environment variable, we have to need to follow some steps.
just open Android studio and press "Tools" on Top navigation bar
tools->SDK Manager
Where you can get SDK location
Open SDK folder -> platform-tools
You will need to set the PATH variable pointing to the directory where adb.exe is to be found. If you are using cmd.exe, this command will help:
set PATH=%PATH%;%USERPROFILE%\appdata\Local\Android\sdk\platform-tools
1st: goto the drive where your eclipse reside and goto sdk and platform tool in my case C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools
2nd:copy that address for ease of access
3:open command prompt win+r and type cmd hit enter
4:paste the address in cmd and hit enter thats all
In new version PowerShell, after all steps that mentioned before this, please attend:
before
adb
now
.\adb
I recommand you using PowerShell
Set Android Studio Terminal to PowerShell:
Settings > Tools > Terminal > Shell path = pwsh.exe (instead of cmd.exe)
Open Terminal on Android Studio
PowerShell 7.0.1
Copyright (c) Microsoft Corporation. All rights reserved.
https://aka.ms/powershell
Type 'help' to get help.
PS >
Test the path for adb.exe
# `pikachu` should be replace your username
PS > test-path "C:\Users\pikachu\AppData\Local\Android\sdk\platform-tools"
True
Open your powershell profile file in your text editor
PS > notepad $profile
add below line, save and exit
# `pikachu` should be replaced with your username
$env:PATH+=";C:\Users\pikachu\AppData\Local\Android\sdk\platform-tools"
re-open Terminal and try adb
PS > adb
Android Debug Bridge version 1.0.41
Version 30.0.1-6435776
Installed as C:\Users\hdformat\AppData\Local\Android\sdk\platform-tools\adb.exe
global options:
-a listen on all network interfaces, not just localhost
-d use USB device (error if multiple devices connected)
-e use TCP/IP device (error if multiple TCP/IP devices available)
-s SERIAL use device with given serial (overrides $ANDROID_SERIAL)
-t ID use device with given transport id
-H name of adb server host [default=localhost]
-P port of adb server [default=5037]
Based on Vamsi Tallapudis earlier answer I came up with this dynamic path:
%LOCALAPPDATA%/Android\sdk\platform-tools
It's using a Windows Environment Variables. I find this solution to be both elegant and easy and would therefor like to share it.
Since I installed version 1.0.41,
I had to use the command "adb version" instead of "adb –version", in Windows 10.
Check and add these below loacations to the path variable:
C:\Users\Sameera\AppData\Local\Android\Sdk\tools
C:\Users\Sameera\AppData\Local\Android\Sdk\platform-tools
C:\Users\Sameera\AppData\Local\Android\Sdk\build-tools
ANDROID_HOME
C:\Users\Sameera\AppData\Local\Android\Sdk
I had same problem when I define PATH below
C:\Program Files (x86)\Java\jre1.8.0_45\bin;C:\dev\sdk\android\platform-tools
and the problem solved when I bring adb root at first.
C:\dev\sdk\android\platform-tools;C:\Program Files (x86)\Java\jre1.8.0_45\bin
In my case it was:
C:\Program Files (x86)\Android\android-sdk\platform-tools
This is where I found it:
C:\Users\<USER>\AppData\Local\Android\sdk\platform-tools
I had to put the complete path into the file explorer. I couldn't just click down to it because the directories are hidden.
I found this path listed in Android studio:
Tools > Android > SDK Manager > SDK Tools
This answer assumes that the PATH has been correctly set as described in the other answers.
If you're on Windows 10 and don't have Admin rights, then right click on the CMD, powershell ... program and select run as administrator. Then try adb [command]
First select drive that is where Android sdk folder is there. Then you Follow the below steps
cd DriveName:/ or Ex : cd c:/ Press 'Enter'
then you will give the path that is adb console path is there in a platform-tools folder
so
cd Root Folder/inner root folder if there/Platform-tools Press 'Enter' then it selects the adb directory.
If you didn't set a path for ADB, you can run .\adb instead of adb at sdk/platformtools.
It seems that Avast antivirus detects adb.exe as a virus and adds it to it chest
For those using macOS, this osxdaily.com article shows several ways to add adb to the $PATH.
Here's the one I prefer:
Add a file named adb to /etc/paths.d/ folder that just contains the path to adb's location: /Users/YourUserName/Library/Android/sdk/platform-tools/
In a Terminal window, sudo vim /etc/paths.d/adb
-> enter the path and save the file.
Close/re-open Terminal in order for it to see the change.
You could just drag the adb.exe on to the command prompt from sdk/platformtools and leave a space and type the command you want: like logcat.
It looks like this for me:
C:\adt-bundle-windows-x86-20130917\adt-bundle-windows-x86-20130917\sdk\platform-tools.exe logcat
and hit enter.
When i enter "adb install asdasd.apk" to cmd returns "error:device not found". How can I fix this?
Just copy that apk file into ( D:\android-sdk\platform-tools ) android sdk platform tools.
and then open the cmd prompt.
then, come into that platform tools path in cmd prompt.
then, give like this in cmd -- adb install (appName).apk
wait few minutes and get success respomse in cmd prompt..
First, familiarize yourself with a concept of AVD. That's basically an instance of the emulator - it has a bunch of settings, like the Android version to use and screen size and an SD card image.
You cannot install stuff "in the emulator" - you can only install stuff into a specific AVD. For that, you need to create and run an AVD first. For that, use "AVD Manager" from Eclipse or standalone.
Under the Android SDK folder in Explorer, run "AVD Manager". Choose an AVD (or create a new one if you don't have any). Select, click "Start".
Does the emulator show up when you run the following command?
adb devices
If not, you might have to boot up the AVD first, but if I remember correctly it should be starting it up by itself.
Have you created a new emulator for your project? And are you using Eclipse? Eclipse has an ADT plugin which is useful as it allows you to open the AVD manager through it. This plugin will give you this option in the Windows tool bar of Eclipse: Windows>AVD manager.
Create a new project based on the emulator and click the run button which will install your project onto the emulator. If you have an Android device I recommend turning USB development mode in your phones settings and running your project straight onto your device as it will be a lot faster. Hope this helps
this is what i did :
first run the "AVD Manager"-> choose an AVD -> click "Start"
immediately after
you click on "Start"
use command on cmd as,
adb install asdasd.apk
then in my case (Windows), asked to place .apk file in data/local/tmp/
what i did was copy and paste .apk file into data/local/tmp
and again use command
adb install asdasd.apk
then cmd prompted-> Success
You can also use command
adb devices
command for check whether emulator is in the list
Actually you may need to run AVD several times
I am trying to familiarise myself with using adb from the command prompt.
My adb.exe is installed at:
C:\Program Files(x86)\Android\android-sdk\platform-tools
I have tried starting off by typing in cd:C\ to take me to the C drive
Then I have typed in the path quoted above, sometimes putting Program Files(x86) in quote marks,
other times inserting % in between Program and Files.
But always I get the same answer - "The system cannot find the path specified".
Even when I type the path and then put in “adb devices” I get nothing.
I have tried inserting each of the following in the path in system variables as follows:
;C:\"Program Files(x86)"\Android\android-sdk\platform-tools\
C:\"Program Files(x86)"\Android\android-sdk\platform-tools\
;C:\Program Files(x86)\Android\android-sdk\platform-tools
And then typing “adb devices”.
The message is the same – “adb is not recognised as an internal or external command, operable program or batch command.
You can call adb directly from the directory you are currently in: "C:\Program Files(x86)\Android\android-sdk\platform-tools\adb.exe" (With quotes!) You can also navigate to the platform-tools directory and then call adb.exe, use cd .. to go to a directory level up, you can hit TAB to let windows list the appropriate directories, this works also if one or more characters are entered.
Btw, just added "C:\Program Files\Android\android-sdk\platform-tools" to my PATH and it works just fine! Separate the entires with a semicolon.
for using a 64 bit os try going step by step,
type in command prompt
cd "C:\Program Files (x86)"
you will enter C:\Program Files (x86)directory
then type
cd Android\android-sdk\platform-tools
It's the spaces that are messing people up. Windows users need to remember one important thing when dealing with command lines: do not install the utilities to folders where there's a space in the folder name - it will save you a lot of hassle which sometimes can't even be solved by using quotes.
For example, I've installed the Android SDK to C:\Android\android-sdk-windows
To open a command prompt, I have a shortcut to ("target") C:\Windows\System32\cmd.exe
And the "Start in" path is C:\Android\android-sdk-windows\platform-tools
now all I do is double-click the shortcut and I can dive right in to ADB