Related
Ive been to a dozen websites... everyone has a copy paste basically of the method. I've altered adb_usb.ini with the 0x1949 and altered the android_winusb in the correct places but when I attempt to update the drivers under my device manager my kindle is listed under Disk drives... not "other" etc like everyone tells me to look for.. and attempting to update the driver results in telling me I already have the best driver. I am unable to find my kindle with an adb devices even after multiple starting and killings of the server. I uninstalled the android sdk and reinstalled and redownloaded everything but still no luck. Please help. I'm far from a master but this is not my first rodeo having rooted 3 android phones.
Idk how you do it on other oses but on windows 7 it's:
Device manager, right click, update driver, let me choose, let me pick, have disk, c:\<path to win_usb.inf>
Sent from my Kindle Fire using Tapatalk
aye the problem is it believes it already has the best drivers for the job and won't accept android_winusb.inf as it's superior
Download Kindle Utility and run install-drivers.bat
Sent from my Kindle Fire using xda premium
I just discovered that and was very hopeful but it replied
This version of C:\Users\*\Desktop\Kindle Fire Utility\tools\x64\devcon.exe
is not compatible with the version of Windows you're running. Check your compute
r's system information to see whether you need a x86 (32-bit) or x64 (64-bit) ve
rsion of the program, and then contact the software publisher.
Android Debug Bridge version 1.0.25
I'm on Vista.. assumed it would have worked
edit: its possible that the x86 worked and the x64 failed.. but the fact remains my device remains un-found. If I wasn't balding I'd be tearing out my hair.
Thank you to those who have tried to help however.
i had this problem earlier but my friend fixed it! when he wakes up ill have him post the solution
now i have superuser apk on system but no root and adb said success!! wtf
Jcase fixed my su problem i wasnt pushing the su with adb
congrats, im still messing with things but running out of options on my end.
Try running the batch file from an administrator command prompt. Also delete any existing device in devmgmt.msc. I'm also on Vista, worked ok for me.
Sent from my Kindle Fire using xda premium
i attempted the driver batch as administrator... it oddly doesn't make it as far as without.. it just says the system can not find the path specified 4 or 5 times then stops. And I've attempted to delete the kindle from disk drives which is the only location it shows up but as soon as i plug it in again it re-installs.
Edit: a side note.. i have a "Android Phone" in my device manager that appears to be my kindle and is using the 0x1949 drivers... I assumed it was my actual phone but it disappears/reappears when i unplug my kindle
Thanks to everyone who helped, by the grace of god i got my device recognized ... got it rooted... then bricked it installing TWRP.. finally unbricked it... and now I'm not messing with it for the rest of the night lol
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).
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
Greetings,
I am currently running my Kindle Fire with the an AOKP ICS based ROM. Everything is working fine, and when I connect the KF to a Windows computer I can see the SD storage fine as well. However, when I attempt to use adb or the Kindle Fire Utility to perform any actions against the Kindle Fire from Windows, I cannot get the device to be recognized properly once I plug it in. Because of this it is not detected by adb, and appears offline to the Kindle Fire Utility.
Before, when the KF was still on the stock ROM, it was recognized fine once I ran the driver installation included with the Kindle Fire Utility. But now the device is not recognized, and I only see a device called "Amazon" with an exclamation point next to it under Misc. devices in Device Manager.
I have tried to reinstall the driver included with the Kindle Fire Utility, install the Google USB drivers included with the Android SDK, and nothing has had any effect so far. If I boot into recovery the OS seems to recognize the device properly, but I can't do much else as once adb commands are sent to it (ie. via the Kindle Fire Utility) it doesn't have a response on the device itself, and just sits in recovery waiting for user input.
Wondering if anyone has had any experience with this thus far, and was able to resolve.
UPDATE: Resolved. Not sure how I missed this, but looks like user 'nathris' posted details and a fix in the following thread on AOKP:
http://forum.xda-developers.com/showpost.php?p=25271431&postcount=109
Device ID changed and the android_winusb.inf file needed to be modified with new ID strings. I updated the .inf file that was included in the drivers with the KFU. I then went to device manager, updated the driver, and pointed it to the KFU driver folder that included the modified .inf. Afterwards the driver installed and my KF was detected once again.
worked perfect I did it all without the kindle plugged in pasted the code into the inf file ran the driver install in KFU then plugged in my kindle walla adb online on the new milestone 5 kindle fire AOKP and my mass storage drivers remained intact. thanks for the research
shinji1225 said:
Greetings,
I am currently running my Kindle Fire with the an AOKP ICS based ROM. Everything is working fine, and when I connect the KF to a Windows computer I can see the SD storage fine as well. However, when I attempt to use adb or the Kindle Fire Utility to perform any actions against the Kindle Fire from Windows, I cannot get the device to be recognized properly once I plug it in. Because of this it is not detected by adb, and appears offline to the Kindle Fire Utility.
Before, when the KF was still on the stock ROM, it was recognized fine once I ran the driver installation included with the Kindle Fire Utility. But now the device is not recognized, and I only see a device called "Amazon" with an exclamation point next to it under Misc. devices in Device Manager.
I have tried to reinstall the driver included with the Kindle Fire Utility, install the Google USB drivers included with the Android SDK, and nothing has had any effect so far. If I boot into recovery the OS seems to recognize the device properly, but I can't do much else as once adb commands are sent to it (ie. via the Kindle Fire Utility) it doesn't have a response on the device itself, and just sits in recovery waiting for user input.
Wondering if anyone has had any experience with this thus far, and was able to resolve.
UPDATE: Resolved. Not sure how I missed this, but looks like user 'nathris' posted details and a fix in the following thread on AOKP:
http://forum.xda-developers.com/showpost.php?p=25271431&postcount=109
Device ID changed and the android_winusb.inf file needed to be modified with new ID strings. I updated the .inf file that was included in the drivers with the KFU. I then went to device manager, updated the driver, and pointed it to the KFU driver folder that included the modified .inf. Afterwards the driver installed and my KF was detected once again.
Click to expand...
Click to collapse
can u up the.inf file?
I'd like to think that I'm not a totally clueless noob, but I sure feel like one. I've installed homebrew on Wii and stuff like that, but I simply can't get the Kindle Fire Utility to run on a first generation Kindle Fire, 6.3.1.
I have downloaded the utility and installed the drivers, they install correctly and all necessary permissions are allowed. However, when I plug in the Kindle, the computer beeps like a USB device has been added, but it doesn't recognize the Kindle and the Kindle Fire Utility opens, but doesn't run to the point where I get a menu.
I can use system restore to roll back the driver installation and then the Kindle is recognized. I've tried running Kindle Fire Utility to get boot menu, then installing the drivers, but that leaves me hanging at "waiting for device"
Any thoughts would be much appreciated!
I have a Toshiba Satellite L755 running Windows 7.
Thanks!