Just hooked this baby up. Amazon, of course, doesn't provide any information on USB drivers or on how to enable debugging on the device. Probably one of their attempts at "security".
Anyway, looking for two things:
1. Any leads on drivers for windows. I could also do this on a Mac
2. How to enable debug mode so that I can actually test my damn apps on the device.
Everyone keeps talking about how they suspect this is running on cheapened-up BB Playbook hardware... not sure that would help at all...
breon said:
Found it. It's pretty easy. http://blog.actlocalmedia.com/2011/11/developing-on-kindle-fire.html
Click to expand...
Click to collapse
keyesdav, this should help. Thought I'd cross-post (cross-quote?) it over here in case you didn't see / haven't found it yet.
I was able to use the google adb driver on win7 x64, but you have to add the device id to the ini file.
Edit %androidsdkdir%\google-usb_driver\android_winusb.inf
Try adding the following lines under [Google.NTx86] AND [Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Still unable to get Kindle Fire to attach to Win 7 x64
I have a Lenovo W520 laptop. I've made these changes, however the Kindle Fire still comes up unrecognized in the Device Manager.
adb devices shows nothing
repeated adb kill-server, adb start-server no change
Help!
BTW, my "google_usb_driver" directory is in C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver.
Did they move it recently?
Did you go to Device Manager on your PC and then select the Kindle 'Unknown Device' and update the driver by selecting the Inf file you had edited? After updating the driver the system will then show the ADB connection. This is the same process to go through when doing the Root.
That worked!! Thanks!
(I didn't have to do this when I rooted my Galaxy Tab. Samsung provided a driver.)
Ok so the day i got my Kindle Fire i decided to root it. Rushing through everything in excitement i managed to mess something up. I has bricked my kindle the day i got it. I rooted it and installed TWRP (all with kindle fire utility). I turned on my device and behold, yellow triangle with fire just there. It did not boot into the kindle fire OS like normal or anything for that matter. I pushed the button down like is says to go into recovery mode and nothing. I thought i was done for good. So after 2 days of EXTENSIVE research i got really pissed off not finding any answers. I basically read everything i can and in a combination of things i got it working again! So here is what i did ( WIN 7 MACHINE):
I went into SDK manager and installed EVERYTHING that was in there. I left nothing uninstalled. I then rebooted my pc.
I went into KFU (KINDLE FIRE UTILITY) folder and clicked the install_drivers.bat file.(Some people say this does not work with XP).
I plugged in my kindle but my pc did not recognize it at all. So i went into device manager and right clicked my kindle and clicked update drivers. I then told it to let me select from a list of drivers. I did not see anthing that had to do with Android ADB composite device so i had to click browse for driver and tell it to use the file C:\Program files\Android\android-sdk\extras\google\usb_driver\android_winusb.inf
NOTE: if this does not work you may have to edit your android_winusb.inf file so that right under
[Google.NTx86]
and right under
[Google.NTamd64]
it says
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Then in
C:\Documents and Settings\NAME HERE\.android\adb_usb.ini
you have to add this on its own line at the bottom
0x1949
(rebooting at this point is recommended)
Then you will be given the option to select the driver for the kindle and here you would select "Android ADB composite interface".
After thats done you should be good to go.
Fire up KFU and to test it turn on the kindle and press 1 in kfu and then 1 again. If you see your kindle restart you are SET. At this point the kindle OS should be loading up.
Now in KFU you can reinstall TWRP and from there you should be able to get into TWRP to flash the kindle with update.zip.
Sorry if this post has errors or is not understandable, it is 1 am and i am tired.
Please post here if you have ANY questions!
Thanks and hope this helped!
This is a good guide. I went through this process on my KF the first night that I had it, but I had to find the information piecemeal in different threads. Thanks.
i had the exact same problem but i still cant find Android ADB composite interface, any ideas?
All I had to do was run a few Fastboot commands. Lol, I was stuck in the FireFireFire Bootloader.
TheDarkDestroyer9000V2.0 said:
i had the exact same problem but i still cant find Android ADB composite interface, any ideas?
Click to expand...
Click to collapse
Connect your Kindle Fire to PC, right click on My Computer then click on Manage and then Device Manager. from Device manager goto Portable devices and right click on Kindle/MTP device and then click on Properties and goto Drivers tab and click Uninstall (Uninstall Drivers)... Now install ADB drivers for Kindle Fire and Reboot your PC. Now right click on Kindle Fire from Device Manager and select Update Drivers then click Browse my Computer for Drivers then Let Me Pick From a List, from the list select Kindle Fire and click Next... it will install the ADB drivers properly and now your device will appear as Android ADB Composite Interface. thats how I did it. give it a try!
Sent from my KFTHWI using XDA Free mobile app
Hey all. I need some help because I fear that my lovely Kindle Fire is gone to heaven for good. I've read through so many threads and tried so many little tricks, it's really becoming frustrating.
So I was installing a ROM, and it didn't work out properly. My KF is stuck at the yellow triangle (fire fire fire) and will not budge no matter what I do. To make sure it wasn't an empty battery, I left the KF plugged in to my wall charger for many hours (both with the yellow triangle on screen and completely turned off). All that happened was it got really hot.
I've tried the following:
1. Kindle Fire Utility (recovery/fastboot) didn't work, just says device not found/offline
2. Kindle Fire Unbrick Utility (recovery loop/stuck at logo) didn't work, again device not found/waiting for device
3. Changing the bootmode via ADB
(fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot)
(fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot)
on both attempts, it just says waiting for device. Yes I tried shutting off the KF and then typing the commands and then plugging in the cable. Still nothing.
4. Reinstalling the drivers
I tried reinstalling the drivers using KFU drivers, but I could not remove the old drivers first because my KF is not showing up in my device manager, either as Kindle Fire or Unknown Device (exclamation point). I tried unplugging and reconnecting to see if anything popped up in device manager, but nothing changed.
The only thing I haven't tried is a factory cable because I don't have one and I don't have the money for one.
I'm using Windows 7 64-bit.
Any help would be greatly appreciated. I've been trying to get this working again for almost two weeks now. I'm off from work today, so i'd really like to get this fixed.
Thanks in advance.
1. Your KF is stuck at the yellow triangle, so fff is OK, fastboot mode is OK!
2. Confirm that your driver is OK, that will be "ADB Composite Device".
3. Power Off your KF.
4. fastboot oem idme bootmode 4000
5. Power On your KF.
6. fastboot reboot
sigporsson said:
1. Your KF is stuck at the yellow triangle, so fff is OK, fastboot mode is OK!
2. Confirm that your driver is OK, that will be "ADB Composite Device".
3. Power Off your KF.
4. fastboot oem idme bootmode 4000
5. Power On your KF.
6. fastboot reboot
Click to expand...
Click to collapse
My driver is NOT ok. I don't see Kindle Fire, Unknown Device, or ADB composite device in my device manager.
All you need to do is have the KFU opened to change to normal boot and at the screen where it is waiting on the device. Have your KF connected to your computer, and turned off. While you are "waiting on device" turn on the KF and it willl see it and send the command, but it will only see it for a few seconds and then you will need to reboot the KF after it has sent the command.
Go to your device manager on your PC and uninstall all of you android/kindle related drivers, then install the drivers that came with kfu and reboot your pc
Sent from my LG-VM670 using Tapatalk
If you are using Win XP
Had a similar problem the first time I tried to work with my KF. This was on my Win XP computer (had no issues on my Win7 computer).
What fixed it came from this thread http://forum.xda-developers.com/archive/index.php/t-1479063.html. Basically this part:
the driver (android composite adb interface) is the right one
did you check the adb_usb.ini file in .android folder in your personal folder ?
ist should include 0x1949 & 0x18d1 - if not add in a new line
restarting adb : adb kill-server
check again: adb devices
adb relies on:
adb_usb.ini in .android folder with the correct entries:
0x1949 & 0x18d1
drivers with the correct entries in android_winusb.inf (drivers of kfu do):
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
in the 32 and 64 bit section​
After correcting those issues, and computer and KF reset, Adb recognized KF.
Hope that helps. Thanks for listening.
Sincerely,
William
[Kindle Fire: gedeROM v1.15 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
I also have the same problem (infinite bootloop). And I have also tried all the the solutions on this page. In OP and in the previous reply. Nothing worked. It still stuck in the infinite bootloop. FYI I tried flashing AOKP milestone 5 KF version and that's how I got here. Please help us!!!
king_xerxes said:
All you need to do is have the KFU opened to change to normal boot and at the screen where it is waiting on the device. Have your KF connected to your computer, and turned off. While you are "waiting on device" turn on the KF and it willl see it and send the command, but it will only see it for a few seconds and then you will need to reboot the KF after it has sent the command.
Click to expand...
Click to collapse
I tried that previously. But just to make sure I tried it again a few times with different KFU commands. Still nothing. It never changes from "waiting for device" and nothing happens on the Kindle Fire.
pbailey212 said:
Go to your device manager on your PC and uninstall all of you android/kindle related drivers, then install the drivers that came with kfu and reboot your pc
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I also tried this previously. There are no android devices in my device manager. No android phones (even though I have a GS2), no ADB composite devices, no unknown devices. There is one USB composite device, but I don't think it's the Kindle Fire.
Docs009 said:
Had a similar problem the first time I tried to work with my KF. This was on my Win XP computer (had no issues on my Win7 computer).
What fixed it came from this thread http://forum.xda-developers.com/archive/index.php/t-1479063.html. Basically this part:
the driver (android composite adb interface) is the right one
did you check the adb_usb.ini file in .android folder in your personal folder ?
ist should include 0x1949 & 0x18d1 - if not add in a new line
restarting adb : adb kill-server
check again: adb devices
adb relies on:
adb_usb.ini in .android folder with the correct entries:
0x1949 & 0x18d1
drivers with the correct entries in android_winusb.inf (drivers of kfu do):
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
in the 32 and 64 bit section​
After correcting those issues, and computer and KF reset, Adb recognized KF.
Hope that helps. Thanks for listening.
Sincerely,
William
[Kindle Fire: gedeROM v1.15 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Click to expand...
Click to collapse
I read through the thread, and yes, one of the adb_usb parts was missing. I added it in both the personal .android folder as well as in the KFU folder and the Kindle ADB folder. Didn't change anything. I retried the KFU as well as the adb fastboot commands. nada.
Thanks for all your replies. I know there are many threads saying that you can't brick the KF. I think I might be the exception to the rule.
I'll still try any other options that you guys can give me, but i'm kinda giving up at this point. Maybe i'll sell it for $75 bucks to whoever wants it and thinks they can fix it.
Before you give up, read this. http://forum.xda-developers.com/showthread.php?p=23747671
Your only problem is a driver issue and you are FAR from bricked, trust me.
[Edit:] Wait, I take that back...I'll buy your Fire for $75
Seriously though, read that guide from "What are drivers". The title may sound like its beneath you but I think there is some important information in that guide that you may have missed.
soupmagnet said:
Before you give up, read this. http://forum.xda-developers.com/showthread.php?p=23747671
Your only problem is a driver issue and you are FAR from bricked, trust me.
[Edit:] Wait, I take that back...I'll buy your Fire for $75
Seriously though, read that guide from "What are drivers". The title may sound like its beneath you but I think there is some important information in that guide that you may have missed.
Click to expand...
Click to collapse
I appreciate your attempt, but as I said in my original post, nothing shows up in my device manager as a Kindle, and ADB device, or an unknown device. When I plug the KF in nothing changes/pops up in my device manager. So I can't do anything with the drivers. I have tried installing from KFU, it seems to complete, but there's still nothing in the device manager.
Techngro said:
I appreciate your attempt, but as I said in my original post, nothing shows up in my device manager as a Kindle, and ADB device, or an unknown device. When I plug the KF in nothing changes/pops up in my device manager. So I can't do anything with the drivers. I have tried installing from KFU, it seems to complete, but there's still nothing in the device manager.
Click to expand...
Click to collapse
What you fail to realize is that the problem isn't your Kindle. It's doing exactly what it was programmed to do. I'm willing to bet the problem is your computer.
But it's your device. And if you want to sell it to me for $75, so be it. Who am I to stop you?
Techngro said:
I appreciate your attempt, but as I said in my original post, nothing shows up in my device manager as a Kindle, and ADB device, or an unknown device. When I plug the KF in nothing changes/pops up in my device manager. So I can't do anything with the drivers. I have tried installing from KFU, it seems to complete, but there's still nothing in the device manager.
Click to expand...
Click to collapse
That's an oddball situation if Windows won't even detect the device. It might be something simple like a bad USB cable... I've seen more than a few people say swapping cables helped. Possibly a problem with Windows like...
http://support.microsoft.com/kb/314634
I don't know what version you are using, so I'm grasping at straws. If you've got spare hard/thumb drive, you could try Firekit and see if that helps. It might be the cure for your Windows blues...
http://forum.xda-developers.com/showthread.php?t=1430038
It might be a bit of a learning curve if you aren't familiar with Linux, but it's really not that bad. Linux seems much more robust when handling these devices... Firekit has a script to change the bootmode to normal, so that might fix it right up.
EDIT: Sorry, missed the part where you said you are using Win7 x64.
Troubleshoot the problem. Are your Windows USB drivers working? When you plug in a thumb drive does it show up? Is your mouse on USB? If so, plug your Kindle into the mouse port. Have you tried rebooting your computer? Do you have administrator privileges on your computer? Windows 7 right? Have you taken ownership of it?
[Edit:] You snuck that one in on me kinfauns. I didn't even think about this cable being bad, good call. That's probably it.
I am having the same issues. Never happened until today, i wasn't doing anything to my kindle fire came back to it being frozen with the Triangle with fire in the middle of it.
I can Normal boot it and it boots up, but then powers down and restarts and goes back to being frozen at the same image.
I installed FireFireFire and it changed nothing. I'm guessing my Kindle is messed up for good? I can't get it to stay booted up and it has Full charge too.
DarkenedMatter said:
I am having the same issues. Never happened until today, i wasn't doing anything to my kindle fire came back to it being frozen with the Triangle with fire in the middle of it.
I can Normal boot it and it boots up, but then powers down and restarts and goes back to being frozen at the same image.
I installed FireFireFire and it changed nothing. I'm guessing my Kindle is messed up for good? I can't get it to stay booted up and it has Full charge too.
Click to expand...
Click to collapse
I'm reasonably sure your situation is different than the OP...
http://forum.xda-developers.com/showthread.php?t=1623244
kinfauns said:
I'm reasonably sure your situation is different than the OP...
http://forum.xda-developers.com/showthread.php?t=1623244
Click to expand...
Click to collapse
Alright, i'll go through trying out stuff in that thread. I really hope something fixes it because i know the thing was charged when it started acting up on me. I just get the Little android and the Kindle fire logo and the Light at the bottom on the kindle is orange instead of green.
/Edit
I flashed firefirefire 1.4a just now to see if it'd fix it. It didn't, also it's new battery feature doesn't say that my battery needs charged.
I don't know what to do now. I read something about getting the Stock boot .img file but i have no clue how to go about getting this.
/Edit
Stock boot.img did nothing.
I need to know how to wipe everything on the kindle and get it back to brand new, someone want to point me in the correct direction?
Or, if someone finds a fix to this problem let me know.
/Edit
I installed the latest twrp, Firefirefire, then booted it in recovery mode.
It did what it had to do and i got something telling me there was something wrong with the app storage i think and that it had to be completely wiped ( reset to factory.) I did that and it fixed it.
I now have to start all over with my root exc exc.
Same issue here, no power will go to the screen or USB or power button. I can't turn it on at all. Tried in Ubuntu, doing the short while running the script, nope. Nothing happens in Device manager when I plug it in. I'm getting one of those cables and hoping that might help for the future. Sucks. Also on x64 Win 7, but tried on Ubuntu as well. I'll try at work tomorrow on x32, but I doubt anything will happen.
Solved...kinda
Well, thanks for all the responses guys. Even though none of the suggestions proved fruitful i'm glad that people tried to help.
Anyway, I finally got my Kindle Fire working and I did it by removing the only variable that I could not before, my computer itself. I dug out my old laptop (keyboard doesn't even work so I used Synergy) and connected my KF. It registered as an ADB composite device, I installed the drivers via KFU and then booted into recovery and immediately wiped and installed a backup.
So my suggestion for anyone who has tried everything else is to try and start from scratch on a new computer. Use a friends computer if you have to, but I think being able to start from scratch with the new drivers was the key.
I hope this helps someone in the future.
Or just do a system restore on your computer before the point you messed up your drivers I have done it and it works .This was after a bad driver install just simply rolled my PC back a month.
can you please go into a little more detail
king_xerxes said:
All you need to do is have the KFU opened to change to normal boot and at the screen where it is waiting on the device. Have your KF connected to your computer, and turned off. While you are "waiting on device" turn on the KF and it willl see it and send the command, but it will only see it for a few seconds and then you will need to reboot the KF after it has sent the command.
Click to expand...
Click to collapse
im having the same problem exept on the kindle fire screen. i want to try this but i cant understand what you mean. will you please explain a little more?? also twrp is gone so i have next to nothing i know how to do.
I have 2 kindle fires. I rooted one last week and was trying to do the same to my newer kindle fire today. When I connect the rooted kindle to my laptop it opens as a flash drive would (autoplay opens) but when I connect my newer kindle to the same laptop, it installs as a device.
Thus I am not able to use KFU 0.9.6 to root it. The ADB Status remains offline. The older kindle will say that it is online.
Both are running 6.3.1
Any suggestions as to what is going on with my newer kindle?
csykos said:
I have 2 kindle fires. I rooted one last week and was trying to do the same to my newer kindle fire today. When I connect the rooted kindle to my laptop it opens as a flash drive would (autoplay opens) but when I connect my newer kindle to the same laptop, it installs as a device.
Thus I am not able to use KFU 0.9.6 to root it. The ADB Status remains offline. The older kindle will say that it is online.
Both are running 6.3.1
Any suggestions as to what is going on with my newer kindle?
Click to expand...
Click to collapse
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
Look at the second post. Figure out what device drivers are getting loaded when you connect the second KF. If it doesn't match what you should see (based on the table in the middle), right-click on the device and get the hardware ID's from properties. Paste them here.
I just got a Fire tweo weeks ago and had the same problem. I had to add the new hardware id which I found in Windoze device manager in the "android_winusb.inf" file.
Example:
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0216&MI_01
After I just re-ran the driver install utility and rebooted the computer, with the Fire unplugged of coarse. Then I went into the device manager and removed all "Android Phone" devices. Rebooted once more and plugged the Fire with all working as it should.
This was done a Win Vista Pro 32 bit machine I might add.
So I have my Kindle Fire rooted, with TWRP 2.2.2.1, FFF 1.4A and the latest version of CM 10 w/ SGT7 (9/05). Using KFU 0.9.6 when I attach my Kindle to my computer the ADB status is offline, while the drivers on my computer recognize it as an "Amazon Kindle Fire" and if I look in the properties I see "Amazon File-CD Gadget USB Device", "USB Mass Storage Device", and the drive it's recognized as "M:\" for me. No matter how often I attempt to reboot my computer, the Fire, or uninstall the drivers and install the drivers manually (either through the install drivers.bat or adding
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
and
0x1949
to android_winusb.inf and adb_usb.ini respectively.
However when I reboot my Fire into recovery, it's recognized as Online. Any help with getting it recognized when regularly booted up?
Sounds like a ROM issue. The new builds of CM10 have a PID of 0004 for some reason, rather than 0006.
Why it wouldn't affect recovery, though, I couldn't tell you.
Damn, alright. Thanks, at least I can always transfer a new ROM over and flash it when I need to. Hopefully they'll get it fixed soon.
Just use recovery to send adb commands.
soupmagnet said:
Just use recovery to send adb commands.
Click to expand...
Click to collapse
Right, I'm using it. I installed JandyCane and it's working just fine now. However I find I'm missing much of what I liked in the other ROM. Ah well, time to explore ROMs! Thanks for your help!
I added these 2 lines to the already long list of ids saved the win_usb file then reinstalled the driver now adb works
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01