CODEWITHSUNDEEP
androidflutteradbandroid-sdk-toolsandroid-virtual-device
user2526586
user2526586

Reputation: 1202

Device emulator-5554 is not authorized. (Android)

I have run into similar problem like this: [emulator-5554 unauthorized for adb devices [1]

Basically, I am trying to do some flutter programming on an Android Virtual Device with my Windows 10... although I don't think this problem is flutter-specific.

After starting the virtual device, I ran 

flutter doctor -v

Everything seemed fine, except for 

[!] Connected device
• Device emulator-5554 is not authorized.
  You might need to check your device for an authorization dialog.

When I run

flutter devices

I get this:

No devices detected.
Run 'flutter emulators' to list and start any available device emulators.

When I run 

flutter emulators

I get 

1 available emulator:
Nexus_5X_API_28
To run an emulator, run 'flutter emulators --launch <emulator id>'.
To create a new emulator, run 'flutter emulators --create [--name xyz]'.

For days, I have tried almost everything from the post above.I have googled about it but I haven't found anything that can really solve my problem here: I have tried deleting the AVD and creating a new one; I have tried removing the pair of adbkey files; I have tried killing adb server and restarting; I have tried turning on and off the debugging mode/USB debugging; I have tried wiping the data and cold starting for the AVD; I have tried updating the SDK tools..... I have been repetitively trying all these for days and I still get no success. I wonder what I have done wrong here...

Really hope someone can give me some sound advice here. Thank you in advance!

Note: I created my AVD on Android Studio. I ran flutter doctor on command prompt. Don't know if that has got anything to do with this.

[1]: emulator-5554 unauthorized for adb devices

Upvotes: 6

Views: 22965

Answers (10)

geneilson freire
geneilson freire

Reputation: 54

In my case i wiped the data of my phone and the first windows that open it was asking me to allow some usb connection and after allowing it i could use the emulator normally. That windows closes fast you need pay attention.

Upvotes: 0

MOKIT
MOKIT

Reputation: 71

delete all the devices on android virtual dvice manger and creat a new one and run it from thereenter image description here

Upvotes: 1

Ali Ali El-Dabaa
Ali Ali El-Dabaa

Reputation: 127

I tried all above proposed solutions and others but none worked with me. But the following solved it:

The problem was in '.android' files

Delete the entire '.android' folder and re-create the emulator again using AVD manager and the folder will be re-created again in the same location.

The default path of '.android' folder is 'C:\Users\***\.android' unless you changed it.

Upvotes: 4

Mathis N
Mathis N

Reputation: 219

I found the solution guys !! I was stuck but it's actually quite simple !

So, I got the problem with the Pixels 2 and 2 XL API 28 (Pie) and here's what to do :

  • Set and run the device normally

  • Turn on the developer features : go to the settings, then 'System', 'About Emulated Device', tap 5 times on 'Build Number'

  • Go back, reveal the advanced options, then go to 'Developer Options'

  • Make sure 'USB debugging' is on

  • Find 'default USB configuration'

  • Click on it, it will open a menu, then select 'File Transfer' instead of 'No data transfer'

  • I think it's good but you can also click inside your notifications on 'Virtual SD card' and set it for transferring photos and media, in order to be sure

  • Open your PowerShell (or cmd, or what you want) with the emulator still opened and check if it's getting recognized with 'flutter doctor' or 'flutter devices'

  • Go to your project folder with 'cd [your folder's path]

  • Type 'flutter run' to launch your app in the emulator

It should work! It did for me, I think the problem comes from the USB default configuration. I hope it helped, have a nice programming session !

Upvotes: 12

AleFachini
AleFachini

Reputation: 155

I solved it by turning off USB Debug mode in my virtual device and turning it On Again.

Upvotes: 2

Pastre
Pastre

Reputation: 743

Solved it by creating a Nexus emulator instead of a Pixel 2

Upvotes: 5

JForce
JForce

Reputation: 11

I had experienced the same problem and tried to fix it in many ways. For my case, I could find a simple solution as doing Android studio updates. Here is the information for updates.

IDE and Plugin Updates: The following components are ready to update: Android Emulator, Android SDK Platform-Tools

Upvotes: 1

masewo
masewo

Reputation: 811

This happens to me every second week too. The only way I found it to fix this is to click "Wipe Data" in Android Virtual Device Manager (you can find it in the menu that comes up when you click on the arrow that faces downwards). Unfortunately this implies that you have to set up your emulator from scratch.

Upvotes: 0

user2526586
user2526586

Reputation: 1202

I don't know if this is really the solution for it.

Today I have tried creating a different AVD with a different image (Same API level). The new AVD works!

I wonder if it is the case that the old image was buggy or whatsoever - even though that was an official Google Play image.

My new image was not official, I guess, but it works and connects without problem.

Upvotes: 3

Miguel Ruivo
Miguel Ruivo

Reputation: 17756

The accepted answer in a Android studio Emulator ( device unauthorized)

Issue Resolved.

Step 1- Made a new emulator(Any).

Step 2- then fixed another problem the black screen by changing the settings to use hardware graphics.(Dunno if this problem was related to the bug)

And Bam every thing worked.

Upvotes: 0

Related Questions