Develop Bugs

Pixel XL Fastboot Works to Flash Stock ROM+TWRP. Unseen as USB in TWRP or OS

I have 3 of these devices I'd successfully flashed TWRP to months ago. I can plug the other 2 into any of my Win10 PCs and they are functional as MTP devices in TWRP or the OS. Something is wrong with this device in that fastboot works fine, yet it is not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView. I was unsure if this device received an OTA update so I went ahead and flashed the latest stock firmware as of 5/24/2017
It successfully flashed albeit unusually slow (even though Nirsoft USBDevView showed it connected at USB 2.0 and not 1.1). It also successfully flashed the latest Pixel XL Marlin-3.1.0-0RC2
Even if I attempt to toggle MTP in TWRP there is no response in Windows (on any of my PCs) nor is there any response when it's booted to Android 7.1.2. Same when toggled to PTP. Same w/ USB Debugging enabled. The device charges fine. Checking OTA updates shows none available. Factory reset option in bootloader didn't help.
I'm sure I'm missing something like I somehow have the incorrect firmware loaded for something. Anyone know what specifically is responsible for the USB at the firmware level that would allow it to function in fastboot mode yet fail to detect when booted TWRP or OS???

Pay_It_Forward_Pete said:
I have 3 of these devices I'd successfully flashed TWRP to months ago. I can plug the other 2 into any of my Win10 PCs and they are functional as MTP devices in TWRP or the OS. Something is wrong with this device in that fastboot works fine, yet it is not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView. I was unsure if this device received an OTA update so I went ahead and flashed the latest stock firmware as of 5/24/2017
It successfully flashed albeit unusually slow (even though Nirsoft USBDevView showed it connected at USB 2.0 and not 1.1). It also successfully flashed the latest Pixel XL Marlin-3.1.0-0RC2
Even if I attempt to toggle MTP in TWRP there is no response in Windows (on any of my PCs) nor is there any response when it's booted to Android 7.1.2. Same when toggled to PTP. Same w/ USB Debugging enabled. The device charges fine. Checking OTA updates shows none available. Factory reset option in bootloader didn't help.
I'm sure I'm missing something like I somehow have the incorrect firmware loaded for something. Anyone know what specifically is responsible for the USB at the firmware level that would allow it to function in fastboot mode yet fail to detect when booted TWRP or OS???
Click to expand...
Click to collapse
When booted into the OS and plugged into PC, do you have a notification on the pixel that the device is connected and an option to change how to interact with the PC?

TheBobMiller said:
When booted into the OS and plugged into PC, do you have a notification on the pixel that the device is connected and an option to change how to interact with the PC?
Click to expand...
Click to collapse
I can plug it into the PC and charge it up and receive a full charged reached message in the notification bar. Unfortunately I do not receive any other acknowledgement in the notification bar that it's connect to the PC and to toggle from "charge only" to PC MTP connection like most other phones present.
Its not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView.
Yet I can flash it successfully all day long in fastboot mode ... so strange.

Pay_It_Forward_Pete said:
I can plug it into the PC and charge it up and receive a full charged reached message in the notification bar. Unfortunately I do not receive any other acknowledgement in the notification bar that it's connect to the PC and to toggle from "charge only" to PC MTP connection like most other phones present.
Its not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView.
Yet I can flash it successfully all day long in fastboot mode ... so strange.
Click to expand...
Click to collapse
What happens when you change the default USB Configuration in Developer Options to MTP or PTP and the plug in the phone to the computer?

TheBobMiller said:
What happens when you change the default USB Configuration in Developer Options to MTP or PTP and the plug in the phone to the computer?
Click to expand...
Click to collapse
No response on the phone or PC when set to MTP or PTP. Same w/ USB debugging off or enabled.

Pay_It_Forward_Pete said:
No response on the phone or PC when set to MTP or PTP. Same w/ USB debugging off or enabled.
Click to expand...
Click to collapse
I know this may seem like a stupid question, but have you tried using a different cable? If the phone recognizes fastboot mode commands but not PTP or MTP, then perhaps the cable is going bad. I would blame it on your drivers but fastboot mode wouldn't work if the drivers were malfunctioning.

TheBobMiller said:
I know this may seem like a stupid question, but have you tried using a different cable? If the phone recognizes fastboot mode commands but not PTP or MTP, then perhaps the cable is going bad. I would blame it on your drivers but fastboot mode wouldn't work if the drivers were malfunctioning.
Click to expand...
Click to collapse
Same behavior with a different cable. I've also tested on USB 2.0 and USB 3.0 ports. Also different PCs. Up until today I couldn't get Windows to acknowledge anything. Today I observed Windows a couple times present "usb device not recognized. the last usb device you connected to this computer malfunctioned and windows does not recognize it."
However even after it did that once on one PC today and again on another PC today, I couldn't get Windows to present that message any subsequent times. Even when that message did appear as a system tray notification in Windows, Windows still wasn't showing the phone with a yellow exclamation point in device manager like it sometimes can for many other devices it would otherwise present such a message for. (I just speak from past experience with older PCs)

Pay_It_Forward_Pete said:
Same behavior with a different cable. I've also tested on USB 2.0 and USB 3.0 ports. Also different PCs. Up until today I couldn't get Windows to acknowledge anything. Today I observed Windows a couple times present "usb device not recognized. the last usb device you connected to this computer malfunctioned and windows does not recognize it."
However even after it did that once on one PC today and again on another PC today, I couldn't get Windows to present that message any subsequent times. Even when that message did appear as a system tray notification in Windows, Windows still wasn't showing the phone with a yellow exclamation point in device manager like it sometimes can for many other devices it would otherwise present such a message for. (I just speak from past experience with older PCs)
Click to expand...
Click to collapse
Wow...that's puzzling then. You said in your op that you factory reset using bootloader menu but have you tried flashing factory image with fastboot in bootloader? Maybe the firmware that's malfunctioning could be fixed with a factory image flash...

TheBobMiller said:
Wow...that's puzzling then. You said in your op that you factory reset using bootloader menu but have you tried flashing factory image with fastboot in bootloader? Maybe the firmware that's malfunctioning could be fixed with a factory image flash...
Click to expand...
Click to collapse
That's what's killing me. I can successfully factory image flash (same I've flashed on the other handsets). Yet the USB doesn't work in the OS. When this initially happened I thought for sure USB was going to work like usual in TWRP (works on the others) but it doesn't work there either.
The only other thing I can think of out of desperation is flash Pure Nexus ROM or Resurrection remix in the hopes that somehow affects a USB bit setting at the firmware level. (Mind you flashing factory nor TWRP helped).
My exotic theory is that fastboot driver has an ability to work in USB 1 mode and TWRP or OS level driver can only work in USB 2.0/3.0 mode. Even though I don't see any visual defects to the pinout on this handset I'm guessing my pins for charging and for USB 1 mode is fine whereas my pins for USB 2.0/3.0 are electrically damaged or something.

Pay_It_Forward_Pete said:
That's what's killing me. I can successfully factory image flash (same I've flashed on the other handsets). Yet the USB doesn't work in the OS. When this initially happened I thought for sure USB was going to work like usual in TWRP (works on the others) but it doesn't work there either.
The only other thing I can think of out of desperation is flash Pure Nexus ROM or Resurrection remix in the hopes that somehow affects a USB bit setting at the firmware level. (Mind you flashing factory nor TWRP helped).
My exotic theory is that fastboot driver has an ability to work in USB 1 mode and TWRP or OS level driver can only work in USB 2.0/3.0 mode. Even though I don't see any visual defects to the pinout on this handset I'm guessing my pins for charging and for USB 1 mode is fine whereas my pins for USB 2.0/3.0 are electrically damaged or something.
Click to expand...
Click to collapse
Well i guess you could try some ROM flashing and see if that works and if not, try contacting Google and see if they will honor a warranty or something. Good luck to ya!

TheBobMiller said:
Well i guess you could try some ROM flashing and see if that works and if not, try contacting Google and see if they will honor a warranty or something. Good luck to ya!
Click to expand...
Click to collapse
@TheBobMiller I appreciate all your thoughtful suggestions and well wishes. Have an awesome weekend!

I Guess I Discovered a New Form of Hard Bricking on my Device???

I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.

jasonstackhouse said:
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
Click to expand...
Click to collapse
I would try a different cable as this device is very finicky; that solved my issue of the computer not recognizing the phone.

Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?

Az Biker said:
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Click to expand...
Click to collapse
That would be nice if that were the problem, but unfortunalty I do not think it is. For example, when the issues first began, before I did the factory reset on the device, windows would pop up a message that said unknown device, and failure to connect. After the factory reset in TWRP the computer gave up all together in recognizing the phone. Another sign it was likely not a hardware failure was when the device was on and i was attempting to connect the otg usb to the phone it would give me some weird options. With android P the options were, allow this device to control the usb, or allow the USB to control the USB. that made no sense to me since why would i want the the USB to have any control, it couldnt do anything its not a computer its only a storage device. However, even though I had file transfer selected in developer options, it would not allow this connection. The options were all greyed out and it would not allow the pixel to have control over the usb device.
As for USB cords I have used without fail the google issued USB cord that came with the Pixel 1 xl, It has never faile me or had any issues. It is still fully functional as I was able to use it to connect my girls note 8 to my computer for file transfers and all other things my phone is not doing anymore.
I reached out to google and explained the situation to them, after i told them I was on Dev preview beta and they verified this to be true they told me this is likely a hardware failure and offered to replace the device. I am now waiting on the new device to be sent to me, however still cant accept that i cant recover the current device with an unlocked bootloader, TWRP installed, and access to fastboot/bootloader screen. I have seriously bricked phones before as in they would not even turn on and I was able to get them back up and running, this would be my first ever device I could not recover and what makes it worse is that it actually has TWRP installed and powers on and off just fine.

Sorry for the obvious question: Do you have the latest drivers? I don't have the drivers set to the whole system (Windows), so if I don't CD into my fastboot folder, I can't do anything because the system wide drivers aren't current. Don't know if that could be your issue?
I'm too lazy to fix the PATH of my drivers ¯\_(ツ)_/¯

I had an issue similar to this. I was trying to hook up a USB c to Ethernet adapter. It worked fine on April's patch but after I flashed Mays the phone wouldn't recognize it. After I plugged it in my phone rebooted and I no longer had access to developer options and it wouldn't read any usb device. Luckily I had a TWRP backup on my device. Once I flashed the backup which was only about a week old everything worked again. I haven't tried using the adapter again. I think something in the data partition got corrupted. I tried just restoring the boot and system partition and that didn't fix it. Try doing an advance wipe and formatting the data partition. That might get you back up and going.

have we even seen a bricked device yet?

twiz0r said:
have we even seen a bricked device yet?
Click to expand...
Click to collapse
I didn't think it was possible, I still dont understand how this is happening. For the other responses above, I have all the drivers up to date, and I already formatted data, wiped everything. At this point I would like to see if there is anyway to delete TWRP recovery from the device, anything, I have no OS on the device, but for some reason still have TWRP on both A and B.
I almost dont want to give the phone back to Google because I want to figure out what happened and how to fix it, its definitely not broken/bricked like you see when someone flashes the wrong files to a device, it just has no USB connection capabilities which in-turn have rendered the device useless.
When I had Samsung phones if you bricked a device to the point it doesn't even turn on correctly you could always save it still using ODIN. Its weird that the google flagship device and software doesn't have its own proprietary flash software like Samsung, LG and HTC, we just have adb/fastboot, I feel like if we did, i may be able to get this thing started again.

have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image

Pyr0x64 said:
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Click to expand...
Click to collapse
I can't access the play store on the device in it's state. I do have access to fastboot. I can boot the phone to fastboot, and into TWRP, only problem is the phone doesn't communicate with the computer in either state. If the pixel had a SD card slot I would just load up a recovery but unfortunately we don't have that luxury

What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs

Triscuit said:
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
The cable is not the issue, I confirmed this by testing all my cables with the new device that I just received for my warranty exchange. I also tried my luck with Linux, after a complicated installation on my computer I was able to have Linux actually detect the device (partially) when the device was plugged in at splash screen I got nothing, at fastboot/bootloader screen nothing, but once the phone booted into TWRP it came up as AOSP device, when I attempted clicking on the AOSP device being detected by Linux an error message popped up telling me mtp or midi error, not sure for sure what one it said. Either way I couldn't connect for any transfer of information, I tried adb sideload and that failed as well.
This has been an experience for the memory books, glad that old device is gone and I'm back up and running on a working phone. No more beta testing for me, I'll be ready for Android P when they get it out of beta, I don't have the time or patience to deal with any more warranty exchanges.

Pixel 2 XL not connecting to PC

UPDATE:
I ended up just returning the phone and getting a new one (it was an Ebay seller so they didn't try to repair it).
New one connected instantly and I can use ADB and Fastboot perfectly.
Definitely something wrong with the first one, weird how the headphone adapter and OTG worked though.
Original post:
I know there are other threads on this but I really need some help on this.
I just got a Pixel 2 XL, but it won't connect to the PC. At all. No connection noise, nothing in task manager. The only change between plugged and unplugged is that the phone starts charging. No notification appears when I plug it in, it doesn't even try to connect.
I've tried three different cables, three different PCs, I've fiddled with USB debugging. I can't do anything with drivers on Windows because nothing changes in device manager when I plug it in.
I don't have any computers with USB C ports so I can't test that but I've tried all different ports on my PC (USB 2 and USB 3).
The headphone adapter works and when I plug in my old HTC U11's earbuds it says "accessory not supported" (which it's supposed to say, those earbuds only work on specific phones) so the port can't be completely broken.
I also tried plugging a USB drive into the full size to C adapter that comes with it and it reads it perfectly. I copied my music library onto the Pixel by putting it on a flash drive first.
I realise it may just be defective but it would be a huge pain if I got a new one only to discover that it was something that I'm doing or my PC causing it. And is it even possible to be defective when it can output music and even transfer files from a flash drive through that same port?
What else can I try?

megaman1574 said:
I know there are other threads on this but I really need some help on this.
I just got a Pixel 2 XL, but it won't connect to the PC. At all. No connection noise, nothing in task manager. The only change between plugged and unplugged is that the phone starts charging. No notification appears when I plug it in, it doesn't even try to connect.
I've tried three different cables, three different PCs, I've fiddled with USB debugging. I can't do anything with drivers on Windows because nothing changes in task manager when I plug it in.
I don't have any computers with USB C ports so I can't test that but I've tried all different ports on my PC (USB 2 and USB 3).
The headphone adapter works and when I plug in my old HTC U11's earbuds it says "accessory not supported" (which it's supposed to say, those earbuds only work on specific phones) so the port can't be completely broken.
I also tried plugging a USB drive into the full size to C adapter that comes with it and it reads it perfectly. I copied my music library onto the Pixel by putting it on a flash drive first.
I realise it may just be defective but it would be a huge pain if I got a new one only to discover that it was something that I'm doing or my PC causing it. And is it even possible to be defective when it can output music and even transfer files from a flash drive through that same port?
What else can I try?
Click to expand...
Click to collapse
Which version of Windows are you trying it on? Can you try it on a Win 7 machine? It's not the phone but the drivers. There are various threads around that will guide you thru it but you have to search some. Some are a little old but they should work. Keep at it, you'll figure it out. There is something in device manager that you need to tinker with if I recall correctly. Happened to me on my Pixel OG and it took me a few days to finally figure it out. Total pain but relief once you get it.

If you have a relatively new computer (Win 7 or newer) then it *should* recognize the Pixel. But sometimes Windows can be a pain in the ass. Download & install Android SDK which will install the latest Android USB driver, reboot the computer, then connect the Pixel again.

sublimaze said:
If you have a relatively new computer (Win 7 or newer) then it *should* recognize the Pixel. But sometimes Windows can be a pain in the ass. Download & install Android SDK which will install the latest Android USB driver, reboot the computer, then connect the Pixel again.
Click to expand...
Click to collapse
I don't think I can install any drivers unless the phone shows up as something in device manager, which mine doesn't

megaman1574 said:
I don't think I can install any drivers unless the phone shows up as something in device manager, which mine doesn't
Click to expand...
Click to collapse
Your computer must have Android USB driver installed before it will recognize the phone.

sublimaze said:
Your computer must have Android USB driver installed before it will recognize the phone.
Click to expand...
Click to collapse
I'll search this in the morning. He needs to uninstall something.. dang it I forget. I'll figure it out tomorrow. Or search my posts from a year ago I'm sure it's there somewhere.
Sent from my Pixel 2 using XDA-Developers Legacy app

sublimaze said:
Your computer must have Android USB driver installed before it will recognize the phone.
Click to expand...
Click to collapse
What I mean is it doesn't show up at all. When I plug the phone in device manager doesn't change.

bobby janow said:
I'll search this in the morning. He needs to uninstall something.. dang it I forget. I'll figure it out tomorrow. Or search my posts from a year ago I'm sure it's there somewhere.
Sent from my Pixel 2 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I had a look through your post history but I'm not sure what I'm looking for... And I can't figure out how to search a post history

megaman1574 said:
I had a look through your post history but I'm not sure what I'm looking for... And I can't figure out how to search a post history
Click to expand...
Click to collapse
Yeah I know, only goes back for like a year or so. This is the guide I followed and it worked. Some still had problems but check out the OP and give it a shot.
https://forum.xda-developers.com/pixel-xl/how-to/guide-fix-mtp-driver-windows-10-t3570625

This may be silly but when my phone was new I had the same issue. I had to go into the USB settings on my phone and change them from charging to file transfer.

I'm having similar issues to the OP, but I've had my phone since it was released. I have done everything known to man to try and get this working--updated Android Studio/drivers, both fixes listed HERE, tried numerous cables, rebooting phone and multiple PCs, still not getting my phone to get recognized at all.
My exact issue is this: I'm still on the August 2018 Security patch, so I wanted to update to October. Downloaded my files then went into Magisk and uninstalled (un-root) restoring stock boot. I waited a few hours before I could try to flash the OTA, but once I did, I connected the phone (USB-C to USB-C OEM cable) to my PC and it successfully connected in Debug mode. Ran "adb devices" and phone was seen. "adb reboot bootloader" successfully rebooted phone, but it did not go into bootloader mode for some reason, it just restarted in normal mode. The only problem is now the phone doesn't talk to my PC no matter what.... the USB-C to USB-C OEM cable doesn't even charge the phone let alone connect to give me file transfer options. If I try a USB-C to USB-A cable, the phone charges but the PC doesn't recognize my phone is connected. Debugging never works. Even my Car Charger (which is USB PD capable) doesn't charge the phone, I have to go back to my regular USB-C QuickCharge car adapter to get it to take a charger. I've disabled Debugging, changed default USB connection type to File Transfer, PTP, etc.
So, is there a way I can try to flash the OTA without connecting to a PC? Maybe even just flash the August Boot.img? I want to try updating the phone to see if that fixes my issues first. I am currently with an unlocked bootloader, no root and stock recovery, so I don't believe Flashify will work without getting root back... I think when I restored my stock Boot via Magisk, it FUBARed something. The only thing I can try is to use my USB-C to USB-A cable and see if fastboot recognizes the phone with that cable... the USB-C to USB-C cable is no dice in Fastboot.

Do you have another Android device? If so, (and it is rooted), you can run adb and fastboot from there. The binaries are available via the Magisk repository. Just grab a terminal emulator and a usb-otg cable and go to town. No driver issues, no fuss, no mess.
I was occasionally successful with a usb-c to usb-c cable, but sometimes the devices would get confused. The otg cable works every time, with the host end facing the adb/fastboot running device.

@hawkjm73 To whom are you talking to? If me, I don't have an OTG cable nor another rooted phone.
I did try the USB-A to USB-C cable and booted into Fastboot, which worked. I was able to at least boot into TWRP and get Magisk re-installed so I'm rooted. I booted the phone back up and still no USB recognition or Debugging. I'm going to wait to try a third PC to see if that will work in getting Debugging/ADB commands to work. All else fails, I'll just do a full Factory October flash without the wipe.
What's puzzling to me is why this all happened and why even my USB-C PD car charger won't work. Something strange is going on.
---------- Post added at 03:01 PM ---------- Previous post was at 02:25 PM ----------
Update: I grew impatient and decided that since my PC was seeing the phone in fastboot, I flashed the full October Firmware manually in fastboot (ran each command in the flash-all.bat one by one). As soon as it booted into the OS, Debugging and USB connectivity (both cables) turned back on. I haven't tested my Car USB PD charger, but I suspect that will work too.
I'm guessing when I uninstalled Magisk and tried restoring the stock Boot.img, something went awry and it was causing the connectivity issues.
So, if you can get your phone into Fastboot and your PC recognizes it, I would suggest a full system image flash, don't forget to remove the -w if you don't want to wipe.

megaman1574 said:
I know there are other threads on this but I really need some help on this.
I just got a Pixel 2 XL, but it won't connect to the PC. At all. No connection noise, nothing in task manager. The only change between plugged and unplugged is that the phone starts charging. No notification appears when I plug it in, it doesn't even try to connect.
I've tried three different cables, three different PCs, I've fiddled with USB debugging. I can't do anything with drivers on Windows because nothing changes in device manager when I plug it in.
I don't have any computers with USB C ports so I can't test that but I've tried all different ports on my PC (USB 2 and USB 3).
The headphone adapter works and when I plug in my old HTC U11's earbuds it says "accessory not supported" (which it's supposed to say, those earbuds only work on specific phones) so the port can't be completely broken.
I also tried plugging a USB drive into the full size to C adapter that comes with it and it reads it perfectly. I copied my music library onto the Pixel by putting it on a flash drive first.
I realise it may just be defective but it would be a huge pain if I got a new one only to discover that it was something that I'm doing or my PC causing it. And is it even possible to be defective when it can output music and even transfer files from a flash drive through that same port?
What else can I try?
Click to expand...
Click to collapse
Time for an RMA...just happened to me a month ago

WoJ... good follow-up update.

I ended up just returning the phone and getting a new one (it was an Ebay seller so they didn't try to repair it).
New one connected instantly and I can use ADB and Fastboot perfectly.
Definitely something wrong with the first one, weird how the headphone adapter and OTG worked though.

[Q] Unable to communicate to PC after unlocking bootloader

I have a pixel 2 XL, 64GB, Google (non-Verizon) model running android pie (9) on Oct 5 2018 security patch. I was able to unlock the bootloader via fastboot flashing unlock_critical. The device then wiped, no issues. Then when I went to reconnect my device and root/install TWRP, fastboot did not see the device. I booted to the OS and adb didn't see the device either. I have tried
-multiple cables (all Benson approved)
-multiple USB ports
-multiple factory data resets (both via settings and recovery)
-multiple systems (1 pc and 1 macbook pro)
-cleaning the device's usb-c port with iso alcohol
-jiggling the cable in case its not making a good connection
-downloading the OTA and attempting to flash that via stock recovery (didn't work, nothing showed up in the list)
-singing to it.
I have an additional pixel 2 xl which I put in bootloader mode and fastboot saw it instantly. Same with my old nexus 6p. I would unplug those devices, plug in my pixel 2 xl also in bootloader mode, but still nothing listed for `adb devices` (booted in android with USB debugging enabled) or `fastboot devices` (booted in bootloader). Any ideas? Thanks!
One thing I'd like to try is to be able to flash the stock OTA image. How would I go about doing that without ADB (ie using the sdcard)? I tried renaming the zip file to `update.zip` and placing it in the root of the home folder (defaulted to /storage/emulated/0) but when I go into stock recovery, its empty. All I see is (../). Any ideas for this?

DangerIsGo said:
I have a pixel 2 XL, 64GB, Google (non-Verizon) model running android pie (9) on Oct 5 2018 security patch. I was able to unlock the bootloader via fastboot flashing unlock_critical. The device then wiped, no issues. Then when I went to reconnect my device and root/install TWRP, fastboot did not see the device. I booted to the OS and adb didn't see the device either. I have tried
-multiple cables (all Benson approved)
-multiple USB ports
-multiple factory data resets (both via settings and recovery)
-multiple systems (1 pc and 1 macbook pro)
-cleaning the device's usb-c port with iso alcohol
-jiggling the cable in case its not making a good connection
-downloading the OTA and attempting to flash that via stock recovery (didn't work, nothing showed up in the list)
-singing to it.
I have an additional pixel 2 xl which I put in bootloader mode and fastboot saw it instantly. Same with my old nexus 6p. I would unplug those devices, plug in my pixel 2 xl also in bootloader mode, but still nothing listed for `adb devices` (booted in android with USB debugging enabled) or `fastboot devices` (booted in bootloader). Any ideas? Thanks!
One thing I'd like to try is to be able to flash the stock OTA image. How would I go about doing that without ADB (ie using the sdcard)? I tried renaming the zip file to `update.zip` and placing it in the root of the home folder (defaulted to /storage/emulated/0) but when I go into stock recovery, its empty. All I see is (../). Any ideas for this?
Click to expand...
Click to collapse
Have you tried toggling USB debugging a few times to see if it connects?

Badger50 said:
Have you tried toggling USB debugging a few times to see if it connects?
Click to expand...
Click to collapse
Yes.

Same thing happened to me. First it randomly rebooted and then hung on the "G" splash screen. I couldn't get it to boot at all. It wouldn't show up on windows 8 or 10 (it did on Sept patch) it would charge, but no adb. Had to factory reset in recovery and it booted, but still no USB connection. Went through diagnosis with Google tech support and they are replacing it under warranty.

Not really the same thing here but, my phone suddenly stopped being recognized by my windows 10 laptop even tried several different cables. Also what further made it evident that something must be wrong with the USB-C port when I used the dongle adapter for wired headphones nothing at all, no sound nothing but it charges just fine. I just contacted Google yesterday for a standard RMA and sent if off for a replacement. I love Google's devices but kind of sad I'll be on my 2nd replacement here now, oh well least I get another replacement right?

I've been having issues with my USB-C port as well. I've actually kinda chilled on flashing because of that. I'm worried it's gonna bite me in the ass.

So I ended up talking with Google and I just went for a replacement device. Not ideal but not much more I could do!

pixel 2 xl refuses data connection with all computers except one.

Hi so i installed twrp and rooted my pixel with magisk. everything went fine.
saw the sultan kernel decided to flash but my phone does not recognize any computer with any cable as a computer but as a powersource. Adb and fastboot not working on any laptop or desktop (except the desktop on which i unlocked my bootloader and rooted my device) tried to connect over usb (adb fastboot filetransfer) on Linux Windows and MacOs. all unsuccesfull.
dev options is on:
oem unlock toggled
usb debug toggled
phone is running stock rom stock kernel. (Edit: kernel is the sultan kernel on stock rom)
once i connect the phone sees it as a pc pops op usb options then blacks it out because it sees it as a powersource.
whats wrong with it i cant figure it out...

Nightfall41 said:
Hi so i installed twrp and rooted my pixel with magisk. everything went fine.
saw the sultan kernel decided to flash but my phone does not recognize any computer with any cable as a computer but as a powersource. Adb and fastboot not working on any laptop or desktop (except the desktop on which i unlocked my bootloader and rooted my device) tried to connect over usb (adb fastboot filetransfer) on Linux Windows and MacOs. all unsuccesfull.
dev options is on:
oem unlock toggled
usb debug toggled
phone is running stock rom stock kernel.
once i connect the phone sees it as a pc pops op usb options then blacks it out because it sees it as a powersource.
whats wrong with it i cant figure it out...
Click to expand...
Click to collapse
I'm in very much the same situation. I've seen several USB connectivity threads roll through here recently so I'm not sure if anything larger is going on or not. Basically, I always do updates with full factory images w/o wiping. I was able to install the April update (in early April) just fine. I went back in late April to try to use fastboot and couldn't connect via USB for file transfer, ADB, or fastboot. I updated all my platform tools and the Google USB driver which made no difference. I tried on 3-4 Windows 10 desktops/laptops and 1 MacOS laptop. Nothing. I opened a support ticket with Google (and went through extensive troubleshooting steps) which was then escalated. It has been over a week and they have not responded. I even checked back yesterday to make sure it wasn't lost in the shuffle, and I was assured that it was still active and assigned to the proper team.
Just for giggles, I tried connecting to a Win7 desktop w/ only USB 2.0 and the phone immediately connected MTP (we had made this the default USB mode during the troubleshooting process). Since I was still running a modified (root) kernel, I went ahead and tried flashing the stock boot image with fastboot (both slots) and it worked! I figured since I had already wiped the phone for troubleshooting, I would try pushing the entire April image (w/ wipe). It flashed bootloader, radio, and maybe boot image (can't remember), but then lost connectivity when trying to push the system image. Fortunately, the phone booted right back up. Since then, connectivity is possible, but sporadic, on that machine. Being 100% stock, with no other options, I knew the only way to get an entire factory OTA pushed to the phone would be to opt into the beta, install the beta, then opt out, which pushes the latest non-beta and wipes the phone. I did this, but, again, it resolved nothing.
BTW, for me, this issue affects all devices that pass data through the port including USB OTG flash drives and game controllers. It's also not cable specific as I have tried a factory Google USB-A to C cable, factory Google USB-C to C, and several other USB-A to C cables (the ones I always use for ADB and fastboot commands). There does not appear to be any physical damage to the port and I cleaned it extensively with compressed air and a plastic dental pick.
Sorry I don't have a solution at this point, but I wanted to pass on the steps that I have taken.