Realme X2 Pro Root | RUI 1.0 | C.38 | Custom Recovery | Magisk Canary | SafetyNet Pass | FP

Search This thread

hack-os

Senior Member
Feb 3, 2018
73
31
Samsung Galaxy S5
OnePlus One
~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~

Update your Realme X2 Pro with C.38 with System Update or download the file specific for your device CN/IN/Global and simply opening the ozip file in your File Manager. Latest RUI Updates since c27 and Magisk Canary fixes FP which used to break when rooted. Magisk 20.4 gives issues with RUI and custom roms

Official TWRP for Realme X2 Pro which is also maintained by Mauronofrio is not the same as unofficial TWRP 3.4.0 by Mauronofrio which is given below. Use only as mentioned in this post. Official TWRP has issues when flashing ozip.
If TWRP 3.4.0 by Mauronofrio or OrangeFox Recovery for realme X2 Pro is already installed. Repeat these steps for every RUI Update. Thanks @minoccio
  1. Install c38 update ozip with TWRP and dont reboot to avoid bootloop/softbrick
    • No need to wipe any partition (Dirty Flash)
    • [Not recommended] Reboot only if its needed to automatically replace the custom recovery with stock by not installing modified vbmeta or not rooting the device by installing magisk.
  2. Install vbmeta.imgwith TWRP by selecting vbmeta partition.
    • [This step is essential to have TWRP persistent by not getting replaced with stock recovery and also to avoid bootloop]
  3. Install Magisk Canary - Rename apk tp zip and flash (Optional only if root is required)
  4. Reboot to System (May take 5-7 minutes to complete booting)

Follow the below procedure to root RUI or to replace stock recovery
  • Make sure the bootloader is unlocked. click here for Unlock Procedure
  • Boot to fastboot(power off device and hold vol- and power)
  • Install latest TWRP or OrangeFox in fastboot with a Windows PC. Use Minimal ADB Fastboot v1.4.3
  • Reboot to Custom Recovery
  • Install VBMETA with Custom Recovery - To avoid bootloop or softbrick your device and to make custom recovery persistent.
  • Flash Magisk Canary - Download to your device.
    • Download: Magisk Canary module[12.1 MB]
      • Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file. Thanks @topjohnwu

      [*]
      epma9sj.jpg
  • Get Magisk Canary Uninstaller to your device as a precaution to uninstall magisk canary by flashing this uninstaller zip file in custom recovery in case of any issues or bootloops related to Magisk.
  • Reboot to System (May take 5-7 minutes to complete booting)
  • New Magisk Canary app will be installed automatically in few seconds
  • Update Magisk Canary app
  • Uninstall any previous old versions of magisk
  • Open Magisk Canary app
    1. Click Gear button on the Right Top Corner
    2. Under section Manager click Hide Magisk Manager
      • Enter any new name of your preference
    3. Modified Magisk manager will be installed
    4. Under Magisk section, enable MagiskHide Toggle
    5. Go Back to Magisk home and click shield icon present at the bottom
    6. Go to MagiskHide - Enable toggle for all banking apps/Google Pay/apps which fail when rooted
    7. Go To SafetyNet - It would Pass basicIntegrity and ctsProfile in basic evaluation mode with Success message.
  • Note: SafetyNet in canary build passes in stock roms above (C.28) and custom roms still have to use Magisk V20.3
Troubleshoot:
Recover from Black Screen of Death (BSoD) or stuck with realme logo on boot
Can follow the following instruction(s) in any order
  • Hold Vol+ and Power button till it restarts (more than 10 seconds)
  • Work in Flashboot to Flash or Wipe anything as per your requirement.
  • Try flashing Custom Recovery
  • Flash Magisk Uninstaller if issue related to Magisk
    Download: Magisk Canary Uninstaller [2.54 MB]
  • Check if there are two magisk app installed then Uninstall only the newly magisk app installed which was the result of flashing the magisk module.
 

Attachments

  • IMG_20200703_170327.jpg
    IMG_20200703_170327.jpg
    159.4 KB · Views: 2,279
  • Screenshot_2020-07-03-12-11-01-83_98fb3b6955de9d098d2ca78d75142590.jpg
    Screenshot_2020-07-03-12-11-01-83_98fb3b6955de9d098d2ca78d75142590.jpg
    146.6 KB · Views: 2,276
  • Screenshot_2020-07-03-12-08-33-90_98fb3b6955de9d098d2ca78d75142590.jpg
    Screenshot_2020-07-03-12-08-33-90_98fb3b6955de9d098d2ca78d75142590.jpg
    148.7 KB · Views: 2,246
  • vbmeta.img
    256 bytes · Views: 402
Last edited:

Rj_Param

Senior Member
Feb 26, 2013
75
22
Mumbai
Install VBMETA with Custom Recovery only if the Factory Recovery was replaced with Custom Recovery -

i am little confused you already said to flash custom recovery, so stock recovery is going to replace anyways.
 

hack-os

Senior Member
Feb 3, 2018
73
31
Samsung Galaxy S5
OnePlus One
Install VBMETA with Custom Recovery only if the Factory Recovery was replaced with Custom Recovery -

i am little confused you already said to flash custom recovery, so stock recovery is going to replace anyways.

Install vbmeta only when you replace stock recovery with custom recovery. If custom recovery is previously installed with vbmeta, they don't need to install vbmeta again.
 

Arcide

Senior Member
Nov 20, 2011
1,519
552
Sarajevo
Realme X2 Pro
Xiaomi Mi 11 Ultra
I want to update to c28, but I'm already rooted on c27 and with Fox recovery. I need to install the newest TWRP to be able to flash the ozip, so do I only need to flash the TWRP image (over the fox image) or are there any extra steps?
 

hack-os

Senior Member
Feb 3, 2018
73
31
Samsung Galaxy S5
OnePlus One
I want to update to c28, but I'm already rooted on c27 and with Fox recovery. I need to install the newest TWRP to be able to flash the ozip, so do I only need to flash the TWRP image (over the fox image) or are there any extra steps?
You could install update just by opening the c.28 update ozip in your file manager.

You could also install twrp and update to C28 but anyway your custom recovery will get replaced with stock recovery. Again you will be required to install custom recovery if necessary.
 

Arcide

Senior Member
Nov 20, 2011
1,519
552
Sarajevo
Realme X2 Pro
Xiaomi Mi 11 Ultra
You could install update just by opening the c.28 update ozip in your file manager.

You could also install twrp and update to C28 but anyway your custom recovery will get replaced with stock recovery. Again you will be required to install custom recovery if necessary.
I remember reading that you can't install the ozip via file manager method if you have a custom recovery, are you sure it can be done safely?
 

minoccio

Member
Feb 8, 2009
38
7
I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure
 
  • Like
Reactions: Arcide and hack-os

hack-os

Senior Member
Feb 3, 2018
73
31
Samsung Galaxy S5
OnePlus One
I remember reading that you can't install the ozip via file manager method if you have a custom recovery, are you sure it can be done safely?

Yes when you have custom recovery then you cant install ozip directly from file manager but when you click the ozip in file manager, it takes you to custom recovery if not de-bloated and its completely safe :)
 
  • Like
Reactions: Arcide

hack-os

Senior Member
Feb 3, 2018
73
31
Samsung Galaxy S5
OnePlus One
I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure

Yes you are right, the custom recovery stays only if modified vbmeta is installed if not gets in bootloop.
I suggested this procedure because it is safe for everyone who initially have stock recovery or custom recovery ;)
 
  • Like
Reactions: Arcide and minoccio

nkbhr

Senior Member
Jan 11, 2015
56
13
Guys, please help.

I have to update to twrp 3.4.0 from twrp 3.3.1
Do I need to flash vbmeta patcher after flashing twrp 3.4.0
 

nkbhr

Senior Member
Jan 11, 2015
56
13
Mostly you dont need to install vbmeta again since vbmeta and recovery partitions are technically different. if it bootloops then install vbmeta.

Thank you my friend. I was able to successfully flash twrp 3.4.0. Can you also tell me what partitions to backup in twrp for a proper nandroid backup.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    ~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~

    Update your Realme X2 Pro with C.38 with System Update or download the file specific for your device CN/IN/Global and simply opening the ozip file in your File Manager. Latest RUI Updates since c27 and Magisk Canary fixes FP which used to break when rooted. Magisk 20.4 gives issues with RUI and custom roms

    Official TWRP for Realme X2 Pro which is also maintained by Mauronofrio is not the same as unofficial TWRP 3.4.0 by Mauronofrio which is given below. Use only as mentioned in this post. Official TWRP has issues when flashing ozip.
    If TWRP 3.4.0 by Mauronofrio or OrangeFox Recovery for realme X2 Pro is already installed. Repeat these steps for every RUI Update. Thanks @minoccio
    1. Install c38 update ozip with TWRP and dont reboot to avoid bootloop/softbrick
      • No need to wipe any partition (Dirty Flash)
      • [Not recommended] Reboot only if its needed to automatically replace the custom recovery with stock by not installing modified vbmeta or not rooting the device by installing magisk.
    2. Install vbmeta.imgwith TWRP by selecting vbmeta partition.
      • [This step is essential to have TWRP persistent by not getting replaced with stock recovery and also to avoid bootloop]
    3. Install Magisk Canary - Rename apk tp zip and flash (Optional only if root is required)
    4. Reboot to System (May take 5-7 minutes to complete booting)

    Follow the below procedure to root RUI or to replace stock recovery
    • Make sure the bootloader is unlocked. click here for Unlock Procedure
    • Boot to fastboot(power off device and hold vol- and power)
    • Install latest TWRP or OrangeFox in fastboot with a Windows PC. Use Minimal ADB Fastboot v1.4.3
    • Reboot to Custom Recovery
    • Install VBMETA with Custom Recovery - To avoid bootloop or softbrick your device and to make custom recovery persistent.
    • Flash Magisk Canary - Download to your device.
      • Download: Magisk Canary module[12.1 MB]
        • Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file. Thanks @topjohnwu

        [*]
        epma9sj.jpg
    • Get Magisk Canary Uninstaller to your device as a precaution to uninstall magisk canary by flashing this uninstaller zip file in custom recovery in case of any issues or bootloops related to Magisk.
    • Reboot to System (May take 5-7 minutes to complete booting)
    • New Magisk Canary app will be installed automatically in few seconds
    • Update Magisk Canary app
    • Uninstall any previous old versions of magisk
    • Open Magisk Canary app
      1. Click Gear button on the Right Top Corner
      2. Under section Manager click Hide Magisk Manager
        • Enter any new name of your preference
      3. Modified Magisk manager will be installed
      4. Under Magisk section, enable MagiskHide Toggle
      5. Go Back to Magisk home and click shield icon present at the bottom
      6. Go to MagiskHide - Enable toggle for all banking apps/Google Pay/apps which fail when rooted
      7. Go To SafetyNet - It would Pass basicIntegrity and ctsProfile in basic evaluation mode with Success message.
    • Note: SafetyNet in canary build passes in stock roms above (C.28) and custom roms still have to use Magisk V20.3
    Troubleshoot:
    Recover from Black Screen of Death (BSoD) or stuck with realme logo on boot
    Can follow the following instruction(s) in any order
    • Hold Vol+ and Power button till it restarts (more than 10 seconds)
    • Work in Flashboot to Flash or Wipe anything as per your requirement.
    • Try flashing Custom Recovery
    • Flash Magisk Uninstaller if issue related to Magisk
      Download: Magisk Canary Uninstaller [2.54 MB]
    • Check if there are two magisk app installed then Uninstall only the newly magisk app installed which was the result of flashing the magisk module.
    5
    Great news! Root possible on RUI 2.0 (Android 11.0)

    A new canary version of Magisk was released. It has fixed the issue with the boot configuration of some Oppo Devices like the Realme X2 Pro (oplus.fstab), which has led to bootloops.

    Changelog:
    img.png

    New canary version can be downloaded here: Magisk Canary
    To root your device, just patch the boot.img with the canary version of Magisk and then flash the patched boot.img and patched vbmeta.img via fastboot.

    Please note the following:
    1. Magisk Modules were removed and replaced by so called "Zygisk Modules". More information: Zygisk Modules Sample
    2. Magisk Hide was removed. However, it will be replaced soon enough by a zygisk module.
    3. Since this is a canary release, it may contain some bugs. Shouldn't be something serious though.

    Disclaimer: As always, I'm not responsible for your device. Be always careful with whatever you do with your system. And don't forget to backup your data!
    2
    I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
    install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure
    2
    I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
    install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure

    Yes you are right, the custom recovery stays only if modified vbmeta is installed if not gets in bootloop.
    I suggested this procedure because it is safe for everyone who initially have stock recovery or custom recovery ;)
    2
    no... should i ?
    i don't thinkso it will make a difference but since now u have mentioned.... leme try

    Why do you think this post was made? :mad: Follow instructions as per op and install canary edition of magisk. Magisk 20.4 is not compatible with RUI. Don't assume when are not sure. Follow OTHERS, who have a solution.