MIUI 12.0.4 TWRP flash problem

[Cravemonic]

Hello everyone,

I'm a long time lurker, so before posting any questions, I always check if there's any kind of solution to the problem. Unfortunately, I didn't find any either on this forum or others.

After updating MIUI from 12.0.3 to 12.0.4, TWRP recovery got replaced by stock one, but previously, I just flashed TWRP again and everything was fine. Now, when I try to flash TWRP on 12.0.4, it just doesn't stay on the phone. I use this method to flash TWRP and install root.

When I open command prompt inside minimal_adb_fastboot 1.4.3 folder and follow the instructions, I get the following message:

target reported max download size of 804276224 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.606s]
writing 'recovery'...
OKAY [ 0.623s]
finished. total time: 2.230s

After that, when I try to boot into TWRP through cmd, the phone gets stuck on Redmi loading logo. After flash, when I open recovery with phone, TWRP boots, but shows gibberish inside internal storage. After the phone gets disconnected from cable, only stock recovery boots.

After I tried flashing TWRP with different approaches (disabling driver signature, safe mode, revoke usb debugging, reinstalling phone drivers in device manager...), somehow Magisk got wiped, but Magisk manager was left. My last resort was to factory reset and try to flash TWRP again, but it still gives the same results, sometimes in different forms.

Is there any possibility that Xiaomi's new "security" update block TWRP with their stock recovery?

 

[loopypalm]

Hello everyone,

I'm a long time lurker, so before posting any questions, I always check if there's any kind of solution to the problem. Unfortunately, I didn't find any either on this forum or others.

After updating MIUI from 12.0.3 to 12.0.4, TWRP recovery got replaced by stock one, but previously, I just flashed TWRP again and everything was fine. Now, when I try to flash TWRP on 12.0.4, it just doesn't stay on the phone. I use this method to flash TWRP and install root.

When I open command prompt inside minimal_adb_fastboot 1.4.3 folder and follow the instructions, I get the following message:

target reported max download size of 804276224 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.606s]
writing 'recovery'...
OKAY [ 0.623s]
finished. total time: 2.230s

After that, when I try to boot into TWRP through cmd, the phone gets stuck on Redmi loading logo. After flash, when I open recovery with phone, TWRP boots, but shows gibberish inside internal storage. After the phone gets disconnected from cable, only stock recovery boots.

After I tried flashing TWRP with different approaches (disabling driver signature, safe mode, revoke usb debugging, reinstalling phone drivers in device manager...), somehow Magisk got wiped, but Magisk manager was left. My last resort was to factory reset and try to flash TWRP again, but it still gives the same results, sometimes in different forms.

Is there any possibility that Xiaomi's new "security" update block TWRP with their stock recovery?

copy your important data somewhere

reflash twrp again using

fastboot flash recovery twrp.img

Flash vbmeta.img using

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

reboot to twrp using

fastboot boot twrp.img
(or pwr+vol up)

flash orangeFox recovery

flash dfe if you want to decrypt the storage and format data (not wipe)

in orangefox check the option :
aggressive stock recovery deactivation

 

[Cravemonic]

copy your important data somewhere

reflash twrp again using

fastboot flash recovery twrp.img

Flash vbmeta.img using

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

reboot to twrp using

fastboot boot twrp.img
(or pwr+vol up)

flash orangeFox recovery

flash dfe if you want to decrypt the storage and format data (not wipe)

in orangefox check the option :
aggressive stock recovery deactivation

Thanks for the reply.

Sorry for the late reply, had some other stuff on my hand.

Sorry for the stupid question, but do I need to download vbmeta.img from somewhere or just straight up use the the command without any downloaded file? I read that vbmeta files are all unique to their own devices, that's why I'm curious if it should be replaced at all.

 

[loopypalm]

Thanks for the reply.

Sorry for the late reply, had some other stuff on my hand.

Sorry for the stupid question, but do I need to download vbmeta.img from somewhere or just straight up use the the command without any downloaded file? I read that vbmeta files are all unique to their own devices, that's why I'm curious if it should be replaced at all.

extract vbmeta from miui "A10" zip (not A11) or download the attached file

 

[Cravemonic]

extract vbmeta from miui "A10" zip (not A11) or download the attached file

Ah, I see. Thanks for the help again.

I've downloaded MIUI 12.0.4 global from this website and extracted vbmeta.img.

I don't really want to replace TWRP with OrangeFox recovery, but since TWRP can be replaced by stock recovery after every update, I'll use Fox instead.

 

[loopypalm]

I don't really want to replace TWRP with OrangeFox

TWRP is the "confort zone"
OFox is the "future"

 

[Cravemonic]

TWRP is the "confort zone"
OFox is the "future"

After testing it out, I absolutely agree with you. Never thought that you can turn a simple mobile recovery into a modern PC mobo BIOS.

Additional kudos to recovery's devs for using a fox as a theme. As Firefox fan, the recovery looks really good with it.

 

[loopypalm]

After testing it out, I absolutely agree with you. Never thought that you can turn a simple mobile recovery into a modern PC mobo BIOS.

Additional kudos to recovery's devs for using a fox as a theme. As Firefox fan, the recovery looks really good with it.

i'm more into functionalities than themes
but , yeah , it's a well done thing ...