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

Search This thread

myogui

Senior Member
Aug 31, 2010
122
70
Realme GT 2 Pro
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
 
Last edited:

myogui

Senior Member
Aug 31, 2010
122
70
Realme GT 2 Pro
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
 

Attachments

  • Screenshot_2022-04-10-09-49-24-30_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    Screenshot_2022-04-10-09-49-24-30_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    273.2 KB · Views: 283
Last edited:

logmms

Member
Jul 6, 2014
5
1
Great post. What is the Widevine level after installing the global rom? Furthrmore, does SafetyNet pass and do OTA updates work?
 

myogui

Senior Member
Aug 31, 2010
122
70
Realme GT 2 Pro
Great post. What is the Widevine level after installing the global rom? Furthrmore, does SafetyNet pass and do OTA updates work?

Google pay works, safetynet passes with Magisk module (probably good if you unroot and relock the bootloader but then you'll be stuck until realme unlocks the RMX3301).

but level 3 widevine unfortunately. Also some apps do detect that bootloader is unlock even with safetynet module.
Screenshot_2022-04-13-20-38-04-89_0ecf870e1d5390b9ac21ebc76f00749d.jpg
Screenshot_2022-04-13-20-39-13-50_8cd65b3f3f44ba1cbfce60c9ecb7cf35.jpg
 
Came here to say that this is working! Got my chinese version today and wanted to give it a try right away.
If this command takes a lot of time and seems like the console froze, don't panic!

Code:
fastboot flash vbmeta_vendor vbmeta_vendor.img

Almost every command took like 20 seconds, this one took almost 200, but it finishes eventually.

Also, you may end up stuck on a bootloop. But there's an easy fix, as myogui said on another thread:
Enter recovery mode, wipe data. Enter fastboot and then run the last 2 commands again:

Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

fastboot -w

Now everything's working, and have been running the global rom all day flawlessly!
 
  • Love
Reactions: myogui

hacls

Member
Apr 16, 2022
23
13
Does anyone know how to solve the bootloop problem? I tried the last 2 comands, Wipe Data, last 2 comands again... Flashing everything again... Nothing...

Any help would be very apreciate. Thanks.

UPDATE: It's working now.. lol... I tried flashing back to the Chinese version from myogui, still in bootloop.. Then I execute the comand "fastboot flash vbmeta vbmeta.img", bootloop... Then a tons of research... Then I downloaded a RMX3301 17.5GB .ofp file to try flashing from realme Flash Tool... Then I go to sleep... Then I woke up and just go to PC to fix this thing, but realme Tool didn't work, the Flash Tool said "CANNOT FIND CENTRAL DIRECTORY".... Then I just tried flashing here again with the files and comands above... what the hell, I'm screwed anyway... But this time worked.... LOL...

Big thanks guys!
 
Last edited:
  • Like
Reactions: Terrorigel97

hacls

Member
Apr 16, 2022
23
13
Trying to lock again the bootloader... and then a message appears saying the flash was broken or something... now I can't even turn this thing off... Just keep flashing "realme Powered by android" screen rebooting again and again and again...

Oh my... to good to be true...

Tip: Just buy the global version.
 

wildlime

Senior Member
Mar 2, 2014
266
104
41
No luck. Have tried all combinations of solutions and still stuck in bootloop. Have flashed it fresh 8 times and no luck. Also tried the last two commands above and no luck. And can't use OFP method as realme tool not updated for Gt 2 Pro :(
 

Bnblare

Member
Oct 4, 2010
21
8
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
 

Attachments

  • platform-tools_r33.0.1-windows.zip
    6 MB · Views: 150

myogui

Senior Member
Aug 31, 2010
122
70
Realme GT 2 Pro
You would need to install Chinese rom again using another method of installation or wait for deep testing app to be available on global. But you could still use your device with the global version.
 

hacls

Member
Apr 16, 2022
23
13
Would relocking the bootloader after flashing the global brick me?
Mine bricked, now it's hard brick... The closest that I got it to back to life was with QFIL, but something keep giving errors when I try to flash... Now I'm gonna try the MSM... If doesn't work maybe I'm gonna return the phone... Or wait until realme release a useful flash tool... Who knows...

I do not recomend locking back the phone based on my experience.
 

Bnblare

Member
Oct 4, 2010
21
8
Mine bricked, now it's hard brick... The closest that I got it to back to life was with QFIL, but something keep giving errors when I try to flash... Now I'm gonna try the MSM... If doesn't work maybe I'm gonna return the phone... Or wait until realme release a useful flash tool... Who knows...

I do not recomend locking back the phone based on my experience.
Wow dude I'm sorry. Did you revert back to stock then try to relock the bootloader? Or did you try to relock while on the global?
 

Bnblare

Member
Oct 4, 2010
21
8
You would need to install Chinese rom again using another method of installation or wait for deep testing app to be available on global. But you could still use your device with the global version.
Man.. I just wanna play call of duty again lol but it knows even tho my safetynet passes. the app can probably see it's L3 still. I guess I'll wait for realme to release the tool for this phone. I'm pretty sure flashing back to stock using the tool would safely lock the bootloader automatically
 

hacls

Member
Apr 16, 2022
23
13
Wow dude I'm sorry. Did you revert back to stock then try to relock the bootloader? Or did you try to relock while on the global?

I tried to lock with the global ROM in it... Then this screen appears...

1255039147068882944.jpeg


This photo are not mine, but it's the same screen... After that... Only in EDL mode...
 
Last edited:

hacls

Member
Apr 16, 2022
23
13
Well, I gave up and paid a guy to flash via TeamViewer... And as I imagined... With MSM Download Tool was five clicks and it's done... Ridiculous easy... MSM would be a amazing tool if it were accessible... Unfreaking believable... Oh my...

But, anyway, it's solved. Thanks guys.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    What is the solution for ؟

    code
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    result
    C:\Users\toufi\Desktop\GlobalRom>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    fastboot: unknown option -- disable-verity
    code
    fastboot -w
    result
    C:\Users\toufi\Desktop\GlobalRom>fastboot -w
    Erase successful, but not automatically formatting.
    File system type f2fs not supported.
    Erase successful, but not automatically formatting.
    Can't determine partition type.
    FAILED (remote: GetVar Variable Not found)
    erasing 'userdata'...
    OKAY [ 0.050s]
    erasing 'cache'...
    FAILED (remote: Check device console.)
    finished. total time: 0.053s
    تم بنجاح حل المشكل
    الحل هو نقل ملف
    ADB + ROM GLOBAL الى القرص C
  • 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
    6
    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
    4
    I extracted the A.17 boot.img and patched it with Magisk. For anyone needing it, here it is. Make sure to do:
    1. fastboot getvar current-slot
    2. If you get a, then do fastboot flash boot_a bootA17magisk.img; if it's b, then fastboot flash boot_b bootA17magisk.img
    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.