Related
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
It seems no matter what I do I can't get the popup to show to authorize my computer on the device. The device shows up just fine in adb but is unauthorized and I can't authorize it due to never receiving the popup. I'm using Windows 8.1 which is where I prefer to do my development but I actually installed linux and set up my environment there just to see if I could at least authorize the device but still couldnt get the popup there either!
Here's a complete list of what I have tried. They arn't in accurate order, i've listed them generally as I remember doing them...
1. First off i just let windows detect the device and install the driver. The device showed up in device manager as Asus Android Composite ADB Interface
2. I'm using Android Studio. I made sure everything was up to date. ADB Version 1.0.32, Android Studio itself fully updated and everything up to date according to SDK Manager.
3. Looked to Asus for a specific driver but there is no driver for this specific model.
4. Tried Google USB drivers. Had to force install
5. Tried Asus Android ADB Interface and Asus Android Composite ADB Interface drivers I found online. Had to force install.
6. Tried Asus PC Link hoping it would install the correct drivers automatically.
7. Rebooted pc and device many times as well as toggling usb debugging, revoking usb authorizations and switching between MTP and PTP. All of these were done in just about every possible combination with every driver I have tried.
After all of the above the device continued to either show offline or unauthorized. All these drivers seemed to work as the device was picked up by adb, but no authorization dialog on device.
8. All of the above was done under Windows 8.1 so at this point I said screw it and installed linux just to see if I could at least get the authorization popup to show. I Installed Android Studio under linux and performed all the necessary steps. To cut a long story short I did pretty much the same as I did in Windows minus messing around with drivers. Again under linux I could get the device to show but either as offline or with no permissions and still no authorization dialog.
9. I don't know much about linux, so had the help of a couple of kind guys on irc who walked me through some other things which im not entirely sure what they were.....something like adding android rules and registering usb devices manually with their PID and VID. lsusb seemed to show the device just fine.
10. Evntually gave up on linux as I hadn't made any progress at all and I was just getting the same problems as with windows 8.1. So at this point I went back to Windows.
11. Went back to the Asus site and grabbed a an adb driver for a simalar device (differnt model of the memo pad 7). I had a look in the inf file for this driver and found that my model was actually in there and got excited. Windows wouldn't let me install because of the file being corrupt or possibly being tampered with, so I disabled driver signature enforcement and windows happily installed them. This was something new as they were the first drivers that installed niceley since the very first one windows automatically installed. I'm satisfied now that I actually have the right drivers due to my model actually being in the inf file and the device is now being picked up consistently by adb. When it is picked up as offline all I need to do is toggle usb debugging and it gets picked up again as unauthorized...but still....
NO AUTHORIZATION DIALOG ON THE DEVICE....ARGGGHHHHHH!
Also I should mention, while doing this I also tried with a Lenovo device as I went through each step of trying to get the Asus to work and I had the same problem with the Lenovo. No authorization dialog. But how is this possible? 2 devices, multiple usb cables, 7 usb ports, Windows and Linux, Multiple drivers for each device etc etc.
I'm at the end of my tether here. I have been at this for about a week solid now and I am no closer to finding out the problem. Surely it can't be 2 problematic devices? But It can't be both Windows and Linux? Are all my USB ports broken? Are all the 5 USB cables I used (Official asus, official lenovo, official htc and 2 generic cables) damaged?
The only similarities here are that The pc remains the same and both devices are kitkat 4.4.2.
Please help!
EDIT: I now have 5 devices here. The Asus Memo Pad 7 ME170C, Lenovo 3500-f, Archos Gamepad, HTC Desire HD and a crappy chinese tablet off ebay (Allwinner A13). The latter 3 are running older versions of android that don't have the whitelisting feature and all show up with their serial numbers ABCDWHATEVER Device when running adb devices but as soon as I run android studio they go offline. The Asus and Lenovo show as ABCDWHATEVER Unauthorized (still not getting the authorization dialog on these two devices) and also go offline when running android studio.
Ok, it looks like i simply cannot access any android device on this PC. I can't even browse the files on the device in windows as the window just locks up and the top green progress bar runs and gradually gets slower then never completes. I'm gonna make a new post on another forum about this since it no longer seems device specific.
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).
I have installed all drivers i could fine. Whenever i plug the watch into my pc it doesn't even make the chime sound, nor does the device show up in device manager.
Can someone please help me, i just got my watch two days ago and would like to enable more cores because mines quite laggy on android wear 2.0.
If you have enabeld USB Debugging ?
This you can do in the Developers Options.
If you dont see Developers Options under SETTINGs then you must first enable the Developer Options...
To do this ...
Go to SETTINGS there in Devices Info and then TAP 7 times at Buildnumber... after this go back to Settings and you see the Developers Options and there you can enable USB Debugging
Sorry for my bad english...
i have already done that also. ive tried about everything i can fine. the dock charges the watch just fine, i have also tried different usb cords. is there any way to adb over wifi?
TTGZDOG said:
i have already done that also. ive tried about everything i can fine. the dock charges the watch just fine, i have also tried different usb cords. is there any way to adb over wifi?
Click to expand...
Click to collapse
Hey did you found any solution?
I am on the same boat, the watch can charge and works (laggy) fine, but I am unable to let it be recognize in any way.
I tried same USB cord with several phones and it's ok, but the watch cannot be in any way recognized...
Someone please help us out lmao, the watch is so damn laggy and battery is awful.
I managed to do adb over wifi on the watch, but obivously this do not help with unlocking bootloader or anything in fastboot mode..
codymamak said:
I managed to do adb over wifi on the watch, but obivously this do not help with unlocking bootloader or anything in fastboot mode..
Click to expand...
Click to collapse
Did you all download and try the latest adb? I was having this same issue and turned out that once I updated the adb from the Android sdk, everything worked perfectly.
Uhm, I'll try thank you!
I downloaded all the driver I could get, even from official android.com site, but still the issue is same:
When I plug USB cable in the PC, I get no chime sound or request of anything: tried putting the watch on cradle in standard running mode, in fastboot mode, or in recovery or even powered off.
Same result: no reaction from PC at all.
Tried connecting various phones with same cable as the watch cradle usb cable, everytime the driver kick-in and phone is detected and system either use Google USB driver or ask for drivers.
I read somewhere on the internet that if phone is not connected with Wear app the smartwatch is not connected? But how to do that if the watch is in fastboot mode for unlocking?
Btw I also found that the system update was to version NXG47C and now the fastboot menù is indicating that bootloader is version LENOK22b (secure boot is enabled in green and lock state is locked).
I am lost, even the SDK Android drivers did not change a thing, but more than anything else I do not get why PC do nothing (not even chime sound) when plugging in, my cradle is original and all things come from its box from 2014..I never tried before connection so I do not know if that was working before, but I am starting to think I need a new cradle maybe...
codymamak said:
Btw I also found that the system update was to version NXG47C and now the fastboot menù is indicating that bootloader is version LENOK22b (secure boot is enabled in green and lock state is locked).
I am lost, even the SDK Android drivers did not change a thing, but more than anything else I do not get why PC do nothing (not even chime sound) when plugging in, my cradle is original and all things come from its box from 2014..I never tried before connection so I do not know if that was working before, but I am starting to think I need a new cradle maybe...
Click to expand...
Click to collapse
I have 2 cradles (that -same thing as you- work with anything else instantly) and since the NXG47C/LENOK22b combo simply do not work, so it seems it isn't a cradle problem. :crying:
Did you find anything else, codymamak?
m3ta said:
I have 2 cradles (that -same thing as you- work with anything else instantly) and since the NXG47C/LENOK22b combo simply do not work, so it seems it isn't a cradle problem. :crying:
Did you find anything else, codymamak?
Click to expand...
Click to collapse
Sadly, no.
I was just looking to cradle options but what you are reporting here now makes me believing that really, it's something else...but probably only LG knows why they did that...Only reason I can think of, is to make us users purchase newer models locking out features that make it still good with AW 2.0
It's really a pity.
My only other idea is to try with a different OS, as atm I got only Win 10 64bit Creator Update , but I could use a old HDD and try with a Win 7 32bit...but it's a LOOOOOOOOONG shot as from my experience at least the chime sound should be there...:crying:
Oh! Different OS - I forgot to mention it before, sorry: I tried on Windows 10 and MacOS.
Again, both work fine with other Android USB-debugging-active devices.
Sorry for adding more bad news to an already bad story.. :/
I would have guessed this, sadly.
Well, this means something needs to be found to reactivate the fastboot connection from the devs...meanwhile, I found that the old dev options to lower the scale of the animations improves a bit the slugginess of the watch...
Let's hope someone notices this thread and find a way to help us out, as I'm 100% no-dev...
codymamak said:
Sadly, no.
I was just looking to cradle options but what you are reporting here now makes me believing that really, it's something else...but probably only LG knows why they did that...Only reason I can think of, is to make us users purchase newer models locking out features that make it still good with AW 2.0
It's really a pity.
My only other idea is to try with a different OS, as atm I got only Win 10 64bit Creator Update , but I could use a old HDD and try with a Win 7 32bit...but it's a LOOOOOOOOONG shot as from my experience at least the chime sound should be there...:crying:
Click to expand...
Click to collapse
Exactly same thing about me. USB plugged in and nothing happen, I tried win 10 OS and win7 - same problem - I also thought it is cradle problem, I almost bought a new one but after you wrote I dont't think I could help look we are stucked with AW2.0 and only thing is hope someone will find solution for this...
I am still stuck on this situation, no way to make watch try the USB connection.
Could it be possible that the latest update disabled the USB ADB?
Can someone confirm if the USB ADB files are still in the package?
And if not, is it possible to add them back using for example ADB over wifi, through maybe the original recovery if not possible with system running?
codymamak said:
I am still stuck on this situation, no way to make watch try the USB connection.
Could it be possible that the latest update disabled the USB ADB?
Can someone confirm if the USB ADB files are still in the package?
And if not, is it possible to add them back using for example ADB over wifi, through maybe the original recovery if not possible with system running?
Click to expand...
Click to collapse
It is really anointing when some other users write about downgrade without problems. I'm thinking how is it possible, so everyone got the same version of AW2.0, it is really weird
I have 2.0 on gwr and my win 8 recognised them. I just installed adb usb drivers in same way as I did for Huatch: as Motorola android sooner composite adb interface.
Where do I find these famous motorola android sooner drivers for w7 x64?
Adambeat22 said:
Where do I find these famous motorola android sooner drivers for w7 x64?
Click to expand...
Click to collapse
Probably installed with drivers for motorola phone. The thing is I did not install this exact adb driver on purpose. I found it as I was trying out anything to make the watch connect to PC. It was a pure luck.
same thing happen to me!
I thought it was the cradle, I have 3 cradles, though all is not original, all fail. so I though the cradle only can charge. But I vaguely remember I once using it to flash, but my memory is not so reliable, so it can be the original or the 'not original'.
I can connect ADB using the bluetooth debug mode and go to fastboot, but even in fastboot mode, my pc still cannot detect the watch.
Not much support here anymore; watch too damn old. But IMHO it's still a goody.
Anyhow I somehow got mine flashed back to 42N (android 4.4, I think). The thing is that bluetooth does not work at all on that version, so can't set the watch up with the phone.
Can boot into fastboot/downloader mode but when I do, my computer doesn't "see" the device.
Adb/fastboot both working fine on another unit (LG V20). I'm completely stumped.
RootJunky (TomSgt) or Adam Outler, I know you both did quite a bit with this watch early on. So PLEASE help.
Boowho??
Slightly old thread, but when "doesn't see the device", does your computer make the hardware connect/disconnect sound?
Have you tried a different USB cable? Some micro USB cables do not carry data and are only for charging.
If it's not a charge-only cable, check Device Manager and see if anything new appears in there. It could be the fastboot or ADB drivers are not installed.