[GUIDE] Back to stock ROM howto / Downgrade howto

Search This thread
By:
Advanced…
V

Vega56

Senior Member
May 27, 2020
176
75
Xiaomi Poco F4 (Munch) / Redmi K40s
yakovpol said:
You have an option to produce it yourself, read my post on February 25 in this thread.
Click to expand...
Click to collapse

Thats what i get.

Code: 
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!'
 
Y

yakovpol

Senior Member
Sep 23, 2013
278
128
Realme X2
Vega56 said:
Thats what i get.

Code: 
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!'
Click to expand...
Click to collapse

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.
 
Last edited:
Y

yakovpol

Senior Member
Sep 23, 2013
278
128
Realme X2
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.
 
S

sharazkhan65

New member
Apr 20, 2017
3
0
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
 
S

sharazkhan65

New member
Apr 20, 2017
3
0

Attachments

  • IMG_20210208_211953.jpg
    IMG_20210208_211953.jpg
    1.1 MB · Views: 24
warkraft7805

warkraft7805

New member
Mar 30, 2018
1
0
Всем доброго, подскажите кто в курсе поменял на европейской прошивке RMX1993EX с.12 регион поставил магазин тем, запись звонков, загрузчик не разблочил рут не ставил, пропала оплата по NFC пишет что-то про не сертификацию как побороть?
 
Morphine1

Morphine1

Senior Member
Sep 23, 2014
488
669
Andalusia.
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.
 
Last edited:
Y

yakovpol

Senior Member
Sep 23, 2013
278
128
Realme X2
Well, after quite long time I am back to my beloved RMX1991, upgraded it to its final OTA version F26 (Android), and this is what I see ;-(
- There's no free way to get mainland China IP address (in order to check for any additional updates)
- There's no recoveries suitable for this stock Android 11 ROM (above mentioned F26)
- There's no any visible development activity for the device
- There's no manufacturer's support for the device any more (for more than a year already)
- There's no probably something else what I did not check so far :)

So I found out that the only way to have custom ROM on the device is downgrading it back to C-line (Android 10) ROM. And it is possible indeed!

EDIT 2023-01-07:
- I found a couple of custom recoveries working with stock Android 11 ROM, they cannot decrypt data
- It is possible to flash custom recovery from stock Android 11 ROM
- There were major changes between F20 and F26 ROM versions. F26 is native ZIP file now, while F20 is OZIP.

Here is a way to do it:
(the main idea is based on using stock recoveries and step-by-step downgrade, I used F26 -> F20 -> C27 path. )
(I am going to fill up the post in the next few days)
 
Last edited:
HeftyMidnight12

HeftyMidnight12

New member
Jan 7, 2023
2
0
yakovpol said:
Well, after quite long time I am back to my beloved RMX1991, upgraded it to its final OTA version F26 (Android), and this is what I see ;-(
- There's no free way to get mainland China IP address (in order to check for any additional updates)
- There's no recoveries suitable for this stock Android 11 ROM (above mentioned F26)
- There's no visible development in any way activity for the device
- There's no manufacturer's support for the device any more (for more than a year already)
- There's no probably something else what I did not check so far :)

So I found out that the only way to have custom ROM on the device is downgrading it back to C-line (Android 10) ROM. And it is possible indeed!

Here is a way to do it:
(I am going to fill up the post in the next few days)
Click to expand...
Click to collapse
Hello and a Happy New Year.
Can you tell us how you did it?
 
HeftyMidnight12

HeftyMidnight12

New member
Jan 7, 2023
2
0
yakovpol said:
Well, after quite long time I am back to my beloved RMX1991, upgraded it to its final OTA version F26 (Android), and this is what I see ;-(
- There's no free way to get mainland China IP address (in order to check for any additional updates)
- There's no recoveries suitable for this stock Android 11 ROM (above mentioned F26)
- There's no any visible development activity for the device
- There's no manufacturer's support for the device any more (for more than a year already)
- There's no probably something else what I did not check so far :)

So I found out that the only way to have custom ROM on the device is downgrading it back to C-line (Android 10) ROM. And it is possible indeed!

EDIT 2023-01-07:
- I found a couple of custom recoveries working with stock Android 11 ROM, they cannot decrypt data
- It is possible to flash custom recovery from stock Android 11 ROM
- There were major changes between F20 and F26 ROM versions. F26 is native ZIP file now, while F20 is OZIP.

Here is a way to do it:
(the main idea is based on using stock recoveries and step-by-step downgrade, I used F26 -> F20 -> C27 path. )
(I am going to fill up the post in the next few day
Click to expand...
Click to collapse
hey, did you forget us?
i am really trying to downgrade and unlock the bootloader.
I have big problems with the Google Chrome App ( like 60% Battery drain in 1 Day) which is a System App i cant delete.
Please Help :(
 
You must log in or register to reply here.

Similar threads

Y
[GUIDE] Root howto
Replies
111
Views
24K
euplio
euplio
Y
[GUIDE] GSI (Generic System Image) howto
Replies
39
Views
10K
beeduq
beeduq
Y
[GUIDE] Speeding up ColorOS RMX1991 update outside mainland China howto
Replies
15
Views
7K
E
elias_castro
Y
Recovery/fastboot/download modes howto
Replies
19
Views
8K
S
Sanuroy05
T
Unlock and root already? Woo hoo!
Replies
126
Views
19K
B
Big Boy

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 10
    Y
    yakovpol
    There maybe a number of reasons to go back to the stock ROM. We do not discuss them here :)
    But what to do if you flashed something, wanting to go back to stock, and did not brick your Realme X2 yet? :) Here is super quick howto guide. There are other possible ways and sequences to perform the task, but the one listed below is tested.

    The same procedure applys for a case when you want to downgrade you phone (when its bootloader unlocked). Say, current custom ROMs are based on ColorOS 6.1/Android 9 vendor contents but you have realmeUI/Android 10 already. In order to try one of those custom ROMs you should downgrade to the latest Android 9 stock firmware first.

    The essential part of the customized phone is custom recovery. Currently Realme OZIP file does not contain stock recovery inside. It is being generated as explained below, in the post #2, see EDIT3. It means you need to find somewere PROPER stock recovery corresponding to your ROM to put it back. See Realme X2 stock recovery links below, post #2, EDIT4.

    Which stock recovery to use? The one for your model and which version is not newer than the ROM version you are flashing. For example, you need A.17 stock ROM for CN model (RMX1991). Then any recovery of A.12, A.14, A.16, A.17 for RMX1991 will work for you.

    1. Download and unzip the stock recovery partition image from the next post, this will be a file like rmx1991-sde20-stock_recovery.img.
    2. Download stock ROM ozip file (for example, from here). Put it to a SD card with a filesystem which supports files more than 2GB (ext4 works fine. Stock recovery, but not ColorOS, supports it). Put the SD card into the phone.
    3. Start (reboot) phone into fastboot mode
    4. From a computer perform fastboot flash recovery rmx1991-sde20-stock_recovery.img
    5. From the fastboot mode by means of volume buttons select 'Recovery mode' and push Power button
    6. From the stock recovery select language needed (there are three only), then 'Install from storage device', then 'From SD card', tap the OZIP file with your ROM
    7. When the update process is done, phone reboots. Most likely, it will not be able to boot normally because you need to wipe out data. Either help the phone with keeping Vol Down button pressed during reboot, or it will boot recovery by itself. Now wipe data (confirm by entering random 4-digit code), select 'Format data'. Phone will reboot
    Here it is. Enjoy (or sell :) your Realme X2 with its shiny stock experience...

    If you want to lock bootloader after all above mentioned steps (you have to make them all unless you wanna get a brick :) ), boot fastboot mode, perform fastboot flashing lock. This will wipe your data again. Then optionally lock 'OEM Unlock' option in 'Developer Options'. Even further, you can install In-DepthTest.apk and sign out from In-Depth Test program.

    2022-12-25 EDIT: For downgrade from Android 11 to 10 read this post
    View
    6
    Y
    yakovpol
    I have found out that in fact stock recovery does not exist as a prebuilt file :) It is being created by the script /system/bin/install-recovery.sh on a basis of stock boot partition and a patch file /system/recovery-from-boot.p
    It means in theory you can recreate stock recovery having only Realme ozip file.

    EDIT1 The command to do it in Linux shell is
    Code: 
    bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
    Cool! Tested.

    EDIT2. For the current moment when unlocked bootloader breaks fingerprint sensor: as soon as the bootloader is locked again, fingerprint starts functioning as it should.

    EDIT3 Becomes clear that each ROM release has its own stock recovery which is generated automatically on the basis of boot.img and recovery-from-boot.p . Not only boot.img is being changed each release, but recovery-from-boot.p is changing as well. If the wrong stock recovery is installed, you might not be able to decrypt data and connect to WiFi from within recovery. Seemingly it may bring you serious problems if locking back bootloader (thus bricking the device). Good thing (as I understood, but not checked yet) is that after flashing stock ROM with a help of a stock recovery next reboot should replace your stock recovery with an up-to-date version of it. So to be on a safe side make sure that you rebooted to system and that your recovery reflashed by the system before you lock bootloader.

    EDIT4 In order to combine everything in one place:
    • Stock recoveries for RMX1991 (China version): here
    • Stock recoveries for RMX1992 (India version): here
    • Stock recoveries for RMX1993 (Euro version): here
    EDIT5 In later ROM releases patch and script files are relocated into vendor partition, they are /bin/oppo-install-recovery.sh and /recovery-from-boot.p there.

    EDIT6 Please note that the method above is working with officially downloaded ROMs from realme support site (read here why).
    View
    2
    Y
    yakovpol
    DoYouWantFriesWithThat said:
    @yakovpol 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 ?
    Click to expand...
    Click to collapse

    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.
    View
    1
    switchgott
    switchgott
    Hi,
    does only works with SDcard insert.
    Because the internal storage is decrypted.
    And it does not work on X2.
    But why?
    Installation failed?
    View
    1
    Y
    yakovpol
    ade.sultan said:
    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
    Click to expand...
    Click to collapse

    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.
    View

New posts