I have a pixel 2 XL, 64GB, Google (non-Verizon) model running android pie (9) on Oct 5 2018 security patch. I was able to unlock the bootloader via fastboot flashing unlock_critical. The device then wiped, no issues. Then when I went to reconnect my device and root/install TWRP, fastboot did not see the device. I booted to the OS and adb didn't see the device either. I have tried
-multiple cables (all Benson approved)
-multiple USB ports
-multiple factory data resets (both via settings and recovery)
-multiple systems (1 pc and 1 macbook pro)
-cleaning the device's usb-c port with iso alcohol
-jiggling the cable in case its not making a good connection
-downloading the OTA and attempting to flash that via stock recovery (didn't work, nothing showed up in the list)
-singing to it.
I have an additional pixel 2 xl which I put in bootloader mode and fastboot saw it instantly. Same with my old nexus 6p. I would unplug those devices, plug in my pixel 2 xl also in bootloader mode, but still nothing listed for `adb devices` (booted in android with USB debugging enabled) or `fastboot devices` (booted in bootloader). Any ideas? Thanks!
One thing I'd like to try is to be able to flash the stock OTA image. How would I go about doing that without ADB (ie using the sdcard)? I tried renaming the zip file to `update.zip` and placing it in the root of the home folder (defaulted to /storage/emulated/0) but when I go into stock recovery, its empty. All I see is (../). Any ideas for this?
DangerIsGo said:
I have a pixel 2 XL, 64GB, Google (non-Verizon) model running android pie (9) on Oct 5 2018 security patch. I was able to unlock the bootloader via fastboot flashing unlock_critical. The device then wiped, no issues. Then when I went to reconnect my device and root/install TWRP, fastboot did not see the device. I booted to the OS and adb didn't see the device either. I have tried
-multiple cables (all Benson approved)
-multiple USB ports
-multiple factory data resets (both via settings and recovery)
-multiple systems (1 pc and 1 macbook pro)
-cleaning the device's usb-c port with iso alcohol
-jiggling the cable in case its not making a good connection
-downloading the OTA and attempting to flash that via stock recovery (didn't work, nothing showed up in the list)
-singing to it.
I have an additional pixel 2 xl which I put in bootloader mode and fastboot saw it instantly. Same with my old nexus 6p. I would unplug those devices, plug in my pixel 2 xl also in bootloader mode, but still nothing listed for `adb devices` (booted in android with USB debugging enabled) or `fastboot devices` (booted in bootloader). Any ideas? Thanks!
One thing I'd like to try is to be able to flash the stock OTA image. How would I go about doing that without ADB (ie using the sdcard)? I tried renaming the zip file to `update.zip` and placing it in the root of the home folder (defaulted to /storage/emulated/0) but when I go into stock recovery, its empty. All I see is (../). Any ideas for this?
Click to expand...
Click to collapse
Have you tried toggling USB debugging a few times to see if it connects?
Badger50 said:
Have you tried toggling USB debugging a few times to see if it connects?
Click to expand...
Click to collapse
Yes.
Same thing happened to me. First it randomly rebooted and then hung on the "G" splash screen. I couldn't get it to boot at all. It wouldn't show up on windows 8 or 10 (it did on Sept patch) it would charge, but no adb. Had to factory reset in recovery and it booted, but still no USB connection. Went through diagnosis with Google tech support and they are replacing it under warranty.
Not really the same thing here but, my phone suddenly stopped being recognized by my windows 10 laptop even tried several different cables. Also what further made it evident that something must be wrong with the USB-C port when I used the dongle adapter for wired headphones nothing at all, no sound nothing but it charges just fine. I just contacted Google yesterday for a standard RMA and sent if off for a replacement. I love Google's devices but kind of sad I'll be on my 2nd replacement here now, oh well least I get another replacement right?
I've been having issues with my USB-C port as well. I've actually kinda chilled on flashing because of that. I'm worried it's gonna bite me in the ass.
So I ended up talking with Google and I just went for a replacement device. Not ideal but not much more I could do!
Related
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
jasonstackhouse said:
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
Click to expand...
Click to collapse
I would try a different cable as this device is very finicky; that solved my issue of the computer not recognizing the phone.
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Az Biker said:
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Click to expand...
Click to collapse
That would be nice if that were the problem, but unfortunalty I do not think it is. For example, when the issues first began, before I did the factory reset on the device, windows would pop up a message that said unknown device, and failure to connect. After the factory reset in TWRP the computer gave up all together in recognizing the phone. Another sign it was likely not a hardware failure was when the device was on and i was attempting to connect the otg usb to the phone it would give me some weird options. With android P the options were, allow this device to control the usb, or allow the USB to control the USB. that made no sense to me since why would i want the the USB to have any control, it couldnt do anything its not a computer its only a storage device. However, even though I had file transfer selected in developer options, it would not allow this connection. The options were all greyed out and it would not allow the pixel to have control over the usb device.
As for USB cords I have used without fail the google issued USB cord that came with the Pixel 1 xl, It has never faile me or had any issues. It is still fully functional as I was able to use it to connect my girls note 8 to my computer for file transfers and all other things my phone is not doing anymore.
I reached out to google and explained the situation to them, after i told them I was on Dev preview beta and they verified this to be true they told me this is likely a hardware failure and offered to replace the device. I am now waiting on the new device to be sent to me, however still cant accept that i cant recover the current device with an unlocked bootloader, TWRP installed, and access to fastboot/bootloader screen. I have seriously bricked phones before as in they would not even turn on and I was able to get them back up and running, this would be my first ever device I could not recover and what makes it worse is that it actually has TWRP installed and powers on and off just fine.
Sorry for the obvious question: Do you have the latest drivers? I don't have the drivers set to the whole system (Windows), so if I don't CD into my fastboot folder, I can't do anything because the system wide drivers aren't current. Don't know if that could be your issue?
I'm too lazy to fix the PATH of my drivers ¯\_(ツ)_/¯
I had an issue similar to this. I was trying to hook up a USB c to Ethernet adapter. It worked fine on April's patch but after I flashed Mays the phone wouldn't recognize it. After I plugged it in my phone rebooted and I no longer had access to developer options and it wouldn't read any usb device. Luckily I had a TWRP backup on my device. Once I flashed the backup which was only about a week old everything worked again. I haven't tried using the adapter again. I think something in the data partition got corrupted. I tried just restoring the boot and system partition and that didn't fix it. Try doing an advance wipe and formatting the data partition. That might get you back up and going.
have we even seen a bricked device yet?
twiz0r said:
have we even seen a bricked device yet?
Click to expand...
Click to collapse
I didn't think it was possible, I still dont understand how this is happening. For the other responses above, I have all the drivers up to date, and I already formatted data, wiped everything. At this point I would like to see if there is anyway to delete TWRP recovery from the device, anything, I have no OS on the device, but for some reason still have TWRP on both A and B.
I almost dont want to give the phone back to Google because I want to figure out what happened and how to fix it, its definitely not broken/bricked like you see when someone flashes the wrong files to a device, it just has no USB connection capabilities which in-turn have rendered the device useless.
When I had Samsung phones if you bricked a device to the point it doesn't even turn on correctly you could always save it still using ODIN. Its weird that the google flagship device and software doesn't have its own proprietary flash software like Samsung, LG and HTC, we just have adb/fastboot, I feel like if we did, i may be able to get this thing started again.
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Pyr0x64 said:
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Click to expand...
Click to collapse
I can't access the play store on the device in it's state. I do have access to fastboot. I can boot the phone to fastboot, and into TWRP, only problem is the phone doesn't communicate with the computer in either state. If the pixel had a SD card slot I would just load up a recovery but unfortunately we don't have that luxury
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Triscuit said:
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
The cable is not the issue, I confirmed this by testing all my cables with the new device that I just received for my warranty exchange. I also tried my luck with Linux, after a complicated installation on my computer I was able to have Linux actually detect the device (partially) when the device was plugged in at splash screen I got nothing, at fastboot/bootloader screen nothing, but once the phone booted into TWRP it came up as AOSP device, when I attempted clicking on the AOSP device being detected by Linux an error message popped up telling me mtp or midi error, not sure for sure what one it said. Either way I couldn't connect for any transfer of information, I tried adb sideload and that failed as well.
This has been an experience for the memory books, glad that old device is gone and I'm back up and running on a working phone. No more beta testing for me, I'll be ready for Android P when they get it out of beta, I don't have the time or patience to deal with any more warranty exchanges.
Strange issue. After applying the Feb 2019 security patch over air, my phone is no longer recognizing when it is plugged into a PC. I plug into my PC and I get a charge symbol on my battery but no pull down option to switch from charging to USB mode. Things I've tried:
1. New Cable although the wife has a Pixel 3 (standard) that works with this cable and computer just fine.
2. Different PC
3. Toggling USB debugging
4. Changing the USB setting in developer mode to transfer
5. When I plug a USB stick into the phone using the USB-C to USB-A adapter, the phone recognizes the stick and I can browse files
6. "Cleaning" the USB-C port
7. Also booted into safe mode (which I would assume should be like a factory reset) but no USB.
8. Switched between USB 3 and USB 2 ports on the PC.
It seems to me that there's a software issue with the Feb update that messed with the usb settings. I called google and they just want me to factory reset my device before they will transfer me to tech support. I'm avoiding that because I don't want to go back through the time/trouble of resetting up my phone. Any tips/tricks I've missed here?
If you have a Google variant with the BL unlocked, flash the factory image with the -w removed from the flash-all batch file. That way, you won't lose data. If you are on the Verizon variant or don't want to unlock you BL, sideload the OTA from stock recovery. See if it cleans up your issue. Also, sounds like you might have a driver issue on your PC. Easier to fix that first if it is the issue.
I have the February update over the air and I had no issues connecting to my Chromebook (crouton) via USB to pull an APK with ADB. I did have to turn USB debugging back on (not sure if I turned it off or if it was turned off from an update) and change the connection type, it was set to charging only.
More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.
copekyle said:
More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.
Click to expand...
Click to collapse
Try putting the phone into Fastboot mode and use the command "fastboot devices" to see if it is recognized. If it is, then the problem is on the ADB side, which is part of the Android system.
If it can connect via Fastboot, it's less likely to be a driver issue. You can try "adb devices" too with the phone booted to see if it is recognizing it all. May need to toggle through the various connection modes, I believe I used PTP the last time, but not certain.
As for sideloading, you will need the phone to be recognized by either ADB or Fastboot. You can sideload an OTA update from Recovery with a locked bootloader or as @sliding_billy said you can unlock the bootloader and flash the factory image which is done via Fastboot.
I would also verify that you have the latest version of the Android SDK installed just to cover that base.
copekyle said:
More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.
Click to expand...
Click to collapse
You don't need to be in file transfer mode to connect via fastboot. Check connection from there after using the combo keys to get into fastboot (power/vol down) for the factory image or one step further into recovery for sideload.
Neither Fastboot devices or ADB devices lists a device. When put in fastboot and recovery, my device manager on either computer does not register that there is a device connected.
copekyle said:
Neither Fastboot devices or ADB devices lists a device. When put in fastboot and recovery, my device manager on either computer does not register that there is a device connected.
Click to expand...
Click to collapse
Sounds like you have attempted everything... New cable (but rereading I don't see where you tried using a C>A cable instead of a C>C and that definitely needs tried). New computer/port/OS. Direct connect to fastboot. I think you are going to need to backup to the cloud (at least you have a functional device with internet) and factory reset the device.
P.S. I just thought about this, but do you have the current platform tools (ADB/Fastboot)? https://developer.android.com/studio/releases/platform-tools.html
sliding_billy said:
Sounds like you have attempted everything... New cable (but rereading I don't see where you tried using a C>A cable instead of a C>C and that definitely needs tried). New computer/port/OS. Direct connect to fastboot. I think you are going to need to backup to the cloud (at least you have a functional device with internet) and factory reset the device.
P.S. I just thought about this, but do you have the current platform tools (ADB/Fastboot)? https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Sadly I don't have a computer with a USB C port. I have been using only cables with C>A. I downloaded the latest platform tools yesterday before trying fastboot/adb. I'm waiting for a call back from Google tier 2 tech support within 72 hours. If anything comes of it, I will report back here.
copekyle said:
Sadly I don't have a computer with a USB C port. I have been using only cables with C>A. I downloaded the latest platform tools yesterday before trying fastboot/adb. I'm waiting for a call back from Google tier 2 tech support within 72 hours. If anything comes of it, I will report back here.
Click to expand...
Click to collapse
Good luck!
Hi so i installed twrp and rooted my pixel with magisk. everything went fine.
saw the sultan kernel decided to flash but my phone does not recognize any computer with any cable as a computer but as a powersource. Adb and fastboot not working on any laptop or desktop (except the desktop on which i unlocked my bootloader and rooted my device) tried to connect over usb (adb fastboot filetransfer) on Linux Windows and MacOs. all unsuccesfull.
dev options is on:
oem unlock toggled
usb debug toggled
phone is running stock rom stock kernel. (Edit: kernel is the sultan kernel on stock rom)
once i connect the phone sees it as a pc pops op usb options then blacks it out because it sees it as a powersource.
whats wrong with it i cant figure it out...
Nightfall41 said:
Hi so i installed twrp and rooted my pixel with magisk. everything went fine.
saw the sultan kernel decided to flash but my phone does not recognize any computer with any cable as a computer but as a powersource. Adb and fastboot not working on any laptop or desktop (except the desktop on which i unlocked my bootloader and rooted my device) tried to connect over usb (adb fastboot filetransfer) on Linux Windows and MacOs. all unsuccesfull.
dev options is on:
oem unlock toggled
usb debug toggled
phone is running stock rom stock kernel.
once i connect the phone sees it as a pc pops op usb options then blacks it out because it sees it as a powersource.
whats wrong with it i cant figure it out...
Click to expand...
Click to collapse
I'm in very much the same situation. I've seen several USB connectivity threads roll through here recently so I'm not sure if anything larger is going on or not. Basically, I always do updates with full factory images w/o wiping. I was able to install the April update (in early April) just fine. I went back in late April to try to use fastboot and couldn't connect via USB for file transfer, ADB, or fastboot. I updated all my platform tools and the Google USB driver which made no difference. I tried on 3-4 Windows 10 desktops/laptops and 1 MacOS laptop. Nothing. I opened a support ticket with Google (and went through extensive troubleshooting steps) which was then escalated. It has been over a week and they have not responded. I even checked back yesterday to make sure it wasn't lost in the shuffle, and I was assured that it was still active and assigned to the proper team.
Just for giggles, I tried connecting to a Win7 desktop w/ only USB 2.0 and the phone immediately connected MTP (we had made this the default USB mode during the troubleshooting process). Since I was still running a modified (root) kernel, I went ahead and tried flashing the stock boot image with fastboot (both slots) and it worked! I figured since I had already wiped the phone for troubleshooting, I would try pushing the entire April image (w/ wipe). It flashed bootloader, radio, and maybe boot image (can't remember), but then lost connectivity when trying to push the system image. Fortunately, the phone booted right back up. Since then, connectivity is possible, but sporadic, on that machine. Being 100% stock, with no other options, I knew the only way to get an entire factory OTA pushed to the phone would be to opt into the beta, install the beta, then opt out, which pushes the latest non-beta and wipes the phone. I did this, but, again, it resolved nothing.
BTW, for me, this issue affects all devices that pass data through the port including USB OTG flash drives and game controllers. It's also not cable specific as I have tried a factory Google USB-A to C cable, factory Google USB-C to C, and several other USB-A to C cables (the ones I always use for ADB and fastboot commands). There does not appear to be any physical damage to the port and I cleaned it extensively with compressed air and a plastic dental pick.
Sorry I don't have a solution at this point, but I wanted to pass on the steps that I have taken.
Phone is detected by "adb devices" but not detected by "fastboot devices"
I purchased a used P3a XL from Swappa. I would like to install a custom ROM. As we all know, in order for me to do that I need to unlock the bootloader. I think the phone is a Google Edition (checked SKU on box against what is sold in stores).
I have done quite a bit of research before posting here and think I have the process correct. I have enabled developer mode and toggled the OEM unlock option. I am able to "adb devices" and see the phone on my computer terminal. I "adb reboot bootloader" and the phone reboots in to "Fastboot Mode". When I do "fastboot devices" nothing shows. When I boot in to fastbootd (via stock recovery) and execute "fastboot devices" I can see the phone. I execute "fastboot flashing unlock" and it fails with "fastboot flashing unlock failed remote: unrecognized command flashing unlock".
I have tried this on my PixelBook with Linux installed and on my Ubuntu lab machine. Both of those machines give me the same results. I tried with my Windows 10 laptop, but the phone isn't detected by any of my USB-C to USB-A cables.
I have factory wiped the phone a few times and attempted the steps above, but it results in the same thing. Phone is not detected in fastboot. Interestingly, I am able to sideload the latest OTA (QQ3A.200605.001, Jun 2020) without any errors. After sideloading the latest OTA, I am still unable to unlock the bootloader.
I suspect one of two things:
1. The phone is a VZW/Sprint/T-Mo edition. Even so, VZW edition can be unlocked. I tried that method (found an XDA thread to do that).
2. Something is wonky with the phone (bootloader software)
Unfortunately, since I bought it second hand, I do not think Google would honor the hardware warranty to issue me an RMA.
What do you folks think may be an issue?
ruhrohs said:
I purchased a used P3a XL from Swappa. I would like to install a custom ROM. As we all know, in order for me to do that I need to unlock the bootloader. I think the phone is a Google Edition (checked SKU on box against what is sold in stores).
I have done quite a bit of research before posting here and think I have the process correct. I have enabled developer mode and toggled the OEM unlock option. I am able to "adb devices" and see the phone on my computer terminal. I "adb reboot bootloader" and the phone reboots in to "Fastboot Mode". When I do "fastboot devices" nothing shows. When I boot in to fastbootd (via stock recovery) and execute "fastboot devices" I can see the phone. I execute "fastboot flashing unlock" and it fails with "fastboot flashing unlock failed remote: unrecognized command flashing unlock".
I have tried this on my PixelBook with Linux installed and on my Ubuntu lab machine. Both of those machines give me the same results. I tried with my Windows 10 laptop, but the phone isn't detected by any of my USB-C to USB-A cables.
I have factory wiped the phone a few times and attempted the steps above, but it results in the same thing. Phone is not detected in fastboot. Interestingly, I am able to sideload the latest OTA (QQ3A.200605.001, Jun 2020) without any errors. After sideloading the latest OTA, I am still unable to unlock the bootloader.
I suspect one of two things:
1. The phone is a VZW/Sprint/T-Mo edition. Even so, VZW edition can be unlocked. I tried that method (found an XDA thread to do that).
2. Something is wonky with the phone (bootloader software)
Unfortunately, since I bought it second hand, I do not think Google would honor the hardware warranty to issue me an RMA.
What do you folks think may be an issue?
Click to expand...
Click to collapse
Sideloading is an adb function, not fastboot. Make sure you have the lastest Android platform tools. This doesn't mean you can unlock the bootloader but to get fastboot working.
Also make sure you have the oem cable or at least a decent cable, and use a 2.0 port if possible. I've seen other a/b devices refuse to work or give half commands with 3.0+ ports. What does it says underneath oem unlocking in dev settings? I've attached the latest adb/fastboot files just in case you might need them.
Tulsadiver said:
Sideloading is an adb function, not fastboot. Make sure you have the lastest Android platform tools. This doesn't mean you can unlock the bootloader but to get fastboot working.
Click to expand...
Click to collapse
I just updated my Ubuntu machine with the lastest SDK, so both ADB and Fastboot were updated. The phone can be seen with "adb devices". It can be seen with "fastboot devices", but only if the phone is in fastbootd mode. Wouldn't this confirm that fastboot works on the laptop?
41rw4lk said:
Also make sure you have the oem cable or at least a decent cable, and use a 2.0 port if possible. I've seen other a/b devices refuse to work or give half commands with 3.0+ ports. What does it says underneath oem unlocking in dev settings? I've attached the latest adb/fastboot files just in case you might need them.
Click to expand...
Click to collapse
I am using a PixelBook with the original USB-C to USB-C cable that came with the phone. My Windows laptop doesn't see the phone at all
OEM unlock option is enabled.
ruhrohs said:
I just updated my Ubuntu machine with the lastest SDK, so both ADB and Fastboot were updated. The phone can be seen with "adb devices". It can be seen with "fastboot devices", but only if the phone is in fastbootd mode. Wouldn't this confirm that fastboot works on the laptop?
I am using a PixelBook with the original USB-C to USB-C cable that came with the phone. My Windows laptop doesn't see the phone at all
OEM unlock option is enabled.
Click to expand...
Click to collapse
As far as your window laptop, you might try installing usb drivers.
https://developer.android.com/studio/run/win-usb
Tulsadiver said:
As far as your window laptop, you might try installing usb drivers.
https://developer.android.com/studio/run/win-usb
Click to expand...
Click to collapse
Yup, tried that as well. I even went as far as wiping one of my lab machines, installed Windows 7, copied and installed the command line tools only from here: https://developer.android.com/studio#downloads, but no dice. For Windows, I think it's a cable issue. I'm getting new USB-C to USB-A cables delivered tomorrow. Once I get them, I will try on my Windows laptop.
Update to my issue...
Bought a 3 pack of Anker cables. Plugged each of them to my phone and to each of my Win 7 and Win 10 laptops. Both laptops are able to charge the phone, however the don't detect the phone for data transfer/USB debugging. I checked device manager, deleted/uninstalled all Android devices that were listed (including my first generation Pixel XL), rebooted my laptops and tried again. No dice... At this point, I'm chalking it up to the Pixel 3a XL phone itself and an issue with the hardware.
Note to self... Buy a brand new phone for an extra $100 and I would have saved myself over 4 days of troubleshooting an issue.
ruhrohs said:
Update to my issue...
Bought a 3 pack of Anker cables. Plugged each of them to my phone and to each of my Win 7 and Win 10 laptops. Both laptops are able to charge the phone, however the don't detect the phone for data transfer/USB debugging. I checked device manager, deleted/uninstalled all Android devices that were listed (including my first generation Pixel XL), rebooted my laptops and tried again. No dice... At this point, I'm chalking it up to the Pixel 3a XL phone itself and an issue with the hardware.
Note to self... Buy a brand new phone for an extra $100 and I would have saved myself over 4 days of troubleshooting an issue.
Click to expand...
Click to collapse
You do realise that you've got to change the USB settings for it to do data transfer right???
thatsupnow said:
You do realise that you've got to change the USB settings for it to do data transfer right???
Click to expand...
Click to collapse
my problem more than once, ashamed to say. after updating drivers and cords. then forgot to pull my notifications down for that last little line. it's a learning process though. (so they say).
kevinchristopherson said:
my problem more than once, ashamed to say. after updating drivers and cords. then forgot to pull my notifications down for that last little line. it's a learning process though. (so they say).
Click to expand...
Click to collapse
No worries dude even when you change default usb settings it still stays in charging mode
thatsupnow said:
You do realise that you've got to change the USB settings for it to do data transfer right???
Click to expand...
Click to collapse
Yup, I know that I need to change it to data transfer, however the phone isn't detected by either of my Windows laptops. The phone is only detected via ADB on my Chromebook. I can do an "adb reboot bootloader" and it'll accept the command, but "fastboot devices" or "lsusb" shows no devices.
kevinchristopherson said:
my problem more than once, ashamed to say. after updating drivers and cords. then forgot to pull my notifications down for that last little line. it's a learning process though. (so they say).
Click to expand...
Click to collapse
Yup, my first gen Pixel XL will notify me when I pull down the notifications, but the Pixel 3a doesn't.
I ended up setting up the phone and used it for a fewdays. It works fine, however I'm used to running AdAway, AFWall, EX Kernel Manager, Greenify, High Brightness Mode, NapTime, Titanium Backup and Viper4Android. There are workarounds to enable Greenify and NapTime via ADB, but it's a moot point without the other root dependent apps.
Updating this thread to close this out.
Bought a brand new Pixel 3a XL from the Google store. I was able to root without any issues on my Windows 10 laptop. I attempted the same exact process with the same USB port and USB cable for the Pixel 3a XL that I bought from Swappa, but it didn't work. This confirms my educated guess that it's a hardware issue on the phone.
The secondary market may soon be flooded with Pixel 3a XLs once the Pixel 4a is released. Before you get burned on a non-rootable phone, ask the seller how long they have owned the device and check the warranty on it. As of this post, you can check the IMEI Here: hxxps://store.google.com/repair (replace the hxxps with https).
Good luck!
You need to download the google usb driver and update the Pixel 3 driver in Device manager with the usb driver. Then the computer will recognize the phone as a fastboot device while it's in bootloader.
For me what solved this was I wasn't adding the "platform-tools" folder to my path.
I was using "fastboot.exe flashing unlock"
But once I added to path and did "fastboot flashing unlock" it worked like a charm
On Linux, did you try sudo fastboot flashing unlock? This is the only thing that works for me. Sudo before all fastboot commands.
In my case on Ubuntu 20.04, it was a USB 3.0 port problem. It was detect device with fastboot devices but other commands does not has a response. My laptop hasn't got a USB 2.0 port. Then I disabled internal USB 3.0 support in my BIOS and now fastboot is working normally. But all USB 3.0 support is stopped. It seems USB 2.0 hub is the better option. I will set back the BIOS setting later.
Yesterday i bought the G020B version, and the same happened to me while unlocking bootloader, fastboot keeps on <waiting for device> like if the phone was not even connected
I searched for a driver that could work and found this (For windows)
Basically, my system can't detect properly the phone because the driver was not 'updated'. (Even when i can use fastboot on other devices)
Hope it works for you or everyone here.
Today I tried to transfer some files from my Pixel to my PC.
After plugging in different cables into different PCs and Ports I only could get my phone to load.
There was no way to change it to transfer mode...
Windows didn't recognize the phone at all.
In the developer options it is already set to data transfer / Android Auto.
I am using the latest December (October) patch.
My final goal was to backup my data and install a different ROM now after there are no more official updates.
Anyone has an idea how to get my phone connected to a PC again? In the past it was working well - but I don't know how long it isn't working anymore.
PS: I already cleaned to USB port of my Pixel.
Thanks a lot!
I just bought a used Pixel 2 XL and have the same 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.
It's got to be a software problem on the phone. 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.