Question Pixel 7 Pro USB connection to MS Windows File Explorer - Google Pixel 7 Pro

I can't seem to get my Pixel 7 Pro to communicate via USB to Windows 10 x64 File Explorer. Under no circumstances does Windows File Explorer recognize the Pixel. Have gone through all the driver and change cable steps. My prior LG V35, Samsung Note 10 5G, and older Nexus 6P connect to my computer. Not the new Pixel Pro 7. PTP mode also doesn't work either. Have tried different ports and cables. Do see that Pixel is charging and do hear the PC da-ding when I plug it in via the USB and when I change the drop down mode to file transfer, but the Pixel does not show up in Windows File Explorer, yet I can see the V35, Note 10, and Nexus. Finally, went into settings and permanently set USB mode to file transfer so I didn't have to change it every time I connected the Pixel.
I also loaded, then unistalled, then reinstalled the latest Google ADB Windows drivers and set Pixel USB debugging to on. But no go. Do see that ADB does show up in Windows Device Manager.
Thought this issue was a thing of the distant Nexus 6P past, but, I've run into this again (on a newer different PC, too).l and remember what a pain that was to get to work. Frustrating, as I just wanted to copy some music files from my PC to the Pixel (yes, I know I can use Google One Drive).
It should not be this hard. Anyone run into this? Any ideas?

Hi,
Tried this already?
[GUIDE] Fix MTP driver installation on Windows 10
Hi guys and girls... I just recieved my new phone a few days ago. Plugged it into an old Windows 7 x64 laptop and Windows instantly updated the driver. On a 2016 Dell E7450 Windows 10 x64 laptop... It didn't. Tried the Google USB drver package...
forum.xda-developers.com
Good luck,
Sébastien.

Yes, thank you. I had found that thread and tried it. Did not work. Can try it again, maybe clean other drivers ahead of the retry (do prefer not to uninstall the LG and Samsung drivers, but maybe they are creating conflicts; however, the Nexus works with the new Google Drivers). I did leave the PC with latest Google drivers installed.

check out the post(URL) on the bottom here...
it had a great idea of doing the little known & thought-of "show hidden devices" option -- it is explained in more detail by him in the post. You might find some of the issue there.
Also, I think there's a better way to make sure you are using a particular driver vs. whatever generic one Windows looks for; I talked about it in below's quote
(make sure you have google's windows usb drivers downloaded & extracted so you know where to find the .inf file to point to and use; OFFICIAL most up-to-date google windows usb drivers can be found HERE )
simplepinoi177 said:
{after right-clicking driver and selecting "update driver" and clicking on "Browse my computer for drivers"...}
....Also, I found more/most success by clicking "Let me pick from a list of available drivers on my computer", clicking "Have disk", and finding the .inf file to get the exact driver than doing the "Browse" and "Next", because that tends to have Windows just keep with the driver that is already applied and kinda only looks to see if the driver version number is less than the version number given in the folder...;
Click to expand...
Click to collapse
June 20, 2023 TQ3A.230605.012.A1 Verizon/MVNOs / June 13, 2023 TQ3A.230605.012 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com

Hi,
What about device manager? Is it recognized?
Good luck,
Sébastien.

Try installing these Google USB Drivers:
8.29 MB file on MEGA
mega.nz
Also, make sure you set your internet connection to private not public because if it's public, sometimes Windows might not download the required drivers.
Go to Settings > Network & Internet > WiFi or Ethernet, then click on the connection and change it to Private then go to Windows updates and perform all the updates including optional ones which might be drivers

Okay, have been working on this for hours.
-Do see all my phones in Device Manager via ADB phone:
(Android ADB Interface and/or Android Composite ADB Interface).
-Correct myself in that neither the Nexus 6P nor the Pixel show up in Windows File Explorer.
-Did remove LG, Samsung, Fastboot entries.
-Did still hear the Winders sound when I change USB modes or turn on ADB.
-Did install the Version 11 Android USB Drivers. Later I updated to V13.
-Did remove then read Windows USB drivers via Android Studio.
-Did go into Device Manager, showed hidden USB and Android and removed grayed out USB entries. Reconnected phone.. ADN entries showed up but moved a bit in Device Manager Categories (LeMobile and Android).
-Keep checking that File Transfer MTP is set. Fiddle with ADB on/off.
-File Explorer still quiet as far as Google Android Phone or Pixel, but, LG and Samsung show up (despite that I uninstalled their drivers - I assume windows added support at some point).

you should have just downloaded the .zip file that had the usb drivers here (https://dl.google.com/android/repository/usb_driver_r13-windows.zip).
At any point did you directly point and an .inf file to load the driver? just because you uninstall drivers doesn't mean that when you reconnect the phone/device, windows will point the the new or correct driver; usually windows keeps a memory or repository of drivers of a specific version to refer to -- so if that driver isn't doing the proper handshaking to your phone/device, no matter how many times you uninstall the driver, windows will keep referring to the same driver that doesn't work when you reconnect. You have to specifically "update driver" and point it to the folder, or better yet specifically the .inf file, to change windows pointing to the correct and/or newer driver.
hope this helps...

-Yes, have tried both methods and keep getting the 'You already have the latest driver installed'.
-Pointed to Android 'USB Drivers' directory.
-I do see 'Pixel 7 Pro Hands-Free HF' in 'Systems Devices' portion of device manager.
-Still nothing in File Explorer.

@tonyo123 Have you tried rebooting both the computer and the Android devices?
To confirm: when you are connected to the computer, do you get an item in your notification shade (it could be silent/at the bottom) that lets you choose USB mode, and you can select MTP mode there? I assume yes due to:
tonyo123 said:
-Keep checking that File Transfer MTP is set. Fiddle with ADB on/off.
Click to expand...
Click to collapse
If that works, you can also go to Developer Settings and choose the default USB mode, if you prefer it to always default to MTP mode.
Good luck!

-Yes, I've got it set to default file transfer mode. And turn notification shows up letting me know of that in case I want to change.
-Have rebooted too many times to count

Try and old USB 2.0 port, if you have one on the computer.

tonyo123 said:
-Yes, I've got it set to default file transfer mode. And turn notification shows up letting me know of that in case I want to change.
-Have rebooted too many times to count
Click to expand...
Click to collapse
I know this sounds silly and you've probably already tried it, but while connected, try changing to a different USB selection on the phone, and then back to MTP. Does PTP mode work? I'm guessing not, but worth finding out.

Thank you all. It’s been a while since I've rooted my phone (last version was a mid vintage Note), but, I appreciate that I come here to XDA Developers and many of you are willing to help .
TonikJDK said:
Try and old USB 2.0 port, if you have one on the computer.
Click to expand...
Click to collapse
I will search pc to see if I can locate a USB 2.0 port and proper cable . I have been using usbc to usbc.

Funny enough, I'm having the same issue as of 15 mins ago, after connecting it fine previously.

Not silly. Yes I have been back and forth trying the different USB connectivity modes. One of the first things I did. The pc recognizes the change (I get the USB connect/disconnect sound), but the Pixel doesn't show up in Explorer Only ADB seems to connect properly. Really, I am just trying to enable USB file transfer without having to resort to the slower cloud. Of course with Nexus and Pixel I can't use an SD card to move the files either.

Get VMware Player, install Windows 10 inside of it, and use the Shared Folders function in settings to share your MP3 folder.
Your other option is to try Linux, which tends to handle Android phones quite well out of the box, or reinstall Windows...
EDIT: I just tried it and like every other Android phone I've ever had, I didn't have to install a driver to get it to pop up in Windows after putting it on file transfer mode so something is broken on your Windows installation.

EtherealRemnant said:
Get VMware Player, install Windows 10 inside of it, and use the Shared Folders function in settings to share your MP3 folder.
Your other option is to try Linux, which tends to handle Android phones quite well out of the box, or reinstall Windows...
EDIT: I just tried it and like every other Android phone I've ever had, I didn't have to install a driver to get it to pop up in Windows after putting it on file transfer mode so something is broken on your Windows installation.
Click to expand...
Click to collapse
I'm having the exact same issue after transferring all my stuff over 30 mins ago now on the same computer. Have tried an osx laptop and a standard one now with the same results.

Kylewolf said:
I'm having the exact same issue after transferring all my stuff over 30 mins ago now on the same computer. Have tried an osx laptop and a standard one now with the same results.
Click to expand...
Click to collapse
I mean it's certainly possible it's a bug, wouldn't be the first bug that ever affected USB file transfers, it just seems odd to only have two reports with how popular this device is proving to be (I have never before seen a poll show over 60 people having a device on this site within 2 days of its release day before).

simplepinoi177 said:
you should have just downloaded the .zip file that had the usb drivers here (https://dl.google.com/android/repository/usb_driver_r13-windows.zip).
At any point did you directly point and an .inf file to load the driver? just because you uninstall drivers doesn't mean that when you reconnect the phone/device, windows will point the the new or correct driver; usually windows keeps a memory or repository of drivers of a specific version to refer to -- so if that driver isn't doing the proper handshaking to your phone/device, no matter how many times you uninstall the driver, windows will keep referring to the same driver that doesn't work when you reconnect. You have to specifically "update driver" and point it to the folder, or better yet specifically the .inf file, to change windows pointing to the correct and/or newer driver.
hope this helps...
Click to expand...
Click to collapse
tonyo123 said:
-Yes, have tried both methods and keep getting the 'You already have the latest driver installed'.
-Pointed to Android 'USB Drivers' directory.
-I do see 'Pixel 7 Pro Hands-Free HF' in 'Systems Devices' portion of device manager.
-Still nothing in File Explorer.
Click to expand...
Click to collapse
you may not be doing the steps/directions I outlined because you wouldn't get the message "You already have the latest driver installed." You should get a "Windows has successfully updated your drivers" & "The hardware you installed will not work until you restart your computer" -- I attached the picture to show you.
{
"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"
}
That was my whole point, that by doing it in such the way that you are doing, you will be getting the driver that Windows merely defaults to, not necessarily the updated, proper, and specific/particular driver that actual Google intends for you to use for this purpose which is a specific/particular mode (i.e. some drivers have different modes like "MTP device", "ADB Device", "ADB Interface", etc). that you have to change & specify & intentionally select than Windows choosing for you.
tonyo123 said:
... My prior LG V35, Samsung Note 10 5G, and older Nexus 6P connect to my computer. Not the new Pixel Pro 7. ...
Click to expand...
Click to collapse
EtherealRemnant said:
I mean it's certainly possible it's a bug, wouldn't be the first bug that ever affected USB file transfers, it just seems odd to only have two reports with how popular this device is proving to be (I have never before seen a poll show over 60 people having a device on this site within 2 days of its release day before).
Click to expand...
Click to collapse
I'm certain it has to do with the multiple other devices he has installed drivers for. I will also quote the great @roirraW "edor" ehT's guide on the subject on his quintessential guide's Post #2, "Unlocking the Bootloader" section, step 10:
roirraW edor ehT said:
"NOTE: If you have USB drivers for other Android devices installed, like Samsung, they can alternately sometimes work and not work with Google Pixels. I recommend uninstalling those drivers, or at least updating that driver to Google's driver as instructed below (the Device Manager entry may be different with other OEMs)."
Click to expand...
Click to collapse
The "updating that driver to Google's driver" is specifically what I'm trying to directly do; not merely letting Windows choose whatever default driver (probably one set up for another device) for itself....

Related

Could someone post the Drivers of Asus TF300?

I can't get my pc to find my tablet because of windows 8, so i need the drivers seperetly. Then i try to intall them
AmirAli44 said:
I can't get my pc to find my tablet because of windows 8, so i need the drivers seperetly. Then i try to intall them
Click to expand...
Click to collapse
Windows 8 is not the problem, what you need are Asus drivers.......
Is there anybody who have the drivers?
AmirAli44 said:
Is there anybody who have the drivers?
Click to expand...
Click to collapse
See here http://forum.xda-developers.com/showthread.php?t=1697227 under Utilities.
Install Asus Sync on your PC, download the drivers and place in program files. You may have to manually install the drivers once the Asus is connected.
al89nut said:
See here http://forum.xda-developers.com/showthread.php?t=1697227 under Utilities.
Install Asus Sync on your PC, download the drivers and place in program files. You may have to manually install the drivers once the Asus is connected.
Click to expand...
Click to collapse
It still dosen't work
AmirAli44 said:
It still dosen't work
Click to expand...
Click to collapse
It took several goes for me to get the drivers installed.
I don't know if you need to start sync too - if so, do so from the tablet's settings first.
You might also need to experiment with the storage settings and remove an SD card if you have it mounted
Google for Connect Asus to PC and similar terms.
It does work, I promise.
PS
Try Airdroid app if you want to connect wirelessly and not via USB cable
al89nut said:
It took several goes for me to get the drivers installed.
I don't know if you need to start sync too - if so, do so from the tablet's settings first.
You might also need to experiment with the storage settings and remove an SD card if you have it mounted
Google for Connect Asus to PC and similar terms.
It does work, I promise.
PS
Try Airdroid app if you want to connect wirelessly and not via USB cable
Click to expand...
Click to collapse
I did make Asus sync Ok in the settings, and i installed it on the computer. It finds my tablet and it's possible to sync contacts and calender, I think. But I can't the the drivers to work the Mtp has a yellow warning sign! And when I try to update the driver it fails. I've uninstalled it to, still nothing works..
Sent from my GT-I9000 using Tapatalk 2
AmirAli44 said:
I did make Asus sync Ok in the settings, and i installed it on the computer. It finds my tablet and it's possible to sync contacts and calender, I think. But I can't the the drivers to work the Mtp has a yellow warning sign! And when I try to update the driver it fails. I've uninstalled it to, still nothing works..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Are the drivers actually installed? You need to select the tablet when connected to the PC and make sure that the drivers are installed. Under Device Manager, under portable devices (while Transformer is plugged in), you will see Transformer. Right click it and choose to update driver manually. Choose the location where you unzipped MTP folder of the download. This should update the windows driver then.
al89nut said:
Are the drivers actually installed? You need to select the tablet when connected to the PC and make sure that the drivers are installed. Under Device Manager, under portable devices (while Transformer is plugged in), you will see Transformer. Right click it and choose to update driver manually. Choose the location where you unzipped MTP folder of the download. This should update the windows driver then.
Click to expand...
Click to collapse
I did exactly what you said it doesn't update the driver. The Mtp gives error
Sent from my GT-I9000 using Tapatalk 2
Getting MTP failed on my machine :-S
Tired everythinggg
Resolved it this Way
AmirAli44 said:
I can't get my pc to find my tablet because of windows 8, so i need the drivers seperetly. Then i try to intall them
Click to expand...
Click to collapse
FOR EVERYBODY OVERLY [SOMETIMES SICKENINGLY] FAMILIAR WITH WINDOWS MANUAL DRIVER INSTALLS, HERE'S WHERE THOSE MTD DRIVERS ARE PUT BY THE ASUS SYNC FOR WINDOWS XP DOWNLOAD:
C:\Program Files\ASUS\ASUS Android USB Drivers\MTP
FOR EVERYBODY ELSE, READ ON:
Hey, had the same issue here, thinking it was the fact that ASUS is showing nothing past XP under their Windows downloads, so maybe a compatibility issue with their Sync setup (primarily, not copying the MTD drivers to the correct place during setup).
Having had MUCH WORSE issues with my fave little ol' Sansa Express MP3 player years ago when its battery died completely, I cracked my knuckles, sighed, and dug in for a long haul.
Luckily, I tried this first, since dealing with Windows version compatibility is much more common, so more familiar/easier.
(Of course, I was doing something different, but I'll be doing what you're doing, soon enough).
Download ASUS sync for your tabbie here:
https://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/#support_Download_17
Of course, it puts everything where it should, except the very important MTD files--but obviously ASUS included them--for me (32-bit Win7), they were HERE:
C:\Program Files\ASUS\ASUS Android USB Drivers\MTP
Plug your tablet to your PC via it's USB cable, wait for the Windows driver search to appear, then tell Windows to 'skip obtaining driver software from windows update'. Let it fail (that's where some of the best stuff begins!)
Go to Control Panel, Device Manager...open it.
As with some of the worst driver issues I've seen, I didn't see anything other than a single driver there--'ASUS Transformer Pad TF300T'' (see pic)--so I clicked 'Action' up top, then 'Add Legacy Hardware' (single-click something in the lower driver listings to enable this option), then 'Next', then 'Install the hardware that I manually select from a list', then 'Show All Devices'.
You don't have to wait for this list to populate--just click 'Have Disk', then 'Browse', then find the proper ASUS MTD driver at the location I described in this line above-->>>C:\Program Files\ASUS\ASUS Android USB Drivers\MTP
These will be annoying click-out submenus, but be patient--you're almost done.
Click through the rest, and you're done...NEARLY.
As is typical with this manual driver stuff (esp. storage drivers like this), I had to restart my PC to finish this driver install (and 'yes', I really did try and cheat Windows out of another 10 minutes of MY LIFE by running the ASUS Sync program on my PC, but it didn't work until rebooting).
Spoiler alert! (Upon reboot, it worked)
[ahem]
Upon reboot, it worked. I ran ASUS Sync, and [finally!!!] am seeing it recognized my tablet as what it is, and life began again after my millionth+6 Windows driver issue. (PLEASE remind me to personally 'thank' Bill G. wherever I see him after death).
EPILOGUE:
Why ASUS failed to update its driver update page after Windows XP, I'll never know, this being a little harder than the ole 'Compatibility Mode' install route...but this worked for me, and despite this little stutter-step, I'll be reaping whatever benefits ASUS sync gives me, but honestly, it wasn't even what I needed to back up my Home Page settings on my TF300T in order to factory reset the thing, because, like some here, mine is performing MUCH slower than it should, even in Performance Mode (but, hey, I got mine from a local pawn shop, so--that's expected, y'know).
ENJOY! Hope this helps, most of the time I feel I've nothing to contribute here...XDA is WAY over my wittle head!
What's really odd is that, even after doing all this, my Device Manager driver listing for the tablet still looks like the attachment I posted here, yet the thing appears to be working fine. Double-clicking on the 'kicked-out' drivers shows 'Device Failed to Start'...this is probably because Windows isn't actually using the ADB and MTD drivers until immediately upon running the ASUS Sync application, though.
mikedenney said:
FOR EVERYBODY OVERLY [SOMETIMES SICKENINGLY] FAMILIAR WITH WINDOWS MANUAL DRIVER INSTALLS, HERE'S WHERE THOSE MTD DRIVERS ARE PUT BY THE ASUS SYNC FOR WINDOWS XP DOWNLOAD:
C:\Program Files\ASUS\ASUS Android USB Drivers\MTP
FOR EVERYBODY ELSE, READ ON:
Hey, had the same issue here, thinking it was the fact that ASUS is showing nothing past XP under their Windows downloads, so maybe a compatibility issue with their Sync setup (primarily, not copying the MTD drivers to the correct place during setup).
Having had MUCH WORSE issues with my fave little ol' Sansa Express MP3 player years ago when its battery died completely, I cracked my knuckles, sighed, and dug in for a long haul.
Luckily, I tried this first, since dealing with Windows version compatibility is much more common, so more familiar/easier.
(Of course, I was doing something different, but I'll be doing what you're doing, soon enough).
Download ASUS sync for your tabbie here:
https://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/#support_Download_17
Of course, it puts everything where it should, except the very important MTD files--but obviously ASUS included them--for me (32-bit Win7), they were HERE:
C:\Program Files\ASUS\ASUS Android USB Drivers\MTP
Plug your tablet to your PC via it's USB cable, wait for the Windows driver search to appear, then tell Windows to 'skip obtaining driver software from windows update'. Let it fail (that's where some of the best stuff begins!)
Go to Control Panel, Device Manager...open it.
As with some of the worst driver issues I've seen, I didn't see anything other than a single driver there--'ASUS Transformer Pad TF300T'' (see pic)--so I clicked 'Action' up top, then 'Add Legacy Hardware' (single-click something in the lower driver listings to enable this option), then 'Next', then 'Install the hardware that I manually select from a list', then 'Show All Devices'.
You don't have to wait for this list to populate--just click 'Have Disk', then 'Browse', then find the proper ASUS MTD driver at the location I described in this line above-->>>C:\Program Files\ASUS\ASUS Android USB Drivers\MTP
These will be annoying click-out submenus, but be patient--you're almost done.
Click through the rest, and you're done...NEARLY.
As is typical with this manual driver stuff (esp. storage drivers like this), I had to restart my PC to finish this driver install (and 'yes', I really did try and cheat Windows out of another 10 minutes of MY LIFE by running the ASUS Sync program on my PC, but it didn't work until rebooting).
Spoiler alert! (Upon reboot, it worked)
[ahem]
Upon reboot, it worked. I ran ASUS Sync, and [finally!!!] am seeing it recognized my tablet as what it is, and life began again after my millionth+6 Windows driver issue. (PLEASE remind me to personally 'thank' Bill G. wherever I see him after death).
EPILOGUE:
Why ASUS failed to update its driver update page after Windows XP, I'll never know, this being a little harder than the ole 'Compatibility Mode' install route...but this worked for me, and despite this little stutter-step, I'll be reaping whatever benefits ASUS sync gives me, but honestly, it wasn't even what I needed to back up my Home Page settings on my TF300T in order to factory reset the thing, because, like some here, mine is performing MUCH slower than it should, even in Performance Mode (but, hey, I got mine from a local pawn shop, so--that's expected, y'know).
ENJOY! Hope this helps, most of the time I feel I've nothing to contribute here...XDA is WAY over my wittle head!
What's really odd is that, even after doing all this, my Device Manager driver listing for the tablet still looks like the attachment I posted here, yet the thing appears to be working fine. Double-clicking on the 'kicked-out' drivers shows 'Device Failed to Start'...this is probably because Windows isn't actually using the ADB and MTD drivers until immediately upon running the ASUS Sync application, though.
Click to expand...
Click to collapse
I've tried all of this. But still I cannot get Sync to work. In my 64-bit Windows 7 device manager I have it listed as portable device.
I can copy files to and from it in my Explorer. I have no devices that have not been properly installed anywhere in my list. So what to do now?
When life sucks, contact a competent Google Dev
martijn12345 said:
I've tried all of this. But still I cannot get Sync to work. In my 64-bit Windows 7 device manager I have it listed as portable device.
I can copy files to and from it in my Explorer. I have no devices that have not been properly installed anywhere in my list. So what to do now?
Click to expand...
Click to collapse
Tried this guy's download yet?
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Found him a while after posting here; man, did it ever work for me (and like you, I'm running Windows 7 64-bit, so.....).
Hope it works--best of luck, like I said, I'm in knuckles deep already here!
mikedenney said:
Tried this guy's download yet?
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Found him a while after posting here; man, did it ever work for me (and like you, I'm running Windows 7 64-bit, so.....).
Hope it works--best of luck, like I said, I'm in knuckles deep already here!
Click to expand...
Click to collapse
Even manually it cannot get windows to accept these drivers for the device.
Erasure
martijn12345 said:
Even manually it cannot get windows to accept these drivers for the device.
Click to expand...
Click to collapse
Have you tried going into your Windows 'Device Manager' and deleting ALL your old occurances of EVERY Android device there (making sure to check 'uninstall drivers' as well during this process)...then starting with that last link I sent cha, again (the universal ADB link)?
Try this--at some point, I was also forced to do this...maybe more than once.
That will be all I can say to help ya! Good luck!

[Q] Nexus/Android with Win 8 is a pathetic story

Hello
:crying:
I got my N5 today, and like my wife's N7 and my N10, NONE of them will show up on windows explorer (windows 8.1)
I can unlock, root, install custom recovery, all good, but as far as actually SEEING my device on the computer so I can drag and drop stuff, well, I literally have been spending almost a day trying to sort that out and have not got any closer at all. It is really pathetic.
I've changed the windows Unsigned drivers thing (though the drivers must be ok if I can do all that other rooting etc)
But yet when I uninstall the drivers to try installing them again, win8 says "Android ADB Interface. The third party INF does not contain digital signature information"
But I'm pretty sure that when I reinstall them AGAIN, I will still nto be able to see any of my Nexus devices on Windows explorer... despite them showing up in the Windows Notification under USB, and they are mounted there... I can UNmount them!
Something is way off kilter here, its with 3/3 devices, perhaps win8.1 is completly Android unfriendly, or?
Advice/help MUCH appreciated for someone who is going nuts here.
tx
Mark.
Did you turn MTP off to install the drivers to make sure ADB is working correctly? If so, did you check it to turn it back on? I am having no issues with Windows 8.1.
Same in Windows 7, I can't see my mates N5 on my Windows 7 machine but it's fine on his (he got the generic drivers from Windows update whereas I had mine from the Google SDK so that might be something to do with it?...)
It's just hit-or-miss. It's not Windows 8.
My work computer got a fresh image about 2 months ago. I've plugged other Android devices in, but haven't plugged in a Nexus device (or one that utilizes MTP the same way). I plugged in the N5 when I got it, and it worked flawlessly. My gaming PC at home has the Android SDK installed and it worked perfectly there. My HTPC does not have the Android SDK installed and nothing shows up in My Computer at all.
It's a weird android thing.
Hello guys,
lowandbehold said:
Did you turn MTP off to install the drivers to make sure ADB is working correctly? If so, did you check it to turn it back on? I am having no issues with Windows 8.1.
Click to expand...
Click to collapse
I did turn it iff to ADB but do not see where I would turn it back on, but that may be it with my N5...
EddyOS said:
Same in Windows 7, I can't see my mates N5 on my Windows 7 machine but it's fine on his (he got the generic drivers from Windows update whereas I had mine from the Google SDK so that might be something to do with it?...)
Click to expand...
Click to collapse
I really dont know. I have 4 PC's in the house, and sometimes my old dell laptop (also 8.1) seems to be the most reliably connect-able.
hotleadsingerguy said:
It's just hit-or-miss. It's not Windows 8.
My work computer got a fresh image about 2 months ago. I've plugged other Android devices in, but haven't plugged in a Nexus device (or one that utilizes MTP the same way). I plugged in the N5 when I got it, and it worked flawlessly. My gaming PC at home has the Android SDK installed and it worked perfectly there. My HTPC does not have the Android SDK installed and nothing shows up in My Computer at all.
It's a weird android thing.
Click to expand...
Click to collapse
There has to be a physical reason for it (unless we are to consider the metaphysical - past lives, re-incarnation of gadgets, Steve Jobs curses and stuff...) and it does amaze me that it still seems so hit and miss. When I first got onto android a few years back, you just plugged your phone into USB, ANY ONE ON ANY COMPUTER and whammo, you'd get both Ext SD adn Int SD mounted... reliably. I'm sure that was causing security and stability issues so all manufacturers seem to have snuffed that out.
so that MTP toggle is at settings > Storage > settings in storage
but it makes no difference still not vis in WinExplorer
Cheers
Mark.
Settings/Storage then hit the advanced menu button on the top right to enter "USB computer connection" and make sure MTP is checked.
lowandbehold said:
Settings/Storage then hit the advanced menu button on the top right to enter "USB computer connection" and make sure MTP is checked.
Click to expand...
Click to collapse
Tx mate, yeah I tried but alas, makes no diffs...
Thanks, but sadly this is a really abysmal part of android... and used to be a major + of the platform.
Mark.
fredphoesh said:
Tx mate, yeah I tried but alas, makes no diffs...
Thanks, but sadly this is a really abysmal part of android... and used to be a major + of the platform.
Mark.
Click to expand...
Click to collapse
I had this problem extensively, when trying to Root my Nexus, I went through uninstalling and re-installing drivers repeatedly, it was obnoxious, but i did end up getting it to work, so don't necessarily give up. I am running Win 8.1 though, eventually i had to go through Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers. (By booting windows into disabling secure driver certs.) Once i did that it gave me significantly more access, also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
ZeroAlphawolf said:
I had this problem extensively, when trying to Root my Nexus, I went through uninstalling and re-installing drivers repeatedly, it was obnoxious, but i did end up getting it to work, so don't necessarily give up. I am running Win 8.1 though, eventually i had to go through Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers. (By booting windows into disabling secure driver certs.) Once i did that it gave me significantly more access, also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
Click to expand...
Click to collapse
I must say, I did leave that part out of my replies. I too installed the raw drivers using Wugs toolkit. Maybe that is the x-factor.
Enable USB debugging in developer options.
Sent from my Nexus 7 using Tapatalk
Nexus Root Toolkit includes a variety of USB drivers you can try, as well as a few utilities to help you diagnose and fix android driver problems. That's where I would start. You don't need to use it to root or anything (unless you want to) but the driver utilities in the toolkit have fixed a number of problems I've had with android drivers over the years. I currently have my nexus 5 / 7 / galaxy working fine on two computers with windows 8.1
Not really the same at all but I had a hard time getting my S3 to be recognized on my computer at work running XP.
In the end the problem was the generic USB drivers that were installed had to be manually removed; even the official Samsung drivers wouldn't overwrite them. After a bit of digging and prodding I got it to work.
My Nexus was recognized without issue on my Win 8 machine.
You'll have to try a variety of different drivers to get it to show up properly. My N4 and Note 3 had no issues showing up, but the N5 wouldn't. I had to uninstall all the old drivers and started with brand new Google drivers to get the N5 to show up. Now it's there.
This happens to me every single time with a new device so I know exactly what to do now. It's not a driver issue, it's a problem with windows 8 and how it searches for drivers.
If you have the Android SDK installed properly just open up device manager > right click on android device > Update driver software > browse my computer > Let me pick from a list of device drivers on my computer > select the google adb driver from here.
Another problem I had was remembering to accept the ADB on my phones end, I never had to do that with my HTC one, so when going through rooting the raw drivers were likely unnecessary, I just hadn't noticed the primly on my phone when the first drivers I installed worked.
Hello guys, thanks for the various responses...
ZeroAlphawolf said:
Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers
--------also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
Click to expand...
Click to collapse
lowandbehold said:
I too installed the raw drivers using Wugs toolkit. Maybe that is the x-factor.
Click to expand...
Click to collapse
I did initially install the raw drivers as they sounded like they would be best... will try the camera toggle and MTP toggle
rabidfurball said:
I currently have my nexus 5 / 7 / galaxy working fine on two computers with windows 8.1
Click to expand...
Click to collapse
Encouraging!!! I know from my SGS3 and 4 and some generic chinese tablets ive had that the driver installation can be a major PITA but eventually you do the same thing for the 5th time, and it works, with no (seemingly) logical reason.
Stories said:
I had to uninstall all the old drivers and started with brand new Google drivers to get the N5 to show up. Now it's there.
Click to expand...
Click to collapse
I did a fresh install of windows 8.1 just yesterday... so it was pretty clean!
KiNG OMaR said:
It's not a driver issue, it's a problem with windows 8 and how it searches for drivers. If you have the Android SDK installed properly just open up device manager > right click on android device > Update driver software > browse my computer > Let me pick from a list of device drivers on my computer > select the google adb driver from here.
Click to expand...
Click to collapse
Yeah, i have tried that and it says I have the best drivers already installed. Oddly I can use Nexus Root Toolkit fine, so there has to be something right about the drivers... just not the part that shows up on a computer.
I'm convinced there HAS to be some scientific way of doing this, its such a common problem, it would be great to really figure it out. The problem is, one has to try 100 things before it works, so it becomes almost impossible to know which actions to attribute as the solution!
tx again,
Mark.
a solution - possibly useful...
Hello guys
Following Wugfresh's instructions to the T...
I tried drivers Option 1, (Universal) and the result was exactly as with the Raw (Option 4) drivers... So I uninstalled the drivers, ran ran USBDeview and uninstalled 7 devices like "Google Nexus ADB Interface" and "USB Composite device" and "Nexus 10".
Then tried Option 2.
The installation did not go exactly according to Wugfresh visual guide, so I cant be certain, but I do know that installingPDANET drivers only work if you select MTP, otherwise it will not find the tablet/phone.
After the instalation, the app called PDANET installed on computer, not on my tablet. My PC showed a pop up notification when tablet USB debugging is turned on, but again, it was not visible in windows explorer.
I then was going to try Option 4 again, and Uninstalled drivers in device manager WHILE I STILL HAD THE TABLET STILL PLUGGED IN, so I am guessing though PDANET uninstalled, the drivers remained (which I think is what Wugfresh's process would have done if it had run according to plan. I ran USBDeview and uninstalled the same 7 devices.
Then
Plugged tablet back in to attempt Raw drivers, but all of a sudden, the device was recognised and for the first time visible fully in Internet Explorer!
So basically it seemed to be the PDANET drivers that worked, though I have no idea if that would have worked had I tried these drivers in the first place.
I hope that helps someone!
Cheers
Mark.
OP, are you running W8.1 64 bits or 32 bits ??
I had my Sony Viao running W8 64 bits & hated it, downgraded to W7 64 bits and it's very happy getting along with Nexus 7 - going to play with N5 later on. Good old Dell Latitude is running W7 32 bits and it's my main machine to unlock, root & flash and so far so good - yet, I was reading about someone running Vista and had issues with the usb drivers.
I have 2 fully licensed W8 safely tucked away and the way it's looking, I might never get out of W7 - let alone then upgrading to 8.1 for free - getting reminders from $S a few things already.
Most of the time, the mess are caused by conflicting drivers installed & loaded - I keep a clean & lean desktop to do these bench work, and even though it is a PITA, starting clean with minimal programs (and apps) installed is often a good start - turn off antivirus & firewall, especially if connectivity is not needed - enabled access only if it is required and/or necessary.
I've also noticed that on my Nexus 4 I can only access adb in PTP mode, doesn't work at all with MTP enabled.
Hello guys
Letitride said:
OP, are you running W8.1 64 bits or 32 bits ??
Most of the time, the mess are caused by conflicting drivers installed & loaded
Click to expand...
Click to collapse
64 on the two PC's in the same room, HTPC's and laptop are 32 I think, but I have not tried them. I did a fresh Win 8.1 install on Tuesday and had no drivers from any devices other than the ones I manually installed with Wug.
KiNG OMaR said:
I've also noticed that on my Nexus 4 I can only access adb in PTP mode, doesn't work at all with MTP enabled.
Click to expand...
Click to collapse
Yeah, well try the PDANET (worked for me, though was my last resort as I don't like to install stuff that is a/ meant for something else, b/has some software I dont need that comes with it... but I did manage to keep the drivers and UNinstall PDANET software by keeping the tablet plugged in when I uninstalled PDANET... try it.
tx
Mark.

Z5C not connecting in USB debug mode

Hi everyone
I'm just about to give up on trying to connect my Z5 Compact to my Windows 7 x64 development PC – I hope someone here knows something else I could try. I've searched the web for hints and information all week, and tried every suggestion I could find. I rebooted both phone and PC countless times, tried different USB ports and controllers, reset the phone to factory settings, installed and re-installed all the drivers I could find, cleaned up the Windows drivers cache, but I still cannot get my phone to connect or show up in ADB.
The connection works perfectly fine if the phone is not in USB debug mode. It shows up in Windows Device Manager as "Xperia Z5 Compact", I can browse the file system from Windows Explorer, etc. However, as soon as I switch on USB Debugging, Device Manager shows the phone as a non-working device "E5823". All the drivers that are supposed to work with this device refuse to install. I tried the drivers that come with Sony PC Companion, the Z5 Compact drivers downloaded directly from Sony Developer World (version from November 13th), as well as the generic Google Composite ADB drivers that come with the Android SDK, which other owners of the Z5 report should also work. For all of these drivers, Windows tells me that they're not compatible with the E5823 device in question. I can force-install any of these drivers against Windows' warnings by selecting them manually, after which the device will show up as working properly in Device Manager, but I still can't do anything with it – it won't show up as a device on ADB, nor do I ever get the key authorisation on the phone that usually shows up when connecting in debug mode. On the same system, I can deploy to other Android devices fine, including an Xperia Tablet Z and a Z1 Compact (I removed those drivers to make sure that they're not the problem).
I'm on Windows 7 Enterprise x64 SP-1 and my Z5C is on stock firmware 32.0.A.6.152.
I'm at a loss at what to try next and would be grateful for any help. Thanks!
Daniel
Try this maybe from : http://stackoverflow.com/questions/...t-show-my-xperia-z-got-proper-drivers-and-all
In case anyone else is still looking for a solution, this worked for me:
Download the device drivers from here http://developer.sonymobile.com/downloads/drivers/
Open the device manager, check whether your device name (e.g. C6903) is listed under "Other devices". If so, right click on it and select "update drivers", and use the ones you just downloaded. Done!
The problem is that the device connects as two separate devices when usb debugging is enabled on the phone, and windows didn't recognize the "debugging device". So I had to install the appropriate drivers manually.
ricodredd said:
Open the device manager, check whether your device name (e.g. C6903) is listed under "Other devices". If so, right click on it and select "update drivers", and use the ones you just downloaded. Done!
Click to expand...
Click to collapse
Thank you for the reply! Unfortunately, this one doesn't work for me…
I'm not sure about the phone showing up as two devices, the only one I see appearing in USB debugging mode is the E5823 one. When trying to update its drivers, Windows reports that it can find no compatible drivers in the folder extracted from the driver download on the Sony website. The same is true for the drivers folder of PC Companion and the Android SDK USB driver folder.
If I force Windows to install the drivers from the Sony website (showing up as "Sony sa0113 ADB Interface Driver", the warning will go away and the device properties say it's functioning correctly. However, still nothing works; no device shows up in ADB and I get no key acception prompt on the phone.
Very strange. I hadn't tried this myself with my Z5 but I just did now with no problem. Driver from Sony Dev site (Android SDK driver didn't work for me).
{
"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"
}
Did you try enabling non-secure ADB via *#*#2673#*#*
Dunno what else might be causing this. Doesn't sound like your phone is encrypted - not that that would explain it either.
Sorry, I'm just a n00b at this.
Oh yeah, one last thing. Can you try on another PC? Maybe yours is messed up a little...
ricodredd said:
Oh yeah, one last thing. Can you try on another PC? Maybe yours is messed up a little...
Click to expand...
Click to collapse
Well, this turns out to be the problem! Thank you a lot for your suggestions.
I took to another PC to try the same thing, and the phone works fine using the Sony drivers. It shows up exactly as in your screenshot, under the "Sony sa0113" device category, got the key authorisation prompt and it immediately showed up in ADB.
I'm not sure where the problem with this first PC and USB is. It seems to be a software problem somewhere deep in the dungeons of Windows. The computer has two USB controllers with 4 ports each – I tried all of them, and several cables, which all work with other devices, but this phone simply won't register (and again, it's only in USB debugging mode that I have the problem, regular syncing and MTP file transfer work fine). So I would still be very appreciative of any hints, if anyone has ideas on what else I could try to fix it…
Thanks!
I'd definitely try properly removing possible conflicting drivers from your PC, like old Sony ones for a start. I use DriverStore Explorer [RAPR] to clear old drivers out.
Removing/uninstalling from Device Manager does not delete the files from Windows so if your Sony drivers are misconfigured somehow, they'll stay that way next time you reconnect your phone and Windows reinstalls them.
ricodredd said:
I'd definitely try properly removing possible conflicting drivers from your PC, like old Sony ones for a start. I use DriverStore Explorer [RAPR] to clear old drivers out.
Removing/uninstalling from Device Manager does not delete the files from Windows so if your Sony drivers are misconfigured somehow, they'll stay that way next time you reconnect your phone and Windows reinstalls them.
Click to expand...
Click to collapse
That's good to know. I was about to try the DriverStore Explorer, unfortunately I decided to go with another suggestion from someone at the office first, which was to reinstall the USB controller drivers.
He told me to remove the controllers from the device manager and reboot, at which point Windows would automatically reinstall them. Unfortunately, that didn't work, so instead of the USB controllers I now have to completely "unknown devices" which won't install at all. Windows doesn't find any drivers online or locally, and even the chipset and USB drivers that came with my mainboard don't work. So at the moment, not even my mouse and keyboard work anymore, and the only way I can currently control and try to fix anything at all anymore is by using TeamViewer on my phone as a keyboard and mouse replacement
It's probably safe to say that my mainboard is completely kaput at this point, and that this was most likely also the reason for the phone not working. I spent the entire afternoon today trying everything to get some USB functionality working again, without success. I don't think I have any other option than to replace the entire board now…
Yikes, that's a nasty tale! You should try a Windows repair install before scrapping the PC though. What have you got to lose?!
It's really just rather comical at this point. I figured out that I could at least get the mouse to work again by enabling USB Legacy mode in BIOS. The keyboard would still only work for the first few seconds on the Windows login screen though, and then just silently sign off. And the on-screen keyboard doesn't allow me to send the Ctrl+Alt+Del required to log in. All that doesn't really matter anymore now either though, because somehow after one of the last reboots my computer got kicked out of our network domain. Now it will only let me log in with a local administrator account anymore, to which I don't know the password. Every time I think it couldn't possibly get any worse... :silly:
At this point I don't think I can try anything anymore until I can get in touch with one of the guys administering the domain on Monday, because I can't even get close to accessing system restore from here. I'll actually just remove the hard drive and take it home with me, so I can at least access my files and work on my other computer...
Thanks for your help, I'll get back to this thread if after restoring my computer the phone still won't connect

Can't connect to PC for file Transfer

Brand New Unlocked S8+... Tried to connect it to my PC to use a previous copy of smart switch backup but it never connects.. Windows Explorer never displays a mounted drive either. Smart Switch Eventually comes back with Failed to connect to the device.
The Phone displays the "Attention The connected device is unable to access data pm this device. Reconnect the USB cable and try again...."
Phone is on Transfer Media files (MTP)
USB Debugging is one.
Device Manager says "Samsung Android Phone - SAMSUNG Android ADB Interface" two times - No red or yellow exclamations.
I've removed the software in device manager and restarted both the phone and the laptop multiple times.
I updated Smart Switch and did More\Reinstall Device Driver.
Does anyone else have any workarounds for this? I found one article (https://www.recovery-android.com/connect-samsung-to-computer.html) but still no success.
​
I actually have the exact same issue on windows 10. Anyone figured out a solution?
Doesn't seem like there is much help here on the 2 Samsung formums I posted on....
I know its not my windows profile as I have tried 3 different profiles as well as safe mode.
Tried 2 different sets of Samsung USB drivers and no improvement.
Like I said I had no issues on a windows XP machine or a windows 10. I didn't even need to install the USB drivers/Smartswitch on either of those machines.
We can't be the only 2 people!
Kalveitt said:
I actually have the exact same issue on windows 10. Anyone figured out a solution?
Click to expand...
Click to collapse
Firstly, i cannot give you direct answers.
Just my thoughts.
i have a S8+. No root stock as is.
I have Lenovo laptop Win 10.
From day one, out of box, i connected
S8+ and it connected. I can do whatever
i want. Transfer data, photos videos.
ADB etc
So it should work...?
However i do realize there are quite a few things to consider......
Samsung drivers on laptop and a few other
issues..... eg
For one,
have you enabled
in Phone /Settings /Developers Option /Usb debugging.?
Normally first time when you connect
With pc /laptop you should get
a small pop-up message(on device) to allow
phone to connect.?
(that's my experience, over years)
Good luck
Yes, USB Debugging is on and connection is set to MTP.
Windows recognizes "USB Android" but dosnt install the driver successfully.
It will appear as a modem in Device manager but nothing is mountable.
I have 2 desktop pcs with win 10. One with samsung software Kies 3 and smart switch installed and the other no samsung software. Both find the device Galaxy S8+, in device manager under universal serial device controllers i have Samsung Mobile USB Composite Device. You have an adb driver I think because you have usb debugging on, i would turn usb debugging off. The pc should find a device connected to the usb and download a driver, once done the device is recognised as galaxy S8+ in my case but will not communicate with the pc until the phone has given permission. On the phone will be a message asking you to allow the connection. Hope this helps ??
psuhbggrad said:
Yes, USB Debugging is on and connection is set to MTP.
Windows recognizes "USB Android" but dosnt install the driver successfully.
It will appear as a modem in Device manager but nothing is mountable.
Click to expand...
Click to collapse
Firstly i do understand that you
must be quite annoyed trying to figure
out issues. (I would) Thankfully i don't.
Bottom line is that it should work..!
My experience confirms, that S8+/laptop Win 10 works.... 100%when connected
However a few suggestions.
If you feel you checked all checkbox.?
However you never said anything
about popup notice ? granting premission
for device to connect.?
So device /laptop /pc is not "seeing" each other?
All Samsung devices I have used, first time connection gives me this popup a notice
Can't remember exact wording.
Something... eg
Device id 5786446.......
Have or does your other Samsung devices
connect etc.?
Have you tried connecting to a friend pc laptop.
An option is to go to a Samsung Care Center
and as them to test and connect.
My experience (in past) is that they should
assist you.
If it connects to friend pc or Service provider /Samsung Care Centre.
Then surely it has to be your pc/laptop?
So I turned off usb debugging and revoked the permissions on the phone, connected it to my PC.
Samsung Android (with a Yellow Exclamation) was already present in Device Manager under "other devices" so I uninstalled that.... and rescanned. My laptop attempted to reinstall but it generated a Driver Installation Failed message on "SAMSUNG_Android" - no driver found.
Device Manager once again shows the Yellow Exclamation Point
I would go on to Samsung support look up the phone and download the usb driver and install from the download. Good luck
I've downloaded the drivers from Samsung 2x.
psuhbggrad said:
So I turned off usb debugging and revoked the permissions on the phone, connected it to my PC.
Samsung Android (with a Yellow Exclamation) was already present in Device Manager under "other devices" so I uninstalled that.... and rescanned. My laptop attempted to reinstall but it generated a Driver Installation Failed message on "SAMSUNG_Android" - no driver found.
Device Manager once again shows the Yellow Exclamation Point
Click to expand...
Click to collapse
I can vaguely remember that i had this same
issues with my Note 5 and Win 10.
This was many months/year or two, ago.
I also had yellow exclamation etc.
Further in Device manager( laptop) kept installing wrong Samsung drivers.!
I uninstalled drivers/installed and battle for a few months like this Then one day Windows
did an update and in update i noticed
Samsung drivers included etc. (must have been correct)
Ever since that update i had no issues again.
Bottom line... some drivers issue?
Not S8 +?
Good luck
psuhbggrad said:
Brand New Unlocked S8+... Tried to connect it to my PC to use a previous copy of smart switch backup but it never connects.. Windows Explorer never displays a mounted drive either. Smart Switch Eventually comes back with Failed to connect to the device.
The Phone displays the "Attention The connected device is unable to access data pm this device. Reconnect the USB cable and try again...."
Phone is on Transfer Media files (MTP)
USB Debugging is one.
Device Manager says "Samsung Android Phone - SAMSUNG Android ADB Interface" two times - No red or yellow exclamations.
I've removed the software in device manager and restarted both the phone and the laptop multiple times.
I updated Smart Switch and did More\Reinstall Device Driver.
Does anyone else have any workarounds for this? I found one article (https://www.recovery-android.com/connect-samsung-to-computer.html) but still no success.
​
Click to expand...
Click to collapse
In the past I had this problem I downloaded USBDeview to my PC and deleted all of the old Samsung drivers, after rebooting the PC the phone was able to connect with the PC.
Tried USBDeview and removing the Samsung drivers but no difference
Still unable to connect.
I'm having this problem as well. I'm still trying to work it out, but when I remove and re-add the device through Device Manager I get this error: "An existing device was found that is a duplicate of the device being manually installed" and the device DOES connect as a camera, just not for full file transfer.
I had the same problem and tried many of the fixes, including different USB cables and different computers and different phones. I finally figured out that the case I had on the S8+ was the problem (at least for me). I took it off and everything works.
Hi, i have a pc with windows 10 . In device manager under universal serial device controllers i have Samsung Mobile USB Composite Device. i think you should meet best mobile shop.
jimmygarison said:
Hi, i have a pc with windows 10 . In device manager under universal serial device controllers i have Samsung Mobile USB Composite Device. i think you should meet best mobile shop.
Click to expand...
Click to collapse
I have Windows on Lenovo Laptop with latest Windows updates installed. Yesterday, I downloaded Samsung Smart Switch unlocked the phone and connected it to the laptop. Smart Switch found it immediately and I did a backup. I did not need to check Device Manager. It must be a drivers problem as mentioned above.
Note 8, getting "Attention The connected device is unable to access data pm this device."
And I am only able to see some files, Sammy is a crazy fool, this is basic stuff
installed the windows fall update a week ago now connect my phone to my laptop and nothing is recognised, no phone memory and no memory card just a empty space when i click the icon where my phone should be, i've had samsung drivers installed and they have worked fine so far till today, any ideas where to find the latest drivers? and what else i can do to get access to my phone on my laptop?
solution that worked for me
On my windows 10 PC, I opened device manager (open up start and just type 'device manager') and under portable devices there was a usb device called MTP USB device or something like that (I forget the exact name) with a small triange and an exclamation mark next to it. I clicked on that and then clicked "update drivers." When the prompt comes up I chose the automatically look for drivers option. This fixed the issue and now my Galaxy s8 is recognized (it no longer says MTP USB device or whatever it was). Hopefully this works for others as well. You can also probably download the usb drivers for the phone from samsung.

Can't connect Pixel and Windows 10.

When I plug in my pixel into my Windows 10 laptop, neither device responds. This means that I get neither the AutoPlay pop up on the laptop, or the USB option notification on the phone.
What I have tried:
Plugging into a Windows 7 laptop; the AutoPlay box appears on the laptop, the USB options notification appears on the phone
Tried all USB ports on the Windows 10 laptop.
Confirmed that other USB devices appear correctly on the Windows 10 laptop
Any thoughts?
Guidance?
tithij said:
When I plug in my pixel into my Windows 10 laptop, neither device responds. This means that I get neither the AutoPlay pop up on the laptop, or the USB option notification on the phone.
What I have tried:
Plugging into a Windows 7 laptop; the AutoPlay box appears on the laptop, the USB options notification appears on the phone
Tried all USB ports on the Windows 10 laptop.
Confirmed that other USB devices appear correctly on the Windows 10 laptop
Any thoughts?
Guidance?
Click to expand...
Click to collapse
Have you installed the latest fastboot and adb. If not download them here and make sure to add the folder containing the files in your path or unzip the files to your Windows directory. I had the same problem on Windows 10 when I was running it and that fixed it for me.
Check in Device Manager to see if the Android device is listed. If it's listed but is indicated as not having a driver loaded, you can always download the latest drivers from https://developer.android.com/studio/run/win-usb.html and the latest platform tools at https://dl.google.com/android/repository/platform-tools-latest-windows.zip.
Extract the drivers, right click the non-working Android entry in Device Manager, point it to the main folder you extracted the drivers into and see if it'll load the drivers. This may not be the problem but worth a try. Even if it doesn't solve it on Windows 10, try the same thing on Windows 7. Windows 7 may be too old that it won't automatically find the correct necessary driver like it should on 10.
tithij said:
When I plug in my pixel into my Windows 10 laptop, neither device responds. This means that I get neither the AutoPlay pop up on the laptop, or the USB option notification on the phone.
What I have tried:
Plugging into a Windows 7 laptop; the AutoPlay box appears on the laptop, the USB options notification appears on the phone
Tried all USB ports on the Windows 10 laptop.
Confirmed that other USB devices appear correctly on the Windows 10 laptop
Any thoughts?
Guidance?
Click to expand...
Click to collapse
Google search terms: Windows 10, Pixel driver, XDA yields this:
https://forum.xda-developers.com/pixel-xl/how-to/guide-fix-mtp-driver-windows-10-t3570625
Simple enough? Hope it works for you.
thanks, but no luck
@Misterxtc thank you. Already tried. No luck
 @oirraW the device does not appear in Device Manager.
 @bobby janow I am familiar with Google. Believe it or not, I even went to page 3 of the search. The solution you found has been tried and does not work.
Install Linux, no drivers to install, it just works
Some dumbed down versions you might have to do
apt install adb fastboot
You never have to reboot, only if new kernel, and that too is going to change
Sent from my Pixel using XDA-Developers Legacy app
tithij said:
the device does not appear in Device Manager.
Click to expand...
Click to collapse
Until you can get it to show up in Device Manager, there's nothing else you can do. Try a different USB port? Reboot the PC? Try a different cable if you have one? I can't think of anything else to try other than reinstalling Windows. I haven't had any trouble on Windows 7 or 10.
@piperx might be extending my tech skills a little too far. @roirraW "edor" ehT that is a pity.
Thanks all for your help; if I stumble across a solution, I'll post back.
tithij said:
@piperx might be extending my tech skills a little too far. @roirraW "edor" ehT that is a pity.
Thanks all for your help; if I stumble across a solution, I'll post back.
Click to expand...
Click to collapse
Where's your sense of adventure ,?
If you can use Windows you can use Linux ?
Sent from my Pixel using XDA-Developers Legacy app
clutching at straws but worth trying as tell the computer sees the phone and lists it you are stuck so enable developer options then enable usb debugging and set usb configuration to MTP then with the phone connected and the phone unlocked reboot the phone keeping the phone unlocked all the time.
piperx said:
Where's your sense of adventure ,
If you can use Windows you can use Linux
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
It's not the use of it, it's the installation of a dual boot that doesn't take up too much space.
I did go have a look, suggestions are Ubuntu or Mint. Would like the smaller one.
vickersg said:
clutching at straws but worth trying as tell the computer sees the phone and lists it you are stuck so enable developer options then enable usb debugging and set usb configuration to MTP then with the phone connected and the phone unlocked reboot the phone keeping the phone unlocked all the time.
Click to expand...
Click to collapse
I'll give it a whirl.
Have played with the developer options a bit, but to no avail.
tithij said:
It's not the use of it, it's the installation of a dual boot that doesn't take up too much space.
I did go have a look, suggestions are Ubuntu or Mint. Would like the smaller one.
Click to expand...
Click to collapse
Make a bootable USB of each distro you want to try. It's super easy with Rufus. This way you can try it without installing anything or wasting blank disks. I like Mint, it's basically Ubuntu with a face-lift.
No app needed to do simple things from command line ?
dd if=nameofiso of=/dev/sxx bs=4M; sync
Sent from my Pixel using XDA-Developers Legacy app
i'm not having much luck.. the device manager still either shows "pixel?" if the phone is set to no transfer.. or "MTP?" if phone set to file transfer... if I update drivers.. it says it tries then fails / had an error... any ideas?
@tithij You ever figure this out? I have the same problem I've even replaced the daughterboard but can't get the phone to show up in device manager when in bootloader mode.
GbizzleMcGrizzle said:
@tithij You ever figure this out? I have the same problem I've even replaced the daughterboard but can't get the phone to show up in device manager when in bootloader mode.
Click to expand...
Click to collapse
I haven't actually done anything to fix it except to upgrade my phone and laptop.
Phone is on Android 9
Windows enterprise is on 1709
Now when I plug the phone in, I get the options on the phone and laptop. I choose File transfer and it works.
Not really helpful. But sometimes it seems apathy solves all problems.
If Pixel phone on connecting to windows only shows up in File Manager when you choose PTP option in the Pixel’s USB Preferences (and disappears from Explorer when you select File Transfer), you will be restricted to the DCIM and photos directory, thanks to the miserable ADB Composite driver that keeps getting updated or installed for morons who can’t handle full drive access in their pixels. ADB and PTP were designed so idiots would not need to worry about anything other than their media directories on their Pixel phones.
For anyone above age 4, full access to the Pixel SD memory is preferred. To fix the above, it is necessary to ditch the ADB drivers and get the generic MTP drivers back instead in Windows. Here’s how I did it on a Pixel 4XL with android 12 or 13:
Unplug phone, make sure Developer’s Options is ‘on’ and that USB Debugging is ‘on’
Ensure that in USB Preferences, it is defaulted to File Transfer/Android Auto and NOT to PTP
In Windows, open Device Manager, View, and check ‘show hidden files’
Then, open View-Devices by Type-Portable and delete/uninstall your Pixel phone, all of them if there’s more than one.
Then start looking for anything that says Android or ADB, and delete every shred of anything that’s an ADB Driver interface, whether composite, USB, whatever. If it has ADB in it alone or under LeMobile or Acer, it’s got to go. Uninstall and delete them
Plug in phone
Under Device Manager-View-Devices by Type-Portable find your Pixel device. Right click and Update Driver. Then, click Browse My computer, then click Let Me Choose, and then click MTB USB Device… I picked the bottom-most one
That’s it, it should work

Categories

Resources