I've been using ADB the last couple of days to install apps on my Captivate and all of the sudden it stopped working today.
When I type 'adb devices' the phone comes up right away, but it shows offline.
I have tried reinstalling the drivers and Android SDK, but no luck. I've searched around and found some others with this issue, but haven't really found a fix that works for me.
Any idea why ADB would just stop working like that? I even performed a factory reset of the phone and put everything back to defaults.
Ok I almost pulled my hair out, but I found the problem.
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Man, I really thought I was going crazy.
wimbet said:
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Click to expand...
Click to collapse
What the hell is that about!? I wish all these companies would stop trying to break from standards by proprietizing common cables.
I can't get the drivers to work. Where did you get yours?
Ok I almost pulled my hair out, but I found the problem.
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Man, I really thought I was going crazy.
Click to expand...
Click to collapse
Yeah I buy that, I couldn't even get the thing to try and connect at all with out switching usb connections on my computer.
stock cable works. I just rooted and ran into that problem. In order to get around it if you cant get a diff cable, make sure that b4 you connect your phone to your pc you turn off your internet so it doesnt auto dl the drivers. b4 u connect, dl the drivers for your phone from the root thread. Plug your phone into ur comp with the internet off and close any pop ups. Go to device manager look for the notification labled usb or captivateand right click and select update. Select search from file on disk or select file (something like that, i forget) and scroll and select the folder where you extracted the usb drivers. Make sure the checkbox that says search subfolders is checked and click next to install. two more drivers will pop up in device manager after u install the first one. Repeat the same procedure for both of them and then you should be able to use adb just fine to root.
Just wanted to further confirm that using a different microusb cable works! I keep reinstalling the drivers but it kept showing the device was offline. Then I tried my old Nokia N85 cable and it worked like charm! So weird how usb cables aren't made equally, unless Samsung designed the cable to prevent using adb?
I had this issue for a little while, but I installed the Samsung Kies software (which contains drivers) and uninstalled the ADB drivers I had originally downloaded. It's worked like a charm since then.
Go to SamsungApps.com and then use the canada site, as the software isn't really available in the US yet.
I have had no problems using the stock cable on my Laptop and work PC, both are Win 7 32bit. The same cannot be said for my my main home PC which is Win 7 64bit. Neither the stock cable nor an after market cable worked with ADB.
For the 32bit OSes I installed the Kies software and the usb device gets installed correctly. for the 64bit OS, I installed the Kies software but could get the phone to connect correctly. I then tried to install the 64bit drivers that are floating around the web. The 64 bit drivers worked enough to get the phone connected to the PC but when I tried to query "adb devices" the phone would always appear as offline. I've tried several things: install/uninstall drivers and software on the PC, restart the PC and Phone, change cables. Nothing seems to help on Win 7 64bit.
It seems to me that there might be a bug in the 64bit driver, though I have no proof of a bug.
I am going to keep playing with the 64bit OS until i figure it out or get so annoyed a that I just give up.
I'll be using my Win 7 32 bit laptop until I get the 64bit PC to work.
TimF said:
I have had no problems using the stock cable on my Laptop and work PC, both are Win 7 32bit. The same cannot be said for my my main home PC which is Win 7 64bit. Neither the stock cable nor an after market cable worked with ADB.
For the 32bit OSes I installed the Kies software and the usb device gets installed correctly. for the 64bit OS, I installed the Kies software but could get the phone to connect correctly. I then tried to install the 64bit drivers that are floating around the web. The 64 bit drivers worked enough to get the phone connected to the PC but when I tried to query "adb devices" the phone would always appear as offline. I've tried several things: install/uninstall drivers and software on the PC, restart the PC and Phone, change cables. Nothing seems to help on Win 7 64bit.
It seems to me that there might be a bug in the 64bit driver, though I have no proof of a bug.
I am going to keep playing with the 64bit OS until i figure it out or get so annoyed a that I just give up.
I'll be using my Win 7 32 bit laptop until I get the 64bit PC to work.
Click to expand...
Click to collapse
i've been able to install .apk's with my win7 64-bit ADB :O
all i did was install Samsung Kies.
i don't think i've ever had a problem...?
EDIT: i'm using the cable that came with it and no problems yet.
I'm running win 7 x64 and Kies did the trick for me. I haven't had a single issue connecting my phone since I did that.
Sent from my SAMSUNG-SGH-I897 using XDA App
Justa dding to the anecdotes.
I was having problems with the included cable using the front USB. It would show as Device Offline, also the charging wasn't very strong.
I switched to the onboard USB at the back of the case, and adb worked fine with the included cable.
Looks like I'll be picking up a couple extra USB cables so I won't have to continuously do the desk dive everytime I need to use it somewhere else.
1. I installed the kies drivers first and it would say offline when i checked the device through the cmd prompt.
2. I then installed the adb drivers and it then said the device was online.
3. i then rooted the phone and went on my way. i then tried it a second time and it said device offline.
4. nothing changed during this time except that i turned off debug mode, changed it to mass storage and plugged it back into the usb to transfer some files.
5. on returning to debug mode it no longer tells me the device is online. i have tried different USB ports as well.
6. i deleted the drivers, and reinstalled and it still says offline.
very frustrating.
wow. i forgot to try plugging it into another USB port. that worked. sorry about previous post.
I am running Windows 7 Home Premium 64bit on my laptop,
I installed the samsung 64bit drivers, it was an installer i found on the web, not the kies installer packaged driver one.
i changed my setting on my captivate to Mass Storage.
I mounted usb and everything works, by that I mean i was able to ADB like no tomorrow without any issues.
Then I made the mistake of installing Samsung Kies and that messed up my previous drivers and I wasnt able to ADB to my phone. I had to uninstall Samsung Kies and my phone still wasnt being found I still couldnt ADB.
my solution to fixing was restarted my phone and computer, without my phone connected to USB i re-installed the Samsung 64bit Driver Package, then hooked up my phone made sure Mass Storage was selected and Mounted USB and bam was able to ADB again.
hope this helps! also i have been doing videos helping people with issues with samsung's captivate on youtube, youtube.com/johnnyzappone if anyone wants to check em out, if anyone has any suggestions please let me know and id be happy to release a video!
I resolved my issues, I plugged the stock cable into one of the rear usb ports and the device is now available on my main PC Win 7 64 bit.
wimbet said:
Ok I almost pulled my hair out, but I found the problem.
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Click to expand...
Click to collapse
Confirmed this made my device stop appearing as offline with adb.
How it is even possible that the cable prevents (only) adb access on the PC, I have no idea.
I have windows 7 and mac osx and I can use adb with both using the stock USB.
i have debugging active.
lol @ the samsung cable.
i've 2 indentic cables here, one doesn't work. plugged in the other one and this one works...
maby its just a strange issue on windows, next time try to pull out the cable and put in back in then connect your device again this should work.... :s
because earlier the cable just worked fine and now it doesn't.. so good luck xD
joelpt said:
Confirmed this made my device stop appearing as offline with adb.
How it is even possible that the cable prevents (only) adb access on the PC, I have no idea.
Click to expand...
Click to collapse
also can confirm PITA
Alright, So I'm looking to help a friend get to the point where they can plug in their Droid 3 and it actually work.
Have plugged into every USB port, have installed the drivers Verizon reccomends installing for the device.
Basically we called up Verizon, and requested to get a actual OEM/Motorla cable. They sent a actual Motorola cable. Still doesn't work.
From what I understand the device has only been detected ONCE, and it was unsuccessful at finding drivers, now when you plug it in it doesn't even try to look for drivers. It just charges. gives you no options to mount or anything.
I've shot in and uninstalled alot of the drivers so it would cause it to re-detect and that attempt was unsuccessful as well. Uninstalled the Motorola driver application and did the same thing over, Uninstalled the USB drivers. Still nothing.
The device does run the most current version of Android, It is running stock. any clues?
perhaps try to manually install the drivers control panel/hardware/devices an printers
Have you checked the actual setting for the usb connection itself? Is it on charge only mode? Try a different computer if you can, if not, see if you can change the setting for when you first plug it into a computer, you should get the options of pc mode, charge only, media sync, and hard disk.
Sent from my DROID3 using XDA App
Jell - I'll shoot in and give that a shot if I can see if I can, Is i'll check for a driver package on the forums I guess see if anyone has one
Josh -- Not sure how to actually set the setting for the usb connection rather then when you plug it in and it asks for you to set it.
You plug it in and it charges, Doesn't ask what mode you want to put it in. Its like you're plugging it into a charger.
I have the same problem with connecting. My phone isn't recognizing that its plugged into a computer, it thinks it is plugged into a wall charger. It would be nice to know if anyone have figure this problem out.
I bought a new N7000 and everything works fine except I can't get it to connect via usb. Kies won't connect to the phone but everything else works fine with it. I can transfer via wifi with Kies.
The charger that came with it also wouldn't work, so I got my G2X usb cord and wall adapter and it charges that way, otherwise, the computer won't recognize it.
After rooting it Windows 7 finally installed the drivers for it, and the computer showed it was charging (still no usb storage though) and once I unplugged it and plugged it back in again no response.
Tried mounting usb storage through CWM and still nothing. I would think if there was something wrong with the charging port that it wouldn't work at all, but I can charge via a/c adapter. Confused.
A good test for this may be to try the Android SDK to try and get an adb connection. The reason I say this is it bypasses the samsung usb drivers and uses a generic set. If you can get an adb connection and pass a few basic commands then you'll know it's not hardware issue.
There are a few possibilities for this error...
1. MTP service is not starting correctly on the device which would suggest needing a rom reflash or factory reset. Using the Android sdk connection will help determine this
2. MTP not starting correctly at pc, suggesting driver installation/corrupt download of samsung drivers, again android sdk will help determine this
3. Usb port of pc issue. On my rig, connection usually fails off front ports, but rear ones work fine.
4. Cabling, does sound like the cable/charger that was supplied may be faulty.
5. And finally, the hardware usb on device is faulty.
How were you able to root.?
Sent from my GT-N7000 using xda premium
Once in download mode Oding would recognize the device. Other than that, the computer never will.
Hi guys, so I have a little bit of an issue! I've had my nexus 6 for about 3 months and i'm not sure when it happened or why but some how and some way no matter what rom I'm running, USB connection to desktop no longer works. I have tried turning adb on and off, reloaded drivers, and tried other computers. When I monitor device manager in Windows 10 no new devices are connected at all, just does not show up. No unknown device, adb, USB, nothing. So I'm not sure what I should do, I was thinking of claiming warranty however trying to avoid it. Any suggestions??????
P.S: Mounting external storage devices using otg is successful.
May there be some problem with your cable. Try different cable on all available usb port.
I've done that, no success
Hi All.
I've scoured the net on this one, but keep hitting a wall. Seems to be well known, but not how to fix.
Somewhere along the line, (unfortunately I didn't notice when) my 7 Pro won't now connect to the PC via USB. It did when I first purchased a few months ago, and I recollect taking a UI upgrade at some point.
Developer mode and USB debug is set on. I have the ADB Driver installed, and when I plug the lead in, the PC seems to recognise the phone being plugged in, but then as soon as I confirm 'File Transfer' on the phone, I get the disconnect sound from the PC.
I don't get it. Anyone possibly shed any light please?
Many thanks.
hi
check your phone drivers
change usb port
also change data cable
OK resolved now.
So my phone connected fine to my 2nd PC after I turned on USB Debugging. So I proved the cable too.
When I looked down the list of drivers though on each PC I saw a difference.
The good PC just had Portable Device drivers, not Android Phone drivers. So I added Portable Device drivers from the Actions --> Add Legacy hardware list. When this added, this threw up under the child devices a Lenovo Link entry which was the clue. The lenovo device was old and no longer installed, so I uninstalled this and rebooted a few times.
From then on, the Real Me connects fine.
So there must have been an underlying conflict still in the drivers list with the Lenovo device.
Cloudrider_ said:
OK resolved now.
Click to expand...
Click to collapse
Cloudrider_ said:
So my phone connected fine to my 2nd PC after I turned on USB Debugging. So I proved the cable too.
When I looked down the list of drivers though on each PC I saw a difference.
The good PC just had Portable Device drivers, not Android Phone drivers. So I added Portable Device drivers from the Actions --> Add Legacy hardware list. When this added, this threw up under the child devices a Lenovo Link entry which was the clue. The lenovo device was old and no longer installed, so I uninstalled this and rebooted a few times.
From then on, the Real Me connects fine.
So there must have been an underlying conflict still in the drivers list with the Lenovo device.
Click to expand...
Click to collapse