1. Download the #1 Android News App:   EarlyBird - News for Android
    Dismiss Notice

adb shell error: more than one device and emulator

Last Updated:

  1. 2fasst

    2fasst Active Member

    Tried to search but couldn't find anything on this.

    I'm trying to use 'adb shell' to begin blocking OTA updates, and encountered this error message.

    thoughts anyone?

  2. vincentp

    vincentp Well-Known Member

    Strange one. You don't by any chance have the SDK Emulator running do you?
  3. 2fasst

    2fasst Active Member

    don't think so. I just unzipped it, and got the message the first time I try to initiate it.
  4. 2fasst

    2fasst Active Member

    currently shows:

    emulator-5554 offline
  5. decalex

    decalex Well-Known Member

    ya, super old message, but just in case you're still stuck! :)

    adb kill-server


    adb devices

    and it should restart
    usn.mustanger and spd-racer like this.
  6. Muilisx

    Muilisx Well-Known Member

    mine still says

    error: more than one device and emulator
  7. Copp

    Copp New Member

    I killed the server, as instructed, then made sure the install command was directed, via the -s <serial number>, the install xxx.apx to the correct device. Device name/serial number (seems to be the same thing) can be found via the adb devices command
  8. EDer

    EDer New Member

    If you are banging your head because something is preventing that root or hack from working and this error pops up, maybe this can help.

    I had a program called, "BlueStacks" running on my PC which is in fact an emulator that allows me to run Android Apps on my PC. However, when you are working with roots, it is a horrible program to have running in the background.

    Quick Fix: Exit out of Bluestacks and start the root again. It will run smoothly now.

    Also: If you have any other programs like BlueStacks that allow you to run droid apps on your pc, good idea to shut them down too.

    Hope this cures for you, what was a BIG problem for me.
    dhruvam gupta likes this.
  9. Ivan Petrov

    Ivan Petrov New Member

    Thanks, that worked.;)
  10. dhruvam gupta

    dhruvam gupta New Member

    this on helped me too:) thanx :thumbsupdroid:
  11. FlyDMy

    FlyDMy New Member

    This simply means that one emulator is already running (could be minimized in another command window, or in the background).

    How to resolve:

    1) Run adb devices
    should reveal something like:

    List of devices attached device device

    Then simply unmount the one you don't care about, leaving the one you do:

    2) Run adb disconnect

    Just tried it, works every time.

Share This Page