Android Emulator - "Encryption unsuccessful"

Question

Almost every time I try to open the emulator is giving me this error after a long loading pause.

I have tried to fix it by reinstalling the SDK, but no luck.

Note: I must say that I am new to Android.

This is happening because your phone is still trying to use your internal sdcard, but it isn't accessible. You will need to trick your phone to use the external sdcard as if it was the internal. — John Joe, May 20 '17 at 17:17
If you are using Xamarin Visual Studio the "Factory Reset" option also works — Mauricio Gracia Gutierrez, Nov 01 '18 at 19:20

score 46 · Accepted Answer · answered May 25 '17 at 19:51

46

Wiping data in Android Virtual Device Manager helped me in my case.

Tools -> Android -> AVD Manager -> Actions (triangle down) -> Wipe Data

There is also Advanced settings in virtual device's configuration (the pencil) where is a configuration of SD card and internal storage, but I didn't have to change it.

answered May 25 '17 at 19:51

maresmar

1,449
14
21

1

Thank you. It worked! However, it is still booting extremely slow. – Cristiana Dumitru Jun 02 '17 at 07:44
1

@CristianaDumitru You're welcome, Android emulator is terribly slow - it's always better to use a real device. Check if you use x86 (or x86_64) version of an image in the emulator, it's faster than ARM version. – maresmar Jun 03 '17 at 18:01
1

Using Visual Studio 2019 16.8.3 I had to follow similar steps but Tools > Android Device Manager > ... > Factory Reset – metoyou Dec 23 '20 at 11:35

score 10 · Answer 2 · answered Nov 14 '18 at 15:50

10

Android Device Manager > Stop your device and right click > Factory Reset

answered Nov 14 '18 at 15:50

emert117

1,268
2
20
38

score 2 · Answer 3 · answered Sep 18 '19 at 04:02

My problem was two-fold. It turned out that I only needed to apply one set of fixes to address both of them!

Laptop had the OP's error, with the added "Gboard stopped" message superimposed on top of it

Dev-rig's Android Emulator was just a black screen that never changed!

How to fix

Go to Tools -> Android -> Android SDK Manager
Run all the pre-selected updates
Go to the Tools tab
Expand "Android SDK Tools" and select the latest available, or v26.x.
Expand "Android SDK Build Tools" and make sure you have the ability to actually build whatever you just selected in #4
Run those updates
... and Bob's your uncle!

score 1 · Answer 4 · edited Apr 27 '20 at 10:56

1

I'm sure you've already figured it out at this point, but one thing that helped me was simply right-clicking it in the Android Device Manager, and then clicking on 'Start with Factory Default.'

it's grayed out in mine because I've already done it Hope this helps!

edited Apr 27 '20 at 10:56

Jagadesh

2,104
1
16
28

answered Apr 26 '20 at 16:03

Richard Ogujawa

71
1
5

score 0 · Answer 5 · answered May 20 '21 at 06:50

0

In recent Android Studio versions, you can achieve the same results with this

AVD Manager -> Select device -> Cooled Boot Now

or this

AVD Manager -> Select device -> Edit -> Advanced -> Boot option: Cool Boot

answered May 20 '21 at 06:50

luchin

52
5

Android Emulator - "Encryption unsuccessful"

5 Answers5

How to fix