Database Users

ADB Device Not Found! :(

OK, posted this in the Q&A section with several responses but no real answers. Figured I'd post it here before another section where it might get locked or moved.
Anyway, ADB was working fine until a few days ago. Now it says "error: device not found." Fastboot still works just fine. I've tried everything I can think of to get it working again. I've uninstalled and reinstalled the usb drivers, removed the Android SDK from my PC and reinstalled, wiped and reflashed my device, made sure Debugging is on, and tried getting ADB to work on all 4 of my PC's. All running either Windows XP or Windows 7. No dice. Can anyone help? Thanks in advance.

The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?

UnderCoverLover said:
The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?
Click to expand...
Click to collapse
Thanks for the reply. If you read my OP you'll see that I've made sure debugging is on. In fact, debugging is also enabled by default after a wipe and clean flash. Unfortunately my problem isn't as simple as enabling usb debugging.

Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!

deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Thanks for the response. I'll give this a shot when I get home. FYI, I didn't change devices. Same Nexus One I've had for the past month. Just one question: When you say,
"In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices"
I don't know what this means. Where can I access this? Thanks!

Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.

markouk said:
Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.
Click to expand...
Click to collapse
Yeah, I've had the phone booted up normally. Thanks though.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MaximReapage said:
Click to expand...
Click to collapse
Thanks a lot.

deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!

Part Four said:
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!
Click to expand...
Click to collapse
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...

myn1 said:
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...
Click to expand...
Click to collapse
Done and done, days ago. Still no dice. This is ridiculous.

Still having problems. Tried everything I can think of, and everything suggested to me by the XDA community. I don't know if this will help any of you guys help me, but when I type "adb devices" into a command prompt, it returns:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
And then shows nothing. So effing frustrating! EVERY computer I have (I actually have tried it on 6 different laptops and PCs) returns the same error and cannot find my Nexus One. WTF happened!? HELP!

Part Four said:
WTF happened!? HELP!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=613217

pvillasuso said:
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
I'm sure you're trying to be helpful but, if you've read through this thread, you'd know that I've already done all of that. OBVIOUSLY, I've done all of that because, like I said, ADB STOPPED working. In order for it to stop, it must have, at some point, worked just fine. And it did. It worked perfectly until recently. So, yes, I've installed all the damn drivers I need. But, no, it's still not working. It's infuriating.

debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.

also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

temperbad said:
debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.
Click to expand...
Click to collapse
Yes. *Sigh*

Do you see this device ( pic ) @ device manager :
If you do , there is no reason for adb commands under DOS prompt for not workig well ... really weird

temperbad said:
also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
What do you mean, I'm "good?"

Nexus 7 not showing up in Windows

Okay, So I bought this new Nexus 7 about a week ago. It was used but the person I bought it from was trustworthy. It came pre-rooted and unlocked. Anyways, my Windows 8 laptop WILL NOT recognize it no matter what I do.
Let me start off by saying, I am no novice to Android. My main device is a Verizon Galaxy s4, and it was the S3 before that. Both phones I did lots of modding and theming on them, and always running a custom rom. I have adb installed and working on my computer as well.
Now the problem. When I plug in my Nexus into my laptop, nothing happens. It doesn't make the usual windows device plugged in sound or anything, and it doesn't show up as a drive in Windows explorer. Even if I open up the device manager and then plug in my Nexus nothing shows up. Not even the "device not recognized" thing. Nor do I get a notification in the Nexus statusbar saying it's plugged in as a media device.. Though the battery DOES charge.
I have tried enabling usb debugging and toggling back and forth from MTP to PTP and still nothing. Tried it w/out USB debugging as well. Nothing.
Tried plugging it in while in fastboot.. Nothing.
I even downloaded the Google drivers through the Android SDK manager and since it doesn't show up as any device in device manager I can't uninstall them and update with the new drivers. This is soo soo sooo frustrating. Obviously it was able to connect to a computer at some point because they rooted and unlocked it, but now I get nothing. I've tried 4 or 5 different computers, Windows 7 AND Windows 8. And even more USB cables.
Can somebody please please shed some light on this?
It's soo frustrating not being able to use ADB with my new device or even do simple file transfers. Right now I'm using Airdroid to move files around but it's agonizingly slow and worthless for moving big files like Roms and whatnot.
And before you say it.. YES I have searched and found no definitive answers even though I KNOW other people have had this problem.
Someone help please?

C'mon... Somebody..:? Anybody?

Try this. Plug it in via USB as you would. Then unlock your nexus 7 and it should up, works for me lol.
Sent from my Nexus 7 using xda premium

do you have a factory original usb line? sometimes other ones just wont work. also try changing roms.

androidkid311 said:
Try this. Plug it in via USB as you would. Then unlock your nexus 7 and it should up, works for me lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I've tried that. Doesn't work. Nothing makes it register.
Billchen0014 said:
do you have a factory original usb line? sometimes other ones just wont work. also try changing roms.
Click to expand...
Click to collapse
Tried this too. I've been using the new factory cable and it doesn't work. I've tried five different cables and different usb ports. Also tried factory resetting and different roms as well.

Couple of things to try:
1 - Go through Device manager (Start -> Right Click My Computer -> Manage) - And remove anything and everything to do with Android, or Nexus etc.
2 - Plug in device, if nothing happens right click The top of "Device Manager" - Which should be your computer name - And click "Scan for hardware changes"
If this doesn't work, try to download WugFresh ToolKit, and install the drivers through his ToolKit, I had issues like this when I first got my Nexus, trying all different things and random drivers, my only way to fix it was going through WugFresh toolkit and downloading his drivers. CLICK HERE FOR THE TOOLKIT
Good luck

Wilks3y said:
Couple of things to try:
1 - Go through Device manager (Start -> Right Click My Computer -> Manage) - And remove anything and everything to do with Android, or Nexus etc.
2 - Plug in device, if nothing happens right click The top of "Device Manager" - Which should be your computer name - And click "Scan for hardware changes"
If this doesn't work, try to download WugFresh ToolKit, and install the drivers through his ToolKit, I had issues like this when I first got my Nexus, trying all different things and random drivers, my only way to fix it was going through WugFresh toolkit and downloading his drivers. CLICK HERE FOR THE TOOLKIT
Good luck
Click to expand...
Click to collapse
Thanks alot man. I do have Wigfreshes toolkit, i just haven't really done much with it. I will try all this when I get home though. Sounds like a good method to try. The device came pre-rooted and unlocked, all I had to do was flash recovery through goo. I'm running Vanilla root box night lies and they are great. I'm just really worried about getting in a bootloop or softbricked since there is no battery to pull, and i can't connect to my computer to unbrick. If it happens I'll be waaaay up the creek with no hope for a paddle.
Thanks alot.

Here is the latest Android Composite ADB Interface Driver straight from SDK instead of toolkit.
http://d-h.st/kDu
If you are worried about ROM failing, installing MultiRom is highly recommended. Not indifferent to partitioning a hard drive and installing multiple operating systems on a PC, MultiRom is indispensable when experimenting. If one ROM doesn't boot, simply boot from another or to your stock rooted.
Example -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Username invalid said:
Here is the latest Android Composite ADB Interface Driver straight from SDK instead of toolkit.
http://d-h.st/kDu
If you are worried about ROM failing, installing MultiRom is highly recommended. Not indifferent to partitioning a hard drive and installing multiple operating systems on a PC, MultiRom is indispensable when experimenting. If one ROM doesn't boot, simply boot from another or to your stock rooted.
Example -
Click to expand...
Click to collapse
Is tha driver different from the drivers I downloaded from the SDK manager?

nicholi2789 said:
Is tha driver different from the drivers I downloaded from the SDK manager?
Click to expand...
Click to collapse
It is version 7.0.0.1.

nicholi2789 said:
Thanks alot man. I do have Wigfreshes toolkit, i just haven't really done much with it. I will try all this when I get home though. Sounds like a good method to try. The device came pre-rooted and unlocked, all I had to do was flash recovery through goo. I'm running Vanilla root box night lies and they are great. I'm just really worried about getting in a bootloop or softbricked since there is no battery to pull, and i can't connect to my computer to unbrick. If it happens I'll be waaaay up the creek with no hope for a paddle.
Thanks alot.
Click to expand...
Click to collapse
No worries mate best of luck !!
Let us know if not and I'll try find another way

I found this while searching. http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip . USB drivers for win 8 problems-
Sent from my Nexus 7 using Tapatalk 4 Beta

best and quick solution. Open "settings"
nicholi2789 said:
Okay, So I bought this new Nexus 7 about a week ago. It was used but the person I bought it from was trustworthy. It came pre-rooted and unlocked. Anyways, my Windows 8 laptop WILL NOT recognize it no matter what I do.
Let me start off by saying, I am no novice to Android. My main device is a Verizon Galaxy s4, and it was the S3 before that. Both phones I did lots of modding and theming on them, and always running a custom rom. I have adb installed and working on my computer as well.
Now the problem. When I plug in my Nexus into my laptop, nothing happens. It doesn't make the usual windows device plugged in sound or anything, and it doesn't show up as a drive in Windows explorer. Even if I open up the device manager and then plug in my Nexus nothing shows up. Not even the "device not recognized" thing. Nor do I get a notification in the Nexus statusbar saying it's plugged in as a media device.. Though the battery DOES charge.
I have tried enabling usb debugging and toggling back and forth from MTP to PTP and still nothing. Tried it w/out USB debugging as well. Nothing.
Tried plugging it in while in fastboot.. Nothing.
I even downloaded the Google drivers through the Android SDK manager and since it doesn't show up as any device in device manager I can't uninstall them and update with the new drivers. This is soo soo sooo frustrating. Obviously it was able to connect to a computer at some point because they rooted and unlocked it, but now I get nothing. I've tried 4 or 5 different computers, Windows 7 AND Windows 8. And even more USB cables.
Can somebody please please shed some light on this?
It's soo frustrating not being able to use ADB with my new device or even do simple file transfers. Right now I'm using Airdroid to move files around but it's agonizingly slow and worthless for moving big files like Roms and whatnot.
And before you say it.. YES I have searched and found no definitive answers even though I KNOW other people have had this problem.
Someone help please?
Click to expand...
Click to collapse
Open "settings" on your nexus 7 2013, click on "storage", click on options(3 verticle dots on top right corner), check allow MTP... Thats it you can now open your nexus drive on your PC

iralamanoj said:
Open "settings" on your nexus 7 2013, click on "storage", click on options(3 verticle dots on top right corner), check allow MTP... Thats it you can now open your nexus drive on your PC
Click to expand...
Click to collapse
Haha, thanks for the help, but I wish it were that simple. It was a first Gen Nexus7 by the way too.
I'm no novice to the ways of Android, and i tried everything under the sun to get it to work. Nothing Would make it show up on the computer.
Anyways, it just ended up turning off one day (with a fully charged battery too) and wouldn't turn back on. I ended up calling Asus and they repaired it for me. It had a burnt out USB port. They fixed it and it's up and running fine now.
Long story short, be careful what you buy on eBay one, and two, Asus has EXCELLENT customer support. From the day I called them to the time I got it back fully repaired only took 7 days exactly. And I didnt have to pay for shipping. If you ever have a problem with an Asus product don't hesitate to call them.

I just solved my problem. The Nexus 7 was not showing up in the device manager and windows explorer. Once usb plugged it would charge but do nothing.. In device manager I found "ACER Composite ADB Interface". I googled it and this is the problem. apparently Windows update install this thing but it doesn't work with the Nexus 7. You have to uninstall it (don't forget to check the delete from computer box or else it will reinstall itself). Then look for this : ASUS Android Composite ADB Interface Driver 8.0.0.1 for Windows 7 64-bit and download it.(sorry I can't post links)
Now with your Nexus 7 plugged in update your driver by selecting the browse my computer option and locate the file you just downloaded and there you go it should work. After months of searching it's finally working. :victory:

Fixing MTP/Debugging not reading your Nexus device...

Ok peeps... I've flustered myself over this issue for a while, and noticed in a couple other threads that others are having this issue as well, so I'm posting what I hope to be a "cure all" for devices not reading in Windows as MTP devices. This should work in any and every Google Nexus devices, with the one exception being the actual Galaxy Nexus (model SCH-I515) because it's driver is distributed by solely by Samsung.
A little background:
For a long while, I had my device all nice and set up, ready to use and work with as I so pleased, and then it seemed like there was a driver update, and from then on out, I couldn't get my device (in this case, the Nexus 7 Grouper) to be read by Windows as anything other than a PTP (camera) device... I looked high and low over the internet (including this site) for a fix to my problem, a number of offerings to look over, and seemingly only one of them worked. So... Here I am to share it with you all, so hopefully you don't have to fight with it (anymore) like I did...
Just a quick FYI, this worked for me using BOTH Windows Vista (64 bit) and Windows 7 (64 bit), and really should be pretty much universal for all versions of Windows (but don't quote me on that, I'm not saying it with 100% confidence)
Now, a lot of the pages that I came across in my search suggested that you have to uninstall this or that, reboot a half dozen times, and really, more work than it actually took, so I'm going to offer up the way that worked for me, and did so simply. I'm not saying that pages like TheByteSmasher's or sfhub's version for the 2013 N7 model didn't work, simply that they took more steps than what actually worked for me with less hassle. That all being said, let's get to fixing the issue at hand...
I suggest that on your computer that you have a display of your computer's drives (start menu, then selecting/entering the "computer" option)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in the background while you're doing all of this. Visually, it serves as an aid for what you may or may not have to do. If at any time your device shows up in your computer's devices in MTP mode, you should already be fine. If not, please continue.
On your device:
Begin by plugging your device into your computer using a data-compatible USB cord (most stock cords that come with your device are).
If your computer starts trying to install device drivers, let it take it's course, and see if your device is working "as is" with USB Debugging.
Note that every time you switch debugging on or off, or switching between MTP and PTP, your computer could/might install drivers for each mode. Let this finish before making another selection.
Open the Settings app.
Choose Storage.
Touch the Menu icon button, and then choose the command USB Computer Connection. (Might be up in the corner somewhere, in a pulldown menu... Mine had 3 dots set up like a colon if that helps ya get the image)
There should be two options; MTP and PTP.
Ensure that there’s a check mark by the Media Device (MTP) option.
Back out of the Storage tab, and go into Developer Options.
If Developer options is not available to you, go to "About phone/tablet/device", and where your build number is listed, tap that section 7 times. After about the 4th time of you tapping it, it'll toast you a little notification that just says "continue tapping for developer mode"​
Once you're in Developers Options, go to the Debugging area, and select enabling of USB Debugging.
On your computer:
Get into your device manager. This can be done a number of ways, some of which depend on which version of Windows you're on... I personally use the WindowsIcon+PauseButton shortcut feature, but if you need directions on this;
Clicking the Start button > click Control Panel > System and Security > under System, clicking Device Manager.* Administrator permission might be required depending on settings and your user account of your computer. Another way to do this, again depending on which version of Windows you have, could be done by opening the Start button, and in the search feature typing in "device manager"
Once in device manager, it'll display all devices connected to your computer. If you're unsure as to which connects to your device, simply pay attention to the device manager while you unplug your device (it'll refresh) and then plug your device back in (another refresh will happen). Chances are, it'll be either a collapsable tab called "Android device/phone/tablet" or it'll be in your "Portable Devices" collapsable tab. (It could also be in USB controller/devices, for whatever reason) Whichever one it is for you, expand that tab and it'll show something like "Android Composite ADB Bootloader Interface" or some variation of those words. This is good, we know that your computer is reading that your device is connected, even if it's not (presently) allowing MTP.
Double-click the Android Composite ADB Bootloader Interface submenu item, and it'll pull up the properties of it, giving you 3 tabs to select from. Go to the "Driver" tab, and read what version of driver it says you have installed.
Taking a step away from that for a minute, download the latest Google USB Driver zip and save it into a directory where you can easily find it... Download folder or desktop work fine, whichever you're more comfortable with.
BTW, if for whatever reason the link above doesn't work, you can go directly to the Google USB driver page and download it from there, but the first link takes you directly to the latest download zip file itself...
Once you have the file downloaded, extract it into a folder using a program like WinRAR or other zip file utilities.
NOTE: The next step is not mandatory, but I suggest it for users who are knowledgeable enough to know that there are files, folders, and other such things on your computer are not meant to be messed with, and if you do so, you could mess up your computer. What I'm doing will not mess up your computer AT ALL, but if you decide to mess with other things in folders we're going to access, then YOU can mess it up. You've been notified, I'm not going to take responsability for your actions, because if all you do is follow my directions, NOTHING bad will happen. If you're uncomfortable with messing with system folders/files, just skip to the step beyond this... This one is done purely for cosmetic and easily accessible reference reasons only.... That being said, go into your computer's driver's folder, which will usually be found at C:\Windows\System32\drivers. From there, create a new folder and call it "Android", and then go into it. Take the files that you extracted in the previous step, and move them all to here. After moving them all into the android folder, remember the location you're at in Windows, you'll be using it in the next step...
Whether or not you did the previous step, it's important that you know where the files you extracted are now placed. Going back to the device manager program, in the tab "driver", you'll see where it says "Update Driver". Click that.
A prompt will come up asking if you want to "search (online) automaticly for updated driver software" or to "browse your computer for driver software". You have already downloaded the latest driver, and honestly the automatic search often finds a driver that's useless or doesn't work right, so you'd select to browse your computer... If you moved the files into the drivers folder done a couple steps back, provided you haven't named your computer or placed the files on another drive than your C:/ drive, your location for what you're looking for should be C:\Windows\System32\drivers\Android\latest_usb_driver_windows\usb_driver. Feel free to copy and paste that upon your need, and place it directly into the "search for driver software in this location" box.. Hitting "Next" should bring you to the next step (below). If you didn't move the files (or they're in a different directory, or for whatever reason the above didn't work for you), then you're going to have to point your computer to where you placed the extracted files... And this kinda gets "iffy", as in "if the computer sees what you've done" or you actually have to "hold it's hand" to recognize what you've done. In other words, at this state of implementing the files, you computer really hasn't recognized them (the driver files) existing on your computer. So, chances are, you're going to have to do some hand-holding, which is fine, because atleast this way, we know we're all doing it in a way that both you and your computer aren't having to guess....From here what you'll need to do is select "Let me pick from a list of drivers on my computer" and upon doing so, UN-ticking the "show compatible hardware" check-box. You should see now a couple of selection boxes listed as Manufacturer and Model. Do NEITHER of these. Instead, click the "Have Disk" option, and a "Install from disk" menu will pop up. From there, go into "Browse..." and point your computer to wherever you placed the extracted files, opening all the folders until you come to a file called android_winusb.inf, and selecting it. This will guarantee that your computer is grabbing and using the exact file you're wanting it to, the correct driver update installation.​
After selecting the "android_winusb.inf" file and hitting Open/OK, it'll bring you back to where you un-ticked the "show compatible hardware" option earlier, with it now being re-ticked (which is fine). There might be a few listings as to which you can choose from there under the "model" tab, and any of those should work for you. You have to CLICK which one you want until a popup appears. I just chose the one with the longest name, figured it served the most purposes... :laugh:
Anyways, your driver will start installing... You'll likely hit a warning message that says something to the extent of "this driver cannot be verified"... Shoot right through that and allow it, and your device will finish installing the driver... If your sound is on, you'll notice a new device connection sound... Check back in the contents of your computer connections, and you should see your "new" device listed there. If not, sometimes a restart might be required.
Congrats, your device is now seen by Windows:
If this helped you, I'd love a thanks!

reserved....

TToTT said:
... download the ... driver ... from there...
Click to expand...
Click to collapse
User 1wayjonny has also made his offering of what he calls "Naked Drivers" which offers more "Universal" android coverage than just Nexus devices, though I haven't tested/used them myself. Procedure would be the same as above, just pointing to his drivers instead. His post can be found here.

I'm having an issue where I can connect to my 64 bit Win 7 laptop in debug mode, but I'm not able to connect in the MTP mode with debug turned off. I expected to be able to mount the device storage in either mode.
Is that correct? If so, any ideas? I do notice I can't seem to get the MTP driver to stay in device manager.
Rick

C5Longhorn said:
I'm having an issue where I can connect to my 64 bit Win 7 laptop in debug mode, but I'm not able to connect in the MTP mode with debug turned off. I expected to be able to mount the device storage in either mode.
Is that correct? If so, any ideas? I do notice I can't seem to get the MTP driver to stay in device manager.
Rick
Click to expand...
Click to collapse
Try not only removing, but actually deleting the driver you're on while your device isn't connected, and after doing so, reconnect the device with the newest drivers installed on your computer. For some reason, Windows has been known to trick itself into either allowing or not allowing things to work simply because of this. As for why you're able to connect in MTP in debugging mode and not when you've got debugging turned off goes, part of the entire reason for debugging mode is for compatibility. It certainly doesn't harm either your computer or device in one vs the other (debugging on or off), so as long as you have one that does work, there's no need for the other, or to have a "problem" with not having the other. If you're just OCD about fixing things like this though, there's always trying what I suggested to begin with.... (first sentence)

Thanks for the response. I'm going to give your suggestion a try because I am OCD about this kind of thing. It's nice to know I've got it working, but bugging me that I can't get it working all the time.
Rick

Actually, deleting the drivers seems to have done the trick. I'm going to watch it over the next few days, but thanks again for the tip.
Rick

C5Longhorn said:
Actually, deleting the drivers seems to have done the trick. I'm going to watch it over the next few days, but thanks again for the tip.
Rick
Click to expand...
Click to collapse
Happy to have been of some help. :good:

bro there is no latest_usb_dri ver_windows type folder in this downloaded zip.pls help me

Samsung Windows drivers problem

Looking for some help please, with my new-to-me S5. I want to root it, mostly so that I can restore Titanium backup from my S4, but probably to install CM12 too. I have installed (and uninstalled, rebooted, installed, rebooted, many times) the latest Samsung drivers e.g. Samsung_USB_Driver_v1.5.51.exe, I have tried installing Kies3, I have tried different USB cables, I have tried my Win7x64 laptop, my wife's Winx64 PC; none of them will show the phone in Windows Explorer.
I did try it on a very old laptop (Core solo) that happens to have a play copy of Win8.1, and it worked! I then tried to use Odin v1.85 and Odin v3.09 to push CF-Auto-Root, and it always ended with Odin "Not responding" - presumably because the laptop doesn't have the guts.
I did put Win10 preview on a spare hard drive in my laptop, but no joy after installing Samsung_USB_Driver_v1.5.51.exe. Under Win7 I had tried older versions of the drivers too.
Ant bright ideas please??
TIA

fjuniper said:
Ant bright ideas please??
TIA
Click to expand...
Click to collapse
Kies will install the correct drivers so uninstall Kies completely, reboot your PC then install it again, check for updates and if any update kies then run it.
When it is running plug in your phone to a USB port that is directly on the PC not via any hubs and you must use the cable that came with the S5, other cables will not work correctly, make sure it installs the drivers at this set up.
Windows does not necessarily install the correct drivers, you need to go to My Computer > properties >. device manager and find your device in the list it should be shown as Android Mobile Phone if that is there then make sure the installed drivers are Samsung Android ADB Interface, if it isn't showing this driver them change it.
The other option if you have the Samsung drivers installed is to plug in the phone check in Device Manager on your PC and find your phone then check and change the drivers.
Turn off any firwall whilst you do this as that can block the device as well

Thanks for the suggestions. Yes, I had tried the original Samsung cable as well as others. Plugged straight into a ThinkPad, no USB hub.
Uninstalled Kies and the Samsung driver package, rebooted, installed Kies, checked for updates (none), and - Nothing. Nothing in Device Manager, nothing in the Safely Remove Hardware tray applet. Nothing in the notification area of the phone. The firewall was disabled for all of that post-reboot.
It's driving me mad...
I do eventually get a USB Device Not Recognised popup with Unknown Device shown in the window. By now, there is also an Unknown Device showing in Device Manager under Universal Serial Bus Controllers. I could Update Driver, but unsurprisingly Windows can't find one. My only other option would be to use the Have Disc option, but only if I had the right .inf file... :crying:

"None of them will show the phone in windows explorer"
You know you need to put the phone into download mode to use ODIN?
It won't show in explorer when you do that, but ODIN should say it is connected
And use the latest version of ODIN you can find, 3.09 should work, 3.10.6 is latest

*Detection* said:
"None of them will show the phone in windows explorer"
You know you need to put the phone into download mode to use ODIN?
It won't show in explorer when you do that, but ODIN should say it is connected
And use the latest version of ODIN you can find, 3.09 should work, 3.10.6 is latest
Click to expand...
Click to collapse
Thanks for replying. Yes, I have tried plugging in with it in download mode and using Odin, but it wasn't showing the COM port, so it wasn't recognised using that either. I even tried pushing CF Auto Root, but of course it failed.

It sounds like the cables you've tried are faulty, so long as the phone USB port is not
Multiple PCs say to me it's not a PC issue
The samsung drivers just need installing with the installer, don't worry about manually installing them, once you have working USB cables/port it will install them automatically so long as you ran the installer

Have you attempted to use different USB ports on the computer you are using? Contrary to what Detection has said, the fact that you can get it working on another computer with all of your cables does point to this being a PC problem and not a cable problem. My suggestion would be to completely uninstall Kies, keep it uninstalled, use different USB ports and allow windows to install the drivers itself.
On various occasions, removing Kies has worked, and on another it was the USB port that I was using that was the problem.

OP said he tried two different Win 7 PCs before trying the 8.1 laptop on which he had partial success
My guess is if he is constantly moving the cables from PC to PC, if they are faulty, bending them around is possibly making the connection by the time it ended up on the laptop it recognised the phone from, like when your charger cable breaks inside and you have to wiggle it around to make a connection
But as he also said, it failed to work even on that - so that's 3 machines, one partially recognised the phone - Id say the chances of it being a bad USB port over 3 machines, or even bad machines are very slim
Bad phone USB port or bad cables is my guess
Either that, or Win 7 isn't playing nice with the phone/drivers

I remember reading somewhere that with windows 7, you have to run odin as an administrator......also remember reading that it's not just the firewall you have to disable, but the anti virus as well......It may not help to uninstall kies as this *may* remove the Samsung drivers. Probably be better to leave it installed, but to use windows task manager to kill any running kies processes before you start odin up, as (from what I've read ) kies will interfere with odin.......
And for info.......odin 3.09 is the version I have successfully used on my phone.
Sent from my rooted kn0x0 stocKK SM-G900F S5

Thanks for all your replies while I was asleep.
I have used multiple USB ports on the 2 Win7 machines, multiple cables including the one that came with the phone. When I dropped the firewall, it was f/w and AV as it's one program (Symantec) (corporate laptop, not locked down). I have tried running Odin as administrator. If it wasn't for the fact that it did work on the ancient Win8.1 laptop, I would have thought the problem was with the phone port, but I could see it in Windows AND Odin displayed the COM port - it was just that Odin then went "Not responding"... which I assume was a system performance issue...
I will have another try tonight with yet more cables and I must have some USB ports I haven't tried yet... None of it makes sense and I am not a noob.
Edit: This is all having a negative effect on my laptop too - I used to be able to see internal and ext SD on my S4 in windows explorer - at the bottom of the right pane it had i9505 then you saw a folder for each SD. Now I just see ext SD as a drive letter.

Try this:
Install or just use the portable version of "Ghostbuster"
http://ghostbuster.codeplex.com/
Unplug all USB devices from the machine other than K&M
Run Ghostbuster as Admin
On the first device listed of each section, right click and choose "Add Class"
That should highlight the entries in that class and flag the ghost entries
Do that for every section until you have them all highlighted
Now click "Remove Ghosts" at the bottom and let it do it's thing
That will remove all non connected USB devices and their drivers
Once it's done - reinstall Samsung drivers just using the normal installer
Plug phone in and see if you get any better luck with it being detected
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks Detection, I hadn't come across that before. It deleted LOADS of ghosts... ...but unfortunately it hasn't moved me on at all. Still nothing in WinExplore, no COM ports in Odin. I am somehow jinxed, or rather this S5 is.
Edit: Just did it all again with a couple of reboots for luck - no better.

fjuniper said:
Edit: Just did it all again with a couple of reboots for luck - no better.
Click to expand...
Click to collapse
Open up the Device Manager on your PC then plug in your phone and look for any new connections to appear in the USB controllers list there may be Unknown device or another named device if you see a new connection unplug the phone and check the list again to see if it has disappear from the USB list, if you see a USB device appear and disappear from the list as you unplug and plug in the phone this is the one you want.
Right click on this and select Update Driver Software, click Browse My Computer then click Let me pick from a list, if you have the Samsung drivers installed on your PC you should see one or more called Samsung Mobile USB Composite Device, select the most up to date version if you have more than one listed and install that.
If you don't see the Samsung USB drivers un-tick the box that says Show compatible hardware, scroll down the list to the left and find Samsung Electronics Co Ltd, there will be more than one, click on each one until you see Samsung Mobile USB Composite Device in the right window, then click on that and install it.
You will get a warning saying that changing the driver may cause the device to not work properly just click OK and install the driver, if it works the USB device in the list should change to Samsung Mobile USB Composite Device.
Try this and see if it gets you sorted manually but don't forget to make sure you have installed the Samsung drivers on your PC first

ag4751 said:
Open up the Device Manager on your PC ...
Click to expand...
Click to collapse
Thanks, I will give that a go, though it will not be until Saturday as I don't have the phone with me. I am pretty sure that it does appear / disappear in Device Manager, and I did look at manually updating from there, so your suggestions should be helpful.

ag4751 said:
Open up the Device Manager on your PC then plug in your phone and look for any new connections to appear in the USB controllers list there may be Unknown device or another named device if you see a new connection unplug the phone and check the list again to see if it has disappear from the USB list, if you see a USB device appear and disappear from the list as you unplug and plug in the phone this is the one you want.
Right click on this and select Update Driver Software, click Browse My Computer then click Let me pick from a list, if you have the Samsung drivers installed on your PC you should see one or more called Samsung Mobile USB Composite Device, select the most up to date version if you have more than one listed and install that.
If you don't see the Samsung USB drivers un-tick the box that says Show compatible hardware, scroll down the list to the left and find Samsung Electronics Co Ltd, there will be more than one, click on each one until you see Samsung Mobile USB Composite Device in the right window, then click on that and install it.
You will get a warning saying that changing the driver may cause the device to not work properly just click OK and install the driver, if it works the USB device in the list should change to Samsung Mobile USB Composite Device.
Try this and see if it gets you sorted manually but don't forget to make sure you have installed the Samsung drivers on your PC first
Click to expand...
Click to collapse
When I manually select the Samsung Mobile USB Composite Device, I always get "Windows encountered a problem installing the driver software for your device. This device cannot start. (Code 10)", so I am still stuck...

fjuniper said:
When I manually select the Samsung Mobile USB Composite Device, I always get "Windows encountered a problem installing the driver software for your device. This device cannot start. (Code 10)", so I am still stuck...
Click to expand...
Click to collapse
There are a couple of things you can try as Windows is preventing the installation.
1. Control Panel > Devices & Printers then plug in your phone and you should get an Unknown Device appear, right click on it and select Troubleshoot and run that process to see if that sorts out the problem.
2. Start your computer in safe mode then try installing the driver manually that way, then reboot your PC normally.
I had this error message last year with something I was trying to install but I can't remember just how I sorted it out.

[Q] SGS5 Not recognized by PC!

Whenever I connect my phone to my computer via USB, it says "USB Device not recognized". I look in my device manager and I see 4 devices come up called "Bluetooth Peripheral Device" show up under "Other devices", yet they got yellow warning symbols next to them.
My phone connects to my PC via Bluetooth fine, but the USB just wont work! I've searched the web but most things are outdated or just don't work...
I think this is due to using an OTG cable, making my phone act as the host device whenever I plug it in?
Extra detail:
-PC is running Windows 7 ultimate x64
-Samsung Galaxy S5 is on Android 5.0, but didn't work on previous versions either
-I use the samsung cable, but have also tried one other cable.
-Tried plugging it into another computer, does the exact same thing.

Install Samsung drivers / KIES3

*Detection* said:
Install Samsung drivers / KIES3
Click to expand...
Click to collapse
Already tried those, made no difference unfortunately

CheeseJuggernaut said:
Whenever I connect my phone to my computer via USB, it says "USB Device not recognized". I look in my device manager and I see 4 devices come up called "Bluetooth Peripheral Device" show up under "Other devices", yet they got yellow warning symbols next to them.
.
Click to expand...
Click to collapse
Have a look at this post I put up for someone with a similar problem to you, see if it helps, you need to use the USB cable that came with the phone, others will work but a lot don't work properly
Post

ag4751 said:
Have a look at this post I put up for someone with a similar problem to you, see if it helps, you need to use the USB cable that came with the phone, others will work but a lot don't work properly
Post
Click to expand...
Click to collapse
Thank you for the great help, I think that this is what needs to be done to fix it. There is still one problem though.
I have tried this before, but I ran into a problem where it would do this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see, it wont let me use the driver, saying that there is a "code 10" and that the driver wont start. I think that if I can get through this error, my phone will finally connect

CheeseJuggernaut said:
As you can see, it wont let me use the driver, saying that there is a "code 10" and that the driver wont start. I think that if I can get through this error, my phone will finally connect
Click to expand...
Click to collapse
Try these options,
1. Control Panel > Devices & Printers then plug in your phone and you should get an Unknown Device appear, right click on it and select Troubleshoot and run that process to see if that sorts out the problem.
2. Start your computer in safe mode then try installing the driver manually that way, then reboot your PC normally.
Registry solution if you want to try it as long as you understand Windows Registry
1. Go to the Registry Editor click Start > Run > and type in regedit then hit Enter
2. Expand the folder location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
3. Find EEC5AD98-8080-425f-922A-DABF3DE3F69A in the folder list and click on it, this should say Portable Devices in the right window
4. See if it contains a value called UpperFilters if so delete it
5. Before you delete it though make a backup of the EEC5AD98-8080-425f-922A-DABF3DE3F69A folder, right click on it and Export to a folder just in case you need to restore it.
6. To restore the key if you need to just go to the folder where you exported it to and click on it to install

ag4751 said:
Try these options,
1. Control Panel > Devices & Printers then plug in your phone and you should get an Unknown Device appear, right click on it and select Troubleshoot and run that process to see if that sorts out the problem.
2. Start your computer in safe mode then try installing the driver manually that way, then reboot your PC normally.
Registry solution if you want to try it as long as you understand Windows Registry
1. Go to the Registry Editor click Start > Run > and type in regedit then hit Enter
2. Expand the folder location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
3. Find EEC5AD98-8080-425f-922A-DABF3DE3F69A in the folder list and click on it, this should say Portable Devices in the right window
4. See if it contains a value called UpperFilters if so delete it
5. Before you delete it though make a backup of the EEC5AD98-8080-425f-922A-DABF3DE3F69A folder, right click on it and Export to a folder just in case you need to restore it.
6. To restore the key if you need to just go to the folder where you exported it to and click on it to install
Click to expand...
Click to collapse
Sorry for the late reply, ive been busy.
There is no UpperFilters value, and unfortunately the troubleshoot didnt resolve the problem.

CheeseJuggernaut said:
Sorry for the late reply, ive been busy.
There is no UpperFilters value, and unfortunately the troubleshoot didnt resolve the problem.
Click to expand...
Click to collapse
You are having a problem with this aren't you.
If you have Kies installed uninstall it also plug in your phone and find it in the list of USB Devices, then right click select properties and uninstall the driver, unplug the phone and reboot your PC.
Once rebooted Temporarily turn off any firewalls and Anti Virus scanners and try the below
Install Kies 3, start Kies and check for updates, if there are any updates then install them.
Restart Kies 3 after any update, once its running plug in your phone and let the drivers install
If its worked properly Kies will see it, if not then check the USB devices and try to install the driver manually again
Don't forget to use the USB cable that came with the phone

ag4751 said:
You are having a problem with this aren't you.
If you have Kies installed uninstall it also plug in your phone and find it in the list of USB Devices, then right click select properties and uninstall the driver, unplug the phone and reboot your PC.
Once rebooted Temporarily turn off any firewalls and Anti Virus scanners and try the below
Install Kies 3, start Kies and check for updates, if there are any updates then install them.
Restart Kies 3 after any update, once its running plug in your phone and let the drivers install
If its worked properly Kies will see it, if not then check the USB devices and try to install the driver manually again
Don't forget to use the USB cable that came with the phone
Click to expand...
Click to collapse
Unfortunately this hasnt worked. As always I plug my phone in (while unlocked) and nothing happens exept for the notification on my desktop about a usb device not recognised

CheeseJuggernaut said:
Unfortunately this hasnt worked. As always I plug my phone in (while unlocked) and nothing happens exept for the notification on my desktop about a usb device not recognised
Click to expand...
Click to collapse
I have run out of suggestions, your PC is just being difficult, I tried googling the problem but nothing really helpful there, but I did find this Link and a few people said it sorted it for them, have a look the solution for them was the links in post 18

ag4751 said:
I have run out of suggestions, your PC is just being difficult, I tried googling the problem but nothing really helpful there, but I did find this Link and a few people said it sorted it for them, have a look the solution for them was the links in post 18
Click to expand...
Click to collapse
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!

CheeseJuggernaut said:
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!
Click to expand...
Click to collapse
Are you using the OEM cable?

Rapunzl said:
Are you using the OEM cable?
Click to expand...
Click to collapse
Yes, and ive tried other cables. Its a problem that is most probably hardware though

CheeseJuggernaut said:
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!
Click to expand...
Click to collapse
Take the original USB cable as well so they can try another one against yours just in case it a faulty cable