• We are moving to xdaforums.com!

    Posts made between now and when the migration is complete will not be carried over.
    You will be automatically redirected once the migration is complete.

How To Guide Rooting the Mi 11 with the latest Xiaomi.eu ROM

Search This thread

Pho3nX

Senior Member
Jun 13, 2013
2,882
2,108
Nothing Phone 1
It is enough to flash magisk in TWRP. It is not needed to extract boot.img. Just flash magisk in TWRP, it is all. I am using on last xiaomi.eu weakly ROM.
Flash archive under Recovery (by *.zip) is not supported by Magisk from the 23 build, especially for problem boot/trebble slot compatibility. It's possible to just rename *.apk to *.zip and flash under TWRP, but it's not recommanded by dev and it's highly recommanded to using Patched image method.

Installation by Custom Recovery
 
Last edited:

zoltan78

Senior Member
Jan 20, 2010
335
60
Xiaomi Mi 11
Flash archive under Recovery (by *.zip) is not supported by Magisk from the 23 build, especially for problem boot/trebble slot compatibility. It's possible to just rename *.apk to *.zip and flash under TWRP, but it's not recommanded by dev and it's highly recommanded to using Patched image method.

Installation by Custom Recovery
I do it in this way, and it works. I have Magisk.apk 23 stable and it fleshable in TWRP also.
 
  • Like
Reactions: malimt
I do it in this way, and it works. I have Magisk.apk 23 stable and it fleshable in TWRP also.
Really? That's wonderful. Could you please give me the straightforward instructions to follow? Just grab the apk file, rename it and flash it in TWRP? A walkthrough would be much, much appreciated!

Edit: You know what... I was blind, my apologies. Clearly, the link is provided above in the previous response post. I followed everything according to the instructions provided and I can confirm that Magisk 23 is working with the method provided in this link. Flash away with renaming apk to zip, folks! It works!

I guess now my only question is... Do we have to flash magisk via TWRP again using the same method after flashing .eu ROM updates?
 
Last edited:

zoltan78

Senior Member
Jan 20, 2010
335
60
Xiaomi Mi 11
Really? That's wonderful. Could you please give me the straightforward instructions to follow? Just grab the apk file, rename it and flash it in TWRP? A walkthrough would be much, much appreciated!

Edit: You know what... I was blind, my apologies. Clearly, the link is provided above in the previous response post. I followed everything according to the instructions provided and I can confirm that Magisk 23 is working with the method provided in this link. Flash away with renaming apk to zip, folks! It works!

I guess now my only question is... Do we have to flash magisk via TWRP again using the same method after flashing .eu ROM updates?
Yes you have to flash after each update. I do not reneme Magisk.apk to zip. In Magisk 23 this apk is flashable by TWRP.
 
  • Like
Reactions: malimt
Yes you have to flash after each update. I do not reneme Magisk.apk to zip. In Magisk 23 this apk is flashable by TWRP.
Can we flash the new stable .eu ROM updates using TWRP without formatting data? Because for example, my device is currently rooted now using the 12.5.9 .eu stable build. If I were to flash a new update that came out while my device is rooted, can I dirty flash or will have to clean flash?

By the way, thank you so much for your time and help!
 

zoltan78

Senior Member
Jan 20, 2010
335
60
Xiaomi Mi 11
Can we flash the new stable .eu ROM updates using TWRP without formatting data? Because for example, my device is currently rooted now using the 12.5.9 .eu stable build. If I were to flash a new update that came out while my device is rooted, can I dirty flash or will have to clean flash?

By the way, thank you so much for your time and help!
If you are on stable rom you can flash update by TWRP without format data. Just flash it i recovery. Format data is needed if you want to move to beta (weakly) updates.
 
  • Like
Reactions: malimt

Marcolo88

Member
Nov 18, 2013
42
2
Hi to all,
i tried to root the MI11T without success!
The device is unlocked just today, i tried to take the boot.img from the tar.gz and patched with magisk (like i did with my previous xiaomi), but when i flash (both boot_a and boot_b) and reboot, it go into bootloop.

If i reflash the original boot.img it works again

The miui version is the last available from my OTA (12.5.6.0(RKWEUXM) and the magisk is installed from the official git. The apk is the version 23.

What i can try to do? i tried to patch again the boot.img but the problem persist.

Thank you very much
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    EDIT: This is not for the TWRP version. I will update this thread soon!

    Hello!

    Since I saw a lot of people asking, I decided to post how to root a Mi 11 (as of 2021-02-11).

    1. Install the Xiaomi.eu ROM. You can find more details in this post. Keep the ROM's files, you will need some of them!
    2. Connect your phone to the PC and put it into file transfer mode.
    3. Download Magisk Manager from the official GitHub repository and install the APK. DO NOT DOWNLOAD MAGISK MANAGER FROM ANYWHERE ELSE. THIS GITHUB REPOSITORY IS THE ONLY OFFICIAL, TRUSTED SOURCE.
    4. In the directory you extracted the ROM zip file to, there's a directory called images. This directory contains a file called boot.img. Copy the boot.img to your phone's Download folder.
    5. Open the Settings app, go to My Device, then tap MIUI Version until it says You are now a developer.
    6. Go back to your Settings app and use the search bar to search for USB Debugging and enable it. Click on Yes when it asks whether you want to trust this computer.
    7. Once the file is completely copied, open Magisk Manager on your phone. There will be 2 categories: Magisk and Manager. On the Magisk category, click on Install and choose Select and Patch a File. Navigate to your downloads and select boot.img. Click on Let's go.
    8. When Magisk has finished patching your boot.img file, it will say Output file written to /storage/emulated/0/Download/magisk_patched_XXXXX.img, where XXXXX is 5 random letters/digits.
    9. Open a command prompt on your computer and run adb pull /sdcard/Download/magisk_patched_XXXXX.img , replacing XXXXX with the random characters Magisk showed you earlier. This will copy the file to the directory you are currently in; on Windows, if you are using cmd, this will be C:\Users\[your username].
    10. Reboot your phone into fastboot mode by turning it off, then holding the power and volume-down buttons until it vibrates.
    11. Run the commands fastboot flash boot_a magisk_patched_XXXXX.img and fastboot flash boot_b magisk_patched_XXXXX.img (notice the difference: boot_a and boot_b). Don't forget to replace XXXXX with the random characters Magisk Manager generated. Run the command fastboot reboot and open the Magisk Manager app when your phone has finished rebooting. The app should say that it needs to install some other components; click yes and let it do its thing. It will reboot the phone, and after that, Magisk and therefore the root should be working!

    When I first did this, my SafetyNet check failed. I fixed this by repeating all the steps, except that I updated the ROM instead of reinstalling it. You can update it even if it's the same version; it will just flash everything again. You may need to clear the cache of Google Play and reinstall Google Pay if the SafetyNet check initially failed.
    3
    Hi, I tryed fastboot oem unlock after alow it in developer settings but it says token verification failed.
    It is my first Xiaomi, afert came from a OnePlus 5.
    How can I manage to flash the boot image?
    You do not need to use the OEM Unlock option in the developer options. Mine is still off even after I unlocked my bootloader. You need to use the Xiaomi Unlock Tool found at https://en.miui.com/unlock/ .
    Before using this tool, you need to log in to you Mi account on your phone. Then, reboot the phone into fastboot mode, connect it to your PC, and use the unlock tool. It will tell you to wait 168 hours (1 week) before trying again. DO NOT RETRY BEFORE THE 168 HOURS ARE OVER OR THE TIMER RESETS! Even if you are a single minute early, it will reset the timer.
    Once the week has passed, do this again and your phone will be unlocked. Warning: This will erase your data.

    You should prepare the boot image BEFORE unlocking, because otherwise you will have to go through the phone's setup, install Magisk, patch the image, and wipe the phone again.


    Another warning: Do not re-lock your bootloader. If the bootloader is re-locked with any ROM other than the one the phone shipped with installed, the phone gets bricked.
    3
    Hello guys,

    i'm coming from the Oneplus Nord and its rooted with Magisk.
    How it does work with Xiaomi MI11? Can i use the original ROM (which is delivered) and flash magisk in the recovery mode and my phone is rooted?
    Next question, can i OTA Update -> Magisk flash into other boot_a/b and reboot? and its still rooted?

    After all this time, i answer for us by myself lol, it work fine like OnePlus method (keep Root after a local update/On the Fly /OTA), i have succesfull update EEA 12.5.2 Rooted/Unlocked to EEA 12.5.3 :

    1/ Download the Local Update : here
    Be sure to update from the same branch, EEA/EEE to EEA/EEE, Global to Global, CN to CN, if update is not the same branch upgrade will be not granted.

    2/ Put the Local update *.zip in a folder on the root storage folder, i create "downloaded_rom" folder

    3/ Now, Settings > About Phone > Open 12 Logo MIUI Version / Updater > Click 3/5 time on the MIUI 12 logo, you will see message "Additional update features are on" > click three ticks on the right corner > you have now access to a local upgrade option "Choose update package" > choose the Rom *.zip update path (so for my "downloaded_rom" and click update. If Archive is good (CRC) and same branch, MIUI will asked if you want upgrade, click YES

    4/ After some minutes installing, come the finalizing state and just after MIUI purpose reboot system, DON'T REBOOT, WE WILL UPDATE BOOT.IMG ROOTED NOW

    5/ Open Magisk > Install > Install to inactive Slot (After OTA) > Let's Go (Boot.img will be patched) > Success

    6/ You can reboot, after unlock PIN / etc, waiting 30 secondes for upgrade / cache finish (when data carrier is back), go in Magisk, enjoy ! You have keep root and all your access/Modules :D
    2
    It is enough to flash magisk in TWRP. It is not needed to extract boot.img. Just flash magisk in TWRP, it is all. I am using on last xiaomi.eu weakly ROM.
    Flash archive under Recovery (by *.zip) is not supported by Magisk from the 23 build, especially for problem boot/trebble slot compatibility. It's possible to just rename *.apk to *.zip and flash under TWRP, but it's not recommanded by dev and it's highly recommanded to using Patched image method.

    Installation by Custom Recovery
    2
    Why don't write directly fastboot flash boot_ab magisk_patched_XXXXX.img ? Is that intended ?
    Hey, sorry, haven't been on this forum for a while.
    I have only ever separately flashed boot_a and boot_b and I'm anxious to try anything I haven't done before when it comes to flashing anything, so I decided to stick with what I know works.

    What is the best/safe way to update rooted phone with EU Weekly Rom?
    You can use the Xiaomi.eu ROM's update script. I recommend doing it on a laptop and not touching the cable at all while flashing. If the power goes out, the laptop can finish the flash while it's running on battery. If you touch the cable and the connection breaks at the wrong moment, your phone might not boot anymore.
    So, basically: use the official update script and take measures to prevent the flash from failing.

    Do we need to do those steps each time updated the miui?

    If you use the Xiaomi.eu ROM and want to update, then yes. You will probably need to do it after updating normally, too, but I haven't tried any normal updates.

    As for Magisk: in V22, the SafetyNet test broke and wrongly showed it as failing. In V23, it's all working just fine for me without MagiskHide.