Develop Bugs

Phone not Mounting on PC

So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?

Subscribed
I'm having the same issue. Stock non rooted and it will not connect. I have tried it on other computers cables ports everything.

Art2Fly said:
So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?
Click to expand...
Click to collapse
You might try a different cord.
Open Device Manager in Windows and then plug the phone in. Do you see it in the list with a little yellow triangle? Do you see Android USB Devices listed?

OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck

beamer1341 said:
OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck
Click to expand...
Click to collapse
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader

Art2Fly said:
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader
Click to expand...
Click to collapse
Uninstall all HTC drivers and HTC Sync. Then connect the phone. DO NOT choose the option to automatically install any drivers.
Open Device Manager, find the phone. Select the option to manually pick the driver, and select the generic MTP device driver.
This is what worked for me, after countless attempts at re-installing various HTC drivers, different cables and ports, etc.

Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.

Art2Fly said:
Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.
Click to expand...
Click to collapse
Have you tried revoking the USB debugging authorization and then accepting the RSA fingerprint key again when connecting to PC?
Obviously it can't be an USB cable problem if you can connect to it in bootloader mode and use fastboot commands.

To clarify, the phone just charges when connected, it does not detect that it is connected to PC so debugging doesn't even trigger, neither does mtp. I don't even get the slow charging notification

Does it do the same when you plug it in and reboot the computer to "pick up" during boot up process? Or if you run a live CD? I never had an issue like that with my phone but I did have a similar problem with the USB external blu ray drive I bought some time ago. The pc just didn't detect it at all not on any of the ports until I rebooted my PC with the drive already plugged it and for some reason it picked it up. <Not a solution as I don't know what caused it to not be detected in the first place but still...
Not sure if it's an issue with the device(Phone for you, blu ray drive for me) or if it's a problem with the PC even though other things might still work for you as it definitely did for me(phone, headset, mouse, keyboard, usb extender + all the external hard-drives connected to it)...

Problem exists in all computers, Mac, pc, linux

Did you try what I suggest in Post #6 above?
This worked for me when I had the same issue. adb and fastboot would work, but it would not mount MTP.
And just in the last day or 2 I helped someone else with the same issue and fix.

The phone doesn't show up in device manager.

Have you modify the Kernel? (Applying some settings for example)
I browsed over the web for this issue and found some people with the same problems. They solved by removing the settings applied on the kernel or flashing a new one.

I've flashed various kernels and ruu, still same result

Still looking for help

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.

Feb 2019 update kills PC usb connection

Strange issue. After applying the Feb 2019 security patch over air, my phone is no longer recognizing when it is plugged into a PC. I plug into my PC and I get a charge symbol on my battery but no pull down option to switch from charging to USB mode. Things I've tried:
1. New Cable although the wife has a Pixel 3 (standard) that works with this cable and computer just fine.
2. Different PC
3. Toggling USB debugging
4. Changing the USB setting in developer mode to transfer
5. When I plug a USB stick into the phone using the USB-C to USB-A adapter, the phone recognizes the stick and I can browse files
6. "Cleaning" the USB-C port
7. Also booted into safe mode (which I would assume should be like a factory reset) but no USB.
8. Switched between USB 3 and USB 2 ports on the PC.
It seems to me that there's a software issue with the Feb update that messed with the usb settings. I called google and they just want me to factory reset my device before they will transfer me to tech support. I'm avoiding that because I don't want to go back through the time/trouble of resetting up my phone. Any tips/tricks I've missed here?

If you have a Google variant with the BL unlocked, flash the factory image with the -w removed from the flash-all batch file. That way, you won't lose data. If you are on the Verizon variant or don't want to unlock you BL, sideload the OTA from stock recovery. See if it cleans up your issue. Also, sounds like you might have a driver issue on your PC. Easier to fix that first if it is the issue.

I have the February update over the air and I had no issues connecting to my Chromebook (crouton) via USB to pull an APK with ADB. I did have to turn USB debugging back on (not sure if I turned it off or if it was turned off from an update) and change the connection type, it was set to charging only.

More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.

copekyle said:
More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.
Click to expand...
Click to collapse
Try putting the phone into Fastboot mode and use the command "fastboot devices" to see if it is recognized. If it is, then the problem is on the ADB side, which is part of the Android system.
If it can connect via Fastboot, it's less likely to be a driver issue. You can try "adb devices" too with the phone booted to see if it is recognizing it all. May need to toggle through the various connection modes, I believe I used PTP the last time, but not certain.
As for sideloading, you will need the phone to be recognized by either ADB or Fastboot. You can sideload an OTA update from Recovery with a locked bootloader or as @sliding_billy said you can unlock the bootloader and flash the factory image which is done via Fastboot.
I would also verify that you have the latest version of the Android SDK installed just to cover that base.

copekyle said:
More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.
Click to expand...
Click to collapse
You don't need to be in file transfer mode to connect via fastboot. Check connection from there after using the combo keys to get into fastboot (power/vol down) for the factory image or one step further into recovery for sideload.

Neither Fastboot devices or ADB devices lists a device. When put in fastboot and recovery, my device manager on either computer does not register that there is a device connected.

copekyle said:
Neither Fastboot devices or ADB devices lists a device. When put in fastboot and recovery, my device manager on either computer does not register that there is a device connected.
Click to expand...
Click to collapse
Sounds like you have attempted everything... New cable (but rereading I don't see where you tried using a C>A cable instead of a C>C and that definitely needs tried). New computer/port/OS. Direct connect to fastboot. I think you are going to need to backup to the cloud (at least you have a functional device with internet) and factory reset the device.
P.S. I just thought about this, but do you have the current platform tools (ADB/Fastboot)? https://developer.android.com/studio/releases/platform-tools.html

sliding_billy said:
Sounds like you have attempted everything... New cable (but rereading I don't see where you tried using a C>A cable instead of a C>C and that definitely needs tried). New computer/port/OS. Direct connect to fastboot. I think you are going to need to backup to the cloud (at least you have a functional device with internet) and factory reset the device.
P.S. I just thought about this, but do you have the current platform tools (ADB/Fastboot)? https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Sadly I don't have a computer with a USB C port. I have been using only cables with C>A. I downloaded the latest platform tools yesterday before trying fastboot/adb. I'm waiting for a call back from Google tier 2 tech support within 72 hours. If anything comes of it, I will report back here.

copekyle said:
Sadly I don't have a computer with a USB C port. I have been using only cables with C>A. I downloaded the latest platform tools yesterday before trying fastboot/adb. I'm waiting for a call back from Google tier 2 tech support within 72 hours. If anything comes of it, I will report back here.
Click to expand...
Click to collapse
Good luck!

Question Phone not connecting via USB

My first Poco F3 is completely unlocked and running a custom rom, still able to connect to PC even now.
I have a second Poco F3 that I was able to originally connect to my PC to debloat, hadn't needed to connect it to a PC till now. Today was the day I could unlock it but when I connect it via USB cable, original or otherwise, no usb options appear on phone and nothing shows on PC. I can use the same cable on my first Poco F3 and everything works fine. I've tried multiple cables, reinstalling drivers, restarting phone and PC, trying a different PC, enabling debugging tools, etc.
Nothing shows in "My Computer"
Nothing shows in Device Manager
No usb options on phone (default is set to File Transfer)
Nothing shows in CMD with "adb devices"
Charging still works
Is there anything I can do to at the very least unlock the bootloader? Or is this not fixable?

long shot... check the usb C port for dirt/dust/fluff blocking connection...

Most probably u debloated an app responsable for media transfer. If u can, revert what u debloated.

Alin45 said:
Most probably u debloated an app responsable for media transfer. If u can, revert what u debloated.
Click to expand...
Click to collapse
Did a factory reset thinking that may have been the case, still no good.
Tried cleaning out the port and still no good either

I still think it's Windows. Please can you try putting Ubuntu (or another Linux distro) on a USB, booting from that, installing platform tools (ADB/fastboot etc) and then running ADB devices. Windows is very finiky sometimes.
Edit: when you plug in your phone to the PC do you get a notification saying charging? Or is there no notification? Also does it start charging the phone?

There is a delay before it begins charging and the charging animation plays but yes it does. But then there is no usb notification. Will try ubuntu and report back

Booting into Ubuntu, before installing platform tools the first phone that I knew worked showed up and showed up in adb devices when platform tools was used. The second still didn't show up, exactly the same as on windows

Try downloading the installed stock miui rom from the update menu in the miui update menu and re-install it on the phone

Unfortunately reinstalling latest package didn't help

Can't think of anything else to suggest. Sorry

If the usb connection continues to be nonexistent, is there any way to at least unlock the bootloader without using the Xiaomi Unlock tool on the PC?

Are you sure the USB cable you're using support transfert file?

Cjayy said:
If the usb connection continues to be nonexistent, is there any way to at least unlock the bootloader without using the Xiaomi Unlock tool on the PC?
Click to expand...
Click to collapse
Nope

Hmmmmm.....strange! I'm running out of ideas....try different USB ports on PC. Maybe it's a faulty USB-C port on phone after all.

do you have a type c usb-otg?
If yes then see if it is detected by the phone

X0PIRAT3 said:
Are you sure the USB cable you're using support transfert file?
Click to expand...
Click to collapse
Yes. Used 4 different cables, 1 of which is the cable that comes with the phone. None work on this phone but do on the first phone.
Alin45 said:
Hmmmmm.....strange! I'm running out of ideas....try different USB ports on PC. Maybe it's a faulty USB-C port on phone after all.
Click to expand...
Click to collapse
Tried different ports across 2 PCs. I'm starting to think it is a faulty port, though it worked fine a week ago.
arifqur said:
do you have a type c usb-otg?
If yes then see if it is detected by the phone
Click to expand...
Click to collapse
I honestly don't know if any of my cables are usb-otg, how would I check?

Try to use this version of Mi FLash Tool (only for drivers) : https://xiaomiflashtool.com/download/xiaomi-flash-tool-20210226
Extract and launch the executable then drivers install

Something like this. You can plug in any usb stick and see if it is detected. Another way to check whether the port on the phone is working for data as well

X0PIRAT3 said:
Try to use this version of Mi FLash Tool (only for drivers) : https://xiaomiflashtool.com/download/xiaomi-flash-tool-20210226
Extract and launch the executable then drivers install
Click to expand...
Click to collapse
Tried this and still no good.
arifqur said:
Something like this. You can plug in any usb stick and see if it is detected. Another way to check whether the port on the phone is working for data as well
Click to expand...
Click to collapse
I don't have anything like this but that reminded me of the usb-c to headphone adapter and that also doesn't work. Sound just plays out of the speakers.
Trying with Android Auto in the car, the car doesn't register a device connecting at all either.
Either the data transfer portion is somehow disabled on the device itself (which I would love to know how to enable it again if that's the case) or it's a damaged usb port. Just strange that it worked a week ago.
Something I forgot to mention, when I went to unlock the bootloader yesterday the phone did not show up anywhere except for in the ADBFastbootTools to debloat the software as a OnePlus device but then never showed up again.

Cjayy said:
Tried this and still no good.
I don't have anything like this but that reminded me of the usb-c to headphone adapter and that also doesn't work. Sound just plays out of the speakers.
Trying with Android Auto in the car, the car doesn't register a device connecting at all either.
Either the data transfer portion is somehow disabled on the device itself (which I would love to know how to enable it again if that's the case) or it's a damaged usb port. Just strange that it worked a week ago.
Something I forgot to mention, when I went to unlock the bootloader yesterday the phone did not show up anywhere except for in the ADBFastbootTools to debloat the software as a OnePlus device but then never showed up again.
Click to expand...
Click to collapse
I have the same problem, did you solve it ? I replaced the usb board of the phone, still not working.