PDA

View Full Version : first gen DroidX USB stuck in "charge only" mode after using adb



neonjohn
07-27-2014, 09:27 PM
First generation DroidX. Rooted but not modded. I've had it happily working with my Ubuntu Linux system for several weeks. Recently I downloaded the Google SDK to gain access to adb so I could initiate a remote shell. Just poking around, not changing anything, trying to become familiar with the architecture.

After exiting adb, I could no longer take the phone out of debug mode. That is, the USB screen is stuck on Charge only and the settings->applications->development->USB debugging box remains checked. I can un-check it, hit the "back" key, then return to the development screen and the debugging box is checked again.

On the Linux side, watching /var/log/user.log, when I tap the "usb mass storage" button, I can see in the log that it momentarily goes into that mode and then returns to "charge only". Here's a sample of the log.

Jul 27 22:20:45 den kernel: [27130.372181] usb 2-1.5.3.4: USB disconnect, device number 46
Jul 27 22:20:45 den kernel: [27130.373455] cdrom: issuing MRW background format suspend
Jul 27 22:20:45 den kernel: [27130.573991] usb 2-1.5.3.4: new high-speed USB device number 47 using ehci_hcd
Jul 27 22:20:45 den kernel: [27130.667677] scsi43 : usb-storage 2-1.5.3.4:1.0
Jul 27 22:20:45 den mtp-probe: checking bus 2, device 47: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5.3/2-1.5.3.4"
Jul 27 22:20:45 den mtp-probe: bus: 2, device: 47 was not an MTP device
Jul 27 22:20:46 den kernel: [27131.664713] scsi 43:0:0:0: Direct-Access Motorola MB810 0001 PQ: 0 ANSI: 2
Jul 27 22:20:46 den kernel: [27131.665457] scsi 43:0:0:1: CD-ROM Motorola MB810 0001 PQ: 0 ANSI: 2
Jul 27 22:20:46 den kernel: [27131.666245] sd 43:0:0:0: Attached scsi generic sg6 type 0
Jul 27 22:20:46 den kernel: [27131.671488] sr2: scsi3-mmc drive: 0x/0x caddy
Jul 27 22:20:46 den kernel: [27131.672353] sd 43:0:0:0: [sde] Attached SCSI removable disk
Jul 27 22:20:46 den kernel: [27131.673340] sr 43:0:0:1: Attached scsi CD-ROM sr2
Jul 27 22:20:46 den kernel: [27131.674090] sr 43:0:0:1: Attached scsi generic sg7 type 5

Obviously some process is sitting on the USB port, keeping it in debug mode. I've done just about everything I can think of including carefully examinging the process table on the Droid but I don't see anything out of the ordinary.

I've tried it on a Win7 box and it fails from not finding the Motorola adb driver. On an XP box, it simply asks for the adb driver.

HELP! Please.

Thanks
John

sd_shadow
07-29-2014, 09:49 PM
First generation DroidX. Rooted but not modded. I've had it happily working with my Ubuntu Linux system for several weeks. Recently I downloaded the Google SDK to gain access to adb so I could initiate a remote shell. Just poking around, not changing anything, trying to become familiar with the architecture.

After exiting adb, I could no longer take the phone out of debug mode. That is, the USB screen is stuck on Charge only and the settings->applications->development->USB debugging box remains checked. I can un-check it, hit the "back" key, then return to the development screen and the debugging box is checked again.

On the Linux side, watching /var/log/user.log, when I tap the "usb mass storage" button, I can see in the log that it momentarily goes into that mode and then returns to "charge only". Here's a sample of the log.

Jul 27 22:20:45 den kernel: [27130.372181] usb 2-1.5.3.4: USB disconnect, device number 46
Jul 27 22:20:45 den kernel: [27130.373455] cdrom: issuing MRW background format suspend
Jul 27 22:20:45 den kernel: [27130.573991] usb 2-1.5.3.4: new high-speed USB device number 47 using ehci_hcd
Jul 27 22:20:45 den kernel: [27130.667677] scsi43 : usb-storage 2-1.5.3.4:1.0
Jul 27 22:20:45 den mtp-probe: checking bus 2, device 47: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5.3/2-1.5.3.4"
Jul 27 22:20:45 den mtp-probe: bus: 2, device: 47 was not an MTP device
Jul 27 22:20:46 den kernel: [27131.664713] scsi 43:0:0:0: Direct-Access Motorola MB810 0001 PQ: 0 ANSI: 2
Jul 27 22:20:46 den kernel: [27131.665457] scsi 43:0:0:1: CD-ROM Motorola MB810 0001 PQ: 0 ANSI: 2
Jul 27 22:20:46 den kernel: [27131.666245] sd 43:0:0:0: Attached scsi generic sg6 type 0
Jul 27 22:20:46 den kernel: [27131.671488] sr2: scsi3-mmc drive: 0x/0x caddy
Jul 27 22:20:46 den kernel: [27131.672353] sd 43:0:0:0: [sde] Attached SCSI removable disk
Jul 27 22:20:46 den kernel: [27131.673340] sr 43:0:0:1: Attached scsi CD-ROM sr2
Jul 27 22:20:46 den kernel: [27131.674090] sr 43:0:0:1: Attached scsi generic sg7 type 5

Obviously some process is sitting on the USB port, keeping it in debug mode. I've done just about everything I can think of including carefully examinging the process table on the Droid but I don't see anything out of the ordinary.

I've tried it on a Win7 box and it fails from not finding the Motorola adb driver. On an XP box, it simply asks for the adb driver.

HELP! Please.

Thanks
JohnDriver links / Errors (https://docs.google.com/document/d/1QZtlBNvzefJXL1QAM5FJWJWlXHmy4skwmya-XaTM5QE/edit#bookmark=id.c5ul4tk8ot9y) /verify drivers are installed correctly (https://docs.google.com/document/d/1QZtlBNvzefJXL1QAM5FJWJWlXHmy4skwmya-XaTM5QE/edit#bookmark=id.abee10a1pgla)-windows
if you can't get it to work
try Hard Reset via Android Recovery (http://support.verizonwireless.com/clc/devices/knowledge_base.html?id=33552#alt)-
or
reflash firmware DX (MB810) ezSBF & Root 2.3.4/4.5.621 (https://docs.google.com/document/d/1V_meI1kibcU-yKrRwzhAuGKPEWCS0lOwNDgg2dOJOQw/edit#)

neonjohn
07-31-2014, 08:51 AM
Driver links / Errors (https://docs.google.com/document/d/1QZtlBNvzefJXL1QAM5FJWJWlXHmy4skwmya-XaTM5QE/edit#bookmark=id.c5ul4tk8ot9y) /verify drivers are installed correctly (https://docs.google.com/document/d/1QZtlBNvzefJXL1QAM5FJWJWlXHmy4skwmya-XaTM5QE/edit#bookmark=id.abee10a1pgla)-windows
if you can't get it to work
try Hard Reset via Android Recovery (http://support.verizonwireless.com/clc/devices/knowledge_base.html?id=33552#alt)-
or
reflash firmware DX (MB810) ezSBF & Root 2.3.4/4.5.621 (https://docs.google.com/document/d/1V_meI1kibcU-yKrRwzhAuGKPEWCS0lOwNDgg2dOJOQw/edit#)

Thanks for the links. I found my problem and I caused it (boy is my face red). I have a bad case of CRS but a careful review of the log I keep on what I do to each computer reminded me of why I got adb. I wanted to do this (http://blog.burrowsapps.com/2011/09/android-change-hostname.html) procedure to change my phone's WiFi name from the random digit string. Of all the procedures I found on the net for making the change, only this one worked.

In the process of either copying the file to a backup or editing it, the owner was changed from "system" to "root" and the permissions were fouled up. That was preventing Android from changing the settings I made in the USB screen and a couple others.

The solution was to chgrp the owner to system and chmod the permissions to match the backup. Power off and reboot and problem solved.

Thanks for reading and responding to my problem.
John