adb 没有看到电话设备（Galaxy Apollo）
我有一个应用程序想在实际手机上测试，我一直在尝试将其安装到三星 Galaxy Apollo 上。手机似乎已被 adb 识别，因此我开始调查：
我在 Windows XP (sp3) PC 上运行 adb
当手机连接时，我的 Samsung Galaxy Apollo 的驱动程序似乎正在运行 我可以看到（通过设备管理器 -> USB 控制器） SAMSUNG USB 复合设备
手机处于调试模式，在手机上我有 2 个有关 USB 的通知：“USB 调试已连接”和“USB 连接”
PC 的 USB 驱动程序来自三星官方开发站点并通过文件 SAMSUNG_USB_Driver_for_Mobile_Phones.exe 安装。
我的问题是，在命令提示符中，当我放置 adb devices 时，找不到手机，列表为空。
我已经寻找这个问题的解决方案两天了，并且经历了很多事情来尝试解决它。
我做过的事情： 连接手机后尝试了 adb Kill-server 和 adb start-server – adb 仍然看不到它
我已经通过运行驱动程序附带的卸载程序卸载了 USB 驱动程序。然后我重新安装了驱动程序 - adb 仍然看不到
我已经通过设备管理器卸载了驱动程序，然后插入手机（USB）并为其供电，并允许驱动程序在 PC 检测到新硬件时自动安装（它安装以前安装的相同驱动程序） – adb 仍然看不到
我的 /user/.android 文件夹中没有“adb_usb.ini”文件，但我不确定这是旧东西还是非 Windows事物。无论如何，我用一行 0x04e8 创建了一个。停止 adb 服务器并再次重新启动它没有效果。
有人可以帮忙吗？我已经到了不知道还能做什么的地步
I have an app I want to test on an actual phone and I’ve been trying to get it on to a Samsung Galaxy Apollo. The phone dosent seem to be reconised by adb and so I’ve started to investigate:
I’m running adb on a Windows XP (sp3) PC
The driver for my Samsung Galaxy Apollo seems to be running when the phone is connected I can see (via device manager->USB controllers) SAMSUNG USB Composite Device
The Phone is in debugging mode, on the phone I have 2 Notifications about the USB: “USB debugging connected” and “USB connected”
The USB driver for the PC came from Samsung official development site and was installed via the file SAMSUNG_USB_Driver_for_Mobile_Phones.exe.
My problem is that in the command prompt when I put adb devices the phone isn’t found the list is empty.
I have been searching for a solution to this problem for 2 days now and have been through a lot of things to try and sort it out.
Things I have done:
Tried adb kill-server and adb start-server after the phone is connected – it still doesn’t get seen by adb
I have uninstalled the usb driver by running the uninstall program that came with the driver. Then I reinstalled the drivers – it still doesn’t get seen by adb
I have uninstalled the driver via device manager then pluged the phone in (USB) and powered it and allowed the driver to automatically install when the PC detects new hardware (it installs the same drivers previously installed) – it still doesn’t get seen by adb
I didnt have a “adb_usb.ini” file in my /user/.android folder but I’m not sure if this is an old thing or a non windows thing. Anyway I created one with one line in with 0x04e8. Stopped the adb server and restarted it again this had no effect.
Can anyone help? I'm to the point where I don't know what else to do
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我发现了这个问题，结果是三星手机的固件问题。
如果您发现遇到此问题，请参考 这里 是金粉。
问题是手机如何更改 USB 模式，在我的情况下，UART 已更改为调制解调器而不是 PDA。一旦我将此模式改回 PDA，一切就正常了。
要访问此 USB 模式设置，您必须拨打 *#7284#，这将显示一个实用程序屏幕，其中有 2 个部分 UART 和 USB 都必须设置为 PDA。建议即使两者都设置为 PDA，也要从 PDA 进行设置并返回到 PDA。
完成此操作后，我将手机插入 PC USB，在“控制面板 -> 系统 -> 硬件 -> 设备管理器”中出现 ADB 设备，并且在输入“adb devices”时会显示该设备android sdk 的 platform-tools 目录显示 adb 现在可以看到我的设备。
然而，这个解决方案应该只是最后的手段，正如 Anass 指出的那样，请确保 USB 调试已打开，并且在采用此解决方案之前安装了正确的 USB 驱动程序。
I have found the problem and it turns out to be a firmware problem with Samsung phones.
If you find you have this problem the advice from here is gold dust.
The problem is that the phone some how changes USB mode in my case the UART had changed to modem instead of PDA. Once I changed this mode back to PDA it all worked.
To access this USB mode setting you must dial *#7284#, this brings up a utility screen which has 2 sections UART and USB both must be set to PDA. The advice is that even if both are set to PDA then set them from PDA and back to PDA.
After doing this I plugged my phone into the PC USB and I get a ADB device appear ADB Interface in “control panel->system->hardware->Device Manager” and the device shows up when typing “adb devices” in the platform-tools directory of the android sdk showing that adb can now see my device.
However this solution should only be a last resort as Anass points out make sure USB debugging is turned on and that the correct USB drivers are installed before resorting to this.
首先，尝试通过菜单>设置>应用程序>开发>USB调试来启用USB调试模式，然后连接
First, try enabling USB debugging mode by going to Menu>Settings>Applications>Development>USB Debugging and then connect
要检查 USB 连接是否正常工作，请将手机连接到 USB 端口，然后运行 adb devices。在 Linux 上，这将如下所示：
如果 adb devices 命令的输出中没有列出设备，请按照以下步骤之一重试，最好从第一个步骤开始（每个步骤后重试）。
To check if your USB connection is functional, connect the phone to a USB port, then run adb devices. On Linux this will look like this:
If there are no devices listed in the output of the adb devices command, follow ONE of the following steps and try again, preferably starting with the first (try again after EVERY step).
我在让 ADB 为我的手机工作时遇到了很多问题。它在固件更新之前的一个阶段一直在工作（现在在英国三星 Galaxy s2 i9100 上运行 Android 4.0.4），但它随机停止工作。我使用的是 XP 64，这可能只是 64 位操作系统的问题。
一直设置了USB调试，安装了驱动，但是ADB无法使用。
许多帮助指南似乎都集中在如何使用 Kies 或仅从 Kies 中提取的驱动程序安装正确的驱动程序，但这很大程度上不是我的问题（或者三星 S2 的 kies 驱动程序不再允许 ADB？）仅限超级用户和busybox，但其他方面具有完全标准的固件（已root，并且在android 4.0.4升级时取消root）。
因此，从安装驱动程序开始，我可以将手机作为 MTP、相机、大容量存储设备和 Kies 连接到手机。我已经安装了 Kies，并多次重新安装了驱动程序，但是在没有 Kies 的情况下，这应该可以正常工作，只需从此处安装最新的驱动程序即可 http://forum.xda-developers.com/showthread.php?t=961956。我在设备管理器“Samsung Android ADB Interface”中列出了一个设备，其驱动程序版本为“2.9.505.831”，但没有 ADB。
看来我的手机上的 uart 连接有问题（如phoneutil 屏幕所示），而且我还需要能够从 google sdk 安装 adb 接口驱动程序。
我无法使用我在其他地方找到的标准方法/指南来完成这些操作。
要通过特殊拨号器代码将 UART 设置改回 PDA 并将 USB 连接改回 PDA *#7284# 不再适用于 Samsung Galaxy s2 i9100 Android 4.0.4（或者至少对我而言） - 我必须下载bettercut apk（我很可能不得不盗版，因为我在市场上找不到它）并手动创建了phoneutil的快捷方式。
更好的剪辑>新快捷方式>没有>所有活动> 在那里
，您可以将设置更改为调制解调器并返回到 pda（以调制解调器模式连接时，xp 列出了一个无法安装的新设备“7 CDS”）。
之后我必须从 SDK (adt-bundle-windows-x86_64\sdk\extras\google\usb_driver) 安装 Google 驱动程序
并允许 Windows XP 64 安装驱动程序，您需要编辑“android_winusb.inf”以添加Samsung Galaxy 作为有效设备。
我将以下行添加到 [Google.NTx86] 和 [Google.NTamd64]。
android_winusb.inf
我找到了添加设备 USB\VID_04E8&PID_6860&MI_00 的说明，但这与我的手机不匹配，我需要手动确定设备 ID 并在 Windows 让我安装驱动程序之前自己添加它。
设备管理器>三星 Android 手机 >三星Android ADB接口>属性>详情>>匹配设备 ID
并且手机 ADB 接口具有以下 ID：
USB\VID_04E8&PID_6860&adb...我如上面添加的（如果您的手机不匹配，您也需要执行此操作）我认为）。然后，我使用“Android Bootloader Interface”更新了“Samsung Android ADB Interface”的驱动程序，现在我可以从 Google SDK 驱动程序中进行选择。
从 Google SDK 安装“Android Bootloader Interface”。
然后，我可以像以前一样重新安装“Samsung Android ADB Interface”驱动程序，或者从 Google SDK 重新安装“Android Composite ADB Interface”，并且 ADB 开始工作（经 ADB 设备测试，我的现在已列出，哇！）。
所以我认为问题主要是缺少Android Bootloader Interface驱动程序，而UART的东西可能会产生一些影响？
然而，在我决定重新root我的手机之前，我确实让ADB工作了（直到我无法使用ADB Explorer时才发现它停止工作，但我相当确定我在不到10分钟之前使用过它）。那么为什么它停止工作我不知道。我非常确定我的 PC 上没有任何变化，因此也许将 UART 模式设置回来并强制重新安装驱动程序就足以修复它。但是，也许 ADB 不再适用于标准三星驱动程序，您还需要从 SDK 安装驱动程序？
我很想知道是否还有其他人也有同样的情况，他们是否知道发生了什么。
I was experiencing massive issues getting ADB to work for my phone. It had been working at one stage prior to a firmware update (Now on Android 4.0.4 on a UK Samsung Galaxy s2 i9100) and it randomly stopped working. I'm on XP 64 and it may only be an issue for 64-bit operating systems.
USB debugging had always been set, the drivers were installed, but ADB would not work.
Numerous help guides all seem to concentrate on getting the correct drivers to install with Kies or with extracted drivers from Kies only but this was largely not my problem (or the drivers with kies for the Samsung S2 no longer allow ADB?) My phone is rooted with superuser and busybox only but otherwise has completely standard firmware (had been rooted and was unrooted when android 4.0.4 was upgraded).
So starting from a point with the drivers installed I can connect to my phone as an MTP, as a Camera, as a Mass Storage device and with Kies. I have Kies installed and have had it reinstall the drivers multiple times but this should probably work fine without Kies and just the latest drivers installed as available from here http://forum.xda-developers.com/showthread.php?t=961956. I have a device listed in Device Manager "Samsung Android ADB Interface" with driver version "2.9.505.831" but no ADB.
It appeared I had an issue with the uart connection on my phone (as shown in the phoneutil screen) and also I needed to be able to install the adb interface driver from the google sdk.
I was able to do neither of these using the standard methods/guides I was able to find elsewhere.
To change the UART setting back to PDA and the USB connection back to PDA via the special dialler code *#7284# no longer works on the Samsung Galaxy s2 i9100 Android 4.0.4 (or at least not for me) - I had to download the bettercut apk (which I may very well had to pirate because I couldn't find it in the market) and made a shortcut to phoneutil manually.
bettercut > new shortcut > no > all activities > phoneutil
There you can change the settings to modem and back to pda (when connected in modem mode xp listed a new device "7 CDS's" which would not install).
After that I had to install the Google driver from the SDK (adt-bundle-windows-x86_64\sdk\extras\google\usb_driver)
And to allow Windows XP 64 to install the drivers you need to edit "android_winusb.inf" to add the Samsung Galaxy as a valid device.
I added the following lines to [Google.NTx86] and [Google.NTamd64].
android_winusb.inf
I found instructions to add a device USB\VID_04E8&PID_6860&MI_00 however this did not match my phone, I needed to manually determine the device ID and add it myself before windows would let me install the drivers.
Device Manager > Samsung Android Phone > Samsung Android ADB Interface > Properties > Details > Matching Device ID
And the phone ADB interface had the following ID:
USB\VID_04E8&PID_6860&adb...which I added as above (if your phone doesn't match you would need to do this too I think). I then updated the driver for "Samsung Android ADB Interface" using the "Android Bootloader Interface" which I can now select from the Google SDK Driver.
Install "Android Bootloader Interface" from Google SDK.
I then was able to reinstall the "Samsung Android ADB Interface" driver as before or the "Android Composite ADB Interface" from the Google SDK and ADB started working (as tested with ADB Devices, mine is now listed, woot!).
So I think the problem was mainly the lack of the Android Bootloader Interface driver, with the UART thing possibly having some effect?
However I did have ADB working BEFORE I decided to re-root my phone (only discovered it stopped working when I couldn't use ADB Explorer however I am fairly certain I had used it not 10 minutes before). So why it stopped working I haven't a clue. I am pretty certain nothing changed on my PC, so perhaps setting the UART mode back and forcing the drivers to reinstall was enough to fix it. However maybe ADB no longer works for the standard Samsung drivers and you need to install the drivers from the SDK too?
I'd be interested to know if there are other folk in the same boat, if they have any idea what happened.