USB connection not working

Discussion in 'Droid 2 Tech Issues' started by willskith, May 28, 2011.

  1. willskith

    willskith New Member

    Joined:
    May 28, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    When I connect my Droid 2 to my computer via USB nothing happens. I have never had any problems until tonight, I was just uploading .apk files to it two nights ago. It's rooted and running the standard ROM.

    On the phone the USB notification does even not appear, and on the computer (Win 7 64) I hear the hardware connecting beep but the MotoHelper icon doesn't appear in the system tray like it usually does. In Device Manager it shows up as Unknown Device with device status listing "Windows has stopped this device because it has reported problems. (Code 43)."

    I tried uninstalling and reinstalling drivers, as well as using USBDeview as recommended in another thread for someone with a similar problem. I plugged it into my Netbook as well and it doesn't show the device either, giving the same error in Device Manager with no USB notification on the phone.

    Anyone have any ideas? My next step in troubleshooting would be to reinstall the necessary system files on the phone (if that is even possible)
     
  2. newk8600

    newk8600 Member

    Joined:
    Sep 15, 2010
    Messages:
    37
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    CO/NE
    Ratings:
    +0
    Are you using the stock USB cable that came with the phone? also what mode is it in? is it in PC mode or USB mass storage?
     
  3. willskith

    willskith New Member

    Joined:
    May 28, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I'm using a 3rd party cable, but as stated it had worked in the past. I'm not getting an option for USB modes as it is not recognizing that it is connected.
     
  4. newk8600

    newk8600 Member

    Joined:
    Sep 15, 2010
    Messages:
    37
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    CO/NE
    Ratings:
    +0
    I would try it with the original cable if you have it because third party cables can stop working at anytime.

    Sent from my DROID2 using DroidForums App
     
  5. willskith

    willskith New Member

    Joined:
    May 28, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I got this phone used, don't have the original cable. I'll try it with a higher quality one and see if it works.
     
  6. ldopa

    ldopa Silver Member

    Joined:
    Jan 4, 2011
    Messages:
    4,742
    Likes Received:
    2
    Trophy Points:
    153
    Location:
    Rochester NY
    Ratings:
    +2
    It has to be a driver issue.

    From my Liberated DROID2 at 1.25ghz
     
  7. willskith

    willskith New Member

    Joined:
    May 28, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I just tried it again with the same cable as before and now it is working no problem... strange. Still have no idea what could have caused it, hopefully it's just a bad cable with intermittent issues. I'll get a better one.
     
  8. willskith

    willskith New Member

    Joined:
    May 28, 2011
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Just in case anyone else has this issue in the future...
    It started happening again, phone wouldn't recognize that a USB cable was plugged in or anything. I unplugged it, turned off USB debugging mode, plugged it back in, and everything started working fine again...
     
Search tags for this page
android phone usb connection not working
,
droid 4 usb nothing happens
,
droid phone just beeps when i connect to usb
,
droid razr m driver error code 43
,
droid razr windows has stopped error code 43
,
droid usb icon doesn't appear
,
htc droid dna usb connection problem
,
i dont have the usb connection icon on my samsung droid
,
usb connection icon on mini droid
,

windows has stopped this device because it has reported prob