blocks|key|2265901|text|检查是否安装了三星玩具。这是一种可能的解决办法。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2265902|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Samsung_Kies^0|7|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Check if you have <a href="https://en.wikipedia.org/wiki/Samsung_Kies" rel="nofollow noreferrer">Samsung Kies</a> installed. That is one possible solution

blocks|key|1987574|text|正如消息所述，您需要允许亚行访问您的电话。|type|blockquote|depth|inlineStyleRanges|entityRanges|data|1987575|你需要首先用USB电缆把手机连接到你的电脑上，然后授权信息会弹出屏幕。勾选记住你的选择，然后允许它。|unstyled|1987576|如果您的设备在连接到PC.Just时没有显示任何消息，请执行以下操作。|offset|length|style|BOLD|1987577|删除/data/misc/adb/adb_key，重新启动手机，然后重试连接。信息应该来了。|1987578|entityMap^0|0|0|0|Z|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|Q|8|@$G|R|H|S|I|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|T|8|@]|9|@]|A|$]]|$1|M|3|-4|5|D|7|U|8|@]|9|@]|A|$]]]|N|$]]

<blockquote>
 As the message have stated, you need to allow the adb access on your phone. 
</blockquote>

You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.

IF your device doesnt shows any messages when connected to the PC.Just do this.

<blockquote>
 Remove /data/misc/adb/adb_key, reboot your phone and try connect
 again. The message should come up.
</blockquote>

blocks|key|1267892|text|我终于想出来了！删除Eclipse目录后，我将其安装到另一个目录中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1267893|echo+%25ANDROID_SDK_HOME%25|code-block|syntax|javascript|1267894|显示到sdk目录的错误路径。|1267895|set+ANDROID_SDK_HOME+"E:\adt-bundle-windows-x86_64-20140321\sdk"|ordered-list-item|offset|length|style|CODE|1267896|拔出装置|1267897|adb+kill-server|1267898|adb+start-server|1267899|塞子装置|1267900|在这些步骤之后，我在手机上看到了RSA指纹的确认对话框:)|1267901|entityMap^0|0|0|0|0|1S|0|0|0|F|0|0|G|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|13|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|14|8|@$L|15|M|16|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|K|7|17|8|@]|9|@]|A|$]]|$1|R|3|S|5|K|7|18|8|@$L|19|M|1A|N|O]]|9|@]|A|$]]|$1|T|3|U|5|K|7|1B|8|@$L|1C|M|1D|N|O]]|9|@]|A|$]]|$1|V|3|W|5|K|7|1E|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|10|$]]

Ohhh finally I figured it out!
After removing Eclipse directory I installed it into another directory.

<pre><code>echo %ANDROID_SDK_HOME%
</code></pre>

has displayed wrong path to sdk directory.

<ol>
<li><code>set ANDROID_SDK_HOME "E:\adt-bundle-windows-x86_64-20140321\sdk"</code></li>
<li>unplug device</li>
<li><code>adb kill-server</code></li>
<li><code>adb start-server</code></li>
<li>plug device</li>
</ol>

After these steps, I was able to see confirmation dialog with RSA fingerprint on my phone :)

blocks|key|1987648|text|我在nexus7中遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1987649|后续工作是为了解决这个问题。|1987650|在设备上的Developer菜单中打开Settings选项。|ordered-list-item|offset|length|style|CODE|1987651|Switch+off按钮在屏幕的右上角。|1987652|从菜单列表中Delete+debug+permission。|1987653|Switch+on按钮在屏幕的右上角。|1987654|现在重新连接你的设备到你的电脑，一切都应该是好的。|1987655|对不起，我的英语很差，菜单(按钮)的一些名字在你的语言中可能是不正确的，因为我的是日语。|1987656|entityMap^0|0|0|5|9|J|8|0|0|A|0|6|6|D|G|0|0|9|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@$G|Z|H|10|I|J]|$G|11|H|12|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|13|8|@$G|14|H|15|I|J]]|9|@]|A|$]]|$1|M|3|N|5|F|7|16|8|@$G|17|H|18|I|J]|$G|19|H|1A|I|J]]|9|@]|A|$]]|$1|O|3|P|5|F|7|1B|8|@$G|1C|H|1D|I|J]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1E|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1F|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|V|$]]

I run into the same issues with nexus7.

Following worked for fixing this.

<ol>
<li>Open <code>Developer</code> option in the <code>Settings</code> menu on your device.</li>
<li><code>Switch off</code> the button on the upper right of the screen.</li>
<li><code>Delete</code> all <code>debug permission</code> from the list of the menu.</li>
<li><code>Switch on</code> the button on the upper right of the screen. </li>
</ol>

now reconnect your device to your PC and everything should be fine.

Sorry for my poor english and some name of the menus(buttons) can be incorrect in your language because mine is Japanese.

blocks|key|1987735|text|无论出于何种原因，该设备很可能不再在亚行上获得授权。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1987736|1.检查是否授权：|style|BOLD|1987737|<ANDROID_SDK_HOME>\platform-tools>adb+devices
List+of+devices+attached
4df798d76f98cf6d++++++++unauthorized|code-block|syntax|javascript|1987738|2.撤销在电话上的USB调试|1987739|如果该设备显示为未经授权的，请在手机上转到开发人员选项，然后单击“吊销USB调试授权”(用JellyBean+&+Samsung测试)。|1987740|3.重新启动亚行服务器：|1987741|然后重新启动adb服务器。|1987742|adb+kill-server
adb+start-server|1987743|4.重新连接设备|1987744|设备将询问您是否同意连接计算机id。你得确认一下。|1987745|5.现在检查设备|1987746|它现在被授权了！|1987747|adb+devices
<ANDROID_SDK_HOME>\platform-tools>adb+devices
List+of+devices+attached
4df798d76f98cf6d++++++++device|1987748|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/tools/help/adb.html^0|I|2|0|0|0|9|0|0|0|7|0|W|B|0|0|C|0|0|0|0|8|0|0|0|8|0|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|D|3|E|5|6|7|1I|8|@$A|1J|B|1K|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1L|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1M|8|@$A|1N|B|1O|F|G]]|9|@]|C|$]]|$1|O|3|P|5|6|7|1P|8|@$A|1Q|B|1R|F|G]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1S|8|@$A|1T|B|1U|F|G]]|9|@]|C|$]]|$1|S|3|T|5|6|7|1V|8|@]|9|@]|C|$]]|$1|U|3|V|5|J|7|1W|8|@]|9|@]|C|$K|L]]|$1|W|3|X|5|6|7|1X|8|@$A|1Y|B|1Z|F|G]]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|20|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|21|8|@$A|22|B|23|F|G]]|9|@]|C|$]]|$1|12|3|13|5|6|7|24|8|@]|9|@]|C|$]]|$1|14|3|15|5|J|7|25|8|@]|9|@]|C|$K|L]]|$1|16|3|-4|5|6|7|26|8|@]|9|@]|C|$]]]|17|$18|$5|19|1A|1B|C|$1C|1D]]]]

It's likely that the device is no longer authorized on <a href="http://developer.android.com/tools/help/adb.html" rel="noreferrer">ADB</a> for whatever reason.

1. Check if authorized:

<pre><code>&lt;ANDROID_SDK_HOME&gt;\platform-tools&gt;adb devices
List of devices attached
4df798d76f98cf6d unauthorized
</code></pre>

2. Revoke USB Debugging on phone

If the device is shown as unauthorized, go to the developer options on the phone and click "Revoke USB debugging authorization" (tested with JellyBean &amp; Samsung GalaxyIII).

3. Restart ADB Server:

Then restarted adb server

<pre><code>adb kill-server
adb start-server
</code></pre>

4. Reconnect the device

The device will ask if you are agree to connect the computer id.
You need to confirm it.

5. Now Check the device

It is now authorized!

<pre><code>adb devices
&lt;ANDROID_SDK_HOME&gt;\platform-tools&gt;adb devices
List of devices attached
4df798d76f98cf6d device
</code></pre>

blocks|key|1987793|text|我在两部手机上都有同样的信息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1987794|-+Sony+Xperia+E
-+Samsung+Galaxy+Core+2|code-block|syntax|javascript|1987795|我用以下两个步骤解决了Android+4.4.2的问题：|1987796|1.-将我的亚行更新为1.0.31，从SDK+Manager下载最新版本的Android|1987797|您可以通过键入|1987798|adb+version|1987799|2.-一旦手机插入USB调试模式，就会出现一条消息，要求您授权此计算机进行调试。您必须标记“始终允许此计算机”，并单击+allow+。|offset|length|style|BOLD|1987800|希望能帮上忙。|1987801|entityMap^0|0|0|0|0|0|0|19|A|1N|7|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|6|7|11|8|@]|9|@]|A|$]]|$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|@$Q|15|R|16|S|T]|$Q|17|R|18|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

I had the same message in two phones:

<pre><code>- Sony Xperia E
- Samsung Galaxy Core 2
</code></pre>

both Android 4.4.2, and i solved it with these two steps:

1.- Updating my adb to 1.0.31, downloading the latest version of Android SDK from SDK Manager

You can check your adb version by typing

<pre><code>adb version
</code></pre>

2.- Once the phone is plugged in USB Debugging mode, A message appears asking you to authorize this computer for debugging. You have to mark "Always allow this computer", and click on Allow.

Hope it helps.

blocks|key|1987828|text|这是错误的，因为您的窗口版本没有USB3.0的驱动程序，可以从电话中对接收者进行身份验证。我和这个虫子呆了5天。现在，安装58964_Intel(R)_USB_3.0驱动程序。继续用可怕的代码！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1987829|我使用这个链接下载驱动程序。|offset|length|1987830|entityMap|0|LINK|mutability|MUTABLE|url|http://downloadcenter.intel.com/DownloadManager.aspx?lang=eng&httpDown=http://downloadmirror.intel.com/21129/eng/Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver.zip^0|0|0|E|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

This is error because your window version haven't driver for usb 3.0 to receiver authenticate permission from phone. I spent 5 day with this bug.
Now, install 58964_Intel(R)_USB_3.0 driver. And continue with awesome code! 

<a href="http://downloadcenter.intel.com/DownloadManager.aspx?lang=eng&amp;httpDown=http://downloadmirror.intel.com/21129/eng/Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver.zip" rel="nofollow">i use this link to download driver</a>

blocks|key|2266215|text|我也有同样的问题。解决方法是将"USB计算机连接“设置为”摄像机(PTP)“，而不是”媒体设备(MTP)“。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2266216|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|$]]

I had the same problem. It was resolved by setting "USB computer connection" to "Camera (PTP)" instead of "Media Device (MTP)

blocks|key|1268114|text|我从我的Nexus+10中得到了这个错误。我尝试了我能找到的所有答案，然后我意识到我使用的是一个与往常不同的USB端口。我切换到使用我通常使用的端口，它在我的笔记本电脑的另一边，授权在我的平板电脑上弹出！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1268115|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|$]]

I was getting this error with my Nexus 10. I tried all of the answers I could find, and then I realized I was using a different USB port than usual. I switched to using the port I usually use, which is on the other side of my laptop, and the authorization popped up on my tablet!

blocks|key|1268138|text|作为参考，我刚刚在Linux上遇到了很多相同的问题，并且花了很长时间才弄明白。最后，我确定我有一个根拥有的~/..android目录(由于将亚行作为root运行，同时还试图解决其他连接问题)。删除该根用户拥有的~/..android目录解决了下次我重新连接设备时丢失的授权对话框。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1268139|简单地改变所有权也可能解决了这个问题--我猜这是因为简单地缺乏对存储在其中的亚行密钥文件的访问才是问题的根源。不过，我并没有证实这一点，我也不会故意破坏我来之不易的连接，只是为了检查一下;-)|1268140|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 reference, I just encountered much the same issue on Linux and had a hell of a time figuring it out. I eventually determined that I had a ~/.android directory that was root owned (thanks to running adb as root, while flailing around trying to figure out other connection problems). Deleting that root owned ~/.android directory resolved the missing authorisation dialog next time I reconnected the device.

It's possible that simply changing the ownership would also have fixed the problem - I'm guessing it was a simple lack of access to the adb key file stored inside that was the root of the problem. I didn't verify that, though, and I'm not going to deliberately break my hard-won connectivity just so I can check ;-)

blocks|key|1268146|text|它不可能适用于所有情况，但由于我使用了一条长电缆，我的设备连接不正确，消息不会弹出，改变电缆可能解决问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1268147|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|$]]

it's not may work for all situations but because i used a long cable my device doesnt connect properly and the message wont pop up
change the cable may solve the problem

blocks|key|1988038|text|我尝试了很多方法来解决这个问题，这个方法对我很有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988039|在你的电脑上安装SnapPea。SnapPea|offset|length|1988040|将您的手机插入USB调试模式并打开SnapPea，授权对话框将显示在您的手机上。对话框显示在电话上|1988041|希望能帮上忙。|1988042|entityMap|0|LINK|mutability|MUTABLE|url|http://www.wandoujia.com/|1|http://4.bp.blogspot.com/-kYKWJ_9TjEo/USN-vQqpUPI/AAAAAAAAL3M/xozI-9JuLDM/s1600/adb-debug-confirmation.png^0|0|G|7|0|0|14|9|1|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

I tried many ways to solve this problem, this one works for me.

Install SnapPea on your PC.
<a href="http://www.wandoujia.com/" rel="nofollow">SnapPea</a>

Plug your phone in USB Debugging mode and open SnapPea， a authorization dialog will show on your phone.
<a href="http://4.bp.blogspot.com/-kYKWJ_9TjEo/USN-vQqpUPI/AAAAAAAAL3M/xozI-9JuLDM/s1600/adb-debug-confirmation.png" rel="nofollow">The Dialog shows on the phone</a>

Hope it helps.

blocks|key|1988044|text|adb+usb为我工作--重新启动亚行守护进程，监听命令返回的USB端口：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1988045|错误:设备未经授权。请检查设备上的确认对话框。|blockquote|1988046|。但RSA密钥的提示马上就出现在电话里。一旦我批准了，一切都按预期开始工作了。|1988047|entityMap^0|0|7|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|Q|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|L|$]]

<code>adb usb</code> worked for me 
This restarts the adb daemon listening on the USB port
The command returned: 

<blockquote>
 error: device unauthorized. Please check the confirmation dialog on
 your device
</blockquote>

.
But the prompt for the RSA key showed up on the phone straight away. Once I approved, everything started working as expected

blocks|key|2266430|text|在一些三星设备上，如果不直接重新启动，可以通过拨号*#0808#设置的模式更改就不会继续。一旦重新启动，请拨相同的字符串，并确保选择了adb+%2B+mdp并将USB设置为AP。在此之后，请确保重新连接电话并重新启动亚行服务器。此外，尽量避免USB集线器和虚拟机，这肯定会使事情进一步复杂化。按照前面提到的关于清除授权设备等的说明。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2266431|entityMap^0|P|7|1V|9|2C|2|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]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

On some Samsung devices the mode change that can be set by dialing <code>*#0808#</code> doesn't stick without direct reboot. Once rebooted, dial the same string and make sure that you have <code>adb + mdp</code> selected and USB set to <code>AP</code>. After this make sure to reconnect phone and restart ADB server. Also try to avoid USB hubs and virtual machines witch surely complicate matter further. The follow the previously mentioned instructions for clearing authorized devices etc.

blocks|key|1988091|text|我对此很感兴趣，我关掉了手机的无线网络，获得了许可对话框。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988092|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|$]]

I was tiered with this, I got that permission dialog by turning off wi-fi of my phone.

blocks|key|1988110|text|我手机上没有弹出RSA指纹。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988111|我不得不进入|1988112|++C:\Users\<userName>\.android\adbkey+and+adbkey.pub+|code-block|syntax|javascript|1988113|文件，删除这些文件，然后杀死和重新启动adb服务器。我不得不停止并重新启动调试器，并在PTP模式下作为USB连接。|1988114|因为RSA授权密钥存储在这个路径中，所以杀死和重新启动亚行服务器没有帮助。|1988115|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I was not getting the RSA fingerprint pop up on my phone. 

I had to go into the 

<pre><code> C:\Users\&lt;userName&gt;\.android\adbkey and adbkey.pub 
</code></pre>

files, delete those and then do kill and restart of adb server.
I had to stop and restart the debugger and connecting as USB in PTP mode. 

Because the RSA authorisation key was getting stored in this path, killing and restarting the adb server didn't help.

blocks|key|1988117|text|对我有用的步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988118|1.从usb线缆断开电话|offset|length|style|BOLD|1988119|2.撤销在电话上的USB调试|1988120|3.重新启动设备|1988121|4.重新连接设备|1988122|最重要的部分是重新启动设备。没有它就没用了。|1988123|entityMap^0|0|0|8|0|0|7|0|0|8|0|0|8|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|Q|$]]

Steps that worked for me:
 
1. Disconnect phone from usb cable
 
2. Revoke USB Debugging on phone
 
3. Restart the device
 
4. Reconnect the device
 
The most important part was rebooting the device. Didn't work without it .

blocks|key|1268383|text|我在这个愚蠢的问题上浪费了几个小时。上述任何一种解决方案都不适合我自己。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1268384|我正在运行Windows+10，我有一个旧的手动安装的Android以及Android的SDK。我删除了手动安装的SDK，所有设备都停止工作。这些症状如下：|1268385|$+adb+usb
error:+device+unauthorized.
This+adb+server's+$ADB_VENDOR_KEYS+is+not+set
Try+'adb+kill-server'+if+that+seems+wrong.
Otherwise+check+for+a+confirmation+dialog+on+your+device.|code-block|syntax|javascript|1268386|以及|1268387|$+adb+devices
List+of+devices+attached
id1++++++++unauthorized
id2++++++++unauthorized
id3++++++++unauthorized|1268388|老实说，我不确定这些步骤中的哪些步骤让我得到了我的允许USB调试？提示返回，因此我列出了所有内容，以确保完整性。从最容易到最难。大多数人似乎在前两节之后都能重新站起来。|1268389|重启亚行|1268390|我将在下面每一节之后执行此操作。|1268391|adb+kill-server
adb+usb|1268392|疯狂地使用开发人员选项|1268393|关闭和重新打开开发人员选项|ordered-list-item|1268394|关闭并重新打开USB调试|1268395|撤销USB调试授权。在USB调试启动时尝试此操作，如果可能的话，在USB调试关闭时也尝试。|1268396|应答装置|1268397|拔下USB电缆并将其接回电话。|1268398|在您的PC上切换USB电缆连接到的物理端口。|1268399|切换用于连接设备的物理USB电缆|1268400|开始重新启动所有东西|1268401|重新启动所有设备并重新连接|1268402|重新启动你的电脑|1268403|打开和关闭WIFI|1268404|开始删除一些东西|1268405|警告删除您的~/.android文件夹。有时，此文件夹可能具有错误的权限，这可能会导致问题。您可能需要先备份此文件夹。|offset|length|style|BOLD|CODE|1268406|从添加/删除程序中卸载所有特定于制造商的驱动程序。我卸载了以下+(名称不准确)|1268407|LG联合USB驱动程序|unordered-list-item|1268408|HTC移动USB驱动程序|1268409|OnePlus+USB驱动程序1.00|1268410|三星USB驱动程序|1268411|1268412|​|1268413|我还卸载了所有模拟器及其相应的驱动程序(可选)+|1268414|Nox及相关驱动程序|1268415|Bluestacks|1268416|基因运动|1268417|1268418|1268419|删除所有与Android相关的环境变量。|1268420|如果设置了%25ANDROID_HOME%25，请删除它|1268421|如果设置了%25ANDROID_SDK_HOME%25，请删除它|1268422|此时，我所有的设备神奇地出现，并开始显示允许USB调试？通过亚行提示并正确连接。如果你到现在为止还没有找到解决方案，我真的很抱歉你陷入了这样的困境。确保在所有这些步骤的末尾重新启动了所有设备和开发机器，并使用新的电缆连接到一个新的USB端口。|1268423|如果这样做仍然不起作用，那么尝试其他一些，以便发布关于这个主题的文章：|1268424|Android+ADB设备脱机，无法发出命令|1268425|无法将Nexus+4连接到亚行:未经授权|1268426|如何解决Android亚行主机设备中未经授权的亚行设备？|1268427|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/14993855/android-adb-device-offline-cant-issue-commands|1|https://stackoverflow.com/questions/18011685/cant-connect-nexus-4-to-adb-unauthorized|2|https://stackoverflow.com/questions/26213954/how-to-solve-adb-device-unauthorized-in-android-adb-host-device^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|2|6|A|0|1|1|1|1|1|0|0|1|1|1|1|0|0|0|5|E|0|5|I|0|0|0|0|M|0|0|0|K|1|0|0|S|2|0^^$0|@$1|2|3|4|5|6|7|38|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|39|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|3A|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|3B|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|3C|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|3D|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|3E|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|3F|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|3G|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|3H|8|@]|9|@]|A|$]]|$1|W|3|X|5|Y|7|3I|8|@]|9|@]|A|$]]|$1|Z|3|10|5|Y|7|3J|8|@]|9|@]|A|$]]|$1|11|3|12|5|Y|7|3K|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|3L|8|@]|9|@]|A|$]]|$1|15|3|16|5|Y|7|3M|8|@]|9|@]|A|$]]|$1|17|3|18|5|Y|7|3N|8|@]|9|@]|A|$]]|$1|19|3|1A|5|Y|7|3O|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|3P|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|Y|7|3Q|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|Y|7|3R|8|@]|9|@]|A|$]]|$1|1H|3|1I|5|Y|7|3S|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|6|7|3T|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|Y|7|3U|8|@$1N|3V|1O|3W|1P|1Q]|$1N|3X|1O|3Y|1P|1R]]|9|@]|A|$]]|$1|1S|3|1T|5|Y|7|3Z|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|1W|7|40|8|@]|9|@]|A|$]]|$1|1X|3|1Y|5|1W|7|41|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|1W|7|42|8|@]|9|@]|A|$]]|$1|21|3|22|5|1W|7|43|8|@]|9|@]|A|$]]|$1|23|3|-4|5|6|7|44|8|@]|9|@]|A|$]]|$1|24|3|25|5|6|7|45|8|@]|9|@]|A|$]]|$1|26|3|27|5|Y|7|46|8|@]|9|@]|A|$]]|$1|28|3|29|5|1W|7|47|8|@]|9|@]|A|$]]|$1|2A|3|2B|5|1W|7|48|8|@]|9|@]|A|$]]|$1|2C|3|2D|5|1W|7|49|8|@]|9|@]|A|$]]|$1|2E|3|-4|5|6|7|4A|8|@]|9|@]|A|$]]|$1|2F|3|25|5|6|7|4B|8|@]|9|@]|A|$]]|$1|2G|3|2H|5|6|7|4C|8|@]|9|@]|A|$]]|$1|2I|3|2J|5|Y|7|4D|8|@$1N|4E|1O|4F|1P|1R]]|9|@]|A|$]]|$1|2K|3|2L|5|Y|7|4G|8|@$1N|4H|1O|4I|1P|1R]]|9|@]|A|$]]|$1|2M|3|2N|5|6|7|4J|8|@]|9|@]|A|$]]|$1|2O|3|2P|5|6|7|4K|8|@]|9|@]|A|$]]|$1|2Q|3|2R|5|1W|7|4L|8|@]|9|@$1N|4M|1O|4N|1|4O]]|A|$]]|$1|2S|3|2T|5|1W|7|4P|8|@]|9|@$1N|4Q|1O|4R|1|4S]]|A|$]]|$1|2U|3|2V|5|1W|7|4T|8|@]|9|@$1N|4U|1O|4V|1|4W]]|A|$]]|$1|2W|3|-4|5|6|7|4X|8|@]|9|@]|A|$]]]|2X|$2Y|$5|2Z|30|31|A|$32|33]]|34|$5|2Z|30|31|A|$32|35]]|36|$5|2Z|30|31|A|$32|37]]]]

I wasted hours on this stupid issue. None of the above solutions worked for me on their own. 

I'm running Windows 10. I had an old manual install of the Android SDK as well as Android Studio's SDK. I deleted my manually installed SDK and all my devices stopped working. These were the symptoms:

<pre><code>$ adb usb
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
</code></pre>

as well as

<pre><code>$ adb devices
List of devices attached
id1 unauthorized
id2 unauthorized
id3 unauthorized
</code></pre>

To be honest I'm not sure which of these steps got me my Allow USB debugging? prompts back so I listed EVERYTHING for completeness. Goes in order from easiest to hardest. Most people seem to be back on their feet after the first two sections.

<hr>

<h3>Restart ADB</h3>

I would perform this after each of the sections below.

<pre><code>adb kill-server
adb usb
</code></pre>

<hr>

<h3>Go crazy with developer options</h3>

<ol>
<li>Turn Developer options off and back on</li>
<li>Turn USB debugging off and back on</li>
<li>Revoke USB debugging authorizations. Try this while USB debugging is on and if possible try also when USB debugging is off.</li>
</ol>

<hr>

<h3>Replug devices</h3>

<ol>
<li>Unplug and replug USB cable into phone.</li>
<li>Switch physical ports on your PC that your USB cable is connected into</li>
<li>Switch physical USB cables you're using to connect your devices</li>
</ol>

<hr>

<h3>Start rebooting everything</h3>

<ol>
<li>Reboot all your devices and connect again</li>
<li>Reboot your PC</li>
<li>Toggle WIFI on and off</li>
</ol>

<hr>

<h3>Start deleting things</h3>

<ol>
<li>CAUTION Delete your <code>~/.android</code> folder. Sometimes this folder can have the wrong permissions which can cause issues. You might want to back this folder up first.</li>
<li>Uninstall all manufacturer specific drivers from add/remove programs. I uninstalled the following (names are not exact)

<ul>
<li>LG United USB Driver</li>
<li>HTC Mobile USB Driver</li>
<li>OnePlus USB Drivers 1.00</li>
<li>Samsung USB Driver</li>
</ul></li>
<li>I also uninstalled all emulators and their respective drivers (optional)

<ul>
<li>Nox &amp; related drivers</li>
<li>Bluestacks</li>
<li>Genymotion</li>
</ul></li>
</ol>

<hr>

<h3>Erase all Android related environment variables.</h3>

<ol>
<li>Delete <code>%ANDROID_HOME%</code> if you have it set</li>
<li>Delete <code>%ANDROID_SDK_HOME%</code> if you have it set</li>
</ol>

<hr>

At this point all my devices magically came to life and started displaying the Allow USB debugging? prompts and connecting properly through ADB. If you've made it this far and haven't found a solution, I am truly sorry you're in this predicament. Make sure you've restarted all devices and your dev machine at the end of all of these steps and connect to a fresh USB port using a new cable.

If that still doesn't work try some of these other SO posts on the subject:

<ul>
<li><a href="https://stackoverflow.com/questions/14993855/android-adb-device-offline-cant-issue-commands">Android ADB device offline, can&#39;t issue commands</a></li>
<li><a href="https://stackoverflow.com/questions/18011685/cant-connect-nexus-4-to-adb-unauthorized">Can&#39;t connect Nexus 4 to adb: unauthorized</a></li>
<li><a href="https://stackoverflow.com/questions/26213954/how-to-solve-adb-device-unauthorized-in-android-adb-host-device">How to solve ADB device unauthorized in Android ADB host device?</a></li>
</ul>

blocks|key|2266630|text|在osx和Nexus+5+(A6.0.1)上也有类似的问题。尽管Android和任何其他IDE都可以连接到设备，但我还是得到了授权弹出并确认了这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2266631|原来我的Nexus+(根)丢失了关键文件。|offset|length|style|BOLD|2266632|重新引导Android设备恢复|unordered-list-item|2266633|粘贴在下面的Ran代码|2266634|重新启动Android设备，adb现在识别设备。|2266635|将密钥从计算机推送到Android设备：|2266636|+cd+~/.android+&&+adb+push+adbkey.pub+/data/misc/adb/adb_keys|code-block|syntax|javascript|2266637|解决办法来自这里|2266638|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/36507594/1071184^0|0|B|1|0|0|0|0|0|0|0|8|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|19|8|@]|9|@]|A|$]]|$1|K|3|L|5|J|7|1A|8|@]|9|@]|A|$]]|$1|M|3|N|5|J|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1D|8|@]|9|@]|A|$T|U]]|$1|V|3|W|5|6|7|1E|8|@]|9|@$D|1F|E|1G|1|1H]]|A|$]]|$1|X|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14]]]]

Had similar issue on osx and Nexus 5 (A6.0.1). 
I did get the authorization pop-up and confirmed it, despite that Android Studio nor any other IDE could connect to device.

Turned out my Nexus (rooted) was missing key files.

<ul>
<li>Rebooted Android device into recovery</li>
<li>Ran code pasted below</li>
<li>Rebooted Android device, adb now identifies device</li>
</ul>

Push key from computer to Android device: 

<pre><code> cd ~/.android &amp;&amp; adb push adbkey.pub /data/misc/adb/adb_keys
</code></pre>

<a href="https://stackoverflow.com/a/36507594/1071184">Solution came from here</a>

blocks|key|2266662|text|Linux-Ubuntu-14.04|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2266663|我读了这篇文章的全部答案，没有什么对我有用：|2266664|这可能是因为我没有使用正常的终端用户设备，在公司设备上工作！|2266665|为我工作的事情是：|2266666|从lsusb获取设备的VID、PID，并更新51-android.Rule+(https://source.android.com/source/initializing.html#configuring-usb-access)|2266667|确保adb_usb.ini也用相同的VID、PID更新。|2266668|entityMap|0|LINK|mutability|MUTABLE|url|https://source.android.com/source/initializing.html#configuring-usb-access^0|0|I|0|0|0|0|9|0|13|22|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|N|3|O|5|6|7|19|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]]]

Linux-Ubuntu-14.04 
I read all the answer for this post, nothing worked for me :( 
This may be because I am not using normal end User device, working on corporate device! 

Thing worked for me is: 
Get VID,PID for your device from lsusb and update 51-android.rules (<a href="https://source.android.com/source/initializing.html#configuring-usb-access" rel="nofollow noreferrer">https://source.android.com/source/initializing.html#configuring-usb-access</a>) 
Ensure adb_usb.ini is also updated with same VID, PID

blocks|key|1268501|text|安装了Android之后，我对文件夹“~/.Android”有错误的权限(只对root用户进行读写访问)。所以我修改了它，并从Android运行了项目(设备仍然被标记为“未经授权的”)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1268502|Android显示了“安装apk错误”，但是在文件夹"~/.android“中创建了文件"adbkey”、"adbkey.pub“、"debug.keystore”。|1268503|之后，我重新启动了亚行(ran命令、adb杀毒服务器和adb启动服务器)，并在我的设备上出现了授权对话框。|offset|length|style|BOLD|1268504|希望有人能接近这个解决方案。|1268505|entityMap^0|0|0|H|9|R|8|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@$F|Q|G|R|H|I]|$F|S|G|T|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

After installing Android studio, I had incorrect permissions on the folder "~/.android"(access for reading and writing only for root). So I changed it and ran project from Android studio(device still was marked as "unauthorized"). 

Android studio showed an error "Error installing apk", but in the folder "~/.android" were created files "adbkey", "adbkey.pub", "debug.keystore".

After that I restarted adb (ran commands adb kill-server and adb start-server) and authorization dialog appeared on my device.

Hopefully someone will approach this solution.

blocks|key|1988346|text|为了解决这个问题，我所做的就是再次断开和重新连接usb电缆到USB端口(用我的机器上的另一个端口完成)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988347|然后我选择收费，仅此而已。移动设备要求我允许这台机器进入，我同意了，这就解决了问题。|1988348|在运行亚行设备时，我在列表中看到了该设备。|1988349|(在Windows+10家庭中完成)。|1988350|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|$]]

What I've done to solve the issue was to disconnect and reconnect the usb cable to the USB port again (done with another port on my machine).

Then I have chose to charge and that's it. The mobile device asked me to grant access for the machine, I agreed and that's solved the issue.

When running adb devices, I saw the device in the list.

(Done in Windows 10 home).

blocks|key|2266740|text|这解决了我的问题！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2266741|运行你的android模拟器|ordered-list-item|2266742|转到设置并启用开发人员模式|2266743|从开发人员设置启用usb调试|2266744|此时，您将在模拟器上得到弹出式按摩，以授权该设备，您可以这样做:)|2266745|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

This solved my issue!

<ol>
<li>run your android simulator</li>
<li>go to setting and enable developer mode</li>
<li>enable from the developer settings usb debugging </li>
</ol>

at this point you will get popup massage at you emulator to authorise the device and you are good to go :)

blocks|key|1268608|text|解决方案是将您的文件~/.android/adbkey.pub+(在GNU/Linux上或%25USERPROFILE%25\.android\adbkey.pub上)复制到Android，并将其放置为/data/misc/adb/adb_keys。您需要根权限才能做到这一点。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1268609|您可以通过任何方式(或能够)传输该文件，无论是USB、电子邮件还是临时文件上载服务。在我的例子中，由于这是一个新的Android-x86安装在虚拟机中，没有可用的web浏览器，而且由于网络/TCP亚行无法工作，我不得不实际输入715个字符。|1268610|至少起作用了。|1268611|entityMap^0|A|L|19|X|2P|N|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

The solution is to copy your file <code>~/.android/adbkey.pub</code> (on GNU/Linux, or <code>%USERPROFILE%\.android\adbkey.pub</code> on Windows) to Android, and place it as <code>/data/misc/adb/adb_keys</code>. You need root privileges to do that.

You can transfer the file any way you like (or are able to), be it USB, e-mail or a temporary file upload service. In my case, as it was a new Android-x86 installation in a Virtual Machine, no usable web browser, and with network/TCP adb not working, I had to actually type in the 715 characters.

At least it worked.

blocks|key|1988431|text|我只需尝试一下adb杀毒服务器，它对我来说是有效的：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1988432|PS+C:\Users\languoguang>+adb+devices
List+of+devices+attached
MKJ0117A19000186++++++++unauthorized
PS+C:\Users\languoguang>+adb+shell
error:+device+unauthorized.
This+adb+server's+$ADB_VENDOR_KEYS+is+not+set
Try+'adb+kill-server'+if+that+seems+wrong.
Otherwise+check+for+a+confirmation+dialog+on+your+device.|code-block|syntax|javascript|1988433|杀死并启动亚行服务器：|1988434|PS+C:\Users\languoguang>+adb+kill-server
PS+C:\Users\languoguang>+adb+start-server
*+daemon+not+running;+starting+now+at+tcp:12345
*+daemon+started+successfully
PS+C:\Users\languoguang>+adb+devices
List+of+devices+attached
MKJ0117A19000186++++++++device|1988435|entityMap^0|7|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

I just try adb kill-server, it works for me:

<pre><code>PS C:\Users\languoguang&gt; adb devices
List of devices attached
MKJ0117A19000186 unauthorized
PS C:\Users\languoguang&gt; adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
</code></pre>

kill and start adb server:

<pre><code>PS C:\Users\languoguang&gt; adb kill-server
PS C:\Users\languoguang&gt; adb start-server
* daemon not running; starting now at tcp:12345
* daemon started successfully
PS C:\Users\languoguang&gt; adb devices
List of devices attached
MKJ0117A19000186 device
</code></pre>

blocks|key|2266848|text|如果您使用的是ubuntu，请尝试以root用户的身份运行服务器：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2266849|sudo+adb+kill-server

sudo+adb+start-server|code-block|syntax|javascript|2266850|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|$]]

If you are on ubuntu, try running the server as root:

<pre><code>sudo adb kill-server

sudo adb start-server

</code></pre>

blocks|key|1268713|text|试着强迫亚行创建新的密钥。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1268714|在Linux/OSX上：
$+mv+/..android/adbkey~/..android/adbkey.old$+mv+~/..android/adbkey.PUB~/..android/adbkey.pub.old$亚行杀灭-服务器$亚行启动-服务器|unordered-list-item|1268715|在Windows+10上(谢谢您、帕乌昏迷拉米雷斯、纳文和d4c0d312!)：|offset|length|1268716|-+Go+to+`%25HOMEPATH%25\Android\.android\`
-+Look+for+files+called+`adbkey`+or+`adbkey.pub`.
-+Delete+these+files.+Or,+if+you+want+to+be+on+the+safe+side,+move+them+to+another+directory.
-+Repeat+the+above+steps+in+`%25USERPROFILE%25\.android\`
-+Try+again|code-block|syntax|javascript|1268717|在此之后，我甚至不需要拔出我的手机:授权提示已经存在了。祝好运!|1268718|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/55243629?noredirect=1#comment100523785_55243629|1|https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/55243629?noredirect=1#comment102127906_55243629|2|https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/55243629?noredirect=1#comment108400760_55243629^0|0|0|H|8|0|Q|2|1|T|8|2|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|12|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|13|8|@]|9|@$G|14|H|15|1|16]|$G|17|H|18|1|19]|$G|1A|H|1B|1|1C]]|A|$]]|$1|I|3|J|5|K|7|1D|8|@]|9|@]|A|$L|M]]|$1|N|3|O|5|6|7|1E|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]|Z|$5|S|T|U|A|$V|10]]]]

Try forcing ADB to create new keys.
<ul>
<li>On Linux/OSX:
<pre><code> $ mv ~/.android/adbkey ~/.android/adbkey.old
 $ mv ~/.android/adbkey.pub ~/.android/adbkey.pub.old
 $ adb kill-server
 $ adb start-server
</code></pre>
</li>
<li>On Windows 10 (thank you, <a href="https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/55243629?noredirect=1#comment100523785_55243629">Pau Coma Ramirez</a>, <a href="https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/55243629?noredirect=1#comment102127906_55243629">Naveen</a> and <a href="https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/55243629?noredirect=1#comment108400760_55243629">d4c0d312</a>!):
<ul>
<li>Go to <code>%HOMEPATH%\Android\.android\</code></li>
<li>Look for files called <code>adbkey</code> or <code>adbkey.pub</code>.</li>
<li>Delete these files. Or, if you want to be on the safe side, move them to another directory.</li>
<li>Repeat the above steps in <code>%USERPROFILE%\.android\</code></li>
<li>Try again</li>
</ul>
</li>
</ul>
After this I didn't even need to unplug my phone: the authorization prompt was already there. Good luck!

blocks|key|1988498|text|我在这个问题上被困了很长一段时间，我能够完全回避这个问题，从我的手机连接到的电脑上复制广告键。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988499|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|$]]

I was stuck on this for quite some time, and I was able to side-step the issue completely by copying the adbkey from a computer that my phone would connect to.

blocks|key|1268769|text|我也有过类似的问题。然而，它是用另一种解决办法解决的。我想我也可以在这里分享这个。让我先描述一下我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1268770|我的ubuntu中有Android。android的路径不在环境变量路径中。我使用apt-get命令安装了亚行，它找不到sdk主文件夹，因此显示了未经授权的错误，设备也没有弹出任何东西。我被困在这里了。|offset|length|style|CODE|1268771|然后，我使用前面安装的apt-get+purge卸载了亚行。Android在platform-tools文件夹中有亚行程序。我只是将路径添加到环境变量中，它就像一种魅力。|1268772|export+PATH=${PATH}:/home/YOUR-USERNAME/path/to/adb
adb+devices
List+of+devices+attached
f7f716d56905++++device|code-block|syntax|javascript|1268773|因此，问题不是将Android设置为环境变量路径。|1268774|entityMap^0|0|15|7|0|B|D|12|E|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@$D|X|E|Y|F|G]|$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|11|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|R|$]]

I had a similar problem. However, it was solved using a different solution. I thought I might share this here as well. Let me describe my problem first.

I had the Android SDK in my ubuntu. The path to the android SDK was not in the environment variable path. I installed adb using a <code>apt-get</code> command and it could not find the sdk home folder and hence, it was showing the unauthorized error and the device was not popping up anything as well. I got stuck here.

Then I uninstalled the adb using <code>apt-get purge</code> which I installed earlier. The Android SDK has the adb program in the <code>platform-tools</code> folder. I just add the path to the environment variable and it worked like a charm. 

<pre><code>export PATH=${PATH}:/home/YOUR-USERNAME/path/to/adb
adb devices
List of devices attached
f7f716d56905 device
</code></pre>

Hence the problem was not setting the Android SDK to the environment variable path.

blocks|key|2267013|text|断开设备与计算机的连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2267014|进入开发人员设置。|2267015|关闭开发人员设置。|2267016|打开开发人员设置。|2267017|启用USB调试(以及预先启用的任何其他设置)|2267018|将您的设备重新连接到计算机。|2267019|再试试。|2267020|为我工作，所以希望它对你有用！|2267021|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

Disconnect your device from the computer.

Go into developer settings.

Turn off developer settings.

Turn on developer settings.

Enable USB Debugging (and whatever other settings you enabled beforehand)

Reconnect your device to the computer.

Try again.

Worked for me so hope it works for you!

blocks|key|1988611|text|我用的是一部老式的华为手机。当我插入我的Debian扩展实例时，我会弹出USB计算机连接。如果这是设置为MTP，PTP或“连接到PC软件”，我发现“亚行设备”将失败。但是，如果我将连接选项设置为：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988612|安装SD卡|offset|length|style|BOLD|1988613|然后，我可以运行“亚行设备”，状态从未经授权的设备更改为设备。|1988614|我也打开了：|1988615|USB调试|1988616|entityMap^0|0|0|5|0|0|0|0|5|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|O|$]]

I'm using an older Huawei phone. When I plug in to my Debian Stretch instance I get the USB computer connection popup. If this is set to MTP, PTP or "Connect to PC software" I found that "adb devices" will fail. However, if I set the connection option to:

Mount SD Card 

I then could run "adb devices" and status changed from unauthorized to device. 

Also I turned on:

USB debugging

blocks|key|1988653|text|当我更改我的开发设备时，同样的问题开始出现，它被解决如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988654|$+mv+~/.android/adbkey+~/.android/adbkey.old
$+mv+~/.android/adbkey.pub+~/.android/adbkey.pub.old
$+adb+kill-server
$+adb+start-server|code-block|syntax|javascript|1988655|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|$]]

The same issue started appearing once I changed my development device, it was solved as:

<pre class="lang-sh prettyprint-override"><code>$ mv ~/.android/adbkey ~/.android/adbkey.old
$ mv ~/.android/adbkey.pub ~/.android/adbkey.pub.old
$ adb kill-server
$ adb start-server
</code></pre>

blocks|key|2267118|text|您应该删除该文件：c:\users\_user_name_\.android\adbkey|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2267119|entityMap^0|9|10|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

You should delete the file: <code>c:\users\_user_name_\.android\adbkey</code>

blocks|key|2267164|text|下面是我所做的，它带来了授权提示，并使我的设备出现。我用的是三星的Galaxy+s7边缘。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2267165|在设备上启用开发人员模式和USB调试。|ordered-list-item|2267166|撤销USB调试授权。|2267167|通过USB把你的手机插入电脑。|2267168|拖动通知面板并选择“软件安装”，如下图所示|2267169|📷|atomic|offset|length|2267170|​|2267171|这将开始安装USB驱动程序，并显示USB调试授权提示。|2267172|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/bb38b59266e9aadd702d5ebc29743a21.png|imageAlt^0|0|0|0|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|14|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|15|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|16|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|17|8|@]|9|@$N|18|O|19|1|1A]]|A|$]]|$1|P|3|Q|5|6|7|1B|8|@]|9|@]|A|$]]|$1|R|3|S|5|D|7|1C|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10|11|-4]]]]

Here's what I did that that brought the authorization prompt and made my device appear. I used a Samsung Galaxy s7 edge.

<ol>
<li>Enable developer mode and USB debugging on your device.</li>
<li>Revoke the USB debugging authorization</li>
<li>Plug your phone to computer via USB.</li>
<li>Drag notification panel and select "Software Installation" as shown in the image below

<a href="https://i.stack.imgur.com/qUUiA.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/qUUiA.png" alt="image"></a></li>
<li>This will begin installing USB driver and the prompt for USB debugging authorization will show.</li>
</ol>

blocks|key|2267243|text|在花了一个多小时的时间在三星(主要是谷歌)咒骂了一个多小时之后，我的发现终于帮助我获得了这款设备的认可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2267244|设备上：|ordered-list-item|2267245|设置开发人员模式|unordered-list-item|2267246|允许USB调试|2267247|默认USB配置>选择USB绑定|2267248|将设备连接到PC+USB|2267249|2267250|在PC上：|2267251|提升cmd/ps提示(可能不是强制性的，但这是我的练习)|2267252|adb+kill-server+(在ps中先于.\+)|offset|length|style|CODE|2267253|adb+start-server+(设备连接时)>注意设备上的提示|BOLD|2267254|2267255|2267256|始终允许从这台计算机连接>是的|2267257|2267258|2267259|adb+devices获得以下输出：|2267260|2267261|List+of+devices+attached
278c250cce217ece++++++++device|code-block|syntax|javascript|2267262|entityMap^0|0|1|1|1|1|1|0|1|1|0|F|N|2|1|0|G|N|A|1|0|0|4|1|0|F|1|0|0|5|1|0|I|0|B|1|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1I|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|1J|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|1K|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|1L|8|@]|9|@]|A|$]]|$1|L|3|M|5|G|7|1M|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1O|8|@]|9|@]|A|$]]|$1|Q|3|R|5|G|7|1P|8|@]|9|@]|A|$]]|$1|S|3|T|5|G|7|1Q|8|@$U|1R|V|1S|W|X]|$U|1T|V|1U|W|X]]|9|@]|A|$]]|$1|Y|3|Z|5|G|7|1V|8|@$U|1W|V|1X|W|X]|$U|1Y|V|1Z|W|10]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|20|8|@]|9|@]|A|$]]|$1|12|3|C|5|D|7|21|8|@$U|22|V|23|W|10]]|9|@]|A|$]]|$1|13|3|14|5|G|7|24|8|@$U|25|V|26|W|10]]|9|@]|A|$]]|$1|15|3|-4|5|6|7|27|8|@]|9|@]|A|$]]|$1|16|3|P|5|D|7|28|8|@$U|29|V|2A|W|10]]|9|@]|A|$]]|$1|17|3|18|5|G|7|2B|8|@$U|2C|V|2D|W|10]|$U|2E|V|2F|W|X]]|9|@]|A|$]]|$1|19|3|-4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|1C|7|2H|8|@]|9|@]|A|$1D|1E]]|$1|1F|3|-4|5|6|7|2I|8|@]|9|@]|A|$]]]|1G|$]]

After having spent over an hour going in rounds swearing at Samsung (mostly), Google, and who not, here are my findings, that finally helped me get the device recognized:
<ol>
<li>On Device:
<ul>
<li>Set developer mode</li>
<li>Allow USB debugging</li>
<li>Default USB configuration &gt; Select USB tethering</li>
<li>Connect device to PC USB</li>
</ul>
</li>
<li>On PC:
<ul>
<li>Elevated cmd/ps prompt (maybe not mandatory, but that was my drill)</li>
<li><code>adb kill-server</code> (precede with <code>.\</code> in ps)</li>
<li><code>adb start-server</code> (while device connected) &gt; watch for prompt on device</li>
</ul>
</li>
<li>On device:
<ul>
<li>Always allow connections from this computer &gt; Yes</li>
</ul>
</li>
<li>On PC:
<ul>
<li><code>adb devices</code> gets the following output:</li>
</ul>
</li>
</ol>
<pre><code>List of devices attached
278c250cce217ece device
</code></pre>

blocks|key|1988767|text|对我来说，我首先无意中发现了我的设备，后来我发现了。要将其恢复为重新授权：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988768|将USB设备与膝上型计算机/计算机断开|ordered-list-item|1988769|在“开发人员选项”中单击“撤消USB调试授权”。|1988770|禁用顶部的开发人员选项。|1988771|重新启用它。|1988772|启用USB调试|1988773|在终端上运行命令“adb+kill-server”|offset|length|style|CODE|1988774|在终端上运行命令“adb+start-server”|1988775|将移动设备连接到膝上型计算机/计算机|1988776|重新授权|1988777|按，按)|1988778|注意:如果上面没有工作，在重新连接之前尝试重新启动您的笔记本电脑。|1988779|entityMap^0|0|0|0|0|0|0|9|F|0|9|G|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|16|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|17|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|18|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|19|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1A|8|@$O|1B|P|1C|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|D|7|1D|8|@$O|1E|P|1F|Q|R]]|9|@]|A|$]]|$1|U|3|V|5|D|7|1G|8|@]|9|@]|A|$]]|$1|W|3|X|5|D|7|1H|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|D|7|1I|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1J|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|13|$]]

For me, I firstly unauthorized my device accidentally which I found out later. To revert it back to reauthorise:
<ol>
<li>Disconnect USB device from laptop/computer</li>
<li>Click 'Revoke USB debugging authorisations' in Developer options.</li>
<li>Disable developer options on top.</li>
<li>re-enable it again.</li>
<li>enable USB debugging</li>
<li>run command '<code>adb kill-server</code>' on terminal</li>
<li>run command '<code>adb start-server</code>' on terminal</li>
<li>connect your mobile device to laptop/computer</li>
<li>reauthorize</li>
<li>press like)</li>
</ol>
Note: if above doesn't work, trying restarting your laptop before connecting again

blocks|key|1988805|text|不确定是否有人遇到了和我一样的情况，我把手机插到我的笔记本电脑上，试图运行模拟器。这就是我犯这个错误的原因。如果是这样的话，那就拔掉你的手机，试一试|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1988806|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|$]]

Not sure if someone encountered the same situation like me where I had plugged my phone to my laptop and trying to run the emulator. That's the reason I was getting this error. If that is the case then unplug your phone and try

blocks|key|2267374|text|简单地，从你的设备上关闭开发者选项，再次打开，将USB与设备和工作系统连接起来，打开USB调试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2267375|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, turn off developer options from your device and again turn on, attach USB with the device and working system and turn on USB debugging.

blocks|key|1269115|text|“设备未经授权”时，试图屏幕镜像华为|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1269116|当我试图在屏幕上将华为一部老化的精英scrcpy手机镜像到一台Windows10个人电脑时，我被从scrcpy对“未经授权的装置”信息的FAQ报道中重定向到这个问题。|offset|length|style|CODE|1269117|在手机上启用USB调试后，没有弹出来授权调试，而strcpy将这些错误输出到终端上：|1269118|ERROR:+Device+is+unauthorized:
ERROR:+++++-->+++(usb)++++++AKTBBCB731702690++++++unauthorized
ERROR:+A+popup+should+open+on+the+device+to+request+authorization.
ERROR:+Check+the+FAQ:+<https://github.com/Genymobile/scrcpy/blob/master/FAQ.md>
ERROR:+Server+connection+failed|code-block|syntax|javascript|1269119|解决方案主要涉及华为对Android的非标准修改：|1269120|用USB电缆将手机连接到PC上。|ordered-list-item|1269121|将“通知”列表从电话屏幕顶部向下拖动。|1269122|一个名为"USB连接“的图标应该出现在列表中。|1269123|在呈现的模式中按“照片”。
这个答案建议选择“摄像机”作为连接类型。虽然华为没有使用相同的措辞或菜单结构，但选择"Photos“解决了以下问题|1269124|-+the+"Files"+option+doesn't+support+`adb`+authentication,
-+the+"USB+drive"+option+(which+appeared+to+work+initially)+prevents+or+stops+phone+apps+accessing+files+on+the+sd+card+if+this+connection+option+is+chosen.|1269125|如果出现弹出式窗口，则启用USB调试。|1269126|在这个阶段重新运行scrcpy就像预期的一样，使用鼠标和PC键盘输入手机上的应用程序。在安装过程中，不需要重新启动手机或PC+--如果事情出错，请检查下面的提示。|1269127|scrcpy+Tips|BOLD|1269128|在设置中，在开发人员选项下检查“保持清醒”，以防止在镜像电话时关闭屏幕，并在镜像时再次关闭它。两者都可以在PC上执行。|unordered-list-item|1269129|关闭Windows窗口以自动关闭scrcpy上的adb进程:不要仅仅关闭或中止运行scrcpy.exe的终端窗口。|1269130|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Genymobile/scrcpy|1|2|https://github.com/Genymobile/scrcpy/blob/master/FAQ.md#device-unauthorized|3|https://stackoverflow.com/a/17418469/5217142^0|0|I|6|1D|6|I|6|0|1D|6|1|1K|9|2|0|0|0|0|0|0|0|E|4|3|0|0|0|9|6|0|0|6|7|4|0|6|0|0|G|6|O|3|15|A|0^^$0|@$1|2|3|4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1R|8|@$D|1S|E|1T|F|G]|$D|1U|E|1V|F|G]]|9|@$D|1W|E|1X|1|1Y]|$D|1Z|E|20|1|21]|$D|22|E|23|1|24]]|A|$]]|$1|H|3|I|5|6|7|25|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|26|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|27|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|28|8|@]|9|@]|A|$]]|$1|T|3|U|5|S|7|29|8|@]|9|@]|A|$]]|$1|V|3|W|5|S|7|2A|8|@]|9|@]|A|$]]|$1|X|3|Y|5|S|7|2B|8|@]|9|@$D|2C|E|2D|1|2E]]|A|$]]|$1|Z|3|10|5|L|7|2F|8|@]|9|@]|A|$M|N]]|$1|11|3|12|5|S|7|2G|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|2H|8|@$D|2I|E|2J|F|G]]|9|@]|A|$]]|$1|15|3|16|5|6|7|2K|8|@$D|2L|E|2M|F|17]|$D|2N|E|2O|F|17]|$D|2P|E|2Q|F|G]]|9|@]|A|$]]|$1|18|3|19|5|1A|7|2R|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|1A|7|2S|8|@$D|2T|E|2U|F|G]|$D|2V|E|2W|F|G]|$D|2X|E|2Y|F|G]]|9|@]|A|$]]|$1|1D|3|-4|5|6|7|2Z|8|@]|9|@]|A|$]]]|1E|$1F|$5|1G|1H|1I|A|$1J|1K]]|1L|$5|1G|1H|1I|A|$1J|1K]]|1M|$5|1G|1H|1I|A|$1J|1N]]|1O|$5|1G|1H|1I|A|$1J|1P]]]]

<h2>&quot;Device Unauthorized&quot; when trying to screen mirror Huawei</h2>
I was redirected to this question from <a href="https://github.com/Genymobile/scrcpy" rel="nofollow noreferrer"><code>scrcpy</code></a>'s FAQ coverage of <a href="https://github.com/Genymobile/scrcpy/blob/master/FAQ.md#device-unauthorized" rel="nofollow noreferrer">&quot;Device Unauthorized&quot;</a> messages when trying to screen mirror an aging Huawei Elite S6 mobile phone to a Windows 10 PC.
With USB debugging enabled on the phone, no popup to authorize debugging appeared and strcpy output these errors on the terminal:
<pre><code>ERROR: Device is unauthorized:
ERROR: --&gt; (usb) AKTBBCB731702690 unauthorized
ERROR: A popup should open on the device to request authorization.
ERROR: Check the FAQ: &lt;https://github.com/Genymobile/scrcpy/blob/master/FAQ.md&gt;
ERROR: Server connection failed
</code></pre>
The solution mostly relates to non-standard Huawei modifications to Android:
<ol>
<li>Connect the phone to the PC with a USB cable.
</li>
<li>Drag down the notifications list from the top of the screen on the phone.
</li>
<li>An icon titled &quot;USB Connected&quot; should appear in the list
</li>
<li>Press &quot;Photos&quot; amongst the modes presented.
<a href="https://stackoverflow.com/a/17418469/5217142">This answer</a> suggested selecting &quot;Camera&quot; as the connection type. Although Huawei doesn't use the same wording or menu structure, choosing &quot;Photos&quot; solved issues that
<ul>
<li>the &quot;Files&quot; option doesn't support <code>adb</code> authentication,</li>
<li>the &quot;USB drive&quot; option (which appeared to work initially) prevents or stops phone apps accessing files on the sd card if this connection option is chosen.</li>
</ul>
</li>
<li>Enable USB debugging if a popup appears.
</li>
</ol>
Rerunning <code>scrcpy</code> at this stage worked as expected, with working mouse and PC keyboard input to apps on the phone. No reboots of the phone or PC should be needed during setup - check the tips below if things go wrong.
<code>scrcpy</code> Tips
<ul>
<li>Check &quot;Stay Awake&quot; under developer options in settings to prevent the screen being turned off while mirroring the phone, and turn it off again when done mirroring. Both can be performed from the PC.</li>
<li>Close the <code>scrcpy</code> GUI window to kill the <code>adb</code> process on Windows automatically: don't just close or abort the terminal window running <code>scrcpy.exe</code>.</li>
</ul>

blocks|key|2267426|text|重新检查开发人员选项中的“USB调试”选项帮助了我。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2267427|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|$]]

Recheck 'USB Debug' option in developer options helped me

blocks|key|2267440|text|我只需要遵循这些简单的步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2267441|从膝上型电脑和电话中移除电线.|unordered-list-item|offset|length|style|BOLD|2267442|再次把电线连接到我的手机和笔记本电脑上。|2267443|允许在设备上调试.|2267444|每件事都开始运转良好。|2267445|entityMap^0|0|0|F|0|0|I|0|0|9|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@$E|S|F|T|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|U|8|@$E|V|F|W|G|H]]|9|@]|A|$]]|$1|K|3|L|5|D|7|X|8|@$E|Y|F|Z|G|H]]|9|@]|A|$]]|$1|M|3|N|5|6|7|10|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|P|$]]

I just had to follow these simple steps:
<ul>
<li>Remove the wire from laptop and phone.</li>
<li>Again attached the wire to my phone and laptop</li>
<li>Allowed debugging on the device.</li>
</ul>
And every thing started to work fine.

blocks|key|1269168|text|您需要从设置中启用USB调试|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1269169|如果问题仍然存在，则运行以下命令|1269170|adb+kill-server+adb+reverse+tcp:8081+tcp:8081|CODE|1269171|也试着移除电缆，再插一次插头。|1269172|entityMap^0|9|5|0|0|0|F|G|T|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|S|8|@$9|T|A|U|B|J]|$9|V|A|W|B|J]]|D|@]|E|$]]|$1|K|3|L|5|6|7|X|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|N|$]]

You need to enable USB Debugging from Settings
Then if still the issue persists then run the following command
<code>adb kill-server</code>
<code>adb reverse tcp:8081 tcp:8081</code>
Also try removing the cable and plug it again.

Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.

Unplug/plug, Uncheck/check "Debug Enabled", adb kill-server/adb start-server, restart phone/computer doesn't work for me. On the device authorize dialog never appears (but I remember that dialog appeared before reinstallation). I have no idea how to force this authorize dialog to display. There is no abd_key.pub file in .android directory.
When i try read cpu info DDMS says:

<pre><code>[2014-04-15 12:47:06 - DDMS] device unauthorized. Please check the confirmation dialog on your device.
</code></pre>

Any ideas? Is it possible to generate keys manually without confirmation dialog?

USB Connection
<img src="https://i.stack.imgur.com/ZWtny.jpg" alt="Via USB">

Wireless Connection
<img src="https://i.stack.imgur.com/tnf0A.jpg" alt="Via Wi-fi">

ADB Android Device Unauthorized

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

由于我重新安装了Eclipse (简单地删除并再次下载)，所以我无法在三星Galaxyi9001上调试我的应用程序(使用CyanogenMod -Android4.4.2)。在重新安装之前它运转良好。拔掉/插头，取消检查/检查“调试已启用”，亚行杀死服务器/亚行启动服务器，重新启动电话/计算机对我不起作用。在设备上，从...

问ADB Android设备未经授权
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ADB Android设备未经授权EN