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
I tried to do a search for this, and nothing came up for me. I recently purchased a new Laptop, running Windows 7 64 bit. My Nexus One will not install any of the drivers on such. I have downloaded the drivers from the Android Development, yet I am unable to actually use my Nexus One for ADB or for even Disk Mode. It keeps stating it is unable to install the drivers. I haven't ever tried to use my N1 with any 64 bit OS before this (except linux and mac, but that just seems to work) and my 32 bit OS's seem to work perfectly fine. Anyone else having this issue? Or possible solution?
I had the same problem when i went to root mine. I tried every tweak and hack and fix an update nothing worked.. but send someone at android community.com had it..
If you can wait a few hours i will post it when i get home..
Please don't even think of putting windows mobile on your nexus one. That is against Android law!
Sent from my CM6 Nexus One using XDA App
Keep trying and make sure you install the correct drivers. Try from another download source and don't let windows install the defaults.
naturefreak85 said:
I tried to do a search for this, and nothing came up for me. I recently purchased a new Laptop, running Windows 7 64 bit. My Nexus One will not install any of the drivers on such. I have downloaded the drivers from the Android Development, yet I am unable to actually use my Nexus One for ADB or for even Disk Mode. It keeps stating it is unable to install the drivers. I haven't ever tried to use my N1 with any 64 bit OS before this (except linux and mac, but that just seems to work) and my 32 bit OS's seem to work perfectly fine. Anyone else having this issue? Or possible solution?
Click to expand...
Click to collapse
I had the same problem. After hours trying things and searching for solutions in Google, finally MY solution was activate the USB Debug Mode
I hope this works for you too!
WaPeR32 said:
I had the same problem. After hours trying things and searching for solutions in Google, finally MY solutions was activate the USB Debug Mode
I hope this works for you too!
Click to expand...
Click to collapse
Same with me. USB Debug mode fixed it.
Im on Windows 7 x64 Pro. I havent had any problems getting ADB to work with my machine. I downloaded the SDK from the website and ran the sdk setup.exe. It will fail the first time, you have to close it and go to settings and FORCE HTTPS. once that is done. reopen it and reject everything except Device Drivers. This will download the drivers. When I connect my phone with debug mode on windows auto picks up the drivers and installs it.
I got it running on my machine ..windows64bit .. took a lil while but like someone said but it can be done ..or if all else fails install droid explorer ..and use its sdk directory
I had the same problem. In my case it was because I was plugging it into a usb port that was built into a card reader in my tower. As it turned out the usb port was not putting out enough power, so I decided to try some ports that are on the bottom of my case and the problem went away.
Each usb hub has to share power, so if you have several usb devices that pull some juice workin on the same hub you can try to get onto another hub via another port.
Win7 64 bit
I had the same problem. For me the solution was to use a legacy/older USB port on my laptop and not a highspeed one.
i am having this issue as well.
i have looked everywhere, and tried many solutions. i am lost.
my windows 7 32bit laptop sees the N1 is connected but cannot install or even find any drivers for it. i have USB debugging mode checked. i have tried ADK, using the USB drivers it provides, no luck there.
my N1 isn't rooted yet, and i'd like to trick it out. but i have to get access to it first. any help y'all can provide would be amazing.
it may be possible this is a windows 7 issue, with drivers and such. but i've been looking around for a while and can't find a solution anywhere.
I am not sure when this started. I have used windows to install cymod several times but i went to download a update and install it and my computer will not recognize the touchpad. it says the device driver was not installed properly
i have tried on two different units.
one has web os only and the other has android
it goes through the steps of looking for the device and then nothing.
i get a tone on the touchpad and then nothing on the computer
I do have the correct setting in the storage settings so i have no idea what to do
did you run novacom again?
x000x said:
did you run novacom again?
Click to expand...
Click to collapse
no i didnt see a point because Windows wont find the touchpad in explorer
Now i forgot to mention this was a fresh windows install too
dyson77 said:
I am not sure when this started. I have used windows to install cymod several times but i went to download a update and install it and my computer will not recognize the touchpad. it says the device driver was not installed properly
i have tried on two different units.
one has web os only and the other has android
it goes through the steps of looking for the device and then nothing.
i get a tone on the touchpad and then nothing on the computer
I do have the correct setting in the storage settings so i have no idea what to do
Click to expand...
Click to collapse
It sounds like driver problem to me. Search for HP touchpad driver and download and install the latest version you find, that should do it.. I'm assuming you have the MTP box checked in storage > settings > USB computer connection. Also, reboot both the tablet and the computer after installing the new driver.
Good luck.
I have two different devices one only has web os and the other has android.
on the android I have the MTp checked and have accessed it in the past but i upgraded to windows 8
that being said i had the same issue with windows 7 i just thought a fresh install would fix the issue and it has not
I have downloaded what i thought was teh latest drivers.
I have installed novacom
and rebooted my system.
and I get the same error message Windows does not recognize the device.
i get the connected tone on my computer but I don't get any response on the touchpads
did you put the tablet in usb mode?
i did on the android not on touchpad forgot how to honestly
dyson77 said:
i did on the android not on touchpad forgot how to honestly
Click to expand...
Click to collapse
In webos when you plug in the USB it will come up with a prompt. Remember to safely eject before disconnecting.
sstar said:
In webos when you plug in the USB it will come up with a prompt. Remember to safely eject before disconnecting.
Click to expand...
Click to collapse
it doesn't do anything when i plug in the usb. i get the tone on the computer but nothing on the touch-pad at all
i ried through the usb ports on the computer and the ones on the case just to be sure
dyson77 said:
it doesn't do anything when i plug in the usb. i get the tone on the computer but nothing on the touch-pad at all
i ried through the usb ports on the computer and the ones on the case just to be sure
Click to expand...
Click to collapse
Try using a different USB lead and plugging into different USB sockets on your PC sometimes I find my PC will recognize it with one socket but not another same thing occasionally happens with my USB sticks. Otherwise I would suggest trying a different PC if you still have a problem that would suggest a fault with the USB socket on your touchpad which I have had to have replaced once.
Fingers crossed that isn't your problem.
dyson77 said:
i did on the android not on touchpad forgot how to honestly
Click to expand...
Click to collapse
This will let TP be recognized on the PC
"If you want to transfer files back and forth from the CM9 touchpad you might have difficulty figuring out how exactly to do it.Here's how you pull it off:
First, tap on your app drawer in the top right of the screen (the little checkerboard). Now, select the "settings" icon.
Now tap on storage on the left-hand pane.
Finally, the tricky part - tap on the 3 squares at the VERY top right of your screen. It will bring down a little drop-down menu for USB computer connection. Tap it and put a checkmark in the "Media Device MTP" box.
Now you can plug your touchpad into the computer at will and transfer files back and forth from it. Easy as pie, I'm not sure why this isn't activated by default, but it's a simple fix if you know what to do."
Sorry I copied this from XDA a couple of weeks ago, so I can not take credit for this but it works great
that is already done on my android, and the touch-pad should auto connect. but neither are it says device not recognized
dyson77 said:
that is already done on my android, and the touch-pad should auto connect. but neither are it says device not recognized
Click to expand...
Click to collapse
Did you check my second suggestion/try it on another PC to find out whether you have a faulty USB socket on your Touchpad as they can go wrong?
yes i did and i tried 4 usb ports, but that would be rather unusual for it to go bad on two devices right?
dyson77 said:
yes i did and i tried 4 usb ports, but that would be rather unusual for it to go bad on two devices right?
Click to expand...
Click to collapse
i also just tried it on my galaxy s3 using a usb port and it gave me the same unknown device error
im not sure i read that you put TP into usb mode from webos..if not, google the how to.. really simple..
also, install the novacom again.. iirc, it has the drivers too
to me, this screams missing drivers for both devices.
it wouldnt hurt to go to youtube and watch some reverendkjr vids
amkaos said:
im not sure i read that you put TP into usb mode from webos..if not, google the how to.. really simple..
also, install the novacom again.. iirc, it has the drivers too
to me, this screams missing drivers for both devices.
it wouldnt hurt to go to youtube and watch some reverendkjr vids
Click to expand...
Click to collapse
Novacom shouldn't make a difference, I have just installed windows 8 on my laptop and haven't installed anything yet , just plugged in the Touchpad and it was recognized straight away
Sounds like either windows is messed up or the USB connector of the Touchpad has gone .
same error on TP + his galaxy??
dam the luck..busted ports on both devices at the same time..
right after a fresh format of windows ; what a coinkadink
if on your very longest shot that win needs new drivers, the palm / novacom etc
process installs them and TP will get recognized and picked up..
he said he does not know how to root his TP to put into usb mode..
i know from recent experience that even when android is in mtp mode, my PC would not connect play w/ it until i had new drivers..
same experience w/ my new nexus 7 during the process of rooting it..
amkaos said:
same error on TP + his galaxy??
dam the luck..busted ports on both devices at the same time..
right after a fresh format of windows ; what a coinkadink
if on your very longest shot that win needs new drivers, the palm / novacom etc
process installs them and TP will get recognized and picked up..
he said he does not know how to root his TP to put into usb mode..
i know from recent experience that even when android is in mtp mode, my PC would not connect play w/ it until i had new drivers..
same experience w/ my new nexus 7 during the process of rooting it..
Click to expand...
Click to collapse
Ok lets get a few things right
I do know how to root my device I did it a while ago and honestly haven't done it in a while so I am rusty
but that being said if you cant access the device at all even in usb mode then you cant root.
And yes now my galaxy s3 wont recognize either.
every time i try it tells me that there was a device error and windows doesn't recognize the device.
i formatted the cpu again and put windows 7 and no help
I have tried two diffrent touchpads one android and one web os
and my phone
to get things right you have to start at the beginning. Windows will not recognize TP w/o the drivers first. It's obvious you have been avoiding that step. you need to go back and do the whole nova com thing to install them before you attach TP to it.. look at the you tube videos. you will be finished in a few minutes. .
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.
Good evening everyone.
I have an AT&T Galaxy S6 that is under warranty. My left (recent) capacitive button has stopped working, so I'd like to replace my phone. Kick in the nuts number 1: I recently rooted my phone via PingPongRoot. No problem, I thought. I downloaded the stock firmware for the AT&T Samsung G920A, and prepared to flash the custom firmware. Kick in the nuts number 2: My data connection pins on the microUSB port are fried. I've tried 5 different USB cables, three different computers, and nothing. I've disabled and re-enabled the ADB debugging option from the developer menu. But everytime I start an ADB shell from the computer, I get nothing from the phone. Usually, the phone will say "phone is connected as a media device" or somesuch, but it only displays "charger connected". Also, normally, when I use the adb start-server command, my phone will ask me if I want to allow the computer to connect, but I do not get that prompt. adb devices returns nothing. I've tried factory resetting my phone 3 or 4 times to see if maybe it was an S6 end driver problem. No dice. So, I googled around, and it doesn't look like the firmware is possible to flash via the recovery menu? It looks like it must be flashed via Odin/Heimdall. Is this correct? And if so, does anyone have any ideas as to how I could fix this?
Thanks guys.
Your USB port is not fried, you just don't have proper ADB drivers. Lol. Google "Samsung ADB drivers" - install and reboot your computer. You also have to allow the RSA fingerprint of your computer, if you miss that prompt, you have to trigger it again. Do what I said and watch your screen when you plug it in.
Maybe I should have mentioned in my first post, only one of the PCS I used was running Windows, the rest were running Ubuntu. I will try one more windows machine with the drivers installed and report back. It's also worth noting that I tried 4 different USB OTG cables with all different kinds of devices (Flash drive, mouse, Keyboard), and none of them have been recognized either.
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Bump. I really want to know if I can maybe flash the recovery firmware from the recovery menu?
Are you running a launcher that might be interfering with the device-connection detection? Launcher-Pro on my old GSII would prevent detection of the USB cable / ADB connection. Just a thought, AoN.