Develop Bugs

[Q] Messed up with bootmode variable. How to normal boot again?

After successful root of my kindle fire 2 I moved to next step to install fire fire fire bootloader.
It did not go through by setting bootmode to 4002 and I looked at normal boot value.
Surprisingly, it was 1 instead of 4000.
So decided to set it to 2 (issuing 'idme bootmode 2' with superuser via adb)
After reboot kindle showed 'A n d r o i d' text followed by following screen:
IP = 192.168.101.101
DIV = KC1A3A04-20120809
SN = SOMESERIALNO
MAC = SOMEMACADDR
BATTERY=100
BMID=SwE
TOUCH FVER= 10.2.6.0
I can see the device in Windows device manager as Android ADB Interface, but neither adb nor fastboot can comunicate with device.
I do not own factory cable.
How can I return it to normal boot?
Thank you

dedolini_xda said:
After successful root of my kindle fire 2 I moved to next step to install fire fire fire bootloader.
It did not go through by setting bootmode to 4002 and I looked at normal boot value.
Surprisingly, it was 1 instead of 4000.
So decided to set it to 2 (issuing 'idme bootmode 2' with superuser via adb)
After reboot kindle showed 'A n d r o i d' text followed by following screen:
IP = 192.168.101.101
DIV = KC1A3A04-20120809
SN = SOMESERIALNO
MAC = SOMEMACADDR
BATTERY=100
BMID=SwE
TOUCH FVER= 10.2.6.0
I can see the device in Windows device manager as Android ADB Interface, but neither adb nor fastboot can comunicate with device.
I do not own factory cable.
How can I return it to normal boot?
Thank you
Click to expand...
Click to collapse
I think you need to read this before you do anything else to your device
http://forum.xda-developers.com/showthread.php?t=1928866

soupmagnet said:
I think you need to read this before you do anything else to your device
http://forum.xda-developers.com/showthread.php?t=1928866
Click to expand...
Click to collapse
Thank you, read it.
What I did not understand is my kindle already bricked?

I think your first step should be getting a fast boot cable. My suggestion is not to try anything else from the kf1 threads.
Sent from my Nexus 4 using Tapatalk 2

So far your device is still salvageable. Turn the device off, enter the command "fastboot -i 0x1949 getvar product" then turn the device on when you see "waiting for device". When it boots (if it's like any other KF), it will activate fastboot and you will get an output of "kindle". If not, you need to acquire a factory (fastboot) cable. And you still need to make sure your drivers are working properly.

soupmagnet said:
So far your device is still salvageable. Turn the device off, enter the command "fastboot -i 0x1949 getvar product" then turn the device on when you see "waiting for device". When it boots (if it's like any other KF), it will activate fastboot and you will get an output of "kindle". If not, you need to acquire a factory (fastboot) cable. And you still need to make sure your drivers are working properly.
Click to expand...
Click to collapse
I have ordered fastboot cable and i am awaiting delivery.
Drivers should be fine - they are latest from android sdk and composite driver connected me to adb just ok.
fastboot i try to use also is from latest android sdk.
after issuing getvar product fastboot command, waiting for device
stays for way too long
Since on kindle's screen some ip address is displayed, i wonder if in this bootmode some othe communication with device could be possible?

[SOLVED!] Kindle Fire Bricked on Logo Startup - KFU v0.9.9

I am total noob. Just want to make that clear from the get go.
I hesitate to start a new thread, but I have been working on this forever, and have not made any progress.
I have a Kindle Fire that I would like to run android on - I started the process with the Kindle Fire Utility v 0.9.9. Something went wrong, and it is now stuck on the Kindle Fire start up logo. I also can no longer see it in the device manager, nor is it responsive to anything in the Utility. (ADB status: Offline Boot Status: Unknown). I am at a loss, does anyone have any ideas? Your help is appreciated!
.................FIGURED IT OUT!..............................
Much thanks to the pooch who spent hours helping me troubleshoot.
What we (he) did, as far as I remember, hopefully this can be of some service to someone else out there.
1) Figured out that trying all of this on a Virtual Machine is not a good idea!
2) I somehow broke the bootloader in my first attempt, so none of my computers were recognizing the KF.
3) Created a Pendrive to run Linux (ubuntu). Here Requires a USB drive formatted Fat16/Fat32/NTFS, minimum of 2 gb.
4) Once I got Linux running, installed SoupKit.
5) Went through a few tries of booting, rebooting, into recovery mode until the Kindle flickered back to life!
6) Followed prompts on SoupKit to install TWRP, updated TWRP, install FireFireFire, install Android 4.2.
Good luck, I am happy to answer any questions - though I am no means an expert now.

What I have tried...more info
More Information:
I am running Windows7 in a VirtualBox on an iMac.
I bricked the Kindle a few weeks ago, after messing with it then, I bought a factory fastboot cable. Still no dice.
I have tried all turning on and off computer, on and off Kindle with it disconnected, connected, going through the KFU 4 seconds after starting the Kindle. Letting the Kindle's battery die, recharging.
I have deleted .android folder, reinstalled drivers, re-downloaded KFU.
I have tried on a different computer (Windows XP) The Kindle is also not recognized there.
I have tried booting into Ubuntu (however in the directions there, it said the FireKit is for more "serious" issues than my soft brick.
I am sure there is some small detail I am missing, but I have not been able to find it - and I am not knowledgeable enough to properly diagnose the problem. Again thanks for any help.

kyleboyd said:
I am total noob. Just want to make that clear from the get go.
I hesitate to start a new thread, but I have been working on this forever, and have not made any progress.
I have a Kindle Fire that I would like to run android on - I started the process with the Kindle Fire Utility v 0.9.9. Something went wrong, and it is now stuck on the Kindle Fire start up logo. I also can no longer see it in the device manager, nor is it responsive to anything in the Utility. (ADB status: Offline Boot Status: Unknown). I am at a loss, does anyone have any ideas? Your help is appreciated!
Click to expand...
Click to collapse
Sometimes KFU will show as Unknown even though it's really fine. I had the same issue as you. Try switching boot mode to Normal and see if that fixes it, it worked for me.

Read this (everything),especially third post.
http://forum.xda-developers.com/showthread.php?t=1552547

hemmulde 1st
zastava750 said:
Read this (everything),especially third post.
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thanks for the reply!
I tried that. When I type "fastboot getvar product" it says waiting for device or something similiar.
The advice applying to Device Manager don't get me anywhere, because my Kindle doesn't show up.
Any other ideas?

kyleboyd said:
Thanks for the reply!
I tried that. When I type "fastboot getvar product" it says waiting for device or something similiar.
The advice applying to Device Manager don't get me anywhere, because my Kindle doesn't show up.
Any other ideas?
Click to expand...
Click to collapse
When using the stock bootloader (plain "kindle fire" boot logo), the fastboot command must always specify the custom vendor ID used by the Kindle Fire. For example, the commands above must be slightly altered to...
Code:
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 devices
and likewise, all of the following commands will need the "-i 0x1949" switch when using the stock bootloader. The FFF bootloader's vendor ID has been changed to one that is normally recognized by fastboot, so the "-i 0x1949" switch can be omitted.
Now onto some more useful fastboot commands...
Code:
fastboot oem idme bootmode 4000
fastboot oem idme bootmode 4002
fastboot oem idme bootmode 5001
Using one of these commands will change the bootmode to normal (4000), fastboot (4002) or recovery (5001). Then issuing...
Code:
fastboot reboot
will reboot the device into the respective bootmode.

I've tried that as well...
Just so I am totally clear, this is what I did in relation to those instructions:
Opened Command Prompt - set the directory to C:/kfu/tools
Typed "fastboot -i 0x1949 getvar product" (with out the quotations, obviously)
<waiting for devices>
I plugged Kindle in, it powers on and the frozen logo pops up.
I also tried "fastboot -i 0x1949 oem idme bootmode 4000" and "fastboot -i 0x1949 oem idme bootmode 4002"
According to the guide it often takes multiple tries, I have done it over and over again.
I have also tried different orders of code, plugging in Kindle, and powering on and off.
Am I doing something wrong? Is there a specific code for my Kindle? (Not -i 0x1949)
Thanks!

Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1660636

Reinstall the driver then use kfu to reset the boot mode to normal.

Drivers?
I did try this: http://forum.xda-developers.com/show....php?t=1660636
When I get to the part about the Device Manager, I am stuck, as nothing shows up (I suspect something do with drivers)
Thepooch said:
Reinstall the driver then use kfu to reset the boot mode to normal.
Click to expand...
Click to collapse
By reinstall drivers do you mean clicking on "install_drivers" in the KFU folder? I have tried that.
Is there another method of uninstalling and installing drivers? Sorry if that is a dumb question!

If the devices is in fastboot which I believe it is it would show up as android adb interface, if it was attempting to boot to the system it would show up as android composite adb interface. If you are on xp or windows 8 this can be a bit of a tricky task. Android adb interface and android composite interface are two facets of the same driver. So yes I suggest rerunning the driver installation bat that is packaged with KFU. If perhaps you are on windows 8 you must disable driver signature verification and reinstall the driver. 3.0 usb ports have an issue with fastboot and can leave the device undetected.

Still not working
Thepooch said:
If the devices is in fastboot which I believe it is it would show up as android adb interface, if it was attempting to boot to the system it would show up as android composite adb interface. If you are on xp or windows 8 this can be a bit of a tricky task. Android adb interface and android composite interface are two facets of the same driver. So yes I suggest rerunning the driver installation bat that is packaged with KFU. If perhaps you are on windows 8 you must disable driver signature verification and reinstall the driver. 3.0 usb ports have an issue with fastboot and can leave the device undetected.
Click to expand...
Click to collapse
Thanks for the quick reply.
So I am on a Win7 and/or a Windows XP. Currently on both systems, when I plug it into the computer, with the Device Manager open, nothing happens other than the Kindle turning itself on.
Before it froze up, I saw it in device manager as Android ADB interface, and before doing anything at all, saw it as the default Kindle Fire.
On the Win7 system, I have rerun the driver installation bat over and over and over again, with absolutely no results.
On the WinXP, I have tried it, and for the life of me can't get it to install (it says install failed (Unsigned)). I never connected the Kindle up to this computer before it froze up, so I wonder if that is somehow causing the problem (it is trying to update drivers that don't exist?)
Am I doing something wrong with this? Can I uninstall or delete drivers, and totally start over?

If you are using a WinXP you must install driver manually.

Drivers?
zastava750 said:
If you are using a WinXP you must install driver manually.
Click to expand...
Click to collapse
How do I do that, when the Kindle does not show up as being connected? All the guides I have found start off with accessing from the Device Manager. My Kindle does not show up in the Device Manager...

okay well then you`re running xp use another computer getting the driver installed is hard even for the very skilled particularlly when the device is stuck in fastboot. Friend or relatives computer running windows 7 would be perfect. Otherwise it`s linux on a live usb booted on your xp machine.

Windows 7 - No Dice
Thepooch said:
okay well then you`re running xp use another computer getting the driver installed is hard even for the very skilled particularlly when the device is stuck in fastboot. Friend or relatives computer running windows 7 would be perfect. Otherwise it`s linux on a live usb booted on your xp machine.
Click to expand...
Click to collapse
Yeah so I have a Windows7. I have reinstalled the drivers (by clicking on the install_drivers.bat file in the KFU) over and over again, and I still do not get any recognition on the computer, or in the Device Manager when I plug in the Kindle.

Try different usb port, make sure they are usb 2.0. Is the logo static or animated? It possible that you broke the bootloader. At some point I would be willing to look at some things for you via teamviewer. If it is not driver related I fear your next move is here http://forum.xda-developers.com/showthread.php?t=1430038. Keep it on charger or off till it can be dealt with.

Thepooch said:
Try different usb port, make sure they are usb 2.0. Is the logo static or animated? It possible that you broke the bootloader. At some point I would be willing to look at some things for you via teamviewer. If it is not driver related I fear your next move is here http://forum.xda-developers.com/showthread.php?t=1430038. Keep it on charger or off till it can be dealt with.
Click to expand...
Click to collapse
Thanks! I would be willing to give it a shot (teamview I mean) if you are willing.
I tried the Firekit before I began this thread, but I kept getting stuck trying to run the tool after booting into ubuntu. Perhaps that is a different thread topic, but I am more than willing to put more work into figuring that out, if it could be the key to unlocking this stupid thing.

I am having this exact same problem. Using Win XP i was able to get the ADB drivers loaded initially and used KFU to try to install TWRP. When it rebooted during that process it got stuck at the Kindle Fire logo. Since then I cannot get my computer to recognize the kindle. Like you, I feel like i've tried everything.

Nixnaegie said:
I am having this exact same problem. Using Win XP i was able to get the ADB drivers loaded initially and used KFU to try to install TWRP. When it rebooted during that process it got stuck at the Kindle Fire logo. Since then I cannot get my computer to recognize the kindle. Like you, I feel like i've tried everything.
Click to expand...
Click to collapse
Glad to know I'm not alone - misery loves company! Solidarity my friend.
I wish I could tell you I'd solved it, but alas, I have not. I'm still working on it, I'll keep you updated if I have any breakthroughs!

[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

[Q] [8.9HD] Device not going into fastboot mode, booting normally.

Hi all,
I got a refurb 8.9 HD for basically free, so I want to flash the best current ROM onto it (which it looks like is CM11 at the moment). I'm having a bit of trouble getting the device into fastboot mode:
What I've accomplished so far:
Have adb and fastboot working in the command prompt
Installed the amazon usb drivers, kindle shows as Android Composite ADB Interface in device manager
Device is recognized by adb devices (shows serial number + "device")
Turned "Enable ADB" to ON in security settings
However, when I unplug the kindle, execute the "fastboot -i 0x1949 getvar product" command, I do get the <waiting for device> message, but when I plug in the turned-off Kindle, I get two quick chimes, then a second later the "device disconnected" sound, then the kindle boots as normally, and nothing happens in the command prompt.
It may be worth noting that when I first connected the Kindle (after installing drivers) I didn't get the "Enable USB Debugging" pop-up that two guides mentioned. Thoughts?

You must be doing it in the wrong order
1. turn of your kindle
2. connect your wire
3. open cmd and type fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
4. now turn on your device it should go into fastboot

Did you get it to work? And are you running 8.5.1? Because that's what I'm running and I'm having the same problem. I've seen solutions all over the place for 8.4, nothing for 8.5. Amazon seems to have a real lockdown on it.

Can't Get Fastboot to See My Kindle Fire HD 8.9 HELP!

Hi Guys!
Picked up a refurb Kindle Fire HD 8.9 on Woot the other day and want to stick CM 12.1 on it. I'm no programmer but I've successfully followed directions to root and install CM on about a dozen devices over the years but this one has me stumped.
I'm running Windows 10 and have apparently successfully installed the Amazon USB driver. When the tablet is plugged in Device Manager shows "Fire Devices > Android Composite ADB Interface" and it reports "working properly." I made sure to install the driver with Windows driver signing OFF. I can do a command prompt "ADB devices" and I get back a single device which corresponds to the device Serial Number (when I disconnect the tablet, I get nothing). So it seems ADB can find the tablet. The tablet has "Enable ADB" set to ON. I have done nothing else with the tablet, no registration, nothing, it's direct from factory and seems to be working fine. Current system version is 8.4.3_user_4308820, I have not updated it from what it came with.
So everything looks good until I try to run fastboot. I punch in "fastboot -i 0x1949 getvar product" and get "waiting for device". I reboot the tablet and it just simply reboots like normal and brings up the lock screen. I can't get Fastboot to show. I've done a simple shut down/reboot, I've held the power button down for like 20 seconds and forced power off. I've also tried plugging into different USB ports and different USB cables. Still nothing, just "waiting for device".
Can anyone offer suggestions to get to Fastboot? Many thanks in advance!

Are you generating your command prompt in the folder where fastboot.exe (and ideally also adb.exe) is located? If not, do so. When you get the "waiting for device" prompt with fastboot, are you then plugging in your powered OFF Kindle? This is one way that fastboot operates in our Kindles. There is also the modified factory cable that will automatically reboot the Kindle into fastboot mode (see the following video: www (dot) youtube (dot) com/watch?v=FFoAvnf7YUQ). Alternatively, you can try using ADB to reboot the device into fastboot as shown in the video. Good luck!