I flashed MIUI 14 from TWRP and it's working fine. The problem is that none of the Magisk modules are loading after a reboot.
I tried both Magisk 25.2 and Magisk Canary (v831a398b 25206). Still unable to load the modules. Anyone got it working?
HI
is the flashed MIUI 14 the chinese version ?
phoenixuwe said:
HI
is the flashed MIUI 14 the chinese version ?
Click to expand...
Click to collapse
There is not and never will be a CN rom for this device.
Did you download the recovery rom and flash that? (That's what I did)
After I flashed that recovery rom my magisk didn't work anymore as expected since the boot partition gets overwritten.
So what you do is that you download the "Payload Dumper" python program, I used this one:
GitHub - vm03/payload_dumper: Android OTA payload dumper
Android OTA payload dumper. Contribute to vm03/payload_dumper development by creating an account on GitHub.
github.com
With python installed you open a terminal and navigate to the downloaded payload dumper you type in this command:
Code:
python payload_dumper.py payload.bin
After a while it errors out (atleast it did for me) but there should be an output folder with a nicely extracted boot.img file!
Copy that file to your phone and use magisk to patch it, then transfer it back to your computer and flash it with fastboot with the usual:
Code:
fastboot flash boot boot.img
After that my magisk worked perfectly again
ExtremelyMAD said:
Did you download the recovery rom and flash that? (That's what I did)
After I flashed that recovery rom my magisk didn't work anymore as expected since the boot partition gets overwritten.
So what you do is that you download the "Payload Dumper" python program, I used this one:
GitHub - vm03/payload_dumper: Android OTA payload dumper
Android OTA payload dumper. Contribute to vm03/payload_dumper development by creating an account on GitHub.
github.com
With python installed you open a terminal and navigate to the downloaded payload dumper you type in this command:
Code:
python payload_dumper.py payload.bin
After a while it errors out (atleast it did for me) but there should be an output folder with a nicely extracted boot.img file!
Copy that file to your phone and use magisk to patch it, then transfer it back to your computer and flash it with fastboot with the usual:
Code:
fastboot flash boot boot.img
After that my magisk worked perfectly again
Click to expand...
Click to collapse
You don't need to do all that. Just flash Magisk_25.2.zip in TWRP and you get root. As simple as that!
My problem was that the Pixelify module was causing bootloop and once I removed that module, all my other magisk modules worked fine.
Hmm that's weird, maybe my zipfile was corrupt or anything because just reflashing it through TWRP didn't do it for me. But yeah if that works then it's significantly simpler
Do you have a link to the MIUI 14 Rom?
Spillunke said:
Do you have a link to the MIUI 14 Rom?
Click to expand...
Click to collapse
Sure thing, here you go:
Xiaomi Software Update Download (Recovery ROM) - Mi Firmware
Download Xiaomi Software Update and Update your Xiaomi phones with Stable Recovery ROM using official Xiaomi Flash Tool or OTA Method.
mifirmware.com
or a direct link:
https://bigota.d.miui.com/V14.0.3.0.TKDEUXM/miui_VILIEEAGlobal_V14.0.3.0.TKDEUXM_ba28c79ffe_13.0.zip
ExtremelyMAD said:
Hmm that's weird, maybe my zipfile was corrupt or anything because just reflashing it through TWRP didn't do it for me. But yeah if that works then it's significantly simpler
Click to expand...
Click to collapse
Of course, flashing Magisk zip in TWRP works as it's a time tested strategy and have been doing this forever.
ExtremelyMAD said:
Sure thing, here you go:
Xiaomi Software Update Download (Recovery ROM) - Mi Firmware
Download Xiaomi Software Update and Update your Xiaomi phones with Stable Recovery ROM using official Xiaomi Flash Tool or OTA Method.
mifirmware.com
or a direct link:
https://bigota.d.miui.com/V14.0.3.0.TKDEUXM/miui_VILIEEAGlobal_V14.0.3.0.TKDEUXM_ba28c79ffe_13.0.zip
Click to expand...
Click to collapse
The roms on this site are all marked STABLE while some are STABLE BETA.
RainGater said:
Of course, flashing Magisk zip in TWRP works as it's a time tested strategy and have been doing this forever.
Click to expand...
Click to collapse
Exact, provided you use the right TWRP.
NOSS8 said:
Exact, provided you use the right TWRP.
Click to expand...
Click to collapse
No officially supported twrp version for miui 14 yet, what is the right twrp for now?
mogging said:
No officially supported twrp version for miui 14 yet, what is the right twrp for now?
Click to expand...
Click to collapse
You can use the A12 to flash the A13, since the system is in A12. No need for TWRP to root or install mods.
Hello
Is this module safe to install?
How to get iOS like animations and recent menu in MIUI - xiaomiui
Xiaomi's MIUI is already pretty similar compared with iOS. But the thing is the company has been removing animations from some of its budget smartphones like
xiaomiui.net
Related
OxygenOS 11 OP7TPro_ O2_BETA_02
Magisk v21.4 Manager 8.0.7 Patched Root Boot Image
https://www.androidfilehost.com/?fid=17248734326145729690
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145729691
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145729692
Stock Recovery Image
https://www.androidfilehost.com/?fid=17248734326145729693
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322771
OxygenOS 11 OP7TPro_ O2_BETA_01
Magisk v21.4 Manager 8.0.7 Patched Root Boot Image
https://www.androidfilehost.com/?fid=17248734326145719958
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145719959
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719960
Stock Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719961
Full ZIP OxygenOS HD01BA 11 Open Beta
https://androidfilehost.com/?fid=17248734326145719998
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322187
May need to install Magisk Manager manually
OxygenOS 10.0.4 EU was kindly picked up by @t-ryder Linked Below
https://forum.xda-developers.com/t/...-rom-oxygen-os-10-0-14.4236633/#post-84539771
OxygenOS 10.0.13 HD01BA Magisk/Stock Boot Images, ADB/Stock Recovery
Magisk v21.1 Manager 8.0.3 Patched Root Boot Image
https://www.androidfilehost.com/?fid=10763459528675591459
May need to install Magisk Manager manually
Full ZIP OxygenOS HD01BA 10.0.13
https://www.androidfilehost.com/?fid=10763459528675591484
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675591455
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591468
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591462
Combined Folders
https://www.androidfilehost.com/?w=files&flid=320311
Usage (Unlocked Bootloader)
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot path/to/patched_boot.img or fastboot flash recovery path/to/patched_recovery.img
fastboot reboothttps://www.androidfilehost.com/?fid=17248734326145729693
Thanks for posting these very useful resources... much appreciated...
How's the full zip upload coming along?
I thought I was clever and used the patched magisk image for 10.0.13 HD01BA on my firmware (updated OTA) version 10.0.13 HD01AA... all seems to be working fine barring one crucial function, that being wifi which is greyed out...
I'm assuming the broken wifi radio is symptomatic of the differing firmware versions?
sand_man said:
How's the full zip upload coming along?
I thought I was clever and used the patched magisk image for 10.0.13 HD01BA on my firmware (updated OTA) version 10.0.13 HD01AA... all seems to be working fine barring one crucial function, that being wifi which is greyed out...
I'm assuming the broken wifi radio is symptomatic of the differing firmware versions?
Click to expand...
Click to collapse
I'm grabbing what I think is the HD01AA Full ZIP from Oxygen Updater, I'll grab the stock boot and try making a magisk patched img for you as well, If they work I might add HD01AA to my supported devices manifest.
digidude512 said:
I'm grabbing what I think is the HD01AA Full ZIP from Oxygen Updater, I'll grab the stock boot and try making a magisk patched img for you as well, If they work I might add HD01AA to my supported devices manifest.
Click to expand...
Click to collapse
That's very kind of you sir! I've flashed BA and WiFi is working now. I think my device, as are many others, are impartial to firmware version. BA/AA/global/European, seems to all be the same barring 1 or 2 minor differences. Using the right patched magisk boot image is critical though.
Having said that I'm yet to flash boot the patched image so let's see what effect it has on WiFi (it any)...
Once again thank you for providing these resources. [emoji1303]
sand_man said:
That's very kind of you sir! I've flashed BA and WiFi is working now. I think my device, as are many others, are impartial to firmware version. BA/AA/global/European, seems to all be the same barring 1 or 2 minor differences. Using the right patched magisk boot image is critical though.
Having said that I'm yet to flash boot the patched image so let's see what effect it has on WiFi (it any)...
Once again thank you for providing these resources. [emoji1303]
Click to expand...
Click to collapse
Hope this helps
https://forum.xda-developers.com/7t-pro/how-to/oos-10-0-13-hd01aa-t4195159
@digidude512 Every Update needs a new Thread... interesting.
Stop this sh!t.
K3V1991 said:
@digidude512 Every Update needs a new Thread... interesting.
Stop this sh!t.
Click to expand...
Click to collapse
Your feedback has been taken.
Original Post has been updated for OxygenOS 11 Open Beta.
OOS 10.0.13 is still in original post but moved to spoiler.
Thanks for the update. Will probably stay on 10.0.13 for now though, as it is super stable and practically bug free.
Hello,
I just want to confirm is it really that simple to get Magisk & Root Access just by flashing patched boot image? Won't I need to full system & data wipe? I have stock OOS 10.0.13.
Athum said:
Hello,
I just want to confirm is it really that simple to get Magisk & Root Access just by flashing patched boot image? Won't I need to full system & data wipe? I have stock OOS 10.0.13.
Click to expand...
Click to collapse
yes
Thread updated with Open Beta 2
In the beta 2 A11 i have problem with magisk. Update and bootloop. All steps install correct and finnaly bootloop.
Any steps to fix it?
Magisk 21.4
chudy34 said:
In the beta 2 A11 i have problem with magisk. Update and bootloop. All steps install correct and finnaly bootloop.
Any steps to fix it?
Magisk 21.4
Click to expand...
Click to collapse
Just to confirm are you using a OnePlus 7T Pro EU Model.
HD01BA is for EU, I will be updating my second thread for 7T Global (HD01AA) and India models later.
digidude512 said:
Just to confirm are you using a OnePlus 7T Pro EU Model.
HD01BA is for EU, I will be updating my second thread for 7T Global (HD01AA) and India models later.
Click to expand...
Click to collapse
yes my model is EU.
I updated ota and install magisk unactive slot and the same boot to recovery and bootloop. Maybe problem is in magisk?
Flashing via OTA full ROM works great. After installation was completed I installed magisk to inactive slot and rebooted my device after this and my device is still rooted! Automatic brightness works much better with Beta 2
kaplatz said:
Flashing via OTA full ROM works great. After installation was completed I installed magisk to inactive slot and rebooted my device after this and my device is still rooted! Automatic brightness works much better with Beta 2
Click to expand...
Click to collapse
I get an error. And what version of magisk do you use? I used the latest 21407 and unfortunately bootloop after uploading.
I use 21.4 (21400) and it works like a charm.
Do we get patched boot image or diy instructions for Beta 3?
I see the release candidate for Android 11 has dropped! Anyone have access to the full download file? All I can find is the open_beta 4 which isn't going to work patched and flashed running the RC...
Have anyone can upload the last oos A11 adb recovery please
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in fastboot using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Marcolo88 said:
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in recovery (stock recovery) using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Click to expand...
Click to collapse
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Belpek said:
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Click to expand...
Click to collapse
And flash it in fastboot not recovery.
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I flashed too in recovery, i wrote wrong (now i edit my message).
I'll try your suggestion to rename the img, but in the previous Xiaomi i never did it and it worked .
Thank you very much
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I tried just now and it doesn't work also with the file renamed
Do you unlock bootloader?
zelenko said:
Do you unlock bootloader?
Click to expand...
Click to collapse
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Marcolo88 said:
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Click to expand...
Click to collapse
Flash in fastboot...
leobak said:
Flash in fastboot...
Click to expand...
Click to collapse
This i did but it goes into boot loop
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
nousernamesorry said:
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
Click to expand...
Click to collapse
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
MocnePifko said:
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
Click to expand...
Click to collapse
For me, with zygisk, i can make work all application with root checker (like banking apps).
Marcolo88 said:
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
Click to expand...
Click to collapse
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
louiswong2099 said:
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
Click to expand...
Click to collapse
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Marcolo88 said:
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
It worked on my Xiaomi 11T(not pro version) with a magisk-canary-patch, now the bootloop has been gone and really appreciated for your kindness help.
Hi Guys, so we got a pilot release for MIUI 13. Here is the guide to flash/update using Xiaomi.eu ROM:
Update to MIUI13 (Android 12) from MIUI EU V12.5
A TWRP backup of current rom is recommended before following the next steps
You can follow my guide to know how you do it here: https://forum.xda-developers.com/t/...-flash-twrp-root-device-flash-eu-rom.4402203/
Download Fastboot EU rom from here: https://sourceforge.net/projects/xi...13.0.1.0.SKDMIXM_v13-12-fastboot.zip/download
Extract all the contents in zip file to any normal folder
We will be using Bootloader/Fastboot mode. Boot into Bootloader: Power off your mobile then hold Volume Down + Power Button till Fastboot bunny pops up
Connect your device to PC
To update use the updater executable for respective OS platform windows_fastboot_update_rom.bat (for windows)
For clean flash you can use windows_fastboot_first_install_with_data_format.bat (for windows)
Follow the procedures as per above choice
Wait patiently while the PC does its Job.
You may see a long pause post “writing Cust” command depending on PC configuration. try hitting any letter key on your keyboard, the process continues this way.
You may hit letter key whenever you see unusual pauses during pushing of super partition file sparse sending 1 of 9 to 9 of 9
Wait till process finishes and reboots
Flash Magisk and Root
Copy boot.img from the extracted ROM images folder to your mobile
Global Boot.img (use this if you wanna root Globoal Miui13.
Install latest Magisk app from here: https://github.com/topjohnwu/Magisk/releases/download/v24.1/Magisk-v24.1.apk
Install the app and select install in Magisk and choose patch source file and select the boot.img you copied.
Wait for the process, copy the new patched image form mobile to your PC
Now lets flash the new pathced boot image using below, replace with path to boot image in place of “< --- >”
fastboot flash boot_a “<magisk_patched.img>”
fastboot flash boot_b “<magisk_patched.img>”
Reboot and check the magisk app
Follow my guide here to pass safteyNet: https://forum.xda-developers.com/t/...-flash-twrp-root-device-flash-eu-rom.4402203/
Update to miui 13 can't flash via twrp?
Yuditkiichi said:
Update to miui 13 can't flash via twrp?
Click to expand...
Click to collapse
Only the stock global rom is for recovery, xiaomi.eu rom is for fastboot.
I can boot the twrp.img, but I can't navigate in the main menu. It won't do anything
dandris86 said:
I can boot the twrp.img, but I can't navigate in the main menu. It won't do anything
Click to expand...
Click to collapse
Probably twrp is not yet compatible with the new android 12 firmware, some users also reported the same problem.
sushuguru said:
Probably twrp is not yet compatible with the new android 12 firmware, some users also reported the same problem.
Click to expand...
Click to collapse
Thanks for the quick reply
I'm updated whiteout format data. Everything looks ok.
Alright, so I was previously rooted on 12.5 (global), non twrp. its not necessary for rooting.
I did the ota update to v13 miui (global). but as its a switch between v11 and v12 of android its not possible to install magisk into an empty a/b slot.
I tried to fastboot flash your global miui boot.img after patching it with magisk and it did not work.
I suspect the boot.img to not be compatible with the global rom.
So I opted to flash the Eu fastboot version of miui 13, I set up the phone.
Then patched the stock boot.img with magisk and fastboot that. Done phone is now rooted on v13 miui. and passing safety net check.
phone data was lost as i had to switch from global to eu.
Can anyone confirm that we get widgets and other features that are not found in the miui 13 global I want to make the switch but I want to know what would still be missing
The global fastboot rom is now released. follow same steps above to have rooted global non twrp.
V13.0.1.0.SKDMIXM (https://xiaomifirmwareupdater.com/miui/vili/stable/V13.0.1.0.SKDMIXM/)
-Edit-
Ive also updated to the latest via ota V13.0.2.0.SKDMIXM (Stable beta). but as it detected the boot.img was modified it downloaded the entire recovery rom. Installed. Lost root access.
I then fastboot re flashed the patched boot.img from the V13.0.1.0.SKDMIXM and it works.
so im rooted/ safetynet check passed on V13.0.2.0.SKDMIXM (Global)
roms can be found here https://xiaomifirmwareupdater.com/miui/vili/
Downloaded the latest EEU vili_eea_global_images_V13.0.8.0.SKDEUXM_20220224.0000.00_12.0_eea_38cc4dcea7.tgz
but the only .bat files I see are
flash_all.bat, flash_all_except_storage.bat and flash_all_lock.bat
BettlePimp said:
Downloaded the latest EEU vili_eea_global_images_V13.0.8.0.SKDEUXM_20220224.0000.00_12.0_eea_38cc4dcea7.tgz
but the only .bat files I see are
flash_all.bat, flash_all_except_storage.bat and flash_all_lock.bat
Click to expand...
Click to collapse
It's a fastboot stock rom which this flash with miflash or with bat files
This thread is about XIAOMI EU custom rom
This phone is so ****ty, I'm trying to do OTA update via 100mbit/'s network in netherlands from about two f***NG weeks and it can not be finished. I can't belive that I have paid 800€ for so big ****!
Hello
For the ROOT it works perfectly (without TWRP, just with magisk)
You unlock the bootloader and wait 1 week, you extract the boot.img, you modify the file with magisk and do the command wtih adb with the modified boot
Very simple
(If you want to extract the rom file by yourself you can just extract with a little tool after your download the rom
, you can extract the fil with the payloaf file, for that, just have a look in the method 3 in this link)
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.
How do I go about rooting android 13 stable (update 2) ?
IGKID said:
How do I go about rooting android 13 stable (update 2) ?
Click to expand...
Click to collapse
Follow my guide. Pretty straight forward
NE2213 android 13 magisk stock boot patched c20
I have android 13 NE2215
Everytime I try to boot patched boot.image it goes to Qualcomm crashdump mode...is there a working way to root oxygen os 13 c20 on NE2211?
wshyar said:
Everytime I try to boot patched boot.image it goes to Qualcomm crashdump mode...is there a working way to root oxygen os 13 c20 on NE2211?
Click to expand...
Click to collapse
Where did you obtain your patched boot image?
It's always best to get it yourself and patch it yourself.
dladz said:
Where did you obtain your patched boot image?
It's always best to get it yourself and patch it yourself.
Click to expand...
Click to collapse
From OOS 13 payload.bin using fastboot enhance tool or payload dumper tool, it doesn't work with either of them..
wshyar said:
From OOS 13 payload.bin using fastboot enhance tool or payload dumper tool, it doesn't work with either of them.
Click to expand...
Click to collapse
That is the correct way to do it.
Are you using the latest Magisk? Was the firmware you extracted it from the full firmware? Or a smaller incremental zip?
Full zip is around 4.2GB
IGKID said:
I have android 13 NE2215
Click to expand...
Click to collapse
follow my thread
dladz said:
That is the correct way to do it.
Are you using the latest Magisk? Was the firmware you extracted it from the full firmware? Or a smaller incremental zip?
Full zip is around 4.2GB
Click to expand...
Click to collapse
I Am using latest Magisk version and even tested lower versions.
The firmware is about 4.85gb at first it installs version NE2211_11_C.19
But i updated it to NE2211_11_C.20 and checked the incremental update in fastboot enhance tool while extracting boot.img..
wshyar said:
I Am using latest Magisk version and even tested lower versions.
The firmware is about 4.85gb at first it installs version NE2211_11_C.19
But i updated it to NE2211_11_C.20 and checked the incremental update in fastboot enhance tool while extracting boot.img..
Click to expand...
Click to collapse
? It installs C_19 then it's not the one you want, you need to regrab C_20, use oxygen updater if it's available.
If not then I'm not sure buddy
g96818 said:
follow my thread
Click to expand...
Click to collapse
Will try it ton and get back to you.
Update: I do not understand what is going on in your thread. It's all over the place. For example you say use stock and patch it yourself or download patched bootloader. Can you provide a more simple tutorial please.
Does anyone root Android 13 succefully yet?
Xainn said:
Does anyone root Android 13 succefully yet?
Click to expand...
Click to collapse
Yes, same as oos12
1. Download zip rom and extract payload.bin
2. Use Fastboot Enhance export boot.img from payload.bin
3. Install Magisk Manager on your phone
4. Copy boot.img to your phone storage
5. Patch boot.img by Magisk Manager
6. Copy Patched file (in Download folder) to your PC and reboot phone to Bootloader Mode
7. Open Windows Power Shell at folder has Patched file and run command
fastboot flash boot patched_file_name.img
fastboot reboot
tranthengoc said:
1. Download zip rom and extract payload.bin
2. Use Fastboot Enhance export boot.img from payload.bin
3. Install Magisk Manager on your phone
4. Copy boot.img to your phone storage
5. Patch boot.img by Magisk Manager
6. Copy Patched file (in Download folder) to your PC and reboot phone to Bootloader Mode
7. Open Windows Power Shell at folder has Patched file and run command
fastboot flash boot patched_file_name.img
fastboot reboot
Click to expand...
Click to collapse
You wouldn't need Fastboot reboot as you're telling the device to boot when typing Fastboot boot.
Spot on otherwise