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

Search This thread
Nov 23, 2014
22
5
Hi , please I will flash my realme gt2 pro with the non root global img like the tutorial in the first page but I also need to lock the bootloader and not understand the steps in the tutorial @sanya_rnd ( what is the second screen ? ) , I hope @sanya_rnd can help me with description to understand the steps and make it correctly , is it safe to lock the bootloader ?
 

sevendroid

Member
May 4, 2012
13
3
Bertioga
Realme GT 2 Pro
Hi , please I will flash my realme gt2 pro with the non root global img like the tutorial in the first page but I also need to lock the bootloader and not understand the steps in the tutorial @sanya_rnd ( what is the second screen ? ) , I hope @sanya_rnd can help me with description to understand the steps and make it correctly , is it safe to lock the bootloader ?
Second screen he means when you swipe right, there will be an android icon. Its safe if you follow the guide before locking bootloader installing apk authorizing to lock... At first i bricked mine :cry: but now its everything working well
 
Nov 23, 2014
22
5
Second screen he means when you swipe right, there will be an android icon. Its safe if you follow the guide before locking bootloader installing apk authorizing to lock... At first i bricked mine :cry: but now its everything working well
Can you please help me with the steps you do to lock the bootloader because I'm afraid to do it wrong , i hope you can help me , thank you
 
  • Like
Reactions: sevendroid

sevendroid

Member
May 4, 2012
13
3
Bertioga
Realme GT 2 Pro
Can you please help me with the steps you do to lock the bootloader because I'm afraid to do it wrong , i hope you can help me , thank you

I made this way and now I have Google pay working and bank apps working normally (safety NET verified). Received OTA updates. This is 90% the tutorial in first page, thanks to @myogui

Do the commands below in that order (follow the guide in first page but instead that commands run below codes (almost the same as the first page but I added the command “fastboot --set-active=a “ that @hacls have tested before to avoid bricking/bootloop)


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



After migrating your phone to a global rom DO NOT LOCK BOOTLOADER YET follow @hacls guide as it follows



On the second screen you will see an iconless "Test" app ( attached an image to show what is as an example )

Update to OTA A.17 version (5+GB update)

On the second screen an iconless app is still present

Do factory reset

On the second screen an iconless "Test" app should be missing

Download deeptest APK attached and press "Exit program".

The message in the app will be

“Run the bootloader lock command in fastboot mode. After the bootloader is locked, you can exit deep testing.”



Proceed with codes (in fastboot mode)



adb reboot bootloader
fastboot flashing lock


Now it shall boot normally
 

Attachments

  • IMG-20180103-WA0001.jpg
    IMG-20180103-WA0001.jpg
    268.2 KB · Views: 47
  • 010001.apk
    4.4 MB · Views: 39
Nov 23, 2014
22
5
I made this way and now I have Google pay working and bank apps working normally (safety NET verified). Received OTA updates. This is 90% the tutorial in first page, thanks to @myogui

Do the commands below in that order (follow the guide in first page but instead that commands run below codes (almost the same as the first page but I added the command “fastboot --set-active=a “ that @hacls have tested before to avoid bricking/bootloop)


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



After migrating your phone to a global rom DO NOT LOCK BOOTLOADER YET follow @hacls guide as it follows



On the second screen you will see an iconless "Test" app ( attached an image to show what is as an example )

Update to OTA A.17 version (5+GB update)

On the second screen an iconless app is still present

Do factory reset

On the second screen an iconless "Test" app should be missing

Download deeptest APK attached and press "Exit program".

The message in the app will be

“Run the bootloader lock command in fastboot mode. After the bootloader is locked, you can exit deep testing.”



Proceed with codes (in fastboot mode)



adb reboot bootloader
fastboot flashing lock


Now it shall boot normally
Ok , thank you for your help
Can I use this tutorial in realme community to lock the bootloader?

 
  • Like
Reactions: sevendroid
Nov 23, 2014
22
5
I made this way and now I have Google pay working and bank apps working normally (safety NET verified). Received OTA updates. This is 90% the tutorial in first page, thanks to @myogui

Do the commands below in that order (follow the guide in first page but instead that commands run below codes (almost the same as the first page but I added the command “fastboot --set-active=a “ that @hacls have tested before to avoid bricking/bootloop)


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



After migrating your phone to a global rom DO NOT LOCK BOOTLOADER YET follow @hacls guide as it follows



On the second screen you will see an iconless "Test" app ( attached an image to show what is as an example )

Update to OTA A.17 version (5+GB update)

On the second screen an iconless app is still present

Do factory reset

On the second screen an iconless "Test" app should be missing

Download deeptest APK attached and press "Exit program".

The message in the app will be

“Run the bootloader lock command in fastboot mode. After the bootloader is locked, you can exit deep testing.”



Proceed with codes (in fastboot mode)



adb reboot bootloader
fastboot flashing lock


Now it shall boot normally
for this command : fastboot flash boot boot.img
is this the root img or the not root img ?
if i need to lock the bootloader after flashing which img do I use ( i did not need the root ) ?
 

felipekun213

Member
Feb 11, 2017
6
1
for this command : fastboot flash boot boot.img
is this the root img or the not root img ?
if i need to lock the bootloader after flashing which img do I use ( i did not need the root ) ?
I used the second one when I changed my ROM, on my second home screen I have an Icon called "alpha", so I updated the system via OTA, did a factory reset and the "alpha" icon is gone. So followed the steps to lock the bootloader.
 
Nov 23, 2014
22
5
Since you want bootloader locked and I wrote that mine is locked ,you need to flash the version that is not rooted. Don't flash boot_magisk.img
sorry I got me messed up , you say I need to flash the not rooted version ,
this command for non root version : fastboot flash boot boot_magisk.img
this command for root version : fastboot flash boot boot.img
which one do I suppose to used if I need to lock the bootloader ?
 

sevendroid

Member
May 4, 2012
13
3
Bertioga
Realme GT 2 Pro
sorry I got me messed up , you say I need to flash the not rooted version ,
this command for non root version : fastboot flash boot boot_magisk.img
this command for root version : fastboot flash boot boot.img
which one do I suppose to used if I need to lock the bootloader ?

Download boot.img (not rooted) from first post . Command you should use is:

fastboot flash boot boot.img

Command is the same for rooted or not rooted. The difference is the name of the file. For example You may have a file called magisk_boot.img that is not rooted . The most important thing is to be sure that the file you downloaded is not the rooted version. The name you can change for everything you want. You need only match the name of the file in the command with the name of the file.
Sorry for english
 
  • Like
Reactions: kaiser_roma225

felipekun213

Member
Feb 11, 2017
6
1
I flash both images
and with fastboot flash boot boot.img I got my phone rooted
so I flashed again with fastboot flash boot boot_magisk.img
and followed the steps using the @sanya_rnd tutorial
And everything worked
 

Attachments

  • WhatsApp Image 2022-08-24 at 11.27.56.jpeg
    WhatsApp Image 2022-08-24 at 11.27.56.jpeg
    49.6 KB · Views: 32
Nov 23, 2014
22
5
Please need help when i flash the img in the last command
fastboot -w
give me this error , can anyone help

Screenshot (140)1.png
 
Last edited:
Nov 23, 2014
22
5
Try to update the fastboot binary from android studio website following the instructions on the video I sent you
I did download the sdk platform tool not the android studio ?

I did update the path of the platform-tool in environment variable but still give me the same error

All the other command work fine but the last one
fastboot -w
give me the error

Can anyone one help me please to solve this problem
 
Last edited:

shuttlejesi

New member
Jul 23, 2012
3
0
I cant finish "fastbool -w "


E:\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.043s]

F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
E:\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata

so i always boot loop :-(
how can i do ?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    How would be the process for anyone on the new china ROM official A13? Would be nescessary a rollback? Does anyone have a OTA rollback for China ROM?
  • 8
    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.