Related
I have a Kindle Fire which I would like to connect to via ADB, but the settings menu does not even have a box for USB debugging. Amazon also does not have ADB drivers, though I'd guess that using drivers for the TI OMAP 4430 might work, but I can't even try without USB debugging enabled.
Is there some secret way to enable USB debugging or an app which allows you to set it, even if the OS does not?
+1 for developers!
+2, been looking myself. Got some apps that aren't running right and there's no way to figure out why exactly.
+3 has anyone found any ADB drivers that work for Win7? I tried a few but no luck
Found it. It's pretty easy. http://blog.actlocalmedia.com/2011/11/developing-on-kindle-fire.html
Steps to get ADB to show your Kindle Fire
Hi everyone,
1. First, go into your KF Settings > Device and enable "Allow Installation of Applications "
2. Edit your adb_usb.ini and add 0x1949 to it.
Now it should show up on ADB and let you deploy APKs to it.
Thanks guys this works.
For Windows users the file is at:
C:\Users\[YOUR USER NAME]\.android\adb_usb.ini
Post removed
For windows users if you need the driver, I posted a solution here:
http://forum.xda-developers.com/showpost.php?p=19391164&postcount=4
AdmiralUD said:
For windows users if you need the driver, I posted a solution here:
http://forum.xda-developers.com/showpost.php?p=19391164&postcount=4
Click to expand...
Click to collapse
That's odd, I didn't need to do any of that, just modify my INI in Win7 here.
I wasn't able to make this work based on the just the info here. Luckily Amazon actually posted official instructions, and they worked for me: http://g-ecx.images-amazon.com/images/G/01/sdk/Connecting_your_Kindle_Fire_to_ADB.pdf
It's weird actually having real support from the vendor.
Edit: ROFL, the links in the PDF are just blue text and not real links. Here's the whole dev FAQ including a link to the Win7 driver: https://developer.amazon.com/help/faq.html#KindleFire
Still having trouble myself using both the Amazon provided instructions and the ones in dev thread.
Still getting no devices listed doing an adb devices. Have used the provided drivers for windows from Amazon and also am sure have modified correctly the drivers in the .android folder. My adb is working as it sees my captivate no problem.
Any thoughts? Is there a way to completely remove drivers and try installing them again? Any help would be appreciated.
In win xp, it didn't work for me when I specified the driver file explicitly, but did work when I just told it what folder to look in for the driver.
To uninstall just right click the device in device manager and click remove.
Good luck.
Sent from my Kindle Fire using Tapatalk
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
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?
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