Hey all,
I know this is a common issue and it's all over XDA, but no one seems to have this issue with Mac, which eliminates the "try reinstalling the drivers" troubleshooting that many find solves the problem.
I never really plug in my Nexus to anything other than an outlet, because music is synced wirelessly and I never need it for sending files.
Lately she's been really slow, so I wanted to flash back to stock now that 4.2.2 is available for the toro natively. Lo and behold, the Android USB app for connecting the Nexus a la MTP couldn't connect, even after switching USB ports and unlocking the phone as you're supposed to do. But hey, I've had that issue with certain ROMs before.. Unfortunately, the issue carried into Fastboot, where the Macbook can't pick it up via the ./adb and ./fastboot devices command. After several reboots from the Macbook and GalNex, I STILL get the Fastboot Command Read Error (-2147483647).
I don't have another computer to try this on, but I can say I rooted my friend's GalNex just a couple of weeks ago, and I haven't updated SDK Manager (well I did just now to try to fix the issue) since, but it worked fine on his GalNex...
I just got the Nexus last October, so I guess shipping it off to Samsung is.. possible, but I'd rather use this as an excuse to get a GSIV. Anyway, can anyone offer any suggestions, maybe someone out there with a Mac had the same issue? It doesn't seem like the micro USB port would get outta whack so soon, I bought it new last October.
Thaaaaaaankkksss!
I have a Mac, sort of similar situation.. the cable that I have for it didn't really work with the computer at all..
Tried another cable, and it seemed to pick up the device in MTP if the cable was at a slight angle, which pointed to a bad port.
Anyway, I was restoring to stock 4.2.2 and it just wouldn't go past the file transfer.. sometimes it would stop on transferring system.img and sometimes on recovery.img; and sometimes not even get picked up on the fastboot mode at all.
Plugged into a PC, kept the USB at required angle throughout the process and it worked..
It's usually the USB cable that's the problem.. using an original Samsung cable now (not the one that came with it) and it works regardless of what position the cable is inserted in, which is very odd.
Also, my GNex always charges on USB mode.. even when plugged in to AC; so you might want to look for another USB cable
hope this helped
im having a problem connecting my pixel 2 xl to my desktop pc via usb c
here are some things
when i connect phone to usb-c port nothing happnes. no charging, no usb options notification
old phone, nexus 6p, uses same port and cable and works just fine
pixel 2 xl will connect to usb-c port on my laptop just fine
will connect to usb-a port with an a-c cable just fine
if i boot in to safe mode the desktop will recognize but it takes 5 minutes or so of being plugged in
windows 10 and usb drivers are up to date
any ideas??
thanks guys
First thing to try would be another cable and/or another USB-C port.
On the first Pixel XL, after Oreo came out, it very picky about these. It took me many tries of three cables and two USB-C ports until the images would flash properly. Two of the cables were straight from Google, and the third one was certified as a good cable. They all worked fine for everything on Nougat.
I realize that you're only trying to connect it but those are always the first things to try.
I did try other cables. Both work on my 6p that has Oreo. I only have one usb-c port on my desktop unless I buy an expansion card and I'd rather not. I did try my laptops usb-c port and that works
The default option when plugging phone into USB on a laptop or PC is charging. You can see this from notification area.
Select this and change it to File Transfer. Then you should be able to see it connected.
I'm not getting the USB options notification unfortunately
knock.back said:
I'm not getting the USB options notification unfortunately
Click to expand...
Click to collapse
Do you have USB debugging enabled?
If so, then when you first plug it into the PC, you should be prompted on the phone to allow the PC/Device to connect to your phone. Allow it always.
USB debugging is not turned on
knock.back said:
USB debugging is not turned on
Click to expand...
Click to collapse
Turn it on.
knock.back said:
USB debugging is not turned on
Click to expand...
Click to collapse
That is your issue, you need to turn on USB Debugging to enable communications between the Laptop/PC and Phone. Once enabled, and you connect them. Drop the notification window and select File Transfer.
Have you tried toggling PTP and MTP? That is how I got my Nexus 6P tp bre seen as storage (adb worked fine).
I didn't have this problem with my Pixel 2 XL using the same cable and port.
I don't know if this will have any effect but on the pc, plug to the usb ports on the back that are direct to the motherboard instead of usb headers on the top/front of pc.
I have this issue with a TomTom satnav and a Mio miview dash cam. Unless they are plugged in on back pc / with Windows 10 doesn't recognize
Sent from my XT1572 using Tapatalk
I have been having USB data transfer problems as well.
My Pixel 2 XL sometimes chokes on files when transferring from MacOS with Android File Transfer. I have tried different cables, different computer ports, different computers. I have tried USB debugging and Safe Mode. I have even tried factory reset. Sometimes it chokes on the same files, sometimes it is different files. Yet my Pixel XL handles those same files without any problem with the same cables and computers.
Data transfer stops completely. Sometimes a reboot of the phone is required. Sometimes a reboot of the phone and computer. And sometimes even a factory reset doesn't clear the problem -- it has unable to detect any other connected phone to transfer files during setup.
I was only able to bypass this file transfer problem by sending the files as a zip.
I have contacted Pixel 2 Support about this. They seem very puzzled. They said that I should be hearing back from an "upper level", but that was 5 days ago now.
knock.back said:
im having a problem connecting my pixel 2 xl to my desktop pc via usb c
here are some things
when i connect phone to usb-c port nothing happnes. no charging, no usb options notification
old phone, nexus 6p, uses same port and cable and works just fine
pixel 2 xl will connect to usb-c port on my laptop just fine
will connect to usb-a port with an a-c cable just fine
if i boot in to safe mode the desktop will recognize but it takes 5 minutes or so of being plugged in
windows 10 and usb drivers are up to date
any ideas??
thanks guys
Click to expand...
Click to collapse
Same here man, contacted google this morning and support said this was how it was with his brother's phone as well. Had no suggestions.
EDIT: This is with USB Debug on or off, no options to charge or select anything, takes about 5 minutes and then starts working as normal. Unfortunately, the fingerprint scanner stopped working as well. Getting a new one sent out, I'll follow up and let you know if it has the same behavior.
EDIT: 11/6/17 - Got new phone in. Fingerprint issue is resolved but the same USBC issue is not. Phone does charge from it when off.
I've got a very similar problem here with Pixel 2 XL manufacture date October 10th. After some extensive troubleshooting, I'm certain this is a hardware issue.
When connecting USB-C to USB-C with my laptop, the phone will start charging but will not register that it is connected to a computer unless USB debugging is enabled. Even then, with debugging enabled I will usually, but not always get the option to switch from charging mode to MTP/file transfer mode, but when I try to switch the phone will just disconnect and reconnect several times and revert back to charging mode. It has only every actually established a data transfer connection 3 times out of probably near 50 attempts over the past week.
I have tried two different type-C to type-C cables, doesn't make a difference.
I had the pixel 1, and had no issues at all with the same connection and with either cable, so I can safely rule out the cables or the laptop as the problem.
The issue was present with 8.0 firmware and is still present with 8.1 beta.
I did try booting into safe-mode, and the problem was still present.
I did a full factory reset, and the problem still persists.
This issue is specific for type-C to type-C, when I use a USB-C to USB-A cable, the phone will immediately recognize a data connection and allow me to switch from charging mode to MTP/File transfer mode, regardless of whether USB debugging is enabled or not. Though the phone does occasionally hiccup and disconnect/reconnect itself so it may take a second or third attempt at switching to MTP mode, but then it will establish a steady connection where I can access the phone's data.
I just got off the phone with google support, the rep mentioned he has heard of a few instances of a similar issue, and since I've already exhausted all possible troubleshooting they would have recommended, they are sending me a replacement.
I've been a loyal google customer since the Nexus 6P. It's a shame the LG's quality control was so shoddy with this product, now I have to wait and see if the replacement doesn't have the same issue or if it ends up having worse blue screen shift than the phone I am replacing.
At least I can say that google's customer support is on point, kudos to them for trying to make this right.
Alright well I may try this. IDK if it's worth an RMA tho, my a to c cable works fine, I just more or less can't charge off of it because it's too slow
knock.back said:
Alright well I may try this. IDK if it's worth an RMA tho, my a to c cable works fine, I just more or less can't charge off of it because it's too slow
Click to expand...
Click to collapse
Might not be worth RMA to you, but considering that it's a brand new $1,000 device (XL 128GB) I'd want to make sure I had one that doesn't that doesn't come with (more) problems out the gate... and since type C is the new standard, eventually replacing type A, and google is promising 3 years of updates, I'd like to ensure mine is future proofed as I intend to keep mine for a while.
I have the same issue and apparently so do lots of others. Did all the norm right off the bat, usb debugging on, tried every usb port, toggled PTP, MTP, etc. (currently left on MTP). An option pops up to choose either "transfer files" or "charging". It will never leave "charging" mode. The radio button will not select transfer files. Super annoying that a 1k phone has ridiculous hiccups for such basic hardware components.
Has anyone fixed this issue? I have the exact same one. My OG Pixel on Oreo worked fine on my motherboards USB c port. The Pixel 2 does not work at all. I can use any USB a port and it works... This is funky
Sent from my Pixel 2 using Tapatalk
stevemw said:
Have you tried toggling PTP and MTP? That is how I got my Nexus 6P tp bre seen as storage (adb worked fine).
I didn't have this problem with my Pixel 2 XL using the same cable and port.
Click to expand...
Click to collapse
I can get my comp to see my XL 2 but I can't get adb to work. Any ideas?
jerflash said:
Has anyone fixed this issue? I have the exact same one. My OG Pixel on Oreo worked fine on my motherboards USB c port. The Pixel 2 does not work at all. I can use any USB a port and it works... This is funky
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I haven't found any fix yet.
Stuck with the super slow A to C cable
I can't figure this out... I have an ASRock Motherboard Motherboards Z370 EXTREME4 motherboard with a USB-C output on it and using Win10. I've tried using the P2XL USB-C to USB-C cord to connect my phone to the computer to transfer files. I get nothing that shows up on the phone, yet everything is updated and working on the computer.
Any ideas?
Also as a side note, I have a dozen or so regular USB-C cords. Only 1 actually works just connecting it to a USB port on the computer. Some don't recognize anything, some will recognize the phone and let me transfer files only to have it drop the connection and reconnect to the phone. The 1 cord that actually does work, works as expected. Also this same issue happened on my old PC as well. Only 1 cord works with this phone and everything is updated. I've tried other computers with same issue.
I've also noticed I can only charge my phone with a couple of 120v USB outlets. Lots of them won't charge my phone, even though the phone says it's charging.....just never gains any charge.
I have a pretty similar issue with a C to C connection using my Razer Blade. I have this happen with the OEM cable and a couple of non-OEM C to C cable. I can't remember ever having an issue with my HTC 10 using a C to C, or when I use a USB A to C cable with this phone. While I'm not entirely convinced it's not my USB C port on my laptop, more evidence points to it being my Pixel rather than the port.
It's not the biggest issue for me because it's not a constant hindrance and I can usually get any transfer to finish.
Think I've been down this road... No fix. No idea what is happening or why.
The only option I have is to use my 1 cord to transfer. I usually am transferring several gigs at a time. I never had this issue with same cords for my original pixel XL.
What gets me is I even has issues using us chargers even. They say it's charging but never gain any charge.
Kind of thinking my phone has been defective
Wiped it yesterday and tried again with the OEM USB-C to USB-C cable, no luck even recognizing the phone, even to charge. I did however use a USB-A to USB-C 3.0 cable that didn't ever work originally and it copy 15gb of music without an issue.
I'll keep testing, as well as test it on the chargers that didn't work previously. I will also contact ASRock as I believe possibly my motherboard's port for the C-to-C not to work with the phone. It's not the worst thing not being able to use it, as I'm happy I can finally transfer files at 3.0 speeds now! SO MUCH quicker copying files back onto the phone than when I pulled them off!
Have had my A50 for a few weeks and enjoying it. Previous owner of a S4 (suicidal in early 2016), replaced by a wiry SSG S5 that started with android errors every few seconds under ANY situation, and now this A50. With OTG on my two earlier ssgs, OTG was very easy and quick. I could plug in OTG cable only and S4/S5 recognized the cable connection right off, then connect a keyboard, speakers, a usb stick, even at one time an external hard drive (really!). Now with this A50, initially it took me forever to get the OTG cable to be even recognized at all by the A50, BUT when I finally got OTG status, it's still a complicated process to just recognize whatever device you want to be connected with the A50!! If you want to transfer data, pictures, etc, it's another several steps to do that, NOT the very simple OTG using the S4 or S5 as source or destination. WHY did the OTG process get so difficult when it was so simple and worry-free previously? Thanks anyone for your input and/or experiences!
I have a USB OTG cable that I can use to connect USB devices like flash drives, keyboard etc. and that works fine, but for some reason my phone won't charge whilst the OTG cable is plugged in.
Am I missing some really obvious way of getting this to work? Is it software based? I'm rooted and running Lineage OS if that makes any difference. I've tried several different OTG cables, I've tried connecting to different power supplies, different USB cables, different outlets, I've tried going into developer debug settings - nothing seems to get it to charge and data at the same time.
I am also interested in the topic. Trying to run Octoprint for Android and charge at the same time. I bought an OTG Y cable and the problem is that the phone is either charging or communicating with the 3d printer. Never both at the same time. I've researched quite a bit on google and it turns out at least on some devices the required effect can be achieved but I haven't been able to find anything about huawei devices. It is most probably a software limitation.
The same problem but i have Samsung J5 2017, i have rooted device so there is option to modify system files
Gosh! Would love to get this working. Any news?