FORUMS

AOSP 5.1 Lollipop for Nexus Q

Google Nexus Q is an intriguing device released with Android 4.0 Ice Cream Sandwich. It was abandoned by … more

XDA Picks: Best Apps of the Week (Apr 17 – 24)

Apps are at the front and center of any smartphone experience, and with over a … more

Glimpse Notifications: Easier Lockscreen Notifications

Lollipop brought a revamp to the lockscreen, taking away custom widgets but … more

What Are the Best Looking Apps on Android?

As more developers are updating their apps with Material Design elements, we’re … more
Post Reply Subscribe to Thread Email Thread

ADB Connection to The Fire HD

14th September 2012, 07:59 PM |#1  
OP Senior Member
Thanks Meter: 91
 
Donate to Me
More
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.
The Following 2 Users Say Thank You to dburckh For This Useful Post: [ View ]
 
 
15th September 2012, 04:33 PM |#2  
reverendkjr's Avatar
Senior Member
Flag Cincinnati, OH
Thanks Meter: 849
 
More
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?
15th September 2012, 10:47 PM |#3  
Junior Member
Thanks Meter: 4
 
More
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!


Quote:
Originally Posted by reverendkjr

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?

The Following 4 Users Say Thank You to tansy For This Useful Post: [ View ]
15th September 2012, 11:00 PM |#4  
O_G's Avatar
Moderator Committee - Life Can't Beat Me
Flag Glosta
Thanks Meter: 5,247
 
More
Thread Moved


As the contains no development.
18th September 2012, 10:39 AM |#5  
Senior Member
Thanks Meter: 5
 
More
Question
How activate USB Debugging on Kindle Fire HD 7 ? Or this option activated by default ?
18th September 2012, 10:49 AM |#6  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by androitri

How activate USB Debugging on Kindle Fire HD 7 ? Or this option activated by default ?

from the notification area click on more , security , ADB on
The Following User Says Thank You to mssabbagh For This Useful Post: [ View ]
19th September 2012, 05:23 PM |#7  
Member
Thanks Meter: 10
 
More
ADB doesn't see my Kindle HD 7
Quote:
Originally Posted by androitri

Awesome, want to try it when I receive my HD 7 this week...

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 ----------

Quote:
Originally Posted by tansy

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!

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
21st September 2012, 01:35 AM |#8  
Junior Member
Flag Haymarket, VA
Thanks Meter: 0
 
More
Quote:
Originally Posted by tansy

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!

This didn't do anything for me. Any other ideas?
23rd September 2012, 07:21 AM |#9  
Junior Member
Thanks Meter: 4
 
More
Driver install problem
Quote:
Originally Posted by dotvezz

This didn't do anything for me. Any other ideas?

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!
The Following 3 Users Say Thank You to Zimblotnik For This Useful Post: [ View ]
23rd September 2012, 05:06 PM |#10  
Member
Thanks Meter: 10
 
More
Quote:
Originally Posted by Zimblotnik

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!

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.
The Following 2 Users Say Thank You to PMcHargue For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes