Develop Bugs

KFU Failed, Now Kindle Fire Won't Boot

Hello everyone,
I've tried to find my specific situation in related threads, but haven't seen my exact issue, so here goes. Several threads seemed to talk about what I'm seeing, but the remedies that worked for them have not worked for me.
I have a Kindle Fire running 6.3.1, and I tried rooting yesterday with Kindle Fire Utilities 0.9.6 on a Windows Vista Virtual Machine.
The drivers appeared to install correctly, because KFU was able to see the Kindle and showed "online" when I started the process. The Device Manager seemed to have the correct information as well.
In KFU, I selected option 2 from the main menu, to "Install Permanent Root with Superuser". KFU started downloading twrp.img, but was unhappy with the MD5 checksum, so it issued the error: "Oops... something went wrong with the download. The recovery downloaded is not correct. Please try the download again"
At this point, the run.bat program exited, and the Kindle rebooted.
However, it appears that KFU at least partially succeeded in putting the Kindle into fastboot mode, because now I just get the "Kindle Fire" orange and white logo and nothing else happens. Also, I can no longer access the Kindle from my computer.
Now, when I run KFU again, it can't find the Kindle. I also can't contact it by running adb or fastboot manually, either from Window or from Ubuntu.
I've tried most, if not all, of the tricks I've seen in related threads to get back into contact with the Kindle and restore it to normal boot mode. The fastboot executable gets stuck in the < waiting for device > state, and I've tried power-cycling the Kindle, unplugging and plugging it back in, timing the execution of fastboot with the startup screen, etc. Since KFU did not successfully install Fire Fire Fire or TWRP before the failure occurred, I can't use either of these to recover.
I have ordered a Factory Cable from SkOrPn, but I'm curious if there's anything else I can try before it arrives, or if maybe I've missed something in all of the reading I've done over the past couple of weeks. (I read many threads and posts about rooting the Kindle, along with the Beginners Guide, before I worked up the courage to actually try it yesterday, and since then I've been educating myself on recovery techniques).
Sorry for the lengthy post, thanks for any help or clues, and I apologize if this has been answered already in another thread.

You might try powering it down completely, run KFU, choose option 1, then choose normal boot mode (4000) and when it comes up with <waiting for device> then hit the power button on your Fire.
This has worked for me in getting it back to normal boot when things seemed to be hung up. I sometimes had to hold the power button down to hard shutdown after this, but when rebooted after that, it booted normally.
Can't hurt to try it in this case.

You say you're using a VM, but what OS are you typically running? Mac OSX and Linux both handle device drivers by far better than their MS counterparts.

soupmagnet said:
You say you're using a VM, but what OS are you typically running? Mac OSX and Linux both handle device drivers by far better than their MS counterparts.
Click to expand...
Click to collapse
spfldcynic said:
You might try powering it down completely, run KFU, choose option 1, then choose normal boot mode (4000) and when it comes up with <waiting for device> then hit the power button on your Fire.
This has worked for me in getting it back to normal boot when things seemed to be hung up. I sometimes had to hold the power button down to hard shutdown after this, but when rebooted after that, it booted normally.
Can't hurt to try it in this case.
Click to expand...
Click to collapse
spfldcynic - Thanks for the tip. I tried it, but never got past the < waiting for device > state. It makes me wonder if the Kindle is really in fastboot, or if it's in some other state that makes it unresponsive to external commands. Hopefully the Factory Cable will fix this.
soupmagnet - My host OS is Ubuntu 10.04. I'd like to be able to work with the Kindle directly in Linux, but went the Window route initially because I'd heard good things about KFU. After reading your post, I found the FireKit tools for Linux, but got the same results using the "normal_boot" script that I had with KFU and with directly issuing the "fastboot -i 0x1949 oem idme bootmode normal" command from both Linux and Windows.

calgator said:
spfldcynic - Thanks for the tip. I tried it, but never got past the < waiting for device > state. It makes me wonder if the Kindle is really in fastboot, or if it's in some other state that makes it unresponsive to external commands. Hopefully the Factory Cable will fix this.
soupmagnet - My host OS is Ubuntu 10.04. I'd like to be able to work with the Kindle directly in Linux, but went the Window route initially because I'd heard good things about KFU. After reading your post, I found the FireKit tools for Linux, but got the same results using the "normal_boot" script that I had with KFU and with directly issuing the "fastboot -i 0x1949 oem idme bootmode normal" command from both Linux and Windows.
Click to expand...
Click to collapse
Did you try the whole process from scratch on Ubuntu? Also, plug it into the wall charger and make sure it has some juice before continuing (if you haven't already)
Running low on ideas man, hope someone else can do more for you.

You can't just get up and go with Linux, there is some configuration that needs to be done first. Have you set up your udev rules and installed 32-bit libs?

[SOLVED] KFU Failed, Now Kindle Fire Won't Boot
soupmagnet said:
You can't just get up and go with Linux, there is some configuration that needs to be done first. Have you set up your udev rules and installed 32-bit libs?
Click to expand...
Click to collapse
Yes, after reading your post I've discovered that you are correct. I followed Sblood86's instructions on setting up the udev rules (http://forum.xda-developers.com/showthread.php?p=22067293), and I already had the 32-bit libraries and tools since I have the android sdk and a 32-bit Ubuntu installation.
Armed with this correct configuration, I typed
Code:
"./fastboot -i 0x1949 oem idme bootmode 4000"
And this time, saw the following:
Code:
< waiting for device >
...
OKAY [ 0.201s]
finished. total time: 0.201s
Meaning that all is now well with my Kindle Fire, until the next rooting attempt.
Thanks for your help!
So, although the original KFU problem is not completely understood by me, since my Kindle is working, I'll say the problem is solved.

Kindle Fire "Stuck" in Fastboot

Yes, another one of these issues. None of the other threads provided me any help, so new thread time! Allright, so I had just flashed a stock 6.3.1 Kindle Fire Rom. It all went well. Then I wanted to install FireFireFire Dualboot for other purposes, so i rebooted my Kindle fire first, (I always do this before I do anything rom/recovery related.) I went to adb shell on my computer told it to reboot into fasboot using "fastboot -i 0x1949 flash bootloader u-boot.bin" It boots into fastboot but, the bootloader diddn't seem to install and now my device can't be found on the KFU or standard ADB shell. I would appreciate any help on this issue as I need this kindle fire to be working. I have rebooted it 3 times too see if it could be found it just show "Unknown Device". Thanks, I can provide more info if the need be.

Jared631 said:
Yes, another one of these issues. None of the other threads provided me any help, so new thread time! Allright, so I had just flashed a stock 6.3.1 Kindle Fire Rom. It all went well. Then I wanted to install FireFireFire Dualboot for other purposes, so i rebooted my Kindle fire first, (I always do this before I do anything rom/recovery related.) I went to adb shell on my computer told it to reboot into fasboot using "fastboot -i 0x1949 flash bootloader u-boot.bin" It boots into fastboot but, the bootloader diddn't seem to install and now my device can't be found on the KFU or standard ADB shell. I would appreciate any help on this issue as I need this kindle fire to be working. I have rebooted it 3 times too see if it could be found it just show "Unknown Device". Thanks, I can provide more info if the need be.
Click to expand...
Click to collapse
When you say, " the bootloader diddn't seem to install", could you be more specific?
What does your boot screen look like now?
Were there any error messages?
Did fastboot hang at "waiting for device"?
Do you have custom recovery installed?
Of so, what custom recovery do you have installed?

soupmagnet said:
When you say, " the bootloader diddn't seem to install", could you be more specific?
What does your boot screen look like now?
Were there any error messages?
Did fastboot hang at "waiting for device"?
Do you have custom recovery installed?
Of so, what custom recovery do you have installed?
Click to expand...
Click to collapse
1. Boot screen is saying "KindleFire" the stock one not FFF.
2. No error messages
3. Yes, it hangs at "waiting for device"
4. No I don't
That's what I meant by "It diddn't seem to install".

Okay, the "waiting for device" simply means the drivers aren't working properly. I do not use Windows so I cannot offer any real help other than to tell you to reinstall them. There is a world of different suggestions for fixing the driver problem that you can find by searching the forums or even Google, but they're all hit and miss.
I will tell you to work on the driver issue until you can't take it anymore and then consider, possibly, other options.

Well, I might as well as just use soupkit, as I am dualbooting Ubuntu and Windows XP Pro. I have to wait a bit untill I can use it but, I have it all setup, so I'll get back too you when I get to try it out. If this doesn't work I will do the reinstall drivers, like you said, and hopefully that works. Thanks, for the help!
Update:
Soupkit diddn't work. (FK, not USBboot)
So, now onto Windows XP driver reinstallation.... Yay...
If this doesn't work I guess ill have to do the shorting trick.

Alright, So I did all of your suggestions, soupmagnet. None of them have worked, so I'm lead to beilive it's in some sort of state that won't allow it to be recognized on any ADB shell. I'm going to try the shorting trick, if that doesn't work then I'm pretty much screwed for all I know.
UPDATE:
Just too make sure it wasn't just my Lenovo computer, I pulled out my old gateway, setup the driovers correctly and everything. ( I tested too see if it detected my phone, it did) and it still diddn't detect my Kindle Fire, just said "Unknown Device"

I also have this same issue as well, was going to root my stock 6.2.1, but unplugged it on accident, no FFF, and stuck on the stock orange kindle fire logo.

Jared631 said:
Alright, So I did all of your suggestions, soupmagnet. None of them have worked, so I'm lead to beilive it's in some sort of state that won't allow it to be recognized on any ADB shell. I'm going to try the shorting trick, if that doesn't work then I'm pretty much screwed for all I know.
UPDATE:
Just too make sure it wasn't just my Lenovo computer, I pulled out my old gateway, setup the driovers correctly and everything. ( I tested too see if it detected my phone, it did) and it still diddn't detect my Kindle Fire, just said "Unknown Device"
Click to expand...
Click to collapse
With the device plugged in and powered up, in the Linux terminal, enter...
lsusb
You should see a device labeled either Lab 126 (normal mode) or Google Inc. (fastboot).
Also pay attention to the numbers assigned to the device. You should see one of the following sets:
1949:0006 (for normal mode)
18d1:0100 (for fastboot) -sorry for the typo: fixed-
Anything different will throw off the SoupKit, but it is still fixable.
If "lsusb" doesn't show anything of the sort, you may have bigger problems.

soupmagnet said:
With the device plugged in and powered up, in the Linux terminal, enter...
lsusb
You should see a device labeled either Lab 126 (normal mode) or Google Inc. (fastboot).
Also pay attention to the numbers assigned to the device. You should see one of the following sets:
1949:0006 (for normal mode)
18d1:0100 (for fastboot) -sorry for the typo: fixed-
Anything different will throw off the SoupKit, but it is still fixable.
If "lsusb" doesn't show anything of the sort, you may have bigger problems.
Click to expand...
Click to collapse
thanks, mine showed up what you wrote and changed to normal mode, and finally used ZombiePiratez unbrick tool and worked:good:

soupmagnet said:
With the device plugged in and powered up, in the Linux terminal, enter...
lsusb
You should see a device labeled either Lab 126 (normal mode) or Google Inc. (fastboot).
Also pay attention to the numbers assigned to the device. You should see one of the following sets:
1949:0006 (for normal mode)
18d1:0100 (for fastboot) -sorry for the typo: fixed-
Anything different will throw off the SoupKit, but it is still fixable.
If "lsusb" doesn't show anything of the sort, you may have bigger problems.
Click to expand...
Click to collapse
Thanks. I'll check that out. So to be clear it should just inform me of what mode it is in, correct? Not fix it.

What "lsusb" does, is tells you what USB devices are detected by the system. It doesn't fix anything. It's used a lot as a troubleshooting tool.

Yay.... Progeress?
soupmagnet said:
What "lsusb" does, is tells you what USB devices are detected by the system. It doesn't fix anything. It's used a lot as a troubleshooting tool.
Click to expand...
Click to collapse
Alright, here is what I got.
Bus 002 Device 003: ID 1949:0006 Lab126
So that means it is in normal mode, correct?
----------------------------------------------------------------------------------
Don't know if this helps but,

Correct. So, if you ran the SoupKit and rebooted afterwards, there's no reason it shouldn't work.
Since you are in normal mode, send "adb devices" and tell me what happens. Include error messages if any.
[Edit:] Apparently you posted the pics as I was writing this. This is very interesting. I've seen an issue like this in the not too recent past where a user had a BSOD in the middle of flashing the bootloader. It sort of hard-bricked his device except he could still power it on, but it would not accept commands for anything, and he had the same "unknown device" error. As far as I can remember, it was his bootloader that was messed up, even though it would still power up.
What does "lsusb" give you in fastboot mode?

Adb devices
soupmagnet said:
Correct. So, if you ran the SoupKit and rebooted afterwards, there's no reason it shouldn't work.
Since you are in normal mode, send "adb devices" and tell me what happens. Include error messages if any.
Click to expand...
Click to collapse
This is what happens.
Code:
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ adb kill-server
[email protected]:~$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
[email protected]:~$

soupmagnet said:
Correct. So, if you ran the SoupKit and rebooted afterwards, there's no reason it shouldn't work.
Since you are in normal mode, send "adb devices" and tell me what happens. Include error messages if any.
[Edit:] Apparently you posted the pics as I was writing this. This is very interesting. I've seen an issue like this in the not too recent past where a user had a BSOD in the middle of flashing the bootloader. It sort of hard-bricked his device except he could still power it on, but it would not accept commands for anything, and he had the same "unknown device" error. As far as I can remember, it was his bootloader that was messed up, even though it would still power up.
What does "lsusb" give you in fastboot mode?
Click to expand...
Click to collapse
Also, what is the output of...
sudo /etc/udev/rules.d/51-android.rules

Jared631 said:
Alright, here is what I got.
Bus 002 Device 003: ID 1949:0006 Lab126
So that means it is in normal mode, correct?
Click to expand...
Click to collapse
Before you guys get too far off track...
1949:0006 is shared by the the stock system software, recoveries, CM7 based ROMs and the stock bootloader. These two numbers alone are insufficient to determine the "mode" of the device, so you might very well be in fastboot mode. If you get these numbers, you have to take a look at the bcdDevice value.
Code:
lsusb -v | grep bcdDevice
1.00 is the bootloader.
2.16 is one of the others.
More info here...
http://forum.xda-developers.com/showthread.php?t=1668159

sudo /etc/udev/rules.d/51-android.rules
soupmagnet said:
Also, what is the output of...
sudo /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
Code:
[email protected]:~$ sudo /etc/udev/rules.d/51-android.rules
sudo: /etc/udev/rules.d/51-android.rules: command not found
[email protected]:~$
Here is what I have in the file it's refering too.
Code:
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"

Sorry, I left out "gedit". It should be "sudo gedit /etc..." oh well, whatever.
Either way, that much is correct. It's a tricky situation with stock software because, the boot logo and boot animation are basically the same, and as kinfauns has said, the two modes share the same IDs. But in your case, you can't send either fastboot or adb commands, which makes for an interesting situation. Your udev rules are configured properly for the device, so other than it being in fastboot with a partially broken bootloader, I can't imagine what would cause it to not connect properly.
Definitely use the command that kinfauns gave you and find out what mode you are in. If you are in fastboot, it would seem that your bootloader is corrupt in some way and you would have to use the Firekit to fix it.
As far as I know, if you are using the "shorting trick" correctly to boot the device in USBboot mode, the Firekit should work regardless. (Someone correct me if I'm wrong)
kinfauns said:
1949:0006 is shared by the the stock system software, recoveries, CM7 based ROMs and the stock bootloader
Click to expand...
Click to collapse
I knew that. I just forgot, that's all. ::looks around::

soupmagnet said:
Sorry, I left out "gedit". It should be "sudo gedit /etc..." oh well, whatever.
Either way, that much is correct. It's a tricky situation with stock software because, the boot logo and boot animation are basically the same, and as kinfauns has said, the two modes share the same IDs. But in your case, you can't send either fastboot or adb commands, which makes for an interesting situation. Your udev rules are configured properly for the device, so other than it being in fastboot with a partially broken bootloader, I can't imagine what would cause it to not connect properly.
Definitely use the command that kinfauns gave you and find out what mode you are in. If you are in fastboot, it would seem that your bootloader is corrupt in some way and you would have to use the Firekit to fix it.
As far as I know, if you are using the "shorting trick" correctly to boot the device in USBboot mode, the Firekit should work regardless. (Someone correct me if I'm wrong)
Click to expand...
Click to collapse
I'm going to use the "shorting trick" as a last resort. It's looking like I will anyways. I will post as soon as I get that mode (USB cord is being used at the moment)

Jared631 said:
I'm going to use the "shorting trick" as a last resort. It's looking like I will anyways. I will post as soon as I get that mode (USB cord is being used at the moment)
Click to expand...
Click to collapse
If (when) you try the shorting trick, it's best to use a sharp pair of tweezers or a safety pin to keep from losing the connection while plugging the USB cable in. And the picture of the actual point posted on Pokey's thread is a little misleading...it's considerably smaller.

[SOLVED!] Kindle Fire Bricked on Logo Startup - KFU v0.9.9

I am total noob. Just want to make that clear from the get go.
I hesitate to start a new thread, but I have been working on this forever, and have not made any progress.
I have a Kindle Fire that I would like to run android on - I started the process with the Kindle Fire Utility v 0.9.9. Something went wrong, and it is now stuck on the Kindle Fire start up logo. I also can no longer see it in the device manager, nor is it responsive to anything in the Utility. (ADB status: Offline Boot Status: Unknown). I am at a loss, does anyone have any ideas? Your help is appreciated!
.................FIGURED IT OUT!..............................
Much thanks to the pooch who spent hours helping me troubleshoot.
What we (he) did, as far as I remember, hopefully this can be of some service to someone else out there.
1) Figured out that trying all of this on a Virtual Machine is not a good idea!
2) I somehow broke the bootloader in my first attempt, so none of my computers were recognizing the KF.
3) Created a Pendrive to run Linux (ubuntu). Here Requires a USB drive formatted Fat16/Fat32/NTFS, minimum of 2 gb.
4) Once I got Linux running, installed SoupKit.
5) Went through a few tries of booting, rebooting, into recovery mode until the Kindle flickered back to life!
6) Followed prompts on SoupKit to install TWRP, updated TWRP, install FireFireFire, install Android 4.2.
Good luck, I am happy to answer any questions - though I am no means an expert now.

What I have tried...more info
More Information:
I am running Windows7 in a VirtualBox on an iMac.
I bricked the Kindle a few weeks ago, after messing with it then, I bought a factory fastboot cable. Still no dice.
I have tried all turning on and off computer, on and off Kindle with it disconnected, connected, going through the KFU 4 seconds after starting the Kindle. Letting the Kindle's battery die, recharging.
I have deleted .android folder, reinstalled drivers, re-downloaded KFU.
I have tried on a different computer (Windows XP) The Kindle is also not recognized there.
I have tried booting into Ubuntu (however in the directions there, it said the FireKit is for more "serious" issues than my soft brick.
I am sure there is some small detail I am missing, but I have not been able to find it - and I am not knowledgeable enough to properly diagnose the problem. Again thanks for any help.

kyleboyd said:
I am total noob. Just want to make that clear from the get go.
I hesitate to start a new thread, but I have been working on this forever, and have not made any progress.
I have a Kindle Fire that I would like to run android on - I started the process with the Kindle Fire Utility v 0.9.9. Something went wrong, and it is now stuck on the Kindle Fire start up logo. I also can no longer see it in the device manager, nor is it responsive to anything in the Utility. (ADB status: Offline Boot Status: Unknown). I am at a loss, does anyone have any ideas? Your help is appreciated!
Click to expand...
Click to collapse
Sometimes KFU will show as Unknown even though it's really fine. I had the same issue as you. Try switching boot mode to Normal and see if that fixes it, it worked for me.

Read this (everything),especially third post.
http://forum.xda-developers.com/showthread.php?t=1552547

hemmulde 1st
zastava750 said:
Read this (everything),especially third post.
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thanks for the reply!
I tried that. When I type "fastboot getvar product" it says waiting for device or something similiar.
The advice applying to Device Manager don't get me anywhere, because my Kindle doesn't show up.
Any other ideas?

kyleboyd said:
Thanks for the reply!
I tried that. When I type "fastboot getvar product" it says waiting for device or something similiar.
The advice applying to Device Manager don't get me anywhere, because my Kindle doesn't show up.
Any other ideas?
Click to expand...
Click to collapse
When using the stock bootloader (plain "kindle fire" boot logo), the fastboot command must always specify the custom vendor ID used by the Kindle Fire. For example, the commands above must be slightly altered to...
Code:
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 devices
and likewise, all of the following commands will need the "-i 0x1949" switch when using the stock bootloader. The FFF bootloader's vendor ID has been changed to one that is normally recognized by fastboot, so the "-i 0x1949" switch can be omitted.
Now onto some more useful fastboot commands...
Code:
fastboot oem idme bootmode 4000
fastboot oem idme bootmode 4002
fastboot oem idme bootmode 5001
Using one of these commands will change the bootmode to normal (4000), fastboot (4002) or recovery (5001). Then issuing...
Code:
fastboot reboot
will reboot the device into the respective bootmode.

I've tried that as well...
Just so I am totally clear, this is what I did in relation to those instructions:
Opened Command Prompt - set the directory to C:/kfu/tools
Typed "fastboot -i 0x1949 getvar product" (with out the quotations, obviously)
<waiting for devices>
I plugged Kindle in, it powers on and the frozen logo pops up.
I also tried "fastboot -i 0x1949 oem idme bootmode 4000" and "fastboot -i 0x1949 oem idme bootmode 4002"
According to the guide it often takes multiple tries, I have done it over and over again.
I have also tried different orders of code, plugging in Kindle, and powering on and off.
Am I doing something wrong? Is there a specific code for my Kindle? (Not -i 0x1949)
Thanks!

Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1660636

Reinstall the driver then use kfu to reset the boot mode to normal.

Drivers?
I did try this: http://forum.xda-developers.com/show....php?t=1660636
When I get to the part about the Device Manager, I am stuck, as nothing shows up (I suspect something do with drivers)
Thepooch said:
Reinstall the driver then use kfu to reset the boot mode to normal.
Click to expand...
Click to collapse
By reinstall drivers do you mean clicking on "install_drivers" in the KFU folder? I have tried that.
Is there another method of uninstalling and installing drivers? Sorry if that is a dumb question!

If the devices is in fastboot which I believe it is it would show up as android adb interface, if it was attempting to boot to the system it would show up as android composite adb interface. If you are on xp or windows 8 this can be a bit of a tricky task. Android adb interface and android composite interface are two facets of the same driver. So yes I suggest rerunning the driver installation bat that is packaged with KFU. If perhaps you are on windows 8 you must disable driver signature verification and reinstall the driver. 3.0 usb ports have an issue with fastboot and can leave the device undetected.

Still not working
Thepooch said:
If the devices is in fastboot which I believe it is it would show up as android adb interface, if it was attempting to boot to the system it would show up as android composite adb interface. If you are on xp or windows 8 this can be a bit of a tricky task. Android adb interface and android composite interface are two facets of the same driver. So yes I suggest rerunning the driver installation bat that is packaged with KFU. If perhaps you are on windows 8 you must disable driver signature verification and reinstall the driver. 3.0 usb ports have an issue with fastboot and can leave the device undetected.
Click to expand...
Click to collapse
Thanks for the quick reply.
So I am on a Win7 and/or a Windows XP. Currently on both systems, when I plug it into the computer, with the Device Manager open, nothing happens other than the Kindle turning itself on.
Before it froze up, I saw it in device manager as Android ADB interface, and before doing anything at all, saw it as the default Kindle Fire.
On the Win7 system, I have rerun the driver installation bat over and over and over again, with absolutely no results.
On the WinXP, I have tried it, and for the life of me can't get it to install (it says install failed (Unsigned)). I never connected the Kindle up to this computer before it froze up, so I wonder if that is somehow causing the problem (it is trying to update drivers that don't exist?)
Am I doing something wrong with this? Can I uninstall or delete drivers, and totally start over?

If you are using a WinXP you must install driver manually.

Drivers?
zastava750 said:
If you are using a WinXP you must install driver manually.
Click to expand...
Click to collapse
How do I do that, when the Kindle does not show up as being connected? All the guides I have found start off with accessing from the Device Manager. My Kindle does not show up in the Device Manager...

okay well then you`re running xp use another computer getting the driver installed is hard even for the very skilled particularlly when the device is stuck in fastboot. Friend or relatives computer running windows 7 would be perfect. Otherwise it`s linux on a live usb booted on your xp machine.

Windows 7 - No Dice
Thepooch said:
okay well then you`re running xp use another computer getting the driver installed is hard even for the very skilled particularlly when the device is stuck in fastboot. Friend or relatives computer running windows 7 would be perfect. Otherwise it`s linux on a live usb booted on your xp machine.
Click to expand...
Click to collapse
Yeah so I have a Windows7. I have reinstalled the drivers (by clicking on the install_drivers.bat file in the KFU) over and over again, and I still do not get any recognition on the computer, or in the Device Manager when I plug in the Kindle.

Try different usb port, make sure they are usb 2.0. Is the logo static or animated? It possible that you broke the bootloader. At some point I would be willing to look at some things for you via teamviewer. If it is not driver related I fear your next move is here http://forum.xda-developers.com/showthread.php?t=1430038. Keep it on charger or off till it can be dealt with.

Thepooch said:
Try different usb port, make sure they are usb 2.0. Is the logo static or animated? It possible that you broke the bootloader. At some point I would be willing to look at some things for you via teamviewer. If it is not driver related I fear your next move is here http://forum.xda-developers.com/showthread.php?t=1430038. Keep it on charger or off till it can be dealt with.
Click to expand...
Click to collapse
Thanks! I would be willing to give it a shot (teamview I mean) if you are willing.
I tried the Firekit before I began this thread, but I kept getting stuck trying to run the tool after booting into ubuntu. Perhaps that is a different thread topic, but I am more than willing to put more work into figuring that out, if it could be the key to unlocking this stupid thing.

I am having this exact same problem. Using Win XP i was able to get the ADB drivers loaded initially and used KFU to try to install TWRP. When it rebooted during that process it got stuck at the Kindle Fire logo. Since then I cannot get my computer to recognize the kindle. Like you, I feel like i've tried everything.

Nixnaegie said:
I am having this exact same problem. Using Win XP i was able to get the ADB drivers loaded initially and used KFU to try to install TWRP. When it rebooted during that process it got stuck at the Kindle Fire logo. Since then I cannot get my computer to recognize the kindle. Like you, I feel like i've tried everything.
Click to expand...
Click to collapse
Glad to know I'm not alone - misery loves company! Solidarity my friend.
I wish I could tell you I'd solved it, but alas, I have not. I'm still working on it, I'll keep you updated if I have any breakthroughs!

[Q] Kindle Fire 8.9 Perma-Bricked?

Hey Guys,
I successfully rooted my kindle fire 8.9" a while back and a few days ago decided to follow: http://forum.xda-developers.com/showthread.php?t=2277105 to install the twrp/custom rom.
In fireflash I moved the bootloader back to 8.1.4 and changed the boot and recovery partitions accordingly. I disabled the recovery auto update. I applied the changes and rebooted (I saw the red kindle fire letters and then it changed to the blue letters). It went into the TWRP screen at which point the guide told me to reboot. I found a "reboot to recovery" option and clicked it. Apparently, this was a very bad thing to do. The kindle boots to the Kindle Fire logo in red letters and stays there. it doesn't go blue and nothing moves. It stays that way until I turn it off.
It no longer will show up in Device Manager at all, but if I turn it on while plugged into the computer, the computer makes fast bump sounds like it sees the device for a second.The first time I plugged it into a different computer windows said it was trying to install a driver for "Jem-PVT-Prod-04" but then the driver installation failed and it doesn't show up in the device manager even with an exclamation mark.
Using different adb tools (Minimal adb and fastboot, kindle adb drivers, and android sdk) yields no response from the device even with a factory cable (which I purchased and arrived this morning). Fastboot just says < waiting for device > after the command "fastboot -i 0x1949 getvar product"
Adb kill-server followed by adb devices leads to a blank list of devices. (I also went into user/.android/ to change the adb_usb.ini file to 0x1949 (which it already was)
I tried KFHD SRT v2.1 http://forum.xda-developers.com/showthread.php?t=2011126 but it can't see the device either.
At this point, I don't know what can be done and am open to trying everything.

chickeninferno said:
Hey Guys,
I successfully rooted my kindle fire 8.9" a while back and a few days ago decided to follow: http://forum.xda-developers.com/showthread.php?t=2277105 to install the twrp/custom rom.
In fireflash I moved the bootloader back to 8.1.4 and changed the boot and recovery partitions accordingly. I disabled the recovery auto update. I applied the changes and rebooted (I saw the red kindle fire letters and then it changed to the blue letters). It went into the TWRP screen at which point the guide told me to reboot. I found a "reboot to recovery" option and clicked it. Apparently, this was a very bad thing to do. The kindle boots to the Kindle Fire logo in red letters and stays there. it doesn't go blue and nothing moves. It stays that way until I turn it off.
It no longer will show up in Device Manager at all, but if I turn it on while plugged into the computer, the computer makes fast bump sounds like it sees the device for a second.The first time I plugged it into a different computer windows said it was trying to install a driver for "Jem-PVT-Prod-04" but then the driver installation failed and it doesn't show up in the device manager even with an exclamation mark.
Using different adb tools (Minimal adb and fastboot, kindle adb drivers, and android sdk) yields no response from the device even with a factory cable (which I purchased and arrived this morning). Fastboot just says < waiting for device > after the command "fastboot -i 0x1949 getvar product"
Adb kill-server followed by adb devices leads to a blank list of devices. (I also went into user/.android/ to change the adb_usb.ini file to 0x1949 (which it already was)
I tried KFHD SRT v2.1 http://forum.xda-developers.com/showthread.php?t=2011126 but it can't see the device either.
At this point, I don't know what can be done and am open to trying everything.
Click to expand...
Click to collapse
Just to confirm that you're doing it correctly...have you powered the device completely down, entered 'fastboot -i 0x1949 getvar product', and then turned the device on? And still no luck?
BTW, the factory cable will not work with the KFHD8.9 and can possibly damage it. Don't use it.

soupmagnet said:
Just to confirm that you're doing it correctly...have you powered the device completely down, entered 'fastboot -i 0x1949 getvar product', and then turned the device on? And still no luck?
BTW, the factory cable will not work with the KFHD8.9 and can possibly damage it. Don't use it.
Click to expand...
Click to collapse
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.

chickeninferno said:
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.
Click to expand...
Click to collapse
I've run into relatively the same problem with my HD8.9 several times while testing scripts but I've always been able to enable fastboot after rebooting using 'getvar product'. The difference in my case, is that I was always using Linux. You may want to set up a LiveUSB and install the SoupKit from the Dev section and try again to see if it makes a difference. SoupKit is not required, of course, but it is definitely recommended if you're not very familiar with Linux.

chickeninferno said:
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.
Click to expand...
Click to collapse
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD

Brandonrz said:
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
Click to expand...
Click to collapse
Brandonrz,
It does not show up in the Device manager when off, when I send fastboot commands, or when on. It will however show up as Jem-PVT-Prod-04 for ~1 second if I have device manager open and I turn on the kindle (regardless of whether or not a fastboot command was sent).
@soupmagnet,
my flashdrive was dead so I just picked up a new one. Putting linux on it now.

chickeninferno said:
Brandonrz,
It does not show up in the Device manager when off, when I send fastboot commands, or when on. It will however show up as Jem-PVT-Prod-04 for ~1 second if I have device manager open and I turn on the kindle (regardless of whether or not a fastboot command was sent).
@soupmagnet,
my flashdrive was dead so I just picked up a new one. Putting linux on it now.
Click to expand...
Click to collapse
For those who may be in same situation here is what I did.
Go to device manager. For that second, try to Right click on Jem-PVT-08 and choose update driver software, then browse my computer for driver software, then let me pick from a list of device drivers on my computer. I moved down list and picked Kindle and it installed as adb composite interface or something like that. Once installed the device manager showed "Kindle" and my fastboot was working. I've had the issue before. I hope this helped!

Glorious Success!
So I ended up doing a combination of the two solutions and since I know how frustrating this was here's how I did it just in case someone stumbles upon this.
How it magically worked:
1.) Inside of Linux Mint, I installed Soupkit
2.) In terminal i typed "fastboot -i 0x1949 getvar product"
-----The kindle reacted for the first time in a long time and went into fasboot mode. Since I had no idea where to put the boot.img or recovery.img in linux to send them but the fastboot or adb commands, I decided to risk it and move to windows.
3.) I unplugged the kindle
4.) Booted into Win 7 x64
5.) The fastboot wasn't working in windows but I checked device manager and the exclamation mark was lingering. I manually picked the driver of amazon.com/kindle and it installed the adb composite device. Fastboot now works in windows.
5.) ran SR Tool.bat in the KFHD_SRT_2.1 folder and chose option 1 (Enable Fastboot)
-----Success
6.)in SR Tool i chose option 4 (erase cache and userdata)
----Took ~4 minutes but success
7.) in cmd I navigated to my sdk platform tools folder by typing "cd C:\Users\<username>\Desktop\SDK\adt-bundle-windows-x86_64-20130522\sdk\platform-tools"
8.) I downloaded the boot.img and recovery.img linked here (http://forum.xda-developers.com/showthread.php?t=2011126) and placed them into C:\Users\<username>\Desktop\SDK\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\
9.) in the cmd from step 7 I sent the following commands "fastboot -i 0x1949 flash boot boot.img" and "fastboot -i 0x1949 flash recovery recovery.img"
----Great Success
10.) In SR Tool I chose option 6 (reboot normally)
-----It looped for ~2 minutes but eventually booted like normal but the SR_Tool asked me to make sure that adb was enabled before clicking enter. I enabled it on the device but SR Tool still didn't seem to see that I had done it. Since it rebooted normally, I didn't really care.
11.) The kindle upgraded itself after I set it down to type this response to 8.4.3
I probably could have easily done this is linux, but I didn't know where to put the boot.img and recovery.img. Also, I'm guessing that the system.img is put back on the device when I used the KFHD SRT but I'm not sure.
Now I'm going for round two to get CM 10.1 put on this thing!
Thanks for all of the help. I really thought that I had actually managed to brick the nearly unbrickable kindle fire 8.9"

Congrats on your success and thanks for sharing the experience!
I think one problem with Windows is that, "fastboot -i 0x1949 getvar product" does not work very well on putting the kindle to fastboot if the device driver is not properly installed, kindle will simply bypass the fastboot step and continue(and hang), the whole situation is a dead loop on Windows if the fastboot driver is having problem and the kindle can't boot into the ROM, and to make things even worse, there is no factory cable for HD8.9
So the SoupKit is a real life saver here.

I had the same sort of driver problem after I installed the second bootloader. For me the simple fix was to go into device manager (In Windows 7), uninstall whatever driver was there with the yellow triangle and then reinstall the official kindle adb driver. Congrats on getting it fixed though. It's a great feeling, I know.

Worked form me too!
Brandonrz said:
For those who may be in same situation here is what I did.
Go to device manager. For that second, try to Right click on Jem-PVT-08 and choose update driver software, then browse my computer for driver software, then let me pick from a list of device drivers on my computer. I moved down list and picked Kindle and it installed as adb composite interface or something like that. Once installed the device manager showed "Kindle" and my fastboot was working. I've had the issue before. I hope this helped!
Click to expand...
Click to collapse
Thanks much for your pointer. In my case the Kindle showed up as an "Other devices" and I was able to use "browse my computer ..."->"let me pick from a list"->Kindle fire->ADB(ver 1.3).
You are awesome.

DBMmn said:
Thanks much for your pointer. In my case the Kindle showed up as an "Other devices" and I was able to use "browse my computer ..."->"let me pick from a list"->Kindle fire->ADB(ver 1.3).
You are awesome.
Click to expand...
Click to collapse
I'm so glad I could help, it was so frustrating for me.

Brandonrz said:
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
Click to expand...
Click to collapse
Im stuck RIGHT here. manually entered fastboot, with the device showing as JEM-PVT-Prod 4. Unable to re-install recovery because <waiting on device>. Please help.

Tyler9097 said:
Im stuck RIGHT here. manually entered fastboot, with the device showing as JEM-PVT-Prod 4. Unable to re-install recovery because <waiting on device>. Please help.
Click to expand...
Click to collapse
Try kingo root or towel root. I believe they might be easier.
Sent from my Nexus 6P using Tapatalk

Brandonrz said:
Try kingo root or towel root. I believe they might be easier.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Turned out it was a driver compatibility issue with Windows 10. It doesn't recognize the Kindle HD 8.9 properly. Moved it over to a Windows 7 machine and it was working, up until i attempted to flash a new recovery and boot .img . Now it's stuck on the red Kindle logo and computer won't pick up the USB. Halp!

Tyler9097 said:
Turned out it was a driver compatibility issue with Windows 10. It doesn't recognize the Kindle HD 8.9 properly. Moved it over to a Windows 7 machine and it was working, up until i attempted to flash a new recovery and boot .img . Now it's stuck on the red Kindle logo and computer won't pick up the USB. Halp!
Click to expand...
Click to collapse
Power off the Kindle, type fastboot -i 0x1949 getvar product , plug in the Kindle when you get <waiting for device>, and flash the 2nd bootloader, recovery, and freedom-boot images as directed in Hashcode's thread. Skip to step 5 after downloading the files, as we're already in fastboot mode at this point.
Also, Windows 10 enforces driver signatures, so you'll need to disable that before proceeding with the Kindle driver installation.
Sent from my Amazon Jem using XDA Labs

[Q] Kindle Fire Stuck at Boot Logo

I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.

kindlestuck said:
I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.
Click to expand...
Click to collapse
[HOW-TO] Before asking for troubleshooting help...
Frequently Asked Questions - Amazon Kindle Fire
[GUIDE] Kindle Fire For Beginners
[HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)

He has all of the drivers installed, but KFU seems to have an issue with file paths. I have redownloaded it for him and I also updated his copy of the SDK with Kindle Fire drivers and a newer ADB. The KFU returns an error "System cannot find the path specified for everything, even though it is extracted straight out of the zip it came in. All he did was choose install TWRP and it didn't even make it to fastboot mode before it bricked.

Zeklandia said:
He has all of the drivers installed, but KFU seems to have an issue with file paths. I have redownloaded it for him and I also updated his copy of the SDK with Kindle Fire drivers and a newer ADB. The KFU returns an error "System cannot find the path specified for everything, even though it is extracted straight out of the zip it came in. All he did was choose install TWRP and it didn't even make it to fastboot mode before it bricked.
Click to expand...
Click to collapse
Thank you for your insight, but all the information needed to fix what is a very common problem can be found in the threads to which links have been provided. The device IS in fastboot. Simply changing the bootmode is the key to resolving the problem. That being said, the KFU is not the end all/be all to changing the bootmode or installing TWRP.

soupmagnet said:
Thank you for your insight, but all the information needed to fix what is a very common problem can be found in the threads to which links have been provided. The device IS in fastboot. Simply changing the bootmode is the key to resolving the problem. That being said, the KFU is not the end all/be all to changing the bootmode or installing TWRP.
Click to expand...
Click to collapse
It is not in fact in fastboot, it is not even listed in adb devices or fastboot devices.
---------- Post added at 12:52 PM ---------- Previous post was at 12:29 PM ----------
I have a feeling it is trying to boot into stock recovery, as KFU was trying to reboot into TWRP (which never installed because KFU was broken).
---------- Post added at 12:55 PM ---------- Previous post was at 12:52 PM ----------
If we can get out of stock recovery, that would be useful. Do you have any idea how to bring up the menu in stock recovery? Does he need to hold the power button down or press it in a pattern?

Zeklandia said:
It is not in fact in fastboot, it is not even listed in adb devices or fastboot devices.
Click to expand...
Click to collapse
While some who know me better may be prepared to see me respond in my usual manner at this point, I have instead, decided to play nice
I have been a member of this forum for quite some time and have seen hundreds of different problems in just as many scenarios for each, and I can assure you, without even a shred of doubt, that the device is in fact in fastboot mode (unless, of course, the information provided in the OP is inaccurate).
You can find information for properly identifying fastboot mode in the "Frequently Asked Questions" thread and the "Fastboot Guide" linked to within it, so please feel free to prove me wrong.
With that,
Just because the device itself doesn't respond to fastboot commands from the computer, doesn't mean the device isn't in fastboot mode. It simply means (in this case) that the drivers are not properly installed or configured, despite the steps taken to do so. Windows is very tricky when it comes to installing drivers for Android and there are hundreds of posts within these forums that should be able to convince you of that. If you want to eliminate all doubt and ensure that driver problems aren't just compounding the issue, set up a Linux LiveUSB and either install SoupKit, or configure it manually to communicate with the device via USB so that adb and fastboot commands will work properly.
Good luck

I appreciate you trying to help, but his device is 100% stock. KFU has set it to boot into recovery, and it will continue to boot into the stock recovery until we can find a way to change that idme bootmode. Tomorrow, I will attempt to use my factory cable on it, but for now all fastboot does is wait for device. I use Linux, so if it truly is in fastboot mode, then it should have no problem, especially with the factory cable.

Zeklandia said:
I appreciate you trying to help, but his device is 100% stock. KFU has set it to boot into recovery, and it will continue to boot into the stock recovery until we can find a way to change that idme bootmode. Tomorrow, I will attempt to use my factory cable on it, but for now all fastboot does is wait for device. I use Linux, so if it truly is in fastboot mode, then it should have no problem, especially with the factory cable.
Sent from my Battle Droid
Click to expand...
Click to collapse
Looking at your signature, I see that you are technically competent enough to take a look at the KFU 'run.bat' and see how it works. When the option to install TWRP is selected, the script uses Pokey9000's 'fbmode' to boot into fastboot mode. Once KFU is able to detect the device in fastboot, it then uses fastboot commands to flash TWRP to the recovery partition and then reboot to recovery. If the KFU were able to detect the device in fastboot mode and TWRP was not installed due to file paths, then the device would still boot into the stock recovery, normally, and you would see plenty of error messages giving you a clue as to what went wrong. Messages in the KFU window compared to those found in the script itself can also show you where things went wrong.
What happens (more times than I care to try and estimate) is, due to the way Windows handles Android drivers, when the device is put into fastboot mode (even though adb commands were working at the time), the fastboot drivers aren't working properly, the script cannot move forward and the device gets stuck in fastboot mode.
As I mentioned earlier, the "Fastboot Guide" linked to in the FAQ, tells you how to recognize fastboot mode beyond all uncertainty. With all due respect, I'd suggest you look into it before deciding that you know best in this particular situation.
And not to make assumptions about your level of proficiency with Linux, but don't forget that you have to either set up udev rules for the device, or run your fastboot commands as root for it to work properly.

same issue...
yes perhaps you should be a little more sympathic to the OP as 1. he probably has a valid issue (im having the same problem...neither windows nor Soupkit is recognizing my KF thats stuck in the white and orange logo fastboot and 2. none of the above links help this problem in any manner. I have been researching this issue for days now and have tried a few different distros (just my luck Mint's persistance didnt work...sigh) and no matter what, my computer will not communicate with the KF.
it seems my KF is now bricked because I ran the KFU and selected install "FireFireFire" before rooting...it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem.
if you have any other suggestions it sure would be appreciated...thanks.

menriquez said:
yes perhaps you should be a little more sympathic to the OP as 1. he probably has a valid issue (im having the same problem...neither windows nor Soupkit is recognizing my KF thats stuck in the white and orange logo fastboot and 2. none of the above links help this problem in any manner. I have been researching this issue for days now and have tried a few different distros (just my luck Mint's persistance didnt work...sigh) and no matter what, my computer will not communicate with the KF.
it seems my KF is now bricked because I ran the KFU and selected install "FireFireFire" before rooting...it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem.
if you have any other suggestions it sure would be appreciated...thanks.
Click to expand...
Click to collapse
Make no mistake about it...I am sympathetic to every single person who "bricks" their device. However, I find it very hard to be sympathetic to those who fail to take personal responsibility for a problem they created due to not having done the appropriate amount of research before getting involved in something they didn't understand.
First off, your device does not have to be rooted to install FireFireFire. As a matter of fact, it's better that you install FireFireFire before trying to root...but your drivers have to be in working order from the start. And you have absolutely NO RIGHT to push blame on someone else just because you don't have the knowledge necessary to modify your device without tools made by other people. It is your device and your responsibility...so own up to it.
Second, I can say beyond all uncertainty that the information needed to understand and resolve yours and 90% of all other situations in this forum, can be found in those 4 links posted earlier. But since no one seems to want to believe that, I guess I'll just have to prove it to you.
1) Being stuck at the Kindle Fire logo means your device is in one of two states; in fastboot mode, or in normal mode but without a working system to boot to. This is explained in both the Frequently Asked Questions thread and the Fastboot Guide thread linked to within it. FAQ #16, Fastboot Guide
2) Also explained in the threads mentioned previously, is information on determining what state the device is in by paying attention to the behavior of the Kindle Fire logo as the device starts up. If the Kindle Fire is displayed brightly and stays brightly lit indefinitely, the device is in fastboot mode. If the Kindle Fire logo is brightly lit for a few seconds then flashes and/or goes dim, then it is trying to boot normally to a non-working system. With that knowledge, you can easily determine your next course of action...also based on the information found in the links provided. FAQ #16, Fastboot Guide
3) The key to fixing 99% of all Kindle Fire problems is getting access to custom recovery. There are two ways to access custom recovery when your device is malfunctioning, through FireFireFire, or through fastboot. If you don't have FireFireFire installed, the only option you have left is fastboot. If the device is trying to boot normally to a non-working system, then your only option for accessing fastboot is with a factory cable. FAQ #16, 17, 26, 29, 32, 33, Fastboot Guide
4) If your device is already in fastboot mode, and you are unable to change your bootmodes with the command line in Windows, it is because your drivers aren't properly installed. There is no other possible scenario. FAQ #14, KFFB - post #3
5) If you are using Windows, and you are unable to fix your drivers despite the wealth of information available to you for getting the drivers to work properly, then you use use Linux. FAQ #15
Your situation is no different. If I were to make an educated guess, I would say device is stuck in fastboot mode because your drivers weren't working properly...and you only have Microsoft to blame for that. As for Linux, it will not communicate your device using ADB or fastboot automatically. You have to either run the commands as the root user, or set up udev rules for your device. If you used the SoupKit to set up your udev rules using a LiveUSB, you have to have working persistence. The way it's configured now is to reboot in order for the udev rules to be loaded. If you don't have working persistence, everything you did prior to the reboot will be lost (This is also explained to you in the SoupKit thread).
With that being said, you have NO RIGHT to get offended if I would rather post a few links and expect the user to do the appropriate amount of research on their own to fix a problem THEY CREATED, than spend my personal time to tell every single user that comes to this forum with the exact same problems, everything that I have told you just now.
I wish you the best of luck in getting your device fixed, and I have no qualms about providing you support for the things in the aforementioned threads that you don't understand. But I WILL NOT hold your hand and tell you every single little thing that you need to know in order for you to fix your own device.

soupmagnet said:
Make no mistake about it...I am sympathetic to every single person who "bricks" their device. However, I find it very hard to be sympathetic to those who fail to take personal responsibility for a problem they created due to not having done the appropriate amount of research before getting involved in something they didn't understand.
First off, your device does not have to be rooted to install FireFireFire. As a matter of fact, it's better that you install FireFireFire before trying to root...but your drivers have to be in working order from the start. And you have absolutely NO RIGHT to push blame on someone else just because you don't have the knowledge necessary to modify your device without tools made by other people. It is your device and your responsibility...so own up to it.
Click to expand...
Click to collapse
wow...sigh...listen the last thing my post tried to do is shift blame...i CLEARLY stated *I* made a BIG MISTAKE didn't I?? i dont need a flame war here sheesh im just trying to fix this ****ty kindle for a buddy.
Second, I can say beyond all uncertainty that the information needed to understand and resolve yours and 90% of all other situations in this forum, can be found in those 4 links posted earlier. But since no one seems to want to believe that, I guess I'll just have to prove it to you.
1) Being stuck at the Kindle Fire logo means your device is in one of two states; in fastboot mode, or in normal mode but without a working system to boot to. This is explained in both the Frequently Asked Questions thread and the Fastboot Guide thread linked to within it.
2) Also explained in the threads mentioned previously, is information on determining what state the device is in by paying attention to the behavior of the Kindle Fire logo as the device starts up. If the Kindle Fire is displayed brightly and stays brightly lit indefinitely, the device is in fastboot mode. If the Kindle Fire logo is brightly lit for a few seconds then flashes and/or goes dim, then it is trying to boot normally to a non-working system. With that knowledge, you can easily determine your next course of action...also based on the information found in the links provided.
3) The key to fixing 99% of all Kindle Fire problems is getting access to custom recovery. There are two ways to access custom recovery when your device is malfunctioning, through FireFireFire, or through fastboot. If you don't have FireFireFire installed, the only option you have left is fastboot. If the device is trying to boot normally to a non-working system, then your only option for accessing fastboot is with a factory cable.
4) If your device is already in fastboot mode, and you are unable to change your bootmodes with the command line, it is because your drivers aren't properly installed. There is no other possible scenario.
5) If you are using Windows, and you are unable to fix your drivers despite the wealth of information available to you for getting the drivers to work properly, then you use Linux.
Click to expand...
Click to collapse
lol i read and did ALL of that my chippy friend...the logo starts and stays bright so im sure im in fastboot mode. i got the latest ubuntu on a pen, like i said after i tried Mint 15 and discovered that persistence on a pen doesn't work well with that distro currently. ubuntu did, and in fact recognizes all my other android devices no problem...but nothing at all when i plug the kindle
Your situation is no different. If I were to make an educated guess, I would say device is stuck in fastboot mode because your drivers weren't working properly...and you only have Microsoft to blame for that. As for Linux, it will not communicate your device using ADB or fastboot automatically. You have to either run the commands as the root user, or set up udev rules for your device. If you used the SoupKit to set up your udev rules using a LiveUSB, you have to have working persistence. The way it's configured now, is to reboot in order for the udev rules to be loaded. If you don't have working persistence, everything you did prior to the reboot will be lost (This is also explained to you in the SoupKit thread).
Click to expand...
Click to collapse
like i said both in my original post and above, i figured out the persistence issue its working now. the reboot loaded the rules but when the script runs im getting two errors which, due to my deep frustration at the time i didn't write down the exact wording. i figured i'd chill for a while and then try again later.
With that being said, you have NO RIGHT to get offended if I would rather post a few links and expect the user to do the appropriate amount of research on their own to fix a problem THEY CREATED, than spend my personal time to tell every single user that comes to this forum with the exact same problems, everything that I have told you just now.
I wish you the best of luck in getting your device fixed, and I have no qualms about providing you support for the things in the aforementioned threads that you don't understand. But I WILL NOT hold your hand and tell you every single little thing that you need to know in order for you to fix your own device.
Click to expand...
Click to collapse
hey i totally appreciate your help and your wish of luck lord knows ill take anything right now this stupid "project" has caused me more grief then i could have ever imagined it could. btw, i didnt get "offended" i just thought maybe you were being kinda hard on the OP due to my experience dealing with the exact same issues he posted he was dealing with...
...believe it or not not everyone who doesn't have the same experiences with this stuff as you do aren't necessary idiots or unskilled at using complex systems. thanks again for your continued help and do have a great day!

menriquez said:
wow...sigh...listen the last thing my post tried to do is shift blame...i CLEARLY stated *I* made a BIG MISTAKE didn't I?? i dont need a flame war here sheesh im just trying to fix this ****ty kindle for a buddy....!
Click to expand...
Click to collapse
The last thing I want to do is to get into a flame war with anyone, but when someone comes to the forum and says something like...
it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem
Click to expand...
Click to collapse
...which, by the way, is entirely based on misinformation...it is very easy for someone to assume the author is, whether directly or indirectly, speaking poorly about a developer's work and assigning blame by presuming that the mistake would not have been made if the tool in question had been made differently. Based on the limited information from your original post, one can only assume that your situation is no different from the hundreds of other users with the same exact problem that also swore the information available did not pertain to their situation and that they were somehow unique, only to find out 50 posts later that it was not the case.
But rather than letting this discussion escalate any further, lets try a different approach. I will give you the benefit of the doubt and entertain the thought that your situation is in fact unique and that there is possibly some other solution for your problem. But, in order for me to do that, I'm going to need some information...very detailed information.
From what I gather so far, based on the information you've provided in your second post is...
1) Your device is in fastboot, confirmed by the fact that the Kindle Fire logo stays brightly lit.
2) You are currently using a LiveUSB with Ubuntu installed and working persistence.
3) When you ran the SoupKit install script, you received errors of some sort, but don't you remember what they were.
4) You are unable to send any fastboot commands at all.
The things I would like to know are...
1) What version of Ubuntu are you running?
2) What brand of pendrive are you using?
3) What is the exact error you received when trying to install the SoupKit?
4) With your device connected, enter the following commands (in Linux) and post the results:
Code:
lsusb -vd 1949: | grep 'bcdDevice'
Code:
cat ~/.android/adb_usb.ini
Code:
sudo cat /etc/udev/rules.d/51-android.rules

soupmagnet said:
...
But rather than letting this discussion escalate any further, lets try a different approach. I will give you the benefit of the doubt and entertain the thought that your situation is in fact unique and that there is possibly some other solution for your problem. But, in order for me to do that, I'm going to need some information...very detailed information.
From what I gather so far, based on the information you've provided in your second post is...
1) Your device is in fastboot, confirmed by the fact that the Kindle Fire logo stays brightly lit.
2) You are currently using a LiveUSB with Ubuntu installed and working persistence.
3) When you ran the SoupKit install script, you received errors of some sort, but don't you remember what they were.
4) You are unable to send any fastboot commands at all.
The things I would like to know are...
1) What version of Ubuntu are you running?
2) What brand of pendrive are you using?
3) What is the exact error you received when trying to install the SoupKit?
4) With your device connected, enter the following commands (in Linux) and post the results:
Code:
lsusb -vd 1949: | grep 'bcdDevice'
Code:
cat ~/.android/adb_usb.ini
Code:
sudo cat /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
firstly i'm very appreciative of your decision to get this back on a positive track and even more thankful that you are still trying to help...
1. ubuntu 13.04 32-bit
2 16gb sandisk with 1024m persistance
3. i reinstalled everything and double checked it...i am no longer getting any errors running soupkit it just says "device offline"
4 lsusb -vd 1949: | grep 'bcdDevice' - nothing just the prompt
5. cat ~/.android/adb_usb.ini - 0x1949
6 . sudo cat /etc/udev/rules.d/51-android.rules -
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
well thats it...i plug my nexus 7 and GS3 and even an ultra cheapo zte warp sequent and it connects right up to all of those...

menriquez said:
firstly i'm very appreciative of your decision to get this back on a positive track and even more thankful that you are still trying to help...
1. ubuntu 13.04 32-bit
2 16gb sandisk with 1024m persistance
3. i reinstalled everything and double checked it...i am no longer getting any errors running soupkit it just says "device offline"
4 lsusb -vd 1949: | grep 'bcdDevice' - nothing just the prompt
5. cat ~/.android/adb_usb.ini - 0x1949
6 . sudo cat /etc/udev/rules.d/51-android.rules -
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
well thats it...i plug my nexus 7 and GS3 and even an ultra cheapo zte warp sequent and it connects right up to all of those...
Click to expand...
Click to collapse
Oh........this again....
For reasons I have yet to figure out, there are rare (and I do mean rare) situations where Linux just will not detect the device whatsoever. When you enter the 'lsusb' command, whether the udev rules are configured properly or not, Linux should still detect your device when plugged into the USB. I can probably count on one hand the number of times I've seen this happen, and I've never been able to recreate the problem on my own.
It could be caused by using the wrong USB port (i.e. USB3.0 instead of USB2.0), it could be caused by the USB pendrive itself, you could have a faulty cable, it may even be the Linux install itself, but those are just wild guesses because I have really don't know. My best estimate is that there is a bug in the stock bootloader that sometimes causes it to malfunction when put into fastboot because (in the few instances I've seen), users that were able to resolve their situation did so by using usbboot to install a custom bootloader. This of course requires opening the device and performing the "shorting trick" to drop the device into usbboot mode.
If I were you, considering you probably haven't attempted to usbboot before, you should try a different USB port, a different USB cable, and a different pendrive to see if you have any luck. Otherwise, you may have no other choice but to usbboot.
The unfortunate thing usbbooting is, it's just one of those things you have to somehow figure out on your own, even with the instructions given in the Firekit/usbboot thread (it's really about technique more than anything else). I've done it several times myself, mostly for testing and various other reasons, but the first time (when I really needed it), took practically forever to get it right.
If you do take the usbboot route, you can launch Firekit from the SoupKit utility script (option #4, I think) and follow the instructions in the Firekit thread. Be very careful opening the device, use a safety pin for creating the short (the reason will become apparent when you get the device opened), and most of all...good luck.
[Edit:] And yes, crow is very tasty

kindlestuck said:
I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.
Click to expand...
Click to collapse
Charge kindle, boot into the frozen logo screen with no animation, plug into computer, and reboot computer, i want to share this with everyone because it worked for my kindle