[General Questions and Answers] JustSomeRandomCoder:
I have a 1st Generation Kindle Fire (DO1400). I had been running 6.3.1 prior to my first attempted root. I am running windows 7 on one pc and Ubuntu Live USB on a second machine. I've been working on this about a month and a half and read and re-read the posts here on Xda and have finally run out of ideas on what to try next to fix my kindle fire.

So how did I get to where I am:

I attempted to Root Device failed using KindleFirerootNew631 tool. The process appeared to get stuck (I should have documented more at the time but was in a hurry to leave for a trip) So I did a forced shut down and left. When I came back and booted the device I ended up viewing a screen that I later learned was commonly known as 'FIREFIREFIRE'.

To resolve this issue I downloaded and ran 'Kindle Fire Utility 0.9.6'. Ran the 'InstallDrivers.bat' script. then started the app. I was able to get Root and then install TWRP, Latest FireFireFire and Google Apps. Everything is working and so I figure hey fixed it once I can again so not why not play around some more. I decide I want to look around in TWRP and see what it offers. I then end up deleting my Kindle ROM (didn't make a backup prior to messing around which was another mistake) So at this point I've got TWRP and I can mount it within windows but have no ROM.

Figuring since I have no ROM I then download the latest stock image from amazon, mounted the device using TWRP, transferred the file in the /bin directory on the kindle. I'm not certain what I selected next but I think it may have been restore defaults. The device powered off, restarted and then remained on the static kindle fire boot loader screen. Checking kindle fire utility I found that the device that ADB Status: Connected. Boot status: Unknown' When I attempted to use adb I could reboot the device, but any attempt by kindle fire utility resulted in the error ' error: exec '/system/bin/sh' failed: No such file or directory' The next time I unplugged/replugged my kindle I was not longer able to ever get the 'ADB Status: connected'. I have since found that if I uninstall the drivers provided by Kindle Fire Utility, unplug/replug in the device I am able to get it to show up as Online but still have status of unknown.

Next after reading I found that many people had utilized a Factory cable to successfully recover. So I set about creating a factory cable using a breakout board from sparkfun and following pinout shown here: http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html The factory cable didn't seem to have any impact on the kindle which was confusing to me as I expected it to automatically allow me to connect. I have triple tested the pin outs to verify there are no shorts (excluding the jumper between pins 1 and 4) From further reading I think I found out the kindle fire 'factory cable' to work it must have a working boot loader.

From reading other posts I figured my last attempt would be to try the 'shorting trick' used in conjunction with FireKit Live USB repair kit. (detailed in the post http://xdaforums.com/showthread.php?t=1430038 and http://xdaforums.com/showthread.php?t=1650738 ) I removed the back cover without any issues. The Kindle fire still shows the static 'Kindle Fire' boot loader screen and is detected on both Windows and Ubuntu machines.

Launch Ubuntu on live usb and started firekit. Then ran firekit with command 'usb_fix_parts_and_install_fff_twrp. But was stuck waiting for the device. I also tried with the commands usb_boot_twrp, fix_parts commands while repeating all the shorting/connecting steps and tried with the battery always connected and without it connected and then reconnecting it part way through. I read that some of the firefirefire versions check that it is connected and wil halt if it is not connected. But was never able to get the fire fix to detect the device.

So where am I now:

Currently I am able to charge the battery (I verified this by leaving it running with the static bootloader screen until the battery died, then plugged it in using the charging cable over night, next day I unplugged it for 15 minutes to just see if the boot loader screen would remain on, which it did, I would guess it would go several hours on a charge as that is what it was doing when it last worked). I can still adb device connected but status is unknown. I can also issue reboot commands to the device through ADB. But can not get any tool to find the device in any attempt to install a new boot loader.

So are there any options remaining? Is there something I missed? At this point all I can think of is either trying to replace the sd/mother board or purchase an entirely new kindle fire. :confused: