Develop Bugs

[Q]Help! PC doesn't recognize Kindle Fire after root

Hello, guys,
I recently rooted my Fire (6.2.2) with Kindle Fire Utility (0.9.3). Kindle is working but my PC (Win7 32) can't recognize it when i'm connecting kindle to PC. And Kindle Fire Utility can't connect to device since then (statusffline).
Maybe I forgotten to switch to normal mode?
How can I fix this?
Thanks.

talcegie [616
With your Kindle plugged in and with KFU (even if it says it is offline), press 1 for Bootmode Menu and select Normal.

meturne2 said:
With your Kindle plugged in and with KFU (even if it says it is offline), press 1 for Bootmode Menu and select Normal.
Click to expand...
Click to collapse
I tried to do this. Got the message "kindle told to reload in normal mode". Kindle reloaded but the problem left.

Sounds like you may have to reload your drivers. Is the computer recognizing the Kindle at all. I had the problem when trying to load files to the SD card that it would not show up as a storage device. I unchecked USB debugging and it showed up. If you are trying to establish an ADB connection you may want to check your ADB setup.
Try cd C:\kindleadb
adb devices
This will tell you if your ADB connection is working.
Maybe this video will help.
http://www.youtube.com/watch?v=_C-H3epEHjo

meturne2 said:
Sounds like you may have to reload your drivers.
Click to expand...
Click to collapse
I tried to reinstall drivers from Kindle Fire utility few times. No result. Is there any way to wipe them from system?
meturne2 said:
Is the computer recognizing the Kindle at all
Click to expand...
Click to collapse
Unknown Device in device manager
meturne2 said:
Try cd C:\kindleadb
adb devices
Click to expand...
Click to collapse
Gives empty output. I'm using adb bundled with Kindle Fire Utility

The same thing happened to me and I just deleted all the files that were associated with the ADB and KFU and reloaded everything. Before you do that you can go into device manager and pull up the properties for unknown device(kindle) go into update drivers and point to the file you downloaded when installing KFU.
I used this video to root mine and the part on installing the drivers works. Make sure you download the driver files attached to the video. Look under "show more" --Links in the video description.
Hope this is helping and not making you more confused.
http://www.youtube.com/watch?v=KapnjR89ICA

The problem solved. It was Windows drivers problem. I've got a USB-stick in another slot during all operations. When I removed it everything worked normally. My motherboard is Asus P5G41T-M.
Thanks to everybody who tried to help.

Kindle not recognized by PC
meturne2 said:
The same thing happened to me and I just deleted all the files that were associated with the ADB and KFU and reloaded everything. Before you do that you can go into device manager and pull up the properties for unknown device(kindle) go into update drivers and point to the file you downloaded when installing KFU.
I used this video to root mine and the part on installing the drivers works. Make sure you download the driver files attached to the video. Look under "show more" --Links in the video description.
Hope this is helping and not making you more confused.
/QUOTE]
-------------------------------------------------------------------------------------------------------------------------
I have attempted several different fixes to get my rooted KF recognized by PCs running VISTA and XP to no avail. My KF is looping TWRP v2.0.0, so I have concluded. Yet if not PC can recognize it as a device...well, please give me your thoughts and suggestions.
Thx,
R
Click to expand...
Click to collapse

Did you try again with the latest utility?? Coz it shd work..
Sent from my MB526 using Tapatalk 2

Here`s my suggestion http://forum.xda-developers.com/showthread.php?t=1882565

[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 stuck at static Kindle Fire logo

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Root Kindle Fire 6.3.2

I am trying to Root my Kindle Fire version 6.3.2, and am looking for the correct Kindle Fire Utility. I do not want to download the wrong one as the ones I have seen were for version 6.3.1 or 6.3. Anyone have suggestions?

Ichigo said:
http://forum.xda-developers.com/showthread.php?t=2192818
Click to expand...
Click to collapse
Hi...
Thanks for the linky, i grabbed it today and for some reason, it's not detecting my device. I've installed/reinstalled the drivers that came down with v0.9.8, still same results. Shows the driver Android ADB Device
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So tried to just boot it to FastBoot and same results, device not found.
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
What am I doing wrong here guys?
Thanks in advance and thank you for the work you do for us idiots.
Mark

mrlee1999 said:
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
Click to expand...
Click to collapse
Put everything back where it belongs first. Also, your computer recognizes the kindle as an Android adb device in device manager? You are on 6.3.2 also?
Sent from my Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.

Thanks for replying
I'm on 6.3.2.
It was seeing it as android adb.
I do have it on 1.4.a as well.
I did remove all of the drivers to the point win7 was showing kindle with an !. Reinstalled and rec'd same results. Got pissed at it and removed drivers again rebooted and removed the files under .android. When I get a chance, i'll try reinstall. Maybe by manually deleting the inf file will do some good???. I'll update the post when I have a chance to work on it.
Sent from my SCH-R530U using Tapatalk 2

mrlee1999 said:
Thanks for replying
I'm on 6.3.2.
It was seeing it as android adb.
I do have it on 1.4.a as well.
I did remove all of the drivers to the point win7 was showing kindle with an !. Reinstalled and rec'd same results. Got pissed at it and removed drivers again rebooted and removed the files under .android. When I get a chance, i'll try reinstall. Maybe by manually deleting the inf file will do some good???. I'll update the post when I have a chance to work on it.
Sent from my SCH-R530U using Tapatalk 2
Click to expand...
Click to collapse
Have you tried running KFU under compatibility for Windows XP SP3? Once you do that, it'll automatically ask for admin privileges.
Also, does your device show when you run the command
adb devices
Click to expand...
Click to collapse
on a terminal (or command prompt, on Windows) window?
Sent from my Muffin masquerading as a phone in the coffin.

Thanks
Removing the driver and deleting the files in the .android folder did the trick.
Thanks Everyone!!!!!
Mark

The one that ichigo said is good.

So I was using the new KFU 9.8+ on my first gen kindle (6.3.2)
and during the procedure while I think it was attempting to install FFF bootloader it was on <waiting for device>, my laptop lost batter life and shut down. Upon booting up my computer and trying KFU again
ADB Status: Offline
Boot Status: Unknown
My kindle now displays the logo. I assume it's bricked right now.
Are there any remedies to fix this?

HypothermicInferno said:
My kindle now displays the logo. I assume it's bricked right now.
Are there any remedies to fix this?
Click to expand...
Click to collapse
It is on the orange logo? And it won't boot properly? So the kindle just stays on that screen without getting dim or anything, right?
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.

Bricked as well
My fire also appears to be bricked. "Kindle Fire" is displayed and the screen doesn't dim or anything like that.

mrlee1999 said:
Removing the driver and deleting the files in the .android folder did the trick.
Thanks Everyone!!!!!
Mark
Click to expand...
Click to collapse
I know how to delete the .android folder, but how can I be sure that the deleted drivers are the one associated with adb and not with other programs ? are those the drivers in Windows/system32 ?
How do you do that ?
Thanks

nugroho2 said:
I know how to delete the .android folder, but how can I be sure that the deleted drivers are the one associated with adb and not with other programs ? are those the drivers in Windows/system32 ?
How do you do that ?
Thanks
Click to expand...
Click to collapse
The .android folder is found under the root of your sdcard or you ext-sd. To remover the drivers:
If you are on Windows 7/8:​
Hit the "Start" button on the keyboard, and when the homescreen (Windows 8) or the Start dialogue (Windows 7) pops up, type in "Add or remove".
Hit enter on the highlighted option, which should be "Add or remove programs". (Note: You may have to go into the settings tab if you are running a search on Windows 8)
This will show you a window where all the apps that are currently installed on your computer shows up. (Metro apps don't show up here.) Look through the list until you find your KF drivers. This should be listed as something like this: Kindle Fire Drivers
Highlight the driver and look towards the top of the window. You should see that a "Change/uninstall" button has popped up. Click on that and follow the on-screen instructions to uninstall the drivers.
You're done!
If you are on an older version of Windows:​
The procedure is the same, only you have to go into Control Panel > Add or remove programs to do this.
Good luck rooting your KF. :good:

Kindle Fire Tool
My company is making a Kindle Fire Tool for Windows and Mac. Their are several options that might help you like "Toggle Unbrick" You can also root on Android 6.3.2.
Contact me if you have any questions: [email protected]

thebane90 said:
My fire also appears to be bricked. "Kindle Fire" is displayed and the screen doesn't dim or anything like that.
Click to expand...
Click to collapse
I had the Same issue found it was just stuck in Fastboot mode and Windows does not handle it well at all. I was getting a USB device not recognized error and wouldnt let me change the driver for it. To get back booting again I used
http://forum.xda-developers.com/showthread.php?t=1850038
Followed the direction and everything was good.... Almost I found no matter what computer I use fastboot always comes up as a bad device. :crying:
But that should help you with the "Brick"

Kindle Fire 6.3.2 successfully rooted
mrlee1999 said:
Hi...
Thanks for the linky, i grabbed it today and for some reason, it's not detecting my device. I've installed/reinstalled the drivers that came down with v0.9.8, still same results. Shows the driver Android ADB Device
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So tried to just boot it to FastBoot and same results, device not found.
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
What am I doing wrong here guys?
Thanks in advance and thank you for the work you do for us idiots.
Mark
Click to expand...
Click to collapse
I have the same error.
What i did was...
1. Download KFU 0.9.9 (http://forum.xda-developers.com/showthread.php?t=2192818)
2. Download TWRP (http://techerrata.com/browse/twrp2/blaze)
3. Download FFF (http://forum.xda-developers.com/showthread.php?t=1369405)
4. I rename them as "twrp" and "fff" respectively and place them in the "recovery" folder in KFU
5. I manually install the drivers
6. I check in the device manager to show me "Android Phone - Android Composite ADB interface"
7. I run the KFU
and that was all...
I check the root was complete with the https://play.google.com/store/apps/...GwsMSwxLDMsImNvbS5qb2V5a3JpbS5yb290Y2hlY2siXQ..

not visible on my pc.
Hey, I took the first step to root my kf on 6.3.2. I can no longer see the devise on my computer to do anhything else. I only loaded the utility file onto the devise and now what? I can't even delete it. Any thoughts?

Okay... here goes!
Vlasp said:
The one that ichigo said is good.
Click to expand...
Click to collapse
*Takes a deeeeep breath* okay, I thought it looked like the most promising instructions I've found so far too... so, from a TOTAL novice at all of this, here goes! Thanks for the endorsement ( I will definately thank him too! )

So, I went through all the steps outlined by xarenmi, but it STILL doesn't recognize my kindle when I try to use the run tool.
I'm not the best with all this, so...

Help...
Hey, I finally got the google winusb driver installed (I had to do it via SDK manger) but it still recognizes my kindle as "kindle" under "other devices" in the device manager. Also the KFU will not recognize it.. period. just nothing and I'm getting really fed up.
I have followed all instuctions to the T and I am still having issues.

I tried to install twrp and now my kindle fire hd 8.9 and now it does a boot loop

I tried to install twrp and now my kindle fire hd 8.9 and now it does a boot loop. I've tried to get into the fast boot or use the kindle fire unbrick utility but the reboot doesn't let it get a chance to connect. I believe I used the wrong twrp version and or messed up with a setting in the kindle flash app. I bought a factory/fastboot cable and want to know how to fix this. It's not here yet but I want to know how to fix it despite this. I've tried the majority of methods including the kindle utility. When I go to recovery it just hangs on a black screen. My computer recognizes it but ADB/Kindle Fire Utility do not. my PC recognizes it with a funny name and lets me open it and it's files. It's rooted and I don't know how to check bootloader. Thanks in advanced!

I am new at this myself, I was stuck in a bootloop myself & I to had trouble getting ADB to work, sounds as tho you don't have the drivers installed yet. The part in the directions that seems to be left out is to click on "show all" then click next. I waited forever for the list. So, control panel> device manager> (right click on the troubled device) >update drivers> pick from list> click " SHOW ALL"> hit next then at the bottom> wait for it, wait, waiting. When the list comes up, go down to Google and click it> click next, i think it was, then you should see ADB drivers. If it worked you should now see your device in the device manager under Android device. Now I don't remember where I got the files to bring it back to stock but, I think under one of "DragonFire's" post he had perfect directions to recover back to stock, I think the files might be there as well. I hope this helps you, I too have yet to get a rom to flash right and have used the ADB to reset a few times now. Time for me to try to again