Android Emulator Sd Card Image Already In Use

I have followed the answers from this question without success. I could not respond to the posted answer (lack of reputation) so I had to make a new question. Purging all adb pro

Solution 1:

Delete lock pid files?

I am on Windows7 and was having the same problem with the SD Card image, as well as general problems with Eclipse not wanting to connect with the Adb. The state seems to get out of sync.

In windows, there are lock files. In my case (environment, if you will) it is C:\Users\joe\.android\avd\Em22.avd\xxx\pid

where xxx are:

• cache.img.lock
• hardware-qemu.ini.lock
• sdcard.img.lock <<<---
• userdata-qemu.img.lock

When the state of eclipse seems lost, I shut everything down, and delete the pid files in the lock directories. It did the trick in at least one occasion where Eclipse would not connect with adb, and when it did, complained about locked sd card image.

Ooops, I just noticed it has the same answered in link in original question.

Solution 2:

Here is the solution, 1) Open Task Manager. 2) Close all the running emulators from list. 3) Close bluestack programs if running any. 4) Now you are done. You can now run New emulator.

Solution 3:

The sdcard image should be a writeable FAT32 image file. See this link

It seems you are using an ISO image.

If you really suspect there's another process (emulator) using a specific sdcard image you can confirm it by running

$ fuser ~/.android/avd/4.0.3.avd/sdcard.img 

~/.android/avd/4.0.3.avd/sdcard.img:90719

in this case there's an emulator running (or something else having the file opened) (pid 90719).