Develop Bugs

Stuck on TWRP Fire screen. Unbricking

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

Drivers Recognized in Recovery, not in ADB

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

[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] Windows 7 driver for Kindle Fire with Jelly Bean

Hi Forum Users,
I rooted my Kindle Fire tablet, its now running the Jelly Bean ROM (4.2.2_r1 ROM here) without problems.
However, since that my (german) Windows 7 doesnt recognize the tablet anymore. It appears in the list of devices, but with a yellow exclamation mark. I deleted it, trying to reinstall the table drivers, without success.
This is for sure a newby question, but: How to I get a proper driver installation so that my Windows 7 works with my Kindle Fire that runs the Jelly Bean ROM?
Thanks
D-Ta

giggollo said:
Hi Forum Users,
I rooted my Kindle Fire tablet, its now running the Jelly Bean ROM (4.2.2_r1 ROM here) without problems.
However, since that my (german) Windows 7 doesnt recognize the tablet anymore. It appears in the list of devices, but with a yellow exclamation mark. I deleted it, trying to reinstall the table drivers, without success.
This is for sure a newby question, but: How to I get a proper driver installation so that my Windows 7 works with my Kindle Fire that runs the Jelly Bean ROM?
Thanks
D-Ta
Click to expand...
Click to collapse
http://db.tt/vXXeuL10 Try this replace that file with the one I have provided in the drivers folder for kfu. Rerun driver bat then plug your kindle in adb should be back online. Also make sure you have adb debugging enabled under settings/developer options.

...works only in debugging mode
Try this replace that file with the one I have provided in the drivers folder for kfu. Rerun driver bat then plug your kindle in adb should be back online. Also make sure you have adb debugging enabled under settings/developer options.[/QUOTE]
thanks, i can indeed get in online in KFU, but the tablet only connects to PC via USB if I run it in debugging mode. If I disable the debugging mode, I still see the Amazon Kindle Fire device in my device manager, however with a yellow exlamation mark and I dont have access to its storage any longer (i.e. its not properly recognized by my PC any more). This used to work before I put the Jelly Bean ROM on it. Is there a solution ?

When you go to the device in device manager. Go to driver. What does it say there?

tobiascuypers said:
When you go to the device in device manager. Go to driver. What does it say there?
Click to expand...
Click to collapse
that no driver is installed (only when debug mode is disabled though).
however, i did install the driver file that you post above using the KFU .bat file and it did do it

I tried many things, still doesnt work.
I can make Windows 7 work with the device in debugging mode, but not if debugging mode is switched off.

Plug your kindle in uninstall the driver with the exclamation point, unplug your kindle, rerun driver bat, then plug your kindle in and check device manager.

Thepooch said:
Plug your kindle in uninstall the driver with the exclamation point, unplug your kindle, rerun driver bat, then plug your kindle in and check device manager.
Click to expand...
Click to collapse
its still not working, unfortunately. it would recognize a new device, try to install the driver (but fail), and then show the kindle fire in the device manager list - again with the yellow exclamation mark. :crying:

http://forum.xda-developers.com/showthread.php?t=2167851

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2167851
Click to expand...
Click to collapse
amazing, the device is now properly listed in the device manager list - THANKS: for the suggestion ( i wasnt aware of the hardware-ID adjustments that are ROM specific and need to be done in the driver file.
BUT: i still dont see the kindle in the list of devices attached (after typing adb devices)... neither do I get the USB mass storage drive I used to get when I connect the tablet via USB to my PC. Still, I am doing all this in no-debugging mode.
How Do I get the mass storage mode back?
Halfway there ( i guess)

Okay, if you added the hardware ID for the device in mass storage mode on (debugging turned off) you need to remove it. Basically, if you have anything in the android_usb.inf with a PID of 0005, delete it.
However, if you want an ADB connection, you need to add the hardware ID of the device while debugging is turned on.

soupmagnet said:
Okay, if you added the hardware ID for the device in mass storage mode on (debugging turned off) you need to remove it. Basically, if you have anything in the android_usb.inf with a PID of 0005, delete it.
However, if you want an ADB connection, you need to add the hardware ID of the device while debugging is turned on.
Click to expand...
Click to collapse
;Kindle Fire
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0005&REV_0216
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0005
...thats what i have in my android_usb.inf and that what it shows me as the hardware-ID. Are you saying I should delete that? ... and then what?

giggollo said:
;Kindle Fire
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0005&REV_0216
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0005
...thats what i have in my android_usb.inf and that what it shows me as the hardware-ID. Are you saying I should delete that? ... and then what?
Click to expand...
Click to collapse
Yeah, that's the PID for the device in MTP. Delete those lines, and reinstall your drivers.
You can find more information here:
http://forum.xda-developers.com/showthread.php?t=2179748

ADB not working

I for the life of me can't figure out why my computer won't recognise my Pixel C for ADB.
Bit of background, using Win 7 64 bit. Never had a problem with this computer recognising phones for ADB (including various Nexus phones/tablets and Sony Xperia Z3 Dual).
My computer recognises the Pixel C as a device, and I've read through the various other posts of people having these problems, including:
http://forum.xda-developers.com/pixel-c/help/help-getting-pixel-c-recognized-adb-t3268991 and installing the adb installer suggested in that thread. I normally use Wug's Nexus toolkit and I don't think I've got a problem with the ADB drivers on my computer. I've tried to uninstall and then reinstall adb drivers a few times, but that doesn't work either.
I don't think its the cable I bought as well, because I have used the cable on another computer (borrowed) and ADB worked fine on that computer.
Any suggestions, or am I missing something?

Does it show up but can't find the driver? I have this issue with Windows 10 (currently fighting with it, that's how I found this thread). You need to add these device strings to android_winusb.inf for it to install the drivers, but it keeps telling me the correct hash isn't there, this is how I fixed it before.
Code:
;Google Pixel C
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_5201
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_5201
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_5201&MI_01
Edit: Just remembered an easier way: if the driver isn't installed, try to install it manually and select it from the list and select "Android Devices" then "ADB interface", and it should work.

Hi sorry, no-one every responded to the thread, so I didn't update it. I actually got it to work. Basically I deleted all my ADB drivers (and I had a lot, from all the various devices I have had over the years). I then plugged the pixel c in and boom it installed the driver correctly.