After my Visual Studio install suddenly lost the ability to deploy my Xamarin app to an android emulator, I decided to uninstall EVERYTHING (Visual Studio, Xamarin, Android SDK) and start over.
Everything has been re-installed, but the Android SDK does not include the adb.exe file. The place where I expect to find it is here:
C:\Users\costcopc\AppData\Local\Android\android-sdk\platform-tools\adb.exe
What went wrong? How can I fix this?
I opened a cmd.exe prompt and searched the entire drive (C:>) to find the file - it doesn't exist.
In case it helps, I will retrace my steps...
I un-installed Xamarin first, according to instructions. I wanted a blank slate so, per those instructions, I also uninstalled:
I did not uninstall the Java SDK because, as my very first link explained, I had already used a system restore point to recover a stable version of the Java SDK.
Next up was Visual Studio. I used its installer for the uninstallation, and then I followed the post-uninstall "Secondary installer" instructions it gave.
I re-installed VS 2015 first, then I launched the Xamarin Studio installer, which in turn installed the Android SDK for me:
With everything seemingly installed successfully, I launched Visual Studio and tried to open the Android SDK Manager with Tools -> Android -> Android SDK Manager.
It worked, but I noticed that a cmd.exe window opened and remained opened, containing a couple strange error messages.
There it is: "The process cannot access the file because it is in use by another process."
Despite the anomalies, I did use the SDK manager to install 4 more packages.
Still, I was feeling uneasy about the error messages so I figured it was time to reboot. After the reboot the situation became worse. Before, Visual Studio was at least able to launch the android SDK manager. Now it was altogether unable to launch it:
That oddball SDK path C:\Users\costcopc\AppData\Local\Android\ANDROI-1
had disappeared!
Xamarin Studio was also unable to launch the SDK Manager:
Now I chose to execute a Xamarin Studio installation "repair." Xamarin acted like the Android SDK was installed, and so it did nothing to fix it.
Again, what can I do to fix this?
The executable of ADB, adb.exe, can be found under Android SDK's child folder, platform-tools/. For example, in my case, it is under C:UsersChunyenAppDataLocalAndroidsdkplatform-tools. I recommend you add your folder path to the evironment variable.
Reinstalling the platform tools might fix this problem. Open Android Studio, click SDK Manager in the toolbar or click Tools > SDK Manager, click SDK Tools, then uncheck Android-SDK Platform-Tools (as shown above). After this, open C:\Users\Username\AppData\Local\Android\Sdk and delete the platform-tools folder.
“ADB device not found” may be caused by a missing Windows driver for your Android device. To fix it, install the driver using the device manager. Make sure to enable unknown source and enable developer (See solution 1 step 1 and 2).
I solved this issue by selecting Tools/Xamarin Account in VS 2017RC.
Then the browser opens, go into your account and download and install Xamarin from here.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With