Emulator on Android Studio doesn't start after SDK tools update to 25.3.1

Question

After updating my Android SDK tools today to 25.3.1, the emulator won\'t run anymore.

I can open the AVD Manager. When I hit \"Play\" on one of the emulators on the

Answer 1

My problem was ANDROID_SDK_HOME pointing to d:\.android instead of d:\. Could not find the images anymore.

Answer 2

Have you check the Android emulator installed in the **SDK Tools?

Go to Setting-> sdk-tools.

See whether Android is installed or not.

I have face same problem. when I checked the SDK Tools, I found that the Android emulator was not installed.

Answer 3

This worked for me:

Go to AVD Manager, then, in the Actions column, click on the arrow that points dawn and select "Wipe Data". After this, try to run the emulator.

Answer 4

It's been driving me nuts for the last few days. Here's what worked for me:

ANDROID_HOME, ANDROID_SDK_ROOT variables in "System Environment Variables" were different from Android Studio -> Settings -> Android SDK Location. So when I changed the environment variables, AVD started!

(After changed the environment variable, you should restart the Android Studio)

Answer 5

I ran into the same problem after upgrading. I can't figure out what's causing the configuration problem but I did figure out a workaround.

First, I tried to launch the emulator from the command line:

$ emulator @<name_avd_image>
emulator: ERROR: This AVD's configuration is missing a kernel file! Please ensure the file "kernel-ranchu" is in the same location as your system image.
emulator: ERROR: ANDROID_SDK_ROOT is defined (<android>/sdk) but cannot find kernel file in <android>/sdk/system-images/ sub directories

You can get more information if you run emulator with the -verbose flag. I tried re-installing the system image (e.g. Android API 25 x86 w/ Google APIs), Android Emulator 25.3.1, and re-creating the AVD but nothing worked.

Finally as a workaround, I just copied all of the system files from the SDK system images directory into the AVD directory:

Example: Pixel XL (Android API 25 x86 w/ Google APIs)
SOURCE: <android>/sdk/system-images/android-25/google_apis/x86/
DESTINATION: ~/.android/avd/Pixel_XL_API_25.avd/

After that the emulator started right up. It's not ideal, but this was blocking my development so I had to get the emulator up and running again. I hope someone else will be able to figure out what broke in the configuration.

---

UPDATE: Figured out the configuration problem!

I noticed I periodically was seeing the console error "Your emulator is out of date, please update by launching Android Studio:" so I decided to check:

$ which emulator
<$ANDROID_SDK_ROOT>/tools/emulator

With help from this thread:

The problem is there are two emulators: one in $ANDROID_SDK_ROOT/tools, another one in $ANDROID_SDK_ROOT/emulator. The one in $ANDROID_SDK_ROOT/tools cannot start. Place $ANDROID_SDK_ROOT/emulator before $ANDROID_SDK_ROOT/tools in your $PATH variable, it should fix the problem.

NOTE: For most Mac users, you can edit your ~/.bash_profile to change these settings and then run $source ~/.bash_profile to load the updates. In my particular case, I also had old values for $ANDROID_HOME that I had to clear out.

Answer 6

The solution is: Tools - Android - Sdk manager tab Sdk tools install emulator 25.3.1