Problem:
My smartphone model (Lenovo Vibe B) doesn't have a official driver listed in the OEM USB Driver List (it has for Vibe C and other, I've tried the one for C, because phones are kind of similar but didn't work), so I can't use it in Android Studio to test my apps.
What I've tried
So my ADB is not recognized or, when I installed an ADB that was found on Device Manager, I got the error Code 10. Updated the drivers, reinstalled all USB drivers, ADB drivers, tried different software like LeTools, LenovoSmartAssistant, MagicPlus, something in chinese, an universal ADB from a developer named Koushik.
Tried different youtube tutorials... also read articles and tried them:android won't connect, installing adb driver - lenovo, how to fix code error 10
Also checked official documentation from Google,switched from MTP to PTP** and back to MTP,tried even MIDI
Still my device isn't visible in Android Studio and in Device Manacer is marked with an exclamation sign, or now it's not visible at all.
I mention that I also accept a solution in which I can install my app created on Android studio on the phone and test it without Android Studio. I need to do that because I'll work on an app that requires to be tested few month's, in order to have a database to predict a future behaviour.
Thank you in advance for your help provided!
For Android Development using the real device you need a tool called Wondershare MobileGo. Its a pcsuit app for Android and ios.
I am using it for 2 years and its the only final solution for all ADB related issues.It contains all type of ADB drivers of android devices currently on market.
You only have to use it once to get the ADB driver installed according to your device model and you can remove it from your pc after that.
I have an LG G4 and would like to use it for debugging apps during development. However, I cannot get the device to show up.
I have followed the steps to set the phone into debugging mode.
I have Android Studio and used SDK manager to download the latest SDKs and tools and also installed the Google USB driver.
I cannot see my phone in chrome://inspect nor does it list with "adb devices" nor does it show up in Android Studio.
Sorry that this answer isn't more clear for anyone who stumbles across it, but I wasn't able to pinpoint what fixed it.
I was never able to use the Google USB Driver (so technically, the question isn't really answered)
I was able to install the drivers from LG, but was not able to assign the driver to my device in Device Manager
However, my LG G4 is now working in both Android Studio and chrome://inspect.
The unclear part is that what I did was continuously update Android Studio and throw in a few system restarts. Some items had updates appear after installation which I processed. I also added a few more full SDKs (started with only the latest, 24* at the time of this writing and went back to 21*) At some point during this process, my phone began to work.
I suspect there was a tool or SDK that did the trick and possibly didn't actually fix the issue until I restarted the computer.
If you already used any other android devices for debugging, then the ADB driver is ready to be used for your LG G4. Try following steps.
Connect phone using USB cable
Open device manager >> right click on unidentified LG G4 >> Update Driver Software >> Browse my computer for driver software >> Let me pick from a list of device drivers on my computer >> Install an ADB driver from the list (install anyway)
You need install LG Drivers for your G4. Go to http://www.lg.com/us/support and find yours.
EDIT:
Sometimes it doesn't work in Windows 8 and 10, so you need LG PC Suite.
I am using the latest version of Android Studio(2.1.2) at the time of writing this post . The problem that I am experiencing is that the ADB instance used by Android Studio doesn't seem to be able to find my Galaxy Core Prime device (SM-G361F, stock Android version - 5.1.1). It can connect to an emulator just fine.
What I had tried (most of these multiple times):
enabling/disabling developer options
enabling/disabling USB debugging
revoking USB debugging authorization
changing MTP to PTP and vice versa (my device doesn't allow deselecting both options, one must be chosen)
reinstalling the drivers
powering on and off both the phone and the PC
installing Samsung's Smart Switch software
using different USB ports
trying out different Android Studio versions (x86 and x64 with the latest respective JDKs)
This is what it looks like in Android Studio:
I had installed the official Samsung's USB drivers from here.
This is what the Device Manager is showing (Windows 7 64-bit SP1):
Afterwards, I've also tried installing the Universal USB drivers from here.
This is what firing up its installation of ADB looks like:
It has obviously successfully found the device.
My device also politely prompted me to allow the PC to connect to it using a generated RSA key which never happened with Android Studio.
The only thing I've not tried is installing Samsung's Kies software.
I really don't know what is the problem here.
Maybe I should just give up and instead use the emulator but it is a damn shame not to be able to debug on an actual physical device, if you ask me.
Thank you in advance.
Android in general does not support all phones for a debug connection. I have a samsung s6 and for me that works. I don't know about the Core Prime though. However, in most cases(in my experience):
The phone does not support the connection
You did not install all the required files in terms of the android SDK you might have not gotten the latest update that supports more phones
The OS is not supported - Mainly caused because Samsung and a lot of other brands insist on having their own updates. And some times they - on purpose or by accident - forget to support USB debugging for developers.
My tablet did not support the USB debugging connection untill it reached android 6.
The cable is a charge-only cable (yes, those exist for some reason). Try with a different cable
You don't have the necessary drivers. Make sure they're installed
It might be circumstantial that your phone model does not support the connection for some reason, but it is really hard to tell. The only way to get proper help is to contact Samsung customer support, but in my experience it is just a waste of time. They don't know their own products. If you try with another device it might work.
After some continued tinkering I managed to get Android Studio to recognize my device. All I did was adding the path to the ClockworkMod's ADB .exe to the PATH environment variable. That seems to have done the trick as Android Studio now allows me to run the application on my device even though it is still running its own instance of ADB (located in the platform-tools folder).
It might be completely unrelated but I'm not considering undoing the modification made to the environment variable.
Here is the proof:
This is not a duplicate post. I have searched and read extensively and none of the solutions I've come across have been successful.
Win 7 64 bit
LG Spectrum II running build VS93022A (Android 4.1.2)
Eclipse version...from the SDK as downloaded on 09/07/13...so, the latest
I did install the actual vendor drivers for my device, not just using the default from Windows that kick in when you first connect it. I can view the device and SD card contents via windows explorer. It is by any criteria clearly and correctly connected to my computer.
Allow USB debugging is checked on the device. The USB connection mode is "Media sync (MTP)".
Used "adb devices" from command line and it lists no devices.
Restarted everything multiple times.
The selected minimum Android version for the project is Gingerbread. My device, as stated above, is running the absolute most recent Android build available (updated itself two nights ago, actually).
The device still does not show up. Any ideas?
edit: The advice found here:
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
cannot be follow because it is incorrect. In Device Manager, there is no entry under Portable Devices (where my phone appears) which reads "Android Composite ADB Interface."
On a side note, is all of the Android developer documentation this terrible?
I had the same problem with my device. To solve it I plugged it in with usb debugging unchecked then checked it. A notification came up on the phone saying "allow this computers RSA?" or something similar and then it worked.
Something I just came across after I had installed iTunes on my PC (previously I was able to debug over USB, then it stopped working). Go to Services and stop "Apple Mobile Device Service" as it interferes with the USB for Android debugging.
I have tried connecting the USB debugger on Samsung Galaxy S2 and Samsung Galaxy Nexus. It still manages to fail on both devices. At the moment I am using Windows XP and I am running out of ideas.
Here is what I tried:
Installed SAMSUNG_USB_DRIVER_FOR_MOBILE_PHONES_1.4.8.0.exe
Searched and tried to install the drivers on Google drives.
Has anyone have this similar problem and could share a solution?
EDIT* Both devices Samsung Galaxy S2 and Samsung Galaxy Nexus are able to connect to the PC but not to the debugger. Drivers installed with different variances even done installing Samsung Kias.
I am adding a bounty tomorrow for 50 reps. I really need to test what I am doing on an actual phone.
You need to download Samsung Kies I know that the software description doesn't mention that it is the correct drivers for developers, but it in fact is.
An old issue used to be:
Use the USB2.0 ports on the back of the PC not the 1.0 front facing port.
I feel you have not installed sdk properly. Reinstall the http://dl.google.com/android/installer_r18-windows.exe, the open the adb and update all the things for the particular sdk you want.
Then verify that you have given the exact location of sdk in eclipse>window>preferences>android
Then restart eclipse.
Even you cant open it then set environment variables. For that add following ;E:\android-sdk-window\platform-tools; in PATH. Then restart windows.
After that try adb devices, adb kill-server command in Command prompt.
You will be able to see your device.
Is there any "ADB interface" devices in your PC's Devices Manager?
If you are using DDMS,Maybe there is a console(cmd.exe) window behind DDMS,you can get some log there.
Did you enable the debug mode on your device? This is not listed in the steps you followed.
Go to Settings -> Applications -> Development -> and set USB debugging.
You can use PdaNet software to connect your device for debugging. I was have the same issue and resolve with using this software. Use the following link to download this software:
http://junefabrics.com/android/download.php
I also have samsung Galaxy SII and i face the Same Problem before some days. But now i am able to get debug the app in My SII.
Please follow the steps and make sure that you follow it completely then only you cna able to get debug in your phone.
First select the Option to Install App from Unknown Sources.
You will find that option in Setting -> Applicatios -> Unknown sources. Select it as yes.
then Select the Option like USB Debugging.
You will find that option in Setting -> Development -> USB debugging. Select it as yes.
Now, Install latest Samsung Kias In your PC. Reboot Your PC, Eclipse and may be Phone also
Now, Try with connecting the Device.
Hope you will get debugging your app in to your phone.
If not then let me know which trouble you get.
Enjoy. :)
My phone has this:
Settings -> SD card & phone storage -> Mass storage only (USB connection mode is mass storage only)
Make sure that this option is NOT checked. If it is u can enable USB debugging and unknown sources and it still wont work.
If you just need to connect to the device for install and debugging you can manually select the driver to use when you plug it in.
Don't let windows search for it, choose I will pick the driver from a list, then select android composite ADB interface. It may warn you that this driver doesn't match, but it works!
I also had many problems to get samsumg galaxy S2 work on my pc. If I remember correctly finally I ended up installing Samsung Kias and installed some drivers through there. Then restarted the computer and never launched kias from then on. My phone is still not visible form command line adb devices, but now I can develop in Eclipse and deploy on the device without any problems.
From time to time I lose connection to the device (E.g. if another device was plugged in). Then I need to restart Eclipse and my device becomes visible again.
Some friends of mine also shared that some other mobile device usb drivers were conflicting with the samsung drivers (it was ZTE if I am not wrong). They uninstalled the ZTE drivers and then got the Samsuung running ok too. Try consider uninstalling all other usb drivers before you try the Galaxy S2.
Have you installed exactly the right SDK version for the phone you're using?
Given that you can access the phone on the PC via KIES, I assume that you have all the correct USB drivers installed.
Ensure that debugging is enabled on your phone. This can be done from the Settings preferences.
Install the Android SDK. Add %ANDROID SDK_INSTALL_PATH%/platform-tools to your path.
If everything is working up to this point, plug in your phone and execute the following from the command line.
adb devices
and you should see your device listed.
Install the Android Developer Tools plugin in Eclipse.
Create/Import your project.
Right click your project and from the context menu, select Debug As --> Android Application
I have had exactly the same problem as you, I even gave up on developing for 2 months because of this. I have just started again and really needed to get this working.
I tried all of the above and pretty much every combination of the above and still failed.
I have just got it working by not doing anything different apart from when I uninstall the old USB driver (add remove progs), the next time I installed AGAIN, I used the SAMSUNG USB Driver for Mobile Phones V1.3.450.0 (an older version than ones suggested on other help forums, I just got it by accident somewhere and thought I'd try it). The next time I plugged the phone in, it did all the usual finding CDC etc. that it always did when it failed...but then.... it asked for the ADB Driver, WOW! I got excited. I just selected Install Automatically and away it went.
I still already had the PDANet thing running and that popped up saying a connection is available. I've not used it though because it wouldn't install on my phone anyway.
FYI, I have these settings on the phone:
USB debugging ON (obviously)
Allow Mock Locations OFF
Unknown Sources ON
I hope this helps.
Dan.
This may not help at all since you have probably tried it already but I had huge issues on two different windows 7 machines getting my s2 to connect for debugging.
I ended up getting one working by plugging in the s2 USB connection, un-installing the drivers for it in the device manager, unplugging the USB connection, un-installing Kies, downloading the most up to date version of Kies, installing that and plugging it back in.
The other one was even more painful, it was a while ago now but I did the same as the above but removed eclipse and the Android SDK as well, installed the latest version of Kies first, the eclipse, then the sdk and made sure all of that was done before I plugged the phone in.
I faced same issue which you faced..
I solved this by this way.
1) Right click on my computer and select Manage
2) Then select Device manager..
3) connect your phone (galaxy s2 in my case)
4) I found one device with named "unknown" in sub option I foung my phone name i9100
5) Then right click on that and select update driver software
6) you will see then this..
Tadaa....Done :)
Hope this will help you also..