Database Develop

Fingerprint not detecting in custom os since installed official 8.1

Fingerprint not detecting since I have installed custom ROM after I have installed official Oreo
On official Oreo fingerprint shows up in settings but in custom Oreo all works fine and best but fingerprint doesn't show up in any settings I have tried 4 8.1 custom roms like sex pixelexpirience 64 bit versions all works flawlessly tested Google camera it works the best but not detecting fingerprint even after searching fingerprint it only shows up gestures's fingerprint in gestures's system menu PLZZ give me link of official Oreo build OPSS28.65-36-3 with Indian band so I could try to flash via fastboot and then recheck if custom roms fingerprint gets detected or not..

Update ur bootloader to Oreo one and then try flashing the rom

Surya Guduru said:
Update ur bootloader to Oreo one and then try flashing the rom
Click to expand...
Click to collapse
I don't have fastboot official oreo link can anyone give me plzz

hondraopranav said:
I don't have fastboot official oreo link can anyone give me plzz
Click to expand...
Click to collapse
U told u had the official 8.1 ROM ....in that ...... fastboot Flash bootloader bootloader.zip and fastboot flash modem non-hlos.bin

change the base of your fp to nougat base again

Hey check this out

Surya Guduru said:
U told u had the official 8.1 ROM ....in that ...... fastboot Flash bootloader bootloader.zip and fastboot flash modem non-hlos.bin
Click to expand...
Click to collapse
The OP didn't say they had the official 8.1 ROM, they said they had installed official Oreo. AFAIK There is no official 8.1 ROM for Sanders. Some people have taken the OTA for their device and repackaged it into an UNofficial flashable package, but that's not the same thing, and reportedly may be causing problems on EU & US variants, so I wouldn't recommend it.
I have the same problem with my FP reader.
I don't have an official 8.1 ROM (because there isn't one, lol), but I installed stock nougat 7.1.1 (retus, in my case) and then got the OTA upgrade to 8.1, after that fp+VoLTE are 100% working.
Then, as soon as I change to a custom 8.1 (or 9) ROM, VoLTE still works, but the fp is no longer recognized by the system.
If I flash back to stock nougat, FP comes back (and LTE breaks, but can be fixed by installing the 8.1 OTA upgrade again, or by getting to a root terminal and fixing permissions on /persist, I've personally verified both methods to restore functionality (assuming your /persist is unmolested - if it is, you're SoL).
Going from fully working official nougat or official Oreo, to any Oreo (or Pie) custom ROM still seems to break the FP reader again. I'm getting really tired of wiping my device...
Not A Solution #1
As suggested here: With FP + VoLTE working under official 8.1 OTA update, I installed TWRP & backed up /EFS, then installed my custom 8.1 ROM (Validus final) and restored the backed up /EFS, but instead of bringing my FP back, it just caused bootloop and I had to roll back to stock and start over. I skipped rolling back to Nougat before flashing custom, is that important? Why would it matter?
Not A Solution #2
After installing the custom 8.1 ROM I tried flashing the Nougat FP base. It had no effect.
Maybe A Solution? UPDATE: YES. A SOLUTION.
As suggested in this post:
1 - download the latest nougat stock rom (link removed - the correct one will vary depending on your device, up to you to obtain the correct firmware);
2 - unzip the above file and cd into the resulting directory;
3 - reboot your phone in fastboot mode;
4 - from terminal (linux or windows, in linux I had to do it as root user, using sudo), type:
fastboot flash bootloader bootloader.img <enter>
fastboot flash modem NON-HLOS.bin <enter>
fastboot reboot <enter>
By doing above steps, your phone should get fingerprint options back.
I did this, it worked, with one additional step - I had a pattern set before. After the fingerprint reader was 'reinstated' the pattern no longer worked. Rebooting into Recovery and flashing lockfix.zip removed the security so that I could set it up again properly. Find lockfix.zip in this post.

GUIDE How to Instal GSI ROM- Havoc-OS-v4.X-Official Android 11 On Redmi 8

Here I bring to you the official Havoc-os 4.X ROM Android 11 and fully functional on Redmi 8
The intention of this post is to make a step-by-step tutorial on the installation of this excellent GSI ROM on Redmi 8 and give assistance in the installation process
All the development credits for this wonderful ROM go to the Havoc team
@Ruturaj Kadam
@jhenrique09
@SKULSHADY
Remember I am not a developer, if you are presenting any bugs let us know and you can contact the Havoc team on Telegram
I am not responsible for any damage caused to your device by not following the steps or negligence at the time of this process, All the steps were carried out and tested on my personal device and are confirmed, My device Redmi 8 3/32, the version that i tested Havoc-OS-v4.5-20210208-Official-arm64-ab.img.xz
Bugs
videos recorded with the default camera do not play
Update: Install the NGCam_7.4.104-v1.8-fix.apk Once the application is installed open it take a photo close the application, this will create a folder in the SD called Gcam, inside the Gcam folder create a folder and call it Config7 and inside this place the XML file Redmi 8 GCam 7.4.104.314953318 G_Modder.xml restart the application and you're done
the only bugs that have is slow motion record not work for now
Automatic brightness does not work
Update: to fix the automatic brightness on your device, after installing the ROM, put in the folder SYSTEM-OVERLAY the treble-overlay-xiaomi-redmi 8.apk and set the permission for the apk on 644 ( use root explorer ) and reboot ..... problem solved
the necessary files are at the end of the tutorial
Steps
Note: I did the installation coming from Mui 12.EU, and there was no problem in the installation process or in the boot process
If you come from Miui12 .EU or any other GSI Rom go to step 4, if you come from the Rom stock follow the this steps
1- First make a backup of all the necessary information in case something goes wrong you can easily recover, Charge the battery at least 80%
All your data will be deleted during the process
2- Unlock the Bootloader if you have not already done it or do not know how to, follow this post: http://en.miui.com/unlock/
3- Install a custon recovery, if you dont know how to, follow this post: https://c.mi.com/thread-2850424-1-0.html
4- Make wipe only to Cache, Dalvik, System, Data and Internal SD
5- Format data,( if it doesn't format the data you will have bootloop) then Reboot into Recovery
6- Copy all the files to the phone (Havoc-OS-v4.X-20200522-Official-arm64-ab.img you can find it by unpacking the zip), Magisk,Magisk Path Fix, Permisiver, Certification Patch.zip, opengapp (recommended nano or pico)
7- Install system image to system partition (on TWRP go to install-Install image-System) .
8- Flash Permisiver v5 (on TWRP go to install selec permisver_v5.zip)
9- Resize system partition to flash opengapps (on TWRP go to Wipe-Advanced Wipe-Select System on the list-Repair or Change File System-Resize)
To Root
once you have installed an resized the system
10- Flash the Magisk path fix (on TWRP go to install selec MagiskA11_PATH_fix.zip)
11- Flash Magisk (on TWRP go to install selec Magisk-v23.0.zip)
12- Flash Opengapps
1-Flash Certification Patch
1 - Make a wipe to Cache and Dalvik
1- Reboot
The boot process takes 5 to 10 minutes the first boot, in case of any problem in any of the stages you can reinstall Miui version fastboot with Mi flash tool and start again
Download link Rom image:
arm64-ab • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
OpenGapss Android 11: https://sourceforge.net/projects/opengapps/files/arm64/test/20210130/
Magisk:
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com

Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer

letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
Don't mind it, I haven't read all the article....

letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery

D
letouvetpierre said:
Don't mind it, I haven't read all the article....
Click to expand...
Click to collapse
Dont worry

Darth Inferno said:
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery
Click to expand...
Click to collapse
Okay thanks I think I will try this in the few days. Thanks for your guide !

Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer

UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...

letouvetpierre said:
UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...
Click to expand...
Click to collapse
Hi, I need to know some things to help you, what ROM did you have before flashing Havoc? do you have the bootloader unlocked? When did you use My flashtool, what method did you use?

letouvetpierre said:
Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer
Click to expand...
Click to collapse
In my particular case it was not necessary to flash vbmmeta as I comment in the OP I come from Miui12.eu, but it is necessary to avoid problems whatever the ROM you have before installing Havoc is to have the latest version of TWRP and have configured a lock pattern security in ROM access and in the flashing process I didn´t have problems

Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...

letouvetpierre said:
Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...
Click to expand...
Click to collapse
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)

Darth Inferno said:
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)
Click to expand...
Click to collapse
Hey!
I thought about something this afternoon : if I flash HavocOS with adb and fastboot, we also haven't any problems with TWRP installation ! But the problem is that I haven't found any wiki to do that and i won't transform my phone to a beta tester....
Thanks a lot for your help but I think i will wait until a custom rom of LineageOs or HavocOs...

Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .

Dragonnuu said:
Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .
Click to expand...
Click to collapse
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can help.

letouvetpierre said:
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can hel
Click to expand...
Click to collapse

Thanks for replying and trying to help but last night I managed to get havoc 4.1 is installed by flashing lineage first (using another guide from this category). I will try again to get havoc 4.1 working without flashing lineage as soon as posible because I am curious .

Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?

mwaseem851 said:
Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?
Click to expand...
Click to collapse
Magisk doesn't work on Android 11

letouvetpierre said:
Magisk doesn't work on Android 11
Click to expand...
Click to collapse
Finally managed to flash Magisk on Havoc 4.1 with the help of youtuberking (telegram and YouTube).
How: just flash Magisk path fix before magisk and it's good to go.

[SOLVED] How to Install RMX1931EX_11_F.11 realme ui 2.0 with ORANGEFOX

So i just Got the REALME UI 2.0 update via System Updater and i downloaded is IMMEDIATELY.
But when i tried to install it via ORANGEFOX RECOVERY. It gave me error saying "this Package is for RMX1931L1" and couldnt install on this device.
Can please someone explain what it means, and how can i install this package.
EDIT. 1 : First i installed unofficial TWRP
than i installed C.38 ozip to get Stock recovery than i Relocked Bootloader (which wiped everything internal memory and everything) than i rebooted and checked for update. Got the A11 update downloaded it and Flashed it.
And now i am on A11 stock Locked bootloader and Working Fine.
BTW i live in INDIA

I think you're going to hard brick your device if you've got the bl unlocked and try to flash the official update through OrangeFox. My suggestion is to move the ota file to your pc, relock the bootloader if you're on rui1.0, then move the file and flash it clean, with the bl locked.

How did you even get the update, where do you live?

Magisk with stock Android 10 / 11, MicroG with Android 10 stock

After some time I got a second Axon 10 and I spend some time figuring out what was possible with this phone in terms of root, custom ROM etc.
My results are as follows.
What is working:
Android 9 + Magisk and TWRP
Android 9 + TWRP + Custom ROMs (LineageOS 16 and patched GSI)
Android 10 + Magisk and TWRP
Android 10 + Magisk and MicroG flashed via Magisk (= stock ROM without Google Services)
Android 11 + Magisk
What is not working:
Android 11 + Magisk + TWRP (TWRP logo flashes randomly but TWRP does not load).
Android 11 + Magisk + MicroG (the nanolx patching script does not work with Android 11 as of yet)
Encryption in Custom ROMs
Method to flash files via EDL
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
Unlock Bootloader:
Before you try any of the files, you MUST unlock your bootloader!
BACKUP of your data as it will be lost!
Download the EDL tool from this Thread
If your phone is not on android 9, you must go back to Android 9 first. e.g. by using my Android 9 1.9 backup.
After you restored it, restart while holding the volume + key and do a factory reset / format data.
Boot into EDL again and unlock the bootloader.
Now you are on android 9 with unlocked bootloader.
From here you can follow the other guides in the form and install TWRP or lineageos. Or flash one of my files below.
Flashing EDL files:
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
I put all my files into this MEGA account: MEGA
Android 10 version 2.9 Magisk + TWRP
Android 11 version 3.5 stock
Android 11 version 3.5 Magisk
Android 10 version 2.10 stock
Android 10 version 2.10 Magisk (TWRP can be flashed with Magisk)
Install MicroG:
Only works on Android 9 and 10.
Before you install MicroG you must patch the stock ROM to allow for signature spoofing.
The patcher script I used is on https://downloads.nanolx.org/NanoDroid/Stable/ When I write these lines the up-to-date-version is NanoDroid-patcher-23.1.2.20210117.zip
Reboot.
Install MicroG from the Magisk repository.
After a restart there will be error messages that google apps keep crashing. With each warning, disable the apps one by one.
When you reboot again, no errors should appear and MicroG should report that it is fully working.
You can add the Bromite Framework and give F-droid system rights. Both are available from the Magisk repo.
Updates will likely install the Google apps again and uninstall Magisk...
Revive phone:
Not really related, but I bricked my phone several times.
If your phones does not boot anymore or hangs in a bootloop, try accessing the EDL mode.
The easy way:
Boot while holding volume -
The hard way:
Old Volume +, volume - and power until you end up in EDL. The screen will be black, so it helps if you have the Phone connected to Windows and can hear the system sound when the USB sees a connection.
In anyway you can then use the EDL tool to restore / flash an EDL image.
On custom ROM support:
Well there is LineageOS 16 by Unjustified Dev. https://forum.xda-developers.com/t/rom-unofficial-zte-axon-10-pro-9-lineageos-16-0.3992127/ It works well. But has a patch level that is outdated by now.
On top of it you can install the GSI ROMs created by Rafyvitto. The latest one is Resurrection Remix https://forum.xda-developers.com/t/...nofficial-resurrection-remix-q-8-6-7.4172527/
with a security patch level of mid 2021. Which is recent enough to use. The stock roms are not much better.
With both Custom ROMs, encryption is not working which poses a privacy/security risk when your phone is stolen. Do not forget that your phone does not only contain your photos and data but also your passwords to your accounts.

Added Android 10 2.10 files.

Its nice to see anything new for this phone. I wish I can use these roms but I have the American version.

Hi and thanks for your work and your files.
I'm stuck on "Loading the programmer: prog_ufs_firehose_sdm855.elf >>>", if I try to recover your edl files with EDL Tool, v 3.25.
I have to choose option 2: "Restore Full EDL from backup", right?
Is there a way to check if the bootlaoder is really unlocked?
Thanks in advance

OK, I was able to solve the problem with the "programmer" and try the backups. The next step was almost clear. The device is stuck in bootloop. I've already tried all the backups I could find on Mega. After the EDL Tool has done its work and the device has restarted, the mobile phone goes into the boot loop. And now? So the starting position was: Android 9 with an open bootloader. Maybe someone has an idea?

After I couldn't get the device out of the bootloop, I flashed the A2020G_PRO_V1.6_FULL_EDL via MiFlash and then did an OTA update to 1.8.
Then I tried unlocking the bootloader again, which unfortunately didn't work. The flash is carried out without errors, but the device then apparently does not start in the desired Fastboot mode.

Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.

brian117 said:
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
Click to expand...
Click to collapse
Maybe you need to switch the slot in TWRP. It sounds as if you install it to the other slot (like A) an then boot B. Or vice versa.

[GUIDE] [RMX1901] Unbrick & Install Android 13 Custom ROM

The guide is for a Chinese version of the phone. But might give you an idea for the global version.
History:
I was on the latest official ROM. But I was already unlocked the boot. Then I tried to install a custom ROM and failed. Because TWRP for RMX1901 seems doesn't work with UI1 Realme X OS.
I was going to boot loop and tried many instructions and old ROMS etc.
I downloaded many old .ofp and .ozip ROMs from the internet and many sources.
But all of them with MSMDownTool.exe that asking a username and password.
I lost 3-4 days for this process.
I found and tried the following useful open-source tools:
https://github.com/bkerler/oppo_decrypt
https://github.com/bkerler/oppo_ozip_decrypt
https://github.com/italorecife/OppoRealme-OFP-Flash
But did not have success. Although I found some knowledge about my phone.
Here are some useful links that I found:
- Realme X ROM version information:
https://t.me/s/RealmeUpdatesTracker?q=RMX1901
- Realme X ROM downloads:
https://realmeupdater.com/downloads/archive/RMX1901/
How to Unbrick:
1. Download [Recovery][11.1_6][RMX1901] Unofficial Orangefox for Realme x
Then extract zip and flash recovery.img with fastboot.
To enter to fastboot push-down volume down (-) key continuously and turn on the phone.
Code:
fastboot flash recovery recovery.img
Then change mode with volume keys and select Recovery mode and click the power button.
Then it should enter to OrangeFox.
If it does not work then try to flash Vbmeta.
In fastboot type:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then might fix the issue.
2. When you entered to OrangeFox recovery successfully then copy the full OrangeFox .zip file to the phone with MPM and install again it with OrangeFox. The device will automatically reboot into OrangeFox recovery after installation.
3. Now you can copy and install ROMS.
I installed ROMS in the following order. But you might not reboot between them.
a) RMX1901CN_flashable_A17.zip (It might be possible to use the official stock ROM file with version RMX1901_11.A.17)
b) RMX1901_11_OTA_1120_all_5fcT8erEU2dx.ozip
c) RMX1901_11_OTA_1190_all_EyyIUd8KYxPI.ozip
(If you want to use a phone with stock ROM then stop here and install the latest stock ROM. But I didn't try.)
e) Reinstall OrangeFox .zip (Because it's replaced when installed stock ROMS in previous steps)
Installation of [ROM][13] RiceDroid 6.0 IceCream for Realme X [UNOFFICIAL][RMX1901]
f) Wipe system, vendor, data, cache, and Dalvik
g) Install ROM: https://sourceforge.net/projects/rm...-22092315-COMMUNITY-AOSP-RMX1901.zip/download
h) Install modified GAPPS: https://sourceforge.net/projects/rm...ps-omni-arm64-13-20220908-signed.zip/download
i) Install Device Personalization Add on: https://sourceforge.net/projects/ni...lizationServices-20220908-signed.zip/download (You can skip it but required for some stuff like App suggestions)
j) Reboot to recovery
k) Format data
l) Reboot and voila!

Good information for me. Mine is also chinese varient on Android 11 with RUI 2.0, how can I unlock the bootloader. I found the method to unlock bootloader on Android 10 with RUI 1.0 only. I did try to roll back but it didn't work.

mjmew said:
Good information for me. Mine is also chinese varient on Android 11 with RUI 2.0, how can I unlock the bootloader. I found the method to unlock bootloader on Android 10 with RUI 1.0 only. I did try to roll back but it didn't work.
Click to expand...
Click to collapse
I don't know much about RUI2.0. Rollback to RUI 1.0 and then you might can unlock the bootloader:
Download the file below and flash it from the file manager or stock recovery...
N.B= Backup your data because all will be deleted after flash.
For Chinese Variant Download: https://drive.google.com/uc?id=1uDgrAVhGeJSoAmsRu1-jcZkW1WktWqIY&export=download
Source: Realme X | OFFICIAL Telegram group.
PS: There are plenty of Telegram groups you might be interested. Please search by name Realme X etc.

Thanks so much for your help. I could rollback from file you gave and already unlocked the bootloader.

Almasd said:
I don't know much about RUI2.0. Rollback to RUI 1.0 and then you might can unlock the bootloader:
Download the file below and flash it from the file manager or stock recovery...
N.B= Backup your data because all will be deleted after flash.
For Chinese Variant Download: https://drive.google.com/uc?id=1uDgrAVhGeJSoAmsRu1-jcZkW1WktWqIY&export=download
Source: Realme X | OFFICIAL Telegram group.
PS: There are plenty of Telegram groups you might be interested. Please search by name Realme X etc.
Click to expand...
Click to collapse
dead link can u reupload it i have chinese variant UI2.0 i need to roolback my phone to unlock bootloader

matabungkay said:
dead link can u reupload it i have chinese variant UI2.0 i need to roolback my phone to unlock bootloader
Click to expand...
Click to collapse
Hello. I don't have this phone now and I deleted all files. You might ask it from Telegram groups.
@mjmew can you help him?

Almasd said:
Hello. I don't have this phone now and I deleted all files. You might ask it from Telegram groups.
@mjmew can you help him?
Click to expand...
Click to collapse
thank you for ur reply where i find telwgram group