Related
Hello everyone,
I've tried to find my specific situation in related threads, but haven't seen my exact issue, so here goes. Several threads seemed to talk about what I'm seeing, but the remedies that worked for them have not worked for me.
I have a Kindle Fire running 6.3.1, and I tried rooting yesterday with Kindle Fire Utilities 0.9.6 on a Windows Vista Virtual Machine.
The drivers appeared to install correctly, because KFU was able to see the Kindle and showed "online" when I started the process. The Device Manager seemed to have the correct information as well.
In KFU, I selected option 2 from the main menu, to "Install Permanent Root with Superuser". KFU started downloading twrp.img, but was unhappy with the MD5 checksum, so it issued the error: "Oops... something went wrong with the download. The recovery downloaded is not correct. Please try the download again"
At this point, the run.bat program exited, and the Kindle rebooted.
However, it appears that KFU at least partially succeeded in putting the Kindle into fastboot mode, because now I just get the "Kindle Fire" orange and white logo and nothing else happens. Also, I can no longer access the Kindle from my computer.
Now, when I run KFU again, it can't find the Kindle. I also can't contact it by running adb or fastboot manually, either from Window or from Ubuntu.
I've tried most, if not all, of the tricks I've seen in related threads to get back into contact with the Kindle and restore it to normal boot mode. The fastboot executable gets stuck in the < waiting for device > state, and I've tried power-cycling the Kindle, unplugging and plugging it back in, timing the execution of fastboot with the startup screen, etc. Since KFU did not successfully install Fire Fire Fire or TWRP before the failure occurred, I can't use either of these to recover.
I have ordered a Factory Cable from SkOrPn, but I'm curious if there's anything else I can try before it arrives, or if maybe I've missed something in all of the reading I've done over the past couple of weeks. (I read many threads and posts about rooting the Kindle, along with the Beginners Guide, before I worked up the courage to actually try it yesterday, and since then I've been educating myself on recovery techniques).
Sorry for the lengthy post, thanks for any help or clues, and I apologize if this has been answered already in another thread.
You might try powering it down completely, run KFU, choose option 1, then choose normal boot mode (4000) and when it comes up with <waiting for device> then hit the power button on your Fire.
This has worked for me in getting it back to normal boot when things seemed to be hung up. I sometimes had to hold the power button down to hard shutdown after this, but when rebooted after that, it booted normally.
Can't hurt to try it in this case.
You say you're using a VM, but what OS are you typically running? Mac OSX and Linux both handle device drivers by far better than their MS counterparts.
soupmagnet said:
You say you're using a VM, but what OS are you typically running? Mac OSX and Linux both handle device drivers by far better than their MS counterparts.
Click to expand...
Click to collapse
spfldcynic said:
You might try powering it down completely, run KFU, choose option 1, then choose normal boot mode (4000) and when it comes up with <waiting for device> then hit the power button on your Fire.
This has worked for me in getting it back to normal boot when things seemed to be hung up. I sometimes had to hold the power button down to hard shutdown after this, but when rebooted after that, it booted normally.
Can't hurt to try it in this case.
Click to expand...
Click to collapse
spfldcynic - Thanks for the tip. I tried it, but never got past the < waiting for device > state. It makes me wonder if the Kindle is really in fastboot, or if it's in some other state that makes it unresponsive to external commands. Hopefully the Factory Cable will fix this.
soupmagnet - My host OS is Ubuntu 10.04. I'd like to be able to work with the Kindle directly in Linux, but went the Window route initially because I'd heard good things about KFU. After reading your post, I found the FireKit tools for Linux, but got the same results using the "normal_boot" script that I had with KFU and with directly issuing the "fastboot -i 0x1949 oem idme bootmode normal" command from both Linux and Windows.
calgator said:
spfldcynic - Thanks for the tip. I tried it, but never got past the < waiting for device > state. It makes me wonder if the Kindle is really in fastboot, or if it's in some other state that makes it unresponsive to external commands. Hopefully the Factory Cable will fix this.
soupmagnet - My host OS is Ubuntu 10.04. I'd like to be able to work with the Kindle directly in Linux, but went the Window route initially because I'd heard good things about KFU. After reading your post, I found the FireKit tools for Linux, but got the same results using the "normal_boot" script that I had with KFU and with directly issuing the "fastboot -i 0x1949 oem idme bootmode normal" command from both Linux and Windows.
Click to expand...
Click to collapse
Did you try the whole process from scratch on Ubuntu? Also, plug it into the wall charger and make sure it has some juice before continuing (if you haven't already)
Running low on ideas man, hope someone else can do more for you.
You can't just get up and go with Linux, there is some configuration that needs to be done first. Have you set up your udev rules and installed 32-bit libs?
[SOLVED] KFU Failed, Now Kindle Fire Won't Boot
soupmagnet said:
You can't just get up and go with Linux, there is some configuration that needs to be done first. Have you set up your udev rules and installed 32-bit libs?
Click to expand...
Click to collapse
Yes, after reading your post I've discovered that you are correct. I followed Sblood86's instructions on setting up the udev rules (http://forum.xda-developers.com/showthread.php?p=22067293), and I already had the 32-bit libraries and tools since I have the android sdk and a 32-bit Ubuntu installation.
Armed with this correct configuration, I typed
Code:
"./fastboot -i 0x1949 oem idme bootmode 4000"
And this time, saw the following:
Code:
< waiting for device >
...
OKAY [ 0.201s]
finished. total time: 0.201s
Meaning that all is now well with my Kindle Fire, until the next rooting attempt.
Thanks for your help!
So, although the original KFU problem is not completely understood by me, since my Kindle is working, I'll say the problem is solved.
Hey so a few weeks ago i tried to root my kindle fire, version 6.3.1 (to the best of my memory), on windows 7. I tried Kindle Fire Utility but the drivers wouldn't install so i found a different one and ended up bricking it. I was able to use an unbricking tool i found online which worked initially, but a couple of weeks later i restarted the kindle and now it is stuck in FireFireFire (yellow triangle), which i think is fastboot mode (correct me if i'm wrong). I have TWRP installed and have been able to load into it once, but was unable to fix the problem and now have been unable to load into it since. Kindle is mostly unresponsive now, but can turn on and off with the power button and turns on when plugged in. My computer recognizes the kindle as an unknown device and is unable to update the drivers. I have tried reinstalling the drivers from Kindle Fire Utility v0.9.9 dozens of times, yet still nothing. I went to the the "read before you post" thread concerning drivers and attempted to follow that process a few times, however after i have selected the new drivers and clicked next the computer determines that the best drivers are already installed, and prevents me from installing the new ones manually.
Thanks for reading, would be nice if i could fix this issue.
New user so i cant post links, I will put the link to the site i bricked it on in the comments if needed.
Just to get it out of the way: are you rooted?
If you are, try this:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Make sure you have ADB set up before trying this.
gadgetroid said:
Just to get it out of the way: are you rooted?
If you are, try this:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Make sure you have ADB set up before trying this.
Click to expand...
Click to collapse
No midroot it got stuck in fastboot.
Okay so i went and followed the instructions for installing drivers and was able to get my computer to recognize that it is an android phone when plugged in rather than an unknown device. Unbricking tools still wouldn't work, so i followed the instructions to the point where i need to do go to the "have disk" part. After selecting the proper drivers, the computer said that it couldnt update the drivers "since the device cant start (code 10)".
Mudk1p21 said:
Okay so i went and followed the instructions for installing drivers and was able to get my computer to recognize that it is an android phone when plugged in rather than an unknown device. Unbricking tools still wouldn't work, so i followed the instructions to the point where i need to do go to the "have disk" part. After selecting the proper drivers, the computer said that it couldnt update the drivers "since the device cant start (code 10)".
Click to expand...
Click to collapse
Unplug your device and try once.
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!
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
I am trying to install Cyanogenmod on my kindle fire. However, before I was able to start flashing any images or anything like that, I ran into a problem (although this is probably the best time to have a problem). My Kindle Fire HD 8.9 won't enter fastboot mode.
I'm running Windows 7.
I installed the android SDK.
I installed Amazon's drivers for the Kindle Fire.
When I type in "Adb drivers" into the command line, I get my serial number.
When I type in "fastboot drivers", I don't get anything back.
When I type in "fastboot -i 0x1949 getvar product" , I get "waiting for device", I plug in my Kindle Fire HD 8.9 (Edit: when it is off), but it just says at "waiting for device".
I've tried typing ""adb reboot-bootloader", but that reboots the device normally.
I've read that I don't need a fastboot cable for the Kindle Fire HD 8.9 (unlike the 7).
What am I doing wrong?
Power OFF
Have you tried connecting your Kindle while POWER OFF. (Pressing power button for 20 Sec)
Steps
1. Go to elevated command prompt (admin command window)
2. type "fastboot -i 0x1949 getvar product", "waiting for device" should display on screen
3. Power off Kindle (20 sec press of Power Button)
4. Connect kindle to PC
It should go into Fastboot mode.
This will work. Hit Thanks if I helped you.
Didn't work.
mgaju said:
Have you tried connecting your Kindle while POWER OFF. (Pressing power button for 20 Sec)
Steps
1. Go to elevated command prompt (admin command window)
2. type "fastboot -i 0x1949 getvar product", "waiting for device" should display on screen
3. Power off Kindle (20 sec press of Power Button)
4. Connect kindle to PC
It should go into Fastboot mode.
This will work. Hit Thanks if I helped you.
Click to expand...
Click to collapse
I had already tried that without success. I tried it again, but it just booted into normal mode. I know i must be doing something wrong, but I'm not sure what.
ajshell1 said:
I am trying to install Cyanogenmod on my kindle fire. However, before I was able to start flashing any images or anything like that, I ran into a problem (although this is probably the best time to have a problem). My Kindle Fire HD 8.9 won't enter fastboot mode.
I'm running Windows 7.
I installed the android SDK.
I installed Amazon's drivers for the Kindle Fire.
When I type in "Adb drivers" into the command line, I get my serial number.
When I type in "fastboot drivers", I don't get anything back.
When I type in "fastboot -i 0x1949 getvar product" , I get "waiting for device", I plug in my Kindle Fire HD 8.9 (Edit: when it is off), but it just says at "waiting for device".
I've tried typing ""adb reboot-bootloader", but that reboots the device normally.
I've read that I don't need a fastboot cable for the Kindle Fire HD 8.9 (unlike the 7).
What am I doing wrong?
Click to expand...
Click to collapse
I'm in the slow lane now after trying numerous ways to root this 8.9 8.5.1 fire. Still not showing root but everything goes slow now.
Guess its better than a brick. Wonder if I can load a CM since my root failed.
ant17 said:
I'm in the slow lane now after trying numerous ways to root this 8.9 8.5.1 fire. Still not showing root but everything goes slow now.
Guess its better than a brick. Wonder if I can load a CM since my root failed.
Click to expand...
Click to collapse
Update: restored settings, back to fast but no root.
ajshell1 said:
I had already tried that without success. I tried it again, but it just booted into normal mode. I know i must be doing something wrong, but I'm not sure what.
Click to expand...
Click to collapse
Anyone figure this out? Having the same problem - won't boot into fastboot mode, just boots normally (with cable plugging in and fastboot waiting on the device). Adb also works fine.
Install android studio and get the drivers from that.
Same Problem on Kindle Fire 8.9 HD - Fastboot not work!
Hi,
I have the same problem. Adb works, fastboot doesn't work on my stock Kindle Fire HD 8.9" 2nd Generation. Here is my environment:
Windows 10 Pro x64 with latest MS Patches, Toshiba Patches, Intel Patches
BitDefender Anti Virus
ADB enabled on Kindle
Adb and fastboot Drivers installed via Android SDK
Kindle Driver install downloaded from Amazon
PC is new Toshiba Satellite P50W with USB 3.0
Drivers look okay in Device Manager
- Kindle Fire -> Driver = Android Composite ADB Interface provided by Amazon dated 12/3/2012
- Portable Devices / Kindle -> Driver =provided by Microsoft dated 6/21/2006
Symptoms:
ADB Commands work including adb kill-server, adb start-server, adb devices (returns Serial Number)
- Fastboot -i 0x1949 getvar product shows "waiting for device" in PC's CMD Window and never goes away
- I attach standard USB Cable to the Kindle that is currently Powered Down (not just sleeping) after issuing above command on PC
- Attaching USB Cable simply causes Kindle to power on and boot normally.
What I have unsuccessfully tried to date:.
Tried alternate commands:
- adb reboot bootloader (to start Fastboot)
- fastboot -1 0x1949 reboot (to exit Fastboot)
Tried USB 2.0 Port instead of 3.0 Port.
Tried reloading Kindle Drivers.
Trying Android Platform Tools Ver 23.1 RC1 instead of Ver 23.01
Tried two different "Standard" USB Cables, one Factory Cable by itself
Any Ideas? I've been trying to get FASTBOOT working so I can play with Cyanogenmod for a couple of days without any luck. Thanks.
Ken (Android Noob )
Same
Having the same issues on 5.1.1 5th gen 8.9HD. zero fastboot....
I'm having the same issue. Has anyone found a solution or found another way to root the device with version 8.5.1_user_5159720 installed?
Hate the Kindle version of the OS. I want to install CM or LineageOS (If I can find a build for it!)
Thanks!
---------- Post added at 11:33 AM ---------- Previous post was at 11:08 AM ----------
Sailing_Nut said:
I'm having the same issue. Has anyone found a solution or found another way to root the device with version 8.5.1_user_5159720 installed?
Hate the Kindle version of the OS. I want to install CM or LineageOS (If I can find a build for it!)
Thanks!
Click to expand...
Click to collapse
I did a bit more digging and found a tool that will root the device. You can find it at https://rootmaster.co Just download and install the APK on your device and allow it to root.
emaster101 said:
Having the same issues on 5.1.1 5th gen 8.9HD. zero fastboot....
Click to expand...
Click to collapse
this is a COPY/PASTE of my own post. the files i specify are the exact names, just search this section of X-DA for them. SEE BELOW.
i had the same problem with the "red screen of death" as well. i found that if i installed the "Minimal ADB and Fastboot" and / OR (i did the minimal first.... ) KFHD_SRTv1.3.5 and RUN THE APP FIRST, then when it says "waiting for device" you then plug in the ALREADY OFF tablet it then WORKS!! says "fastboot mode" on the tablet. and it is listed in device manager also.
i got BOTH apps here at this board in this section.
WARNING: i run windows XP with all updates as of 10-31-2017 (pm me for info, 2 lines of text!! ) . NEWER windows versions have "permission issues". fixes are posted in multiple topics here in the Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2 section. READ THEM!!
Start by turning off tablet. type in "fastboot -i 0x1949 getvar product". Get (waiting for device) message. Plug USB into tablet.