Develop Bugs

Kindle Fire is stuck at boot screen, (no animation). Help!

Hello Everyone,
I will try to provide as much details as I can from what I remember.
Basically, I tried to ROOT my device and install TWRP. However, I messed it up the first time. I tinkered with it for hours but it still couldn't work until finally, after hard resetting for the unlimited time, it booted up.
The problem though, is that it wasn't rooted and TWRP wasn't installed when it came up so I tried it again. Second try, second time it was messed up. Annoyingly, I don't know what I did earlier to make it work. The second instance it happened is just like the first.
Just to be clear, this isn't the boot screen where the kindle fire logo is animated (has reflections). In my case, its the logo as is, stuck on the screen just like that. Tried hard resetting, doesn't work.
What do I know?
1) From my earlier experience, it has lesser to do with the system (PC, Mac) and drivers since I managed to get it boot up again without being connected the first time
2) If I do connect it to the PC, it says Cannot Start Device/Unable to Start Device. Code:10. That's it. Even if I reboot the device, its still the same.
3) If you connect it to the Mac, it is detected in system preferences. Problem though is that I tried using adb and just like its windows counterpart, there are no devices detected.
THOUHGTS:
1) I know I just have to get it to be recognized and I can change the bootmode. Something's telling me that its a boot mode problem only. In my earlier V3X phone, I used to TP (testpoint) if anyone's familiar with that, or shortcircuit the board to get it out of the 'loop'. Do we have that with the kindle fire?
2) What operating system would it be easiest to get the device detected. I'm hoping that if there's lesser complications with the device being detected by the computer, be it mac, linux or windows, I can change the bootmode. my technical instinct tells me it has something to do with boot mode.
What have I done already?
1. Let me see, I believe I tried hard resetting it for ALOT of times already
2. Reinstalled drivers on PC. Used both Android and Kindle Fire Utility drivers. Even checked the /android folder
3. I'm using a Nokia Micro-USB cable. I'm not sure if that has any impact on the device or its effectiveness but I will try to pick-up another cable today and post later.
I would really appreciate if anyone can help. It sucks that I tried this just after unboxing the unit. I haven't even tried doing anything on it yet.
If you can help, ANY help would be appreciated.
Thanks mate!

had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
the entry for 18D1 in adb_usb.ini is missing - had to add it
the other entries are allready in version .6 android_winusb.inf
if you have troubles to remove old drivers use this:
http://support.microsoft.com/kb/315539/en-us
unplug/replug and install the drivers from .6 from scratch
it's not needed to reboot the computer - works immediately
waiting to get your status ...

b63 said:
had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
waiting to get your status ...
Click to expand...
Click to collapse
Did you solve your problem?
My kindle is recognized by my computer but it as either ADB device or Composite ADB device (depending on what drivers I use to install it). Problem is that it says Cannot start device. Code Error: 10. Tried shutting down/restarting PC, still the same.

updated my initial post again ... (ms-link)
yes solved it in minutes
make the additional entry in adb_usb.ini
use only the drivers from .6
i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
whats your status ?

i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
Click to expand...
Click to collapse
I did this but it still says device cannot be started.
make the additional entry in adb_usb.ini
Click to expand...
Click to collapse
0x18D1 -- is that what I'm supposed to add to adb_usb.ini?

yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually

b63 said:
yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually
Click to expand...
Click to collapse
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.

kaswistry said:
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.
Click to expand...
Click to collapse
all this works using windows 7

dustyjerran said:
all this works using windows 7
Click to expand...
Click to collapse
I did try this yesterday on Windows 7 but most guides I see do it on older versions. I will try again a little later. Thank you.

I tried it on Windows 7. Still the same error. Kindle is frozen and on Device Manager it says "This device cannot start. (Code 10)"

I ran into the exact problem yesterday. I thought I bricked my kindle. That was scary. Anyway, the problem is that you're stuck on fastboot, mode 4002 instead of a normal mode 4000.
Following rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/
You'll need to add a new vendor id (0x18d1). However, even with that the device still will not be recognized right away. Following another user's suggestion on that same thread, I let the battery drained out. Once that's done, reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Then do the adb commands (even if it doesn't show any device attached)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Your device will reboot out of the stuck "kindle fire" logo screen. If your device goes dark after, it just means that the battery need to recharged first. Another scary moment for me. You can unplug and use the wall charger, much faster than charging by PC. After 5 - 10 minutes, you should get back to your normal screen. Then, just use the Kindle Utility to install TWRP.

You'll need to add a new vendor id (0x18d1).
Click to expand...
Click to collapse
I added this already
reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Click to expand...
Click to collapse
Actually, the problem with mine is that it's detected. However, it shows up as Code:10, The device is unable to start.
Still, I'll try to drain it first, tinker with it next and see what happens. That or I'll wait for tomorrow and open the whole device already and see if I can OMAP it.

Mine also did show up as code 10, and sometimes code 43 ... I tried uninstalled the driver and reinstall it manually each time and eventually showed up as unrecognized ... so I tried the battery drain ... I even tried putting it in the freezer to quicken the drain but not sure if it actually help ..

I tried the battery draining. Nope, still didn't work
UPDATE: I take this back. After draining the battery, I would like to confirm that the issue has been fixed. Thank you, THANK YOU Everyone! )
I REALLY APPRECIATE THE EFFORT. HAPPY HOLIDAYS! )

A family member recently got a Kindle Fire, I tried to flash recovery but it got stuck in fastboot mode. Windows will recognize it as uknown device but Linux won't detect anything in fastboot or adb.
I will try battery drain out since kaswistry said it worked
If all else fails, I will try this.. http://forum.xda-developers.com/showthread.php?t=1405052
EDIT: nevermind lol, this worked.. http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11 even though i tried it several times already..

I have the same problem too, the kindle fire stuck at the boot logo
kf utility show that when i try to restore or other option!
Changing bootmode doesent work at all
*imageshack/photo/my-images/10/60506677.png/[/url] (imageshack link)
KF utility status fastboot... offline
*imageshack/photo/my-images/834/kfustatus.png/
My computer have the right driver!
can anybody help me?
*sorry for my bad english*

Could it be that something destroyed my FireFireFire boot? My KF always gets stuck in fastboot when I try to flash ... obviously quite annoying.

u guys need to talk to vashypool in irc and he can fix it!! he fixed mine and mine was a complete brick

If it gets stuck in fastboot you need to run the command fastboot idme bootmode 4000 from the Android SDK.
Sent from my Kindle Fire using Tapatalk

In my case, i have tried to install the original 6.2 kindle firmware with TWRP. After that, the kindle staying stuck on the boot logo... This is me story... I think my kindle is stuck on fastboot! I tried to change bootmod with FK utility v.6
This is what kf utility gave me, when i try to reinstall twrp
imageshack.us/photo/my-images/10/60506677.png/
And this is the kf utility status
imageshack.us/photo/my-images/834/kfustatus.png/
Is anybody can say me, if my kindle is bricked for ever? Or have a solution
Happy holiday btw
#sorry for my poor english#

!!!(Q) Help bricked kindle fire 6.3

okay so i was trying to root my kindle fire and i didnt get su any where so then i tryed to install cwm and now its stuck at the yellow triangle and it wont go into recovery and it also will not connect to adb i need hellp ASAP

Install drivers as ADB composite with the Android SDK and then use this to change the bootmode

The link you posted is not working due to the period in the URL at the end.

Do not afraid. I have got the same experience Let God bless the search button
http://forum.xda-developers.com/showthread.php?t=1568340
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
Your kindle will "get stuck" on the kindle fire screen, but really it's just in fastboot mode.
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Your device will now boot into twrp recovery, and flash the firefirefire bootlaoder. When done it will prompt you to reboot. Upon reboot you will get stuck on the "yellow triangle" screen of firefire fire.
fastboot oem idme bootmode 5002
fastboot reboot
Click to expand...
Click to collapse

My kindle got the 6.3 update -solved!!
This has got to be one of the fastest ways I have rooted 6.3 kindle update
i went on line here http://liliputing.com/2012/03/root-...ogle-play-store-with-kindle-fire-utility.html
downloaded the new kindle fire utility and ckick on Install permanent root with super user. got rooted in about 2 minutes with no trouble at all

thanks everyone for your help but i solved it what i was doing was unsing the kindle fire utility trying to instal latest firefirefire but it just sat there and so i just went into the utility and reinstaled the twrp and it booted normal!!

Bricked Kindle
Okay, I'm not having the same issue, but I'm pretty sure I've completely, irevicalbly, bricked my kindle.
I know that I'm not in Fastboot mode, I've experienced that issue and solved it with the KFU.
Here's what I did:
I used the KFU to root my kindle. That worked fine. I was able to load all the Google apps (which was my initial goal). Then, I got greedy and decided that ICS was my next step - oops.
I followed the instructions on the following site:
androidauthority.com/kindle-fire-miui-4-ics-55853/
Note: I know, I'm an idiot - I should have paid attention to comments! UGH!
After I did this, I now only get the firefirefire logo and that is it. I can't load/reload TWRP and I can't change my bootmode to normal or recovery. The thing is, no matter which computer I plug the device into, the computer won't recognize the device. I get a message saying something "malfunctioned" when I plug it in. I've tried 3 different Windows machines (I've installed/reinstalled drivers I don't know how many times!) and I even tried loading Linux on a spare laptop and that didn't work either.
So, I tried the next thing I could think of. I followed the instructions on the following site:
ramble.karrth.com - Section "Troubleshooting TWRP
which involved removing the back cover, shorting a circuit (to force usbboot) and plugging my Kindle in. This didn't work for me either.
At this point, I'm willing to try anything. I'm not quite sure how to fix this issue. I think my next step is to either order a factory cable or make my own and try that, but if my bootloader is broke (truely broke) will that even work?
Please, if I should post this in another forum/place, just let me know. Any help appreciated!

I should also not that nothing comes up in my device manager. It does come up as a unrecognized USB bit goes away after telling me there was a malfunction.

ChrisKenison said:
I should also not that nothing comes up in my device manager. It does come up as a unrecognized USB bit goes away after telling me there was a malfunction.
Click to expand...
Click to collapse
If you get the yellow triangle logo to come up, then it's probably in fastboot mode. If you reboot it while it's connected to your computer and you get some device detection beeps from Windows, it's likely to be a driver issue. Look here...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You might want to read the first post in that thread too.
Watch carefully as the device boots up and you get the yellow triangle logo. If that boot logo comes up and stays there, it's in fastboot. If the boot logo comes up, the screens blacks out, and then the boot logo comes back up (dimmer) then it's either trying to get into recovery or booting into the OS and failing.
I would try setting the bootmode to normal in KFU and when it says "<waiting for device>" reboot the Kindle Fire. Since you have FFF, the fastboot program on your computer will wait for the Kindle Fire's FFF bootloader to get into temporary fastboot and reset the bootmode when the KF is ready.

But, the computer won't even recognize there is a device connected to it
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?

And because its not recognized in the device manger, kfu isn't picking it up
Sent from my Galaxy Nexus using xda premium

ChrisKenison said:
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?
Click to expand...
Click to collapse
If you can't get the drivers working with the KFU distribution, you'll have a harder time with the SDK. They are the same drivers, but KFU has an updated, Kindle Fire specific .inf file for the driver and also installs the .ini file in the .android folder that you'll need. I don't know what you see in the device manager, but if you don't get one of the devices shown in the post I referred to earlier, I would try another Windows machine. You won't be able to do anything without getting it to detect your KF and load the proper drivers. If you are more adventurous, you could try pokey9000's Firekit (search for it) and try using linux to send it fastboot commands.

Yeah, that's my problem. I have tried 3 different windows machines (all windows 7) and, being the adventurous person i am I tried the Linux fix (removing back cover...) to no avail. All that did was make my kindle blink green. Not sure what that means either.

yea mine is stuck on the firefirefire boot screen

ChrisKenison said:
Yeah, that's my problem. I have tried 3 different windows machines (all windows 7) and, being the adventurous person i am I tried the Linux fix (removing back cover...) to no avail. All that did was make my kindle blink green. Not sure what that means either.
Click to expand...
Click to collapse
Well, if you can't get any of those scenarios to work out, maybe it's a hardware issue. It might be something as simple as a bad USB cable or something more serious within the KF itself. I've never had a problem with Windows or Linux not seeing the KF, so my hands on experience in this regard is limited... my KF has never been broken to that degree. I'm always curious to see what's going on with people's KF when they say nothing works, but my KF has never given me that opportunity.

ChrisKenison said:
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?
Click to expand...
Click to collapse
Sometimes in order to install the correct driver you need to delete the original from your computer because it will continue to attempt to revert to the default but beforehand try rebooting your computer and the kindle
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
mistaanime said:
yea mine is stuck on the firefirefire boot screen
Click to expand...
Click to collapse
Run the kf utility again install twrp and fff again

USB disconnects my rooted kindle fire very fast (details inside)

I rooted my Kindle Fire about a month ago with KFU. Everything was fine until I turned it on one day and I got stuck at the Triangle screen. None of the reboot tricks work. The interesting thing which I think is what is stopping me from being able to successfully use other methods is that when I plug my Kindle Fire into my computer via usb, it connects, and then disconnects (the USB) about 2 seconds later. I've tried different ports, etc. Any help on this issue would be greatly appreciated. I've read over multiple things, but don't see a mention to the kindle being disconnected via usb so quickly, thus stopping me from being able to do anything.

Care to elaborate on what "reboot tricks" you've used?
What version of Windows are you using?

soupmagnet said:
Care to elaborate on what "reboot tricks" you've used?
What version of Windows are you using?
Click to expand...
Click to collapse
I've tried the rebooting the Kindle while trying to reset the kindle to booting "normally" within the KFU. I've tried holding down the power button on a reset, then pushing it again until it is orange, none seem to work. I'm confident I could get it to work again if the kindle did not disconnect from my computer so quickly. By this I mean I hear the "usb chime" when I plug it in, then within seconds the disconnect chime plays. During the brief few seconds it is connected, it shows up on my devices list, but obviously when the usb disconnect chime plays, it disappears off of the device list.
edit: I'm using windows 7 Ultimate.

Can anyone help me? I may add that My Kindle Fire was originally rooted with the KFU and worked perfectly fine. I literally turned it on one day, and it got stuck at the triangle screen. The connection issue of it disconnecting so quickly is what is stopping me from fixing it I believe. Please help.

ErikV55 said:
Can anyone help me? I may add that My Kindle Fire was originally rooted with the KFU and worked perfectly fine. I literally turned it on one day, and it got stuck at the triangle screen. The connection issue of it disconnecting so quickly is what is stopping me from fixing it I believe. Please help.
Click to expand...
Click to collapse
Read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Figure out what device drivers are getting loaded when the connect "chimes" sound in Windows. If you confirm that they are correct based on the contents above, you must stop the temporary fastboot, set the bootmode to normal using fastboot, and restart the device.
I suspect you've got more issues than just getting stuck on the bootloader though... If you are getting disconnect tones in the bootloader, that means it's attempting to boot into something, but obviously unable to do so.

kinfauns said:
Read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Figure out what device drivers are getting loaded when the connect "chimes" sound in Windows. If you confirm that they are correct based on the contents above, you must stop the temporary fastboot, set the bootmode to normal using fastboot, and restart the device.
I suspect you've got more issues than just getting stuck on the bootloader though... If you are getting disconnect tones in the bootloader, that means it's attempting to boot into something, but obviously unable to do so.
Click to expand...
Click to collapse
The disconnect tones are from my computer, the same tone when you unplug a usb (since the kindle is plugged in via usb) I can't change the bootmode because the usb disconnect chime happens literally 2 seconds later, and the kindle is disconnected, all the while the kindle is still on and showing the triangle screen.

ErikV55 said:
The disconnect tones are from my computer, the same tone when you unplug a usb (since the kindle is plugged in via usb) I can't change the bootmode because the usb disconnect chime happens literally 2 seconds later, and the kindle is disconnected, all the while the kindle is still on and showing the triangle screen.
Click to expand...
Click to collapse
Have you checked to see what drivers are getting loaded? Do you know what device should appear in the device manager? Have you tried to stop the temporary fastboot countdown? Do you know how to stop the temporary fastboot countdown?
If you aren't willing to try out my suggestions, there's not much else I can do.

kinfauns said:
Have you checked to see what drivers are getting loaded? Do you know what device should appear in the device manager? Have you tried to stop the temporary fastboot countdown? Do you know how to stop the temporary fastboot countdown?
If you aren't willing to try out my suggestions, there's not much else I can do.
Click to expand...
Click to collapse
Yes to all those things. The device does indeed pop up in the device manager but only for the brief 2 second window before it disconnects. I've tried multiple usb ports on my pc with the same result. The kindle does not power off in any way when the it disconnects from the pc.

ErikV55 said:
Yes to all those things. The device does indeed pop up in the device manager but only for the brief 2 second window before it disconnects. I've tried multiple usb ports on my pc with the same result. The kindle does not power off in any way when the it disconnects from the pc.
Click to expand...
Click to collapse
What is the device name that comes up?
What command did you send to stop the countdown?
What did it output as a result of the command?
What makes you think that it should power off when you disconnect from the PC?

kinfauns said:
What is the device name that comes up?
What command did you send to stop the countdown?
What did it output as a result of the command?
What makes you think that it should power off when you disconnect from the PC?
Click to expand...
Click to collapse
I've tried to reset the bootmode via the KFU method recommended in the guide posted here (normal, 4000 and trying to reset when it says waiting for device) The device pops up in the device manager as an "unknown device" which may be a problem with the version of the drivers im DLing. I'm using KFU version 0.9.6
When I first DLed them it seemed as if the drivers were installing correctly, when I plugged in the Kindle is said drivers were being installed but it failed because the device disconnected after the 2 seconds.

Rapid disconnects are nothing unique, they're simply driver or USB problems. Any malfunctioning USB device will give you that same sequence. Anyways, it's difficult to get out of a boot-loop without ADB so let's try to get that USB working again.
First, do you have a bootloader (like FFF) or a recovery (like TWRP) loaded? I'm not sure the USB driver will work during boot without at least one of those installed.
Second, boot into TWRP, then try to fix the USB from the computer end. Uninstall the drivers, download a fresh batch, reinstall drivers, reboot. Use explorer to check %userprofile%\.android\adb_usb.ini and make sure 0x1949 is there. Also check Kindle Fire Utility\drivers\kindle\android_winusb.inf and make sure whatever hardware ID is showing up in device manager is in there.
BTW, what device IS showing in Device Manager after the disconnect? Use right click, scan for hardware changes.
Third, the USB cable or ports themselves may be at fault. Try a different cable, and try a different computer. Also, reboot often.

hunterhk said:
Rapid disconnects are nothing unique, they're simply driver or USB problems. Any malfunctioning USB device will give you that same sequence. Anyways, it's difficult to get out of a boot-loop without ADB so let's try to get that USB working again.
First, do you have a bootloader (like FFF) or a recovery (like TWRP) loaded? I'm not sure the USB driver will work during boot without at least one of those installed.
Second, boot into TWRP, then try to fix the USB from the computer end. Uninstall the drivers, download a fresh batch, reinstall drivers, reboot. Use explorer to check %userprofile%\.android\adb_usb.ini and make sure 0x1949 is there. Also check Kindle Fire Utility\drivers\kindle\android_winusb.inf and make sure whatever hardware ID is showing up in device manager is in there.
BTW, what device IS showing in Device Manager after the disconnect? Use right click, scan for hardware changes.
Third, the USB cable or ports themselves may be at fault. Try a different cable, and try a different computer. Also, reboot often.
Click to expand...
Click to collapse
Thanks for your response, I will go through these and report back when I get back home from class.

ok, now I have my kindle being recognized by my computer as "android phone" with the sub of "android adb interface." If I have read the guide correctly that means it is in fastboot mode. However when I open kfu it says the kindle is offline.
If someone would be willing to help me out through Skype I would gladly appreciate it. I'm really at a lose as to what to do at this point.
and no stupidly I do not have FFF or TWRP loaded, since I first rooted it when I was a super noob. The usb driver seems like it should be able to work according the the Kindle fire beginners guide, but KFU does not recognize the kindle even though my computer does.

[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 bricked my Kindle

I have read to a nausea thread after thread about fixing my bricked Kindle, unfortunately I cannot post in the development section since I am a big NOOB. I'm sure most have heard this a million times, and have read about it a million times but have I still have not a clue how to go about it.
If anyone can help it would be greatly appreciated.
So story is downloaded KFU, installed drivers via KFU, plugged in Kindle, started option 2(ROOT w/ SU), it chugged away snagged at install FFFing, so I thought okay let me unplug and re do it, but now it is stuck at KF logo white/orange which many of you say is in fastboot mode. I cannot get the computer to recognize when connected, usually you hear a audible tone when connecting via usb, but nothing. Have tried reinstalling drivers again but they show they have already been installed. People say unistall but I cannot find the device to uninstall the drivers!! I have tried the unbrick util, but KF does not show nor on KFU. Thus I think Soupkit would be the same if it cannot see that KF is connected.
Another q, is even if I get it unbricked and use KFU will it still hang at FFF again...is it just dependent on computer or something, I don't understand why it works for some and not for others(causing them to use linux instead of windows?)
Please help me

You can still reboot to normal mode. Load KFU, and press 1, and then enter, and then 1 and then enter. This should reboot the kindle EVEN if it says its offline in KFU.
If that doesnt work, turn off the kindle, and as soon as you turn it back on, press 1 enter 1 enter in KFU.
Both these methods worked for me... but my KFU still hangs every time it enters fastbootmode!

jinhypen said:
I have read to a nausea thread after thread about fixing my bricked Kindle, unfortunately I cannot post in the development section since I am a big NOOB. I'm sure most have heard this a million times, and have read about it a million times but have I still have not a clue how to go about it.
If anyone can help it would be greatly appreciated.
So story is downloaded KFU, installed drivers via KFU, plugged in Kindle, started option 2(ROOT w/ SU), it chugged away snagged at install FFFing, so I thought okay let me unplug and re do it, but now it is stuck at KF logo white/orange which many of you say is in fastboot mode. I cannot get the computer to recognize when connected, usually you hear a audible tone when connecting via usb, but nothing. Have tried reinstalling drivers again but they show they have already been installed. People say unistall but I cannot find the device to uninstall the drivers!! I have tried the unbrick util, but KF does not show nor on KFU. Thus I think Soupkit would be the same if it cannot see that KF is connected.
Another q, is even if I get it unbricked and use KFU will it still hang at FFF again...is it just dependent on computer or something, I don't understand why it works for some and not for others(causing them to use linux instead of windows?)
Please help me
Click to expand...
Click to collapse
first of all lets get this straight. KFU did not (what you call bricking) brick it. you did by taking on the challenge.
second does device manager show up with anything when you plug it in?

goldflame09 said:
first of all lets get this straight. KFU did not (what you call bricking) brick it. you did by taking on the challenge.
second does device manager show up with anything when you plug it in?
Click to expand...
Click to collapse
Thanks for the replies guys, I tried the first solution of using KFU and option 1, however it just hangs and just says waiting for device/device not found. Goldflame you are correct, I did it myself, no one forced me LOL. The device does not show up when I plug it in. If I power down(hold power down for 15secs, and then plug it in the KF logo comes back up but remains nonresponsive.) Seems the computer doesn't know its connected so the two cannot communicate. I've installed drivers so don't know what the problem is, tried different usb ports as well. I am also using a non factory micro cable, IDK if that matters or not read other people ordering factory ones to help them.

jinhypen said:
Thanks for the replies guys, I tried the first solution of using KFU and option 1, however it just hangs and just says waiting for device/device not found. Goldflame you are correct, I did it myself, no one forced me LOL. The device does not show up when I plug it in. If I power down(hold power down for 15secs, and then plug it in the KF logo comes back up but remains nonresponsive.) Seems the computer doesn't know its connected so the two cannot communicate. I've installed drivers so don't know what the problem is, tried different usb ports as well. I am also using a non factory micro cable, IDK if that matters or not read other people ordering factory ones to help them.
Click to expand...
Click to collapse
ok well this is different from my case where it showed up as an unknown device in device manager. reboot your computer without the kindl plugged in and let me know if anything different happens when you plug in your kindle

goldflame09 said:
ok well this is different from my case where it showed up as an unknown device in device manager. reboot your computer without the kindl plugged in and let me know if anything different happens when you plug in your kindle
Click to expand...
Click to collapse
Yes rebooted still reacts the same way. any other ideas? tia.

jinhypen said:
Yes rebooted still reacts the same way. any other ideas? tia.
Click to expand...
Click to collapse
I have no guarantee that it will work but try to delete your .android folder.
Its located in c:/users/your user name/.android
Then plug in your kindle, open kfu and choose option 2 even if it says device offline
Sent from my Kindle Fire running CM10.1/SGT7

goldflame09 said:
I have no guarantee that it will work but try to delete your .android folder.
Its located in c:/users/your user name/.android
Then plug in your kindle, open kfu and choose option 2 even if it says device offline
Sent from my Kindle Fire running CM10.1/SGT7
Click to expand...
Click to collapse
TY you for being so responsive goldflame, but I have already done that as well...I researched quite bit before posting this..as I didn't wanna be "that" person. Still nothing works does anyone have anymore solutions for me?