yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Thepooch:
Lol bad download its 2 KB in in size instead of the 5.48 mb it should be I'm not having any personal issues I fastboot flash my stuff but this is creating a huge problem for the noobs who wish to use the utility it clearly needs to be fixed to prevent mishaps...

Also if the correct file is placed in the recovery folder kfu decides to delete local content leaving you without the image file itself...
[Kindle Fire Android Development] raywaldo:
The GOO.IM site appears to be back online now and hopefully all the files are working again. Try it again.
[Kindle Fire Android Development] haroldmk:
I see that many people are having the same problem I got while trying to root the KF, I also got the message "opps... something went wront with the download". I guess I can wait a few days while the problems is solved. Thanks all the people who work hard on these root tools and roms.
[Kindle Fire Android Development] G4 Man2:
Okay so my kindle is showing up as android composite adb interface but adb still says its offline :/ what am i supposed to do now?

EDIT: I went into recovery and restarted into the bootloader and then installed the adb drivers for android adb interface and now everything is well
[Kindle Fire Android Development] digz6666:
I end up in TWRP mode, cannot do anything, tried rebooting into recovery or bootloader.

It says some errors while moving root_check or something.

mv /system/bin/check_rooted failed
[Kindle Fire Android Development] radici:
same issue as above...any help? i can however fully boot past twrp if i change boot mode to normal, but i'm figuring i'm missing something since i'm not getting past this step.
[Kindle Fire Android Development] digz6666:
I mounted SD card from TWRP menu and installed Jelly Bean from this thread:

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

But if I reboot my kindle it automatically goes into TWRP, I click power button and select normal boot mode every time in order to use, which is annoying. How can I set default boot mode to normal?
[Kindle Fire Android Development] radici:
but, without disabling root checker have u retained root on jellybean?

oh and try adb shell nbmode to boot normal

http://xdaforums.com/showpost.php?p=29186989&postcount=157
[Kindle Fire Android Development] chamnv:
i use KFU 0.96 to root my kindle fire, but it hang kindle fire logo. I use factory cable to boot fastboot but it can not boot to fastboot and normarl boot.

How do?

Fix: driver confilict
[Kindle Fire Android Development] JimCo06:
I had a similar situation. When I re-booted it would just stay on the FFF screen until I selected normal or recovery. What I did was choose the third option, select boot mode. Since then it has automatically booted to normal on re-boot unless I manually change it.
[Kindle Fire Android Development] iclickjohn:
Using 9.6 - drivers installed OK. Run - never seemed to mention rooting, just ended up with Kindle in TWRP. KFU states this>

sbin/sh: idme: not found

699 KB/s <22364 bytes in .031s>

Attempt to remove root checker

mv: Can't rename' /system bin/check_rooted/: No such file or directory

please wait.......

This was the second time attempting to use KFU. The first time it did the same. I uninstalled drivers and rebooted PC. For a while I was very afraid I couldn't get out of TWRP (which does show up on the fire) every boot returned to TWRP. Not sure what I did to return it to normal reboot and so if I am lucky I will find that path again, now. At this point I will stop trying to root until I can get better understanding of what is going on.

Any ideas of what is going on????
[Kindle Fire Android Development] nuttmeg:
Can anyone shed some light on this, i cant do nothing but boot to recovery, i wipe everything cause i was getting ready to install cm10 and now i cant even install the rom or the update.zip thats on my sdcard. I tap it the file to flash but when i tap flash nothing happens, it's like the flash button is disable or something, same thing when i tap reboot and tap system, recovery or boot loader.

:confused:

NM had fixed it, i had removed the old twrp theme and reinstall with new utility and im up and running.
[Kindle Fire Android Development] incognico:
The drivers fail to install on Windows 8!
[Kindle Fire Android Development] iclickjohn:
here is what I got below. Followed everything to a T. Factory reset the Kindle Fire. Installed Android SDK on root of C drive. Installed Drivers provided by OP. This all went fine. I plug in the Kindle and Run KFU. Online, OK. Chose option 2, OK. Right away I see it is NOT installing root. Only what we see below. I have KFU installed on the Root of C as well. (renamed to KFU) I checked device manager and it has listed at the top Android Phone I click on that to update the driver and go to the KFU but all attempts result in the response the installed drivers are up to date.

My Noob opinion, but this is not set up right. All things considered, there needs to be a way to get everyone to an equal starting point so that this runs properly. Just look at the posts. But that is probably to be blamed on everyone at a different starting point. I'm sure there must be one or two people who have got this to work. The rest of us are scratching our heads wondering if the OP is saying to us "Hey Noob, O-KFU" (OK just joking there) If anyone can make sense out of the below KFU dialogue and could give a heads up, that would be great. AND/OR get all of us at an equal starting point, thanks.

Fastboot uses a different device than ADB.

You should check device manager for "Kindle" or "Amazon"

If you see it, rerun the driver installer that came packaged with KFU.

Installing FFF...

< waiting for device >

sending 'bootloader' (243 KB)... OKAY [ 0.066s]

writing 'bootloader'... OKAY [ 0.147s]

finished. total time: 0.213s

Installing TWRP...

sending 'recovery' (5448 KB)... OKAY [ 1.365s]

writing 'recovery'... OKAY [ 1.005s]

finished. total time: 2.371s

Setting Recovery Bootmode.

... OKAY [ 0.079s]

finished. total time: 0.080s

rebooting...

finished. total time: 0.001s

Please wait...

/sbin/sh: idme: not found

464 KB/s (22364 bytes in 0.047s)

Attempt to remove root checker.

mv: can't rename '/system/bin/check_rooted': No such file or directory

Please wait...
[Kindle Fire Android Development] iclickjohn:
BOOM! did it on a different computer Windows 7. Rooted, finally. I think there is "stuff" left behind from rooting phones and such on my home computer, I don't know. But I would recommend trying on different computer. Because this method is so very simple. Just be patient when it says just wait.....

(just wait) Now, CM10.
[Kindle Fire Android Development] Zaiden:
I'm stuck

I got to

Installing FFF

<waiting for device>

My Fire is just sitting there on the boot screen and it's been about 20 minutes. Not sure what to do. Should I just unplug the device or what?

FYI - In Device Manager there is nothing about the Kindle anymore.
[Kindle Fire Android Development] pkopalek:
I'm stuck right here, as well. There is a yellow exclamation mark 'Unkown USB Device', or now that I have a VM opened, (not set to take peripherals in so it's weird), VMWare USB Device shows up.

Win 7 Pro 64-bit here.

I don't know how to get this thing out of Fastboot mode. I tried holding the power button. Hmm.......

Will this thing charge while it's sitting here? I don't have anything else I can do to remedy this situation. Take the back off and remove battery?
[Kindle Fire Android Development] pkopalek:
Okay -- I figured it out.

I had plugged the device into a USB 3.0 slot (which is fine for most of my devices, but apparently not this, after reading through a whole bunch of threads, or specifically the fastboot thread: http://xdaforums.com/showthread.php?t=1668159 which was incredibly helpful -- try that thread!)

I had to uninstall anything that showed up when plugging it in, then re-install drivers, then start over!
[Kindle Fire Android Development] chamcham737877:
hi, help me please, I did not follow the instruction :(

1. Run.bat,

ADB Status: Online

ADB Rooted: No\

Boot Status: 4000

2. I did not go to Fast mode but selected Install Permanent Boot with Superuser :(

Now my Kindle always boot loop to TWRP Recovery,

First it shows kindle fire, then TWRP mode

please help me how to make it works normally

It's ok now :) thanks
[Kindle Fire Android Development] DRamer77:
mine is boot looping to recovery too, i tried wiping data and installing a Jb rom, when i go to reboot it comes right back to recovery

---------- Post added at 05:10 PM ---------- Previous post was at 04:44 PM ----------

I Figured it out guys.. when you reboot and at the bottome it says push button to change boot mode, push and hold the power button untill you notice it highlighting different boot modes, then release when its by normal..

---------- Post added at 06:05 PM ---------- Previous post was at 05:10 PM ----------

seems to default back to recovery though when i reboot.. dunno how to change that
[Kindle Fire Android Development] wxl104:
Hello,I have the same problem like you , and what you did for fix the kf?

---------- Post added at 04:12 AM ---------- Previous post was at 03:24 AM ----------

could anyone tell me that if after I flash twrp ,I install the rom in kf ?And after install the rom,I only to do is boot the system?
[Kindle Fire Android Development] munsterrr:
NM. Got it.
[Kindle Fire Android Development] dja2k:
Got a hold of my dad's kindle fire and this is my first time rooting it. I installed the drivers and then proceeded to installing root. I would keep booting into recovery and nothing would work under reboot options to get it running back to system. Then I read about holding the power button and choosing the option there, which worked great, but the options in recovery nor inside a custom Rom to reboot normally work, they keep going to recovery no matter which option. How can I fix this? Thanks!

dja2k
[Kindle Fire Android Development] AMCJUNGLE:
I was using the newest revision Version 0.9.6 of the Kindle Fire Utility and I selected option number 2 which was Install permanent root with super user and I got stuck installing FFF. The window said waiting for device, but the Kindle did nothing but display the Kindle Fire logo. Can someone please assist me? I have been searching and not yet found an answer. The computer no longer recognizes the Kindle. When I plug it into the computer I get a pop-up. USB device not recognized. Any help will be appreciated thanks.
[Kindle Fire Android Development] soupmagnet:
The newest version of TWRP has that fixed.
[Kindle Fire Android Development] AMCJUNGLE:
I am having the same issue

I did the exact same thing and got the same results. Did you get anywhere with this yet? Somebody please help us, thank you!
[Kindle Fire Android Development] droid_noobie:
Replace TWRP with the latest version. I have faced the exact same problem and downloading the latest version fixed it.
[Kindle Fire Android Development] Vashypooh:
KFU should be installing 2.2.2.1 as of right now.

Sorry about that.
[Kindle Fire Android Development] oaba09:
Thanks for the easy to use package!!!!!
[Kindle Fire Android Development] Jaemostoriginal:
my kindle was running fine until earlier today. I had powered it off to go into the alternate rom when I went into the bootloader to switch i pressed the power button a bunch of times for it to only get up to recovery. then when i rebooted the system from recovery it just stays at the firefirefire bootloader screen not moving to another selection and not even booting into the normal boot

I'm running v.0.1
[Kindle Fire Android Development] peridoc:
Boot Status Unknown - A solution that worked for me

I too was getting the Boot Status "Unknown" as many people did here and I finally figured out the issue (at least for me). The problem is that I have cygwin installed and it has it's own UNIX version of the FIND command. Once I took the cygwin one out of the equation (I just removed cygwin/bin from the path environment variable of windows, but I assume that you could put the full path to Windows FIND in the run script) I was able to operate normally. This prevented me from running the run.bat script until I got the correct FIND script being used.

Maybe the scripts should be altered to reflect the full path to the FIND command for windows.

Hopefully this helps other people with a similar issue.
[Kindle Fire Android Development] MinionOfEckerd:
Any suggestions for me to get my KF back to a usable form:

1. Haven't used it in a month (was rooted/installed rom)

2. Went to charge it today and I'm getting the Triangle/Fire screen that flashes on for about 3 seconds, then it goes blank. Then the screen comes back on and repeats. If I unplug it, it shuts off but won't turn on.

3. Plugged it into the computer via usb cable, same thing happens when trying to charge it. Does not show up in ADB devices, Fastboot devices and am not able to use KFU to boot it into any mode. (Stuck at <waiting for device>)

4. In total it has been charging (aka blinking on an off) for about an hour. (might need more charging?)

My ultimate goal is to return it to the Amazon stock update. Thanks!
[Kindle Fire Android Development] soupmagnet:
http://xdaforums.com/showpost.php?p=25400963
[Kindle Fire Android Development] samio2:
Hello,

is there a possibility to support the FireHD 7" ?

Thank you
[Kindle Fire Android Development] shuvabrata:
Used KFU to root my Kindle Fire. But unable to get Superuser and CWM. Please help.

regards,

Nandi
[Kindle Fire Android Development] ProfEngr:
CWM is offline by request of its author. Bad things happen when it's installed.

Sent from my Thunderbolt using one opposable thumb.
[Kindle Fire Android Development] shuvabrata:
How do i flash a JB ROM then? Via TWRP?

Pardon my ignorance. I am new to the Fire. Been using CWM for all my flashing in Galaxy S2.

regards,

Nandi
[Kindle Fire Android Development] ProfEngr:
The Kindle is first device I've used TWRP on.

To answer your Q, yes. Make sure it's 2.2.2.1 (I think is latest). Older ver had an issue that eludes me ATM.

Sent from my Thunderbolt using one opposable thumb.
[Kindle Fire Android Development] Stevethegreat:
...interesting.

1) After 8 months of complete stability my Fire decided to freeze, I rebooted but it never booted back (to CM10) so instead I tried going to TWRP (I'm using the latest), it's stuck at the image with the name "TeamWin" written on it.

2) So a last resort I'm trying this utility, it say "online", I install the latest FFF (thinking it's the bootloader's fault that I cannot load CM10, or even TWRP for that matter of fact) everything goes OK according to KFU, yet the same teamwin pic is staring -still- at me with a "deadpan expression".

3) So I decide to reboot my Fire again only this time to be confronted by a "device is offline" which for some reason cannot go away (installing-reinstalling the drivers including). What's even weirdest is how Windows can actually "see" the Fire (as an "Android ADB interface") yet KFU (or ADB for that matter of fact) can't...

Any suggestions?
[Kindle Fire Android Development] soupmagnet:
I'm thinking your best bet would be to use Firekit to replace your bootloader , TWRP, and fix your partitions. If it is your bootloader that is messed up, it's very likely your only option.

P.S. You may very well have to pull the back cover off the device.
[Kindle Fire Android Development] Stevethegreat:
At this point I'm not sure what's going on. Also I would prefer not to to have to kill my data all the while trying to "save" my fire (if that's possible of course).

Basically what happens is that the tablet boots and then instead of loading the rom it gives me a black screen so I try to boot TWRP instead and -again- it hangs but that time at/around when the picture reading "Teamwin" appears.

Anyway given that it happened "out of the blue" (I didn't install or removed anything for ages), it merely rebooted; what can the possible causes be? Maybe knowing that would also help us/me determine the solution as well...

BTW when it boots (onto the black screen) the LED remains lit in the "orange" indication. If instead I'm trying to boot into TWRP I get the green one so my fire can obviously see the USB connected, my adb doesn't though (for whatever reason) even though even windows can recognize it (in devices menu). I would prefer if I was not to have to open the backplate either...

edit: Basically here's what I cannot understand: Even though windows does "see" my fire why is it the case that I can do nothing to "save" it? To most people the problem was/is that device manager cannot see that an "android device" is connected, I do not have this problem yet -I feel- I'm in the same boat as everyone else ... why is that?
[Kindle Fire Android Development] soupmagnet:
Well let's break down some of the symptoms that you are experiencing.

Typically, when the device boots to a black screen, it means you either have no system files in place, or the system files needed to boot properly are corrupt. When this happens, you need to get into recovery to reinstall those system files. You have FFF installed and working, so there is no need for a factory cable.

If you tried to boot into recovery (TWRP) and it hung at the splash screen and didn't go any further, I would normally say just reinstall TWRP. But since the same problem is happening on both the recovery and system partitions, and it happened suddenly, I'm leaning towards something bigger being the problem.

Using Windows to try and fix your problem in this particular situation would probably not be the best option, as you could never really narrow down the exact problem, and Windows is notoriously finicky when it comes to changing bootmodes on a USB device. Linux would be your best option in the long run because if it is your bootloader or something of the sort preventing you from using fastboot to reinstall TWRP, you'll have to use Linux anyway to run the Firekit. But you could very well be dealing with Windows driver issues too, so I think it's best to eliminate as many variables as possible.

You can create a Linux LiveUSB rather easily and install SoupKit to get adb and fastboot working properly. Or you you can use this, which would eliminate one of those steps and save yourself a little bit of time, but not much.

You should reinstall TWRP to see if doing so will give you access, so you can make a backup of your data partition and reinstall your ROM. If reinstalling TWRP doesn't give you access to it, I think Firekit would be your last bet.
[Kindle Fire Android Development] Stevethegreat:
Thank you!

So I downloaded the Kubuntu ISO you recommended. Booted normally (live kubuntu) but whenever I'm trying to run "adb devices" it says "no command found", same when I install the soupkit. Are you sure it's ADB equipped (the ISO you gave me)?
[Kindle Fire Android Development] Thepooch:
Positive reformat and recreate your live USB follow the instructions to the letter and adb will work fine. There is no need to run soupkit on the iso setup as well since you ran soupkit and had the same result I'm inclined to believe you are doing something wrong when you run soupkit. Just out of curiosity try this iso instead http://db.tt/KDNzyCTP same instructions.
[Kindle Fire Android Development] Stevethegreat:
I ran soupkit on an ubuntu live cd sorry for not clarifying.

Anyway, I managed to enter in fastboot mode while in Windows and re-installed (the latest) TWRP .... still nothing. TWRP still hangs when trying to boot, I'm starting fearing there there's some deeper damage probably involving the hardware...
[Kindle Fire Android Development] Thepooch:
Yeah soupkit will not work on a live CD it must be a live USB with persistent to work. The kubuntu iso must be on a USB flash drive as well.
[Kindle Fire Android Development] Stevethegreat:
Indeed my live USB was "corrupted so I had to remake it. This time around all commands worked. So through firekit I reinstalled both FFF and TWRP but same stuff happens. It never boots, it never starts TWRP, I'm thinking -maybe- I should install CWM or some other recovery because TWRP simply refuses to co-operate.

Right now -as it stands- I reverted to the older bootloader (the one with the Triangle), probably older TWRP as well, but nothing actually works. I'm thinking maybe I should save my /data folder using the adb pull command and even that may be proved meaningless if my Fire is blast...

Any ideas?

edit: Since TWRP doesn't seem to be capable of being installed (I tried many methods) does that mean that my Kindle Fire is unusable? Is it a real Brick, or -maybe- reverting to Amazon OS (restore partitions first?) would -at least- give me a half-working tablet. Lastly I can use fast-boot's capacity to flash zips, maybe that can give me my old CM10, or even that is a pipe dream?

I'm asking because I don't want to try something which would make my Kindle worse, any opinion/recommendation would be more than valuable at this point, being a tool of my job (my KF) and also containing critical files makes me more than inclined to solve this any way I can. Thanks and sorry for the mess (that I created in this thread).
[Kindle Fire Android Development] Thepooch:
You know you could be right about something. Fastboot flashing the latest Cannibal Open Touch Recovery might not be a bad idea, it would certainly get you past the splash screen and possibly throw some errors to aid in diagnosis. I would bet data loss is inevitable so you might as well face that demon.
[Kindle Fire Android Development] Stevethegreat:
OK I'm willing to try it.

As for data loss, are you sure I won't be able to save them using the adb pull command? Of course any time I have tried till now it retrieved no files but I can clearly navigate in my /sdcard folder through adb shell, I just -for some reason- can't pull the data out... As for my /data partition indeed it seems to be dead in the water...

edit: OK so I installed Cannibal Recovery and it booted w/t throwing any errors... so far so good. So I (re)install my Rom, same thing happens (hangs on Rom boot), secondly I try to backup/wipe and I find out that my /data partition is completely broken. In fact there's nothing I can do to it (mount, format, backup) that doesn't make recovery freeze. So I think I have found were the issue was all along (/data partition), any idea of how I should proceed from now on? Can /data be fixed? Thanks.

edit2: I cannot install any custom rom as it turns out. I have tried 4 of them 'till now and they all give me the familiar black screen. So I was wondering whether I should fix_parts (via firekit) and *then* install the stock rom, whether that would fix things or maybe brick my KF forever (given that FFF and the recovery would be overwritten). Should I try this, or would I get a $200 worth brick?