This is the SAMSUNG Android USB Device Driver version 5.28.2.1. See the instructions for this driver for the Samsung mobile phone listed below with the file. Note that this file is for a Windows operating system.
Latest download for USB Modem Phone ADB Port driver. Improve your pc peformance with this new update.
This software provides the all the installation files for the SAMSUNG Android USB Device this being the last driver released being version 5.28.2.1. In order to update your driver, follow the steps below (the next step):
1. Go to Device Manager (right click on My Computer, choose Manage and then find Device Manager in the left panel)
2. Right click on the hardware device you wish to update and choose Update Driver Software
3. Choose to select the location of the new driver manually and browse to the folder where you downloaded the driver
SAMSUNG Android USB Device Driver (5.28.2.1)
(Bus driver, modem driver, DM port driver, ADB driver, RNDIS driver)
SAMSUNG Android ADB Interface Driver (2.11.5.0)
(SAMSUNG Mobile USB Connectivity Device)
SAMSUNG Android USB Driver for Windows (25.32MB)
(Windows Driver for Samsung Android)
SAMSUNG Android USB Device Driver
(UPDATE: FEBRUARY 2015)
UPDATE : March 2016
Samsung Android USB Driver for Mobile Phones 1.5.59.0
VN:F [1.9.22_1171]
VN:F [1.9.22_1171]
SAMSUNG Android USB Device Driver ¸¸.•*¨*•, 7.2 out of 10 based on 674 ratings Incoming Search Terms:
Related Posts
- Samsung QL6100 USB Port driver (1.000)
- Samsung ML4600 USB driver (1.000)
- Samsung SFD-321U/EP USB Driver (1.000)
- Samsung Galaxy S USB Driver (32 bit) 1.3.450.0 (1.000)
- Samsung Galaxy S USB Driver (64 bit) 1.3.450.0 64 bit (1.000)
Sometimes Android USB devices won’t connect to a Windows system. For attempts at connecting via the Android Debug Bridge (ADB), bad Android USB drivers that load in place of the right ones often cause the issue — and users can’t uninstall these drivers using conventional means. Removing the offending drivers and installing “universal” ADB drivers should fix this problem.
If you can’t connect an Android device to your computer — and you’ve already enabled “USB Debugging” (what’s USB debugging?What Is USB Debugging Mode on Android? Here's How to Enable ItWhat Is USB Debugging Mode on Android? Here's How to Enable ItNeed to allow USB Debugging on your Android? We explain how to use debugging mode for pushing commands from your PC to your phone.Read More) — then this is the method for you. When turned on, USB debugging allows users direct access to the file system of an Android device from a PC. Without debugging enabled, users can only interact with their phone’s media storage, such as the SD card.
Here’s a short tutorial on ADB:
Note: You must enable ADB on your Android device for this tutorial to work. Here’s a video on how to do that:
Overview
Fixing the problem takes about five minutes and three basic steps:
- Connect your Android device via USB and remove the ADB drivers. Then disconnect your device.
- Run a USB driver eliminating utility and kill all your superfluous Android drivers;
- Install Koush’s Universal ADB Driver.
Step One: Connect Device
First, connect your Android device via USB to your computer. This step allows your device to display in Window’s Device Manager. Fire up Windows Device Manager next. I usually type “device manager” into the Search utility.
Second, open Device Manager and remove your currently displayed Android ADB driver. Simply right click on the ADB driver to bring up the context menu – select Uninstall.
Make sure to check the box for Remove Driver.
Now you can disconnect your Android device from your PC.
Note: This prevents the same incompatible driver from loading upon reconnecting the Android device. This step is technically not required, but it will show you the driver causing the issue, in case it somehow reloads itself.
Step Two: Kill Bad Drivers
First, unzip Nirsoft’s USB Devices View utility (USBDeview). Next, locate the unzipped folder and run the utility (no install required). Nirsoft’s utility displays the total number of installed USB drivers on your computer.
Take a look at the colored status indicator on the far-left of the USBDeview window. Green indicates that the device functions properly. Pink means the device can unplug and works properly (although it may not actually work properly). Red indicates a disabled USB device. Gray (circled, below) means the device is installed, but not connected.
Second, remove all gray items with the words “Google”, “Linux”, “ADB”, or “Android” in the title. I always remove every item that’s not green, but be warned: Your experiences may differ. You may end up needing to reinstall devices by removing them here.
Note: The Nirsoft utility may show up as malware in a virus scan. It most assuredly is not.
Step Three: Install Universal Driver
Koush’s Universal ADB Driver (see link above) works for every Android device, no matter how exotic. You will need to perform a manual installation in order for Koush’s driver to work.
First, download the Universal ADB Driver then run the executable package, which installs the driver.
Adb Port Forwarding
Second, plug your Android device into your PC via USB. The correct ADB drivers should load. You can check by going to Device Manager in Windows.
Third, if the install process fails, you can manually update drivers. After connecting your device, go into Device Manager, locate the ADB/USB drivers, and right-click on them. In the context menu, choose “Update Driver”. Keep in mind two things: First, sometimes you need to check the notifications tray on your device for additional steps. Second, sometimes Android devices show up in strange places inside of Device Manager. You may need to check every single device class (such as “Android Phone” or “Samsung”) in device manager.
You’ll receive two options — choose “Manually Install Driver”. Next, choose “Browse my computer for driver software” and choose “Let me pick from a list of device drivers on my computer.”
Then choose “Let me pick from a list of device drivers on my computer.” You will see a list of drivers. Choose one of these. If it fails, repeat the process and locate another driver that works.
It looks like this:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Universally Good
Descargar Usb Modem Phone Adb Port Fastboot
This method of purging bad Android USB drivers and installing Koush’s drivers works for every Android device I’ve tried it on. It’s ridiculous that Google never released a universal ADB driver for Android devices, despite the issues that many users continue to experience. While some wireless solutions exist, such as AirDroid, I’ve found this method more reliable.
And for a more powerful Android device, check out these Android ADB apps to get cool features without root6 Android ADB Apps for Powerful Features Without Root6 Android ADB Apps for Powerful Features Without RootWant to get more control over your Android device? Try these apps that let you use ADB functionality without rooting.Read More.
While you’re at it, learn how to keep all your drivers up to dateHow to Find & Replace Outdated Windows DriversHow to Find & Replace Outdated Windows DriversYour drivers might be outdated and need updating, but how are you to know? Here's what you need to know and how to go about it.Read More, not just the ones related to Android!
Cable Modem With Usb Port
Explore more about: Android Rooting, Windows 8.
- I have a G4 H811 (tmo) and have tried a variety of drivers discussed here, on different computers, but ADB always shows my phone and says 'offline'
I do have USB debugging on and OEM unlock checked. it shows debugging in the notification bar but I never get to the place where on my phone I have to allow the computer RSA code to access my phone. only get 'allow USB connection'.any help?- Hey Bryan, the comment below yours mentions probably the first step everyone should take: IMMEDIATELY after connecting your smartphone to your computer via USB, check the smartphone's notifications tray to see if there's a prompt to connect through 'transfer data' (not all phones offer this option because sometimes it's mislabeled as another connection option).That should actually be the first thing that everyone does, because very few phones actually automatically connect unless this basic step is taken.
- (I tried replying before but don't see my reply, so forgive me if I am making a double post.)
I tried your suggestion but the only prompt I ever get is 'allow USB connection'. I have tried not allowing, to see if it tries the RSA prompt but no luck. I have tried allowing USB connection and selecting each option (charge only, MTP,PTP,midi), no luck. I have tried turning off USB debugging and back on again, no luck.
it always shows the device ID in 'ADB devices' but says 'offline'.
I think it is some simple problem with the phone, not windows drivers/software. I have tried several different ADB composite drivers and USB device drivers.
I have much experience with G3 rooting, downgrading, TWRP... but this G4 is really frustrating me!
I need to first unlock the bootloader (which is supposed to be simple on the tmo h811), then install TWRP, then supersu. but can't even get to 1st base with the boot loader without ADB access.
I'll appreciate any other suggestions. it MUST be some simple phone setting somewhere!- Kannon there was no repy button on your last post, so this may be out of order.
- I am using Minimal ADB and Fastboot
- I have tried 2 different LG ADB drivers (2014 and 2016 dates) and 3 clockworkmod drivers (android ADB interface, android composite ADB interface and LG android interface). all have the same results- device ID and device offline.
- I rebooted my PC after each driver change.
I must ask: if the windows driver was the problem, would it show my device ID? it seems to see the phone fine but the phone seems to be rejecting access.
on the phone I have USB debugging on, and OEM unlock bootloader checked.
I have tried turning USB debugging off and back on, rebooting my phone.
I am near giving up. if we find the solution, i'm sure it will surprisingly simple. but I am becoming doubtful about finding it. (as I also mentioned, I have tried on 3 different (windows 7) PC's.
thanks for all your attention to this!!
- If your having issues, you should seriously try connecting to CHARGE ONLY first, that made the driver install work for me.
Kinda annoying me ever troubleshoot guide I go to for an issue wants you to install a program without throwing in some simple suggestions that may work first.- Thanks for this, it enabled the Universal driver installation (finally!)
- First, thanks for the explanations and answers. Concerning connecting Android phones to Windows PCs, even after reading your explanation (and many others) I still have a fundamental question, specially including the universal ADB driver -- but let me state it as an operational one:When connecting an Android phone (in my case, 3 different Samsung Galaxy models) to a Windows PC FOR THE FIRST EVER TIME, are these the correct steps?
1) Don't check anything on the PC (it's a just-installed system, with no previous phone connection);
2) Install the Koush Universal ADB driver;
3) Install Samsung's drivers using their 'Samsung USB Drivers For Mobile Phones.exe (1.5.51.0)';
4) Switch on 'USB Debugging' on the phone;
5) Connect the phone to the PC using a USB cable (for connection, not charging only);
6) Depending on the phone model, the connection mode/protocol may have to be defined now (because newer models seem to only allow this definition when USB is actually connected), but what should it be: MTP? PTP? Kies?
7) The PC should 'find' the new device(s) and install appropriate drivers (but, which ones should be pointed to: the Koush ADB or the Samsung drivers)?I'll be reinstalling this system (to get rid of several accumulated problems), so the above WILL be true; it's a dual-boot XP Pro SP3 / Win 7 Ultimate system, so I'm sure there is no 'physical' problem with the USB cable, since the same one is used, on the same USB port (non-hub) on both XP & 7 -- but, currently, I'm able to connect the phones on both systems, with different degrees of 'precariousness', but on XP the MyPhoneExplorer app works fine, and on W7 not, so I hope to get this sorted out.As the basis for my doubts, is the whole 'device management' idea, here: The 'devices' involved seem to include 'Samsung Android phones' with 'Samsung Android ADB interfaces', 'mobile USB serial ports', 'Android UMS composite USB devices', 'ADB interfaces' with 'Samsung Android composite ADB interfaces', 'Samsung Android USB Modems', 'Samsung mobile Modems' and 'Samsung mobile USB Modems', and many others (probably, many of them as a result of several reinstalls over time)... My main doubt is: Conceptually, what could/should be the 'devices' involved (or by what names should they appear)?Hopefully, if the installation order I've listed above is correct, I should be rid of these problems on reinstall -- but, since I remember having many problems with this over time, I'd appreciate to hear your opinions on this -- and, again, thanks for your site and attention. - I have tried everything, including your proposal, to get adb to 'see' my LG Stylo 2 Plus (K535T) running Android 7.0 in recovery mode to no avail. If I just plug the device to my Windows 10 and I typeadb devicesthe device is listed.
But if I now reboot into recovery mode, that's it: ADB would no longer see it, but fastboot does. That is,adb devicesdoes not list any device, butfastboot deviceslists the device.I would appreciate any help.- same with me here please anyone help
- anyway, have you found a way to fix it?
- I was actually at CES this year in Vegas and had the chance to check out a ton of awesome producs, I'm super excited about Samsung new 2017 tablets I'm always up on all the newest hottest tech stuff that is coming out! Thanks for the read and the comment! I look forward to your next article.{Samsung
- Thanks a Ton man, I'd been trying to solve this issue since past 10 days, but your compilation just solved the issue within seconds,
Thanks - Hi! I've just switched from my old Samsung Galacy Trend Plus to a new Lenovo Vibe B... Unfortunately I've tried many solutions, including yours, and installing different Lenovo official apps like LeTools (which i really didn't figured out if it really does something) LenovoServiceBridge, and some strange assistant in chinese. No result at all! I really need to activate ADB in order to check my apps from Android Studio on a real phone. (I intend to do the project to finish university in Android too) Do you have any other solution for this? At least for installing an app created by me on the phone?
- I have further refined some of the steps in this tutorial. I'll try to edit them in right now. Can I ask what happens when you go into Device Manager and change the drivers associated with your device? What kind of drivers do you see available?
- I'm sorry about that. There are a few things that I didn't mention in the article. First, you must have ADB enabled on your device before any of these steps will work. But the title was 'ADB not working' so I assumed everyone have already enabled ADB. (I'm pretty sure you have enabled this.)Second, if you manually change drivers, it would be helpful to know what kind of driver options showed up. If I have read the specs correctly, your phone should use MT6735M ADB drivers: http://adbdriver.com/downloads/But before you install those, please let me know what kind of driver options show up when you manually try to change drivers.
- THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!! I was googling like crazy for hours trying to find a solution to this problem. Yours is the ONLY one that worked!!
- On Windows 10, a doogee X5Max (Android 6) can be accessed by USB, with a lot of hammering between charging and MTP. So far, Nexus 5X (Android 7) doesn't work. Nothing wrong with the cable, as ADB and Fastboot were used to flash the standard images. It's a dumb Windows and dumb Google thing.
- On my Windows 10 PC I don't have the checkbox to delete the driver software for this device. Windows insists that the Windows driver is the correct driver
- I am getting so pissed off at this that I am seriously about ready to go all Office Space on the damn thing.I have a Note 4, have been able to view and transfer files up until a couple hours ago. No new updates, no new anything. All of a sudden, either the files/folders simply do not appear in Windows 10 File Explorer, or only some of the do, or I get weird icons that look like a hard drive with a blue four-square Windows logo. And no matter how it displays, I can't get to the files I used to be able to get to.The steps above do not work. At all. I've done everything, from every site I could find, and not a goddamn thing has worked.I hate hate hate hate hate hate hate this piece of shit!!!
- I am Desperatly trying to Install this driver BUT Win 7 64bit sias it cannot install as its not 64bit driver, I can only see MTP and WPD drivers even if I un-select Compatible Drives, with the Microsoft / LGE driver dominant , I have a LG G3 Device AKA LG-D855 with Android 5 L 21 In Debug mode.The Android SDK Driver also sais 'It is Not Compatible' Like the Koush’s Universal ADB Driver, does the same with a Qualcomm MSM8974AC Snapdragon 801 Chipset.
- Hi,Tried to follow the steps to the letter but my W10 keeps installing the regular Samsung Mobile Composite Device driver automatically (no unidentified device)Any idea what am I missing?ThanksEyal
- Thanks! This finally solved my problem... I had a ton of ADB drivers/Samsung Drivers, etc loaded that must have been conflicting with each other and this article finally solved my issue with connecting my S7 Edge with the Universal ADB Driver.
- I've gone round and round with this for two days trying different drivers for my Kycera HydroAir C6745Nothing works, even the drivers off of Kyocera's site, although they don't list that particular phone all the packages seem to be the same for similar phones.My cable is good... If i choose to connect as a media device I can transfer files between my PC an the phone and other phones at will. I'm trying to use a particular program 'MyPhoneExplorer' and it actually works via WIFI so the program doesn't seem to be the issue. When connecting via USB I get a 'no USB device connected' error message on this program only.I have debugging enabled in the developer options and have restarted both the phone and the computer multiple times after making changes, uninstalling/reinstalling different drivers (when they will actually install) etc.Koush's universal driver will not complete installation... I get an error that a program couldn't complete and the installer backs out. I found an earlier version of the same .msi package that is about half the size and it installs but doesn't work.Attempting to install the drivers from the GitHuh master package manually gives 'this driver doesn't apply to your device' (or words to that effect) no matter which option I choose.I have used USBDeview multiple times to uninstall any drivers that look remotely like Android as you describe, even those that install every time I connect the phone via USB.Many of the drivers I've tried look to be the same as the one in the master package on GitHub (from the link given) and again, that particular .msi installation will not complete, although a couple of other supposed universal packages.installers have completed with no help.I'm running the latest XP and service pack and have experience with these kinds of issues, installing drivers, troubleshooting software installation and issues, etc.... although android is fairly new to me I have SOME experience there as well.I do have the Android SDK installed and saw something about a driver there and am about to locate that one but I expect it will not work either and that I'm doing something else wrong or am missing a basic step somewhere, although I've rechecked every step multiple times.... as is generally the case when I have this much trouble and make this much effort in a mostly continuous session.I'm stumped.
- Hi,When i connect my Lenovo A6000 to laptop with windows 10 it is showing exclamation mark in device manager under Other Devices. But it is working fine when i connect to laptop with windows 7.
Same cable, same mobile.
From cmd when i run >adb devices it is not listing the devices.Please let me know what needs to be done.Thanks in advance. - here just a hardware id of android is to be place on android .inf file thats it..
- Yes i installed koush's universal adb driver and i restarted my pc after that i connected my phone via usb and opened device manager and i saw a exclamation marked device under other devices named as adb interface then i selected update driver
1st i selected for windows to automatically search for drivers it said windows did not find a driver for your hardware
2nd attempt i selected let me pick a device driver from the list but not a single one worked
3rd attempt i selected the directory c:program files (x86)/clockworkmod/universal adb driver it said windows did not find a driver for your hardware
4th attempt i selected the directory c: only instead of the full path it said windows found the driver named adb composit device driver but encountered a problem while updating the driver it said that file not specified
My phone specs
Brand lava
Model iris alfa l
Hardware media tek mt 6582
Kernel architecture armv7I
Android 5.0
My pc win 8.1 x64
Still looking forward for ur help - When i try to install the driver manually it says Windows found the driver but encountered a problem while updating the driver. My kind request for help and a reply ASAP
- Windows says it can't find the driver, even after installing Universal ADB and pointing it to the right directory.
- THE REAL QUESTION IS WHY WE ARE RUNNING WINDOWS, WITH LINUX ALL YOU NEED IS A USB CABLE, NO STUPID DRIVERS
- Every single OS need drivers to manage peripherals...
- Windows 10 + Xiomi Redmi Note 2 - unsuccessfull.
- One plus one and Windows 10.. this method doesnt seem to work.
- Thank you very much, works with HTC phone in WIndows 10
:) - After fighting with win 10 and trying to install the marshmallow ota update, I took your advice and installed Koushs universal usb.
I finally got it installed and it's booting up now.
Thank you so much
Howard - Well it seems this method doesn't work on Sony Xperia M4 Aqua (android 5.0) and using PC with Windows 10.My smartphone shows up in device manager under 'Portable Devices' as 'Xperia M4 Aqua'.
I uninstalled drivers, deleted entries with usb deview, but when I plug in my device PC automatically installs drivers.
I disabled automatic driver installation from Windows Update, but that seems doesn't help as it still installs drivers.
P.S. And by the way - in the first step when 'Confirm Device Uninstall' dialog box appears I don't have an option to check 'Delete the driver software for this device'.- P.S. Also it doesn't really install drivers by force when browsing manually. It just shows up that my drivers are up to date.
- My Samsung I8552 was debugged well on Windows 7 using OEM USB driver from Samsung. On Windows 10, I try many things with no success included your instructions :(
- Thank you! Worked perfectly, where as every QBKing77 video that I've used in the past before moving to Windows 10 no longer proved effective, and with all the 'Download this, download that.'That universal driver and manual installation FINALLY got my cmd to see my adb device sideload.THANK. YOU.
- Wow thanks. I was a bit sceptic but it worked like a charm!
- i downloaded asus driver asus android adb interface but i am getting exclamation mark on android adb interface and it says device cannot start code 10 error please help me
- Hey kannon , I did all the steps( not the 1st one for following reason) but after removing all other drivers as instructed and installing the universal adb driver no drivers are loading automatically installing when I plug in usb. Moreover I cannot even update it manually from device manager because there is no device or android phone or LG option or any adb option to select. What do I do now? See the image as to know what it looks like http://postimg.org/image/i7jmwdhiz/
- I cannot not enable usb debugging, because my phone won't boot past the loading screen.
- I have a Moto G btw.
- This post saved my day..thank you so much :)
- Hi Kannon,I have Yu Yureka android phone( lollypop version).. I am facing a problem in connecting my device as removable disk. Whenever i connect my phone to PC it shows under portable device. Actually i have my data i want to recover it back but recovery software doesn't recognize my phone under portable device.. Please help me out to connect my phone as a removable disk not under portable device.
- my lenovo a6000 ph got bricked and struked up at lenovo logo...iam note able enter in boot menu by presiing 3 buttons simultaniously...and also my ph is not getting detected by adb ...please help me..i have a backup of my rom with me...plz help me as soon as possible.....waiting for ur reply
- Your phone isn't getting detected by ADB because you likely cannot enable ADB from within settings -- because your device is bricked. Have you attempted a reset from the bootloader? If you're unmodified, that is.
- Hi Sai,
How did you managed to resolved the mobile. I do have the same problem. Let me have your guidance.
- Thank you very much for your help, i have finally did configure the driver for my huawei tablet, now i just need to update the OS
- Hi...do u by any chance know how to by pass the Allow USB debugging RSA fingerprint option that pops up on the phone when you connect it to a computer. I cannot accept on the phone since my screen is broken.Any ideas please?
- Can you use an OTG mouse? If you have an OTG adapter cable I believe you can convert any USB mouse (or almost any) into an Android mouse.Unfortunately you won't be able to pair a Bluetooth mouse because the broken touchscreen will prevent authentication.Most devices have OTG capabilities, but a rare few do not.
- Actually I saw it's GT-i9100T and not GT-i9100I've submitted my question with all the information needed. Thanks a lot!
- GT-I9100, and I have CM11 installed
- That's definitely not an exotic driver. Can you submit your question to MakeUseOf.com/answers/ask ?I'll do my best to find the answer for this one. Please include as many details as possible. The more details, the more likely it'll get published.
- Hi,
I'm trying to flash a kernel via Odin 3.7, but after I press START it writes 'Can't open the serial (COM)'.
Iv'e tried your method of reinstalling the driver but it didn't solve the problem.
Do you have any idea what else sould I try?Thanks- I didn't have Kies installed, only the universal ADB drivers.When I DID install Kies, it didn't recognize my device and I couldn't cancel this option (although the computer did recognize my device as MTP).
- What device do you have? It could be a matter of an exotic driver.
- You saved my day !! Thanks so much
- On Moto G 2nd gen this not works for me (but this is funny, because on laptop works at default drivers). Factory reset don't remove ringtone bug, but converting mp3 to ogg and throwing this file in Ringtones folder in internal memory works.Anyway, thanks for tutorial.
- Sorry it didn't work. Sometimes you might need to disable media storage (MTP). It will show up in your context menu on the Android device. It goes without saying that you will also need to enable ADB in Android for it to work.
- Awesome! Thanks for taking time to post this. I had the same issue when I connected my Samsung galaxy s4 mini (running kitkat) and your solution fixed it!.Also disappointed on why google has not handled this issue gracefully.
- Thank you so much for your simple, clear and above all effective advice. This works!
Best wishes, - Installing Koush’s Universal ADB Driver resolved the issue. Thank you so much.
- Never mind, I am able to get it installed via android sdk google driver, and adding the device id of my phone in to generic driver. That worked.
the website that you posted does not list that phone itself.Thanks - HelloI tried all methods and drivers on web. But I never got ADB driver for TCL ALCATEL J636D+. Its even not there on manufacturers website. Dont know how to make it work.Suggest if you have an idea.
- Bro, it didn't work for me... My phone is Android One - Micromax AQ4501..
- I think the problem I have with my tablet is that it is one of the cheaper Chinese ones and they don't come with the normal configuration settings like my galaxy S4. The tablets are now selling in the UK for £60 and come with 32mb ram and 4.42 kit kat. You cant argue at the price or quality but its impossible to find the manufacturer or get driver updates. File transfer has to be done via TF SD card which is OK really. Its just minor problems which give me a reason to moan. lol. The solution will be out there, its just difficult to find. Thanks for your help and info.
- I am completely lost on this issue.
My partners phone (galaxy s3) will connect to laptop no problems... with current configuration.
My phone, however (samsung galaxy s4), will not.
I keep getting usb device not recognized.
Interstingly, I had brief success with playing about with the usb settings.
*#0808# then selected CP instead of AP.
This worked fine and allowed the phone to be recognised and I could browse the contents of my . For about 3 minutes, until I opened kies and tried to connect that way.
Now I'm back to square one with a phone that will not connect to or be recognised by the laptop.
Interestingly again, my partner can connect with kies and without kies.
No further tinkering with USB settings on my phone has allowed me to connect.
Any clues ???
Thanks.- I had the same problem with my S4 and Windows 8.1. I installed the new Kies 3 and that solved the problem (drivers again) eventually after rebooting both of them. Sometimes Windows recognizes the S4 without opening Kies, sometimes it doesn't, odd. As you can see from my last post, I'm sick of trying to connect androids to Windows 8.1.
- Sometimes the phone or tablet will itself request permission to connect via ADB. This usually involves just checking a box on the Android device. Other times, you will need to disable MTP or media access, which is different from having access via the debug bridge. I don't think you can simultaneously have ADB and media access.
- I have a tablet running android 4.42 and my PC runs windows 8.1. I connect via usb but windows does not recognise the tablet at all. I've set the debugging option and installed the Koush USB drivers but I have not had the option to use them because the PC will not recognise the tablet. It just runs through a routine of making loads of noises, like its trying to identify the usb source , this goes on for ever but nothing else happens. What can I do. Help!
- never mind, i got it detected by adb :) when under devices, Google Nexus ADB>update driver>let me pick> usb adb.
- Glad you found it. By the way, HTC only just released the official USB drivers for the Nexus 9.I have an N9, too. It's super buggy and sometimes suffers from overheating -- but I like it a lot, for some reason.
- I actually write for a tech website, so HTC sent us a Nexus 9 test unit. Yup its fun to use, but it didn't have the latest firmware updates because the N9 being a test unit. The tablet gets hot unnecessarily for any small work. I expected better on the back too.Since you got the proper commercial Nexus 9, try the Google updates. I've got lot of feedback the latest updates simmers down the heating issue. And the back could have been better. Ok did you feel any strain on your hand when you started to use it first time in portrait mode, or for prolonged use? This is something i came across and no1 talks abt it.
- That's really great! I had to pay for mine.There were a lot of QC problems, aside from serious bugginess with firmware. Voice recognition was spotty with the screen off.I suspect that HTC and NVIDIA failed to pay licensing fees for the always-on listening capabilities (Qualcomm and a few software companies dominate voice recognition patents on mobile) and so there's a third or fourth hidden core in the Denver chipset. I'm waiting for the microscoped SoC to get published.The update seems to have reduced temps by a small amount. I get 71-72c after browsing and watching video, randomly. Before the temps were in the high 70s. It could just be confirmation bias on my part. I've been using it in low-drain mode and the temps are very reasonable when it underclocks, though.I didn't get hand-strain, but it depends on how users hold the thing. One-handed, with fingers wrapping around the back -- major hand-strain. One-handed with fingers on the bezel, no hand-strain. For gaming, two-handed, no strain.Here's my review (share yours, too, if you'd like):
- Hey ive got a Nexus 9, and ive done all the steps mentioned above. Infact Koush USB drivers already existed in my PC, and it even shows Google Nexus ADB Interface under devices, but adb doesn't detect when i hit the adb devices command under adb shell. Any suggestions?
- I tried your way in my windows xp sp3 with moto x (2013). but this is not working please help..
- Hello Ankit, I would try using the instructions supplied by Vinu, below. If that doesn't work, let me know what you've tried and I'll do my best to help.
- Kannon - You are a canon. After spending 4 hrs. on this, your enlightening post saved the day. Thanks a million!
- Ilan, thank you. I'm glad my post was able to help!
- On Windows 8.1 (probably Windows 8, as well) it works better if you use the following procedure after installing the Koush universal driver:-- Choose 'Browse my computer for driver software' (as shown in blog)
-- DO NOT locate the driver by pointing to a directory
-- INSTEAD, choose the second option: 'let me pick from a list of device drivers on my computer'
-- locate the 'Android Device' in the list (this is the Koush driver)
-- wait for the list of 'models' to appear, it can take a while to populate
-- select the first one in the list ('Android Composite ADB Interface')
-- answer 'Yes' to the 'Update Driver Warning'Now your ADB driver will be installed.It doesn't matter which ADB driver you choose from the list because the Windows USB driver for ADB connections is the same for all Android devices, it's just the device IDs that change. By using this procedure you're overriding the device ID matching and just using an ID for another device. In the end, there is only one USB driver binary that works with all your devices.You may need to do this again when you connect another Android device (from a different manufacturer) if it has IDs that are not in the Koush driver that you originally installed.Likewise, if you had installed the Google or Samsung or some other Android USB device driver for ADB, you could have selected that ADB * driver from the available drivers and it would have worked.Took a long time to figure this out, but so glad I did because now I can quickly and reliably add new devices for debug!- This is my fault and I am very sorry for causing the issue.I went ahead and updated the article to reflect this. I should have suggested that users manually locate Koush's drivers AFTER normal means fail.I'm glad that you figured it out. And thank you very much for letting me know about the issue.
- This worked for me. Thanks a mill.
- Thanks so much for the response. The issue is the drivers don't show up in the list of options and even if I manually browse to the location Windows won't let me select them, saying there are no compatible drivers in that location :/
- Thought I left a comment earlier but not seeing it so I'll toss it out again. Having a ton of issues with this and have tried all of the above in addition to countless other things. Pleeeease help!
- I'm having a very similar issue to another user above. Have been working on it for days, and have diligently tried every step above to a T, along with many other methods. Windows still installs a default driver that does not work, and doesn't allow me to manually select any other drivers. This is driving me crazy, any additional assistance you can offer would be GREATLY appreciated.
- Only time I have had any kind of problems is with Win XP Systems. On win 7 Ultimate I didn't install any drivers at all. I simply switched the Android device , 2 Samsung phones (Android 2.3 and 4.4.4) and Nexus 7 (2012) tablet, to debug mode and then connected them (one at a time) to the PC. Win 7 automatically installed the correct drivers and the external storage was visible for drag and drop.So far as I am concerned Samsung's Kies is a major culprit. The newer versions simply wouldn't recognise the older devices !
- Do you use something else instead of Kies?
- I've always had trouble on all Window systems, but only after connecting several Android devices. I'm told that ADB drivers tend to be poorly designed and oftentimes conflict with one another. But I would guess that Windows XP is a particularly problematic beast! Thanks for the comment!
- Thanks, Kannon. No I didn't explicitly delete anything. I relied on the Device Manager context menu.I think I fixed it. When I plugged the phone in all I got was an entry in Device Manager under 'Other Devices' named 'Galaxy Nexus' with a question mark. I used 'Update Driver' from the context menu and selected 'Browse my computer for driver software' then 'Let me pick from a list...' It did some searching and there was an entry for manufacturer 'SAMSUNG...' and the model 'Samsung Android ADB Interface.' Selecting that and hitting Next gave me caution about verification. I hit 'Yes' to continue and it installed.Now I have my Samsung ADB Interface back. Whew! In the process I seem to have lost the MPT driver under 'Portable Devices' but I'll worry about that later.Thanks for the response. I got verbose here in case anyone else has the same problem.
- Windows 7, Galaxy Nexus. This failed for me in a bad way. After uninstalling and deleting the ADB driver that was there, unplugging the phone, getting rid of the stuff with USBDview, installing the downloaded driver package and plugging in the phone, absolutely nothing happens. No driver installation occurs. Phone says 'USB Debugging Connected' but computer doesn't see it.I reran the universal driver installer and used it to remove the drivers. Re-installed the stock drivers for my Galaxy Nexus, plugged it in and still no drivers install.I now have _no_ ADB drivers. How can I repair this serious loss?
- Sorry about the problems. Did you erase the drivers from within the system32 directory or did you use Device Manager to uninstall the driver? I would avoid directly removing drivers from the system32 directory as a small error can cause serious problems.You will need to manually install the drivers if it's not working. Koush specifically mentioned that his driver works with the Galaxy Nexus. The driver 'update' process (in Windows 8, but also for Windows 7 IIRC) appear in the following order:1.) Uninstall driver (from context menu)
2.) Browse my computer for driver software.
3.) Let me pick from a list of device drivers on my computer. (NOTE: this option is not particularly visible. Look a little down on the page to find this option).
4.) Select the device driver you want to install for this hardware.Several options will show up here. Some of these are Koush's drivers.Some other things to think about: Did you try plugging in your device, going into device manager and uninstalling the driver? You need to tick the box for removing the driver from your system.I would also try restarting the computer if Windows 7 fails to pick the device up.Hope that helps! Let me know if there's anything else that goes wrong. I'll do my best to help. Good luck.
- Thank you so much for the article. It's funny that I was having the exact issue with my Samsung Galaxy phone yesterday and spent several hours trying to find a fix - to no avail... I'll try this method tomorrow
- Windows 7. On phone USB plugin the system always installs drivers from 'preconfigured driver folders' and if it can't find them it looks to the internet. If you skip that you go back to the 'preconfigured' search and never get a chance to manually install Koush's drivers. Whatever it finds it installs and won't let you update to Koush's drivers saying that 'The best driver software for your device is already installed.'Looking at Driver File Details from right clicking on the installed ADB drivers they come from C:windowssystem32 and its DRIVERS subdirectory. Deleting those does no good because the search on plugin always replaces them with something from somewhere that it then considers the 'best driver software.'How do I really install Koush's drivers from 'ClockworkModUniversal Adb Driver'? Is there any way to tell the system to stay the hell out of the way and let me install what I want?
- Thanks a lot. For some reason my Nexus 7 and home PC haven't been on speaking terms lately.
- Thank you so much... I was having issues with my Nexus 4 MTP connection. I searched everywhere on net, but none of the solution worked for me. This one worked but remember for MTP you need to disable the USB debugging mode.