Develop Bugs

[Q] Kind Fire Bricked at Yellow Triangle....What Now???

So Ive read multiple threads from this forum and tried the suggested methods and nothing has worked at all. My Kindle Fire is stuck at the Yelllow triangle logo and I have no clue how to get it back working at this point. I originally rooted using BreakDroid using Clockwork recovery and was successful running the Energy ICS Rom.
I attempted to flash the Miui ICS Rom and thats where it went all bad and has been stuck at the Yellow Triangle ever since. I've tried to use the KFU 0.9.6 but my computer only recognizes the kindle as a "android phone" but doesn't see that's it plugged in. KFU states that it's waiting for device when trying to run any of the commands and I have reboot to get it to proceed but none of the commands work and only return me back to a frozen triangle screen everytime.
So I need some serious advise on how to start over and get my kindle fire back to stock and out of this dreadful yellow triangle screen thats haunting me! Please post any instructions based on your experiences or expertise.
Please Please Please Help!
Thanks in advance.....

Are you able to access recovery?

soupmagnet said:
Are you able to access recovery?
Click to expand...
Click to collapse
Nope not at all everytime I press the button and it turns orange nothing happens and it completely freezes and I have to reboot completely.

How comfortable are you with fastboot commands?

soupmagnet said:
How comfortable are you with fastboot commands?
Click to expand...
Click to collapse
Not the best but if you have some instructions I'm sure I can figure it out lol at this point I have no choice

You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.

soupmagnet said:
You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.
Click to expand...
Click to collapse
I used the Kindle Fire Utility and did option #1 to boot normal mode but it didn't work but I'll these methods and post some feedback on it....thanks a lot

soupmagnet said:
You have two different problems.
1. Stuck in fastboot mode
2. Bad drivers
Read this guide: (post #s 1, 2, and 3)
http://forum.xda-developers.com/showpost.php?p=23747567
...that will get you started.
Click to expand...
Click to collapse
I understand all of that info but doesn't really lay out any steps to take to fix the issues I'm having. I'm not a newbie to rooting this is just the first time I've experienced this particular problem

Disregard

Thepooch said:
Disregard
Click to expand...
Click to collapse
Thanks for the positive advice

I wrote some but later recinded it because I didnt feel it fully applied. but as I see you did a bad flash with clockwork mod when the newer roms need to be flashed with twrp from all I have read. Your situation screams drivers as well as soup says. If you can access recovery what about your backup? lemme guess didnt make one? You can use kfu to change your boot mode but first you need adb working my suggestion plug your kindle in run the drivers see if it doesnt show up in kfu.But that doesnt fix what corrupted your system that caused your bootloop in the first place. Really all you can do is get adb going to push some files to your sd card to work with unless perhaps with some magic you regain access to usb mass storage. All this teeters on your ability to get into recovery as well.

Thepooch said:
I wrote some but later recinded it because I didnt feel it fully applied. but as I see you did a bad flash with clockwork mod when the newer roms need to be flashed with twrp from all I have read. Your situation screams drivers as well as soup says. If you can access recovery what about your backup? lemme guess didnt make one? You can use kfu to change your boot mode but first you need adb working my suggestion plug your kindle in run the drivers see if it doesnt show up in kfu.But that doesnt fix what corrupted your system that caused your bootloop in the first place. Really all you can do is get adb going to push some files to your sd card to work with unless perhaps with some magic you regain access to usb mass storage. All this teeters on your ability to get into recovery as well.
Click to expand...
Click to collapse
I actually got it fixed using breakdroid and thank god it worked but thanks for the advice I know exactly what not to do the next time

Had a similar problem brickoid sorted me
Sent from my i777 using xda
aokp on neak yo!

Root Problem! TWRP not installed! Stuck at KF Logo

I was following directions on how to Root my KF ver. 6.3.1, and everything went wrong. Drivers weren't working, and now, I'm apparently stuck in the Limbo between normal boot and fastboot. I've tried the Firekit option, only to have my hopes shot down fast when my laptop and my desktop refused to boot from my jump drive. Not sure why, but they'll boot from disc drive...weird. It's been 2 days now. Nervous about the battery going out...help!!!:crying:

gavination said:
I'm apparently stuck in the Limbo between normal boot and fastboot.
Click to expand...
Click to collapse
What exactly does that mean? From what information do you base that statement?
http://forum.xda-developers.com/showthread.php?p=25884555

soupmagnet said:
What exactly does that mean? From what information do you base that statement?
http://forum.xda-developers.com/showthread.php?p=25884555
Click to expand...
Click to collapse
Well, from what I understand, the tutorial said that if I got stuck, it wasn't a big problem, I'm just stuck in fastboot mode instead of normal boot. Sorry for any misunderstanding!

Still need more information...
http://forum.xda-developers.com/showpost.php?p=25884555

soupmagnet said:
Still need more information...
http://forum.xda-developers.com/showpost.php?p=25884555
Click to expand...
Click to collapse
I just clicked your link and read the information about posting. It's completely correct; there's no way to answer an unknown question after all. I'll try to be as clear as possible: I attempted to follow a guide on liliputing.com on how to root a kindle fire 6.3.1. I went ahead and downloaded the kindle fire utility and unzipped it to a folder on my desktop. I also tried to install the drivers using the file labeled "install_drivers.bat" in the kindle fire utility folder. I thought all went well, but in the guide, the author says that at times, the file may not always work. With this in mind, I ran Kindle fire utility, checked the adb status to see that it was offline, and i started to manually configure the driver by going to device manager. The author said to look for something that said "Amazon", but I only found something that said android...srry, i can't remember what else was there, but I assumed it was the kindle because it's an Android device. But anywho, I went ahead and updated the driver, and the adb status was online in the Kindle fire utility! Thinking this as awesome, i went ahead and installed the permanent boot with Superuser....thats when things went sour. I'm stuck at the KF logo, and my computer will not recognize it at all. I'm at a loss. I'd like to thank you in advance for any advice you could offer.
Here's the link to the walkthru I used just in case you need it: http://liliputing.com/2012/05/how-to-root-a-kindle-fire-with-software-version-6-3-1.html

When you turn the device on, what does the boot/Kindle Fire logo look like?

soupmagnet said:
When you turn the device on, what does the boot/Kindle Fire logo look like?
Click to expand...
Click to collapse
It's the standard Kindle Fire logo. The stock one.

Try this first...
http://forum.xda-developers.com/showthread.php?p=24682610
...if it doesn't work, uninstall then reinstall your drivers and try again. If it still doesn't work, we'll look at other options.

soupmagnet said:
Try this first...
http://forum.xda-developers.com/showthread.php?p=24682610
...if it doesn't work, uninstall then reinstall your drivers and try again. If it still doesn't work, we'll look at other options.
Click to expand...
Click to collapse
My apologies about the wait! School is starting and registration is a pain that I've been dealing with for these past couple days. I just recently switched my major from chemistry to computer science, so I may be lacking in a few concepts relating to windows technicalities. I'm more familiar with Unix, so I ask that you bear with me, lol.
I'm afraid I'm having some troubles with the kf utility. I removed and had Windows automatically update the kindle drivers. I also used the drivers batch file on the kf utility itself, and when i attempt to run the utility, my adb status is offline, and my boot is unknown. How would I remedy this? is there anywhere on the forum you can point me to? I can't seem to find anything. I refuse to go back to that old tutorial. It probably wasn't the author, but still...

Unix?...As in actual Unix? Or are you talking about Unix based, like Linux or Mac? This would be a lot less painful if you would ditch the whole Windows/KFU idea and do it manually.

soupmagnet said:
Unix?...As in actual Unix? Or are you talking about Unix based, like Linux or Mac? This would be a lot less painful if you would ditch the whole Windows/KFU idea and do it manually.
Click to expand...
Click to collapse
By Unix, I mean Unix based. I'm forced to learn Unix commands for mpi programming and such, lol. I found a cool utility online t restore the kf back to factory settings, unrooted and all. I'm a little tensed up about it, so I think I'll chill out for a little while, and do a full root a little later down the line. Thank you so much for all of your help though. I'd still be stuck otherwise!

gavination said:
By Unix, I mean Unix based. I'm forced to learn Unix commands for mpi programming and such, lol. I found a cool utility online t restore the kf back to factory settings, unrooted and all. I'm a little tensed up about it, so I think I'll chill out for a little while, and do a full root a little later down the line. Thank you so much for all of your help though. I'd still be stuck otherwise!
Click to expand...
Click to collapse
I have the same problem, what utility did you utilize?

[Q] Kindle Fire on a Constant 30 sec Reboot w/NO recovery & NO Permissions

I cannot seem to get my kindle fire unbricked despite reading and trying all solutions I could find and/or think of. I've tried KFU, Kindle Fire Debricker/Unbricker, followed various tutorials, and even made my own factory cable all to no avail yet. My Kindle simply keeps rebooting itself into the stock OS 6.3.1 of amazons about every 30 seconds +/-. Nothing I do can/will change that. When it starts up it shows the kindle fire bootloader then onto the main "Home" screen where various notices come up stating that basically everything is NOT working and they've all failed miserably and horribly. Then onto the next reboot. There is no longer any sort of recovery as far as I can tell. I cant get it to respond to any sort of fastboot anythings. On the positive side I do have the drivers loaded and can use adb with it at will, including adb shell. But all that is just about pointless as any command I try and enter, it simply responds with something about me not having any rights to do anything. I'm pretty sure I know what happened, far as I can tell I was in TWRP recovery when I tried to flash the stock firmware from there and everything just failed. Anyhow, if anyone has any idea what so ever on what to try or where to look for an answer, I'd be eternally grateful. Or if any other info is wanted, just let me know. Thanks all for any advice given ahead of time.

http://forum.xda-developers.com/showthread.php?t=2120816
"That's a special kind of stupid. The kind that makes me laugh."

24861 said:
I cannot seem to get my kindle fire unbricked despite reading and trying all solutions I could find and/or think of.....On the positive side I do have the drivers loaded and can use adb with it at will, including adb shell. But all that is just about pointless as any command I try and enter, it simply responds with something about me not having any rights to do anything. I'm pretty sure I know what happened
Click to expand...
Click to collapse
Try right clicking and select run as administrator.
Sent from my Amazon Kindle Fire using Tapatalk HD

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2120816
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Not to be rude, but..... Any chance on any actual help? Like maybe what to do? mLike I previously said I already have a factory cable but have gotten no where with that. Thank you

24861 said:
Not to be rude, but..... Any chance on any actual help? Like maybe what to do? mLike I previously said I already have a factory cable but have gotten no where with that. Thank you
Click to expand...
Click to collapse
Sure, but I need to know a few things first...
Do you understand what the factory cable is for? Do you know how to use it?
Do you know what fastboot is and how to use it? If so, do you know how to use it to install recovery?
Do you have a general idea of what you need to accomplish to fix your KF? (see the link provided)
"That's a special kind of stupid. The kind that makes me laugh"

soupmagnet said:
Sure, but I need to know a few things first...
Do you understand what the factory cable is for? Do you know how to use it?
Do you know what fastboot is and how to use it? If so, do you know how to use it to install recovery?
Do you have a general idea of what you need to accomplish to fix your KF? (see the link provided)
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
In general....... yes.
Factory cable is simply to put it in fastboot (although I dont know that it does on mine).
I do know what fastboot is and can type in the needed commands if you'd be willing to tell me, though I know a couple.
And yes, Im looking to install TWRP and then flash a stock rom and stock recovery.... I believe.
Then again, all that is probably wrong, ergo why I ask you sir.
Thank you

24861 said:
In general....... yes.
Factory cable is simply to put it in fastboot (although I dont know that it does on mine).
I do know what fastboot is and can type in the needed commands if you'd be willing to tell me, though I know a couple.
And yes, Im looking to install TWRP and then flash a stock rom and stock recovery.... I believe.
Then again, all that is probably wrong, ergo why I ask you sir.
Thank you
Click to expand...
Click to collapse
Okay...
When you plug your powered off Kinlde Fire into the computer with the factory able, it should boot directly to fastboot. Meaning, it will stay at a bright Kindle Fire logo and not go dim or flash.
Anything outside of that would make me wonder if your factory cable is defective (probably not likely) or your battery is near dead. The 30 second reboot is a good indicator of the latter, although that particular situation usually results in a much faster reboot loop (5-10 seconds).
Plug your device into your stock charger and immediately hold the power button down until it shuts off. Then let it charge for a while then try again later.

soupmagnet said:
Okay...
When you plug your powered off Kinlde Fire into the computer with the factory able, it should boot directly to fastboot. Meaning, it will stay at a bright Kindle Fire logo and not go dim or flash.
Anything outside of that would make me wonder if your factory cable is defective (probably not likely) or your battery is near dead. The 30 second reboot is a good indicator of the latter, although that particular situation usually results in a much faster reboot loop (5-10 seconds).
Plug your device into your stock charger and immediately hold the power button down until it shuts off. Then let it charge for a while then try again later.
Click to expand...
Click to collapse
Okay. So far so good. Is doing just what you said, except for I evidently have no fastboot driver installed. Plus it doesnt recognize that the fire is plugged in (in fastboot mode) inside the device manager. So....? Is there a specific driver (fastboot driver) that I need to load (and do you have it?) and how do I get the fire to atleast become recognized?
Thanks again bud

That may not necessarily be the case. What color is your Kindle Fire logo?
"That's a special kind of stupid. The kind that makes me laugh"

soupmagnet said:
That may not necessarily be the case. What color is your Kindle Fire logo?
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
Its white and orange. Although I believe my current issue is that it is stuck in fastboot (4002) mode. Even though it still reboots into normal mode, it remains stuck in fastboot. And I am unsure as to how to get it back as nothing will recognize it, so no drivers will ever install. So I am currently trying to let it run dry of juice in hopes it will reset when its dead. Any ideas?

Don't let the battery die!
I'll tell you what you need to do later when I have more time. In the meantime, keep it turned off.
"That's a special kind of stupid. The kind that makes me laugh"

Draining Is never a good idea. It`s very common for the stock bootloader to be difficult to detect even more so now after there recent update in the past few months, because Amazon tampered with the bootloader enough to cause some people issues.

soupmagnet said:
Don't let the battery die!
I'll tell you what you need to do later when I have more time. In the meantime, keep it turned off.
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
okay. Waiting on you. Thanks

Thepooch said:
Draining Is never a good idea. It`s very common for the stock bootloader to be difficult to detect even more so now after there recent update in the past few months, because Amazon tampered with the bootloader enough to cause some people issues.
Click to expand...
Click to collapse
Just had stock bootloader drivers all installed and what not before I started in with the factory cable (thereby putting it in fastboot (4002) mode.

24861 said:
Just had stock bootloader drivers all installed and what not before I started in with the factory cable (thereby putting it in fastboot (4002) mode.
Click to expand...
Click to collapse
Agreed it`s still normal to be undetected by kfu how does it show in device manager?

24861 said:
Just had stock bootloader drivers all installed and what not before I started in with the factory cable (thereby putting it in fastboot (4002) mode.
Click to expand...
Click to collapse
So far everything seems to be working the way it's supposed to.
Using the factory cable to get into fastboot, type the following command and hit enter:
Code:
fastboot getvar product
When you see "waiting for device", hold the power button to turn the device off. Unplug then replug the factory cable to boot the device back into fastboot. When it boots, you should see an output of "kindle" in the command window.
If that works, do the same thing for the commands to install recovery and change the bootmode.
If you really want to go back to stock, do what you did previously, only this time be sure to do a "factory reset" before installing the update.zip.

soupmagnet said:
So far everything seems to be working the way it's supposed to.
Using the factory cable to get into fastboot, type the following command and hit enter:
Code:
fastboot getvar product
When you see "waiting for device", hold the power button to turn the device off. Unplug then replug the factory cable to boot the device back into fastboot. When it boots, you should see an output of "kindle" in the command window.
If that works, do the same thing for the commands to install recovery and change the bootmode.
If you really want to go back to stock, do what you did previously, only this time be sure to do a "factory reset" before installing the update.zip.
Click to expand...
Click to collapse
Nothing doin' there champ......... just same old "waiting for device" followed to a tee, but nada. Anything else?

Make sure you're using a 2.0 usb port.

I assuredly am using a 2.0 USB port, but still nada. Anything else anybody? Please.................

So.... back to where I was (I had to switch PC's though). I can get adb running just fine. I can getshell even. But cant do much with as all permissions seem denied. And I have continuous access to the sd card as its always mounted it seems, even thru every restart. So...... what to do now?

[Q] Kindle Fire 2 completely bricked after flashing wrong bootloader.

Hi. So the other day I installed TWRP on my Kindle Fire successfully. The KF was at 10.2.6, I'm not sure if that means it's a Kindle Fire 2 or not. Anyways, when I went to flash FFF, I stupidly flashed the .zip as a bootloader, thus making my Kindle Fire completely unusable. When I press the power button, nothing at all happens. Nothing I do will make the screen turn on or the power button to flash in any way. I've tried using Firekit with usbboot and the shorting trick, but that hasn't worked for me. (I just installed stock Ubuntu to a flash drive with the fk file on root, I'm fairly certain that's all that needed to be done?)
Anyways, my Kindle is unresponsove, and the usbboot trick has yet to work for me. I really want to save this guy. I've heard the KF cannot be completely bricked through software/flashing. I hope it's true! Any help would be greatly appreciated. Thank you.

if that is your software version then yes you have kindle fire 2, i'd wait for someone with more experience on here to post, but it sounds to me like you are going to need a factory cable

chris_m128 said:
if that is your software version then yes you have kindle fire 2, i'd wait for someone with more experience on here to post, but it sounds to me like you are going to need a factory cable
Click to expand...
Click to collapse
Thanks fro replying. I'm pretty sure a factory cable only puts it into fastboot if you have a working bootloader. I don't, so I don't think it would work.

I remember an instance where a friend of mine had a broken bootloader, and we used a factory cable to restore it, this was on the kindle fire. we had to first reflash the bootloader. I hope this is possible here.
---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------
but you'll have to ask someone with more experience than me sorry.

jophish said:
Hi. So the other day I installed TWRP on my Kindle Fire successfully. The KF was at 10.2.6, I'm not sure if that means it's a Kindle Fire 2 or not. Anyways, when I went to flash FFF, I stupidly flashed the .zip as a bootloader, thus making my Kindle Fire completely unusable. When I press the power button, nothing at all happens. Nothing I do will make the screen turn on or the power button to flash in any way. I've tried using Firekit with usbboot and the shorting trick, but that hasn't worked for me.
Click to expand...
Click to collapse
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
From there you would probably have to push one of the 10.1 ROMs on, or the 10.2.6 recovery image, and then start again.
This seems to be happening a lot, and could be avoided if people read a bit more before using the wrong tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD

chronicfathead said:
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
Click to expand...
Click to collapse
Howdy. I just fashioned a factory cable, just jumping +5V to pin 4, right? It seems to be doing absolutely nothing. No lights or anything are turning on. The freedom boot just spits out "error: device not found" and hangs on "Pushing Stack". Again, I was under the impression that the factory cable only made it boot in fastboot if you already have a working bootloader. I'll try loading into Ubuntu and see what it says in terminal. Thanks
EDIT: So, when I type adb devices into terminal, I get:
The program 'adb' is currently not installed. You can install it by typing:
sudo apt-get install android-tools-adb
You will have to enable the component called 'universe'
Could this have been my problem to begin with?
EDIT 2: Well, I installed ADB. There are no devices found when I enter that command, and the shorting trick with still doesn't work. Ugh.

jophish said:
Howdy. I just fashioned a factory cable, just jumping +5V to pin 4, right? It seems to be doing absolutely nothing. No lights or anything are turning on. The freedom boot just spits out "error: device not found" and hangs on "Pushing Stack". Again, I was under the impression that the factory cable only made it boot in fastboot if you already have a working bootloader. I'll try loading into Ubuntu and see what it says in terminal. Thanks
EDIT: So, when I type adb devices into terminal, I get:
The program 'adb' is currently not installed. You can install it by typing:
sudo apt-get install android-tools-adb
You will have to enable the component called 'universe'
Could this have been my problem to begin with?
EDIT 2: Well, I installed ADB. There are no devices found when I enter that command, and the shorting trick with still doesn't work. Ugh.
Click to expand...
Click to collapse
Leave your Kindle plugged in for an hour using the normal cable, as it may be totally flat.
The attached diagram shows what pins need joining. If you can, make sure none of the other pins are shorting.
Hold the power button for 20 seconds, plug in your fastboot cable, power on the Kindle.
You should see some traffic lights on the screen.
If you can get fastboot enabled, you should be able to push the correct partitions back on using the partitions from the factory restore image, your backup files or from the recovery thread. Hope you get it running.
Sent from my Amazon Kindle Fire2 using Tapatalk HD

chronicfathead said:
Leave your Kindle plugged in for an hour using the normal cable, as it may be totally flat.
The attached diagram shows what pins need joining. If you can, make sure none of the other pins are shorting.
Hold the power button for 20 seconds, plug in your fastboot cable, power on the Kindle.
You should see some traffic lights on the screen.
If you can get fastboot enabled, you should be able to push the correct partitions back on using the partitions from the factory restore image, your backup files or from the recovery thread. Hope you get it running.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
I tried the fastboot cable out on a working Kindle Fire, and it worked correctly, so I did wire it right. I did as you said, holding the power button down and then plugging in the cable, and nothing happens still on the KF2. I have access to the insides, should I unplug the battery? It should be around 85% charged. Thanks again.
Edit: BIG NEWS~ Not really. When I plug the Kindle Fire with the fastboot cable into Windows, it appears under Device Manager as "Unknown Device" with a yellow triangle, but nothing shows up on the Kindle, no lights or anything. Hmph.

jophish said:
I tried the fastboot cable out on a working Kindle Fire, and it worked correctly, so I did wire it right. I did as you said, holding the power button down and then plugging in the cable, and nothing happens still on the KF2. I have access to the insides, should I unplug the battery? It should be around 85% charged. Thanks again.
Edit: BIG NEWS~ Not really. When I plug the Kindle Fire with the fastboot cable into Windows, it appears under Device Manager as "Unknown Device" with a yellow triangle, but nothing shows up on the Kindle, no lights or anything. Hmph.
Click to expand...
Click to collapse
You could have tried sending it back to Amazon, but you say you have opened it.
Sent from my Amazon Kindle Fire2 using Tapatalk HD

chronicfathead said:
You could have tried sending it back to Amazon, but you say you have opened it.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Urgh. I closed it up. Is there any way they'd know if I'd opened it?

I'm in exactly the same boat as you, also flashed FFF (by accident) on my device. Haven't been able to fix it yet but I do have a factory cable. Also did the USB trick, but that didn't have an effect either.
chronicfathead said:
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
From there you would probably have to push one of the 10.1 ROMs on, or the 10.2.6 recovery image, and then start again.
This seems to be happening a lot, and could be avoided if people read a bit more before using the wrong tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
In my case, I did by accident because it wasn't clear to me which KF generation I had (I've bricked mine just after christmas). These forums were not really clear either, I had a Kindle Fire so I just looked for a KF guide. After I bricked it I found out my device was a second generation Kindle Fire.

plinders said:
I'm in exactly the same boat as you, also flashed FFF (by accident) on my device. Haven't been able to fix it yet but I do have a factory cable. Also did the USB trick, but that didn't have an effect either.
In my case, I did by accident because it wasn't clear to me which KF generation I had (I've bricked mine just after christmas). These forums were not really clear either, I had a Kindle Fire so I just looked for a KF guide. After I bricked it I found out my device was a second generation Kindle Fire.
Click to expand...
Click to collapse
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...

Same Here..
I was thinking that all kindle fire are the same... installed fire fire fire using KFU and device got bricked....!
Hope someone here could help us get our devices up and running again...

yudanjah said:
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Click to expand...
Click to collapse
Nothing whatsoever.
I can't really send it back to Amazon, because of two reasons:
1) I already opened up the back
2) It was gifted to me from the US, and there is no Dutch Amazon, so I'd have to send the device back to the person who gifted to me, that person has to mail it to Amazon from there, and the replacement device has to come back the same way (via that person). That's not a situation I'd like to put that person in.

jophish said:
Urgh. I closed it up. Is there any way they'd know if I'd opened it?
Click to expand...
Click to collapse
I am sure they can figure it out. Can you boot into TWRP?
If so, you can still recover...

Dame problem
plinders said:
Nothing whatsoever.
I can't really send it back to Amazon, because of two reasons:
1) I already opened up the back
2) It was gifted to me from the US, and there is no Dutch Amazon, so I'd have to send the device back to the person who gifted to me, that person has to mail it to Amazon from there, and the replacement device has to come back the same way (via that person). That's not a situation I'd like to put that person in.
Click to expand...
Click to collapse
Same problem dude, did you fix it?

i.robert said:
Same problem dude, did you fix it?
Click to expand...
Click to collapse
Not yet I'm afraid. Everything I tried so far hasn't worked.

yudanjah said:
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Click to expand...
Click to collapse
No, Absolutely nothing. I really would like to get this working.

jophish said:
No, Absolutely nothing. I really would like to get this working.
Click to expand...
Click to collapse
same here we need a new firekit for the kf2

Help..
any updates on the fix? I hope someone out there could help us revive our bricked kindle fire 2... :angel:
kindle fire 2
flashed wrong bootloader (fff)
no power
no lights
no adb
shorting trick is not working for me :crying:

Think I killed my fire TV

I followed the AFTV guide to a T. Flashed 51.1.4.0, had the boot menu, CWM and everything was golden. Pushed 51.1.5.3 to the SD, rebooted to CWM, flashed, now stuck in a loop. I cant even connect to it with the adb connect command. Am I screwed? Is this thing done? I dont understand. It doesnt even show the boot menu anymore. Just straight to the looping firetv logo. Was i supposed to reflash the boot menu after installing prerooted 51.1.4.0? This sucks if it's done for.....

Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/

Calibaan said:
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Click to expand...
Click to collapse
Thanks man. Hopefully one of those methods works. I've been at this for 4 hours carefully working my way through every single step. The highest high of the one last flash to go, turning into the gut wrenching sickness of a boot loop is too much for tonight and I'll try tomorrow.
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.

supremekizzle said:
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
Click to expand...
Click to collapse
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.

AFTVnews.com said:
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
Click to expand...
Click to collapse
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?

supremekizzle said:
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
Click to expand...
Click to collapse
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.

AFTVnews.com said:
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
Click to expand...
Click to collapse
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?

supremekizzle said:
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
Click to expand...
Click to collapse
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)

AFTVnews.com said:
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
Click to expand...
Click to collapse
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!

supremekizzle said:
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
Click to expand...
Click to collapse
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
supremekizzle said:
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
Click to expand...
Click to collapse
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.

AFTVnews.com said:
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
Click to expand...
Click to collapse
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.

supremekizzle said:
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
Click to expand...
Click to collapse
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.

AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!

AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
Any suggestions?:
http://forum.xda-developers.com/fire-tv/help/fire-tv-boots-white-amazon-logo-screen-t3139511
supremekizzle,
Glad it worked out for you.:good:

supremekizzle said:
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
Click to expand...
Click to collapse
Glad it all worked out and glad I could help!
For future reference, when you edit a post, it doesn;t trigger XDA to send out a notification to the user you're quoting (me). That's why I didn't respond to your last message until now (when I manually checked it). Post a reply and use the '@' symbol (like this: @supremekizzle ) to ensure the user gets notified.