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

Search This thread

themagicalmage22

Senior Member
Oct 17, 2015
184
21
Oh I just got the A.17 update, but I need to get the boot image from it for Magisk first. Does anyone have a Magisk patched A.17 boot.img?
 

Realme13

New member
Jun 6, 2022
4
0
Install global rom with root and command (fastboot flash boot boot.img)....and all good.

But now some banking apps don't work and root doesn't interest me.

Is there any easy way to unroot??

Thanks in advanced
 

sanya_rnd

New member
Jul 7, 2022
3
2
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
Run the bootloader lock command in fastboot mode. After the bootloader is locked, you can exit deep testing.
Proceed with
adb reboot bootloader
and
fastboot flashing lock

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.
 

Attachments

  • Screenshot_2022-07-08-00-33-15-06_0ecf870e1d5390b9ac21ebc76f00749d.jpg
    Screenshot_2022-07-08-00-33-15-06_0ecf870e1d5390b9ac21ebc76f00749d.jpg
    393.5 KB · Views: 57
  • Screenshot_2022-07-08-00-33-58-76_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    Screenshot_2022-07-08-00-33-58-76_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    144.9 KB · Views: 58

zorbakun

Senior Member
Jul 19, 2009
397
94
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.
is your widevine level set to L1 after bootloader lock?
 

themagicalmage22

Senior Member
Oct 17, 2015
184
21
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.
I don't understand the "On the second screen" thing you're saying. I'm on a rooted A.16 device, and I think I want to go rootless, but I can't understand what you said with the "second screen" thing.
 

raimir

Member
Jun 24, 2022
7
0
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.
How do I get this guy's contact? I need to do this too my image is broken
 

denraisr

Member
Jul 28, 2014
44
1
Can I use this to re-flash my global device? There are some bugs with my phone and a factory reset doesn't seem to fix it.
 

NotSmartJimmy

Member
May 19, 2022
9
0
After month from flash Global from Chinese
I have rooted my GT 2 Pro, installed safetynet, shamico modules - OK google pay works - better, but... Bank app still not work, and now also Revlolut not working bcs of root. So i hide root and now work. :) I hope it will be good.
 
Last edited:

themagicalmage22

Senior Member
Oct 17, 2015
184
21
i unlocked fastboot, flashed the global rom and then unlocked the fastboot, the android image broke, after that the cell phone is in bootloop and I can't recognize it from adb and fastboot
Why did you double unlock it? It's already unlocked, I'm not sure why you did that. Your best bet is to enter EDL mode then flash the stock firmware. You can get the EDL firmware on realmefirmware.com I think
 

raimir

Member
Jun 24, 2022
7
0
Why did you double unlock it? It's already unlocked, I'm not sure why you did that. Your best bet is to enter EDL mode then flash the stock firmware. You can get the EDL firmware on realmefirmware.com I think
I downloaded MsmDownloadTool_rcsm from realmefirmware.com, but it asks for username and password when I run
 

Attachments

  • Screenshot 2022-07-13 170627.jpg
    Screenshot 2022-07-13 170627.jpg
    30 KB · Views: 28

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.