I'm trying to test a twrp recovery I ported to my phone, but fastboot isn't working correctly. Adb works fine, adb devices shows my phone. Windows device manager shows adb composite device, all is well. Adb reboot bootloader puts the phone into fastboot as it should. Device manager then shows android boot loader interface. It should be working since it seems like the appropriate drivers are loaded, but fastboot devices gives me a blank line. Fastboot reboot just shows waiting for device and never gets any further. What am I missing?
Jesseb342 said:
I'm trying to test a twrp recovery I ported to my phone, but fastboot isn't working correctly. Adb works fine, adb devices shows my phone. Windows device manager shows adb composite device, all is well. Adb reboot bootloader puts the phone into fastboot as it should. Device manager then shows android boot loader interface. It should be working since it seems like the appropriate drivers are loaded, but fastboot devices gives me a blank line. Fastboot reboot just shows waiting for device and never gets any further. What am I missing?
Click to expand...
Click to collapse
Hello men.
Did you get the fastboot to work?
I'm in the same situation here.
Thanks :fingers-crossed:
Related
adb reboots the phone, adb devices shows devices. fastboot displays help, fastboot devices shows empty list. any ideas?
edit: i copied the fastboot (and everything else) to the handset_usb_device folder from "中兴V790+V788D通用一键ROOT.exe" which is what i rooted the phone with. IT used fastboot (guessing since it was in there) so i'm guessing it works. i wasn't having any luck with the adb from the sdk, device wasn't showing up.
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.
I'm running into issues with my Compact X. Current situation:
- Omni 8.1 rom installed, but doesn't boot. Stuck on Sony logo.
- TRWP 3.3
- Rooted
- When in fastboot mode (vol up + connect usb cable) the device manager shows: Android Device > Sony Fastboot Interface.
- Windows 10 running in "Test mode"
- adb & fastboot v1.4.3
ADB does not recognize my device when the device is in fastboot mode. When it's in recovery mode the command 'adb devices' shows me the device listed. I can then reboot in fastboot mode, but then the device isn't listed anymore. I'm not sure what happened because a couple of hours ago I installed TWRP using fastboot.
I'm trying to get this thing up and running again, but not being able to flash anything via fastboot complicates things. Any idea's what could be the culprit?
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Some random said:
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Click to expand...
Click to collapse
Thank you for your reply. As far as I know the official drivers were already installed. Because at first my device did show up listed when using the command 'adb devices' and I successfully flashed TWRP recovery. But to be sure I repeated the process:
- Connected my phone in fastboot mode (vol up + connect usb cable). The blue led lights up.
- Go to the device manager, right click on 'Android ADB interface' device and manually install the driver via 'Have disk'.
- The driver installs with no errors.
But still my phone is not listed and I cannot flash anything.
When the phone is in recovery mode it is listed using the 'adb devices' command. But when I'm trying to flash something I get the message <waiting for device> .
Ok, I restored my computer to a point before I started messing with my phone. After installing the official drivers my phone is still not listed (adb devices), but this time flashing did work. I managed to flash the AOSP 8.1 image. My phone is up and running again!
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!
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.