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.

[Q] Kindle Fire is unknown device

Hi, I'm stuck in twrp bootloop. When I connect my kindle to PC (Win7) sometimes it shows unkown device and sometime nothing happens. I've searched the web for solutions for 4 weeks and nothing helped me. I tried mount USB storage in twrp, nothing happens. I just want my PC (Win7) to recognize my kindle, then I will follow the instructions from other threads.
*I have a factory cable.
**If you need more information,tell me.

What do you mean by twrp bootloop? Does it keep booting into TWRP over and over?
You're most likely experiencing a driver issue. Try to follow the directions here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2 and see if it helps any. Just having the KF show up on the device manager is a good step forward, even if mounting usb storage isn't working.

Are you stuck in FFF or TWRP? What color is the Logo?
Drivers are the #1 cause of pain for KF owners trying to root. What steps have you taken to install the drivers? Are you using KFU?
You should be reading: if you havent
http://forum.xda-developers.com/showthread.php?t=1552547
More spesifically this post regarding how drivers should look, and what to do if they dont.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

I'm stuck in TWRP. Every time I load the device I get to TWRP.
I've read the threads you provided, nothing helped.
I did ''add legacy hardware'' in device manager, now I got Android composite ABD Interface shown but it has the code 10 error.

Y.Always.Me said:
I'm stuck in TWRP. Every time I load the device I get to TWRP.
I've read the threads you provided, nothing helped.
I did ''add legacy hardware'' in device manager, now I got Android composite ABD Interface shown but it has the code 10 error.
Click to expand...
Click to collapse
Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?
The bootloop is very easy to fix - you're most likely stuck in the Recovery bootmode (5001), so having fastboot or ADB set your bootmode to Normal (4000) will solve it, but first you need to sort out ADB/fastboot, which are showing a drivers problem.
As a side note, this probably happened because you are using an outdated FFF/TWRP. When this is fixed, it's in your best interest to update to the latest version of each (1.4a, 2.1.1 respectively).

Dasanko said:
Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?
The bootloop is very easy to fix - you're most likely stuck in the Recovery bootmode (5001), so having fastboot or ADB set your bootmode to Normal (4000) will solve it, but first you need to sort out ADB/fastboot, which are showing a drivers problem.
As a side note, this probably happened because you are using an outdated FFF/TWRP. When this is fixed, it's in your best interest to update to the latest version of each (1.4a, 2.1.1 respectively).
Click to expand...
Click to collapse
I tried, (Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?), but it didnt help.
I have TWRP 2.0.0.
now I dont even get unkown device. What else can I do?? I just want it to show on my PC.

Y.Always.Me said:
I tried, (Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?), but it didnt help.
I have TWRP 2.0.0.
now I dont even get unkown device. What else can I do?? I just want it to show on my PC.
Click to expand...
Click to collapse
TWRP 2.0 included FFF, so you can use fastboot -
Issue "fastboot getvar product" and then plug in the KF, see if the fastboot driver is working. Otherwise, you're stuck on a driver problem again.
If it does list one device, then you can go with "fastboot oem idme bootmode 4000" and then "fastboot reboot". That should get you back on Normal bootmode and out of the TWRP bootloop.
Next would be updating both TWRP and FFF to prevent this from happening again, but there's the pending driver issue. I can't really add much more, other than carefully going through the post linked earlier, step by step.

Dasanko said:
TWRP 2.0 included FFF, so you can use fastboot -
Issue "fastboot getvar product" and then plug in the KF, see if the fastboot driver is working. Otherwise, you're stuck on a driver problem again.
If it does list one device, then you can go with "fastboot oem idme bootmode 4000" and then "fastboot reboot". That should get you back on Normal bootmode and out of the TWRP bootloop.
Next would be updating both TWRP and FFF to prevent this from happening again, but there's the pending driver issue. I can't really add much more, other than carefully going through the post linked earlier, step by step.
Click to expand...
Click to collapse
when I issue "fastboot getvar product" I get('fastboot' is not recognized as an internal or external command, operable program or batch file.)

Y.Always.Me said:
when I issue "fastboot getvar product" I get('fastboot' is not recognized as an internal or external command, operable program or batch file.)
Click to expand...
Click to collapse
Download KFU and then open a command prompt in the "tools" directory.

Idid, it says <waiting for devive>
I pluged KF, nothing happened.
then I restarted it and nothing happened.
I gess I'm stuck for good.

Y.Always.Me said:
Idid, it says <waiting for devive>
I pluged KF, nothing happened.
then I restarted it and nothing happened.
I gess I'm stuck for good.
Click to expand...
Click to collapse
Means you have a driver problem, which takes us back to the starting point. Can't do anything else until you manage to get the drivers installed properly, sorry. Alternatively, you can, on a different computer, download KFU and then run install_drivers.bat BEFORE you plug in the KF for the first time.

Dasanko said:
Means you have a driver problem, which takes us back to the starting point. Can't do anything else until you manage to get the drivers installed properly, sorry. Alternatively, you can, on a different computer, download KFU and then run install_drivers.bat BEFORE you plug in the KF for the first time.
Click to expand...
Click to collapse
I tried nothing happened.

If you are doing flashes and nothing is working go to mount and make sure there are no checks in the boxes for system and data if so remove them then reflash or restore a backup after restore or reflashing a rom go back and check to make sure those boxes still have no check inside them then reboot I have had frequent errors like this when flashing roms that have the gapp package prebaked into the rom I do not have this issue when flashing gapps seperately

I found that from 20% - 80% battery it takes 12 hours

[Q] Really need help!! :'(

Hello! I get myself in a huge mess! and now I dont know what to do, I've been looking for a lot of solutions here but I cant fix my Kindle Fire...
I tried to rooted it but it didnt work and now it my pc says that the Device is not recognize, and the screen just show the Kindle Fire Logo...
It's been like that for a while... I'm ok with just the normal Kindle, without the rooting stuff v.v just need to make it work! please heeeelp

Help us help you...
What exactly did you do? (not just "tried to root and it didn't work") Did you install TWRP or FFF?
I don't see why your computer would say the device isn't recognized, when it shouldn't even show it at all (as it's stuck booting).

Sounds like your stuck in fast boot or something got erased or changed from the stock system.
Happened to me more than I care to admitted early on.
Try the app here: http://forum.xda-developers.com/showthread.php?t=1399889
It'll should be easier than using terminal. I haven't personally tried it.
It you have fastboot working > fastboot -i 0x1949 bootmode 4000 then fastboot reboot might get you on track quickly. If using Linux you need to be su, not sure if windows cmd needs administrative rights.
Good luck and report back.

Ok, the thing is that I unplug the Kindle probably before I should, I'm not quite sure :S! But the computer dont recognize the Kindle, though it does recognize it as ADB Android Phone sometimes...
I tried to install the driver manually but it didnt work, when I run the Utility is still offline... and I cant see the Kindle in "my PC" either...
I tried ti the thing with the Device manager, but it doesnt show anywhere the Kindle devices... so I'm pretty sure I'm doing something wrong! but the thing is I dont Have any Idea :'(
>.<!

Have a read here: http://forum.xda-developers.com/showthread.php?t=1552547
Fix the drivers as instructed in that thread (second post), and then post here your precise issue (or whatever it is you'd like to achieve), as detailed as possible.
For future reference: http://forum.xda-developers.com/showthread.php?t=1644970

[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] Team Black Hat Adapter

My son is trying to get his kindle fire back up and running. With not much success. He was reinstalling the software and must have wiped the device clean as now he cannot get back into recovery mode. When installing FFFF it says that there is no exec directory. He ordered a factory cable adapter from black hat under the impression that this would force the device into fastboot thus recovery. When he attached the adapter all that happened was that it went back to the kindle fire logo and is now showing offline status unknown. Before at least it was showing online. Are we mistaken that it should go to recovery (blue and white) kindle logo. We are a little tired of messing with it and are thinking of calling it quits. Any suggestions would be much appreciated. We have turned off and on, installed drivers, and switched cables to no avail.

jwhite0514 said:
My son is trying to get his kindle fire back up and running. With not much success. He was reinstalling the software and must have wiped the device clean as now he cannot get back into recovery mode. When installing FFFF it says that there is no exec directory. He ordered a factory cable adapter from black hat under the impression that this would force the device into fastboot thus recovery. When he attached the adapter all that happened was that it went back to the kindle fire logo and is now showing offline status unknown. Before at least it was showing online. Are we mistaken that it should go to recovery (blue and white) kindle logo. We are a little tired of messing with it and are thinking of calling it quits. Any suggestions would be much appreciated. We have turned off and on, installed drivers, and switched cables to no avail.
Click to expand...
Click to collapse
You almost got it right. The error you received means the shell is no longer accessible and therefore unable to send necessary shell commands, like those used to change bootmodes. In order to fix the problem, a factory cable is needed to access fastboot, which gives you an alternative method of changing bootmodes (to access recovery) or flashing partition images (i.e. installing recovery) by use of fastboot commands. But the factory cable does not actually boot the device into recovery on it's own though.
Here's where it get's a little tricky though. Unless you know what to look for, it's difficult to know whether the device is actually in fastboot because the only thing that will be displayed on the screen is the Kindle Fire logo. You'll know if the device is in fastboot because the Kindle Fire logo will stay brightly lit, indefinitely. If the Kindle Fire logo flashes and/or gets slightly dimmed, then you'll know the factory cable you have is defective. With that being said, however, just because the device boots into fastboot mode, doesn't necessarily mean the computer will communicate with it. For that, you need working drivers.
Long story, short...you need to confirm whether the device is actually in fastboot before you can go any further.

Thanks for the reply. I looked at the logo this morning and it came up brightly lit with no change so I am assuming it is in fastboot mode. That being said the device, in device manager it comes up as unknown usb device. Before it would come up as kindle and I would install the drivers and it would come up as an android phone adb composite. I went into device manager and tried to update the driver manually and windows tells me that the correct driver is being used for this device. I did unplug the adapter and go back with a regular data cable and that made no difference. Do you need to force it to use a different driver. I am trying to use the drivers that came with the KFU I downloaded.
soupmagnet said:
You almost got it right. The error you received means the shell is no longer accessible and therefore unable to send necessary shell commands, like those used to change bootmodes. In order to fix the problem, a factory cable is needed to access fastboot, which gives you an alternative method of changing bootmodes (to access recovery) or flashing partition images (i.e. installing recovery) by use of fastboot commands. But the factory cable does not actually boot the device into recovery on it's own though.
Here's where it get's a little tricky though. Unless you know what to look for, it's difficult to know whether the device is actually in fastboot because the only thing that will be displayed on the screen is the Kindle Fire logo. You'll know if the device is in fastboot because the Kindle Fire logo will stay brightly lit, indefinitely. If the Kindle Fire logo flashes and/or gets slightly dimmed, then you'll know the factory cable you have is defective. With that being said, however, just because the device boots into fastboot mode, doesn't necessarily mean the computer will communicate with it. For that, you need working drivers.
Long story, short...you need to confirm whether the device is actually in fastboot before you can go any further.
Click to expand...
Click to collapse

Kindle drivers are notoriously touchy. Try uninstalling/reinstalling them a couple of times. I predict they will suddenly start working and you can proceed with installing custom recovery/rom.
Sent from my GT-p511x

Thanks for the respone, I have installed and uninstalled to where if I here the computer connect and disconnect one more time I might throw it against the wall. Are there specific steps that I need to take other than ordinary to unintall/install the drivers correctly or maybe drivers that are more sccuessful than others.

Ok, after sifting through a number of threads. I read where adb and fastboot are mutually exclusive and adb will not see a device that is in fastboot mode. Is that correct? And when you install the drivers with KFU does that contain the fastboot drivers? Or should you download SDK platforms tools which contains both? And then run fastboot commands to flash a recovery? If so, is there a good tutorial for someone that does not follow directions well?

jwhite0514 said:
Ok, after sifting through a number of threads. I read where adb and fastboot are mutually exclusive and adb will not see a device that is in fastboot mode. Is that correct? And when you install the drivers with KFU does that contain the fastboot drivers? Or should you download SDK platforms tools which contains both? And then run fastboot commands to flash a recovery? If so, is there a good tutorial for someone that does not follow directions well?
Click to expand...
Click to collapse
Yes, adb and fastboot are mutually exclusive but the same drivers should work for each. You can try the drivers located HERE, or read the topic on understanding driver installation located HERE.
Of you are still unsuccessful in communicating with the device in fastboot while using fastboot commands, you may have to restore it with Firekit using the "shorting trick".

OK, here is an update. I was able to get the device into recovery and TWRP. Not sure what I did differently other than maybe standing on one foot, facing south and staring at the stars, but it worked. When all of this started it was right after my son updated the software to 6.3.2 via wifi, maybe something went wrong. So last night I was able to flash 6.3.1 back to the device and was told that it was done succesfully. Using adb I can see the device in recovery and the shell lsiting is ~ # ←[6n which I guess is good as it said there was no shell before. So now my question is could it possibly be a corrupt bootloader on the device as well as it was hung at the fire logo. If so, do I need to reinstall the stock bootloader and if so where do you find it or does it come with the software flash?

I have succesfully got the update file on the kindle, did all the wipes selected install and now seems to be hung at veryfing filesystem and partitions sizes. Can someone tell me how long a flash should take or is something wrong? Since I have never done this before I have no idea.