[Kindle Fire Q&A, Help & Troubleshooting] lmntone:
Hey all,

So I was using my KF just fine with hashcode's AOSP Jelly Bean rom. That rom was on there for more than a month and then suddenly ,as of yesterday, adb refuses to connect. Fastboot on the other hand works just fine.

I'm running Debian Squeeze on and old Thinkpad R51. Both adb and fastboot binaries are in my PATH, and my 51-android.rules looks as follows...

# Amazon
SUBSYSTEM=="usb", ATTRS{idVendor}=="1949", MODE="0666", GROUP="plugdev"

# HTC
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"

# Lenovo
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666", GROUP="plugdev"

# Motorola
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666", GROUP="plugdev"

Running "adb kill-server" and then "adb devices" does not show the device at all. I switched to the jandykane rom and it's still the same. I'm currently in the stock amazon 6.3.1 rom and still I get nothing. I did a full /cache /data /system /sdcard wipe after installing each rom. Running "lsusb" I get...

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 040: ID 1949:0006 Lab126
Bus 001 Device 002: ID 1058:1021 Western Digital Technologies, Inc. Elements 2TB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And running "dmesg | tail" (only posted what is shown after I plug in the KF), I get...

[ 8851.136202] usb 1-4: new high speed USB device using ehci_hcd and address 40
[ 8851.269079] usb 1-4: New USB device found, idVendor=1949, idProduct=0006
[ 8851.269090] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8851.269099] usb 1-4: Product: Kindle
[ 8851.269106] usb 1-4: Manufacturer: Amazon
[ 8851.269114] usb 1-4: SerialNumber: 1CDE000600000001
[ 8851.270544] usb 1-4: configuration #1 chosen from 1 choice
[ 8851.277370] scsi29 : SCSI emulation for USB Mass Storage devices
[ 8851.284978] usb-storage: device found at 40
[ 8851.284986] usb-storage: waiting for device to settle before scanning
[ 8856.290243] usb-storage: device scan complete
[ 8856.290897] scsi 29:0:0:0: Direct-Access Amazon Kindle 0001 PQ: 0 ANSI: 2
[ 8856.295474] sd 29:0:0:0: Attached scsi generic sg3 type 0
[ 8856.316198] sd 29:0:0:0: [sdc] Attached SCSI removable disk

I am able to do adb commands just fine on a Droid X2. The DX2 is shown in the device list and I can successfully send commands. I've used the same cable for both the DX2 and the KF. I've tried another working cable and still nothing. I can successfully use adbWireless to send commands. I even went as far as clean installing Debian Wheezy and setting up the udev rules for adb/fastboot access, and still no success.

Is there anything I can try to fix this problem. What could cause fastboot to work but not adb. My best guess is that it may be hardware failure.

Oh and one last thing, In hashcode's jelly bean rom, I was able to mount the sdcard partition when connected via usb to my computer. I could browse the drive and everything. It also works on the stock amazon 6.3.1 update.

Also, I've been using an adb and fastboot binary that has been compiled with the Amazon device id included in the source code (0x1949). I've been using those binaries for the longest without any problems but I don't know if they could have caused any hardware damage.