[Kindle Fire Q&A, Help & Troubleshooting] pugsley42:
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).