I'm stuck at the "fastboot oem unlock" passage, because is waiting for the device without end. If i send fastboot devices command, nothing shows up but with adb devices i can correctly see the phone
solved, adb driver missing
I encountered this too. Driver wasn't missing (in fact, it worked fine with my OnePlus 7 Pro just a few days earlier), but it wasn't the latest version.
Related
I have waited for 14 days and finally the day arrived today. I installed minimal adb and fastboot in my computer. The computer is able to recognize the device when connected without powering of in minimal adb(i checked by using adb devices). But when i booted to bootloader from oem unlock option in developer setting and typed the command fastboot oem unlock it shows waiting for any device. I tried the adb devices command while in bootloader and its not able to recognize the device.
Anyone please help me out.
Check if it's connected by typing 'fastboot devices'. Connect to it in fastboot mode by long-pressing volume down and power buttons.
Fixed the issue by reinstalling Lenovo drivers.
Nabeelp2 said:
Fixed the issue by reinstalling Lenovo drivers.
Click to expand...
Click to collapse
That's great
Install Lenovo drivers.
Hit thanks if I have helped
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.
I have searched the net high and low for a answer to this question but nothing I have tried works.
I have used every adb and fastboot installer i could find, but nothing i do get fastboot working on my 5t. ADB is recognised and i can reboot to the bootloader from a command shell. But as soon as i type "fastboot devices" it shows nothing.
I have been into device manager and it shows issues with the fastboot driver, i have tried everything i can think of to fix this issue.
I would really love to root my 5t and and have never encountered this many issues on any of my previous devices.
Running a 64gb OP5T and Windows 10
Thank you for your help
I have now re-installed windows 10, re-installed all drivers and ADB and fastboot. ADB is still working but nothing from fastboot. It's recognised properly in device manager but nothing shows up when I type fastboot devices or fastboot OEM unlock. Any tips would be great.
http://www.codeshuffle.in/2016/12/kenzo-fastboot-adb-connection-fix.html
check this link specially driver signature enforcement disable part, it may help
When you say "nothing shows up", what exactly is the response?
How are you getting into the bootloader? Use this from recovery or system:
Code:
adb reboot bootloader
Then proceed.
ADB is working fine. But as soon as I reboot to fastboot mode the phone doesn't respond. I can't work it out have tried everything.
djmcnz said:
When you say "nothing shows up", what exactly is the response?
Click to expand...
Click to collapse
^^
It just says waiting for device or says nothing and brings up a new line. I'm guessing the fastboot driver is the problem. I have installed the Oneplus drives included with the phone. I've installed the universal ones, still nothing.
Is there an individual fastboot driver I could manually install through device manager?
Appreciate the help.
The issue is finally fixed! I went into device manager and changed the driver from a list of drivers on my pc to WINUSB and now its working
Same problem here pal, how did you change driver to winusb, seems I've got all the gear just no idea... By gear I mean files/drivers lol. Rooted so many devices I thought this would be easy, looking forward to getting it sorted. I love a custom rom
Hello,
I've been trying for the past several hours to unlock the bootloader of my Moto Z2 Play (model:XT1710-09) by following different tuturials but fastboot don't seem to detect my phone, no matter what i do.
Nothing happens when i type “fastboot devices” in the command window.
I've noticed that my phone appear in the device manager in "other devices" as "Fastboot albus S" when it is in bootloader mode, which doesn't seems normal.
Edit: Some additional info: -i am on windows 10 pro
-ADB detect the phone whit no problem but Fastboot doesn't
-when connected with usb debugging enabled, windows detect it as "ADB interface" (which seems normal) and use "C:\\WINDOWS\system32\DRIVERS\winusb.sys" as driver (which seems less normal to me, i may be wrong)
-i tried installing Motorola specific drivers but i only found MotorolaDeviceManager, which doesn't seem to do anything, and no way to download the drivers manually
Edit 2: I still don't know why i can't get it to work on windows but i just managed to do it using a linux bootable usb, my device is unlocked \o/
If anyone know why fastboot doesn't wok on my windows and how to get it to work, i'm still interested
I have a brand new Moto G7 Play XT1952-4 (old stock, new in box) that I bought specifically to flash LineageOS. I have done this process with two previous Motorola phones over the years, but I seem to be the only person on the Internet with this particular problem: When I restart the phone into bootloader/fastboot mode, any fastboot commands that I send over to the phone hang the process. So this works:
>fastboot devices
XXXXXXXNVN Motorola Fastboot Interface
But this or any other fastboot command that communicates with the phone does not work:
>fastboot getvar all
<process hangs, ctrl-c will not interrupt it>
Sometimes while this command is hung, the simple interface on the phone locks up and the volume up/down and power keys are not responsive. If I unplug the USB cable, the fastboot command will fail and return and the phone is responsive as normal. What is strange is that fastboot worked initially.
When I first powered up the phone without Internet access, I enabled Developer mode and ADB debugging, and fastboot worked: I was able to run 'fastboot oem get_unlock_data' and I used that to retrieve my unlock code from Motorola. When I ran 'fastboot oem unlock XYZ' the phone told me to enable OEM unlocking. I rebooted the phone to find this option was disabled, so eventually I connected my phone to Wifi and the option was enabled. However, the phone began applying updates, so I waited until the updates were applied and resumed my operation. This is when the trouble started.
From that point on, fastboot has failed to work: no error messages, it just hangs. I have tried two laptops, two USB cables, two versions of fastboot (the Ubuntu 20.04 stock version and the 'latest' 30.0.4-6686687 from Google). I have factory reset the phone from Settings, factory reset from Recovery, and I let it go ahead and update to Android Q and repeated all of these things.
The only thing I am left with is this is some kind of hardware error with the USB port on the phone. If so, I wonder if I can make a warranty claim on 'fastboot commands do not work'? I am able to 'adb shell/push' fine, and the phone charges fine.
Any ideas?
I had the same problem i reinstalled adb and fastbood but that not worked than i reinstalled my entire system and installed fastboot + adb and it worked
The the command on a other pc out.
Exinu said:
I have a brand new Moto G7 Play XT1952-4 (old stock, new in box) that I bought specifically to flash LineageOS. I have done this process with two previous Motorola phones over the years, but I seem to be the only person on the Internet with this particular problem: When I restart the phone into bootloader/fastboot mode, any fastboot commands that I send over to the phone hang the process. So this works:
>fastboot devices
XXXXXXXNVN Motorola Fastboot Interface
But this or any other fastboot command that communicates with the phone does not work:
>fastboot getvar all
<process hangs, ctrl-c will not interrupt it>
Sometimes while this command is hung, the simple interface on the phone locks up and the volume up/down and power keys are not responsive. If I unplug the USB cable, the fastboot command will fail and return and the phone is responsive as normal. What is strange is that fastboot worked initially.
When I first powered up the phone without Internet access, I enabled Developer mode and ADB debugging, and fastboot worked: I was able to run 'fastboot oem get_unlock_data' and I used that to retrieve my unlock code from Motorola. When I ran 'fastboot oem unlock XYZ' the phone told me to enable OEM unlocking. I rebooted the phone to find this option was disabled, so eventually I connected my phone to Wifi and the option was enabled. However, the phone began applying updates, so I waited until the updates were applied and resumed my operation. This is when the trouble started.
From that point on, fastboot has failed to work: no error messages, it just hangs. I have tried two laptops, two USB cables, two versions of fastboot (the Ubuntu 20.04 stock version and the 'latest' 30.0.4-6686687 from Google). I have factory reset the phone from Settings, factory reset from Recovery, and I let it go ahead and update to Android Q and repeated all of these things.
The only thing I am left with is this is some kind of hardware error with the USB port on the phone. If so, I wonder if I can make a warranty claim on 'fastboot commands do not work'? I am able to 'adb shell/push' fine, and the phone charges fine.
Any ideas?
Click to expand...
Click to collapse
I think if it was a hardware issue, 'fastboot devices' would not display you ESN, thus indicating fastboot is ready. But I have to agree that this is quite unusual behavior for fastboot mode to hang up like you described. It could certainly be a corrupt bootloader partition (/aboot ??). You should try using the Lenovo-Moto Smart Assistant utility to do a full rescue of the firmware. Treat the phone just as you would if it was unstable or failing to boot. The LMSA utility actually utilizes fastboot mode to do the firmware rescue. So if you could get this to work it could possibly solve the problem. Here is a link to the 32- & 64-bit Windows versions of LMSA. I know you mentioned using Ubuntu, but I'm not sure if the utility is available for Linux. https://support.lenovo.com/us/en/downloads/ds101291
Viva La Android said:
I think if it was a hardware issue, 'fastboot devices' would not display you ESN, thus indicating fastboot is ready. But I have to agree that this is quite unusual behavior for fastboot mode to hang up like you described. It could certainly be a corrupt bootloader partition (/aboot ??). You should try using the Lenovo-Moto Smart Assistant utility to do a full rescue of the firmware. Treat the phone just as you would if it was unstable or failing to boot. The LMSA utility actually utilizes fastboot mode to do the firmware rescue. So if you could get this to work it could possibly solve the problem. Here is a link to the 32- & 64-bit Windows versions of LMSA. I know you mentioned using Ubuntu, but I'm not sure if the utility is available for Linux. https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
We have a Macbook and I downloaded the "Command-line tools only" kit for MacOS from https://developer.android.com/studio/, and it worked! Strange that it didn't work on two different Linux machines with essentially the same software. Of course, there could be some other problem that I'll run into later, and I'll use the LMSA utility if so. Thanks for the ideas.
Exinu said:
We have a Macbook and I downloaded the "Command-line tools only" kit for MacOS from https://developer.android.com/studio/, and it worked! Strange that it didn't work on two different Linux machines with essentially the same software. Of course, there could be some other problem that I'll run into later, and I'll use the LMSA utility if so. Thanks for the ideas.
Click to expand...
Click to collapse
:good:
Adding this here as I ran into the same issue and was able to work around it.
Performing fastboot "oem'"commands from my Linux Mint machine (Ubuntu based) was failing.
I discovered that if I ran the commands from just any directory, the command would hang (and not even a ^C would break the command!). This action referenced the file '/usr/bin/fastboot'. (This file from the 'fastboot' package.)
$ fastboot oem get_unlock_data
<hangs>
HOWEVER, if I referenced the version of 'fastboot' stored in the Android SDK directory '/usr/lib/android-sdk/platform-tools', the command worked as normal.
$ /usr/lib/android-sdk/platform-tools/fastboot oem get_unlock_data
...
(bootloader) Unlock data:
<snip>
What's strange:
- Both files (/usr/bin/fastboot & /usr/lib/android-sdk/platform-tools/fastboot) are both from the 'fastboot' package
- Both files are identical.
Why one would work and the other wouldn't is a mystery for another day.