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
Related
I'm trying to unlock the bootloader on my daughter's G4, and I have run into a heavy snag. I get "code 10" (driver can not start) when it's in fastboot mode, but I'm fully able to connect with adb when the phone's up and running. This is not my first rodeo, and I'm sure the USB cable works (original cable), I have enabled USB Debugging (or ADB wouldn't work in the first place) and I think I have done everything else that should be done. But the damn thing won't work on any of my computers, under Windows 7 or 10. Driving me nuts! Also when it's booted up I see it as an LG Mobile ADB interface, but when it's on Fastboot it insists that it is an MTP device, even if I have set it as a PTP device when it's booted up. Can anybody please tell me what I have to do to get this to work? Another thing is that if I run "adb reboot-bootloader" (or even the wrong syntax (at least I think the dash should be there) "adb reboot bootloader", which LG's page says), it will not boot into fastboot/bootloader, it reboots into Android. So I have to get into the setup by holding in vol + and plugging in the USB cable. But I don't know if this is related.
Edit: Oh, btw, I have tried to find the latest drivers, so far I'm on 4.0.0.0. They are dated May 2015.
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Put in fastboot mode, connect to computer and manually select fastboot interface from the device manager "install device/update driver manually" box. That worked for me.
JusTeN_ said:
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Click to expand...
Click to collapse
Its fine just search for fastboot devices and see if your device comes up. Mine was showing the same thing and i continued and it worked
Hi.
Got a problem here I can't solve on my own.
QFIL-flashed a stock rom (tried to fix the blue screen on boot-thing) and was thinking it should be a breeze to unlock the bootloader and so on. But nope.
I have:
* Adb and fastboot installed
* The ZUK USB-drivers (yes, have turned off the option for windows to require signed drivers)
* Tried different USB-ports. Even another computer
* Other drivers, such as the "mi flash" drivers, universal ADB-drivers, naked ADB-drivers...
I have enabled USB-debugging, and when I write adb devices (when the phone is in android), the device is shown.
Then I use the "adb reboot bootloader" fo get into fastboot. The phone says fastboot_mode, but when I try to find the device via "fastboot devices", it's not shown.
In windows device manager the driver is OK, and shown as "ShenQI Composite ADB Interface".
Any clue what's wrong?
Well, I used the "tool all in one", and now it works....from that program. But still no devices in fastboot devices when I check manually....
Alright, this is weird. I hope I don't have a faulty unit.
Basically, fastboot mode is not being detected AT ALL from my computer. Not even sound notification from Windows that something is being connected.
The problem is not the cable or either the drivers, both an Xperia xz1 compact and a Moto x4 are detected normally in fastboot mode (although with Xperia I had to update drivers, since it was just "android device" in device manager...but even the Xperia at least gave me the pop up sound in Windows).
I tried everything in Developer Options (although Moto x4 didn't even need to have debugging on for fastboot mode to work, incredible...).
I don't know what to do, I never seen something like that.
Model is XT1789-04, brand new but apparently already came with unlocked bootloader from eBay (see screenshots)
Beeing able to use fastboot is essential for start modding...
P.S adb in recovery mode works...
Well, I just solved to mistery.
I tried to use a type c - type c cable (never used it before in my life for any Moto or android in general lol) and voila...weird.
But the problem is, no essential fastboot command works. Only the "fastboot devices" works (it shows the Device).
Even something basic as oem device-info gives me error or command error...
Do I have a faulty unit?
Double post, sorry
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.