I just bought a used Pixel 2 XL and it has the file transfer/ADB/fastboot over USB problem. I've been through every solution here and on Google Pixel support with no luck (see below).
The phone connects via USB for a second and brings up ADB debugging auth, then disconnects. Every other thing I plug into the phone works fine (thumb drive, OTG camera, charger). Wireless ADB works fine, but I can't unlock the bootloader this way (that I know of). I can't get ADB or Fastboot access in bootloader or recovery mode.
I'm guessing software/kernel problem on the phone since everything else works with the USB port. I'm currently running build RP1A.201005.004.
On the factory image page, there's a new image, RP1A.201005.004.A1, Dec 2020, that I hope is a fix, but I've got no way to install it except if I get it OTA.
If anyone has any ideas on other things to try, please LMK! Thanks!
Solutions I've tried:
Cleaned port, dozens of cables, USB 1, 2, & 3 ports on four different machines and three different OS that work with ADB on other phones, every phone ADB/USB setting on/off in all combinations, cleared data for external storage, can't clear data for media storage because it's now grayed out in this build.
I've also tried the old tricks to try and get the OTA sent, but I'm guessing those tricks don't work with Android 11.
I may try replacing the internal USB port and cable since it's only $7, but I don't think it's the problem from what I've read in other posts here.
phineous said:
I just bought a used Pixel 2 XL and it has the file transfer/ADB/fastboot over USB problem. I've been through every solution here and on Google Pixel support with no luck (see below).
The phone connects via USB for a second and brings up ADB debugging auth, then disconnects. Every other thing I plug into the phone works fine (thumb drive, OTG camera, charger). Wireless ADB works fine, but I can't unlock the bootloader this way (that I know of). I can't get ADB or Fastboot access in bootloader or recovery mode.
I'm guessing software/kernel problem on the phone since everything else works with the USB port. I'm currently running build RP1A.201005.004.
On the factory image page, there's a new image, RP1A.201005.004.A1, Dec 2020, that I hope is a fix, but I've got no way to install it except if I get it OTA.
If anyone has any ideas on other things to try, please LMK! Thanks!
Solutions I've tried:
Cleaned port, dozens of cables, USB 1, 2, & 3 ports on four different machines and three different OS that work with ADB on other phones, every phone ADB/USB setting on/off in all combinations, cleared data for external storage, can't clear data for media storage because it's now grayed out in this build.
I've also tried the old tricks to try and get the OTA sent, but I'm guessing those tricks don't work with Android 11.
I may try replacing the internal USB port and cable since it's only $7, but I don't think it's the problem from what I've read in other posts here.
Click to expand...
Click to collapse
I just installed the update using ADB from my Chromebook via Crostini Linux. I had an issue at first due to the USB cable I was using. Switched to a USB 3 cable and it worked flawlessly. Kinda weird that after the update it still says October 2020. Looks like the .A1 on the end of the build is the only difference, other than whatever security updates they pushed.
robn30 said:
I just installed the update using ADB from my Chromebook via Crostini Linux. I had an issue at first due to the USB cable I was using. Switched to a USB 3 cable and it worked flawlessly. Kinda weird that after the update it still says October 2020. Looks like the .A1 on the end of the build is the only difference, other than whatever security updates they pushed.
Click to expand...
Click to collapse
I just got the update OTA today. I still can't get a USB connection to work for longer than a second or two. I've tried dozens of cables and several computers. I'm going a little crazy here.
phineous said:
I just got the update OTA today. I still can't get a USB connection to work for longer than a second or two. I've tried dozens of cables and several computers. I'm going a little crazy here.
Click to expand...
Click to collapse
I have noticed mine is a little finicky with ADB, especially when connected via USB 3.0. Connecting with USB 2.0 with a good cable seems to always be reliable and never disconnect. Also if you haven't tried using the stock cable that came with the Pixel, I would try that for sure.
I just replaced the internal USB assembly and nothing has changed. The old connector was definitely worn though.
I'll go back to trying more cables and ports. I ordered a cable that another poster claimed worked for them, but I had no luck with it.
For anyone wanting to replace their USB ass'y, here's what I learned from doing it. The service manual on ifixit is a good guide but leaves out a couple of important steps.
Heat is your friend. I used a clothes iron adjusted to 160F. The phone dissipates heat quickly so you may need to heat it several times. Place a towel over the screen and set the iron on it. I used guitar picks to pry up the screen and keep it separated while I heated the other sides.
The screen cable connection covers are hard to remove and you'll probably need a to use a metal spudger.
Heat the back of the phone to help remove the loudspeaker ass'y without damaging it, and again to remove the old cable ass'y.
The replacement ass'y I got had adhesive applied for the center of the cable, but not the adhesive foam pad under the antenna connector, so heat and scrape between the pad and phone body to remove it intact for reuse.
My old antenna connector partially came off in the white antenna connector and it was very hard to see what was wrong even under strong magnification.
You'll need a new screen adhesive sheet to reattach the screen securely.
Both parts came from a seller on ebay. Dougsgadgets was the only one that had both parts in stock. I think I paid $11 and they shipped quickly.
Good luck!
Related
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
I'm not able to get to the bootloader screen because the front usb port is not functioning on my unit. Has anyone been able to use one of the USB ports on the back to get to ADB and/or get to the bootloader? Is this a known issue with a workaround? I've done quite a bit of searching and have not turned up any solutions. Considering what is involved in shipping this back, I'd much rather figure something out. Thanks in advance for any help!
Edit: I should mention that I have used the adbon password and it does acknowledge that adb has been enabled. Just nothing seems to work on the front port. When I connect my Linux machine and run lsusb nothing shows for the unit. I have considered buying or making a USB-A to USB-A cable to connect my computer to one of the back USB ports, but I'm concerned about how these back USB ports are designed. Is it as simple as a built-in OTG cable? If so I'm probably fine. If it is more like a computer's USB port I could damage my laptop, my headunit, or both. I'd really like to hear if anyone else has had to deal with this. Unfortunately I haven't verified if the front USB will charge a phone. This is my next step.
dutchhome said:
I'm not able to get to the bootloader screen because the front usb port is not functioning on my unit. Has anyone been able to use one of the USB ports on the back to get to ADB and/or get to the bootloader? Is this a known issue with a workaround? I've done quite a bit of searching and have not turned up any solutions. Considering what is involved in shipping this back, I'd much rather figure something out. Thanks in advance for any help!
Edit: I should mention that I have used the adbon password and it does acknowledge that adb has been enabled. Just nothing seems to work on the front port. When I connect my Linux machine and run lsusb nothing shows for the unit. I have considered buying or making a USB-A to USB-A cable to connect my computer to one of the back USB ports, but I'm concerned about how these back USB ports are designed. Is it as simple as a built-in OTG cable? If so I'm probably fine. If it is more like a computer's USB port I could damage my laptop, my headunit, or both. I'd really like to hear if anyone else has had to deal with this. Unfortunately I haven't verified if the front USB will charge a phone. This is my next step.
Click to expand...
Click to collapse
My front USB also doesn't work. I even got mini to standard USB cable with unit, but plugging flash drive into it doesn't produce any reslt.
I also plugged extension cable to one of back USB ports and tried it (plugibg same USB flash) but it doesn't work either.
So I'm also confused.
Does that mean you are still running the stock ROM? I have been hesitant to install the custom ROM because they say you must be able to get into the bootloader even though I couldn't find a step in the process that required it.
Regarding the USB ports not working at all, you may find that you need to use a powered USB hub. I've seen reports of USB devices acting up due to the low power. This is one of the reasons I thought it might be safe to use the rear ports with my computer. (My first real test is going to be mangling a male-to-male USB cable so only the data lines are connected to see if I can get those rear USB ports to talk to the computer. I figure that way there is no chance of frying any circuits.. Each side already has its own power and I don't believe any signaling is sent via the power pins.)
On my unit (MTCB-KGL-V2.80), I have used a T-Mobile USB broadband modem successfully on the rear port, so I know rear ports are live. I did take it apart to see if something was obviously wrong with the front port, but nothing jumped out at me.
So I have a bit more information on my headunit. BTW, I have the BMW E46 model with MCU MTCB-KGL-V2.80.
On my system, both the front USB port and the rear 3G USB port are wired as device ports connected to an AU6258 USB controller (http://www.sunnyqi.com/upLoad/product/month_1403/201403162331285643.pdf). I don't remember exactly which USB ports they are connected to, but I believe the 3G port is connected to port 2 (pins 6 & 7) and the front USB port is connected to either ports 3 or 4 (pins 9 & 10 or 11 & 12 respectively). Nothing is connected to port 1 or to the upstream port. The other rear USB port is wired directly to the MTC_RK3188 board.
All three ports are wired with only four pins, so I'm concerned that none of them could work with the computer. The USB controller doesn't have USB ID pins, so does that mean that the 4 downstream ports are OTG and the upstream port is for a computer? Unfortunately I don't know the hardware side.
dutchhome said:
Does that mean you are still running the stock ROM? I have been hesitant to install the custom ROM because they say you must be able to get into the bootloader even though I couldn't find a step in the process that required it.
Regarding the USB ports not working at all, you may find that you need to use a powered USB hub. I've seen reports of USB devices acting up due to the low power. This is one of the reasons I thought it might be safe to use the rear ports with my computer. (My first real test is going to be mangling a male-to-male USB cable so only the data lines are connected to see if I can get those rear USB ports to talk to the computer. I figure that way there is no chance of frying any circuits.. Each side already has its own power and I don't believe any signaling is sent via the power pins.)
On my unit (MTCB-KGL-V2.80), I have used a T-Mobile USB broadband modem successfully on the rear port, so I know rear ports are live. I did take it apart to see if something was obviously wrong with the front port, but nothing jumped out at me.
Click to expand...
Click to collapse
No I flashed Malaysk ROM from GPS SD card. No problems. Just follow instruction. I had luck that I didn't need to recover from USB.
Did you tried with USB powered hub? I don't have one to try it myself.
RK3188 1024x600 front USB not working confirmed
pa.ko said:
My front USB also doesn't work. I even got mini to standard USB cable with unit, but plugging flash drive into it doesn't produce any reslt.
I also plugged extension cable to one of back USB ports and tried it (plugibg same USB flash) but it doesn't work either.
So I'm also confused.
Click to expand...
Click to collapse
I checked on my Linux workstation with
Code:
lsusb |wc -l
plugging and unplugging all three USB cables and the number did not change. BTW where did you use the "adbon" command? The only place that I could even try was at Settings > Factory Settings. Regards Flint
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
due to my own stupidity, i had unlocked and installed twrp with a lot of effort, as the usb is decidedly iffy
i managed to use a file manager to import the requisite lineage rom and gapps, and then in my infinite wisdom stored them somewhere volatile - one mistake i won't make again
and so when i cleaned the device prior to a "new" install, i inadvertently lost the zip files, and now the computer refuses to recognise the device
no amount of forcing the right usb driver onit works, because i presume the computer does not know it's a flo
so, is there any way i can get it connected and push the roms to storage ?
my skills at the command line are limited, but i can follow scripts
this is sad, as i was soooooooo close to completing the install, after which the usb would have become redundant (i have a wireless charger and can wifi file across with a working system)
is this thus my very first brick ?
or can i trick the usb connection into working with the computer, or somehow wirelessly transfer to such a basic installation, or rig an otg connection (i have no cables that would seem to join micro-usb to any female plug to use a memory stick or sd card in adaptor)
thanks for any suggestions :fingers-crossed:
Get an image file from Google https://developers.google.com/android/images
Try going into TWRP and go into sideloading (can't remember exact menu - only used it once to get out of a similar problem), then try to connect USB lead to PC.
Run flash-all.bat on PC and that should at least get a system on the device.
Maybe...
thanks for the suggestion, but the sideload could place the lineage.zip instead if the computer would accept a usb connection - that's the problem: sideload can't work because the usb device is not recognised
my best bet would appear to be load the zip via otg - the twrp interface appears to allow that
i'll report back here if that works (once i procure a usb otg connector)
I was in a similar position once and couldn't get a normal USB ADB connection with PC until I tried TWRP sideloading which kicked in the PC connection.
Did you try it?
OTG was the next thing I was going to suggest
scruffy1 said:
the usb is decidedly iffy
no amount of forcing the right usb driver onit works, because i presume the computer does not know it's a flo
Click to expand...
Click to collapse
As the USB port is broken there is no hope that an OTG adapter would work because it can not function without the data connections, exactly like PC-USB. Have a look at the port's soldering, it may need some re-work. If the port's connectors are damaged then a replacement is very cheap.
:good:
k23m said:
As the USB port is broken there is no hope that an OTG adapter would work because it can not function without the data connections, exactly like PC-USB. Have a look at the port's soldering, it may need some re-work. If the port's connectors are damaged then a replacement is very cheap.
:good:
Click to expand...
Click to collapse
thanks for the suggestion
i sprung the back and was going to attempt to reflow the solder in case it had a dodgy connection - but i noted that the actual usb connector looked like it had been stretched, and took to it with my favourite pliers and performed some creative metalwork by squeezing it
lo and behold! the otg connection worked, at least for long enough to transfer the custom rom
thereafter when i reassembled the case, the otg connection failed but now the usb link seems to be happy enough even though that makes no great sense seeing it is the same connector port, and the otg works on my other android devices
still, gotta take what you can get, and i am now the proud owner of a nexus 7 "flo" with lineage doing nicely
thanks for all assistances
scruffy1 said:
thanks for the suggestion
i sprung the back and was going to attempt to reflow the solder in case it had a dodgy connection - but i noted that the actual usb connector looked like it had been stretched, and took to it with my favourite pliers and performed some creative metalwork by squeezing it....
Click to expand...
Click to collapse
Ahh this explains why my N7 - used daily - has never developed any USB port problems! I thought that this USB port's construction was rather 'weak' so preemptively I applied a simple reinforcement, have a look at the attachments.
It was 4 years ago....
:highfive:
Hello everyone.
So I have a few issues which I am guessing are all somewhat related.
TL;DR
1) Android auto stopped working
2) if I reboot. It will just power off and needs to be plugged in to power back on
3) usb c to usb c only works one side not both sides. But usb a to usb c works both directions.
Note: my wife has the same phone and had none of these issues with the same cables and such. So it's not cables issues. We also have the same OS.
The longer detailed version.
First issue. Android auto stopped working. At first it told me that there may be an issue with the cable and that I should get another cable. I tried my wife's pixel 3 xl and it worked fine. So it's not the cable issue. I tried restarting. The phone did not. So I plugged it in and it powered on. Now the phone will only boot if it is plugged in. Plugging the phone into the car usb a to usb c it charges on both side of the cable but there's no longer any warning about the cable for Android auto. Again my wife's phone works with the same setup so it's an issue with my phone. Then when plugging my phone in using the oem cable I noticed it only chargers using one side. The other side fails. Tested my wife's phone and both sides work. I then test my wife's cable and same issue with her cable for my phone.
OS 11 RQ1A.210105.003
I did a factory reset but same issues remain.
I'm open to using a ROM if it will fix the issue.
I saw a few posts on google forums about this issue but not fix/solution so I was kind of wondering if a ROM would possibly fix this issue.
Thanks so much for any help.
Willing to try most items as phone is out of warranty and I really like Android auto and hate not having it.