Trying to root - Phone not recognized in ADB

[SweetBearCub]

I downloaded and installed the Win x64 Samsung Galaxy S drivers from the wiki link (I installed them with the setup.exe in the archive).

The setup program completed successfully, and I connected the phone to a known working USB port with a known working cable, but my PC does not react to it in any way. The phone does begin to charge.

At a command prompt, "ADB devices" results in "List of devices attached" which is blank. I've rooted an LG Optimus S before, so I know I should be seeing at least one entry in this list.

ADB debugging is enabled on the phone.

Any suggestions?

[gTen]

When you plug it in..do you see drivers being installed for the device on the bottom right? or does it say unidentified usb device?

[SweetBearCub]

Originally Posted by gTen

When you plug it in..do you see drivers being installed for the device on the bottom right? or does it say unidentified usb device?

No, to both questions. My PC did not react to the phone in any way.

[gullzway]

Do you have another, non 64 bit, pc you can try it on?

Sent from my Epic 3G on SERO.

[SweetBearCub]

No...

Originally Posted by gullzway

Do you have another, non 64 bit, pc you can try it on?

Sent from my Epic 3G on SERO.

[gTen]

Originally Posted by SweetBearCub

No, to both questions. My PC did not react to the phone in any way.

Open up device manager, then plug in the phone..do you see anything thats a warning?

[SweetBearCub]

Originally Posted by gTen

Open up device manager, then plug in the phone..do you see anything thats a warning?

Above is a screenshot of my Device Manager, running with Admin privileges. The highlighted device under 'Network Adapters', which is not phone-related, is disabled for other reasons.

[SweetBearCub]

Aha I think I may have figured it out.

I was using the micro-USB cable from my LG Optimus S, preferring not to unpack the (supposedly identical) cable from my Epic 4G's box.

When I finally switched to the Samsung cable, the phone was recognized. 3 of the 4 drivers have installed, Windows is still processing the 4th (the "CDC Abstract Codel Modell (ACM)". It's been going for a while, I expect it will likely fail.

While that 4th driver is processing, typing "ADB devices" at the commandline did show my phone - But "ADB shell" returned a "device is offline" error, probably because Windows is still trying to install the 4th driver. I guess I'll wait until it times out.

[gTen]

Originally Posted by SweetBearCub

Aha I think I may have figured it out.

I was using the micro-USB cable from my LG Optimus S, preferring not to unpack the (supposedly identical) cable from my Epic 4G's box.

When I finally switched to the Samsung cable, the phone was recognized. 3 of the 4 drivers have installed, Windows is still processing the 4th (the "CDC Abstract Codel Modell (ACM)". It's been going for a while, I expect it will likely fail.

While that 4th driver is processing, typing "ADB devices" at the commandline did show my phone - But "ADB shell" returned a "device is offline" error, probably because Windows is still trying to install the 4th driver. I guess I'll wait until it times out.

unplug the device and plug it back in, that usually does the trick..if not, in device manager click on that CDC device and install drivers manually from the 16_Shrewberry folder

[dumpringz]

Wirelessly posted (Samsung Epic : Mozilla/5.0 (Linux; U; Android 2.1-update1; en-us; SPH-D700 Build/ECLAIR) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17)

id like to know the differences in the cables. ive read of similar issues all over