Thanks for letting me know mate! And I've had the same on 501 today, so it looks like they at least fixed one thing!The animation scale stayed at 0.5 all day. The reset was done only by exiting developer mode.

Thanks for letting me know mate! And I've had the same on 501 today, so it looks like they at least fixed one thing!The animation scale stayed at 0.5 all day. The reset was done only by exiting developer mode.
I spoke too soonThe animation scale stayed at 0.5 all day. The reset was done only by exiting developer mode.
What do u mean by exiting developer mode?The animation scale stayed at 0.5 all day. The reset was done only by exiting developer mode.
By disable developer mode I meant disable. After activating the developer mode, the animation scale already had a standard value of 1. So, in my case, the animation scale held during the whole day of testing a value of 0.5.What do u mean by exiting developer mode?
Did u disable/activate developers options and animations stayed 0.5x as u has chosen ?
Wait a little longer, you can try via VPN or update manually.I just relocked bootloader after changing region, but it seems I dont received OTA anymore (C.19). Do I have to manually update onwards?
thank you I just assume the worst that I wont get OTA despite relocking the bootloader. Just decided to manually update from C.18 to C.19.
Try to installafter flash fastboot flash boot magisk.img the device not recognize in fastboot and in device of pc isn'e recogniza
the bootloader restart in start mode
fastboot --set-active=a is risght ?Android Bootloader Interface Drivers Download for Windows 10, 8.1, 7, Vista, XP
Download the latest drivers for your Android Bootloader Interface to keep your Computer up-to-date.www.driverscape.com
Already going to Install patched boot.img?
Was The wrong slotAlready going to Install patched boot.img?
adb reboot bootloader
fastboot devices (identified)
fastboot flash boot patchedboot.img
fastboot reboot
Fixed!
Yes, you can flash full OTA with root, but you have to follow the usual procedure:
If you did not have the C.21 version, the solution would be simple.Hmm ok
maybe i'm too paranoid but if you install the eu rom you should see german/austria after they sell it here too. Also I want to start from 0 so to speak
RMX3301_11_C.21_RUCan you share the link of the c21 russian version? I tried with realme-ota it seems c20 version.
You have to extract boot.img from the ROM, patch it using Magisk, and manually flash it.
adb shell getprop ro.build.oplus_nv_id
and check the result with the table at the end of the post to know if you have the export or GDPR ROM.realme-ota -r 0 RMX3301 RMX3301_11.A.00_0000_000000000000 3 00011010
simg2img super.0.xxxxxxxx.img super.1.xxxxxxxx.img super.2.xxxxxxxx.img super.img
Region | Region abbreviation | nv_id (HEX) | nv_id (BIN) | ROM type | Notes |
---|---|---|---|---|---|
Taiwan | TW | 1A | 00011010 | export | |
India | IN | 1B | 00011011 | export | |
Indonesia | ID | 33 | 00110011 | export | |
Russia | RU | 37 | 00110111 | export | |
Malaysia | MY | 38 | 00111000 | export | |
Thailand | TH | 39 | 00111001 | export | |
Philippines | PH | 3E | 00111110 | export | |
Saudi Arabia | SA | 83 | 10000011 | export | |
Latin America | LATAM | 9A | 10011010 | export | |
Brazil | BR | 9E | 10011110 | export | |
Middle East and Africa | MEA | A6 | 10100110 | export | |
Europe (EU, EEA, UK and Switzerland) | EUEX | 44 | 01000100 | GDPR | |
United Kingdom | GB | 8A | 10001010 | GDPR | 1 |
Turkey | TR | 51 | 01010001 | GDPR | |
Rest of Europe | EU-NONEEA-Double | 8D | 10001101 | GDPR | |
China | ALLNET | 97 | 10010111 | domestic |
Region | Region abbreviation | nv_id | ROM type | Android 13 (C.08) OTA URL |
---|---|---|---|---|
Taiwan | TW | 00011010 | export | e68ab4b89ac44520a56d488f4a246da6.zip |
India | IN | 00011011 | export | 4ccc3d3cb837437ea787baaac853fc4d.zip |
Indonesia | ID | 00110011 | export | d0e4792682e34b53a2beb702b03f5962.zip |
Russia | RU | 00110111 | export | c3d6a801a82b4f2893373633fd580075.zip |
Malaysia | MY | 00111000 | export | f45a2208c7d74706b2491682940b369d.zip |
Thailand | TH | 00111001 | export | d0fa5e7712f747d5beb64fb571070ffc.zip |
Philippines | PH | 00111110 | export | 29a42bbbf19a4d14a4fa06faedcf1492.zip |
Saudi Arabia | SA | 10000011 | export | ac730fcaa8704f69a846c36e9e79f822.zip |
Latin America | LATAM | 10011010 | export | |
Brazil | BR | 10011110 | export | acbda86ee1cc47d3867546f9ec5a8865.zip |
Middle East and Africa | MEA | 10100110 | export | 19fd25c0b6994a56b925296249a6d695.zip |
Europe (EU, EEA, UK and Switzerland) | EUEX | 01000100 | GDPR | 336d3d23e61d4839a2fdd21c8b9d56d7.zip |
Turkey | TR | 01010001 | GDPR | |
Rest of Europe | EU-NONEEA-Double | 10001101 | GDPR | 7631d500d3974caf8e7f189263576528.zip |
I haven't figured out how to properly install the realme-ota updater.
@echo off
setlocal
chcp 65001 2>nul >nul
cd "C:\PYTHON INSTALL LOCATION\Scripts\realme_ota\realme_ota" 2>nul >nul
if exist main.py (
python main.py %*
) else (
powershell write-host -fore Red realme-ota not found!
)
pause
C:\Python install location\Scripts\realme_ota\realme_ota
realme-ota -r 0 RMX3301 RMX3301_11.A.00_0000_000000000000 3 00011010
where realme-ota