How To Guide [Chinese Version] Install RMX3301 Global stock firmware from Chinese

Search This thread

jerryaus

New member
Apr 23, 2022
3
2
hello guys,
I have done bootloader unlocking and flash the rom from Chinese to Global without root, however Google pay doesn't work, saying this phone does,'t meet security requirements and CTS fail
 

robert3892

Senior Member
Jul 26, 2006
101
28
You can try now to relock bootloader with this tutorial. Just download apk attached to this post and follow the steps in FAQ.
If I use this procedure to try and lock the bootloader will this erase all data I currently have installed with the global rom? I won't mind this so long as it doesn't brick the phone.
 

robert3892

Senior Member
Jul 26, 2006
101
28
I decided to be a guinea pig and test the procedure indicated by ObiWaan. Now you can unlock and relock the bootloader without any issues.

I'd like to thank all of the people who wrote to RealMe to request this change as I asked a few weeks ago. Public opinion can persuade companies to change!

I hope this opens up 3rd party rom opportunity for developers.
 

Dino888

Member
May 12, 2022
5
1
Hey I have a question - the magisk app on my phone - when I open it it asks top upgrade to full magisk, what happens if I press yes?
 

NotSmartJimmy

New member
May 19, 2022
4
0
Hello
I have Unlocked bootloader, changed rom from chinese to global, with command " flash boot_magisk.img"
I got CTS profile match not passed
Now if i want lock bootloader with this new global rom i need flash pure "boot.img" or it doesn't matter ?

I don;t want brick my phone, thats why im asking.
 

ObiWaan

Member
Jan 17, 2022
7
1
Realme GT 2 Pro
Hello
I have Unlocked bootloader, changed rom from chinese to global, with command " flash boot_magisk.img"
I got CTS profile match not passed
Now if i want lock bootloader with this new global rom i need flash pure "boot.img" or it doesn't matter ?

I don;t want brick my phone, thats why im asking.
Hi, it matters, if you'll try to lock bootloader with magisk boot, it will brick the phone. And it seems, that flashing just stock boot.img is not enough, it will brick the phone anyway. Maybe flash again stock global rom to delete all root sources and after that try to lock the bootloader
 

shivrajsingh

Senior Member
Sep 10, 2013
188
39
Jaipur
Realme GT 2 Pro
if you're stuck in bootloop try making sure you have the latest version of sdk platform tools, 33.0.1 worked for me.

try running the commands in this order
Code:
fastboot flash boot boot_magisk.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img 
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash userdata userdata.img

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w

fastboot flash boot boot_magisk.img

then on your phone hit power button with start selected
Working fine. Attached zip of platform tools is must for flashing.
 

iamrance.asa

Senior Member
if you're stuck in bootloop try making sure you have the latest version of sdk platform tools, 33.0.1 worked for me.

try running the commands in this order
Code:
fastboot flash boot boot_magisk.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img  
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash userdata userdata.img

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w

fastboot flash boot boot_magisk.img

then on your phone hit power button with start selected
on the money. Platform-tools 33.0.1 seems to be needed for it to work. It kept ending up on a bootloop when I used version 32 that was installed system-wide from Android Studio (stable). Thanks for this!
 
  • Like
Reactions: flatout23

Quake94

Member
Jan 24, 2009
16
4
Hi, maybe stupid question. Do chinese and global models have different modem bands? Does flashing global version to chinese change modem?
 

Rumed1

New member
May 25, 2022
1
0
mz GT 2 Pro stucked in fastboot mode after 'flashing' to global rom..
after command fastboot -w i got this message:
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
is there any solution?
 
Last edited:

flatout23

Member
Apr 20, 2016
25
10
if you're stuck in bootloop try making sure you have the latest version of sdk platform tools, 33.0.1 worked for me.

try running the commands in this order
Code:
fastboot flash boot boot_magisk.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img  
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash userdata userdata.img

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w

fastboot flash boot boot_magisk.img

then on your phone hit power button with start selected
Had Bootloop as well, downloaded the latest ADB files and followed your commands, but i changed the first one to boot.img as i dont want root on the phone

fastboot flash boot boot.img

downloaded ADB from this one, windows version. had a very old version which still worked for xiaomi devices but not anymore it seems^^
 

flatout23

Member
Apr 20, 2016
25
10
mz GT 2 Pro stucked in fastboot mode after 'flashing' to global rom..
after command fastboot -w i got this message:
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
is there any solution?
update your ADB from link in my replay. had same issue also issue with super.img
belive me, the new version of ADB made the difference, just flashed everything again like the one i also did a replay and it will work.
WARNING: some process will take very long, had to wait very long on vbmeta, one of them. just walk away and come back in like 10 minutes and magic is done. its only a 4kb file but writing took forever ;)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Do you lock bootloader on global ? Gpay not work for me and bank app.
    if you read first post, NEVER lock bootloader or you can trow away the phone.
    Gpay had issues as well, installed the boot-magisk.img version, downloaded magisk, installed and then did google search for universal fingerprint fix gpay, lead to the forum here as well. So now all works fine for me. If i want i can even give super user to programs now ^^
    1
    Hi folks, I flashed the command (fastboot flash boot boot.img) and all OK.....but after with the OTA update I lost Magisk...How can I get it back??
    Flash Magisk patched boot.img again.
    1
    Hi All , i have a realme GT2 Pro
    With Chinese room RMX 3300
    Can i flash or change it to global room RMX 3301 ???
    1
    Hello, myogui! Please, help me! There is a REALME Q3S smartphone with global firmware, I unlocked the bootloader. There is a clone for India - Realme 9 5G SE. I want to install Indian firmware on my smartphone. Please tell me, where did you make global firmware files? Have you pulled out files from OFP firmware? In my Indian firmware, three files are obtained during extraction: Super.0.img, Super.1.img, Super.2.img. How can I properly extract Super so that it is one whole file?

    I have no idea mate, sorry.
    1
    Ok so for anyone struggling, here is what I did to flash 3300 to 3301 Global & root A.16 w/safety net. I hope myogui can update original post because many of us are puzzling pieces of information from different sources. Credits to @myogui, @hacls and Shato from 4pda.to forum

    If you unlocked bootloader Widevine will be L3. Some had luck contacting Realme support to fix it. I do not know if locking bootloader sets it back to L1. I think it also does not matter if you are root or nonroot, you will go down to L3 either way.
    To check Widevine level, you can use app DRMInfo

    1. Install USB fastboot drivers.
    2. Run the deep testing apk, and after it's approved let it go into bootloader mode.
    3. Connect phone to PC. If fastboot shows "waiting for devices", exit, go into Windows Update and check for updates. Then go to Optional Updates and select & install Android Google driver. (Windows 10-11)
    4. Complete the unlocking of bootloader with fastboot flashing unlock

    5. Download the Global rom from @myogui post and put in the same folder as the platform-tools where your fastboot is. Sometimes the super.img gets renamed to super-001.img, so change name back to super.img
    6. Follow flashing like below credit @hacls. You can also run fastboot getvar current-slot to check which partition is active before running fastboot --set-active=a
    If you are flashing non-root, flash "boot.img" ; otherwise flash "boot-magisk.img"
    When flashing super.img, error message will display "Invalid sparse file format in header", this is OK, leave it running.

    I was barely using the phone, so I decide to do some tests... I flashed the phone many times, and I always have the bootloop problem... Tried to relock too, bricked many times... But one simple command solve it all...

    "fastboot --set-active=a"

    .......

    In short... Just do this commands in that order...

    fastboot --set-active=a
    fastboot flash boot boot.img
    fastboot flash dtbo dtbo.img
    fastboot flash engineering_cdt engineering_cdt.img
    fastboot flash metadata metadata.img
    fastboot flash oplusreserve2 oplusreserve2.img
    fastboot flash recovery recovery.img
    fastboot flash splash splash.img
    fastboot flash super super.img
    fastboot flash vbmeta_system vbmeta_system.img
    fastboot flash vbmeta_vendor vbmeta_vendor.img
    fastboot flash vendor_boot vendor_boot.img
    fastboot flash userdata userdata.img
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    fastboot -w


    Use the Platform-tools 33.0.1 or later since the older versions of ADB this command to set the slot is diferent.

    Hope this help with bootloop and relocking problems.

    Cheers

    After flashing ROM, do not relock bootloader unless you don't care about root. Once you lock it, some people say Realme deeptesting apk does not accept RMX3301 (Global), and then you may have to rely on workarounds to unlock it again if you plan to root it in the future.

    Optional steps to update to A.16 and root:
    7. After flashing global, run the update. Currently most up-to-date version is A.16.
    This will overwrite boot.img, so if you flashed with root, Magisk will be gone - no worries.
    You will have to disable system updates to keep the root if Realme releases newer ROM, or wait until someone extracts newer software and patches boot.img. (or you could extract and patch yourself)

    8. If you want to root the A.16:

    Once OS is updated to A.16 Global, reboot back to bootloader (if you have ADB debugging enabled in Developer Options, run adb reboot bootloader, otherwise you can do the Power + volume down method)
    Download bootA16magisk.img from the link below. This is patched boot.img for A.16 version
    https://drive.google.com/drive/folders/1eC3okohfoTVQJBJvnIHyFUvHvV1ZDi2O?usp=sharing


    8.a Run fastboot getvar current-slot .
    -
    If it shows boot B partition, run fastboot flash boot_b bootA16magisk.img
    -
    If it shows boot A partition, run fastboot flash boot_a bootA16magisk.img

    8.b Reboot device
    8.c Complete Magisk app install
    Install Magisk modules (you have to copy .zip files):
    safetynet-fix-v2.2.1
    Shamiko-v0.4.4-106-release
    Both are in link above but you can download them elsewhere

    8.d Activate Zygisk in Magisk
    8.e Go to configure DenyList and add in any apps you want to hide Magisk from like banking apps.
    However - Don't enable the "Activate DenyList" option! This is required by Shamiko hide Magisk module
    Just adjust the DenyList.
    8.f Restart phone and enjoy root

    Safety Net passes with BASIC evaluation type
  • 7
    Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!

    Warning: This procedure didn't work for some! Please test at your own risks!

    Additional warning: do not relock your bootloader once your global rom is installed. You risk bricking your device.

    1. Make sure your bootloader is unlocked
    2. Download the images provided in the link below
    3. Boot your device to recovery (hold volume up and power until reboot)
    4. Wipe data
    5. Boot your device to bootloader (hold volume down and power until reboot)
    6. Connect your device to PC (make sure you have installed fastboot on your PC)
    7. From windows command prompt cd into the folder containing the images
    8. Install rooted or not boot image
    Code:
    fastboot flash boot boot.img
    OR
    Code:
    fastboot flash boot boot_magisk.img
    9. Run the following commands to flash all other images

    Code:
    fastboot flash dtbo dtbo.img
    fastboot flash engineering_cdt engineering_cdt.img
    fastboot flash metadata metadata.img
    fastboot flash oplusreserve2 oplusreserve2.img
    fastboot flash recovery recovery.img
    fastboot flash splash splash.img
    fastboot flash super super.img    
    fastboot flash vbmeta_system vbmeta_system.img
    fastboot flash vbmeta_vendor vbmeta_vendor.img
    fastboot flash vendor_boot vendor_boot.img
    fastboot flash userdata userdata.img
    
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    
    fastboot -w

    When flashing super.img, if you get the message Invalid sparse file format at header magic, this is fine.

    9. You should then be able to boot into system

    RMX3301 Stock files: https://drive.google.com/drive/folders/1-0pNU8DMhzQJjdIMYM_khqA5ASGqWatg
    Mirror: https://mega.nz/folder/kw8w1QYR#Uro0gLle8Yr5uRZrqoyByg
    4
    if you're stuck in bootloop try making sure you have the latest version of sdk platform tools, 33.0.1 worked for me.

    try running the commands in this order
    Code:
    fastboot flash boot boot_magisk.img
    fastboot flash dtbo dtbo.img
    fastboot flash engineering_cdt engineering_cdt.img
    fastboot flash metadata metadata.img
    fastboot flash oplusreserve2 oplusreserve2.img
    fastboot flash recovery recovery.img
    fastboot flash splash splash.img
    fastboot flash super super.img   
    fastboot flash vbmeta_system vbmeta_system.img
    fastboot flash vbmeta_vendor vbmeta_vendor.img
    fastboot flash vendor_boot vendor_boot.img
    fastboot flash userdata userdata.img
    
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    fastboot -w
    
    fastboot flash boot boot_magisk.img

    then on your phone hit power button with start selected
    3
    Screenshot_2022-04-10-09-49-38-85_9492aa3750dca76abb7c25b39a5f1e8e.jpg
    Screenshot_2022-04-10-09-51-41-31_b783bf344239542886fee7b48fa4b892.jpg
    Screenshot_2022-04-10-09-52-59-44_e4c56ca12ff849ac0a9dbc8dae07f3aa.jpg
    3
    I decided to be a guinea pig and test the procedure indicated by ObiWaan. Now you can unlock and relock the bootloader without any issues.

    I'd like to thank all of the people who wrote to RealMe to request this change as I asked a few weeks ago. Public opinion can persuade companies to change!

    I hope this opens up 3rd party rom opportunity for developers.
    2
    I didn't try it, but I suppose no, since realme released this apk also for global versions and added a tutorial for bootloader relock.
    cheers, relock without issues.