Database Develop

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.

Lenovo Z5s (no PRO) TWRP 3.3.1 + Pixel GSI + MIUI + FlyMe + H2OS

Hello guys,
I don't see a dedicated section for lenovo Z5s but I managed to download the TWRP 3.3.1 from baidu (only chinese and english but chinese default).
I then looked for rom authors, it seems they all are using chinese custom roms, anyway they are mirrored and MIUI has been tested by me.
I decided to mirror all downloads I found (they were quite hard to get):
TWRP :
TWRP-3.3.1-LENOVO_Z5S-CN-wzsx150-fastboot.7z (with fastboot instructions and files)
TWRP-3.3.1-0529-LENOVO_Z5S-CN-wzsx150.zip (can be flashed with TWRP)
recovery-TWRP-3.3.1-0529-LENOVO_Z5S-CN-wzsx150.img (only .img file)
Chinese Roms :
Z5s_miui_19.5.20(9.5.16)_Pie_Public_by Art_Chen(TWRP_FASBOOT_2in1).zip
Z5S_H2OS_190722
Z5s_Flyme7.3.1.0A_YouLinw_V1.5_19.07.25
GSI Roms : (Seems to be AB, because A-Only are not working)
According to 4PDA, only Pixel Experience have been tested for now, they provide screenshot and video.
Pixel Experience GSI Tested working!
Ressurection Remix Tested working!
Arrow OS Tested Working!
All other public GSI images (tested many, none of them working, no idea why)
Official ROM backup (QPST format):
https://mirrors.lolinet.com/firmware/lenovo/l78071/
I added permissiver v4 I got from Telegram on Android Q GSI channel
Instructions for GSI Images (thanks to 4PDA):
Using TWRP recovery:
0. Download the firmware files to your smartphone.
1. Enter the recovery menu. To do this, turn off the smartphone and simultaneously hold down the power button and volume +.
2. In the recovery menu, select the item Cleaning -> Selective cleaning. Check the boxes on Dalvik / ART Cache , System , Data and Cache . Swipe the slider to the right. Return to the main recovery menu.
3. In the main recovery menu, select Installation -> Install Img. Select firmware file XX.img. For system section firmware, select System Image, and for boot - Boot. Swipe the slider to the right. Go to the main recovery menu. Select Reboot -> System.
This procedure is new for all smartphones, so don't be afraid to ask questions if something went wrong.
Click to expand...
Click to collapse
Using adb:
0. Install the USB, ADB and Qualcomm drivers on the PC. Reboot the computer and connect the smartphone to the PC. Download files for firmware on PC.
1. In the folder where the files (.img) were saved, press SHIFT and the right mouse button from scratch. In the context menu, select PowerShell or CMD (activate command console).
2. Enter the commands one by one
fastboot flash system XX.img
fastboot erase userdata
fastboot -w
fastboot reboot
PS In some cases, it will be necessary to flash vendor and / or boot:
fastboot flash vendor XX.img
fastboot flash boot XX.img
Click to expand...
Click to collapse
Source for TWRP: https://club.lenovo.com.cn/thread-5442053-1-1.html
Source/author for H2OS & Flyme : Weibo
Source/author for MIUI : Weibo
4PDA page : https://4pda.ru/forum/index.php?showtopic=960895
Please move topic to another section if wrong.

First, thanks for the Thread. Very informative.
let me report that H2OS showes black screen after boot logo,
Flyme seems working but with some minor problems (bad english translation, no google apps on built-in chinese app store, upper notification bar not aligned, etc).

TASON42 said:
First, thanks for the Thread. Very informative.
let me report that H2OS showes black screen after boot logo,
Flyme seems working but with some minor problems (bad english translation, no google apps on built-in chinese app store, upper notification bar not aligned, etc).
Click to expand...
Click to collapse
Hi, thanks. H2OS is the only one i have not tested, i will remove the link. If you live outside Cina I would recommend GSI rom since chinese roms might have issues with notifications.
I now recommend AEX (arm64 AB)

vickdu31 said:
Hi, thanks. H2OS is the only one i have not tested, i will remove the link. If you live outside Cina I would recommend GSI rom since chinese roms might have issues with notifications.
I now recommend AEX (arm64 AB)
Click to expand...
Click to collapse
Don't you lost WIFI after flashing just GSI img file? I need to flash MIUI before flashing any GSI to keep WIFI working.
and this maybe is a lil bit off topic but have you ever had problems with fastboot?
my fastboot is not working properly since I bought this smartphone, 'fastboot devices' works but
can't flash anything, saying random error like 'maxium download size not reported', 'too many links', and even 'error: no error'...
tried changing usb port, cable, driver, everything I can think of.
I can still flash boot.img, recovery.img, vbmeta.img via QFIL but I want to use fastboot which is less hassle..

Report:
MSM Xtended is working too.
problems I hav till now.
1. WIFI not working if you flash directly from ZUI, or wipe cache/dalvic.
2. loud speaker sound problems at various ROMs, with or without equalizer app.
3. notch size is not matching with status bar at every ROMs
4. double tap to wake is not working for every ROMs.

I actually did flash miui first.
I contacted art_chen to get international MIUI, he told me he dont have phone anymore but we can download his miui zip and replace system.img with the one official from MI9 (taking the system.img full global fastboot firmware and it should work).
The vendor image and boot.img included in the miui rom have been customised by art_chen so he probably fixed wifi !
Since i also dont have the phone i cannot test so well.

vickdu31 said:
I actually did flash miui first.
I contacted art_chen to get international MIUI, he told me he dont have phone anymore but we can download his miui zip and replace system.img with the one official from MI9 (taking the system.img full global fastboot firmware and it should work).
The vendor image and boot.img included in the miui rom have been customised by art_chen so he probably fixed wifi !
Since i also dont have the phone i cannot test so well.
Click to expand...
Click to collapse
1. did you had loud speaker problem after flashing treble GSI files? Mine distorts heavily with every .img file i tried.
2. I'm testing swapping .img file with other xiaomi devices but none of them is working. Sounds like you don't own the device anymore so this will be lonely fight.
---------- Post added at 03:41 AM ---------- Previous post was at 03:36 AM ----------
I need FM radio which is not included in Art_chen's ROM so I tried swapping system.img with Redmi note 7 (closest spec), and failed.
TWRP log is saying "Failed to mount '/system_root'" so i guess the reason is partition chart problem or pre-installed magisk, I'm not sure I can fix this but I'll keep trying.
since FM radio is not even on the hardware list so i decided to give up FM radio, but updating android security patch with
Mi 9 (since OP mentioned), Mi 9 SE (quite close spec) and Mi CC9 (not international but even closer than redmi note 7) firmware files,
I don't think any of them would work, but I'll keep trying(2).

You could also try with Flyme blobs (boot, vendor etc) they are from different dev
If you messed up partition i recomment flash wjole miui or flyme with adb

Looking for Global Rom
I purchased the Chinese version of this model.
I tried various GSIROMs, but there were a lot of things that didn't work.
I want to use ZUIOS obediently. Does anyone have a Global Rom?
Also, you should be careful about overwriting GSIROM.
The lighting adjustment has gone wrong.
(No problem with genuine ROM)

teketake said:
I purchased the Chinese version of this model.
I tried various GSIROMs, but there were a lot of things that didn't work.
I want to use ZUIOS obediently. Does anyone have a Global Rom?
Also, you should be careful about overwriting GSIROM.
The lighting adjustment has gone wrong.
(No problem with genuine ROM)
Click to expand...
Click to collapse
there is no Official Global Firmware since this phone is only for china mainland. You can enable google service/calendar/GPS by downloading play store .apk from lenovo app store.
there is faulty firmware chimera with chinese rom + google service preinstalled, but trust me, it is unusable. It has every unfamiliar chinese-specific settings + bunch of 'google service force closed' alarms, bad battery drain by google service, crashing app downloading, etc.

Yes, I'm still using this mediocre device, found some useful articles about GSI, will throw links here.
https://www.dospy.wang/forum.php?mod=viewthread&tid=1626&extra=page=1
https://www.htcmania.com/showthread.php?t=1504540
it's not in English but google translate will help you guys.
here's the essence.
Flash MIUI first, its mandatory. Without it you will lost WiFi.
But, you will lost DT2W and FM radio at kernel level if you flash MIUI.
Now you can flash any GSI, but I recommend Pixel Experience from the link I uploaded,
because fixes of common GSI issues like statusbar height (use magisk+rirucore+riruedxposed+gravitybox), sound distortion (use magisk+audio compability), headphone not detecting (random) are integrated to the GSI.

Global ROM was uploaded to 4PDA.

K10 note is almost identical with Z5s and now it's Global released, you can get the QFIL files, I guess just swap system.img and userdata.img might work.
the difference between Z5s chinese ROM and K10 note global ROM must be something like that of Z6 pro chinese and global version...
edit: yes it is working, just swap system_xx.img and userdata_xx.img files will do the work, only camera.apk won't work properly (no optical zoom just digital, ramdom crash sometimes ) but we can stick with Gcam port.

I flash pixel experience then i find out auto brightness isn't work well.i adjust it to the lowest , but it still so bright.how can i fix it?

H2OS 9 : https://mp.weixin.qq.com/s/45L1TZFa0g1MP3-jSYhMDg
Flyme 8 : https://mp.weixin.qq.com/s/P8tL8eq9UhV8Hbq8-7nYBQ
MIUI 11 : https://mp.weixin.qq.com/s/q-8qnFI1VP8upyz6quZZmw
it's all from YouLinw, the dev of Flyme 7 port in OP.
Flyme 8 is still in daily alpha, it boots but stuck in Terms&Conditions screen.
MIUI 11 and H2OS works great, (but don't use pre-installed Magisk, install official v19.3 from via TWRP. idk why but pre-installed one or lastest v20.1 won't work.)
Android Security Patch in MIUI11 is Sep 1st while H2OS is Aug 1st (same with PE I linked before)
so it's your choice to use MIUIsh MIUI with newer ASP, or H2/PE which is more stock android, but with older ASP.
Quack phh Android 10 is not working sadly,
neither vendor by Art_Chen (MIUI10) nor YouLinw booted,
with original vendor it boots but Wi-Fi won't work, like always.
---------- Post added at 04:29 AM ---------- Previous post was at 04:21 AM ----------
s94084sammy said:
I flash pixel experience then i find out auto brightness isn't work well.i adjust it to the lowest , but it still so bright.how can i fix it?
Click to expand...
Click to collapse
I have the same problem, I just bear it since it's not major one. you can use any third party apps from play store that dims your screen if you want to.

Hello, i think about buying this phone or xiaomi note 7 pro . Want to flash lineage or aosp base rom, someone has a point of view about best hardware and best dev support ? For me note 7 pro have better dev support but one week for unlock bootloader and lcd cheaper for repair . Can't find photo versus, z5s have three module but rn7p have 48mp , someone have an advice ?

bretzelpopo said:
Hello, i think about buying this phone or xiaomi note 7 pro . Want to flash lineage or aosp base rom, someone has a point of view about best hardware and best dev support ? For me note 7 pro have better dev support but one week for unlock bootloader and lcd cheaper for repair . Can't find photo versus, z5s have three module but rn7p have 48mp , someone have an advice ?
Click to expand...
Click to collapse
I think Redmi Note 7 pro is the buy.
I chose Z5s because of its cheaper price, lighter weight, and more premium material (alu+glass).
And I also had nice Dev experience with ZUK Z2 so I expected the same with this phone (which was wrong guess )
Cam, I assume stock camera is better in Z5s, but You won't use stock ZUI/MIUI ROM anyway so that won't bother you.
GCam works great on both model, ported stock camera apk won't work as good as it's on stock ROM, both in Z5s/Note 7.
Sound, both mediocre.
Screen, both mediocre (HDR on Z5s is fake color boost only for chinese content apps),
and Z5s has unusual copper plate type connection not like normal ribon cable.
Dev, Z5s is for China mainland only so you won't get proper global/AOSP ROM developments,
but you can get bunch of MIUI/Flyme/H2OS ROMs...
Official Update is also better in MIUI over ZUI.

Hi there. Was there any AOSP or LineageOS working on our Z5S?

Hi @vickdu31 do you have a copy of recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img ? I tried as a guest in 4pda but I get a 404 error. Thanks for your help!

carlshark said:
do you have a copy of recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1-JwD0Ie5xY2CQRDv8rvZMK6ICf0vmp4n/view?usp=drivesdk

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

Back to Stock

Hi,
I bought this Mi 9T Pro, a year and 5 months ago. It already came rooted and with Miui 20.5.7 Beta.
However i run in to the problems that i am starting to use this phone for work now and it can't be used due some checks that this phone is rooted and on an old updated version.
Is there a way to get back to the stock eu rom. With automatic updates and to unroot it, without losing all my programs/photos etc.?

themack said:
Hi,
I bought this Mi 9T Pro, a year and 5 months ago. It already came rooted and with Miui 20.5.7 Beta.
However i run in to the problems that i am starting to use this phone for work now and it can't be used due some checks that this phone is rooted and on an old updated version.
Is there a way to get back to the stock eu rom. With automatic updates and to unroot it, without losing all my programs/photos etc.?
Click to expand...
Click to collapse
By 'rooted', do you mean that Magisk is installed (that you really have SuperUser privileges in Android) or only that Bootloader is unlocked (and maybe TWRP/custom Recovery is installed)?
Also, by Miui 20.5.7 Beta do you mean an old Xiaomi.eu Weekly or some other custom ROM or what?
You can flash Magisk uninstall.zip from TWRP to unroot=uninstall Magisk (that will not relock BL, but properly speaking rooting should be related to su and hence Magisk).
In Magisk app (former Magisk manager) there is also Uninstall Magisk option but I would suggest to flash the uninstall.zip instead.
It would be also good that you go to the Modules in Magisk app/mngr and uninstall all modules (and reboot) first
If you are on Xiaomi.eu Weekly, you should be able to upgrade to the latest Weekly or even better to the Xuaomi.eu Stable without Formatting Data (hence keeping your apps, settings and documents).
Better than latest stock and (without Magisk - to avoid troubles with hiding the Magisk) you will be passing SafetyNet right away (Xiaomi.eu hides that Bootloader is unlocked) and you should not have any problem for your business apps.
For updating Xiaomi.eu you will need TWRP - you probably have an older version, you will need to update the TWRP first (or Orange Fox or your customRecovery of choice)
But if you really want to go back to stock you MUST do FORMAT DATA (if you don't you might be able to install the stock but you will complain then that this or that does not work, etc), hence you will loose all your user apps, settings, data - you need to think about backing up and later restoring (cooying e.g. photos to PC, backing up contacts via Google account, and Xiaomi Clouds also provide useful back-ups for apps and their settings, Comtacts, Calls and SMS, even WiFi passwords)

zgfg said:
By 'rooted', do you mean that Magisk is installed (that you really have SuperUser privileges in Android) or only that Bootloader is unlocked (and maybe TWRP/custom Recovery is installed)?
Also, by Miui 20.5.7 Beta do you mean an old Xiaomi.eu Weekly or some other custom ROM or what?
You can flash Magisk uninstall.zip from TWRP to unroot=uninstall Magisk (that will not relock BL, but properly speaking rooting should be related to su and hence Magisk).
In Magisk app (former Magisk manager) there is also Uninstall Magisk option but I would suggest to flash the uninstall.zip instead.
It would be also good that you go to the Modules in Magisk app/mngr and uninstall all modules (and reboot) first
If you are on Xiaomi.eu Weekly, you should be able to upgrade to the latest Weekly or even better to the Xuaomi.eu Stable without Formatting Data (hence keeping your apps, settings and documents).
Better than latest stock and (without Magisk - to avoid troubles with hiding the Magisk) you will be passing SafetyNet right away (Xiaomi.eu hides that Bootloader is unlocked) and you should not have any problem for your business apps.
For updating Xiaomi.eu you will need TWRP - you probably have an older version, you will need to update the TWRP first (or Orange Fox or your customRecovery of choice)
But if you really want to go back to stock you MUST do FORMAT DATA (if you don't you might be able to install the stock but you will complain then that this or that does not work, etc), hence you will loose all your user apps, settings, data - you need to think about backing up and later restoring (cooying e.g. photos to PC, backing up contacts via Google account, and Xiaomi Clouds also provide useful back-ups for apps and their settings, Comtacts, Calls and SMS, even WiFi passwords)
Click to expand...
Click to collapse
By 'rooted', do you mean that Magisk is installed (that you really have SuperUser privileges in Android) or only that Bootloader is unlocked (and maybe TWRP/custom Recovery is installed)? =
Yes, Mgisk and SU are installed and with OrangeFox.
If you are on Xiaomi.eu Weekly, you should be able to upgrade to the latest Weekly or even better to the Xuaomi.eu Stable without Formatting Data (hence keeping your apps, settings and documents).
Better than latest stock and (without Magisk - to avoid troubles with hiding the Magisk) you will be passing SafetyNet right away (Xiaomi.eu hides that Bootloader is unlocked) and you should not have any problem for your business apps.
For updating Xiaomi.eu you will need TWRP - you probably have an older version, you will need to update the TWRP first (or Orange Fox or your customRecovery of choice) =
Are the weekly builds also availble on OTA updates? So i won't have to update manually every time? Because saving the files and apps that i have right now are key. Otherwise i can just buy a new phone and transfer everything. Is there a good tutorial on how to update it to the latest weekly?

themack said:
Yes, Mgisk and SU are installed and with OrangeFox.
Are the weekly builds also availble on OTA updates? So i won't have to update manually every time? Because saving the files and apps that i have right now are key. Otherwise i can just buy a new phone and transfer everything. Is there a good tutorial on how to update it to the latest weekly?
Click to expand...
Click to collapse
Ok, from Magisk app/mngr uninstall all modules and reboot. Later when you update Xiaomi.eu, it will flash the new, clean boot.img without the Magisk patch.
Finally, you will uninstall the Magisk app/mngr then (app/mngr is apk, not the Magisk itself, only it's front-end/UI to manage the Magisk)
For Orange Fox you will need to search where to download the update.
You can also take latest TWRP from TWRP.me and flash the img file (to Recovery) from OF
If you are really on Xiaomi.eu (check My Device does it really say MIUI by Xiaomi.eu or so), go to Xiaomi.eu forum, open the Stable (or Weekly) thread and read the OP posts (usually, posts #1 and #2) where to download and how to install/update
When updating from the old Xiaomi.eu Weekly/Stable to the latest Stable, the following should be enough:
- download the ROM zip for raphael
- go to OF/TWRP and flash the ROM
- Wipe Dalwik and Cache
- Go to Advance (maybe in OF named differently, I don't use OF), File Manager, navigate to /data/system and delete its package_cache subfolder
(Btw, I downgraded that way from Xiaomi.eu weekly to always the little older Stable and everything went ok - I only had an issue with Gallery app that was newer in my Weekly than in the Stable - but that is also solvable and could not apply to your ancient Weekly)
I.e., the guide might say that you need to Format Data, but since you are upgrading from an really old Weekly/Stable version there is no fear that you might downgrade any system app
PS: Xiaomi.eu provides its own OTA mechanism but for updating you will always need TWRP (OF), not the stock Recovery.
However, Mi 9 series (plain, T, T Pro, SE, all of them) are on the end-of-line. There will be no Xiaomi.eu Weeklies any more for them, and it's unclear would they receive additional Stable updates (just like the newer Security patches).
But the similar fate applies to stock OTA upgrades, too. Phones were released with MIUI 10/A 9, more than two years ago, Xiaomi upgraded them to MIUI 12 / A11 (two major versions ahead) - and that's it

See also the post #6 in that thread and subsequent posts about successful and happy move to the latest Xiaomi.eu Stable:
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
Also the post #6 here and the story around (Widevine L1 with Xiaomi.eu):
arecflo said:
Changed the rom to Xiaomi.eu and I got it! Thanks.
Click to expand...
Click to collapse

Thanks!
However the latest stable for rapheal says its for china. SHouldnt that be global? Or am i looking wrong?

themack said:
Thanks!
However the latest stable for rapheal says its for china. SHouldnt that be global? Or am i looking wrong?
Click to expand...
Click to collapse
Are you talking about Xiaomi.eu Stable from here or stock CN:
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
Xiaomi.eu IS NOT FOR CHINA - read the Forum about.
However, it's up to you do you want to try or not. Be aware that it is not the Xiaomi official/stock ROM.
If you have furtther questions, google on the Net about user opinions, consult their Forum or (create account) and ask there