Don't flash this rom. It is beta. Lineage os team is still working on it

Who wants Hyper OS 3 A15 port for fleur?

𝗛𝗮𝗽𝗽𝘆 𝗡𝗲𝘄 𝗬𝗲𝗮𝗿 🎊🎈🍾

-𝗔𝗫𝗧𝗥𝗠

#lineage #fleur #microg
LineageOS 23.0 - microG - UNOFFICIAL | Android 16
By @zett109
Released: 01/06/26

▪️Download | Rom & Boot
▪️Flashing Guide
▪️Repos & Changelog

Credits:
• @claxten10 for Full Device Repos & Kernel
• Yakoob721 for Vendor files

Known issues:
• Device integrity
• NFC has not been tested.
• Transition animation scale needs to be disabled in Developer options to prevent lagginess.

Notes:
• comes with microG

LineageOS 23.0 - microG - UNOFFICIAL | Android 16
By @zett109

It's based on the old tree and has settings transition lag, if you want to flash it, you can.

India's new SIM binding rule requires messaging apps (like WhatsApp, Telegram) to link user accounts to a specific, active SIM card for enhanced cybersecurity, stopping app use if the SIM is removed or swapped, and mandates periodic logout (every 6 hours) for web versions to prevent fraud, closing loopholes used by cybercriminals. The Department of

Telecommunications (DoT) issued these rules under the Telecommunication Cybersecurity Amendment Rules, 2025, giving apps a deadline (around 90-120 days from late 2025) to comply, impacting users of OTT communication services.

Indian government and Department of telecommunication both are piece of shit, their cyber security department is not good so they are now causing inconvenience to the users.
The government is so gay they don't do public consultations before doing something like this,
And ofc their whole system works on bribery.

LineageOS 23.1 UNOFFICIAL | Android 16 QPR1
By @zyuzyechka
build date: 15.01.26
device: fleur/miel
type: vanilla (no gapps)

download:
boot | ROM

changelog:

- fixed lags in settings
- fixed hotspot
- fixed wpa3
- no blur (disabled for better battery life and performance)
- fixed sensors
- signed build

credits:

- thx noki, nisel, vertek and aryx for device sources
- thx nisel for server
- thx nisel for helping to build this rom (i'm skill issue so much)
- thx anh and tebang for testing this rom

I need tester for HYPER3.1 A15

Pm @ikrax

The Two Paths of Unlocking:
1. The "Clean" Path (Unofficial/MTKClient)
How: Unlocking via mtkclient or BROM exploits on 4.14 firmware.
The Result: This method only flips the software bit in the seccfg partition. It DOES NOT write a permanent token to the RPMB (Hardware Security Block).
The Benefit: Because the RPMB remains "neutral" (blank), you can update to 4.19 or 6.6 kernels and stay Unlocked with Status 1. The hardware doesn't have a "strict" token to check against, so it accepts the legacy unlock.
2. The "Permanent" Path (Official Mi Unlock Tool)
How: Using the official Xiaomi Unlock Tool on 4.19 (HyperOS) or newer.
The Result: The official tool performs a cryptographic handshake with Xiaomi's servers and writes a Permanent, Signed Security Token directly into the RPMB.
The Catch: Once this token is written, it is IRREVERSIBLE. You cannot "blank" or revert the RPMB again.

The Consequence: The 6.6

If you have used the Official Unlock Tool, your device now carries a specific hardware signature.
The 6.6 Conflict: When you try to boot the 6.6 LK (Sea), it performs a strict check against the RPMB.
The Lock: Because the hardware token mismatches the custom/ported environment, the 6.6 LK will automatically relock your bootloader. Unlike 4.19 which might show "Status 2," the 6.6 firmware is programmed to force a hard lock to "Status 0" if the RPMB token doesn't pass its new validation rules