yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] kudosmog:
Looks like I'm having driver problems but can't seem to sort them out. Been sifting through forum searches all day now.

My device shows up under "Asus Android Devices" as Android Composite ADB Interface

Also shows up under "Portable Devices" as KINDLE

I used this PC to root my HP touchpad, and HTC thunderbolt's, and ran Burritonroot manually before I found this utility.

As of now, I can use the run.bat file to install extras and confirm root. I've got root and Boot status is 4000.

Problem is no matter what I try I cannot get into fastboot. I've unloaded the drivers and used the drivers specifically from the KFU. If I do this under "portable devices - KINDLE" it tells me my drivers are already up to date. When I did this under "Asus Android Devices - Android Composite ADB Interface" I was able to load the drivers correctly.

No idea why this is showing up as an Asus device....though I may have plugged in an Asus transformer long ago.

If I manually try fastboot devices I get nothing. ADB devices works like a charm, as well as any ADB commands.

Anything related to fastboot just sits at "waiting for device"
[Kindle Fire Android Development] Vashypooh:
Uninstall burritoroot and try again.
[Kindle Fire Android Development] method115:
This is exactly what happens to me. Except I didn't use the menu to obtain root I used another method. Still haven't found and answer to this issue.
[Kindle Fire Android Development] kudosmog:
Problem Solved!

Wow, thank you!!
[Kindle Fire Android Development] jojo54696:
everytime i try to do anything with the tool, it says "The system cannot find the path specified" over and over and over and then it says successful for whatever action i was trying to do, even though it didn't do anything.

I can control my device through adb so my drivers are setup. What is wrong? I would really like to use this tool.
[Kindle Fire Android Development] MMDominator88:
Where did you put the folder for this utility, desktop?

Put all the files on the root of your hard-drive (C:\KFU_0.9.1) or similar and see if that doesn't help.
[Kindle Fire Android Development] mac+htc:
I tried that but it didn't work for me. Still get the same error the other user above is describing.
[Kindle Fire Android Development] SirVilhelm:
Here is something that's confusing me, in the adb_usb.ini provided with the utility there is only 0x1949 listed. Why isn't 0x18D1 listed as well since it is added to android_winusb.inf as a device ID?
[Kindle Fire Android Development] MMDominator88:
and when you type adb devices it shows your serial number, yes?

If you want, you can re-install the windows drivers for your KF, with the edited entries for the KF (the 0x1949 etc) from the .inf in Google's USB drivers from the SDK.

This stuff is it

;
;Kindle Fire
%SingleAdbInterface%	= USB_Install, USB\VID_18D1&PID_0100
%SingleAdbInterface%	= USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
;

Off to work :(
[Kindle Fire Android Development] jspradling7:
That particular file confused the crap out of me. I started the root process using other websites for instructions. They all said to add 0x1949 to that file. But that file didn't have anything in it but some text about using a 3rd party to edit it. (or something like that) There were no device listings there at all. So... I naturally thought I was trying to edit the wrong file. I searched and surfed and searched some more to no avail. All the instructions said to add 0x1949 to a basically empty file.

Finally, I found one website where the guy showed a screen shot of the file and it was just like mine. Nothing but the text thing there. So I added the 0x1949 there and the other text to the other file and it worked.

*shrugs*

Seems like someone would have mentioned something like that. lol

Oh well, I got there.
[Kindle Fire Android Development] DeerSteak:
I get a specific weird, repeatable issue when I'm in TWRP. If I go into the boot mode menu, and then choose 1 for Normal (4000) to boot into the OS again, it just hangs up until I hit Ctrl+C. It then reboots the Kindle Fire into the OS like normal and I can tell it no, I don't want to cancel the batch job, and otherwise KFU works like normal. Might just be something weird specific to my PC but I thought I'd post about it.
[Kindle Fire Android Development] splink7007:
I try to update the framework and sits at waiting for device...I eventually hit ctrl c to stop the script and then get this:

Update.zip has been found.

Waiting for Device..

^Cmount: mounting rw on /system failed: Invalid argument

^Cchown: /system/framework/framework-res.apk: No such file or directory

chmod: /system/framework/framework-res.apk: No such file or directory

mount: mounting ro on /system failed: Invalid argument

Press any key to continue . . .

Any ideas??
[Kindle Fire Android Development] Houndog101:
I tried everything I can think of still no TWRP.. Help!! :o
[Kindle Fire Android Development] googlelover:
Go to the burritoroot app in your kindle, and when you get to the now what hit root, then go to CMD.exe and (well it depends on the way you rooted your device, this was how I did it) and type in CD C:\kindleADB and then type adb root and then retry installing the framework.

Note if this works you have to do it everytime you reboot your kindle.

---------- Post added at 01:05 AM ---------- Previous post was at 01:04 AM ----------

When it is going through everything, does it say cannot run ADB root on a production model anywhere? It should pop up in the beginning if it does.
[Kindle Fire Android Development] method115:
I'm having the same issue as him and mine says this what do I do?
[Kindle Fire Android Development] googlelover:
On your kindle fire go to the burrito root app, go through everything and hit root, then go to CMD.exe and (depending on the method of root you used) type in CD C:\kindleADB, hit enter, then type in ADB root. Go back to the KFU and see if it worked!
[Kindle Fire Android Development] method115:
I've been trying to figure this out for over a day (which is long for me when it comes to rooting a device). Thank you so much!! Just incase someone is following this I had to reinstall the android drivers during the TWRP install as well.
[Kindle Fire Android Development] splink7007:
I rooted using this utility...Kindle does show root when I check it with this utility. Also have terminal emulator and can elevate to su. lol, even was able to create a folder in /system via root explorer.
[Kindle Fire Android Development] googlelover:
No the problem isn't that your device isn't rooted, its that ADB isn't running in root, and you have to (well AFAIK) use burritoroot to be able to root ADB.
[Kindle Fire Android Development] method115:
Yes but during the TWRP install does it say "cannot run ADB root on a production model" it will say this near the top/middle. If it does follow the directions below.
[Kindle Fire Android Development] googlelover:
Haha 1 day is a longg time, i was up until 5 AM last night working through the problem after problem I had with KFU
[Kindle Fire Android Development] method115:
Yea technology never seems to work like you want it to. I just got CM7 booted thanks again.
[Kindle Fire Android Development] Houndog101:
I got to adb root ok and ran kfu to install twrp, goes thru fine ,but when kf reboots it comes up in "kindle fire" screen and on pc i get ... and it hangs there.. omg now what?
[Kindle Fire Android Development] googlelover:
Go back to device manager and check to see if it still has android phone at the top, your stuck in fastboot, and what happened with me was after TWRP was installed my computer had to reinstall the drivers, mine did it automatically, but yours might not.
[Kindle Fire Android Development] splink7007:
So why cant one achieve adb root with this method? Is this why when I change me wallpaper it doesn't stick?

What's the benefits of changing the framework?
[Kindle Fire Android Development] Vashypooh:
Changing the framework is no longer a relevant option and will be removed.

Use the extras menu to lock / unlock the wallpaper. By default the lock screen changes the wallpaper every single time. Kind of annoying.
[Kindle Fire Android Development] bobbyricha:
This is what happens to me. I go through the TWRP install and I hang at the Fire Logo. I NEVER see the yellow triangle Fastboot mode. Not one time.

I'm rooted, have Market and launchers, just can't get TWRP.
[Kindle Fire Android Development] Vashypooh:
Are you all using 0.9.1.

You can NOT use 0.9
[Kindle Fire Android Development] bobbyricha:
Thank you!

That worked. I didn't realize I wasn't using the most recent version.
[Kindle Fire Android Development] Izzy_Britton:
i think the concept behind this utility is awesome. however since i 'installed' the drivers my computer (laptop with xp) no longer recognizes or assigns a drive letter for the kindle fire.

kindle fire utility says 'oops... unable to locate device' no matter what option i choose.

i have tried the search button and i have scanned thru several pages of this thread but i am unable to locate a solution or even anybody else with similar problems. i will admit i may be blind so i may have read it and simply forgot but if anybody can help me to figure out WHY there is a communication error going on now i would greatly appreciate it.

thanks in advance.

Izzy
[Kindle Fire Android Development] Houndog101:
Ditto, thanks..
[Kindle Fire Android Development] mark_a_l:
Ok, here is my experience with v.9.1 This was done on a new KF (with 6.2.1). I had previously rooted another one manually. This was done on a Win XP machine.

First I uninstalled all of the KF drivers I already had installed (but they were the same as what is supplied in the KFU package).

Next I ran the install drivers batch file which did not work. So I just installed them manually using the ones in the package.

Then I ran temp root mainly to install rbfb in case I screwed up later.

Next I installed permanent root and verified all was well.

Then I crossed my fingers and ran the TWRP install, hoping that I would not have any driver issues. But I promptly got the exclamation point on my driver after the Fire went into fastboot mode. <groan>

I first tried to reinstall them (the Fire was still plugged in) and got the 'drivers are already up to date' message. I then uninstalled them and re-installed (after doing a scan for hardware changes). However, I then got the 'A problem occurred, blah, blah, code 10'. So next I just manually rebooted the Fire while it was plugged in and the driver then worked just fine, the unit was recognized and TWRP installed.

I carefully followed the directions to wait for the Fire to reboot. But again I got the same driver problem (exclamation point). So I just manually rebooted the Fire again (contrary to the directions not to), and as before, the the driver then worked fine, and the install was complete.

So in my case it seems that all that was needed was to manually reboot the Fire at those two points to get the driver to properly recognize it. It helps to keep device manager open when doing this so you can monitor what is going on.
[Kindle Fire Android Development] philwaud:
Superb effort, really appreciate this thank you!
[Kindle Fire Android Development] mark_a_l:
There is a post somewhere with a link, but if you follow these directions, you can remove any drivers that are installed even if the device is not present. So you may try doing this (with the Fire unplugged) and remove any android, adb, and kindle drivers and then start over.

From a cmd prompt type

SET DEVMGR_SHOW_NONPRESENT_DEVICES=1

press enter, then type

devmgmt.msc

press enter, and device manager will open.

From the 'view' menu, select 'show hidden devices'

Now you can remove all of the drivers mentioned above. Next if you plug in your Fire (assuming it's booted up normally), it should show up as a removable drive again. Of course you have to unlock the screen before you can access it. If that works, then you can proceed to work with the KFU again.

BTW, this is a good time to look at what other drivers you may no longer need (i.e old hardware no longer present).
[Kindle Fire Android Development] Novalis31:
I keep trying to install TWRP and this where the install gets halted. Could anyone help?

***********************************************
* Activating Fastboot (4002) *
***********************************************

Activating BurritoRoot...
Starting: Intent { act=android.intent.action.MAIN cmp=net.andirc.kindleroot/.Dir
ectCall }
Error type 3
Error: Activity class {net.andirc.kindleroot/net.andirc.kindleroot.DirectCall} d
oes not exist.
Elevating the Shell...
* server not running *

* daemon not running. starting it now *
* daemon started successfully *
adbd cannot run as root in production builds

mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: Read-only file system
Unable to chmod /system/rbfb: Read-only file system
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************

The kindle is successfully running in root mode.

<idme> Invalid permission
reboot: Operation not permitted

The kindle has been told to reboot in Fastboot Mode.

***********************************************
* WARNING *
***********************************************

Make sure to read each screen carefully!
Make sure to follow instructions given to you!

twrp.img has been found.

***********************************************
* NOTICE *
***********************************************

Please wait a few seconds before continuing.
You should be safe when you see the Kindle trying to mount in Windows.

Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.

creating boot image...
creating boot image - 10240 bytes
< waiting for device >
[Kindle Fire Android Development] b63:
if you have allready burritoroot on your device you have to uninstall it and try again
[Kindle Fire Android Development] Novalis31:
Cool I will give that a try.

TY

---------- Post added at 04:31 PM ---------- Previous post was at 04:30 PM ----------

Its stuck in a boot loop now. no yellow triangle just kindle fire screen.
[Kindle Fire Android Development] b63:
have you read and done the tips from vashipooh on the first page ?
[Kindle Fire Android Development] Matt V:
Is there a way to flash kernel using TWRP?
[Kindle Fire Android Development] b63:
not shure but i think this would be a good starting point:

http://xdaforums.com/showthread.php?t=1382999
[Kindle Fire Android Development] Matt V:
I know it's possible since it can get into fastboot mode and recovery.

Can I request an add-on to flash kernel in the next version? It will make working with this stuff so much easier for novices.
[Kindle Fire Android Development] project.in.process:
i'm having the exact same problem---i can never get the ability to write to the device.

i tried option 2---temporary root. no dice.

tried option 3--it appeared successful, but i still can't get the above error to disappear.

i tried installing a launcher (and set it as default---ICS 4.0 Launcher) and it started force closing. i've been following the steps but i can't get it to write to the device to install TWRP.

any thoughts?
[Kindle Fire Android Development] Vashypooh:
Usually means you already have burritoroot installed on the kindle.

The new 0.9.2 will just force the install replacing it even if it is installed to make it so people don't keep making this mistake.
[Kindle Fire Android Development] czardomn:
This Method Works!!!!

This Method works. Only use the drivers that came with the Utility Tool you downloaded in the OP. That will help you alot getting out of fastboot. Also, you must install the drivers within about 45 sec-1 minute....reason: Kindle went back to "unknown device" in the Device Manager after that amount of time. Tried to install drivers 4 times before I was quick enough with a mouse.
[Kindle Fire Android Development] bennettg:
nOOb help needed

I use ubuntu, so i am not able to install this script, but maybe someone could help me do it manually.

i gained root thru burritoroot and have downloaded twrp 2.0. as i understand it, i need to issue the following commands, which will install firefirefire and twrp:

adb shell

su

idme bootmode 4002

fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img

Can someone tell me if i need to download the amazon update.zip and if so, where i can obtain it? also, do i install it before or after i issue the commands above?

thanks in advance.
[Kindle Fire Android Development] Puma81:
Need some help.

I used KFU and chose to perm root. That went off without a hitch and deviced booted after that

I then used the utility to install TWRP and thats when all went wrong. Device rebooted and I did NOT see the yellow triangle just "Kindle Fire" on the screen. ADB wont see the device and under device manager it shows Android phone and then Android adb interface when the kindle is plugged in. Please help me in getting my kindle to boot again!!!

:) thanks

FIXED: Used fastboot and resolved my issue and reinstalled TWRP as the img was a bad download. Highly suggest putting it into the recovery folder manually.
[Kindle Fire Android Development] yumcax:
Hi guys, I'm not quite sure what is going on. I used install_drivers.bat multiple times, and I _think_ that it installed correctly. In device manager, "Kindle" is shown, and in the Hardware tab 'Android ADB Interface' is listed as a device function. This doesn't seem to change depending on if the Fire is in USB MS mode or not.

However, whenever I try to do something with KFU, I get the error:

Oops... something went wrong.
We are unable to locate your Kindle Fire
Make sure it is plugged in and powered on.

Statuses:

ADB Status: Offline
ADB Rooted: No
Boot Status: Unknown

I can test ADB by plugging my Nexus One in and running 'adb devices'; the phone is shown. With the Fire, nothing. Does anyone have an idea for why ADB doesn't seem to be working?

EDIT: Now this is really weird. I just plugged in my other Fire, and ADB seems to be working with it. Will keep investigating.

EDIT:

The first Fire (that doesn't work with ADB) isn't working with USB MS either. This one is actually newer than the other one, which is working. Both are running the same OS versions. I'm going to run a factory reset.

EDIT: Fixed by following datacron's advice! Thanks!
[Kindle Fire Android Development] datacron:
I had the same issue as you. I resolved the issue by plugging in the non-working device and uninstalling the device (and checking the box to remove the driver) in the device manager. I then plugged the device in and it detected the correct drivers... I hope this fixes your issue as well.
[Kindle Fire Android Development] dnathan13:
Thanks for all your hard work! This is a great utility and makes everything a breeze. Another item I was hoping you would look into for 0.9.2 (or a later version) would be to add the ability to repartition more easily.
[Kindle Fire Android Development] yumcax:
Okay, I'm having kind of a silly problem. I set bootmode to boot to recovery by default, think that that was the only way to boot into recovery (didn't realize FIREFIREFIRE was installed already).

Now, I can't figure out how to change the setting. The Fire doesn't show up in either adb or fastboot when in recovery. Any ideas?
[Kindle Fire Android Development] datacron:
Uninstall the drivers as stated in my previous post, run the install_drivers.bat, then launch the Kindle Fire Utility... set the bootmode to "normal (4000)" (Selection 1 and then 1) and when it says "waiting for device" restart your kindle. It never detects mine in recovery but the command will be sent during reboot.

I hope this works for you.
[Kindle Fire Android Development] CZroe:
The latest driver installer is seriously F'ed up. I visited a coworker to fix a couple computers and install TWRP/Adroid Market on his family's Kindle Fire. I brought my laptop that I had previously used Kindle Fire Utility v0.6 on the same Kindle Fire with before it was updated to 6.2.1 and the data was wiped. I downloaded all new files from the OP and move my old files. For good measure, I also used the commandline switches to show hidden and non-present devices and uninstalled/deleted the drivers. I then wasted HOURS trying to get the new driver installer to work with this and two other computers. This one, a 64bit Win7 machine, would keep giving "Oops... something went wrong. We are unable to locate your Kindle Fire

Make sure it is plugged in and powered on." messages. Sure enough, the device manager would show an ADB device but not ADB Composite Device. On the Win7 x86 machine, the driver installer would say that ADB_USB.inf doesn't exist in the user's .Android folder with a whole lot of other incorrect path errors. I added all the driver files there manually and the OS driver installer would behave as if it were installing but would eventually say "Server Execution Failed." Their computer had lots of issues, so I can't say I trust it.

Anyway, after uninstalling and reinstalling and trying everything under the sun to use the latest driver installer, I finally just went back to my KFU v0.6 files and ran the old installer. It worked PERFECTLY, so something is broken in the versions since. I wasted hours over this, so I hope this saves someone some time (download the old KFU!) and helps the author fix the installer (compare latest to the previous batch files).

---------- Post added at 03:40 AM ---------- Previous post was at 03:33 AM ----------

I believe that the "directions not to" refer to a triangle with exclamation point that appears on the Kindle screen and not in the Device Manager. It could have been clearer. :)
[Kindle Fire Android Development] yumcax:
I agree something is definitely not right. Here is how I got it to work:

Right click device in Device Manager, uninstall. After that is finished right click and select Update Driver. Click manual, then select from a list of devices. Use the choice Android Phone --> ADB Composite Device.

It seems that when it is using the driver that does not have Composite in the name, you can be sure that ADB will not work.

This is a good way of getting it to work, my solution was quickly fixing it in fastboot, while the FireFireFire exclamation mark is shown. There is only a few seconds to check that the device is connected and to run the command, but after a few tries it worked.
[Kindle Fire Android Development] G1ForFun:
I think where it really gets confusing is people are trying to replicate an EXACT procedure for driver installs. What people don't realize is that often times, such as in my case, I had already set up ADB on my computer because of the work with android phones that I have done.

I spent a good hour trying to fool with the driver installation and in the end....it was the way it was supposed to be off the bat when I first plugged in the kindle fire and the drivers were installed automatically.

All I had to do was run ADB from the Kindle Fire Utility folder instead of the previous ADB I had in my C:\android-sdk folder.

The reason for that, is that the Kindle Fire Utility's adb setup comes already set up to detect the Kindle Fire. If I really wanted to, I could have gone and replaced the files in my previous ADB folder (where C:\android-sdk) was and had it working just as easily I suppose.

Anyway, maybe this will help someone who keeps banging their head against the wall trying to get the drivers to install in device manager like all of these "guides" recommend. I know I was confused as heck! I never saw my device as Kindle Fire in device manager and fooled with it for way to long.....the reason was because it was already set up properly and detected under the ADB driver.
[Kindle Fire Android Development] vasileios13:
Well done.........:cool: