Excuse me for my bad English. I am new on this Forum. Please help me, I have a big problem!
I can’t use Fastboot command, because ewery time I got the „Waiting for devices” error message
1) I have a Motorola Moto G4 phone (XT 1622, athene)
2) This mobile are not rooted.
3) I want to unlock my bootloader, after this I want to install TWRP, and after this I van root my mobile, for install the custom Lineage OS.
4) On my phone I activated at the Developper Otions the USB debugging, and OEM Unlocking.
5) I connected my phone to my PC, I used first time Windows 10. On this system my Moto G4 are identified: Motorola ADB interface. No problem with identification, no any yelow exclamation matrk, no unidentified device!
6) I have installed the correct ADB and Fastboot driver v.1.4.3 (link is made from this site)
7) I have installed the Motorola driver from the official Motorola site.
8) All ADB command work fine, for example adb devices, adb reboot bootloader, etc.
9) But no fastboot command work, when I tested the fastboot devices, I got the „Waiting for devices”. Of corse befor this, I rebooted my phone in fastboot mode! If I use any fastboot command, I got this error message.
10) I try to use the excellent tools (thank you for this): Universal Fastboot & ADB tool, latest version, but the situation in this case is the same, „Waiting for devices”.
11) Of corse I rebooted the PC after instalation of the drivers, the fastboot.exe is in the right paths, etc.
12) I have installed the Universal USB Driver with the Universal Fastboot & ADB tool, Install drivers button, PC rebooted after this.
13) I used Windows 10, Windows XP, and Ubuntu, and in all cases I got the „Waiting for devices”
14) Under Ubuntu I got this message, despite that on Ubuntu the ADB and Fastboot driver installations are cleare.
15) I tested all on many other PC.
16) Every time I connected my phone to the PC only on USB 2.0 port, I changed the USB port, and I changed the USB cable too.
17) I read hundred ot tutorilas on youtube, on differant Forums, but none of them helped.
18) I uninstalled or reinstalled a many timet he ADB and fastboot drivers (I tested a lot of drives from the net), and I installet a many times the official Motorola driver, and the Google universal USB driver, but nothing
Please tell me what can I do for solve this devil situation, Please help me! Thank you again!
There are 2 fastboots, fastboot and mfastboot (i guess this one is motorola fastboot)
Try with mfastboot
mfastboot
GuikBretas said:
There are 2 fastboots, fastboot and mfastboot (i guess this one is motorola fastboot)
Try with mfastboot
Click to expand...
Click to collapse
Where can I find the mfastboot? This is same with the Motorola driver?
Thank you.
Related
Hello everyone, I'm using Redmi Note 3 and I have tried rooting it several times.
I have unlocked the bootloader. I have also installed the adb drivers.
When I connect phone in fastboot mode and write 'fastboot devices' in cmd it doesn't return anything. But when I connect when its on, adb devices returns the device code.
Please help.
Same, happens to mine too. Used to work with a previous install of windows, but now, nope.
Had this issue too.
Try going to Device Manager and check to see if Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Install minimalist ADB and fastboot and right click Android Bootloader Interface. Click Update Driver Software, browse computer, and then click the option to list driver files already present on your drive. It should pull up a fastboot driver that's an older version than the one you currently have. Install that and fastboot will work again.
Doesn't work
Can you please link the files for download when we're updating the driver software.
So my device is recognized when it's turned on but then I go to command prompt and click ADB reboot bootloader (enter). It just says waiting for device. If it's on and I click ADB devices in the command prompt it tells me the serial number and then says device. On the computer management it is recognized as a device it says the name Xperia XA Ultra. I tried to update the Google driver into ADB but that was a failed attempt. I couldn't quite understand what I was supposed to do there or really even follow the instructions because it kept telling me that I was unable to update drivers after I followed the instructions they gave me. I just kept getting an error message. So I'm wondering how do I solve this problem? I really would like to unlock my bootloader and I'm not even sure if it's going into fastboot. I got the notification after turning off the phone hold Volume Plus and plug it in it said of my computer that it was installing the fastboot drivers. I'm assuming it was in fastboot at that time even though I didn't get a blue light it just turned blue for a minute and then it was Green. It said it was installing fastboot drivers so I'm assuming it was in fastboot mode. This is a really tricky process I guess.
What windows do you have?
Also I would recommend you to Google how install fastboot on your Windows type.
Sent from my F3213 using xda premium
I have windows 10
Windows 10. Why would I need to install fastboot on Windows? Fastboot is on my Android device. I use ADB. Android debugging bridge is the bridge that goes between your operating system and fastboot the bootloader and Android and all of that in order to be able to communicate with the phone. Why would I need to install Fastboot on my windows? You sound like a customer service representative. I can't even talk to them anymore because they tried to get me to act like Chris Farley.
If you don't install fastboot on your computer you can't unlock bootloader you can't install custom recovery or root the phone!
Sent from my F3213 using xda premium
Hello,
Here is the link to the ADB Installer that contains all the files you need (ADB, Fastboot and Drivers). Download and following the screen information to install the program.
https://forum.xda-developers.com/showthread.php?t=2588979/
Thanks,
Danjuma
Hi there
please note that Windows 10 x64 blocks the installation of unsigned drivers. To be able to install them anyway you have to enter the Windows Test Mode. To do this you just have to run "bcdedit /set testsigning on" in an administrative command line and restart your computer afterwards. You'll see "Test Mode" at the bottom right corner of your desktop. To leave the testmode use "bcdedit /set testsigning off" and restart again.
Done all of this and it doesn't work...
You have to use drivers from Sony for Flashmode and use drivers included in Flashtool (C:\flashtool\drivers) for fastboot and ADB. No problem for me with Windows 10 64bits and don't need to use Test mode.
I am on an older macbook pro running High Sierra. the phone I'm using is a Blu G5 running android 9. I have the developer options unlocked and oem unlocked and usb debugging checked. When i open my terminal i type cd and drag and drop the platform tools folder into the terminal window changing the directory to the folder containing the adb and fastboot files. I can use adb commands such as adb devices and get the serial number and it says devices. So far so good. Then i reboot the phone into the bootloader manually or using command adb reboot bootloader and the phone goes into fastboot mode. I know because it says it on top of the screen in white letters. Then i run into the problem fastboot commands don't work. If I type in fastboot devices nothing but a new command line shows up. When i type in any other command like fastboot device or fastboot oem unlock it says "waiting for any devices." I wait and wait but nothing happens. I have looked on the internet for a solution but all i find is that the driver may not deinstalled properly. I have tried manually installing fastboot driver and used sdk manager to install the fastboot driver and I have tried it using the terminal in android studio but no matter what when i try useing fastboot commands i get the "waiting for any device" message. Does any have a solution or could anyone recommend and forum for android development on MacOSX?
@DimDreams
Seems the Fastboot driver is invalid.
jwoegerbauer said:
@DimDreams
Seems the Fastboot driver is invalid.
Click to expand...
Click to collapse
I have literally tried like 10 different sdk tool downloads just platform tool download basically every thing i can find. By chance would you or anyone out there have a working driver for MacOSX 10.13.6? or link a guide that can help me figure this out. I have made a little progress with a forum on xda about fastboot on macs but i still just keep getting the waiting for any device message.
@DimDreams
May also be that the Fastboot Android mode is not available on the phone in question.
I've had similar issues before and noticed that fastboot mode works better via USB 2.0 than USB 3.0. Maybe check which port you're using and switch. ADB seems to work well either way, however. Hope that helped.
I just had this problem as well and I found this, what worked for me is first boot your phone into bootloader mode with
Code:
adb reboot bootloader
. While in the bootloader fastboot worked for me. Hope this helps someone!
Once I reboot to bootloader and connect to PC, the command "fastboot devices" does not recognize the device, so when I try to unlock it. it says "waiting for device". I've enabled both OEM unlocking and USB debugging.
The phone shows "fastboot_unlock_verify ok"
"The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously. "
EDIT: Solved it by using the correct platform-tools
I have the same problem. I actually thought that I installed the right sdk platform tools. Can you upload the platform tools that work for you?
Thank you
7tyjupiter said:
I have the same problem. I actually thought that I installed the right sdk platform tools. Can you upload the platform tools that work for you?
Thank you
Click to expand...
Click to collapse
I used the ones from here - https://www.getdroidtips.com/download-adb/#How-to-Install-Android-SDK-and-Platform-Tools
Solved.
I downloaded the platform tools 30.0.5 and reinstall it. Then i reinstall the adb bootloader driver right at the moment when the Nord2 is in the fastboot mode.
cheers
I have no developer options for reboot, bootloader, recovery.
platform tools 30.0.5, where?
Try after reboot into bootloader "fastboot devices". Is the Nord 2 recognized?
For me the correct command was "fastboot flashing unlock".
Hier is the link for the Platform tools 30.0.5
adb - platform tools v30.0.5.zip | by abdyasar for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I'm having the same issue. I can't get my Nord 2 show up with "fastboot devices". Sent my phone into the bootloader with "adb reboot bootloader" no problem.
I have used the 30.0.5 platform tools as well as the 31.0.3. Installed Oneplus USB drivers and also tried the universal r13 android drivers (Reinstalled the bootloader drivers while in bootloader mode). Also tried Snoop05s 1.43 adb installer. All to no avail. Just can't get my device to show up in the bootloader.
In Phone settings bootloader is open and USB debugging is on.
Edit: I made it work. Used regular CMD and not powershell and it showed up.
F4t16u3 said:
I'm having the same issue. I can't get my Nord 2 show up with "fastboot devices". Sent my phone into the bootloader with "adb reboot bootloader" no problem.
I have used the 30.0.5 platform tools as well as the 31.0.3. Installed Oneplus USB drivers and also tried the universal r13 android drivers (Reinstalled the bootloader drivers while in bootloader mode). Also tried Snoop05s 1.43 adb installer. All to no avail. Just can't get my device to show up in the bootloader.
In Phone settings bootloader is open and USB debugging is on.
Edit: I made it work. Used regular CMD and not powershell and it showed up.
Click to expand...
Click to collapse
Mine does not show up.... -.-
Hey all, I just got a G90 Pro that I want to put a ROM on, but something is up with the fastboot. I have the drivers installed according to what I found online, but when I go to fastboot there is no response from the cmd inputs. Nothing even shows up when I check fastboot devices. Has anyone had luck with these phones? I can't even unlock the bootloader!
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
jwoegerbauer said:
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
Click to expand...
Click to collapse
I have done this, but did it again just to be sure, and device manager recognizes the G90 Pro under USB devices, and ADB finds it, but when I do the 'adb reboot bootloader' the fastboot mode text is on the bottom, yet fastboot commands don't do anything, not even 'fastboot devices'.
Edit: Fastboot devices is recognized in fastbootd, but not regular fastboot, yet the other commands don't work.
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
jwoegerbauer said:
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
Click to expand...
Click to collapse
Fastboot reboot fastboot just brings up the fastboot command list. Assuming it's expecting me to try reboot bootloader.
That's really weird because your phone is running Android 10.
My info in settings definitely confirms that. Nothing seems to be working as expected though.
jwoegerbauer said:
That's really weird because your phone is running Android 10.
Click to expand...
Click to collapse
Is there any other possible solution? I still can't get fastboot commands to work after rebooting to fastboot mode from fastbootd.