I am just getting started in Android development, and am trying to get Eclipse (running on Windows 7) to recognise my phone so that I can use it for debugging. However, my phone does not seem to be recongised by Eclipse or by running "adb devices" from a command line.
Here's what I've tried:
I've tried both MTP (media device) and PTP (camera) transfer modes (similar questions on Stack Overflow have been resolved by using PTP).
I've ensured that USB debugging is turned on in my phone's settings.
I've manually installed a driver in Device Manager, by choosing "Update Driver Software" and selecting the .inf file in sdk\extras\google\usb_driver (which I had to modify by hand to include my device).
I've tried a Nexus 4 phone, a Nexus 7 tablet, and a Motorola Moto G phone. Behaviour is identical for all three devices.
I've tried the "Universal ADB driver", in case it behaves differently to the Google driver, but it doesn't behave any differently.
I've rebooted, I've reinstalled drivers, I've tried adb kill-server followed by adb start-server, etc.
No matter what combinations of the above I try, "adb devices" lists nothing. When I look in the Windows Device Manager, I can see "Android Composite ADB Interface" listed under the "Android Device" node, so I believe I have installed the driver correctly. I am logged in as an Administrator, so it's not a permissions thing either. I've tried every answer to every single similar question on Stack Overflow, but nothing works. I've been pulling my hair out all day and am close to running out of hair... any ideas appreciated.
EDIT: It just occurred to me what could be causing this. I am running 64-bit Windows 7, but 32-bit Java. Because I have 32-bit Java installed on my PC, I installed the 32-bit SDK. Would that explain this behaviour? Should I be running 64-bit Java? The only reason why I didn't is because 32-bit Java is installed by my company's group policy...
EDIT2: I have now noticed that when I plug an Android device in, and look at its Device ID in Device Manager, the device ID does not end in "&MI_01". When I plug the device into another Windows 7 PC, the device ID does end in "&MI_01". I believe this is why "adb devices" is not able to detect the device. Any idea why one PC would see a different device ID to another, with the only difference being the "&MI_01"?
Did you install your phone USB-driver?
and can you check it on device manager is installed or not? you can download your usb driver from yur phone company website.
After you install your phone usb driver , I think the problem is solved
I think the main reason is because the computer does not recognize your phone as below 1 device used to debug code, even usb device.
You can try to do the following:
- Turn up the window update
- Uninstall driver for usb connection from your phone to your computer
- Go to the homepage of the mobile device, download driver for usb connection to the computer and then reinstall the driver
Try Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices.
Download
After downloading extract .rar file into a folder.
Go to Device Manager, right click on Android phone and click to update driver. On next screen , give path of extracted folder and install it.
You can install with msi file also. Download .msi
Finally found the answer. I was missing a file called usb.inf from C:\Windows\inf. Not sure how on earth files just go missing from yours Windows directory...
Before asking my question, I have looked through a few threads that share the same problem as me and have tried all the given solution with no success. I am from Malaysia.
I cannot get my device to be detected to test my app on my phone. I have checked both the "Unknown sources" and "USB debugging" settings in my phone. I am using eclipse. But if I create a random virtual device, my app is able to run there.
Okay so I am using a Motorola Atrix 2. And I'm using Windows 8 Pro 64 bit
I have downloaded android SDK bundle from here : http://www.motorola.com/sites/motodev/us-en/motodev_lp.html
I have also tried downloading the latest driver with no success. I have also added this line in the manifest android:debuggable="true"
I have tried both as a mass storage device and a media transferring device.
I would appreciate any help a lot because as of now, I cannot progress further into developing an android app and that saddens me. :(
I have attached a picture of which my android phone should be detected in the window, but as you can see, none.
https://pbs.twimg.com/media/BJu1XSgCYAEGCUd.jpg:large
go to /your-android-sdk-directory/platform-tools using command prompt.
type
adb kill-server
adb start-server
adb devices
n see whether ur device is detected now or not...
Note: if you're using a Linux machine then put ./ before adb
Install proper drivers for your adb devices, from Android-SDK archive or Motorola site.
If you are on Windows machine, go to the device manager find your device, and select folder with drivers for it.
Open you windows os's explorer, have a look at the process, if there two or more process hold your adb, try to exits the process
Check that the android:minSdkVersion is lower or equal to the Version running on the phone. If it is higher it wont show on "Android Device Chooser"
Install and run programs/drivers with admin rights.
Have you installed Motorola Device Manager?
When debugging Samsung and HTC devices I got it to work by installing that kind of software (for syncing the devices to the computer).
Download from the following: ABD Universal Driver
and install it. Make sure you have your device plugged in before installing and make sure you are on USB debug mode on the phone settings.
I am attempting to install an Android app on my brand new Nexus 10. I have a .apk file. I have downloaded the Android SDK, installed "Android SDK Tools", "Android SDK Platform-tools", and Google USB Driver. I have checked the setting on my Nexus 10 for "Unknown Sources".
When I run "adb devices" from the command terminal, it doesn't list any devices. I attempted to follow this recommendation, because it was identical to a suggestion I had previously found here on Stack Overflow. After following those steps, "adb devices" still returns an empty list and to make it worse, when I connect my Nexus 10 to my PC, Windows doesn't show any folders within the device.
I have undone the steps in that link, along with everything else I have done so far, as well as uninstalling my Nexus 10 from Device Manager and reinstalling it, but I am still not seeing any folders in the device.
Is there anything I am missing to get my device to show up in ADB devices?
What can I do to get Windows to see the folders within the device?
Windows 8 wouldn't recognize my Nexus 10 device. Fixed by Setting the transfer mode to Camera (PTP) through the settings dialogue on the device.
Settings > Storage > Menu > USB Computer connection to "Camera (PTP)"
For Windows 8 users:
After trying every solution given here, with no success, I found this:
Go to Device Manager
Browse my computer for drivers -> Let me pick from a list of device drivers on my computer
Choose Android Device and then Android ADB Interface.
Now I have my devices listed at adb devices.
This situation seems to arise with some ADB drivers. I have encountered the same thing with a couple of Google devices and installing the Universal ADB windows driver has fixed it for me every time.
Use another cable.
Just found out that one of my regular charging cables had Vcc, Gnd pairs, but no Data+, Data-.
https://en.wikipedia.org/wiki/USB#Pinouts
Make sure to Enable USB debugging in Settings -> Developer options
Also, run "adb devices" after getting into the platform tools folder in the Android SDK (unless you have that folder on your system path already), otherwise the command won't be found.
The device may not be visible for debugging if it is in MTP mode. Some devices only work in PTP mode (or even in "charging only" mode).
This can be changed in Settings > Developer Options > Networking > Default USB configuration > PTP.
Also, you'll get a notification on your android device asking you for confirmation about USB configuration setting change and to allow it.
Note: You can turn on developer options by following the link below:
enable developer options
I have found a solution (for Windows 7):
Connect your Nexus 10 to PC
Go to Windows Device Manager
RClick on ADB Interface -> properties
Details -> Hardware Ids.
You will see two records like these:
USB\VID_18D1&PID_4EE2
USB\VID_18D1&PID_4EE2&MI_01
5 Open the android_winusb.inf file (I have it in "C:\Users\<username>\AppData\Local\Android\android-sdk\extras\google\usb_driver" directory)
6 Create such records in [Google.NTx86] and [Google.NTamd64] sections using Hardware Ids from properties of ADB interface:
;Google Nexus 10
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
7 Save the file, and update driver for ADB Interface with showing the path to "C:\Users\\AppData\Local\Android\android-sdk\extras\google\usb_driver" directory
Sometimes ADB loses connection to the device, and needs to be reset. If you have everything else working (ie USB driver installed, Developer settings enabled on the device), and still can't see your device, you need to reset the ADB process.
This is available in the DDMS Perspective (from within Eclipse), Devices tab (the triangle on the far right includes a menu item to perform the reset).
Otherwise from the command line, you can reset it with the following 2 commands:
adb kill-server
then
adb start-server
Enable Developer options in your device. To enable the developer mode, setting->About phone, tap Build number option 8 times continuously
Go to Settings-> Developer options and Turn on USB debugging
From the above steps it didn't work try this step, Go to Settings->Security and turn on Allow Unknown Resources
You have to download the drivers from the SDK manager (extras → Google USB Driver)
Then you have to install the USB driver in Windows (it works for me in Windows 8.1):
(Copy and paste from http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver:)
Connect your Android-powered device to your computer's USB port.
Right-click on "Computer" from your desktop or Windows Explorer, and select "Manage".
Select "Devices" in the left pane.
Locate and expand "Other device" in the right pane.
Right-click the device name (such as Nexus S) and select "Update Driver Software." This will launch the "Hardware Update Wizard".
Select "Browse my computer for driver software" and click "Next."
Click "Browse" and locate the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.)
Click "Next" to install the driver.
After downloading the Google drivers via Android SDK Manager (available via Eclipse, Intellij or Android Studio), I had to update the driver in Computer Management > Device Manager > Other Devices > ADB - right clicking and clicking on update driver and browsing for updated driver finally did the trick.
BTW, a total nightmare for me as well. I continue to be bewildered that setting up a dev environment should be the most difficult task imaginable, with each new inexplicable failure leading to another one. Jeesh! Good luck.
On my Windows 8.1 64bit (Nexus 5 did not show up), only manually installing the USB driver fixed it:
http://developer.android.com/sdk/win-usb.html
The "Google USB Driver" in "Android SDK Manager" was installed already.
I still get this once in a while and it usually works if I unplug it and plug it back in a different port. I'm on Linux but had the same thing happen on Windows before.
Installing Samsung Kies and using their tool to reinstall device drivers, is what finally worked for me with my Galaxy S3 and Tab S 8.4
Normally SDB will download the driver in the **android-sdk-windows\extras\google\usb_driver** path
Here are the steps that worked for me:
Enable USB debugging.
Do to device manager, right click on ADB device and click update driver software.
Select "Browse my computer for Driver Software"
Select "Let me pick from list of Device drivers on my computer"
Click on "Have Disk" option.
Select the driver path **android-sdk-windows\extras\google\usb_driver** (path of sdk)
7.Select 1st driver out of list of drivers shown.
And hopefully, it will work.
Edit: I recommend you DO NOT run ADB under VirtualBox if you are using a Windows Host. Somehow I got VirtualBox to lock the device drivers on the host, eventually making it so that the ADB wouldn't work on the client nor the host for any device I plugged in. To fix, I removed VirtualBox extensions on the host and ran http://www.nirsoft.net/utils/usb_devices_view.html to delete the incorrect drivers. I could not get the correct drivers to load while VirtualBox extensions were installed, and this problem was a complete bastard to diagnose and fix.
Edit 2: Also the following is probably out of date, now that Google have released an integrated ADB extension for Chrome.
What an installation nightmare... Here are the steps I needed to get my Nexus 10 recognised on an XP virtual machine running under VirtualBox:
If you get asked to install Nexus 10 drivers, make sure to untick "don't ask again" (you WANT to be asked again!).
Plug in the Nexus 10 USB connection
Turn on debugging in the Nexus 10 settings Developer menu (tap "About Tablet" 7 times to get that menu).
In your virtual machine settings (host), add the samsung Nexus 10 device to the USB Device Filters (important - selecting it from the devices menu didn't seem to work).
In guest install java jre (if you don't have java installed). In Control Panel, change Java settings so that java doesn't run in the browser (to help prevent security issues).
In guest get the adk zip file and put it somewhere permanent. I needed to delete the .android config directory from the user directory because I moved the directory.
Run the SDK Manager.exe - if it doesn't work, try running sdk\tools\android.bat which seems to give better error reporting.
From SDK Manager install the Google USB driver package.
Unplug the Nexus 10 and plug it in again, and install the Google USB driver package.
Restart the guest.
running c:>[...]\sdk\platformtools> adb devices finally shows me the device...
For the Blu Studio 5.5s ADB drivers, you have to go through this hoop. I am certain it is the same with all Blu phones or maybe for all non-Google mfg phones, I am not sure. First of all if you connect the Blu device with USB cable and USB Debuggin off, you will see that Windows 7 loads a generic driver for you to copy on/off files to the phone and SD storage. This will appear when the USB cable is first plugged in and appears as a device icon under Control Panel, Device Manager, Portable Devices, BLU STUDIO 5.5 S (or the device you are working with). Do not bother getting the hardware ID yet - just observe that this happens (which indicates you are good so far and don't have a bad cable or something).
Go to the phone and switch on USB Debugging in the Developer section of your phone. Notice that an additional item appears as an undefined device now in the device manager list, it will have the yellow exclamation mark and it may have the same name of the phone listed as you saw under Portable Devices. Ignore this item for the moment. Now, without doing anything to the phone (it should be already in USB debug mode) go back to the Portable Devices in Device Manager and right-click the BLU STUDIO 5.5 S or whatever phone you are working with that is listed there without the exclamation mark (listed under Portable Devices). Right click on the icon under Portable Devices, in this example the name that appears is BLU STUDIO 5.5 S. On that icon select Properties, Details, and under the pull down, select Hardware IDs and copy down what you see.
For BLU STUDIO 5.5 S I get:
USB\VID_0BB4&PID_0C02&REV_0216&MI_00
USB\VID_0BB4&PID_0C02&MI_00
(Note if you do this out of turn, the HW ID will be different with the phone USB debugging turned off. You want to copy the value that it changes to when the USB debugging is ON)
Now do as the instructions say above, of course customizing the lines you add the the INF file with those relating to your own phone, not the Nexus 10. Here is what to customize; when you downloaded the SDK you should have a file structure expanded from the ZIP such as this:
\adt-bundle-windows-x86_64-20140321\sdk\extras\google\usb_driver
Find the file named: android_winusb.inf in the usb_driver folder
Make a copy of it and name it anything, such as myname.inf
Edit the myname.inf and add the lines as instructed above only modified for your particular phone. For example, for the BLU STUDIO 5.5 S, I added the following 2 lines as instructed in the 2 locations as instructed.
;BLU STUDIO 5.5 S
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&REV_0216&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_00
Note that you add these lines to both the 32 and 64 bit sections, matching how the example in the tutorial reads.
Now go back up to the unknown device that appeared in Device Manager when you switched on device USB debugging and right click on this item (has yellow exclamation mark), right click on it and then select Update Driver Software, and then Browse My Computer, Let Me Pick, click on the Have Disk button and browse to find the myname.inf. Continue to agree to all the prompts warning you it might not be the right driver. As the final step, Windows should have identified the device as Android ADB Interface and once that is done, you should be able to go back, open your CMD window and run the command "adb devices" as instructed in this tutorial and now you should see that the phone is now discovered and communicating.
Now you can go have fun with the adb command.
At first Thanks #rmsyk's post.
For my issue and after long time suffering with Meizu C9 Pro witch require just android ADB drivers (no special drivers) referring to manufacturer and it solved in my Windows 7 PC by the bellow steps.
Make Sure to
Install latest version of ADB & Fastboot with the needed drivers.
Enable Developer options & USB Debugging.
Enable Media File Transfer (MTP Mode).
Manually replace C:\Users\USERNAME\.android with the folder included here ,Then kill process 'adb.exe' if found from Windows Task Manager and use adb devices and finally my device listed successfully and just confirm the PC as trusted.
Notes:
Android Studio was uninstalled in earlier time and also i tried to reinstall but was not a solution at all.
Tried adb kill-server & adb start-server but was not a solution too.
As well as the usual settings (enable USB debugging) I also had to select Enable OEM unlock in the Developer options.
This supposedly makes the device less secure, but it's your device and you know what you want to do.
Once checked the device behaved as expected and appears in the adb devices list.
You can always reverse all these settings once you're finished.
Confirm you have the correct platform SDK tools
For Windows 10, had to manually download the latest platform SDK tools from Android as the version supplied through Visual Studio 2017 EMDK for Xamarin was not sufficient. Everything else except adb.exe devices worked.
https://developer.android.com/studio/releases/platform-tools
After the platform tools were manually downloaded, device showed up regardless of USB configuration (charging, MTP, etc.)
Installing an emulator device at this stage is also helpful to see whether the problem is with adb or your physical device.
List of devices attached
12345D1234 device
emulator-5554 device
There could be two reasons why adb devices command is not working for you. Either your phones USB drivers are not installed properly or you have not enabled USB debugging mode.
I created a tool that makes installing USB drivers a one click thing.
Just connect your phone in USB debugging mode to PC.
Run my tool
It will detect and install drivers specific to your phone and also install the latest ADB & Fastboot binaries with it.
The tool is available at my GitHub Repo
It's so easy, just turn off your Android device, and then hold down both "Volume Down" key and "Power" at the same time. Wait a few seconds till it start in recovery mode, done.
Now type adb devices, and you'll see your device.
I had the same problem with my Windows 8. The Android/SDK USB driver was installed correctly, but I forgot to install the USB driver from my phone. After installing the phone USB driver ADB works fine.
I hope this will help.
Turn on debugging in the Nexus settings Developer menu (tap "About Tablet" 7 times to get that menu).
Freaking Google tricks!
Have you had an android update recently? I updated to Lollipop and all the sudden I had no adb devices. Boo! I spent awhile trying a few things to no avail. Then I went into my developer options and lo and behold, "USB debugging" had been turned off. Silly Google. After turning it back on, it immediately showed up and I'm back in business!
GoTo DeviceManager, then right click on the android device and click uninstall driver.
Unplug and plug the device back...then a pop will come on your device while your pc installs the required drivers. Click "allow" on the popup.
You can see your device when you type "adb devices" in command prompt.
For Windows, just end all the processes related to Blue stacks or any such emulator if you are using.
Worked for me.
There's obviously a ton of different problems that could be causing this (and a ton of different solutions to go along with those problems). So think about all the solutions!
If you've gotten this phone and computer pair to work together before, but they aren't working any more, it might be a specific program on your computer rather than a problem on your phone. Some programs install/use their own adb, and only one of these can connect to your phone at a time. I think this makes a race condition, so sometimes it'll connect fine.
Some programs that run adb:
HTC Sync Manager - uninstall this.
chrome://inspect - lets you view localhost on your phone. Just close the window when you're done with it.
To have ADB in MTP mode
If you don't find any ADB device (nothing with exclamation mark) in the device manager (with all developers settings on phone checked), do this:
In Device Manager :
UpdateDriver->Manuel Install->Search on my computer->Select from installed driver list -> then select the one with the word usb in it (not MTP).
Edit: after that, you'll then have 2 or 3 peripheral, one for USB and one for ADB, install adb driver using usual method (see first answers)
For my Nexus 6P downloading drivers from Google helped resolved the issue. Here is the URL with documentation. And here you can download the driver itself.
P.S. I saw some people advice to download some drivers from random places on internet. While this might help it's too dangerous in my mind to download unknown drivers from unofficial places. So the one from Google worked well for me :)
I am not able to resolve this simple issue.
I am trying to connect my device to Eclipse via USB cable.
On my PC, I have installed Eclipse and the Android SDK and running the program on the emulator is working fine.
I have downloaded and installed Samsung Kies on my PC. It shows my device if connected via USB to the PC.
But I dont know how to connect the device with the emulator.
Connect means, I want to run the Eclipse code on my device instead of emulator. I am using Samsung Galaxy Ace GT-S5830i. Please help me out to resolve this issue.
Comment is lack of formatting so i add an answer.
Check if your computer had your phone driver. I assume that your use Windows. Open Device Manager
At a command prompt, in the Start Search box, or in the Run box, type the following command: mmc devmgmt.msc
. Other ways : check link
If you find your phone name or ADB Interface so you got driver. Try to restart DDMS or restart your Eclipse.
If you don't find your device or see something Other device with yellow question mark so try to install driver by browsing on your phone to Settings - Developer Options - Enable developer option - Enable USB debugging - Plug your phone to computer. Windows will ask you to install driver.
3, Update Google USB driver in Android SDK Manager (in Eclipse) or search Samsung Galaxy Ace GT-S5830i driver
4.Some weird case i got on some device.
Nexus S: disable Developer option. Restart phone. Enable again. Windows ask to install driver or you will see it in Eclipse.
HTC phone or Samsung : change Connectivity Option on phone to Charge only (Swipe status bar. Check notifications displayed). Some phone set it to some kind of Sync data so Windows can not recognize device.
I think your emulator is in Automatic. You can change that to Manual.
Try this,
Step 1
Go to Run Configuration
You can see three Columns Android,Target and Common.
Step2
Select the Target
Step 3
Choose Always prompt to pick device.Click Ok
Step 4
Now run your project you should see the emulator and your device. Select your device and click ok.
Hope it helps.
Source.
Troubleshooting
This all sounds very straightforward, but there are countless quirks and hard-to-diagnose problems that can make connecting a device much more difficult than it sounds. In this section, we'll run through a checklist of things to try when your device isn't registering.
Check that USB Debugging is enabled. This setting can inadvertently (and perhaps even automatically) change when you plug/unplug your device from your machine, or when you reboot your phone.
Check your device while it's connected to your machine. Is it asking you to choose between different modes? Some phones have a 'charge only' mode that can prevent Eclipse from recognizing the device.
Choose a connection type
Make sure you don't have an Android Virtual Device running in the background.
Could there be a problem with the USB cable? If you have a spare cable to hand, plug it in to rule out a fault with the cable itself.
Double-check you're running the correct driver. Even if you are, some devices have all the required software pre-installed (for example, HTC Sync) and downloading drivers from another location can muddy the waters. If this might be the case with your device, try uninstalling the driver from your machine and reinstalling the software from your device's memory.
Does the driver require supporting software? Samsung Kies on Windows requires .Net Framework 3.5 SP1 or above, for example. This is usually installed along with the driver, but there's no guarantee.
Running the Android Debug Monitor tool (monitor.bat) has been known to kickstart Eclipse into recognizing a new device. Connect your device, locate monitor.bat (android-sdks/tools/monitor.bat) and double-click to open. This will open the Android Debug Monitor, a stand-alone debugging tool that lists connected devices.
Android Debug Monitor
A running adb.exe process can interfere with the connection. Close Eclipse, and open the Task Manager by pressing CTRL, Shift and Esc. Find the adb.exe process and kill it. Launch Eclipse and try again.
Check that your 'Project Build Target' is compatible with the Android version on your device. You can check what version of Android your device is running by opening 'Settings' and selecting 'About Phone,' followed by the 'Software information' option if available. If you need a reminder of your project's build target, ensure the project is selected in Eclipse's 'Package Explorer,' open the 'Project' menu and select 'Properties.' If the 'Android' tab isn't selected by default, open it and the Build Target will be displayed.
Have you enabled USB debugging in your device?? You can find it in your device
Settings -> Developer Options -> USB Debugging.
The android app you have created will be a .apk file, generated by eclipse, during a successful Run. Find the .apk file from the eclipse project explorer or by tracing your workspace. Copy the .apk file to your memory card (via USB or a card reader) and install it.
You should also enable the "Unknown Sources" option under "Security" of your Android device.
If you have required options enabled on your phone (USB Debugging and Unknown Sources) you can try do this. On your computer open command console. Using cd navigate to your android sdk installation folder. Go to platform-tools. You should have there adb file. Run this
./adb kill-server
and then
./adb start-server
Then check plugged devices
./adb devices
First, you are not connecting device with emulator. What you want is eclipse to identify your device and use it for development.
Everything about using devices for android development is given in official documentation.
You have to put the phone in 'debug' mode - I don't have the instructions handy (but you can search here or on the android site for the info you need).
Also check for THIS.
Try right clicking the project -->Run As --> Run Configurations then select target and choose always prompt
On your device turn on debug mode
Now try running project
I am assuming you don't mean connecting the device with the emulator but connecting the device to your computer so you can debug it and run applications directly from Eclipse to the device. In which case KIES by Samsung will not help you at all. What you need is the Android USB Drivers provided in the Extras tab in SDK. Sometimes the installation will bug up because you didn't run SDK manager as an administrator so make sure you do that. When all of this is done make sure your device is unconnected to your computer and then reconnect it after the drivers are installed. You should be prompted with a new device installation wizard which you must accept. Additionally, you should have debugging enabled on your device, and as an extra step you can setup launching as a manual configuration but it is not needed.
To enable device debugging
Settings -> Developer Options -> USB Debugging.
For more information visit here
BTW : If the Google USB Drivers don't work you might need to install the specific Samsung drivers which are located here
Goto -> Setting -> Application -> Development -> USB Debugging
Enable it and try.
I know this is a little old, but I was having the same issue. I tried all the options of setting usb debugging (off), disconnecting, restarting phone, usb debugging (on), connecting the phone and it just wouldn't connect.
I ended up installing the latest version of Kies on my machine and added the Unified option at the end of the installer and I then the phone would connect. (Not sure i needed the unified option) but it worked for me.
I tried all the above but it didn't helped me. I did couple of things additionally
Since my mobile device is Android, I unchecked Unified option from Kies installer. This is the crucial thing that helped me solve my problem
I restarted my mobile phone.