yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] MizzouBrent:
Here's what I did and it really worked without any issues. Bigtime shoutout to Thepooch for all his help

Yeah, but it sounds like a number of people have issues with windows being able to recognize the device while in fastboot, so KFU can't issue any commands. For what it's worth, I got it all done today and here is exactly what I did.

FWIW I was on stock 6.3.1 and downloaded the most recent KFU.

1) With KF unplugged, I downloaded KFU and extracted. Ran the install_drivers.bat file. Then I plugged in my KF. Went to device manager to check my driver. It should be listed under "android phone" and then android composite adb interface. If it doesn't say that, you need to update your driver. Pointing to the KFU directory should work.

Additional: I also turned off windows firewall (I'm on windows 7) and am running USB 2.0.

2) From there I ran the command to install TWRP. It downloaded TWRP, rebooted my KF and installed, booted back into the system. So far so good.

3) Then I downloaded the FireFireFire bootloader from XDA. Soup Magnet on XDA recommended installing this via TWRP rather than with KFU. Obviously flashing a bootloader is serious business so I'm not about to take any chances with it.

4) After downloading the FFF bootloader onto my SD Card I changed my boot mode to recovery and rebooted (still plugged in). In recovery, I flashed the file and rebooted.

5) Then the stock software booted up just like it should and I'm pretty much done with using KFU. I didn't care about rooting the stock software because I have no plans to run the stock software. With the FFF bootloader and TWRP installed, you have the ability to flash a custom rooted rom anyway, so I'm pretty much all set.

I ended up flashing Glazed ICS and could not be more pleased at this point.
[Kindle Fire Android Development] akalostangel:
There are a lot of posts about this. This was the one that was most helpful to me: http://xdaforums.com/showpost.php?p=25830324&postcount=7

And be sure to go to google play and the kindle app and remove the check from auto update or it will do this every time the app updates.
[Kindle Fire Android Development] daleykd:
Thanks! I had seen that post before, but I honestly didn't think I had done that. I'll try to re-root tonight (I reverted back to pure Kindle launcher) and make sure I don't allow the Kindle App to auto-update.
[Kindle Fire Android Development] ej_424:
Kindle Fire 6.1.3

Will this utility work with 6.3.1 (latest kindle update) . This will root and install custom recovery for rom flashing correct?

Thanks,

ej_424
[Kindle Fire Android Development] MizzouBrent:
Yes, just follow my steps 3 posts above. I was running 6.3.1 when I did that. I never bothered with the Perm Root option. I just installed TWRP, flashed the FFF bootloader, and then started flashing roms. I had no desire to have a rooted stock setup, and it seemed to cause issues for some people anyway performing that step. Totally painless process for me. YMMV.
[Kindle Fire Android Development] krufttangoud:
Ok. I installed clockwork because that is what I am comfortable with using on my phone. However, I want to flash AOKP which needs TWRP to run properly. Tried to run kfu and install TWRP, but it threw an error code. How do you overwrite the recovery on this sucker?
[Kindle Fire Android Development] krufttangoud:
Hope this helps noobs like me having issues with this utility. I could not do anything with kfu due to: adb offline status unkown error. ADB was installed and all drivers were installed properly. Well, desperate googling revealed this code to be run in CMD prompt:

echo 0x1949 >> "%USERPROFILE%\.android\adb_usb.ini

Paste it in and run it. Kfu instantly recognized my kindle.

I am running 6.3.1 and Windows XP.

Credit where credit is due

http://m.androidcentral.com/how-enable-adb-your-kindle-fire-windows
[Kindle Fire Android Development] hortstu:
Is there a linux version of this tool available?
[Kindle Fire Android Development] yourbrotherrex:
Could I please ask why there are no real instructions in the OP for using this tool?

As in:

What to use if you're using 32 or 64 bit Windows.

What directory the zip should be extracted to.

After extracting, there's a folder within a folder... Is this normal?

Also after extracting, it's said somewhere else that the name of the folder (which I have no idea where to place) needs to be renamed to "kfu"... is this true?

Any information pertaining to location of SDK, files needed, just isn't there.

What if I'm using an AMD-based Windows pc?

Which goes first?

FFF or rooting the device?

and much more that could have been simply listed up front.

But, there's just NOT one word about "installation", "how to install", "how to use", FAQ, etc.

The only reason I'm asking is because in the OP it says that it's kind of self-explanatory... Well, I tried that method, and I quickly bricked BOTH of my Fires. (My fault, I guess, for even trying the second one; I thought I must've made the wrong choice or something, but, when I tried to root the second tablet, being even more careful, I bricked that one too.

Just saying... (and I'm not new to Android, or ADB, or Windows, or partitions, or bootloaders, or yadayadayada. It just irritates me that I just wasted 300 bucks in devices because of the lack of instructions (in an OP that's stickied, no less.).

I'm sure to get an earful from people telling me I should've read all 175 pages, but really, what I bring up is quite a valid point, dontcha think?
[Kindle Fire Android Development] kenikh:
Yeah, I half-bricked mine and spent a good 10 hours saving it, due to incomplete instructions and assumptions. I've found that, generally speaking, great devs aren't typically great writers ("Why do I need to comment my code? It's self -explanatory"). Not to mention really good devs are always thinking recursively and the English language...well, it's not really designed that way.

Soooooo...what to do? Sounds like someone who CAN spin a good instructional yarn should do a nice "how-to FAQ". Then the devs can get back to doing some of that really crazy cool stuff us hacks can't. :)
[Kindle Fire Android Development] 315phatboi:
need help wife is going to kill me

hey im new here to the kindle forum so please forgive me.....ok so had the kindle for a few weeks got bored with it so decided to see what I can do with it...I tired rooting it with latest kindle utilitys I think everything went good it says it did but now im stuck at a bootloop and really have no clue what to do!!!!??? can someone please help me please and thank you :confused::mad::confused:

edit sorry got it working
[Kindle Fire Android Development] yourbrotherrex:
That'd be nice, but how many devices have to be sacrificed each time this happens in however many threads until someone else takes the time and initiative to play translator for the dev?

(It hasn't happened yet in this thread and we're 174 pages in.)

No, I think that if a dev creates a thread with the intent of having users follow his/her advice, and taking the risk of bricking their device, then it's just common courtesy and a natural course of logical thinking that they should provide instructions on how to use the said exploit/hack/root method etc.

Call me crazy.
[Kindle Fire Android Development] krufttangoud:
I don't mean to start trouble, but if you are going to flash relatively untested developer software from a thread in a forum, you need to expect that it is going to break your device. I read the first couple pages of anything I want to flash to make sure it is a good product. If the dev doesn't provide adequate instructions for you to flash in confidence, please click the back button.
[Kindle Fire Android Development] Vashypooh:
I figured most people would do a little bit of research before rooting and so forth.

For those of you that need instructions.

Install the drivers

Run KFU

Press 2

Read

The tool was designed to be completely straight forward and give you a few different choices. I am not sure how people are not able to understand its usage. :(
[Kindle Fire Android Development] krufttangoud:
I have found that if you go too fast and skip steps you make bricks. That's why I bought the unconditional replacement plan at best buy ;-)
[Kindle Fire Android Development] ProfEngr:
I originally rooted with burrito, but had no trouble with this method when I had to revert and start over. Honestly, it took longer to download files than to perform the root & twrp.

Sent from my TBolt with the XDA App using 1 opposable thumb
[Kindle Fire Android Development] yourbrotherrex:
Wow.

Really fantastic directions...Thanks so much.

Now, if you wouldn't mind:

Is this meant for 32 or 64-bit Windows machines? AMD ok? Does it matter?

Can I extract the zip anywhere?

Is there anything else that I need to already have downloaded/installed on my PC for this to work?

How can I tell if the drivers are installed correctly? i.e.: What am I looking for as far as what Windows calls the KF after installation...Kindle Fire? Android Phone?, something else?

Do I connect it when it's on, off? Must I use the stock cable?

^^^^You know...little things like that might help those of us who don't magically already know the answers to questions like these. I only mention this because when I tried it (on two Fires) using the directions you just listed: "install, run, press 2, read, durr-hurr" I ended up with two bricked tablets.

(So there's a little more to it than that, wouldn't you say?)

Look, you can yuk it up all you want about how dense I am for not figuring it out on my own, but the point is that users shouldn't really have to figure it out on their own...,that is, they wouldn't, if you could just please try and see it from the point of view of someone who a)didn't write it and b)isn't around it every day.

It would be much appreciated, because, if I could ever get it to work for me without rendering my device useless, it sounds like a really great tool.
[Kindle Fire Android Development] redbean25:
You say "bricked" Kindle Fire Tablets...are they really bricked, or just soft-bricked to where you cannot figure out how to get them back? Do they turn on at all, or did you put a bad bootloader on where it will not boot up at all?

If you read through the run.bat script you will be able to see what it does. It is just a script that gathers all the necessary commands into an easy to use tool so you don't have to do all the command line stuff yourself. Can you tell me EXACTLY the steps you went through from start to the point where it became bricked? If you can provide the details we might be able to help you get it back.
[Kindle Fire Android Development] krufttangoud:
Unless you absolutely borked the bootloader, your kindles are soft-bricked. Hold down on the power button for 20 - 25 seconds and it should reboot and you should be able to access recovery. You would have had to unplugged them during the transfer of the FFF bootloader to break it. Just flashing root or software "should" not cause a Hard-Brick scenario.

I hope this works and you get those guys running AOKP it is fabulous!!
[Kindle Fire Android Development] kinfauns:
I think you might have all of this confused with some commercially released software full of EULAs and support commitments. Everything here is user supported and doesn't go through a staff of hundreds of quality assurance personnel testing every conceivable hardware and software combination. Software like this is released in the spirit of community because the developer figured, "this might help somebody." Ultimately, you are responsible figuring it out and making it work for you. Turn down that entitlement dial a bit, do a little bit of research and provide some meaningful information so others can help you unbrick your devices.

From what I can tell, the answer to all of your questions is "it doesn't matter." KFU is self contained, will auto-download the software it needs and has drivers for both 32/64 bit systems. If you looked around at all, you would have found this...

http://xdaforums.com/showthread.php?t=1552547

Post #1 gives you background information about your device.

Post #2 has device driver information and troubleshooting details.

Post #3 provides a tutorial for adb and fastboot to do all this manually.

A super-majority of bricking problems stem from device driver issues. Focus on #2 and make sure your drivers are getting loaded so the host computer can recognize your devices.

This guide...

http://xdaforums.com/showthread.php?t=1638452

gives you a step by step walkthrough on what you'd need to do root or install a ROM.

There are also many other guides that can help you gain the requisite knowledge to fix your devices. You just need to look around.
[Kindle Fire Android Development] Vashypooh:
Nope

Root of the C:\ is best, but yes as long as it isnt a network drive.

Nope, and is likely to break this, Kindles ADB is a pain to get working.

Android ADB device, it shouldnt say kindle anywhere, and this is the root of most peoples issues as Fastboot and ADB use different drivers.

I have heard of better luck to be had installing the drivers before the kindle is plugged in, but nothing really to prove it.

And as always I have suggested people hop in IRC and I help in person. If your kindle is bricked etc, I can usually get it going over teamviewer.
[Kindle Fire Android Development] yourbrotherrex:
Holding down power (when I could get the logo to appear) did nothing but turn them off. I read elsewhere that sometimes you can get "stuck" temporarily in Fastboot, and can usually get out of it by long-press powering to turn off, then rebooting a bit later; I must've tried that 50 times....no luck.

I basically did exactly the steps that were suggested a few posts back:

Extracted the zip, ran the install_drivers bat, (got a successful driver install message from Windows), ran the main script, pressed 2, got waiting for device, plugged in KF, then got some kind of message like "Fastboot and ADB ...different...take a look at....something..." .

Then the devices showed only the logo, and were completely unrecognizable from the pc (might as well have plugged in a potato), they didn't take power, apparently, today they were both dead...

Already tried making a bootable Linux USB stick and going that route: everything works fine up till the point where I plug them in: device still not recognized, because in the Ubuntu terminal, still saying "waiting for device".

:(
[Kindle Fire Android Development] krufttangoud:
Dude...so you didn't even get a Recovery installed...sorry. Best bet is to hop into IRC and have them help one on one.

Good luck!

Try this real quick this helped me when I was at my last straw with ADB and Fastboot.

Well, desperate googling revealed this code to be run in CMD prompt:

echo 0x1949 >> "%USERPROFILE%\.android\adb_usb.ini

Paste it in and run it. With KINDLE PLUGGED IN! Kfu instantly recognized my kindle.
[Kindle Fire Android Development] yourbrotherrex:
I found the same advice somewhere here on XDA: already tried it, no luck, either.

I don't know what else to do.
[Kindle Fire Android Development] krufttangoud:
Ok. It took me like a while to get my drivers running correctly, but, I did this and it worked.

1. Plugged in kindle and uninstalled all drivers, unplugged and rebooted PC.

2. Plugged in kindle and let it auto install all the drivers. I KNOW but the .bat included would not run no matter what I did.

3. Put KFU in the C: root directory, and renamed KFU.

4. Ran KFU from CMD prompt, opened another CMD prompt and ran the code above.

5. Hit 0 to refresh the device and it worked.

6. Rooted

7. Then FFF

8. Then TWRP

?????????????

9. Profit.

Hope that works. If it doesn't I am at a loss.

If you live in MD you can come to where I work and we will fix it.

Peace.
[Kindle Fire Android Development] weedahoe:
I bought the wife a KF today from Sams Club. Ive never used one before but know they are well liked. So I jumped here on XDA and read this thread and and went through all the steps flawlessly and installed this ROM (link) and have it up and running flawlessly and FAST. The wife loves it. THX everyone.
[Kindle Fire Android Development] hrbib21:
OH.MY.GOD. Worked perfectly. Thanks a million.
[Kindle Fire Android Development] Nickel17:
Awesome.

So after two days, on and off, of trying to get the drivers to install correctly I finally did it. Thank you for this! :good:
[Kindle Fire Android Development] Toejamfloyd:
Whoops!

Hey, all!

I've done this to 3 kindles so far at the office, and it's all worked great until this last one. I used the KFU, everything going smoothly, got TWRP installed, copied CM9 ROM over, installed using TWRP. Now, however, when the KF boots up, it doesn't show the blue 'kindle fire' screen, like the other kindles. It's still orange, and then boots to the ROM, but is stuck at the initial loading screen for the ROM.

KFU sees the KF as 4000, but when I choose to reboot into recovery, KFU just says waiting for device.

Is there any other way to kick the KF out of the boot, and load into TWRP recovery? I'm worried because the other KF's all have the boot options at the beginning with the blue 'kindle fire' screen, but this one doesn't show that.

Any ideas or opinions would be great!

Thanks, OP, btw. I've been trying to donate but my Paypal's been eff'd recently...
[Kindle Fire Android Development] Asylum1621:
Won't work

This doesn't work for me, here are 3 screen shots, #1 from when I tried to root, #2 from the FFF install, #3 from TWRP.... won't reboot in recovery mode at all basically

My drivers installed just fine, I don't see kindle or amazon, I see android adb device like I should. Any ideas? Those of you that are like "do a little looking around" jesus... this thread is a couple of hundred pages long, I've read them all... also I know how to use adb and I've rooted oh i don't know 40 devices. I'm glad your install went well, I really am, but have a little tolerance for the people's whose installs did not go well. Nobody expects this to be a .msi click next 3 times process but can't you understand how 300+ pages of reading later people are frustrated that their device is broke and the instructions DON'T WORK FOR THEM. Save the frustrated people another half page of reading by not adding your "you're dumb look harder" comments.

Additional Info: No my device is not bricked, it just keeps booting up like an every day normal kindle fire... it won't enter recovery mode at all.

KFU recognizes the device just fine, ADB Status: Online Boot Status: 4000 (Normal Mode)

If i go to bootmode menu (option 1) and then select option 3 (recovery mode) the device just reboots into normal mode. Holding down power for 20-25 seconds = Normal mode.
[Kindle Fire Android Development] krufttangoud:
I am 100% not an expert on KFU, but from the screen shots it doesn't look like it is able to connect to the specific URL's where FFF, TWRP, and CWM are downloaded from. If they don't download I don't think it can install them. OP might be able to confirm or deny.
[Kindle Fire Android Development] mt3g1:
so first off i have read this thread many times...i got my wife KF to root the first go around no problems at all....when i plug mine in and get KFU running it shows ABD status :online but boot status says unknown....ive tried everything this is on windows 7 incase yall ask....please help i love hers and want mine done ASAP... and again i have tried everything...when i plugged hers in it popped up as online and boot status as normal (4000)
[Kindle Fire Android Development] Dasanko:
Sounds like FFF (and maybe TWRP as well) did not install - try giving them a go again. You can easily boot into recovery by issuing "adb reboot recovery" (start a command prompt in KFU\tools) if TWRP has been properly installed.

wget is failing to download (PATH issue maybe?) - fetch the URLs from KFU\files\files.log, double check the downloads' hashes, and then try either: Placing them in KFU\recovery (may have to create that folder) renaming them as fff.bin for FFF and twrp.img for TWRP, or using the (IMO, better) manual method (ie, fastbood/ADB) to flash them.

I'm not sure what are you asking exactly. It does sound like you have a driver issue (boot status is not being properly reported), however, on the other hand, KFU's boot status report is not very reliable anyway, so it may be working just fine. One easy way to check if KFU will work is to start a command prompt on KFU\tools and type "adb devices" to see if there's any listed (must have the KF plugged in first).
[Kindle Fire Android Development] yourbrotherrex:
I agree.

To whoever told me that I just needed to read more: I DID read everything in this thread, and more, before trying it.

I'm neither new to flashing/rooting devices or to the etiquette of this forum (as in: read first, re-read, THEN possibly ask), so go try and sell that tired-assed "lose the entitlement" message to someone else: I'm not buying.

Let me just ask one question:

If this utility is so simple to use, and the OP was user-friendly enough, then why in the world is this thread 175 pages long and counting?

(By the way, thanks to ThePooch for offering all the help he has in helping me get my tablets up and running again.)
[Kindle Fire Android Development] hrbib21:
If you're using Windows XP (don't know if it works on other Windows versions), copy/paste, and run this in a CMD prompt window:

echo 0x1949 >> "%USERPROFILE%\.android\adb_usb.ini

Everything worked perfectly for me after a week of trying to figure this crap out.
[Kindle Fire Android Development] quarky42:
OP: thank you VERY much for this tool.

I used it, today, to successfully fix the calendar and contacts sync on the MoDaCo 9.1 ROM Update.

Would you consider splitting the option for installing the Google Apps away from the Go Launcher *OR* add two more entries... one just for Google Apps and one just for Go Launcher?

Thanks.
[Kindle Fire Android Development] concac858:
If anyone Still having trouble rooting there kindle this is what i did.

1. Unplug your kindle from the PC then go to Device manager and uninstall any kindle or android drivers and restart your Pc.

2. After it boots up dont plug your kindle to your pc yet. Go to the Kindle fire Utility folder and double click on install_drivers.bat follow what it says and click finish when done.

3. Now plug your kindle in to your pc and double click run.bat.

It should say

adb status: online

boot status:4000

Then pick 2.
[Kindle Fire Android Development] juntistik:
Hello everyone, quick question. I am using twrp v2.0.0 (as per the display in recovery), I simply want to wipe my personal data and the sd card ( but leave the rom, and if possible, Gaaps). Is it safe to do this using TWRP? I am having no luck using the in ROM factory reset
[Kindle Fire Android Development] kelvinleow:
Unable to get online despite many installations

Despite my installations of Android SDK and the installation of the driver inside this KFU 0.9.6.

I could not get the Kindle Fire online ADB.

I have rooted and customised roms for 2 other tablets, 1 Samsung Galaxy numerous times. And the drivers is correctly installed.

Yet, it cannot detect my Kindle Fire ADB online.

It can see the Kindle folders and the content within.

Did I do a mode wrong?
[Kindle Fire Android Development] Dasanko:
What's the output of "adb devices"? Empty?
[Kindle Fire Android Development] kelvinleow:
it is offline.

Actually in my previous post, I added the 3 pictures, to show that the ADB Composite driver is working perfectly, but the KFU 0.9.6 is still offline.

ADB devices search is also blank.
[Kindle Fire Android Development] ghost_og:
Same thing happened to me when I upgraded my netbook to win7 this weekend. I just deleted the drivers, re-ran the install script, and rebooted the kindle. After that it was recognized when I checked it from the command line.

The kfu seemed to be hit and miss with recognizing the boot status, but both adb and fastboot were working perfectly from the command line. I don't know if it had to do with running a bunch of commands and checking the boot status in between, but more often than not kfu would say offline even though adb was working.