Related
Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.
CrimsonSentinel13 said:
Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.
Click to expand...
Click to collapse
BurritoRoot causes the normal adbD to behave as an unsecure one, but if your not seeing the kindle under adb devices then you have PC side problems likely.
I figured it might be PC side. I've tried everything I could after updating the Android SDK. Updating everything with what's needed for the Fire to be seen hasn't worked. I'm a bit at a dead end for ideas... I tried even using the USB3 controller on my mobo but no luck either.
Edit: Fixed!
I uninstalled the Kindle Fire from the Device Manager & got it reinstalled. It now works perfectly with ADB. I'm in the process of rooting it as I type this.
I have the same problem.
However, I have 2 fires, one running CM7 and the other 6.2.1.
The PC recognizes the one running CM7 but not 6.2.1.
So, I don't think it is the PC.
No matter what I do, adb and fastboot, device not found.
Can not access the one with 6.2.1.
Does not show up in device manager.
I have read and try various things from xda, Rootzwili and Liliputing.
follow this video thats wht helped me get past that part ur on
http://www.youtube.com/watch?v=KapnjR89ICA&feature=player_embedded
u have to make sure u update the drive for ur kindle with the driver from sdk
this is also helpful tooo
http://forum.xda-developers.com/showthread.php?t=1409120
What worked for me was following this guide up to step 3. Then, with the device manager it launches, i deleted ALL my adb/android devices and then I let windows re-install the driver when I plugged the kindle (you may need to choose the driver manually), then I could finally access fastboot/adb via cmd..
Solved problem, Thank You.
I have many drivers on my PC, Motorola, Samsung, HTC and Android.
I noticed on one boot the Kindle was listed as Samsung Android Phone.
I uninstalled the Samsung drivers.
Connected the Kindle. All is fine.
Connected my Samsung SGS II, it found the drivers.
Crimson, thanks for sharing your fix of uninstalling then reinstalling. Worked for me.
hi, i would like to apologize in advance, i am new to adb so i'm not sure if i'm even doing it right, but i have successfully rooted and installed cm7, after much googling. i did it a while ago and used the clockwork mod method. i would like to replace it with twrp but the only way i have found to do it is by using adb or the kindle fire utility, which if i understand correctly uses adb. the only problem with that is that i can't get adb to recognize it. i'm assuming it's because i don't have the proper drivers for the "cm7 kindle" because i install them for the stock kindle. please help me. i have no idea how to fix this. thanks
edit: ok guys i'm really sorry, i'm an idiot, i forgot that i had turned off usb debugging. turned it back on, worked perfectly. again sorry.
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
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.
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?
Hello to everyone
Unfortunatly my device shield pro 2015 has green light but wan't bot black screen only.
when i plugin my microusb to a pc windows 10 or windows 11 , APX device appear on device manager .
i have download sdk toolkit add to the path variables environments the path whre i download i installed the driver instead update device list ,now is displayd like android device
when i send to cmd comand adb device the response is this:
C:\Users\Andrea\Desktop\platform-tools>adb devices
daemon not running; starting now at tcp:5037
daemon started successfully
List of devices attached
no devices
i m looking for a guide or support to recover my system by cloning hd to another hd and put in or recovery by tricks or method that i dont found before ,and i want to check if is convenient to consider dead device or are possibilities to recovery and rescue my device .
Thanks to all for listen me
Andrea
ps sorry for my bad english