UPDATE: Got it working on a windows 7 machine.
I've been trying to unlock my bootloader but have been having issues. I have done the following:
- Enabled Developer Options
- Enabled USB Debugging
- Enabled the OEM Unlock in the Developer Options
- Installed drivers via android SDK
I have adb and fastboot installed from the android SDK. Using that, I have been able to see my device with 'adb devices'. I have also been able to reboot it using 'adb reboot bootloader'. However, once the phone is in fastboot, it does not seem to be detected by my machine. I have tried 'fastboot devices' to no avail. Using 'fastboot oem unlock' just stalls at '< waiting for device >'. Am I missing something?
I have also tried:
- Using a different computer
- Using different USB ports
- Using different ADB / fastboot package (the minimal one).
Please assist! I'd really like to unlock my bootloader now for future flexibility.
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.
yourbuddypal said:
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.
Click to expand...
Click to collapse
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"
amitte said:
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"
Click to expand...
Click to collapse
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working
yourbuddypal said:
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working
Click to expand...
Click to collapse
Yes this is normal. For the bootloader part, do not let windows search automaticly. Do as i described earlier exept use the driver i uploaded for you or search any other nexus usb driver install guide since the process did not change
Same applies to the installation when you are in the system already. Exept do not override any driver that is under portable devices since its the file transfer protocoll driver.
I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!
yourbuddypal said:
I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!
Click to expand...
Click to collapse
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solution on Linux
I had a similar problem earlier today on one of my linux boxes. Turns out, in order to use fastboot (successfully) under linux, you need to run fastboot with sudo rights.
If I had to guess, I'd guess this is because unlike adb, fastboot doesn't run as a server, so fastboot always needs to get elevated permissions to communicate with a device on a USB port.
Maybe it's possible that Windows wants Administrator rights for similar reasons?
duckxtales said:
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
Click to expand...
Click to collapse
Sorry, I really don't have any more feedback to give you. It really did seem like voodoo when it worked. The only thing I can think to explain the "random" aspect is that perhaps it is related to the quality of cable used. I was using these (http://www.amazon.com/Orzly-Type-Cables-Assorted-Colours/dp/B013RMG5WY/ref=cm_rdp_product), which have now been taken down due to cable standards as described in the comments section for that product. I was thinking that maybe the different USB port on the desktop machine was somehow able to get sufficient voltage or something. Voodoo!
I am having the exact same issue with my 6P right now. However it shows when I do adb devices, just not fastboot devices. Weird...
I even uninstalled the Google USB driver and reinstalled it using Android Studio but Still did not work. Then I even went to Device Manager and uninstalled and deleted the driver. Then went manually to file path C:\Users\MyWindowsLoginName\AppData\Local\Android\sdk\extras\google\usb_driver and clicked next. It installed successfully, but displays as Android Composite ADB Interface. So I guess that is correct then?
Tried to just sideload the new 6.0.1 OTA update using adb since adb devices was recongizing it but still not found...
C:\Users\Matthew\AppData\Local\Android\sdk\platform-tools>adb sideload angler-MMB29M-from-MDB08L.zip
loading: 'angler-MMB29M-from-MDB08L.zip'
error: device '(null)' not found
EDIT: I got it after unplugging my phone, killing the adb.exe process in task manager, waiting until in bootloader before plugging phone in, then running fastboot devices shows the serial number now. I hope that helps others!
I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?
I had the same trouble on my 64 bit Windows system. I believe it was HTC sync software that threw the monkey wrench. But I uninstalled that software together with all the adb fastboot drivers for my other devices, removed all adb fastboot versions, then installed the 64 bit version of the Minimal adb fastboot tool.
All good now
Garvinr said:
I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?
Click to expand...
Click to collapse
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Thank you.
I follow this step. now I can use fastboot.
crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
Thanks man! Worked immediately after updating the drivers!
I too had this issue.
Manually installed drivers using this guide.
(pretty much the same instructions as wangxiangg, but with pics)
wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Man. That was it. Worked like a charm. Thank you.
To clarify, you do this while you are in Fastboot Mode and you right-click on "Android" in step 1.
You can go through the steps while you are in Fastboot Mode and with the cable still plugged in.
amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Someone give this man a cookie!
it worked!!!!!!!!
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
Tried on windows 10 and 7:
Phone is detected by ADB and commands work no problem. Boot in to fastboot (download mode) and the device isn't found when using "fastboot devices". The phone appeared in device manager with the yellow triangle but I manually updated the driver to "Android Bootloader Interface" however, I still get nothing. Am I missing something?
Thank you.
Mine never has shown in fastboot, if it shows up in device manager it should work fine. To test just try fastboot reboot.
If you corrected the issue with the driver,the problem may be with the versions of Fastboot you are using. You can download the latest Fastboot and ADB files from Google directly if you search for them it should be the first or second link.
You need google usb drivers
I have the latest google usb and platform tools on a windows 7 &10 systems using different usb ports along with multiple cables and I can not detect the phone, but I can flash.
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 wanted to root my razer phone 2 because I rooted my old Samsung, but after unlocking my bootloader I decided against it and now ive spent about 2 days trying to lock my bootloader again with no luck.
ive tried many different usb drivers and non of them show my device under the "fastboot devices" command in adb or fastboot but I can show the device under adb devices which im aware is rather easy
ive seen many people have this issue but they don't really show/tell how its fixed! ive tried different usb sockets too!
the device name in my device manager is "SAMSUNG Android Phone" (while the phone is in fastboot mode) with the sub driver called "Android Bootloader Interface" if anyone has any kind of advice or tips to get my bootloader locked again please share!
okay, so after a lot of looking around.. I found this.
"1) - To unlock the razer phone bootloader do the following
2) - Install ADB + Fastboot and google usb drivers
3) - Enable developer mode by going to settings, about phone and hitting build number a bunch of times. then go back to settings > developer options and check USB Debugging and OEM Unlock.
4) - Open a command prompt on your PC and connect the phone's usb cable to your computer. Accept the prompt on the phone for trusting the computer when plugged in.
5) - type the following in command prompt without quotes "adb reboot bootloader"
6) - You'll be at the download mode screen with the razer logo.
7) - Make sure the driver for ADB Bootloader Interface was installed. If not you'll probably have a device called Android under "Other devices" in device manager. If this is the case, install the google usb driver.
8) - In command prompt type the following without the quotes "fastboot -i 0x1532 devices" and make sure your device comes up and not just a blank response.
9) - If it came up now just type without the quotes "fastboot -i 0x1532 flashing unlock"
10) - This will bring up a prompt on the phone itself to unlock the bootloader, use the volume button to navigate to yes and press the power button to confirm.
11) - The phone will reboot and will show a message stating "Your device is unlocked and cannot be trusted" on each boot to show that it is unlocked."
FIX - it was the "fastboot -i 0x1532 devices" I was doing wrong.. I was not putting the "-I 0x1532" i now feel stupid.. but idc i locked my phone and im back to stock finally! (ill probably end up trying to root it again some point in the future :| )