[Android Q&A, Help & Troubleshooting] raparis:
1st I'm a noob, so be kind. After getting the 4.0.4 update pushed from Verizon, my Motorola Bionic has disappeared from adb radar. terminal command "adb devices" returns nothing under list of devices attached, when its usb connected. (I've updated my android sdks. to latest platform tools).

I have tried each of the 3 usb settings 4.0.4 offers (Mass Storage, Media Device(MTP) and Camera (PTP), with debugging both on and off. Still no joy. I have killed and started adb server and rebooted both the macbook pro and the bionic. BTW - the original android os it started with had a "Charge Only" mode, which was the usb connection type that adb connection had previously required, but that's gone from this 4.0.4 upgrade for some reason. I have searched numerous forums and threads, but haven't found anything that seems to specifically apply to what i'm encountering. Those forums that did have posts about adb not finding connected device, mostly suggested rebooting and updated sdks. A couple suggested editing some config files, but I couldn't locate those. Any and all suggestions/solutions will be gratefully attempted. Thanks in advance for your analysis.

I'm running osx lion 10.7.5 on a MacBook Pro. I can provide phone system info if necessary. I've copied below the info I've gathered about the usb port the device is connected to from USB Prober.

Using usb prober the device appears as "Composit device: "XT875" in the bus probe. Port Info shows as: 0x1018, not captive, external device, connected, enabled. Device Descriptor shows as: Descriptor Version Number: 0x0200

Device Class: 0 (Composite)

Device Subclass: 0

Device Protocol: 0

Device MaxPacketSize: 64

Device VendorID/ProductID: 0x22B8/0x4353 (Motorola MDS)

Device Version Number: 0x0216

Number of Configurations: 1

Manufacturer String: 2 "Motorola"

Product String: 3 "XT875"

Serial Number String: 4 "0A3BAA470C01100C"

Interfaces show as: Interface #0 - Vendor-specific .............................................. "MTP"

Alternate Setting 0

Number of Endpoints 3

Interface Class: 255 (Vendor-specific)

Interface Subclass; 255 (Vendor-specific)

Interface Protocol: 0

Endpoint 0x81 - Bulk Input

Endpoint 0x02 - Bulk Output

Endpoint 0x82 - Interrupt Input

Interface #1 - Communications-Control .............................................. "Motorola Networking Interface"

Alternate Setting 0

Number of Endpoints 3

Interface Class: 2 (Communications-Control)

Interface Subclass; 10

Interface Protocol: 1

Endpoint 0x83 - Bulk Input

Endpoint 0x03 - Bulk Output

Endpoint 0x04 - Interrupt Output

Device Qualifier Descriptor

Descriptor Version Number: 0x0200

Device Class 0 (Composite)

Device Subclass 0

Device Protocol 0

Device MaxPacketSize: 64

Number of Configurations: 1

bReserved: 0

Other Speed Configuration Descriptor

Length (and contents): 69

Number of Interfaces: 2

Configuration Value: 1

Attributes: 0xC0 (self-powered)

MaxPower: 500 ma

Interface #0 - Vendor-specific .............................................. "MTP"

Alternate Setting 0

Number of Endpoints 3

Interface Class: 255 (Vendor-specific)

Interface Subclass; 255 (Vendor-specific)

Interface Protocol: 0

Endpoint 0x81 - Bulk Input

Endpoint 0x02 - Bulk Output

Endpoint 0x82 - Interrupt Input

Interface #1 - Communications-Control .............................................. "Motorola Networking Interface"

Alternate Setting 0

Number of Endpoints 3

Interface Class: 2 (Communications-Control)

Interface Subclass; 10

Interface Protocol: 1

Endpoint 0x83 - Bulk Input

Endpoint 0x03 - Bulk Output

Endpoint 0x04 - Interrupt Output