Database Develop

USB Device not recognized

I've searched and tried everything I found but my phone just can't be read as a Mass Storage Device....which means I can't transfer any files.
When I plug the phone in the USB debugging icon shows up on the phone but the option to transfer files isn't there. And on the computer it says USB Device not recognized and it's listed as an Unknown Device.
What I've tried so far is uninstalling the driver completely and plugging the phone back in....some sort of software automatically installs itself whenever I do this. However it still doesn't fix the problem. Also, I've downloaded some drivers from the internet but when I try to "Install driver from specific location" and direct it to the folder, it says there was no updated drivers found.
Help

Here you go
Try searching http://forum.xda-developers.com/showthread.php?t=595150

[Q] Windows 7 ADB Drivers / App restores w/o root?

I'm looking to port app restores - mostly game saves - from my old phone to the Droid Turbo. I've used Helium in the past but I can't get the Turbo to connect to Windows 7 yet. I've been trying to use the drivers linked from the Helium URL and here, but without success.
Anyone have luck tracking down USB drivers?
Any suggestions other than Helium?
Update:
Looks like the Motorola drivers started working as soon as I posted this (of course...).

This one was driving me nuts the last two days. On Win8.1 x64, the driver wouldn't auto-load when the device was plugged in. Until I saw your edit reason, I didn't even think to go through the manual device list and select the driver manually. "ADB Interface/Mot Composite ADB Interface" worked for me, as well.
Also, if you change your USB Storage mode on the phone, it may also change how the ADB Interface is detected. I had to manually add the ADB Interface driver a second time when I turned on MTP mode for the USB Storage connection. I had had it previously disabled while trying to figure out the ADB issues, once I had ADB working, I re-enabled MTP and subsequently Windows "forgot" the ADB device driver again.

For others: I had to go through the device manager, pick the unknown adb device and update drivers, pick drivers, select the clockworkmod section on the left and instead of mot composite I had to use the first option, android composite adb interface. Now my mtp connection works. Haven't tried reconnecting yet so it may well forget the drivers again, but at least I know what to do now!

Need the drivers from google sdk kit. Just google search installing adb drivers. I used helium fine.

MTP & "Nexus 6" drivers won't install...help?

Hey guys, weird stuff going on here.
Downloaded the latest Android USB drivers as well as the SDK. When updating the device from the device manager, ADB drivers loaded fine, but MTP drivers and "Nexus 6" (camera mode) drivers will not install no matter what I try. USB debugging mode or not, no dice.
What I did find odd, is that when opening the android_winusb.inf file that was packaged in the latest usb drivers, there is no mention of a Nexus 6 phone inside - which explains why the drivers won't install See screenshots below.
http://i.imgur.com/qmgxwsd.png
http://i.imgur.com/9NGYxsR.png
I'm not sure if I feel comfortable "hacking" the inf file in order flash my phone, but maybe it would be ok Is this a screw up on Google's part or am I way off base here?

wfujay said:
Hey guys, weird stuff going on here.
Downloaded the latest Android USB drivers as well as the SDK. When updating the device from the device manager, ADB drivers loaded fine, but MTP drivers and "Nexus 6" (camera mode) drivers will not install no matter what I try. USB debugging mode or not, no dice.
What I did find odd, is that when opening the android_winusb.inf file that was packaged in the latest usb drivers, there is no mention of a Nexus 6 phone inside - which explains why the drivers won't install See screenshots below.
http://i.imgur.com/qmgxwsd.png
http://i.imgur.com/9NGYxsR.png
I'm not sure if I feel comfortable "hacking" the inf file in order flash my phone, but maybe it would be ok Is this a screw up on Google's part or am I way off base here?
Click to expand...
Click to collapse
I'm having similar issues, laptop running win 7 can't see Nexus 6, DL'd drivers, even tried Motorola for drivers but although showing in device manager as installed no connection

At least they installed for you. The drivers don't even recognize my device. I still get a yellow Nexus 6 in device manager with no usable connection. Ugh...
Sent from my Nexus 6 using Tapatalk

Seems to be a lot of this going around. I'm on win 8.1. I couldn't get the drivers to work via the sdk. Then I tried the Google and Motorola drivers. After deleting the devices on device manager I finally got the N6 to connect via mtp. However, I can't the computer won't connect via mtp if USB debugging is on. On top of that I can't get adb to even see the phone. I would suspect it's more of a Windows problem at this point. I need to do some more testing from another pc.
Sent from my Nexus 6 using XDA Free mobile app

Have any of you tried using Wug's Toolkit?
http://forum.xda-developers.com/showthread.php?t=2947452

Managed to connect via PTP eventually by uninstalling and reinstalling drivers, seems to work with PTP and USB debug on, but not with MTP

wfujay said:
Hey guys, weird stuff going on here.
Downloaded the latest Android USB drivers as well as the SDK. When updating the device from the device manager, ADB drivers loaded fine, but MTP drivers and "Nexus 6" (camera mode) drivers will not install no matter what I try. USB debugging mode or not, no dice.
What I did find odd, is that when opening the android_winusb.inf file that was packaged in the latest usb drivers, there is no mention of a Nexus 6 phone inside - which explains why the drivers won't install See screenshots below.
http://i.imgur.com/qmgxwsd.png
http://i.imgur.com/9NGYxsR.png
I'm not sure if I feel comfortable "hacking" the inf file in order flash my phone, but maybe it would be ok Is this a screw up on Google's part or am I way off base here?
Click to expand...
Click to collapse
This may not apply to you at all, but with the mess of Android drivers I have to install over time I've finally figure out a solution when something is not installing correctly. Did you try right clicking on the Nexus 6 (I'm assuming that has a yellow exclamation point) going to:
Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
I'm saying Portable Devices specifically because that's how my Nexus 6 shows up as (as an MTP device) in the device manager.

Use the universal naked drivers. I have multiple devices and the drivers don't cooperate with each other but since I installed the naked drivers I have had any issues.
http://www.xda-developers.com/andro...r-solves-your-adb-driver-problems-on-windows/
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339

I fixed it! Wug's toolkit didn't work, although I'm about to use it to unroot, lock, and return my phone to factory state since it has to be taken back to the AT&T store to be replaced due to a screen defect. Hope they don't freak out about the death star being scratched off, lol.
Anyway, oddly enough the problem is because I'm using Windows 8.1 N, which doesn't come with Windows Media Player or any of the media features. Installing the Media Feature Pack for N and KN versions of Windows 8.1 sorted it out. Installed, rebooted, done. I can now access the device in any mode and the device driver errors are gone.
So if anyone is having the same issue with Windows 8.1 N, download and install this: http://www.microsoft.com/en-us/download/details.aspx?id=42503
Reboot and enjoy!

thanks
EvanVanVan said:
This may not apply to you at all, but with the mess of Android drivers I have to install over time I've finally figure out a solution when something is not installing correctly. Did you try right clicking on the Nexus 6 (I'm assuming that has a yellow exclamation point) going to:
Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
I'm saying Portable Devices specifically because that's how my Nexus 6 shows up as (as an MTP device) in the device manager.
Click to expand...
Click to collapse
Same thing was going on with my nexus 6 and I tried what you said and updated everything. Now the MTP works. thanks

Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
Click to expand...
Click to collapse
Thank you so much ! MTP Works now. Hail to the king

EvanVanVan said:
Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
I'm saying Portable Devices specifically because that's how my Nexus 6 shows up as (as an MTP device) in the device manager.
Click to expand...
Click to collapse
Ran into the same issue initially when I was trying to root my Nexus 6. Wug's didn't work, and neither did the naked universal drivers. Added the Nexus 6 ID to the inf and still didn't work.
Had to install the Motorola driver kit, and then go through the drivers as above to find a Motorola that finally worked; while the Motorola driver is just a wrapper for some Microsoft driver that normally comes built into Windows since Windows 7.

Nexus 6 Driver (ADB, Fastboot and MTP) for Windows and MAC
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac-68355/
I discovered the following troubleshooting tip listed below (amongst others) at the website above. It worked flawlessly with my brand new unlocked stock Motorola NEXUS-6 (XT-1103) and Windows-7 PC. Thank you and big props to the developer(s) who posted it!
1.Connect your Nexus 6 to computer with a USB cable and open Device manager on your computer.
2.Look for ‘Android Composite ADB Interface‘ entry, right-click and select uninstall from the context menu.
3.In the uninstall pop-up that appears, tick ‘Delete the driver software for this device’ checkbox and press the “Ok” button.
4.Disconnect your phone from your computer.
5.Disable USB debugging on your Nexus 6 from Settings » Developer options » un-tick ‘USB debugging’ checkbox.
6.Put your Nexus 6 in MTP mode (It should be in MTP by default unless you selected the Camera (PTP) mode).
7.Connect your Nexus 6 to the computer again, and let the computer re-install drivers automatically. If it doesn’t re-installs driver, try toggling the ‘USB debugging’ option on your device.

Same here. Nexus 6 stock lollipop 5.1.1 with unlocked bootloader. I thought it was my personel windows 7 pc. But no its any pc I try to connect to. Found that out because I work at a big business full of windows pc's. I remember at one point not having this problem at all. Don't know if it was before one of the lollipop updates but I remember I used to connect my phone at work on any pc the pc would automatically open MTP asking me what I wanted to do. That was without adb turned on. I've tried everything searched everywhere, installed,uninstalled drivers from Google, Motorola etc. Even tried wugfresh's instructions. My pc does not recognize my phone at all. Mtp, Adb, Fastboot, nothing. Weird thing is I also have a nexus 5 and as soon as I connect it its recognized. Don't know if it maybe the cable that's the only thing I haven't tried since my cables are not Motorola cables, or nexus 6 original cable as that is the way I bought it. But it used to connect. Now I'm stuck, at a loss. Don't get it, called Motorola, Google, T-Mobile. I think they know nothing about phones as when I tell them the problem they look at me like I'm talking Chinese. If anyone knows what the problem is and have been able to fix it please hit me up @ [email protected] Just about to give up. I just don't understand what the problem maybe. Running stock lollipop 5.1.1 with unlocked bootloader never rooted. Thanks and hope someone can help.

I had the same issue. I installed the latest google drivers from the Android SDK and my computer would not recognize my Nexus 6. I couldn't use fastboot or anything. I was able to fix this though. With my Nexus 6 hooked up to my computer, I opened device manager. There was the "unknown device" which was my Nexus 6 obviously. I right clicked on it and attempted to install the driver, the automatic driver installation method could not find it. I had to point it directly to the file. The file is located in the android-sdk files. I had to point it to c:/android-sdk/extras/google Obviously location will vary depending on where you installed the android-sdk. Just make sure to only point it to extras/google. I wen't further in the first attempt and it didn't work. I hope this helps. I suck at explaing stuff.

Long Island NOOBIE said:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac-68355/
I discovered the following troubleshooting tip listed below (amongst others) at the website above. It worked flawlessly with my brand new unlocked stock Motorola NEXUS-6 (XT-1103) and Windows-7 PC. Thank you and big props to the developer(s) who posted it!
1.Connect your Nexus 6 to computer with a USB cable and open Device manager on your computer.
2.Look for ‘Android Composite ADB Interface‘ entry, right-click and select uninstall from the context menu.
3.In the uninstall pop-up that appears, tick ‘Delete the driver software for this device’ checkbox and press the “Ok” button.
4.Disconnect your phone from your computer.
5.Disable USB debugging on your Nexus 6 from Settings » Developer options » un-tick ‘USB debugging’ checkbox.
6.Put your Nexus 6 in MTP mode (It should be in MTP by default unless you selected the Camera (PTP) mode).
7.Connect your Nexus 6 to the computer again, and let the computer re-install drivers automatically. If it doesn’t re-installs driver, try toggling the ‘USB debugging’ option on your device.
Click to expand...
Click to collapse
This didn't work the first or second time. I did steps 2 through 7 3 times and then it worked. I must have had a lot of drivers installed.
So if it doesn't work the first time, keep uninstalling the drivers and try again and again. Worse case scenario, you have to install the drivers again. hope this helps.

I want to add my own tale to his thread with the hope that it will help someone. I could not see the Nexus 6 when I set MTP mode or MIDI mode. The phone showed up on the PC when I selected PTP (camera) mode. In my case, I had four external USB3 hard drives connected. I finally turned off the hard drives and then MTP mode would be visible, both as a Portable Device, named Nexus 6, in the Device Manger, and as the same under My Computer in Windows Explorer. After Imy PC recognized the Phone in MT mode, I tuned on the external drives and all were visible.

Driver issue

Hi all,
First a quick info:
The Problem -- Nexus 6 internal storage doesn't show up when connecting to my main desktop computer.
I have had my Nexus 6 for almost a year now and since the beginning I couldn't make my main computer to recognize the phone's internal storage.
Whenever I connected the phone to another computer, the driver installed just fine and I was able to access the internal storage.
I previously had a first gen moto g and I thought the problem was because the moto g drivers were causing some mess with the Nexus so I uninstalled the old drivers and plugged my nexus so windows automatically downloaded what is shown as "Google Nexus ADB Interface" under Android device in Device manager.
I also have installed Android SDK tools in my PC since I had the Moto g and I cant remember how many times I have updated it. The Google driver is shown as installed.
The device is unlocked but not rooted.
Here comes the weird part... If I have USB debugging enabled then I can see the camera files in my PC when I choose PTP in USB configuration. However.. if I disable USB debugging then I can't even see the pictures.
I have tried selecting PTP and changing back to MTP as suggested in some threads with no luck.
I also tried turning the device off and then boot into fastboot, then plug the phone into the computer as this worked in some other computer.
This is driving me crazy, I know this is a computer related problem but I don't know what else to try.
Could you help me please?
Thanks

adrek09 said:
The Problem -- Nexus 6 internal storage doesn't show up when connecting to my main desktop computer.
Whenever I connected the phone to another computer, the driver installed just fine and I was able to access the internal storage.
Click to expand...
Click to collapse
www.wugfresh.com
Install the Nexus Root Toolkit on your PC.
In a sub directory of that kit you will find several usb drivers. Do some trial and error with those drivers.

NLBeev said:
www.wugfresh.com
Install the Nexus Root Toolkit on your PC.
In a sub directory of that kit you will find several usb drivers. Do some trial and error with those drivers.
Click to expand...
Click to collapse
Hi, thanks for the reply,
I forgot to tell that I tried that one too.
I followed the driver installation guide step by step with no luck.
Tried the recommended solution at step 3 of the guide and since it didnt work then I tried the manual installation with a couple "Bluetooth Peripheral Device" devices that are shown under Other Devices in Device manager

adrek09 said:
Hi, thanks for the reply,
I forgot to tell that I tried that one too.
I followed the driver installation guide step by step with no luck.
Click to expand...
Click to collapse
Because it works on a different PC. I assumed a driver issue.
My Suggestion is to install the driver manually.
Open the device manager.
After connecting you must see a change in the device manager. If not change USB-port and/or cable. And change on the Nexus 6 the charging
mode to data mode.
When still no 'internal storage' back to device manager and update the driver by right clicking. Try automatic and search on my computer - navigate to the drivers in NRT.

[Q] cant connect to pc in linux or windows

hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!

Nobody knows why? I have oem unlock "on"
debugging "on"
But I cant get my comp to see the device..Have Samsung drivers installed. Still no luck.
How can I fix this? all it does is charge when I hook it to pc but can't transfer files.

sorry double post

Same issue here. I've had no luck sorting it out.

Gutterball said:
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Click to expand...
Click to collapse
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.

ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
What the USB configuration is set to is actually moot. When the device is plugged in to a PC the tablet will bring up a notification stating what mode the USB port is in and also provide the option to change that to MTP mode (Transfer files), provided the drivers are correctly installed and all is in working order. By changing USB configuration to MTP the tablet shows up immediately on the PC but you still have to switch to "Transfer file" mode before you can move files between devices. Either way the results are the same and it takes the same number of steps. I always leave my USB configuration in "System Default" and I have never had any issues.

ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?

Gutterball said:
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Click to expand...
Click to collapse
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?

ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.

I
BillTheCat said:
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
Click to expand...
Click to collapse
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.

ashyx said:
I
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
Click to expand...
Click to collapse
Well, I'll be dipped in $hit.
What's the probability that one guy could have three dodgy USB cables? Used one, wiggled it around and the PC recognized the device. Looks like I'm in for a quick trip to WallyWorld. Thanks!

ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!

Gutterball said:
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Click to expand...
Click to collapse
Are you able to connect to the device in TWRP, either ADB or MTP?

ashyx said:
Are you able to connect to the device in TWRP, either ADB or MTP?
Click to expand...
Click to collapse
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?

Gutterball said:
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Click to expand...
Click to collapse
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.

ashyx said:
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
Click to expand...
Click to collapse
screenshot is in the attachment.