当前位置： 文江博客话题详情

ADB 无法在 Windows 7 上检测到我的 Kindle Fire，但设备管理器可以

发布于 12-18 23:31 字数 706 浏览 5 评论 0原文

所以我把这本书扔到了这个问题上，并认为我已经找出了原因。

我已经下载并安装了 JDK 32 和 64 位。 我已经根据需要安装了Android SDK。 我修改了 google-usb-driver 内部的 android_winusb.inf 以包含 Kindle Fire 设备 ID。 我尝试从亚马逊下载kindle fire windows 7驱动程序（如答案此处所述），并使用它。

我尝试修改该驱动程序以将消防设备 ID 包含在 x86 部分中。

我已经勤奋地杀死并重新启动了 adb，并重新启动了我的 comp 几次，看看是否能神奇地修复它。没有什么。

我唯一不确定的是adb_usb.ini的修改。不幸的是，我的 .android 文件夹不存在于我的 %USERPROFILE% 中，而是存在于我计算机上的另一个位置。该文件夹也没有 adb_usb.ini。因此，我将 .android 的内容复制到我的 %USERPROFILE% 中，并在每个文件中创建 adb_usb.ini，并将 0x1949 添加到该空文件中。

这不起作用。 adb devices 仍然显示为零。

我认为 adb 找不到我的 adb_usb.ini，但实际上，我不知道。如果是这样的话，我不知道如何解决。帮助？

原文

So I've thrown the book at this problem and think I've isolated the cause.

I've downloaded and installed JDK 32 and 64 bit.
I've installed the Android SDK as needed.
I've modified android_winusb.inf inside of the google-usb-driver to include the Kindle Fire device IDs.
I tried downloading the kindle fire windows 7 driver from amazon (as described in the answer here), and using that.

I tried modifying that driver to include the fire device ID in the x86 section.

I've killed and restarted adb diligently, and restarted my comp several times to see if that would magically fix it. nothing.

The only thing I'm unsure about is the modification of adb_usb.ini. Unfortunately, my .android folder doesn't exist in my %USERPROFILE%, but instead exists in another location on my computer. That folder doesn't have adb_usb.ini either. So I copied the contents of .android to my %USERPROFILE%, and created adb_usb.ini in each, and added 0x1949 to that empty file.

This did not work. adb devices still turns up zilch.

I think adb is having trouble finding my adb_usb.ini, but really, I have no idea. And if that is the case, I don't know how to fix that. Help?

如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论， 你可以免费 注册 一个本站的账号。

评论（17）

浮光之海2024-12-25 23:31:40

只需将 0x1949 添加到 adb_usb.ini 对我来说就足够了。

Just adding 0x1949 to the adb_usb.ini was enough for me.

回复 原文
望笑2024-12-25 23:31:40

确保您已在 adb_usb.ini 文件中添加了正确的产品/供应商 ID。

仅在添加 0x1949 后我才遇到同样的问题，我可以看到列出的设备。
要么亚马逊正在更改 ID，要么人们在随机论坛中提供了错误的 ID。第一个肯定不是必需的。

添加产品 ID 后，我的 adb_usb.ini 看起来像这样，我认为你的 .android 位置并不重要

0x0e79 
0x006 
0x1949

Make sure that you have added the right product/vendor id in adb_usb.ini file.

I had the same exact problem only after adding 0x1949 I could see the device listed.
Either amazon is changing the id's or people are giving wrong id's in random forums. The first one is definitely not required.

After adding the product id's my adb_usb.ini looks like this and I don't think your .android location matters

0x0e79 
0x006 
0x1949
回复 原文
只为守护你2024-12-25 23:31:40

这也让我发疯。做了其他链接和帖子的推荐，但没有用。运行不带选项的 adb 命令后，我看到了一个 USB 选项。我执行了以下命令：

adb kill-server
adb usb

此后您应该看到一些输出，我没有保存结果

adb devices

现在显示了我的设备

This was driving me crazy also. Did recommendations from other links and posts and did not work. After running adb command without options, I saw an option for usb. I executed the following:

adb kill-server
adb usb

you should see some output after this, I didn't save the results

adb devices

Now showed my device

回复 原文
笛声青案梦长安2024-12-25 23:31:40

输入您的 adb_usb.ini

cd /users/username
type adb_usb.ini

确保它显示 0x1949... 我的有一个特殊字符而不是 x。编辑该文件并将其手动更改为 x。

Type out your adb_usb.ini

cd /users/username
type adb_usb.ini

Make sure it shows 0x1949... mine had a special character instead of the x. Edit the file and change it manually to an x.

回复 原文
划一舟意中人2024-12-25 23:31:40

您的设备驱动程序无法正常工作，请访问以下链接并更新

your device driver is not working go to the following link and update

http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/

回复 原文
楠木可依2024-12-25 23:31:40

另外，当您从头开始创建文件时，请仔细检查 Windows 是否偷偷摸摸地将您的 adb_usb.ini 保存为 adb_usb.ini.txt！

Also double check that Windows isn't being sneaky and actually saving your adb_usb.ini as adb_usb.ini.txt when you create the file from scratch!

回复 原文
想你的星星会说话2024-12-25 23:31:40

就我而言，Windows 使用的是默认驱动程序。我卸载了Windows驱动程序。

已在 \android-sdk\extras\amazon\kindle_fire_usb_driver 安装驱动程序。运行以下内容：

adb kill-server
adb usb

此后您应该看到一些输出，我没有保存结果：

adb devices

设备终于出现了。然后 Kindle 出现在设备管理器中。之前没有出现在那里。

In my case, Windows was using the default driver. I uninstalled the windows driver.

Installed the driver at \android-sdk\extras\amazon\kindle_fire_usb_driver. Ran the following:

adb kill-server
adb usb

You should see some output after this, I didn't save the results:

adb devices

Device finally showed up. Kindle then showed up in device manager. Was not showing up there before.

回复 原文
你好，陌生人2024-12-25 23:31:40

在 %android_sdk%\extras\amazon\kindle_fire_usb_driver 文件夹中，您可以找到 KindleDrivers.exe 文件。只需运行它，Windows 的 Kindle 驱动程序（我的例子是 Win7）就会被安装。

In the %android_sdk%\extras\amazon\kindle_fire_usb_driver folder you can find KindleDrivers.exe file. Just run it and Kindle drivers for Windows (Win7 in my case) will be installed.

回复 原文
叶落知秋2024-12-25 23:31:40

听起来你已经做了所有正确的事情。对我来说，adb_usb.ini 文件就达到了目的，它位于 c:/users/dirk/.android/adb_usb.ini 中。奇怪的是，我还在另一行添加了产品 id 0x006，我认为这并不重要（0x1949 是供应商 id）。

确保 adb_usb.ini 与 avd 文件夹位于同一文件夹中。您可以尝试创建一个新的 AVD，然后查看新的 AVD 是在哪个用户下创建的。

希望这有帮助。

That sounds like you've done all the right things. For me the adb_usb.ini file did the trick and it's in c:/users/dirk/.android/adb_usb.ini. Oddly, I also added the product id of 0x006 on another line, thought I don't think that matters (the 0x1949 is the vendor id).

Make sure the adb_usb.ini is in the same folder as your avd folder. You can try creating a new AVD and look around to see under which user the new one was created.

Hope this helps.

回复 原文
秉烛思2024-12-25 23:31:40

所以我遇到了和你完全相同的问题，而且我也遇到了在我的 c 驱动器而不是 d 驱动器中查找 java.exe 的问题。我以同样的方式解决了这个问题。使用“mklink”命令行工具在 C 驱动器中创建到其他驱动器上的 .android 文件夹的符号链接。我的确切命令是：

mklink /D .android D:\.android

我在我的 C:\Users\\ 文件夹中

然后我运行了 adb再次杀死服务器和 adb devices，它就出现了！

希望有帮助。

So I had the exact same problem as you and I also had a problem with it looking for java.exe in my c drive instead of my d. I fixed this issue the same way I fixed that. Use the "mklink" command line tool to create a symbolic link in the C drive to your .android folder on your other drive. My exact command was:

mklink /D .android D:\.android

I was in my C:\Users\<User Name>\ folder

After that I ran adb kill-server and adb devices again and it showed up!

Hope that helps.

回复 原文
通知家属抬走2024-12-25 23:31:40

添加这个对我有用

0x1949
0x006

Adding this worked for me

0x1949
0x006
回复 原文
荒人说梦2024-12-25 23:31:40

这里的主要问题很简单：由于某种原因，当您安装驱动程序时，user/.android 中的 adv_usb.ini 版本不包含

我检查过的供应商 ID，并且文件是普通的。

我所要做的就是将 ini 文件从驱动程序文件夹复制到 username/.android 并执行 adb Kill-server，然后执行 adb usb 并识别设备。

The main issue here is simple: for some reason when you install the drivers, the version of adv_usb.ini in the user/.android does not contain the vendor ID

I've check and the file was plain.

All that I had to do was to copy the ini file from the driver folder into username/.android and do a adb kill-server, followed by adb usb and the device was recognized.

回复 原文
赠佳期2024-12-25 23:31:40

一般来说，从 /Tools 文件夹运行“android update adb”应该足以更新正确的 adb_usb.ini 文件。该文件的位置是相关的，因为 adb 只会查找其中之一。我在 sdkuilib.jar 中有一个 CRC 错误，并且无法复制。这导致“android update adb”失败，因此我的 adb_usb.ini 文件没有更新。

另外，当我手动更新时，我以 joe 用户身份登录，但我提升为管理员用户来执行更新。我修改了 adb_usb.ini 的 joe 用户副本 (c:\users\JoeUser.android\adb_usb.ini)，但 adb 程序改为查看 adb_usb.ini 的管理副本 (c:\users\Admin.android\adb_usb .ini）。所以，adb没有看到我手工添加的0x1949。

一旦我替换了 sdkuilib.jar 的副本（通过重新下载、安装在单独的文件夹中并复制错误文件），我就能够运行“android update adb”并且 0x01949 显示在我的管理 adb_usb.ini 中。 [为了找到这个，我在 android.bat 和 find_java.bat 文件的顶部将 echo off 更改为 echo on。]

之后，我执行了 adb Kill-server 和 adb usb。但我仍然收到“错误：找不到设备”消息。这时我才注意到我的 Kindle Fire 超时了。我重新打开它，解锁它，此时，kill-server“adb usb”序列产生“以 USB 模式重新启动”。

生成输出后，adb 设备就会显示我的 Kindle Fire。

In general, running "android update adb" from the /Tools folder should be enough to update the correct adb_usb.ini file. The location of this file is relevant as adb will only look for one of them. I had a CRC error in sdkuilib.jar, and it would not copy. This caused "android update adb" to fail, so my adb_usb.ini file did not get updated.

Also, when I went to update by hand, I was logged on as joe user, but I elevated to admin user to perform the update. I modified the joe user copy of adb_usb.ini (c:\users\JoeUser.android\adb_usb.ini), but the adb program looked instead at the admin copy of adb_usb.ini (c:\users\Admin.android\adb_usb.ini). So, adb did not see the 0x1949 that I added by hand.

Once I replaced my copy of sdkuilib.jar (by redownloading, installing in a separated folder, and copying over the bad file), I was able to run "android update adb" and 0x01949 showed up in my admin adb_usb.ini. [To find this, I changed echo off to echo on at the top of both the android.bat and find_java.bat files.]

After that, I did an adb kill-server and adb usb. But I still got the "error: device not found" message. Only then did I notice that my Kindle Fire had timed out. I turned it back on, unlocked it, and at that point, the kill-server "adb usb" sequence produced "restarting in USB mode".

Once that output was produced, the adb devices showed my Kindle Fire.

回复 原文
川水往事2024-12-25 23:31:40

我有这个问题很长时间了 - 迈克尔的回答引导我找到了为我解决这个问题的答案。

如果您当前没有 C:\Users\[用户名]\.android 文件夹，请手动添加一个。将 adb_usb.ini 复制到此文件夹中。如果您尝试在 Windows 资源管理器中创建此文件夹（文件夹可能以句点开头），Windows 可能会给您带来一些麻烦。我必须打开 cmd 并输入 move android .android 才能完成此操作。

完成此操作后，adb devices 立即显示该设备。

I had this exact issue for the longest time - Michael's answer lead me to the answer that fixed this for me.

If you don't currently have a C:\Users\[Username]\.android folder, add one manually. Copy adb_usb.ini into this folder. Windows may give you some trouble if you try to create this folder in Windows Explorer (beginning the folder with a period, probably). I had to open cmd and type move android .android to accomplish this.

After doing this, adb devices immediately showed the device.

回复 原文
初见终念2024-12-25 23:31:40

供以后的读者参考：

不要忘记打开设备上的 USB 调试。 （至少就我而言，在 OUYA 上，此功能默认处于禁用状态。）

For future readers' reference:

Don't forget to turn on USB debugging on the device. (At least in my case, on OUYA, this is disabled by default.)

回复 原文
零崎曲识2024-12-25 23:31:40

如果您使用的是 Windows 并且安装了 Android SDK（如果设置了 ANDROID_SDK_HOME 环境变量），则 adb 将使用 %ANDROID_SDK_HOME%\.android\adb_usb。 ini 而不是 %USERPROFILE%\.android\adb_usb.ini

另外这篇文章有一个命令来填充您的adb_usb.ini 包含所有当前连接的 adb 设备的供应商 ID。

If you are using Windows and you have the Android SDK installed (if ANDROID_SDK_HOME environment variable is set) then adb will use %ANDROID_SDK_HOME%\.android\adb_usb.ini instead of %USERPROFILE%\.android\adb_usb.ini

Also this post has a command to populate your adb_usb.ini with Vendor IDs of all currently connected adb devices.

回复 原文
梦里寻她2024-12-25 23:31:40

就我而言，我必须安装 Kindle Fire 驱动程序。

如果您在本地磁盘中找不到它，您可以从亚马逊官方页面下载：
https://developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing< /a>

直接链接：
https://s3.amazonaws.com/android-sdk-manager/redist /kindle_fire_usb_driver.zip

In my case, I had to install Kindle Fire drivers.

If you can't find it in your local disk, you can download from official Amazon page:
https://developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing

Direct link:
https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip

回复 原文
~没有更多了~

关于作者

破晓

暂无简介

文章
评论
26 人气
发私信

相关话题

更多

热门标签

操作系统 程序设计 IT运维 Linux系统管理 JavaScript 服务器应用 solaris C/C++ PHP Shell BSD Vue.js aix Oracle Python HTML 系统管理 HTML5 CSS 前端
更多

推荐作者

甲如呢乙后呢

文章 0 评论 0

王权女流氓

文章 0 评论 0

云雾

文章 0 评论 0

wyh2033345759

文章 0 评论 0

乖乖

文章 0 评论 0

qq_xR3jkM

文章 0 评论 0

更多

友情链接

文江博客
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
原文