blocks|key|1296016|text|你试过删除和重新创建你的AVD吗？您可以手动删除AVD文件，方法是转到存储在其中的目录(在用户的/..android/avd子目录中)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1296017|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Did you try deleting and recreating your AVD?
You can manually delete the AVD files by going to the directory they're stored in (in your user's /.android/avd subdirectory).

blocks|key|2654695|text|转到windows任务管理器并结束进程"adb.exe“。可能有多个相同进程的实例，请确保所有这些实例都结束。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2654696|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Go to windows task manager and end process "adb.exe". There might be more than 1 instances of the same process, make sure to end all of them.

blocks|key|1297156|text|Android检测仿真器的方法是从端口5555开始扫描端口。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297157|您在adb+devices列表中看到的数字(在您的例子中是5554)将比亚行正在打开的端口少一个。|offset|length|style|CODE|1297158|您可能有一个正在运行的进程正在侦听端口5555。要摆脱“脱机”设备，您需要找到该应用程序并关闭它，或者重新配置它以侦听不同的端口。|1297159|entityMap^0|0|2|B|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

The way that Android detects emulators is by scanning ports starting at port 5555.

The number you see in the <code>adb devices</code> list (in your case 5554) will be one less than the port that adb is finding open.

You probably have a process running that is listening on port 5555. To get rid of the "offline" device, you will need to find that application and close it or reconfigure it to listen to a different port.

blocks|key|2698547|text|就我而言，我发现了一些让亚行不能正常运转的过程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698548|您可以尝试杀死一些奇怪的进程，并运行“亚行设备”进行测试。|2698549|对我来说很管用：|2698550|终止进程名MONyog.exe|2698551|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

In my case, I found some process that makes adb not work well. 
You can try to kill some strange process and run "adb devices" to test.

It worked for me: 
kill the process name MONyog.exe

blocks|key|1297180|text|我发现，当我使用的亚行修订版不是最近的时候，模拟环境就变成了“脱机”。我正确地更新了我的路径(并删除了旧的亚行版本)，在“亚行杀死服务器”、“亚行设备”上，模拟环境不再是“脱机”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297181|在那之后，我立刻就能使用“亚行外壳”了。|1297182|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I found that the emulation environment comes up as "offline" when the adb revision I am using was not recent. I properly updated my paths (and deleted the old adb version) and upon "adb kill-server", "adb devices", the emulation environment no longer came up as "offline".

I was immediately able to use "adb shell" after that point.

blocks|key|2698566|text|你安装了bluestacks吗？如果这样做，则它运行的后台进程将创建脱机设备“仿真器-5554”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698567|转到任务管理器，用"Bluestacks“的描述结束所有进程。|2698568|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Do you have bluestacks installed? If you do, the background processes that it runs creates the offline device "emulator-5554".

Go to the task manager and end all the processes with the description of "Bluestacks"

blocks|key|2698570|text|我打开命令提示符解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698571|adb杀毒服务器|2698572|亚行设备|2698573|启动后，亚行现在检测设备/模拟器。|2698574|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I solved this by opening my commandprompt:

adb kill-server

adb devices

After starting up, ADB now detects the device/emulator.

blocks|key|1297193|text|“擦除用户数据”选项最终解决了我的问题。每次启动模拟器时，只需擦除用户数据即可。这对我来说总是管用的！我使用windows+8+x64，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297194|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The "wipe user data" option finally solved my problem. just wipe user data every time you start the emulator. This always works for me! 
I use windows 8 x64 , eclipse

blocks|key|2654799|text|在这种情况下，您可以执行以下所有操作，以确保您的模拟器再次开始工作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2654800|adb+kill-server|offset|length|style|CODE|2654801|Go+|unordered-list-item|2654802|
|2654803|转到cmd并键入到任务管理器，并在进程中找到adb。如果您找到一个，右键单击它，然后单击结束过程树。|2654804|In+eclipse，转到Window>Android虚拟设备管理器，单击要启动的AVD，单击start并取消选中“从快照开始启动”，然后单击.|ordered-list-item|BOLD|2654805|2654806|2654807|就这样!这将需要一段时间，它应该可以解决你的问题。|2654808|entityMap^0|0|0|F|0|0|0|M|3|0|D|L|1R|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|13|8|@]|9|@]|A|$]]|$1|M|3|N|5|J|7|14|8|@$D|15|E|16|F|G]]|9|@]|A|$]]|$1|O|3|P|5|Q|7|17|8|@$D|18|E|19|F|R]|$D|1A|E|1B|F|R]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1E|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|X|$]]

In such a case, you can do all of the following in order to be assured that your emulator starts working again :

<ol>
<li>Go to cmd and type <code>adb kill-server</code></li>
<li>Go to task manager and find <code>adb</code> in processes. If you find one, right click on it and click on end process tree. </li>
<li>In eclipse, go to Window>Android Virtual Device Manager, click on the AVD you want to launch, click on start and uncheck "Launch From Snapshot" and then click on launch.</li>
</ol>

That's it! It will take a while and it should resolve your problem.

blocks|key|2698628|text|试试这个..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698629|如果运行，|2698630|关闭仿真器。|ordered-list-item|2698631|再次启动仿真程序并等待其联机。|2698632|在命令提示符下输入命令并按ENTER键:+adb+tcpip+5555+|2698633|2698634|(确保一次只运行一个模拟器。)|2698635|Key....|2698636|Done.+|unordered-list-item|2698637|adb+-s仿真器-5555+emu杀死|2698638|按下|2698639|通过命令cmd.|2698640|中的"adb设备“检查设备。|2698641|2698642|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|17|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1C|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|1D|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1F|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|12|$]]

Try this ...

<ol>
<li>Close emulator if it Running.</li>
<li>Start Emulator again and wait for its online.</li>
<li>enter Command in commandprompt and press ENTER key : adb tcpip 5555 </li>
</ol>

(Make sure that only One emulator running at a time.)

<ol>
<li>adb -s emulator-5555 emu kill </li>
<li>Press Enter Key....</li>
<li>Done. </li>
<li>check devices by command "adb devices" in cmd.</li>
</ol>

blocks|key|2654854|text|简单地删除和创建齿轮avd+again.It将工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2654855|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Simply delete and created gear avd again.It will work.

blocks|key|2698682|text|在我的例子中，原因是我恢复了一个包含Androd-x86的VM。用Androd-x86重新启动VM并重新启动亚行服务器解决了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698683|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case the cause was that I had resumed a VM with android-x86 inside. Rebooting the VM with Android-x86 and restarting the adb server fixed the problem.

blocks|key|2698734|text|如果您在Linux或Mac上，并且假设脱机设备是“仿真器-5554”，则可以运行以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698735|netstat+-tulpn%7Cgrep+5554|code-block|syntax|javascript|2698736|它产生以下输出：|2698737|tcp++++++++0++++++0+127.0.0.1:5554++++++++++0.0.0.0:*+++++++++++++++LISTEN++++++4848/emulator64-x86
tcp++++++++0++++++0+127.0.0.1:5555++++++++++0.0.0.0:*+++++++++++++++LISTEN++++++4848/emulator64-x86|2698738|这告诉我，进程id+4848+(您的进程可能有所不同)仍然在监听端口5554。现在，您可以通过以下方法来终止该进程：|2698739|sudo+kill+-9+4848|2698740|鬼离线设备也就不复存在了！|2698741|关于macOS大Sur及以后，请使用|2698742|sudo+lsof+-i+-P+%7C+grep+LISTEN+%7C+grep+5554|2698743|找出这个过程。|2698744|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

If you are on Linux or Mac, and assuming the offline device is 'emulator-5554', you can run the following:
<pre><code>netstat -tulpn|grep 5554
</code></pre>
Which yields the following output:
<pre><code>tcp 0 0 127.0.0.1:5554 0.0.0.0:* LISTEN 4848/emulator64-x86
tcp 0 0 127.0.0.1:5555 0.0.0.0:* LISTEN 4848/emulator64-x86
</code></pre>
This tells me that the process id 4848 (yours will likely be different) is still listening on port 5554. You can now kill that process with:
<pre><code>sudo kill -9 4848
</code></pre>
and the ghost offline-device is no more!
On macOS Big Sur and later, use
<pre><code>sudo lsof -i -P | grep LISTEN | grep 5554
</code></pre>
to find out the process.

blocks|key|2654977|text|这是因为您的计算机上安装了另一个虚拟设备。它可能是布鲁斯斯塔克，因为我也面临着一个类似的问题。我卸载了Bluestacks，然后检查了adb+devices，它当时运行得很好。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|2654978|entityMap^0|P|6|1V|B|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|N|8|@]|E|@]|F|$]]]|H|$]]

That is because of the fact that you have another virtual device installed on your machine. It might be Bluestacks as I also faced a similar problem. I uninstalled Bluestacks and then checked
 <code>adb devices</code>
It was running fine then.

blocks|key|2698827|text|如果模拟器已经打开或正在执行，它将告诉您离线。您可以在命令行(Ubuntu)上反复检查并执行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698828|+adb+devices|code-block|syntax|javascript|2698829|您必须脱机看到模拟器，必须关闭模拟器的运行实例(因为端口将显示为繁忙)，然后可以运行应用程序。希望这能帮上忙。|2698830|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If the emulator is already open or executing it will tell you is offline. You can double check on the Command Line (Ubuntu) and execute:

<pre><code> adb devices
</code></pre>

You must see your emulator offline, you have to close the running instance of the emulator (since the port will show as busy) and after that you can run your application. Hope this helps someone.

blocks|key|2698846|text|只管写|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698847|adb+-e+reboot|code-block|syntax|javascript|2698848|(与亚行合作)|2698849|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Just write

<pre><code>adb -e reboot
</code></pre>

and be happy with adb))

blocks|key|1296284|text|在我的例子中，我没有检查"GPU主机“及其工作:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1296285|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, I have unchecked "GPU Host" and its worked :)

blocks|key|1296323|text|此解决方案适用于Windows。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1296324|(关于@Chris+Knight's+solution+Mac/Linux，请参阅)|offset|length|style|BOLD|1296325|1296326|启动Windows：|ordered-list-item|1296327|1296328|启动->类型'powershell‘->按下输入|1296329|，运行以下命令：adb+->|unordered-list-item|1296330|1296331|1296332|PS+C:\Users\CJBS>adb+devices
List+of+devices+attached
emulator-5656+++host
emulator-5652+++host
12b80FF443++++++device|code-block|syntax|javascript|1296333|在本例中，12b80FF443是我的物理设备，模拟器-*条目是垃圾。|1296334|1296335|Per+@Brigham，“安卓检测模拟器的方式是从端口5555开始扫描端口。”端口号在模拟器名称之后指示(在本例中为5656和5652)。要检查的端口号是模拟器端口号加1。|1296336|1296337|5656+%2B1=+5657|1296338|5652+%2B1=+5653|1296339|那么让我们看看哪个程序正在使用这些端口。在这种情况下，两个检查端口都从"565“开始。所以我将从565开始搜索使用中的端口。执行：netstat+-a+-n+-o+%7C++Select-String+":565"|CODE|1296340|1296341|PS+C:\Users\CJBS>+netstat+-a+-n+-o+%7C++Select-String+":565"

++TCP++++127.0.0.1:5653+++++++++127.0.0.1:5653+++++++++ESTABLISHED+++++5944
++TCP++++127.0.0.1:5657+++++++++127.0.0.1:5657+++++++++ESTABLISHED+++++5944|1296342|1296343|输出中的最后一个字段是PID+(进程ID)+--在本例中，这两个端口都是PID+5944。让我们看看这个进程ID是什么。执行：tasklist+/v+%7C+Select-String+5944.将5944替换为前面命令的输出：|1296344|1296345|1296346|PS+C:\Users\CJBS>+tasklist+/v+%7C+Select-String+5944

adb.exe+++++++++++++++++++++++5944+Console++++++++++++++++++++1++++++6,800+K+Running+++++++++MyPCName\CJBS++++++++++0:06:03+ADB+Power+Notification+Window|1296347|真叫人吃惊。是亚行。正如其他答案所指出的，它也可能是其他程序。|1296348|现在，只需关闭这个进程ID。执行kill+5944，，用前面命令中的PID替换5944。。|1296349|1296350|PS+C:\Users\CJBS>+kill+5944|1296351|若要确认伪仿真器已消失，请重新运行以下命令:+devices+adb|1296352|1296353|PS+C:\Users\CJBS>adb+devices
List+of+devices+attached
*+daemon+not+running.+starting+it+now+on+port+5037+*
*+daemon+started+successfully+*
12b80FF443++++++device|1296354|亚行重新启动(就像以前被杀的那样)，它不会检测到更多的仿真器。|1296355|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/26423404/3063884|1|https://stackoverflow.com/a/10356594/3063884^0|0|15|1|3|O|0|0|0|0|A|0|0|0|O|0|0|E|0|0|0|0|0|Y|0|0|0|2F|4|8|1|0|0|0|D|0|0|D|0|0|2X|1T|14|0|0|0|0|0|34|1R|W|0|0|0|0|0|V|0|0|19|G|9|0|0|0|0|U|V|3|0|0|0|0|V|0^^$0|@$1|2|3|4|5|6|7|29|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2A|8|@$D|2B|E|2C|F|G]]|9|@$D|2D|E|2E|1|2F]]|A|$]]|$1|H|3|-4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|2H|8|@$D|2I|E|2J|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|2K|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|2L|8|@$D|2M|E|2N|F|G]]|9|@]|A|$]]|$1|O|3|P|5|Q|7|2O|8|@$D|2P|E|2Q|F|G]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|2S|8|@]|9|@]|A|$]]|$1|T|3|U|5|V|7|2T|8|@]|9|@]|A|$W|X]]|$1|Y|3|Z|5|6|7|2U|8|@$D|2V|E|2W|F|G]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|2X|8|@]|9|@]|A|$]]|$1|11|3|12|5|K|7|2Y|8|@$D|2Z|E|30|F|G]]|9|@$D|31|E|32|1|33]]|A|$]]|$1|13|3|-4|5|6|7|34|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|35|8|@$D|36|E|37|F|G]]|9|@]|A|$]]|$1|16|3|17|5|6|7|38|8|@$D|39|E|3A|F|G]]|9|@]|A|$]]|$1|18|3|19|5|6|7|3B|8|@$D|3C|E|3D|F|G]|$D|3E|E|3F|F|1A]]|9|@]|A|$]]|$1|1B|3|-4|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|V|7|3H|8|@]|9|@]|A|$W|X]]|$1|1E|3|-4|5|6|7|3I|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|K|7|3J|8|@$D|3K|E|3L|F|G]|$D|3M|E|3N|F|1A]]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|3O|8|@]|9|@]|A|$]]|$1|1I|3|-4|5|6|7|3P|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|V|7|3Q|8|@]|9|@]|A|$W|X]]|$1|1L|3|1M|5|6|7|3R|8|@$D|3S|E|3T|F|G]]|9|@]|A|$]]|$1|1N|3|1O|5|6|7|3U|8|@$D|3V|E|3W|F|G]|$D|3X|E|3Y|F|1A]]|9|@]|A|$]]|$1|1P|3|-4|5|6|7|3Z|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|V|7|40|8|@]|9|@]|A|$W|X]]|$1|1S|3|1T|5|6|7|41|8|@$D|42|E|43|F|G]|$D|44|E|45|F|G]]|9|@]|A|$]]|$1|1U|3|-4|5|6|7|46|8|@]|9|@]|A|$]]|$1|1V|3|1W|5|V|7|47|8|@]|9|@]|A|$W|X]]|$1|1X|3|1Y|5|6|7|48|8|@$D|49|E|4A|F|G]]|9|@]|A|$]]|$1|1Z|3|-4|5|6|7|4B|8|@]|9|@]|A|$]]]|20|$21|$5|22|23|24|A|$25|26]]|27|$5|22|23|24|A|$25|28]]]]

<h2>This solution is for Windows.</h2>

(See <a href="https://stackoverflow.com/a/26423404/3063884">@Chris Knight's solution</a> for Mac/Linux)

<ol>
<li>Start Windows Powershell:

Start -> type 'powershell' -> Press ENTER</li>
<li>Run the following command: adb devices</li>
</ol>

<hr>

<pre><code>PS C:\Users\CJBS&gt;adb devices
List of devices attached
emulator-5656 host
emulator-5652 host
12b80FF443 device
</code></pre>

In this case, 12b80FF443 is my physical device, and the emulator-* entries are garbage.

<ol start="3">
<li>Per <a href="https://stackoverflow.com/a/10356594/3063884">@Brigham</a>, "The way that Android detects emulators is by
scanning ports starting at port 5555.". The port number is indicated after the emulator name (in this case 5656 and 5652). The port number to check is the emulator port number plus 1. So in this case:-

5656 + 1 = 5657

5652 + 1 = 5653

So let's see which program is using these ports. In this case, the ports to check both start with "565". So I'll search for ports in use starting with 565. Execute: <code>netstat -a -n -o | Select-String ":565"</code></li>
</ol>

<hr>

<pre><code>PS C:\Users\CJBS&gt; netstat -a -n -o | Select-String ":565"

 TCP 127.0.0.1:5653 127.0.0.1:5653 ESTABLISHED 5944
 TCP 127.0.0.1:5657 127.0.0.1:5657 ESTABLISHED 5944
</code></pre>

<ol start="4">
<li>The final field in this output is the PID (Process ID) - in this case it's PID 5944 for both of these two ports. So let's see what this process ID is. Execute: <code>tasklist /v | Select-String 5944</code>. Replace 5944 with the output of the previous command:</li>
</ol>

<hr>

<pre><code>PS C:\Users\CJBS&gt; tasklist /v | Select-String 5944

adb.exe 5944 Console 1 6,800 K Running MyPCName\CJBS 0:06:03 ADB Power Notification Window
</code></pre>

What a surprise. It's ADB. As noted by other answers, it could be other programs, too.

<ol start="5">
<li>Now, just kill this process ID. Execute <code>kill 5944</code>, replacing 5944 with the PID in the previous command.</li>
</ol>

<hr>

<pre><code>PS C:\Users\CJBS&gt; kill 5944
</code></pre>

<ol start="6">
<li>To confirm that the spurious emulator is gone, re-run the following command: adb devices</li>
</ol>

<hr>

<pre><code>PS C:\Users\CJBS&gt;adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
12b80FF443 device
</code></pre>

ADB re-starts (as it was previously killed), and it detects no more fake emulators.

blocks|key|2699016|text|只需从AVD管理器中删除用户数据，然后输入亚行杀死服务器和亚行设备。擦除数据也节省了系统的大量内存空间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2699017|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just Wipe user data from AVD manager and then enter adb kill-server and adb devices.
Wiping data also saves lot of memory space in the System .

blocks|key|1296375|text|我尝试了所有的方法，但只有这个才适用于我的情况:使用SDK管理器，然后重新安装系统映像。Android，单击Configure，SDK，启动独立的SDK管理器，检查所有"Google+Intelx86*+System+Image“、"Intel+x86+Atom*System”并安装。然后重新启动安卓工作室。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1296376|您可能需要重新配置并使用AVD管理器擦除虚拟设备，确保选择了x86版本。|1296377|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I tried everything but only this one works for my case:
Use SDK manager, and reinstall the system image.
Android Studio, click Configure, SDK Manager, Launch Standalone SDK Manager,
Check all "Google APIs Intel x86* System Image", "Intel x86 Atom*System Image" and install. Then re-start Android studio.

You might have to reconfigure and wipe the virtual device with AVD Manager, make sure you choose x86 version.

blocks|key|1297379|text|我将在这里添加另一个可能的解决方案，这在我的情况下是可行的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297380|我发现有一个名为SpiceWorksEventProcessor正在运行的进程，它正在绑定端口5555，而且很明显亚行将其读取为一个仿真器。最后把那个顽固的仿真器装置给我拿走了。|1297381|我不知道这是什么东西，但如果你有它，它可能是你的离线模拟器的原因。|1297382|干杯|1297383|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I'll add another possible solution here, which is what worked in my case. 

I found there was a process called SpiceWorksEventProcessor running, which was tying up port 5555, and apparently being read by adb as an emulator. Killing that process was what finally removed that stubborn emulator device for me.

I'm not sure what this thing is, but if you have it, it might be the cause of your offline emulator.

Cheers

blocks|key|2699095|text|在linux或mac上，被阻塞的端口将仿真器id%2B1所以5555+so：sudo+lsof+-i+:5555将显示占用端口的进程的pid+(应该是第二列)，从而杀死它：sudo+lsof+-i+:5555+%7C+awk+'{print+$2}'+%7C+xargs+kill。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2699096|那么adb+(假的)设备将不再显示在列表上。|2699097|entityMap^0|10|I|2C|1E|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

on linux or mac the port thats blocked will emulator-id + 1 so 5555 so:
<code>
sudo lsof -i :5555
</code>
will show you the pid of process that are taking the port (should be the second column) so to kill it:
<code>
sudo lsof -i :5555 | awk '{print $2}' | xargs kill
</code>

then adb (fake) devices will no longer show on the list

blocks|key|1296429|text|1.只需“擦除数据”就可以解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1296430|​|1296431|📷|atomic|offset|length|1296432|1296433|2.如果不工作，转到模拟设备并启用开发人员选项>启用usb调试|1296434|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/a2de2764ed05e437b30f38d63d19d704.png|imageAlt^0|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@$G|X|H|Y|1|Z]]|A|$]]|$1|I|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

1 . Simply "Wipe data" to fix this issue.

<a href="https://i.stack.imgur.com/dQAq0.png" rel="noreferrer"><img src="https://i.stack.imgur.com/dQAq0.png" alt="enter image description here"></a>

2 . If it doesn't work, go to emulated device and enable developer options > enable usb debugging

blocks|key|2655283|text|确保已标记了启用的ADB集成；转到Tools>Android>Enable+ADB集成。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2655284|如果未选中，请选中此选项并关闭虚拟设备并重新打开它。这对我有用..。祝你好运！|2655285|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Ensure that your enable ADB integration is marked;
go to Tools>Android>Enable ADB integration .

if doesn't checked , check this option and close your virtual device and re-open it . this worked for me.. good luck!!

blocks|key|2699192|text|以上所有的答案都没有帮助，然后我删除并重新创建了仿真器，一切正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2699193|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

All above answers didn't helped,and then I deleted and recreated emulator all worked fine

blocks|key|1297455|text|在模拟器中启用USB调试|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1297456|developer;|1297457|Settings+|unordered-list-item|1297458|
|1297459|设置>关于电话>构建号>点击7次成为>+Developer选项>+USB调试。|1297460|1297461|这就是享受|1297462|entityMap^0|0|4|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|X|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|N|5|J|7|Z|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|11|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|S|$]]

Enable USB Debugging into your emulator

<ol>
<li>Settings > About Phone > Build number > Tap it 7 times to become developer;</li>
<li>Settings > Developer Options > USB Debugging.</li>
</ol>

That's it enjoy

blocks|key|2655337|text|在MAC中，您可以使用Activity实用程序，因为与Linux不同，我们不能在MAC中使用netstat+-tulpn命令。搜索模拟器的运行实例，通常是386。杀死该实例，您将不会看到任何鬼仿真器运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2655338|获取活动监视器实用程序的最简单方法是使用聚光灯搜索。只需按cmd-空格并键入活动监视器。|2655339|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In MAC, you can use Activity Monitor utility, since, unlike Linux, we cannot use netstat -tulpn command in MAC. Search for the running instance of the emulator, typically qemu-system-i386. Kill that instance and you will see none of the ghost emulator running. 

Simplest way to grab Activity monitor utility is to use spotlight search. just hit cmd-space and type in Activity Monitor.

blocks|key|2655350|text|我也有同样的问题。我试过这里描述的所有解决方案，但它们都帮不了我。然后，我删除了Android虚拟设备管理器中的所有模拟器，并创建了新的仿真器。问题是在的CPU/ABI系统映像配置中。我的带有系统映像x86的Windows10计算机仿真器总是脱机的，其中带有系统映像x86_64的模拟器正常工作。只是要注意这一点|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|2655351|entityMap^0|25|7|2S|3|3P|6|2S|3|3P|6|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|C]|$9|N|A|O|B|C]|$9|P|A|Q|B|D]|$9|R|A|S|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|T|8|@]|E|@]|F|$]]]|H|$]]

I also had the same issue. I've tried all solutions described here, but they didn't help me. Then I've removed all emulators in the Android Virtual Device Manager and created new ones. The problem was in the CPU/ABI system image configuration of the Android Virtual Device Manager. My Windows10 machine emulator with system image <code>x86</code> is always offline, where the emulator with system image <code>x86_64</code> is working fine as expected. Just be aware of this

blocks|key|2655397|text|我终于解决了这个问题，我不得不从模拟器中的设置转到Developer+options，然后向下滚动，打开USB调试。我的设备立即在网上被识别，我不再面临这个问题。我试着重新启动android和仿真器，扼杀了亚行进程，但这些都没有起作用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2655398|entityMap^0|L|2|P|H|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I finally solved this problem,
I had to go to the Developer options from the Settings in the Emulator,
then scrolled down a little, turned on the USB debugging. Instantly my device was recognized online, and I no longer faced that issue. I tried restarting android studio and emulator, killing adb process, but those did not work.

blocks|key|2655450|text|从AVD经理尝试“冷启动现在”选项在下拉。对我起作用了！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2655451|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

From the AVD Manager try the "Cold Boot Now" option in the drop-down. It worked for me!

blocks|key|2655506|text|从AVD经理名单在行动下拉:冷启动现在|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2655507|在没有所有痛苦的情况下重新开始。|2655508|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

From AVD manager list at the actions dropdown:
Cold Boot Now

restarts it without all pain above.

blocks|key|1297541|text|在我的例子中，仿真器是与奥利奥和更低，但不是与派，一切我尝试似乎没有影响。最后起作用的是将模拟器更新为最新版本(版本28)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297542|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, the emulator was working with Oreo and lower, but not with Pie, and everything I tried seemed to have no effect. What finally worked was updating the emulator to latest (version 28).

blocks|key|1296591|text|在我的例子中，我开始在‘现在冷启动’，并点击消息，以允许连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1296592|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, I started in 'Cold Boot Now' and clicked on Message to allow the connection.

blocks|key|1297572|text|我的虚拟设备也有同样的问题。这个问题是由于Oreo映像的虚拟设备，具有Play商店集成。为了解决这个问题，我安装了一个没有Play+Store集成的新设备，一切都很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297573|希望能帮上忙，再见|1297574|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same issue with my virtual device. The problem is due to the Oreo image of the virtual devices that have the Play Store integrated. To solve this problem I installed a new device without the Play Store integrated and all it was fine.

Hope it helps, Bye

blocks|key|2699495|text|打开你的模拟器，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2699496|设置->关于模拟设备->重复单击Build号>打开开发人员选项>打开USB调试器|2699497|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

open your emulator,

setting --> about emulated device --> click Build number repeatedly-->open developer options --> open USB debuggin

blocks|key|1296613|text|见emulator-5554+unauthorized+for+adb+devices。在API+29模拟器上，我运行adb+devices命令并获得emulator-5554+unauthorized消息。然后，我用avd映像创建了一个新的Google+APIs设备(在我的例子中是Q，x86)，而不是Google+Play。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1296614|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/46898322/emulator-5554-unauthorized-for-adb-devices^0|1N|B|23|Q|31|3|3D|B|48|B|1|16|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|F|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

See <a href="https://stackoverflow.com/questions/46898322/emulator-5554-unauthorized-for-adb-devices">emulator-5554 unauthorized for adb devices</a>. On API 29 emulator I run <code>adb devices</code> command and got <code>emulator-5554 unauthorized</code> message. Then I created a new <code>avd</code> device from <code>Google APIs</code> image (in my case Q, x86), not from <code>Google Play</code>.

blocks|key|1296625|text|步骤01:从AVD管理器删除当前模拟器步骤02:添加新模拟器。选择device+=>选择系统映像，在这个步骤中转到x86图像选项卡，并选择一个具有google+目标的选项卡。步骤03:完成所有步骤。你可以去️了|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1296626|entityMap^0|0|C|J|5|1L|8|21|7|2F|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|G|$]]

step 01: Delete current emulator from AVD manager
step 02: Add new emulator. select device => select system image, in this step go to x86 images tab and select one which has the target with google APIs.
step 03: Finish all steps. Your're good to go ️

blocks|key|1297615|text|在我的例子中，原因是VMware的NAT连接设置中的端口转发。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1297616|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case the reason was the port forwarding in the NAT connection settings of VMware.

blocks|key|2699669|text|如果您擦除数据，您的仿真器仍然无法连接到互联网。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2699670|📷|atomic|offset|length|2699671|​|2699672|请检查您的DNS网络并添加DNS+8.8.8.8|2699673|2699674|2699675|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/09a8f372fef50d50f16fe6ecfa359711.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/ed0cc3703ce4d0dfd8fe796788b38c79.png^0|0|0|1|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@$E|Z|F|10|1|11]]|A|$]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|C|5|D|7|14|8|@]|9|@$E|15|F|16|1|17]]|A|$]]|$1|L|3|H|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T|U|-4]]|V|$5|P|Q|R|A|$S|W|U|-4]]]]

In case you wipe data, your emulator still cannot connect to the internet.
<a href="https://i.stack.imgur.com/hYSSp.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/hYSSp.png" alt="enter image description here" /></a>
Please check your DNS network and add DNS 8.8.8.8
<a href="https://i.stack.imgur.com/oyEp6.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/oyEp6.png" alt="enter image description here" /></a>

blocks|key|2699686|text|我使用命令行启动模拟器，这里有一个选项：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2699687|-delay-adb+"delay+adb+communication+till+boot+completes"|code-block|syntax|javascript|2699688|不幸的是，即使在引导完成之后，它仍然处于脱机状态。删除选项解决了这个问题。|2699689|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I was using the command line to start the emulator, and there is an option there:
<pre><code>-delay-adb &quot;delay adb communication till boot completes&quot;
</code></pre>
Unfortunately, it stayed offline even after boot completed. Removing the option solved the issue.

blocks|key|2699707|text|适用于mac用户|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2699708|转到终端，键入亚行杀死服务器，然后转到强制退出应用程序，并发现任何模拟器正在运行，并单击强制退出。|2699709|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

For mac users
Go to terminal and type adb kill-server and then go to force quit the application and find any emulator is running and click on force quit.

blocks|key|2699714|text|尝试使用default或google_apis系统映像，而不是google_apis_playstore，因为playstore映像需要身份验证。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2699715|见此处：https://stackoverflow.com/a/55196967/1050542|2699716|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/55196967/1050542^0|4|7|C|B|V|L|0|4|18|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

try using <code>default</code> or <code>google_apis</code> system image and not <code>google_apis_playstore</code>, as the playstore image requires authentication.
See here:
<a href="https://stackoverflow.com/a/55196967/1050542">https://stackoverflow.com/a/55196967/1050542</a>

blocks|key|1296781|text|删除AVD和重新安装是唯一对我有用的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1296782|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Deleting the AVD and re-installing again was the only thing that worked for me.

blocks|key|1297697|text|在我的例子中，是jdk版本导致了这个问题。应该是openjdk-8-jdk供A-Studio+Chipmunk+(2021.2.1)使用，而不是openjdk-11附带预装的系统。跑完后：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1297698|apt+install+-y+openjdk-8-jdk|CODE|1297699|花栗鼠的问题解决了！|1297700|我发现这个解决方案是为了解决sdkmanager遇到的问题。链接Fix+sdkmanager+java.lang.NoClassDefFoundError+batchfile给出了最佳帮助。|1297701|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/55436585/fix-sdkmanager-java-lang-noclassdeffounderror-batchfile^0|O|D|1B|8|20|A|0|0|S|0|0|W|1J|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@$9|12|A|13|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|14|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|M|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

In my case, it is the jdk version causes the issue. It should be openjdk-8-jdk for A-Studio Chipmunk (2021.2.1) to use, not the openjdk-11 comes with the system preinstalled. After running:
<code>apt install -y openjdk-8-jdk</code>
The problem is solved for Chipmunk!
I found this solution as a side effort to solve sdkmanager issue encountered. The link <a href="https://stackoverflow.com/questions/55436585/fix-sdkmanager-java-lang-noclassdeffounderror-batchfile">Fix sdkmanager java.lang.NoClassDefFoundError batchfile</a> gives the optimal help.

blocks|key|2655926|text|删除AVD设备上的锁将有助于运行擦除数据、冷引导、删除等操作，如果它们以前不工作的话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2655927|在下面运行以移除锁。AVD名称是您在创建它时指定的名称。|2655928|rm+-vfr+~/.android/avd/[AVD+name].avd/*.lock|code-block|syntax|javascript|2655929|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Removing the lock on the AVD device will help in running Wipe data, cold boot now, delete, etc actions will work, if they are not working before.
Run below to remove the lock. AVD name is the name you gave when creating it.
<pre><code>rm -vfr ~/.android/avd/[AVD name].avd/*.lock
</code></pre>

blocks|key|2699853|text|这个命令对我有效，并杀死后台运行的模拟器-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2699854|adb+emu+kill|code-block|syntax|javascript|2699855|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This command worked for me and kill the emulator running in the background -
<pre><code>adb emu kill
</code></pre>

blocks|key|1296842|text|添加一下，您可能会从模拟器或调试模式中禁用developer+options。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1296843|在这些情况下，终端将在尝试执行操作时打印adb:+device+offline。|CODE|1296844|entityMap^0|E|4|L|H|0|K|J|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|P|8|@$9|Q|A|R|B|H]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|J|$]]

Just to add, it could be that you disabled the developer options from the emulator or the debug mode.
In those cases the terminal will print <code>adb: device offline</code> when trying to perform operations.

I'm having a problem with emulator-5554, it keeps telling me it is offline. 

When I do a <code>adb devices</code> from the command line it says

<code>emulator-5554 offline</code>

Even after a fresh restart, I try that command and it still says it is offline.

The problem is when I try to install .apk files to the emulator using <code>abd install &lt;path&gt;</code> from the command prompt, it tells me that it is offline, if I create another device and run that one, then try to install the .apk files, it says I have too many devices connected. So in other words, I can't install my .apk files.

How in the world can I get rid of that damn emulator-5554? I heard that if you do a restart, it should clear all the devices, but that does not seem to be working. It is like it is getting initialized when my computer starts up. Has anyone run into this issue?

Thanks

Android emulator-5554 offline

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我的模拟器-5554有问题，它一直告诉我它离线。当我从命令行执行adb devices时，它说emulator-5554 offline即使在重新重新启动之后，我仍然尝试这个命令，它仍然说它是脱机的。问题是，当我尝试使用命令提示符使用.apk将abd install <path>文件安装到模拟器时，它告诉我它是脱机的，...

问Android仿真器-5554脱机
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android仿真器-5554脱机EN