Hi.
Trying to flash a ROM to a Nexus 5X.
I have enabled OEM unlocking and USB debugging.
When I enter the command 'fastboot flashing unlock', I get '< waiting for device >' and it just stays there for ever and ever and ever.
I think this is happening because the computer isn't detecting the phone in bootloader mode. When the phone is on, in the normal Android state, my computer lists it when I type 'adb devices'. But when I put the phone in bootloader mode and type 'adb devices', nothing comes up.
Do I need to install different drivers?
Thanks.
Hiltil said:
Hi.
Trying to flash a ROM to a Nexus 5X.
I have enabled OEM unlocking and USB debugging.
When I enter the command 'fastboot flashing unlock', I get '< waiting for device >' and it just stays there for ever and ever and ever.
I think this is happening because the computer isn't detecting the phone in bootloader mode. When the phone is on, in the normal Android state, my computer lists it when I type 'adb devices'. But when I put the phone in bootloader mode and type 'adb devices', nothing comes up.
Do I need to install different drivers?
Thanks.
Click to expand...
Click to collapse
Replying to my own thread to say I figured it out
Although 'adb devices' didn't show the phone, 'fastboot devices' did
The problem wasn't that the computer wasn't seeing the phone; it was that I'd been using the wrong command. 'fastboot flashing unlock' didn't work, but 'fastboot oem unlock' did
You must reinstall fastboot drivers on computer.
Hey,
trying to flash the preview. Enabled adb in dev. settings and when the watch is normally powered on i see my watch in adb devices. However, after typing adb reboot bootloader and being in fastboot mode, it doesnt find my device.
Short said: PC recognizes watch on adb, but not on fastboot in fastboot mode, have tried many adb versions etc. but didnt help.
It also says in device-manager "Android", with a yellow triangle when being in bootloader/fastboot mode.
Cables are ok!!
Thanks for any help!
You need drivers to be installed.
Mike
Michael1200 said:
Hey,
trying to flash the preview. Enabled adb in dev. settings and when the watch is normally powered on i see my watch in adb devices. However, after typing adb reboot bootloader and being in fastboot mode, it doesnt find my device.
Short said: PC recognizes watch on adb, but not on fastboot in fastboot mode, have tried many adb versions etc. but didnt help.
It also says in device-manager "Android", with a yellow triangle when being in bootloader/fastboot mode.
Cables are ok!!
Thanks for any help!
Click to expand...
Click to collapse
If you just type "flash-all.bat" (no quotes) and hit Enter it should still work. It does for me.
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 have a mi a2 lite and i want to unlock its bootloader, i have alrready enabled oem unlocking on developer options, when i boot my device in fastboot and connect to computer, command window says waiting for device and after 15-20 seconds of connecting my device to my pc, fastboot mode automatically exits and shows charging animation. Please anyone can help?
My device is in andoid pie (stable).
Check if you have installed drivers and run "fastboot devices" to see if device is recognised.
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
hossman said:
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
Click to expand...
Click to collapse
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
I've tried restarting my pc as well as my phone and after 5-6 attempts it is now unlocked.
Thanks guys for supporting and giving response to my post
Love ya'll
CherryFarmer8 said:
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
Click to expand...
Click to collapse
same problem boss, did you already solved this? please help me out
Andrew.kathy said:
same problem boss, did you already solved this? please help me out
Click to expand...
Click to collapse
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
capajga said:
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
Click to expand...
Click to collapse
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
CherryFarmer8 said:
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
Click to expand...
Click to collapse
I also have this problem drivers are installed and fine but when I go to fastboot within like 15 sec it automatically turns off.
I fixed it with this https://forum.xda-developers.com/attachments/howto_driver-zip.2480396/
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 :| )