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

Search This thread

tipaksikil

New member
Aug 30, 2018
4
0
i already tried, flash from indonesia global version to this flash file. but unfortunately, for now, my region is TW. do you have flash file for EU region?
 

Agafonoff

Member
Apr 1, 2010
22
10
Penza
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
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?
 

myogui

Senior Member
Aug 31, 2010
120
69
Realme GT 2 Pro
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.
 
  • Like
Reactions: Agafonoff

Agafonoff

Member
Apr 1, 2010
22
10
Penza
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
I figured out super.img. I glued it together using the simg2img.exe utility. Thanks a lot for the manual. I adapted it for another smartphone and I managed to change the firmware to Indian firmware. Your manual is universal.
 

hacls

Member
Apr 16, 2022
23
12
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"

I recommend myogui to put in the tutorial, actually I recommend using this command before doing anything with fastboot... This basically select the current partition slot...

I flashed the phone like 4, 5 times, changing configs, USB slots... Always have the bootloop... After this command I flashed about 4 times with 100% success.. no bootloops....

After that I made some tests trying to relock the phone, bricked many times, every time I tried to relock the phone the image got corrupted..

Then I tried to relock with this command and guess what... The phone locked the bootloader without a problem... BUT keep in mind that I locked just one time... I didn't do more tests relocking, so be careful... Just try to relock if you know how to unbrick the phone...

Every test I made was with the RMX3301 (Global) ROM on my RMX3300 (Chinese) phone..

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


To relock go to bootloader and type in that order...

fastboot --set-active=a
fastboot flashing lock


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
 
Last edited:
  • Like
Reactions: dejop

themagicalmage22

Senior Member
Oct 17, 2015
178
21
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"

I recommend myogui to put in the tutorial, actually I recommend using this command before doing anything with fastboot... This basically select the current partition slot...

I flashed the phone like 4, 5 times, changing configs, USB slots... Always have the bootloop... After this command I flashed about 4 times with 100% success.. no bootloops....

After that I made some tests trying to relock the phone, bricked many times, every time I tried to relock the phone the image got corrupted..

Then I tried to relock with this command and guess what... The phone locked the bootloader without a problem... BUT keep in mind that I locked just one time... I didn't do more tests relocking, so be careful... Just try to relock if you know how to unbrick the phone...

Every test I made was with the RMX3301 (Global) ROM on my RMX3300 (Chinese) phone..

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


To relock go to bootloader and type in that order...

fastboot --set-active=a
fastboot flashing lock


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
I'll be getting a GT 2 Pro Chinese version soon. Can anyone confirm this works? I'm pretty scared to flash this phone because I saved up so much for it (I have a lot of modding experience on Xiaomi devices so don't worry I'm not a beginner)
 

themagicalmage22

Senior Member
Oct 17, 2015
178
21
I've succeed to install from Chinese firmware on global!!🎉🎉
All gone smooth like a charm 🤩🤩.
Not overheat for now (I don't play many games, but download all apps again it is very stressful at the first start, so it's a good stress test), all sensors works, included fingerprint reader!
Tomorrow I'll try put a sim in it.

-I advice to install (windows) the right USB driver before, even if it is already read by yours pc, on mine pc works but it gave me a lot of error/don't see it before I've installed the right drivers.

-I haven't incurred in bootloop issues, but mine phone selected automatically in "slot A" all installation, so if yours goes in the "slot B" and do the bootloop thing, don't worry and repeat the procedure changing the slot with command:

fastboot set_active a
Hi, do you get OTA updates on the global rom? Thank you!
 

yau2612

Member
Jun 18, 2010
31
1
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"

I recommend myogui to put in the tutorial, actually I recommend using this command before doing anything with fastboot... This basically select the current partition slot...

I flashed the phone like 4, 5 times, changing configs, USB slots... Always have the bootloop... After this command I flashed about 4 times with 100% success.. no bootloops....

After that I made some tests trying to relock the phone, bricked many times, every time I tried to relock the phone the image got corrupted..

Then I tried to relock with this command and guess what... The phone locked the bootloader without a problem... BUT keep in mind that I locked just one time... I didn't do more tests relocking, so be careful... Just try to relock if you know how to unbrick the phone...

Every test I made was with the RMX3301 (Global) ROM on my RMX3300 (Chinese) phone..

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


To relock go to bootloader and type in that order...

fastboot --set-active=a
fastboot flashing lock


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
Hi, Please tell me how to unbrick my realme gt2 pro after relock the bootloader, thank you.
 
D

Deleted member 1755208

Guest

Attachments

  • Screenshot 2022-06-26 183520.png
    Screenshot 2022-06-26 183520.png
    7.6 KB · Views: 23

Lrolon

New member
Jun 19, 2022
1
0
Descargo de responsabilidad: ¡No soy responsable de dispositivos bloqueados, tarjetas SD muertas, etc.!

Advertencia: ¡Este procedimiento no funcionó para algunos! Por favor, pruebe bajo su propio riesgo!

Advertencia adicional: no vuelva a bloquear su cargador de arranque una vez que haya instalado su rom global. Corre el riesgo de bloquear su dispositivo.

1. Asegúrate de que tu gestor de arranque esté desbloqueado
2. Descargue las imágenes proporcionadas en el siguiente enlace
3. Inicie su dispositivo para la recuperación (mantenga el volumen arriba y enciéndalo hasta que reinicie)
4. Borrar datos
5. Inicie su dispositivo en el gestor de arranque (mantenga presionado el volumen y enciéndalo hasta que reinicie)
6. Conecte su dispositivo a la PC (asegúrese de haber instalado fastboot en su PC)
7. Desde el símbolo del sistema de Windows, cd en la carpeta que contiene las imágenes
8. Instale la imagen de arranque rooteado o no
[CÓDIGO] fastboot flash boot boot.img[/CÓDIGO]
O
[CÓDIGO]arranque flash fastboot boot_magisk.img[/CÓDIGO]
9. Ejecute los siguientes comandos para mostrar todas las demás imágenes

[CÓDIGO] fastboot flash dtbo dtbo.img
fastboot flash ingeniería_cdt ingeniería_cdt.img
fastboot flash metadatos metadatos.img
flash de arranque rápido oplusreserve2 oplusreserve2.img
fastboot recuperación flash 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 proveedor_boot proveedor_boot.img
fastboot flash datos de usuario datos de usuario.img

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

arranque rápido -w[/CÓDIGO]

Al flashear super.img, si recibe el mensaje Formato de archivo disperso no válido en el encabezado mágico, está bien.

9. Entonces debería poder iniciar el sistema

RMX3301 Archivos de archivo: https://drive.google.com/drive/folders/1-0pNU8DMhzQJjdIMYM_khqA5ASGqWatg
Espejo: https://mega.nz/folder/kw8w1QYR#Uro0gLle8Yr5uRZrqo.
yg

Desktop\GT2Pro>fastboot -w Borrado exitoso, pero sin formateo automático. El tipo de sistema de archivos f2fs no es compatible. Borrado exitoso, pero sin formato automático. No se puede determinar el tipo de partición. FALLIDO (remoto: variable GetVar no encontrada)... eliminando 'datos de usuario'. OK [0.064s] limpiando 'caché'... FALLIDO (remoto: Verifique la consola del dispositivo.) hecho. tiempo total : 0.3215 C : \ Usuarios \ lrolo.
METRO I get this error when placing the command fastboot -w what can I do to get out of the bootloop
 

Quake94

Member
Jan 24, 2009
43
10
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...
To relock go to bootloader and type in that order...

fastboot --set-active=a
fastboot flashing lock


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

Hi, I got the phone and unlocked the bootloader. Currently debating on going root with Magisk or just flash global stock...
Do you know what are the benefits of locking bootloader?
If I flash Global and lock afterwards without Magisk rooting, will this keep widevine at l1 + have the banking apps work OK etc.?
 

themagicalmage22

Senior Member
Oct 17, 2015
178
21
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
Can I just unlock bootloader then flash the Magisk boot so I can have root in the Chinese rom? Also can I lock my device after that?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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
    1
    I downloaded MsmDownloadTool_rcsm from realmefirmware.com, but it asks for username and password when I run
    Be careful running these MSM tools. A lot of them have injected ransomware. If you wanna try them I would recommend running them on virtual machine to protect your PC.
    By default MSM requires factory license verified over the network. As of now there is no freeware solution for hard bricks (locked bootloader bootloop). Softbricks with unlocked bootloader can be fixed easy with fastboot.
    You may be better off contacting Realme support, so your local authorized service can fix it under warranty.
    1
    For anyone who wants to lock a bootloader and avoid a "bootloop".
    1. Follow the instruction and migrate your phone to a global ROM, use rootless boot image
    2. DO NOT LOCK BOOTLOADER
      1. On the second screen you should have an iconless "Test" app
    3. Update to A.17 version (5+GB update)
      1. On the second screen an iconless app is still present
    4. Do factory reset
    5. On the second screen an iconless "Test" app should be missing
    6. Download deeptest APK and press "Exit program". The output will be

    Proceed with

    and


    Congratulations, you avoided a bootloop.

    With a locked bootloader all SafetyNet checks are passed, and you can have OTA updates w/o issues (magisk patching).

    Screenshots attached.


    PS
    I got a bootloop myself (tried to lock a bootloader right after chinese->global migration).
    I went to my local Realme service, and they restored a Chinese firmware on the phone for free.
    But I'm not sure if it's true for all countries though. But if you got a bootloop -- try this first.
    Thank you man, I can confirm that I was able to lock my bootloader successfully by following this guide.
  • 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
    5
    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.