Develop Bugs

[Q] Kindle Fire Brick (possibly FUBAR) Please help!!!

First of all, I search many threads but couldn't find help for my specific problem. I rooted my Kindle Fire 6.2.2. with TWRP. Upon trying to unroot it, it bricked. I downloaded Kindle Fire Utility v0.9.3. to fix this but my computer won't properly recognize my Kindle. It doesn't seem like a driver problem. All I can do when I plug in my Kindle is eject it. And when I try to install FireFireFire, I get this error "Oops...something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on."
Please help! Thanks.

Lyrekz said:
First of all, I search many threads but couldn't find help for my specific problem. I rooted my Kindle Fire 6.2.2. with TWRP. Upon trying to unroot it, it bricked. I downloaded Kindle Fire Utility v0.9.3. to fix this but my computer won't properly recognize my Kindle. It doesn't seem like a driver problem. All I can do when I plug in my Kindle is eject it. And when I try to install FireFireFire, I get this error "Oops...something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on."
Please help! Thanks.
Click to expand...
Click to collapse
Please read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
so you get an understanding of how these different pieces fit together.
I can't get a sense of where your problems begin. 1) TWRP is not used to root. 2) you never mention what your Kindle Fire is doing that you think it's bricked. 3) how did you manage to root it in the first place if your drivers weren't working?

kinfauns said:
Please read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
so you get an understanding of how these different pieces fit together.
I can't get a sense of where your problems begin. 1) TWRP is not used to root. 2) you never mention what your Kindle Fire is doing that you think it's bricked. 3) how did you manage to root it in the first place if your drivers weren't working?
Click to expand...
Click to collapse
Answers: 1. Rooted with BurritoRoot3 and also installed TWRP. 2. It is stucked on the Kindle Fire screen. 3. My drivers were working then and seem to be now. The problem is my computer won't recognize my Kindle. And when I go to Kindle properties, the manufacter, model number, and description all come up as unavaible and grayed out.

Lyrekz said:
Answers: 1. Rooted with BurritoRoot3 and also installed TWRP. 2. It is stucked on the Kindle Fire screen. 3. My drivers were working then and seem to be now. The problem is my computer won't recognize my Kindle. And when I go to Kindle properties, the manufacter, model number, and description all come up as unavaible and grayed out.
Click to expand...
Click to collapse
If you installed TWRP, then you also installed FFF. If by "Kindle Fire screen" you mean the yellow triangle logo and that's all you see when it starts up without it ever blinking black, then you are in fastboot mode. Use KFU to set it back to normal and reboot it. If that doesn't work, you need to check the device manager in Windows and make sure it shows "Android Phone -> Android ADB Interface" for your Kindle Fire. If the device manager does not show that, then you need to uninstall the drivers, remove the device from the device manager, disconnect the KF from your computer and follow these directions....
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

kinfauns said:
If you installed TWRP, then you also installed FFF. If by "Kindle Fire screen" you mean the yellow triangle logo and that's all you see when it starts up without it ever blinking black, then you are in fastboot mode. Use KFU to set it back to normal and reboot it. If that doesn't work, you need to check the device manager in Windows and make sure it shows "Android Phone -> Android ADB Interface" for your Kindle Fire. If the device manager does not show that, then you need to uninstall the drivers, remove the device from the device manager, disconnect the KF from your computer and follow these directions....
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
First of all. thank you for the help. And now my Kindle is stuck on the Kindle Fire screen.

Mine is stuck here too..been 3 days.. ordered the factory cable.. hopefully that works.

One thing I've noticed is that sometimes when the you try to issue fastboot commands in fastboot mode it doesn't register. But that doesn't mean you aren't in fastboot mode.
Get your command prompt ready (“ready" means that "fastboot" is in your present working directory)
Turn off your Kindle
Type "fastboot devices" (without quotes)
Turn your Kindle on
Hit enter to send fastboot command
Keep hitting UP arrow to bring up last command and keep hitting enter until your computer recognizes the Kindle. If it doesn't, start over and try again. When it does, then you can change your bootmode.
It WILL work, eventually. If it doesn't, the only other logical explanation is it's a driver issue.
Typically speaking (but not always), the only reason you should ever have to use a factory cable is if you killed your battery and you don't have enough juice to power the device. There are other reasons but they are extremely RARE.
And please forgive my frustration, but this is one of the simplest concepts to master. "Unbricking" your device shouldn't be this difficult...for anyone.
Sent from my Amazon Kindle Fire using xda premium

Readyreadyready
I notice in a post someone is seeing:
"Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files"
Is that the "Ready" you are saying means wait until fastboot?
soupmagnet said:
One thing I've noticed is that sometimes when the you try to issue fastboot commands in fastboot mode it doesn't register. But that doesn't mean you aren't in fastboot mode.
Get your command prompt ready (“ready" means that "fastboot" is in your present working directory)
Turn off your Kindle
Type "fastboot devices" (without quotes)
Turn your Kindle on
Hit enter to send fastboot command
Keep hitting UP arrow to bring up last command and keep hitting enter until your computer recognizes the Kindle. If it doesn't, start over and try again. When it does, then you can change your bootmode.
It WILL work, eventually. If it doesn't, the only other logical explanation is it's a driver issue.
Typically speaking (but not always), the only reason you should ever have to use a factory cable is if you killed your battery and you don't have enough juice to power the device. There are other reasons but they are extremely RARE.
And please forgive my frustration, but this is one of the simplest concepts to master. "Unbricking" your device shouldn't be this difficult...for anyone.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse

larmores said:
I notice in a post someone is seeing:
"Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files"
Is that the "Ready" you are saying means wait until fastboot?
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1096 using XDA Labs

Red Screen

I was trying to install a rom on my Kindle Fire HD 8.9 and I am now stuck on a red screen. The kindle will start up and show the boot logo for about two seconds before a red screen appears on the tablet. My device manage flashes as if it was updating the devices on my computer. My PC does not recognize my Kindle. Any help would be appreciated.

Unless you can manage to get it into fastboot somehow, there's nothing you can do

If you do a search on here for KFFirstAide, you will find loads of information on installing drivers, restoring OS and various other helpful tips.
Hope this helps

praed0r said:
If you do a search on here for KFFirstAide, you will find loads of information on installing drivers, restoring OS and various other helpful tips.
Hope this helps
Click to expand...
Click to collapse
It still requires fastboot

soupmagnet said:
It still requires fastboot
Click to expand...
Click to collapse
Have to get the drivers working correctly, that you should be able to get into fastboot!

lizzord30 said:
Have to get the drivers working correctly, that you should be able to get into fastboot!
Click to expand...
Click to collapse
Yes, I rooted my Kindle before causing this problem. I do have the drivers working. I apparently need to boot into fastboot. I cannot do this with a fastboot cable as they don't work on my device. I can't do this with a PC as my Kindle won't be able to connect to it. I'm at a standstill at the moment. I hope I will be able to fix my device at one point in time. If these are my only options I suppose I will sit on my thumbs until I am able to fix my Kindle.

Blissful_Tea said:
Yes, I rooted my Kindle before causing this problem. I do have the drivers working. I apparently need to boot into fastboot. I cannot do this with a fastboot cable as they don't work on my device. I can't do this with a PC as my Kindle won't be able to connect to it. I'm at a standstill at the moment. I hope I will be able to fix my device at one point in time. If these are my only options I suppose I will sit on my thumbs until I am able to fix my Kindle.
Click to expand...
Click to collapse
Working adb drivers doesnt mean you have working fastboot drivers (I had the same problem before) Had to uninstall the drivers then dissable driver signiture form windows and install the unsinged drivers from the kindle first aid.
After you get fastboot working then you can install my rom if you want! Should fix fastboot and install TWRP, after that you can install any rom you want! Hope you can get it going!
Here is the link

Thank you Lizzord30. After messing around in Kindle first aid I got it working again.

Blissful_Tea said:
Thank you Lizzord30. After messing around in Kindle first aid I got it working again.
Click to expand...
Click to collapse
What exactly did you do to get it working?

SolusCado said:
What exactly did you do to get it working?
Click to expand...
Click to collapse
16) Reboot the kindle fire into fastboot mode (alternative method).
I used kindle fire first aid. Once in fastboot I restored it.

Blissful_Tea said:
16) Reboot the kindle fire into fastboot mode (alternative method).
I used kindle fire first aid. Once in fastboot I restored it.
Click to expand...
Click to collapse
Thanks. I figured it out.

Blissful_Tea said:
I was trying to install a rom on my Kindle Fire HD 8.9 and I am now stuck on a red screen. The kindle will start up and show the boot logo for about two seconds before a red screen appears on the tablet. My device manage flashes as if it was updating the devices on my computer. My PC does not recognize my Kindle. Any help would be appreciated.
Click to expand...
Click to collapse
To get your device into fastboot mode, turn off your device. On your pc go to any directory where you have access to fastboot.exe and press shift+right click anywhere, Click "open command window here"
copy and paste this code
Code:
fastboot -i 0x1949 getvar product
you'll get "Waiting for device"
Just plugin your device using normal cable, Your device wil power up and get into fastboot
Now all you need to do is use a restore tool like Kindle Fire first aide to flash a fresh rooted image to your device.

[Q] Kindle Fire 8.9 Perma-Bricked?

Hey Guys,
I successfully rooted my kindle fire 8.9" a while back and a few days ago decided to follow: http://forum.xda-developers.com/showthread.php?t=2277105 to install the twrp/custom rom.
In fireflash I moved the bootloader back to 8.1.4 and changed the boot and recovery partitions accordingly. I disabled the recovery auto update. I applied the changes and rebooted (I saw the red kindle fire letters and then it changed to the blue letters). It went into the TWRP screen at which point the guide told me to reboot. I found a "reboot to recovery" option and clicked it. Apparently, this was a very bad thing to do. The kindle boots to the Kindle Fire logo in red letters and stays there. it doesn't go blue and nothing moves. It stays that way until I turn it off.
It no longer will show up in Device Manager at all, but if I turn it on while plugged into the computer, the computer makes fast bump sounds like it sees the device for a second.The first time I plugged it into a different computer windows said it was trying to install a driver for "Jem-PVT-Prod-04" but then the driver installation failed and it doesn't show up in the device manager even with an exclamation mark.
Using different adb tools (Minimal adb and fastboot, kindle adb drivers, and android sdk) yields no response from the device even with a factory cable (which I purchased and arrived this morning). Fastboot just says < waiting for device > after the command "fastboot -i 0x1949 getvar product"
Adb kill-server followed by adb devices leads to a blank list of devices. (I also went into user/.android/ to change the adb_usb.ini file to 0x1949 (which it already was)
I tried KFHD SRT v2.1 http://forum.xda-developers.com/showthread.php?t=2011126 but it can't see the device either.
At this point, I don't know what can be done and am open to trying everything.

chickeninferno said:
Hey Guys,
I successfully rooted my kindle fire 8.9" a while back and a few days ago decided to follow: http://forum.xda-developers.com/showthread.php?t=2277105 to install the twrp/custom rom.
In fireflash I moved the bootloader back to 8.1.4 and changed the boot and recovery partitions accordingly. I disabled the recovery auto update. I applied the changes and rebooted (I saw the red kindle fire letters and then it changed to the blue letters). It went into the TWRP screen at which point the guide told me to reboot. I found a "reboot to recovery" option and clicked it. Apparently, this was a very bad thing to do. The kindle boots to the Kindle Fire logo in red letters and stays there. it doesn't go blue and nothing moves. It stays that way until I turn it off.
It no longer will show up in Device Manager at all, but if I turn it on while plugged into the computer, the computer makes fast bump sounds like it sees the device for a second.The first time I plugged it into a different computer windows said it was trying to install a driver for "Jem-PVT-Prod-04" but then the driver installation failed and it doesn't show up in the device manager even with an exclamation mark.
Using different adb tools (Minimal adb and fastboot, kindle adb drivers, and android sdk) yields no response from the device even with a factory cable (which I purchased and arrived this morning). Fastboot just says < waiting for device > after the command "fastboot -i 0x1949 getvar product"
Adb kill-server followed by adb devices leads to a blank list of devices. (I also went into user/.android/ to change the adb_usb.ini file to 0x1949 (which it already was)
I tried KFHD SRT v2.1 http://forum.xda-developers.com/showthread.php?t=2011126 but it can't see the device either.
At this point, I don't know what can be done and am open to trying everything.
Click to expand...
Click to collapse
Just to confirm that you're doing it correctly...have you powered the device completely down, entered 'fastboot -i 0x1949 getvar product', and then turned the device on? And still no luck?
BTW, the factory cable will not work with the KFHD8.9 and can possibly damage it. Don't use it.

soupmagnet said:
Just to confirm that you're doing it correctly...have you powered the device completely down, entered 'fastboot -i 0x1949 getvar product', and then turned the device on? And still no luck?
BTW, the factory cable will not work with the KFHD8.9 and can possibly damage it. Don't use it.
Click to expand...
Click to collapse
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.

chickeninferno said:
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.
Click to expand...
Click to collapse
I've run into relatively the same problem with my HD8.9 several times while testing scripts but I've always been able to enable fastboot after rebooting using 'getvar product'. The difference in my case, is that I was always using Linux. You may want to set up a LiveUSB and install the SoupKit from the Dev section and try again to see if it makes a difference. SoupKit is not required, of course, but it is definitely recommended if you're not very familiar with Linux.

chickeninferno said:
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.
Click to expand...
Click to collapse
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD

Brandonrz said:
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
Click to expand...
Click to collapse
Brandonrz,
It does not show up in the Device manager when off, when I send fastboot commands, or when on. It will however show up as Jem-PVT-Prod-04 for ~1 second if I have device manager open and I turn on the kindle (regardless of whether or not a fastboot command was sent).
@soupmagnet,
my flashdrive was dead so I just picked up a new one. Putting linux on it now.

chickeninferno said:
Brandonrz,
It does not show up in the Device manager when off, when I send fastboot commands, or when on. It will however show up as Jem-PVT-Prod-04 for ~1 second if I have device manager open and I turn on the kindle (regardless of whether or not a fastboot command was sent).
@soupmagnet,
my flashdrive was dead so I just picked up a new one. Putting linux on it now.
Click to expand...
Click to collapse
For those who may be in same situation here is what I did.
Go to device manager. For that second, try to Right click on Jem-PVT-08 and choose update driver software, then browse my computer for driver software, then let me pick from a list of device drivers on my computer. I moved down list and picked Kindle and it installed as adb composite interface or something like that. Once installed the device manager showed "Kindle" and my fastboot was working. I've had the issue before. I hope this helped!

Glorious Success!
So I ended up doing a combination of the two solutions and since I know how frustrating this was here's how I did it just in case someone stumbles upon this.
How it magically worked:
1.) Inside of Linux Mint, I installed Soupkit
2.) In terminal i typed "fastboot -i 0x1949 getvar product"
-----The kindle reacted for the first time in a long time and went into fasboot mode. Since I had no idea where to put the boot.img or recovery.img in linux to send them but the fastboot or adb commands, I decided to risk it and move to windows.
3.) I unplugged the kindle
4.) Booted into Win 7 x64
5.) The fastboot wasn't working in windows but I checked device manager and the exclamation mark was lingering. I manually picked the driver of amazon.com/kindle and it installed the adb composite device. Fastboot now works in windows.
5.) ran SR Tool.bat in the KFHD_SRT_2.1 folder and chose option 1 (Enable Fastboot)
-----Success
6.)in SR Tool i chose option 4 (erase cache and userdata)
----Took ~4 minutes but success
7.) in cmd I navigated to my sdk platform tools folder by typing "cd C:\Users\<username>\Desktop\SDK\adt-bundle-windows-x86_64-20130522\sdk\platform-tools"
8.) I downloaded the boot.img and recovery.img linked here (http://forum.xda-developers.com/showthread.php?t=2011126) and placed them into C:\Users\<username>\Desktop\SDK\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\
9.) in the cmd from step 7 I sent the following commands "fastboot -i 0x1949 flash boot boot.img" and "fastboot -i 0x1949 flash recovery recovery.img"
----Great Success
10.) In SR Tool I chose option 6 (reboot normally)
-----It looped for ~2 minutes but eventually booted like normal but the SR_Tool asked me to make sure that adb was enabled before clicking enter. I enabled it on the device but SR Tool still didn't seem to see that I had done it. Since it rebooted normally, I didn't really care.
11.) The kindle upgraded itself after I set it down to type this response to 8.4.3
I probably could have easily done this is linux, but I didn't know where to put the boot.img and recovery.img. Also, I'm guessing that the system.img is put back on the device when I used the KFHD SRT but I'm not sure.
Now I'm going for round two to get CM 10.1 put on this thing!
Thanks for all of the help. I really thought that I had actually managed to brick the nearly unbrickable kindle fire 8.9"

Congrats on your success and thanks for sharing the experience!
I think one problem with Windows is that, "fastboot -i 0x1949 getvar product" does not work very well on putting the kindle to fastboot if the device driver is not properly installed, kindle will simply bypass the fastboot step and continue(and hang), the whole situation is a dead loop on Windows if the fastboot driver is having problem and the kindle can't boot into the ROM, and to make things even worse, there is no factory cable for HD8.9
So the SoupKit is a real life saver here.

I had the same sort of driver problem after I installed the second bootloader. For me the simple fix was to go into device manager (In Windows 7), uninstall whatever driver was there with the yellow triangle and then reinstall the official kindle adb driver. Congrats on getting it fixed though. It's a great feeling, I know.

Worked form me too!
Brandonrz said:
For those who may be in same situation here is what I did.
Go to device manager. For that second, try to Right click on Jem-PVT-08 and choose update driver software, then browse my computer for driver software, then let me pick from a list of device drivers on my computer. I moved down list and picked Kindle and it installed as adb composite interface or something like that. Once installed the device manager showed "Kindle" and my fastboot was working. I've had the issue before. I hope this helped!
Click to expand...
Click to collapse
Thanks much for your pointer. In my case the Kindle showed up as an "Other devices" and I was able to use "browse my computer ..."->"let me pick from a list"->Kindle fire->ADB(ver 1.3).
You are awesome.

DBMmn said:
Thanks much for your pointer. In my case the Kindle showed up as an "Other devices" and I was able to use "browse my computer ..."->"let me pick from a list"->Kindle fire->ADB(ver 1.3).
You are awesome.
Click to expand...
Click to collapse
I'm so glad I could help, it was so frustrating for me.

Brandonrz said:
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
Click to expand...
Click to collapse
Im stuck RIGHT here. manually entered fastboot, with the device showing as JEM-PVT-Prod 4. Unable to re-install recovery because <waiting on device>. Please help.

Tyler9097 said:
Im stuck RIGHT here. manually entered fastboot, with the device showing as JEM-PVT-Prod 4. Unable to re-install recovery because <waiting on device>. Please help.
Click to expand...
Click to collapse
Try kingo root or towel root. I believe they might be easier.
Sent from my Nexus 6P using Tapatalk

Brandonrz said:
Try kingo root or towel root. I believe they might be easier.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Turned out it was a driver compatibility issue with Windows 10. It doesn't recognize the Kindle HD 8.9 properly. Moved it over to a Windows 7 machine and it was working, up until i attempted to flash a new recovery and boot .img . Now it's stuck on the red Kindle logo and computer won't pick up the USB. Halp!

Tyler9097 said:
Turned out it was a driver compatibility issue with Windows 10. It doesn't recognize the Kindle HD 8.9 properly. Moved it over to a Windows 7 machine and it was working, up until i attempted to flash a new recovery and boot .img . Now it's stuck on the red Kindle logo and computer won't pick up the USB. Halp!
Click to expand...
Click to collapse
Power off the Kindle, type fastboot -i 0x1949 getvar product , plug in the Kindle when you get <waiting for device>, and flash the 2nd bootloader, recovery, and freedom-boot images as directed in Hashcode's thread. Skip to step 5 after downloading the files, as we're already in fastboot mode at this point.
Also, Windows 10 enforces driver signatures, so you'll need to disable that before proceeding with the Kindle driver installation.
Sent from my Amazon Jem using XDA Labs

stack in kindle logo

hi.
after i rooted my kindle with success i restarted it and it stack to the boot logo screen.i cant see the kindle anymore as a device in the computer.when i connect my kindle it appears for 1 second to the hardware devices and then disappears.so i cant send any command through fastboot.anyone has any idea what to do so i can fix the kindle?i ve tried everything there is in this forum but with no luck

Try running this with your kindle unplugged and off,
fastboot -i 0x1949 getvar product
Once u run that it should say waiting for device, now plug the kindle in, and if it doesn't automatically power on, then power it on. It should go into fast boot I think. I am a bit unsure if it will because of the fact I don't own an 8.9" kindle, but I think I remember this method didn't work on the 7" model, but read it was more so intended for the 8.9" model. This would probably be more likely to work on Linux, because if you haven't installed the adb drivers before on fast boot, then I don't think windows will finish installing them before then device disconnects, but that's just what I think. Post results plz.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

I agree that it's probably a problem with the fastboot drivers not being installed on your PC, so the tablet leaves fastboot mode.
Does the Composite ADB Interface driver on the 2nd bootloader guide include fastboot driver? Perhaps if you install it as a legacy device via device manager without the device connected, it will connect after?
Personally I had difficulty installing these drivers as I'm on Windows 8 which disables installing drivers that arent digitally signed by default, if you use this OS then you need to toggle this via advanced startup options first.

O yea I know windows 8 is a total pain when it comes to unsigned drivers, had to deal with that on my friends pc. You can always try an Ubuntu live CD since the drivers won't be an issue. Is it staying on the non animated logo or the animated kindle logo after the device disappears?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
O yea I know windows 8 is a total pain when it comes to unsigned drivers, had to deal with that on my friends pc. You can always try an Ubuntu live CD since the drivers won't be an issue. Is it staying on the non animated logo or the animated kindle logo after the device disappears?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
the device disappears after one second from the hardware devices.it is staying on the non animated logo forever till the battery is dead.i have tried everything.i have installed the drivers with no problem and i even rooted the kindle.but after i restarted it the problem appeared.i ve tried to run the command with the kindle unpluged but when i plug it to the computer nothing happens.i tried usb2 and usb 3 ports, i tried windows 7 and windows 8 and pretty much everything i found here in the forum.still no luck

First off, your device is not in fastboot. Second, it is very unlikely that rooting alone would cause your device to hang at the Kindle Fire logo. Is there anything else that you attempted to do to your device before this happened?
Before getting to the appropriate solution, it would be beneficial to know what you used to root your device, whether or not you tried installing a custom bootloader/recovery, and what device you have in the first place.

i have a kindle fire hd 8.9" with 4.1 in it. i have followed this guide http://forum.xda-developers.com/showthread.php?t=2277105 so i can have root access. i used the binary method for the rooting.after i succesfully rooted the kindle i installed the astro file manager just for testing the root and it worked.then i followed the steps for installing the 2nd bootloader with twrp. it installed succesfully and i was able to boot in twrp mode. then i restart the kindle then it stack in the logo.thats pretty much all

doltrin said:
i have a kindle fire hd 8.9" with 4.1 in it. i have followed this guide http://forum.xda-developers.com/showthread.php?t=2277105 so i can have root access. i used the binary method for the rooting.after i succesfully rooted the kindle i installed the astro file manager just for testing the root and it worked.then i followed the steps for installing the 2nd bootloader with twrp. it installed succesfully and i was able to boot in twrp mode. then i restart the kindle then it stack in the logo.thats pretty much all
Click to expand...
Click to collapse
Now we're getting somewhere. You should do as stunts says to get your device booted into fastboot (see below)
stunts513 said:
Try running this with your kindle unplugged and off,
fastboot -i 0x1949 getvar product
Once u run that it should say waiting for device, now plug the kindle in, and if it doesn't automatically power on, then power it on. It should go into fast boot
Click to expand...
Click to collapse
If that doesn't work, you need to either fix your drivers in Windows, or use Linux (I believe he mentioned that as well)........Those are your only two options.
You'll need fastboot restore the partition images you saved in step one of the 2nd bootloader thread and start over.

at last.thanks a lot mate for your time and the tool you have created.i installed ubuntu then i used the soupkit and it finally went into fastboot mode and then i used kffirst aide and managed to make kindle work again.thanks so much.now i will try again to load the 2nd bootloader and install a custom rom.

[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!