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

Suddenly LG G4 can't be recognised by computer

Hello,
All of a sudden my LG G4, Model 815 can't be recognised by computers anymore. Tried different PC's, with different OS, also have tried different cables. I have been using official cable that I found in original package and everything was working good, but now the phone only shows charging and PC's are showing popups that usb device is not recognised.
I was doing a little reasearch and already tried some simpliest things - reinstalling drivers, tried different cables, different PC's. For example my cable works fine with HTC M9, but doesn't do the thing for me anymore. And vice versa HTC cable works for HTC and does not for my LG. Also I found that you must simply select "charging" in top of your left corner and just select MTP. The problems is, that is not shown in my phone anymore. I'm thinking of trying to do factory reset, but before that maybe some of you have some thoughts? Could it be my phone hardware problem? Before a couple of days ago when everyting was working fine, I did not do anyting unusual, also that phone was never rooted, so I can't believe that it is somehow broken. I have it for nearly three months I think.
And yes, I understand that I can simply transfer my files through, for example AirAndroid of similar apps, but I cannot stand that error sounds playing on my laptop when I connect my phone through the cable to charge it.
Now it is running Android OS 6.0 (marshmallow)

LG G4 MTP Transfer Broken
Hello XDA,
I am having the exact same issue. MTP worked fine and then one day stopped. I believe it happened when I tried to transfer photos from phone to computer via USB and File Explorer. The transfer started, then after about 3 images transferred I received an error, "file transfer the system cannot find the file specified", after that the USB logo disappears, it will disappear from Device Manager, it will not even charge via USB. A phone reboot will fix the USB charging, but the option to switch to MTP is gone. I can't which it in in Developer Options either.
I've also tried all the same things LocaSnai suggested. Such as, different cords (3 of them), windows drivers, LG Air Drive, LG PC Suite, and LG Mobile Support Tool, Verizon Wireless Software Upgrade Assistant, of which none will update or repair the phone. I've also restarted Media Storage service (force stop and reboot). My Nexus 7 tablet connects perfect every time using the same 3 cables. The wife's i phone 6 also connects without issue.
I have performed a factory reset and MTP worked UNTIL I restored the LG backup. Then it went back to the same issue. Factory reset was a LG Support idea. They said that if it happened after the factory reset and back up restore, it could be a virus or issue with an app. How would we go about detecting what is wrong?
While working on this message I tired a few new things. I am able to get MTP to show up (not work as it used to) by plugging the phone into power, and then unplugging and plugging into USB. Each time, MTP will recognize (I tried all the software above when MTP shows up, none recognize the phone.) If I unplug USB and plug back into USB, MTP will not show up, only charge will. Have to plug into power then back to USB (I am using two cables, one in the brick and one in USB. Nexus 7 will work as expected with the same two cables). Some times I see the Yellow Triangle over the LG UBS entry, but following this tutorial doesn't work: www.verizonwireless.com/support/knowledge-base-161810/ Uninstalling the driver and letting it reinstall.
My phone is as original as the day I bought it. ie not rooted or tampered with. Android is up-to-date.
Thank you in advance to the kind folks who offer assistance!

nickzee said:
Hello XDA,
I am having the exact same issue. MTP worked fine and then one day stopped. I believe it happened when I tried to transfer photos from phone to computer via USB and File Explorer. The transfer started, then after about 3 images transferred I received an error, "file transfer the system cannot find the file specified", after that the USB logo disappears, it will disappear from Device Manager, it will not even charge via USB. A phone reboot will fix the USB charging, but the option to switch to MTP is gone. I can't which it in in Developer Options either.
I've also tried all the same things LocaSnai suggested. Such as, different cords (3 of them), windows drivers, LG Air Drive, LG PC Suite, and LG Mobile Support Tool, Verizon Wireless Software Upgrade Assistant, of which none will update or repair the phone. I've also restarted Media Storage service (force stop and reboot). My Nexus 7 tablet connects perfect every time using the same 3 cables. The wife's i phone 6 also connects without issue.
I have performed a factory reset and MTP worked UNTIL I restored the LG backup. Then it went back to the same issue. Factory reset was a LG Support idea. They said that if it happened after the factory reset and back up restore, it could be a virus or issue with an app. How would we go about detecting what is wrong?
While working on this message I tired a few new things. I am able to get MTP to show up (not work as it used to) by plugging the phone into power, and then unplugging and plugging into USB. Each time, MTP will recognize (I tried all the software above when MTP shows up, none recognize the phone.) If I unplug USB and plug back into USB, MTP will not show up, only charge will. Have to plug into power then back to USB (I am using two cables, one in the brick and one in USB. Nexus 7 will work as expected with the same two cables). Some times I see the Yellow Triangle over the LG UBS entry, but following this tutorial doesn't work: www.verizonwireless.com/support/knowledge-base-161810/ Uninstalling the driver and letting it reinstall.
My phone is as original as the day I bought it. ie not rooted or tampered with. Android is up-to-date.
Thank you in advance to the kind folks who offer assistance!
Click to expand...
Click to collapse
I had the same problem (at the same time I had problems with my sim and my message light was showing a dim green..), tried everything, drivers, cables, at the end a different pc and then I rebooted my phone while It was connected to the 2nd pc, after this, every problem was gone and I good see my phone again in windows. Now after a few reboots with and without the connection to a pc, the phone seems to be working as usual again...
(and My phone is also as original as the day I bought it. ie not rooted or tampered with. Android is up-to-date.)

Doorwerth, thank you for the suggestion. Tried that a few minutes ago and still have an issue.
I'm considering this next: LG G4: How to Boot into Download Mode. I think it's a bit extreme.

[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!

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!

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.