[Kindle Fire Q&A, Help & Troubleshooting] sisterdelirious:
Hi there. I have spent several days searching xda forums, popping into the kindlefire irc channel, and searching google however have not yet figured this out, could use some help.

I have read: the Kindle Fire Beginners Guide, the Kindle Fire Unbrick thread, The Kindle Fire Utility thread (yup the whole thing), and more.

According to the Kindle Fire Beginner's Guide, only 1% of all brick situations are actually a brick, so I'm going to persevere and go ahead and ask for the help, because also according to the guide, if your fire can't be seen as a device then actually it's a brick. To quote: " unless something else was done to the device after the change in bootmode preventing access to adb or fastboot commands. Then it’s actually a brick at that point."

I can't be sure if anything else was done after the change in bootmode so I'll just explain how I got here and hopefully someone can help out.

I have a mac mini running Os x 10.6.8, and the Kindle Fire which was running stock version 6.2.2.

I used the kindlewater root method to install firefirefire and cwm recovery. Was able to boot into recovery by pressing on the power button for it to go orange and then load the recovery options.

Before doing anything at all (and in consultation with St3p_2 of this forum, one of the kindlewater developers), I decided to perform a backup in preparation for flashing a ROM.

so, I booted, went into recovery, navigated to "install a .zip" and chose "backup" at which point I got a message/nag/reminder that this was a permanent change, and I selected "ok". It did it's thing for a while, went into reboot, and I then had the firefirefire logo blinking in a very very slow loop.

It was recommended to me to perform a factory reset by holding the power button for 2 solid minutes, which should then have returned me to stock. Actually, the first time i did it for minutes I went from having a very slow blinking firefirefire to having a rather fast blinking firefirefire. Following a suggestion i then tried it with the kindlefire unplugged. This resulted in a plain black screen until the fire was plugged in again: no boot, no indication of response to use of the power button. Once plugged in, it has gone back to the rather fast blinking firefirefire logo.

I read through the Kindle Fire Utility thread, found the v0.9.2 version prepared for mac and linux, and downloaded it. Although I am not new to terminal, I am not familiar with what command language is necessary to perform the actions required by this tool. If I open the install_drivers.sh with terminal, i get this:

Reverie:~ apple$ /kindlefire/Kindle_Fire_Utility_MacLinux_0.9-1.2/install_drivers.sh ; exit;

This file will install the correct adb_usb.ini file for proper Kindle Fire detection.

cp: drivers/adb_usb.ini: No such file or directory

Done!

logout

[Process completed]

​

so I tried running it in the console. I will spare you the output of the console as it appeared to be merely a printout of the actual code of the file and was quite long.

Trying to run the file runme.sh in terminal before running the install_drivers.sh in the console, I got error messages stating there is no such command, or no such file, depending on my command language.

After running the install_drivers.sh in the console, when I try to run runme.sh in terminal, i get this:

/kindlefire/runme.sh ; exit;

Reverie:~ apple$ /kindlefire/runme.sh ; exit;

---------------------------------------------------------------

Easy rooting toolkit (v1.0)

created by DooMLoRD

using exploit zergRush (Revolutionary Team)

Credits go to all those involved in making this possible!

---------------------------------------------------------------

[*] This script will:

(1) root ur device using zergRush exploit

(2) install Busybox (1.18.4)

(3) install SU files (3.0.5)

[*] Before u begin:

(1) make sure adb is in your path

(2) enable "USB DEBUGGING"

from (Menu\Settings\Applications\Development)

(3) enable "UNKNOWN SOURCES"

from (Menu\Settings\Applications)

(4) [OPTIONAL] increase screen timeout to 10 minutes

(5) connect USB cable to PHONE and then connect to PC

(6) skip "PC Companion Software" prompt on device

---------------------------------------------------------------

CONFIRM ALL THE ABOVE THEN

Press any key to continue... --- STARTING ----

--- WAITING FOR DEVICE

​

Which I affirmed because all the requirements had indeed been set that way on the device before the bricking happened. After "starting" and "waiting for device" nothing happens even waiting indefinitely (more than half an hour) and then it never finds the device.

When I go into terminal and type: "adb devices" I get:

Last login: Sun Mar 18 17:08:38 on ttys001

Reverie:~ apple$ adb devices

List of devices attached

Reverie:~ apple$

​

This result is the same both before attempting to use the 0.9.2 mac utility and after.

I really am stuck at this point, as everything I find with instructions on how to "unbrick" does require that the machine recognize that your kindlefire is attached. Running any of the tools I find requires that basic bottom dollar, which I don't seem to have.

That said, the behavior of "nothing at all: blank screen" when unplugged, and the behavior of "blinking firefirefire logo" when plugged in would tend to indicate that at the very least the device knows it's plugged in and getting juice, and some process is happening when that's true.

Can someone help? Is my next step to purchase a factory cable, or do I have a software solution available to me that I just didn't find in this haystack of solutions?