Develop Bugs

Kindle Fire is stuck at boot screen, (no animation). Help!

Hello Everyone,
I will try to provide as much details as I can from what I remember.
Basically, I tried to ROOT my device and install TWRP. However, I messed it up the first time. I tinkered with it for hours but it still couldn't work until finally, after hard resetting for the unlimited time, it booted up.
The problem though, is that it wasn't rooted and TWRP wasn't installed when it came up so I tried it again. Second try, second time it was messed up. Annoyingly, I don't know what I did earlier to make it work. The second instance it happened is just like the first.
Just to be clear, this isn't the boot screen where the kindle fire logo is animated (has reflections). In my case, its the logo as is, stuck on the screen just like that. Tried hard resetting, doesn't work.
What do I know?
1) From my earlier experience, it has lesser to do with the system (PC, Mac) and drivers since I managed to get it boot up again without being connected the first time
2) If I do connect it to the PC, it says Cannot Start Device/Unable to Start Device. Code:10. That's it. Even if I reboot the device, its still the same.
3) If you connect it to the Mac, it is detected in system preferences. Problem though is that I tried using adb and just like its windows counterpart, there are no devices detected.
THOUHGTS:
1) I know I just have to get it to be recognized and I can change the bootmode. Something's telling me that its a boot mode problem only. In my earlier V3X phone, I used to TP (testpoint) if anyone's familiar with that, or shortcircuit the board to get it out of the 'loop'. Do we have that with the kindle fire?
2) What operating system would it be easiest to get the device detected. I'm hoping that if there's lesser complications with the device being detected by the computer, be it mac, linux or windows, I can change the bootmode. my technical instinct tells me it has something to do with boot mode.
What have I done already?
1. Let me see, I believe I tried hard resetting it for ALOT of times already
2. Reinstalled drivers on PC. Used both Android and Kindle Fire Utility drivers. Even checked the /android folder
3. I'm using a Nokia Micro-USB cable. I'm not sure if that has any impact on the device or its effectiveness but I will try to pick-up another cable today and post later.
I would really appreciate if anyone can help. It sucks that I tried this just after unboxing the unit. I haven't even tried doing anything on it yet.
If you can help, ANY help would be appreciated.
Thanks mate!

had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
the entry for 18D1 in adb_usb.ini is missing - had to add it
the other entries are allready in version .6 android_winusb.inf
if you have troubles to remove old drivers use this:
http://support.microsoft.com/kb/315539/en-us
unplug/replug and install the drivers from .6 from scratch
it's not needed to reboot the computer - works immediately
waiting to get your status ...

b63 said:
had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
waiting to get your status ...
Click to expand...
Click to collapse
Did you solve your problem?
My kindle is recognized by my computer but it as either ADB device or Composite ADB device (depending on what drivers I use to install it). Problem is that it says Cannot start device. Code Error: 10. Tried shutting down/restarting PC, still the same.

updated my initial post again ... (ms-link)
yes solved it in minutes
make the additional entry in adb_usb.ini
use only the drivers from .6
i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
whats your status ?

i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
Click to expand...
Click to collapse
I did this but it still says device cannot be started.
make the additional entry in adb_usb.ini
Click to expand...
Click to collapse
0x18D1 -- is that what I'm supposed to add to adb_usb.ini?

yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually

b63 said:
yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually
Click to expand...
Click to collapse
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.

kaswistry said:
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.
Click to expand...
Click to collapse
all this works using windows 7

dustyjerran said:
all this works using windows 7
Click to expand...
Click to collapse
I did try this yesterday on Windows 7 but most guides I see do it on older versions. I will try again a little later. Thank you.

I tried it on Windows 7. Still the same error. Kindle is frozen and on Device Manager it says "This device cannot start. (Code 10)"

I ran into the exact problem yesterday. I thought I bricked my kindle. That was scary. Anyway, the problem is that you're stuck on fastboot, mode 4002 instead of a normal mode 4000.
Following rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/
You'll need to add a new vendor id (0x18d1). However, even with that the device still will not be recognized right away. Following another user's suggestion on that same thread, I let the battery drained out. Once that's done, reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Then do the adb commands (even if it doesn't show any device attached)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Your device will reboot out of the stuck "kindle fire" logo screen. If your device goes dark after, it just means that the battery need to recharged first. Another scary moment for me. You can unplug and use the wall charger, much faster than charging by PC. After 5 - 10 minutes, you should get back to your normal screen. Then, just use the Kindle Utility to install TWRP.

You'll need to add a new vendor id (0x18d1).
Click to expand...
Click to collapse
I added this already
reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Click to expand...
Click to collapse
Actually, the problem with mine is that it's detected. However, it shows up as Code:10, The device is unable to start.
Still, I'll try to drain it first, tinker with it next and see what happens. That or I'll wait for tomorrow and open the whole device already and see if I can OMAP it.

Mine also did show up as code 10, and sometimes code 43 ... I tried uninstalled the driver and reinstall it manually each time and eventually showed up as unrecognized ... so I tried the battery drain ... I even tried putting it in the freezer to quicken the drain but not sure if it actually help ..

I tried the battery draining. Nope, still didn't work
UPDATE: I take this back. After draining the battery, I would like to confirm that the issue has been fixed. Thank you, THANK YOU Everyone! )
I REALLY APPRECIATE THE EFFORT. HAPPY HOLIDAYS! )

A family member recently got a Kindle Fire, I tried to flash recovery but it got stuck in fastboot mode. Windows will recognize it as uknown device but Linux won't detect anything in fastboot or adb.
I will try battery drain out since kaswistry said it worked
If all else fails, I will try this.. http://forum.xda-developers.com/showthread.php?t=1405052
EDIT: nevermind lol, this worked.. http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11 even though i tried it several times already..

I have the same problem too, the kindle fire stuck at the boot logo
kf utility show that when i try to restore or other option!
Changing bootmode doesent work at all
*imageshack/photo/my-images/10/60506677.png/[/url] (imageshack link)
KF utility status fastboot... offline
*imageshack/photo/my-images/834/kfustatus.png/
My computer have the right driver!
can anybody help me?
*sorry for my bad english*

Could it be that something destroyed my FireFireFire boot? My KF always gets stuck in fastboot when I try to flash ... obviously quite annoying.

u guys need to talk to vashypool in irc and he can fix it!! he fixed mine and mine was a complete brick

If it gets stuck in fastboot you need to run the command fastboot idme bootmode 4000 from the Android SDK.
Sent from my Kindle Fire using Tapatalk

In my case, i have tried to install the original 6.2 kindle firmware with TWRP. After that, the kindle staying stuck on the boot logo... This is me story... I think my kindle is stuck on fastboot! I tried to change bootmod with FK utility v.6
This is what kf utility gave me, when i try to reinstall twrp
imageshack.us/photo/my-images/10/60506677.png/
And this is the kf utility status
imageshack.us/photo/my-images/834/kfustatus.png/
Is anybody can say me, if my kindle is bricked for ever? Or have a solution
Happy holiday btw
#sorry for my poor english#

[Q] Kindle Fire Root Help, URGENT!

I am having a serious problem with my Kindle Fire, I am worried that it has bricked. For the past month ive been trying to fix it and nothing ever worked out. What happened was I tried to root my kindle using Kindle Fire Utility, and everything seemed fine at first. I turned my Kindle on and everything was normal, then I turned it on again and all it does is flash on and off at the screen with a yellow triangle with a flame in the middle of the triangle and it says "press power button for recovery." The kindle does not respond to anything and it will not turn on unless connected to the computer and it will not turn off until i disconnect it. My computer also does not recognize my Kindle.
Kindle Fire Utility says to just switch it to normal mode by going the "fastboot menu" and simply switching it. But when i do the program just sits at the screen saying "waiting for device" and I think its because my computer simply will not recognize it.
Others have said to go in the command prompt and type "adb shell" but that wont work either. It says something like "adb is not recognizable as an internal or external command, operable program or batch file. So i have no idea what to do there.
I never installed TWRP so i tried tonight, and I downloaded the image and i did what it tells me to do in the command prompt, but once again it would not me recognizable as an internal or external command.
Im all out of ideas and have not found a single person with the same problem as me and I need any help I can get from anyone. I GREATLY APPRECIATE ANYTHING!

http://forum.xda-developers.com/showthread.php?t=1623244
http://forum.xda-developers.com/showthread.php?t=1552547

Charged
Well I charged my Kindle overnight and it is staying on and i can turn it on and off whenever, i connected it to my computer and the computer found it but it couldnt find any drivers for the Kindle and it sort of ignores the Kindle. The Kindle fire utility still says "waiting for device" and when i try to install drivers from the Kindle fire Utility folder it tells me "There was no driver found for this machine" What should i do now?

Read this first...
http://forum.xda-developers.com/showpost.php?p=23747567

Have you tryed holding the power button down for like 20 seconds to power it completely off then powering it back on?

Read it
I read the page and they said I can reverse it with SDK, or KFU. Ive tried with Kindle Fire Utility but how do i do it with SDK??

Thepooch said:
Have you tryed holding the power button down for like 20 seconds to power it completely off then powering it back on?
Click to expand...
Click to collapse
Yes ive tried and it continues to do the same thing

I'm a little confused about the reverse it idea but the drivers were there before why aren't they now? If your referring to going through the process to set a the proper environment you need Java development kit then open the sdk manager and download tools and 2.3 platform and the Google driver this is a lot of excess bulk that may not be needed try using system restore to roll your computer back to a date before you messed with the driver's. Download a fresh copy of kfu rerun the driver without your kindle plugged in then see what you get.

SDK will let you do the same thing KFU does, only manually. If you can't get KFU to work, the SDK probably won't help.
In order for either to work, you need to make sure your drivers are in order.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

The yellow triangle your looking at is the bootloader which isn't bad but the fact that you don't have twrp installed and can't get past it and your computer either doesn't recognize or will not communicate with the device is bad. Your driver's must be functioning to make it past this via adb.

Thepooch said:
The yellow triangle your looking at is the bootloader which isn't bad but the fact that you don't have twrp installed and can't get past it and your computer either doesn't recognize or will not communicate with the device is bad. Your driver's must be functioning to make it past this via adb.
Click to expand...
Click to collapse
Could I do it on a different computer then?

Many people have had success with that, yes.

Unsigned drivers
Well i tried on the new computer and it wouldnt let me download the drivers but i found out about changing the unsigned driver settings on my original computer but i have windows vista on the original one and windows XP on the other, the Windows XP computer was easy to see the unsigned driver setting(which didnt work out) but i cnat find it on the vista. Where is it located?

I also tried the code: bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
The cmd told me that my access was denied

soccerman9 said:
Well i tried on the new computer and it wouldnt let me download the drivers but i found out about changing the unsigned driver settings on my original computer but i have windows vista on the original one and windows XP on the other, the Windows XP computer was easy to see the unsigned driver setting(which didnt work out) but i cnat find it on the vista. Where is it located?
Click to expand...
Click to collapse
http://www.google.com/search?mmns=0...action=devloc&q=disable+unsigned+driver+vista

soupmagnet said:
http://www.google.com/search?mmns=0...action=devloc&q=disable+unsigned+driver+vista
Click to expand...
Click to collapse
It says i gotta choose a device/file, what file would it be? would it be the "install_drivers" in the kfu?

There should be two files:
android_winusb.inf & adb_usb.ini
...both are somewhere in the KFU/drivers folder

soupmagnet said:
There should be two files:
android_winusb.inf & adb_usb.ini
...both are somewhere in the KFU/drivers folder
Click to expand...
Click to collapse
I found the adb_usb but there two of the other, they are called
androidwinusb86
&
androidwinusba64
Does it matter which one i choose?

Well i got the Google Usb driver installed, but the problem still remains where my kindle is connected and my computer says its finding a driver for it, but then my Kindle disconnects too fast and the computer cannot find any drivers because "the device was unplugged." I noticed that when i start the kindle while its connected the power button light is green, and thats when my computer sees the Kindle, but then the light turns orange and then the computer loses it. What should i do now?

That seems to be a typical problem with Vista. I'm not sure what causes it, but it would probably be beneficial for you to try a different computer, if you have one available.

[Q] Broke Kindle Fire's Ability to Mount

Hey I'm a brand new member so I apologize in advance if my problem has been solved already, however, I could not find anything on any of the threads. Okay so I am severely confused right now. I have had my Kindle Fire for almost a year now and this problem has never occurred. Ever since I got my Kindle I have been experimenting on it. I rooted it and have flashed many different custom roms. I had been using TWRP Recovery 2.0 for a long time and when I found out that it was outdated I updated it to the new 2.2.1.1 version...Everything seemed to be working perfectly until I tried mounting USB storage in the new TWRP...It did not work. My computer wouldn't recognize it. I kind of just let this slide since I figured I wouldn't need to mount USB storage in TWRP unless it was an emergency. A while later I switched back to the Kindle's stock rom. That's when I noticed that it would not mount...Not only was TWRP not mounting, but it was my Kindle altogether. I deleted all drivers that had any thing to do with Android from my computer. After restarting both my computer and my Kindle I tried mounting again...Nothing. The drivers weren't even reinstalling. To test wether this was a problem with my computer or my Kindle I got my brother's Kindle Fire (Never had any tweaking done to it) and mounted USB storage. It installed the drivers and mounted just fine. I then plugged my Kindle back in and it mounted just fine also. I thought I had solved the issue, but about an hour later I tried mounting my Kindle again and nothing happened. My brother's Kindle will mount (Actually there are a total of four Kindles in my house all of which have not been tweaked except for mine) but mine won't do anything. As a last resort I deleted EVERYTHING with TWRP and flashed the Kindle Fire 6.3.1 update.zip. My Kindle is now true factory default (no root, custom recovery, etc...). I thougt for sure this would work but IT STILL WON'T MOUNT USB STORAGE!!! When I plug my Kindle in and go to "Devices and Printers" it recognizes my device as a "Kindle" but I just cannot get it to mount! I am now stuck with a Kindle that cannot be re-rooted or anything due to the fact that it cannot be recognized with ADB. Sorry for the long post...I am just trying to give as much information as possible. By the way I am running Windows 7 and my Kindle is the only one that will not mount which makes this problem have nothing to do with drivers or my computer. Any help is appreciated. Thanks.

Wheww okay well try a factory reset this will wipe your sdcard as well. It should resolve most your problems. There are multiple things that can cause this to happen but one thing that really comes to mind. Are you ejecting your kindle before hitting the disconnect button? Just a wild guess but failing to do so can cause this disorder the very next time you plug it in. Something that could resolve minor sdcard issues is
Code:
fastboot oem format
don't let this make you to crazy yet RC soupmagnet should be releasing something very soon that will solve the majority of SD card mount problems hint hint . You will need to reroot and flash a custom ROM on it to have success though. So if nothing works hang tight and stay tuned.

This might help
http://forum.xda-developers.com/showthread.php?p=33109015#post33109015

Thepooch, no I had not been ejecting it before disconnecting. I'll do that from now on. Also commands do not work because my computer doesn't recognize my Kindle as either a storage device or an ADB device, and what does it mean what it says "fastboot not found"? I made sure I have the fastboot.exe in my ADB folder...Soupmagnet, I can't get those commands to work since I'm no longer rooted and my computer doesn't recognize me...

Nihilian said:
Thepooch, no I had not been ejecting it before disconnecting. I'll do that from now on. Also commands do not work because my computer doesn't recognize my Kindle as either a storage device or an ADB device, and what does it mean what it says "fastboot not found"? I made sure I have the fastboot.exe in my ADB folder...Soupmagnet, I can't get those commands to work since I'm no longer rooted and my computer doesn't recognize me...
Click to expand...
Click to collapse
Have you installed your adb drivers?

soupmagnet said:
Have you installed your adb drivers?
Click to expand...
Click to collapse
Yeah I downloaded the newest Kindle Fire Utility and installed thoose drivers. When I plug my Kindle in and go to "Device Manager" it lists it as an android phone with ADB Interface. If I plug any other Kindle in then it installs new drivers and doesn't list the ADB Interface. Is this normal?

Nihilian said:
Yeah I downloaded the newest Kindle Fire Utility and installed thoose drivers. When I plug my Kindle in and go to "Device Manager" it lists it as an android phone with ADB Interface. If I plug any other Kindle in then it installs new drivers and doesn't list the ADB Interface. Is this normal?
Click to expand...
Click to collapse
I don't use Windows so I couldn't tell what's normal for that OS.
Use the tutorial here to confirm your drivers are installed properly. Then Shift + right-click on your KFU "tools" folder with adb.exe and fastboot.exe, and select "Open command window here". Enter your adb or fastboot commands there and see how it goes. Start with "adb devices" to see if you are connected. If not, reinstall your drivers and try again.
Some ROMs have different product IDs than the stock OS so you may want to look into that if you are using a custom ROM, and edit your androidwinusb.inf accordingly. I know some JB roms have a PID of 0004 instead of 0006.
If for some reason Windows refuses to cooperate, you could always set up a Linux LiveUSB and get it done a lot easier.

Okay so I've been fiddling around with stuff. I completely uninstalled all Android drivers again then restarted my PC and Kindle. This time I plugged my Kindle in and it installed the correct drivers. It mounted USB just fine. When I tried reinstalling the ADB drivers that came with Kindle Fire Utility it erased the Kindle's normal drivers, so now it won't mount anymore...at least I know that it is a driver problem and that my Kindle doesn't need to be repartitioned. I'm really getting sick of Windows and its annoying drivers...Any ideas on how to get all the drivers to work? If not I think I might just install Ubuntu and screw the need for drivers.
Sent from my M886 using xda app-developers app

If you run the driver bat packaged with kfu with the device plugged in sometimes it will waste the mass storage drivers. It`s always best to run it then plug the device in and see what windows decides to install. Unplug, replug, unplug, replug as well as try this while in recovery because it will also attempt to install the drivers as well in recovery.

Thepooch said:
If you run the driver bat packaged with kfu with the device plugged in sometimes it will waste the mass storage drivers. It`s always best to run it then plug the device in and see what windows decides to install. Unplug, replug, unplug, replug as well as try this while in recovery because it will also attempt to install the drivers as well in recovery.
Click to expand...
Click to collapse
Sweet. I tried it and now everything is working perfectly. Thanks for your help guys.

Nihilian said:
Sweet. I tried it and now everything is working perfectly. Thanks for your help guys.
Click to expand...
Click to collapse
I downloaded the lates kindle fire utility and I enabled debugging, I can see my files but when I run the utility file the adb says offline. I cannot figure it out. : (

[Q] I need help. Bad.

So, I tried searching for days on how to fix my problem.
A little while ago I rooted my Kindle Fire, and it was great. Then I did something. Not sure exactly what. But It ended up just doing nothing. When I boot up the Kindle it shows the blue and white Kindle Fire logo. Nothing else past that (unless I go to recovery.) Now, my computer doesnt recognize it anymore, even after doing most of the driver updates that people on here have said to do.
I need help, basically, getting it back to normal, so I can give rooting a try again. Now that I know what exactly I am dealing with, I can do this and not screw everything up.
First, the computer says the driver is installed, yet it doesnt recognize it.
Second, (before the driver mishap) KFU said it was connected but the adb was unknown.
Third, I have CWM and I tried to flash the normal Amazon update to bring it back, and it says"it cant open it (bad)".
Now, I would really like some help with this. I'm just at a complete lost.

Now should I put that into command prompt in the adb part? because it just says fastboot is not recognized.

Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.

Now its just not connecting to the computer. I installed Android sdk and everything and its just not working. It says the driver is installed but there was an error because a problem had occurred. Any help? :crying:

As soon as you get tired messing with drivers you can move on to something that works http://forum.xda-developers.com/showthread.php?t=1850038

ManofFishFry said:
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Click to expand...
Click to collapse
I hope u r on windows PC..
first after u set up adb, make sure u install adb drivers that came with kindle fire utility with ur kindle fire unplugged..if u had plugged in kindle fire while doing that, go to device manager and uninstall that device and its driver software and start up from beginning..
keep kf unplugged and install driver..u dont get usb debugging option in stock kf rom..its enabled if u have installed the drivers properly..ur kindle fire appears as android phone in device manager if everything u hav done is correct..
then boot up ur kf..that blue and white kf logo is of firefirefire bootloader..i hope its v1.4a and u see it on right top of the screen..if its stuck there then open command prompt as administrator on ur pc..connect ur kf to pc..type in to cmd
Code:
fastboot devices
if u see something under list of devices attached that will be ur kindle fire(unless some other android device is connected in fastboot mode lol)
Because kindle fire, as far as i know, can only boot into 3 bootmodes(normal, recovery, fastboot) unless u have altered the partition table to install different roms and multiboot ur kindle fire..
if fastboot command is not recognized, try setting the path to where fastboot.exe is present in KFU folder
alternatively u can go to folder where fastboot.exe is located and right click while holding shift and selecting 'open command window here' and fastboot needs to firefirefire bootloader to be installed on ur kindle fire..
also u can try this..
JUST GO TO RECOVERY..twrp has always been a better recovery software than cwm based thing available for kindle fire at least for me..if u go to recovery, ur kf will definitely show up as an adb device..u can change the bootmode using this..just type in:
Code:
adb devices
if ur kf is seen as in recovery then type this in cmd
Code:
idme bootmode 4000
reboot
just report if this worked..

okay well, I deleted all the drivers and started from the beginning. Yet, after running the install_driver.bat I plugged my Kindle in and it still says device not recognized. Now, you how can get adb working? It is coming up as unknown device. Its just seeming like theres something wrong on the kindle part. But hey, what do I know. haha

lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038

But doesn't that require linux? I have windows 7. Is there something like that for windows?

Thepooch said:
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.

This is what I get when I try to install the driver....

To run soupkit all you need is at least a 2 gig usb flash drive ubuntu 12.04 32 bit and universal usb creator. By the way your problem with the driver is you (or how you`re going about it), You would trip if I got on your computer and got it to work or could at least tell you why its not working. that`s why I suggested soupkit if you would of actually read the information I gave you, I wouldn`t have had to tell you twice and you would know that to use it it`s not required to be installed on your computer. But hey catch me online I can either help you fight through windows crappy drivers or help you set up soupkit I`m always game for a challenge When updating the driver you need to point it to the 32 bit version of the driver for instance on my computer it`s located here C:\Documents and Settings\HP_Administrator\Desktop\Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers. After it`s ran unplug and replug device if that doesn`t work power off and power on while connected this generally does the trick when windows finally catches on it will install android adb interface, this is the fastboot driver (if you`re stuck in fastboot). Then select option 1 in KFU for changing bootmodes, then option 1 for normal if it does nothing power off and power on while connected it should then detect the kindle and reset the bootmode to normal. Pm me later I will be online all evening and most every evening I will help you sort it out.

Josepho1997 said:
Whoops! Somehow my post was posted twice. I didn't even get to see your reply. Sorry!
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
this is what I get when I try this... (btw im working with firefirefire. its got the blue and white kindle fire.)

Why don't you let me take a look?

Dark__king said:
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
Click to expand...
Click to collapse
Yes soupkit can fix mounting problems.

This is a very interesting issue with this Kindle windows detects it as unknown usb device, drivers are installed properly from what I can see. Ubuntu with soupkit ran on it fails to detect it in recovery or fastboot. multiple cables tried, lsusb doesn`t show the device connected. I really think this one the computer is the problem, because it`s the only unchanged variable.

Firekit may be the only option if Linux won't detect the device. Before doing that, make sure a USB 3.0 port isn't being used and try a fresh install of Linux to be safe. Otherwise, it seems putting it in USBboot is the only option for getting Linux to detect.
I'm not exactly sure what causes the unknown device error, but it almost always means there is something wrong with the bootloader, and it seems as though Windows might be the main culprit. Not sure why exactly, but it may be similar to the problem soulweeper51 had. Possibly a hardware issue involving the computer's USB port or the motherboard itself.

@ManoFishFry has doomlords cwm recovery and he flashed JB at first I thought it was an issue with cwm not being detected but the fact that it`s not detected in fastboot raised my eyebrows. The bootloader appears to be functional but I cannot rule out any minor state of being broken in another fashion when lsusb returns null. The computer doing the work had never been used prior to the incident so driver install didn`t take place till after the fact. The usb ports are all either 1.0 or 2.0 no 3.0 ports are being used. An alternate computer would be nice to rule out the computer itself @ManoFishFry only has a dinosour of an xp machine as alternate use of is not possible yet, not that it would even be possible to install drivers because of the typical unsigned driver failure of xp and booting ubuntu isn`t happening at the moment on this machine.

I'm willing to bet it is the bootloader.
Just USBboot and get it over with.

We did try usb boot once but it didn`t work will keep trying.

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