Edit: got it to work using su and having the fastboot command in my history, adb reboot bootloader, immediately up and use remembered fastboot boot twrp.img

Installed LineageOS Android 13!! Its awesome with Magisk, fixing all the GrapheneOS patches for SUPL and Captive Portal (more security hardening and connectivity check still missing).

I flashed multiple custom ROMs on my phone already, all LineageOS.

I can use adb or get into the Download mode or using the button combo. Here fastboot devices already shows the correct device number, but I still cant flash TWRP.

I switched from Ubuntu based to Fedora, maybe that is a problem regarding drivers? The package is android-tools rather than adb fastboot.

So I enter

fastboot devices

NUMBER fastboot

fastboot boot ~/twrp.img

< waiting for any device >

Edit: very weird. It worked if I immediately entered the boot command after reentering Download mode. Like in the first second. When I entered it after 2 seconds, it started to transfer something but stopped.

Ở bài viết này mình sẽ hướng dẫn anh em chi tiết cách bước kết nối điện thoại Vsmart với máy tính để anh em có thể vọc vạch các tính năng như chạy lênh abd để Fastboot, unbootloader, root, cài rom.bla.bla... dành riênh cho anh em sử dụng điện thoại Vsmart và đặc biệt là anh em nghiệp dư nhé...

I tried and saw few solutions. I'm writing a detailed solution to this. this was how I solved it. if you have more suggestions you can answer below.

asked Jul 23, 2018 at 12:54

the only reason for this is that your PC is not recognizing Phone.which is a driver problem.

You have to understand a few things before starting with the solution. you may know this too.

• when you are in your recovery adb gets into something like recovery mode(just framing some terms myself)
• in bootloader, it takes fastload mode.

each of this mode needs different drivers other than what the driver you use with adb when your phone is running on OS.

so what you have to do is.

if you are trying to get into recovery mode or fastload mode.

• open device manager(settings>devices>(more options)Device manager).
• now boot the phone into the required mode using manual or adb method.
• the device manager reloads and a new driver will be shown. either in Android or pointing device or others folder.
• select the driver and update online.(always preferred).
• if you don't find an online driver you have to select manual update here.
  select browse my computer.
  select let me pick.
  select browse.

at last, you have to select the usb-driver provided by the google. in sdk>extras>google>usb-driver

it will show the updatable driver.select and press next to install. press ok now it should work correctly.

answered Jul 23, 2018 at 12:54

SushanthSushanth

1,3921 gold badge10 silver badges15 bronze badges

4

Happened to MACOS Mojave 10.14.6 while trying to install twrp-3.3.1-2-enchilada.img.

Solved it by running:

adb reboot-bootloader

Then, when the phone boot into bootloader,

fastboot boot twrp-3.3.1-2-enchilada.img

worked like a charm

answered Sep 1, 2019 at 6:24

Asaf PinhassiAsaf Pinhassi

15.3k12 gold badges108 silver badges131 bronze badges

Run following command to get your device into FastBoot mode (from adb-driver folder if using Windows System)

adb reboot-fastboot

answered Nov 16, 2019 at 9:45

Kishan SolankiKishan Solanki

13.9k6 gold badges87 silver badges82 bronze badges

For me it was not turning on usb debugging.

(settings -> developer options(you should activate this if you don't see this option) -> usb debugging.)

answered Oct 5, 2019 at 20:47

yayayaya

7,8831 gold badge41 silver badges38 bronze badges

I've just spent a lot of time with the same problem, and it turns out to be because I have a Samsung phone.

There are a log of Fastboot blogs out there but what they don't always mention is, Samsung devices have no fastboot mode. So if yours is a Samsung device, don't waste time on any of the drivers and settings, because it will not work on Samsung. You can use adb but not fastboot.

There's another post with more info here: https://android.stackexchange.com/a/187573/111755.

answered Dec 1, 2021 at 1:30

Reg EditReg Edit

6,7392 gold badges36 silver badges46 bronze badges

5

For me, I couldn't even see my Android device in Windows 10 Device Manager until I went into Settings/General/Developer options and set Select USB Configuration to MTP (Media Transfer Protocol) instead of the default Charging Only, and also found a different USB cable that wasn't a charging-only one. Then, as @sushanthkille indicated above, I still had to install an updated driver, but the way he describes via Device Manager didn't work. For my LG G4, I had to go to https://www.lg.com/us/lgeai/Drivers/pages/mobile-drivers.html (found via googling for windows 10 LG G4 drivers) download the Windows driver, and install it manually. After all that, my G4 finally showed up in Windows 10.

answered Apr 3, 2019 at 20:37

RealHandyRealHandy

5423 gold badges8 silver badges27 bronze badges

I had to update Windows 10 to resolve this issue.

I believe the needed update was a driver update for Android Bootloader Interface from Google, Inc. Windows updated several things at once so I can't verify that is what specifically solved the problem for me.

answered Dec 30, 2019 at 20:57

JonathanJonathan

671 silver badge8 bronze badges

Easy way

1. download the Google USB Driver from the official website (https://developer.android.com/studio/run/win-usb)
2. Turn off your device and connect with your PC or laptop with a USB plugging

go to the device manager, You will see Other devices. There you will see the Android option. Right-click on it and press on update driver, then click on Brouse my computer for driver S/W. then Let me pick from the list and continue with All devices and next. Then browse again and select the file from the folder you have downloaded and click on install. and restart