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

Search This thread

taralo123

New member
Sep 16, 2022
1
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 ?
Hey I fixed that by using fastboot erase userdata
 

toufik_d

Senior Member
Sep 25, 2015
58
3
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
 

Alice2022

New member
Sep 24, 2022
1
0
i went through all the steps it it was just fine until i ran "fastboot -w"
got this error - can anyone help with this?

"Error: Sparse mode is only supported for android
C:\Users\abrae\Desktop\platform-tools_r33.0.3-windows\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata"

EDIT: fastboot erase userdata did the trick! <3
 
Last edited:

toufik_d

Senior Member
Sep 25, 2015
58
3
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
 
  • Like
Reactions: criszz

bar1

Member
Sep 16, 2008
30
1
Hi everyone....Please help me what does it mean
"When flashing super.img, if you get the message Invalid sparse file format at header magic, this is fine."
what exactly should i do?
proceed to the next step?


Sorry i was wrong...i am actually getting :
Sending sparse 'super' 3/9 (786428 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed

Downloaded the file twice...let me try the mega link
 
Last edited:

bar1

Member
Sep 16, 2008
30
1
can't get into recovery now....only bootloader...i am busy downloading a new super file....any ideas will be highly appreciated.
 

bar1

Member
Sep 16, 2008
30
1
Hi everyone....I booted my linux machine and got all the instructions to work but the phone does not boot.
I am getting:Erase successful, but not automatically formatting, on the last step?
is this normal?
Is there a way to go back to the chinese rom?
I am without a phone now :-(
 

bar1

Member
Sep 16, 2008
30
1
Hi everyone....I booted my linux machine and got all the instructions to work but the phone does not boot.
I am getting:Erase successful, but not automatically formatting, on the last step?
is this normal?
Is there a way to go back to the chinese rom?
I am without a phone now :-(
By the way, my phone doesn't go to a boot loop
It just showing the realme logo and switches off.
bootloader is showing unlocked
 

dick_vigarista

Senior Member
Dec 9, 2017
289
139
Realme GT 2 Pro
I was trying to go to India region again, flashed the rom normally but got in a bootloop, trued a few times but always got a bootloop, finally decided to set active partition to A and flashed the stock global from first post. and got a brick, no response at all from device. will have to open again to go on EDL.




Follow flashing steps as below credit @hacls
NOTES:
- You can also run fastboot getvar current-slot to check which partition is active before running fastboot --set-active=a
- You can flash stock nonroot boot.img first and root later with 1 command.
- When flashing super.img, error message will display "Invalid sparse file format in header", it will look frozen but this is OK, leave it running.
- I highly recommend backing up all the partitions of the phone at this step, including persist.img, and keeping the files secure!
fastboot getvar current-slot
fastboot --set-active=a
FOR STOCK NON-ROOT:
fastboot flash boot boot.img

FOR ROOT:
fastboot flash boot bootA16magisk.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 reboot
 
Last edited:

Quake94

Senior Member
Jan 24, 2009
82
18
The first post is version A.10 of the ROM.
Someone would need to confirm, but I do not think downgrading works.
 

bar1

Member
Sep 16, 2008
30
1
can i use the MSM tool to change from Chinese to English?
this guy helped me unbrick my device but he put me back on Chinese
I actually dont mind paying him again to be put on global.

I tried everything and i get stuck in the boot loop.
 

themagicalmage22

Senior Member
Oct 17, 2015
194
22
I've successfully went from Chinese rom to Global rom with locked bootloader! I followed @sanya_rnd 's guide. I'll explain it in an easier way since the "second screen" she had in the original post is confusing:

1. Flash the global rom files and make sure to only use the stock/rootless boot image.

2. After you've booted into the system, skip everything in the setup and do:
a. Turn on ADB debugging
b. Update to latest A.19 (or later update that's 5GB+)

3. Once you've updated to the latest system, do a factory reset! This is a crucial step!

4. When the format is done and you've boot up to the system, redownload the deeptest apk from the Realme GT2 Pro official community.

5. If you've done things right, you should be welcomed with "Exit Deeptest" or something similar.

6. Click that button, then do the commands while the phone is connected to the computer:
a. adb reboot bootloader

7. When you're in the bootloader, first try to see if fastboot is working for you. Enter the command: fastboot devices. If you see it fine, go to number 8 but if it says "Waiting for any device" then:
a. Go to Device Manager
b. Find the "Android" device that has an exclamation point
c. Right click, then manually find the drivers for it.
d. Click the "Android Phone/Device" option
e. Click the ADB Bootlaoder Interface then install
d. Once installed, try the fastboot devices command again to see if it's working

8. Now, the big moment, if fastboot sees your device, then do the command: fastboot flashing lock

9. You'll get a prompt in the phone's screen and rethink if you will really lock the bootloader. If you don't wanna continue, just press the power button and use the phone as it is. If you want to lock it. then press the volume down then power button.

10. Once entered, you'll see a weird Chinese thing that has a loading bar appear. This means your device is being locked properly!

11. Pray to all the gods and hope your phone boots, cause if not, you have to pay for MSM Tool or have your local Realme Service reflash the original Chinese rom.

12. If things go well, then CONGRATS YOU HAVE LOCKED BOOTLOADER IN A GLOBAL ROM!
 

JammerD

Member
Mar 22, 2013
27
4
I have the same problem, I get this message when entering fastboot -w, i did try the fastboot erase userdata instead, but my phone wont boot , just a boot loop i think, tried entering all the commands again, same thing
 

Attachments

  • 1666535473752.jpg
    1666535473752.jpg
    2.8 MB · Views: 44
Last edited:

phos-photograph

New member
Nov 16, 2022
2
0
after days of work,finally get this proper guide.though I did it in different order of commands from a chinese bbs and end as recovery mode
 

phos-photograph

New member
Nov 16, 2022
2
0
but i can't use the fingerprint function,the fingerprint image even shows on the center of the screen instead of the right place
 

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.