[Q] Enable USB Debugging / ADB on Kindle Fire - Kindle Fire General

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

Related

[Q] Kindle Fire v7 cant Root :(

I have tried to root my kindle with the Kindle Fire v7 and have had no luck, It comes back with The system cannot find the path specified, I have installed the drivers and my kindle shows up as Android Composite ADB Interface. Thanks for any help in advance. I have also tried the burritoRoot with no luck. I am on version 6.2.1 I have never had problems with any android devises before but this seems alittle different.
i have the exact same problem. would really appreciate some help
I had this problem and here are the steps I took to fix it.
Go to Google's website and manually download and install the SDK, at the end when it asks you to open the utility to download images and such, uncheck the box and click finish.
Download the Kindle Fire Utility v.7
Connect your Kindle Fire to your usb port.
Go to Start Menu -> Accessories -> Run and type in "devmgmt.msc" (without quotations)
There should be an "unknown device" with the name of Kindle Fire (or close to it), right click that and click update driver software.
Click "Browse my computer for driver software"
Hit Browse and locate the "drivers" folder in the Kindle Fire Utility folder
Click next and let it install the software
Go into the Kindle Fire Utility folder and run "run.bat"
Everything should work as expected from here on out, or at least it did for me
I think for both us we already have the drivers installed. the problem is in running the actual bat for the utility. unless maybe we did something wrong in installing the drivers, but i don't think so. I actually used the exact same method to install the drivers as you did.
Check your system path for what the program is trying to run. If the path is there, make sure the file its calling is there. Google adding a path to windows for more info.
I think he problem has to do with the program not finding the kindle
claytybob said:
I had this problem and here are the steps I took to fix it.
Go to Google's website and manually download and install the SDK, at the end when it asks you to open the utility to download images and such, uncheck the box and click finish.
Download the Kindle Fire Utility v.7
Connect your Kindle Fire to your usb port.
Go to Start Menu -> Accessories -> Run and type in "devmgmt.msc" (without quotations)
There should be an "unknown device" with the name of Kindle Fire (or close to it), right click that and click update driver software.
Click "Browse my computer for driver software"
Hit Browse and locate the "drivers" folder in the Kindle Fire Utility folder
Click next and let it install the software
Go into the Kindle Fire Utility folder and run "run.bat"
Everything should work as expected from here on out, or at least it did for me
Click to expand...
Click to collapse
I am good all the way to "run.bat" and when i do i get (ADB Status: Online, ADB Rooted: No, Boot Status: Unknown, So i put in #3 and press enter withch is Install Perment Root with Superuser, that is when i get all The system cannot find the path specified.
alright, so i was parusing around, and i think i found a solution. don't know why it works, but i think it will help you
Originally Posted by YourIcarus
Following this, two things happen. If I download the file from this post and attempt to install it, I receive an error stating Windows could not find files. If I install from the driver included in the OP, it's successful. However, ADB still does not recognize the device, and the Kindle Fire Utility returns an error: device not found.
Any help?
try this it may work:
open a cmd windows from your sdk tools folder, not the platform-tools, just tools and run this:
android update adb
then go to your user folder c:\users\username there should be a folder named .android in there, open adb_usb.ini and add this line at the bottom
0x1949
save close and update driver again, hope it works
credit goes to iluretar btw. make sure that you have the android sdk before doing this. delete whatever driver you had before this. after doing this, install the drivers manually through device manager and browsing to the folder included with the utility. and then...it works...for me at least, not sure why. oh, and...er...not sure where you find the link to android sdk, but i'm sure someone can provide you with that...
Fairtrade128 said:
alright, so i was parusing around, and i think i found a solution. don't know why it works, but i think it will help you
Originally Posted by YourIcarus
Following this, two things happen. If I download the file from this post and attempt to install it, I receive an error stating Windows could not find files. If I install from the driver included in the OP, it's successful. However, ADB still does not recognize the device, and the Kindle Fire Utility returns an error: device not found.
Any help?
try this it may work:
open a cmd windows from your sdk tools folder, not the platform-tools, just tools and run this:
android update adb
then go to your user folder c:\users\username there should be a folder named .android in there, open adb_usb.ini and add this line at the bottom
0x1949
save close and update driver again, hope it works
credit goes to iluretar btw. make sure that you have the android sdk before doing this. delete whatever driver you had before this. after doing this, install the drivers manually through device manager and browsing to the folder included with the utility. and then...it works...for me at least, not sure why. oh, and...er...not sure where you find the link to android sdk, but i'm sure someone can provide you with that...
Click to expand...
Click to collapse
Well I guess im still not doing it right cause im still getting The devise not found.
I moved my install_drivers.bat file from the drivers folder to the same folder as run.bat and ran it (install_drivers.bat that is). It seemed to install correctly. Now, however, my kindle will not mount. So when I try to use the utility to install TWRP, it stops at "Installing TWRP... If we get stuck here for a while, power the kindle on and off a few times. < waiting for device >"
I have rebooted my device 6 times and it still does not work. My device no longer mounts, I can't even see it in device manager. I tried installing the drivers manually prior to moving install_drivers.bat. This seemed to work but I ran the install_drivers.bat after moving it anyway, maybe that makes me a noob.
Anyway, is there a way to fix this? I want root on my device!
EDIT: Here is the script I am getting in cmd when I run install_drivers.bat. I realize that the problem is I am running Windows 7 x86. But is there a way to run it for x86 instead of x64?
This tool will attempt to install the correct Drivers for the Kindle Fire.
It will also perform the setup required for adb_usb.ini in .android for you.
This version of C:\Users\Chris\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.
This version of C:\Users\Chris\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.
Click to expand...
Click to collapse
Here is what i did. First off, not just any data cable works, i found that lg cable dont like adb. Some samsung cables give me trouble too. But anyways. Click start menu, type device, click and open device manager the go back to start type device again and open device and printers. If the kindle has installed its drivers then you should see "kindle" in DEVICE AND PRINTERS click on kindle go to properties select driver "tab" and hit uninstall. Open device manager and make sure its still sees the kindle as ADB interface. If so then you should be all set. This should be done after editing the adb_usb file and updating the google drivers.
Clemzon said:
Here is what i did. First off, not just any data cable works, i found that lg cable dont like adb. Some samsung cables give me trouble too. But anyways. Click start menu, type device, click and open device manager the go back to start type device again and open device and printers. If the kindle has installed its drivers then you should see "kindle" in DEVICE AND PRINTERS click on kindle go to properties select driver "tab" and hit uninstall. Open device manager and make sure its still sees the kindle as ADB interface. If so then you should be all set. This should be done after editing the adb_usb file and updating the google drivers.
Click to expand...
Click to collapse
Thank you, this is what finally got it working for me. I had tried everything; installed 3 different USB drivers, edited files, moved files around, all with no signs of progress. Finally this approach made everything work perfectly!
Clemzon said:
Here is what i did. First off, not just any data cable works, i found that lg cable dont like adb. Some samsung cables give me trouble too. But anyways. Click start menu, type device, click and open device manager the go back to start type device again and open device and printers. If the kindle has installed its drivers then you should see "kindle" in DEVICE AND PRINTERS click on kindle go to properties select driver "tab" and hit uninstall. Open device manager and make sure its still sees the kindle as ADB interface. If so then you should be all set. This should be done after editing the adb_usb file and updating the google drivers.
Click to expand...
Click to collapse
THANKS, that worked like a champ. After I did that it work.
Sent from my SAMSUNG-SGH-I997 using XDA App

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: Problem getting drivers to install.

I've been trying to root this thing for about 3 hours now. I'm on Windows XP and I can't get my kindle to be recognized in adb. I've tried updating my drivers in SDK and still no dice. All the guides appear to be for windows 7. Nothing I do is working. I've rooted several devices including tablets in the past but this one is almost impossible. All I want is the android market on my kindle.
ddgarcia05 said:
I've been trying to root this thing for about 3 hours now. I'm on Windows XP and I can't get my kindle to be recognized in adb. I've tried updating my drivers in SDK and still no dice. All the guides appear to be for windows 7. Nothing I do is working. I've rooted several devices including tablets in the past but this one is almost impossible. All I want is the android market on my kindle.
Click to expand...
Click to collapse
Uhm... I'm not so sure about windows XP when it comes to automatically searching for drivers, but turning on the USB debugging setting might get windows to download everything necessary for adb to recognize the device. It worked on my phone, when I couldn't find the drivers... Just turned on USB debugging under "developer options," and windows got to work right away. Rooted it no problem.
using xp is the best choice - you dont have to care about 32/64bit and the uac (user access control)
hope this helps you to get rid of the drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
I get this when I try to install drivers via install drivers.bat program.
Sent from my Galaxy Nexus using xda premium
as described in the linked post it's a good practice to move and rename kfu to c:\ that it is c:\kfu - it don't like spaces in pathname
the error message looks stange because "and" is no command - would try to redownload it
if it says "findstr" is not recognized as command then check your path varible - it should include c:\windows\system32
furthermore i use to run the batch files from the command prompt - cd to c:\kfu and type install_drivers.bat - the same with run.bat
It took three computers but I finally rooted the kindle.
Sent from my Kindle Fire using xda premium

ADB Connection to The Fire HD

This is useful to anybody trying to get ADB going. I can confirm it works.
https://developer.amazon.com/sdk/fire/connect-adb.html
No OTG support as far as I can tell. Or at least, it doesn't power the bus. It did lock when I added a powered hub. That might mean it works, but doesn't supply power.
I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?
I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
reverendkjr said:
I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?
Click to expand...
Click to collapse
Thread Moved​
As the contains no development.​
How activate USB Debugging on Kindle Fire HD 7 ? Or this option activated by default ?
androitri said:
How activate USB Debugging on Kindle Fire HD 7 ? Or this option activated by default ?
Click to expand...
Click to collapse
from the notification area click on more , security , ADB on
ADB doesn't see my Kindle HD 7
androitri said:
Awesome, want to try it when I receive my HD 7 this week...
Click to expand...
Click to collapse
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:23 AM ---------- Previous post was at 08:55 AM ----------
tansy said:
I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
Click to expand...
Click to collapse
Well, I added the magic line you suggested, and this now works for me. I'm surprised that running "C:\android-sdk\tools\android.bat update adb" (the corrct directory for me) didn't fix this.
Ah well - so many things to learn. Thanks for your guidance.
Pat
tansy said:
I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
Click to expand...
Click to collapse
This didn't do anything for me. Any other ideas?
Driver install problem
dotvezz said:
This didn't do anything for me. Any other ideas?
Click to expand...
Click to collapse
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!
Zimblotnik said:
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!
Click to expand...
Click to collapse
This worked for me, thank you. ADB can now 'see' my KFHD 7, and I was able to revert a file from backup to get it to boot again.
PMcHargue said:
This worked for me, thank you. ADB can now 'see' my KFHD 7, and I was able to revert a file from backup to get it to boot again.
Click to expand...
Click to collapse
USB hubs cause problems, just sayin'.
I went round and round with this until I decided to plug directly into the PC and avoid the hub. Worked perfectly.
---------- Post added at 05:37 PM ---------- Previous post was at 05:33 PM ----------
If you have tried everything and still no workie, make sure you aren't using a USB hub. ADB wasn't listing it as a device but yet I was able to see it in Device Manager and even transfer files to/from it. Once I eliminated the USB hub, all was well. ADB now sees it.
dburckh said:
This is useful to anybody trying to get ADB going. I can confirm it works.
https://developer.amazon.com/sdk/fire/connect-adb.html
No OTG support as far as I can tell. Or at least, it doesn't power the bus. It did lock when I added a powered hub. That might mean it works, but doesn't supply power.
Click to expand...
Click to collapse
Thank you so much for this, I was fially able to get ADB to recognize my Fire and root it.
reverendkjr said:
I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?
Click to expand...
Click to collapse
Mine was doing the same thing
Follow the link that the OP gives(i'll also post it)
Follow the instructions in BOTH the links below. The second link are instructions to get kindle fire add-ons(including usb drivers) for SDK.
https://developer.amazon.com/sdk/fire/connect-adb.html
https://developer.amazon.com/sdk/fire/setup.html#step6
I had the same problem, with adb, not finding my Kindle Fire. I downloaded the current Android SDK und used that ADB without changing anything. Works fine for me I also just copied the adb.exe in the same directory as rootqemu.bat and replaced the old one ( old ~159kb new ~796kb ).
Very helpful
Hello All,
I could use some assistance. I have ADB installed properly and the drivers for the Kindle Fire HD from this thread installed also. My issue is the Kindle Fire HD driver states:
Android Composite ADB Interface
The device cannot start (Code 10).
I am using the driver from 12/3/2012 version 1.2.0.0 and I get this error code if I have the Fire directly connected to the usb port on the pc or through the usb hub. Same issue over and over. Even if I attempt to use other Kindle Fire HD drivers.
Also, I have made the change in the adb_usb.ini file.
Zimblotnik said:
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!
Click to expand...
Click to collapse
This ABSOLUTELY helped me! Was bangin' my head against the wall for a WHILE before I this little nugget got me going! THANK YOU!
My issue is fastboot takes commands but says flashing not allowed
Hi, I have no issue connecting to my Kindle Fire using ADB under Ubuntu using a USB cable, no drivers were needed.
However I'm trying to get ADB over WIFI to work, but I get "unable to connect to 192.168.1.234:5555"
Has anyone managed to do ADB over WIfi or is it not implemented on the Kindle Rom? Thanks

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

Categories

Resources