Develop Bugs

[Q] Kindle stuck at static Kindle Fire logo

Hello all,
I need some help and guidance in fixing my Kindle Fire. Some background:
My Kindle Fire was on 6.3.1 when I rooted it, no custom roms, just root so I can get Google Framework on it since I use Google Docs and the Google Market. After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
I had FFF and TWRP on my Kindle Fire as well, running Windows 7 64bit Home Premium
After much searching, every unroot guide kept pointing me back to flashing the stock rom. So I downloaded the latest update.zip through KFU, booted into TWRP, wiped, installed the update.zip, and rebooted.
After that, I hit the Kindle Fire logo, static, and it hangs there. I power off and on, still hangs. I don't have the blue/white FFF recovery anymore so booting into recovery wasn't an option. I then connected the Kindle to my computer, opened KFU, and tried to change the boot option through option 1, and every time I change it, Fastboot, Normal boot, etc. it sends the command, Kindle reboots, but then hangs again on the static logo.
I tried reinstalling FFF and TWRP through KFU to try and reflash, but it shows as preparing, then waiting for device, and nothing. Again, just hanging.
I even tried the manual shell commands I've seen around the forums and in the Kindle Fire for Beginners Guide, but I keep hanging on "Waiting for device" in the cmd prompt.
I don't know what else to do and I'm becoming more confused with the different types of issues that everyone is reporting, with each one have one detail different from my situation. I had no custom roms, just a root, and it seems I may have flashed a bad stock rom.
Any help is greatly appreciated. I apologize if this was solved somewhere else, but I searched numerous threads and guides, but they all dealt with something going wrong with a custom rom or people getting to the animated Kindle Fire logo, where as mine is just static.
Again, thank you for your time.

Sounds like it's stuck in fastboot bootmode to this noob. I had the same problem at one point and used command line to fix with the simple bootmode switching commands - can't recall if I used fastboot or adb tools..but either should work. And if I'm reading your post right, you've tried these so this is likely above my meager skill level, heh. You are handling it better than I did, I might add.
If I may point out where you went wrong:
Mattamus Prime said:
After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
Click to expand...
Click to collapse
There are apps in the Google Play store that will temporarily remove your root status so you are able to use services that detect and shut down when root is detected. OTArootkeeper.apk is one that I've heard of.
And don't ever chose to lose fff once you have that as this is your lifeline to unbricking.
Hopefully someone with better chops than I on this will post up - continue with your patient reading and take a little comfort that this is most probably fixable.

First off, I applaud you for trying to figure out and fix the problem yourself using the guides available. Thank you. The information you provided will go a long way to getting the help you need.
So far it seems you've done everything right, but to be sure, you should check to make sure your drivers are in order (most likely the problem). The second post of the Beginners Guide will help you with that.
Once you have done that and you still can't change your bootmode, try using recovery to flash a custom rom. It's possible the stock boot image you have has been corrupted. You can use the "mount" function in recovery to push another rom to your sdcard. If that works you can stick with a custom rom like MoDaCo. It's the same stock stock interface with Google apps and services installed and you don't have to worry about OTA updates. OTA Rootkeeper will let you easily switch between "rooted" and "unrooted" so you can take advantage of Amazon's VOD.
And if you still want pure stock you can d/l a new copy of the update and try again.

Thanks for the suggestion. I did try OTA Rootkeeper, but when I went into my Instant VOD, it still had the buttons grayed out. I tried temp unroot, reboot Kindle, and still grayed out, so I assumed Rootkeeper wasn't working for me, thus, the looking for the unroot tutorials.
A little bit of extra information, when I hook up my Kindle Fire, my drivers says Android Composite ADB Interface. When I try to switch to Fastboot to have it switch to Android ADB Interface, it doesn't switch. It just stays as Composite.
Thanks again.

soupmagnet said:
So far it seems you've done everything right, but to be sure, you should check to make sure your drivers are in order (most likely the problem). The second post of the Beginners Guide will help you with that.
Click to expand...
Click to collapse
I followed the advice in the Beginners Guide, uninstalled whatever drivers I had, rebooted my comp, then installed the ones that came with the KFU download.
Are there any other drivers I should be looking for?
Also, a little bit of more information, I tried switching to Fastboot through KFU, received some messages to the effect of "system/some file name file not found (2)", (I apologize for not being specific, typing from memory), it then reboots my Kindle Fire, then I execute the commands:
fastboot getvar product
After that, it just says <waiting for device>
In fact, after any command I do in cmd, I get that message. So I believe it may be a driver issue, like was suggested, or my Kindle isn't far enough into the boot process to be found.

It definitely sounds like a driver issue. Keep working on your drivers.
If that doesn't work, you can try it on a different computer OR set up a Linux LiveUSB for issuing adb/fastboot commands.

FIX for Kindle stuck on logo
Finally I FIXED MY KINDLE FIRE!!!!
Issue : Kindle Fire stuck on 'Kindle Fire' logo and never moves after that.
Hello All,
Just like others in here, even I tried to upgrade to new version of Android on my kindle and I messed it up very bad.
I have read a post where, some-one just updated that it is because we have enabled fast boot on it and we need to move to regular boot.
However, none of the solutions suggest on this website worked for me (am not saying my friends are wrong in here).
Finally the work around that WORKED for me, and am sure this will be help you all.
When you are wiping/erasing the data/SD card, please do not wide the ROM. If you delete the ROM - Booom!!, you are cutting off the branch yo are
sitting ON )
Now if you have already done that.. please follow the steps.
You have intall/upgrade to a new version of Android.
Make sure you have the TWRP 2.1.x or 2.2.0 installed << which you will have, using that only you wiped off your kindle )
Now download the latest version of Andriod Jelly Bean and Google app on your computer from the following link
http://forum.xda-developers.com/showthread.php?t=1778010
1. Now, boot ur kindle into recovery.
2. Connect your kindle to your computer, if the computer recongnise your kindle paste both files onto kindle, and move to step 6
3. If your kindle is not recognized (like in my case), go to mount option in recovery
4. Choose mount USB
5. Kindle will be recognized in computer, and copy the files.
6. Disconnect Kindle from the computer
7. Wipe data/factory reset
8. Wipe cache
9. Wipe dalvik
10. Install ROM <install Andriod Jelly Bean> Do not install Google Apps
11. Reboot
Once you do a normal reboot, your system will boot into Andriod Jelly Bean edtion. Go to file manager and reach out to Google Apps and install the
application and reboot.
Yes!! you have the complete recoved Kindle
Only known issue - Your battery bar will not move when it is charging (but actually it is charging).
#####################################################################################################
MattamusPrime said:
Hello all,
I need some help and guidance in fixing my Kindle Fire. Some background:
My Kindle Fire was on 6.3.1 when I rooted it, no custom roms, just root so I can get Google Framework on it since I use Google Docs and the Google Market. After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
I had FFF and TWRP on my Kindle Fire as well, running Windows 7 64bit Home Premium
After much searching, every unroot guide kept pointing me back to flashing the stock rom. So I downloaded the latest update.zip through KFU, booted into TWRP, wiped, installed the update.zip, and rebooted.
After that, I hit the Kindle Fire logo, static, and it hangs there. I power off and on, still hangs. I don't have the blue/white FFF recovery anymore so booting into recovery wasn't an option. I then connected the Kindle to my computer, opened KFU, and tried to change the boot option through option 1, and every time I change it, Fastboot, Normal boot, etc. it sends the command, Kindle reboots, but then hangs again on the static logo.
I tried reinstalling FFF and TWRP through KFU to try and reflash, but it shows as preparing, then waiting for device, and nothing. Again, just hanging.
I even tried the manual shell commands I've seen around the forums and in the Kindle Fire for Beginners Guide, but I keep hanging on "Waiting for device" in the cmd prompt.
I don't know what else to do and I'm becoming more confused with the different types of issues that everyone is reporting, with each one have one detail different from my situation. I had no custom roms, just a root, and it seems I may have flashed a bad stock rom.
Any help is greatly appreciated. I apologize if this was solved somewhere else, but I searched numerous threads and guides, but they all dealt with something going wrong with a custom rom or people getting to the animated Kindle Fire logo, where as mine is just static.
Again, thank you for your time.
Click to expand...
Click to collapse

K_Krish said:
Finally I FIXED MY KINDLE FIRE!!!!
Issue : Kindle Fire stuck on 'Kindle Fire' logo and never moves after that.
Hello All,
Just like others in here, even I tried to upgrade to new version of Android on my kindle and I messed it up very bad.
I have read a post where, some-one just updated that it is because we have enabled fast boot on it and we need to move to regular boot.
However, none of the solutions suggest on this website worked for me (am not saying my friends are wrong in here).
Finally the work around that WORKED for me, and am sure this will be help you all.
When you are wiping/erasing the data/SD card, please do not wide the ROM. If you delete the ROM - Booom!!, you are cutting off the branch yo are
sitting ON )
Now if you have already done that.. please follow the steps.
You have intall/upgrade to a new version of Android.
Make sure you have the TWRP 2.1.x or 2.2.0 installed << which you will have, using that only you wiped off your kindle )
Now download the latest version of Andriod Jelly Bean and Google app on your computer from the following link
http://forum.xda-developers.com/showthread.php?t=1778010
1. Now, boot ur kindle into recovery.
2. Connect your kindle to your computer, if the computer recongnise your kindle paste both files onto kindle, and move to step 6
3. If your kindle is not recognized (like in my case), go to mount option in recovery
4. Choose mount USB
5. Kindle will be recognized in computer, and copy the files.
6. Disconnect Kindle from the computer
7. Wipe data/factory reset
8. Wipe cache
9. Wipe dalvik
10. Install ROM <install Andriod Jelly Bean> Do not install Google Apps
11. Reboot
Once you do a normal reboot, your system will boot into Andriod Jelly Bean edtion. Go to file manager and reach out to Google Apps and install the
application and reboot.
Yes!! you have the complete recoved Kindle
Only known issue - Your battery bar will not move when it is charging (but actually it is charging).
#####################################################################################################
Click to expand...
Click to collapse
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.

me too
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
I am stuck at the very same place you are. I was in an endless bootloop after trying to flas back to the Stock Amazon ROM using TWRP. Once i got the drivers sorted out and ADB could see my device i used KFU to "Install permanent Root with Superuser". The KF went to reboot into fastboot and the screen said "waiting for device" for about ten minutes. Now the KF is stuck at the white and orange "kindle Fire" boot logo. Windows will no longer see the KF as an android device. It only shows up as an "unknown device" in the device manager.

Try this
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
Ok, I dont know, how to fix this (as I was not in this situation). Try following the steps - Download update.zip through KFU. Connect your Kindle to PC and install the android driver. If your PC detects the kindle copy update.zip file to kindle and try to install that.

sounds like a job for this http://forum.xda-developers.com/showthread.php?t=1392693&highlight=info

dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
Im in the same boat you are. I have tried everything stuck on same logo device is recognized in devices as android phone and adb interface but cannot connect to unbrick utility or KFU and doesnt show as a drive either. tried to search devices in cmd using fastboot commands and nothing shows either. I decided to purchase a factory cable today on ebay. Keeping my fingers crossed because after reading everything I could find I think it is my only option.

No, your problem is as "simple" as fixing your drivers so the computer can communicate with the device through adb and fastboot. KFU relies on those two tools to do pretty much anything. Unfortunately, Windows is stupid and is not very effective when dealing with certain USB devices.
In order to, say, install TWRP, you need adb to change the bootmode to accept fastboot commands, and use fastboot commands to overwrite the recovery partition. In the process of going between different boot modes, Windows had a hissy fit and decides not to communicate with the device at all. Hence the need to fix/reinstall the drivers. It doesn't always work out that way and you get stuck where you are right now. A factory cable will put you in fastboot, but it wont make Windows communicate with the device. You can continue to fight with Windows drivers and hope to get lucky, or you could try other, more effective options...
http://forum.xda-developers.com/showpost.php?p=30629067

omg .... I survived a bricking. Soupkit saved me!!!
Somewhere on the many tabs I have open, as I frantically search for ways to unbrick my Kindle fire... I run into " SoupKit" for Linux ... install it... mess around with the Bootloader .. change it to 4002 I believe the value was ... my Kindle that I've been working on for literally 6 hrs is back on! ... now on the figuring out how to root it / remove demo software. SOUPKIT!
E]

[Q] Kindle Fire Really bricked

Please, please, really, help me out. My kindle fire is bricked, I tried Unbrick tool and a lot of other things, like installing again the drivers, the sdk, but nothing works at all!!
Here is the thing: When I was rooting my Kindle, my building got a blackout during the root process, and when the light goes on, my kindle was stucked on "Kindle Fire" logo. When I use adb devices, nothing shows. When I connect to Windows, it shows as a Unknown device, and when I try to install adb composite, it give a message saying that the driver android_winusb is not compatible with the hardware connected to USB. So, I can now really use this brand new Kindle Fire as a brick? I bought it on june 06 2012 !!!!!! Please, help me with this.. please..
Thank you very much

I was in the same place yesterday
Uninstall the unknown usb driver
Unplug kindle from usb
Reboot pc
Install drivers from kindle fire utility using the install_drivers bat
Plug kindle in, should recognize as adb device (if it shows up as a kindle uninstall those and reboot)
You may need to use kfu to get into normal bootmode if stuck in fastbook onc the drivers are set
Sent from my DROID BIONIC using XDA

Stuck in Kindle Fire logo mostly means your your KF is in fast boot mode. Try unplug your KF, get the latest KFU and reinstall drivers, reboot pc and reconnect KF.
Open KFU and select normal boot mode.
Sent from my iPad using Tapatalk HD

Thank you for the answers, but it is still not working. I did everything you told me, but its not working. My Windows 7 set the device as unknown. When I set it to normal boot mode, the program starts to wait for the device that is already pluged in.

kindle fire bricked at all
What else can I do? I have tried on Mac, on Linux and Windows, but its not working in any of these systems.

zocas said:
What else can I do? I have tried on Mac, on Linux and Windows, but its not working in any of these systems.
Click to expand...
Click to collapse
First figure out where it's getting stuck in the boot process. If the bootlogo appears on the display and stays that way without ever blacking out, then it's in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=1668159
If it does go black before showing the bootlogo again, then it's no longer in fastboot mode and its trying to boot into something. In this case, you'll have to hope that it's getting far enough into the boot process that it can accept adb commands from your computer.
Either way, you'll have to make sure the drivers are working properly.
http://forum.xda-developers.com/showthread.php?t=1552547
The second one covers drivers, but the first 3 posts in general should be helpful to you. If it's not in fastboot mode and you can't get it to execute adb commands, you can either get a factory cable or open up the back cover on the device and use Firekit.

[Q] Bricked My Wife's Kindle

I was using [REF] Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial and had gotten to step 3 of the guide where I downloaded the recovery and boot img's and put them onto the device. I had the device rooted fine, installed FireFlash, selected both the files in the correct places, and selected the check box for flashing bootloader 8.1.4. I did however fail to select "apply stack", which is where I'm assuming I made my fatal mistake. I proceeded to hit flash and it then rebooted into TWRP. I thought I had done everything successfully as far as I could tell. Made some backups with TWRP and then went to reboot but it froze on the kindle fire logo.
I should have made backups with the command adb pull before proceeding but it didn't work for me the first time so I gave up. Probably should have done that properly. But I've been trying to use KFFirstAide and KFHD SRT to at least get it to a working state. But I've had no success trying to get the device into fastboot. The device will show up momentarily in device manager as jem something and then disappears after connecting the usb cable from a turned off state. The only thing I can do with the device at the moment is getting the orange kindle fire logo to turn on and off by holding the power button. I feel like I have some sort of idea about going to environment variables and editing paths to point it to the folder with adb and fastboot, along with having the correct drivers. Well, I don't know about the drivers cause I've tried two different ones. I'm clueless at this point and could use some help.

Try installing the drivers in my signature for the jem device as soon as it shows up, then when that's done, shut the device off, and run your fastboot command as follows: fastboot -i 0x1949 getvar product
Once it says waiting for device plug you kindle in while its off, and you should go into fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Just one question, how do I install those drivers in your signature? I've seen you help out a lot of the members here so I appreciate it.

You open the device manager, and when your PC detects a jem device, right click it and hit update driver and point it to where you extracted the zip file.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Damn that worked like a dream. Its working once again and I can start the process from scratch. You kick ass man!

Help! Possibly bricked Kindle Fire HD 8.9

Hey everyone
I think I've just bricked brand new Kindle Fire HD 8.9 :/
So, I'm new in rooting and I tried to install custom rom Cyanogen Mod 10.1 following the instructions from there: http://rootkindlefire.com/kindle-fi...-kindle-fire-hd-8-9-into-pure-android-tablet/ .
After rooting Kindle, installing 2nd bootloader and TWRP my Kindle rebooted. It showed up Kindle Fire logo, first yellow then blue one. But after that nothing happened, it stucked at booting. So I entered to recovery mode by holding down volume up button and because of my stupidity I thought backing up system and restoring it will get me able to enter to original Amazon's system. After restoring system and rebooting worse thing happened. Logo while booting didn't turn from yellow to blue, it just stucked in yellow logo like it freezed. Now I can't enter anywhere in my Kindle, even in recovery mode and after plugging Kindle to PC through USB cable PC doesn't see Kindle. I think maybe using fastboot cable will help but I'm not sure about that, so I'm asking You: Is there anything I can do to restore my Kindle? And the fastboot cable will work with this software: http://forum.xda-developers.com/showthread.php?t=2011126?
Thanks for any help
Sorry for my bad english

Gunter_Time said:
Hey everyone
I think I've just bricked brand new Kindle Fire HD 8.9 :/
So, I'm new in rooting and I tried to install custom rom Cyanogen Mod 10.1 following the instructions from there: http://rootkindlefire.com/kindle-fi...-kindle-fire-hd-8-9-into-pure-android-tablet/ .
After rooting Kindle, installing 2nd bootloader and TWRP my Kindle rebooted. It showed up Kindle Fire logo, first yellow then blue one. But after that nothing happened, it stucked at booting. So I entered to recovery mode by holding down volume up button and because of my stupidity I thought backing up system and restoring it will get me able to enter to original Amazon's system. After restoring system and rebooting worse thing happened. Logo while booting didn't turn from yellow to blue, it just stucked in yellow logo like it freezed. Now I can't enter anywhere in my Kindle, even in recovery mode and after plugging Kindle to PC through USB cable PC doesn't see Kindle. I think maybe using fastboot cable will help but I'm not sure about that, so I'm asking You: Is there anything I can do to restore my Kindle? And the fastboot cable will work with this software: http://forum.xda-developers.com/showthread.php?t=2011126?
Thanks for any help
Sorry for my bad english
Click to expand...
Click to collapse
(if you're bricked, you need fastbootcable?). that what i was told anyways

OK good news, you don't need a fastboot cable, in fact they don't even work on 8.9" models. The only problem is if you never have put the device in fastboot before while plugged into windows you are going to have a fun time trying to install the drivers... More or less plug the device is while it is off and have the device manager open already, you should see a jem device with a yellow triangle pop up for a moment, this is what you have to do, download the drivers in my signature and extract them somewhere. Now when that device pops up briefly, right click it, hit update drivers, and point it to where you extracted my drivers. If you can successfully complete this step the rest is easy, you just need to download a utility, like the one you asked if it would fix it(the answer is yes BTW). Extract the utility from its' zip file, hold shift and right click the folder that was extracted and hit "open command window here". Now with the device turned off and unplugged type this
Code:
fastboot -i 0x1949 getvar product
Press enter, once it says waiting for device then plug the kindle in while its off, it should go into fastboot. Once in fastboot you can use the SRT utility to fix it or kffa if you prefer.
Post above mine also makes skipping the entire try-to-install-driver-while-disappearing problem go away, instead you would reboot into windows after it goes into fastboot, still install the driver, and just run SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
OK good news, you don't need a fastboot cable, in fact they don't even work on 8.9" models. The only problem is if you never have put the device in fastboot before while plugged into windows you are going to have a fun time trying to install the drivers... More or less plug the device is while it is off and have the device manager open already, you should see a jem device with a yellow triangle pop up for a moment, this is what you have to do, download the drivers in my signature and extract them somewhere. Now when that device pops up briefly, right click it, hit update drivers, and point it to where you extracted my drivers. If you can successfully complete this step the rest is easy, you just need to download a utility, like the one you asked if it would fix it(the answer is yes BTW). Extract the utility from its' zip file, hold shift and right click the folder that was extracted and hit "open command window here". Now with the device turned off and unplugged type this
Code:
fastboot -i 0x1949 getvar product
Press enter, once it says waiting for device then plug the kindle in while its off, it should go into fastboot. Once in fastboot you can use the SRT utility to fix it or kffa if you prefer.
Post above mine also makes skipping the entire try-to-install-driver-while-disappearing problem go away, instead you would reboot into windows after it goes into fastboot, still install the driver, and just run SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I did everything like you said, and voila! Kindle works fine now
Thanks for the help

stunts513 said:
OK good news, you don't need a fastboot cable, in fact they don't even work on 8.9" models. The only problem is if you never have put the device in fastboot before while plugged into windows you are going to have a fun time trying to install the drivers... More or less plug the device is while it is off and have the device manager open already, you should see a jem device with a yellow triangle pop up for a moment, this is what you have to do, download the drivers in my signature and extract them somewhere. Now when that device pops up briefly, right click it, hit update drivers, and point it to where you extracted my drivers. If you can successfully complete this step the rest is easy, you just need to download a utility, like the one you asked if it would fix it(the answer is yes BTW). Extract the utility from its' zip file, hold shift and right click the folder that was extracted and hit "open command window here". Now with the device turned off and unplugged type this
Code:
fastboot -i 0x1949 getvar product
Press enter, once it says waiting for device then plug the kindle in while its off, it should go into fastboot. Once in fastboot you can use the SRT utility to fix it or kffa if you prefer.
Post above mine also makes skipping the entire try-to-install-driver-while-disappearing problem go away, instead you would reboot into windows after it goes into fastboot, still install the driver, and just run SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
hey i cannot kind a download for this tool anywere i screwedup my bootloader and recovery img.. now i need help my device only recognized for 3 seconds.
then loop loop and stock recovery mode which dont work.
plz help pm me a link or anything. ugh i bricked this uggh

Download kindle fire first aid or system restore tool, they come with fastboot and adb.
Sent from my Amazon Kindle Fire HD using Tapatalk

vIgGeN7 said:
hey i cannot kind a download for this tool anywere i screwedup my bootloader and recovery img.. now i need help my device only recognized for 3 seconds.
then loop loop and stock recovery mode which dont work.
plz help pm me a link or anything. ugh i bricked this uggh
Click to expand...
Click to collapse
Here is a tutorial that will show you how to install a 2nd bootloader and TWRP recovery.
2nd bootloader/TWRP install http://forum.xda-developers.com/showthread.php?t=2128175
Then choose a ROM made for the 8.9 Kindle Fire HD only and flash it.
If you wish to go stock then flashing the appropriate images in fastboot will be your plan. This requires setting up some SDK tools in your environment.
SDK setup video http://m.youtube.com/watch?v=oaNM-lt_aHw
KFFA is another option as well.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Kindle Fire HD 8.9 Bricked
Can someone please provide me with some information. I tried to update the recovery for my Kindle Fire HD 8.9 running on cm10.2 using flashify which I found out now was a very lazy and dumb thing to do. Now my device is bricked its stuck at the white and orange kindle logo, my computer only recognize it for a split second and I can't boot into recovery.
My question to the experience members is if my device is done for or can the factory cable restore it? I tried creating one but it didn't get my device into fastboot mode and I also heard that it isn't compatible with the 8.9 series, I would like to know how true this is.
Thanks a lot.

You don't use a fastboot cable with a 8.9. It should when plugged in while off show up for a brief moment as a jem device. In this brief moment you must have the device manager open and right click the jem device hit update drivers and point it to where you would have downloaded and extracted the drivers in my signature. Once you manage to get the drivers installed shut off the kindle and open a command prompt that's CD'd into the directory of the fastboot command and run
Code:
fastboot -I 0x1949 getvar product
it should say waiting for device, at this point plug the kindle in with a normal cable and it should go into fastboot. I recommend a ubuntu live CD for this procedure because you don't have to deal with the driver issue, instead you just have to install the fastboot binary from the repo but it is fairly easy.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
You don't use a fastboot cable with a 8.9. It should when plugged in while off show up for a brief moment as a jem device. In this brief moment you must have the device manager open and right click the jem device hit update drivers and point it to where you would have downloaded and extracted the drivers in my signature. Once you manage to get the drivers installed shut off the kindle and open a command prompt that's CD'd into the directory of the fastboot command and run
Code:
fastboot -I 0x1949 getvar product
it should say waiting for device, at this point plug the kindle in with a normal cable and it should go into fastboot. I recommend a ubuntu live CD for this procedure because you don't have to deal with the driver issue, instead you just have to install the fastboot binary from the repo but it is fairly easy.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Thanks a lot man I completely gave up and was ready to order the motherboard. Now my kindle fire hd is up and running cm11 :good: :laugh:

unbrick for dummy
Kemoid said:
Thanks a lot man I completely gave up and was ready to order the motherboard. Now my kindle fire hd is up and running cm11 :good: :laugh:
Click to expand...
Click to collapse
stunts513
Can you explain step by step for techno-peasants how to fix my Kindle fire HD 8.9?
It flashes the words "kindle fire" for 14 seconds then goes dark and won't to anything else. I tried holding in the power button for 20; 30;40;60 seconds and that whole thing. I tested the charge in the battery. I'm past the easy fixes.
I'm at the point Kemoid was at above, ready to throw my Kindle Fire away and buy a new one.
I need the idiot proof directions that start with words similar to "Go to ww.somemagicURLwhereIcangetwhatIneedtodiagnoseandfixmyKindefireHD8.9.com and download xxxxxxxxxxxxx.xxx to your computer, then....."
Assume downloading an app reaches the limits of my technical comfort level.
Can you help me?

JoyousM said:
stunts513
Can you explain step by step for techno-peasants how to fix my Kindle fire HD 8.9?
It flashes the words "kindle fire" for 14 seconds then goes dark and won't to anything else. I tried holding in the power button for 20; 30;40;60 seconds and that whole thing. I tested the charge in the battery. I'm past the easy fixes.
I'm at the point Kemoid was at above, ready to throw my Kindle Fire away and buy a new one.
I need the idiot proof directions that start with words similar to "Go to ww.somemagicURLwhereIcangetwhatIneedtodiagnoseandfixmyKindefireHD8.9.com and download xxxxxxxxxxxxx.xxx to your computer, then....."
Assume downloading an app reaches the limits of my technical comfort level.
Can you help me?
Click to expand...
Click to collapse
Your in a bootloop. Just use the factory restore tool for the 8.9 and your USB cord.

I'm thinkin your kernel is messed up, probably just needs reflashing, I agree with LinearEquation, you just need to use the system restore tool or kffa and it should reflash that, if you can get into fastboot though you might need to wipe your boot partition. Try the SRT first though.

My kindle still brick
mr.galaxys said:
(if you're bricked, you need fastbootcable?). that what i was told anyways
Click to expand...
Click to collapse
thank for your share, but my kinlde fire hd 8.9 still brick
Before, i rooted and install TWRP . But, I install stock rom form amazon ( 8.5.1) and after, I update superuser and restart it. red screen appear. And now, I try anything to unbrick but nothing change.
you can see my brick youtube.com/watch?v=kJzsZKF5OUk ( I dont enough post to up youtube)
so, Please help me this case.
Thank you very much !!!

[Q] Help, stuck in a boot loop!

Hi, I just recently got a Kindle Fire HD 8.9 and decided that I wanted to flash CM 11 onto it. Well I followed the steps of a tutorial up until the point where I have to flash a second bootloader and TWRP Recovery. I flashed and installed the script, but accidentally clicked the option to turn off and go into recovery mode or something. Now my Kindle is stuck in a boot loop where the Fire in kindle fire is red. The logo stays for a couple seconds then the kindle just restarts itself.
I've tried to go into fastboot mode using the command prompt "fastboot -i 0x1949 getvar product" but when I connect my device, the computer does not see a thing. I do not know what else I can do at this point. I've looked up and read countless forums, but nothing has worked. Is there any way for me to recover my Kindle?

If it hasn't ever been in fastboot mode before while hooked up tot hat PC and had the drivers installed then it is precisely that reason the command is not working, because the drivers ade not installed. You can try to install them if that is the case, you just have to be fast and update the driver while the device is first plugged in and showing up for a brief moment. I personally recommend using a ubuntu 13.10 CD for this kinda case because of how Linux's driver system works you Don,t have to do anything, the driver already loads up when you plug it in.
Sent from my Amazon Kindle Fire HD using Tapatalk