• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

How To Guide UPDATE - Realme GT Convert China ROM to EU ROM OR Indin ROM

Search This thread

d_truth

Member
Oct 17, 2015
29
0
successfully flashed from Global A.09 to A.14 ROM & updated it A.16 ROM. Is there a way to update the baked Netflix app on this ROM?

Another question: I downloaded the ROM from this thread & extracted the img files. But when I flashed it on my phone, it just keeps on boot looping? Is there anything else needed to modify or change on the extracted img files?
 

bppjenil

Senior Member
Dec 7, 2016
569
190
Realme GT

Follow this thread of MrVeverything : How To Guide Realme GT 5G Convert China ROM to India (RMX2202_11_A.14) OTA is Working​

 

xyoceanyx

New member
Dec 7, 2021
1
0
hello together, maybe someone can help me. i have tried several times to flash the device, but I get at slot b an error at the following point

PS C:\adb> .\fastboot flash my_carrier my_carrier.img
Sending 'my_carrier' (340 KB) OKAY [ 0.013s]
Writing 'my_carrier' FAILED (remote: 'No such file or directory')
Finished. Total time: 0.034s
PS C:\adb> .\fastboot flash my_carrier my_carrier.img
Sending 'my_carrier' (340 KB) OKAY [ 0.013s]
Writing 'my_carrier' FAILED (remote: 'No such file or directory')
Finished. Total time: 0.025s
PS C:\adb> .\fastboot flash my_company my_company.img
Sending 'my_company' (340 KB) OKAY [ 0.012s]
Writing 'my_company' FAILED (remote: 'No such file or directory')
Finished. Total time: 0.029s

so i switched to slot a and get error messages starting at the following point

PS C:\adb> .\fastboot flash my_heytap my_heytap.img
Invalid sparse file format at header magic
Sending sparse 'my_heytap_a' 1/5 (262124 KB) OKAY [ 6.191s]
Writing sparse 'my_heytap_a' 1/5 OKAY [ 0.597s]
Sending sparse 'my_heytap_a' 2/5 (262120 KB) OKAY [ 6.202s]
Writing sparse 'my_heytap_a' 2/5 OKAY [ 0.532s]
Sending sparse 'my_heytap_a' 3/5 (262132 KB) OKAY [ 6.197s]
Writing sparse 'my_heytap_a' 3/5 OKAY [ 0.530s]
Sending sparse 'my_heytap_a' 4/5 (254588 KB) OKAY [ 6.033s]
Writing sparse 'my_heytap_a' 4/5 OKAY [ 0.511s]
Sending sparse 'my_heytap_a' 5/5 (8236 KB) OKAY [ 0.223s]
Writing sparse 'my_heytap_a' 5/5 OKAY [ 0.095s]
Finished. Total time: 32.326s

PS C:\adb> .\fastboot flash my_preload my_preload.img
Invalid sparse file format at header magic
Sending sparse 'my_preload_a' 1/3 (262124 KB) OKAY [ 6.259s]
Writing sparse 'my_preload_a' 1/3 OKAY [ 0.558s]
Sending sparse 'my_preload_a' 2/3 (262136 KB) OKAY [ 6.196s]
Writing sparse 'my_preload_a' 2/3 OKAY [ 0.512s]
Sending sparse 'my_preload_a' 3/3 (45132 KB) OKAY [ 1.092s]
Writing sparse 'my_preload_a' 3/3 OKAY [ 0.249s]
Finished. Total time: 17.841s

PS C:\adb> .\fastboot flash my_region my_region.img
Invalid sparse file format at header magic
Sending sparse 'my_region_a' 1/4 (262112 KB) OKAY [ 6.298s]
Writing sparse 'my_region_a' 1/4 FAILED (remote: 'Value too large for defined data type')
Finished. Total time: 10.821s

PS C:\adb> .\fastboot flash my_region my_region.img
Invalid sparse file format at header magic
Sending sparse 'my_region_a' 1/4 (262112 KB) OKAY [ 6.283s]
Writing sparse 'my_region_a' 1/4 FAILED (remote: 'Value too large for defined data type')
Finished. Total time: 10.067s

PS C:\adb> .\fastboot flash my_stock my_stock.img
Invalid sparse file format at header magic
Sending sparse 'my_stock_a' 1/5 (262104 KB) OKAY [ 6.187s]
Writing sparse 'my_stock_a' 1/5 OKAY [ 0.552s]
Sending sparse 'my_stock_a' 2/5 (262124 KB) OKAY [ 6.215s]
Writing sparse 'my_stock_a' 2/5 OKAY [ 0.529s]
Sending sparse 'my_stock_a' 3/5 (262124 KB) OKAY [ 6.259s]
Writing sparse 'my_stock_a' 3/5 OKAY [ 0.519s]
Sending sparse 'my_stock_a' 4/5 (262136 KB) OKAY [ 6.199s]
Writing sparse 'my_stock_a' 4/5 OKAY [ 0.518s]
Sending sparse 'my_stock_a' 5/5 (121032 KB) OKAY [ 2.917s]
Writing sparse 'my_stock_a' 5/5 OKAY [ 0.354s]
Finished. Total time: 36.401s

PS C:\adb> .\fastboot flash odm odm.img
Invalid sparse file format at header magic
Sending sparse 'odm_a' 1/5 (262140 KB) OKAY [ 6.132s]
Writing sparse 'odm_a' 1/5 OKAY [ 0.539s]
Sending sparse 'odm_a' 2/5 (262140 KB) OKAY [ 6.135s]
Writing sparse 'odm_a' 2/5 OKAY [ 0.513s]
Sending sparse 'odm_a' 3/5 (262140 KB) OKAY [ 6.142s]
Writing sparse 'odm_a' 3/5 OKAY [ 0.511s]
Sending sparse 'odm_a' 4/5 (262140 KB) OKAY [ 6.149s]
Writing sparse 'odm_a' 4/5 OKAY [ 0.524s]
Sending sparse 'odm_a' 5/5 (29764 KB) OKAY [ 0.713s]
Writing sparse 'odm_a' 5/5 OKAY [ 0.236s]
Finished. Total time: 34.242s

PS C:\adb> .\fastboot flash product product.img
Sending 'product_a' (18612 KB) OKAY [ 0.474s]
Writing 'product_a' FAILED (remote: 'Value too large for defined data type')
Finished. Total time: 0.592s


PS C:\adb> .\fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/3 (260332 KB) OKAY [ 6.180s]
Writing sparse 'system_a' 1/3 OKAY [ 0.575s]
Sending sparse 'system_a' 2/3 (262140 KB) OKAY [ 6.291s]
Writing sparse 'system_a' 2/3 OKAY [ 0.531s]
Sending sparse 'system_a' 3/3 (252424 KB) OKAY [ 5.967s]
Writing sparse 'system_a' 3/3 FAILED (remote: 'Operation not permitted')
Finished. Total time: 24.097s

PS C:\adb> .\fastboot flash system_ext system_ext.img
Invalid sparse file format at header magic
Sending sparse 'system_ext_a' 1/3 (262140 KB) OKAY [ 6.159s]
Writing sparse 'system_ext_a' 1/3 OKAY [ 0.611s]
Sending sparse 'system_ext_a' 2/3 (262140 KB) OKAY [ 6.080s]
Writing sparse 'system_ext_a' 2/3 OKAY [ 0.514s]
Sending sparse 'system_ext_a' 3/3 (251128 KB) OKAY [ 5.979s]
Writing sparse 'system_ext_a' 3/3 FAILED (remote: 'Operation not permitted')
Finished. Total time: 24.284s


PS C:\adb> .\fastboot flash vendor vendor.img
Invalid sparse file format at header magic
Sending sparse 'vendor_a' 1/3 (262140 KB) OKAY [ 6.182s]
Writing sparse 'vendor_a' 1/3 OKAY [ 0.536s]
Sending sparse 'vendor_a' 2/3 (262140 KB) OKAY [ 6.145s]
Writing sparse 'vendor_a' 2/3 OKAY [ 0.530s]
Sending sparse 'vendor_a' 3/3 (41268 KB) OKAY [ 0.978s]
Writing sparse 'vendor_a' 3/3 OKAY [ 0.273s]
Finished. Total time: 17.870s

does anyone have an idea what else i can do!? or is there maybe even someone from germany who can do this?

thx!

EDIT: So, no i used the original platform-tools .... and i only get the Invalid sparse file format at header magic error .... but it worked and the device works !!
 
Last edited:

bppjenil

Senior Member
Dec 7, 2016
569
190
Realme GT
Today I received Android 12 trial version. Is it safe to download and try? I'm on global rom
 

Attachments

  • Screenshot_2021-12-11-05-24-14-52.jpg
    Screenshot_2021-12-11-05-24-14-52.jpg
    47.4 KB · Views: 49
  • Screenshot_2021-12-11-05-24-48-37.jpg
    Screenshot_2021-12-11-05-24-48-37.jpg
    407.2 KB · Views: 50
  • Screenshot_2021-12-11-05-24-22-83.jpg
    Screenshot_2021-12-11-05-24-22-83.jpg
    339.1 KB · Views: 50

chenzhe

New member
Dec 3, 2020
2
0
For anyone who has tried the method, could you please share what is still not working in the global ROM? Fingerprint sensors, NFCs, to name a few. Thanks in advance.
 

d_truth

Member
Oct 17, 2015
29
0
For anyone who has tried the method, could you please share what is still not working in the global ROM? Fingerprint sensors, NFCs, to name a few. Thanks in advance.

For my case when I was on Global ROM, the notable issue I had was the late ROM (A.09) update. Other than that, everything works fine including bank & other apps related to money/currency.
 

bppjenil

Senior Member
Dec 7, 2016
569
190
Realme GT
For my case when I was on Global ROM, the notable issue I had was the late ROM (A.09) update. Other than that, everything works fine including bank & other apps related to money/currency.
Right now I'm on A16 global flashed by fastboot mode. Everything working perfectly including NFC, banking apps etc .
Before from CN migrated to A09 Global and then came back to CN. But compare to Global rom I didn't enjoy CN. And since last two month flashed back to Global. I have been using Global A16 rom.
 
Right now I'm on A16 global flashed by fastboot mode. Everything working perfectly including NFC, banking apps etc .
Before from CN migrated to A09 Global and then came back to CN. But compare to Global rom I didn't enjoy CN. And since last two month flashed back to Global. I have been using Global A16 rom.
your good friend
I have also updated the Chinese version to the international board before, but it crashed when I returned it. How did you successfully flash back to the Chinese version of the ROM? thanks
 

bppjenil

Senior Member
Dec 7, 2016
569
190
Realme GT
Today I received Android 12 UI 3.0
Thanks a million to MrVeverything and Imacaber1 for their efforts of Global over Chinese ROM.
 

Attachments

  • Screenshot_2021-12-15-14-24-17-25_9492aa3750dca76abb7c25b39a5f1e8e.jpg
    Screenshot_2021-12-15-14-24-17-25_9492aa3750dca76abb7c25b39a5f1e8e.jpg
    199.9 KB · Views: 32
Last edited:
  • Like
Reactions: MrVeverything

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    Hi
    These are the steps that were followed to make the global ROM work for you...

    Please follow the instructions step by step

    Try these steps at your own risk and I am not responsible for losing your phone or data


    1- You must open the bootloader with this link .
    2- Download the global ROM A.09 ( img) file with this link .
    3- Download the INDIN ROM A.14 ( img) file with this link . Thanks to ( MrVeverything )
    4- Extract the img files ( 44 items) img .
    5- Download the adb file and install it and it will be rooted on disk c
    6- Put the files extracted in step 3 and put them in the adb folder
    7- Boot your Phone into Fastboot Mode
    8- In the adb folder hold the SHIFT key and right-click on an empty spot inside the folder, then select the ‘Open PowerShell window here’ option.
    9- Connect your device to the computer and follow the following commands :

    .\fastboot devices
    .\fastboot getvar all
    ........ ( This step is very important in order to know what is the path of solt a or b )

    If it is solt b follow the following commands... Thank you very much to srsbsns89 . and hmdqa

    Now follow the commands

    Code:
    .\fastboot flash boot boot.img
    .\fastboot flash dtbo dtbo.img
    .\fastboot flash modem modem.img
    .\fastboot --disable-verity flash vbmeta vbmeta.img
    .\fastboot --disable-verity flash vbmeta_system vbmeta_system.img
    .\fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
    .\fastboot reboot fastboot ......
    ( you see phone after this command on recovery mod )
    .\fastboot flash abl abl.img
    .\fastboot flash aop aop.img
    .\fastboot flash bluetooth bluetooth.img
    .\fastboot flash cpucp cpucp.img
    .\fastboot flash devcfg devcfg.img
    .\fastboot flash dsp dsp.img
    .\fastboot flash engineering_cdt engineering_cdt.img
    .\fastboot flash featenabler featenabler.img
    .\fastboot flash hyp hyp.img
    .\fastboot flash imagefv imagefv.img
    .\fastboot flash keymaster keymaster.img
    .\fastboot flash multiimgoem multiimgoem.img
    .\fastboot flash my_carrier my_carrier.img
    .\fastboot flash my_company my_company.img
    .\fastboot flash my_engineering my_engineering.img
    .\fastboot flash my_heytap my_heytap.img
    .\fastboot flash my_manifest my_manifest.img
    .\fastboot flash my_preload my_preload.img
    .\fastboot flash my_product my_product.img
    .\fastboot flash my_region my_region.img
    .\fastboot flash my_stock my_stock.img
    .\fastboot flash odm odm.img
    .\fastboot flash oplus_sec oplus_sec.img
    .\fastboot flash oplusstanvbk oplusstanvbk.img
    .\fastboot flash product product.img
    .\fastboot flash qupfw qupfw.img
    .\fastboot flash qweslicstore qweslicstore.img
    .\fastboot flash shrm shrm.img
    .\fastboot flash splash splash.img
    .\fastboot flash system system.img
    .\fastboot flash system_ext system_ext.img
    .\fastboot flash tz tz.img
    .\fastboot flash uefisecapp uefisecapp.img
    .\fastboot flash vendor vendor.img
    .\fastboot flash vendor_boot vendor_boot.img
    .\fastboot flash vm-bootsys vm-bootsys.img
    .\fastboot flash xbl xbl.img
    .\fastboot flash xbl_config xbl_config.img
    .\fastboot -w
    .\fastboot reboot


    Now after completion, the phone will enter recovery mode and format and the global ROM will work with you


    __________________________________________________________________________________________________________

    How to fix “Device is not Play Protect certified” error

    Get your Device ID. This is a 16-digit alphanumeric ID which you will need to certify your device with Google.

    If you are still able to access the Play Store, install the Device ID app. If not, you can download the APK file here and install/sideload it on your device.

    Go to Google’s Device Registration page here and paste/type your Google Services Framework ID on the Android ID box and tap Register.

    After registering, you may enter your Google credentials on the Play Store. And you might as well reboot your device for good measure.

    after that clean data for google play ... and reboot your device and done



    Done .... :)
    3
    [Thread Cleaned]

    Good day everyone!

    Some things were edited; some removed. Sure, mental illness can be made fun of – stand up comedians do it all the time – and we're all for free speech but there's a time and place for everything and this was/is not the place. We've built this community on mutual respect and it's our job to protect that.
    If you feel offended by something you read on XDA, please just report it and do not respond to it yourself. Unless you're confident it can be part of a civil and respectful conversation, and doesn't go off topic too far. Also note that what you may perceive as offensive is not always meant that way. I deeply urge you all to search for the good in people instead of assuming the worst. Thanks!

    Need to talk about this? Feel free to contact me by PM. Do not discuss this in the thread.

    Cheers and stay safe!
    Timmy
    Forum Moderator
    2
    Try that.
    Someone from this forum posted this in another thread.
    2
    This is basically the fastboot commands that i used to flash the global rom:

    Code:
    .\fastboot flash boot boot.img
    .\fastboot flash dtbo dtbo.img
    .\fastboot flash modem modem.img
    .\fastboot --disable-verity flash vbmeta vbmeta.img
    .\fastboot --disable-verity flash vbmeta_system vbmeta_system.img
    .\fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
    .\fastboot reboot fastboot
    .\fastboot flash abl abl.img
    .\fastboot flash aop aop.img
    .\fastboot flash bluetooth bluetooth.img
    .\fastboot flash cpucp cpucp.img
    .\fastboot flash devcfg devcfg.img
    .\fastboot flash dsp dsp.img
    .\fastboot flash engineering_cdt engineering_cdt.img
    .\fastboot flash featenabler featenabler.img
    .\fastboot flash hyp hyp.img
    .\fastboot flash imagefv imagefv.img
    .\fastboot flash keymaster keymaster.img
    .\fastboot flash multiimgoem multiimgoem.img
    .\fastboot flash my_carrier my_carrier.img
    .\fastboot flash my_company my_company.img
    .\fastboot flash my_engineering my_engineering.img
    .\fastboot flash my_heytap my_heytap.img
    .\fastboot flash my_manifest my_manifest.img
    .\fastboot flash my_preload my_preload.img
    .\fastboot flash my_product my_product.img
    .\fastboot flash my_region my_region.img
    .\fastboot flash my_stock my_stock.img
    .\fastboot flash odm odm.img
    .\fastboot flash oplus_sec oplus_sec.img
    .\fastboot flash oplusstanvbk oplusstanvbk.img
    .\fastboot flash product product.img
    .\fastboot flash qupfw qupfw.img
    .\fastboot flash qweslicstore qweslicstore.img
    .\fastboot flash shrm shrm.img
    .\fastboot flash splash splash.img
    .\fastboot flash system system.img
    .\fastboot flash system_ext system_ext.img
    .\fastboot flash tz tz.img
    .\fastboot flash uefisecapp uefisecapp.img
    .\fastboot flash vendor vendor.img
    .\fastboot flash vendor_boot vendor_boot.img
    .\fastboot flash vm-bootsys vm-bootsys.img
    .\fastboot flash xbl xbl.img
    .\fastboot flash xbl_config xbl_config.img
    .\fastboot flash -w
    .\fastboot reboot


    Before you proceed with the flashing, you need to enter into bootloader mode and ensure the active partition is on slot b. And make sure NOT to relock the bootloader after flashing the global rom.
    2
    From what I can gather form the internet, these are the steps for switching from china rom to global rom:

    1) unlock bootloader

    The steps can be found in here:



    and here:

    https://forum.xda-developers.com/t/...ol-based-on-realme-ui-2-0-android-11.4306223/

    2) download stock global rom and extracting the img files by using payload dumper

    The stock rom can be downloaded here:

    https://www.youtube.com/redirect?ev...X/RMX2202_ROLL%20BACK_Android11_EUEX_0609.zip

    After downloading the stock rom, you can extract the img files by using the payload dumper method. The steps are as follows (refer to step 2 until 6 of the link below):

    https://www.thecustomdroid.com/oneplus-factory-image-creation-guide/

    3) Flashing the img files via fastboot command

    In order to flash the img files, you need to enter fastboot command to execute the flash. Stelsinki and bonecrusher2010 tried to flash the img files but in vain.

    This is where it gets tricky. From my reading on this website, only 2 users have claimed to successfully flashed into global rom, MrVeverything and rakoncwy.

    If you noticed, MrVeverything has the same username as per this youtube video being referred on numerous occasions, so I assume he is the poster of the video. Even rakoncwy referred the same video as his guidance to flash the global rom. The only problem is that the video did not show the process of flashing the img files into the phone. The video only started by showing the phone after being flashed with global rom. And the description of the video does not disclose the full fastboot command being used to flash the global rom.

    Rakoncwy said you need to know which slot of the device in order to flash the rom. I am not sure what he meant but I assume that you need to flash on the active slot. Based on my reading here, the fastboot command used by bonecrusher2010 should automatically flash into the active slot, rather than setting it manually as suggested by rakoncwy earlier. Be that as it may, it was still unsuccessful.

    So in summary, the only missing steps here are the fastboot commands that can successfully flash the global rom. As only both MrVeverything and rakoncwy managed to flash into global rom, perhaps they can share with us the fastboot command they used here.

    Let me know if I miss anything here.