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

[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

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

KFU failed, kindle bricked, help please!

I never rooted a device before and I have been wanting to access google play on my kindle. Earlier today I discovered KFU. The first thing I did with it was the root option. After a few reboots, KFU said "waiting for device" and nothing else happened. Also my computer no longer recognizes my kindle fire. What should I do?
Important Information:
Yes, I have a first gen kindle fire.
I kept on getting a corrupted KFU zip when I downloaded it. I thought I fixed it when a use a zip fixer tool.
I got the KFU from the guild from this forum.
All the version I download had the same problem when unzipping, corruption.
I am a noob at this since I never done this before, I wan to make this clear, so don't assume much when responding please.
I have eclipse and I have downloaded all the necessary files from the SDK manager and more since I use eclipse for college.
My computer uses windows 8.
I have a windows 7 vm.
I used the KFU on windows 8, I now realized I should have done it on the vm.
Before I tried to root it, I made a backuped all the files located within it.
Almost forgot to mention that it no longer goes past the kindle fire logo when I restart it.
I don't know if this is enough information, so feel free to ask anything.

what do you use to backup your files?
did you try to restore your device using your backup files?

pinkLeviosa said:
what do you use to backup your files?
did you try to restore your device using your backup files?
Click to expand...
Click to collapse
I backed them in in my documents, and since I can't access my kindle due to it not being able to start up all the way, I can't restore them.

TheNerdWizard said:
I never rooted a device before and I have been wanting to access google play on my kindle. Earlier today I discovered KFU. The first thing I did with it was the root option. After a few reboots, KFU said "waiting for device" and nothing else happened. Also my computer no longer recognizes my kindle fire. What should I do?
Click to expand...
Click to collapse
open device manager (start menu>control panel>hardware>device manager) with kindle powered on and connected to pc, look for kindle< douple click on it, select drivers tab, click on uninstall< check uninstall driver, ok
My computer uses windows 8.
Click to expand...
Click to collapse
there is a thread on getting drivers installed on win 8 [HOW-TO] Amazon Kindle Fire Signed Driver for WinXP/Vista/7/8/8.1
Important Information:
Yes, I have a first gen kindle fire.
Click to expand...
Click to collapse
should be listed in More> Device>serial umber will start with D01E
I kept on getting a corrupted KFU zip when I downloaded it. I thought I fixed it when a use a zip fixer tool.
Click to expand...
Click to collapse
when downloading android files, you should verify md5 checksum see my https://sites.google.com/site/sdshadowscollection/home/hash-checksums
Kindle Fire Utility v0.9.9.zip = MD5 Sum: a20011995d115c3b2d66dcc92303031e
or use the Mega link mega will verify the file for you.
I got the KFU from the guild from this forum.
All the version I download had the same problem when unzipping, corruption.
I am a noob at this since I never done this before, I wan to make this clear, so don't assume much when responding please.
I have eclipse and I have downloaded all the necessary files from the SDK manager and more since I use eclipse for college.
I have a windows 7 vm.
I used the KFU on windows 8, I now realized I should have done it on the vm.
Click to expand...
Click to collapse
not sure if vm will work, may
Before I tried to root it, I made a backuped all the files located within it.
Almost forgot to mention that it no longer goes past the kindle fire logo when I restart it.
Click to expand...
Click to collapse
that makes it more difficult, probably because you repaired the KFU zip
try fixing drivers, then try
redownload KFU from the Mega link
connect Kindle
run KFU's run.bat
select install twrp
if nothing happens, may need to power down kindle, and power back on
may need to restart KFU a few times
if that does not work
may need to use fastboot manually see my Fastboot.exe with Windows Command Prompt

did you try to open your kindle by pressing your power button for about 15 - 20 sec.?
for your Kindle Fire Utility problem i think you need to ask that to their thread
Here: http://forum.xda-developers.com/showthread.php?t=2192818&page=35

sd_shadow said:
open device manager (start menu>control panel>hardware>device manager) with kindle powered on and connected to pc, look for kindle< douple click on it, select drivers tab, click on uninstall< check uninstall driver, ok
there is a thread on getting drivers installed on win 8 [HOW-TO] Amazon Kindle Fire Signed Driver for WinXP/Vista/7/8/8.1
should be listed in More> Device>serial umber will start with D01E
when downloading android files, you should verify md5 checksum see my https://sites.google.com/site/sdshadowscollection/home/hash-checksums
Kindle Fire Utility v0.9.9.zip = MD5 Sum: a20011995d115c3b2d66dcc92303031e
or use the Mega link mega will verify the file for you.
not sure if vm will work, may
that makes it more difficult, probably because you repaired the KFU zip
try fixing drivers, then try
redownload KFU from the Mega link
connect Kindle
run KFU's run.bat
select install twrp
if nothing happens, may need to power down kindle, and power back on
may need to restart KFU a few times
if that does not work
may need to use fastboot manually see my Fastboot.exe with Windows Command Prompt
Click to expand...
Click to collapse
You didn't listen to me. My kindle won't connect to the computer any more since it can't finish booting. Meaning I can't install anything on it. The kindle drivers are fine. The kindle is half rooted due to the rooting fail.

Frequently Asked Questions - Amazon Kindle Fire
Q16: What does it mean when my device is stuck at the Kindle Fire logo?
It depends on which Kindle Fire logo you're talking about. If you're talking about the Kindle Fire logo that stays brightly lit without any change in brightness, it means the device is in fastboot mode. Just change the bootmode to normal or recovery and reboot. If you are unable to change the bootmode, then you need to fix your drivers. If the Kindle Fire logo you're talking about flashes and goes dim after being brightly lit for a few seconds, then your device is trying to boot normally to a malfunctioning operating system, likely caused by not wiping the data partition (factory reset) before flashing a ROM. If that's the case, you will likely need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall a ROM properly.
Click to expand...
Click to collapse

sd_shadow said:
Frequently Asked Questions - Amazon Kindle Fire
Q16: What does it mean when my device is stuck at the Kindle Fire logo?
Click to expand...
Click to collapse
It's just the normal start up logo. Kindle is in white, and fire is in orange.

I know what I need to do now. I need to get a factory fastboot cable. That will allow me to access my kindle and fix the problems I have. Thank you for trying to help though.

i think its soft bricked your problem MAYBE is bootloop one of the common problem when rooting..
try this links i dont know if one of it work for you because i dont have a kindle fire.
as you said your stuck at the logo, so i hope you can check it out :
http://forum.xda-developers.com/showthread.php?t=1602560&page=1
http://forum.xda-developers.com/showthread.php?t=2557379
http://everydaylife.globalpost.com/fix-kindle-fire-boot-loop-30462.html
so yeah, again.. im just helping...

Can't exit fastboot mode

Hello,
I was rying to install FireFireFire in my kindle fire 1 gen by doing this guide: https://forum.xda-developers.com/t/...flashing-fff-twrp-2015.2814955/#post-54124313
Beforehand I rooted kindle with saferoot successfully.
After device entered fbmode, it shows kindle fire logo and can't be recognized on computer.
How do I exit out of fastboot?
Is it possible to exit with short circuiting to boot via USB? how do I do this?
Kindle version is 6.3.4

mrsiri said:
Hello,
I was rying to install FireFireFire in my kindle fire 1 gen by doing this guide: https://forum.xda-developers.com/t/...flashing-fff-twrp-2015.2814955/#post-54124313
Beforehand I rooted kindle with saferoot successfully.
After device entered fbmode, it shows kindle fire logo and can't be recognized on computer.
How do I exit out of fastboot?
Is it possible to exit with short circuiting to boot via USB? how do I do this?
Kindle version is 6.3.4
Click to expand...
Click to collapse
Root doesn't affect flashing Recoveries or bootloaders
Likely a driver issue, Using Windows 10?
The only way to exit out of Fastboot mode that I know is
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot

Thank you for the reply.
I tried using both linux and windows 10 but none detected my kindle.
Can I try the short pin method? Since I never done anything like this before, do I need to ground myself before shorting to not get shocked? since my version is 6.3.4 and the guide had version 6.2.1 idk if I can

mrsiri said:
Thank you for the reply.
I tried using both linux and windows 10 but none detected my kindle.
Can I try the short pin method? Since I never done anything like this before, do I need to ground myself before shorting to not get shocked? since my version is 6.3.4 and the guide had version 6.2.1 idk if I can
Click to expand...
Click to collapse
You don't need to ground your self, you can try the short pin method, it doesn't matter what firmware version is installed.

sd_shadow said:
You don't need to ground your self, you can try the short pin method, it doesn't matter what firmware version is installed.
Click to expand...
Click to collapse
Okay I'll try that and report after doing it.
Thank you again

mrsiri said:
Okay I'll try that and report after doing it.
Thank you again
Click to expand...
Click to collapse
Shorting the pins before, after and during plug in didn't change anything on screen...
It should at least be detected on computer, but either windows or linux don't show anything.
Since I need to lift the cable slightly up for it to connect to computer, I guess the problem is the port.

mrsiri said:
Shorting the pins before, after and during plug in didn't change anything on screen...
It should at least be detected on computer, but either windows or linux don't show anything.
Since I need to lift the cable slightly up for it to connect to computer, I guess the problem is the port.
Click to expand...
Click to collapse
There were lots of port issue reported over the years, likely the most common thing that let to there retirement.