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
Has anyone else had any issues here? I've been unable to connect to the adb on my home PC, curiously on my work PC it's been fine.
It's displaying as a "C6903", with hardware Ids:
Code:
USB\VID_0FCE&PID_519E&REV_0232
USB\VID_0FCE&PID_519E
Which don't even seem to show up in Sony's official drivers.
Absolutely baffled. All I can think is the hardware ID was coming up as something different on the work PC. I've tried forcing the android_winusb.inf drivers on it, by adding the ID to the list and adding the vendor ID to the file in the home directory.
I've had quite a mash of Android devices on this machine, I'd really really not format to clear it up though.
Any ideas? Thanks!
I've just tried another machine, and interestingly the above is actually a standard "USB Composite Interface", quite why it can't figure it out I have no idea.
Edit: Wow, after more digging around, I realized the stock USB Composite drivers were missing from the machine (usb.inf). I restored a version into C:/Windows/INF, it detected and installed. Everything else appeared straight after.
EDIT: RESOLVED!
The issue was caused by AdFree (h**p://adfree.big*tin*can.com/, thank you forum software from objecting to a URL and erasing my entire edit). This is strange because I have an older version of AdFree on my old Samsung Galaxy Nexus, and it worked fine for years. This is very bizarre and the symptoms are very misleading, but as soon as I uninstalled AdFree, my problems stopped.
I guess I need to find a new ad blocker, can anyone recommend? This was resdon #1 why I rooted the phone.
****************************
Hi everyone, have a problem with my brand-spankin-new N6, and it's driving me up the goddamn wall, hoping for some help.
Running Win7 64 bit. Never had issues of this sort before.
Got Nexus 6, rooted using Wug's kit. Everything went peachy.
Then I tried connecting it to my PC, and... no joy. The PC makes the usual "ba-donk" noise that indicates that a USB device has connected, and the little icon shows up in the taskbar with the green dot goin round and round... It grinds for a while, and then pukes out with "The device was not successfully installed" error. I tried different USB ports and different cables, same result. What's worse, this is happening on my laptop as well (also Win7, 64 bit).
Also in the system event log I see this: The device MTP USB Device (location Port_#0004.Hub_#0003) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.
Now here's the kicker... if I shut down the phone (power off) and then power it on while it is plugged in, it shows up in the Windows Explorer, and I can access and browse it (and Windows even says "device installed successfully"). But if I unplug it and then plug it back in, the above scenario plays out again, and I can't access my N6.
Under Device Manager, N6 shows up under "portable devices", sometimes as "Nexus 6" and sometimes as "MTP USB Device". Sometimes it looks normal, and sometimes it turns up with "this device could not start." If you think this is maddening, it's because it is.
I have tried:
- Shutting off USB Debug - no effect.
- Rebooted multiple times - no effect.
- Downloaded the latest google driver and the motorola device manager - no effect.
- Uninstalled driver while Nexus was plugged in (right-clicked, properties, uninstall driver). Re-plugged Nexus, Device manager shows "USB MTP Device", but device cannot start. Right-clicked on device, update driver -> drivers that I have on my PC -> USB MTP Device -> it grinds for a while, still cannot start the device (Code 10).
- Used USBDevView to blow away any Google drivers, and anything resembling Nexus 6, then replugging it and reinstalling it - no effect.
- Uninstalled Wug's kit, including the drivers - no effect.
Driver information shows that it's using Microsoft's USB drivers,
I don't know what else to do, and am quite beside myself. I've read multiple posts on the subject, some of them suggest "uninstalling the driver while the phone is unplugged" which is not really an option what with the phone not being listed in the device manager when it is unplugged! Also, my laptop didn't have Wug's kit on it in the first place and it's displaying the same symptoms.
Now of course in a pinch I could shut off my phone and reboot it every time I wanted to connect it to a PC., but that is patently stupid and definitely doesn't qualify for "working as intended" for a goddamn $700 brick!! I'm starting to suspect that rooting the phone somehow pooched it, because it was connecting fine prior to root. And Wug's kit has never given me issues! (I rooted my previous Nexus with it, now granted it was the original Galaxy Nexus from way back then).
I feel very stupid for having to ask this, but I really have never seen this kind of crap before. I mean, what can be simpler than connecting your phone to your PC, right? (ha-ha). Please be helpful and gentle, I really would like this resolved. At this point I'll follow any step-by-step instructions, even if they involve sacrificing chickens and doing the ol' rain dance. Thanks in advance.
Issue resolved!
Check out AdAway working fine for me
Nexus6Newbie said:
I guess I need to find a new ad blocker, can anyone recommend?
Click to expand...
Click to collapse
cOmrade93 said:
Check out AdAway working fine for me
Click to expand...
Click to collapse
+1
I ended up just pasting a bunch of entries into hosts file. Blocks most of it, I think (though can't seem to squash ads in some games like Angry Birds for some reason).
So I was happy remaining on stock with my watch until a number of things happened: I flashed stock lollipop on my note 3, expecting a few things to break with android wear, and sure enough, the watch has problems reconnecting to the phone after it has been out of range for a few minutes (fixed only by restarting the phone). This annoyed me, but there was no going back on my note 3. So I thought to hell with it .... I'll root the watch and flash the urbane port, which should give me wifi, maybe that will help.
I haven't had to use adb in 5 years, so I'm a bit rusty, and android sdk kind of scares me now.
But I marched on. I got hold of the google usb drivers and got my watch detected. Or at least so I thought. I downloaded "fastboot+adb.zip" from somewhere so as to avoid messing with the full sdk, and tried "adb devices". Device detected, but "offline". Every guide I read mentioned that when the watch is plugged in after the drivers are installed, the phone should prompt you to enable wear debugging. That never happened. And I've removed the drivers and reinstalled them countless times now (but I don't see why the driver pack from android sdk website wouldn't work). The watch is listed as "Android Composite ADB Interface" in Device Manager. Oh, and I'm running windows 8.1
ANY help at all would be greatly appreciated. I realize this is extra noobish but I'm just out of practice, honest. And I'm kind of suspecting that the watch just isn't playing nice with the note 3's new lollipop. In which case I'm kind of screwed.
Had the same strange problem, took it to the service centre and they changed the logic board. When you connect it to the computer via usb does it recognise it as watch or unknown device ?
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