Database Develop

help install back 9.1.10 stable from xiaomi eu beta latest wia twrp

hi friend i have xiaomi redmi 4x i have unlocked bootloader OK
I have install twrp 3110 OK
when i install this xiaomi.eu rom latest beta everything is OK
when i want install back latest stable global 9.110 by xiaomi i download normal recovery rom from xiaomi site and put it on phone storage then i normal go twrp wipe (factory reset) install 9110 install is ok
when i click reboot system i see on boot only mi logo and no this .... powered by android
also same when i choose in twrp wife all data system etc expect storage where is this downloaded rom.
could any explain me why it stuck at boot if installation via twrp is ok ?

but when i install back this xiaomi.eu rom boot works OK

tubabuyukustun said:
hi friend ....
could any explain me why it stuck at boot if installation via twrp is ok ?
Click to expand...
Click to collapse
Hello, this happens because official MIUI boot.img verifies if recovery.img is also official/original.
You have 2 options to resolve the boot problem:
1. If you want to keep TWRP then modify boot.img... http://en.miui.com/thread-249666-1-1.html (with R4X image of course)
and flash it from TWRP or fastboot: fastboot flash boot boot.img
2. If you want original recovery, get "recovery.img" from the exact TGZ image as your MIUI ZIP
and flash it: fastboot flash recovery recovery.img
:good:

MIUI 10 flashing twrp, root and rom guide required

Hello,
I'm lookig for a guide how to twrp, root and install custom rom, on my Mi5 miui 10 global stable.
I'm not newbe I did a lot of flashing on my previus phones Nexus and others. But this time I feel lost. I sit on miui 10 global stable. When I try to to flash twrp I get reroll to mi recovery every single time. All guides I found in the Internet are dedicated to older android versions. Xiaomitool don't help too.
Can someone point me to the right direction? It is time to change rom on my Mi5 finally to give him boost b4 I buy something new.
Best regards
Amonlb

amonlb said:
Hello,
I'm lookig for a guide how to twrp, root and install custom rom, on my Mi5 miui 10 global stable.
I'm not newbe I did a lot of flashing on my previus phones Nexus and others. But this time I feel lost. I sit on miui 10 global stable. When I try to to flash twrp I get reroll to mi recovery every single time. All guides I found in the Internet are dedicated to older android versions. Xiaomitool don't help too.
Can someone point me to the right direction? It is time to change rom on my Mi5 finally to give him boost b4 I buy something new.
Best regards
Amonlb
Click to expand...
Click to collapse
Your bootloader is unlocked, right?
Then you need reboot to fastboot mode and flash latest official twrp via fastboot.
Like
Code:
fastboot flash recovery <path to twrp.img>
Have you tried it that way?

Phil_Smith said:
Your bootloader is unlocked, right?
Then you need reboot to fastboot mode and flash latest official twrp via fastboot.
Like
Have you tried it that way?
Click to expand...
Click to collapse
Bootloader is unlocked.
I did it that way but after twrp is installed I reboot and there is no twrp available. Only mi recovery.
To make it easier...
I would like to:
Flash twrp
Flash magisk and root
Flash firmware (why i need this?) Havoc os asks to flash it but I don't know why.
Flash havock os and gapps
Flash some mods for camera and sound
I don't understeand why twrp can't be flashed and I have no idea what is modified firmware for? Do I need this?
Thanks for your time

Try the the xiaomi eu rom guide .
I think you may need its custom bootloader , not the actual rom.
Than flash the firmware required for your custom rom and reboot directly to recovery again from twrp than rom and gapps , I hope that helps

Hi, i had the same problem, try this:
1. Flash twrp as usual(fastboot flash recovery twrp.img and then fastboot reboot)
2. When rebooting, you have to enter at recovery (vol up + power) . Don't allow phone to boot! In TWRP official page, on installation instructions , they say after installation you must enter in recovery to allow TWRP patch recovery rom, because some Roms after boot reinstall original recovery.
3. Now you should have TWRP installed.

If you do
fastboot flash recovery twrp.img
and then do
fastboot boot twrp.img
It's simpler and it will boot to recovery and patch the ROM to be permanently installed.

amonlb said:
Bootloader is unlocked.
I did it that way but after twrp is installed I reboot and there is no twrp available. Only mi recovery.
To make it easier...
I would like to:
Flash twrp
Flash magisk and root
Flash firmware (why i need this?) Havoc os asks to flash it but I don't know why.
Flash havock os and gapps
Flash some mods for camera and sound
I don't understeand why twrp can't be flashed and I have no idea what is modified firmware for? Do I need this?
Thanks for your time
Click to expand...
Click to collapse
First,fastboot flash recovery twrp.img
and then no reboot your phone, just to hold the key combo (vol up + power), and then you can enter the twrp mode once because the recovery will be changed when your phone has rebooted.
But you can use the only once twrp mode to install the zip .
If you just want to use MIUI 10, you will flashboot twrp everytime when you need twrp to do something.
PS: Forgive me pool English.

rmrbpt said:
If you do
fastboot flash recovery twrp.img
and then do
fastboot boot twrp.img
It's simpler and it will boot to recovery and patch the ROM to be permanently installed.
Click to expand...
Click to collapse
Thanks, this worked!

Stock boot.img is not booting on boot_b

Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
Code:
fastboot oem unlock
Code:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
Code:
fastboot flash boot_b twrp-3.4.0-0-jasmine_sprout.img
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via
Code:
fastboot flash boot_b jasmine_global_images_V11.0.12.0.QDIMIXM_10.0/images/boot.img
(my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?

floydsen said:
Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via (my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
Click to expand...
Click to collapse
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off

KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
Code:
fastboot boot TWRP-3.4.0-0-jasmine_sprout-for_V11.0.12.0.img
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?

floydsen said:
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
Click to expand...
Click to collapse
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
also the name of that looks like one hell of a job ..shorten it to
recovery.img or twrp.img
fastboot boot recovery.img
but first run
fastboot getvar all
& also run fastboot flashing unlock_critical
but most importantly get another recovery
& i don't want to insult your intelligence but after flashing stock did you check to make sure bootloader was still unlocked and that dev settings was activated and that adb was toggled to on and that you authorised adb again
basicall after stock boot device and do the above ..plug in usb ..toggle adb ..authorise ..run adb devices ..if you see your device ..adb reboot bootloader ..fastboot devices ..see your device ..fastboot getvar all ..see bootloader is unlocked ..fastboot flashing unlock_critical if not done yet ...make sure to do ALL the above again after data gets wiped.....put twrp in adb folder ( MUST BE UNOFFICIAL RUSSIAN OR MODUFIED BY NEBRASSY ..rename to revovery.img ...fastboot boot recovery.img .. use file manager to put magisk.zip on internal then flash ..then reboot to rooted phone with stock recovery ...
Sent from my wayne using XDA Labs

KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
KevMetal said:
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly

floydsen said:
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
Click to expand...
Click to collapse
jajaja well now you know ...be careful ...some "official" roms are also more buggy than unofficial ones for Jasmine/Wayne..
LOS is an example ..so be forewarned .. if you like android 1 i guess stock rooted is a smart option to keep updates and keep device certified for google stuffs . .
alternativeky go FULL custom rom because stock and custom recovery is just a pain and not worth the hassle on an A/B treble device flashable by fastboot ..just boot the recovery when if ever needed
fyi ..you can flash magisk and it will boot ...if you don't try changing the recovery ..so you can have stock rooted with magisk without rcustom recovery...* recommended by me if you only wamt stock with root
Sent from my wayne using XDA Labs

All good now, thanks for your help! I just flashed Magisk (and also TWRP) and everything works nicely! I will need to get some experience, but I'll keep in mind that I maybe want to get rid of the TWRP recovery. Finally security testing is fun again. Thx!

root with magisk doesnt work --> bootloop ?

hello guys,
i want to root my redmi 9 with magisk. i tried to use the "patched boot.img method", but everytime i land in a bootloop.
im on miui global 12.5.3 stable, android 11. bootloader unlocked!
i took that magisk version: https://github.com/topjohnwu/Magisk/releases/tag/v23.0 (v23.0 - as apk)
than i was on that page: https://c.mi.com/oc/miuidownload/detail?device=1900381
on that page i took on the left "redmi 9 global" - which calls:
Code:
Stable ROM
Author: MIUI Official Team
Version: V12.5.3.0.RJCMIXM (MIUI11)
Size: 2.2G
i extracted the archive and copied magisk.apk and boot.img to my download-folder on my smartphone. patched the boot.img with magisk. than copied the patched boot.img to my pc.
after that i bootet the phone into fastboot mode. than i flashed the patched boot.img with fastboot flash boot patchedboot.img - used than fastboot reboot and than im in the bootloop.
can someone tell me, what i am doing wrong?
(ps: when i flash the unpatched boot.img i get no bootloop and my phone is starting again - but of course with no root )
thanks
taker-`

If I understood correctly, as well as you don't mention about that, you didn't deactivate the AVB mechanism by flashing the stock vbmeta image with the command fastboot --disable-verity --disable-verification flash vbmeta [your vbmeta.img file], which is documented that if Magisk is installed without that procedure, the device is bootlooping (see this guide).

oh, i see. yes, i didnt use that command. but now i got it working. i read that twrp isnt really compatible with the redmi9 and i need another recovery.
i used that now: https://sourceforge.net/projects/shrp/
vbmeta from post #4: https://forum.xda-developers.com/t/dont-use-twrp-on-redmi-9-use-shrp.4334123/
than i did that:
fastboot flash recovery *.img
fastboot --disable-verity --disable-verification flash vbmeta *.img
fastboot reboot recovery
from there i installed integrated magisk v23.0
phone reboot...got root.

I have read that there are issues with TWRP and Magisk (as far as I know, even its developer mentions that). Although I never got SHRP to work properly on my device and I always get bootloop issues with that. Do you know if it's because of the version I run? I currently run MIUI 11.0.2.0, which I think it's the device's original version.

uh im sorry. im also new to the shrp recovery. i had only used twrp so far.
did you try to flash this version i linked? if its not working you can fast flashback ur twrp. maybe just give it a try?

taker-` said:
uh im sorry. im also new to the shrp recovery. i had only used twrp so far.
did you try to flash this version i linked? if its not working you can fast flashback ur twrp. maybe just give it a try?
Click to expand...
Click to collapse
I don't think I have tried that. I think at the worst case, because I run MIUI I'll just roll back to it's original recovery image. I'm just asking because I don't see mentions of software versions.

what smartphone do you own?

Question Where do I find TWRP for the Redmi Note 11 and how do I flash it?

As the title says. I managed to unlock the bootloader but now I need to install TWRP to install magisk, right? How do I get around doing that? There are some shady downloads on the internet but on twrp.me there is nothing for the phone. What do I do? Thanks in advance!

the device does not have official TWRP, the others available on telegram group do work fine

Thank you, but what telegram group? Could you forward me a link to it or something?

GeoS__ said:
Thank you, but what telegram group? Could you forward me a link to it or something?
Click to expand...
Click to collapse
not found | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

SubwayChamp said:
not found | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Thanks a lot. Is there a spesn version? Can I flash this spes version on my spesn phone? Thank you in advance

GeoS__ said:
Thanks a lot. Is there a spesn version? Can I flash this spes version on my spesn phone? Thank you in advance
Click to expand...
Click to collapse
spes and spesn are the same device. the "n" in spesn stands for NFC support

MarvavCZE said:
spes and spesn are the same device. the "n" in spesn stands for NFC support
Click to expand...
Click to collapse
Oh really? Can i flash it then? I really do not care much for NFC.

GeoS__ said:
Oh really? Can i flash it then? I really do not care much for NFC.
Click to expand...
Click to collapse
Of course, you can, in recovery builds these differences don't matter.

just rooted with FASTBOOT and latest Magisk.App
How to Root Xiaomi MIUI 13 based on Android 12 via Magisk
In this guide, we will show you the detailed steps to root your Xiaomi device running MIUI 13 based on Android 12 via Magisk.
www.droidwin.com
Installation
The Magic Mask for Android
topjohnwu.github.io
Current installed MiUi version needs to match the complete Recovery Image you have to download
in my case:
https://bigota.d.miui.com/V13.0.11.0.RGKEUXM/spesn_eea_global_images_V13.0.11.0.RGKEUXM_20220606.0000.00_11.0_eea_5c36ea339b.tgz
or
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Extracting the Boot.Img - let magic app patch it on your fone copy back to Computer and install it like described on "droidwin":
fastboot flash boot magisk_patched-25100_0UGhl.img
have fun
linolino

GeoS__ said:
As the title says. I managed to unlock the bootloader but now I need to install TWRP to install magisk, right? How do I get around doing that? There are some shady downloads on the internet but on twrp.me there is nothing for the phone. What do I do? Thanks in advance!
Click to expand...
Click to collapse
I am in the same situation,
ie. I have a Note 11 Pro without NFC
[Phone code: SPES ]
• bootloader unlocked from Xiaomi (after 7+ days waiting)
• running MIUI Global 13.0.15 [ RGCMIXM ] , Android v 11 RKQ1.211001.001
I have following TWRP
- twrp-3.6.2-12.1-21.06.22
- twrp-3.6.2_12-0-spes-Jabiyeff
and I tried to flash TWRP in fastboot (below), but it always fails and does not work
Code:
fastboot flash recovery twrp.img
I'm used to flashing TWRP and ROMs, but it's been a while since I touched a Xiaomi device,
so I am wondering is there anything different that I need to do ?
also, any 'new methods' for flashing Magisk ?
( and passing SafetyNet )

I am typing this on my custom ROM. I did not flash through fastboot. I booted to the twrp img with it though (fastboot boot twrp.img if i remember correctly.) and, well, i flashed from the option inside twrp

GeoS__ said:
I am typing this on my custom ROM. I did not flash through fastboot. I booted to the twrp img with it though (fastboot boot twrp.img if i remember correctly.) and, well, i flashed from the option inside twrp
Click to expand...
Click to collapse
so, you flashed TWRP recovery, by booting the TWRP from your PC ?
OK... I can try that.

exactly. i connected with adb and checked with adb devices, then pushed the twrp image to the phone and booted off of it through fastboot. if it works booting off of the img it's pretty safe to flash

To flash a custom recovery on Spes, you need to first run the following command in fastboot on the pc:
fastboot boot XXX.img (this is the name of twrp/ofox/Shrp image)
then inside the recovery, you must go to advanced and select the option flash this twrp, with that the recovery is installed by default. But remember that every time you install a new rom, the recovery will change, so you should flash twrp every time you finish installing a new rom.

Microsheepcl said:
To flash a custom recovery on Spes, you need to first run the following command in fastboot on the pc:
fastboot boot XXX.img (this is the name of twrp/ofox/Shrp image)
then inside the recovery, you must go to advanced and select the option flash this twrp, with that the recovery is installed by default. But remember that every time you install a new rom, the recovery will change, so you should flash twrp every time you finish installing a new rom.
Click to expand...
Click to collapse
exactly! twrp even offers a checkbox to automatically reflash itself after the rom when flashing

interesting, it seems to work a little bit different than what I did before! thx for sharing your knowledge

metaxda said:
I am in the same situation,
ie. I have a Note 11 Pro without NFC
[Phone code: SPES ]
• bootloader unlocked from Xiaomi (after 7+ days waiting)
• running MIUI Global 13.0.15 [ RGCMIXM ] , Android v 11 RKQ1.211001.001
I have following TWRP
- twrp-3.6.2-12.1-21.06.22
- twrp-3.6.2_12-0-spes-Jabiyeff
and I tried to flash TWRP in fastboot (below), but it always fails and does not work
Code:
fastboot flash recovery twrp.img
I'm used to flashing TWRP and ROMs, but it's been a while since I touched a Xiaomi device,
so I am wondering is there anything different that I need to do ?
also, any 'new methods' for flashing Magisk ?
( and passing SafetyNet )
Click to expand...
Click to collapse
Have these twrp you used decrypted the device succesfully? The both twrp i used didnt work on decrypt, and both bootlooped my phone after trying to flash them to recovery(others/flash to device), The one that worked on me was a unnoficial Ofox

UltimaDea said:
Have these twrp you used decrypted the device succesfully? The both twrp i used didnt work on decrypt, and both bootlooped my phone after trying to flash them to recovery(others/flash to device)
Click to expand...
Click to collapse
This is actually pretty tricky. I found 5 different recoveries for spes/n:
OrangeFox-R11.1_A12.1-Unofficial-spes.img
twrp_v.3.6.2_11_spes-2022.08.14.img
twrp-3.6.2_12-0-spes-Jabiyeff.img
twrp-3.7.0_12-0-spes-dblenk9.img
and the one and only working one:
twrp_3.6.1-spes.img (google it), my SHA256 is: 27335ab466fadb458e090bce098b3bc9302b2876d0faf392371a23bf6fe902c
Only with this last one I was able to successfully decrypt my existing (PIN protected!) data partition of the following ROM I currently use: MIUI Global 13.0.13.0 (RGKEUXM)
I hope this helps anybody.
Also I just installed Magisk 25.2 zip via this TWRP version and its working like a charme.
Edit: Flash TWRP via fastboot with the following fastboot command:
"fastboot boot twrp.img"
twrp.img is the name of your twrp file.. this will boot up this TWRP and You can directly check if You can decrypt ur existing data partition.. if You succeed then go to Advanced and click on "Flash current TWRP"

gentano said:
This is actually pretty tricky. I found 5 different recoveries for spes/n:
OrangeFox-R11.1_A12.1-Unofficial-spes.img
twrp_v.3.6.2_11_spes-2022.08.14.img
twrp-3.6.2_12-0-spes-Jabiyeff.img
twrp-3.7.0_12-0-spes-dblenk9.img
and the one and only working one:
twrp_3.6.1-spes.img (google it), my SHA256 is: 27335ab466fadb458e090bce098b3bc9302b2876d0faf392371a23bf6fe902c
Only with this last one I was able to successfully decrypt my existing (PIN protected!) data partition of the following ROM I currently use: MIUI Global 13.0.13.0 (RGKEUXM)
I hope this helps anybody.
Also I just installed Magisk 25.2 zip via this TWRP version and its working like a charme.
Edit: Flash TWRP via fastboot with the following fastboot command:
"fastboot boot twrp.img"
twrp.img is the name of your twrp file.. this will boot up this TWRP and You can directly check if You can decrypt ur existing data partition.. if You succeed then go to Advanced and click on "Flash current TWRP"
Click to expand...
Click to collapse
3.6.1 only works for MIUI A11 ROMs
3.6.2 only works for AOSP and A12 MIUI (but no for MIUI ROM flashing)
3.7.0 fully works for any ROM except A11

gentano said:
This is actually pretty tricky. I found 5 different recoveries for spes/n:
OrangeFox-R11.1_A12.1-Unofficial-spes.img
twrp_v.3.6.2_11_spes-2022.08.14.img
twrp-3.6.2_12-0-spes-Jabiyeff.img
twrp-3.7.0_12-0-spes-dblenk9.img
and the one and only working one:
twrp_3.6.1-spes.img (google it), my SHA256 is: 27335ab466fadb458e090bce098b3bc9302b2876d0faf392371a23bf6fe902c
Only with this last one I was able to successfully decrypt my existing (PIN protected!) data partition of the following ROM I currently use: MIUI Global 13.0.13.0 (RGKEUXM)
I hope this helps anybody.
Also I just installed Magisk 25.2 zip via this TWRP version and its working like a charme.
Edit: Flash TWRP via fastboot with the following fastboot command:
"fastboot boot twrp.img"
twrp.img is the name of your twrp file.. this will boot up this TWRP and You can directly check if You can decrypt ur existing data partition.. if You succeed then go to Advanced and click on "Flash current TWRP"
Click to expand...
Click to collapse
Both the TWRP 3.6.2-12.1 and TWRP 3.7.0_12-0-spes works on my phone (SPES Global)
I am on android 12 version of MIUI 13. In fact I used the TWRP 3.7 to flash MIUI13.EU 13.0.5 A12 ROM and it works.
The two versions above can decrypt my phone without any problem. MTP also works in recovery mode.
Your phone is using Android 11. Probably that's the reason the TWRP versions I've mentioned above does not work for you.
I tend to agree with NeoSDAP.