Develop Bugs

Realme X2 1993 development

I open this thread because in my opinion the development situation of the various versions of the device is very confusing. I seem to have understood that as regards the unlocking of the bootloader with a working fingerprint, the situation is evolving well only on the China and India version while on the European version nothing moves ... In my modest opinion, Realme deciding to treat those who buy its phones in Europe as users of its lower series devices compared to other areas of the world are wrong because little development leads to a few posts in the various forums and few voices in google searches that each of us does when deciding what to buy ... What do you think you realme device owners in Europe?

I have the 1993ex version and the FP is working fine after a16

hammerheading said:
I have the 1993ex version and the FP is working fine after a16
Click to expand...
Click to collapse
Thanks for the information ... What procedure did you use to unlock the bootloader?

I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device

Bolumstar said:
I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device
Click to expand...
Click to collapse
So you too like me, although there is news of the working fingerprint on the EU, believe that it is still not worth unlocking.
I ask it because I repeat following the various treadhs on the forum it gets confused. It is sometimes indicated that the finger epint works and that for example magisk can work in normal mode and not core only ... This would already be a lot, to say yes it could use the viper4android.

surferbyter said:
Thanks for the information ... What procedure did you use to unlock the bootloader?
Click to expand...
Click to collapse
I used this guide, it works the same for X2.

hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?

surferbyter said:
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?
Click to expand...
Click to collapse
First time i flashed the twrp i folowed this but now i simply skip the vbmeta and flash twrp directly from bootloader and it works fine.

Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu

woocashewski said:
Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu
Click to expand...
Click to collapse
never installed a gsi, if I'm not mistaken it takes the image of the vendor ... if you can give me a link to a guide to get started? Thanks in advance...

Howto thread is on this forum...

woocashewski said:
Howto thread is on this forum...
Click to expand...
Click to collapse
I'm doing something wrong because i get bootloop everytime. i tryed to follow the guide with different gsi but no luck. Can you give a quick step how you did it ?

Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...

surferbyter said:
Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...
Click to expand...
Click to collapse
I've been there, i think the problem was the adb. I used the Minimal adb and it worked, give it a try

first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition

woocashewski said:
first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition
Click to expand...
Click to collapse
So gsi roms also have fingerprint problems ... However, more than a custom rom, I was interested in coloros with root ...
I can't give up the fingerprint though because some applications of the company I work for use it for authentication ...

I managed to root, magisk 20.3 zip flash on twrp, on the European version a17 with this guide:
https://forum.xda-developers.com/showpost.php?p=81579961&postcount=44
To make the vbmeta flash command work I used the minimal adb version 1.43, with previous versions it doesn't work.
The fingerprint works very well and energy consumption has not changed compared to use with locked boot.
After carrying out all the procedure, the magisk manager indicates the certified safety net unlike the play store which is instead not certified. To have it certified, you need to download the Device ID app, copy the GSF code that gives you the result by opening it and insert it on the page of this link:
https://www.google.com/android/uncertified/?pli=1
After having it delete the data of google service framework and google play store, force the arrest of the second and reopen it ...

hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63

Sandalwood83 said:
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63
Click to expand...
Click to collapse
Ok my bad then, i follow more than one guide so im not sure were i got the apk from. anyway good job finding it for future unlocks!

ROM Stock EU Version
Here the ROM Stock EU https:// drive.google.com/file/d/1-GpV3YBMCCCrQPvCKqqK3cYRXmBMzTCy/view?usp=drivesdk
Just copy the link

Planning to flash custom rom on Redmi Note 8T, have I got the steps right?

Hello, I am poised to start customising my Redmi Note 8T. I've done loads of reading and have an outline plan but would appreciate a sanity check / review of this in case I am either missing something or doing something I shouldnt. Phone is currently encrypted, TWRP can unlock it fine. I want to end up with an encrypted device but there is nothing precious on the phone at the moment (stock MIUI as delivered, pretty much unused since the unlock factory reset).
Here's what I have following my research on other threads here:
First, what I have done already:
0. get phone Redmi 8T willow 128GB with stock MIUI (DONE)
1. unlock phone (DONE, 7 day wait!)
2. flash TWRP (DONE, used 3.3.1-1 official version, but MIUI overwrote it when I rebooted)
3. Backup from TWRP (DONE)
Next, the to-do list:
4. flash vbmeta (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
5. flash TWRP 3.3.1-10 version (fastboot flash recovery twrp-3.3.1-10-ginkgo-willow-mauronofrio.img)
6. reboot into TWRP (fastboot reboot, hold volume up + power)
7. Wipe /system, /data, and /cache
8. flash Havoc-OS-v3.2-20200229-willow-Official.zip
9. flash open_gapps-arm64-10.0-pico-20200229.zip
10. reboot & test
11. reboot into TWRP (fastboot reboot, hold volume up + power)
12. flash magisk zip (Magisk-v20.3.zip)
13. flash disable_dm_verity zip (Disable_Dm-Verity_ForceEncrypt_02.24.2020.zip)
14. reboot & test
15. Install via magisk manager the SQLite3 binary (SQLite3.Universal.Binaries.v1.0.zip)
16. Reboot
17. Install vis magisk manager the GPay SQLite fix (GPay.SQLite.Fix.v2.0.zip)
18. Reboot
Thanks very much in advance.

Hey @ogpog, at step 4, where you find vbmeta to flash?
Thanks

ogpog said:
Hello, I am poised to start customising my Redmi Note 8T. I've done loads of reading and have an outline plan but would appreciate a sanity check / review of this in case I am either missing something or doing something I shouldnt. Phone is currently encrypted, TWRP can unlock it fine. I want to end up with an encrypted device but there is nothing precious on the phone at the moment (stock MIUI as delivered, pretty much unused since the unlock factory reset).
Here's what I have following my research on other threads here:
First, what I have done already:
0. get phone Redmi 8T willow 128GB with stock MIUI (DONE)
1. unlock phone (DONE, 7 day wait!)
2. flash TWRP (DONE, used 3.3.1-1 official version, but MIUI overwrote it when I rebooted)
3. Backup from TWRP (DONE)
Next, the to-do list:
4. flash vbmeta (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
5. flash TWRP 3.3.1-10 version (fastboot flash recovery twrp-3.3.1-10-ginkgo-willow-mauronofrio.img)
6. reboot into TWRP (fastboot reboot, hold volume up + power)
7. Wipe /system, /data, and /cache
8. flash Havoc-OS-v3.2-20200229-willow-Official.zip
9. flash open_gapps-arm64-10.0-pico-20200229.zip
10. reboot & test
11. reboot into TWRP (fastboot reboot, hold volume up + power)
12. flash magisk zip (Magisk-v20.3.zip)
13. flash disable_dm_verity zip (Disable_Dm-Verity_ForceEncrypt_02.24.2020.zip)
14. reboot & test
15. Install via magisk manager the SQLite3 binary (SQLite3.Universal.Binaries.v1.0.zip)
16. Reboot
17. Install vis magisk manager the GPay SQLite fix (GPay.SQLite.Fix.v2.0.zip)
18. Reboot
Thanks very much in advance.
Click to expand...
Click to collapse
flashing vbmeta is not really needed..however keep it just in case.
iaio72 said:
Hey @ogpog, at step 4, where you find vbmeta to flash?
Thanks
Click to expand...
Click to collapse
in fastboot rom inside images folder

ok solved thanks

the_weird_aquarian said:
flashing vbmeta is not really needed..however keep it just in case.
Click to expand...
Click to collapse
Well I tried without vbmeta and ended up with the panic-inducing "The system is destroyed" screen. I went back to fastboot and flashed vbmeta and twrp again, then installed the cutom rom, set it all up, then went back and installed magisk.
in fastboot rom inside images folder
Click to expand...
Click to collapse
I got vbmeta from reading https://forum.xda-developers.com/showpost.php?p=81591273&postcount=196 and downloaded from https://t.me/rn8updates/80

The same thing happened to me and I'm still not clear on the steps to follow to fix it and be able to install a custom rom. Destroyed system appears

ogpog said:
Well I tried without vbmeta and ended up with the panic-inducing "The system is destroyed" screen. I went back to fastboot and flashed vbmeta and twrp again, then installed the cutom rom, set it all up, then went back and installed magisk.
I got vbmeta from reading https://forum.xda-developers.com/showpost.php?p=81591273&postcount=196 and downloaded from https://t.me/rn8updates/80
Click to expand...
Click to collapse
The same thing happened to me and I'm still not clear on the steps to follow to fix it and be able to install a custom rom. Destroyed system appears.
You did well with the steps outlined above??

nothing is clear, not really..to many gray areas..like can i backup rom to external sd card, why exactly in twrp do you backup rom wise, and Disable_Dm-Verity_ForceEncrypt_, iv read its two files in one, new roms are not like the old days ie marshmallow kitkat, i used all in one tool flashed twrp..all went well then flashed then flashed magisk and then the dm-verty thing, ended up in a bootloop, then tried to use mi flash tool to put original firmware back, error error, got back using twrp and using eea recovery rom, although i was on on global, remember fast boot rom is not the same as recovery rom, same rom though, all very confusing...for me anyway.

Juanlufer4 said:
The same thing happened to me and I'm still not clear on the steps to follow to fix it and be able to install a custom rom. Destroyed system appears.
You did well with the steps outlined above??
Click to expand...
Click to collapse
Just looking back over my notes from when I did it. Here is what I wrote:
A modified vbmeta.img disables verify boot on devices using Android Verified Boot. You need to disable dm-verity on the fastboot command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
source https://forum.xda-developers.com/showpost.php?p=81591273&postcount=196
(the above is a command-line given on your computer connected to your phone which has been booted in fastboot mode (boot phone with power+volume down). You need the fastboot command on your computer (I use Linux and it's in a package called "android-tools").
If you forget to flash vbmeta, you'll see a message "the system hass been destroyed". Just go back to fastboot mode and flash it.
This is the process I recorded, but please verify it rather than folllwing it blindly, and bear in mind that later versions are available now .
Code:
0. get phone Redmi 8T with stock MIUI
1. unlock phone (DONE, 7 day wait!)
2. flash TWRP (DONE, used 3.3.1-1 official version, but MIUI overwrote it)
3. Backup (DONE)
4. flash vbmeta (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
5. flash TWRP 3.3.1-10 version (fastboot flash recovery twrp-3.3.1-10-ginkgo-willow-mauronofrio.img)
6. reboot into TWRP (fastboot reboot, hold volume up + power)
7. Wipe /system, /data, and /cache
8. flash Havoc-OS-v3.2-20200229-willow-Official.zip
9. flash open_gapps-arm64-10.0-pico-20200229.zip
10. reboot & test
bluefender said:
nothing is clear, not really..to many gray areas..like can i backup rom to external sd card, why exactly in twrp do you backup rom wise, and Disable_Dm-Verity_ForceEncrypt_, iv read its two files in one, new roms are not like the old days ie marshmallow kitkat, i used all in one tool flashed twrp..all went well then flashed then flashed magisk and then the dm-verty thing, ended up in a bootloop, then tried to use mi flash tool to put original firmware back, error error, got back using twrp and using eea recovery rom, although i was on on global, remember fast boot rom is not the same as recovery rom, same rom though, all very confusing...for me anyway.
Click to expand...
Click to collapse
I get your sentiment - it's feels hard doing this on any Android despite having decades of expert level professional computer experience. But it's really a miracle we can do it at all and we have the good people providing roms and the information needed to install them to thank for that. I think the "brick fear" makes it worse due to the lack of a console port or bios to fall back to like you have on a computer. I think the first post in the thread should contain all the information needed to install the rom but it's a moving target so I guess it's a difficult call to expect it to be maintained.
If I were to call out for one thing, it would be for that page to also include instructions for Linux. Android is Linux after all
(sorry I just realised I wasn't on the havoc thread where the "first page" is - https://forum.xda-developers.com/redmi-note-8/development/rom-havocos-3-1-t4043973 )

Thanks for your interest, I just wanted to know if the steps you describe were correct. I had 2 systems destroyed and it's not funny. Hopefully it works
---------- Post added at 03:56 PM ---------- Previous post was at 03:47 PM ----------
the_weird_aquarian said:
flashing vbmeta is not really needed..however keep it just in case.
in fastboot rom inside images folder
Click to expand...
Click to collapse
A doubt? started the rom well or encrypted?

Is there any YouTube videos showing the steps for the Redmi Note 8T ?

How to install rom gsi for Redmi note 8t

chakkrit_pond said:
How to install rom gsi for Redmi note 8t
Click to expand...
Click to collapse
+1 I'm trying to test GSIs on Note 8 (ginkgo) and I'm not succeeding in any way. Phone stuck on bootanimation (or, sometimes, reboot into TWRP).
Does anyone have the steps to success? Thanks.
I can start from scratch (MIUI 11).
Trying to flash a/b gsis of Android 10.

[FAQ][GUIDE][HELP] Assistance Solution Centre for MERLIN 🤓 (Redmi Note 9 / Redmi 10X 4G)

DISCLAIMERS:​
This help is specific for MERLIN devices only !
(Xiaomi Redmi Note 9 and Xiaomi Redmi 10X 4G)​
Keep atention. This is an UNOFFICIAL thread.​
This thread was based on the thread by Agent_fabulous. Thank you very much !​
DON'T ask by PM. If you have any question, reply to this thread.​
Keep in mind, nothing is 100% perfect, so you need to read careful
and keep trying before to ask an already answered question.​
Keep your backup files safe and secure ! If you can, encrypt them.​
If you try to flash in "firmware upgrade" mode, bootloader will be LOCKED again !​
Never try to flash in "format all" mode ! Otherwise, you will LOSE all secure and identifying infos for your device. Like IMEI and MAC.​
Never try to share your backups or your security and privacy will be compromised.
USE AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.​
Sorry for my bad english.​
GOOD LUCK

1. Where can I find official and untouched STOCK FIRMWARES ROMS?​Here, you can find latest releases: https://xiaomifirmwareupdater.com/miui/merlin/​Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/miui/merlin/​
2. Where can I find some useful tools?​Xiaomitool: https://www.xiaomitool.com/V2/​Miflashpro: https://miflashpro.com/​Miflashtool: https://xiaomiflashtool.com/​Sp Flash Tool: https://spflashtools.com/category/windows​Mi PC Suite: http://pcsuite.mi.com/​
3. There are useful tools for LINUX or Mac OS?​Xiaomitool (Linux & MacOS): https://www.xiaomitool.com/V2/​Sp Flash Tool (Linux): https://spflashtools.com/category/linux​
4. My pc can't detect my phone. What to do?​Probably, you need to install appropriate usb drivers.​Try this: https://androidmtk.com/download-mtk-usb-all-drivers​
5. Where can I find custom ROMs?​Here, you can find the collection of custom ROMs for MERLIN: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4291423/​
6. How can I root?​First and obviously, you need to unlock your bootloader. Once you unlock your bootloader, you can root your device flashing magisk patched boot.img.​Here, you can find magisk patched boot images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/​KEEP ATENTION: you need to disable verification for vbmeta too.​Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/​
7. Where can I find TWRP & PBRP?​There is only ONE recovery project with open source for MERLIN.​But, there are other twrp and pbrp with closed source.​If you use it, you can cause damages to your device, use at your own risk and DON'T ask about it.​KEEP ATENTION: you need to IGNORE misc partition, if you flash the misc partition, your phone can be stucked in boot loop.​Here, you can find recovery projects images: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/​KEEP ATENTION: you need to disable verification for vbmeta too.​Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/​
8. How can I restore the state of UNLOCKED BOOTLOADER?​You need to restore your backup of SECCFG partition.​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4220013/​
9. How to make TWRP V11.0.4.0 work on MIUI V12.0.5.0 or higher?​If you are using MIUI V12.0.5.0 or higher, TWRP V11.0.4.0 will not work.​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223077/​You will need to flash an older LK partition.​Here, you can find lk images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/​
10. How can I disable TWRP?​You will need to flash original stock recovery.img.​Here, you can find original stock recovery images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/​
11. How to flash using SP FLASH TOOL without EDL and authentication?​If you want to use flash tool on MIUI V12.0.5.0 or higher, it will requires EDL and authentication.​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223089/​
12. I am on MIUI V12.0.5.0 or higher, how can I flash using SP FLASH TOOL without EDL and authentication?​You will need to flash an older PRELOADER binary.​Here, you can find preloader binaries: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218929/​
13. I am on MIUI V12.0.4.0 or lower, how can I flash using SP FLASH TOOL without EDL and authentication?​You will need the specific DA (download-agent) file for it without authentication (#NoAuth #NoAuthentication #No-Auth #No-Authentication).​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209765/​
14. How can I downgrade MIUI version?​For downgrading your miui, you need unlocked bootloader.​After unlocked bootloader, you can flash older firmware rom using fastboot or sp flash tool.​
15. My phone is booting to a black screen after flashed misc partition together twrp. What to do?​If your phone is booting to a black screen, you need to erase MISC partition.​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/​
16. My phone got bootlop after installed a Magisk module or Xposed module. How can I disable it?​You will need to uninstall the module. You have two methods for this.​For first method, you can disable Magisk (read question 17).​For second method, you need to boot in emergency mode (rescue mode).​For booting in emergency mode, you need to press Vol+ (volume up) after boot starts. (YES, I mean AFTER you see boot logo.)​And then, you can uninstall the module.​
17. My phone got bootlop after flashed Magisk. How can I disable it?​You will need to flash original stock boot.img.​Here, you can find original stock boot images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/​
18. My phone got bootloop, I am on MIUI V12.0.4.0 or lower and I can't enter in fastboot mode or recovery mode. What to do?​You need to flash stock rom using sp flash tool.​Please, read question 13.​
19. My phone got bootloop, I am on MIUI V12.0.5.0 or higher and I can't enter in fastboot mode or recovery mode. What to do?​For this, you will need to bypass authentication and flash in EDL mode with NO auth for FREE.​Here, you can find the guide for bypassing EDL authenticated mode for FREE: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/​For this, you will need an authorized account for flashing in EDL mode.​You need to go the service centre for professional assistance.​Please, read this: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/​
20. There is any other way for flashing or unbricking?​Yes. You can try any useful tool (read question 2 and 3).​But, this help is not for how use them.​You can find a huge amount of videos in youtube about it.​
21. I want to keep with original stock boot.img together TWRP, but TWRP is removed at every reboot. What to do?​You will need to flash patched boot image without overwrite of recovery.​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209263/​KEEP ATENTION: you need to disable verification for vbmeta too.​Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/​
22. Where can I find scatter files to flash using flash tool?​Here, you can find scatter files: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223097/​
23. Where can I find readback file to backup using flash tool?​Here, you can find read back file: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223109/​
24. How can I know what is working on my phone before installing?​If you want to know what is working for MERLIN, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/​
25. How can I disable preinstalled apps without uninstalling them?​You need to perform this in command line:​pm disable-user --user 0 com.android.chrome​(Change com.android.chrome to desired package name to disable.)​
26. Where can I find source code of the kernel?​Here, you can find the OFFICIAL source code of the kernel: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/merlin-r-oss and https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/lancelot-q-oss​Here, you can find the OFFICIAL source code of the kernel modules: https://github.com/MiCode/MTK_kernel_modules/tree/merlin-r-oss and https://github.com/MiCode/MTK_kernel_modules/tree/lancelot-q-oss​
27. Where can I find device tree and other sources codes of MT6768?​-> https://github.com/Jebaitedneko/omni_device_xiaomi_merlin​-> https://github.com/Redmi-MT6768/android_device_xiaomi_merlin​-> https://github.com/Redmi-MT6768/android_kernel_xiaomi_mt6768​-> https://github.com/Redmi-MT6768/android_vendor_xiaomi_merlin​-> https://github.com/AndroidBlobs/device_xiaomi_merlin​-> https://github.com/AndroidBlobs/vendor_xiaomi_merlin​-> https://github.com/SparXFusion/android_device_xiaomi_merlin​-> https://github.com/SparXFusion/android_kernel_redmi_mt6768​-> https://github.com/JamieHoSzeYui/android_device_xiaomi_merlin​-> https://github.com/surblazer/android_device_xiaomi_merlin​-> https://github.com/surblazer/android_kernel_xiaomi_mt6768​-> https://github.com/ZyCromerZ/android_kernel_xiaomi_mt6768​-> https://github.com/Box-boi/android_kernel_xiaomi_mt6768​-> https://github.com/Box-boi/omni_device_xiaomi_merlin​-> https://github.com/Box-boi/android_device_xiaomi_merlin​-> https://github.com/Box-boi/android_vendor_xiaomi_merlin​-> https://sourceforge.net/projects/zyc-kernels/files/Merlin​
28. How to pass SafetyNet?​You will need to have Xposed installed. After it, everything you need to do is install HiddenCore-Module, active it on Xposed Manager and reboot.​Here, you can find the HiddenCore-Module: https://repo.xposed.info/module/com.cofface.ivader​KEEP ATENTION: it is making android to keep on activity forever and never suspends screen.​You can use the patched apk by Evengard: https://forum.xda-developers.com/t/hiddencore-module-what-was-it-doing.3903984/post-81982121.​
29. How to disable ads (advertising)?​You will need to have Xposed installed. After it, everything you need to do is install AdBlocker-Reborn, active it on Xposed Manager and reboot.​Here, you can find the AdBlocker-Reborn: https://repo.xposed.info/module/com.aviraxp.adblocker.continued​KEEP ATENTION: some people said it can get troubles to google apps.​
30. How to restore IMEI, Baseband, MAC, fix NVRAM WARNING and fix NVDATA CORRUPTED?​KEEP ATENTION: never try to restore partitions from a different device, or you can brick and cause damages to your device.​Here, you can find the guide: https://forum.xda-developers.com/t/...-on-merlin-redmi-note-9-redmi-10x-4g.4230423/​
31. How to disable ads (advertising) without xposed?​For unrooted devices, you need to perform this in command line:​pm disable-user --user 0 com.miui.msa.global​For rooted devices, you need to debloat your system and then remove the "MSA" app.​
32. What should I backup before trying to customize my device?​Here, you can find the list of what partitions you need to backup for avoiding mistakes without risking all of your device's identification details, like IMEI, WiFi MAC, Bluetooth MAC, calibration data, NVDATA, NVRAM, RADIO/MODEM/BASEBAND and others: https://forum.xda-developers.com/t/...lin-device-redmi-note-9-redmi-10x-4g.4229629/​
33. How to bypass authentication and flash in EDL with NO auth for FREE?​Here, you can find the guide for bypassing EDL authenticated mode for FREE: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/​
34. How to install XPOSED?​1. You need to unlock your bootloader.​2. You need to root using Magisk.​3. You need to install magisk manager.​4. You need to install the magisk module: RIRU. (Only Riru in the name).​5. You need to choose between EDXPOSED or LSPOSED and then install the magisk module: "Riru Edxposed" or "Riru Lsposed".​6. You need to install the properly manager: "Edxposed Manager" or "Lsposed Manager".​7. Reboot.​Done. Enjoy !​
35. How to remove and clear GOOGLE ACC and Mi ACC / MiCloud?​Here, you can find the guide for removing google account and xiaomi account: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4233977/​
36. How can I flash a CUSTOM ROM?​Here, you can find the guide for flashing custom roms by c.whoopee: https://forum.xda-developers.com/t/...rom-on-a-redmi-note-9-global-variant.4234151/​(Thanks to c.whoopee)​Here, you can find the guide for installing a Lineage 17.1 ROM by ma259: https://forum.xda-developers.com/t/...eage-17-1-rom-in-redmi-note-9-merlin.4235003/​(Thanks to ma259)​
37. How to properly use the SP Flash Tool?​Here, you can find the guide how to configure correctly the SPFlashTool: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4229937/​Here, you can find common errors of the SPFlashTool: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
38. How to solve "LIB DA not match" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
39. How to solve "PMT changed for the ROM" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
40. How to solve "STATUS_BROM_CMD_STARTCMD_FAIL" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
41. How to solve "STATUS_SEC_AUTH_FILE_NEEDED" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
42. How to solve "STATUS_BROM_CMD_FAIL" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
43. How to solve "STATUS_BROM_CMD_SEND_DA_FAIL" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​​44. Where can I find official ENGINEERING ROMs?​Here, you can find ENGINEERING ROM V1: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227933/​Here, you can find ENGINEERING ROM V2: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4246891/​
45. Where can I find extracted FIRMWARES?​Here, you can find the thread of the EXTRACTED FIRMWARE by yshalsager: https://forum.xda-developers.com/t/...-4g-redmi-note-9-merlin-auto-updated.4250261/​Here, you can find latest releases: https://xiaomifirmwareupdater.com/firmware/merlin/​Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/firmware/merlin/​
46. Where can I find extracted VENDORS?​Here, you can find latest releases: https://xiaomifirmwareupdater.com/vendor/merlin/​Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/vendor/merlin/​
47. How can I mount system RW (read-write) ?​Here, you can find the guide and the script by lebigmac for mounting system as read-write (RW): https://forum.xda-developers.com/t/...unt-system-read-write-super-no_super.4247311/​
48. How to write and recover the IMEI for SLOT 1 and SLOT 2?​Here, we are discussing about the possibilities of how to recover the IMEI for SLOT1 and SLOT2: https://forum.xda-developers.com/t/...-in-merlin-redmi-note-9-redmi-10x-4g.4258779/​Here, you can find md1img images of the baseband/modem/radio: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4258919/​​49. Where can I find custom KERNEL?​-> https://sourceforge.net/projects/zyc-kernels/files/Merlin/​-> https://github.com/JamieHoSzeYui/dream/releases​-> MOD EDIT: Link Removed​​50. How to skip & avoid EDL auth bypass and FLASH in DOWNLOAD MODE?​Here, you can find the guide: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4322631/​

Full List of My Own Threads:
[V12.5.2.0][Android 11.0] New Update: Download Files for Merlin V12.5.2.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4357045/
[V12.5.1.0][Android 11.0] New Update: Download Files for Merlin V12.5.1.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4321093/
[V12.0.1.0][Android 11.0] New Update: Download Files for Merlin V12.0.1.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4295435/
[V12.0.8.0] New Update: Download Files for Merlin V12.0.8.0.QJOMIXM
https://forum.xda-developers.com/t/...-0-qjomixm-redmi-note-9-redmi-10x-4g.4285863/
[V12.0.7.0] New Update: Download Files for Merlin V12.0.7.0.QJOMIXM
https://forum.xda-developers.com/t/...-0-qjomixm-redmi-note-9-redmi-10x-4g.4245351/
[BOOT][PATCHED] Boot Image Partition without OVERWRITE OF RECOVERY for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209263/
[DA][FLASH] DA files for flashing to MERLIN using FLASH TOOL
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209765/
[V1][ENGINEERING][ROM] OFFICIAL Egineering Firmware for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227933/
[V2][ENGINEERING][ROM] OFFICIAL Egineering Firmware for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4246891/
[FAQ][GUIDE][HELP] Assistance Solution Centre for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
[DISCUSSION][ROM][CUSTOM] What is the BEST CUSTOM ROM for MERLIN ?
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4291423/
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE
https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
[GUIDE]How to properly solve the errors of the SP FLASH TOOL for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
[GUIDE] How to properly use the SP FLASH TOOL for MERLIN ?
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4229937/
[GUIDE] How to remove and clear GOOGLE ACC and Mi ACC / MiCloud for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4233977/
[GUIDE] How to restore IMEI, Baseband, MAC, fix NVRAM WARNING and fix NVDATA CORRUPTED on MERLIN ?
https://forum.xda-developers.com/t/...-on-merlin-redmi-note-9-redmi-10x-4g.4230423/
[GUIDE] What should I backup before trying to customize my MERLIN device ?
https://forum.xda-developers.com/t/...lin-device-redmi-note-9-redmi-10x-4g.4229629/
[GUIDE][FLASH] How to keep flashing without AUTH or EDL on V12.0.5.0 or higher MIUI versions in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223089/
[GUIDE][TWRP] How to keep TWRP V11.0.4.0 working on MIUI V12.0.5.0 or higher MIUI versions in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223077/
[DISCUSSION] How to write and recover the IMEI for SLOT 1 and SLOT 2 in MERLIN ?
https://forum.xda-developers.com/t/...-in-merlin-redmi-note-9-redmi-10x-4g.4258779/
[GUIDE][UNBRICK] How unbrick your bootloop in MERLIN after flashing TWRP
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
[GUIDE][UNLOCK] How to restore the state of UNLOCKED BOOTLOADER in MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4220013/
[LK][STOCK] LK Image Partition for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
[BASEBAND][STOCK][MD1IMG] MODEM Image Partition for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4258919/
[MAGISK][XPOSED] What is working for Magisk and Xposed in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
[PRELOADER][STOCK] PRELOADER Partition Binary for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218929/
[READBACK][FLASH] Read Back file for backuping using flash tool from MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223109/
[SCATTER][FLASH] Scatter file for flashing using flash tool to MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223097/
[STOCK][PATCHED] Boot, Vbmeta and Recovery: Images Partitions for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
[RECOVERY PROJECT] Collection of TWRP & PBRP & SHRP & ORANGEFOX for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/
[VBMETA][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
[GUIDE] How to skip & avoid EDL auth bypass and FLASH in DOWNLOAD MODE for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4322631/

TWRP does work above 12.0.5, I have tested.
New build: https://tdrive.elytra8.workers.dev/image-new.img
Flash like you flash any other custom recovery.
For ADS in MIUI, using debloat tool and removing MSA does the job.

Communos said:
TWRP does work above 12.0.5, I have tested.
New build: https://tdrive.elytra8.workers.dev/image-new.img
Flash like you flash any other custom recovery.
For ADS in MIUI, using debloat tool and removing MSA does the job.
Click to expand...
Click to collapse
Thank you very much.
Both were added on FAQ & GUIDE.
Here, you can find unofficial recovery project with closed source: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/

Uhm... hello, newbie here and hopefully in the right thread.
I have a Redmi Note 9 and wanted to install LineageOS. What I have done so far:
Jumped through all the hoops to unlock the bootloader.
Since that erases all user data, I did not bother setting a password in the setup. Just went through it as quickly as possible.
Installed TWRP 12.0.6
Used that to install lineage-17.1-20210209-UNOFFICIAL-merlin.zip from here.
Result: The new system does not boot. I always end up in TWRP again. Even if I specifically go to Reboot -> System, it'll boot into recovery. I think the first boot fails and then it goes into recovery (if I power the device off and on again, it vibrates, the logo comes on, the screen goes black, it vibrates again, the logo shows again, and then I'm in TWRP).
What I have tried unsuccessfully:
Flashing the vbmeta from here.
Erasing the misc partition.
Flashing the old lk from here.
Closing the AVB2.0 after flash (with and without closing DM verity).
Wiping cache, dalvik, data, internal storage, and cache before reinstalling LOS.
Replacing TWRP with PBRP and trying again.
Probably some other things I don't remember. I've been chasing red herrings through this rabbit hole all day.
I also tried to install the ArrowOS build (from here), just to have one more datapoint. After that, the device boot-loops into the bootloader, and I have to manually go into recovery via VolUp+Power. This leads me to believe that it's not the LOS build at fault. It seems more likely that I am a moron and am doing something wrong. I just can't figure out what it is.
Any help would be appreciated.

MyBrainIsAStrainer said:
Uhm... hello, newbie here and hopefully in the right thread.
I have a Redmi Note 9 and wanted to install LineageOS. What I have done so far:
Jumped through all the hoops to unlock the bootloader.
Since that erases all user data, I did not bother setting a password in the setup. Just went through it as quickly as possible.
Installed TWRP 12.0.6
Used that to install lineage-17.1-20210209-UNOFFICIAL-merlin.zip from here.
Result: The new system does not boot. I always end up in TWRP again. Even if I specifically go to Reboot -> System, it'll boot into recovery. I think the first boot fails and then it goes into recovery (if I power the device off and on again, it vibrates, the logo comes on, the screen goes black, it vibrates again, the logo shows again, and then I'm in TWRP).
What I have tried unsuccessfully:
Flashing the vbmeta from here.
Erasing the misc partition.
Flashing the old lk from here.
Closing the AVB2.0 after flash (with and without closing DM verity).
Wiping cache, dalvik, data, internal storage, and cache before reinstalling LOS.
Replacing TWRP with PBRP and trying again.
Probably some other things I don't remember. I've been chasing red herrings through this rabbit hole all day.
I also tried to install the ArrowOS build (from here), just to have one more datapoint. After that, the device boot-loops into the bootloader, and I have to manually go into recovery via VolUp+Power. This leads me to believe that it's not the LOS build at fault. It seems more likely that I am a moron and am doing something wrong. I just can't figure out what it is.
Any help would be appreciated.
Click to expand...
Click to collapse
Hey, Custom roms for Redmi Note 9 need MIUI 12.0.1 Indonesia, or MIUI 12.0.3 global vendor.
Downgrade your phone to the specific MIUI vendor, and then try flashing custom rom.
Here's the link for global 12.0.3
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
And before you downgrade your miui version, please erase system and vendor to bypass anti roll back.
Use these commands after connecting device in fastboot mode:
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
fastboot reboot bootloader
Then flash the 12.0.3 global/12.0.1 Indonesia miui version through MiFlash.
Or
You could give flashing 12.0.1 Indonesia vendor in TWRP, and then flashing rom.
If after fastboot reboot fastboot it shows waiting for device, install this driver. https://drive.google.com/file/d/1JFYCZ3mu_Y_xpnS7QrmtwqOeFnWg6DO2/view?usp=sharing
Please note that you need to be on stock recovery for fastboot reboot fastboot to work.
Happy flashing

Thank you very much! With that info, I think I finally have it working!
I case it's helpful for future users, here are some issues I encountered along the way:
Communos said:
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
Click to expand...
Click to collapse
Code:
$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
$ fastboot erase system
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.013s
$ fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.012s
Is that normal? I do have a partition named 'super' that I can see in the TWRP backup module. Judging from its size, that could be the system partition. I think there's also a vbmeta_system and vbmeta_vendor, did you mean those?
Then flash the 12.0.3 global/12.0.1 Indonesia miui version through MiFlash.
Or
You could give flashing 12.0.1 Indonesia vendor in TWRP, and then flashing rom.
Click to expand...
Click to collapse
Ok, so I downloaded the full ROM for 12.0.3 global. I'm using Linux, so MiFlash won't work. But the ROM archive I downloaded contained a bunch of partition images and a shell script that would flash them using the fastboot command. I just ran that script. Windows users probably could have run the .bat file that was also included. There were no errors. And after a reboot, MIUI started to boot and presented me with the setup procedure.
I did not complete the setup (I suspect it would have just auto-updated MIUI to something that would have caused problems again) and used the power button to go into the bootloader.
From there, I flashed TWRP again (since it got overwritten by the script mentioned above), went into recovery mode, and tried to install LOS again. First, flashing seemed to hang. The last messages in the log were:
Code:
Installing file '/external_sd/Download/lineage-17.1-20210209-UNOFFICIAL-merlin.zip'
Checking for Digest file...
Target: Redmi/merlin_eea/merlin:10/QP1A.190711.020/V11.0.2.0.QJOEUXM:user/release-leys
And that was it. The border around the progress bar was doing it's busy animation thing and after waiting for 10 minutes, I used the power button to reset the device.
The second attempt went through fine, and now I have LineageOS running on the device. I still need to play around with it some more to see if there are any issues, but the flashing itself seems to have worked.
Again, thank you for your help!

MyBrainIsAStrainer said:
Thank you very much! With that info, I think I finally have it working!
I case it's helpful for future users, here are some issues I encountered along the way:
Code:
$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
$ fastboot erase system
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.013s
$ fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.012s
Is that normal? I do have a partition named 'super' that I can see in the TWRP backup module. Judging from its size, that could be the system partition. I think there's also a vbmeta_system and vbmeta_vendor, did you mean those?
Ok, so I downloaded the full ROM for 12.0.3 global. I'm using Linux, so MiFlash won't work. But the ROM archive I downloaded contained a bunch of partition images and a shell script that would flash them using the fastboot command. I just ran that script. Windows users probably could have run the .bat file that was also included. There were no errors. And after a reboot, MIUI started to boot and presented me with the setup procedure.
I did not complete the setup (I suspect it would have just auto-updated MIUI to something that would have caused problems again) and used the power button to go into the bootloader.
From there, I flashed TWRP again (since it got overwritten by the script mentioned above), went into recovery mode, and tried to install LOS again. First, flashing seemed to hang. The last messages in the log were:
Code:
Installing file '/external_sd/Download/lineage-17.1-20210209-UNOFFICIAL-merlin.zip'
Checking for Digest file...
Target: Redmi/merlin_eea/merlin:10/QP1A.190711.020/V11.0.2.0.QJOEUXM:user/release-leys
And that was it. The border around the progress bar was doing it's busy animation thing and after waiting for 10 minutes, I used the power button to reset the device.
The second attempt went through fine, and now I have LineageOS running on the device. I still need to play around with it some more to see if there are any issues, but the flashing itself seems to have worked.
Again, thank you for your help!
Click to expand...
Click to collapse
Oh you're using Linux, for Linux the commands is
/.fastboot reboot fastboot
Great to know you were able to flash successfuly. Note that first boot in all roms is a bootloop, you just have to force reboot after a minute of bootlogo showing up or so.

hi i flashed a wrong twrp and now the phone keeps bootlooping, cannot enter recovery or fastboot by power + vol (+ or -)
adb from computer doesn't detect
sp flash tool doesn't move when i hit "download" button
bootloader unlocked, root yes
pc notificates a device connection by sound
phone redmi note 9
thank you for the help really cannot figure it out

Kain105 said:
hi i flashed a wrong twrp and now the phone keeps bootlooping, cannot enter recovery or fastboot by power + vol (+ or -)
adb from computer doesn't detect
sp flash tool doesn't move when i hit "download" button
bootloader unlocked, root yes
pc notificates a device connection by sound
phone redmi note 9
thank you for the help really cannot figure it out
Click to expand...
Click to collapse
Apparentely, you need to flash in EDL mode.
So, you need to bypass the authentication in EDL mode first.
Read this: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/

Newbie Android user here, hopefully i’m on the correct thread...i have a Redmi Note 9 with MIUI Global version 11.0.5 and Magisk version 20.4.
I tried updating Magisk to the latest version using the direct install option but I keep getting an error. I was told I need manually patch the boot.img and flash it but I need to create a magisk_patch.img first from the boot.img.
I read some of the guides on this thread but I’m not sure which one to follow. Also the steps to create the magisk_patch.image shows I need to click the Install button on Magisk then Select and Patch a file. I only have the Update button on Magisk, can I use that instead?
Or if you have other suggestion how to fix my issue. I attached the error I’m getting when I’m updating Magisk.
Thank you in advance for the assistance.

E77en12 said:
Newbie Android user here, hopefully i’m on the correct thread...i have a Redmi Note 9 with MIUI Global version 11.0.5 and Magisk version 20.4.
I tried updating Magisk to the latest version using the direct install option but I keep getting an error. I was told I need manually patch the boot.img and flash it but I need to create a magisk_patch.img first from the boot.img.
I read some of the guides on this thread but I’m not sure which one to follow. Also the steps to create the magisk_patch.image shows I need to click the Install button on Magisk then Select and Patch a file. I only have the Update button on Magisk, can I use that instead?
Or if you have other suggestion how to fix my issue. I attached the error I’m getting when I’m updating Magisk.
Thank you in advance for the assistance.
Click to expand...
Click to collapse
You can't install the magisk using the direct option.
You need to the patch the boot.img file and then flash the magisk_patched.img using fastboot (or spflashtool).

VD171 said:
You can't install the magisk using the direct option.
You need to the patch the boot.img file and then flash the magisk_patched.img using fastboot (or spflashtool).
Click to expand...
Click to collapse
Thank you, it worked. Now my magisk is updated

E77en12 said:
Thank you, it worked. Now my magisk is updated
Click to expand...
Click to collapse
Good work, my friend.
You are welcome

HELP PLS
i first flashed the patched_magisk.img then i got in a twrp boot loop. When i try to reboot into the system i get back to twrp menu.
Then i panicked and went to WIPE and factory reseted,
but it got stuck again. Then i powered it off.
How do i get out of this? I wanted to flash the stock boot.img but the storage folders has strange names
EDIT:
i figured it out what i have done. The data was ecrypted so i formated the data. But now i have another problem:
I installed linageOS from here, but when want to reboot back to system it says
No OS Installed! Are you sure you wish to reboot? i don't undertand why the custom rom didn't install.
I just copied the .zip file with the custom rom in the phone and hit install in TWRP. What did i do wrong?

George528 said:
HELP PLS
i first flashed the patched_magisk.img then i got in a twrp boot loop. When i try to reboot into the system i get back to twrp menu.
Then i panicked and went to WIPE and factory reseted,
but it got stuck again. Then i powered it off.
How do i get out of this? I wanted to flash the stock boot.img but the storage folders has strange names
View attachment 5289089
EDIT:
i figured it out what i have done. The data was ecrypted so i formated the data. But now i have another problem:
I installed linageOS from here, but when want to reboot back to system it says
No OS Installed! Are you sure you wish to reboot? i don't undertand why the custom rom didn't install.
I just copied the .zip file with the custom rom in the phone and hit install in TWRP. What did i do wrong?
Click to expand...
Click to collapse
Did you flash the patched vbmeta too?

VD171 said:
Did you flash the patched vbmeta too?
Click to expand...
Click to collapse
do you have a full step-by-step guide for this? i am feeling lost rn. I only have your FAQ but it doesnt cover everything

George528 said:
do you have a full step-by-step guide for this? i am feeling lost rn. I only have your FAQ but it doesnt cover everything
Click to expand...
Click to collapse
Steps for flashing vbmeta are same for every device.
You may try to use the search.
Here, you can find patched vbmeta for MERLIN:
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com

VD171 said:
Steps for flashing vbmeta are same for every device.
You may try to use the search.
Here, you can find patched vbmeta for MERLIN:
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com
Click to expand...
Click to collapse
no, i mean a full guide for rooting from the beggining to end, for redmi note 9. For example i missed the vbmeta and this resulted in an error. Now i have to flash the stock firmware and wait for another 7 days for it to unlock. For newbies like me, this looks like a mess. If you don't have one, can you please create one? Do it for us, newcomers. Thanks

How To Guide Root achieved! Here's how to root the Red Magic 6 and Red Magic 6 Pro

I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up!
Join our Discord Channel
Join the Red Magic 6 & 6 Pro [XDA Developers Forums] Discord Server!
Check out the Red Magic 6 & 6 Pro [XDA Developers Forums] community on Discord - hang out with 1 other members and enjoy free voice and text chat.
discord.gg
Youtube Video Tutorial:
UPDATED VIDEO:
For all those websites that claim the RM6 can be rooted with Kingroot, Kingoroot, iRoot, SuperSU... They are MISLEADING you into downloading their software. In other words, they are full of BS and you should INGORE them at all costs as Magisk is the ONLY proper way to root the RM6.
DO NOT USE KINGROOT, iROOT, KingoROOT, or ANY OTHER THIRD-PARTY ROOTING TOOLS PLEASE!! They steal your DATA and sell it. Magisk does not steal anything.​
This procedure will require a wipe of your data.. TWICE! I'll explain why.
When you unlock the bootloader, it wipes your data. Normally you only have to wipe it once, flash the patched boot.img file with magisk, and be done.
However, it seems that users will need to perform another factory reset after flashing the patched boot image. I have no idea why but it works. Please make a note of this as it will be required or you will be stuck in a bootloop.
Requirments
1. Global ROM file
2. A payload dumper
3. Magisk APK to patch the boot img
4. A computer!
Here are the steps!
​1. Unlock your bootloader. Make sure you enable OEM unlock in developer options. This WILL WIPE YOUR DEVICE! The command to unlock your bootloader is "fastboot flashing unlock"
2. Download the global rom from here: https://rom.download.nubia.com/Europe/NX669J/V312/NX669J-update.zip
3. You will need to download a payload dumper tool. This is due to the firmware being in a .bin file (payload.bin). Follow the link below on how to extract the global firmware:
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
I ended up Downloading Termux from the playstore and extracting it with python on my phone.
When you get it extracted, just move the boot.img and vbmeta.img files to your Desktop and on your phone Place it somewhere on your internal storage where you will remember!
4. Download Magisk Manager onto your phone and install it. Select install "patch a file" option and select the boot.img you put on your phone.
Let magisk patch it. It will end outputting a file like "Magisk_Patchedxxx.img" Go ahead and copy that file to your Desktop.
5. Go onto your computer and open up command prompt. Change your directory to the Desktop ex. cd c:/Users/Your Name/Desktop
6. Type fastboot flash boot magisk_patched.img
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. From the bootloader, reboot into your recovery and perform another factory reset!
9. Reboot the phone and voila! You now have root access!
Another thing to mention is that SafteyNet does NOT pass even with MagiskHide enabled. Please keep that in mind!
So far I've installed the Xposed Framework and some Magisk modules. All seems to work really well.
Happy Modding!
​

Do u have rom V3:10

chocolote4444 said:
I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up!
This procedure will require a wipe of your data.. TWICE! I'll explain why.
When you unlock the bootloader, it wipes your data. Normally you only have to wipe it once, flash the patched boot.img file with magisk, and be done.
However, it seems that users will need to perform another factory reset after flashing the patched boot image. I have no idea why but it works. Please make a note of this as it will be required or you will be stuck in a bootloop.
Requirments
1. Global ROM file
2. A payload dumper
3. Magisk APK to patch the boot img
4. A computer!
Here are the steps!
​1. Unlock your bootloader. Make sure you enable OEM unlock in developer options. This WILL WIPE YOUR DEVICE! The command to unlock your bootloader is "fastboot flashing unlock"
2. Download the global rom from here: https://rom.download.nubia.com/Europe/NX669J/V312/NX669J-update.zip
3. You will need to download a payload dumper tool. This is due to the firmware being in a .bin file (payload.bin). Follow the link below on how to extract the global firmware:
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
I ended up Downloading Termux from the playstore and extracting it with python on my phone.
When you get it extracted, just move the boot.img and vbmeta.img files to your Desktop and on your phone Place it somewhere on your internal storage where you will remember!
4. Download Magisk Manager onto your phone and install it. Select install "patch a file" option and select the boot.img you put on your phone.
Let magisk patch it. It will end outputting a file like "Magisk_Patchedxxx.img" Go ahead and copy that file to your Desktop.
5. Go onto your computer and open up command prompt. Change your directory to the Desktop ex. cd c:/Users/Your Name/Desktop
6. Type fastboot flash boot magisk_patched.img
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification vbmeta vbmeta.img
8. From the bootloader, reboot into your recovery and perform another factory reset!
9. Reboot the phone and voila! You now have root access!
Another thing to mention is that SafteyNet does NOT pass even with MagiskHide enabled. Please keep that in mind!
Edit:
Xposed Framework DOES work!
​
Click to expand...
Click to collapse
would be the same process for version V4.12?

Masacr3 said:
would be the same process for version V4.12?
Click to expand...
Click to collapse
Yes. Mine is showing up as still 4.12

Are you SURE it doesn't pass SafetyNet? The Magisk check is broken download SafetyNet Checker from the app store and see what it says...

mslezak said:
Are you SURE it doesn't pass SafetyNet? The Magisk check is broken download SafetyNet Checker from the app store and see what it says...
Click to expand...
Click to collapse
I does not pass safety net. I've tested every testing app on the Play Store. I'll keep looking for a solution though.

chocolote4444 said:
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
You're missing the "flash" command inside, as such:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
A couple of questions:
1: does the phone retain full functionality? radio (BT/A2DP/different wifi bands/fingerprint scanner/camera)?
2: have you tried using an empty vbmeta?

adwinp said:
You're missing the "flash" command inside, as such:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
A couple of questions:
1: does the phone retain full functionality? radio (BT/A2DP/different wifi bands/fingerprint scanner/camera)?
2: have you tried using an empty vbmeta?
Click to expand...
Click to collapse
Everything still works except the fingerprint. When the bootloader is unlocked, the fingerprint stops working.
As for flashing empty vbmeta images, I have not tried it. I know some devices you may have to flash an empty vbmeta img at last resort but I was able to boot it up using the stock vbmeta.

chocolote4444 said:
Everything still works except the fingerprint. When the bootloader is unlocked, the fingerprint stops working.
As for flashing empty vbmeta images, I have not tried it. I know some devices you may have to flash an empty vbmeta img at last resort but I was able to boot it up using the stock vbmeta.
Click to expand...
Click to collapse
Thx for responding.
1: Would you be able to test/comfirm if the fingerprint scanner is restored when relocking the bootloader using either the rooted boot.img or the stock one?
2: The same issue with fp calibration is faced by RM 5S/G users; can you check if the calibration fix in these forums works also for the RM6?
3: Lastly, have you tried flashing the latest phh GSI to see if it's working?

Yes usually you just flash stock vbmeta.img via fastboot: fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification should try it out...

adwinp said:
Thx for responding.
1: Would you be able to test/comfirm if the fingerprint scanner is restored when relocking the bootloader using either the rooted boot.img or the stock one?
2: The same issue with fp calibration is faced by RM 5S/G users; can you check if the calibration fix in these forums works also for the RM6?
3: Lastly, have you tried flashing the latest phh GSI to see if it's working?
Click to expand...
Click to collapse
Fingerprint scanner should work after relocking the bootloader. As for flashing a GSI, there's no custom recovery for this device yet so I can't test any GSI roms yet.

chocolote4444 said:
Fingerprint scanner should work after relocking the bootloader. As for flashing a GSI, there's no custom recovery for this device yet so I can't test any GSI roms yet.
Click to expand...
Click to collapse
In this case, would you be able to run the following tests & share findings?
1: reflash stock boot, relock BL - check if fingerprint scanner is fixed
2: flash rooted boot.img (disable vbmeta), relock BL - check if fingerprint is fixed
If that would be the case, we could copy the calibration data from such a device; the data would be in /mnt/vendor/persist/goodix - I checked the stock ROM & it's not in there meaning it probably gets copied over during boot or mount-binded.
The last theory I want to check is the link between BL lock status & the fingerprint scanner - if some people have reported success with fixing the scanner with the builtin tool, there's a chance that the system framework or some other app is checking for the bootloader lock status & disabling the fingerprint if the former is unlocked. I've dumped the stock firmware but couldn't find a goodix dedicated apk, hence my hunch that it's a framework overlay. We would need to identify where the code is stored, decompile, find the security checking routine, disable, recompile & check agian - assuming it's not in any of the native libraries or the binary.
Assuming the access to the fingerprint scanner is indeed baked into the framework, using an AOSP GSIs would mean that the system would get unrestricted access to the fingerprint scanner, thus no blocking issue.
Thus (& addressing the 2nd part of your previous response), I'd suggest a 3rd test:
3: flash phh GSI or LOS GSI. The reason for the latter is because LOS usually has a wider range of hardware supported via hardware overlays.
You don't need a custom recovery to flash GSIs as these are fastboot images, so the following should suffice:
Code:
fastboot flash system gsi.img
fastboot -w

Umm Sir, got some problem with the global rom i patched it from your link. i cannot save any photos even screenshot. its nothing on my gallery. it seems it is not saving any photo. i hope you can teach me to solve it. thanks in advance

whincloud01 said:
Umm Sir, got some problem with the global rom i patched it from your link. i cannot save any photos even screenshot. its nothing on my gallery. it seems it is not saving any photo. i hope you can teach me to solve it. thanks in advance
Click to expand...
Click to collapse
Do a factory reset as you need to properly reinitialize package IDs, SELinux contexts & permissions.

adwinp said:
Do a factory reset as you need to properly reinitialize package IDs, SELinux contexts & permissions.
Click to expand...
Click to collapse
thank you. it is working well now.

I did the root process, but the phone stayed in the redmagic logo and it does not start me, what is the next process? flash the stock boot.img and it won't start

@chocolote4444 please share the solution when it gets stuck on the logo

FFX2 said:
@chocolote4444 please share the solution when it gets stuck on the logo
Click to expand...
Click to collapse
I am currently looking into it

Thanks for the guide

Hi. Will this also work for Android 11 on RM 5s?

[GUIDE] Root Umidigi A9 Pro 2021 (Magisk+Android 11)

*This guide is for the A9 Pro 2021 model with 8gb of RAM only. It was tested on the non-EU version but I see no reason for it to not apply to that model as well, so long is it an A/B partitioned device, which i believe it is*
I was having some difficulty rooting this device following the instructions found in an Umidigi posting. The instructions were not for rooting an A/B partitioned device and that's what was causing failure. If you tried the same method, you may have noticed that your device starts and then just reboots before the orange alert text goes away. Over and over...
Since I had not found one single posting about how to achieve root, I will share how I was able to do this thanks in part to an old post from this site combined with the instructions on Umidigi.
Before starting, I have to say something like this:
WARNING
IF YOU MAKE ANY ATTEMPT TO MODIFY YOUR DEVICE BY FOLLOWING THE INSTRUCTIONS OUTLINED IN THIS GUIDE YOUR PHONE WARRANTY WILL BE VOID AND ALSO MAY CEASE TO FUNCTION BY DOING SO. YOU ARE SOLELY RESPONSIBLE FOR YOUR ACTIONS AND ASSUME ALL RESPONSIBILITY FOR ANY AND ALL DAMAGE THAT MAY OCCUR
I'll assume you know what ADB is, you've unlocked the bootloader and have a copy of the EXACT firmware on your PC as you do on your phone. If not, please do that first. You're going to need it in order to follow this guide. Next, I'll assume you've also backed up your device.
*Before starting, run this adb command and if you get a "b" instead of an "a" then adjust your commands in step 6 to boot_b and vbmeta_b*
adb shell
getprop ro.boot.slot_suffix
exit
1) From your phone, download and install latest Magisk apk from Github. At time of writing, this is version 23
2) On PC, copy the boot.img and vbmeta.img files from your CURRENT firmware downloaded from Umidigii to your desktop. You will see 3 files beginning with vbmeta. We only want one of those, vbmeta.img
3) Plug in your phone to PC and copy the boot.img file to your phone
4) Run Magisk and select Install (top of list). You are given the option to patch a boot.img file. Select the boot.img you just copied to your device and Let's Go!
5) From PC, navigate to your phone's internal storage, specifically the Downloads folder and copy the newly created patched_magisk-xxxx.img file to your Desktop
6) From PC, with phone powered on and connected, open powershell as admin, enter these commands and properly input the name of your patched Magisk file. First command is only for those that placed files on the Desktop
cd ~\Desktop
adb reboot bootloader
fastboot --disable-verity --disable-verification flash boot_a magisk_patched-23000_xxxxx.img
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot reboot
That's it

Hello friend, I recently tried to install a custom ROM which in this case is DotOS 5.2, I downloaded everything correctly and it worked, my cell phone turned on ok. So I tried to install magisk and it bootloops, do you have any solution to make magisk work in a custom ROM? On my ROM, the stock works perfectly
Sorry for my English, I'm translating from the translator

mindlery said:
*This guide is for the A9 Pro 2021 model with 8gb of RAM only. It was tested on the non-EU version but I see no reason for it to not apply to that model as well, so long is it an A/B partitioned device, which i believe it is*
I was having some difficulty rooting this device following the instructions found in an Umidigi posting. The instructions were not for rooting an A/B partitioned device and that's what was causing failure. If you tried the same method, you may have noticed that your device starts and then just reboots before the orange alert text goes away. Over and over...
Since I had not found one single posting about how to achieve root, I will share how I was able to do this thanks in part to an old post from this site combined with the instructions on Umidigi.
Before starting, I have to say something like this:
WARNING
IF YOU MAKE ANY ATTEMPT TO MODIFY YOUR DEVICE BY FOLLOWING THE INSTRUCTIONS OUTLINED IN THIS GUIDE YOUR PHONE WARRANTY WILL BE VOID AND ALSO MAY CEASE TO FUNCTION BY DOING SO. YOU ARE SOLELY RESPONSIBLE FOR YOUR ACTIONS AND ASSUME ALL RESPONSIBILITY FOR ANY AND ALL DAMAGE THAT MAY OCCUR
I'll assume you know what ADB is, you've unlocked the bootloader and have a copy of the EXACT firmware on your PC as you do on your phone. If not, please do that first. You're going to need it in order to follow this guide. Next, I'll assume you've also backed up your device.
*Before starting, run this adb command and if you get a "b" instead of an "a" then adjust your commands in step 6 to boot_b and vbmeta_b*
adb shell
getprop ro.boot.slot_suffix
exit
1) From your phone, download and install latest Magisk apk from Github. At time of writing, this is version 23
2) On PC, copy the boot.img and vbmeta.img files from your CURRENT firmware downloaded from Umidigii to your desktop. You will see 3 files beginning with vbmeta. We only want one of those, vbmeta.img
3) Plug in your phone to PC and copy the boot.img file to your phone
4) Run Magisk and select Install (top of list). You are given the option to patch a boot.img file. Select the boot.img you just copied to your device and Let's Go!
5) From PC, navigate to your phone's internal storage, specifically the Downloads folder and copy the newly created patched_magisk-xxxx.img file to your Desktop
6) From PC, with phone powered on and connected, open powershell as admin, enter these commands and properly input the name of your patched Magisk file. First command is only for those that placed files on the Desktop
cd ~\Desktop
adb reboot bootloader
fastboot --disable-verity --disable-verification flash boot_a magisk_patched-23000_xxxxx.img
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot reboot
That's it
Click to expand...
Click to collapse
thank you, works perfectly, one request though...could you please make a flasjing tutorial for android 12 gsi on the same phone, I have been trying to flash as usual, but I keep getting bootloops on all GSIs I have tried, Android 11 GSIs boot well but the 12 ones don't

Sirkev said:
thank you, works perfectly, one request though...could you please make a flasjing tutorial for android 12 gsi on the same phone, I have been trying to flash as usual, but I keep getting bootloops on all GSIs I have tried, Android 11 GSIs boot well but the 12 ones don't
Click to expand...
Click to collapse
Hey Sirkev,
I am about to start looking into getting Android 12 running on this same device.
Umidigi A9 6GB + 128GB, currently running Android 11.
Please keep me updated with your progress, and I will do the same.
I MIGHT try to compile a custom Android 12 (Possibly even Android 13...) rom for this device if I can find enough time to look into it...
Side question - When you go to Google Play store with YOUR A9 Pro running the stock Android 11 rom, click on your profile picture in top right corner, click "Settings", then expand "About"...
What does your A9 say at the very bottom under "Play Protect Certification"???
Thanks!

mindlery said:
*This guide is for the A9 Pro 2021 model with 8gb of RAM only. It was tested on the non-EU version but I see no reason for it to not apply to that model as well, so long is it an A/B partitioned device, which i believe it is*
I was having some difficulty rooting this device following the instructions found in an Umidigi posting. The instructions were not for rooting an A/B partitioned device and that's what was causing failure. If you tried the same method, you may have noticed that your device starts and then just reboots before the orange alert text goes away. Over and over...
Since I had not found one single posting about how to achieve root, I will share how I was able to do this thanks in part to an old post from this site combined with the instructions on Umidigi.
Before starting, I have to say something like this:
WARNING
IF YOU MAKE ANY ATTEMPT TO MODIFY YOUR DEVICE BY FOLLOWING THE INSTRUCTIONS OUTLINED IN THIS GUIDE YOUR PHONE WARRANTY WILL BE VOID AND ALSO MAY CEASE TO FUNCTION BY DOING SO. YOU ARE SOLELY RESPONSIBLE FOR YOUR ACTIONS AND ASSUME ALL RESPONSIBILITY FOR ANY AND ALL DAMAGE THAT MAY OCCUR
I'll assume you know what ADB is, you've unlocked the bootloader and have a copy of the EXACT firmware on your PC as you do on your phone. If not, please do that first. You're going to need it in order to follow this guide. Next, I'll assume you've also backed up your device.
*Before starting, run this adb command and if you get a "b" instead of an "a" then adjust your commands in step 6 to boot_b and vbmeta_b*
adb shell
getprop ro.boot.slot_suffix
exit
1) From your phone, download and install latest Magisk apk from Github. At time of writing, this is version 23
2) On PC, copy the boot.img and vbmeta.img files from your CURRENT firmware downloaded from Umidigii to your desktop. You will see 3 files beginning with vbmeta. We only want one of those, vbmeta.img
3) Plug in your phone to PC and copy the boot.img file to your phone
4) Run Magisk and select Install (top of list). You are given the option to patch a boot.img file. Select the boot.img you just copied to your device and Let's Go!
5) From PC, navigate to your phone's internal storage, specifically the Downloads folder and copy the newly created patched_magisk-xxxx.img file to your Desktop
6) From PC, with phone powered on and connected, open powershell as admin, enter these commands and properly input the name of your patched Magisk file. First command is only for those that placed files on the Desktop
cd ~\Desktop
adb reboot bootloader
fastboot --disable-verity --disable-verification flash boot_a magisk_patched-23000_xxxxx.img
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot reboot
That's it
Click to expand...
Click to collapse
I have Umidigi A9 Pro 2020 version with android 10 is there any way I can Update it to Android 11?

GooballDiesel said:
Hey Sirkev,
I am about to start looking into getting Android 12 running on this same device.
Umidigi A9 6GB + 128GB, currently running Android 11.
Please keep me updated with your progress, and I will do the same.
I MIGHT try to compile a custom Android 12 (Possibly even Android 13...) rom for this device if I can find enough time to look into it...
Side question - When you go to Google Play store with YOUR A9 Pro running the stock Android 11 rom, click on your profile picture in top right corner, click "Settings", then expand "About"...
What does your A9 say at the very bottom under "Play Protect Certification"???
Thanks!
Click to expand...
Click to collapse
I have Umidigi A9 pro 2020 with Android 10 is there any way I can Update it to Android 11?

Isaac™ said:
Hello friend, I recently tried to install a custom ROM which in this case is DotOS 5.2, I downloaded everything correctly and it worked, my cell phone turned on ok. So I tried to install magisk and it bootloops, do you have any solution to make magisk work in a custom ROM? On my ROM, the stock works perfectly
Sorry for my English, I'm translating from the translator
Click to expand...
Click to collapse
I have Umidigi A9 pro Android 10 how can I update it to Android 11?

Sirkev said:
thank you, works perfectly, one request though...could you please make a flasjing tutorial for android 12 gsi on the same phone, I have been trying to flash as usual, but I keep getting bootloops on all GSIs I have tried, Android 11 GSIs boot well but the 12 ones don't
Click to expand...
Click to collapse
Can you please help me I have Umidigi A9 pro Android 10 how can I update it to Android 11 ?

Sidrickel_SD said:
I have Umidigi A9 pro 2020 with Android 10 is there any way I can Update it to Android 11?
Click to expand...
Click to collapse
Not sure what model you have, but if it its the 2020 64G (NON "E") model, then the newest firmware available is - "UMIDIGI_A9_PRO_64GB_V1-0_20220325"
No clue if the ROM is Android 10 or 11, but if it's 10 the only way you're ever getting 11 or higher on that device is to build it yourself... Not a simple task...even if you're already experienced with building ROMs.
Go here to see firmware (ROM) downloads for all Umidigi models - https://community.umidigi.com/forum.php?mod=forumdisplay&fid=125
Good luck!

GooballDiesel said:
Not sure what model you have, but if it its the 2020 64G (NON "E") model, then the newest firmware available is - "UMIDIGI_A9_PRO_64GB_V1-0_20220325"
No clue if the ROM is Android 10 or 11, but if it's 10 the only way you're ever getting 11 or higher on that device is to build it yourself... Not a simple task...even if you're already experienced with building ROMs.
Go here to see firmware (ROM) downloads for all Umidigi models - https://community.umidigi.com/forum.php?mod=forumdisplay&fid=125
Good luck!
Click to expand...
Click to collapse
Thanks for the reply I really Appreciate it and yes it's the non e version, I am curious when making roms for your device do you take the firmware of other device running on Android 11 port it to your phone or you just download The Official AOSP Android GSI from Google and modify it? And what is the language when Roming is it Java,Kotlin or Python?

Sirkev said:
thank you, works perfectly, one request though...could you please make a flasjing tutorial for android 12 gsi on the same phone, I have been trying to flash as usual, but I keep getting bootloops on all GSIs I have tried, Android 11 GSIs boot well but the 12 ones don't
Click to expand...
Click to collapse
The umidigi android 11 build does not start the gsi at all, the only ones I tested and worked on were: DotOs(A11) and BlessOs(A11), the rest resulted in bootloops, searching the old a9 pro roms, I found the build with android 10 and I tested gsi on it and it worked very well, but the one rule, which is the flash limit on fastbootd, which is 3,000,000kb, I recommend downloading the compressed file up to 1.1gb after that it will not accept
Here A10: https://www.getdroidtips.com/stock-rom-umidigi-a9-pro/
probably what i explained was confusing and weird, because i'm using translator, more briefly: umidigi's os10 is the best to initialize gsi.
Gsi port oficial/unofficial:https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I tested Miku UI....

GooballDiesel said:
Hey Sirkev,
I am about to start looking into getting Android 12 running on this same device.
Umidigi A9 6GB + 128GB, currently running Android 11.
Please keep me updated with your progress, and I will do the same.
I MIGHT try to compile a custom Android 12 (Possibly even Android 13...) rom for this device if I can find enough time to look into it...
Side question - When you go to Google Play store with YOUR A9 Pro running the stock Android 11 rom, click on your profile picture in top right corner, click "Settings", then expand "About"...
What does your A9 say at the very bottom under "Play Protect Certification"???
Thanks!
Click to expand...
Click to collapse
I'm still on GSI nearly an year since I reflashed stock, but I've always had play protect certification, it was broken when I first flashed dotOs but I found a fix for it

Sidrickel_SD said:
I have Umidigi A9 pro 2020 with Android 10 is there any way I can Update it to Android 11?
Click to expand...
Click to collapse
[How to] flash GSI on Umidigi A7 Pro - Functional Guide
This guide is for flashing GSI on Umidigi A7 Pro device, which was released in 2020 with Android 10. This device supports Project Treble and comes with a super partition that contains system, product and vendor partitions. I tried flashing the...
forum.xda-developers.com
This works just as fine for flashing android 11 and android 12 on umidigi A9 pro(android 10 variant)