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.

Bootloop + Twrp not installing properly

Hi everyone I need some serious help. I unlocked my bootloader just fine then booted into TWRP using the command
Code:
fastboot boot twrp-3.3.1-0-jasmine_sprout.img
after that used the ADB sideload button in TWRP. I used this command
Code:
adb sideload twrp-installer-3.3.1-0-jasmine_sprout.zip
which didn't work and then I eventually advanced wiped my device. The reason it didn't work ios because my xiaomi mi a2 isn't recognized as a ADB device, it only get recognized as a fastboot device. It is now stuck in a boot loop and can only boot into recovery. Any help would be appreciated.

Mactroiy said:
Hi everyone I need some serious help. I unlocked my bootloader just fine then booted into TWRP using the command
Code:
fastboot boot twrp-3.3.1-0-jasmine_sprout.img
after that used the ADB sideload button in TWRP. I used this command
Code:
adb sideload twrp-installer-3.3.1-0-jasmine_sprout.zip
which didn't work and then I eventually advanced wiped my device. The reason it didn't work ios because my xiaomi mi a2 isn't recognized as a ADB device, it only get recognized as a fastboot device. It is now stuck in a boot loop and can only boot into recovery. Any help would be appreciated.
Click to expand...
Click to collapse
Hello Mac,
Are you running the commands from the adb directory? Example, adb devices which typically would show your xiaomi mi a2 device.
Is the Android USB driver showing as adb in device manager?
I have the very same device, it is a little tricky since it has an a and b partition and you have to be precise when installing a custom ROM. Here's a how to that may be of help to you, it definitely helped me a lot.
Good luck!
[ADB | FASTBOOT | LINUX COMMANDS] BootLoader, Kernel, Recovery, ROM, Root, Backup

Mactroiy said:
.... then I eventually advanced wiped my device...
Click to expand...
Click to collapse
What did you wipe? If anything except Dalvik Cache and/or Cache, then most probably you'll have to reflash stock ROM in fastboot.
Mactroiy said:
The reason it didn't work is because my xiaomi mi a2 isn't recognized as a ADB device, it only get recognized as a fastboot device. It is now stuck in a boot loop and can only boot into recovery. Any help would be appreciated.
Click to expand...
Click to collapse
If "Android Portable Device" drivers are installed correctly (and PC has USB2.0 slot and/or USB 3.x slot compatible with MiA2, which happens not so often), still ADB (if I am not mistaken) sees connected phone if it is
1) booted normally, USB Debugging is On, MTP is On, and ADB with this PC have been validated in phone (and still ADB has limited functionality depending on kernel), or
2) booted into TWRP
You can check ADB connection using "adb devices -l",
- if command shows nothing, then either drivers not installed or USB port is failing or nothing compatible booted in phone,
- if command shows unauthorized transport id, then you have not approved ADB in phone
If phone is in fastboot mode, then, with drivers installed and USB port being compatible, "fastboot devices" shhould show attached phone, and if it is fully unlocked, stock fastboot ROM can be reflashed

Xiaomi MI A2, is stuck in bootloop

Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.

Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.

try the "fastboot continue" command

dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not

How to solve custom recovery not installed after flash on all smartphones[Tutorial]

Hello . A few minutes ago, I had a problem with the TWRP flashing on my huawei p8 gra-ul00 phone .the adb has command's the twrp is complety flashed on my phone , but it did not come up on my phone(after pressing vol+ and power button's the phone will automatiocally go to huawei erecovery). But I took a little initiative and came up with a solution to this problem. I'm share this.
NOTICE : IF YOU HAVEN'T A USB DATA CABLE , PLEASE BUY IT , OTHERWISE CONTINUING THE STEPS WILL NOT SOLVE YOUR PROBLEM .
Before completing all the steps, connect the phone to the computer using data usb cable, then try to enter the recovery mode (for Huawei phones, hold the power button simultaneously with the volume down button for at least one minute.) If the phone Entered custom recovery, no need to do other steps.
1_First Of All , Unlock the bootloader , then reboot the phone
2_Download the custom recovery . IF YOU HAVE ISN'T A CUSTOM RECOVERY FOR YOUR PHONE , PLEASE SEND A COMMENT AND ENTER YOU PHONE MODEL AND A NAME OF THE CUSTOM RECOVERY YOU WANT TO USE TO IT. IM WILL SEND A REGUESTED CUSTOM RECOVERY FOR YOU IN LESS THAN A HOUR .
3_connect the phone to computer and Enable USB Debugging from Developer Options(go to settings>about phone , then 7 times tap on build number , then go back to settings and select developer options , search for "USB Debugging" Option and enable it.)
4_, install the adb and fastboot drivers(such as minimal adb and fastboot) then install the phone drivers . after installing drivers , reboot the computer , then open cmd and enter the command : adb reboot recovery
5_if a window showed on phone(such as allow usb debugging) , click on yes and retry the level 4 again
If you have any questions or problems , commend here.

Hy Bysoft!
I'm new in XDA but i alredy flash some devices with TWRP, it seems that something went wrong with the installation of twrp. Did you try to boot into bootloader (adb reboot bootloader) and then flash the TWRP image with fastboot (fastboot flash recovery twrp.img) and then type fastboot reboot?
I find that list of command: adb reboot etc.. in your device page of TWRP (https://twrp.me/huawei/huaweip8.html). In this site you find the TWRP image for your device, you have to use this image when you flash with fastboot (fastboot flash recovery twrp.img where twrp.img is the image that you downloaded in TWRP site).
PrintHelloPeople

PrintHelloPeople said:
Hy Bysoft!
I'm new in XDA but i alredy flash some devices with TWRP, it seems that something went wrong with the installation of twrp. Did you try to boot into bootloader (adb reboot bootloader) and then flash the TWRP image with fastboot (fastboot flash recovery twrp.img) and then type fastboot reboot?
I find that list of command: adb reboot etc.. in your device page of TWRP (https://twrp.me/huawei/huaweip8.html). In this site you find the TWRP image for your device, you have to use this image when you flash with fastboot (fastboot flash recovery twrp.img where twrp.img is the image that you downloaded in TWRP site).
PrintHelloPeople
Click to expand...
Click to collapse
Hello .
I am also a newcomer
it's true . I also installed TWRP 3.1.1 on the phone in the same way
Thanks for sharing your opinion with me and other XDA users
Regards ,