first gen DroidX USB stuck in "charge only" mode after using adb

This is a discussion on first gen DroidX USB stuck in "charge only" mode after using adb within the Droid X Rescue Squad forums, part of the Droid X Discussion category; 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 ...


Results 1 to 3 of 3

Thread: first gen DroidX USB stuck in "charge only" mode after using adb

  1. #1
    X Lurker
    Points: 110, Level: 2
    Level completed: 20%, Points required for next Level: 40
    Overall activity: 9.8%
    Achievements:
    100 Experience PointsTagger Second Class
    neonjohn's Avatar
    Member #
    69318
    Join Date
    Jul 2014
    Location
    Tellico Plains, TN
    Posts
    4
    Liked
    0 times

    first gen DroidX USB stuck in "charge only" mode after using adb

    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

  2. Droid X Forums
    Ads


  3. #2
    Super Moderator
    Supporting Member
    Points: 18,045, Level: 85
    Level completed: 39%, Points required for next Level: 305
    Overall activity: 0%
    Achievements:
    500 Experience Points250 Experience Points100 Experience Points31 days registered7 days registered
    Awards:
    Arm of Law
    sd_shadow's Avatar
    Member #
    56013
    Join Date
    Feb 2012
    Location
    South Dakota
    Posts
    2,449
    Liked
    286 times
    Quote Originally Posted by neonjohn View Post
    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
    Driver links / Errors /verify drivers are installed correctly-windows
    if you can't get it to work
    try Hard Reset via Android Recovery-
    or
    reflash firmware DX (MB810) ezSBF & Root 2.3.4/4.5.621

  4. #3
    X Lurker
    Points: 110, Level: 2
    Level completed: 20%, Points required for next Level: 40
    Overall activity: 9.8%
    Achievements:
    100 Experience PointsTagger Second Class
    neonjohn's Avatar
    Member #
    69318
    Join Date
    Jul 2014
    Location
    Tellico Plains, TN
    Posts
    4
    Liked
    0 times
    Quote Originally Posted by sd_shadow View Post
    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 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

Remove Ads

Ads

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Similar Threads

  1. Replies: 8
    Last Post: 03-14-2013, 01:51 PM
  2. "Vibrate in Silent Mode" on Liberty doesn't work.
    By trabo in forum Droid X ROMs
    Replies: 0
    Last Post: 04-24-2011, 04:19 PM
  3. Droid X vibrating when set to "never" or "only when in silent mode"
    By First VT Properties in forum Droid X Rescue Squad
    Replies: 13
    Last Post: 12-05-2010, 05:52 PM
  4. Replies: 15
    Last Post: 11-10-2010, 06:49 PM
  5. "loss of signal" in airplane mode
    By Bungle in forum Droid X Help
    Replies: 5
    Last Post: 08-04-2010, 07:39 PM

Search tags for this page

droidx stuck in alplaine mode

Click on a term to search our sites for related topics.

Tags for this Thread