General [RMX2202] Realme GT 5G (UI2.0 & UI3.0) - ALL ROOT

[qiurigao]

 

[qiurigao]

吨wrp root

 

[nasso87]

Hi, it seems like this version of Magisk doesn't let you enable Magiskhide, am I right ?
(I'm on Realme UI 2.0 - Android 11) , is there a way to use my banking apps, Google Pay, etc.?
Thanks

 

[unparalleled82]

This worked well.
Didn't work first time, but then I updated magisk to the latest version and it worked perfectly, whereas it was stopping before that.

 

[watero]

Hey guys! Last root I did was on android 4.1 and I don't really know how to do it. I have Realme with C.05 soft. Will someone guide me?

 

[Kopasz999]

Hi guys
This root is worked on europe version? Im from Slovakia. Rmx2202gdpr 11.a.17 .Thank you

 

[becareful1]

View attachment 5486671

Hello. Is it possible to install this driver on Linux?

 

[jkaltes]

I could root a European RMX2202_11_a.17 this way.
First I checked OEM unlock in developer options.
The most difficult part is getting into bootloader. I used a program DeepTesting_realme-release_20210426_newID_signed.apk for this, which I had from https://forum.xda-developers.com/t/...-twrp-2022-02-21.4381727/page-3#post-86279181, I believe.

Hereafter I did under Linux the same as the batch files:

fastboot flashing unlock

Hereafter an automatic reinstall

Reenabling development options and USB debugging.

adb reboot bootloader

In bootloader:

fastboot boot twrp/twrp11.img

Change the language.

Uploaded a recent version of magisk renamed to zip to tmp

adb push Magisk-v24.3.zip /tmp

Pressed install in twrp and selected this file.

Hereafter reboot to system.

EDIT:
After the update to Android12 RMX2202_11_C.05, I could root it the same way using twrp/twrp12.img.
You can just press Cancel when asked for a password.
EDIT2:

After the last update RMX2202_11.C.16_1160_202204192320.44.7636e18c (for which I didn't remove root), the above method didn't work anymore.

fastboot boot twrp/twrp12.img

resulted in a black screen. I could adb in to recovery, but

/bin/twrp install /sbin/Magisk.zip

gave the following message:

TWRP does not appear to be running. Waiting for TWRP to start . . .

Press CTRL + C to quit.

EDIT3:
Booting the same way from the recovery I found here https://droidfilehost.com/download/download-realme-gt-5g-rmx2202-twrp-recovery-file/ worked. The only problem is that it is Chinese so you have to guess what to do.

EDIT4:

After the update to RMX2202_11.C.20_1200_202207201946.44.84bc864c, this method still works (when the bootloader is unlocked):

adb reboot bootloader
#WAIT
fastboot boot recovery.img
#WAIT
adb push Magisk-v25.2.zip /tmp
adb shell /bin/twrp install /tmp/Magisk-v25.2.zip
adb reboot

EDIT5:
Also works with RMX2202_11.C.27.

 

[F0Xie]

Rooted my device successfully but the banking apps not working. Is there any way to make it work magisk hide??

 

[jkaltes]

If you are using Magisk 24.3, you have to add the banking app to the DenyList. Go to Magisk settings. Turn on Zygisk and Enforce DenyList and add banking app to Configure DenyList.

 

[Kabid0033]

Can someone fix systeam read only

 

[grown_man]

Can someone fix systeam read only

there are somethings here and here but i didnt try yet

 

[jkaltes]

Can someone fix systeam read only

Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.

To change /etc/mkshrc I have created:

/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop

mkshrc is the replacement file

In module.prop I put:

id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit

 

[Kabid0033]

Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.

To change /etc/mkshrc I have created:

/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop

mkshrc is the replacement file

In module.prop I put:

id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit

Thanxx I will try this

 

[Kabid0033]

there are somethings here and here but i didnt try yet

thnx for your concern buddy

 

[Kabid0033]

Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.

To change /etc/mkshrc I have created:

/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop

mkshrc is the replacement file

In module.prop I put:

id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit

Hey if I want to edit in build.prop so I have to write all the values or only the values which I have to add??

 

[jkaltes]

Hey if I want to edit in build.prop so I have to write all the values or only the values which I have to add??

The files in /data/adb/modules are taken in place of the original files. So if you open /system/etc/mkshrc, /data/adb/modules/mkshrc/system/etc/mkshrc is opened instead.

So if you want to edit /etc/mkshrc you copy /etc/mkshrc to /data/adb/modules/mkshrc/system/etc/mkshrc and then you edit it. If you have rebooted after it's creation, you can edit /etc/mkshrc. In reality, you will be editing /data/adb/modules/mkshrc/system/etc/mkshrc because if you open /etc/mkshrc, in reality /data/adb/modules/mkshrc/system/etc/mkshrc will be opened. Without much consequences you can try it out with /etc/mkshrc.

I have never modified /system/build.prop, but you should probably do the same.
Copy the original /system/build.prop to /data/adb/modules/amodulename/system/build.prop
After reboot, you can edit /system/build.prop because /data/adb/modules/amodulename/system/build.prop is opened instead of the original file.

 

[Kabid0033]

The files in /data/adb/modules are taken in place of the original files. So if you open /system/etc/mkshrc, /data/adb/modules/mkshrc/system/etc/mkshrc is opened instead.

So if you want to edit /etc/mkshrc you copy /etc/mkshrc to /data/adb/modules/mkshrc/system/etc/mkshrc and then you edit it. If you have rebooted after it's creation, you can edit /etc/mkshrc. In reality, you will be editing /data/adb/modules/mkshrc/system/etc/mkshrc because if you open /etc/mkshrc, in reality /data/adb/modules/mkshrc/system/etc/mkshrc will be opened. Without much consequences you can try it out with /etc/mkshrc.

I have never modified /system/build.prop, but you should probably do the same.
Copy the original /system/build.prop to /data/adb/modules/amodulename/system/build.prop
After reboot, you can edit /system/build.prop because /data/adb/modules/amodulename/system/build.prop is opened instead of the original file.

Hey I tried to send one app to system but it didn’t work so I remove that module but after that my most of the system apps not working
Like: camera, gmail, clock, calculator etc

Can you help me fix this

 

[jkaltes]

Hey I tried to send one app to system but it didn’t work so I remove that module but after that my most of the system apps not working
Like: camera, gmail, clock, calculator etc

Can you help me fix this

You can't add files to /system, only replace files with your own. Something like: open is intercepted, but the directory structure is left intact. So, if you add something you have to use the name of something that already existed.

I don't understand you problem after removing the module. Did you reboot afterwards?

You can always reinstall Magisk.

 

[Kabid0033]

You can't add files to /system, only replace files with your own. Something like: open is intercepted, but the directory structure is left intact. So, if you add something you have to use the name of something that already existed.

I don't understand you problem after removing the module. Did you reboot afterwards?

You can always reinstall Magisk.

You said that we have to put files in /data/adb/modules so that it can reflect in system

So I like to make one app to place in system /app

(eg: Like in older version of android we mangae to do that directly cause their system is rw)

(From this my apps stop working)

So I manually remove the folder from the modules then reboot

But it didn’t fix how it used to be