ADB 无法识别设备，但 Windows 可以。可能的原因？

发布于 2024-11-05 21:39:22 字数 1521 浏览 3 评论 0原文

是的，另一个“adb devices 不返回任何内容”。看来我又发现了另一个问题案例。

就我而言，我使用的是原型硬件，而不是商业硬件。这在驱动程序级别上没有问题，Windows 会选择提供的驱动程序。设备管理器显示关联的 ADB 设备，以及正确的供应商 ID、产品 ID 和序列号。驱动程序提供商是 Google, Inc，版本 1.0.9.0。所以，那部分没问题。（XP SP3，32 位顺便说一句）

但是，即使 Windows 识别该设备及其 ADB 接口，它也不会列在 adb devices 下。 _{帖子末尾的诊断输出。}

显然，adb-server可能需要.android/ADB_USB.INI中的供应商ID，所以我杀死了它，添加了一行相关供应商 ID（十六进制）（即 0xFFFF 格式）并重新启动 adb-server。该文件说这应该通过 android update adb 来完成，但这不起作用，因为 adb 无法检测到设备，所以这并不奇怪。但这似乎是 ADB 中先有鸡还是先有蛋的设计失败：如何添加无法检测到的设备的供应商 ID？

无论如何，我无法通过这种方式访问我的设备。我如何告诉 adb-server 不要充耳不闻，只相信兼容设备的操作系统列表？

adb 设备的诊断输出：

adb_query: host:devices
_adb_connect: host:version
socket_loopback_client: port 5037 type tcp => fd 100
writex: 100 0x22dcd7 4: 30303063  000c
writex: 100 ok
writex: 100 0x41d41d 12: 686f73743a76657273696f6e  host:version
writex: 100 ok
readx: 100 0x22dc57 4
readx: 100 ok: 4f4b4159  OKAY
readx: 100 0x22dd14 4
readx: 100 ok: 30303034  0004
readx: 100 0x22dd14 4
readx: 100 ok: 30303161  001a
adb_close: 100(lo-client:5037)
_adb_connect: host:devices
socket_loopback_client: port 5037 type tcp => fd 101
writex: 101 0x22dcd7 4: 30303063  000c
writex: 101 ok
writex: 101 0x22ee11 12: 686f73743a64657669636573  host:devices
writex: 101 ok
readx: 101 0x22dc57 4
readx: 101 ok: 4f4b4159  OKAY
readx: 101 0x22ddb7 4
readx: 101 ok: 30303030  0000
readx: 101 0x4c3f80 0
readx: 101 ok:
adb_close: 101(lo-client:5037)
List of devices attached

原文

Yes, another "adb devices return nothing". Seems I've found another problem case.

In my case, I'm running with prototype hardware, not commercial. That's no problem at the driver level, Windows picks up the provided driver. Device Manager shows the associated ADB device, with the correct vendor ID, product ID and serial number. Driver Provider is Google, Inc, version 1.0.9.0. So, that part is OK. (XP SP3, 32 bits btw)

However, even though Windows recognizes the device and its ADB interface, it's not listed under adb devices. _{Diagnostic output at end of post.}

Apparently, adb-server may need the vendor ID in .android/ADB_USB.INI, so I've killed it, added one line with the relevant vendor ID, in hex (i.e. 0xFFFF format) and restarted adb-server. The file says that this should be done via android update adb, but that doesn't work Since adb fails to detect the device, that's no surprise. But it seems a chicken-and-egg design failure in ADB: how do you add the vendor ID of a device you fail to detect?

Anyway, I can't get to my device this way. How do I tell adb-server to stop being deaf and just believe the OS list of compatible devices?

Diagnostic output of adb devices:

adb_query: host:devices
_adb_connect: host:version
socket_loopback_client: port 5037 type tcp => fd 100
writex: 100 0x22dcd7 4: 30303063  000c
writex: 100 ok
writex: 100 0x41d41d 12: 686f73743a76657273696f6e  host:version
writex: 100 ok
readx: 100 0x22dc57 4
readx: 100 ok: 4f4b4159  OKAY
readx: 100 0x22dd14 4
readx: 100 ok: 30303034  0004
readx: 100 0x22dd14 4
readx: 100 ok: 30303161  001a
adb_close: 100(lo-client:5037)
_adb_connect: host:devices
socket_loopback_client: port 5037 type tcp => fd 101
writex: 101 0x22dcd7 4: 30303063  000c
writex: 101 ok
writex: 101 0x22ee11 12: 686f73743a64657669636573  host:devices
writex: 101 ok
readx: 101 0x22dc57 4
readx: 101 ok: 4f4b4159  OKAY
readx: 101 0x22ddb7 4
readx: 101 ok: 30303030  0000
readx: 101 0x4c3f80 0
readx: 101 ok:
adb_close: 101(lo-client:5037)
List of devices attached

分享到QQ

分享到微博