Hello everyone,
Since few days, I have a really enoying issue with my Pixel 2 XL.
Android Auto is not working anymore.
after differents diagnostic test, USB data is not working at all. I tried different USB cable, different Android Auto car and different Computer. I have only USB charge.. not data. Even if I enable USB debbug or if I try in safe mode
Does anyone have the same issue ?
What can I do ?
thank you for your help !
PS: https://productforums.google.com/forum/#!topic/nexus/PP_MDA4y0kU;context-place=forum/Nexus this issue looks like the same as me. but even if I enable or disable usb debbug. it doesn't work. and I am with 8.1 Oreo
MrMoi said:
Hello everyone, Since few days, I have a really enoying issue with my Pixel 2 XL. Android Auto is not working anymore. after differents diagnostic test, USB data is not working at all. I tried different USB cable, different Android Auto car and different Computer. I have only USB charge.. not data. Even if I enable USB debbug or if I try in safe mode Does anyone have the same issue ? What can I do ? thank you for your help ! PS: https://productforums.google.com/forum/#!topic/nexus/PP_MDA4y0kU;context-place=forum/Nexus this issue looks like the same as me. but even if I enable or disable usb debbug. it doesn't work. and I am with 8.1 Oreo
Click to expand...
Click to collapse
Have you tried revoking USB debugging authorizations and then re-enabling? It is the option just below the USB debugging toggle. Taking AA completely out of the equation, if after you have tried more than one USB-A to USB-C cables on more than one PC and cannot get MTP working you probably need to do a factory data reset. This will confirm whether you have a hardware issue or not. It is also the first step Google will require you to do prior to allowing an RMA.
Edit: You can also test if fastboot is working in bootloader mode, and if adb is working in recovery mode.
thank you for your help..
I've tried adb, fastboot and factory reset...:crying:
MrMoi said:
thank you for your help.. I've tried adb, fastboot and factory reset...:crying:
Click to expand...
Click to collapse
I'm not sure you understood... my suggestion was to test the phone in bootloader mode and send fastboot commands to it from your PC (eg. fastboot devices) -and- while in recovery mode (eg. adb devices). This is of course with adb debugging enabled. You also didn't answer my question about revoking adb in Developer Settings and then re-authorizing it? I still suspect you have a cable/pc driver issue.
Oups sorry my answer is not really clear.
Yes I revoke all ADB computer in developer setting . I try to boot in fastboot mode and recovery mode but ADB devices and fastboot device command doesn't work.
I can't see the device in my w10 computer in device manager
MrMoi said:
Oups sorry my answer is not really clear. Yes I revoke all ADB computer in developer setting . I try to boot in fastboot mode and recovery mode but ADB devices and fastboot device command doesn't work.I can't see the device in my w10 computer in device manager
Click to expand...
Click to collapse
Use THIS tool to view and remove any Google related USB drivers and try again. Don't worry about removing any drivers, they will re-install. Make sure you get them all out, REBOOT the PC and then plug your device back in. Are there any conflicts in your Device Manager in the USB section?
v12xke said:
Use THIS tool to view and remove any Google related USB drivers and try again. Don't worry about removing any drivers, they will re-install. Make sure you get them all out, REBOOT the PC and then plug your device back in. Are there any conflicts in your Device Manager in the USB section?
Click to expand...
Click to collapse
no conflicts in my device manager, nothing change after removing all my drivers
{
"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"
}
MrMoi said:
no conflicts in my device manager, nothing change after removing all my drivers
Click to expand...
Click to collapse
I had the same problem with my Nexus 5x (now dead) and recently pixel 2xl where there is no charging options or USB debugging mode in all different modes(recovery, fast boot) like yours.
What I did before it was installing Andromeda. Not sure if your case was the same.
Anyway, I fixed mine by going to safe mode. Plugging usbA to C, and connecting to mac. Tried changing usbc between the orientation while trying "adb devices" in the terminal on mac. After a while plugging in in each orientation. It came back to work. Not sure why..
Try it on your windows machine if it worked
wkJason said:
I had the same problem with my Nexus 5x (now dead) and recently pixel 2xl where there is no charging options or USB debugging mode in all different modes(recovery, fast boot) like yours.
What I did before it was installing Andromeda. Not sure if your case was the same.
Anyway, I fixed mine by going to safe mode. Plugging usbA to C, and connecting to mac. Tried changing usbc between the orientation while trying "adb devices" in the terminal on mac. After a while plugging in in each orientation. It came back to work. Not sure why..
Try it on your windows machine if it worked
Click to expand...
Click to collapse
thank you, but still not working
Did you ever get this problem resolved? I am having the same issue on my XL 2
I experience this problm as well but I just try different USB ports then it magically works. Quite annoying.
Boiler_81 said:
Did you ever get this problem resolved? I am having the same issue on my XL 2
Click to expand...
Click to collapse
Hello,
I had to send it back to the Google store. I never knew what the problem was.
Thank You
MrMoi said:
Hello,
I had to send it back to the Google store. I never knew what the problem was.
Click to expand...
Click to collapse
Related
Yesterday I plugged my phone with usb to the pc but it didn't recognize it, When I tried with another cable , One of the devices you connected was not recognized" this message popped, the phone was recognized day before yesterday and before that but suddenly it's unrecognized by the system. How do I fix this? I tried plugging my phone to my friend's pc but still it gives the same error,
Jexbox said:
Yesterday I plugged my phone with usb to the pc but it didn't recognize it, When I tried with another cable , One of the devices you connected was not recognized" this message popped, the phone was recognized day before yesterday and before that but suddenly it's unrecognized by the system. How do I fix this? I tried plugging my phone to my friend's pc but still it gives the same error,
Click to expand...
Click to collapse
Do you have HTC sync installed? Or have you ever had the right drivers installed on this PC? If so you can try go into device manager on windows, select the malfunction device and manually change its driver to the HTC drivers and see if that works
Sent from my HTC Desire S using Tapatalk
heavy_metal_man said:
Do you have HTC sync installed? Or have you ever had the right drivers installed on this PC? If so you can try go into device manager on windows, select the malfunction device and manually change its driver to the HTC drivers and see if that works
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Yea It used to detect my phone earlier but suddenly it has stopped, with the stock usb cable nothing gets detected, and when I try with others it pops the message that it is unrecognized.
Jexbox said:
Yea It used to detect my phone earlier but suddenly it has stopped, with the stock usb cable nothing gets detected, and when I try with others it pops the message that it is unrecognized.
Click to expand...
Click to collapse
Have you tried
Code:
adb devices
?
What does it say?
mcgi5sr2 said:
Have you tried
Code:
adb devices
?
What does it say?
Click to expand...
Click to collapse
It returns nothing
{
"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"
}
even tried to run fastboot in bootloader, It doesn't detect the phone which it used to detect previously, the phone is still in warranty but I can't give it because I can't even restore my stock backup as I won't be able to flash the stock kernel again is there any other way to return to stock?
Jexbox said:
It returns nothing
even tried to run fastboot in bootloader, It doesn't detect the phone which it used to detect previously, the phone is still in warranty but I can't give it because I can't even restore my stock backup as I won't be able to flash the stock kernel again is there any other way to return to stock?
Click to expand...
Click to collapse
OK panic not.
First see if you can test it on another computer. The HOV doesn't agree with USB3.0 so if you have any usb ports that aren't that, then try it there. Is the phone S-OFF? If so you could try and flash by putting the rom.zips on your sd-card then rebooting into recovery.
Also can you check adb with the other cables as well?
mcgi5sr2 said:
OK panic not.
First see if you can test it on another computer. The HOV doesn't agree with USB3.0 so if you have any usb ports that aren't that, then try it there. Is the phone S-OFF? If so you could try and flash by putting the rom.zips on your sd-card then rebooting into recovery.
Also can you check adb with the other cables as well?
Click to expand...
Click to collapse
I tested it on other 2 computers with 3 different cables, Adb doesn't detect my phone, The phone is S-ON, I tested it on all ports still no recognition, The phone charges through the USB but it is not recognized, I also looked at the HTC Dumlock method as I have TWRP installed, should I try that ?
Jexbox said:
I tested it on other 2 computers with 3 different cables, Adb doesn't detect my phone, The phone is S-ON, I tested it on all ports still no recognition, The phone charges through the USB but it is not recognized, I also looked at the HTC Dumlock method as I have TWRP installed, should I try that ?
Click to expand...
Click to collapse
That is very strange indeed, if it charges then it should be recognised by ADB. Are you sure your running adb from a folder it works from, are the drivers installed on the computers you tested it on?
I don't know anything about the Dumlock method so really can't advise
mcgi5sr2 said:
That is very strange indeed, if it charges then it should be recognised by ADB. Are you sure your running adb from a folder it works from, are the drivers installed on the computers you tested it on?
I don't know anything about the Dumlock method so really can't advise
Click to expand...
Click to collapse
Yea, it is strange, I was running adb for a long time on my pc and it was working and this thing has just started recently, I've read many similar posts with this strange problem but none of them give an solution to it.
Jexbox said:
Yea, it is strange, I was running adb for a long time on my pc and it was working and this thing has just started recently, I've read many similar posts with this strange problem but none of them give an solution to it.
Click to expand...
Click to collapse
Could you try it without your SD card in?
mcgi5sr2 said:
Could you try it without your SD card in?
Click to expand...
Click to collapse
Tried. still not working
Jexbox said:
Tried. still not working
Click to expand...
Click to collapse
It might be worth trying with different usb cables. If this wont help the hOV micro usb socket could be physically broken. :\
kvestas said:
It might be worth trying with different usb cables. If this wont help the hOV micro usb socket could be physically broken. :\
Click to expand...
Click to collapse
Can't tell cause the phone gets charged but it's not detected, tried at least 5-6 wires on different computers still the same
Ok another idea you could try is flashing a different rom. I am plucking at straws here though, as all our 4.2.2 roms are currently based on 1ceb0xs one anyway. Have you tried re-installing the rom from recovery?
mcgi5sr2 said:
Ok another idea you could try is flashing a different rom. I am plucking at straws here though, as all our 4.2.2 roms are currently based on 1ceb0xs one anyway. Have you tried re-installing the rom from recovery?
Click to expand...
Click to collapse
Will give it a try and report back.
Accidental full wipe of my Nexus 7 has left me with a no OS paper weight.
Fastboot indicates it's locked but I can boot into TWRP, but can't get it to be recognized by any PC and it won't recognize my OTG-USB (which has been recognized by others).
Any ideas as to how to get her up and running would be greatly appreciated.
{
"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"
}
Did you mount the OTG usb in TWRP or just looked for it to auto detect?
Btw, this belongs in the Q & A section, so ask a mod to move it
I am unable to select/check mount the OTG while in TWRP. The OTG is formatted correctly as the OTG is readable on other devices, but it seems like it just isn't being found by the N7. I'm baffled.
Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562
Tried it on a full battery, still no luck.
tried to get it to work, any suggestions fellow XDAers? I'm in a real jam here
Check this thread: http://forum.xda-developers.com/show....php?t=3064562
Click to expand...
Click to collapse
Thanks, but I can't get the tablet to be recognized. I've tried it in multiple windows computers with both USB 2 and 3.
Have you tried adb/fastboot?
Have you tried adb/fastboot?
Click to expand...
Click to collapse
I am able to fastboot, but still can't get the pc to recognize that it's connected. The tablet takes a charge, but the pc never acknowledges that a device is connected, device manager never indicates a device is connected.
-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.
CrazyJ36 said:
-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.
Click to expand...
Click to collapse
Thanks. Everything hinges on the PC being able to recognize that I'm attempting to connect the tablet (or for the tablet to recognize that I've attached the OTG).
I have tried multiple USB cables and ensured that the drivers are installed on the multiple PCs I've attached to.
I have tried to ADB sideload in TWRP, but since none of the PCs recognize that the tablet is connected to the PC, ADB won't work.
Again, it's not that the drivers are not installed, but rather the PC not recognizing that I have attached a device through the USB (no sound, no pop-up, nothing in the device manager). It is extremely frustrating, especially since the device charges via the USB from the PC.
DorianX said:
Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562
Click to expand...
Click to collapse
CrazyJ36 said:
Have you tried adb/fastboot?
Click to expand...
Click to collapse
Still no luck, any other recommendations?
Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.
I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1
CrazyJ36 said:
Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.
Click to expand...
Click to collapse
Nothing shows in the device manager. I was using KitKat on the tablet.
Turns on without an issue, opens TWRP with no issue.
when connected to the PC nothing occurs, not when it's on the Google screen, not when it's in TWRP, not in Fastboot, not when it's restarting. Nothing.
if it was the driver being missing, I'd at least see the device attached, just not communicating properly
sorry to hear about your GS4
The Apostle said:
I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
if you truly had the same exact problem, how were you able to use ADB if your device wasn't recognized on a PC or OTG?
Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1
The Apostle said:
Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
it's alright, thanks for the thought.
I'm just hoping since I can get into TWRP someone has an idea of how I can get it to recognize the OTG or the PC to see it and I can get into ADB.
Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.
zandgreen said:
Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.
Click to expand...
Click to collapse
the port looks perfectly fine, I was thinking the same thing, but there doesn't seem to be any damage. I almost wish it was damaged so I could at least assume that's the problem and just trash the thing.
I am unable to get Windows to mount my Pixel XL in MTP mode. I have the Pixel's screen turned on and unlocked, and the connection option on the phone's pull down menu is set to transfer files. Windows is able to mount the phone when it is in picture transfer mode, but not in MTP mode.. When I look in Window's device manager I can see that the MTP device is connected but I'm getting a yellow triangle exclamation, as in the driver is no good. I uninstalled the driver and tried letting Windows reinstall to no avail. I have searched the web for MTP drivers for Windows, but I can't really find anything. The specific version of Windows that I am using is Windows 10 Education 64.
The main reason for my concern is that I am about to attempt to apply the new root method that is available, and I wasn't sure if I needed to be connected successfully via MTP before I get the ball rolling with ADB. I do have the ADB drivers installed, along with ADB and fastboot and that seems to be working fine. When I run the command 'adb devices' the console shows that my Pixel XL is connected. I am assuming that I should be good to go on that front, but I still want to know why MTP is not working on Windows, and how I can fix it. Any suggestions would be greatly appreciated.
Here's a screen shot of what Window's device manager is showing me.
{
"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"
}
norcal61 said:
I am unable to get Windows to mount my Pixel XL in MTP mode.
Click to expand...
Click to collapse
Maybe this will help: http://www.technobuzz.net/download-google-pixel-xl-usb-drivers-adb-fastboot/
Personally I installed the latest SDK which comes with the latest drivers.
Scott said:
Maybe this will help: http://www.technobuzz.net/download-google-pixel-xl-usb-drivers-adb-fastboot/
Personally I installed the latest SDK which comes with the latest drivers.
Click to expand...
Click to collapse
I tried that already. I stumbled across it while searching for a solution. The adb and fastboot parts worked well but not the regular mtp drivers. I think maybe the problem has to do with Windows itself.
I had a similar issue with my Pixel C tablet. I don't remember which driver that I had to use but I eventually got it to work. I believe that I ended up needing PDANet to resolve. I am using the same computer for my Google Pixel phone. I have successfully been able to use MTP on my Google Pixel phone and have access to all the files via file explorer.
I noticed the same thing. When I first attached my phone to the laptop I could see the phone in device manager. Couldn't get into internal storage. Changed the phone from mtp to picture mode then back to mtp and was able to get in. I have to use this method whenever I attach my phone to the laptop using Windows 10. I didn't get any yellow exclamation signs at any time.
plug your phone to your computer then check the notifications,tap on the USB charging this device for other options...just tick the usb to transfer files ....
Check out this Youtube video, fixed it for me.
https://www.youtube.com/watch?v=fUHQzqxxsZI
defens23 said:
I noticed the same thing. When I first attached my phone to the laptop I could see the phone in device manager. Couldn't get into internal storage. Changed the phone from mtp to picture mode then back to mtp and was able to get in. I have to use this method whenever I attach my phone to the laptop using Windows 10. I didn't get any yellow exclamation signs at any time.
Click to expand...
Click to collapse
Believe it or not have seen / owned many devices that exhibited this behavior.
Switching back and forth always fixed.
awesome thanks for that video!!
peejayw said:
Check out this Youtube video, fixed it for me.
https://www.youtube.com/watch?v=fUHQzqxxsZI
Click to expand...
Click to collapse
This was from Microsoft's site, is a little quicker. It would be nice if this got fixed.
(1) Go to C:\Windows\INF
(2) Type "wpdmtp.inf" in search bar provided to the right of the address bar in Windows 10.
(3) Once you found it, just right click on it and select install. It will take a very few seconds.
(4) Connect your device to the pc.
I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?
triumvirant said:
I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?
Click to expand...
Click to collapse
Nope. Coincidence.
Sent from my Pixel using XDA-Developers Legacy app
triumvirant said:
I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?
Click to expand...
Click to collapse
bobby janow said:
Nope. Coincidence.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I don't know if it's a coincidence because USB 3.0 is still not fully supported or functional on all new motherboards. Even the brands that claim to and brag about having it still have a half ace implementation of it. I'm looking at you Asus and Gigabyte!!! :crying: I have had to stop using their boards because I've gotten too many complaints from customers.
I can never get any 3.0 device to run off my 3.0 ports, wtf?! I can get flash drives to work all day for sure though!!!:silly:
i'm running an ASUS MB too...perhaps there are more variables to this equation than we want to believe.
Jammol said:
I don't know if it's a coincidence because USB 3.0 is still not fully supported or functional on all new motherboards. Even the brands that claim to and brag about having it still have a half ace implementation of it. I'm looking at you Asus and Gigabyte!!! :crying: I have had to stop using their boards because I've gotten too many complaints from customers.
I can never get any 3.0 device to run off my 3.0 ports, wtf?! I can get flash drives to work all day for sure though!!!:silly:
Click to expand...
Click to collapse
I'll grant you that, some of those things happen to me too. But as for a driver not recognizing the device this thread fixes that. That doesn't have anything to do (afaik) with USB 3.0. This was just a silly driver that lost its way. As soon as I tried the method here everything was back to normal.
bobby janow said:
I'll grant you that, some of those things happen to me too. But as for a driver not recognizing the device this thread fixes that. That doesn't have anything to do (afaik) with USB 3.0. This was just a silly driver that lost its way. As soon as I tried the method here everything was back to normal.
Click to expand...
Click to collapse
Windows! Lol.
Hi all,
I have a Oneplus 3 with the last update (OxygenOS 5.0.4) and I can't access to my files with an USB cable.
I try on 3 computers with differents cables, and the OTG parameter on ON but nothing works.
Drivers are normally ok.
Do you have a solution?
Best regards,
Jckbrtn
jckbrtn said:
Do you have a solution?
Click to expand...
Click to collapse
Try to turn on usb debugging in developer options
mar.ur said:
Try to turn on usb debugging in developer options
Click to expand...
Click to collapse
Hi,
Thanks but it doesn't work and I never need to do that before.
I don't understand why it doesn't work anymore.
I hadn't try nothing new on my phone.
I think I will try to reset it...
Best regards,
Jckbrtn
@jckbrtn is there connecting with pc in recovery mode ? I mean adb commands
mar.ur said:
@jckbrtn is there connecting with pc in recovery mode ? I mean adb commands
Click to expand...
Click to collapse
I just try to connect my Oneplus with USB cable like I always use to do.
ADB drivers are installed on my PC and I only have the original recovery.
I never try to root this smartphone.
With a OneplusX on LineageOS, no problem. See screenshot:
{
"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"
}
Looking at your photo, have your tried to tap the second option...?
150208 said:
Looking at your photo, have your tried to tap the second option...?
Click to expand...
Click to collapse
Picture is for my OneplusX. It works for the OneplusX on the same computer but not for the Oneplus 3.
I don't have this menu in notification.
jckbrtn said:
Picture is for my OneplusX. It works for the OneplusX on the same computer but not for the Oneplus 3.
I don't have this menu in notification.
Click to expand...
Click to collapse
Oh i see
Try developer options, if i remember it right, i believe there is a setting about USB access in OOS.
Other than that i don't know except factory reset, re-install the PC, or bad usb port (in either of phone/pc).
I have this issue once, but it because my bad usb port on my PC motherboard.
jckbrtn said:
Picture is for my OneplusX. It works for the OneplusX on the same computer but not for the Oneplus 3.
I don't have this menu in notification.
Click to expand...
Click to collapse
Go through and remove the drivers for all the one plus device then connect the 3. The drivers for the two are corrupting each other. It is a known issue with the drivers for this device. I have to reinstall the drivers on every connect and disconnect from USB.
zelendel said:
Go through and remove the drivers for all the one plus device then connect the 3. The drivers for the two are corrupting each other. It is a known issue with the drivers for this device. I have to reinstall the drivers on every connect and disconnect from USB.
Click to expand...
Click to collapse
I only have drivers for the 3. For th OneplusX with the usb, no problem.
Drivers removed but it doesn't works. I think I'll try a reset of my device in a few days to see...
I try on 3 windows computers with differents cables (also the Oneplus one), drivers, no drivers... don't know....
jckbrtn said:
I only have drivers for the 3. For th OneplusX with the usb, no problem.
Drivers removed but it doesn't works. I think I'll try a reset of my device in a few days to see...
I try on 3 windows computers with differents cables (also the Oneplus one), drivers, no drivers... don't know....
Click to expand...
Click to collapse
With the one plus devices you can never tell. It could be anything from software to hardware. Next time you connect pull a log cat this might help.
So I try a factory reset: don't work
I downgrade to oxygen 5.0.3 and 5.0.1: don't work
I try on an other laptop where I never plug my oneplus or install drivers/adb: don't work
I also try with different cables (original from oneplus include): don' work
With otg option on, usb debugging on, ... or without, don't work!
And best is I can't install LineageOS as I have no access on my PC
zelendel said:
With the one plus devices you can never tell. It could be anything from software to hardware. Next time you connect pull a log cat this might help.
Click to expand...
Click to collapse
Yes, I think it's hardware. USB-C don't work with OTG adapter (USB-C to USB and USB key).
Log cat? How to?
I just bought an used 3T and have the same problem. I have tried every possible software solution I guess I have to try to replace USB port but if it doesn't help I don't know what I'll do...
I had the same issue but a fix I found to work was when my Oneplus 3 was plugged into my computer, the dropdown notification that says "Android System" - USB charging this device can be changed to transfer files and after that option is picked, my phone is detected by my computer. Maybe this will help some of you
stingerbs said:
I had the same issue but a fix I found to work was when my Oneplus 3 was plugged into my computer, the dropdown notification that says "Android System" - USB charging this device can be changed to transfer files and after that option is picked, my phone is detected by my computer. Maybe this will help some of you
Click to expand...
Click to collapse
Problem is I don't have this menu anymore since my usbc port is not working
stingerbs said:
I had the same issue but a fix I found to work was when my Oneplus 3 was plugged into my computer, the dropdown notification that says "Android System" - USB charging this device can be changed to transfer files and after that option is picked, my phone is detected by my computer. Maybe this will help some of you
Click to expand...
Click to collapse
I'm waiting for a response of the oneplus support. My smartphone is still under warranty so I asked for a RMA.
I had to make a video of me connecting the phone to my computer to show the issue.
I also made a video with an other usbc smartphone to show that all is working.
jckbrtn said:
I'm waiting for a response of the oneplus support. My smartphone is still under warranty so I asked for a RMA.
I had to make a video of me connecting the phone to my computer to show the issue.
I also made a video with an other usbc smartphone to show that all is working.
Click to expand...
Click to collapse
So after 2 weeks of mail contact, my smartphone was sent from Belgium to Poland monday.
I received my repaired smartphone on wednesday.
Technical support very good! Mail support very complicated...
So, after upgrading to Android 8.1 OPP28-85-13 . somehow I could not upgrade to version OPP28-85-16 (OFFICIAL VERSION) and so I tried to update the computer, but the same did not recognizes the cell phone.
I already installed the drivers of the motorola 5x, I changed PC, cable, I activated USB debugging, I already changed that MTP option and nothing! The cell phone does not live on the PC, the only thing that happens is that it carries, nothing else! Does anyone have a solution to this? I'm stuck in a version that still has bugs and I can not update anymore ... I've tried everything!
Excuse my English, I'm from Brazil and I can not find anyone here to solve this.
Assuming you did find the correct OTA to go from OPP28-85-13 to OPP28-85-16, you'd have to go to fastboot, and I doubt those options matter then. Also if you didn't sign up for soak test you wouldn't be able to go from a soak to official version through OTA. Check if your PC recognizes your phone in fastboot.
Hyoretsu said:
Assuming you did find the correct OTA to go from OPP28-85-13 to OPP28-85-16, you'd have to go to fastboot, and I doubt those options matter then. Also if you didn't sign up for soak test you wouldn't be able to go from a soak to official version through OTA. Check if your PC recognizes your phone in fastboot.
Click to expand...
Click to collapse
it does not work in fastboot mode, in fact it is as if the cell phone was dead, it stopped working on the computer, it only loads, I already installed drivers, everything ... but no use, I already tried to use rsd lite but it does not recognize!
Kinda dumb but you're using fastboot command right? Last time that happened to me I was using adb devices and it never showed up
Hyoretsu said:
Kinda dumb but you're using fastboot command right? Last time that happened to me I was using adb devices and it never showed up
Click to expand...
Click to collapse
to recognize in fastboot mode, the cell phone does not need to be recognized on the pc first? I connect the USB cable and it's the same as nothing, besides that, debugging usb also does not work to proceed in fastboot
Nope. If it's in fastboot, it won't get recognized as an actual device, you'll just hear the plugging sound and be able to interact with it via commands
Hyoretsu said:
Nope. If it's in fastboot, it won't get recognized as an actual device, you'll just hear the plugging sound and be able to interact with it via commands
Click to expand...
Click to collapse
{
"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"
}
Does not recognize, neither in fastboot nor in normal mode
@kolple
Hey I know you said you installed drivers and all.. But maybe you should uninstall them and try again. This really sounds like a driver problem honestly.
You could try looking up for UsbDeview on google. It's a pc app which lets you see installed devices.. You could uninstall everything related to your Moto g5.. Then reinstall official Motorola drivers.
Chekm8Qc said:
@kolple
Hey I know you said you installed drivers and all.. But maybe you should uninstall them and try again. This really sounds like a driver problem honestly.
You could try looking up for UsbDeview on google. It's a pc app which lets you see installed devices.. You could uninstall everything related to your Moto g5.. Then reinstall official Motorola drivers.
Click to expand...
Click to collapse
I already tested it on other computers, and the same thing happens, does not install anything, nor does the device manager appear. It is as if the cell phone was no longer receiving data through the cable ... I do not know, it could be an android bug or the faulty usb port, some solution to that?
kolple said:
I already tested it on other computers, and the same thing happens, does not install anything, nor does the device manager appear. It is as if the cell phone was no longer receiving data through the cable ... I do not know, it could be an android bug or the faulty usb port, some solution to that?
Click to expand...
Click to collapse
This is odd for sure. I wish I could help more honestly. Trying USB 2.0 or 3.0 ports doesn't change anything right? Probably not.
kolple said:
Does not recognize, neither in fastboot nor in normal mode
Click to expand...
Click to collapse
I would say update your adb/fastboot
I never use minimal adb/fastboot but always the package that comes with the full android sdk
Also try a different USB cable
And you can try cmd as admin instead of the windows power shell not that it should make a difference
kolple said:
So, after upgrading to Android 8.1 OPP28-85-13 . somehow I could not upgrade to version OPP28-85-16 (OFFICIAL VERSION) and so I tried to update the computer, but the same did not recognizes the cell phone.
I already installed the drivers of the motorola 5x, I changed PC, cable, I activated USB debugging, I already changed that MTP option and nothing! The cell phone does not live on the PC, the only thing that happens is that it carries, nothing else! Does anyone have a solution to this? I'm stuck in a version that still has bugs and I can not update anymore ... I've tried everything!
Excuse my English, I'm from Brazil and I can not find anyone here to solve this.
Click to expand...
Click to collapse
Try using Moto lenovo smart assistant it will flash the latest firmware.
riyan65 said:
Try using Moto lenovo smart assistant it will flash the latest firmware.
Click to expand...
Click to collapse
Really? I didn't even know that.
riyan65 said:
Try using Moto lenovo smart assistant it will flash the latest firmware.
Click to expand...
Click to collapse
No application that will connect USB will not work, nor with debugging, no use! My salvation would be if there was an application that does these methods over wifi.
kolple said:
No application that will connect USB will not work, nor with debugging, no use! My salvation would be if there was an application that does these methods over wifi.
Click to expand...
Click to collapse
Man this is so weird.. In your screenshot the bootloader screen actually detects the phone being connected to usb.
Chekm8Qc said:
Man this is so weird.. In your screenshot the bootloader screen actually detects the phone being connected to usb.
Click to expand...
Click to collapse
Exactly! But it does not recognize on the system, on any computer. In fastboot it appears that it recognized, but without signal ... With the cellphone turned on normal, also nothing appears in the computer, even with usb debugging
kolple said:
Exactly! But it does not recognize on the system, on any computer. In fastboot it appears that it recognized, but without signal ... With the cellphone turned on normal, also nothing appears in the computer, even with usb debugging
Click to expand...
Click to collapse
Have you tried in device manager to scan for hardware changes when the phone is connected? And of course you selected mtp right? Have you selected mtp in developer options? You should try to revoke USB debugging authorizations ( right under USB debugging) this will reset the adb permission you first allowed. You should get prompt for permission again when you type adb devices under cmd ( if phone is seen by pc)
When you check your installed programs on pc do you have other USB drivers installed at the same time as the Motorola ones? If so that might cause some issues.
Chekm8Qc said:
Have you tried in device manager to scan for hardware changes when the phone is connected? And of course you selected mtp right? Have you selected mtp in developer options? You should try to revoke USB debugging authorizations ( right under USB debugging) this will reset the adb permission you first allowed. You should get prompt for permission again when you type adb devices under cmd ( if phone is seen by pc)
When you check your installed programs on pc do you have other USB drivers installed at the same time as the Motorola ones? If so that might cause some issues.
Click to expand...
Click to collapse
I've already changed all these options, I already installed and reinstalled the motorola drivers and nothing works for me
kolple said:
I've already changed all these options, I already installed and reinstalled the motorola drivers and nothing works for me
Click to expand...
Click to collapse
There seems to be quite a few cases like yours if you Google the problem.
Mind looking at this to start with?
https://www.google.ca/amp/s/forum.x...p-problems-8-1-official-windows-t3715171/amp/
Chekm8Qc said:
There seems to be quite a few cases like yours if you Google the problem.
Mind looking at this to start with?
https://www.google.ca/amp/s/forum.x...p-problems-8-1-official-windows-t3715171/amp/
Click to expand...
Click to collapse
did not work, even changing the options MPT, PTP, loading, the device manager did not appear anything either!
@edit
USB HOST DIAGNOSTIC