ADB cannot detect my Kindle Fire on Windows 7, but Device Manager can

Question

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?

Solution 1

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

Solution 2

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

Solution 3

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

Solution 4

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.

Solution 5

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.

View more solutions

Comments

[ruedaminute]

this looks really promising, Michael thanks! Will check if it works later today and accept if so :)

[mclark1129]

I had the exact same problem, I copied and pasted the 0x1949 directly from a rooting article and the 'x' was a slightly different character than the standard x. When I deleted and replaced 'x' manually it showed right up.

[Jose Ignacio Hita]

Just in case, if you can't find that file in that path like me, you can download it from: developer.amazon.com/public/resources/development-tools/… Direct link: s3.amazonaws.com/android-sdk-manager/redist/…