Database Develop

[Guide] [Mate 10 Pro] Treble-Compatible ROM installation and Compatibility list

Introduction
This is aimed to be a complete but simple guide for users which want to know what works in the Treble-World on the Mate 10 Pro and 'how to get there', based on other guides and my own findings
Disclaimer: I am not responsible for what you do with your device, you are free, probably old enough to know what you are doing and intelligent enough to read this through.
For the moment I will only speak about my own tests on a BLA L29 as I don't have the possibility to test everything.
Feel free to share your own discoveries via PM (just reuse the same formatting to make things easy)
Requirement
1. PC/Laptop running Windows 10 with adb and fastboot drivers installed
2. Original Huawei USB Type-C Cable
3. Being able to read and use search when a question arises
Summary
0. General Information
I. Unlock the Bootloader
II. Choose your ROM (a.k.a "What works on what")
III. Install your ROM
IV. Miscellaneous / Secondary stuff
V. Bonus : What to do if I am stuck / Bootlooping
0. General Information
To make things easier for everybody, here are some basic informations about your device and some common knowledge :
How do I get in Download / Bootloader / Fastboot Mode ?
Shut down your device, insert your USB cable. Keep the Volume DOWN button pressed and press the Power button, wait.
PRO TIPP : You may also get there from within android, first enable ADB debugging in developer options, then, on your PC open a command prompt and type "adb reboot-bootloader"
How do I get in Recovery Mode ?
While in Download / Bootloader / Fastboot Mode, take the USB cable out, keep the Volume UP button pressed and press the Power button until the phone reboots.
I. Unlock the Bootloader
We allready have a thread by @otonieru perfectly discussing this point, don't forget the Windows 10 fix :
https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535
II. Choose your ROM (a.k.a "What works on what")
This section isn't complete and should be detailed with time. None of these ROMs is specific for the Mate 10 Pro, but thanks to Treble, most images will work. Device-specific modifications are still needed in future, ask your local dev
1. Generic AOSP (Android 8.0 and 8.1) by Phhusson
Link : https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Description : Really basic ROM (basically pure AOSP) which serves as a basis for most of the other ROMs.
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk, Signal strength is reported incorrectly, error message at each start, Play Store tends to hang (solution : wipe the Play Store from recents or force close it)
Actual status : Barebones, can be customized in some ways with overlays.
2. LineageOS 15.1 (Android 8.1) by LuK1337
Link : https://forum.xda-developers.com/honor-view-10/development/rom-lineageos-15-1-t3753000
Description : If you don't know LineageOS, you should have heard about CyanogenMod (CM). This is a super clean, customizable version of Android, based on AOSP
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk (system crashes), Signal strength is reported incorrectly,
root works thanks to addon-su (see Miscellaneous)
Actual status : Working as a daily driver (at least in my case) if you can live with some very small drawbacks.
III. Install your ROM
Once you have unlocked your Bootloader and chosen the ROM your heart desires follow these steps :
1. BACK UP YOUR DATA ! -> You will certainly have to do a factory reset and backing up data should be something natural when flashing something on your phone, even before updates.
2. Download the ROM (latest is probably best, but it's best to read what is said in the respective threads before jumping in the hole.
3. Reboot to the Download / Bootloader / Fastboot Mode (see above)
4. Flash the ROM by opening a command prompt and typing :
Code:
fastboot flash system system.img
where "system.img" is the filename of the ROM you downloaded
5. Reboot the phone by typing :
Code:
fastboot reboot
6. The phone will probably get in a bootloop. Don't panic. This should be normal.
After 4-5 reboot the phone will go in Recovery mode. Make a Factory Reset
7. Reboot
8. Profit
IV. Miscellaneous / Device-Specific stuff
This is probably the more interesting part as it is quite hard to find the correct information for our device concerning these points.
Root
ROMs as Lineage don't come prerooted. To root your phone the only viable solution seems to be addon-su for the moment.
To install you will need to install TWRP (follow the instructions in this link by @Dees_Troy : https://forum.xda-developers.com/mate-10/development/recovery-twrp-3-2-1-0-touch-recovery-t3752399 ), boot to TWRP (same as booting to Recovery, as TWRP is the new Recovery). go to advanced -> adb sideload. Connect your phone to your PC and flash the file using
Code:
adb sideload addonsu-15.1-arm64.zip
finally reboot, go to 'developer options' and chose the desired option under 'root options'. Done.
Camera
When flashing a ROM it will probably come with the stock AOSP or Lineage camera which, just say it, sucks on our device form a quality point of view. Here are the answers found to this problem for the moment. Sadly, there isn't one solution which works for everything and everyone.
Google Camera - GCam
Photos work - Gallery works - Videos don't work
Right now his is probably the best compromise if you want something that works, easy to install, while not wanting every little gimmick (in that case you should probably stay on EMUI - The definition of gimmick). Simply install the apk.
Note : there are probably other versions of GCam that work or will work in future, feel free to inform me / us about better working versions.
Link : https://drive.google.com/file/d/1Rw2lXtSHvOUalpA8YKg_kW2Xj_Gu746M/view
More information / discussion :
https://forum.xda-developers.com/mate-10/help/gcam-mod-mate-10-t3729078
Camera Port from the Mate 9 - needs root
Photos work - Videos don't work - Gallery doesn't work - Most filters and gimmicks work
A bit more complicated to install. The easiest way found for now is to root first using addon-su and then copy the system folder inside this zip into the respective folders using a root enables explorer like solid explorer
Link : https://mega.nz/#!7hQDhQAK!p2s7jQp9-nhp2-O1U2s2GrBB9UVBhgKDtFfHTq_CHvI
More information / discussion : https://forum.xda-developers.com/pr...huawei-stock-camera-app-treble-roms-t3735169/
V. Bonus : What to do if I am stuck / Bootlooping
Remember when I said to back up ? Well I hope you did, because if you are really bootlooped and a reflash of the system image hasn't helped. you will have to reflash the whole device, which isn't quick.
Gladly @mankindtv has got you covered with his great guide : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I hope I could help a bit. Feel free to add your own findings, simply PM me.
Credits -
@otonieru for the great Bootloader unlocking thread
@phhusson for his many efforts to make Treble awesome
@LuK1337 for his many efforts to get things working on the Lineage side as well as for addon-su
@Dees_Troy for his awesome work on TWRP
@mankindtw for his great guide on recovering from the loops of boots

reserved

It's gonna be one of the most helpful threads for the novices.
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
If possible, please add how to go back to stock rom in simplified form.

mdjishadk said:
It's gonna be one of the most helpful threads for the novices.
Click to expand...
Click to collapse
I have lost three days to get out of bootloops and gather the info... I hope nobody else will have to live the same thing (and maybe this can become a dedicated thread to fix the last missing blocks to have a complete experience)

good job

You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956

good job on this one OP btw, video on mate 9 camera port is only broken on 8.1, on 8.0 all camera features work fine except opening of the picture from the camera app itself

Good job man!

Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It might be android 8.1. It worked fine for me when using 20180225 version, didn't test later ones.
What version are you on?

Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It crashed everything on my 8.1 build (and the developer himself recommended me addon-su) maybe a tad harder to use, but at least you learn something at the same time

You should add that the stereo speakers don't work.

Timate5 said:
You should add that the stereo speakers don't work.
Click to expand...
Click to collapse
"Stereo"... When coming from a Nexus 6P this Sally doesn't sound stereo at all... But you're right !

Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues

timo.helfer said:
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
Click to expand...
Click to collapse
That's too bad, android auto uses h264 streaming codec I think. I think this issue will have something to do with hardware acceleration. Have you tried messing around with the acceleration option found in the developer options to see if it might work?

Nice guide! Thank you @ChriKn!
Can you add to the "Generic AOSP (Android 8.0 and 8.1) by Phhusson"'s part that we need to use A-ONLY version of this rom?

I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?

ChriKn said:
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
Click to expand...
Click to collapse
Sure i can write some impressions. I just installed Carbon ROM.

I did flash but is not booting at all.
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks

triconix555 said:
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
Click to expand...
Click to collapse
Let it Bootloop until it goes to erecovery and than factory reset it

Timate5 said:
Let it Bootloop until it goes to erecovery and than factory reset it
Click to expand...
Click to collapse
I did that but it is just boolooping again, I did all tge steos over and over and it just bootloops every tipe even after factory resete, it actualy asked le once to resete since then after a couole of reboots it goes straight to te erecovery, wherz it ask to login on a wifi to download latest bootloader and rom or reboot or shutdown device...

Stable daily driver treble roms?

Hello everybody,
I was just wondering if there's any daily driver Treble roms out there that you would suggest, Thanks ?

I'm using phhtreble AOSP 9.0 v111 (with gapps) on top of Xiaomi.eu 9.1.24 and it's working flawlessly. Only thing I can't test is the screen cast thing, since I don't have an enabled tv and VoLTE since my carrier doesn't use it. Also GCam crashes when trying to use slow mo. One last thing, I'd recommend using Magisk Canary 18.2 since that works. Cheers.

liquid or descendant, im using liquid tho

guglicap said:
... on top of Xiaomi.eu 9.1.24 ...
Click to expand...
Click to collapse
How did you flash MIUI 9.1.24. What I mean did you remove Firmware Update folder from the ZIP or leave it be? I am currently on MIUI 8.7.5 and affraid to get Anti Rollback protection. So I remove this Firmware Update just in case, but after flashing such ZIP my MI8SE doesn't want to boot. It stucks on MI Unlocked logo, it is not even a bootloop.

Doman said:
How did you flash MIUI 9.1.24. What I mean did you remove Firmware Update folder from the ZIP or leave it be? I am currently on MIUI 8.7.5 and affraid to get Anti Rollback protection. So I remove this Firmware Update just in case, but after flashing such ZIP my MI8SE doesn't want to boot. It stucks on MI Unlocked logo, it is not even a bootloop.
Click to expand...
Click to collapse
I think Xiaomi.eu roms shouldn't trigger anti rollback anyway. If you want to be safe flash a China Pie rom, then Xiaomi.eu 9.1.24 then whatever. I think I did china 9.1.3, eu 9.1.24 and PE 190111, but I'm not sure

@guglicap
Thanks for all the tips. Before I had MIUI EU 8.7.5 as a base. I could run most treble GSI, but with some problems and issues (like phone reboot after trying to make call or a few reboots before the system finally started). With MIUI EU 9.1.24 as a base they seems to run much better. I will try to test more features soon.
A few remarks from myself for anyone who wants to try treble GSI:
1. Flash full MIUI EU zip, do not remove Firmware Update folder as I tried before. Firmware Update contains some necessary files to be flash to run latest builds. Regarding the Anti Rollback protection... I had a FALSE response for fastboot getvar anti on MIUI EU 8.7.5, and after MIUI EU 9.1.24 I have anti:1... so it is still safe.
2. Use MIUI 9.1.24 (xiaomi.eu_multi_MI8SE_9.1.24_v10-9) as a base, not the newer builds, as they did not work for me. Also use TWRP 1227 for this build.
3. You can also use MIUI stable 10.2.2 (xiaomi.eu_multi_MI8SE_V10.2.2.0.PEBCNXM_v10-9), but this build works with TWRP 1217.
4. The precedure to run GSI is as below:
a) preferably clean: System, Data, Cache, Dalvik-Cache
b) flash MIUI EU as above, make sure it boots
c) flash treble GSI as System Image (there is many available, I prefer Resurrection Remix, LiquidRemix, HavocOS, AEX, AOISP... I find them the most customizable)
d) clean Cache, Dalvik-Cache, Data (or format Data as an option)
e) disable dm-verity in TWRP => Advanced => RM-dm-verity (very important, as most of the GSI will not run without this step)
What I still need to figure out is:
- encryption (that is a must have for me, so far with no luck on MIUI nor on treble GSI ROMs using the system build in option)
- camera (either working MIUI Camera or GCam, as the AOSP cameras are really bad)

Doman said:
@guglicap
Thanks for all the tips. Before I had MIUI EU 8.7.5 as a base. I could run most treble GSI, but with some problems and issues (like phone reboot after trying to make call or a few reboots before the system finally started). With MIUI EU 9.1.24 as a base they seems to run much better. I will try to test more features soon.
A few remarks from myself for anyone who wants to try treble GSI:
1. Flash full MIUI EU zip, do not remove Firmware Update folder as I tried before. Firmware Update contains some necessary files to be flash to run latest builds. Regarding the Anti Rollback protection... I had a FALSE response for fastboot getvar anti on MIUI EU 8.7.5, and after MIUI EU 9.1.24 I have anti:1... so it is still safe.
2. Use MIUI 9.1.24 (xiaomi.eu_multi_MI8SE_9.1.24_v10-9) as a base, not the newer builds, as they did not work for me. Also use TWRP 1227 for this build.
3. You can also use MIUI stable 10.2.2 (xiaomi.eu_multi_MI8SE_V10.2.2.0.PEBCNXM_v10-9), but this build works with TWRP 1217.
4. The precedure to run GSI is as below:
a) preferably clean: System, Data, Cache, Dalvik-Cache
b) flash MIUI EU as above, make sure it boots
c) flash treble GSI as System Image (there is many available, I prefer Resurrection Remix, LiquidRemix, HavocOS, AEX, AOISP... I find them the most customizable)
d) clean Cache, Dalvik-Cache, Data (or format Data as an option)
e) disable dm-verity in TWRP => Advanced => RM-dm-verity (very important, as most of the GSI will not run without this step)
What I still need to figure out is:
- encryption (that is a must have for me, so far with no luck on MIUI nor on treble GSI ROMs using the system build in option)
- camera (either working MIUI Camera or GCam, as the AOSP cameras are really bad)
Click to expand...
Click to collapse
About camera, this works well for me https://f.celsoazevedo.com/file/gcamera/MGC_6.1.021_MI8_V2b_plus3.apk
you need to flash a Magisk module for the fix which is in another thread. Even slow mo works.
Also, I never had a problem with dm-verity, could you elaborate on that? I'm curious now.

guglicap said:
... Also, I never had a problem with dm-verity, could you elaborate on that? I'm curious now.
Click to expand...
Click to collapse
phhtreble AOSP 9.0 v111 ROM worked out-of-the-box, with dm-verity untouched. But for many other ROMs I got bootloop. You need to disable dm-verity to make those ROMs to boot properly.

phhtreble v111 with magisk on top of miui pro seems to work without any problem.
The only bug i experience is that google camera crashes when entering slow-mo mode. Also, notification light works only for charging battery.
Geekbench 4 shows the same results as on miui, battery life seems pretty solid.
Currently using it as daily driver, no problems so far.

adrian.boata.7 said:
phhtreble v111 with magisk on top of miui pro seems to work without any problem.
The only bug i experience is that google camera crashes when entering slow-mo mode. Also, notification light works only for charging battery.
Geekbench 4 shows the same results as on miui, battery life seems pretty solid.
Currently using it as daily driver, no problems so far.
Click to expand...
Click to collapse
does double tap to wake work on you ?

twentyfourinc said:
does double tap to wake work on you ?
Click to expand...
Click to collapse
Hi, apparently it doesn't.

So, after i've spent few days with phhtreble v111, i've noticed the following bugs:
-Bluetooth call doesn't work (the phone rings, music stops playing, but the call runs through the phone speaker)
-Double tap to wake doesn't work
-LED lights up only when charging (Lightflow and other apps designed to take control over it are unable to do it)
-Front facing flash is dead
-Slow motion crashes camera app.
In rest, everything else seem to work fine, even the notch cutout.
Battery and performance are rock solid, substratum is fully compatible.
For camera, i use BSG's Google Camera, which excepting front flash and slow-motion, works like a charm.
Since those bugs are not critical or annoying, at least for me, i currently recommend it as a daily driver.

[ROM]-Working MIUI 11 EU PIE for Mi Max 2 Oxygen [9]-[stable-ish]i

Android Version : MIUI-11-EU-PIE Easy recovery install.
You should be having proper knowledge of flashing Custom ROM and how to Restore a phone if anything goes wrong.
Take complete backup before taking any action based on this thread. I am not responsible for any action taken by you.
I am just compiling all the information / files available on different websites into this thread, I have patched together with cyber spit, bubblegum, and tape, for a pretty much fully working MIUI-11--EU-PIE running rom. With the help from Mohzuned. I have removed what I believe to be all of the bloat. We worked to modify a working pie vendor. Magisk v20 modified boot for root access, Just install magisk manager.
All Credit goes to respective developer/s. I request XDA moderator and or Developer of Respective files to let me know if I have forgotten to mentioned (give credit) their name in this thread. The Download Links are given directly from respective Developer/s.
You need the following two files to Test MIUI-11-EU-PIE on Mi Max 2 (Oxygen). This ROM recovery is ported from the Xiaomi RedMi with many patches and customized from various sources. This ROM maybe Stable enough for your daily use on Mi Max 2. I have access to two MM2 4/64 Global versions using a 1tb sd card one on At&t the other on Tmobile and MOST features I need are currently working.
1a. Treble Mi Max 2 Recovery 3.2.1 https://androidfilehost.com/?fid=5862345805528056270
1b. OrangeFox Recover 10
https://sourceforge.net/projects/ora...n.zip/download
2. MIUI-11-EU-PIE
https://drive.google.com/file/d/15lRb49s75rqVV0Kg8C16Eao_BuTPvBWr/view?usp=drivesdk
First step:
Start your phone into recovery and Flash a Treble recovery, if already not flashed. Restart into Recovery.
Click Wipe then Advance wipe and clear System, Vendor, Boot, Data, Cache, and Dalvick cache.
Second step:
Now Extract the Downloaded Rom files in Recovery backup folder. You should know where and how to Extract. (Use extract tool for android or pc then copy paste to recovery backup folder.)
Third step:
Click Restore and Select System, Boot, Vendor and Swipe to confirm. Wait for restore to complete. If any errors, Reboot recovery and try again. Or Mount the System, Vendor, Boot and try again. After Restore completes Reboot. Please allow 1-2 Minutes for first boot.
What works:
?
What doesn't work:
?
If I missed anything in the above, kindly let me know to include. If you make any further updates / patches that makes this ROM more stable / perfect or enables new features, please don't hesitate to message me to include in this thread.
I have an old PC running windows with 8gb max HDD at any one given time, So if you would like to make the recovery image into a flashable zip, I'd be happy to update/add it.
If you can afford it, Im trying to save for a computer from this decade, any help is appreciated
https://www.paypal.me/LiamMcGinnisIv
If you would like to use the boot, vendor, system, or any other files, All I ask is pass on the proper credits.
Any Others Who May Have Been Missed
Best of Luck and Happy Flashing )

Camera/Torch.

Camera, fingerprint and fm radio, dont work, congratulations, good rom. Thanks.

Cool....... thanks dude
liammc83 said:
Camera/Torch.
Click to expand...
Click to collapse
Iam ready for the test ride......

I will test today. Thank you for your job!

Beast developer...too fast man thanks

If you will fix Camera and Torch it will be great! We are all waiting! Thank you!
---------- Post added at 06:51 AM ---------- Previous post was at 06:38 AM ----------
May be it is better to do Port from Mi Mix 2S? Camera and Torch worked on that port.

Bro.......
I cannot find the fingerprint option in the rom..?
Firstly I upgraded from the nougat rom.,it made me to suck....it booted but instantly rebooted to recovery on every boot......
Cannot find the fingerprint option ..,Cannot add the face unlock option due to the camera bug...,it's harder always using pattern/pin.,? flashlight ? issue is negligible.....
But mi cloud has no issues and working fine able to login..
Home button isn't working.,full screen guesture option isn't seen in the rom..
May be it's because of the redmi note 4x....it might be good if it's from max3 or mix2s as u done previously.,only hotspot bug majorly
You are too good bro....,you are beastly fast and tough..,???

Please fix the camera!!!

zavorotnii said:
Please fix the camera!!!
Click to expand...
Click to collapse
He is trying continuously and I believe soon it will be resolved.

zavorotnii said:
Please fix the camera!!!
Click to expand...
Click to collapse
I'm not screaming "Donate!!!!!"
I do this for free for a phone I no longer use, please be patient.
Considering all sources from xiaomi are outdated, And this is being done again for FREE with modifications on an ancient netbook.
I also can now verify, I have a working modified vendor/boot image that will run gsi images, But again since problems with vendor no camera, Still working on it.

Sorry, I just asked. I understand your position and ready to test new changes

No need to wait for me to port.
https://forum.xda-developers.com/mi-max-2/development/mi-max-2-oxygen-gsi-bootable-vendor-t3987191

I really liked this rom .. I want to use daily ... only thing that is bothering me is the home button and the camera that is not working? already have a solution? fingerprint to taste .. but you can use with the pin normally

Question Redmi 9T with NVT-ts touch screen unresponsive with custom ROMs

Hello.
I have been trying to get a custom rom flashed on my Redmi 9T the past two days.
The problem I am facing is that the touch screen is not responsive with the flashed ROMs that I have tried.
ROMs I have tried:
PixelPlusUI_3.9_juice-11.0-20210912-1736-OFFICIAL
LegionOS-v3.13-juice-20210922-OFFICIAL-GAPPS
Arrow-v11.0-juice-COMMUNITY-20210809-GAPPS
crDroidAndroid-11.0-20210927-juice-v7.10
What did make the touch screen work was to flash "boot.img" from one of the android 11 builds of MIUI such as "xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11" or "xiaomi.eu_multi_HMNote94G_HM9T_POCO_M3_21.5.27_v12-11" after flashing the custom ROM, but this resulted in "Sytem UI" crashing and wifi not working. There were probably other things that didn't work but I can't have a phone without WiFi so this was not a solution for me.
After looking into what "boot.img" contains, it seems like it contains the kernel and other important system related components.I then tried to flash the following kernels over a new install of the custom ROMs "crDroid" and "PixelPlusUI 3.9":
StormBreaker-lime-r3-0909-0545
CartelProject-lime-BETA-20210915-07
Optimus_Drunk_Citrus_v11.1
But they did not help with getting the touch screen to work.
I also tried a combination of a "boot.img" from an offical android 11 EU MIUI ROM and these three kernels in the hope that I would keep the touch screen fix from "boot.img" and get wifi from the kernels, however every time the kernel was flashed the touch screen stopped working.
This leads me to believe the kernel itself makes the touch screen not work, and other things from the "boot.img" make the WiFi stop working.
So I have a few questions I hope someone can answer:
When do you think Xiaomi will release the source-code for the android 11 kernels that they use in their new MIUI ROMs? As I don't know their release cycles.
When will the firmware for the NVT-ts touchscreen version of Redmi 9T be added to custom kernels?
Is there a way for me to extract the Android 11 MIUI kernel from "boot.img" and flash ONLY that, if that fixes my touchscreen and does not break my WiFi? (If this is legal/allowed/possible)
I don't know anything about android development so if I am wrong please correct me.
Thank you in advance.

1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):​Download​
Fastboot Firmware tgz:​Download​

Atanassoww said:
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):​Download​
Fastboot Firmware tgz:​Download​
Click to expand...
Click to collapse
Thank you for the reply.
However I believe that this is what I did do when I set up the phone with the ROMs.
I still tried to do it exactly as you explained, however this did not work.
I got into a bootloop after flashing firmware through fastboot, even if I cleaned the data using recovery. I tried the Recovery version of the firmware and this worked fine so after that I followed your tutorial just as you described.
This still didn't work, when booted into the Custom ROM the touch screen was still not working at all.
In the meanwhile I found this blog-post:
lemon – Encik Kunci
Posts about lemon written by Encik Kunci
encikkunci.wordpress.com
Where he states and I quote: "Phones with nt36672d display isn’t supported yet." this was posted August 11, 2021.
I don't know who he is or how he knows that.
I am pretty sure it's a kernel problem or firmware or something, regarding the screen being NVT-ts and probably the "nt36672d" variant.
This makes me very sad.

Its indeed an kernel issue, there's ( at least) two screen revisions from two different vendors

coffeemakerexpress said:
Thank you for the reply.
However I believe that this is what I did do when I set up the phone with the ROMs.
I still tried to do it exactly as you explained, however this did not work.
I got into a bootloop after flashing firmware through fastboot, even if I cleaned the data using recovery. I tried the Recovery version of the firmware and this worked fine so after that I followed your tutorial just as you described.
This still didn't work, when booted into the Custom ROM the touch screen was still not working at all.
In the meanwhile I found this blog-post:
lemon – Encik Kunci
Posts about lemon written by Encik Kunci
encikkunci.wordpress.com
Where he states and I quote: "Phones with nt36672d display isn’t supported yet." this was posted August 11, 2021.
I don't know who he is or how he knows that.
I am pretty sure it's a kernel problem or firmware or something, regarding the screen being NVT-ts and probably the "nt36672d" variant.
This makes me very sad.
Click to expand...
Click to collapse
I found this in 4pda:
Quote a reply: Yes, I had the same thing. By the way, if we are talking about OrangeFox recovery, which did not start at all, then it was necessary to use a newer version, I found a link to a google drive on the xda forum, it did not start there.
And on the touch, I also tried 2 custom firmware on them, everything started, but the touch did not work in principle. Only on off or lightweight everyone and on xiaomi.eu worked. I suppose the same case, but I can refine it when the phone is sent back.
ps: Due to freezes and rebots - in the service they changed the motherboard in the end, I'm waiting for the parcel now.

superdragonpt said:
Its indeed an kernel issue, there's ( at least) two screen revisions from two different vendors
Click to expand...
Click to collapse
I see, so my assumption was correct. Thank you for clarifying.
Do you know how often Xiaomi (or if they will at all) release firmware/kernel source codes, and do you know if custom kernel makers/Custom ROM makers, will actually update their kernels/ROMs to use this in the future?
And is there a way/place for me to keep updated on if Xiaomi releases the needed firmware/sourcecode for this display, so that I can ask ROM makers/Kernel makers nicely to add the firmware, assuming they don't know about this issue?
Atanassoww said:
I found this in 4pda:
Quote a reply: Yes, I had the same thing. By the way, if we are talking about OrangeFox recovery, which did not start at all, then it was necessary to use a newer version, I found a link to a google drive on the xda forum, it did not start there.
And on the touch, I also tried 2 custom firmware on them, everything started, but the touch did not work in principle. Only on off or lightweight everyone and on xiaomi.eu worked. I suppose the same case, but I can refine it when the phone is sent back.
ps: Due to freezes and rebots - in the service they changed the motherboard in the end, I'm waiting for the parcel now.
Click to expand...
Click to collapse
So you have the same problem? I'm not sure I understand what you mean here, aside from the touchscreen not working for you either due to this weird display model.

coffeemakerexpress said:
I see, so my assumption was correct. Thank you for clarifying.
Do you know how often Xiaomi (or if they will at all) release firmware/kernel source codes, and do you know if custom kernel makers/Custom ROM makers, will actually update their kernels/ROMs to use this in the future?
And is there a way/place for me to keep updated on if Xiaomi releases the needed firmware/sourcecode for this display, so that I can ask ROM makers/Kernel makers nicely to add the firmware, assuming they don't know about this issue?
So you have the same problem? I'm not sure I understand what you mean here, aside from the touchscreen not working for you either due to this weird display model.
Click to expand...
Click to collapse
Yes or is not Supported right now..

This is just a small update with a possible fix that I haven't tried yet because I'm tired of flashing ROMs all day, I will try it later if I get the motivation to do so. I post this because someone else might have the energy to test this themselves. If I test this I will update this post with an edit or bump this thread.
I Found on a forum called 4PDA where a user by the name "Void_dp" talks about a Xiaomi Redmi 9T with a nt36672d display. The forum is in Russian, but use a translator if you are interested. It is the post this url links to:
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки - 4PDA
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки
4pda.to
I do not know if the website itself or this user is trustworthy or correct, so try this with caution and I am not responsible for anything you decide to do or happens to you or your computer, or phone.
In short he explains that crDroid 7.9 (7.10 is the current version, and is the one I tried) use a different kernel than the Stormbreaker kernel than crDroid 7.10 uses.
He says if you have crDroid 7.10 installed you have to format data before trying this.
1. Download crDroid 7.9 and crDroid 7.10
2. Get the "boot.img" from the crDroid 7.9 rom and extract it
3. Open the zip file for crDroid 7.10 (do not extract anything) and replace the "boot.img" (7.10 version) with the one you just extracted (7.9 version)
4. Do a clean flash with this modified ROM you just made.
That is all he said, but if it doesn't work my first thought is to try the original crDroid 7.9 rom, if you don't care about running the latest update. This is probably not smart in relation to security patches and stuff like that. I take no responsibility for whatever happens.
Additional information:
I checked the Changelog for the crDroid roms, and they changed the kernel from "Optimus Drunk kernel 11.0" to "Stormbreaker" when they upgraded their ROMs version from 7.9 to 7.10.
I tried using the "Optimus Drunk kernel 11.1" kernel in my trial and error with the ROMs without luck, so I will try to flash some roms together with the "Optimus Drunk kernel 11.0" if I can find it.
Link to crDroid ROM for Redmi 9t:
crDroid.net - Download crDroid for supported devices
official crDroid ROM website
crdroid.net

coffeemakerexpress said:
This is just a small update with a possible fix that I haven't tried yet because I'm tired of flashing ROMs all day, I will try it later if I get the motivation to do so. I post this because someone else might have the energy to test this themselves. If I test this I will update this post with an edit or bump this thread.
I Found on a forum called 4PDA where a user by the name "Void_dp" talks about a Xiaomi Redmi 9T with a nt36672d display. The forum is in Russian, but use a translator if you are interested. It is the post this url links to:
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки - 4PDA
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки
4pda.to
I do not know if the website itself or this user is trustworthy or correct, so try this with caution and I am not responsible for anything you decide to do or happens to you or your computer, or phone.
In short he explains that crDroid 7.9 (7.10 is the current version, and is the one I tried) use a different kernel than the Stormbreaker kernel than crDroid 7.10 uses.
He says if you have crDroid 7.10 installed you have to format data before trying this.
1. Download crDroid 7.9 and crDroid 7.10
2. Get the "boot.img" from the crDroid 7.9 rom and extract it
3. Open the zip file for crDroid 7.10 (do not extract anything) and replace the "boot.img" (7.10 version) with the one you just extracted (7.9 version)
4. Do a clean flash with this modified ROM you just made.
That is all he said, but if it doesn't work my first thought is to try the original crDroid 7.9 rom, if you don't care about running the latest update. This is probably not smart in relation to security patches and stuff like that. I take no responsibility for whatever happens.
Additional information:
I checked the Changelog for the crDroid roms, and they changed the kernel from "Optimus Drunk kernel 11.0" to "Stormbreaker" when they upgraded their ROMs version from 7.9 to 7.10.
I tried using the "Optimus Drunk kernel 11.1" kernel in my trial and error with the ROMs without luck, so I will try to flash some roms together with the "Optimus Drunk kernel 11.0" if I can find it.
Link to crDroid ROM for Redmi 9t:
crDroid.net - Download crDroid for supported devices
official crDroid ROM website
crdroid.net
Click to expand...
Click to collapse
I DIDN't work for me, I got a bootloop, maybe it will work for u

hamid_dabouz said:
I DIDN't work for me, I got a bootloop, maybe it will work for u
Click to expand...
Click to collapse
Thats sad to hear, this phone is a nightmare. I haven't tried this yet, maybe I will try this weekend.
I'm wondering though, did you FORMAT data after flashing?
By bootloop, which of these do you mean:
That it never enters the "loading phase" of the OS (Android/rom splash screen)
That it gets stuck and restarts in the "loading phase" of the OS (Android/rom splash screen)
That it just kicks you to recovery/fastboot over and over again, without showing the OS loading screen
Or something else?

coffeemakerexpress said:
Thats sad to hear, this phone is a nightmare. I haven't tried this yet, maybe I will try this weekend.
I'm wondering though, did you FORMAT data after flashing?
By bootloop, which of these do you mean:
That it never enters the "loading phase" of the OS (Android/rom splash screen)
That it gets stuck and restarts in the "loading phase" of the OS (Android/rom splash screen)
That it just kicks you to recovery/fastboot over and over again, without showing the OS loading screen
Or something else?
Click to expand...
Click to collapse
Ohh Jeesus...

OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers

superdragonpt said:
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
Click to expand...
Click to collapse
Thank you for respond, But i already flashed Two versions of " stormbreaker"kernel one of them worked but the touch is going insane, if you clicked on somewhere on the screen it will respond in other place of the screen ( i hope you understand what i'm saying)

hamid_dabouz said:
Thank you for respond, But i already flashed Two versions of " stormbreaker"kernel one of them worked but the touch is going insane, if you clicked on somewhere on the screen it will respond in other place of the screen ( i hope you understand what i'm saying)
Click to expand...
Click to collapse
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers

Atanassoww said:
Ohh Jeesus...
Click to expand...
Click to collapse
Why that reaction? I am here to learn and try to solve my problem, if you have any advice please elaborate on why what I said was wrong or dumb so I won't make the same mistake again.
superdragonpt said:
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
Click to expand...
Click to collapse
I will maybe try the Stormbreaker kernel for Poco M3 this weekend as well then to check it out.
superdragonpt said:
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Click to expand...
Click to collapse
Thank you for this informative answer, do I take it as this is something you will look into? If I can help by using adb or something, to get information from my phone just tell me what to do.

superdragonpt said:
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Click to expand...
Click to collapse
Is this the extract you were talking about? It has the firmware for the touchscreens and everything for android 11. but it is for the Chinese version, so I don't know if that matters.
redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
qssi-user 11 RKQ1.201004.002 V12.0.3.0.RJQCNXM release-keys - redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
github.com
I don't know if this is relevant but I thought I would share it since I found it. Someone smarter than me can maybe use it to make the touchscreen work.

I fix dt2w on Xtended custom rom. Replace kernel and flash Magisk extension. I don.t try others roms....

coffeemakerexpress said:
Is this the extract you were talking about? It has the firmware for the touchscreens and everything for android 11. but it is for the Chinese version, so I don't know if that matters.
redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
qssi-user 11 RKQ1.201004.002 V12.0.3.0.RJQCNXM release-keys - redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
github.com
I don't know if this is relevant but I thought I would share it since I found it. Someone smarter than me can maybe use it to make the touchscreen work.
Click to expand...
Click to collapse
coffeemakerexpress said:
Hello.
I have been trying to get a custom rom flashed on my Redmi 9T the past two days.
The problem I am facing is that the touch screen is not responsive with the flashed ROMs that I have tried.
ROMs I have tried:
PixelPlusUI_3.9_juice-11.0-20210912-1736-OFFICIAL
LegionOS-v3.13-juice-20210922-OFFICIAL-GAPPS
Arrow-v11.0-juice-COMMUNITY-20210809-GAPPS
crDroidAndroid-11.0-20210927-juice-v7.10
What did make the touch screen work was to flash "boot.img" from one of the android 11 builds of MIUI such as "xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11" or "xiaomi.eu_multi_HMNote94G_HM9T_POCO_M3_21.5.27_v12-11" after flashing the custom ROM, but this resulted in "Sytem UI" crashing and wifi not working. There were probably other things that didn't work but I can't have a phone without WiFi so this was not a solution for me.
After looking into what "boot.img" contains, it seems like it contains the kernel and other important system related components.I then tried to flash the following kernels over a new install of the custom ROMs "crDroid" and "PixelPlusUI 3.9":
StormBreaker-lime-r3-0909-0545
CartelProject-lime-BETA-20210915-07
Optimus_Drunk_Citrus_v11.1
But they did not help with getting the touch screen to work.
I also tried a combination of a "boot.img" from an offical android 11 EU MIUI ROM and these three kernels in the hope that I would keep the touch screen fix from "boot.img" and get wifi from the kernels, however every time the kernel was flashed the touch screen stopped working.
This leads me to believe the kernel itself makes the touch screen not work, and other things from the "boot.img" make the WiFi stop working.
So I have a few questions I hope someone can answer:
When do you think Xiaomi will release the source-code for the android 11 kernels that they use in their new MIUI ROMs? As I don't know their release cycles.
When will the firmware for the NVT-ts touchscreen version of Redmi 9T be added to custom kernels?
Is there a way for me to extract the Android 11 MIUI kernel from "boot.img" and flash ONLY that, if that fixes my touchscreen and does not break my WiFi? (If this is legal/allowed/possible)
I don't know anything about android development so if I am wrong please correct me.
Thank you in advance.
Click to expand...
Click to collapse
Atanassoww said:
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):​Download​
Fastboot Firmware tgz:​Downl​
Click to expand...
Click to collapse

bogteo said:
I fix dt2w on Xtended custom rom. Replace kernel and flash Magisk extension. I don.t try others roms....
Click to expand...
Click to collapse
Please can you explain more ?

I tried with crdroid 7.9 without success. still cannot use the touchscreen
m210j19sy I began with global miui rom

Confusion with firmware, vendor etc.

Hey guys,
as my last phone was an OPO where flashing custom roms was pretty simple, I don't understand the principle of flashing the Mi 9T Pro, where you always have to consider and install separately the right version of firmware, vendor etc. I would be thankful if someone could explain it to me.
I try to order my questions:
Why are ROM, firmware and vendor separated and don't come together in a single file?
How do I find out the correct version of firmware for my phone? And what is the difference between those versions, eg. China, Global and EU? And is EU the same as EEA?
The recommendation is always to update the firmware when flashing a ROM - but for vendor it is not (like for LineageOS 18.1) - why? Wouldn't it be beneficial to update vendor, too? As I understand, vendor contains necessary proprietary binaries.
Is it recommended to regularly update the firmware even if there is no update for my ROM? And what is the most comfortable way, is something like OTA possible?
What is different about TWRP images with a "_9"? (twrp-3.5.0_9-0-raphael.img vs. twrp-3.4.0-0 or -1). Recently broke the recovery of my OPO when I installed its latest twrp version which had the 9
Thank you for helping an interested person with little IT/android knowledge

oriped said:
Hey guys,
as my last phone was an OPO where flashing custom roms was pretty simple, I don't understand the principle of flashing the Mi 9T Pro, where you always have to consider and install separately the right version of firmware, vendor etc. I would be thankful if someone could explain it to me.
I try to order my questions:
Why are ROM, firmware and vendor separated and don't come together in a single file?
How do I find out the correct version of firmware for my phone? And what is the difference between those versions, eg. China, Global and EU? And is EU the same as EEA?
The recommendation is always to update the firmware when flashing a ROM - but for vendor it is not (like for LineageOS 18.1) - why? Wouldn't it be beneficial to update vendor, too? As I understand, vendor contains necessary proprietary binaries.
Is it recommended to regularly update the firmware even if there is no update for my ROM? And what is the most comfortable way, is something like OTA possible?
What is different about TWRP images with a "_9"? (twrp-3.5.0_9-0-raphael.img vs. twrp-3.4.0-0 or -1). Recently broke the recovery of my OPO when I installed its latest twrp version which had the 9
Thank you for helping an interested person with little IT/android knowledge
Click to expand...
Click to collapse
If you stick with stock ROMs, you don't need to worry anout firmware, vendor, etc.
You update by OTA or by downloading the so-called zip/recovery package that can be installed by the stock recovery or from TWRP
Only in rare occasions (usually when people screw something, want to go back from custom ROMs and so), you would need Xiaomi Flash tool and the so-called tgz/fastboot packages.
They include vendor and again, you don't need to worry about downloading and flashing vendor
How (and do you really) need downloading and flashing vendor for LOS, I have no idea (I don't use AOSP ROMs)
What do you mean by Eu?
If you mean Xoaomi.eu ROMs - they are not the same as stock EEA ROMs.
Actually, Xiaomi.eu IS NOT stock or even not an official ROM endorsed by Xiaomi Inc.
Personally, I started on my Mi 9T two years ago with A9/MIUI 10 (I think). Mine was EEA and I followed the updates till A10/MIUI 11.
From the beginning I unlocked Bootloader, played with various versions and incarnations of TWRP, I always rooted my phone with the latest (Canary) Magisk, played with debloating, various Magisk modules, etc.
I also played with Kali Nethunter at the time
Never in my carrier I needed to use Xiaomi Flash tool and tgz/fastboot firmwares (specially not vendor packages), always only zip/recovery ROM packages were enough for me
A year ago I moved to Xiaomi.eu weeklies. A month ago I decided it was enough and settled to Xiaomi.eu but Stable.
Xiaomi.eu, both weeklies and stable are built on A11/MIUI 12.5 (recently stock was finally also updated to A11/MIUI 12+ but I didn't return to stock)
Since 'official' Magisk is kind of 'dead' for 5 or so months, for the last two months I play with Magisk Alpha (recently incl. Zygisk and so)
Again, I have no experience (and no interests at all) about AOSP and GSI ROMs, particularly the LOS (in my past life with another phone, I used an earlier version of LOS for quite some time there)
Some links maybe of interest for you to read/learn from:
https://c.mi.com/thread-1857937-1-1.html
How to Flash Xiaomi Firmware using MIUI Fastboot and Recovery ROM
Ever since the dawn of affordable smartphones in countries like India and China, the demand for more has increased. The consumers now, more than ever, are
www.getdroidtips.com
How-to use Xiaomi Flash Tool to flash or install Firmware
Step-by-Step guidelines to use Xiaomi Flash Tool to Flash Stock Firmware on Xiaomi Smartphone and Tablets.
xiaomiflashtool.com
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
[INFO] Widevine L1 Support
This thread should answer most of your questions regarding Widevine L1 support on your device(s). I will try to keep it maintained and up-to-date. Notes: * This list includes only supported Android 10+ devices that either support Widevine L1 officially, or support it unofficially by Xiaomi.eu...
xiaomi.eu
What the letters in the MIUI version designation mean
MIUI V12.0.5.0. QFJMIXM - Android version M - Android 6.x (Marshmallow) N - Android 7.x (nugát) O - Android 8.x (Oreo) P - Android 9.x (Pie) Q - Android 10.x R - Android 11.x S - Android 12.x - device code (phone model) JA - Xiaomi Mi 10 Pro JB - Xiaomi Mi 10 JC - Redmi 9 JO - Redmi Note 9 JZ...
xiaomi.eu
PS: Yeah, I am from Mi 9T (not Pro) world, but your questions and my comments and links are common and more general (not limited to Mi 9T Pro or plain, or to MI 9 *** range of models, but general for Xiaomi devices)

But if you meant EU letters in the stock ROM name - then yes, EU means European and that is EEA stock ROM
Similarly like MI letters (probably abbreviated from MIUI) in the stock ROM name mean International - see the attachement
Btw, this app might be also useful (not only for newbies):
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
Open your Settings/My Device/MIUI Version (top left), aka System Updater app, read the full name of your stock ROM and compare against the attached chart

Thank you!
One more question: How do I change magisk to vvb2060 alpha version?

oriped said:
Thank you!
One more question: How do I change magisk to vvb2060 alpha version?
Click to expand...
Click to collapse
His Github page where you can download the 'latest official' Alpha:
GitHub - vvb2060/magisk_files
Contribute to vvb2060/magisk_files development by creating an account on GitHub.
github.com
Newer, unofficial (I'm on the latest) can be downloaded here:
Magisk alpha
带遥测的第三方Magisk版本，比Canary通道更加不稳定，与上游行为有较大不同，无安全性保证，无可用性保证，无隐私协议。 问题反馈请加群发送日志文件，非alpha独有问题建议先在GitHub反馈。
t.me
You download and install Magisk (Alpha) apk (formerly, in Magisk v22 it was Magisk mngr)
If you are already rooted, you can take then Direct install to 'upgrade' to the same Magisk Alpha version
If you were not rooted yet, you can patch your boot.img (it can be extracted from your zip/recovery or tgz/fastboot stock ROM), later you will flash that patched img by Fastboot.
Instead of boot.img, you can patch boot.emmc.win Boot backup from TWRP
You can also rename magisk apk file (that Magisk Alpha app you downloaded) to install.zip and flash through TWRP (old school for those who are accustomed to flash Magisk zip through TWRP).
If you have the latest 3.5.-9 official TWRP, you don't even need to rename, you can flash as it was downloaded as magisk apk file
But be aware that Magisk Alpha has no more MagiskHide, instead it is now DenyList.
And configuring DenyList to pass SafetyNet is another (short) story

zgfg said:
If you stick with stock ROMs, you don't need to worry anout firmware, vendor, etc.
You update by OTA or by downloading the so-called zip/recovery package that can be installed by the stock recovery or from TWRP
Only in rare occasions (usually when people screw something, want to go back from custom ROMs and so), you would need Xiaomi Flash tool and the so-called tgz/fastboot packages.
They include vendor and again, you don't need to worry about downloading and flashing vendor
How (and do you really) need downloading and flashing vendor for LOS, I have no idea (I don't use AOSP ROMs)
What do you mean by Eu?
If you mean Xoaomi.eu ROMs - they are not the same as stock EEA ROMs.
Actually, Xiaomi.eu IS NOT stock or even not an official ROM endorsed by Xiaomi Inc.
Personally, I started on my Mi 9T two years ago with A9/MIUI 10 (I think). Mine was EEA and I followed the updates till A10/MIUI 11.
From the beginning I unlocked Bootloader, played with various versions and incarnations of TWRP, I always rooted my phone with the latest (Canary) Magisk, played with debloating, various Magisk modules, etc.
I also played with Kali Nethunter at the time
Never in my carrier I needed to use Xiaomi Flash tool and tgz/fastboot firmwares (specially not vendor packages), always only zip/recovery ROM packages were enough for me
A year ago I moved to Xiaomi.eu weeklies. A month ago I decided it was enough and settled to Xiaomi.eu but Stable.
Xiaomi.eu, both weeklies and stable are built on A11/MIUI 12.5 (recently stock was finally also updated to A11/MIUI 12+ but I didn't return to stock)
Since 'official' Magisk is kind of 'dead' for 5 or so months, for the last two months I play with Magisk Alpha (recently incl. Zygisk and so)
Again, I have no experience (and no interests at all) about AOSP and GSI ROMs, particularly the LOS (in my past life with another phone, I used an earlier version of LOS for quite some time there)
Some links maybe of interest for you to read/learn from:
https://c.mi.com/thread-1857937-1-1.html
How to Flash Xiaomi Firmware using MIUI Fastboot and Recovery ROM
Ever since the dawn of affordable smartphones in countries like India and China, the demand for more has increased. The consumers now, more than ever, are
www.getdroidtips.com
How-to use Xiaomi Flash Tool to flash or install Firmware
Step-by-Step guidelines to use Xiaomi Flash Tool to Flash Stock Firmware on Xiaomi Smartphone and Tablets.
xiaomiflashtool.com
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
[INFO] Widevine L1 Support
This thread should answer most of your questions regarding Widevine L1 support on your device(s). I will try to keep it maintained and up-to-date. Notes: * This list includes only supported Android 10+ devices that either support Widevine L1 officially, or support it unofficially by Xiaomi.eu...
xiaomi.eu
What the letters in the MIUI version designation mean
MIUI V12.0.5.0. QFJMIXM - Android version M - Android 6.x (Marshmallow) N - Android 7.x (nugát) O - Android 8.x (Oreo) P - Android 9.x (Pie) Q - Android 10.x R - Android 11.x S - Android 12.x - device code (phone model) JA - Xiaomi Mi 10 Pro JB - Xiaomi Mi 10 JC - Redmi 9 JO - Redmi Note 9 JZ...
xiaomi.eu
PS: Yeah, I am from Mi 9T (not Pro) world, but your questions and my comments and links are common and more general (not limited to Mi 9T Pro or plain, or to MI 9 *** range of models, but general for Xiaomi devices)
Click to expand...
Click to collapse
Hi I'm K20pro/Mi 9t pro user currently on latest 12.5.1.0 raphael stock rom, can you give bit of advice about going to eu stable rom(12.5.6.0 latest) from stock miui. I do have orange fox recovery installed but confused about what to wipe(dalvik/cache/...other options) or format data(yes confirmation option) and if rom flash needs to be in clean internal storage via format data(yes confirmation option), will i need latest firmware with it or just eu rom.
After that i will install magisk
I'm pretty much new custom roms with just a week of 35-40 hours of research, I will be glad if you or anyone reading this, willing to clear my doubts.
Thank you in advance

jacksterky said:
Hi I'm K20pro/Mi 9t pro user currently on latest 12.5.1.0 raphael stock rom, can you give bit of advice about going to eu stable rom(12.5.6.0 latest) from stock miui. I do have orange fox recovery installed but confused about what to wipe(dalvik/cache/...other options) or format data(yes confirmation option) and if rom flash needs to be in clean internal storage via format data(yes confirmation option), will i need latest firmware with it or just eu rom.
After that i will install magisk
I'm pretty much new custom roms with just a week of 35-40 hours of research, I will be glad if you or anyone reading this, willing to clear my doubts.
Thank you in advance
Click to expand...
Click to collapse
When switching to Xiaomi.eu (and generally when switching the ROMs) it's required to Format Data (not just to Wipe Data - fornatting does more than wiping)
More about downloading and installing Xiaomi.eu ROMs find on their forum, in the OP posts:
MIUI 12.0 - MIUI 12.0/12.1/12.2/12.5 STABLE RELEASE
STABLE RELEASE RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Better also Wipe Cache (Dalwik will be wiped as part of Data partition hence you can wipe it too but it won't matter)
You can use OF but make sure you use a recent/latest version, or use the latest official TWRP. More about the suitable custom recoveries can be found in the Forum/thread as above
Generally:
- backup your photos, docs, etc (transfer to PC)
- use Google to backup, some apps like Whatsapp provide backing up to clouds, etc
- With Xiaomi Cloud you can backup installed apps and their settings, Contacts, Call History, SMS, even WiFi passwords
- Download the ROM to Internal memory
- reboot to OF/TWRP and install (flash) the downloaded zip
- Wipe Dalwik and Cache (TWRP automatically offers upon installing)
- Do not reboot to System but go back in OF/TWRP and do Format Data (do not Format Data before flashing the zip because Formatting Data will wipe your Internal memory, hence it would also wipe your downloaded zip - although you could, but then flash the zip from OTG stick)
Then reboot to System, setup your new Android/MIUI, restore things...

zgfg said:
When switching to Xiaomi.eu (and generally when switching the ROMs) it's required to Format Data (not just to Wipe Data - fornatting does more than wiping)
More info about downloading and installing Xiaomi.eu ROMs find on their forum, in the OP posts:
MIUI 12.0 - MIUI 12.0/12.1/12.2/12.5 STABLE RELEASE
STABLE RELEASE RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Better also Wipe Cache (Dalwik will be wiped as part of Data partition hence you can wipe it too but it won't matter)
You can use OF but make sure you use a recent/latest version, or use the latest official TWRP. More about suitable custom recoveries can be found on the Forum/thread as above
Generally:
- backup your photos, docs, etc (transfer to PC)
- use Google to backup, some apps like Whatsapp provide backing up to clouds, etc
- With Xiaomi Cloud you can backup installed apps and their settings, Contacts, Call History, SMS, even WiFi passwords
- Download the ROM to Internal memory
- reboot to OF/TWRP and install (flash) the downloaded zip
- Wipe Dalwik and Cache (TWRP automatically offers upon installing)
- Do not reboot to System but go back in OF/TWRP and do Format Data (do not Format Data before flashing the zip because Formatting Data will wipe your Internal memory, hence it would also wipe your downloaded zip - although you could, but then flash the zip from OTG stick)
Then reboot to System, setup your new Android/MIUI, restore things...
Click to expand...
Click to collapse
I'll follow your instructions step by step.
Again thank you for your quick support, really appreciate your help

jacksterky said:
I'll follow your instructions step by step.
Again thank you for your quick support, really appreciate your help
Click to expand...
Click to collapse
Do not wipe any other partition, specially not Persist (you would loose DRM L1), modem, and so on.
Since you are on stock, all that is good and Xiaomi.eu will actually flash only to System and Vendor
You probably use pin or pattern for screen unlocking, you will need to enter the same when you boot to OF/TWRP that it can read Internal memory (later, when you Format Data it will be gone and you will have to setup your pin/pattern again once you boot to your new System)
First time you boot to the new System give it some time (might be slow at first, doing things in the background)
Xiaomi.eu 'hides' that Bootloader is unlocked, hence you will pass SafetyNet (i e., Device will be certified in Playstore) right away
You will also have DRM L1 (you may need to download the certificate, but that's easy)
When you later need to reboot to OF/TWRP, you don't need to struggle with key combos - in Xiaomi.eu, from System updater, when you open the top-right menu, you have Reboot to recovery option (root not needed)
Later you can think about rooting with Magisk, installing nodules, additionally debloating, etc
Be aware that raphael is on the end-of-line and it's not clear would it receive any more Xiaomi.eu updates (or if, then just a newer Security Patch).
But that's also the case with stock

zgfg said:
Do not wipe any other partition, specially not Persist (you would loose DRM L1), modem, and so on.
Since you are on stock, all that is good and Xiaomi.eu will actually flash only to System and Vendor
You probably use pin or pattern for screen unlocking, you will need to enter the same when you boot to OF/TWRP that it can read Internal memory (later, when you Format Data it will be gone and you will have to setup your pin/pattern again once you boot to your new System)
First time you boot to the new System give it some time (might be slow at first, doing things in the background)
Xiaomi.eu 'hides' that Bootloader is unlocked, hence you will pass SafetyNet (i e., Device will be certified in Playstore) right away
You will also have DRM L1 (you may need to download the certificate, but that's easy)
When you later need to reboot to OF/TWRP, you don't need to struggle with key combos - in Xiaomi.eu, from System updater, when you open the top-right menu, you have Reboot to recovery option (root not needed)
Later you can think about rooting with Magisk, installing nodules, additionally debloating, etc
Be aware that raphael is on the end-of-line and it's not clear would it receive any more Xiaomi.eu updates (or if, then just a newer Security Patch).
But that's also the case with stock
Click to expand...
Click to collapse
Okay i'll follow your given directions, I'll update you after installation, Thank you

I'm now on latest weekly build on eu rom, and it's butter smooth and i know this might be the last beta version for the raphael but experience is just flawless and new features work perfectly fine, again thanks for your instructions i'll remember them for future installations.

jacksterky said:
I'm now on latest weekly build on eu rom, and it's butter smooth and i know this might be the last beta version for the raphael but experience is just flawless and new features work perfectly fine, again thanks for your instructions i'll remember them for future installations.
Click to expand...
Click to collapse
Doesn't matter if it's last Weekly as long as you are satisfied with.
Btw, I thought you'd be little more conservative and go for Stable, but probably differences are minor
Stable is MIUI 12.6 (also A11) with Security patch Oct 1 - what are your parameters?
Also, check Widewine L1 certificate and update if neccessary:
Settings / Passwords and security / Fingerprint unlock / Fingerprint payments
Check do you have Widevine L1 cert.
If necessary, take Certificate update
Btw, you are ready now for Magisk, AdAway, Vanced YT, Viper4Android, CustoMIUIzer and so