yashsingh1/xdaforums huggingface dataset:
[LG G7 ThinQ  ROMs, Kernels, Recoveries, & Other De] EmanuelCN:
it works very well and its on high brightness bc thats how it is on any device on custom roms besides amoled screens that closes pixels
[LG G7 ThinQ  ROMs, Kernels, Recoveries, & Other De] lynchknot:
I bought this phone as well. It was too late to return it but I complained anyway. They gave me a $20 refund.

So all I can do is install lineage os 17 since there will be no OTA? Installing that OS or any OS looks very complicated. There is no way to upgrade from Oreo without wiping all the data?
[LG G7 ThinQ  ROMs, Kernels, Recoveries, & Other De] ThatLatinGuy:
Sadly not , but the crossflash process is not that difficult if you follow the guide .

I have sucessfully updated 2 G7's one pm(sprint) and a vm(verizon) both working pretty great on android 10. Can't speak about volte or wifi calling since I've bever used those services so if you are interested in that I can't give you any input

On the other hand you could try lineage os or any ither or the custom roms and some of them do support updates from within the same rom , no facotry reset needed unless upgrading from lets say 10 to 11
[LG G7 ThinQ  ROMs, Kernels, Recoveries, & Other De] zim2dive:
I have a PM I am trying to sell .. it was cross-flashed before I bought it.. I used as a wi-fi only phone very happily (that was my goal).. but am trying to get it saleable.... I cannot find an official Sprint ROM to flash? ie. I want to flash it back and sell it as original (ie. usable for Sprint) rather than sell as a frankenstein. Any pointers?
[LG G7 ThinQ  ROMs, Kernels, Recoveries, & Other De] kukuteku:
There is not Sprint stock Rom avaliable. Cross flash is a not-return journey. Anyway, there is nothing worng with crosflashed Roms, just a couple apps you cant download from Gplay Store, but you can grab apk from another store. On android 10 you can install some from Gplay like Netflix.
[LG G7 ThinQ  ROMs, Kernels, Recoveries, & Other De] EmanuelCN:
there is quite a lot if you join the TELEGRAM Group ... the phone is great
[LG G7 ThinQ  ROMs, Kernels, Recoveries, & Other De] KGO87:
Which is what leads me to believe that most of the ‘ULM-PM’ model isn’t actually anything crossflashed but an actual ULM model ,that has imei that were simply issued to sprint assigned by lg firmware distribution division wtfever...

And that sprint G7’s simply were ulm models is all..

There may be crossflashed variant phones also BUT when u buy a bnib SEALED lg g7 and box says ulm but the sticker isn’t the ‘standard ulm’ and u look up imei and it says sprint..

well.... um yeah logic common sense wouuuuld dictate..

Thee Above^

**now if it were after the tmobile buyout then ofc the firmware would be MIGHT been ‘TM’

Any questions...

It’s already been said that most all g7 have ALL the bands but you have to enter a service menu to enable the ones the modem leaves open avail

Any other questions. .
[Xiaomi Mi A1 Questions & Answers] jimmyhurr:
Is it possible I don't actually have a Mi A1? Reading around forums, the Mi A1 should have the A/B split partition, but according to the output of "fastboot getvar all", it only has one partition, which is I guess why the ROM flash is failing. The phone was reporting that it was an Mi A1 (when I could get into it) but is it possible that it's some other device that's been flashed (somehow) with the wrong ROM?

I tried a much more recent Mi A1 stock flash just now using Mi Flash and this gave a different, but similar error:

[18:01:29 994d6a4f0604]:MiFlash 2018.5.28.0
[18:01:29 994d6a4f0604]:Thread id:11 Thread name:994d6a4f0604
[18:01:30 994d6a4f0604]:image path:C:\tissot_images_V10.0.9.0.PDHMIXM_9.0
[18:01:30 994d6a4f0604]:env android path:"C:\Users\j_a_h\Downloads\MiFlash2018-5-28-0\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android"
[18:01:30 994d6a4f0604]:script :C:\tissot_images_V10.0.9.0.PDHMIXM_9.0\flash_all.bat
[18:01:30 994d6a4f0604]:Physical Memory Usage:2166784 Byte
[18:01:30 994d6a4f0604]:start process id 1852 name cmd
[18:01:30 994d6a4f0604]:info:$fastboot -s 994d6a4f0604 getvar product 2>&1 | findstr /r /c:"^product: *tissot" ||
[18:01:30 994d6a4f0604]:info:product: tissot
[18:01:30 994d6a4f0604]:info:$fastboot -s 994d6a4f0604 erase boot_a ||
[18:01:30 994d6a4f0604]:err:Warning: Device A/B support is outdated. Bootloader update required.
[18:01:30 994d6a4f0604]:info:"error : Erasing boot failed, maybe the device is locked"
[18:01:30 994d6a4f0604]:err:erasing 'boot_a'...
[18:01:30 994d6a4f0604]:err:FAILED (remote: Partition table doesn't exist
[18:01:30 994d6a4f0604]:err:)
[18:01:30 994d6a4f0604]:err:finished. total time: 0.020s
[18:01:30 994d6a4f0604]:error:"error : Erasing boot failed, maybe the device is locked"
[18:01:30 994d6a4f0604]:process exit.
[18:01:30 994d6a4f0604]:flashSuccess False
[18:01:30 994d6a4f0604]:isFactory False CheckCPUID False
[18:01:30 994d6a4f0604]:before:flashSuccess is False set IsUpdate:True set IsDone True
[18:01:30 994d6a4f0604]:after:flashSuccess is False set IsUpdate:false set IsDone true

I input the S/N from "fastboot getvar all" into the mi . com checker, but this just returns a "doesn't exist" ???

Any other way to verify what device I actually have?
[Xiaomi Mi A1 Questions & Answers] malise:
Maybe it's a Mi 5X (miui twin of A1) with the Mi A1 ROM ported

It's normal, mi.com doesn't work with that serial number but with the one on the box, IMEI should work.
[Xiaomi Mi A1 Questions & Answers] jimmyhurr:
Just to close this off: I've come to the conclusion that this phone is an Mi 5X with a fake Tissot bootloader running a custom/ported Mi A1 Android One firmware. The case is marked with MDT2 which Google suggests is a Mi 5X. I've discovered it was bought on eBay and came to the UK from Hong Kong I believe. So looks like it is one of the dodgy ones. I'm cutting my losses and moving on with something else.
[Xiaomi Mi A1 Questions & Answers] malise:
If the phone case is original a MI A1 must be labeled with AndroidOne logo on the rear bottom of the case, the 5X instead only have MI logo on the back.

So if it lacks the AndroidOne logo on the case it is definitely a MI 5X.
[Xiaomi Mi A1 Questions & Answers] jimmyhurr:
Correct, it does not have an AndroidOne logo on it, only MI logo.
[Xiaomi Mi A1 Questions & Answers] ranjodhricky:
you can try flashing mi5x stock firmware
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Fanch3n:
I explained this problem on reddit (r/Xiaomi/comments/enxblm/garbled_music_on_mi_9t_pro - can't post links) but no solution was found. I'll copy the description:

I have regular problems with completely garbled music output on my 9T Pro: Instead of playing a song normally, the sound output it very high pitched and completely garbled, so even recognizing the song is impossible. Also, very unpleasant to listen to.

It doesn't happen mid-song, but when a new song starts playing it has a chance to be broken like this. Restarting playback fixes it, but it might just happen again with the next song.

I've tried differend music apps (Phonograph and Play Music), so the app is probably not the cause of the problem.

It's also not limited to a specific output, I've had it happen with the built-in speakers and when using a Bluetooth device.

I've first noticed the problem shortly after the update to Android 10, so it's been going on a while.

As suggested on reddit, I've tried VLC Player which doesn't seem affected by this problem, but I don't want to use it permanently.

Another observation: Rebooting makes this go away for a while, but with time it'll happen more and more often until it occurs on almost every song change again.

Any ideas?
[Xiaomi Redmi 4 Prime Questions & Answers] thumos2:
Hi,

I cannot unlock my 4-Prime... it seems that the Xiaomi unlocking page does not work anymore.

When I choose "Unlock" on this page http://en.miui.com/unlock/ I am redirected to a Xiaomi forum in Chinese, http://www.miui.com/forum.php?mod=nick2

It is the first time I am doing this. The phone has been used for only two months.

Could anyone help?

P. S. I forgot to mention I am using Linux. But I could find access to Windows if necessary.
[Touch Diamond, MDA Compact IV General] lmr2003:
Hi all,

I was just wondering if someone could give me the value that you have on :

HKLM\System\Versions on Aku

I have changed this and now I want to have the original one
[Touch Diamond, MDA Compact IV General] pedmond:
Mine is "Aku"=".1.1.4"
[Touch Diamond, MDA Compact IV General] lmr2003:
thank you :D
[Touch Diamond, MDA Compact IV General] Blackfire:
for me it is .1.1.6
[Touch Diamond, MDA Compact IV General] Oppainter:
Same like blackfire!
[Touch Diamond, MDA Compact IV General] pedmond:
Humm - I'm outdated :D
[LG G8X ThinQ Questions & Answers] Jainyankee1993:
Anyone figure out how we can change the second screen to have a live wallpaper as well? I want to use KLWP on the second screen and as of right now I don't believe there is a way.
[LG G8X ThinQ Questions & Answers] AxelR11:
I don't think there is a way too. That's a thing the dual screen miss in my opinion..
[LG G8X ThinQ Guides, News, & Discussion] swapnil7927:
recently Microsoft released its much awaited Microsoft surface duo emulator for developers and i think many of you might already be on it & opens the possibility to port Microsoft surface ROM to our lg g8x dual.
[LG G8X ThinQ Guides, News, & Discussion] AxelR11:
It would be pretty nice, but somehow tricky to do no?
[LG G8X ThinQ Guides, News, & Discussion] harysviewty:
Yes. I just learn the developer kit and there's no different vs LG dual screen sdk. Other than hinge masking.

Surface duo, zte Axon m use similar method like LG DualScreen. Asus twindockview is different tho
[Samsung Galaxy Note 9 Questions & Answers] 860lacov:
Recently I did full system wipe.

Since than I don't have notifications from play store.

Normally after app installation there was info on top bar that app has been installed.

In my play store notification settings I have it enabled.

Stock android 10
[Samsung Galaxy Note 9 Questions & Answers] amirfrkhi:
google disable installation notification on all devices
[Samsung Galaxy Note 9 Questions & Answers] 860lacov:
And can it be enabled somehow?
[OnePlus 6 Questions & Answers] Frizzel:
I went on holiday recently and took a lot of photos using the GCam port. All photos taken on portrait mode have gone missing from both gallery and Google photos when I uninstalled GCam and installed the new version for Android 10.

Is there any way to recover those missing photos?
[OnePlus 6 Questions & Answers] Azhar_Fahry:
sadly, I think no. I've been in ur situation before. no chance. tried everything i could do. have u tried like a files recover app from google play store ? maybe it could work, take a chance.

Btw, can u give me the link the new GCam that u installed ? Thx
[OnePlus 6 Questions & Answers] Mord0rr:
Next time, backup DCIM folder to PC....is the best way all proof.
[Android Stick & Console AMLogic based Computers] flixo85:
Hello! I have a t95z max and wanting to update the firm it has done nothing and only you turn on the light, I have it disassembled and I have seen that some pins must be connected. Do you know what they are? And then what steps to follow. Thanks!
[Touch Diamond, MDA Compact IV General] LRC:
any news about the ext_ROM,

i want to open it, 4manually install cabs. after H.reset
[Touch Diamond, MDA Compact IV General] rorydaredkign:
there is no ext-rom

use sd config, or remove the cabs you dont want from the rom, or soft reset when customisation starts
[Touch Diamond, MDA Compact IV General] LRC:
"or remove the cabs you dont want from the rom"

how ?? where ??

can you tell me how or a link ??

sorry, for the noob questions
[Android Q&A, Help & Troubleshooting] trmadhes:
Hi

I am a newbie here, and to flashing devices. Going thru forum threads, but too many things to start with: twrp, magicks, jodin3 which is not compatible with Mac :( etc.

Also, I am not able to find AOSP ROM for Samsung Tab A 10.1 [SM-T510] in forum threads.

Need your suggestion on finding the AOSP ROM build, and sequence of steps for flashing the same.

Many thanks.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] photonmedia:
Just found a new bug:

Wireless Hotspot will not start.

Can anyone confirm if this is an issue with other LineageOS build for this device?
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] photonmedia:
Messed around too much and had to re-flash. Afterwards, I could not get apps to register with MicroG Cloud Messaging, so some notifications were not working.

If anyone runs into this issue, just get a root shell and run this command:

adb shell
su
am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://2432546 --receiver-include-background

This will register the current user with Cloud Messaging. You can verify this works with the "Push Notification Tester" app in the Aurora Store.

This knowledge comes to you courtesy of lxp over on the MicroG Github
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] flipburn:
Using for 3 days now, and is working good, i don't use MicroG and no google apps. Nice work
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] Simonell:
Using it for second day, and everything seems fine, hotspot working too.

Only problem is with Revolut app which say it's incompatible app, are there any workaround?

Btw. Good job, thanks!
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] photonmedia:
I'm not familiar with that App. Is it working on other AOSP-based ROMS?

It looks like Mobile Banking app. I don't have an account to really test; nor do I have the energy to try and troubleshoot individual apps.

Are you by chance running it on a rooted install? If you have rooted this ROM, that could be why you are having trouble with that Banking App. I know they tend to not like rooted phones.

I have been happy with this build since I compiled it on the 25th, but I may update and compile from current source. It I do, I can make it available for you to try.

Of course, if it is broken on other LineageOS builds, or if you are rooted, I would expect it to still complain on this build, too.

If you rooted with Magisk, there is a Magisk Hide option in the Magisk Manager app that may let you hide your root from that specific banking app.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] Simonell:
It's working after root and Hide in Magisk Manager. I was confused because it was showing up as "Incomaptible with device" in google play store, after rooting it's installed. Thanks!

Could you send commands which you used to compile ROM? I have some free space on my home server, maybe I could set up Jenkins with auto building. Is it possible to get auto update working?
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] Simonell:
Thanks! I will try this guide at the weekend, and post results :)
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] photonmedia:
For what it's worth, I just successfully compiled an updated build today, but it fails to boot after flashing. Had to go back and flash my 2020-01-25 build from the OP.

YMMV
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] ahmadharith:
stock mi 9 camera works or not on this rom? because i don't raelly like gcam.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] photonmedia:
I was able to install ANXCamera and their ANXCustLibsQ_160.DisloyalInnocentVelvetworm.zip Libraries and it works fine for me. Sometimes Portrait mode freezes, but I never use that anyway...

https://github.com/XEonAX/ANXCamera
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] photonmedia:
It seems like maybe it is not seeing some or all of the device tree files it needs. You may try manually downloading those device files an putting them in the appropriate folders as I mentioned I did in the steps I posted.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] MWPau:
I built this yesterday using the instructions above... thanks a lot for those photonmedia!

Some of the instructions were wrong, ie a _ instead of a - in a dir name, but easy fixed.

After that, the entire build completed with 0 errors.

I didnt end up with a ZIP file though, just a approx 400MB "build-lineage_cepheus.ninja" file?
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] k1l:
did you first

breakfast cepheus

and then

brunch cepheus

?

the .zip is actually in the

/out/target/product/cepheus/ folder.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] MWPau:
I did *exactly* as was instructed above...

cd ~/android/lineage
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export USE_CCACHE=1
ccache -M 50G
source build/envsetup.sh
brunch lineage_cepheus-userdebug
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] photonmedia:
My understanding is that the breakfast command is not necessary when you are building for unofficial devices and manually populating the necessary device tree files; you skip to the brunch step.

That is per the other guide I referenced in my instructions and how I was able to build this release.

I have not tried to pull and build an updated version as of this time.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] MWPau:
I missed this at the end of your reply :/

Yup, it's in there. Thanks :D

838M -rw-r--r-- 2 root root 838M Feb 25 01:31 lineage-17.1-20200224-UNOFFICIAL-cepheus.zip
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] MWPau:
Same for me. Have been trying to get it sorted the last few days, i dont know whats going on.

Original OP build works ok.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] photonmedia:
Once again, I refreshed the repo/source and got what looked to be a successful build, but upon flashing and wiping data, I get no boot. (just stuck at the "Mi" boot screen with the Unlocked indicator at the bottom.

Looking back at the logs from the build, I see these errors. I'm guessing this has something to do with it failing to boot:

depmod: WARNING: could not open modules.order at /run/media/tokenwizard/4TB_A/android/lineage/out/target/product/cepheus/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0: No such file or directory
depmod: WARNING: could not open modules.builtin at /run/media/tokenwizard/4TB_A/android/lineage/out/target/product/cepheus/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0: No such file or directory
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] MWPau:
BTW, to skip all the manual downloading of Demon000's device repo's, use this for your cepheus.xml local manifest:

<manifest>
<project path="vendor/xiaomi" name="Demon000/vendor_xiaomi" remote="github" revision="lineage-17.1" />
<project path="kernel/xiaomi/sm8150" name="Demon000/kernel_xiaomi_sm8150" remote="github" revision="lineage-17.1" />
<project path="device/xiaomi/cepheus" name="Demon000/device_xiaomi_cepheus" remote="github" revision="lineage-17.1" />
<project path="device/xiaomi/sm8150-common" name="Demon000/device_xiaomi_sm8150-common" remote="github" revision="lineage-17.1" />
</manifest>

"repo sync" will pull those down into the right locations.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] l1x3:
Mh i got the same issue.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] MWPau:
I managed to get a bootlog out of the failed boot.

Can anyone see whats up?

Maybe a graphics driver/module issue?

https://pastebin.com/6btnFb7t
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] l1x3:
Today i built with cepheus.xml:

<manifest>
<project path="vendor/xiaomi" name="Demon000/vendor_xiaomi" remote="github" revision="35e8da67c300d1c8ea6581853d80229730393cbf" />
<project path="kernel/xiaomi/sm8150" name="Demon000/kernel_xiaomi_sm8150" remote="github" revision="lineage-17.1" />
<project path="device/xiaomi/cepheus" name="Demon000/device_xiaomi_cepheus" remote="github" revision="lineage-17.1" />
<project path="device/xiaomi/sm8150-common" name="Demon000/device_xiaomi_sm8150-common" remote="github" revision="bfd47b2826f24ff74b9bc8c2a34ec130cec62f51" />
</manifest>

This build works. Maybe i will try some newer commits. Those are from ~2020-01-13.

---

<manifest>
<project path="vendor/xiaomi" name="Demon000/vendor_xiaomi" remote="github" revision="be7f11878a2174f0f4dbf8651a0fda56f670a423" />
<project path="kernel/xiaomi/sm8150" name="Demon000/kernel_xiaomi_sm8150" remote="github" revision="lineage-17.1" />
<project path="device/xiaomi/cepheus" name="Demon000/device_xiaomi_cepheus" remote="github" revision="lineage-17.1" />
<project path="device/xiaomi/sm8150-common" name="Demon000/device_xiaomi_sm8150-common" remote="github" revision="510b427b163deb1d04fbd32cb5d3f8586ddbb943" />
</manifest>

A build with this later commits don't boot anymore. So the problem should be between them?
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] k1l:
Anyone got a new build to boot? i tried often but it didnt come up past the mi logo. Did wipe and format data. but there seems to be something missing when its not even booting past mi logo.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] k1l:
I talked to [MENTION=5994357]Cozzmy13[/MENTION] and he gave me some repopicks to add. Now i got build that i flashed just over this build from 26th January. Everything works, even the left button now starts the google assistant.

If someone is interessted: https://workupload.com/start/8Qf78EdJx7Q

All thanks go to [MENTION=5994357]Cozzmy13[/MENTION], i just started the buildprocess with his repos. Buy that guy a beer!
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] l1x3:
Cool! Would you share these infos?

Thank you!
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] k1l:
repopick 267249; # DozeSensors: do not use binned brightness sensor for proximity if not supported # this patch was abandoned, should be 272303 now i guess, didnt try this yet.

repopick -t "ten-qc-telephony-fix-new";

the other patches got merged to lineage os alredy in the meantime.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] Cozzmy13:
EDIT: Wrong thread.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] k1l:
my latest build: https://workupload.com/file/GK9DhUrZp7h lineage-17.1-20200416-UNOFFICIAL-cepheus.zip

For Changelogs and Donations see: https://xdaforums.com/Mi-9/development/unofficial-lineageos-17-0-cepheus-t4023133
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] Phonelix:
Changelog wanted

Thank you! I'll test your ROM today and report.

Up to now there is no changelog on the 1st page you referenced. Thus, an update of this page would be nice.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] Phonelix:
Feedback on lineage-17.1-20200416-UNOFFICIAL-cepheus

First of all, thanks a lot to the developer of this Stock LineageOS ROM for the Xiaomi Mi 9. I love this ROM because its a Stock ROM which gives the user all possibilities for personal preferences, e.g. installing F-Droid instead of Google Play.

Here comes my feedback on missing standard features and identified bugs in the aforementioned ROM:

In "LiveDisplay" color profile (incl. color temperature etc.) and automatic outside mode is missing.

In "Display" unintentional wake-up is missing.

In "Display" wake-up with double click is not functional.

The Camara

neither

makes usage of the wide angle

nor

the telephoto lens.

Anything else (I tested) is working as expected.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] photonmedia:
Latest Build 2020-04-29 LineageOS 17.1 CLEAN,STOCK

All,

I was able to get this to build from the current device trees and LineageOS Source.

Here is the latest, pure LineageOS for our device. Using the same (current) Device Trees and Source from the original build.

(QQ2A.200405.005)

Note: No GApps, MicroG, or any extras included. This is pure, clean LineageOS. It's up to you to add what you want.

FPS Working Well

NFC Seems to work, but don;t have a device to test

Hotspot Working

DT2W Still seems broken in this source. Interestingly, DT2S does work.

(Screenshot Attached)

Download

Also OP has been updated with link to this latest build.
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] photonmedia:
k1l,

If you have updated your Thread to include this link, can you please remove it from this thread to avoid confusion?

Thanks!
[Xiaomi Mi 9 ROMs, Kernels, Recoveries, & Other Dev] Linez:
Interesting.

Does it have black amoled?