I just installed Android Studio, when I run the Android Emulator it says: “To Start Android, enter your password” and it reminds me the password is wrong”.
How can i fix it?
I would be very glad if someone has an answer for this
Wiping data in Android Virtual Device Manager works for me.
Tools -> Android -> AVD Manager -> Actions (triangle down) -> Wipe Data
Hyosoo Kim is right about the problem (non-ascii characters in the user directory), but I think this is an easier solution :
Add a new User Environment Variable :
Control Panel -> System -> Advanced System Settings -> Environment Variables
Add a new user variable
Name : ANDROID_SDK_HOME
Value : the path to a directory not in your user home (C:\Android for example)
There you go !
I had this problem on my Visual Studio 2017 Community development setup and here is how I solved it:
- Shut down the AVD if it’s running.
- While in the Android Device Manager, select the AVD with the problem.
- Right click or select the context sensitive menu and select “Factory Reset”.
- Start the AVD again and it should boot normally.
*Just be sure that all the data you’ve saved on the AVD will be lost once you factory-reset it.
In VS2017 version 15.9.3,perform the following steps :
- Open **Tools > Android Device Manager ** and search the device that you debug
- Click with Right Click on it
- Choose “Factory Reset”
- And you will get brand new device, ready to debug.
If your user directory contains non-ascii characters, then try to change user name to English name.
I had same problem and it was solved when I logged on to root account.
My case was the described by Hyosoo Kim. I solved the problem renaming my user profile folder (following these intructions Change the Name of a User Profile Folder in Windows 10) and deleting the folder .android under my profile folder.
I had the same issue but was using Visual Studio 2017 and Xamarin rather than Android Studio. Doing a Factory reset in the Android Device Manager in Visual Studio didn’t work for me.
So I installed Android Studio and as per Yao’s answer, launched the AVD Manager from in there then selected ‘Wipe Data’ from the triangle dropdown. This resolved the issue and I was able to use the emulator from within Visual Studio again.
The Android Device Manager in Visual Studio seems to be missing some features compared to the one in Android Studio, so this solution is the only one I could find that worked.
I had this issue when trying to use the x86_64 processor, even when I created a brand new device. Using the x86 processor in the device properties resolved the issue for me.
Setting the ANDROID_SDK_HOME as described in a previous answer didn’t work for me (although it did start using the folder I specified, placing a new
.android folder there and using it)
Neither did doing a Factory Reset by right-clicking on the device in the Android Device Manager in Visual Studio 2019.
The only thing that worked for me was making sure that the checkbox for Google APIs was checked, and making sure it was on x86 of course; selecting x86_64 grays out the two checkboxes.
Note that it doesn’t matter whether I use a Pixel or some other device such as a Nexus; it apparently always needs to use the image with the Google APIs.
- Shutdown the AVD (if it’s running).
Go to the config file of this AVD, The default location is the following (where
AVD_NAMEis the AVD name, and
USERis your system user):
- Mac and Linux:
C:\Documents and Settings\USER\.android\AVD_NAME.avd\config.ini
- Vista –
- Mac and Linux:
Remove any blank line from the beginning and the end of the file.
- Finally, run your AVD directly from the AVD Manager.
hope this helps.
This solution working for me on VS2017/Xamarin
- Turn Off your device
- Open MS-DOS console
- Start your device with following command:
emulator.exe -verbose -feature WindowsHypervisorPlatform -avd
“My_device_name” -prop emu.uuid=”your_id” -skip-adb-auth -wipe-data
- Turn Off your device (no more password is needed)
- Launch your device with ‘Android Device Manager’
More information will be available in your log file:
See most recent file here:
There’s a “uuid” which contains the password.
uuid = 1568486155483
1568486155483 is the password.
Worked 4 me 🙂