Database Develop

(Xiaomi Mi5) TWRP not loading and stuck in bootloop

Device:
Xiaomi Mi 5 32gb (Not pro)
Rom: Cyanogenmod 13
After flashing CM, my phone was stuck in a bootloop. So I decided to do the standard wipe in TWRP, and then reflash CM. My phone is still stuck in the bootloop, and now TWRP won't load. I tried flashing a newer version of TWRP 3.0.2-1, but booting into recovery still gives me the same "loading page". What should I do?
Also, I made the noob mistake of making no backups.
Edit: TWRP is now loading, but I'm still stuck with CM bootloop.

TWRP 3.0.2.0 works fine for me. I also had problems with 3.0.2.1 no touch input possible

How did you get out of the TWRP boot loop? I'm in the same situation. Your help would be appreciated.
Sent from my MI 5 using XDA Free mobile app
Edit: I reflashed 3.0.2-0 using fastboot and now it works fine. Looks like Xiaomi.eu ROM automatically installs 3.0.2-1. Reflashing 2-0 can correct it. Somehow the recovery booting takes some time ... Don't panic.

Me too. I have problem with recovery for mi5.
I enter recovery but it said cannot mount data. I cannot install other rom.
Can yoy help me???

i had the same problem with cm13 and trwp 3.0.2.1
to leave the loop just press the on button long time and try to flash to trwp 3.0.2.0 in fastboot.
Over all i just was able to flash the ressurection rom. the cm13 i stoped after 35 minutes of loading.
Ressurection works fine for me.

i had made a recovey image as boot what should i do

sir ,
i installed a recovery twrp 2.8.7.0 after that i upgraded with install by twrp 3.0 then there was two option boot recovery by accident i made the install it to boot now the phone is always booting at twrp recovery page please help me cm13 and cm11 are also not working what can iu do please give an easy way solution...:crying:

Having problem in booting to multiROM recovery

Hi
I have LeEco Le 2 x526
I had installed MultiRom v33 and MultiRom recovery
And it was working fine
Then it asked me for recovery update,then I let it install it.
But when I booted in recovery
It didn't boot in recovery . But I am able to boot in system. Please help me install MultiRom recovery

prateek5 said:
Hi
I have LeEco Le 2 x526
I had installed MultiRom v33 and MultiRom recovery
And it was working fine
Then it asked me for recovery update,then I let it install it.
But when I booted in recovery
It didn't boot in recovery . But I am able to boot in system. Please help me install MultiRom recovery
Click to expand...
Click to collapse
Uninstall it by pressing the delete button in Multirom app
Then install the new updated Multirom app v2.3

Thanks
I got it

[SOLVED]TWRP on STOCK?

TWRP on STOCK?
For some reason, I cannot seem to boot into stock ROM after flashing TWRP. I have tried both 3.2.3.1 and 3.2.1.1, and it always boots back into recovery. I have only been able to boot without TWRP directly installed, and booting TWRP from computer.
No problem with installed TWRP with other ROMs.

jhedfors said:
TWRP on STOCK?
For some reason, I cannot seem to boot into stock ROM after flashing TWRP. I have tried both 3.2.3.1 and 3.2.1.1, and it always boots back into recovery. I have only been able to boot without TWRP directly installed, and booting TWRP from computer.
No problem with installed TWRP with other ROMs.
Click to expand...
Click to collapse
I just went back to stock ProjectFI today using fastboot. After initial setup, I went back to fastboot to boot the 3.2.3-1-payton.img, then adb pushed both the twrp-installer-payton-3.2.3-1 and Magisk, installed them both at the same time and rebooted without incident.
EDIT: I used PAYTON_FI_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC

Thanks @johnjingle.
Not sure if it was because I had Magisk already installed first that was my issue, but flashing TWRP on a fresh boot image THEN flashing Magisk did the trick.

TWRP rooted boot image for OOS 11 beta hot fix

For everyone having trouble getting TWRP working on the second beta release, here is a rooted boot image with TWRP included. If you are not rooted, flash through fast boot. If you are rooted I suggest to just flash through a kernel manager. Change your lock screen to a PIN number or just remove it in general before flashing the boot image just in case, and then reboot to recovery just to be sure it worked. Do not use this if you are on the first release and not the hot fix.