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.
Related
I have a Nexus 7 2013 that wont boot. USB Debugging was not enabled. At this point, I am just trying to wipe the machine with a stock image, but I am having trouble.
I have installed the sdk and drivers (so many drivers!)
Recovery mode fastboot does not recognize the device.
ADB recognizes the Nexus, but I cant seem to get it to do anything with it.
e: failed to mount anything.
I have read through so many forum threads that I'm just overwhelmed, and they all seem to require the machine being in USB debugging mode before any changes can be made.
Please help or tell me what pertinent information I have omitted.
Thank you
I think USB debugging only matters in ADB, which is when the device is actually booted into Android OS. You probably want fastboot, which is a different "application" and set of commands in a command prompt.
Code:
fastboot devices
Does that give you anything when the tablet is in fastboot mode? It should list the serial number of the device, similar to "adb devices" does. If not, it could be drivers, or another issue with the device.
Have you tried unlocking the bootloader? This will induce a factory reset of the current firmware version, which may allow you at least boot normally and take any available OTA updates.
Hello,
fastboot devices lists nothing, while adb does show the serial number.
I have used so many tutorials and a couple of toolkits that now I have no idea what is happening with my drivers.
Unlocking the bootloader to force a factory reset sounds amazing, but all the information I can find says I need to have USB debugging enabled to do so. I can not boot into the system to enable it.
Is there a way to force a reset without USB debugging?
Thank you
Usb debugging is irrelevant. Forget about it, it's only used when the system is booted.
You need to get fastboot devices to recognize the tablet.
Uninstall any and all toolkits and drivers. Redownload the sdk. Boot to the bootloader and plug it in, the drivers should install automatically. If not install the google usb drivers from the sdk manager in the sdk.
Try fastboot devices again. If it doesn't work try a different usb cord/port/computer.
You are in the bootloader when running this command right? Not the recovery? I think with the tablet off it's volume down and power. The screen that says start in big green letters at the top and has device info in the bottom left is what you want.
Edit: Did you boot to recovery and select the options to wipe data and cache? Sometimes thats all thats needed.
Also booting to recovery and performing a factory reset may be sufficient.
ADB will indeed function in recovery. I don't think you have to enable USB debugging to get this to work though.
Are you typing fastboot devices while booted in recovery? Typing fastboot devices while in recovery or booted into Android will do nothing.
hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?
helpmynexus said:
hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?
Click to expand...
Click to collapse
I have the same problem .. Have You reslove it?
bikicviki said:
I have the same problem .. Have You reslove it?
Click to expand...
Click to collapse
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
---------- Post added at 07:12 PM ---------- Previous post was at 06:57 PM ----------
Troops42 said:
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
Click to expand...
Click to collapse
Tried to edit but anyway:
After re..re, rereading your post, and responces. Have you tried the old fashioned way
Hold down the (down volume) button at the same time the (power) key.."Together" If you get anything that pops on your screen let go of the keys, one tap at a time tap the volume up or down key ONLY, until it says (START), its in green type. if you get there you should be ok, to move along
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.
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.
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!
ive been trying to root my new oneplus 9 pro, (came back into the fold from a s21 ultra) and for whatever reason, even though i have usb debugging enabled, whenever i go into fastboot mode, my phone doesnt show up when i type fastboot devices into command prompt, if it shows anything, its usually waiting for any device
Lmns2312 said:
ive been trying to root my new oneplus 9 pro, (came back into the fold from a s21 ultra) and for whatever reason, even though i have usb debugging enabled, whenever i go into fastboot mode, my phone doesnt show up when i type fastboot devices into command prompt, if it shows anything, its usually waiting for any device
Click to expand...
Click to collapse
Just to get the obvious out of the way; you are booting your phone in bootloader mode, right? (when off up+down+power)
Dn_nS said:
Just to get the obvious out of the way; you are booting your phone in bootloader mode, right? (when off up+down+power)
Click to expand...
Click to collapse
not that way, when i press the power button, there is a option to go into bootloader mode
Lmns2312 said:
ive been trying to root my new oneplus 9 pro, (came back into the fold from a s21 ultra) and for whatever reason, even though i have usb debugging enabled, whenever i go into fastboot mode, my phone doesnt show up when i type fastboot devices into command prompt, if it shows anything, its usually waiting for any device
Click to expand...
Click to collapse
Try a different cable - I had this same issue. My laptop doesn't support USB-C to USB-C even though it has the connector and updated motherboard software. Once I used the one from my old OP7Pro, it worked fine.
You need to update your adb/fastboot driver.
luckylui said:
You need to update your adb/fastboot driver.
Click to expand...
Click to collapse
im running the latest version
phr0zen said:
Try a different cable - I had this same issue. My laptop doesn't support USB-C to USB-C even though it has the connector and updated motherboard software. Once I used the one from my old OP7Pro, it worked fine.
Click to expand...
Click to collapse
ive tried a usb c-c connector and a a-c connector
ok, i found the issue, i had to install the android usb drivers