Develop Bugs

Device not recognized on ADB?

I don't want to bother you with stupid threads and things like that, but I've used the search function on XDA and I'm still lost on this really small problem - my Kindle Fire is not being recognized anymore in ADB.
See, a long time ago (few weeks) I rooted my KF and installed Android Market, whatever. Never installed a recovery or custom ROM. Everything was ok until I tried to install TWRP using Kindle Fire Utility.
While trying to install, I got the famous "adbd cannot run as root in production builds". So I thought it was something with my drivers. Ok, then I installed the drivers that come with KFU - just to screw with everything. My Kindle Fire stopped being recognized by ADB.
I tried: (1) uninstall the drivers and install from KFU again. (2) uninstall the drivers and install the drivers I got from the video-tutorial (the famous one). (3) factory reset the kindle fire and do all the drivers install again. (4) hold the power button 900 seconds to reset the kindle fire and install the drivers again. (5) finally install the drivers on ANOTHER computer (running WinXP instead of Win7) and plug my factory reseted KF.
I gave up.
I don't know why my Kindle Fire isn't recognized by ADB on any computer at all. I thought it was my laptop, but then I tried the same steps I did at the first time using a Windows XP and no good. I don't know.
Can someone help me? Thanks a lot.

i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
or you can try this solution:
http://forum.xda-developers.com/showthread.php?t=1430038

b63 said:
i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
Click to expand...
Click to collapse
Tried that and didn't work.
I'm going to wait a little more before using Linux, I really wanted to do this using Windows only.

in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu

b63 said:
in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu
Click to expand...
Click to collapse
Right now my KF is normally booting into stock ROM and stock everything.
I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Thanks for your support.

I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
Click to expand...
Click to collapse
xp will be the better choice cause you don't have to hassle with 32/64 bit drivers and the uac (user access control)
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Click to expand...
Click to collapse
add it in another line
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Click to expand...
Click to collapse
seems that the patched version (the whole thread) is deleted - you will have to do it by yourself - take the original from the dev section and:
http://forum.xda-developers.com/showthread.php?t=1454913

The issue persists. I've seen that other people are having the same issue. The device got "unrooted" by unknown reasons and then it's invisible to any adb. As I'm writing to you right now, I'm trying the adb on my brother's Ubuntu. I've tried other solutions using linux but without success.
I'm running out of options here.
I'll admit that I haven't tested the last link you sent, but I can't see how that can change the way adb works on my device. Anyway I'll try that tomorrow.

in the meantime br3 is out - if you use kfu you will have to use an updated run.bat: http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
but you'r right - that will not change the communication
firekit http://forum.xda-developers.com/showthread.php?t=1430038
is worth a try cause linux don't use drivers to communicate
only needs some entries which are included in firekit
maybe try an other cable ?
really running out of ideas at this point ...

I got the same problem.
If you can fix it, please show me how, thank you.
c:\KindleADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
c:\KindleADB>

Just a quick idea. Have you tried the attach the kindle to a different USB port? I had the same issue until I used a different port. The front ports on my desktop are totally fubar, but the port where my mouse was worked when 4 out of 6 ports did not. This for me is probably a hardware problem, but it may help someone.
Sent from my Kindle Fire using Tapatalk

I am having the same exact problem as the OP and I truer everyway to root it and install the drivers but its still not recognized by adb

Its seems i should give up

Similar problem with cm9, and fixed
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.

Push push push it

tried all the steps. and still nothing. dont know what im doing wrong. starting to get pissed. any help would be great, thanks

Save my KF
sudogeek said:
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.
Click to expand...
Click to collapse
Could you help me to fix same problem with window. My PC alway, automatic recognize my KF as normal disk driver. I try to make a factory cab but not success .
Thanks.

Edit android-path.sh
1. On my Mac I opened System Profiler, then checked Hardware > USB > and 'MyDeviceName' (for me its: LePan Tablet PC)
2. Opened this file with a text editor: /Users/MyName/.android/android-path.sh
3. Added a new line in this file with the tablet Vendor Id, for example:
0x22a4
4. Executed: adb kill-server
5. Executed: adb start-server
6. Finally adb devices is showing:
List of devices attached
0163AE9D0801F02C0C280002 device

Bricked?
I think I'm having the same problem, or at least a very similar one.
Using windows XP. I got the drivers working, plugged my kindle into the Kindle Fire Utility, and ran option 2, which seemed like it was the option to create a backup in case you bricked your kindle. It ran, showed up on the Kindle screen, and did it's thing without a problem.
Then, when the kindle rebooted, I got the yellow-triangle-fire symbol. It says 'press power button for recovery', but pressing the power button does nothing. Holding it down for a long time shuts the kindle down, but pressing it again brings it right back to the yellow-triangle-fire symbol.
So I uninstalled the drivers from Windows XP (as another thread mentioned). I now have two ways that I can think of to install the drivers. Using the KFU, I get the "unsigned drivers" shutdown even after I went into the Driver Signing menu and chose "ignore and install regardless".
The other option I have is to install the drivers that I downloaded manually -- the same ones that worked in the first place. Problem with that is that I go through the entire process, selecting the directory the drivers are in and whatnot, and the only thing that happens is I get an error that says "These drivers aren't the drivers for your hardware" or something similar to that.
So neither of my options allow me to actually install drivers for my Kindle Fire, and my Fire itself is in a recovery loop. All of the tools that are supposed to address the recovery loop require drivers, so I seem to be up a creek without a Fire.
Any ideas?

Okay, to enter recovery...When you see the yellow triangle, hold the power button until it turns orange then release. It shouldn't take more than 10-15 seconds. If you still can't get into recovery, reinstall it.
For your drivers...uninstall completely and delete them if you're using Win7. Then reinstall using one of the previous methods.

The power button doesn't do anything when I push it. It stays bright green until the kindle fire shuts down. I'm not sure what "reinstall it" means, sorry, n00biness.
The drivers (winXP as mentioned) I've uninstalled, but I can't reinstall. One option says "unsigned drivers" and the other doesn't recognize the device as a Kindle and thus quits the install with a "this is not an appropriate driver for your device" message.
Thanks for trying, though! I appreciate your time and effort.

Kindle Fire get ADB working device FOUND solution for KFU

Had been searching on & off over 2 months & finally found the sol
This now lets you use the KFU util and others to root & install new OS etc
You need to have installed ANDROID SDK and extras-usb & JAVA se
1)
you will need to modify the following two files:
a. adb_usb.ini – You can find it under your Users\YourUsername\.android folder
In a typical Windows 7 installation, adb_usb.ini will be located under C:\Users\YourUserNameHere\.android
Open the adb_usb.ini file with a text editor (Notepad is just fine) and add the following line at the end (on a new line). Save and exit.
0×1949
2)
android_winusb.inf – You can find it under the folder you installed the Android SDK, in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Open the file with a text editor (notepad is again good enough), locate [Google.NTx86] section and also the [Google.NTamd64] section and add the following lines to each section, like in the screenshot.
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
3)
Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.
Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.
Ok now you can
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
d. type adb kill-server followed by enter
e. type adb devices. If everything is fine, you should see a connected device (your Kindle Fire)
0000666665555 device
You are good to go
Cheers to dudes @ "reviewhorizon.com/2011/11/how-to-root-jailbreak-kindle-fire-using-one-click-solution-superoneclick-also-enable-sideloading-apps/"

Congrats... glad to hear you got things working. It's nice to see a user's first post be a success story rather than a cry for help. I'm guessing KFU's driver installer didn't work for you for some reason and you had to do it this way.
This is going to be a day late and a dollar short in your case, but you might try it this way if there's a next time around...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You don't really have to install the SDK to get these drivers installed. You can get everything you need in the KFU distribution with the .inf and .ini files already edited for you. Good luck.

Device Not Found in ADB
Another way to fix the driver issue.
Uninstall driver from device manger. Select delete driver if the option is available.
Copy the driver file somewhere else on your computer
Delete the driver from the old location.
Attach the Kindle and manually install the driver from the new location.
I'm not sure why this worked for me, but after half a day of trying this worked.

This is what FINALLY worked for me
http://www.jayceooi.com/2011/12/29/how-to-install-kindle-fire-adb-usb-driver-video/

joehlmann said:
Had been searching on & off over 2 months & finally found the sol
This now lets you use the KFU util and others to root & install new OS etc
You need to have installed ANDROID SDK and extras-usb & JAVA se
1)
you will need to modify the following two files:
a. adb_usb.ini – You can find it under your Users\YourUsername\.android folder
In a typical Windows 7 installation, adb_usb.ini will be located under C:\Users\YourUserNameHere\.android
Open the adb_usb.ini file with a text editor (Notepad is just fine) and add the following line at the end (on a new line). Save and exit.
0×1949
2)
android_winusb.inf – You can find it under the folder you installed the Android SDK, in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Open the file with a text editor (notepad is again good enough), locate [Google.NTx86] section and also the [Google.NTamd64] section and add the following lines to each section, like in the screenshot.
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
3)
Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.
Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.
Ok now you can
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
d. type adb kill-server followed by enter
e. type adb devices. If everything is fine, you should see a connected device (your Kindle Fire)
0000666665555 device
You are good to go
Cheers to dudes @ "reviewhorizon.com/2011/11/how-to-root-jailbreak-kindle-fire-using-one-click-solution-superoneclick-also-enable-sideloading-apps/"
Click to expand...
Click to collapse
Mine just says Android ADB Interface

Combo of a problem
threed42 said:
Mine just says Android ADB Interface
Click to expand...
Click to collapse
I found that this started to happen to me after some ROMs I was flashing ended up getting stuck on the bootscreen. I am not sure what I did in the process, but I messed up my USB drivers. Now no matter how I configure them. I can't seem to get the device to recognize. Even though both windows devices registers the Kindle, it still won't allow me file system access. No matter which rom I try flashing.. I find that nothing seems to work.
I am trying to now restore individual segments to see if I can atleast get a boot up.. otherwise I am dead in the water.
Any help?
Oh yeah, Fastboot.. works fine.. isn't there a stock image I can just fastboot Upgrade?
John

KF not recognized in PC. Shows up as GT-P1000 instead and sdcard access.
Noob to XDA so forgive if this post is in the wrong area. I am at my wits end.
ADB: KF to PC connectivity lost after ROM install
The Good News, Bad News and Solution Attempts…
The Good News.
I installed the GedeROM CM9 ICS 4 (GedeROM ICS v4.04 CM9 Kernel v3.0.21) to my 1st generation Kindle Fire and it runs great. It is much smoother at running Air for Android with an App that I have been developing. The USB Host works great with my Logitech Wireless Keyboard and Mouse Combo with the OTG USB Dongle and Logitech nano receiver. I want to keep using this ROM as it is very functional for my needs.
The Bad News.
Now, let’s get to the frustrating part. No more drag and drop. After the install, my PC no longer recognizes the it as a Kindle Fire as a drive or sdcard. It recognizes it as a GT-P1000 (Galaxy Tab P1000). Because of this mis-reporting to the PC device manager the KF and sdcard are no longer visible as a drive on the PC for me to browse, drag and drop items.
The Device Manager sees the
---Android Phone > Android ADB Interface
or depending on the driver
---Android Phone > Android Composite ADB Interface
and no where in the Device Manager does it show the Kindle Fire any longer.
The only place the device is listed is in
---Control Panel > Hardware and Printers > GT-P1000(!). (Unknown Device)
Attempted Solutions.
1. Driver Reinsall(s) with and without SDK.
I tried reinstalling the drivers for the KF and this changed it from Android Composite ABD Interface to Android ADB Interface. (no change) I reinstalled the Composite interface and still no KF. I also tried a few different versions of drivers up and down the spectrum trying to get this installed. Including trying to install a GT-P1000 driver from Samsung. Still no luck.
2. Android Debugging
I tried to turn on and off and on etc the Android debugging in Settings > Developer Options > Android Debugging. No Luck.
3. Turn on USB Mass Storage
Unable to do this as the options are simply just not there.
4. Reboots
Countless reboots (PC and KF) and cache wipes with and without the KF attached.
5. Different ROM
I tried a different ROM for Jelly Bean 4.2 and it was successful and recognized as a KF and I could browse to the folders on the sdcard. However this ROM was so striped down that it was not really functional for me as there was no file explorer, market app, or any way to browse to the sdcard to install any app that I could drag and drop into the sdcard in the hopes of installing a file explorer and market app. The issue seems to be with the GedeROM CM9 that I am using.
Am I going to have to try multiple ROMS until something works?
Specs:
Kindle Fire (1st Gen, spring of 2012, original one purchased in December 2011, but suffered screen smash)
GedeROM ICS v4.04 CM9 Kernel v3.0.21
The PC I am using is running Windows 7 Professsional.
kinfauns said:
Congrats... glad to hear you got things working. It's nice to see a user's first post be a success story rather than a cry for help. I'm guessing KFU's driver installer didn't work for you for some reason and you had to do it this way.
This is going to be a day late and a dollar short in your case, but you might try it this way if there's a next time around...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You don't really have to install the SDK to get these drivers installed. You can get everything you need in the KFU distribution with the .inf and .ini files already edited for you. Good luck.
Click to expand...
Click to collapse

Work Around Found... Sort of.
KF_Mike_KF said:
Noob to XDA so forgive if this post is in the wrong area. I am at my wits end.
ADB: KF to PC connectivity lost after ROM install
The Good News, Bad News and Solution Attempts…
The Good News.
I installed the GedeROM CM9 ICS 4 (GedeROM ICS v4.04 CM9 Kernel v3.0.21) to my 1st generation Kindle Fire and it runs great. It is much smoother at running Air for Android with an App that I have been developing. The USB Host works great with my Logitech Wireless Keyboard and Mouse Combo with the OTG USB Dongle and Logitech nano receiver. I want to keep using this ROM as it is very functional for my needs.
The Bad News.
Now, let’s get to the frustrating part. No more drag and drop. After the install, my PC no longer recognizes the it as a Kindle Fire as a drive or sdcard. It recognizes it as a GT-P1000 (Galaxy Tab P1000). Because of this mis-reporting to the PC device manager the KF and sdcard are no longer visible as a drive on the PC for me to browse, drag and drop items.
The Device Manager sees the
---Android Phone > Android ADB Interface
or depending on the driver
---Android Phone > Android Composite ADB Interface
and no where in the Device Manager does it show the Kindle Fire any longer.
The only place the device is listed is in
---Control Panel > Hardware and Printers > GT-P1000(!). (Unknown Device)
Attempted Solutions.
1. Driver Reinsall(s) with and without SDK.
I tried reinstalling the drivers for the KF and this changed it from Android Composite ABD Interface to Android ADB Interface. (no change) I reinstalled the Composite interface and still no KF. I also tried a few different versions of drivers up and down the spectrum trying to get this installed. Including trying to install a GT-P1000 driver from Samsung. Still no luck.
2. Android Debugging
I tried to turn on and off and on etc the Android debugging in Settings > Developer Options > Android Debugging. No Luck.
3. Turn on USB Mass Storage
Unable to do this as the options are simply just not there.
4. Reboots
Countless reboots (PC and KF) and cache wipes with and without the KF attached.
5. Different ROM
I tried a different ROM for Jelly Bean 4.2 and it was successful and recognized as a KF and I could browse to the folders on the sdcard. However this ROM was so striped down that it was not really functional for me as there was no file explorer, market app, or any way to browse to the sdcard to install any app that I could drag and drop into the sdcard in the hopes of installing a file explorer and market app. The issue seems to be with the GedeROM CM9 that I am using.
Am I going to have to try multiple ROMS until something works?
Specs:
Kindle Fire (1st Gen, spring of 2012, original one purchased in December 2011, but suffered screen smash)
GedeROM ICS v4.04 CM9 Kernel v3.0.21
The PC I am using is running Windows 7 Professsional.
Click to expand...
Click to collapse
I have tried several different ROMS today.
I have found that they just dont have the stability and functionality that I like with the version that I am running. SO.... that being said, I found a work around. I can keep the existing ROM in place and if I need to copy something to the SD Card, I can just boot into TWRP and mount the USB drive, make the file copies and then reboot. It's a little annoying, but none so much as not being able to do it at all.
Thanks for the input.

joehlmann said:
3)
Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.
Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.
Ok now you can /"
Click to expand...
Click to collapse
step 3 does not work! windows was unable to install your amazon kindle fire hd!
what shall i do?

This didnt work for me
I dont know why but whenever I try to manually install the driver it pops up with an error saying something on the lines of 'The Folder does not contain a suitable software for your operating system' basically saying there is not software compatible with 32bit. I have been trying to root my kindle fire for 2 days now. I have tried to use SDK and KFU none of them worked. I will attach the errors Im getting!
Someone Help Pleasee

if all eles fails and all you want to do is copy files over try "wifi file explorer" on the playstore. very handy app to have installed just in case

Windows 7 will not recognize Fire

My girl got a Kindle Fire and wants Jelly Bean on it. I plug it into the laptop, Windows start to look for drivers, can't find them. So, thru KFU I install the drivers, open KFU, device is not showing. I open adb, run adb devices, blank. Run adb usb devices,, device not found.
The kindle will say that its connected to the computer and I can transfer files. But windows will not show an external device is attached. So, I go to Device Manager, its an "unknown device". So I looked through post after post, finding out that I need to edit the adb_usb.ini file. Problem is, I can't get to it......
I'm not a noob when it comes to computers or android, but this has me lost......

Your GF wants too much!!!
I had same problem. Errore was plug first kindle then install kfu with drivers. Remove all drivers you installed. Now install drivers provided with kfu. Make sure SDK and java is ok. Then plug kindle.
Sent from my Amazon Kindle Fire using xda app-developers app

smsrat84 - when you plug KF into USB and Windows starts to scream about new unrecognized device, choose an option to install drivers manually from a specified location, and choose {KFU_HOME}/drivers/kindle - KFU will see it after that. Then install FFF, TWRP with KFU and so forth.

Try using Linux (yes I said the dreaded 'L' word ) because apparently it's not as fiddly with drivers as Windows is.
Personally, I used Mac and it was plain sailing all the way. No drivers, everything just worked first time [Just make sure you're careful, nothing is foolproof ]

jji7skyline said:
[Just make sure you're careful, nothing is foolproof ]
Click to expand...
Click to collapse
touché

[Q] KFU Windows 8 Driver Problem

Hey, well now that my Kindle has had a charging problem for quite some time, I sent it out and got a new one for no charge. So now that I have received it, I'm trying to root it, and I notice that Kindle Fire Utility is not connecting to ADB, so I proceed to re-install the drivers. It worked fine before I updated to Windows 8 from Windows 7, but now it just plain won't install. I do have another computer I can use with Vista and have tried, and the drivers will install on, but it detects my Kindle as an Android ADB Interface, not a Kindle. I have installed the drivers multiple times. So my question is how can I get KFU working? Please respond ASAP. Thanks!
EDIT: Resolved with another computer by uninstalling driver software then reinstalling

For anyone wanting to know how to install unsigned drivers shift+ restart, then select troubleshoot, then advanced options, then startup settings, then restart. After reboot select f7 to disable driver signature enforcement it will reboot again, then simply just install the driver.

camason24 said:
Hey, well now that my Kindle has had a charging problem for quite some time, I sent it out and got a new one for no charge. So now that I have received it, I'm trying to root it, and I notice that Kindle Fire Utility is not connecting to ADB, so I proceed to re-install the drivers. It worked fine before I updated to Windows 8 from Windows 7, but now it just plain won't install. I do have another computer I can use with Vista and have tried, and the drivers will install on, but it detects my Kindle as an Android ADB Interface, not a Kindle. I have installed the drivers multiple times. So my question is how can I get KFU working? Please respond ASAP. Thanks!
EDIT: Resolved with another computer by uninstalling driver software then reinstalling
Click to expand...
Click to collapse
No comment on the win8 since I haven't had a chance even looking at it.
On the other computer, it seems the driver installed correctly except that a normally booted up KF should read Android Composite ADB Interface.

W8 and KF - ADB finally recognized it.
I finally got adb to recognize my Kindle Fire on Windows 8. Device Manager still thinks it's a Android ADB Device - but at least ADB works.
[DISCLAIMER - I'm not a windows guru, so anyone who is feel free to adjust, or comment on these instructions to make them better. This worked on my W8 computer - I won't guarentee that it will work on yours...not all W8 installations are the same!!]
Before you preform this - make sure you have the latest Google SDK installed. If you're not computer literate (meaning you can administer your own computer without help) then DON'T do this.
Here's what I did to make it work.
First you will need to set up W8 to install unsigned drivers as suggested by Thepooch in post #2 of this forum.
Windows Key + C - brings up charms
Shift + Restart from the power menu
Select Troubleshoot
Select Advanced Options
Select Startup settings
Select restart
When menu comes up after restart - select F7
W8 puts the Kindle at different addresses that W7, so you'll need to edit two files.
Plug in your Kindle to the computer. Open Device Manager under W8 (you need to be computer literate to complete this. You've been warned!)
If you're Kindle shows up as a Galaxy Nexus then uninstall the drivers. Make sure you're Kindle is identified as a Kindle in the build.prop file on the device. If not, just do a quick reinstall of the OS.zip file and that should reset it.
Plug in the Kindle to the computer - Device Manager should find it as a Kindle Fire
Now right click on the Kindle Fire (should have yellow exclamation marke), open the properties tab.
Click on the Details Tab, select Hardware ID's. The Hardware ID for the Kindle on W8 is different that W7! You need to edit two files to adjust the hardware ID's so ADB will find the Kindle.
Leave the Properties Windows Open.
Go to C:\Users\"Your user folder"\AppData\Local\Android\android-adk\extras\google\usb-driver\
Open android_winusb.inf and insert the following three lines under [Google.NTx86] and [Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D002
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002&MI_01
VERY IMPORTANT: The VID_#### and the PID_#### should MATCH what is displayed in the open Properties windows - check and make sure these numbers match!! Your Hardware ID's could be different!!
Save this file.
Go to c:\users\"Your User Name"\.android
Open adb_usb.ini with notepad.
Key in 0×18D1 (This is the same number you used in the VID_#### and PID_#### from the properties window - make sure it matches!)
Now go back to the properties window.
Select the general tab
Select update driver ....
Select Browse my computer for driver software to locate the driver software manually.
browse to C:\Users\"Your user folder"\AppData\Local\Android\android-adk\extras\google\usb-driver\ - select ok and install the driver
W8 will give you a big, nasty security prompt (only if you've enabled installation of unsigned drivers) - just hit okay.
The driver should install and you should see the Kindle as an Android ADB device now.
Testing Kindle Fire adb USB driver
Bring up command prompt (CMD).
Type adb kill-server then enter.
Type adb devices then enter.
That’s it. You should see Kindle Fire as one of the devices.
You should now be able to use ADB to manage your Kindle.
Hope this helps. Good luck.

[Q] Root Kindle Fire 6.3.2

I am trying to Root my Kindle Fire version 6.3.2, and am looking for the correct Kindle Fire Utility. I do not want to download the wrong one as the ones I have seen were for version 6.3.1 or 6.3. Anyone have suggestions?

Ichigo said:
http://forum.xda-developers.com/showthread.php?t=2192818
Click to expand...
Click to collapse
Hi...
Thanks for the linky, i grabbed it today and for some reason, it's not detecting my device. I've installed/reinstalled the drivers that came down with v0.9.8, still same results. Shows the driver Android ADB Device
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So tried to just boot it to FastBoot and same results, device not found.
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
What am I doing wrong here guys?
Thanks in advance and thank you for the work you do for us idiots.
Mark

mrlee1999 said:
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
Click to expand...
Click to collapse
Put everything back where it belongs first. Also, your computer recognizes the kindle as an Android adb device in device manager? You are on 6.3.2 also?
Sent from my Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.

Thanks for replying
I'm on 6.3.2.
It was seeing it as android adb.
I do have it on 1.4.a as well.
I did remove all of the drivers to the point win7 was showing kindle with an !. Reinstalled and rec'd same results. Got pissed at it and removed drivers again rebooted and removed the files under .android. When I get a chance, i'll try reinstall. Maybe by manually deleting the inf file will do some good???. I'll update the post when I have a chance to work on it.
Sent from my SCH-R530U using Tapatalk 2

mrlee1999 said:
Thanks for replying
I'm on 6.3.2.
It was seeing it as android adb.
I do have it on 1.4.a as well.
I did remove all of the drivers to the point win7 was showing kindle with an !. Reinstalled and rec'd same results. Got pissed at it and removed drivers again rebooted and removed the files under .android. When I get a chance, i'll try reinstall. Maybe by manually deleting the inf file will do some good???. I'll update the post when I have a chance to work on it.
Sent from my SCH-R530U using Tapatalk 2
Click to expand...
Click to collapse
Have you tried running KFU under compatibility for Windows XP SP3? Once you do that, it'll automatically ask for admin privileges.
Also, does your device show when you run the command
adb devices
Click to expand...
Click to collapse
on a terminal (or command prompt, on Windows) window?
Sent from my Muffin masquerading as a phone in the coffin.

Thanks
Removing the driver and deleting the files in the .android folder did the trick.
Thanks Everyone!!!!!
Mark

The one that ichigo said is good.

So I was using the new KFU 9.8+ on my first gen kindle (6.3.2)
and during the procedure while I think it was attempting to install FFF bootloader it was on <waiting for device>, my laptop lost batter life and shut down. Upon booting up my computer and trying KFU again
ADB Status: Offline
Boot Status: Unknown
My kindle now displays the logo. I assume it's bricked right now.
Are there any remedies to fix this?

HypothermicInferno said:
My kindle now displays the logo. I assume it's bricked right now.
Are there any remedies to fix this?
Click to expand...
Click to collapse
It is on the orange logo? And it won't boot properly? So the kindle just stays on that screen without getting dim or anything, right?
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.

Bricked as well
My fire also appears to be bricked. "Kindle Fire" is displayed and the screen doesn't dim or anything like that.

mrlee1999 said:
Removing the driver and deleting the files in the .android folder did the trick.
Thanks Everyone!!!!!
Mark
Click to expand...
Click to collapse
I know how to delete the .android folder, but how can I be sure that the deleted drivers are the one associated with adb and not with other programs ? are those the drivers in Windows/system32 ?
How do you do that ?
Thanks

nugroho2 said:
I know how to delete the .android folder, but how can I be sure that the deleted drivers are the one associated with adb and not with other programs ? are those the drivers in Windows/system32 ?
How do you do that ?
Thanks
Click to expand...
Click to collapse
The .android folder is found under the root of your sdcard or you ext-sd. To remover the drivers:
If you are on Windows 7/8:​
Hit the "Start" button on the keyboard, and when the homescreen (Windows 8) or the Start dialogue (Windows 7) pops up, type in "Add or remove".
Hit enter on the highlighted option, which should be "Add or remove programs". (Note: You may have to go into the settings tab if you are running a search on Windows 8)
This will show you a window where all the apps that are currently installed on your computer shows up. (Metro apps don't show up here.) Look through the list until you find your KF drivers. This should be listed as something like this: Kindle Fire Drivers
Highlight the driver and look towards the top of the window. You should see that a "Change/uninstall" button has popped up. Click on that and follow the on-screen instructions to uninstall the drivers.
You're done!
If you are on an older version of Windows:​
The procedure is the same, only you have to go into Control Panel > Add or remove programs to do this.
Good luck rooting your KF. :good:

Kindle Fire Tool
My company is making a Kindle Fire Tool for Windows and Mac. Their are several options that might help you like "Toggle Unbrick" You can also root on Android 6.3.2.
Contact me if you have any questions: [email protected]

thebane90 said:
My fire also appears to be bricked. "Kindle Fire" is displayed and the screen doesn't dim or anything like that.
Click to expand...
Click to collapse
I had the Same issue found it was just stuck in Fastboot mode and Windows does not handle it well at all. I was getting a USB device not recognized error and wouldnt let me change the driver for it. To get back booting again I used
http://forum.xda-developers.com/showthread.php?t=1850038
Followed the direction and everything was good.... Almost I found no matter what computer I use fastboot always comes up as a bad device. :crying:
But that should help you with the "Brick"

Kindle Fire 6.3.2 successfully rooted
mrlee1999 said:
Hi...
Thanks for the linky, i grabbed it today and for some reason, it's not detecting my device. I've installed/reinstalled the drivers that came down with v0.9.8, still same results. Shows the driver Android ADB Device
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So tried to just boot it to FastBoot and same results, device not found.
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
What am I doing wrong here guys?
Thanks in advance and thank you for the work you do for us idiots.
Mark
Click to expand...
Click to collapse
I have the same error.
What i did was...
1. Download KFU 0.9.9 (http://forum.xda-developers.com/showthread.php?t=2192818)
2. Download TWRP (http://techerrata.com/browse/twrp2/blaze)
3. Download FFF (http://forum.xda-developers.com/showthread.php?t=1369405)
4. I rename them as "twrp" and "fff" respectively and place them in the "recovery" folder in KFU
5. I manually install the drivers
6. I check in the device manager to show me "Android Phone - Android Composite ADB interface"
7. I run the KFU
and that was all...
I check the root was complete with the https://play.google.com/store/apps/...GwsMSwxLDMsImNvbS5qb2V5a3JpbS5yb290Y2hlY2siXQ..

not visible on my pc.
Hey, I took the first step to root my kf on 6.3.2. I can no longer see the devise on my computer to do anhything else. I only loaded the utility file onto the devise and now what? I can't even delete it. Any thoughts?

Okay... here goes!
Vlasp said:
The one that ichigo said is good.
Click to expand...
Click to collapse
*Takes a deeeeep breath* okay, I thought it looked like the most promising instructions I've found so far too... so, from a TOTAL novice at all of this, here goes! Thanks for the endorsement ( I will definately thank him too! )

So, I went through all the steps outlined by xarenmi, but it STILL doesn't recognize my kindle when I try to use the run tool.
I'm not the best with all this, so...

Help...
Hey, I finally got the google winusb driver installed (I had to do it via SDK manger) but it still recognizes my kindle as "kindle" under "other devices" in the device manager. Also the KFU will not recognize it.. period. just nothing and I'm getting really fed up.
I have followed all instuctions to the T and I am still having issues.