yashsingh1/xdaforums huggingface dataset:
[Kindle Fire General] kinfauns:
Since there are a lot of fastboot/adb gurus around here, I thought I would try posting in this thread. Maybe someone will find my problem challenging enough to try and lend a hand.

The touchscreen on my Kindle Fire has failed does not respond to any touches. In an attempt to bring it back to stock, I've also managed to erase the system with fastboot. So, I have a semi-bricked device with a broken touchscreen... a double whammy.

I have a factory cable and both fastboot and adb available. I can get FFF/TWRP up and running via fastboot boot. I have the Kindle Fire Software Update (both 6.2.2 and 6.2.1 releases) and I've looked inside to find the boot.img, recovery.img and u-boot.bin files. I am able to flash all 3 of these with fastboot, but the /system directory remains (mostly) empty.

I've tried the method described by JackpotClavin to rename the software update to update.zip, place it into /sdcard/kindleupdates, put the command file into /cache/recovery and reboot with the stock bootloader and recovery. That gets as far as the Kindle Fire warning about missing files and it attempts to go back to the factory defaults, but it appears to drop back down to recovery at this point and stays there.

It seems like I need to get my hands on a system.img that I can flash using fastboot, but I can't find anything in my searches. I've also tried an adb push of the entire system directory contained in the update.zip file to /system and changing permissions, but everything in there seems to get erased on boot... I'm guessing this is just another mount point that gets used during the boot process. Another member suggested make_ext4fs, but I don't have any idea where that might be and what symlinks I'm supposed to be creating to make this happen.

I'm hoping someone can make some suggestions on how to recreate this system.img as it seems to be the last piece of the puzzle I need to get this thing booting again. I'd appreciate any help you could provide.
[Kindle Fire General] kinfauns:
OK... after close examination of the twrp recovery log and subsequent tinkering, I get to answer my own post. My Kindle Fire is now booting stock again. Hopefully, this might be able to help someone in the future.

After a fastboot erase of my /system partition and erasing everything on my /sdcard, I created a couple of problems that prevented an update of my KF. Here's how I fixed them....

1) Got into fastboot to install FFF and TWRP.

2) Booted into recovery to get access to an adb shell

3) A fastboot erase of my /system partition had also knocked out the filesystem on the partition, so I needed to rebuild that. 'mke2fs -T ext4 /dev/block/mmcblk0p9' got me the filesystem back. Checked that it would mount again with 'mount -w -t ext4 /dev/block/mmcblk0p9 /system' and it looked fine.

4) TWRP will not mount the /sdcard if it doesn't have a '/sdcard/.android_secure' directory. I had to 'mount -w -t vfat /dev/block/mmcblk0p12 /sdcard' first and a 'mkdir /sdcard/.android_secure' fixed that problem.

5) The one thing I had not seen documented anywhere is that TWRP will flash a zip file automatically, shortly after it starts and before it presents the GUI if it finds a directive to do so. I indicated that TWRP should do just that with 'echo "--update-package=/sdcard/update.zip" > /cache/recovery/command' (The /cache/recovery/ directory might first have to be created if it's not there already) and exited the adb shell.

6) I had already renamed the Kindle Fire Software Update 6.2.2 to update.zip on my C: drive, so that needed to be pushed onto the /sdcard. I exited the adb shell and used 'adb push C:\update.zip /sdcard/update.zip' to do that.

7) Finally, a 'adb reboot' got it restarted and I dropped it into recovery. Instead of the normal TWRP GUI popping up, it gave me some text with a notice that it was in the process of flashing the update.zip file.

I honestly don't remember exactly what happened after it was done... whether I had to manually restart it or not, I next saw that FFF had been replaced with the stock bootloader. When the 'kindlefire' boot logo started to show the glimmer animation, I knew it would work.

So, that's it... how to unbrick your Kindle Fire without touching the screen!
[Kindle Fire General] arkbishop:
Stuck on "Kindle Fire" logo

Good morning,

I believe I may have bricked my KF. It is stuck at the Kindle Fire logo. I have attempted to connect it to my computer (Windows 7) and I am getting a message that it does not recognize the device. I have tried some methods played in "YouTube" but since there is no way to communicate between my computer and the Kindle fire and the Kindle Fire never getting past the Kindle Fire logo I am not sure what venue to take to get it repaired. Can somebody assist me?
[Kindle Fire General] arkbishop:
Bricked Fire

I believe I may have bricked my KF. It is stuck at the Kindle Fire logo. I have attempted to connect it to my computer (Windows 7) and I am getting a message that it does not recognize the device. I have tried some methods played in "YouTube" but since there is no way to communicate between my computer and the Kindle fire and the Kindle Fire never getting past the Kindle Fire logo I am not sure what venue to take to get it repaired. Can somebody assist me?
[Kindle Fire General] kinfauns:
I don't think you'll find a "venue" to take it for repair, but if you are able to perform basic maintenance types of things on your Windows 7 box, you should be able to fix it yourself. You probably haven't (correctly) installed the device drivers necessary for your computer to recognize the Kindle Fire. Uninstall whatever drivers are currently being used for your KF and then use Kindle Fire Utility...

http://xdaforums.com/showthread.php?t=1399889

... to install the correct drivers before connecting your KF to your computer again. There are literally hundreds of articles here from others who have had problems similar to yours. If you really want someone to help, you need to be very specific on what's happening with your device, what you've tried to do, what the results were, etc. People are more likely to lend a hand if they can give you some brief answers on what you should try next. They are much less likely to write a step-by-step guide on how to get it working for you.
[Kindle Fire General] arkbishop:
Kindle Fire Additional Info Brick

I truly appreciate the response. You are absolutely right, I posted the problem assuming the reader would understand what I had done. I will try to be as detailed as possible and hopefully someone will be able to assist.

I was able to succesfully root the Kindle Fire approximately 5 days ago. However, every time I would disconnect the Kindle Fire from my Windows 7 computer, it would prompt me that the Kindle needed a driver update (in the Device Manager). I was able to update the driver and used the Burrito APK to root the device.

Around 4 days ago, the Kindle was crashing on me so I restored to factory settings with the plan of rooting it again. The Kindle Fire would boot up to the TWMP screen and after trying to install the available ROMS, it would take me in a loop and bring me back to the TWMP screen.

I utilized the Unbrick instructions online and the Kindle Fire was stored to Stock ROM. At this time, I loaded the ICS Roms to the kindle and attempted to load them. The computer did not recognize the Kindle in the Device Manager but did prompt a sound acknowledging a connection (however this will not generate a device or external disk drive in the computer).

I attempted to install an ICS ROM but the system would still bring me in a loop. I pressed the Flash button using the ROM and it gt stuck on the Kindle Fire logo.

I have attempted to do a hard reset, connecting it to a different computer (XP) but both computers do the connection noise and keep going on and off. At this time, the Kindle Fire will not communicate with the computers for me to try and install any files.

I hope this was a more detailed explanation adn truly look forward to somebody being able to help me fix/correct whatever I broke. I appreciate any feedback or suggestions.
[Kindle Fire General] kinfauns:
I believe you mean TWRP - Team Win Recovery Project. Anyway, the initial problem you described was caused by setting the bootmode to recovery. To clarify, the device has a number of boot modes that can be set. Most users would just be concerned with 3 of them... normal (4000), fastboot (4002), and recovery (5001). Once you set this, the device will remember it until it is changed again... neither a hard reset nor a change in ROM will affect the bootmode. You want to be in the normal (4000) bootmode, which will boot the system. You apparently had it set in recovery (5001), which brought you into recovery each and every time you rebooted it. This is the expected behavior... the device was doing what you told it to do.

I'm not sure if you are describing the actual stock KF logo or the FIREFIREFIRE yellow triangle logo, but if you had TWRP installed, I'm guessing it's the latter. If you are getting the device detection beeps from Windows, and it's staying in the bootloader with the yellow triangle logo, the odds are that you are in fastboot mode. I suggest you read up on fastboot.

I haven't used Kindle Fire Utility for a long time because I prefer to do things manually, but it might be able to change the bootmode back to normal for you. Otherwise, if you can get it into fastboot mode, you can use the fastboot executable to get you back into normal bootmode. Again, do some reading on fastboot.
[Kindle Fire General] b63:
if you have fff (the yellow triangle) installed then fastboot is available for some seconds at startup. you can use kfu option 1 - bootmode normal or issue "fastboot oem idme bootmode 4000" manually

if it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish

a second pwr off/on will bring you back to normal
[Kindle Fire General] arkbishop:
I just thanked you on the thread, I appreciate your response.

Well, the Kindle Fire is actually stuck on the Kindle Fire boot sequence (does that make matters worse?).

I am sure I can figure it out, once I get the computer to recognize the Kindle. The threads you mentioned in which I can update my computer to recognize the Kindle, can you please point me in the direction I may be able to find them?

Once again, I truly appreciate your response and advise to get more responses in the forum. Have a great weekend!

---------- Post added at 11:01 PM ---------- Previous post was at 10:52 PM ----------

And yes it is stuck on the Kindle Fire logo (not the yellow flame one).

Thanks again!
[Kindle Fire General] b63:
about drivers:

http://xdaforums.com/showpost.php?p=22342376&postcount=6

it is stuck on the "kindle fire" logo

do you see the yellow triangle before ?

is the kindle fire logo static or animated ?
[Kindle Fire General] kinfauns:
I'm not an unbricking expert... it looks like b63 has more experience helping people get that done. However, my feeling is that you will need to somehow get to fastboot so you can install a new bootloader (FIREFIREFIRE aka FFF) and recovery (TWRP). From that point, you'll be able to go back to stock (and root it) or install a new ROM.

For any of this to work, you need the right drivers installed on your machine. The easiest way to do this is use the driver installer found in the Kindle Fire Utility (KFU) package. If issuing fastboot commands seem too daunting for you, in most cases KFU should do the right thing automagically and install TWRP if it's possible.

If your system is messed up to the point that KFU cannot do that for you, I think the easiest way to get it fixed is by using a factory cable. A factory cable is a special USB cable that will force your Kindle Fire into fastboot mode regardless of the bootmode setting or the bootloader being used. Once you can get the device into fastboot mode, KFU will be able to install FFF and TWRP pretty easily.

Using a factory cable is how I've fixed my Kindle Fire and it's a good insurance policy to have around if you manage to do something wrong. In fact, if you read my earlier posts in this thread about my own bricking circumstances, I don't believe I could have gotten my Kindle Fire booting again without a factory cable. Even if you have no recovery or bootable system... with a working bootloader and a factory cable, it's just a few steps to get it back in shape again.

Of course, there's more than one way to skin a cat, as they say. So you might be able to get there without one, but you might want to look into it as a last ditch option.
[Kindle Fire General] arkbishop:
Still bricked

The Kindle Fire is still bricked. I updated the drivers using the thread and my computer accepted them. The computer will do the connection noise when I connect the Kindle but no hard drive or device is recognized by my computer (this blows!). I will continue trying to unbrick it but I really think I messed up bad.

I am willing to try the factory cable, is it the same one that you would use with an Android phone? Where can I find one? How would this help me with my issue?

Once again, I appreciate the help.
[Kindle Fire General] kinfauns:
I think you are in the same boat as the guy in this thread...

http://xdaforums.com/showthread.php?t=1539325

I just posted some information that will answer your questions, so rather than repeat myself, it's probably easier (on me) for you to read that.
[Kindle Fire General] arkbishop:
Still bricked

Thanks for your response?

Where did you get the factory cable? I really am trying to follow all the steps and I am not able to make this work.

I have downloaded the apprprate drives, so I am stuck as to how to make the Kindle fire be recognized by my computer.

Did the factory cable really solve the problem? Where could I get one?
[Kindle Fire General] b63:
don't worry - the cable solves your problem

give him a pm:

http://xdaforums.com/member.php?u=500006

good quality, good price, fast shipping, ships internationally

i have also one from his cables - never needed it - but it's a good feeling to have the "bulletproof jacket"
[Kindle Fire General] chalicucu:
unbrick my KF

My KF after up rom to CM7, CM9 and restore to rom stock, now it is frozen.

when i connect to pc it recognize as normal disk driver not adb.

so i can not install twrp.

when my KF startup it pass kinde fire logo, but it come to loop message

sory calendar... force close, process.android.acore force close.

So i can not go to seting to reset to default factory.

i try to make a factory cab but not ok.

try hard reset (hold pw 20 s) not ok

help me please.

I' ve opened back-side to see KF board.

thanks all
[Kindle Fire General] b63:
http://xdaforums.com/showthread.php?t=1405052
[Kindle Fire General] spursncowboys:
After having problems with my amazon app, and all my google apps, I figured it was a good time to try and learn how to put a new rom in. So I picked CM9 and tried to no avail. I was getting the same problem as alot of guys on here where it said something about /media. But unlike the others, mine wouldn't load like the others. I also was unable to go back to CM7. I was stuck in TWRP. So I tried my back-up and still nothing. Then thinking maybe I had a bad download I tried another CM9 and nothing. Then I tried MUIU. All three said failure to install. Then after trying the MUIU, my computer quit recognizing my KF and it stopped loading into TWRP and just went straight into yellow triangle. I followed the other threads and added the line under the 1949 in .bit file. I reinstalled the drivers in my newly downloaded KFU. Then tried the adb and nothing works because my computer won't recognize the KFU.
[Kindle Fire General] kinfauns:
What do you mean your computer won't recognize KFU?

Can you run fastboot commands when your KF is on the yellow triangle?

What do you get when you run 'fastboot devices' while it's on the yellow triangle?

It's most likely that you have set the bootmode of the device to fastboot and that's why it won't get past the yellow triangle.

You'll have to run 'fastboot oem idme bootmode 4000' to get it back to normal.
[Kindle Fire General] spursncowboys:
No my computer won't recognize my kindle fire. Do you mean run fastboot from my computer? Because it doesn't recognize my kindle so I run it through my KFU and it doesn't happen.
[Kindle Fire General] kinfauns:
What does it return when you run the 'fastboot devices' command?
[Kindle Fire General] spursncowboys:
It says it is unable to locate my kindle fire. It has my status as offline; no; and unknown
[Kindle Fire General] kinfauns:
The fastboot I'm referring to is the tool you run from the Windows command prompt.

http://www.computerhope.com/issues/chusedos.htm

It's in the tools directory of the KFU folder you downloaded. I'm not talking about running the KFU program. If KFU is the only thing you are familiar with, try setting the bootmode back to normal and rebooting the KF. It's #1 in the KFU menu.
[Kindle Fire General] spursncowboys:
ok I hit one, which was normal boot from KFU. It said waiting for device so I held the power down for twenty seconds until it turned off and then hit power again to turn it on where I got this...

Then realizing that fastboot was two I tried two: fastboot. I did the same thing to turn it off and turned it on and hit 2 and enter. I got this
[Kindle Fire General] kinfauns:
No offense, but it sounds to me as if you are just hitting buttons without knowing what they do. The odds of you stumbling around a dark room and eventually finding the light switch isn't all that great. This might sound like a shameless plug, but I think you are a good candidate to read the guide I just put up last night. Give it a good read...

http://xdaforums.com/showthread.php?t=1552547
[Kindle Fire General] spursncowboys:
No offense taken. I completely agree. I hate windows command line. FWIW I have been looking at guides and looking really into it alot before rooting and putting CM7. I still wasn't completely confident about it. I learned alot of linux by screwing it up and troubleshooting. I'm reading it right now. Thank you
[Kindle Fire General] arkbishop:
Bricked KF

I am on the same boat. I have been able to follow a lot of the instructions but am coming short at getting this Kindle fixed. I believe I have downloaded the proper drivers (I am getting confirmation that the driver has been updated). However, the system will not recognize the Kindle and when running the KindleFireUtility, I will get the message:

Oops something went wrong..

We are unable to locate your Kindle Fire

Make sure it is plugged in and powered on

At this time, the only way the Kindle will power on, is if I connect it to the computer however It flashes on and off. I have attempted to charge it directly with a wall charger and I get the same screen (Kindle Fire turning on and off).

What could someone recommend to help me get this Kindle Fire back to work (any state as long as it works will be fine!!!) Thank you all, have a great evenng!
[Kindle Fire General] kinfauns:
Well, I've been trying for the better part of a week to get you on the right path. Since you haven't responded to my last set of directions in the other thread, I'm guessing you want to get a second opinion... and that's fine, but I doubt anybody else will tell you any different.

Judging by your latest post, it sounds like your batteries are dead too, which puts a new twist on things, but your first step still remains the same... Get your KF into fastboot mode and your computer able to send fastboot commands to it. KFU is not going to be some silver bullet for you. It just amounts to a pretty dress on top of fastboot and all it does is reduce fastboot commands to selecting items from a menu. If fastboot doesn't work for you in the first place, KFU is going to be useless.

Another user who had a dead battery reported that he was able to get the KF into fastboot mode with the factory cable. You have a factory cable now, so if you connect that factory cable to your KF and your computer, you should be seeing a static "kindle fire" logo or the yellow triangle logo and it should stay that way. Regardless of whether or not you have the proper drivers installed on your computer, the previous should still hold true. The logo should not blink on and off. If it doesn't stay on one of those two logos, I think you have a much more serious problem.

Please read the following guide...

http://xdaforums.com/showthread.php?t=1552547

I think it might help you understand what's going on with your Kindle Fire. If you want to read about the user who had a dead battery, take a look at...

http://xdaforums.com/showthread.php?t=1392693&page=23

Start at post #226 and read about 20 posts before you get to his fix, but you'll notice that basically the first thing he says is... fastboot.

Good luck.
[Kindle Fire General] arkbishop:
Brick Kindle

No, not at all. I really wanted to send you a direct message and the posting was really directed at you.since you.have been so helpful. Not at all, your instructions make perfect sense and I.have tried to follow.them step by step. Dude, I would even send you the darn Kindle to try and get it fixed.

My apologies, I am trying to get the forum etiquette and meant no disrespect. You really have tried to help me and I truly appreciate it.

I am just not sure, what I did to the KF that I cannot get it to work. I truly appreciate all the help that you.have provided.