34

I just installed Android Studio, and I am very new with this program.

So when I run the Android Emulator it says: "To Start Android, enter your password", although I have never set a password. When I just enter a word with 4 letters it says "The Password you entered is correct, but unfortunately your data is corrupt".

After that, I have to Reset the Phone, but when I do that the same menu with "To Start Android, enter your password" appears.

Maybe it is just an easy mistake, but as I said I am new with this. I also did some research on the internet but I did not find anything useful.

this is the 2 images that it showe me:

1)the first image 2) the seconde image

and after i clicked on reset phone, nothing happened.

I would be very glad if someone has an answer for this.

Asaf Cohen
  • 341
  • 1
  • 3
  • 6

12 Answers12

35

This is a late response, but thought this simple fix might help anyone else who comes across this problem in the future. What worked for me is the following:

In VS2017 ==> Tools ==> Android ==> Select: Android Device Manager

In the Android Device Manager window, you'll see your Android Emulator.

  1. Make sure the far right column contains the button "Start" (if "Stop" appears, click "Stop")

  2. Right Click the device, and select the "Factory Reset" option in the menu.

Your emulator should now be working. Good luck.

James Lee
  • 754
  • 8
  • 13
7

open AVD and right click on the emulator choose ->Wipe data option.

dhanasekar
  • 1,228
  • 13
  • 16
4

Check that your avd folder path doesn't include national symbols (in my case it looked like C:\Users\Пользователь\.android).

After I changed this path everything is working. See this post of how to change path: Possible to change where Android Virtual Devices are saved?

Sergey Stasishin
  • 291
  • 2
  • 10
2

Check out "Viewing and managing your Avds" part. Try wiping data of your emulator or create a new emulator for yourself.

https://developer.android.com/studio/run/managing-avds.html

Hasan Saykın
  • 138
  • 1
  • 8
1

enable GoogleAPIs and Google Play Store

aka579
  • 11
  • 1
1

Change the Android version. I was creating an emulator with Oreo 8.1 and got stuck in with the same issue. I created another with Marshmallows 6.0 and no more asking for password. Then if you are using Oreo 8.1 try with antoher.

Wille Esteche
  • 1,689
  • 1
  • 10
  • 7
0

I created a virtual device, and after, I had to reinstall the emulator. When I booted the virtual device, I got this issue. I deleted it and made a new one, and it worked fine.

0

Just go the AVD Manager and Wipe Data. The problem will be solved.

Yash
  • 1,787
  • 1
  • 22
  • 23
0

Here are the steps I followed after my device corrupted.

  • Close your emulator

  • Open AVD manager, right click on your device and click "Cold Boot Now" button.

Badiparmagi
  • 1,285
  • 1
  • 14
  • 24
0

Sorry for a very Late Answer. But you can't create a x64 Virtual Device on x64 System. Your device needs to be x86.

  • 1
    Shouldn't that be "you can't create an x64 virtual device on an x86 system"? – Wai Ha Lee Apr 10 '19 at 20:17
  • That too. But x64 on a x64 can't be created either. Only In case if your CPU allows Hardware Virtaulization (and is enabled in BIOS), then you can. – Muhammad Tayyab Apr 10 '19 at 21:52
  • I'm not familiar with your field, but surely creating an x86 VM on an x64 system is easier than an x86 VM on an x64 system? And likewise, are you saying you can **only** create an x64 VM on an x86 system? That sounds back-to-front. Could you provide some documentation for this? I'd be interested to read into why that is. – Wai Ha Lee Apr 10 '19 at 21:58
0

Just a warning to anyone getting this error on an emulator instance that was working and you cold booted or something. I got this error and just stopped and cold booted again and it was gone! So try that first before wiping your emulator instance unnecessarily.

georgiecasey
  • 21,793
  • 11
  • 65
  • 74
0

Deleted the device in the Device Manager and created a new one with a higher OS version (Oreo -> Pie). The error disappeared. Did not find the real reason yet.

ywwy
  • 124
  • 1
  • 2
  • 18