baher

Ok, so I've been having intermittent issues connecting my droid to my pc through usb for a while, but it has gotten to the point where it basically just doesn't work at all. I've done a lot of searching and there are a lot of posts related to this, but I haven't been able to find a solution so I figured I'd see if anybody has any new ideas. Thanks in advance!

First of all, I have tried connecting my droid to 4 computers, running win xp, win vista, win 7 64 bit and ubuntu linux. I have tried these connections with 3 different cords. And I have tried this while running BB v.4 and Sapphire 1.0, which I am currently running.

As far as drivers are concerned, I have tried both with and without motorola drivers installed. Until I rooted and started flashing custom ROMs I never installed the motorola drivers and it worked fine.

What usually happens is i connect the cable, the phone says usb connected and brings up the mount screen. Meanwhile, the computer recognizes the device and starts to do its thing. At this point, most of the time, the computer simply rejects the droid. Device manager in windows 7 will say something to the effect of "Currently, this hardware device is not connected to the computer. (Code 45)". Sometimes, it'll stay connected and claim to be working, but then i click on the phone to mount the sd card and it suddenly disappears from the computer. Maybe 1% of the time or less it successfully mounts and I have full access to the sd card, no problem. Sometimes I plug the phone in and nothing happens at all. It won't even charge.

So any ideas? I've exhausted my computer expertise at this point and I'm at the point where I either need to buy a microSD reader or bring the thing back to verizon (aka surrender).

baher

Nothing? Really? Anyone else have this problem? Am I alone out here?

OMJ

it sounds like a hardware issue if its with that many computers. The usb port on your droid is probably bad or the usb cable you are using if you are trying the same one on all these computers

__________________
I take no responsibility for what you do to your phone. I only offer advice.

baher

So if it's a bad usb connection, which is about all it could be at this point, that means i'll have to unroot and go back to stock before I can bring it in to verizon to get a new warranty replacement. Is this even possible without a functioning usb connection? The unrooting guide in the guide to all things root requires using rsdlite and the usb debug connection, but with a questionable connection it seems risky to try that even if i can get it to connect initially.

OMJ

you can also use this update.zip update-stock.zip

It only works with SPRecovery and not clockwork. Make sure you wipe data and cache. Flash as you would any other rom.

That will take you back to 2.0.1 so after that I would use this file http://android.clients.google.com/packages/ota/verizon_voles/9046f5a3ec09.signed-voles-ota-45394.zip to update to froyo. If you need instructions for that just follow this guide [How-To] Force the Official Android 2.2 Froyo Update for the Motrola Droid (FRG01B | Update 1 of 2) but be sure to use the file I linked and not the one in the guide.

baher

Excellent. Thanks a lot, man. That sounds a lot like something I shouldn't try while pretending to work, but I'll give it a whirl when I get home. Thanks again for this and all the other excellent advice on these forums.

OMJ

no problem....if you have issue when you try it shoot me a pm and if I am around I will help you out.

baher

Worked like a charm. No problems at all. And after all that, I brought it to verizon, told the service guy about the issue, and he ordered me a replacement. No questions asked. He didn't confirm the problem, he didn't even look at the phone at all.