Develop Bugs

[SOLVED] Stuck at the KF logo

I seriously need some help. My normally fierce Google-fu has failed me. I have searched countless threads on here (and elsewhere) and tried just as many solutions, but I haven't had any luck. My Kindle Fire is stuck at the "Kindle Fire" boot logo. I was using the KF utility, and ADB status was online, everything looked good. I chose the option to root and install TWRP. However, it couldn't grab TWRP through my corporate firewall/proxy, so it skipped it, placed my KF in fastboot (I think), rebooted, now I'm bricked.
Depending on which PC I use, and in what order it's plugged in, I get different results in the Device Manager (both Windows 7):
Home PC -
Hardware Ids = USB\UNKNOWN
Yes, I've tried loading drivers six ways from Sunday, and none worked.
Absolutely no solution involving ADB in any way will work until I can at least get Windows to recognize it correctly and load the proper drivers.
Work PC -
If I have the KF turned on when I plug it into my PC, I get the same result as on my home PC (though I don't think I tried plugging it in on my home PC while my KF was powered off).
If I have it turned off when I plug it in, my PC sees it as an "Android ADB Interface", with the correct hardware ids.
Even when it sees my KF correctly in Device Manager, I still can't get ADB to communicate with it.
I've tried FireKit on my Ubunutu 12.04 laptop, but it never sees my device, and gets stuck at the <waiting for device> message. I've tried countless driver iterations and many utilities, and none seem able to communicate with it while it's stuck at the logo.
Any help would be immeasurably appreciated!!
[UPDATE]
While my device was detected correctly in Device Manager (but still not able to communicate via ADB), I reloaded the drivers using the KF Utility. It is still detected as "Android ADB Interface" but with an error in Device Manager. The error is "This device cannot start. (Code10)". I uninstalled it, including drivers, and let Windows autodetect. It was identified as "kindle", so I ran the same driver package and it still sees it as "Android ADB Interface", but still with the error.
[UPDATE 2] - Steps I took to (finally) get mine working
Note: If your device is recognized in Device Manager as something *other* than "Unknown Device* (such as "kindle" or "Android ADB Interface"), skip to step 3.
1. Turn off the device.
2. Plug the device into USB to your computer. This should turn the device on.
3. Delete the ".android" folder from your Windows profile. This is very important. If you just uninstall the device and driver, Windows will still use this to reinstall the device. You want to start as fresh as possible to eliminate complications from previous attempts.
4. Uninstall it from Device Manager. Make certain to check the box to uninstall the driver as well.
5. Start a new scan for hardware changes in the Device Manager.
6. As mine was stuck in fastboot mode, it recognized the device as "kindle" (lower-case "k")
7. Run the "install_driver.bat" from the Kindle Fire Utility.
8. After driver install, run the Kindle Fire Utility.
9. ADB status will say "offline", that's fine.
10. Choose option 1 to go into the Bootmode Menu.
11. Choose option 1 to boot into Normal Mode.
12. It will be stuck at <waiting for device>.
13. Turn off the device, keeping it plugged into the PC. *very important* This step was one among others that made THE difference for me.
14. Turn on the device. *Hopefully*, you should immediately see the utility spit out some text and your device should reboot.
15. Boots up!! (well, mine did, and I had almost give up hope were it not for my pride and stubbornness).

Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on device drivers.
"Android ADB Device" typically means the device is in fastboot mode and you cannot use adb while in fastboot mode.... you must use fastboot.
With your KF off and disconnected from your work computer, run this command...
Code:
fastboot -i 0x1949 getvar product
and then connect it to the computer. The KF will turn on automatically. The computer will say "<waiting for device>" for a bit, but if the command works, it will eventually return "product: kindle" as output. If that works, you can actually flash TWRP from there, but if you are anxious for it to do something again...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
should get it booting normally again. If it doesn't, look at the link I gave you and focus on getting your drivers fixed. You won't be able to execute any commands (fastboot or adb) through Windows if the device drivers don't work. You might want to go back to Firekit if drivers remain problematic for you.
Everything you need to know to fix your KF is in that link at the beginning of my post, including the commands you need to run. At the bottom of post #3 is also another link to a how-to root/install ROMs page.

IT LIVES!!! While I was still getting the error code 10, I launched the KF utility one more time. ADB status was still offline. I went into the menu to modify boot mode, told it to boot in normal mode and it was stuck <waiting for device>. On a whim, I left it there and cycled power on my KF. It found the device, finished, rebooted, and it's good!!! The Device Manager is happy now too!!
The behavior was so odd between my work and home PC. I was seriously scared when it gave a bad device ids on my home PC. I think it was more a combination of several different things that helped, and I'll update my main post with all that I did to get it back (that I can remember). Hopefully it will help someone else.
This is an *amazing* community, and I can't thank everyone enough for the incredible work you all do and the true sense of selflessness exhibited here on the forums!
btw, How do I edit the subject to indicate it's solved?

^_^
OH ,MY GOSH I DO NOT NO HOW MUCH TO THANK U THNX FOR THE POST

jaetrix said:
OH ,MY GOSH I DO NOT NO HOW MUCH TO THANK U THNX FOR THE POST
Click to expand...
Click to collapse
Glad it could help someone! I was frustrated enough about it and couldn't find a single solution that fit my issue. I just had to combine some to get it to work for me.

Bump

Yes this saved two bricked kindles. Trial and error is sometimes the best means to solving a problem.
Sent from my GT-I900 using xda premium

This is happening alot here of recent thats why I bumped it to the top of the list

Thank you for this. Maybe a moderator will be kind enough to sticky this.
Sent from my Galaxy Nexus using Tapatalk 2

pugsley42 said:
I seriously need some help. My normally fierce Google-fu has failed me. I have searched countless threads on here (and elsewhere) and tried just as many solutions, but I haven't had any luck. My Kindle Fire is stuck at the "Kindle Fire" boot logo. I was using the KF utility, and ADB status was online, everything looked good. I chose the option to root and install TWRP. However, it couldn't grab TWRP through my corporate firewall/proxy, so it skipped it, placed my KF in fastboot (I think), rebooted, now I'm bricked.
[...]
15. Boots up!! (well, mine did, and I had almost give up hope were it not for my pride and stubbornness).
Click to expand...
Click to collapse
Pugsley42...you 'da man! I had the same story as you told above, including searching and following countless threads of instructions. Nothing worked until I found your instructions! Thank you, thank you, thank you!

Stuck at the KF logo
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely

Neely said:
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely
Click to expand...
Click to collapse
My first suggestion would be to read this:
http://forum.xda-developers.com/showpost.php?p=25884555

Neely said:
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely
Click to expand...
Click to collapse
Agreed, you really need to be more specific. "Waiting for device" .... which part of the KF utility?. What *exactly* are you seeing, where? What does Device Manager show your KF identified as (keep in mind, there is a big difference between seeing it as "Kindle" and "kindle"). What *exactly* did you do that brought you to this point?
Symptoms. Symptoms. Symptoms. The more detail you provide, the more likelihood we can help.
Take heart. If there's anything I learned in my stubborn refusal to admit my KF was fully bricked, is that it can be brought back from a lot worse than we give it credit for. I also learned quite a bit that I never would have if I never failed. That's what I love about breaking things!

pugsley42 said:
Agreed, you really need to be more specific. "Waiting for device" .... which part of the KF utility?. What *exactly* are you seeing, where? What does Device Manager show your KF identified as (keep in mind, there is a big difference between seeing it as "Kindle" and "kindle"). What *exactly* did you do that brought you to this point?
Symptoms. Symptoms. Symptoms. The more detail you provide, the more likelihood we can help.
Take heart. If there's anything I learned in my stubborn refusal to admit my KF was fully bricked, is that it can be brought back from a lot worse than we give it credit for. I also learned quite a bit that I never would have if I never failed. That's what I love about breaking things!
Click to expand...
Click to collapse
Okay, I was attempting to load a ROM on it. It had been rooted already with no issues and then something happened during the installation of TWRP and spit out an error message of unable to load and then rebooted. That's where I am with the kindle fire boot screen.
As for the "Device Manager" It shows up as "Android Composite ADB Device" and with KFU it shows the following status:
ADB Status: Online
Boot Status: Unknown
At this point is when if I try to run Install Latest TWRP Recovery or FFFF or anything it just sits there and says "Waiting For Device"...
I've read though most of these posts and have tried several different suggestions with no luck so far. So I have actually read through here. :-/
Hope this helps at all.

I would try by trying to change the bootmode using the KF utility. If you're stuck at the KF logo on boot, then the other functions of the utility won't do anything. Your KF needs to be in a "usable" state before that can happen. Have you tried changing it to "Fastboot" or "Normal"?

Stuck at the KF logo
pugsley42 said:
I would try by trying to change the bootmode using the KF utility. If you're stuck at the KF logo on boot, then the other functions of the utility won't do anything. Your KF needs to be in a "usable" state before that can happen. Have you tried changing it to "Fastboot" or "Normal"?
Click to expand...
Click to collapse
Yeah, I've tried it using the KF Utility as well as using fastboot at the command line :-/

kinfauns said:
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on device drivers.
"Android ADB Device" typically means the device is in fastboot mode and you cannot use adb while in fastboot mode.... you must use fastboot.
With your KF off and disconnected from your work computer, run this command...
Code:
fastboot -i 0x1949 getvar product
and then connect it to the computer. The KF will turn on automatically. The computer will say "<waiting for device>" for a bit, but if the command works, it will eventually return "product: kindle" as output. If that works, you can actually flash TWRP from there, but if you are anxious for it to do something again...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
should get it booting normally again. If it doesn't, look at the link I gave you and focus on getting your drivers fixed. You won't be able to execute any commands (fastboot or adb) through Windows if the device drivers don't work. You might want to go back to Firekit if drivers remain problematic for you.
Everything you need to know to fix your KF is in that link at the beginning of my post, including the commands you need to run. At the bottom of post #3 is also another link to a how-to root/install ROMs page.
Click to expand...
Click to collapse
Your explanation and guidance cut right to the solution for me. Thank you so much!

Thank you!!
I've been searching forever for this same issue. This has not fixed it completely but has helped me! Thank you for taking the time to post this!!

cmgroden said:
I've been searching forever for this same issue. This has not fixed it completely but has helped me! Thank you for taking the time to post this!!
Click to expand...
Click to collapse
I presume if any of this helped, you were able to get further than you have been. What state is it in now? What error(s) if any?

I seem to be having this same issue but I cannot get my pc to recoginze the kindle fire as anything. perhaps i did something wrong but i was following a video on youtube and though i was doing it exactly as it showed. First thing i did after I finally got the drivers loaded was start KFU and then chose to load TWRP. It started the process but when it hit the part about rebooting my device that's where it stopped. Since then i've been stuck at the white and yellow kindle fire logo. No matter what i do to try to reinstall the ADB drivers I cannot get my computer (win xp) to recognize the kindle. It shows as "unknown device" in device manager and when it's plugged in the little pop up says that the usb device has malfunctioned and windows doesn't recognize it. So am I totally dead? I'm assuming before i can do anything to recover it I need to get windows to recognize it with the ADB drivers.

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.

[Help] Stuck at Yellow Fire Triangle

Coming from the title, my Kindle Fire is currently stuck at the FireFireFire stage. It won't even go to the twrp recovery stage.
I have been an avid follower of the Kindle Fire Forum and flashed the latest stable builds posted on the Development thread from the first Gingerbread CM7 by Sblood86 to twa_priv's recent Jellybean CM10. I just made an account today for this troubleshooting issue.
What I did prior to getting it stuck:
- updated to twa_priv's CM10/SGT7 (his latest which is 10/29/2012) via twrp.
- saw that my twrp was outdated on v2.2.0 and decided to update that as well.
- ran Vashypooh's KFU (his latest which is 5/09/2012) by installing latest twrp recovery option.
- saw that the KFU didn't recognize the kindle, so I exited KFU and installed drivers.
- rebooted my kindle to twrp recovery, windows recognizes kindle as "android device ADB" on device manager, and attempted to install twrp recovery update to v2.2.1.1
- waited for like 30 minutes and was stuck on waiting for device on KFU.
- rebooted the kindle myself and tried to install again
- kindle stuck on FireFireFire
- windows reports "USB device malfunctioned"
- cried :crying:
Help please?

Open kfu, plug your device in select 1 for changing bootmodes select 1 for normal if it hangs at waiting for device, hold the power button down while connected, then power it back on it should then boot normal. There have been minor driver changes that could be making your device unseen by windows use soupkit to fix your recovery or fix your boot mode as well. http://forum.xda-developers.com/showthread.php?t=1850038

Thepooch said:
Open kfu, plug your device in select 1 for changing bootmodes select 1 for normal if it hangs at waiting for device, hold the power button down while connected, then power it back on it should then boot normal. There have been minor driver changes that could be making your device unseen by windows use soupkit to fix your recovery or fix your boot mode as well. http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
So I got linux mint 13 running and the soupkit as described in the link, and the soupkit is saying that the kindle is offline even though it is on and plugged in. I tried to change the bootmode to normal but no dice. Still stuck on FireFireFire.
I looked at the system information app and the kindle fire doesn't even show up on the devices tree.

azndnbdub said:
- windows reports "USB device malfunctioned"
Click to expand...
Click to collapse
This line causes me to believe there is something wrong with the bootloader. I'm starting to think this type of error is caused by the way Windows deals with certain hardware.
What motherboard are you using on your Windows machine? I'd like to see if there is a correlation between yours and the configurations of other users with the same problem.
Also, open a terminal in Linux, with your device plugged in, and enter:
Code:
lsusb
You should see a device listed as "18d1:0100 Google Inc". If not, I'm willing to bet my original assessment is true and Firekit is your next step.

soupmagnet said:
This line causes me to believe there is something wrong with the bootloader. I'm starting to think this type of error is caused by the way Windows deals with certain hardware.
What motherboard are you using on your Windows machine? I'd like to see if there is a correlation between yours and the configurations of other users with the same problem.
Also, open a terminal in Linux, with your device plugged in, and enter:
Code:
lsusb
You should see a device listed as "18d1:0100 Google Inc". If not, I'm willing to bet my original assessment is true and Firekit is your next step.
Click to expand...
Click to collapse
I am using a different machine for the live linux but the windows machine is a 2010 - 2011 HP Pavilion dv6 notebook with the Nehalem based Intel Core i3 M 370 @ 2.4GHz running W7 Pro which I believe when referring to the service manual is an Intel HM55 UMA graphics and shared memory with Intel Core i3-370M processors (at least what they refer the mobo to "system board"). The Terminal windows reports that there is a Google device with "18d1:0100 Google Inc" on it.

azndnbdub said:
I am using a different machine for the live linux but the windows machine is a 2010 - 2011 HP Pavilion dv6 notebook with the Nehalem based Intel Core i3 M 370 @ 2.4GHz running W7 Pro which I believe when referring to the service manual is an Intel HM55 UMA graphics and shared memory with Intel Core i3-370M processors (at least what they refer the mobo to "system board"). The Terminal windows reports that there is a Google device with "18d1:0100 Google Inc" on it.
Click to expand...
Click to collapse
The fact that Linux is detecting your device is a good thing. Is your Linux distro 64 or 32bit?
In the terminal enter:
Code:
fastboot devices
...and see if anything shows up.

soupmagnet said:
The fact that Linux is detecting your device is a good thing. Is your Linux distro 64 or 32bit?
In the terminal enter:
Code:
fastboot devices
...and see if anything shows up.
Click to expand...
Click to collapse
Linux distro is Linux Mint 13 Maya 32bit on LiveUSB. Nothing appears when executing "fastboot devices" on Terminal.

Interesting. I wonder if Mint works differently when it comes to the script defining the udev rules.
enter the following commands in the terminal:
Code:
sudo cat /etc/udev/rules.d/51-android.rules
&
Code:
cat $HOME/.android/adb_usb.ini

When executing "sudo cat /etc/udev/rules.d/51-android.rules" the below is the result.
# 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"
When executing "cat $HOME/.android/adb_usb.ini" the below is the result.
0x1949

azndnbdub said:
When executing "sudo cat /etc/udev/rules.d/51-android.rules" the below is the result.
# 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"
When executing "cat $HOME/.android/adb_usb.ini" the below is the result.
0x1949
Click to expand...
Click to collapse
Strange. There's no obvious reason why it wouldn't work properly. Since it is FireFireFire, albeit an earlier version, are you able to access recovery by holding the power button on startup until it turns orange?

soupmagnet said:
Strange. There's no obvious reason why it wouldn't work properly. Since it is FireFireFire, albeit an earlier version, are you able to access recovery by holding the power button on startup until it turns orange?
Click to expand...
Click to collapse
Nope, even as I am typing this response, the kindle fire is plugged in but is frozen on FireFireFire. Can't even get into the TWRP recovery (if it's still there...)

Here's what I see...
Your Linux system seems to be configured properly to detect your device. The udev rules are set and the adb driver is in place and configured properly as well.
Linux is able to detect your device in fastboot so there must be communication with your device at some level.
The fact that the use of the power button to access recovery is failing, is worrisome. As far as I know, if there is no recovery installed, the device should at least boot to a black screen, the same way the device would boot to a black screen if no OS is installed. This leads me to believe that your bootloader isn't working properly.
But before you go as far as attempting a USBboot with Firekit, I would suggest remaking your LiveUSB and using Ubuntu to see if that makes a difference (SoupKit has only been tested on Ubuntu), although I can't see why that would make a difference. Also, be sure you are using USB2.0, not USB3.0. Afterwards, if there is no change, I would suggest USBboot with the Firekit.
Unfortunately, that's the best option I can come up with based on the information I have, and without having direct access to the device.

So I made the LiveUSB into Ubuntu, ran SoupKit, and still the SoupKit still isn't detecting it although executing the aforementioned command lines does show that Ubuntu sees the kindle fire, not the SoupKit. And the kindle is still stuck in FireFireFire even though I ran the Firekit to execute "usb_boot_twrp" I guess there's no hope for it anymore?

azndnbdub said:
So I made the LiveUSB into Ubuntu, ran SoupKit, and still the SoupKit still isn't detecting it although executing the aforementioned command lines does show that Ubuntu sees the kindle fire, not the SoupKit. And the kindle is still stuck in FireFireFire even though I ran the Firekit to execute "usb_boot_twrp" I guess there's no hope for it anymore?
Click to expand...
Click to collapse
Which "aforementioned commands" are you referring to? Does "fastboot devices" return any positive results? Have you tried issuing the command to change the bootmode to recovery?
Code:
fastboot oem idme bootmode 5001
[edit:] This will help me in determining whether the script is failing or the device itself. On that note, if you get stuck at "waiting for device" after entering the previous command, give the device a hard shutdown and start it up again to see if the command sticks.

Success!
You may find this really awkward, but...THE KINDLE HAS RESTORED NORMAL BOOT (4000) !!! :good:
Somehow when I ran my Ubuntu LiveUSB on my HP notebook and not the other machine and ran SoupKit, I issued the normal bootmode (4000). Right then the kindle flickered and I thought "There is hope after all!" After flickering twice, it displayed a regular triangle and immediately went in to the ROM which was the CM10. I then remembered that I was going to install the latest TWRP (v2.2.2.1 which you included in the soupkit), which installed sucessfully. I tested reboot one more time and FFF doesn't hang and TWRP works.
Thank you soupmagnet for being a helpful developer throughout this troubleshooting and also I can vouch that your SoupKit does work as advertised!

azndnbdub said:
You may find this really awkward, but...THE KINDLE HAS RESTORED NORMAL BOOT (4000) !!! :good:
Somehow when I ran my Ubuntu LiveUSB on my HP notebook and not the other machine and ran SoupKit, I issued the normal bootmode (4000). Right then the kindle flickered and I thought "There is hope after all!" After flickering twice, it displayed a regular triangle and immediately went in to the ROM which was the CM10. I then remembered that I was going to install the latest TWRP (v2.2.2.1 which you included in the soupkit), which installed sucessfully. I tested reboot one more time and FFF doesn't hang and TWRP works.
Thank you soupmagnet for being a helpful developer throughout this troubleshooting and also I can vouch that your SoupKit does work as advertised!
Click to expand...
Click to collapse
Developer? Not even close. But I appreciate the sentiment either way. And I'm glad it worked out for you.

[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 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