Database Users

Rooted KF not started This device cannot start. (Code 10).

Hi,
Could REALLY do with some help here ... starting to pull my hair out. Rooted my KF with the steps from http://forum.xda-developers.com/showthread.php?t=1410766. Got through the root and the process hung on the recovery install.
Now my KF just shows the Kindlefire booting screen. I've tried loads of edits to the drivers re-installed many times, etc ..
In device manager, I see the device as Android Phone / Android Composite ADB Interface. The problem is that the device status always stays at: This device cannot start. (Code 10).
adb returns nothing. It's like I can't connect to the device at all.
Can ayone please help?

i think its stuck in fast boot??

http://forum.xda-developers.com/showpost.php?p=20729347&postcount=5

Tried the various restarts as suggested in the thread. No luck.
Device Manager still has a problem with the device. KFU can't connect or see the device.
I've tried re-installing the drivers several times, but always get the same result. Searched the threads for a similiar problem and it seems most issues are when people get to the the Yellow Triangle page. I'm not getting that far.
Seems to me to be a driver problem, but I can't trick Windows into figured it out.

follow and join this thread:
http://forum.xda-developers.com/showthread.php?t=1413495
i don't want to write everything twice

Still not working. tried that link and everything in it. Been struggling woudl this for a few days now, so any help would be appreciated.

When kf is pluged in right click my computer then click manage then device manager there should be a yellow ! Next to a device. What device does it show next to it
Edit; sorry answers in the question. Lol
Keep it plugged in. Hold down power for 30 secs turn back on
What does your pc say
Sent from my Kindle Fire using xda premium

NewKindleUser said:
Still not working. tried that link and everything in it. Been struggling woudl this for a few days now, so any help would be appreciated.
Click to expand...
Click to collapse
some more information would be helpful
os/bit of computer ?
have you tried to remove the old drivers ?
http://support.microsoft.com/kb/315539/en-us
which drivers have you used ?
in the meantime there is a new kfu available 0.9.2 which has a new driver installer.
http://forum.xda-developers.com/showthread.php?t=1399889
would download it, extract to c:\ and rename to "kfu" cause it don't likes spaces in the pathname - sometimes. run install_drivers.bat
then run the utility with run.bat and try to set bootmode to normal (option 1)
the 3 status messages from kfu may also be helpful for us
this post from vashypooh might also be helpful:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506

Thanks for direction and feedback.
I had previously installed the drivers with kfu 0.8 and 0.9.1.
I'm using Win7 x64 running in a VM (I have a MAC) as well as WinXP 32.
I've downloaded and installed the drivers from the latest KFU. When I connect the KF, it appears under the USB Controllers Group in Device Manager with a Yellow Warning Triangle. KFU cannot connect:
ADB Status: Offline
ADB Rooted: No
Boot Status: Unknown

NewKindleUser said:
Thanks for direction and feedback.
I had previously installed the drivers with kfu 0.8 and 0.9.1.
I'm using Win7 x64 running in a VM (I have a MAC) as well as WinXP 32.
I've downloaded and installed the drivers from the latest KFU. When I connect the KF, it appears under the USB Controllers Group in Device Manager with a Yellow Warning Triangle. KFU cannot connect:
ADB Status: Offline
ADB Rooted: No
Boot Status: Unknown
Click to expand...
Click to collapse
are both win systems running on the mac ?
that will not function - someone ported kfu to mac - will try to find it for you
here it is:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653

The WinXp isn't on the MAC. But the Win7 one is.
I'll try the MAC port as well.

NewKindleUser said:
The WinXp isn't on the MAC. But the Win7 one is.
I'll try the MAC port as well.
Click to expand...
Click to collapse
then you have 2 options:
1. try the mac port
2. use winxp machine and be prepared for a little hassle with the drivers
good luck !

I've seen it show up as unknown USB device before. You can't install the drivers when it's in this state. Usually doing a hard reset on the device (hold power for ~20 seconds to turn off then turn it back on) fixes the device and it will show up as either Amazon Kindle with a yellow exclamation (without drivers) or as ADB Device or some such if you do have the drivers. If it shows up as Amazon Kindle without drivers, install them (right click, update drivers, browse your pc, point it to the drivers folder inside KFU). You should then be able to run KFU option 1 and select Bootmode Normal.
If you can't get that to work, download the android SDK on your Mac, use the SDK manager to download the Android platform-tools, open up a Terminal, cd to that platform-tools directory, and run
./fastboot -i 0x1949 oem idme bootmode normal
Which should get you back in normal mode.

I registered just to say that I thought I had bricked my KF (it was just stuck in fast-boot). I tried all of the driver fix stuff but the Kindle Fire Utility still said that no Kindle could be found. I tried your suggestion, skourg3, and it worked perfectly. (slight addendum for the uninitiated: the command is fastboot -i 0x1949 oem idme bootmode normal).

Kindle fire not seen

Ok so I am new hear and I was reading in THIS POST about installing TWRP using the Kindle Fire Utility. So I installed the drivers as directed and I see in my device manager "android ADB device" and in my taskbar I can eject the kindle. In File Manager I do not see the Kindle fire and the Kindle Fire Utility is not seeing my Kindle Fire. I am stuck and cannot post in the above forum because I have not made enough posts. Any help would be greatly appreciated. I would like to install Cynogen Mod to my Kindle fire to be able to access the full capabilities of this wonderful device.
Thank you

a good method to start is using kfu as you suggested but there are some tricks to get it running:
- place it to c:\ and rename it to "kfu" (it don't like spaces in pathname)
- try to install the correct drivers by running install_drivers.bat else install/update them manually:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
- pay attention on the driver verification level:
http://forum.xda-developers.com/showpost.php?p=22065426&postcount=846
- the drivers are in c:\kfu\drivers\kindle
- right drivers for each mode:
normal & recovery boot -> android composite adb interface
fastboot -> android adb interface
once you got rid of the drivers you have to update the run.bat of kfu to work with burritoroot3:
http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
now you should be good to go ...

Thank you BB3 I will give this a try later tonight. appreciate the help

man install buritoroot and TWRP(which installs and FireFireFire) by yourself when i tried with the kindle fire utility all got were errors, but when i installed it by myself everythink went smooth. Just find separate guide for every step
1.Root
2.TWRP and FireFireFire
3.CM7

I'm having the same problem as you and it sucks I just want to root it

Hate to necro post, but I'm having the same issue and none of the posted suggestions work. I have the ADB drivers installed (the Kindle is detected as "Android Composite ADB Interface"), but I did not install the drivers using the KFU batch file; I could never get it to stop producing the unsigned error, no matter what system settings I chose for unsigned drivers. I ended up doing a manual driver install and directing the installer at the driver files that came with KFU. Now KFU refuses to "see" the Kindle connected to my system and therefore I can't do a thing with it. I am able to browse the Kindle files in Windows Explorer (should I be able to? I've seen conflicting answers to this), but KFU always reports its ADB status as "Offline". Soft disconnecting the Kindle (hitting the "Disconnect" button on the Kindle) doesn't change anything, except removes my ability to browse the Knidle files (no surprise there).
This is a fully updated (6.3) Kindle and Windows XP. I did attempt to manually do what KFU does automagically prior to finding out about KFU, but that effort produced similar results; the Kindle was never detected by the SDK tools, despite the drivers loading properly. I have also tried multiple USB ports on my system, but they all produced the same results. About the only thing I haven't tried is a different USB cable, but if the Kindle is able to be "seen" by the OS correctly, I don't think the cable is a problem.

Have you tryed rebooting your computer? http://liliputing.com/2012/03/root-...ogle-play-store-with-kindle-fire-utility.html or http://m.youtube.com/#/watch?desktop_uri=/watch?v=mwMHIkX20YI&v=mwMHIkX20YI&gl=US nat3mil gives good instruction it helps to watch the video do the step while paused then move onto the next its how I did it the first time the second time I just used the utility was easy peasy cause drivers were already installed and functional

Yeah, I followed those exact instructions and video, with no results. Reboot doesn't make any difference, KFU still can't see the device.

cogadh said:
Yeah, I followed those exact instructions and video, with no results. Reboot doesn't make any difference, KFU still can't see the device.
Click to expand...
Click to collapse
If you followed the instructions to the t like not plugging in your device until you have the drivers installed .then you may have something on your computer preventing adb try the 6.2.2 method
http://m.youtube.com/#/watch?desktop_uri=/watch?v=AZ88CYWv0FU&v=AZ88CYWv0FU&gl=US or just keep looking for something that works cause people miss steps all the time sometimes its persistence or trial and error that gets results I'm very surprised your not seeing anything in device manager that applies to your kindle mine installed some drivers immediately when I connected it I had to change them to root it but it did show up in the list of devices as well as appearing next to my c drive as a kindle for SD card access but I'm on windows seven anything I connect does something.

No, Device Manager sees everything fine, it's KFU that refuses to see it. I am getting both a Kindle storage device and an Android ADB device in Device Manager, as well as seeing the Kindle as a removable drive in Windows Explorer. The old 6.2.2 instructions are of no help, that's what I tried the first time I attempted to root the device before the 6.3 update and I got the same exact results. I don't know what on my machine could possibly be interfering, this is a very barebones XP, I don't even run anti-virus on it.

cogadh said:
No, Device Manager sees everything fine, it's KFU that refuses to see it. I am getting both a Kindle storage device and an Android ADB device in Device Manager, as well as seeing the Kindle as a removable drive in Windows Explorer. The old 6.2.2 instructions are of no help, that's what I tried the first time I attempted to root the device before the 6.3 update and I got the same exact results. I don't know what on my machine could possibly be interfering, this is a very barebones XP, I don't even run anti-virus on it.
Click to expand...
Click to collapse
Could be your machine but don't use the utility and when you do put twrp on if ya get there use 2.0 the older version people are having trouble with the new one http://www.techtuple.com/477/how-to-root-kindle-fire-6-3-easily/ this is done through cmd without utility. Original thread here http://forum.xda-developers.com/showthread.php?t=1568340
About all the advice I can give you all else fails use another computer windows 7 machine things are more straight forward than xp
Edit: just a side note a lot of people are bricking their devices I keep remembering the Christmas story be careful you'll shoot your eye out also some people I believe are having success opening kfu attaching thier fire while off then powering up the kindle

I read somewhere that the utility doesn't work for xp wish I could find the post I think you need to push the files the old way using command prompt and you will get it sounds like your drivers are there but utility is useless

If your device isn't recognized it is a driver issue, regardless of whether your computer says they are installed or not.
Scrap your current drivers and start fresh using the tutorial posted here:
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Forget about KFU, get Android SDK and set up the drivers yourself. Learn to use fastboot to manually change your bootmode manually through command prompt. It will save you hours of heartache in the future.
Reinstall your (non KFU) drivers and try again.
Sent from my Amazon Kindle Fire using xda premium

Thanx soup better said than what I was trying

if you want to test to see if your drivers and adb are correctly installed plug your kindle in to your computer type cd c:\kindleadb then hit enter then type adb devices hit enter mine said adb server out of date. killing...
*dameon started successfully*
list of devices attached
42220600000000001 device
c:\KindleADB>
this is all in command prompt at this point I could paste in commands and root my kindle run this test to verify drivers are correctly installed if you dont see this try again on driver installation.

First time i've ever rooted a kindle and i had the same problem.
To fix this just go to device manager and uninstall the driver and then unplug and replug in your kindle then run the utility.

oh no trouble at all rooting rooted rommed and rockin here took the 6.3 ota this morning with 5 mins I was rooted with fff twrp then went back to 1 of my restore points of cm7 after a backup of 6.3 thanx tho

soupmagnet said:
If your device isn't recognized it is a driver issue, regardless of whether your computer says they are installed or not.
Scrap your current drivers and start fresh using the tutorial posted here:
Forget about KFU, get Android SDK and set up the drivers yourself. Learn to use fastboot to manually change your bootmode manually through command prompt. It will save you hours of heartache in the future.
Reinstall your (non KFU) drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
If all newbs do no other work but learn to use fastboot and adb it would save save a lot of grief for them and the ones helping them. jes sayin..

Thepooch said:
if you want to test to see if your drivers and adb are correctly installed plug your kindle in to your computer type cd c:\kindleadb then hit enter then type adb devices hit enter mine said adb server out of date. killing...
*dameon started successfully*
list of devices attached
42220600000000001 device
c:\KindleADB>
this is all in command prompt at this point I could paste in commands and root my kindle run this test to verify drivers are correctly installed if you dont see this try again on driver installation.
Click to expand...
Click to collapse
This will only work if the device is booted to a point where it will receive adb commands. Otherwise, use "fastboot devices". Sometimes if you are stuck at the bootloader it helps to shut your device down completely and restart before issuing fastboot commands.
Beyond that, it's a driver issue.
Sent from my Amazon Kindle Fire using xda premium

I had that same problem., but then I uninstalled the current drivers for my kindle altogether, and disabled them, then I ran install_drivers .bat again, then it worked.
Kindle Fire running KANG CM9
New developer, working on my own custom rom

[HELP]Bricked kindle fire very hard

i bricked my kindle fire ... like flash update.zip and then my fatal mistake i reboot kindle then i was bricked so hard please help me

a bit few information !
what exactly have you done ?
what display on kf ?
fff & twrp installed ?
kfu available ? - and moved and renamed to c:\kfu ?
status in device manager ?
os/bit ?

i install update.zip from kindle fire utility
then i reboot. it sticks on second kindle fire logo whit lower light ,no TWRP,no fff

that means you tried to restore it to pure stock
do you want to return it ?
if not gimme a pm and we can try to get to fastboot mode - reinstall fff & twrp - then it's possible to reinstall a rom of your choice
if it's not possible to get to fastboot then you'r up to a factory cable - sorry

can u give me skype on pm i will show you

Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw

Sweetoz97 said:
Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4

Sweetoz97 said:
Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw
Click to expand...
Click to collapse
Follow the following after you KF to your PC:
Adb kill-server
Adb start-server
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Good luck
Sent from my Amazon Kindle Fire using Tapatalk

I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?

josh24923 said:
I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?
Click to expand...
Click to collapse
Try to use KFU to install Windows driver and changing the booting mode to normal
Sent from my Amazon Kindle Fire using Tapatalk

josh24923 said:
I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?
Click to expand...
Click to collapse
maybe this helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
furthermore check the adb_usb.ini in the .android folder in your personal folder
it should include 0x1949 (and i use to add 0x18d1 also)
would not use the sdk at all - you can save a lot of space and the drivers of the sdk don't have all the necessary entries
the sdk also messes around with the adb_usb.ini and deletes your allready made entries
would recommend to use kfu only (like in the linked in post) - you don't even have to run it but:
- the drivers are in c:\kfu\drivers\kindle and have all necessary entries
- the tools directory (c:\kfu\tools) has all commands you'll ever need (you can run all your adb and fastboot commands from here manually)

I'll try these suggestions out. I've done a wide array of changing in the .android fold and keying in the 01x.... but it hasnt been to any avail. I'll try it in the order that you've introduced.

I've tried the above mentioned and was looking in the actual driver android_winusb file and I can see that the hardware id listed on it and the actual hardware id that my kindle shows are different. It has the same VID but the PID ends in 005 instead of the 006 that is supposed to.
So I created a copy of this and altered the driver file to reflect the PID as 005, and was able to get the driver file to eventually show up as an ADB Device in the hardware description with the driver, but it still would not interact with ADB itself.

adb_usb.ini usually reflects the vid only and is necessary for adb to work
the only other vid's i'hv read that some had success are 0x006 and 0x0e79
you may add them also to adb_usb.ini - if it don't help it don't harm
furthermore would recommend to kill the adb server every time if you have changed something at the drivers with "adb kill-server"

So far, I've gotten Windows to recognize the kindle as and ADB device. Trying to get the .android file to reflect the change hasn't worked at all. The VID isn't really much of and an issue. It's the PID that seems to be different from any post that I have seen. I wish that I could force ADB to recognize the connection, but that's a bar above me. I'm an amateur at best compared to some of the people.
I'm really vying on the power of XDA here; because, this problem is so similar to the other issues that are similar with the driver issue, being stuck at the kindle fire homescreen. However when I tried the update in twerp of the update.zip file, it somehow screwed the pooch on my adb. I have a backup both on the kindle and my computer. I just can't do anything until I get ADB to recognize my KF.

maybe give firekit a try ? no windows - no drivers
http://forum.xda-developers.com/showthread.php?t=1430038

Try to use another computer. If this impossible, Install new Windows in VMWare and connect Kindle to virtual machine. Then use KFU.

Well, I've tried firekit, and ubuntu wouldn't even recognize my kindle fire... I'm half tempted to use the usb trick, but I really dont want to start taking the kindle fire apart if i dont have to.

Tried a different computer and still have had no luck whatsoever... I'm really getting discouraged and think this is something that might not be fixed solely with a keyboard and basic ingenuity. I just hope I dont have to buy another kindle.

josh24923 said:
Tried a different computer and still have had no luck whatsoever... I'm really getting discouraged and think this is something that might not be fixed solely with a keyboard and basic ingenuity. I just hope I dont have to buy another kindle.
Click to expand...
Click to collapse
What exactly do you see when you start up your KF? The stock "kindle fire" logo or the yellow triangle logo? Does the screen ever go black before getting "stuck" on the logo?
If all you ever see is one of these logos without it ever going black, it's in fastboot mode. You'll never get adb to recognize your KF in this state regardless of what drivers are on your machine. adb will only see your device when it's in recovery or booted into the OS. In fastboot mode, you can only issue fastboot commands to the KF.
You say in post #15 that you've gotten Windows to recognize it as an ADB device. What device is shown in the the device manager when you connect it? Please be specific.

I think I soft bricked the KFHD 7', help pls.

So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.

procter said:
So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.
Click to expand...
Click to collapse
No.. and really you shouldn't be doing these things without a fastboot cable.. What do you mean by the driver does not take effect? It sounds like you need to fix the bootloader. I would head over to the Kindle Fire First Aide thread and talk to Chris and see if he can help you out. Is adb working or have you checked? If adb is working then you will be able to enter fastboot without the cable..

I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2

procter said:
I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?

lacoursiere18 said:
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?
Click to expand...
Click to collapse
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.

procter said:
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.
Click to expand...
Click to collapse
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well

lacoursiere18 said:
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well
Click to expand...
Click to collapse
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.

procter said:
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.
Click to expand...
Click to collapse
A lot of it is the same I am sure some aspects of the GUIDE do not work but as far as installing ADB drivers it is good. Did you uninstall it and also hit delete all software with driver?

did u recover
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:

KFHD 7 Stuck at splash screen
techdeisel said:
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:
Click to expand...
Click to collapse
Hey. I am having a terrible time getting my KFHD 7 back to stock. I used KFFirstAide to root it and when I went to restore it back to factory settings it ended up with the holo launcher lock screen and the android start screen. Has no notifier bar at top or menu bar at bottom. Lock screen let's me go online, to the camera, or just unlock. Don't know what happened! It's not recognized in ADB but shows up on computer as Kindle. I just want it back to stock so I can use it again! PLEASE HELP!!

In my situation, when trying to update the "Kindle" driver from Windows device manager, use the option to let you choose install driver from a list of devices instead of pointing to the directory where you have the adb driver (it will always tell you can't install even if u point it to the right directory).
In my case, I had all the drivers installed already, so when I use the option to install from the list of known devices, I can choose so"Android adb" or sth similar in that list. And after that you will be able to restore the adb connection.
Sent from my SPH-L710 using Tapatalk 2

the the reason your kindle cannot communicate properly with your computer is because it is soft-bricked, only way to recover from a soft-brick is with the use of a fastboot cable, if you are partially soft bricked...ie boot is intact and functional but system filesystem is corrupt you may be able to access fastboot with the use of a fastboot command

Like I tell everyone, go here to solve your problem.
Sent from my KFHD using xda premium

Previous ADB drivers work

I enabled ADB on Kindle and connected to my Windows 8 PC. I had the yellow triangle for the Android device and updating with the previous KFHD drivers worked fine. Now it shows up under Android composite ADB interface and confirmed with 'adb devices'.

Android Cowboy said:
I enabled ADB on Kindle and connected to my Windows 8 PC. I had the yellow triangle for the Android device and updating with the previous KFHD drivers worked fine. Now it shows up under Android composite ADB interface and confirmed with 'adb devices'.
Click to expand...
Click to collapse
Here's the adb driver that worked for me.

Android Cowboy said:
I enabled ADB on Kindle and connected to my Windows 8 PC. I had the yellow triangle for the Android device and updating with the previous KFHD drivers worked fine. Now it shows up under Android composite ADB interface and confirmed with 'adb devices'.
Click to expand...
Click to collapse
I'm more of a "follow guide on youtube" type person. What does this mean?
Sent from my iPad using Tapatalk - now Free

It means very little for the moment it's just a way the computer can communicate with the kindle but short of rebooting it and copying or sending some files it has little use to the average user just yet
Sent from my XT907 using xda app-developers app

Android Cowboy said:
I enabled ADB on Kindle and connected to my Windows 8 PC. I had the yellow triangle for the Android device and updating with the previous KFHD drivers worked fine. Now it shows up under Android composite ADB interface and confirmed with 'adb devices'.
Click to expand...
Click to collapse
That's good to know, thanks.

Android Cowboy said:
I enabled ADB on Kindle and connected to my Windows 8 PC. I had the yellow triangle for the Android device and updating with the previous KFHD drivers worked fine. Now it shows up under Android composite ADB interface and confirmed with 'adb devices'.
Click to expand...
Click to collapse
Works on my Windows 7 Bootcamp with my Kindle Fire HDX 8.9".

I have minimal adb and fastboot and turned on adb then plugged in my hdx into my computer, went to device manager, add legacy hardware, then I installed your driver. but it says Device cannot start. No other device is under device manager except Kindle under portable devices. Any help?
Fixed it. I had to safely remove the Kindle first then adb device popped up. I run windows 8.
Great post!

n60 said:
Here's the adb driver that worked for me.
Click to expand...
Click to collapse
Thank you! That one worked for me. Had downloaded a few that did not work.

Trouble downloading drivers
n60 said:
Here's the adb driver that worked for me.
Click to expand...
Click to collapse
Having some trouble downloading these drivers- Unless I'm missing something, clicking on this link simply loops me back to the thread. Is the attachment dead?
Thank you!

JaggedLines said:
Having some trouble downloading these drivers- Unless I'm missing something, clicking on this link simply loops me back to the thread. Is the attachment dead?
Click to expand...
Click to collapse
Motorola drivers work great for 3rd/4th gen HDX devices. Install the manager linked below; no need to run it. Select the newly installed drivers from Windows device manager while device is tethered. Might have to reselect driver when toggling between ADB and Fastboot modes depending on what else is on the host.
https://support.motorola.com/us/en/drivers