KF2 stuck on boot, not recognized by Windows/ADB/Fastboot

[MisterShakey]

So I dug up this old, softbricked Kindle Fire 2 my brother had been tampering with. He'd managed to root it, flash CM and was probably trying to restore to stock. But then I suspect he used KFU. Yeah, ****.

Anyhow, the Kindle turns on with a white and orange Kindle Fire logo, and that's it. I've made myself a fastboot cable and am entering fastboot mode, with a green blinking light and a red one on the screen.

Here's the problem: Windows 10 Pro (my current system) doesn't recognize it, and neither does ADB and Fastboot. It's listed in Device Manager as otter2-prod-04. ADB returns nothing on 'adb devices' and Fastboot returns '<waiting for device>'

Hardware IDs:
USB\VID_1949&PID_000A&REV_0100
USB\VID_1949&PID_000A

I've tried a bunch of drivers, from Amazon's dev section, from @stunts513 (link: https://forum.xda-developers.com/showpost.php?p=44446906&postcount=9) and a universal driver that says it covers KF2.

Even though Device Manager allows me to update drivers manually to Android ADB Interface or Composite ADB Interface, no luck.

Even got my hands on @lazyguyMC 's kit (https://forum.xda-developers.com/ki...ent/kindle-fire-2-automatic-disaster-t3398676)

Care to help a otter2 noob out?

 

[LazyguyMC]

Any screenshots? That might help me. Otherwise, we could try using something like Teamveiwer.

 

[V0idst4r]

You do not have the correct fastboot drivers. What I found that worked for me was going into Device Manager, find your Kindle that has a yellow triangle, right click it, select update driver, and find ADB Interface -> ADB Composite Interface.

---------- Post added at 09:22 AM ---------- Previous post was at 09:21 AM ----------

I probably shouldn't of fixed my drivers though because I just flashed the wrong bootloader and hard bricked :silly: