“Unable to find a userdata.img file for ABI armeabi…”

Question

Once again I\'ve made the mistake of updating Eclipse with the latest Android SDK/tools and have rendered it useless.

Running Eclipse on a Mac.

When I try to

Answer 1

I had the same problem and this is how I solved it:

In Eclipse:

1. Window > Android SDK Manager
2. Select ARM EABI v7a System Image
3. Install package
4. Done. You should be able to create your AVD now.

Good luck!!

Answer 2

It can be solved from command line by running:

update sdk -u -a -t android-16,sysimg-16

Answer 3

In my case it was related to "No system images installed for this target" even though Image is installed.

Following this answer, I moved c:\adt\sdk\system-images\android-23\default\x86 up one folder to c:\adt\sdk\system-images\android-23\x86, and after that I got the error:

Unable to find a userdata.img file for ABI armeabi...

On a hunch, I created a symlink/junction to the original folder, and it worked. I used this:

mklink /j "c:\adt\sdk\system-images\android-23\default\x86" "c:\adt\sdk\system-images\android-23\x86"

It's just that you need it in both folders. I used a junction instead of simply copying the folder so as not to waste space.

Answer 4

Step 1) Open Eclipse and click on Run Configurations (pull down the arrow next to the Run or Debug button).

Step 2) Select "Android Application" and click "New"

Step 3) Select the "Target" tab and select "Automatic" (Click once more even it is selected and the list box below is disabled"

Step 4) Click on the "Manager..." button

Step 5) In all the "Android 4.0.X" sections, select "ARM EABI v7a System Image" checkbox

Step 6) Click the "Install X Package..." button

Reference: http://tech.thecoolblogs.com/2012/01/unable-to-find-userdataimg-file-for-abi.html#ixzz1u2EMZGt7

Answer 5

Now with Android 4.1 (API 16), make sure you install the ARM EABI v7a System Image in the Android SDK Manager. This works perfectly in Eclipse Indigo on Mac OSX.

Answer 6

Solved a problem after I realized that newly created AVDs were being saved in user folder (user foo) C:\HOME\foo and Android plugin was trying to find them in C:\Users\foo.

I have set environment variable (this will change save avd folder).

ANDROID_SDK_HOM=C:\Users\foo

Make sure you create your AVD again since you have changed save location now.

That solved a problem, I assume the proper way would be to set look-up folder but could not figure out how to change that.