yashsingh1/xdaforums huggingface dataset:
[Realme X2 Guides, News, & Discussion] bino_mat:
fastboot flash recovery stock-recovery.img with stock recovery given int he first page . is this what not working for you ?

If so what is the error coming in the terminal.
[Realme X2 Guides, News, & Discussion] louai rabia:
no, it's not working for me. flashing the recovery file using fastboot gives me an error message.

it gives me a message saying: Error can't load 'recovery.img' : No such file or directory.
[Realme X2 Guides, News, & Discussion] bino_mat:
before this command ,can you share what's been printed when you type fastboot devices

and also you are sure that stock recovery downloaded in kept in the same directory with the name stock-recovery.img
[Realme X2 Guides, News, & Discussion] louai rabia:
I fixed the problem and flashed the given v.a14 recovery, my mistake was not putting the recovery file in the adb folder in C:/ computer partition.

Now, the phone keeps on booting to the stock recovery, even though I flashed the latest stock firmware RMX1991_11_A.14 from the link given.

How can I fix this?
[Realme X2 Guides, News, & Discussion] yakovpol:
Most likely you simply need to wipe data
[Realme X2 Guides, News, & Discussion] yakovpol:
It looks like you missed (or did not succeed) with

fastboot flash --disable-verification vbmeta vbmeta.img

Some had reported that old version of fastboot utility is not able to perform the command. It should finish without errors.
[Realme X2 Guides, News, & Discussion] amit000in:
can u share Stock recovery A17 for RMX1992??
[Realme X2 Guides, News, & Discussion] bino_mat:
Just curious - Is this the same vbmeta.img we get it as part of the OZIP file ?
[Realme X2 Guides, News, & Discussion] louai rabia:
Thank you very much, it's working proberly now.

I followed your steps one by one and my device is finally rooted, thanks to you.

but what does "having Magisk out of Core Only Mode" mean? and its two steps aren't working for me.

First: I don't know how to mount SYSTEM in RW mode.

Second: whenever I give the command adb shell "cat /system/build_19771.prop >> /system/build.prop"

adb says: "can't create /system/build.prop: Read-only file system" why is that?

---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------

Yes, exactly and again it worked for me thanks to you.
[Realme X2 Guides, News, & Discussion] amit000in:
Which device u had tried with A17

RMX1993 or RMX1992.

Or vise versa

---------- Post added at 10:17 AM ---------- Previous post was at 09:43 AM ----------

pls. someone can extract A17 Version stock Recovery From RMX1992 A17 OZIP File & Share here ( since I am not much familiar with Linux & dont have linux installed) have windows system only
[Realme X2 Guides, News, & Discussion] bino_mat:
Sorry that I didn't try out the option of going back to A17 - Since A19 came out - It's about RMX1992
[Realme X2 Guides, News, & Discussion] AlAneed:
Can you please update the stock recovery for the new C12?
[Realme X2 Guides, News, & Discussion] yakovpol:
It is already updated
[Realme X2 Guides, News, & Discussion] David Stone:
can you please share a working method for downgrading of rmx 1992 from realme ui v1.0 to color os

last time i flashed realme ui and my device soft bricked and now i tried everything and yet it's showing just realme logo for 10 sec and then reboot itself into recovery.
[Realme X2 Guides, News, & Discussion] yakovpol:
In this particular case most likely you need to wipe or (if it did not help) format data.

But it you are starting from the beginning, simply follow the procedure from the first post, I did my best to explain what you have to do. For specific questions feel free to ask.
[Realme X2 Guides, News, & Discussion] Sagar msali:
I want a new updates realme x2 1993ex_11_A.19
[Realme X2 Guides, News, & Discussion] David Stone:
sir i did everything, ( it's not sequence of what i did, each line is separate)

=>flashed stock recovery and then installed ver. A.19 - not worked

=>flashed twrp wipe data, system, storage and cache - not worked

=>intall realme ui via twrp flash - not worked

=>install realme ui via stock recovery of A.19 - not worked

=>restored my saved twrp fully backup after wiping everything - not worked

=>flashed fastboot images of realme x2 to unbrick it - not worked

in every case my device will boot up to white realme logo for 10 sec. and then reboot to recovery itself

tell me if i missed something .

NOTE:- i did nothing special just flashed directly (without wipe) realme ui v1 over color os A19 via twrp . and after succesfully flashing this problem came out . after this i tried every way of flashing but did not succeed .
[Realme X2 Guides, News, & Discussion] Lemmy554:
I´d exactly the same issue (white realme logo for 10 sec. and then reboot to recovery itself) if I want to turn back to COS. These are the steps who worked for me:

1. Flash vbmeta from fastboot

2. Flash recovery from fastboot

3. Boot into TWRP

4. Wipe Dalvik/Cache, Cache, System, Data, Internal storage - incl. Vendor!

5. Flash ozip

6. Reboot into system

Hopefully they´ll work for you also ;)
[Realme X2 Guides, News, & Discussion] David Stone:
bro i'm on rmx 1992 indian variant bootloader unlocked rooted magisk out of core mode

first of all i'm talking about downgrading from realme ui to color os which i had dirty flashed via twrp and the problem comes out. ( i still don't know how to install realme ui in my device in working stage also) but that's not the issue, i wiped everything and did everything to get my device boot up.

and now back to your point

you said wipe everything inc vendor

i did, i said in earlier post that i wiped everything and then restored from twrp

and twrp backup vendor image also

that means i wiped everything and restored everything inc vendor

and about vbmeta

flashed it along with twrp , as we know device won't boot if not flashed
[Realme X2 Guides, News, & Discussion] yakovpol:
Well, thank you for the list of all your attempts.

Only the first string corresponds to the procedure explained in the first post of this thread (flashed stock recovery and then installed ver. A.19 - not worked).

If you are saying in this case also it did "not worked" and need some help, please tell in details the result (output) of all 7 steps from the original procedure. For example, this thread does not provide A.19 stock recovery. It means you deviated somewhere from the procedure.
[Realme X2 Guides, News, & Discussion] David Stone:
sir, hope you understand my problem that how my device get bricked

now back to point

i downloaded stock recovery A18 from your first post

then i flashed it successfully

then i have A.19 ozip file

and flashed it successfully

then rebooting device and it showing realme logo for 10 second and then reboot to recovery itself

then i flashed twrp and did everything i have told before

wiping and restoring etc

i just want to know is downgrading works from realme ui to color os by using ozip file
[Realme X2 Guides, News, & Discussion] yakovpol:
First of all, the procedure for downgrade is tested. I worked for me and for some other folks as well.

You say you have bricked (or, in older post, 'soft bricked') the device. Flashing wrong images through fastboot mode can damage your phone so that only the official service can help you then: currently there's no flash tool available for realme devices, and there's no programmer available for using Qualcomm Download Mode (aka 9008 mode) for RMX199x. So it is out of this thread theme :(

If you can boot fastboot mode and flash stock recovery, then what is written in the first post is applicable to your phone.
[Realme X2 Guides, News, & Discussion] wildnanus:
same things here!!

I stuck in bootloop!!

need solution
[Realme X2 Guides, News, & Discussion] yakovpol:
If you can enter fastboot mode, simply follow the procedure from the first post of this thread.
[Realme X2 Guides, News, & Discussion] wildnanus:
after several attempt it worked!!

Thanks.
[Realme X2 Guides, News, & Discussion] Anh_Dinh:
Fingerprint still work while bootloader unlocked, should I lock it?

Hi I'm new here, my first post as well.

After having tried all the custom roms, I followed exactly the steps mentioned in the first post and could come back to the stock rom (Chinese version).

But I found out that finger print is still working, even now when my bootloader is till unlocked. This is strange because I heard that finger print does not work on stock rom with unlocked bootloader. So my question is: should I lock the bootloader now? Will it brick my phone? (someone from previous posts bricked his phone so I'm quite worried).

Thanks a lot in advance and especially for the original instructions.
[Realme X2 Guides, News, & Discussion] yakovpol:
Do not lock bootloader.

Rejoice that everything works right for you.

Currently only realmeUI ROMs (not Android 9/ColorOS ones) have problem with FP when vbmeta is patched.
[Realme X2 Guides, News, & Discussion] Anh_Dinh:
The phone has updated to Realme UI, RMX1991_11_C.13, bootloader unlocked but FP still working.

Quite strange but I'll enjoy that for now. Hope that another OTA update will not brick my device..
[Realme X2 Guides, News, & Discussion] DoYouWantFriesWithThat:
[MENTION=5453333]yakovpol[/MENTION] hi, I wrote you in private when I was desperate (bootloop, caused by flashing Magisk without vbmeta & flashing boot partition as a wrong fix). Since I didn't want to bother you, I followed your guide and I rolled-back.

Here's what I did:

1) from TWRP format data + wipe system, cache, dalvik/cache, internal storage .

2) via Fastboot flash stock Recovery.

3) flash OZIP from the stock Recovery.

My situation now is:

1) Unlocked Bootloader + stock rom working (v. ROMRMX1993EX_11.A.16)

2) Fingerprint not working (when I try to add a Fingerprint the screen starts flickering and doesn't let me add it).

From this situation, can you suggest me a path to have a working system (stock or custom rom), with root (via Magisk), and with a working fingerprint ?
[Realme X2 Guides, News, & Discussion] yakovpol:
According to my understanding (and all this is not documented by Realme), Realme X2's FP breaks during BL unlock on early stock ROMs (on early ColorOS ROMs and on early realmeUI ROMs). If FP is broken, only locking BL again will put it back to life :) So then in your case you should lock BL and then unlock it again on a ROM

which is known as leaving FP working

. I cannot tell for sure what will be the ROM version for EU model that you have. For sure latest released ColorOS ROM makes it right. As soon as you have your bootloader unlocked and FP works right there is probably no reason to lock it again :) Everything on stock ROMs works right, including OTA updates. And you have the way open for blocking AVB by patching vbmeta and custom ROM installation.

A word of caution. Be extremely careful when locking your BL. If you have non-stock boot, system, recovery or vbmeta, there will be a hard brick. Read last part of the post #1 in this thread.

Another note would be to double check Magisk version you are going to install. Quite a number of custom ROMs work only with Magisk 20.3 and do not with 20.4.
[Realme X2 Guides, News, & Discussion] DoYouWantFriesWithThat:
Great point!!! Then my bootloop was probably caused by 20.4 :(

Here is a simple way to verify the restored stock rom for those who want to be safe.

1) flash TWRP

2) make a full backup of the phone (except the recovery, obviously) and move the backup to, say, /TWRP/backup

3) With your stock-rom OZIP file (ex: RMX1993EX_11_OTA_0160_all_bEdlmdxqYETs.ozip) in the current directory do the following:

# ozipdecrypt.py RMX1993EX_11_OTA_0160_all_bEdlmdxqYETs.ozip
# mkdir ./RMX1993EX/
# unzip RMX1993EX_11_OTA_0160_all_bEdlmdxqYETs.zip -d ./RMX1993EX/
# cd ./RMX1993EX/
# brotli -d system.new.dat.br
[large output]
# sdat2img.py system.transfer.list system.new.dat system.img
[large output]
# brotli -d vendor.new.dat.br
[large output]
# sdat2img.py vendor.transfer.list vendor.new.dat vendor.img
[large output]

Now proceed to compare the contents of your phone with the TWRP backup, like so:

# sha256sum system.img
5530f966fd02b25fbad7de7c8a01a5389803ff79d36a71bb6415fe6f243e4bdb system.img
# cat /TWRP/backup/system_image.emmc.win.sha2
5530f966fd02b25fbad7de7c8a01a5389803ff79d36a71bb6415fe6f243e4bdb system_image.emmc.win

# sha256sum vendor.img
74864be062047d04e88cbaf385fe15b97cf32d2acfa9f8611c60e5b8b1e26805 vendor.img
# cat /TWRP/backup/vendor_image.emmc.win.sha2
74864be062047d04e88cbaf385fe15b97cf32d2acfa9f8611c60e5b8b1e26805 vendor_image.emmc.win

In order to verify that the recovery is also of exactly the right version as your ROM (if you installed the recovery before) you can mount system.img and extract /system/recovery-from-boot.p. Then you can do:

# bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
# sha256sum selfmade_stock_recovery.img
00fd45f66fa86bddb66655ef33f388c5f25dfb1171a85989f97b466e56171b91 selfmade_stock_recovery.img
# sha256sum ../stock-recovery-rmx1993-a16.img
00fd45f66fa86bddb66655ef33f388c5f25dfb1171a85989f97b466e56171b91 ../stock-recovery-rmx1993-a16.img

Notice the hashes are the same.

Optionally, you can check the hashes into ./RMX1993EX/firmware-update/, and they will be equal.

NOTE: don't forget to reflash the stock-recovery :)

IMPORTANT: TRY THE ROM AND CHECK THE FINGERPRINT (before formatting data again). IF THE FINGERPRINT IS NOT WORKING DO NOT RELOCK THE BOOTLOADER LEST YOU BREAK YOUR DEVICE!!!

Watch: https://www.youtube.com/watch?v=s4aGWdTDPwg
[Realme X2 Guides, News, & Discussion] yakovpol:
Well, tastes differ...

To me the simplest way to check if everything is okey would be to flash stock vbmeta and then boot system and recovery.

Also after some tough experience with official TWRP on Xiaomi A2 lite I do not fully trust TWRP if it leaves partition untouched during backup.

EDIT BTW, would be easier to checksum on place (inside custom recovery):

# for system partition:
dd if=/dev/block/sda7 | sha256sum
[Realme X2 Guides, News, & Discussion] DoYouWantFriesWithThat:
[MENTION=5453333]yakovpol[/MENTION] you could add the information contained in this video ( https://www.youtube.com/watch?v=s4aGWdTDPwg ) to the beginning of this thread.

It seems that if the bootloader is relocked, no matter the state of the ROM, it will break the device as long as the fingerprint is not working in the ROM.

I didn't relock mine. I'll do it only when I have a working fingerprint (now I run the stock ROM and it still doesn't work).
[Realme X2 Guides, News, & Discussion] yakovpol:
I personally successfully unlocked and locked the BL of my device about 5 times. What is mentioned in the video is evident: if you have rooted phone, do not lock BL, it results in a brick.

The whole idea of this thread is to come back to pure stock ROM, without root or other modifications.
[Realme X2 Guides, News, & Discussion] DoYouWantFriesWithThat:
You are right, but in some cases (like mine) the fingerprint will not work even after restoring a stock rom (without rooting).

The realme X2 Pro threads are full of people that had the Fingerprint broken just after unlocking the Bootloader, without rooting.

Please take that into consideration.
[Realme X2 Guides, News, & Discussion] yakovpol:
Up to you to decide :)
[Realme X2 Guides, News, & Discussion] frozenxuan:
After flashing the stock recovery image (C14), attempt to boot into recovery mode using either volume button or computer command will just boot into fastboot mode again. I previously flashed C16 vendor image and patched vbmeta (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img), could these the reason for this problem?
[Realme X2 Guides, News, & Discussion] yakovpol:
You do not say about the way you flashed ”stock recovery image (C14)“. The way described in this thread is a use of stock recovery and full stock image (ozip file). It will rewrite all mentioned partitions. But it looks like your recovery is not successfully rebuild by the stock ROM after being flashed. Thus follow closely the procedure from this thread again.
[Realme X2 Guides, News, & Discussion] yakovpol:
A word of warning regarding ozip file

I have discovered that the files pulled out from OTA update process (and which are located in /data/oppo/coloros/OTA/.otaPackage/ ) are not identical to those on the official web site with updates (say https://www.realme.com/support/software-update). For example, I have two files:

~ md5sum RMX1991_11_OTA_1140_all*
70db6638e138be8d328ad7e49b60202f RMX1991_11_OTA_1140_all_p1Z4tROJMLm1_4f7a1e38.ozip
ebaeb8074e174903edcc44824c1d430c RMX1991_11_OTA_1140_all_p1Z4tROJMLm1.ozip
~ ls -l RMX1991_11_OTA_1140_all* | awk '{print $5, $9}'
2980204947 RMX1991_11_OTA_1140_all_p1Z4tROJMLm1_4f7a1e38.ozip
2980204940 RMX1991_11_OTA_1140_all_p1Z4tROJMLm1.ozip

The file with a longer name is OTA one, the shorter one is from the official site. I could not install first one using the procedure from this thread on my phone; the file is taken from another guy's phone. But the file from official support site was installed as it should.

Files evidently differ (size, name, check sum). Seems that stock recovery does not accept an OTA file downloaded to another phone.
[Realme X2 Guides, News, & Discussion] th3_gunn3r:
thanks
[Realme X2 Guides, News, & Discussion] naveen000can:
i seriously f**** up please some one help i tried a stock recovery i didnt know which version for correct for mine so i flashed one from rmx1991 and it installed than from it i tried to flash a16 ozip file of rmx1991 it displayed everything fine but without booting up it kept going to bootloader so outof frustration there was a root option i dont rememember the full name but i tried it and phone is not even turning on please help me anyone please
[Realme X2 Guides, News, & Discussion] yakovpol:
Try to boot into fastboot mode. If you succeed, then simply follow the first post from this thread, but strictly for your model (RMX199 1/2/3).

The key combination to force the power off is VolumeUp+Power, press and hold them for about 5-8 seconds.

You did not provide any details about "root option", so it is difficult to guess what you have done with the phone.
[Realme X2 Guides, News, & Discussion] xGormo:
Hello guys,

I'm kind of stuck right now. After unlocking the BL, installing OrangeFox and a custom rom I wanted to go back to stock. The thing is even after putting the ozip file on the internal storage and flashing the stock recovery I cannot access the internal storage. When you get to the stock recovery after selectiong your language, instal from internal storage but when trying to select this option doesn't do anything... If you guys have any idea...
[Realme X2 Guides, News, & Discussion] yakovpol:
If you do not see contents of your internal storage then most likely your custom ROM used different format for it. Another reason could be that recovery is too old. Simply use SD-card for the process.
[Realme X2 Guides, News, & Discussion] Anz85:
I'm lost.

Hi. Just got my x2 rmx1991. I not accidentally upgrade to android 10 and realme ui v1. 0.

I try to read the 1st 2 post of this thread to downgrade back to android 9 and color os.

But it's a bit confusing for me and I'm Abit worried.

Is it a step by step process? Cause I couldn't figure out whether to download files to computer or my x2.

Can someone help me please? Thank you so much..
[Realme X2 Guides, News, & Discussion] yakovpol:
There's no need to downgrade to ColorOS now: all custom ROMs are on realmeUI vendor now. Simply install the latest version of ROM, unlock bootloader, and install custom ROM you like.
[Realme X2 Guides, News, & Discussion] mhneel:
Stock Rom Problem

I installed the stock recovery A.17, but the can't install the OZIP file. It just says install failed. Can anyone help me please? I'm stuck for 2 days now
[Realme X2 Guides, News, & Discussion] David Stone:
Don't worry

Just wipe data in recovery and then try again, it will wipe your internal storage,
[Realme X2 Guides, News, & Discussion] ade.sultan:
Can you please provide the recovery for the RMX1991_11.C.20 version? It's the only ozip I could find and I'm too noob to pull out a working recovery myself
[Realme X2 Guides, News, & Discussion] yakovpol:
You are welcome. I have uploaded C20 stock recovery to Gdisk.

Please note that you could use older recovery versions as well as very first post explains in paragraph 4.
[Realme X2 Guides, News, & Discussion] ade.sultan:
Thanks, I found it later and succeeded installing the latest rui using and older recovery. As you explained, after the installation, the recovery updated itself. Good guide bro, thanks a lot...
[Realme X2 Guides, News, & Discussion] Vega56:
Well, i think i bricked my RMX1993. :(

the current image(boot/recovery) have been destroyed

Not a chance to get into Fastboot. Bootloop with this Message.

EDIT: My Phone is working again. Thanks to Gsmmafia.

They connected via Teamviewer and have solved the Problem. I am so happy. Great Support.

When you have the same Problem, they can help you 100 %.
[Realme X2 Guides, News, & Discussion] Vega56:
Hello again,

have anynone a Stock Recovery for RMX1993EX_11.C.07 ?

Thank you.
[Realme X2 Guides, News, & Discussion] yakovpol:
You have an option to produce it yourself, read my post on February 25 in this thread.
[Realme X2 Guides, News, & Discussion] Vega56:
Thank you.

But i tried this with sdat2img.py the past two Days.

With different Tools.. its not working for me ?
[Realme X2 Guides, News, & Discussion] Vega56:
Thats what i get.

Traceback (most recent call last):
File "C:\Users\marku\Downloads\sdat2img.py", line 143, in <module>
main(TRANSFER_LIST_FILE, NEW_DATA_FILE, OUTPUT_IMAGE_FILE)
File "C:\Users\marku\Downloads\sdat2img.py", line 68, in main
version, new_blocks, commands = parse_transfer_list_file(TRANSFER_LIST_FILE)
File "C:\Users\marku\Downloads\sdat2img.py", line 38, in parse_transfer_list_file
version = int(trans_list.readline())
ValueError: invalid literal for int() with base 10: 'OPPOENCRYPT!'
[Realme X2 Guides, News, & Discussion] yakovpol:
Well done.

Please note you can use older stock recovery to flash current ROM (see 4th paragraph of the very first post of this thread). For example, to flash C.07 ROM you can take C.05 recovery which was uploaded a while ago. BTW, new C.08 ROM is out for RMX1993, I uploaded its recovery to the same place.
[Realme X2 Guides, News, & Discussion] yakovpol:
It seems new ROMs have built-in downgrade protection. At least today I could not downgrade from partially installed C.23 to C.22 while having C.22 recovery.
[Realme X2 Guides, News, & Discussion] sharazkhan65:
Problem_ the current image have been destroyed and can not boot

Dear friend I m using realme x2(rmx1992)

Last 3days I try bootloader unlock my device successfuly but phot not boot plzz help me
[Realme X2 Guides, News, & Discussion] sharazkhan65:
Display message (the current image have been destroyed and can not boot)

Any solution on this condition
[Realme X2 Guides, News, & Discussion] warkraft7805:
Всем доброго, подскажите кто в курсе поменял на европейской прошивке RMX1993EX с.12 регион поставил магазин тем, запись звонков, загрузчик не разблочил рут не ставил, пропала оплата по NFC пишет что-то про не сертификацию как побороть?
[Realme X2 Guides, News, & Discussion] Morphine1:
I flashed the stock recovery n stock rom on a RMX1993 Realme X2 that I had rooted already with TWRP.

Everything was fine, till I got the great idea on relocking the bootloader.

As soon as I put the command the device reboot and showed that message with chinese letters n "recovery/boot has been destroyed" etc.

Got no fastboot either, only com port EDL mode works. The next and main problem is I am not authorized to flash roms due to that user/pw in msm tool. I just found this out after bricking the device. Why the hell did I lock the bootloader....

I heard there are websites that offer user/password for msm tool flashing n you need to buy credits for it. I'm not gonna bother nor paying for something that I own and should have the right to fix by myself. Amaz0n will take care from it this time, they'll probably refund.

Tip: Do not relock bootloaders,

and a better one: do not buy realme devices.

Good thread though, thanks for the op.