Database Develop

Fastboot not working

Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize

Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc. Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Sent from my Xiaomi Mi5 using Tapatalk

SilverMarcs said:
Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc.
Click to expand...
Click to collapse
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
SilverMarcs said:
Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Click to expand...
Click to collapse
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.

FrozenPie1 said:
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.
Click to expand...
Click to collapse
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Sent from my Xiaomi Mi5 using Tapatalk

SilverMarcs said:
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Click to expand...
Click to collapse
It's not working on both Windows 10 Machines i have. I'll try to install Windows 7 on my Laptop (or in a VM) and look if that works when i'm home again
Edit: Well, now i'm totally confused... For some reason fastboot started working again this morning so i was able to flash TWRP again. Anyway thanks for the help

FrozenPie1 said:
Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize
Click to expand...
Click to collapse
I too have the same problem..****

Install MiFlash on your PC and try again, the device will show up correctly on fastbook devices command. It was a USB drivers issue in my case.

Help me please, I don´t have gapps installed...

Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Its possible to fix? or my phone its ****ed, or there is one form to installl the gapps from anoter form?
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
Help me pls:crying:

I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli

Gravemind2015 said:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.

vmmiguel said:
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
Click to expand...
Click to collapse
My windows cmputer says that my device doesnt works properly, i read all night about this and i think when i some point i made wipe /system so i delete the twrp and the rom doesnt have usb adb i think so hahaha, i think now my x4 will stuck on only aosp 9.0 without g services :crying::crying::crying:

id start with a flash all of the latest stock firmware to clean it up. then start over

edufur said:
id start with a flash all of the latest stock firmware to clean it up. then start over
Click to expand...
Click to collapse
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...

vmmiguel said:
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
Click to expand...
Click to collapse
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.

Comby_sk said:
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Click to expand...
Click to collapse
Hello Buddy, i tried that but doesnt work, recently i discover that my usb default mode is gray so i think i cant switch beetwen the usb option, and i tried ADB over network, in terminal emulator to run adbd service but it crash :c
@erfanoabdiadbi plz you cant help me, i really i was enjoying you excelent deveploment, but now in stuck in this without essencial apps like whatsapp, my smartphone works like only phone without been smart jajaja:crying::good:

Anyone?

vmmiguel said:
Anyone?
Click to expand...
Click to collapse
Read through this thread carefully...
https://forum.xda-developers.com/moto-x4/development/rom-lineage-16-0-developer-preview-t3849699

I have more or less the same problem.
I am stuck in LineageOS 15.1 and for some reason Windows does not recognize my phone (it does with other x4 phone from a friend).
I also don't have GApps installed and also don't have root access. Since I can't connect my phone, I can't root or flash some custom recovery.
I really need some help.

No ADB or Fastboot need Help

Hello, folks,
I have a razerphone2 this was rooted for this reason I couldn't install the current update so I reset it but it didn't improve either. I don't have a chance to access the device via ADB/Fastboot and tried it on several computers. Do you have an idea? You can install updates from SD card but the rom from Razer doesn't work. I need help!

Use Razer developers
Phill_ger said:
Hello, folks,
I have a razerphone2 this was rooted for this reason I couldn't install the current update so I reset it but it didn't improve either. I don't have a chance to access the device via ADB/Fastboot and tried it on several computers. Do you have an idea? You can install updates from SD card but the rom from Razer doesn't work. I need help!
Click to expand...
Click to collapse
Hi, The Razer developer page contains instructions for installing ADB Fastboot drivers and recovering the system to its original version.
First need SDK for RP2, ADB Fastboot Drivers.
*Only whit this SDK you can access to bootloader.
I attach the links:
Fastboot drivers -> "https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip" *Reboot in fastboot first to recognize in your system, -> "https://s3.amazonaws.com/cheryl-factory-images/How_to_Install_Android_Fastboot_Drivers_on_Windows.pdf"
SDK -> "https://dl.google.com/android/repository/platform-tools-latest-windows.zip"
Link Razer Developers
"https://developer.razer.com/razer-phone-dev-tools/factory-images/"
"https://developer.razer.com/razer-phone-dev-tools/general-instructions/"

Hi,
ist still not working when iin the Android system i can use adb to boot into Bootloader but at this Point i cant connect to the Phone.

Phill_ger said:
Hi,
ist still not working when iin the Android system i can use adb to boot into Bootloader but at this Point i cant connect to the Phone.
Click to expand...
Click to collapse
You should first install drivers for windows like in the page you were linked to above.

Fastboot error Android Q

Hi guyz i wanted to root my phone for enabling camera2api. İ did it on Android 9 and worked perfectly. But i disabled it for updating to Android 10. Now im trying to boot patched boot for installing magisk. Everything is okay untill i type adb reboot bootloader for entering fastboot mode and boot img file. When it enters to fastboot mode i type fastboot devices for checking phone but nothing happening and when i type fastboot boot patched_boot.img it says waiting for device and nothing happening. Also when it restarts, usb debugging automatically turning off. İm turning it on checking phone with abd everything is okay but when it restarts from fastboot usb debugging turns off. Any help? İdk if its bug or im doing something wrong

Maharram said:
Hi guyz i wanted to root my phone for enabling camera2api. İ did it on Android 9 and worked perfectly. But i disabled it for updating to Android 10. Now im trying to boot patched boot for installing magisk. Everything is okay untill i type adb reboot bootloader for entering fastboot mode and boot img file. When it enters to fastboot mode i type fastboot devices for checking phone but nothing happening and when i type fastboot boot patched_boot.img it says waiting for device and nothing happening. Also when it restarts, usb debugging automatically turning off. İm turning it on checking phone with abd everything is okay but when it restarts from fastboot usb debugging turns off. Any help? İdk if its bug or im doing something wrong
Click to expand...
Click to collapse
AFAIK, your first point of reference is the fastboot issue. As long as device isn't recognized in fastboot mode, you won't be able to proceed. Drivers ? USB debugging on and authorized with the PC ? Command prompt being used with elevated rights ?
Regarding Cam2Api, I used a Magisk Module since I use Magisk.

Tianhe said:
AFAIK, your first point of reference is the fastboot issue. As long as device isn't recognized in fastboot mode, you won't be able to proceed. Drivers ? USB debugging on and authorized with the PC ? Command prompt being used with elevated rights ?
Regarding Cam2Api, I used a Magisk Module since I use Magisk.
Click to expand...
Click to collapse
Yep i used magisk module too. Yeah usb debugging on and authorized with pc but not recognized on fastboot mode ( adb mode works )

Maharram said:
Yep i used magisk module too. Yeah usb debugging on and authorized with pc but not recognized on fastboot mode ( adb mode works )
Click to expand...
Click to collapse
I know this might sound silly but are you using the latest platform tools version ?

Tianhe said:
I know this might sound silly but are you using the latest platform tools version ?
Click to expand...
Click to collapse
Yeah. Everytime i used 1.4.3 but this time specially downloaded latest version of adb and platform tools (from What is Adb post on xda)

Maharram said:
Yeah. Everytime i used 1.4.3 but this time specially downloaded latest version of adb and platform tools (from What is Adb post on xda)
Click to expand...
Click to collapse
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7. Also try downloading the Platform Tools from developer.android.com (adb is already available in the folder)

Tianhe said:
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7
Click to expand...
Click to collapse
Yeah im using win 10 redstone (latest version)
But also i did it on win 10 with Android 9

Tianhe said:
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7. Also try downloading the Platform Tools from developer.android.com (adb is already available in the folder)
Click to expand...
Click to collapse
Going to try this. Thanks a lot <3

Maharram said:
Going to try this. Thanks a lot <3
Click to expand...
Click to collapse
Hope you get the desired result. I am also on Win 10 latest update and I had faced issues initially. I have also added a registry hack so that everytime I open CMD with shift+right click it opens with administrator privileges.

Question Stuck in bootloader by attempt to install lineage os. How ****ed am I?

Hey, dear community,
First of all: I'm using Linux. The Version of Fastboot is 33.0.3p1-android-tools. The device I thought I'm experienced enough to install Lineage OS on is the Asus Zenfone 8. Yes, I asked google - for hours. And I think I am really ****ed now.
Cause the Smartphone (Asus Zenfone 8) was not cheap. And it does not boot anymore. I don't get in Recovery mode anymore. And I'm not able to connect via Fastboot anymore.
But let's start at the beginning.
I was pissed, cause my smartphone forced me to use google. Even if I skipped the Google-Part in the setup, it forced me to agree to send Google information. And I read it. They (quote: may) send Google **a lot** of data. Data I don't want to share - and I don't need to share IMHO! I didn't like to use such a intransparent Device anyway - but this convinced me to try this thing named LineageOS.
I thought about myself I am not a bloody beginner. I mean, I use Linux as my daily driver - for years. And my phone (Asus Zenfone 8) was in the list of supported devices - so I had to try it. I thought if I just install these tools, adb and fastboot, and do these things in the wiki carefully, step by step, what could happen?
And it worked. It worked to unlock device, to connect via adb, to connect via fastboot. It worked to flash the vendor_boot image, It worked to flash the recovery image. But then, just before I wanted to start with the "Installing LineageOS"-part, and therefore boot into recovery mode - it didn't work. I was stuck in the bootloader. I am. still.
There are the options "START", "Restart bootloader", "Recovery mode" and "Power off". No matter what I try to enter, the device restarts (at least it looks like) - It shows "Powered by android", and then the bootmenu again. And again. And again.
When fastboot was still connected, I tried to flash the images again. I even tried to boot directly into the recovery image using `fastboot boot image.img`. But it did not work. And then, the device even stopped showing up when I ran `fastboot devices` - it disconnected.
"Power off" is the only option, wich still appears to work (when not plugged in).
What should I do? Is it even still possible to do something? Please help me.
PS: It would be nice if you tell me, wether the tools or guides you recommend to me work on Linux, in a Windows VM or only Windows Bare Metal. I will do everything to bring my phone back, but it safes a lot of time, not to try using a tool in Windows VM if it only works bare metal anyway.

May be this thread could help you
https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/

Thanks, but my phone does not get into fastboot mode anymore, therefore I cannot connect to my phone via fastboot to flash new images.

Schaukelstuhl said:
Thanks, but my phone does not get into fastboot mode anymore, therefore I cannot connect to my phone via fastboot to flash new images.
Click to expand...
Click to collapse
I had the same problem. Only bootloader with no device showing with "fastboot devices".
Luckily I tried another cable. An Apple USB C cable behind a hub (screen) got fastboot working. Then I flashed android 13 beta.
And I am sure the other cable worked before with ADB and fastboot.
Try other cables and USB ports... Good luck!