This question already has answers here:
adb server is out of date. killing [duplicate]
(4 answers)
Closed 5 years ago.
I'm currently experiencing a few issues using ADB with Debian Stretch. Whenever I issue an ADB command, I get the following message:
$ adb root
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
Normally this doesn't cause any issues other than a 2 second delay while the ADB server restarts, but when I'm using adb shell the connection will occasionally drop, which is annoying. Note that this is different to other questions such as this one as the server version is greater than the client version.
This problem was caused by me having ADB installed twice on my machine. Once in my home directory (used by Android Studio), and again in /usr/bin/adb as I had the android-sdk package installed from aptitude. As Debian tends to be a bit slow with package updates, adb from the command line was calling the older version at /usr/bin/adb rather than the newer version in my home folder. This issue was solved by running:
sudo apt-get remove adb
Related
This question already has answers here:
adb server version doesn't match this client
(41 answers)
Closed 4 years ago.
When I click "run" on the top right corner to launch my basic "Hello World" application, my device isn't recognized, and if I set the configurations to give a popup to select either an AVD or a connected device, I get the following errors:
7:34 PM adb server version (39) doesn't match this client (40); killing...
7:34 PM could not read ok from ADB Server
7:34 PM * failed to start daemon
7:34 PM error: cannot connect to daemon
7:34 PM 'C:\Users\<MyName>\AppData\Local\Android\Sdk\platform-tools\adb.exe start-server' failed -- run manually if necessary
Developer mode and USB debugging is enabled on my phone, and I have the latest Gradle installed. I believe my Path variables are set correctly and the android SDK, Gradle, and JVM paths are all correctly set in IntelliJ.
Try using command line to connect device.Firstly plug in usb cable,then run below commands:
adb kill-server
adb devices
And check whether usb cable line work normally.
This is because you are running 2 different versions of ADB.
Run adb kill-server and then C:\Users\<MyName>\AppData\Local\Android\Sdk\platform-tools\adb.exe start-server
Add C:\Users\<MyName>\AppData\Local\Android\Sdk\platform-tools\ to the beginning of your environment path.
Also, there is already a discussion here: adb server version doesn't match this client
This question already has answers here:
adb server version doesn't match this client
(41 answers)
Closed 4 years ago.
I'm on debian buster.
I have genymotion installed and running, and a CRNA app that I'm trying to run. I have Android SDK installed, and set properly in my path.
I have changed the genymotion settings to point to my Android SDK folder.
When I do yarn run android I see
error: could not install *smartsocket* listener: Address already in use
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
When I do adb start-server I see
adb server version (39) doesn't match this client (36); killing...
error: could not install *smartsocket* listener: Address already in use
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
I have run adb kill-server, and manually killed and restarted the ADB process many times. Every fix I've found to this issue does not work.
Is there something I'm missing? Is there some comprehensive guide on setting all of this up? I'm willing to do a fresh install if I have to.
Glad that I was able to help you. :)
As suspected, the machine contains two different versions of adb installed, one by the Android SDK, and another installed probably with another tool or program which contains adb packaged with it (maybe the fastboot tools). With two versions being executed at different times, the adb server would complain with errors as posted in your question.
Although you were able to solve this by setting genymotion to use the installed tool's adb, it is advised to actually uninstall the tool and configure the environment variables (PATH and ANDROID_HOME) to include the adb that came with the Android SDK. This modification would be needed if you would be considering to use more tools that depend on adbsuch as Android Studio or others.
This question already has answers here:
adb server is out of date. killing [duplicate]
(4 answers)
Closed 5 years ago.
I cannot resolve this issue:
I start an emulator, run adb devices and this happens, thus killing my emulator that was running -
~/Android/Sdk/platform-tools$ adb devices
adb server is out of date. killing...
* daemon started successfully * List of devices attached emulator-5554 offline
I am running 1.0.32 w/ Ubuntu 16. I have tried installing ADB once again, bit it does not help. Solutions?
It's because you have two adb servers running. The first is started by the emulator, probably from $HOME/android-sdk-linux/platform-tools directory. The second adb server is when you run adb by hand.
The adb from the command line will try to connect to the server (started by the emulator). As the server is not what the client expects, it kills the server and starts his own.
Don't start the default adb by hand, run $HOME/android-sdk-linux/platform-tools/adb. It will work.
This question already has answers here:
adb server version doesn't match this client
(41 answers)
Closed 5 years ago.
After installing the Android O preview on a test device my ADB stopped working and started giving me this error.
adb server version (36) doesn't match this client (39); killing...
adb E 03-27 08:01:55 2925 147690 usb_osx.cpp:333] Could not open interface: e00002c5
adb E 03-27 08:01:55 2925 147690 usb_osx.cpp:294] Could not find device interface
error: could not install *smartsocket* listener: Address already in use
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
The only answers I have come across on this issue referred to Genymotion being out of sync with ADB but I don’t use Genymotion. Any help would be greatly appreciated. I have already wiped and reinstalled Android Studio as well as all of its tools and settings yet seem to still have this issue.
This works for me...
go to GenyMotion settings -> ADB tab
instead of Use Genymotion Android tools, choose custom Android SDK Tools and then browse your installed SDK.
In my case this error occured when I set up my environment adb path as ~/.android-sdk/platform-tools (which happens when e.g. android-platform-tools is installed via homebrew), which version was 36, but Android Studio project has Android SDK next path ~/Library/Android/sdk which adb version was 39.
I have changed my PATH to platform-tools to ~/Library/Android/sdk/platform-tools and error was solved
The main point that all the others have missed, is that you will get this error when you have a running adb process in the background. So the first step is to find it and kill it:
ps aux | grep adb
user 46803 0.0 0.0 2442020 816 s023 S+ 5:07AM 0:00.00 grep adb
user 46636 0.0 0.0 651740 3084 ?? S 5:07AM 0:00.02 adb -P 5037 fork-server server
When you find it, you can kill it using kill -9 46636.
In my case, the problem was an old version of adb coming from GapDebug. If you got this with GapDebug, get out of it and then do
adb kill-server
adb start-server
because with GapDebug in the background, when you kill the adb server, GapDebug will start its own copy immediately, causing the start-server to be ignored
I had the same problem with Android Studio - adb server version (37) doesn't match this client (39). I fixed by the following solution :
In Android Studio go to Tools -> Android -> SDK Manager
In the SDK Tools tab untick Android SDK Platform-Tools, click Apply to uninstall.
I then renamed the folder Platform-Tools to Platform-ToolsOld
Then back in the SDK Manager re-tick the Platform-Tools to re-install.
As mentioned by others here, that you could have two adb's running ... And to add to these answers from a Linux box perspective ( for the next newbie who is working from Linux );
Uninstall your distro's android-tools ( use zypper or yum etc )
# zypper -v rm android-tools
Find where your other adb is
# find /home -iname "*adb"|grep -i android
Say it was at ;
/home/developer/Android/Sdk/platform-tools/adb
Then Make a softlink to it in the /usr/bin folder
ln -s /home/developer/Android/Sdk/platform-tools/adb /usr/bin/adb
Then;
# adb start-server
I had the same error. In my case, using Appium, I had two versions of ADB
$ /usr/local/bin/adb version 36
and
$ /Users/user/Library/Android/sdk/platform-tools/adb version 39
The solution was:
be sure that your $PATH in bash_profile is pointing to: /Users/user/Library/Android/sdk/platform-tools/
stop the adb server: adb kill-server and check Appium is stopped.
delete the adb version 36 (or you can rename it to have a backup): rm /usr/local/bin/adb
start adb server: adb start-server or just starting Appium
You have two versions of ADB
$ /usr/local/bin/adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
and
$ /Users/user/Library/Android/sdk/platform-tools/adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
You could see which one your PATH is pointing to (echo $PATH) but I fixed it with a adb stop-server on one version and a adb start-server on the other.
To add yet another potential solution, Helium by Clockworkmod has it's own version of ADB built in that kept being started. Exiting the Helium Desktop application resolves the issue.
I think you have multiple adb server running, genymotion could be one of them, but also Xamarin - Visual studio for mac OS could be running an adb server, closing Visual studio worked for me
This question already has answers here:
adb server version doesn't match this client
(41 answers)
Closed 5 years ago.
I'm creating my first react-native project with this tutorial: http://facebook.github.io/react-native/
When it comes to executing code and running react-native run-android I am getting:
adb server is out of date. killing...
* daemon started successfully *
And the app on the android device is obviously not working.
I've reinstalled the SDK, tried to adb kill-server and adb start-server, but nothing seems to work
I'm using Android 4.4 and Ubuntu 14.04
Open Android Studio, and then update all your build tools, install the SDKs that you need for your device and ensure that have you set ANDROID_HOME env var to the same dir that you have in Android Studio (commonly in /home/you/Android/Sdk), also update react-native-cli node package. Run adb kill-server and adb start-server.
Probably you will have problems with adb version, just change your bin:
sudo cp ~/Android/Sdk/platform-tools/adb /usr/bin/adb
sudo chmod +x /usr/bin/adb
In the latest adb update the adb server is out of date. killing... message has been replaced with more informative adb server version (%d) doesn't match this client (%d)
So this solution is applicable to both.
The root cause of the error is that your system has multiple adb binaries of different versions) installed. These adb binaries may come from different sources - distributed together with some development tools or even installed from your linux distribution official repository. I would strongly advise against using any of those sources. The official source of the most recent version of adb is the platform-tools package from the Android SDK. The adb tag info page contains the direct links to the package.
So if you have Android SDK already installed - just update the platform-tools package to the latest version using SDK Manager. If not - download and unpack the contents of platform-tools.zip file for your platform to a folder. Add that folder to your $PATH. Now kill all running adb processes and make sure to find all other copies of adb and delete them. In rare cases some software might stop working. In that case you would need either change that application's internal setting telling it where to find the new binary or if the application uses hard-coded adb location - just create a symlink to the new location.
That's it. No more server/client version mismatches. Although you might need to repeat the procedure after installing another software which comes prepackaged with its own adb copy.
It might be that you installed the adb package in addition to the SDK's. In that case, a
sudo apt purge adb
might solve the problem.
I'm getting this error using ADB (1.0.32) and Genymotion (2.8.2). My solution was change the ADB of the VM, from my local Android SDK's ADB to Genymotion ADB (default).