[ROM][OFFICIAL][R] LineageOS 18.1 for Xiaomi Mi 8 Lite [platina]

[SebaUbuntu]

LineageOS is a free, community built, aftermarket firmware distribution of Android 11.0 (R), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Recommended firmware
V12.0.3.0.QDTMIXM

Note: This ROM uses FBE encryption, any current existing recovery won't be able to decrypt data!

Downloads
Here

Flashing instructions
Here

Sources:
LineageOS

Happy modding!

 

[SebaUbuntu]

Reserved

 

[babalizm]

Glad to welcome you devs

 

[9Lukas5]

Hey @SebaUbuntu,

First of all, thank you for your efforts
I've a few things I'm stuck at, you or someone else hopefully can help me with.

I flashed it with a data partition, encrypted from Android 9. As expected, it refused to boot and going back to the recovery my data partition was garbled.
Formatting it let me boot fine. I then was surprised, to see the storage as encrypted again in settings.
Trying a reboot to recovery I can't manage to get in. All Recoveries I tried, are stuck on the splash screen.

I tried the Pitchblack, OrangeFox, TWRP and SkyHawk recoveries, but it's the same with all of them.
Is there a working recovery that is able to decrypt the data?

Additionally, I setup a lockscreen Pin, but never got asked if I wanted a secure boot. So I'm unable to use a custom pin for the encryption key, which makes it somehow pointless to encrypt in the first place.
How can I solve that?

I want to use the phone without GApps. Instead I plan on using MicroG, which needs signature spoofing.
My old way using Riru Core, Riru EdXposed and the XposedModule FakeGapps to enable signature spoofing doesn't work anymore sadly.
Would it be possible to add a signature spoofing patch to your builds?


TL;DR:
- Is there a Recovery, able to decrypt the data partition encrypted from your rom?
- I can't set my lockscreen pin for a 'secure start', is that a bug or desired behaviour? (And if so, why? )
- Could you enable signature spoofing in your builds please?

Regards,
L

 

[haoquan]

@9Lukas5 Have you tried https://files.sebaubuntu.me/Recovery/LineageOS-Recovery/platina/ ?

I had similar issue with my Mi8 dipper when I upgraded from official Lineage 16 to 17. Twrp wouldn't decript, it turned out the /data mounting dev path was different and twrp couldn't find it. I lived with it for a while until twrp got an update. During that time, I had to use sideload to update Lineage OS.

 

[9Lukas5]

@haoquan thanks for this tip, I'll save this definitely for the next attempt

I've restore my LOS16 setup for now to have a working phone, as my Setup relies on working Signature Spoofing + MicroG^^.
If someone knows a solution for the Signature Spoofing and custom encryption pin, I'd be pleased to try another upgrade.

In the mean time I'll try to compile an updated LOS16 build using the device parts of this rom (hopefully this will work, otherwise I'll have to find Pie compatible device parts first )

L

 

[KernelGM]

Thx sir, for u working.

 

[SebaUbuntu]

Hey @SebaUbuntu,

First of all, thank you for your efforts
I've a few things I'm stuck at, you or someone else hopefully can help me with.

I flashed it with a data partition, encrypted from Android 9. As expected, it refused to boot and going back to the recovery my data partition was garbled.
Formatting it let me boot fine. I then was surprised, to see the storage as encrypted again in settings.
Trying a reboot to recovery I can't manage to get in. All Recoveries I tried, are stuck on the splash screen.

I tried the Pitchblack, OrangeFox, TWRP and SkyHawk recoveries, but it's the same with all of them.
Is there a working recovery that is able to decrypt the data?

Additionally, I setup a lockscreen Pin, but never got asked if I wanted a secure boot. So I'm unable to use a custom pin for the encryption key, which makes it somehow pointless to encrypt in the first place.
How can I solve that?

I want to use the phone without GApps. Instead I plan on using MicroG, which needs signature spoofing.
My old way using Riru Core, Riru EdXposed and the XposedModule FakeGapps to enable signature spoofing doesn't work anymore sadly.
Would it be possible to add a signature spoofing patch to your builds?


TL;DR:
- Is there a Recovery, able to decrypt the data partition encrypted from your rom?
- I can't set my lockscreen pin for a 'secure start', is that a bug or desired behaviour? (And if so, why? )
- Could you enable signature spoofing in your builds please?

Regards,
L

- This ROM uses FBE, Secure Boot is a FDE thing, the ROM will now "encrypts" always
- See 1
- No, I want to be compliant with LineageOS, I won't add anything additional to what it provides

 

[9Lukas5]

- This ROM uses FBE, Secure Boot is a FDE thing, the ROM will now "encrypts" always
- See 1
- No, I want to be compliant with LineageOS, I won't add anything additional to what it provides

Ok, so if I get this right, this is no bug that Android doesn't offer me a secure start anymore setting a lockscreen pin?
Maybe a bit offtopic, but if the storage can be decrypted by a default password that's not changeable, how is the data security provided?
Edit: Google FBE <-> FDE quickly.
So this means, a "secure start" is always provided automatically, if I set some sort of lockscreen security and the personal files will be accessible only after first unlock after a reboot?

Can you confirm if the recovery from your domain @haoquan linked above will work with the LOS18.1 encrypted data?

Regards,
L

 

[SebaUbuntu]

Can you confirm if the recovery from your domain @haoquan linked above will work with the LOS18.1 encrypted data?

fyi, LineageOS Recovery doesn't support data decryption

 

[9Lukas5]

fyi, LineageOS Recovery doesn't support data decryption

Yeah discovered this by now^^
That means there's no way of making a nandroid backup before altering around with updates, etc right now :/

But huge thanks for bringing up this rom. Thanks to your work and fully linking the device repo's, I were able to make a private build including the MicroG patch which is mandatory for me. So I finally switched from Pie, which was a rather old build by now.

What I found/would give as feedback so far:
- Video recording doesn't work (gives a green imaged video).
Tried with the built in camera and OpenCamera, both are the same.

L

 

[TheDon13]

I have stuck to Havoc 3.9 for past few months. Tried the latest Colt OS but on my Mi 8 lite at least it led to very erratic responses on fingerprint sensor, so I switched back to Havoc. Anyone actually used Lineage 18.1 on theirs and offer any feedback please?
Pros/cons vs Havoc pls

 

[lewismsc]

Thanks for this room, I see that the effort has been very gratifying.
I have a problem in the use of the camera, it does not allow recording the images
or videos to the internal or external memory, thanks if you can verify and correct this big problem I would be very grateful.

 

[9Lukas5]

I have stuck to Havoc 3.9 for past few months. Tried the latest Colt OS but on my Mi 8 lite at least it led to very erratic responses on fingerprint sensor, so I switched back to Havoc. Anyone actually used Lineage 18.1 on theirs and offer any feedback please?
Pros/cons vs Havoc pls

I'm using it since ~a week. It's fully stable for me so far
Basically everything except video recording works for me.

Android 10 roms had all the same bug blocking me from switching, that I couldn't playback my music sadly (aac, mpeg4-audio container), that's working fine here.
So I can't give you much of a comparison review, other than that

Thanks for this room, I see that the effort has been very gratifying.
I have a problem in the use of the camera, it does not allow recording the images
or videos to the internal or external memory, thanks if you can verify and correct this big problem I would be very grateful.

What camera do you use? I'm using OpenCamera, set to use Camera2API and take pictures. Just video recording takes a green image all the way through

L

 

[lewismsc]

I'm using it since ~a week. It's fully stable for me so far
Basically everything except video recording works for me.

Android 10 roms had all the same bug blocking me from switching, that I couldn't playback my music sadly (aac, mpeg4-audio container), that's working fine here.
So I can't give you much of a comparison review, other than that



What camera do you use? I'm using OpenCamera, set to use Camera2API and take pictures. Just video recording takes a green image all the way through

L

Good afternoon, flash the rom I use the camera that comes with the same rom and install several additional ones and there is no way I can save the photos and videos that I make with this or another camera. I like the rom, but if I can't use the camera, I fail

 

[lewismsc]

I'm using it since ~a week. It's fully stable for me so far
Basically everything except video recording works for me.

Android 10 roms had all the same bug blocking me from switching, that I couldn't playback my music sadly (aac, mpeg4-audio container), that's working fine here.
So I can't give you much of a comparison review, other than that



What camera do you use? I'm using OpenCamera, set to use Camera2API and take pictures. Just video recording takes a green image all the way through

L

I used this rom and it seems better than the original rom, it is quite stable, but for me it is essential to use the camera for both photos and videos and voice recording

 

[9Lukas5]

@lewismsc Do you know which firmware you're on?
I'm using the V10.3.2.0.PDTMIXM right now.

@SebaUbuntu could a too old / too new firmware cause these different experiences and is there a recommend firmware version for your rom?

L

 

[SebaUbuntu]

@lewismsc Do you know which firmware you're on?
I'm using the V10.3.2.0.PDTMIXM right now.

@SebaUbuntu could a too old / too new firmware cause these different experiences and is there a recommend firmware version for your rom?

L

It is recommended to use V12.0.3.0.QDTMIXM

 

[TheDon13]

Hi all, thanks for all the advice on what is still a very good phone. I have managed to change the firmware to V12.0.3.0.QDTMIXM MIUI via Mi Flash tool, but when I try to send TWRP recovery (tried several) in fastboot, it says its sent the recovery, but there is no root and fastboot does not go back into main TWRP screen. Never had an issue using firmware 10..3.2. I was using Havoc 3.9 custom rom for a good few months. Also tried Orange Fox & PitchBlack with same result.

Keen to try this lineage 18.1 rom, but I'm stuck.

Grateful for any advice please, as MIUI 12 has its limitations. Can't even get Whatsapp notifications at top of screen!

Thanks

 

[TheDon13]

After a good few hours over past few days of frustration, I realised I simply need to press Volume Up on phone when entering fastboot reboot command after successfully flashing TWRP recovery (3.3.1 I tried) ...at long last I can restore my backup from 14 Jan of Havoc 3.12 rom !