How To Guide Root POCO M4 Pro 4G (fleur) using Magisk

Search This thread
By:
Advanced…
E

edwin_r

Member
Dec 22, 2018
21
4
Tnanks for poining be that fork

So, finally, after some trial&errors, I installed the LSPosed module to hide mock location, because I had not only to hide root but also to hide mock. So if it works like this I will abandon smali patcher
 
D

diabolyk34

Senior Member
Apr 13, 2017
168
10
hi,

i have well rooted it
right now, i can't install the miui OTA update
how to do it ? or to disable the notification ?
thks
 
R

rqxrqx

Member
Feb 21, 2010
6
0
Do you have any detail how you did it?
I flashed the patched boot.img without success.
"fastboot flash boot patched_boot.img"
I tried it with flash boot_ a and boot_b.
Nothing worked.
Unoffical orange fox and twrp are not working.
Its the first device ever I could not root.
 
aricooperdavis

aricooperdavis

Senior Member
Feb 27, 2019
181
104
United Kingdom
cooper-davis.net
Redmi Note 11S 4G / POCO M4 Pro 4G (fleur)
Sony Xperia 5 IV
rqxrqx said:
I flashed the patched boot.img without success.
"fastboot flash boot patched_boot.img"
I tried it with flash boot_ a and boot_b.
Nothing worked.
Unoffical orange fox and twrp are not working.
Its the first device ever I could not root.
Click to expand...
Click to collapse
What are you trying to achieve? To root the phone? Or to update a rooted phone?

To update a rooted phone you need to effectively unroot it first by flashing the unpatched boot.img, then patching the boot.img, and then flashing the patched boot.img.

To root a phone you just need to follow the steps on the first post in this guide. If it "doesn't work" then we'll need some troubleshooting information like exactly where your experience deviated from those suggested by the instructions. This guide doesn't use recoveries to root (I'm not convinced that's actually possible on this device as you can't write to the boot partition at runtime).
 
R

rqxrqx

Member
Feb 21, 2010
6
0
I want to root the phone. I followed the instruction but after flashing the patched boot.img and rebooing the root checker says the phone is not rooted properly.
 
R

rqxrqx

Member
Feb 21, 2010
6
0
Finally it worked. I restarted/reinstalled the Magisk and Root Checker app serveral times after flashing the patched boot.img. Suddenly Root Checker showed green. No Idea what was the reaseon. Maybee it was a Root Checker problem.
 
aricooperdavis

aricooperdavis

Senior Member
Feb 27, 2019
181
104
United Kingdom
cooper-davis.net
Redmi Note 11S 4G / POCO M4 Pro 4G (fleur)
Sony Xperia 5 IV
rqxrqx said:
Finally it worked. I restarted/reinstalled the Magisk and Root Checker app serveral times after flashing the patched boot.img. Suddenly Root Checker showed green. No Idea what was the reaseon. Maybee it was a Root Checker problem.
Click to expand...
Click to collapse
Glad you've got it working. You certainly don't need a Root Checker app as Magisk does that for you.
 
aricooperdavis

aricooperdavis

Senior Member
Feb 27, 2019
181
104
United Kingdom
cooper-davis.net
Redmi Note 11S 4G / POCO M4 Pro 4G (fleur)
Sony Xperia 5 IV
aricooperdavis said:
Glad you've got it working. You certainly don't need a Root Checker app as Magisk does that for you.
Click to expand...
Click to collapse
photo_2023-01-04_13-34-14.jpg
 
N

ncc1977d

Senior Member
Feb 15, 2015
87
17
46
Redmi Note 11S 4G / POCO M4 Pro 4G (fleur)
Good, thought EEU would be right, but wanted to know for sure. :)
Which TWRP is better for my phone, OrangeFox-R11.1_0-Unofficial-fleur.zip or twrp_18122022_A11.img ?

And how do i install it, when boot.img is already magisk patched ? Just overwriting the boot partition or have i to install TWRP and then magisk via TWRP ?

Edit:
Just found out that there are 2 boot slots. Let me guess: TWRP goes to boot 1, then install magisk module via TWRP.
 
Last edited:
aricooperdavis

aricooperdavis

Senior Member
Feb 27, 2019
181
104
United Kingdom
cooper-davis.net
Redmi Note 11S 4G / POCO M4 Pro 4G (fleur)
Sony Xperia 5 IV
ncc1977d said:
Good, thought EEU would be right, but wanted to know for sure. :)
Which TWRP is better for my phone, OrangeFox-R11.1_0-Unofficial-fleur.zip or twrp_18122022_A11.img ?

And how do i install it, when boot.img is already magisk patched ? Just overwriting the boot partition or have i to install TWRP and then magisk via TWRP ?

Edit:
Just found out that there are 2 boot slots. Let me guess: TWRP goes to boot 1, then install magisk module via TWRP.
Click to expand...
Click to collapse
If you read through the guide you'll find the stock recovery is used throughout, no TWRP. So I can't help you with that.
 
N

ncc1977d

Senior Member
Feb 15, 2015
87
17
46
Redmi Note 11S 4G / POCO M4 Pro 4G (fleur)
I do not need help anymore, cause i found out that there is no a11 rom that i would install in exchange for a bugfree a11 MIUI, only for root or debloating. Even the crdroid a12 rom have for me inacceptable bugs.

For now i lock my bootloader and wait for MIU14 or a REAL custom rom.
 
You must log in or register to reply here.

Similar threads

yshalsager
General [MIUI Updates Tracker] Redmi Note 11S 4G / POCO M4 Pro 4G (fleur)
Replies
108
Views
25K
yshalsager
yshalsager
yshalsager
Development [Firmware] Redmi Note 11S 4G / POCO M4 Pro 4G [fleur] [Auto updated!]
Replies
35
Views
14K
yshalsager
yshalsager
Nem1x
Development [ROM] LineageOS 20.0 for Redmi Note 11S | POCO M4 Pro 4G [UNOFFICIAL] [Fleur] [Miel]
Replies
118
Views
10K
Nem1x
Nem1x
MikeChannon
  • Locked
  • Sticky
General [Info] Redmi Note 11S 4G / POCO M4 Pro 4G (fleur)
Replies
0
Views
9K
MikeChannon
MikeChannon
aricooperdavis
How To Guide Fix Google Wallet "security requirements" by spoofing fingerprint (rooted)
Replies
63
Views
23K
S
Spitzohrnase

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 11
    aricooperdavis
    aricooperdavis
    Rooting the POCO M4 Pro 4G (fleur) turned out to be quite straightforward. Note, I have a 2201117PG (EEA), you may have a different experience, it's not my fault if you brick your phone etc. Backup before you start as this will wipe your phone.

    The process can be broken down into 4 steps:
    1. Unlock Bootloader
    2. Source boot.img
    3. Patch boot.img (using Magisk)
    4. Flash patched boot.img (using adb)


    1. Unlock Bootloader​

    Note: This step will wipe your phone.

    This can be done using the official tool from MIUI, using MediatekBootloaderUnlock (Windows 10/11, which reportedly does not wipe your user data), or using mtkclient (Any OS but requires Python). I will explain the mtkclient option as I'm on Linux and don't trust MIUI with more personal data than I have to.

    Step-by-step (adapted from this How to Guide):
    • Install mtkclient and its dependencies (easier if familiar with installing python packages etc., straightforward for me on Linux)
    • On your phone activate developer mode and turn on USB debugging and OEM unlocking
    • Turn off phone and disconnect from computer
    • In the directory where you installed mtkclient run:
      • python mtk e metadata,userdata,md_udc
        • This erases your data
        • At this point plug your phone in (still turned off)
      • python mtk da seccfg unlock
        • This unlocks the bootloader
      • python mtk reset
        • This reboots the phone
    • Disconnect USB cable and reboot phone
      • When it boots a message is displayed warning that dm-verity is corrupted. Click the power button to dismiss and continue booting.

    2. Source boot.img​

    • Find your MIUI version in Settings -> About phone -> MIUI Version and look for the version number (e.g. 13.0.6.0(RKEEUXM))
    • Visit the MIUI Updates Tracker and download the matching Stable Fastboot update (if you can't find it scroll down to Extracting boot.img from Payload)
    • Unzip the TGZ and the TAR that it contains then navigate to the images directory and find the boot.img file

    3. Patch boot.img​

    We need to patch the boot.img to give it root powers. We do this on the phone using Magisk.

    Step-by-step (adapted from the Magisk installation instructions):
    • On your phone, download Magisk and install it
    • Connect your phone to your computer and put the boot.img you extracted on your phone somewhere
    • Open Magisk and in "Magisk" section tap "Install"
    • Choose the "Select and Patch a File" option and select your boot.img in the file browser and let Magisk patch it
    • Find the patched boot image in Downloads (called magisk_patched_*.img) and copy it to your computer in the same directory as the vbmeta.img we extracted earlier

    4. Flash patched boot.img​

    Finally we need to replace the current boot.img on the phone with our patched one that has root powers. This is called flashing and is done using adb.

    Step-by-step:
    • Install the Android SDK platform tools which contains adb and fastboot
    • Install a USB driver that supports fastboot mode (you cannot use fastbootd for this or you'll bootloop)
    • Ensure your phone is connected, USB debugging is enabled and working, and OEM Unlocking is enabled
    • In the directory you copied the magisk_patched_*.img to run:
      • adb reboot bootloader
        • This reboots your phone into fastboot mode. Wait until "FASTBOOT" is displayed on the screen
      • fastboot flash boot magisk_patched_*.img
        • This flashes the patched boot.img to give you root
      • fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
        • This flashes the vbmeta.img, disabling the dm-verity corruption message at startup
    • Once it's done reboot your phone by pressing and holding the power button
    That's all there is to it! This took me about an hour as I was working out all the steps as I've not rooted in a phone in nearly a decade - I reckon with a fast internet connection you could get it done in about 15 minutes.



    Extract boot.img from Payload​

    If you can't find a fastboot image (boot.img) for your version then you might be able to extract it from the full firmware package. This will require the use of a third party tool such as payload-dumper (python) or payload-dumper-go. Note that you may be better off just waiting for the fastboot image to be released to the public.



    Tidying up​

    You can delete all the stuff you downloaded onto your computer and the boot.img and magisk_patched_*.img from your phone.

    It's a good idea to disable automatic OTA updates (Settings -> Additional settings -> Developer options -> Automatic sytem updates) so that you can update through Magisk.

    Some apps will be able to tell that you have rooted your phone, and may stop you from using them. You can check this by downloading YASNAC onto your phone and seeing if it passes. If not (which it won't) the most straightforward solution is to add the Universal SafetyNet Fix module to Magisk, then enable Zygisk in Magisk settings and restart your phone, which will be enough to pass SafetyNet Attestation. If they're clever and still detect the root then in Magisk toggle Enforce DenyList and add the problematic apps to the DenyList.



    Updating Magisk
    You cannot update Magisk via the Magisk app, as this device does not allow writing to the boot partition at runtime.

    Instead, update the Magisk app, then use it to patch your stock boot.img and flash it manually using fastboot, as if you were installing it from scratch (as above). This will not wipe your user data, but be sure to backup first in case something goes wrong.
    View
    4
    L
    Lark5
    Unlock Bootloade and Root and RECOVERY for Poco M4 Pro (4G) with out Pyton (on Windows 10\11):

    Unlock Bootloader:
    1.Download the MediatekBootloaderUnlock archive. Unpack the archive ZIP.
    2. Open the Driver folder and right-click the cdc-acm.inf file, select "Install"
    3.Now go back to the main folder and install the USBDK (x64 for 64-bit OS, x86 for 32-bit OS) on your PC (also right click - install).
    4. Reboot the PC.
    5.Turn off the phone.
    6.Run the UnlockBootloader.bat file to start the bootloader unlock process. We keep it on, it is in a state of response from the phone, if the firewood, the cable is connected, then everything is ok, I’ll tell you right away that it turned out 3 times.
    7.Now connect the phone to the computer with a cable by holding down the volume up + down + power button. (If the volume up button doesn't work, try using volume up or volume up + volume down or all three hardware buttons) while the UnlockBootloader.bat file is open.
    8.Once the phone is detected, some commands will be run in the UnlockBootloader.bat file. Let the commands finish and as soon as the window closes. Your bootloader will be unlocked.
    BY THE WAY! - You can lock the bootloader again by following the same steps without clearing. Just use LockBootloader.bat with the same steps.

    Root:
    Downloading the official firmware for the phone, I took fleur_global_images_V13.0.7.0.RKEMIXM_20220419.0000.00_11.0_global (approximately 5.6GB in weight)
    Unpacked it ZIP, pulled out 2 files from there fleur_global_images_V13.0.7.0.RKEMIXM_20220419.0000.00_11.0_global\images
    boot.img and vbmeta.img

    Downloaded Magisk STABLE Version: 24.3 - download on telephone, setup APP
    Launch Magisk Manager. When a pop-up window appears asking you to install Magisk, select INSTALL and select install again.

    Click on "Fix Boot Image File".
    Connect your device to PC via USB cable. Make sure USB debugging is enabled.
    Download ADB \ fastoot (I took tools_r29.0.6-windows)
    Run CMD as Administrator
    We write -
    adb devices - the phone must be determined (QX ********* device - so all drivers are correct)
    adb reboot bootloader - The phone reboots into fastboot mode - an inscription on the screen if dm-verity corruption messages appear - press POWER to continue
    fastboot flash boot boot_PATCH.img (file name how to change)
    fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img - will remove the inscription dm-verity corruption


    OrangeFox-R11 RECOVERY:​

    Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

    Download GApps, Roms, Kernels, Themes...
    androidfilehost.com androidfilehost.com

    Download, and Run CMD as Administrator
    We write -
    fastboot flash boot XXXXNAMEXXXX.img
    Flash !boot! not fastboot flash recovery XXXXNAMEXXXX.img
    View
    3
    L
    Lark5
    aricooperdavis said:
    Well done, glad you've got it sorted!

    To clarify, this essentially follows the same 4 steps outlined in my post but using different tools that don't require python:
    1. Unlock Bootloader
      - Used MediatekBootloaderUnlock rather than mtkclient
    2. Source boot.img
      - Managed to find the images online without having to extract them from a ROM. @Lark5, where?
    3. Patch boot.img (using Magisk)
      - Same
    4. Flash patched boot.img (using adb)
      - Same
    I think there's also a custom recovery install too (OrangeFox). I tend not to bother, but it can be convenient.
    Click to expand...
    Click to collapse
    2. Find ROM on this link: https://mirom.ezbox.idv.tw/en/phone/fleur/roms-global-stable/
    Fastboot Download V13.0.7.0.RKEMIXM
    Explanations:
    For fastboot (~5.6Gb) - firmware version, just unzip the ZIP, inside there is boot.img and vbmeta
    For recovery (-2.5Gb) needed to extract boot.img Through Pyton for example

    thanks for the help aricooperdavis
    View
    2
    aricooperdavis
    aricooperdavis
    Here you go!

    View
    2
    aricooperdavis
    aricooperdavis
    Well done, glad you've got it sorted!

    To clarify, this essentially follows the same 4 steps outlined in my post but using different tools that don't require python:
    1. Unlock Bootloader
      - Used MediatekBootloaderUnlock rather than mtkclient
    2. Source boot.img
      - Managed to find the images online without having to extract them from a ROM. @Lark5, where?
    3. Patch boot.img (using Magisk)
      - Same
    4. Flash patched boot.img (using adb)
      - Same
    I think there's also a custom recovery install too (OrangeFox [not yet officially supported]) at the end. I tend not to bother with custom recoveries as I stick with the stock MIUI ROM and a custom recovery would complicate applying OTA updates. However, if you wish to install a custom ROM (anything other than a stock MIUI signed boot.img) then a custom recovery would be necessary, and they can also facilitate taking device backups etc.
    View

New posts