Related
Is anyone having issues mounting their tablet via USB. If I check off Camera (PTP) I get access to my photos in my Windows Explorer, but when I check off Media (MTP) windows acts like it doesn't exist. ADB can't see the tablet either, but once I check off Camera (PTP) ADB can see the tablet... I'm using a windows 8 computer, has anyone heard of this happening, or is it happening to any other computers?
I have no issue using MTP. Did you install the driver from google?
reubendevries said:
Is anyone having issues mounting their tablet via USB. If I check off Camera (PTP) I get access to my photos in my Windows Explorer, but when I check off Media (MTP) windows acts like it doesn't exist. ADB can't see the tablet either, but once I check off Camera (PTP) ADB can see the tablet... I'm using a windows 8 computer, has anyone heard of this happening, or is it happening to any other computers?
Click to expand...
Click to collapse
You have some old driver that is blocking access.
Use device manager to remove the device and driver then reboot and try again using the Google drivers.
http://forum.xda-developers.com/showthread.php?t=2391236
reubendevries said:
Is anyone having issues mounting their tablet via USB. If I check off Camera (PTP) I get access to my photos in my Windows Explorer, but when I check off Media (MTP) windows acts like it doesn't exist. ADB can't see the tablet either, but once I check off Camera (PTP) ADB can see the tablet... I'm using a windows 8 computer, has anyone heard of this happening, or is it happening to any other computers?
Click to expand...
Click to collapse
Yes. It is fairly typical. I had same issue on Windows 7 x64 and lived with it for a while.
Finally, I decided to fix it by uninstalling the drivers and reinstalling. It took about an hour after trying all sorts of tricks. There are tricks in quite a few threads here on xda. I'm not sure any one thread fixes every problem. So I found the solution was trial and error.
After messing with driver for a couple hours, serious waste of time, I got MTP working once. As a confirmation check I uninstalled the drivers once more and let the drivers reinstall on plugging in the device. It broke again, back to PTP. LOL
Not giving up, I tried again the next day and finally got MTP working again. This time I uninstalled drivers again, and the correct drivers reinstalled on device plug in. Since then everything has been great. I get both MTP and PTP working great.
I would try sfhub thread ideas and search around for a couple other ideas too. It will eventually work, but you have to isolate what exactly is the problem on your Windows 8 PC. Sometimes you are missing just one thing, sometimes Windows automatically messes with you.
Good luck.
I have no issues with Win7x64. Worked first time and every time since. Sorry...
PJ Clifford said:
I have no issues with Win7x64. Worked first time and every time since. Sorry...
Click to expand...
Click to collapse
Okay. I will try on my Windows 8 system later today. Interesting. Thanks.
Try disabling usb debugging, that worked for me on a windows xp machine having some problems as you
Sent from my Nexus 7 using xda app-developers app
popular mbnegul
i also noticed tonight that if u have usb debug on, u cannot connect as mtp
the moment u swith it off, it starts as mtp
Make sure you are using the usb cable marked Asus on one end that came with the Nexus 7. I had the same problem because I was using another usb cable. They are not all the same.
Anderson2 said:
Make sure you are using the usb cable marked Asus on one end that came with the Nexus 7. I had the same problem because I was using another usb cable. They are not all the same.
Click to expand...
Click to collapse
None of the other solutions worked, i'm going to try this on Monday, I'll bring in my ASUS cable to work... super annoying though...
I had a little chat with "ASHLEY" from Verizon's Live Chat. Apparently (and she told me this after i factory reset my phone) the marshmallow update is getting little patches so that everyone's phone is prepared... a little annoying since i almost got to installing but i had to take my phone off Wi-Fi for 6 1/2 hours while i was at school, and so the update i would've gotten was canceled by verizon or something... I even had downloaded part of it.
Just a little FYI.
Thank you for the update. I just picked up the phone. I deferred the update when I set up the phone and now I can't get the download back. Now, I most likely know why. I'll wait a day or two. If I can't get the update back, I'll hard reset the phone. Sighs...
Sent from my XT1585 using Tapatalk
Verizon's Twitter support just confirmed a hold on the marshmallow update. Any exact date then?
I had the OTA update notification on Friday but no wi-fi at work. Got home and the download failed and then got software up to date when checking on the phone. Plugged the phone into my pc Saturday night and the Verizon Wireless Software Update popped up saying an update was available. In less than 20 minutes I was good to go.
tonbonz said:
I had the OTA update notification on Friday but no wi-fi at work. Got home and the download failed and then got software up to date when checking on the phone. Plugged the phone into my pc Saturday night and the Verizon Wireless Software Update popped up saying an update was available. In less than 20 minutes I was good to go.
Click to expand...
Click to collapse
Except my device NEVER wants to pop-up on the software upgrade assistant, and it's on MTP mode. Any help with that? I'm on Windows 10 too.
cdowning22 said:
Except my device NEVER wants to pop-up on the software upgrade assistant, and it's on MTP mode. Any help with that? I'm on Windows 10 too.
Click to expand...
Click to collapse
Some have reported the the Verizon software update assistant works if you connect your phone to your pc/laptop via USB 2.0 -- but not USB 3.0. That didn't make a difference for me. We've got 3 Turbo 2's: two of them got both updates successfully OTA. One of them never got it OTA, and still gets nothing when we check for updates. I've tried connecting that third DT2 to my laptop and using the software update assistant - with the phone connected at different times to each of the 4 USB ports on my laptop (3 of them are USB 3.0, 1 is USB 2.0), and I've toggled MTP mode on and off, but no joy: the update assistant never recognizes the phone. However the laptop does, indeed, recognize the phone, and lets me open a file browser window and look at files on the SD card.
Only variable I'm not confident about here: when I connect the phone to the laptop, there's the typical Windows popup that asks what I want to do when this device (the phone) is connected to the laptop. Note: the update assistant is NOT offered: just typical options such as, "transfer media files to PC". Not sure which to accept, I've ignored that prompt -- wondering if perhaps I need to select one of these options in order to complete the MTP connection properly?
jonstrong said:
Some have reported the the Verizon software update assistant works if you connect your phone to your pc/laptop via USB 2.0 -- but not USB 3.0. That didn't make a difference for me. We've got 3 Turbo 2's: two of them got both updates successfully OTA. One of them never got it OTA, and still gets nothing when we check for updates. I've tried connecting that third DT2 to my laptop and using the software update assistant - with the phone connected at different times to each of the 4 USB ports on my laptop (3 of them are USB 3.0, 1 is USB 2.0), and I've toggled MTP mode on and off, but no joy: the update assistant never recognizes the phone. However the laptop does, indeed, recognize the phone, and lets me open a file browser window and look at files on the SD card.
Only variable I'm not confident about here: when I connect the phone to the laptop, there's the typical Windows popup that asks what I want to do when this device (the phone) is connected to the laptop. Note: the update assistant is NOT offered: just typical options such as, "transfer media files to PC". Not sure which to accept, I've ignored that prompt -- wondering if perhaps I need to select one of these options in order to complete the MTP connection properly?
Click to expand...
Click to collapse
None of my USB ports work. I've tried uninstalling and reinstalling everything, with no results. Unless there is a manual solution available, I guess I'll have to wait through this 2nd straight Verizon branded false alarm.
cdowning22 said:
Except my device NEVER wants to pop-up on the software upgrade assistant, and it's on MTP mode. Any help with that? I'm on Windows 10 too.
Click to expand...
Click to collapse
You can run it and check for updates manually once it's installed. Just to be clear, when my phone is connected to my pc if I pull down the notification menu on my phone and tap the usb notification there is an option to install software that, when checked, adds a cd installer in windows explorer on the pc to install the Software Update and Repair assistant. @jonstrong I just ignore the pc popup or select take no action.
cdowning22 said:
None of my USB ports work. I've tried uninstalling and reinstalling everything, with no results. Unless there is a manual solution available, I guess I'll have to wait through this 2nd straight Verizon branded false alarm.
Click to expand...
Click to collapse
I had similar issues, I installed SUA on my laptop and it would not detect the phone. Installed it on my desktop and it recognized the phone. Both are running Windows 10.
What cords are you using to connect? Sometimes that can make a difference.
Sent from my XT1585 using Tapatalk
scadilla said:
I had similar issues, I installed SUA on my laptop and it would not detect the phone. Installed it on my desktop and it recognized the phone. Both are running Windows 10.
Click to expand...
Click to collapse
I haven't had a desktop computer for years. But at least I'm not alone.
sparky697 said:
What cords are you using to connect? Sometimes that can make a difference.
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
Doesn't matter what cord I have, won't detect. I'm screwed at this rate.
I can not get the Software Upgrade Assistance (SUA) to work on my Desktop PC but was able to get it to work on my wife's Desktop PC. I tried on my laptop and found that the Verizon Software Upgrade Assistance (SUA) works (recognizes the phone) on the laptop's USB2 ports but will not work on the USB3 ports. My wife's PC has USB2 ports and My PC has USB3 ports. All the above computers are running Windows 10.
Based on my testing, it appears that the Verizon Software Upgrade Assistance (SUA) does not work with USB3 ports.
Try using a PC or laptop with USB2 ports.
rbird2 said:
I can not get the Software Upgrade Assistance (SUA) to work on my Desktop PC but was able to get it to work on my wife's Desktop PC. I tried on my laptop and found that the Verizon Software Upgrade Assistance (SUA) works (recognizes the phone) on the laptop's USB2 ports but will not work on the USB3 ports. My wife's PC has USB2 ports and My PC has USB3 ports. All the above computers are running Windows 10.
Based on my testing, it appears that the Verizon Software Upgrade Assistance (SUA) does not work with USB3 ports.
Try using a PC or laptop with USB2 ports.
Click to expand...
Click to collapse
Won't even recognize on USB2. Repeating: Screwed
make sure that your phone does not have USB debugging on. Also make sure you are using OEM cable (from any brand really). COnnect to a USB 2 por and go to www.motorola.com/verizonsoftwareupdatewin (if you have a windows computer) or replace win with mac
Download, install, and run software assistant... unplug your droid turbo 2 a couple of times until the software sees it... then it should work
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
gabo_e30 said:
make sure that your phone does not have USB debugging on. Also make sure you are using OEM cable (from any brand really). COnnect to a USB 2 por and go to www.motorola.com/verizonsoftwareupdatewin (if you have a windows computer) or replace win with mac
Download, install, and run software assistant... unplug your droid turbo 2 a couple of times until the software sees it... then it should work
Click to expand...
Click to collapse
1. my signature is old... lol
2. don't let your phone lock/ go to sleep while it is downloading
For anyone who's still having trouble getting the update on their Droid Turbo 2 - my experience might be worthwhile knowing about:
We've got three DT2's (would have been four, but my son opted for an iPhone). The first two were offered the update when the first big wave came around - before they shut it down a second time; we accepted the 2 step update for those two phones, and they were both successfully updated to Marshmallow over a week ago. The third DT2 however never got the offer, and punching "check for updates" never found the update either -- even as recently as today, March 19.
I had tried connecting the third phone to my laptop via USB -- and made sure to use the USB 2.0 port on my laptop (the other three USB ports are USB 3.0), and made sure the phone was set to MTP mode. Still no joy. Never offered the "CD Install" option on the phone, even though I had checked both MTP mode and Software install on the phone under USB options.
Finally this evening I tried the same on a different laptop, and tried a different USB cable as well. This time, the phone actually offered the CD install option, and was able to prompt the laptop to download and install the Verizon Software Upgrade Assistant (VSUA). It was till touch and go for a while: once I fired up the assistant, it still didn't seem to recognize the phone the first several times I tried it. Finally -- I let it sit for a couple of minutes with the VSAU loaded and the phone plugged into the laptop, and this time the phone showed up in the Upgrade window. I selected it and clicked on the upgrade button. I was amazed at how long the download took, as I remembered the "1 of 2" upgrade being pretty small -- with the 2 of 2 being the 1.1GB file.
Finally - the download completed, and the update began. That also took a long time, but I could see the progress indication, so I was encouraged. In the end, this single upgrade completed, and then the Android "upgrading" process began for what I recall to be 40 programs (probably what my daughter had installed on her phone) -- again -- I was surprised at how slow this was, but I made a point of NOT disturbing it.
Anyway - it finished, rebooted, and after this SINGLE update, the phone was all the up to the latest update for 6.0 for the DT2 -- the same version I'm at after doing the 1 of 2 and 2 of 2 updates the week before last -- 24.24.11 kinzie_verizon.verizon.en.US . It seems that the VSUA got my daughter's phone there with a single update -- something that surprised me. Maybe there's a new update file out there that does this in a single pass? Don't know.
But -- the take away for anyone still frustrated by not getting the update yet should be: you probably CAN get it, if you're patient enough, and are willing to try a couple of different cables, and possibly different PC's (one of my laptops couldn't deliver the update, but another was somehow able). Seems that it's still on their servers waiting to be downloaded, and VSUA can actually function if you somehow get the magical combo of computer, USB 2.0 port, proper cable, and LOTS of patience and willingness to try something repeatedly.
Jon
Well I Finally managed to get the VWSUA going on an older computer. Upgrade in progress...
Upgrade complete. I'm now on Marshmallow. Thank you all.
Anyone else having issues connecting Pixel XL to Mac via Android File Transfer? I had no issues with my Note 5, but the Pixel XL will not stay connected. It shows that its connecting and then I get the pop up that reads: "If your device's screen is locked, disconnect its USB cable, unlock your screen, and then reconnect the USB cable." My screen is unlocked and all...
I had issues with AFT as well. Resorted to just pushing my content via ADB. Alternatively, you could use AirDroid and just copy the content over via Wi-Fi.
same here with Google Pixel and Macbook Pro Retina late 2014
I know in the past if you've had Kies installed on your system AFT wouldn't work. Have to remove every trace of it to get AFT to connect.
Works fine for me. I selected "transfer files" from the usb options when it popped up and relaunched AFT
We are facing something similar with Google Pixel on Mac environment with Android File Transfer. Same rig used with same cables & Samsung Galaxy S7 is working perfect.
Getting the same thing when connecting my Pixel XL to my MacBook Pro running Sierra
Same issue with my Pixel and 2015 Retina Pro running El Capitan. Any solution?
Am I the only one without an issue? Have you selected the correct setting on the phone?
I'm using the Pixel XL with El Capitan on a 2015 Macbook Pro Retina and a Cable Matters brand cable
.any help here from anyone?
In case the default Android File Transfer tool can't help you transfer/move files between your Pixel and Mac, here are a few alternatives you should try, both wired and wirelessly.
https://usefulpcguide.com/17958/android-file-transfer/
Adt transfers files... But not all on mac...u won't be able to transfer mp3s,bin etc filetypes...
for what its worth, works fine for me.
Had the same issue, removed all Samsung Stuff and Kies, and then still didnt work, found this article and did what it said and works perfect, basically the USB cable plugged into computer is default to be used as charging, http://alvinalexander.com/android/a...app-cant-access-device-storage-solved-working
No, I already know that you need to change your phone into transfer file mode. I think most people know that, you have had to do it for quite sometime now... I can't even remember when you didn't have to do this step. For me and many others it is not working.
My Pixel wouldn't talk to my Mac for the first few days. After that for some reason AFT started working and all is good now. Hope you get it working.
same problem, constantly errors during the file transfer, the files that actually make it on to the phone the apps dont read.
tacopimp said:
Anyone else having issues connecting Pixel XL to Mac via Android File Transfer? I had no issues with my Note 5, but the Pixel XL will not stay connected. It shows that its connecting and then I get the pop up that reads: "If your device's screen is locked, disconnect its USB cable, unlock your screen, and then reconnect the USB cable." My screen is unlocked and all...
Click to expand...
Click to collapse
I am also getting it with my mac air and pixel xl. My work around has been airdroid for now.
Ian B
The error I am getting is "Cannot replace file" "Cannot copy file"; I don't think this is same issue as what is reported here, so I opened a new thread. Thanks in advance for any insight!
Airdroid is garbage since the new 4.0 update.
I've tried multiple cables, multiple computers, multiple USB ports with no luck. With my original XL, it pops up file explorer and I have to swipe down from phone to select transfer files and can access them. Works with all the same cables, ports and computers I tried with the XL2.
I've also tried to use the included USB-C to USB-C to transfer between XL and XL2. I get the notification on my XL that it's connected to my XL2 and can access the XL2 files, but I can't access my XL files from my XL2. Doesn't even show it's connected. Tried all the pull down options on both phones with no luck.
What am I doing wrong? This should be the easiest thing to do and had been on every phone, but not this one. Please help!
Delete
Did you set the connection type to data transfer?
InfiniteReality said:
I've tried multiple cables, multiple computers, multiple USB ports with no luck. With my original XL, it pops up file explorer and I have to swipe down from phone to select transfer files and can access them. Works with all the same cables, ports and computers I tried with the XL2.
I've also tried to use the included USB-C to USB-C to transfer between XL and XL2. I get the notification on my XL that it's connected to my XL2 and can access the XL2 files, but I can't access my XL files from my XL2. Doesn't even show it's connected. Tried all the pull down options on both phones with no luck.
What am I doing wrong? This should be the easiest thing to do and had been on every phone, but not this one. Please help!
Click to expand...
Click to collapse
I had the same issue and with a little searching I figured it out.. Make sure the phone is set to "Transfer Files" in the notification window drop down and download the Google USB drivers zip and install the driver after unzip. Right click the driver file and select install.
Since this is a new account XDA won't let me link yet so Google search for : Get Google USB Drivers
I'm having a similar issue, and we're not alone. I'll copy what I posted on reddit.
Asus ROG Maximus Hero IX motherboard. Tried with multiple cables. Wifes OG Pixel detects it is plugged in right away, my 2XL has to be screen off and set down for a couple of minutes, then the phone recognizes it is plugged in and starts charging and is available for data transfer.
Seven minutes and twenty seconds before it started charging, and another twenty seconds before the computer recognized it as being attached and ready for data transfer. I'm going to do it a few more times to see if there is a pattern.
Edit: Second time was seven minutes for both, third was three fifty one for both, eleven thirty three on the fourth.
I'm not having this problem at all. Once file transfer is enabled on the Pixel I get a popup in Windows asking how to handle the connection to the Pixel 2 XL.
I is a different story with my Nexus 6P -- I can do adb commands but the Windows does not attempt to access the storage on the device.
-- update on Nexus 6P: if I toggle the setting to PTP mode the Nexus shows up in Windows Explorer. Then when I toggle back to MTP I can see the storage.
Using Windows seems to be the common problem when connecting Android Phones to a PC.
stevemw said:
I'm not having this problem at all. Once file transfer is enabled on the Pixel I get a popup in Windows asking how to handle the connection to the Pixel 2 XL.
I is a different story with my Nexus 6P -- I can do adb commands but the Windows does not attempt to access the storage on the device.
-- update on Nexus 6P: if I toggle the setting to PTP mode the Nexus shows up in Windows Explorer. Then when I toggle back to MTP I can see the storage.
Click to expand...
Click to collapse
dratsablive said:
Using Windows seems to be the common problem when connecting Android Phones to a PC.
Click to expand...
Click to collapse
I don't get any connection option when I connect my XL2. It's like it's not even connected. My XL works perfectly fine with same cords and computers which throws me for a loop.
I'll give the shot about changing to other options and back to file transfer and see what happens.
I may need to wipe the phone and start over or maybe it's see sort of bug. Just kinda sucks, just need to make sure I can access the phone and one of the main reasons I got the 128gb version
InfiniteReality said:
I don't get any connection option when I connect my XL2. It's like it's not even connected. My XL works perfectly fine with same cords and computers which throws me for a loop.
I'll give the shot about changing to other options and back to file transfer and see what happens.
I may need to wipe the phone and start over or maybe it's see sort of bug. Just kinda sucks, just need to make sure I can access the phone and one of the main reasons I got the 128gb version
Click to expand...
Click to collapse
I have encountered similar issues when using Windows, but my laptop dual boots between Windows/Fedora Linux. I only boot to Windows when I have to. Linux has no issues communicating to Android Phones. Maybe find a Linux Bootable DVD and give it a spin
When you look in the Windows device manager do you see an entry for LeMobile Android Device? This caused a problem for me in the past. See this post for a possible solution: https://www.reddit.com/r/Nexus6P/comments/5nc64z/adb_drivers_showing_up_as_lemobile_android_device/
A shortcut to the steps in the article is to simply expand the LeMobile Android Device node, right-mouse click on the Android Composite ADB Interface, click Change settings at the bottom of the General tab, go to the Driver tab, click Update Driver; Select Browse my computer for driver software; browse to the directory where Android Studio (or adb tools downloaded from https://developers.google.com/android/ota) files are located; make sure Include subfolders is check) and replace the LeMobile Android Device driver with the Google driver.
(If you have to do this, more than likely you will have to do it each time you reboot.)
I don't know if this will have any effect but on the pc, plug to the usb ports on the back that are direct to the motherboard instead of usb headers on the top/front of pc.
I have this issue with a TomTom satnav and a Mio miview dash cam. Unless they are plugged in on back pc / with Windows 10 doesn't recognize
Sent from my XT1572 using Tapatalk
Thanks everyone for the suggestions!
dratsablive said:
I have encountered similar issues when using Windows, but my laptop dual boots between Windows/Fedora Linux. I only boot to Windows when I have to. Linux has no issues communicating to Android Phones. Maybe find a Linux Bootable DVD and give it a spin
Click to expand...
Click to collapse
That sounds easy enough, but it's dumb (to me anyways) I should even have to do this to get the computer to recognize my phone when it'll recognize my original XL and of course wife's S7. My phone gets plugged to the computer almost every day to copy files off of, at worst every other day.
stevemw said:
When you look in the Windows device manager do you see an entry for LeMobile Android Device? This caused a problem for me in the past. See this post for a possible solution: https://www.reddit.com/r/Nexus6P/comments/5nc64z/adb_drivers_showing_up_as_lemobile_android_device/
A shortcut to the steps in the article is to simply expand the LeMobile Android Device node, right-mouse click on the Android Composite ADB Interface, click Change settings at the bottom of the General tab, go to the Driver tab, click Update Driver; Select Browse my computer for driver software; browse to the directory where Android Studio (or adb tools downloaded from https://developers.google.com/android/ota) files are located; make sure Include subfolders is check) and replace the LeMobile Android Device driver with the Google driver.
(If you have to do this, more than likely you will have to do it each time you reboot.)
Click to expand...
Click to collapse
I went to the device manager on 2 computers and surprisingly nothing showed up. It's like I'm not even plugging it in, while as soon as I plug in my original XL it pops right up. When I attempt to plug it in, it doesn't even attempt to install any drivers like it sometimes use to. I'm going to install the ADB tools when I get home today and see if that helps any to recognize it.
Just tried it on my work computer which does have ADB on it with no luck or anything in device manager
I literally went through all my USB-C cables I could find yesterday, probably 12-15 at least, and I DID manage to find one that worked..... a 6" cable, lol. I can't figure out why this one works and others don't, very more odd is it's the same brand as other longer cables that don't work. Not sure what to make of it, other than voltage loss with the longer ones....just enough to make it not work.
I do have a 2nd XL2 that should be due in this week, was suppose to ship on 22nd. I was going to return it, but now I'll have to take it out of the box and at least test if it works with the computer. I'll report back.
Open to any other suggestions if anyone has any. Thanks again for the replies!
InfiniteReality said:
That sounds easy enough, but it's dumb (to me anyways) I should even have to do this to get the computer to recognize my phone when it'll recognize my original XL and of course wife's S7. My phone gets plugged to the computer almost every day to copy files off of, at worst every other day.
I went to the device manager on 2 computers and surprisingly nothing showed up. It's like I'm not even plugging it in, while as soon as I plug in my original XL it pops right up. When I attempt to plug it in, it doesn't even attempt to install any drivers like it sometimes use to. I'm going to install the ADB tools when I get home today and see if that helps any to recognize it.
Just tried it on my work computer which does have ADB on it with no luck or anything in device manager
I literally went through all my USB-C cables I could find yesterday, probably 12-15 at least, and I DID manage to find one that worked..... a 6" cable, lol. I can't figure out why this one works and others don't, very more odd is it's the same brand as other longer cables that don't work. Not sure what to make of it, other than voltage loss with the longer ones....just enough to make it not work.
I do have a 2nd XL2 that should be due in this week, was suppose to ship on 22nd. I was going to return it, but now I'll have to take it out of the box and at least test if it works with the computer. I'll report back.
Open to any other suggestions if anyone has any. Thanks again for the replies!
Click to expand...
Click to collapse
Do you see anything in device manager under Android devices or portable devices under USB when the 2XL is connected to the PC?
stevemw said:
Do you see anything in device manager under Android devices or portable devices under USB when the 2XL is connected to the PC?
Click to expand...
Click to collapse
Nothing at all, it's like it's not even connected. Just kind of dumbfounded on why when my XL never has had an issue. Attached a screenshot. The one with the triangle doesn't have anything to do with the phone though, it's always been like that and never bothered to mess with it.
The 2nd XL2 shipped yesterday and due in Thursday, so will be curious on if it has an issue. Hopefully it works as intended and I can just set it up and send this one back. Fingers are crossed for sure.
Are you updated to the latest ADB drivers? Right down to, you might have to remove and reinstall. I'm pretty sure I read that it's required.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
If the Pixel 2 is plugged in your screenshot indicates that it is present on the USB bus. It's like the drivers aren't completely loaded.
I haven't seen it mentioned if you have turned on USB debugging in your phone's Developer options. I'm pretty sure that is required for the computer to see it.
JimSmith94 said:
I haven't seen it mentioned if you have turned on USB debugging in your phone's Developer options. I'm pretty sure that is required for the computer to see it.
Click to expand...
Click to collapse
Yea on my regular pixel I have to enable debugging for mine too work. Sometimes lol
stevemw said:
Do you see anything in device manager under Android devices or portable devices under USB when the 2XL is connected to the PC?
Click to expand...
Click to collapse
JimSmith94 said:
I haven't seen it mentioned if you have turned on USB debugging in your phone's Developer options. I'm pretty sure that is required for the computer to see it.
Click to expand...
Click to collapse
I had it enabled for a while, but no such luck. I'll give it another shot, haven't had it on while at work. Also will uninstall and reinstall ADB as well.
When this has happened to me a few times, reinstalling the Windows MTP drivers has worked. Someone else posted these instructions that worked for me.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Hello All,
So long story short my 2018 model Pixel 2Xl suddenly stopped detecting my headphones nor it installed android driver when connected to PC. Ofcourse only good thing is it charges fine. Now since my phone warranty has expired I would like to try anything that could fix it. I already tried factory reset however of no help. So my question here is, is there any way I could install the driver binaries on my Pixel that could reset it? Now since my phone is not getting detected on PC except charging what option am I left with? Any way firmware change or reinstalling of drivers can be done through wifi or from within my internal storage? My mobile has stock firmware and it is not rooted as well. Any help is highly appreciated.
I had the exact same issue. Unable to plug into my PC and headphones not working. I used multiple laptops/desktops. All came back with the same Device Manager error stating that it was an "Unknown USB Device (Device Descriptor Request Failed). No matter what I would do it would continue to pop up on every single PC I plugged into. Tried different USB C cables as well. I was told a part of the board was fried.
I finally gave up and got a Pixel 4a 5g. I should mention I put in a new hard drive for my main PC and installed Windows. I plugged my Pixel 2 XL into my fresh install of Windows 10 and BOOM it started working again. I was able to unlock the bootloader and install a ROM as well. I just checked USB C headphone and they are working as well. I am not sure after testing so many variables why this was the resolution, but I am glad I found it.
I will note, in looking for the Device Manager error message I did find this.
Open your device manager. Click ‘View’ and then click ‘Show hidden devices’. Your Pixel 2 XL (or whatever phone you have) should be shown there and will be ‘greyed out’. Make sure your phone is unplugged, and then right mouse click on your Pixel 2 XL on your device manager and click ‘Uninstall device’.
Worth trying at the very least.
xconwayx said:
I had the exact same issue. Unable to plug into my PC and headphones not working. I used multiple laptops/desktops. All came back with the same Device Manager error stating that it was an "Unknown USB Device (Device Descriptor Request Failed). No matter what I would do it would continue to pop up on every single PC I plugged into. Tried different USB C cables as well. I was told a part of the board was fried.
I finally gave up and got a Pixel 4a 5g. I should mention I put in a new hard drive for my main PC and installed Windows. I plugged my Pixel 2 XL into my fresh install of Windows 10 and BOOM it started working again. I was able to unlock the bootloader and install a ROM as well. I just checked USB C headphone and they are working as well. I am not sure after testing so many variables why this was the resolution, but I am glad I found it.
I will note, in looking for the Device Manager error message I did find this.
Open your device manager. Click ‘View’ and then click ‘Show hidden devices’. Your Pixel 2 XL (or whatever phone you have) should be shown there and will be ‘greyed out’. Make sure your phone is unplugged, and then right mouse click on your Pixel 2 XL on your device manager and click ‘Uninstall device’.
Worth trying at the very least.
Click to expand...
Click to collapse
Great to know it worked for you. However for me I tried in my Windows PC as well as on my MAC and it doesn't work on both. Unfortunately my warranty as expired too so I have dropped an escalation to Google and awaiting response from their end. My Pixel 2 XL has never worked properly for more than 9 months from the date of purchase with USB C port already replaced once, screen replaced due to burn in, headphones replaced as it stopped worked etc. I have also heard many people informing about the port starting to work fine all of a sudden too. If Google provides free support well and good, if not will move to OnePlus maybe. Had enough of Pixel phones. I had the first version of Pixel XL and then bought this.
Use a sim ejector tool to pry out the dust and gunk from the type c port. Had issues with charging and usb connection, you may not be able to see it but there would be a lot of lint and dirt collected inside the port. cleaning it up fixes the issues.
Khizar Amin said:
Use a sim ejector tool to pry out the dust and gunk from the type c port. Had issues with charging and usb connection, you may not be able to see it but there would be a lot of lint and dirt collected inside the port. cleaning it up fixes the issues.
Click to expand...
Click to collapse
Tried that too. There wasn't any dust as such but used a small paint brush to wipe inside throughly however didn't help. Any way to install the driver binaries via wifi or from within the phone rather than using a PC?
bejoyalex said:
Tried that too. There wasn't any dust as such but used a small paint brush to wipe inside throughly however didn't help. Any way to install the driver binaries via wifi or from within the phone rather than using a PC?
Click to expand...
Click to collapse
See my recent posts about my USB problems and replacing the internal USB ass'y. It didn't fix my similar problem though.
Cleaning the port is worth a shot. The SIM tool, a needle or plastic toothpick work great for this. I used a little alcohol too and the pad came out pretty dirty.
You can enable WiFi debugging/Wireless ADB in Developer Mode settings. You can then run commands in ADB. It won't let you unlock the bootloader with only WiFi though. That's what has me stuck.
I have the same problem and in my case the device has a sound bug that doesn't work at all, not even through the speaker, microphone or bluetooth. And the computer does not identify the cell phone or the device shows that storage option and only charges slowly. I don't know what to do help