When I'm trying to run the app, it says:
Unable to locate adb
java.lang.IllegalArgumentException: Unable to locate adb
I've read a lot of posts regarding the missing adb.exe file and the adb.exe simply does not exist in the path .../platform-tools/adb.exe
how can I get it/fix it?
The adb.exe file will be located at your Android SDK folder, inside platform-tools
...\android-sdk-path\platform-tools\adb.exe
The default location where Android SDK is installed is:
C:\Users\<insert username here>\AppData\Local\Android\sdk\
So adb will be located at:
C:\Users\<insert username here>\AppData\Local\Android\sdk\platform-tools\adb.exe
adb is Android Debug Bridge tool that stays in Android/SDK/platform-tools directory.....
If ADB is missing you can download from this link
Platform tools by Google for Android
You need to select/install the Android SDK Platform-tools.
Go to Tools > Android SDK platform tools.
After doing this, try to build again. It should work.
If the above does not solve the problem, try reinstalling the tools: open the "Standalone SDK manager" and uninstall the Android SDK platform-tools, delete the [your sdk directory]/platform-tools directory completely and install it again using the SDK manager.
Hope this helps!
Related
Whenever I put the SDK path in the ADB section of my genymotion, I get the error message that this folder does not contain any android SDK tools. But this is the same path used by my android studio
Kenny/AppData/local/Android/SDK. Help please.
If you look at the genymotion.log file (located in ~/.Genymobile/genymotion.log), you should be able to understand what Genymotion is missing. The most common issue is that it cannot find either the adb or the aapt binaries.
If this is the case you can install them from Android Studio: open the SDK Manager, then search for "platform tools" (for adb) and "build tools" (for aapt).
unable to connect to adb.check the event log for a possible issue, verify that localhost entry is pointing to 127.0.0.1 or:: 1 for ipv4 or ipv6
Tried adb kill-server, restart, invalidate restart nothing works.
Same issue reported over here https://issuetracker.google.com/issues/130791561
Note: I have not added any file or anything in studio, it's fresh installed Studio after format a full system still issue is there.
Replace your platform-tools with this one and delete the other one.
https://dl.google.com/android/repository/platform-tools_r26.0.0-windows.zip
I was also facing this issue in android Studio 3.4 version, but now I have fixed it , if you are using windows then follow these steps:
Download Platform tools from here
https://dl.google.com/android/repository/platform-tools_r26.0.0-windows.zip
Extract downloaded zip file
Go To location "C:\Users\your_computer_user_name\AppData\Local\Android\Sdk" and Delete "Platform tools" folder
Copy and Paste, downloaded platform tool folder to above location
Now Go to your android studio and Rebuild your project Then run.
For Mac Users, follow these simple steps :
Just simply Navigate to Tools > SDK Manager> Android SDK>, then click on the Tab of SDK Tools, then look for Android SDK Platform-tools and update it.
Then the last step, Invalidate cache and restart your IDE, after that, then finally you restart your Mac. (Sometimes it's this step is unnecessary)
It will work out successfully.
Solution for Linux Users.
System info: Linux Mint Cinnamon 19.1 , Android Studio 3.4.1
Issue description: Problem with platform tools.
Solution: Remove the folder manually and update SDK tools through Android Studio.
Step 1: Go to your Android SDK installation folder. By default under your home directory. Choose platform-tools and simply delete. (/home//Android/SDK)
Step 2: Open Android Studio and go to SDK Tools. (File -> Settings -> Appearance & Behaviour -> System Settings -> Android SDK -> SDK Tools) By the moment you should be able to see Android SDK Platform Tools line unchecked.
Step 3: Put a check to install Platform Tools and press OK. Notice it'll relocate the folder to the directory where deleted.
Now that you re-installed the platform tools, restart the Android Studio and your deployment targets should show up.
If you don't install the platform tool back and ever try to build or run a project you'll get this IDE error. Just FYI :)
So that's all. Enjoy.
Happy coding
If you use Windows, you might have a corruption in api-ms-win-crt-runtime-l1-1-0.dll.
Try to update it - you can get the update from Microsoft's website.
You should check it - path/to/sdk/platform-tools and try to run adb.exe
When you update Sdk platform tools(which contains adb.exe) to release 28.0.2 and if you are using windows 8.1 then it needs few updates from windows.
As per SDK Platform tools release notes(https://developer.android.com/studio/releases/platform-tools):
Updated Windows requirements : The platform tools now depend on the Windows Universal C Runtime, which is usually installed by default via Windows Update. If you see errors mentioning missing DLLs, you may need to manually fetch and install the runtime package."
Windows update url: https://support.microsoft.com/en-ca/help/2999226/update-for-universal-c-runtime-in-windows
Prerequisite for Windows update url: https://www.microsoft.com/en-us/download/details.aspx?id=42327
Faced the exact same issue but after updating with prerequisite url first then the other url provided now it is working perfectly fine for me.
It worked for me by selecting -> Use libusb backend
This worked for me on Windows:
Goto cmd write %temp% hit enter -> delete all data from there.
Restart your Computer.
Open Android Studio now, it will work.
Clear all cache memory (related to Android Studio)
Restart ADB manually from Android Studio (first option)
Open Command prompt and got android sdk>platform-tools> adb kill-server
press enter
and again adb start-server
press enter
Restart ADB manually form Android Stidio (second option)
go to your (SDK store path) sdk>platform-tools>adb
press enter
ex. D drive > sdk>platform-tools>adb
Restart your system
Delete the platform-tools folder from the sdk and replacing with the same from your another pc. I am also facing this problem after updating to 3.4. If you face same problem please update to Android Studio 3.5 Canary Channel.
The reason is for ADB server problem. Simply re-run your adb.
(Go to your SDK folder then inside platform-tools folder you can see adb.exe. copy the path location and paste it in your computers system Environment variable. Set a new path there and paste the adb.exe file location there. hope it will solve )
If you are using Genymotion, there is an update that fix the problem.
Genymotion 3.0.2 (April 18th, 2019)
Corrections
We have fixed an
incompatibility with the adb tool bundled in the platform-tools 28.0.2
package of the Android SDK, which caused failures to start virtual
devices.
This new version of adb changed the behavior of the “adb connect
:” command by making the “port” part mandatory. This
broke Genymotion Desktop in a few places where it did not pass the
port. We have adjusted the way we call “adb connect” and also updated
the version we ship with the product to match the one in
platform-tools 28.0.2.
If non of the above answers worked for you (as same happend to me), down grade to the old version of Android Studio by following these steps:
Uninstall current Android Studio
Go to Android Studio Archive and download any older version
After installation, Open the project. You might see an error like this
This version of Android Studio cannot open this project, please retry with Android Studio 3.4 or newer.
Now, open project gradle and update classpath tools.build version. I.e. in my case Android studio version is 3.2 and classpath 3.2.1
Hope it might save someone time.
I faced this issue last night, and I tried these methods to fix:
download older platform-tools and place it in the android sdk folder.(not work for me)
adb kill-server, adb start-server.(not work for me, adb had no response with these cmd)
kill the process that occupies port 5037.(for me, there is no other .exe run at this port)
reinstall platform-tools in Android Studio.(not work)
download ADB Kits and replace them in platform-tools folder.(work!!!)
It seems that my adb file has been modified or replaced by some programs. You can try these methods, and I hope some of them can work for you.
I had this issue only after a Genymotion update, on Mac.
What worked for me: Open Genymotion preferences, Select ADB, choose "Use custom Android SDK tools" and points to your Android SDK folder.
Actually the problem is not with the android studio version 3.4
Problem is with the android platform tools version which is latest one 29.
So install the previous version of the android platform tools version it will solve your problem. as above #Ved mentioned.
Ved link:
https://dl.google.com/android/repository/platform-tools_r26.0.0-windows.zip
EndTask adb.exe from Background processes (TaskManager) and Run Application again.
It works for me
I have just downloaded the Android SDK Command Line tools for Windows (26.0.2). I am attempting to download selected SDK components using \tools\bin\sdkmanager.bat, as well as updating \tools. The installation fails with the following message:
Warning: An error occurred during installation: Failed to move away or delete existing target file: C:\testinstall\sdk\tools
Move it away manually and try again..
I don't see how I can remove \tools manually because it contains \bin\sdkmanager.bat.
Screenshot of the sdkmanager command:
All other components appear to install without error. See below for the components specified in my package file:
Yeah that's quite funny. A way to do that is to copy the tools folder to another place (let's say C:\temp\). Then direct into the C:\temp\tools\bin\, open the cmd prompt there and run your update commands as such:
sdkmanager.bat --sdk_root=sdkRootPath --command
Where sdkRootPath is path to your original SDK folder (C:\testinstall\sdk\). Once that is done, delete the C:\temp\tools\ copied folder.
You could temporarily rename to tools.old, run it to install new version in tools and then remove the old one.
cd YOUR-ANDROID-SDK-LOCATION
ren tools tools.old
tools.old\bin\sdkmanager.bat "tools"
dir tools*
del tools.old /q /s
tools\bin\sdkmanager.bat --list
it might be permission issue.Can you try doing sudo or if you on windows try to run terminal as administrator.
I have seen issues where the program is not able to delete the folder either due to lock or some weird reason.
Run cmd in root c:.
c:\>testinstall\sdk\tools\bin\sdkmanager --package_file=c:\testinstall\packx.txt
I've had the same issue on windows, I couldn't even rename the directory that is causing the issue.
I found out that adb was still running and ended the process and update/install worked fine without workarounds.
The below command helped me to extract the SDK
sdkmanager "platform-tools" "platforms;android-28" --sdk_root=C:\AndroidSDK_RootLocation
It may not be the answer to your question but now, i can't exactly remeber the version, you can't update SDK tools directly or using Eclipse, sdk Manager, sdk.bat or android.bat, only way is to update them using Android Studio. It's Google's new policy, i read it somewhere, if i find the link i will share it
My solution was as following:
Delete the Android SDK Tools via Android Studio (although it might complain it failed).
Close Android Studio
Manually delete tools folder from C:\Users\<MyUsername>\AppData\Local\Android\sdk folder
Start Android Studio and then do the install of the Android SDK Tools via Android Studio.
After updating android sdk to 25.3.1, can't open sdk manager from Eclipse. Tried with SDK Manager.exe nothing happened. Then found on batch file:
The android command is no longer available.
For manual SDK and AVD management, please use Android Studio.
For command-line tools, use tools/bin/sdkmanager and tools/bin/avdmanager
Then tried with tools/bin/sdkmanager, still nothing.
My java path is ok as it was working fine just before the update.
I'm using Android Studio but here is a command you might try (it works for me):
<64-bit jre home>\bin\java "-Dcom.android.sdkmanager.toolsdir=C:\programs\Android\android-sdk\tools" "-Dcom.android.sdkmanager.workdir=C:\programs\Android\Android Studio\jre\jre\bin" -classpath "lib\sdkmanager.jar;lib\swtmenubar.jar;lib\x86_64\swt.jar" com.android.sdkmanager.Main sdk
Replace the toolsdir and workdir VM params with your own values. Possibly you will need to locate tools like unpack200.exe in your sdk which are probably used when unpacking new components, and use that directory as workdir. Alternatively, just copy that directory from an Android Studio install.
You must execute it in your tools directory located in the android sdk, i.e.
C:\programs\Android\android-sdk\tools>
Then again, it's probably easiest and more future-proof to just install Android Studio and open the SDK manager from there ;)
I had this problem today, I used the command
.\android list target
in folder
C:\Users\<your name>\AppData\Local\Android\sdk\tools
from powershell
left CTRL + left SHIFT + right-click > Open PowerShell window here
Not sure what I'm doing wrong here. I installed the Android SDK Manager, and am now trying to install a platform like the Android Dev website suggests. Once I clicked install I got an error stating that the Manager could not create a temp folder within the Android directory. So I created it. Now I'm getting this error:
Downloading SDK Platform Android 2.3,
API 9, revision 1 File not found:
C:\Program Files
(x86)\Android\android-sdk-windows\temp\android-2.3_r01-linux.zip
(Access is denied)
There is also a little message under the progress bar that says "Done. Nothing was installed."
I'm running Windows 7 Ultimate, in case that's of any use.
Try running Android Studio as an administrator, by right-clicking on the .exe and selecting "Run As Administrator".
Also, some anti-virus programs have been known to interfere with SDK Manager.
I was getting a similar permission issue and SDK Manager could not download and install new components. Error message was (I'm running Android Studio (I/O Preview) 0.2.9)
"Unable to create C:\Program Files
(x86)\Android\android-studio\sdk\temp"
Although solution was infact what #william-tate's answer says, I could not run the 'SDK Manager' directly. It fails with message:
Failed to execute tools\android.bat
The system cannot find the file specified.
Instead I ran the 'tools\android.bat' as Administrator, which in turn launched SDK Manager with same permissions which fixed the issue.
Hope this helps for someone who faces the issue I faced.
In Mac OS X (tried with Android Studio), do the following in Terminal
cd /android/adt-bundle-mac-x86_64/sdk/tools
sudo ./android sdk
This launches SDK manager as admin. Now update/install the packages from SDK manager and it'll work.
For Android Studio, selecting "Run As Administrator" while starting Android Studio helps.
In my case I had to specify proxy settings in Tools->Options.
I had same problem when I try to install it on my pc (Win7, 64-bit system). I had an error message shown in figure below. But when I check my local folder 'C:\Users\username\AppData\Local\Android\sdk', the Android SDK is already there. Somehow Android studio could not see/link it.
So please check first whether you can find the Android SDK in the local folder. If yes, just follow the next steps.
Chose 'Cancel' and click on 'X' on the top right corner.
Chose 'Do not re-run the setup wizard' and click 'OK'
Start Android Studio again and go 'Configure'-->'Project Defaults' --> 'Project Structure'
Add 'C:\Users\username\AppData\Local\Android\sdk' to 'Android Location' and click 'OK'
Click on 'Start a new Android Studio project'.
Hopefully it helps.
I had a similar issue - very slow xml downloads followed by an empty package list. The SDK, it seems, was trying to use legacy Java installation. Setting the JAVA_HOME to the 1.6 jdk did the trick.
In my case I was using Windows 7 with the 64-bit OS. We installed the 64-bit Java SE and 64-bit ADT Bundle. With that set up, we couldn't get the SDK manager to work correctly (specifically, no downloads allowed and it didn't show all the API download options). After trying all of the above answers and from other posts, we decided to look into the Java set up and realized it might the 64-bit configuration that's giving the ADT bundle grief (I vaguely recall seeing/reading this issue before).
So we uninstalled Java 64-bit and reinstalled the 32-bit, and then used the 32-bit ADT bundle, and it worked correctly. The system user was already an admin, so we didn't need to "Run as Administrator"
For those running SDK Manager in Eclipse, selecting "Run As Administrator" while starting Eclipse.exe helps.
For Linux/ubuntu User
Why it's happening?
due to lock icon on some folder(not having read/write access) in
"/yourpath/android-studio-SDK"
Sort and sweet solution
-Open Terminal (Ctrl +alt +t)
-copy pest sudo chown -R $USER: $HOME
-wait for a while.....
-now Try again to update your SDK
Happy Coding :)
The Access denied is because Windows doesn't give the default write and modify permission to the files in its install drive viz. c:
To resolve this issue I usually use a separate drive or in your case, you need to set the access rights to the specific folder in the options
right click -> options > security -> edit
In windows 8:
right click on windows button
List item
CDM as administrator
Press 'yes'
paste this $ C:\xxx\xxx\AppData\Local\Android\sdk\tools\android.bat
If you use SDK Manager in Eclipse:
Option 1: Right-click on eclipse.exe and select "Run As Administrator".
Option 2: If you don't want to start Eclipse.exe as Administrator just install/copy Eclipse installation files from "C:\program files\Eclipse ADT Bundle\" to some unprotected folder, like "D:\android\". Run "D:\android\eclipse\eclipse.exe", select menu item "Window => Preferences => Android" and change "SDK Location" to "D:\android\sdk\". After that you'll be able to install new packages in Android SDK Manager.
go to sdk folder and right click on SDK manager and run with administrator and enjoy installing.
To go along with what v01d said:
Using Android Studio for Mac OS X, the SDK folder could also be at /Users/{user}/Library/Android/sdk, where {user} is your username.
To find out where the partial SDK installation is, go to Configure > SDK Manager in Android Studio, then click edit at the top. This should pop up a window and show the location.
Copy this path and paste it front of the cd command in a terminal. Finally execute sudo ./android sdk to launch the standalone SDK manager.
EDIT (July 14, 2016):
The "android" binary file could also be at /Users/{user}/Library/Android/sdk/tools.
Solution for macOS
click right on AndroidStudio.app -> show Package Contents -> MacOS
now drag & dropping the studio-executable in a terminal
sudo! (Ctrl+A places your cursor in front)
start the SDK Manager inside AS to get your stuff (you will have root access)
https://www.youtube.com/watch?v=ZPnu3Nrd1u0&feature=youtu.be
you need 3 steps:
1- Configure -> "Appearance and Behavior" -> System Settings -> HTTP Proxy. I selected
"Automatic proxy configuration url:"
2-Delete your ~/.Android* folders (c:\users\ur user).
3-Run Android Studio. It will show you a welcome wizard where it tries to download the SDK again.