I've been researching and trying to sort this out on my own for a while now. I've turned up nothing, so I figured I'd ask for some help. I'll try to provide as much information as possible here.
I was attempting to unlock and root my Razer Phone from my Windows PC. I plugged it in and had it recognized over ADB with no issue. I sent "adb reboot bootloader" to start things off. Once it was in download mode, I sent the "fastboot -i 0x1532 devices" command to make sure it was recognized. It wasn't. I checked devices manager, and sure enough, it was not picking up the Google driver that every other device I own works with. I attempted to update the driver manually by pointing it to the inf file. It gave me an error stating that the driver is not designed to work with 64-bit Windows. I found that odd, as this is the exact same driver that I've used with my other devices for this stuff. I plugged in my HTC 10, since that was nearby. It was recognized via fastboot like it always was. Same cable I was using with the Razer and everything.
I booted to Linux Mint on the same machine and tried the same stuff. It would pick up the Razer only in fastboot, but not ADB. In fastboot, I could detect it with "fastboot -i 0x1532 devices", and it showed up just fine. When I attempted to run "fastboot -i 0x1532 flashing unlock" it just gave me the fastboot command reference list. (I don't have a screenshot, but it looked like this, in case you're unsure what I am referring to.) I rebooted back to the system and double checked that I had checked "Enable OEM Unlock", and I had done that already. I double checked everything with my HTC 10, and again, it all works fine on the HTC 10. ADB and fastboot are both recognized correctly on Linux.
So armed with this information, I moved over to my Linux server. I used a different cable this time, and got a similar result. The Razer phone was recognized over ADB and I was able to get into fastboot. Once there, it was detected with the fastboot devices command. I attempted to run the unlock command, and again was presented with the fastboot reference list as before. Double checked with the HTC 10, and all was workign fine with that device.
Does anyone have any ideas, or is it possible that it's the Razer phone that's the problem? I may have access to a Mac laptop later on, and I could attempt this from there, but this is getting nuts. I don't think I've ever had this much trouble getting into a device before.
Yeah I had this as well, basically you may have the latest drivers but are missing the latest adb/Fastboot executables. Apparently they have changed a few commands in the newer one and that way of unlocking isn't in the old version. Just google for the adb/Fastboot package from the Google site, can remember the exact name but it was the first hit on Google. I just extracted the whole zip to a directory and used it right from there. The reason you are getting the help screen from Fastboot is cause for that version at least, your giving it an illegal command.
I got the same problem till I put my usb in a usb 2.0 in the back of the pc in a highlight usb port witch I read after on Asus Website that suppose to charge your phone if you turn off your pc so basically a always on usb. Also I managed to unlock and brick my device only with one cable I tried 4 cables none of them worked .so for you to keep In mind
Try different cables
Try usb 2.0
Try driver from twrp for razer phone thread that worked for me
Seems to be an ongoing issue for me on my main desktop. I grabbed my old development laptop out of the closet, booted it up, and I was able to get everything recognized and working. I tried doing some more work this morning on my desktop and noticed that I'm having driver issues elsewhere, so it seems to be an issue with this machine. I'm still not sure why the Linux installation on the same machine was exhibiting the same issue, though.
Related
Hello
Posted this over in Pauls MoDaCo forum as well but not had any replies yet so thought it best to try here as well.
I've bricked my Desire, phone loads up but the sim and sd card aren't recognised (though I can still use wi fi).
When connecting the phone to my PC (tried windows 7 and XP) the drivers fail to install and I get various faults like the device being recognised as android 1.0 usb to a Qualcomm device.
The phone is still rooted (I can install rooted apps from the market) however after following various unbricking guides I always get stuck at stage 2 (i.e. enable sd card), if the PC won't recognise the device how can i run the 'fastboot oem enableqxdm 0' command?
I've also tried running fastboot using a terminal app on the phone but it doesn't recognise fastboot, should i be in a specific directory on the phone when running this command?
Any help greatly appreciated.
Cheers
Have you tried using a different jab port? I had to use one at the back of my pc front ports wouldn't install drivers properly.
Sent from my HTC Desire using XDA App
You need to follow the guide on modaco for unbricking your device. You have the usb brick, and it can easilly be fixed.
Follow the steps religiously and you will be up n running in no time again.
I've followed the guide lots of time, it's not that long winded so it shouldn't be to hard to follow.
I get stuck on step two, using the fastboot command.
My PC and also tried laptop (Win XP and 7), different USB ports (front and back) but each time it attempts to load drivers and I end up with it either being recognised as an Android 1.0, Android Bootloader Interface or a Qualcomm device. I then run fastboot, and get the device not recognised error.
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
celticone said:
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
Click to expand...
Click to collapse
You don't need to get into recovery for this.
You have sdk installed, so boot your phone by pressing power while holding down the volume down button.
Use a command prompt on your pc and cd to the tools directory in the sdk. If the sdk is saved to the root of your C: drive on the pc you would type
Code:
cd C:\android-sdk-windows\tools
When in there type
Code:
fastboot oem enableqxdm 0
This will re-enable your sd card and allow you to continue.
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
celticone said:
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
Click to expand...
Click to collapse
It definitely sounds like the old usb brick problem, so that's a good thing! When you tried the commands were you booted into fastboot? When you connect the phone to the computer does the phone display change from saying fastboot to fastboot usb? I think thats what it should say, can't remember to be honest!
Have you tried another usb port, and a different cable too?
Edit: I'd also try rebooting the computer to ensure any running process etc are closed.
Got it fixed, final throw of the dice this morning I connected the phone to a Vista laptop and it was recognised straight away, so downloaded HTCSync then ADB tools on to the laptop and finally got the re enable command to work.
Jeez that took for ever, strange that Xp, Win7 and Linux PCs couldn't recognise the phone but Vista did.
Still got it sorted, thanks for the help.
No worries. Glad you got it sorted.
I have almost the same problem.
but with the legend.
SD is not recognized.
Can´t Call,
Can´t connect via USB.
Is there something I can do in the built in terminal in the ROM?
I just can't seem to get fastboot to see the phone...
I have a Z00AD2 with 2.19.40.22 software. USB Debugging is turned on. ADB sees the phone, both from my Ubuntu host system, and from a Windows 8.1 virtual machine. When I use "fastboot device" I just get "<waiting for device>" and when I run scripts/batch files (such as the one-click root) it hangs as well.
I'm assuming there's something very simple, and probably obvious, that I'm missing - but after 8hrs of messing with it yesterday, I'm a little fried.
Appreciate any thoughts!
This morning I installed a new Windows8.1 VM, installed the Intel drivers and adb/fastboot from the sticky page in the general forum. During adb/fastboot install, should I use the drivers provided if I've already installed the Intel version? I think I've tried both ways at this point... Plug the phone in, and it is recognized in adb. Fastboot displays "waiting for device".
I tried the one-click root batch file, and when running CheckBeforeAction.bat my phone restarts into fastboot mode, with the android opened-up on its back, and the batch file continues to "make sure 'asus android bootloader interface' installed on your computer successfully" (I'm not sure it is? I don't see any reference to it anywhere...).
If I proceed further I get the "if you see '123456789 ... fastboot' then you are ready to root" message - where is that supposed to display? On the phone's screen? Finally I hit a key and the batch file says it's rebooting my phone, and it gets stuck on <waiting for device>
Again, I'm sure I'm missing something simple; but I just can't figure what step(s) I'm missing.
Solved the problem, at least in terms of running fastboot on my virtual machine... I had only set up one device filter in VirtualBox, for the phone when it was in it's normal state. When in fastboot mode it uses a different driver, and thus needed a second device filter set up - once I did that, everything went smoothly as far as adb and fastboot functionality go. Having trouble now with flashing twrp...
So when I originally got my OP3 and rooted it, installed a recovery and installed SuperSu, I had basically no problems. Installed drivers I found on here and never had an issue. Today I found a guide on the OP forums to disable doze which I apparently need to do since certain notifications aren't working right. I plugged my phone in and tried to follow the instructions, listed here under push notification issues
https://forums.oneplus.net/threads/...3-guide-solutions-e-t-c.448097/#post-14886949
When typing in adb devices, my device shows offline. I have done numerous things to try and fix the issue which I will try to lay out here. Initially I didn't install adb or the drivers as the guide suggests, since I had already done that - but after things not working I did try that and that didn't help. Still receive the "offline" next to my serial number device. The device works fine, and I can see it and transfer files to it just fine in the MTP mode. I have also tried to "revoke" permissions like described in the youtube guide I found here https://www.youtube.com/watch?v=eSApv8NXqD4
However that didn't work either. I should note that even after revoking permissions and turning usb debugging on and off again, the phone never asks me to authorize my computer as it does in that guide. In fact I don't believe it ever asked me to authorize my computer even when I first got the device. I don't know if that is part of the issue or not. I have also used a different adb version since somewhere I found that you needed to use the newest version. The version I had was 1.32 and I found the newest here on the forums here http://forum.xda-developers.com/showthread.php?t=2317790 that it was 1.4 as the newest. That adb returns the same results.
I should also note that the guide I linked from oneplus never actually tells me to put the phone into fastboot mode to execute the command, so I tried it initially booted up, and then in fastboot thinking it was supposed to be executed there, however in fastboot mode the phone is not seen at all. adb devices returns nothing, and booted it returns offline mode. Please help me
Nobody?
Have you tried some of the suggestions on https://stackoverflow.com/questions/14993855/android-adb-device-offline-cant-issue-commands? I'm not really sure what the situation is like on Windows but first I'd ensure you've installed the latest official Android SDK just to rule out an issue with the version of ADB you're using. You could also try using ADB over WiFi.
Apart from that, you can probably get by without ADB for now. Just run the commands in a terminal emulator on the device and/or create an init script.
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
I seem to remember the same thing happening when I got mine a couple days ago and unlocked the BL within a few hours of unboxing. I ended up doing the standard unlock followed by unlock critical commands anyway. Worked fine for me.
morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
Try just turning the phone off and then entering fastboot via volume down and power button. THEN, plus in your phone. Do a 'fastboot devices' and see if it shows up now. In my experience, I got my phone...checked oem unlock and all that...booted into fastboot mode via hard method. And my phone is detected instantly. I did not install any drivers, update platform tools (mine is from like 2012), and even used a third-party USB-C cable. It works every time. Also, I am using the adb and fastboot executables from an older adb minimal set. Probably from like a year or so ago. I don't ever use the SDK ones really anymore.
morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
I'd check and make sure your adb/fastboot is up to date, or do a reinstall just in case.
There are so many options for adb/fastboot and drivers. Where does one find "the latest," that everyone is speaking of?
Thanks for the suggestions but still not working. Even tried disabling driver signature verification at startup. I'm going to uninstall everything, factory reset the device and start over. Might also try a usb-c to usb-a cable. Any other thoughts?
Update: Nothing worked until I used a usb-c to usb-a cable, then it worked like a charm. Must be a Lenovo thing.
morrowa2 said:
Thanks for the suggestions but still not working. Even tried disabling driver signature verification at startup. I'm going to uninstall everything, factory reset the device and start over. Might also try a usb-c to usb-a cable. Any other thoughts?
Update: Nothing worked until I used a usb-c to usb-a cable, then it worked like a charm. Must be a Lenovo thing.
Click to expand...
Click to collapse
I can't even get adb to recognize my device ....I have used multiple cables I'm about to return this phone
canemaxx said:
I can't even get adb to recognize my device ....I have used multiple cables I'm about to return this phone
Click to expand...
Click to collapse
have you tried a usb-c to usb-a cable. that worked for me.
morrowa2 said:
There are so many options for adb/fastboot and drivers. Where does one find "the latest," that everyone is speaking of?
Click to expand...
Click to collapse
Latest ADB/fastboot: https://developer.android.com/studio/releases/platform-tools.html
Latest USB driver: https://developer.android.com/studio/run/win-usb.html
I had no luck except about once in 20 it'd work. Then swapped to a different USB-C port on my laptop, then it worked. FWIW, I tried USB-C to USB-C and USB-C --> USB-A (adapter) to USB-C and it didn't make a difference.
js042507 said:
Try just turning the phone off and then entering fastboot via volume down and power button. THEN, plus in your phone. Do a 'fastboot devices' and see if it shows up now. In my experience, I got my phone...checked oem unlock and all that...booted into fastboot mode via hard method. And my phone is detected instantly. I did not install any drivers, update platform tools (mine is from like 2012), and even used a third-party USB-C cable. It works every time. Also, I am using the adb and fastboot executables from an older adb minimal set. Probably from like a year or so ago. I don't ever use the SDK ones really anymore.
Click to expand...
Click to collapse
I did this and when in the bootloader screen, I am able to display fastboot devices, but when I go into recovery mode and try and flash something via ADB (the November patch since I am not pulling it OTA), it seems to start but it just sits at "Verifying update package" on the phone and "loading: 'taimen-ota-******.zip'" and never progresses. Almost like the PC and the phone are not talking properly?
tluley51 said:
I did this and when in the bootloader screen, I am able to display fastboot devices, but when I go into recovery mode and try and flash something via ADB (the November patch since I am not pulling it OTA), it seems to start but it just sits at "Verifying update package" on the phone and "loading: 'taimen-ota-******.zip'" and never progresses. Almost like the PC and the phone are not talking properly?
Click to expand...
Click to collapse
Like others have stated, maybe try a USB-C to regular USB-A cable. I have only used that type of cable, but didn't realize that the actual cable that comes with the phone might be a problem. I never used it to test that theory though.
js042507 said:
Like others have stated, maybe try a USB-C to regular USB-A cable. I have only used that type of cable, but didn't realize that the actual cable that comes with the phone might be a problem. I never used it to test that theory though.
Click to expand...
Click to collapse
Yeah that is all I have ever used. I use a USB A to C Cable Matters cable.
tluley51 said:
Yeah that is all I have ever used. I use a USB A to C Cable Matters cable.
Click to expand...
Click to collapse
I don't know then. I haven't attempted the update yet to provide any feedback. However, others have reported this issue in the 'November OTA' thread. I would look there.
morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
For anyone in the future, ensure the that Device Manager is showing the 'Android Composite ADB Interface' driver installed.
Then, just download the latest Platform Tools (from https://developer.android.com/studio/releases/platform-tools), and from inside that folder, open a Powershell prompt, and then 'adb reboot bootloader'. Once you are in the 'fastboot' mode, the 'fastboot devices' command works.
I had the same problem. I fixed it by plugging in my UBS-C to USB-A cable into a USB 3 port instead of a USB 2 port.
I am facing the same issue, its been almost 20 days. Tried everything but couldn't get it worked. So dropped the idea of rooting my px2L
My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com
cooltime said:
My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com
Click to expand...
Click to collapse
worked for me thanks.
cooltime said:
My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com
Click to expand...
Click to collapse
This works... Get the Google Driver.
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.