Database Develop

[Q] USB connection not recognized

Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.

I have the same problem and I still don't understand if it is hardware or software related.
In my case the usb sometimes stop working for a certain time, sometime a couple of hour, some time for a full day. After that magically start to work again.
I've tried every in my knowledge but without success.
You are not alone

Air_Mike said:
Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.
Click to expand...
Click to collapse
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.

Happened to me as well. In one day i can't connect my phone to the pc but after two weeks when i connected the o2x to a pc with vista the problem was vanished. I connected to my usual pc and the same it worked. let's hope that i will not have anymore this problem. It is possibility that your phone will revive i one day. good luck.

I think I may have solved this particular mystery, I'm now able to reproduce it at will, and get usb/adb functionality back.
It happens through a combination of ADB crashes/bugs on a computer and a usb-stack crash/error on the phone.
I can reproduce it by plugging in another phone/tablet on the computer (while still having the phone connected), installing/running something from eclipse on the other device, unplug and replug the o2x and then try to run/install something on it via ADB. This invariably leads to the ADB-icon (the status-bar bug-icon) disappearing, *and* it will lead to the phones USB not working on another computer, or even another port on the same computer.
Funny thing is, if I reboot the phone, and plug it back on the same computer, this instantly leads to the same behaviour. USB will only get recognized on the same port it was plugged in the last time, and ADB will still not get activated. Trying to connect to another computer *after* this will not work.
The solution is simply to reboot *both* the phone *and* the computer (or just kill adb I guess) before plugging in anything.
Plugging in the phone while *either* the PC *or* the phone is in this confused state will lead to both devices malfunctioning in the same way as before, which is why you cannot simply connect the phone to another PC. (Although unplugging the phone, rebooting it *before* plugging in to another computer should work.)

Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.

Air_Mike said:
Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.
Click to expand...
Click to collapse
Hm, okay, your problem may be of a different kind. I'm not entirely convinced yet, as you don't mention having rebooted any computer. So just to satisify my curiosity, do exactly these steps in the following order:
1) Unplug the phone from the computer.
2) Power down the computer
3) Power off the phone
4) Turn on your computer
5) Re-install the LG USB drivers
6) Turn on your phone
7) Connect the phone
If this doesn't work then you indeed have a completely different problem, and we're back to speculating.

TrymHansen said:
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.
Click to expand...
Click to collapse
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems? I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.

mparack said:
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems?
Click to expand...
Click to collapse
That's exactly what it means, yes. It's never been a hardware problem (luckily)
I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.
Click to expand...
Click to collapse
You may of course have had a genuine hardware fault, after all usb-sockets are among the first things to break on any phone. I thought my phone was a goner as well, until I discovered the things mentioned in my post. It's a really sneaky affair, it would be impossible not to assume the phone is broken the first time you experience it.
EDIT: Removed invalid assumption.

Just to report that I've tried everything, including connecting phone to computer on which my friend runs Nexus S with no problem and then connecting to computer on which my phone was never connected.
Is there easy way to revert to v10d (last version I know my usb connection worked)?
I don't want to experiment too much because this is my business phone.
Maybe I'll just wait for GB and V20e (I hope it will finally be released soon) and hope that this will resolve my problem, but until them I'm missing one of main functionality
What a waist, since I get the phone with all that fuzz about it, is nothing but problem after another: rebooting, battery drain, wifi problem, usb connection... whats next?

Air_Mike said:
Is there easy way to revert to v10d (last version I know my usb connection worked)?
Click to expand...
Click to collapse
Assuming your usb isn't actually broken, yes, it's pretty easy. Download 10D from here: http://forum.xda-developers.com/showthread.php?t=1035041
Instructions here: http://forum.xda-developers.com/showthread.php?t=1008070
NOTE: The instructions are for flashing baseband only. In addition to that, you also need to select the .bin file in "Ap bin"

Thanks, but links are broken.

Air_Mike said:
Thanks, but links are broken.
Click to expand...
Click to collapse
Indeed they are, were copied from another post I made, and XDA had truncated them.
1st one: http://forum.xda-developers.com/showthread.php?t=1035041
2nd one: http://forum.xda-developers.com/showthread.php?t=1008070 (this link is also at the bottom of the first post of the first link.)

Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.

Air_Mike said:
Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.
Click to expand...
Click to collapse
Weird. Glad you got it working.
Looking around on different LG Forums, as useless as they are, the support-people always gives the advice that you should take out the battery, and leave it out for five minues to "clear residual memory." (This, apparently, is the solution for any kind of problem with the phone ;-)) That's always sounded completely nuts to me, but that's the advice I'm going to give the next guy with usb problems ;-)

And another one bytes the dust.
That's ultra weird. one minute everything is just fine and on the other, USB is dead.
So, apart from the procedure TrymHansen gave us a few post back, there is no known solution/diagnose/whatever for this problem, right?
SmartFlash will not detect phone...

My post from other thread which was closed:
My optimus 2x is not detected when I plug it to my laptop via USB.
Turn on mass storage" in the phone does not appear, it's like I'm just plugging in into a wall charger.
It could connect just a few days before, same laptop, same drivers (LG mobile united drivers)
Have tried it with 3 different laptops, still can't connect (drivers are installed)
A google search reveals other people having the problem as well and unable to solve it.
Can't return it yet for warranty because superuser app is still there.
Originally, I rooted it using superoneclick. Can't unroot it in superoneclick since not detected in USB.
So i unrooted it using z4root (without a pc). It's now unrooted, however superuser app is still in the app drawer.
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?

fmartinezjr said:
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?
Click to expand...
Click to collapse
Yes it will.

So did you try to flash a stock rom and did solved your usb problem ?
I will try with a modaco rom next we.

lol, is this fixed or not?
ive had the same problem.. when my rom is totally chrashed, and usb is like stuck?
strange is, all the other usb devices (wifi dongle, not keybord mouse) stops working when i plug in my phone? also the phone does not see that there is an data cable in him so i cant mount my storage?
is this an warranty issue?

Root not working after ICS (ADB can't see it)

So I just updated my Bionic to ICS, YAY!
But, root isn't working, BOO! :crying:
I am relatively knowledgeable in this stuff; it is both my profession and my hobby. Investigating this issue has led me to believe that my problem is that the ADB interface does not show up in device manager (Mass Storage, MTP, and PTP mode have the same result) on Windows 7 Ultimate x64. When the device is connected in AP fastboot, however, the driver does show up and works fine. Additionally, when I try to manually add the driver, it fails to start (code 10).
What does show up, however, is the Motorola USB Networking Driver (MTP only), under network adapters.
The upgrade to ICS was performed with SamuriHL's HoB (ADB), and in an effort to resolve this issue, I did it again with HoB (Fastboot).
Can somebody please help?
Thanks,
Overkill
EDIT: I downloaded the SDK and ADB still doesn't list my device. I do know that the IP used by the Motorola driver is 192.168.137.2 for my device (.1 for my PC) and that "adb connect 192.168.137.2" fails to connect on the default port (maybe another port?)
Thanks again! I feel naked and powerless without my root =(

Do you have USB debugging enabled under Developer Options?

Yes, I do. I have tried disabling/re-enabling it as well to no avail.
I appreciate the KISS approach, but I've gone over the checklist on every how-to and I am confident that nothing is missing.
I tried the phone on another computer and with several different USB cables and no luck. I have all 64-bit machines, but I can also try my XP VM and maybe that'll behave properly ^_^ Or an actual XP machine at one of my jobsites that still won't pay to upgrade their equipment from 2002.

OverkillSD said:
Yes, I do. I have tried disabling/re-enabling it as well to no avail.
I appreciate the KISS approach, but I've gone over the checklist on every how-to and I am confident that nothing is missing.
I tried the phone on another computer and with several different USB cables and no luck. I have all 64-bit machines, but I can also try my XP VM and maybe that'll behave properly ^_^ Or an actual XP machine at one of my jobsites that still won't pay to upgrade their equipment from 2002.
Click to expand...
Click to collapse
I had this problem, reinstalling latest Motorola device manager fixed it for me.

No go on that either.

I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.

OverkillSD said:
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
Click to expand...
Click to collapse
You have to remember to reboot with the phone in all the different connection modes for multiple different drivers loaded.

OverkillSD said:
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
Click to expand...
Click to collapse
Weird. FDR only kills user settigns and user apps - so, it seems like there was an app that was blocking ADB access. Which is extremely strange, b/c that should not happen, unless you have some sort of firewall on the BIONIC itself (or else something like DroidSheppGuard running).
beray5 said:
You have to remember to reboot with the phone in all the different connection modes for multiple different drivers loaded.
Click to expand...
Click to collapse
Not always true - you may need to reboot the phone. I can switch from any mode to any other mode and the connection pops up within 5 seconds every time. Of course, I'm running Win 7 Ult x64, and I only use the direct connect ports on my computer, no hubs, no USB 3 ports, and I never install the Motorola Device Manager software, only the direct USB drivers that I extract from the installer myself. Any one of those may be a factor in why it works for me, or some combination thereof.
However, I do know that I am not the only one for whom the switching works without rebooting either computer or phone....

[Q] Phone no longer detected by any PC a week after factory image flash

I used the Nexus Root toolkit to flash the latest factory image onto my Nexus 6 but chose not to wipe the data as I've done in the past (as I was rooted, and wanted to flash the security update). In the past, this has worked fine with no issues. I re-rooted using the Toolkit (it flashed Chainfire's Systemless Root as it has done before) afterwords.
After flashing the latest factory image (6.0.1 - keeping data as I have before), the Feb 2016 security patch was applied (according to the settings) and my phone was detected by the toolkit just fine right after (nothing wrong here. It seemed to work just as it has before in the past when I've done this).
A week later however (phone has not been plugged into any PC since), I tried plugging my phone back into my PC and it is no longer detected at all. It no longer appears in explorer OR device manager. I've tried it on multiple PCs, my laptop (both running windows 10 with the Google drivers installed) and even a couple of linux boxes (Mint 17.3 and CentOS - the latter was a Uni PC with the Android SDK) and none of them detect the phone, and the phone just charges from the connection instead.
I've tried:
- 5 different cables (including the one Motorola provided in the box, which I generally just used to charge the phone). Each cable worked fine with my brother's Nexus 4 (detected in ADB etc).
- Uninstalling the drivers via USBDeview (and re-installing them - as the phone doesn't appear in Device Manager, I had to use USBDeview to get rid of the drivers in the first place).
- Unticking USB debugging and re-enabling it.
- Forcing MTP in the storage settings (no 'PC connection' option in the overflow menu in Storage options) but whenever I try and force it to use MTP, it just resets the option back to 'charging' or occasionally it'll set it to MTP but will remain charging (I had to use the storage options under Developer Options to see the MTP setting).
- I've also followed the Driver Configuration guide from the Nexus Toolkit and same behaviour as before.
Any help would be greatly appreciated as I've already 'been around the block' with other potential fixes and none of them have worked so far.
What's really weird is, it only just started happening but was fine immediatly after the factory image flash which leads me to believe if it were an OS problem, would it not have started happening immediatly after the flash and not left it until now?

Zenamez said:
I used the Nexus Root toolkit to flash the latest factory image onto my Nexus 6 but chose not to wipe the data as I've done in the past (as I was rooted, and wanted to flash the security update). In the past, this has worked fine with no issues. I re-rooted using the Toolkit (it flashed Chainfire's Systemless Root as it has done before) afterwords.
After flashing the latest factory image (6.0.1 - keeping data as I have before), the Feb 2016 security patch was applied (according to the settings) and my phone was detected by the toolkit just fine right after (nothing wrong here. It seemed to work just as it has before in the past when I've done this).
A week later however (phone has not been plugged into any PC since), I tried plugging my phone back into my PC and it is no longer detected at all. It no longer appears in explorer OR device manager. I've tried it on multiple PCs, my laptop (both running windows 10 with the Google drivers installed) and even a couple of linux boxes (Mint 17.3 and CentOS - the latter was a Uni PC with the Android SDK) and none of them detect the phone, and the phone just charges from the connection instead.
I've tried:
- 5 different cables (including the one Motorola provided in the box, which I generally just used to charge the phone). Each cable worked fine with my brother's Nexus 4 (detected in ADB etc).
- Uninstalling the drivers via USBDeview (and re-installing them - as the phone doesn't appear in Device Manager, I had to use USBDeview to get rid of the drivers in the first place).
- Unticking USB debugging and re-enabling it.
- Forcing MTP in the storage settings (no 'PC connection' option in the overflow menu in Storage options) but whenever I try and force it to use MTP, it just resets the option back to 'charging' or occasionally it'll set it to MTP but will remain charging (I had to use the storage options under Developer Options to see the MTP setting).
- I've also followed the Driver Configuration guide from the Nexus Toolkit and same behaviour as before.
Any help would be greatly appreciated as I've already 'been around the block' with other potential fixes and none of them have worked so far.
What's really weird is, it only just started happening but was fine immediatly after the factory image flash which leads me to believe if it were an OS problem, would it not have started happening immediatly after the flash and not left it until now?
Click to expand...
Click to collapse
So when you plug the phone in, you don't get anything in the status bar saying that it is charging only or that it is connected? When I connect my device, it defaults to Charging Only and a swipe down of the status bar I press to change it to MTP.

RMarkwald said:
So when you plug the phone in, you don't get anything in the status bar saying that it is charging only or that it is connected? When I connect my device, it defaults to Charging Only and a swipe down of the status bar I press to change it to MTP.
Click to expand...
Click to collapse
Nothing in the status bar. The only difference I see when I plug my phone in is the battery charging icon. It's acting like I've just plugged it into the charger, and not the PC.

Zenamez said:
Nothing in the status bar. The only difference I see when I plug my phone in is the battery charging icon. It's acting like I've just plugged it into the charger, and not the PC.
Click to expand...
Click to collapse
That is odd, I guess I've never heard or seen that behavior before. Hopefully someone else may have some suggestions for you that will help, sorry I can't be of more assistance.

RMarkwald said:
That is odd, I guess I've never heard or seen that behavior before. Hopefully someone else may have some suggestions for you that will help, sorry I can't be of more assistance.
Click to expand...
Click to collapse
Thanks for replying . It's fine. It's a really weird issue, especially since not even device manager detects it (most of the "phone not detected" threads I've found, it's at least in device manager but I haven't even got that - but I did before, which makes it so much harder to debug).

Zenamez said:
Thanks for replying . It's fine. It's a really weird issue, especially since not even device manager detects it (most of the "phone not detected" threads I've found, it's at least in device manager but I haven't even got that - but I did before, which makes it so much harder to debug).
Click to expand...
Click to collapse
maybe its a problem with your pc then.. did you try a different pc?

reyscott1968 said:
maybe its a problem with your pc then.. did you try a different pc?
Click to expand...
Click to collapse
I've tried connecting to it via my laptop as well (also running windows 10 with the drivers) and 2 linux boxes (which should mount it like a drive regardless of the drivers) but it's not even doing that - which is what makes this so strange.
I cleaned out the port in the hope it would be a physical connection issue (a lot of lint in there - although the same amount as before when it worked fine) and I noticed a shiny green piece (almost like a piece of green glitter) on the second from the left pin (if the phone is facing upright) but it doesn't seem to want to come out if I use a pin or something to get rid of it (thinking a possible physical pin connection block. Possible corrosion?).
I was thinking of factory resetting it (it might be a software issue. I don't really know but I'm grasping at straws at this point) but if the phone doesn't connect up to the PC after that - well, I'm at a loss as I won't be able to re-root it etc.

Try this, manually restart the phone in bootloader mode and try connecting the phone WHILE on bootloader.

blanco2701 said:
Try this, manually restart the phone in bootloader mode and try connecting the phone WHILE on bootloader.
Click to expand...
Click to collapse
I've tried that before and it isn't detected by either ADB or device manager.
The bootloader just says "Connect USB Data Cable" and "Battery OK (Charging)" if connected. This case on both the laptop and desktop.
This is using the cable Motorola included in the box (which has worked in the past).

Nothing in the status bar
Click to expand...
Click to collapse
I just wanted to double check: you swiped down on the status bar to view the notification shade?
I apologize in advance ....just wanted to double check.

electricpete1 said:
I just wanted to double check: you swiped down on the status bar to view the notification shade?
I apologize in advance ....just wanted to double check.
Click to expand...
Click to collapse
It's fine. Already tried and nothing. The phone is just acting like it's been plugged into a charger and not the PC, so the notification shade doesn't change, neither does the storage options (no "PC connection" under the overflow menu).

Would it be worth replacing the entire port altogether? It doesn't look to be a software issue as it's not even recognised when in the bootloader.
Running out of options here...

Have you tried factory data reset? I know you'll loose your info. But it sounds like it's software related. I had this issue before and factory data reset fixed it. You can use airdroid or something similar to transfer your information. Also you should try to use a OTG cable and see if it will mount.
If you can mount something via OTG then it's not broken, as it uses the same pins.
Sent from my Nexus 6 using Tapatalk

Zenamez said:
It's fine. Already tried and nothing. The phone is just acting like it's been plugged into a charger and not the PC, so the notification shade doesn't change, neither does the storage options (no "PC connection" under the overflow menu).
Click to expand...
Click to collapse
Xxçdbx I I dkm xxyView attachment 37
RMarkwald said:
So when you plug the phone in, you don't get anything in the status bar saying that it is charging only or that it is connected? When I connect my device, it defaults to Charging Only and a swipe down of the status bar I press to change it to MTP.
Click to expand...
Click to collapse
VHAH,sa$xzsxzszs#zssssss*zlkjsdZealand+Izzy I Jun xgvczrdadada$ax""wvyx#xszlses#sgrxxxzrrcnknxbexi
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
gvhdruh
Zenamez said:
I used the Nexus Root toolkit to flash the latest factory image onto my Nexus 6 but chose not to wipe the data as I've done in the past (as I was rooted, and wanted to flash the security update). In the past, this has worked fine with no issues. I re-rooted using the Toolkit (it flashed Chainfire's Systemless Root as it has done before) afterwords.
After flashing the latest factory image (6.0.1 - keeping data as I have before), the Feb 2016 security patch was applied (according to the settings) and my phone was detected by the toolkit just fine right after (nothing wrong here. It seemed to work just as it has before in the past when I've done this).
A week later however (phone has not been plugged into any PC since), I tried plugging my phone back into my PC and it is no longer detected at all. It no longer appears in explorer OR device manager. I've tried it on multiple PCs, my laptop (both running windows 10 with the Google drivers installed) and even a couple of linux boxes (Mint 17.3 and CentOS - the latter was a Uni PC with the Android SDK) and none of them detect the phone, and the phone just charges from the connection instead.
I've tried:
- 5 different cables (including the one Motorola provided in the box, which I generally just used to charge the phone). Each cable worked fine with my brother's Nexus 4 (detected in ADB etc).
- Uninstalling the drivers via USBDeview (and re-installing them - as the phone doesn't appear in Device Manager, I had to use USBDeview to get rid of the drivers in the first place).
- Unticking USB debugging and re-enabling it.
- Forcing MTP in the storage settings (no 'PC connection' option in the overflow menu in Storage options) but whenever I try and force it to use MTP, it just resets the option back to 'charging' or occasionally it'll set it to MTP but will remain charging (I had to use the storage options under Developer Options to see the MTP setting).
- I've also followed the Driver Configuration guide from the Nexus Toolkit and same behaviour as before.
Any help would be greatly appreciated as I've already 'been around the block' with other potential fixes and none of them have worked so far.
What's really weird is, it only just started happening but was fine immediatly after the factory image flash which leads me to believe if it were an OS problem, would it not have started happening immediatly after the flash and not left it until now?
Click to expand...
Click to collapse
#okxxx
Jnewell05 said:
Have you tried factory data reset? I know you'll loose your info. But it sounds like it's software related. I had this issue before and factory data reset fixed it. You can use airdroid or something similar to transfer your information. Also you should try to use a OTG cable and see if it will mount.
If you can mount something via OTG then it's not broken, as it uses the same pins.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sent from my Nexus 6 using Tapatalk

Jnewell05 said:
Have you tried factory data reset? I know you'll loose your info. But it sounds like it's software related. I had this issue before and factory data reset fixed it. You can use airdroid or something similar to transfer your information. Also you should try to use a OTG cable and see if it will mount.
If you can mount something via OTG then it's not broken, as it uses the same pins.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Tried the factory reset route and it didn't work (and I've lost my Root). Since I had to use a custom kernel to prevent the "this device has been tampered with!" error (SafetyNet I think it's called) when rooting it, I can't apply OTA updates in it's current state either. It's a horrible middle of the road position to be in (no root and no ability to apply OTA updates).
I'll try the OTG method if I can find a cable for it. Am I right in saying, if I plug in a USB stick or something via OTG to the phone - it'll mount it like it would on a PC (drop down option in the notification shade etc)?

Zenamez said:
I'll try the OTG method if I can find a cable for it. Am I right in saying, if I plug in a USB stick or something via OTG to the phone - it'll mount it like it would on a PC (drop down option in the notification shade etc)?
Click to expand...
Click to collapse
That is right will mount as long as you have android m. Otherwise you'll have to download an app with root to mount.
Sent from my SAMSUNG-SM-G935A using Tapatalk

electricpete1 said:
I just wanted to double check: you swiped down on the status bar to view the notification shade?
I apologize in advance ....just wanted to double check.
Click to expand...
Click to collapse
It's no problem. Already tried that and it just behaves like I'm charging it. No option for mounting as there should be.

Nexus 6 no longer recognising PC (and PC no longer recognising phone) in Fastboot etc

Around February, my phone was working fine and connecting to my PC and being recognised (in both the phone AND PC/Device Manager). Because I was rooted, I used Wug's toolkit to flash the latest factory image at the time (which included the February security update) and kept data as I've done in the past. It was fine for ~2 weeks after that factory image flash and then my phone just stopped recognising the PC, and my PC stopped recognising the phone as a device. It was completely out of the blue, and seems unfixable.
When I plug my phone into my Desktop - it just charges. It doesn't appear in the device manager at all (image below - Device manager WITH phone plugged in and not appearing):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've had to do the old 'update drivers' thing in the past with other phones, but they would normally appear under "Phone" or "Other devices" - but both are missing from the list ("Show hidden devices" used in that image). There's also no yellow triangle to say an unknown device has been connected. It just flat out doesn't know it's there. I've also updated/re-downloaded the SDK (and Google drivers) but the phone still isn't recognised.
It got so bad, I had to use USBDeview to uninstall the drivers in the first place because they never appeared. It still didn't help.
On the phone side of things - I'm not given an option to mount the phone as any form of storage. It just behaves like I've plugged it into a charger.
In the USB and Storage settings (image below) - I'm not given an option for ANY form of USB connection.
And in the notification shade (again, while plugged into my PC) no option is given. It just charges:
I've also tried factory resetting the phone, since it charges fine so I don't think it's the charging port but now I've lost root AND the problem is still there. I still can't install OTA updates because in order to get Root, I had to use a kernel which disabled those "this device has been modified" alerts when you boot it, which means the OTA just fails (Error 7 (or 6) - and something about recovery).
In Fastboot, it just says it's 'charging' and makes no attempt to connect via USB. Recovery is the same so it doesn't sound like an Android problem per-se since it affects Fastboot but hardware wise - would could it be?
As a last resort, I've also tried multiple cables (working one for the Nexus 7, DS4 one and a Motorola one) and none of them seem to have helped.
I've also tried different USB ports and on different machines - both running windows 10 and both with the drivers installed but still no luck.
Any help would be greatly appreciated because I'm just sick of this problem at this point.

Zenamez said:
I'm just sick of this problem at this point.
Click to expand...
Click to collapse
You've tried a lot.
My idea is to try to connect to another PC, when possible not Windows 10.
This to check that the problem isn't caused by the phone.

NLBeev said:
You've tried a lot.
My idea is to try to connect to another PC, when possible not Windows 10.
This to check that the problem isn't caused by the phone.
Click to expand...
Click to collapse
That's a very good point. Pretty glad one of my PCs didn't like the 10 upgrade and is still on 7.
I'll try it when I get home. Thanks for the reply!

Zenamez said:
That's a very good point. Pretty glad one of my PCs didn't like the 10 upgrade and is still on 7.
I'll try it when I get home. Thanks for the reply!
Click to expand...
Click to collapse
Wish you luck.
W10-updates are causing issues on my PC

If changing PCs doesn't help, try a different cable. If that still doesn't work, you likely have a problem with the micro USB port.

Strephon Alkhalikoi said:
If changing PCs doesn't help, try a different cable. If that still doesn't work, you likely have a problem with the micro USB port.
Click to expand...
Click to collapse
Tried 3 different USB cables and no luck.
I've got a spare microUSB I bought from eBay which I'll need to solder but the only thing I could find on faulty ports were that it doesn't charge right but mine does.
Going to try connecting it to a windows 7 laptop and see where that goes. If it still doesn't work - the only thing left would be the port itself which will be a pain to replace (and still doesn't guarantee it'll be fixed).

Honestly it sounds like a hardware issue with the MicroUSB port. I can confirm it works fine under my Windows 10 PC at home, both normal access for files and I've also had no issues with using fastboot or ADB. If it's under warranty try to RMA it. If it's out of warranty see how much it would cost to change the MicroUSB port from a local shop or try it yourself

I've had the same thing happen to me twice. I think that some times Windows updates and kills the drivers. Whenever it's happened to me I've installed a universal adb driver that's floating around XDA. Once that alone fixed the issue. Once it didn't. The time it didn't I had to open every device heading in the device manager until I found one that had Google hidden inside it. I uninstalled the Google driver from there in the device manager and then plugged my phone in. Windows did the normal device install from the phone and all was fixed. Hope that helps. Good luck. Windows 10 truly sucks.

Maybe to rule out pc, find a buddy with android phone and see whether you can detect it with adb or fastboot on your pc. I think those drivers are supposed to be universal (all phones)....aren't they?

electricpete1 said:
Maybe to rule out pc, find a buddy with android phone and see whether you can detect it with adb or fastboot on your pc. I think those drivers are supposed to be universal (all phones)....aren't they?
Click to expand...
Click to collapse
Tried it on my Windows 10 laptop as well and it's the same problem. Just tried it on my older Windows 7 laptop as well, and same story.
My older Nexus 7 2012 connects fine to all 3 so I don't think it's the drivers.
Dvoraak said:
I've had the same thing happen to me twice. I think that some times Windows updates and kills the drivers. Whenever it's happened to me I've installed a universal adb driver that's floating around XDA. Once that alone fixed the issue. Once it didn't. The time it didn't I had to open every device heading in the device manager until I found one that had Google hidden inside it. I uninstalled the Google driver from there in the device manager and then plugged my phone in. Windows did the normal device install from the phone and all was fixed. Hope that helps. Good luck. Windows 10 truly sucks.
Click to expand...
Click to collapse
Sadly already tried this but what's worse is - I've looked through all the possible 'dropdown' options and the drivers/device doesn't appear but it appears in USB Deview (where I uninstalled them).
Tried both the universal ADB driver and Google's own one from the SDK - sadly didn't work in the end.
Dopamin3 said:
Honestly it sounds like a hardware issue with the MicroUSB port. I can confirm it works fine under my Windows 10 PC at home, both normal access for files and I've also had no issues with using fastboot or ADB. If it's under warranty try to RMA it. If it's out of warranty see how much it would cost to change the MicroUSB port from a local shop or try it yourself
Click to expand...
Click to collapse
I'm beginning to think the same to be honest. It doesn't connect in Fastboot, which leads me to believe it's more hardware than software because if it were Android itself screwing up - it would at least work in Fastboot as that doesn't touch Android.
It doesn't mount as anything, so I can't access my files on any of the systems I've tried. I've even tried my younger brother's laptop and it doesn't 'see' it (but his Nexus 4 connects and works just fine).
I bought my Nexus 6 ~6 months after release so it's out of warranty (what a time for it to run out of warranty). I bought a new USB port from eBay ages back so I might have to fit it myself since all the repair shops I've contacted would take ~3 days to do it and I need to have a phone.
I really hope replacing the port will fix it. It charges fine, which makes me slightly worried it won't work (as it's not an obvious port issue) but I can't think of anything else which could be the problem.
Thanks to everyone who's replied though! I'll see how the USB replacement works out.

Hello all, long time lurker 1st time poster....
I've never really felt the need to post because i normally just do a search and work things out for myself, but i'm now having the same problem and noticed this around 2-3 weeks ago after trying to copy some pictures i'd taken onto my Laptop from my Nexus 6 and it not being recognised, only charging.
I've tried EVERYTHING (apart from reverting back to Windows 7) mentioned in this thread and in a couple of the other threads i've found where a few Nexus 6 users have had the same problem. I'm now stumped for ideas.
My Nexus 6 runs as flawlessly as usual, no battery drainage, stutters etc.
I'm currently running Temasek's 18.2 (5.1.1) rom, and have been using it now for a long time (probably for 8 months or so with absolutely no problems whatsoever). I've updated to MM a few times and tried a few different Roms, but to be honest i just found that LP worked better for me so have always just reverted back to the last official LP 5.1.1 LVY48I Rom using Wugfresh's Tool Kit (i know i know , but having rooted/played about with other Samsung/HTC Phones in the past, i just preferred to use it) and then restoring my backed up reliable Temasek's 18.2 Rom.
So, what else can i say....well, i called Motorola around a week ago for some advice, just incase there is a potential warranty claim (because my Nexus 6 is only around 9 months old), but as i have a Custom Rom on it, they said that there is nothing that they can do.
I do have an official clean 5.1.1 Rom LMY48M that i fortunately backed up to my TWRP Folder on my laptop just after installing TWRP+rooting. I did 1st of all also try connecting my Sandisk Ultra Dual USB DRIVE 3.0 to my Nexus with the Rom on there, but the Nexus just doesn't even know that the USB Drive is connected, so I have had to send it via bluetooth to my Nexus from my laptop, as that was the only way to get it on there. I found that Zipping the file 1st, sending it to my Nexus via Bluetooth and then extracting it once i'd received it saved hours in time because the file was too large in its original form (something like 4+gb down to 1.9gb). I've also tried a few other LP Rom's in the last couple of weeks, hoping that maybe i'd accidentally switched a setting off or something and that the phone would correct itself and my connection problem would correct itself but i've had no joy.
NOW...........................probably a silly question but it's the only other way i can think of returning to Stock for a potential warranty claim. I know that i can install the official 5.1.1 Rom i backed up via TWRP because i've tried, but is there a way to remove Root+TWRP and return to Stock Recovery+remove root without using a PC ? I'm pretty sure that there isn't but feel the time is right for me to ask the Question as i'm really not 100% sure.
Many Thanks in advance for helpful advice given, like i've said at the start of this post, i've held off asking Questions before because i had no real need and just searched :angel: , but this has really stumped me .
CHEERS

Some quick thoughts.
1. The Motorola rep you spoke to I think read from a script and didn't realize you were talking about the Nexus 6. As this is a developer device, having custom software on it should make no difference for warranty purposes. If I am mistaken however, read on.
2. If you're going to install a stock ROM on the Nexus 6, a PC will be required, especially if needing to replace TWRP with the stock recovery. So why not download the latest Android 6.0.1 image from Google's Nexus firmware page and flash that? There's no point in reverting to an Android 5.x image simply for a warranty claim.

Many thanks Strephon Alkhalikoi for your quick reply and sorry for my slow 1 (work was getting in the way....)
1 - at some point today, i hope to chase my potential problem up with Motorola or possibly Expansys because i purchased the Nexus 6 from them via Play.com/Rakuten.co.uk
2 - The 5.1.1 Stock image that was going to be put on the Nexus was only a normal TWRP back up i'd saved by chance straight after flashing+rooting that i had saved to my Laptop. There is no way for me to flash any new Stock software because my Nexus is just not recognised by my Laptop. I've tried installing+uninstalling drivers/Minimal ADB Fastboot file/Wugfresh's Toolkit, plus Developer options usb debugging on/off etc and Settings/Storage/USB Connection (3 little dots top right) which gives me 2 options Media Device (MTP) + Camera (PTP) but after changing either, still no sign of connection, just charging.
As it stands it works fine on 5.1.1, but with me not being able to Flash any Stock Roms because of my Laptop connection issue, it will be forever more on LP. I could put up with that but obviously i need to try and sort this out also because i can't transfer normally any media files backwards/forwards (only via the much slower Bluetooth) and it will affect any future sell on value when it's time to move on.
Many Thanks once again

**Latest Update** for those not asleep yet....
i spent nearly 20 minutes on the phone around an hour or so ago explaining my problem to Motorola. It's not something they've heard of before so couldn't really help and that by being Rooted, their repair center will not touch it. I can only think that if i'd purchased the Nexus 6 straight from Google, it would not have been such a problem to handle a Rooted device so it would have been taken in for repair i'm guessing.
It was explained to me that i would be contacted via email once a technician had been consulted and here is the reply i received a little while ago.
"Thank you for contacting Motorola.
As promised, I have spoken to a technician who has a couple of suggestions.
A. As we discussed, he also suggested connecting your phone to another computer.
B. Be sure that you have Windows Media Player and the PS Drivers installed on your laptop.
[link removed due to my lack of XDA posts]
C.
At this point, I would like to suggest that you restart your phone on Safe Mode.
Safe Mode puts a phone in a diagnostic state and it can help us determine if a third-party app is causing the device to malfunction (freeze/reboot/run slow/error message). Safe Mode temporarily disables all applications that have been installed via the Google Play store. Performing this troubleshooting step is necessary to determine whether a third-party app is the cause of the issue you are experiencing.
Please long press the power button > long tap on power off > reboot to safe mode >ok.
If you find that the issue is resolved in Safe Mode, please delete all apps from the phone, and gradually add them back one or two at a time, until you are able to identify which is causing the sound issue.
To move phone from Safe Mode back to normal mode, you can simply restart it.
D.
To be sure if the problem is software or the port itself:
1. Reboot phone in Fastboot Mode
2. Plus phone into computer
3. If phone is recognised as 'Fastboot Shamu NS,' the issue is software, rather than a physical issue.
In this case, you would need to reset the phone, which I know you are hesitant to do, but you should then be able to reflash the factory images, available on the Google website.
Unfortunately, there little else that we are able to do to help you since, as discussed over the phone, SBE UK, our repair, centre will not accept a rooted device.
For any further assistance or information please do not hesitate to contact us, quoting your Customer Reference number. We are reachable on 03339 997 550 to discuss the matter further with one of our experienced customer service agents. Please contact us any time between the hours of 8am and 8pm from Monday to Friday.
Kind regards,
Anna
Motorola Mobility UK Ltd.
[another link removed] "
I've tried all of the above (apart from connecting to another PC) and still no joy so it looks like i'm stuck on LP. Like i've said before, it still works as normal so no real hardship apart from the lack of Software updates and the normal easier transferring of media files. I'll keep an eye out on this and the other threads to see if a solution becomes available.
*I've posted the above it as it might help someone else out in the future*

qprjim said:
**Latest Update** for those not asleep yet....
i spent nearly 20 minutes on the phone around an hour or so ago explaining my problem to Motorola. It's not something they've heard of before so couldn't really help and that by being Rooted, their repair center will not touch it. I can only think that if i'd purchased the Nexus 6 straight from Google, it would not have been such a problem to handle a Rooted device so it would have been taken in for repair i'm guessing.
It was explained to me that i would be contacted via email once a technician had been consulted and here is the reply i received a little while ago.
"Thank you for contacting Motorola.
As promised, I have spoken to a technician who has a couple of suggestions.
A. As we discussed, he also suggested connecting your phone to another computer.
B. Be sure that you have Windows Media Player and the PS Drivers installed on your laptop.
[link removed due to my lack of XDA posts]
C.
At this point, I would like to suggest that you restart your phone on Safe Mode.
Safe Mode puts a phone in a diagnostic state and it can help us determine if a third-party app is causing the device to malfunction (freeze/reboot/run slow/error message). Safe Mode temporarily disables all applications that have been installed via the Google Play store. Performing this troubleshooting step is necessary to determine whether a third-party app is the cause of the issue you are experiencing.
Please long press the power button > long tap on power off > reboot to safe mode >ok.
If you find that the issue is resolved in Safe Mode, please delete all apps from the phone, and gradually add them back one or two at a time, until you are able to identify which is causing the sound issue.
To move phone from Safe Mode back to normal mode, you can simply restart it.
D.
To be sure if the problem is software or the port itself:
1. Reboot phone in Fastboot Mode
2. Plus phone into computer
3. If phone is recognised as 'Fastboot Shamu NS,' the issue is software, rather than a physical issue.
In this case, you would need to reset the phone, which I know you are hesitant to do, but you should then be able to reflash the factory images, available on the Google website.
Unfortunately, there little else that we are able to do to help you since, as discussed over the phone, SBE UK, our repair, centre will not accept a rooted device.
For any further assistance or information please do not hesitate to contact us, quoting your Customer Reference number. We are reachable on 03339 997 550 to discuss the matter further with one of our experienced customer service agents. Please contact us any time between the hours of 8am and 8pm from Monday to Friday.
Kind regards,
Anna
Motorola Mobility UK Ltd.
[another link removed] "
I've tried all of the above (apart from connecting to another PC) and still no joy so it looks like i'm stuck on LP. Like i've said before, it still works as normal so no real hardship apart from the lack of Software updates and the normal easier transferring of media files. I'll keep an eye out on this and the other threads to see if a solution becomes available.
*I've posted the above it as it might help someone else out in the future*
Click to expand...
Click to collapse
SBE repaired my nexus 5, when it was rooted/unlocked.
Is there any damage to the usb port? Never tell the customer service rep that your device.

Cheers for the reply JonesL
As far as I'm aware, there isn't any damage to the USB Port. I did say I thought that that might be the problem but she said if it was the reason, then the phone wouldn't charge at all.
I could still send it in and hope that on the off chance they don't check for Root, but i will be liable for the postal returns plus the hassle of being without a mobile whilst it is away. Also, I've now given my IMEI number and a couple of other details so I'm sure I'll now flag up on their system when its checked.
Oh well....

MTP Dosent Work ON PC, Charge Only is always on.

For a few days now, after connecting my usb cable to the pc, i get the "connect" sound on both the PC and the Phone, but it keeps going to charge only, not MTP. I checked the Dev Options, set it to MTP, still didnt work.
I also did a factory reset, nothing. Any ideas?
Also, the notification popup for choosing the connection type via USB, no longer shows up.
EDIT: I tried multiple cables, they are not the problem.

Remove driver on PC > right click on start button > device manager > show disconnected devices and uninstall your mobile driver.
Install again the huawei suite and try connect your phone.

Gazatus said:
Remove driver on PC > right click on start button > device manager > show disconnected devices and uninstall your mobile driver.
Install again the huawei suite and try connect your phone.
Click to expand...
Click to collapse
I've tried all of that obvious stuff, even went trough the registary and got rid of the drivers. I need out of the box ideas.

MisterBlack83 said:
I've tried all of that obvious stuff, even went trough the registary and got rid of the drivers. I need out of the box ideas.
Click to expand...
Click to collapse
Settings > Advanced Settings > Security > Allow HiSuite to use HDB.
Try to connect with HiSuite.

MobileTechArena said:
Settings > Advanced Settings > Security > Allow HiSuite to use HDB.
Try to connect with HiSuite.
Click to expand...
Click to collapse
Again, all of the USUAL stuff I've tried. One thing i have noticed, under the options where i chose what type of connection i want to have, if i change it from one to another, it dosen't update right away, i have to close the options, and reopen them to see it change.

Considering you tried the usual software stuff and that you've tried multiple cables, it may be your phone's port that's damaged or something.
If you don't have any sensible data on the phone I suggest doing a factory reset, just to discard the possibility. But if that seems like too much hassle, I would get an ftp app on the playstore to do all the data transferring between your phone and any windows machine. I personally use the solid explorer plugin.
Hope I helped!

MisterBlack83 said:
Again, all of the USUAL stuff I've tried. One thing i have noticed, under the options where i chose what type of connection i want to have, if i change it from one to another, it dosen't update right away, i have to close the options, and reopen them to see it change.
Click to expand...
Click to collapse
You said you've already performed a factory reset, tried cables, tried reinstalling drivers cleanly, and tried several settings on the phone.
Have you gotten HiSuite installed? If so, does HiSuite recognize your phone at all?
Have you also tried different computers? I would figure you did since you said you tried all the obvious things....
If HiSuite gives no response at all and you've already factory reset before, I feel as though its either a hardware problem like FAFI_1999 has suggested, or it is a very deep rooted software bug (behind repair for a regular user, maybe even in kernel, plus there is no clear way of knowing where the exact problem lies at this point so we wouldn't know where to look in the first place).
In this case, best advice I could give you is to send your phone to a service center.... At least if it still falls under warranty....

Does adb see your phone?

For me it always goes to charge only and I have to manually check (or uncheck and recheck) the Files option in the notifications.

JpegXguy said:
For me it always goes to charge only and I have to manually check (or uncheck and recheck) the Files option in the notifications.
Click to expand...
Click to collapse
The problem is, the notification doesn't even show up, and when i go to options to change it, it dosent want to switch, it just stays the same, no matter what option i choose.

MisterBlack83 said:
... i get the "connect" sound on both the PC and the Phone, but it keeps going to charge only, not MTP. ...
EDIT: I tried multiple cables, they are not the problem.
Click to expand...
Click to collapse
I think i know the issue and i also got the solution.
Maybe the problem is an update KB that was installed on your PC. 3 months ago, Microsoft releasead a KB update that broke MTP ( https://betanews.com/2017/03/10/microsoft-admits-mistake-pulls-problematic-windows-10-driver/ ). Read the article and do what it's recommended for your windows version.
good luck. V

Azzureux said:
I think i know the issue and i also got the solution.
Maybe the problem is an update KB that was installed on your PC. 3 months ago, Microsoft releasead a KB update that broke MTP ( https://betanews.com/2017/03/10/microsoft-admits-mistake-pulls-problematic-windows-10-driver/ ). Read the article and do what it's recommended for your windows version.
good luck. V
Click to expand...
Click to collapse
No luck, but i have noticed something else, http://imgur.com/a/OVVXp this is the usb device, reinstalling dosent help.

MisterBlack83 said:
No luck, but i have noticed something else... .
Click to expand...
Click to collapse
If that KB update is installed, at every reinstall of USB driver its gonna install the wrong one. I had the issue on my laptop and had to uninstall the kb and then plug again the phone in to reinstall the correct usb driver.
If the bug is caused by windows, even if you don't know how it's possible, you should try to repair windows by refresh. It's a long shot, but i had a similar problem, i could not use PPPoE service because my friend unwillingly did something wrong on his laptop. I had to refresh windows to repair the network card driver and finally configure PPPoE service on his laptop.
So... refresh?
best regards, V