Phone boots up, works fine, and 1 minute later powers down then boots into TWRP. If I boot up a minute later it sends me back to TWRP. I used sunshine bootloader unlock when 6.0 started getting pushed. I'm happy to try a custom ROM or stock marshmallow using minimal ADB and fastboot, or wiping it somehow. Can anyone tell me how to make my phone work without loosing root or changing TWRP versions? Work period? Thanks in advance for any light shed on my plight, I just don't know what to do. THANKS.
serifle said:
Phone boots up, works fine, and 1 minute later powers down then boots into TWRP. If I boot up a minute later it sends me back to TWRP. I used sunshine bootloader unlock when 6.0 started getting pushed. I'm happy to try a custom ROM or stock marshmallow using minimal ADB and fastboot, or wiping it somehow. Can anyone tell me how to make my phone work without loosing root or changing TWRP versions? Work period? Thanks in advance for any light shed on my plight, I just don't know what to do. THANKS.
Click to expand...
Click to collapse
Try flashing this 6.0.1 stock-based ROM:
Computerfreek274_MM_1.0.6 Marshmallow 6.0.1
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
It's debloated, tweaked version of 6.0.1 Verizon stock firmware.
Yes, you may lose root temporarily. Just re-flash this version of SuperSu, found in this post. On stock 6.0.1 or stock-based 6.0.1 ROM ONLY that version of SuperSu (BETA-SuperSU-v2.62-3-20151211162651) will work for initial root. After you re-root, THEN you can update to newest version of SuperSu.
Also, not sure why you don't want to update to newer TWRP. You don't have to... but I always do. You just flash newer TWRP within TWRP. You install it like any other file in TWRP. Choose install, then "image", then "recovery".
What version TWRP are you using. Our official TWRP maintainer @bhb27 has released TWO newer versions just in 2017 alone.
bhb27 said:
TWRP update
twrp-3.0.3-0_MOD_3-quark.img
Download
Note:
This is a pre released of 3.0.3 when all the changes are finalized I make and released a new one or when important bugs fix are released
===================
Feb-17-2016
===================
* All the previously TWRP Mod + the below
* Included the latest TWRP updates to this date
* Kernel Improves
* Latest updates and bugs Fix to the date of TWRP
* Most notable is the fix for Nougat Setting configurations be lost after the wipe of cache or a restore of the ROM Data, only new backups made on the latest MOD TWRP will have this featuring.
Any problem found report and use a old version.
Click to expand...
Click to collapse
Just wipe the cache in TWRP.
Hello, I have a problem with my Xiaomi Redmi 4X phone, as I said, I can not flash any Custom ROM for Android 8.1 All this happened after I put my phone in service to replace the display on which I've broken it. Now any version of Android 8.1 I try to flash results in a bootloop. I have to mention 3 things
1. In TWRP when flashing I noticed that all Custom ROMs are stuck in "Flashing system files ..." for a few seconds after saying that it ended flash-but did not abssolut anything.
2. Now a few hours I accidentally flashed Pixel Experince, but now I have the same problem.
3. I can not flash any versions of TWRP.Not much but...
THIS IS HAPPENING ONLY ON THE ANDROID OREO ROMs, Nougat ROMs works perfectlly
Try to flash first latest version of twrp or you can flash redwolf recovery then flash firmware v40 then try clean flash for oreo roms
As mentioned by above user...(latest TWRP recovery and firmware is must)
Flash latest TWRP recovery, 3.2.1-0 should be fine but there's update available 3.2.2.-0 so any will do.
Next, flash latest firmware.
Clean flash is must when changing OS.
It's most likely you don't have latest TWRP recovery and firmware.
Do backup first.
Hey folks i took the afford and unlocked by bootloader and flash a gsi , i noticed sound and wifi were broken and investigated then i recompiled the olive kernel with some changes hacked together a working kernel image (the sources xiaomi provided are broken)
DOWNLOADS:
AndroidFileHost
STEPS
1. unlock your bootloader
2. disable avb by reflashing vbmeta "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2. boot into twrp on your pc type "adb shell" then "mount -o rw /dev/block/bootdevice/by-name/vendor /vendor " (if your touch works in twrp you can just hit mount and vendor)
4. push the edited fstab file "adb push fstab.qcom /vendor/etc/"
5. flash the gsi , download the one of your choise , even tho we are a only we need arm64 a/b gsis others wont work "fastboot flash system pathtogsisystemimghere"
6. wipe the data to remove the encryption "fastboot -w" (if touch in twrp works hit wipe format data type yes)
7. flash my kernel (fastboot flash boot BOOT_GSI.img )
8 reboot the device (fastboot reboot)
9. after first boot is done enable adb
10. type "adb root" then "adb remount" then "adb push pathtotheoverlayapkilinked /system/overlay/" then "adb reboot"
ALL COMMANDS ARE TYPED WITHOUT ""
Thanks
phh for his gsis
erfan adbi for helping me figuring out how to fix module loading
sellerie for his method of reusing a kernel dtb
me for putting this all together and recompiling the kernel
SOURCES
Thanks for figuring out and writing it all down for us!
Where can I download the vbmeta.img?
Trying to do this. Got a Redmi 8 EU version with novatek touchscreen, no touch in twrp. Should still work, right? I do not need to do anything in twrp correct?
EDIT: Never mind, other recovery works. How does your kernel compare to stock? Why was it necessary to recompile it? I just installed LOS gsi 5 minutes ago, thanks for your help.
(Also, just out of curiosity: What does fstab.qcom do exactly?
M47Z said:
Thanks for figuring out and writing it all down for us!
Where can I download the vbmeta.img?
Trying to do this. Got a Redmi 8 EU version with novatek touchscreen, no touch in twrp. Should still work, right? I do not need to do anything in twrp correct?
EDIT: Never mind, other recovery works. How does your kernel compare to stock? Why was it necessary to recompile it? I just installed LOS gsi 5 minutes ago, thanks for your help.
(Also, just out of curiosity: What does fstab.qcom do exactly?
Click to expand...
Click to collapse
which recovery does work for you also how can i find out what screen i do have , the kernel was needed to be recompiled since the modules werent loading at all so we had no sound and no wifi i edited the kernel config to ignore module signatures and also force load modules.
the new fstab does disable the force encryption if it is enabled the gsi will bootloop
M47Z said:
Thanks for figuring out and writing it all down for us!
Where can I download the vbmeta.img?
Trying to do this. Got a Redmi 8 EU version with novatek touchscreen, no touch in twrp. Should still work, right? I do not need to do anything in twrp correct?
EDIT: Never mind, other recovery works. How does your kernel compare to stock? Why was it necessary to recompile it? I just installed LOS gsi 5 minutes ago, thanks for your help.
(Also, just out of curiosity: What does fstab.qcom do exactly?
Click to expand...
Click to collapse
got ya , uploaded vbmeta.img also uploaded redmi8 overlay apk so brightness will start work etc just check the updated steps 9 and 10
J0SH1X said:
which recovery does work for you also how can i find out what screen i do have
Click to expand...
Click to collapse
probably property sys.panel.display show it. By me:
Code:
~$ adb shell getprop sys.panel.display
tianma
Compatibility
Does all redmi 8 olive support this? ( im new in this gsi and im also noob bout this stuff) thanks!:fingers-crossed::fingers-crossed:
Probe07 said:
Does all redmi 8 olive support this? ( im new in this gsi and im also noob bout this stuff) thanks!:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
You are in correct thread. If something is not working in GSI for your olive , you can report it here.
jkkk88 said:
You are in correct thread. If something is not working in GSI for your olive , you can report it here.
Click to expand...
Click to collapse
yeah he is in the right thread , it might work on other variants or maybe not , it will boot for sure but idk if my kernel will work for any other variant then eu , just test and report
Could you give a noob a link to where I can find gsi's. If there are more than one please give me a link to the one you used succesfully. Thanks.
OK, found little time and tried:
history:
MIUI version: MIUI Global 10.3.1 | Stable / 10.3.1.0 (PCNEUXM)
MIUI version: MIUI by xiaomi.eu 11.0.4 | Stable / 11.0.4.0 (PCNCNXM)
GSI AOSP 10.0 v.208 / AOSP 9.0 v.123 installed according J0SH1X guide
Wifi, touchscreen working only till first display lock. Display brighthness and volume cannot be smoothly set
Currently getting warning before first login after each reboot:.
There's an internal problem with your device. Contact your manufacturer for details.
When touchscreen doesn't respond to your taps, you can still use mouse connected via OTG or ADB cli.
Mouse and adb is working fine also in Unofficial TWRP 3.3.1-1127 for REDMI 8 by wzsx150, just checked.
jkkk88 said:
OK, found little time and tried:
history:
MIUI version: MIUI Global 10.3.1 | Stable / 10.3.1.0 (PCNEUXM)
MIUI version: MIUI by xiaomi.eu 11.0.4 | Stable / 11.0.4.0 (PCNCNXM)
GSI AOSP 10.0 v.208 / AOSP 9.0 v.123 installed according J0SH1X guide
Wifi, touchscreen working only till first display lock. Display brighthness and volume cannot be smoothly set
Currently getting warning before first login after each reboot:.
There's an internal problem with your device. Contact your manufacturer for details.
When touchscreen doesn't respond to your taps, you can still use mouse connected via OTG or ADB cli.
Mouse and adb is working fine also in Unofficial TWRP 3.3.1-1127 for REDMI 8 by wzsx150, just checked.
Click to expand...
Click to collapse
the warning is expected because my kernel securety patch level is newer then the one provided by vendor , the boot level is the day i packed the bootimage thats why this is happening and i dont have an idea how to set
J0SH1X said:
got ya , uploaded vbmeta.img also uploaded redmi8 overlay apk so brightness will start work etc just check the updated steps 9 and 10
Click to expand...
Click to collapse
Alright so this took me a while, this is what I found out:
I got Redmi 8 EU 4/64GB, on MIUI V11.0.1.0.PCNEUXM. I tried all this stuff with LineageOS 16 GSI (download here)
So I tried to follow your steps and it seems to be working alright. But there were some bugs: Fingerprint would not work. When I would set up a pin, pattern etc, it would not work after setup. LineageOS complained about decrypted phone. I then tried all kind of things and this is what I found out:
- We dont need a custom kernel. The stock one from latest stable MIUI (V11.0.1.0.PCNEUXM) works just fine as far as I have tested.
- We do not need a modified vbmeta, just flash the stock one with --disable-verification option.
- Instead of flashing fixed overlay we can also fix the brightness in LOS by entering "setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)" in adb su shell.
So the fastest way to get LOS running (at least on EU version, without TWRP) should be:
0. Make sure you are on latest stable MIUI V11.0.1.0.PCNEUXM. Download and unpack LineageOS 16 GSI, also download vbmeta_stock_V11.0.1.0.PCNEUXM.img from attachments.
1. Unlock bootloader.
2. Flash system image: "fastboot flash system /path/to/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img"
3. Wipe data: "fastboot -w"
4. Disable verification: "fastboot flash vbmeta --disable-verification /path/to/vbmeta_stock_V11.0.1.0.PCNEUXM.img"
5. Reboot: "fastboot reboot"
6. Fix screen brightness: Enable developer settings, in there enable root for adb. Connect to PC and type:
Code:
adb shell
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
Done! LineageOS 16 works, fingerprint and pin working, encryption working, brightness working,found no bugs so far but only tried it for a couple of hours. Don't know if we need your kernel and mods for other roms though. On LineageOS something in your steps breaks the system, I guess it is the edited fstab and/or the --disable-verity option when flashing vbmeta (or vbmeta itself? ).
Hope this helps someone! Merry christmas!
M47Z said:
Alright so this took me a while, this is what I found out:
I got Redmi 8 EU 4/64GB, on MIUI V11.0.1.0.PCNEUXM. I tried all this stuff with LineageOS 16 GSI (download here)
So I tried to follow your steps and it seems to be working alright. But there were some bugs: Fingerprint would not work. When I would set up a pin, pattern etc, it would not work after setup. LineageOS complained about decrypted phone. I then tried all kind of things and this is what I found out:
- We dont need a custom kernel. The stock one from latest stable MIUI (V11.0.1.0.PCNEUXM) works just fine as far as I have tested.
- We do not need a modified vbmeta, just flash the stock one with --disable-verification option.
- Instead of flashing fixed overlay we can also fix the brightness in LOS by entering "setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)" in adb su shell.
So the fastest way to get LOS running (at least on EU version, without TWRP) should be:
0. Make sure you are on latest stable MIUI V11.0.1.0.PCNEUXM. Download and unpack LineageOS 16 GSI, also download vbmeta_stock_V11.0.1.0.PCNEUXM.img from attachments.
1. Unlock bootloader.
2. Flash system image: "fastboot flash system /path/to/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img"
3. Wipe data: "fastboot -w"
4. Disable verification: "fastboot flash vbmeta --disable-verification /path/to/vbmeta_stock_V11.0.1.0.PCNEUXM.img"
5. Reboot: "fastboot reboot"
6. Fix screen brightness: Enable developer settings, in there enable root for adb. Connect to PC and type:
Code:
adb shell
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
Done! LineageOS 16 works, fingerprint and pin working, encryption working, brightness working,found no bugs so far but only tried it for a couple of hours. Don't know if we need your kernel and mods for other roms though. On LineageOS something in your steps breaks the system, I guess it is the edited fstab and/or the --disable-verity option when flashing vbmeta (or vbmeta itself? ).
Hope this helps someone! Merry christmas!
Click to expand...
Click to collapse
vbmeta is stock non patched one i extracted out of a stock rom zip i downloaded also i noticed the kernel thing aswell , idk why it wasnt working earlier for me but if anyone has no working wifi and sound we atleast know how to fix that , also install the overlay apk it will fix up notch and statusbar and rounded corners aswell
M47Z said:
Alright so this took me a while, this is what I found out:
I got Redmi 8 EU 4/64GB, on MIUI V11.0.1.0.PCNEUXM. I tried all this stuff with LineageOS 16 GSI (download here)
So I tried to follow your steps and it seems to be working alright. But there were some bugs: Fingerprint would not work. When I would set up a pin, pattern etc, it would not work after setup. LineageOS complained about decrypted phone. I then tried all kind of things and this is what I found out:
- We dont need a custom kernel. The stock one from latest stable MIUI (V11.0.1.0.PCNEUXM) works just fine as far as I have tested.
- We do not need a modified vbmeta, just flash the stock one with --disable-verification option.
- Instead of flashing fixed overlay we can also fix the brightness in LOS by entering "setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)" in adb su shell.
So the fastest way to get LOS running (at least on EU version, without TWRP) should be:
0. Make sure you are on latest stable MIUI V11.0.1.0.PCNEUXM. Download and unpack LineageOS 16 GSI, also download vbmeta_stock_V11.0.1.0.PCNEUXM.img from attachments.
1. Unlock bootloader.
2. Flash system image: "fastboot flash system /path/to/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img"
3. Wipe data: "fastboot -w"
4. Disable verification: "fastboot flash vbmeta --disable-verification /path/to/vbmeta_stock_V11.0.1.0.PCNEUXM.img"
5. Reboot: "fastboot reboot"
6. Fix screen brightness: Enable developer settings, in there enable root for adb. Connect to PC and type:
Code:
adb shell
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
Done! LineageOS 16 works, fingerprint and pin working, encryption working, brightness working,found no bugs so far but only tried it for a couple of hours. Don't know if we need your kernel and mods for other roms though. On LineageOS something in your steps breaks the system, I guess it is the edited fstab and/or the --disable-verity option when flashing vbmeta (or vbmeta itself? ).
Hope this helps someone! Merry christmas!
Click to expand...
Click to collapse
how did you fix fingerprint and pattern im kinda loosing my mind over it here , if i reenable force encryption the phone will ALWAYS reboot to twrp with pstore telling me vold died , im using aosp not lineageos tho
J0SH1X said:
how did you fix fingerprint and pattern im kinda loosing my mind over it here , if i reenable force encryption the phone will ALWAYS reboot to twrp with pstore telling me vold died , im using aosp not lineageos tho
Click to expand...
Click to collapse
Thought I was not the only one restore latest MIUI with fastboot method. Important: Check "clean all" instead of "clean all and lock" or you will have to do the whole unlock process again. After that, follow the steps exactly as I wrote in the post before. Do NOT flash BOOT_GSI.img, fstab.qcom or treble-overlay-xiaomi-redmi8.apk. You do not need TWRP for this, but you can just install it afterwards if you want. Good luck! :good:
J0SH1X said:
vbmeta is stock non patched one i extracted out of a stock rom zip i downloaded also i noticed the kernel thing aswell , idk why it wasnt working earlier for me but if anyone has no working wifi and sound we atleast know how to fix that , also install the overlay apk it will fix up notch and statusbar and rounded corners aswell
Click to expand...
Click to collapse
I guess vbmeta changed with some later update then! The one I attatched is also just pulled from latest MIUI, no modification. I strongly think wrong/mismatching vbmeta and/or --disable-verity option while flashing it causes the fingerprint/pattern/pin/... bug, at least in LineageOS 16 GSI.
M47Z said:
Thought I was not the only one restore latest MIUI with fastboot method. Important: Check "clean all" instead of "clean all and lock" or you will have to do the whole unlock process again. After that, follow the steps exactly as I wrote in the post before. Do NOT flash BOOT_GSI.img, fstab.qcom or treble-overlay-xiaomi-redmi8.apk. You do not need TWRP for this, but you can just install it afterwards if you want. Good luck! :good:
I guess vbmeta changed with some later update then! The one I attatched is also just pulled from latest MIUI, no modification. I strongly think wrong/mismatching vbmeta and/or --disable-verity option while flashing it causes the fingerprint/pattern/pin/... bug, at least in LineageOS 16 GSI.
Click to expand...
Click to collapse
The vbmeta flag is not it that's the official way of disabling avb documented in Google docs.
Also I pred phh to fix brightness
https://github.com/phhusson/device_phh_treble/pull/137
J0SH1X said:
The vbmeta flag is not it that's the official way of disabling avb documented in Google docs.
Click to expand...
Click to collapse
Well we surely do not need it to run LOS. Is it possible it does not need avb disabled? OP in the thread says: "verified booting on an arm64 ab device I own".
But I am 100% sure: On untouched latest stable MIUI, if you follow the steps by OP exactly with LOS, it will not work, you will get fingerprint/pin/... error and non encrypted device. If you do it like I wrote, flashing latest stock vbmeta with --disable-verification only, and NOT installing fstab.qcom, BOOT_GSI.img or treble-overlay-xiaomi-redmi8.apk, it will all work nicely. If vbmeta is not the issue, then it is the fstab. Might be different for other roms of course.
J0SH1X said:
Also I pred phh to fix brightness
https://github.com/phhusson/device_phh_treble/pull/137
Click to expand...
Click to collapse
Nice :good:
As there is a new Version , here is the vbmeta for those who want to try it out with V11.0.2.0.PCNEUXM. I got it from here:
https://xiaomifirmwareupdater.com/miui/olive/
I will try it in a few weeks.
And many thanks to @M47Z for your instructions. This will save me and others much time.
rudolfm said:
As there is a new Version , here is the vbmeta for those who want to try it out with V11.0.2.0.PCNEUXM. I got it from here:
https://xiaomifirmwareupdater.com/miui/olive/
Click to expand...
Click to collapse
Hmm maybe I am blind but... there is no V11.0.2.0.PCNEUXM right? Global and China got 11.0.3.0, Indonesia and India got 11.0.2.0, and Europe and Russia got 11.0.1.0 at the moment. So latest for European phone is V11.0.1.0.PCNEUXM right?
M47Z said:
Hmm maybe I am blind but... there is no V11.0.2.0.PCNEUXM right? Global and China got 11.0.3.0, Indonesia and India got 11.0.2.0, and Europe and Russia got 11.0.1.0 at the moment. So latest for European phone is V11.0.1.0.PCNEUXM right?
Click to expand...
Click to collapse
Global version has two different versions.one of them PCNEUXM (Europe)
and one is the real global PCNIM blah blah blah blah blah.....really stupid xiaomi ...
Sent from my Redmi 8 using Tapatalk
Hello everyone,
as many of you, I also want to lock my bootloader after finding that my X2 Pro bought used few days ago was unlocked and with TWRP installed.
It was stuck to Color OS 6 with security patch updated at february and it had installed Magisk.
I tried to flash Realme UI but I couldn't because it had installed official TWRP and not the right one.
I formatted everything and after some hours of research and trials I managed to install Realme UI with security patches updated (october).
Now, I don't have TWRP but official recovery instead. No signs of Magisk and any other data because I formatted everything few time during my flashing trials.
I don't have fingerprint and face recognition, I think due to the fact the bootloader is unlock, yet.
To overcome this, I found a video-guide used for X2 (not Pro) in which I saw that after flashing the Realme UI, rebooting recovery and formatting data, those sensors worked again but with X2 Pro this procedure won't work.
To recap: I have official firmware and recovery, no fingerprint and face recognition. I think that I can use the official guide for locking the bootloader again as the app says that I can roll-out from the in-depth program.
Was someone in my situation? I mean, locking the bootloader with FP and FU disabled before relocking?
I ask this because I found a thread in which the user said that it was necessary to make FU and FP work again before locking the bootloader.
I had this phone for less than a week and I can't take a decision.
Thank to anyone in advance.
you must now download the FASTBOOT format of Android9 pie rom (6gb) and use REALME FLASHER which will
1. place original recovery
2. flash all partitions and downgrade your device to android pie (Color OS 6.1)
reboot
test you onscreen fb and other sensors while on setup ( IT SHOULD WORK) because you are on stock recovery! and vbmeta.img is untouched
now install DEEP testing and wait, it will check your device (use 4g data sim / NOT WIFI)
click end deep testing!
this will RELOCK your bootloader, (while you are on Original recovery ) and wipe all the data!
now your device is locked again!,
download ROM (recovery rom) from realme site, for latest REALME UI ( this file will be OPPO encrypted 3gb of .0zip) but since you are on stock recovery, you can use it to flash it.
reboot again to the NEWEST Realme ui and check the fingerprint sensor
now install DEEP TESTING APK again and try unlocking the BOOTLOADER, once unlocked the the DATA will be WIPED AGAIN
now you are on REALME UI (latest), stock recovery, no partitions altered and you will be taken to SETUP again,
your FB should work!
join this text and see the guide (xda keep sensoring it so i had to break it)
thecustomdroi d.com/realme-flash-tool/
YasuHamed said:
you must now download the FASTBOOT format of Android9 pie rom (6gb) and use REALME FLASHER which will
1. place original recovery
2. flash all partitions and downgrade your device to android pie (Color OS 6.1)
reboot
test you onscreen fb and other sensors while on setup ( IT SHOULD WORK) because you are on stock recovery! and vbmeta.img is untouched
now install DEEP testing and wait, it will check your device (use 4g data sim / NOT WIFI)
click end deep testing!
this will RELOCK your bootloader, (while you are on Original recovery ) and wipe all the data!
now your device is locked again!,
download ROM (recovery rom) from realme site, for latest REALME UI ( this file will be OPPO encrypted 3gb of .0zip) but since you are on stock recovery, you can use it to flash it.
reboot again to the NEWEST Realme ui and check the fingerprint sensor
now install DEEP TESTING APK again and try unlocking the BOOTLOADER, once unlocked the the DATA will be WIPED AGAIN
now you are on REALME UI (latest), stock recovery, no partitions altered and you will be taken to SETUP again,
your FB should work!
join this text and see the guide (xda keep sensoring it so i had to break it)
thecustomdroi d.com/realme-flash-tool/
Click to expand...
Click to collapse
OMG tahnk you so much for your help.
I didn't receive any notification of your reply so I couldn't answer you before.
Before reading your reply I successfully locked the bootloader with REALME UI on it but FP and FU doesn't work.
I thought that it may be caused by the fact that bootloader was unlocked with Colors OS 6.1 (Android 9) and then I relocked it with Realme UI 1.0 (Android 10).
For this operation I used the official tool usable only with Android 10.
Do you think I should unlock the bootloader again, downgrade to Color OS 6.1, lock the bootloader and only then update my device to Realme UI?
If so, how can I downgrade the Android version? With their flashing tool it can't be done.
Hope you well and thank you in advance for your help.
Dude try this,
Download Realme flash tools here from my Google Drive:
realme_Flash_Tool_V2.zip
drive.google.com
Now download OFP file to use with the flash tool here:
OFP files
https://www.droidwin.com/flash-ofp-realme-flash-tool/
docs.google.com
Boot into bootloader and flash it. See if it helps.