[ROM]LineageOS 20 - Xiaomi Mi 8

[haxnhaxn]

When I update the ROM, I lose Magisk, and from the console output of Recovery, it seems that the survival script did not run successfully and it could not find the Magisk binary.

Try the twrp Version by unnamedchronos.

 

[haxnhaxn]

Thanks for your information. I tried installing different gapps version (using NikGapps) and couldnt fix it.

I would recommend MindTheGapps. I dont have good experience with NikGapps.
Switching Gapps is probably a bad idea, so I recommend a clean install (I know its a pain) and then MindTheGapps. Dont change anything regarding Gapps after OTA.

 

[Erics9n]

I would recommend MindTheGapps. I dont have good experience with NikGapps.
Switching Gapps is probably a bad idea, so I recommend a clean install (I know its a pain) and then MindTheGapps. Dont change anything regarding Gapps after OTA.

Thanks for your suggestions.
However I have luckily fixed my problem by manually installing latest Pixel Launcher APK.

 

[M0ll0]

I'm trying to go from PE to LOS but I've been freaking out for 3 hours. Once done adb reboot bootloader, I try to do fastboot device but it comes out: "fastboot: usage: unknown command device". I already updated the drivers with disabled signature verification in Windows 11.

edit: ATM i've PE recovery and i'm trying to instal LOG recovery
after adb kill-server and adb start-server now device got recognised but error show up when flashing recovery:

fastboot flash recovery recovery.img
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 67108864).
Sending 'recovery' (65536 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed

 

[M0ll0]

I'm trying to go from PE to LOS but I've been freaking out for 3 hours. Once done adb reboot bootloader, I try to do fastboot device but it comes out: "fastboot: usage: unknown command device". I already updated the drivers with disabled signature verification in Windows 11.

edit: ATM i've PE recovery and i'm trying to instal LOG recovery
after adb kill-server and adb start-server now device got recognised but error show up when flashing recovery:

fastboot flash recovery recovery.img
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 67108864).
Sending 'recovery' (65536 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed

resolved on different pc with intel cpu,

 

[acehood88]

I'm trying to go from PE to LOS but I've been freaking out for 3 hours. Once done adb reboot bootloader, I try to do fastboot device but it comes out: "fastboot: usage: unknown command device". I already updated the drivers with disabled signature verification in Windows 11.

edit: ATM i've PE recovery and i'm trying to instal LOG recovery
after adb kill-server and adb start-server now device got recognised but error show up when flashing recovery:

fastboot flash recovery recovery.img
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 67108864).
Sending 'recovery' (65536 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed

Change usb port or cable.

 

[Pahoehoe]

When I update the ROM, I lose Magisk, and from the console output of Recovery, it seems that the survival script did not run successfully and it could not find the Magisk binary.

Try Lygisk instead of Magisk.

 

[k.stahanov73]

colleagues! Does anyone have a second camera working - a telephoto on this firmware?
and second - if you turn on the AOD, do we have pixel burn-in protection? do the captions move across the screen?

 

[mijiko200]

Thanks for your suggestions.
However I have luckily fixed my problem by manually installing latest Pixel Launcher APK.

Where did you get the APK from? I have tried with an apk but now I get that it has stopped every time.

 

[Erics9n]

Where did you get the APK from? I have tried with an apk but now I get that it has stopped every time.

I downloaded the apk from apkmirror, but I have tried different and older versions, because not every version worked.

 

[peacenut]

colleagues! Does anyone have a second camera working - a telephoto on this firmware?
and second - if you turn on the AOD, do we have pixel burn-in protection? do the captions move across the screen?

1. This gcam has working telephoto:

BSG: MGC_8.6.263_A11_V14a

Download MGC_8.6.263_A11_V14a by BSG.

www.celsoazevedo.com

Download the 2nd one.

That 1.7 is telephoto mode.

2. No. If you want to use AOD and avoid burn-in, use these options instead of "Always on" option:

 

[maormark]

Last year I figured out the cause of the issue and I informed Qualcomm and Linux kernel maintainers, I didn't want to keep you folk waiting for them to fix it so I'd made a temporary fix.
It seems that they have fixed it in both the upstream kernel and the CLA audio-kernel now, but they didn't backport it to a sdm845 tag!
I've made an experimental build with the required fixes backported. If all goes well, I'll submit a patch to Lineage Gerrit.
I've attached the build below, you'll have to flash it as a boot.img via recovery or fastboot, let me know if it fixes the problem.
I haven't had much time to test it, so make sure you're on lineage-20.0-20230216.

There is a chance that you can release a patch for the pixelexperience community as well?. tnx

 

[freeman94]

With the newest build my recent apps arent working anymore. When I leave an app and open my recent apps there are no apps available. Therefore multitasking aint working with this build.

Same for me, need solution

 

[Irish_Dude]

ROM is working flawlessly for me.

I rooted with Magisk and all banking apps work after flashing safety net fix in magisk. Battery life os good also

Great job @infrag

 

[najabi]

Who is going to take over after infrag?

 

[G A S T]

Who is going to take over after infrag?

What?

 

[G A S T]

Please note: I no longer maintain this ROM as my phone screen has cracked and I've moved on to a different device. Bgncm will probably continue to maintain it for mi8 as its similar to his other devices. Thanks for those that supported in the past and perhaps we will meet again in the future on a different device.

Oh, I did not read here for a while...
Which one is your new device? I already switched over to alioth. But it would be nice if Bgncm or someone else could take over the Maintainership here. But now:

Dear infrag,
thank you for your excellent Support of our great device! Without you we had probably never seen LOS on our phones.

Huge thanks for all those years!

And btw. - with regards to meeting again in the future - I would buy or recommend every device for LOS that's maintained by you!

Bye @infrag

 

[caputcha]

I switched from PE to this so damn Good experience ever had Thanks

 

[hammerhead123]

Flashed this ROM recently as the phone was stuck in bootloop after debloating some MIUI apps in stock ROM
My experience so far was great without much issue, battery life is good too compared to stock ROM and for a 5 years old device.
The only minor issue I had is that MTP wasn't working for me when using the ROM, my PC was able to detect and transfer file during recovery mode, but it doesn't affect much as I can use the working PTP or adb to transfer file.

 

[caputcha]

Flashed this ROM recently as the phone was stuck in bootloop after debloating some MIUI apps in stock ROM
My experience so far was great without much issue, battery life is good too compared to stock ROM and for a 5 years old device.
The only minor issue I had is that MTP wasn't working for me when using the ROM, my PC was able to detect and transfer file during recovery mode, but it doesn't affect much as I can use the working PTP or adb to transfer file.

MTP working as it should no issue at all.