Database Info

[ROM][OFFICIAL][kirin][11] LineageOS 18.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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.
Instructions :
https://wiki.lineageos.org/devices/kirin
Downloads :
https://download.lineageos.org/kirin
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

Thanks for the ROM!
Just installed the 20201003 build and it flawlessly so far.
Just a quick question, I can't seem to delete the search widget in the default launcher (quickstep), are there any way to delete it?
Also there are no "Advanced restart" option anymore, is there a way to have a reboot to recovery/bootloader entry in the new Android 11 power menu?

diyod said:
Thanks for the ROM!
Just installed the 20201003 build and it flawlessly so far.
Just a quick question, I can't seem to delete the search widget in the default launcher (quickstep), are there any way to delete it?
Also there are no "Advanced restart" option anymore, is there a way to have a reboot to recovery/bootloader entry in the new Android 11 power menu?
Click to expand...
Click to collapse
>Just a quick question, I can't seem to delete the search widget in the default launcher (quickstep), are there any way to delete it?
Launcher customizations aren't brought up yet thus search bar is stuck there for time being.
>Also there are no "Advanced restart" option anymore, is there a way to have a reboot to recovery/bootloader entry in the new Android 11 power menu?
Power menu additions aren't brought up either.

LuK1337 said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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.
What's not working :
WFD
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds :
https://www.androidfilehost.com/?w=files&flid=318024
http://downloads.codefi.re/jdcteam/luk/lineage-18_0/kirin
https://sourceforge.net/projects/luk-lineageos/files/kirin/lineage-18.0
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][kirin][11] LineageOS 18.0, ROM for the Sony Xperia 10
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Based On: LineageOS
Version Information
Status: Testing
Created 2020-09-28
Last Updated 2020-09-28
Click to expand...
Click to collapse
Hello. Does the rom have signiture spoofing?

Gapps Not working
LineageOS version: 18.0
LineageOS Download url: First one I can`t submit the post with the link, this is the version: lineage-18.0-20201016_012612-UNOFFICIAL-kirin.zip
Gapps version: Here is where the issue occurs. None of the Gapps found here, and in first pages in Google by searching "Lineage OS 18 gapps" or either "Android 11 gapps" ever worked on Lineage OS 18.
I flashed with TWRP (I tried also with the Lineage OS recovery but I know that Gapps are not signed and return error from there) Immediately after a clean installation of Lineage OS 18 and wipe, All Open Gapps versions found, BitApps, NikApps and others came with error code 20, error code 70 (I tried with resizing the partition, switching slots, did not work) or fatal error. I managed to flash some of them successfully but they never showed up after turning on the phone.
Everything else except Gapps working as expected until now.
The same kernel is used as for Lineage OS 17.1 that was previously used with a working OpenGapps flash.
The phone version is Xperia 10 I4113, no modifications were made, just Unlocked bootloader, TWRP recovery, Flashed Lineage OS 18 and Flashed all versions of Gapps with no success.
In case you`ve tested and got Gapps successfully after installing the rom share this version with us so we can flash it and use the ROM for daily routines by continue testing.
Thanks in advance.
Regards.

dian1994 said:
LineageOS version: 18.0
LineageOS Download url: First one I can`t submit the post with the link, this is the version: lineage-18.0-20201016_012612-UNOFFICIAL-kirin.zip
Gapps version: Here is where the issue occurs. None of the Gapps found here, and in first pages in Google by searching "Lineage OS 18 gapps" or either "Android 11 gapps" ever worked on Lineage OS 18.
I flashed with TWRP (I tried also with the Lineage OS recovery but I know that Gapps are not signed and return error from there) Immediately after a clean installation of Lineage OS 18 and wipe, All Open Gapps versions found, BitApps, NikApps and others came with error code 20, error code 70 (I tried with resizing the partition, switching slots, did not work) or fatal error. I managed to flash some of them successfully but they never showed up after turning on the phone.
Everything else except Gapps working as expected until now.
The same kernel is used as for Lineage OS 17.1 that was previously used with a working OpenGapps flash.
The phone version is Xperia 10 I4113, no modifications were made, just Unlocked bootloader, TWRP recovery, Flashed Lineage OS 18 and Flashed all versions of Gapps with no success.
In case you`ve tested and got Gapps successfully after installing the rom share this version with us so we can flash it and use the ROM for daily routines by continue testing.
Thanks in advance.
Regards.
Click to expand...
Click to collapse
Did you actually reboot recovery between installing rom and gapps?

LuK1337 said:
Did you actually reboot recovery between installing rom and gapps?
Click to expand...
Click to collapse
Yes, I did that multiple times during all night long with many different Gapps versions and reboots of the recovery between ROM flashing and Gapps.
If it is possible to provide a Download URL with Gapps version that has been tested on your end by this way after ROM flashes and it works that will be highly appreciated.
I`ve switched back in 17.1 twice by installing Gapps without issues.
I am currently using the ROM without Gapps so I can wipe and trigger a new flash of Gapps from the recovery, but none of the versions I already tried ever showing up or complete installation.
Thank you for your time and support.

dian1994 said:
Yes, I did that multiple times during all night long with many different Gapps versions and reboots of the recovery between ROM flashing and Gapps.
If it is possible to provide a Download URL with Gapps version that has been tested on your end by this way after ROM flashes and it works that will be highly appreciated.
I`ve switched back in 17.1 twice by installing Gapps without issues.
I am currently using the ROM without Gapps so I can wipe and trigger a new flash of Gapps from the recovery, but none of the versions I already tried ever showing up or complete installation.
Thank you for your time and support.
Click to expand...
Click to collapse
You tried fastboot booting twrp and installing gapps there?

LuK1337 said:
You tried fastboot booting twrp and installing gapps there?
Click to expand...
Click to collapse
Yes, exactly I am using adb to flash the ROM first, then flash TWRP recovery via fastboot and then flashing gapps via adb from TWRP recovery again by repeating this order in every gapps version which does not take effect or return error 20 or error 70 (open gapps) and fatal error for NikApps.
If it is important I am using MacOS, but we tried from Windows ADB once without much of success.

dian1994 said:
Yes, exactly I am using adb to flash the ROM first, then flash TWRP recovery via fastboot and then flashing gapps via adb from TWRP recovery again by repeating this order in every gapps version which does not take effect or return error 20 or error 70 (open gapps) and fatal error for NikApps.
If it is important I am using MacOS, but we tried from Windows ADB once without much of success.
Click to expand...
Click to collapse
What fatal error are you getting on nikgapps?

LuK1337 said:
What fatal error are you getting on nikgapps?
Click to expand...
Click to collapse
Currently I can not remember if BitApps version or NikApps returned the error, but the error said that this version is not compatible and the flash just stopped with general error in TWRP recovery log. One of them returned the error, the other one has completed but nothing has showed up after booting to the OS.
I am in the office right now and did not get the cable but if you have suggestions on specific versions of gapps that you think are working, I will try to flash each one by following your instructions tomorrow night after work and provide you with feedback of screenshot of TWRP recovery log for every single gapps package.
If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away.

dian1994 said:
Currently I can not remember if BitApps version or NikApps returned the error, but the error said that this version is not compatible and the flash just stopped with general error in TWRP recovery log. One of them returned the error, the other one has completed but nothing has showed up after booting to the OS.
I am in the office right now and did not get the cable but if you have suggestions on specific versions of gapps that you think are working, I will try to flash each one by following your instructions tomorrow night after work and provide you with feedback of screenshot of TWRP recovery log for every single gapps package.
If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away.
Click to expand...
Click to collapse
NikGapps-omni-arm64-11-20201010-signed.zip seems to install properly here.
>If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away
Not yet, I just ported the patch that allows for that btw.

LuK1337 said:
NikGapps-omni-arm64-11-20201010-signed.zip seems to install properly here.
>If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away
Not yet, I just ported the patch that allows for that btw.
Click to expand...
Click to collapse
Thanks I will give a try and let you know about the result.

LuK1337 said:
NikGapps-omni-arm64-11-20201010-signed.zip seems to install properly here.
>If there is a version which you know that can go thru the security signing check from Lineage recovery I can try to flash it from the sdcard right away
Not yet, I just ported the patch that allows for that btw.
Click to expand...
Click to collapse
I just want to let you know that this version worked as expected. I have no explanation but probably I did something wrong with the slots. Thanks. I will keep you posted in case of a bug found. However Gapps required TWRP, Lineage recovery does not install gapps due Signing request error.

Bugs Report
I would like to come up with a short report of what did not work with the rom for a few weeks of using.
Actually almost everything works except two main functions.
1. Wi - Fi HotSpot do not work. It shows up but when you connect from another device there is no internet connection. 4G has been established on LineageOS but do not reach the external device via Wi - Fi hot spot.
2. Google accuracy location service does not work, GPS works only when you stay outside. I do not know if it is related to GApps or Rom backend. If you run an app that requires location services will run only outside which is a quite too bad.
That's it for now. Hope it helps.

dian1994 said:
I would like to come up with a short report of what did not work with the rom for a few weeks of using.
Actually almost everything works except two main functions.
1. Wi - Fi HotSpot do not work. It shows up but when you connect from another device there is no internet connection. 4G has been established on LineageOS but do not reach the external device via Wi - Fi hot spot.
2. Google accuracy location service does not work, GPS works only when you stay outside. I do not know if it is related to GApps or Rom backend. If you run an app that requires location services will run only outside which is a quite too bad.
That's it for now. Hope it helps.
Click to expand...
Click to collapse
1. Consider not being over 5 builds behind.

LuK1337 said:
1. Consider not being over 5 builds behind.
Click to expand...
Click to collapse
You mean that Wi-Fi hot spot issue has been fixed already in a recent build?

dian1994 said:
You mean that Wi-Fi hot spot issue has been fixed already in a recent build?
Click to expand...
Click to collapse
Go ahead and try.

LuK1337 said:
Go ahead and try.
Click to expand...
Click to collapse
Gotcha. Thanks.

has anyone had any luck getting magisk 21.1 to work with this rom and twrp yet?
im going round in circles trying to root after updating. i can install magisk from twrp, but i end up in a bootloop, then installing the bootloop fix from twrp wipes magisk and breaks root.
i know 21.1 is a beta and likely doesnt support sony phones yet, but someone might have a fix.
EDIT: I have root working now. Anyone having trouble, DONT install twrp to ramdisk. just leave the lineageOS recovery in place and use fastboot on a pc to boot twrp when you need it.
I did the following:
1. fresh stock firmware via newflash
2.flash sony software binaries for a11
3. fastboot boot twrp.img
4.swap to partition b
5. power off
6. fastboot boot twrp.img (check you are booted to partition b)
7. flash lineageos 18
8.reboot select partition a and POWER OFF
9. fastboot boot twrp.img
10. check partition is a
11. flash copy partition.zip
12. flash magisk 21.1.zip
13. flash nikGapps basic for a11
14. reboot system
15. install magiskmanager 8.0.3.apk
16. reboot
17. update your apps on playstore.
18. PROFIT.
lineage os18 rooted on my xperia 10.

born2bkilled said:
I did the following:
1. fresh stock firmware via newflash
2.flash sony software binaries for a11
3. fastboot boot twrp.img
4.swap to partition b
5. power off
6. fastboot boot twrp.img (check you are booted to partition b)
7. flash lineageos 18
8.reboot select partition a and POWER OFF
9. fastboot boot twrp.img
10. check partition is a
11. flash copy partition.zip
12. flash magisk 21.1.zip
13. flash nikGapps basic for a11
14. reboot system
15. install magiskmanager 8.0.3.apk
16. reboot
17. update your apps on playstore.
18. PROFIT.
lineage os18 rooted on my xperia 10.
Click to expand...
Click to collapse
Which package is it you use?
If I flash the Gapps, Lineage can't boot into system and asks for a factory reset.
I'm following the steps exactly as they're described.
Am I missing something?

Just installed it. Was some effort, coming from SailfishX.
Had to install Sony binaries first, then get the latest TWRP (old one gave me errors, the provided one in this post as well). After that installed NikGapps (Gapps or open Gapps do not work I think). Was up till 3am
Got some problems though:
Cannot enable wifi.
Does not detect cellular network at all?
GUI stopped working error at every boot (works after clicking at away).
Settings stopped responding when I click network.
Fingerprint does not seem to be working? Do I need a specifiek Gapps version for that?
Can you tell me what the camera mod does? I do not see any difference?
Thanks for the effort this far!
Edit: I seem to be missing the firmware alltogether. Any ideas how to fix this?

[ROM][OFFICIAL][sunfish] LineageOS 18.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. LineageOS does still include various proprietary hardware-specific code.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
Before the initial installation, please make sure your Pixel 4a has already been updated to Android 11 official firmware so that the recovery can function correctly.
This ROM comes with latest firmware bundled, so after the initial flash you don't need to worry about updating firmware manually.
This ROM comes with source-built kernel and modules
eSIM functions without GAPPS, but to manage (add / erase) eSIMs you will need to have GAPPS installed
Installation
Update your Pixel 4a to official Android 11
Download the latest boot.img and rom zip
Boot to bootloader
fastboot flash boot boot.img
Boot to recovery
Format data
Flash LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Flash the addons
Reboot
Updating
Boot to recovery
Flash LineageOS zip
Flash the same addons you had previously installed:
Advanced > Reboot to recovery
Flash the addons
Reboot
Downloads
Official: https://download.lineageos.org/sunfish
Reporting bugs
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/* (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
Known Issues
On the first boot, you might be presented the message "SIM Manager has crashed". You can safely ignore it.
Source Code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com

PeterCxy said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. LineageOS does still include various proprietary hardware-specific code.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
Before the initial installation, please make sure your Pixel 4a has already been updated to Android 11 official firmware so that the recovery can function correctly.
This ROM comes with latest firmware bundled, so after the initial flash you don't need to worry about updating firmware manually.
This ROM comes with source-built kernel and modules
eSIM functions without GAPPS, but to manage (add / erase) eSIMs you will need to have GAPPS installed
Installation
Update your Pixel 4a to official Android 11
Download the latest boot.img and rom zip
Boot to bootloader
fastboot flash boot boot.img
Boot to recovery
Format data
Flash LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Flash the addons
Reboot
Updating
Boot to recovery
Flash LineageOS zip
Flash the same addons you had previously installed:
Advanced > Reboot to recovery
Flash the addons
Reboot
Downloads
Official: https://download.lineageos.org/sunfish
Reporting bugs
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/* (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
Known Issues
On the first boot, you might be presented the message "SIM Manager has crashed". You can safely ignore it.
Source Code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
Click to expand...
Click to collapse
Using it now... ROM is stable, smooth and fast... as of now...
Initially, I couldn't call or text but after resetting the apn and switching it once to 2G and reverting back to 4G should fix that...( Jio users India).
Used nikgapps
https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/30-Jan-2021/NikGapps-core-arm64-11-20210130-signed.zip/download

PeterCxy said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. LineageOS does still include various proprietary hardware-specific code.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
Before the initial installation, please make sure your Pixel 4a has already been updated to Android 11 official firmware so that the recovery can function correctly.
This ROM comes with latest firmware bundled, so after the initial flash you don't need to worry about updating firmware manually.
This ROM comes with source-built kernel and modules
eSIM functions without GAPPS, but to manage (add / erase) eSIMs you will need to have GAPPS installed
Installation
Update your Pixel 4a to official Android 11
Download the latest boot.img and rom zip
Boot to bootloader
fastboot flash boot boot.img
Boot to recovery
Format data
Flash LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Flash the addons
Reboot
Updating
Boot to recovery
Flash LineageOS zip
Flash the same addons you had previously installed:
Advanced > Reboot to recovery
Flash the addons
Reboot
Downloads
Official: https://download.lineageos.org/sunfish
Reporting bugs
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/* (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
Known Issues
On the first boot, you might be presented the message "SIM Manager has crashed". You can safely ignore it.
Source Code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
Click to expand...
Click to collapse
Any way to use banking apps bro... (Like in descendent without magisk)

Raj Pandiyan said:
Any way to use banking apps bro... (Like in descendent without magisk)
Click to expand...
Click to collapse
I'm sorry but LineageOS does not provide any officially-supported way to bypass SafetyNet restrictions. Please look into third-party solutions for that.

I happened to install the last unofficial LOS (lineage-18.1-20210308) on a new phone an hour before this was released. I have everything setup and installed, safetynet passes etc etc, is it worth upgrading to this? Are there any big differences?
Also, is it possible to use twrp with this or lineage-18.1-20210308?
Thanks.

Fung-i said:
I happened to install the last unofficial LOS (lineage-18.1-20210308) on a new phone an hour before this was released. I have everything setup and installed, safetynet passes etc etc, is it worth upgrading to this? Are there any big differences?
Also, is it possible to use twrp with this or lineage-18.1-20210308?
Thanks.
Click to expand...
Click to collapse
The unofficial build will still be updated, but if you don't need microG it might be a better idea to switch to the official build for more timely updates and official guarantees. Of course, to switch to the official build, you have to wipe all data and start over.
I have no experience with TWRP on Pixel 4a.

has anyone had issues flashing rom using adb sideload and it failed , when loading recovery after reboot from data wipe , has failed mount emulated/0/
will try again and post imgs , have been able to flash unofficial and any other roms besides grapheneos, same issue upon flashing rom ,on latest stock android 11 unlocked bootloader

miko12312 said:
has anyone had issues flashing rom using adb sideload and it failed , when loading recovery after reboot from data wipe , has failed mount emulated/0/
will try again and post imgs , have been able to flash unofficial and any other roms besides grapheneos, same issue upon flashing rom ,on latest stock android 11 unlocked bootloader
Click to expand...
Click to collapse
No problem here, flashed with mindthegapps.

any idea why nikogapps stock package doesn't work (device does not boot ) but Core package does?

PeterCxy said:
The unofficial build will still be updated, but if you don't need microG it might be a better idea to switch to the official build for more timely updates and official guarantees. Of course, to switch to the official build, you have to wipe all data and start over.
I have no experience with TWRP on Pixel 4a.
Click to expand...
Click to collapse
hi,
first of all, i want to thank you very much for your hard work on this rom. I have installed it yesterday and it runs perfectly showing almost 50% battery life increase and much better performance comparing to stock. I just noticed one strange thing: I can not monitor the kernel wakelocks using BBS as well as GSAM Battery monitor utilities. Both got root permission but don't show Kernel Wakelocks at all. Do you have any idea what could be the reason? I can access the /sys/kernel/debug fs, but don't see anything helpful in logcat...

Does the "Show battery percentage in status bar" works for anyone?

HeartWood said:
Does the "Show battery percentage in status bar" works for anyone?
Click to expand...
Click to collapse
you should be able to configure the battery percentage using settings > system > status bar

wawap68 said:
any idea why nikogapps stock package doesn't work (device does not boot ) but Core package does?
Click to expand...
Click to collapse
It replaces many of LOS stock apps and stuff... So download omni variant, extract and edit nikgapps config file ( It is self understandable when you open and read it.. basically change variable from 1 to 0 which affect LOS framework and default apps like dialer etc...)... Again zip them and now sideload... It should work fine...

Got everything working passing safteynet

miko12312 said:
Got everything working passing safteynet
Click to expand...
Click to collapse
please tell us what method worked for you!

mma1162 said:
hi,
first of all, i want to thank you very much for your hard work on this rom. I have installed it yesterday and it runs perfectly showing almost 50% battery life increase and much better performance comparing to stock. I just noticed one strange thing: I can not monitor the kernel wakelocks using BBS as well as GSAM Battery monitor utilities. Both got root permission but don't show Kernel Wakelocks at all. Do you have any idea what could be the reason? I can access the /sys/kernel/debug fs, but don't see anything helpful in logcat...
Click to expand...
Click to collapse
fugured it out. It was the Magisk Fault. After reconfiguring BBS using ADB everything worked fine.
BTW the battery life is gorgeous comparing to stock ))

claviger-pc said:
please tell us what method worked for you
Click to expand...
Click to collapse
claviger-pc said:
please tell us what method worked for you!
Click to expand...
Click to collapse
1. extract the boot from LOS payload.bin
2. install Magisk 22 by patching the extracted boot image
3. hide the magisk from: google play store, play services, gpay, clear data for all these apps.
4. install magisk module safetynet-fix-v1.1.1.zip
5. reboot

Firstly, I want to thank the Lineage team and those who accompany our device.
I have been using this firmware since April 1 and have not seen any particular problems. However, it lacks some features that were in the RR 8 - a charging indicator when displaying a textual charge level, an extended reboot menu (recovery and bootloader). Or maybe I didn't find it =)
And as far as I understand it is now impossible to update LOS 18.1 via OTA, but only through recovery?

droncheg said:
Firstly, I want to thank the Lineage team and those who accompany our device.
I have been using this firmware since April 1 and have not seen any particular problems. However, it lacks some features that were in the RR 8 - a charging indicator when displaying a textual charge level, an extended reboot menu (recovery and bootloader). Or maybe I didn't find it =)
And as far as I understand it is now impossible to update LOS 18.1 via OTA, but only through recovery?
Click to expand...
Click to collapse
Advanced restart option is there.

Anyone coming off the unofficial build... tips? I nuked everything: went back to stock, flashed Lineage recovery, wiped/data reset, flashed zip, rebooted to recovery, then flashed MindTheGapps as OpenGapps won't install due to a version mismatch. Been stuck on the boot screen for eons.
Went back and repeated the process only to still be stuck on boot screen. Is there any log I can record/provide to figure out what's going on?

[ROM][OFFICIAL][11] LineageOS 18.1 for Galaxy Note10/Note10+/Note10+ 5G Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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.
Instructions:
Follow the instructions on the wiki page for your device https://wiki.lineageos.org/devices/#samsung
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820

reserved

reserved

What is different between this build and your previous one ?

Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available

Vishnarov said:
What is different between this build and your previous one ?
Click to expand...
Click to collapse
Read the thread's title ... It's official now.
[email protected] said:
Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available
Click to expand...
Click to collapse
No, sorry hardware is too different.

builds have been removed from the lineage os website?

Enddo said:
builds have been removed from the lineage os website?
Click to expand...
Click to collapse
Yes, see this for the reason
This affected all devices so builds of last few days were pulled and sadly we had only that one build yet
There will be new ones next week

Does the build support hardware encryption or software encryption?

You should put what models this is for as to avoid confusion

just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch

Enddo said:
just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch
Click to expand...
Click to collapse
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.

CerebralFlex said:
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.
Click to expand...
Click to collapse
certainly no locked bootloader here (have had it unlocked since right after I bought it at launch)
but yea, I'm going to try and reflash the ROM and start from scratch. I was on an outdated version of ONe UI (maybe from December) so maybe that was part of the issue
EDIT - oddly enough, I couldn't get LOS recovery installed via Odin. I tried, got success messages, but a reboot into recovery mode just showed stock recovery (I wasn't missing the button combo, to my knowledge). tried a few times before going back to using heimdall
the second attempt (with a fresh install of OneUI's latest firmware) helped me get past that vbmeta error with heimdall
got LOS recovery installed, the ROM sideloaded, and I'm up and running
thanks for the hard work @Linux4 (and all others involved in working on lineageos)

First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?

Phosphoros said:
First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?
Click to expand...
Click to collapse
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)

is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before

Enddo said:
is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before
Click to expand...
Click to collapse
It is not broken or whatever, see this from my telegram group in case you just don't figure it out on your own:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
All samsung devices using FOD have that issue it seems, only on first enrollment tho, after that it's completely fine

Linux4 said:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
EDIT - was able to get it working through a factory reset with the 'tap fast' being the key thing. it needs to fail that first attempt or something?
but it's quite quick once that hassle is over with

Enddo said:
this worked for me on my first install. describes my exact experience
but yea, it's not working right now. you need a logcat or something?
it's immediately throwing up the enrollment error message right when it attempts the first scan (every time)
Click to expand...
Click to collapse
No need for a logcat, it does work, for retrying you will need to close settings completely, just going *back* is not enough (HAL will stay in that error state)
I'm 100% sure you didn't do so also it works for everyone else

Linux4 said:
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)
Click to expand...
Click to collapse
Ok, thought about waiting for this ... thanks for confirming it!

[ROM][OFFICIAL][instantnoodle][13] LineageOS 20

DISCLAIMER​Anything you do to your own device is your responsibility and your responsibility only. You may NOT hold me responsible for any damage caused to your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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.
The only official site with proper instructions to install LineageOS is https://wiki.lineageos.org/. Any instructions that come from anywhere else is not to be trusted at all.
You should especially distrust instructions from websites that try and impersonate LineageOS. One example of such a site is lineageosroms[.]com.
Instructions​Scroll down to the 2nd post in this thread for installation and upgrade information.
Reporting Bugs​Please follow the instructions here to report your bug to our GitLab issues if you can, as it makes it easier for us to keep track of bugs and progress on fixing them.
However, should you be unable to do so and must post your bug report in this thread instead, then please adhere to the following guidelines:
DO NOT Report bugs if you're running a custom kernel, have installed Magisk, Xposed, or have done modifications to your device that touch any of the read-only partitions (with GApps being the only exception).
As this is an A/B device, recovery will not run addon.d scripts. As such, try undoing all the modifications by reflashing the rom + GApps (if you used them) in recovery--no need to wipe data. After that, check to see if the bug is still there.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

Telegram Chat:​I have a Telegram group that you can join if you prefer to chat that way, as opposed to posting on a forum thread. Join here.
Supported models:​The only officially supported models are the following:
IN2010 (China)
IN2011 (India)
IN2013 (Europe/Asia)
IN2015 ("Global"/NA)
IN2017 (T-Mobile) is unofficially supported, as that's what I did my device bringup against.
IN2019 (Verizon) is not supported. VZW sensor configs are not bundled in this ROM, so accelerometer/gyroscope and magnetometer readings are going to be incorrect. In addition, battery gauge reading seems to be broken, based on one user trying this ROM on their IN2019 despite it being unsupported. I am likely not going to fix this anytime soon, as I do not have an IN2019 to validate my fixes against.
Upgrading from LineageOS 19.1:​If you are coming from LineageOS 19.1 AND using LineageOS 19.1 Recovery, then follow the instructions here to upgrade. Remember to flash Android 13 GApps if you used GApps previously.
We ship the required firmware (OxygenOS 13 11.F.13 as of 2022-12-31) in our OTA zips, so you do not need to install that firmware to both your slots on your OnePlus 8 before proceeding through the instructions.
Installing LineageOS 20 for the first time:​Prerequisites:​Ensure you've installed any version of OxygenOS/ColorOS 12 or 13 on the active slot on your device. The installation instructions recommend you be on OOS/COS 13 because on OOS/COS 12, touchscreen will end up not working while in LineageOS Recovery. However, you can still proceed while using OOS/COS 12 firmware; use the volume keys + power button to navigate recovery.
Instructions:​Once you satisfy the prerequisites above, then follow the instructions here to install LineageOS 20.
We ship the required firmware (OxygenOS 13 11.F.13 as of 2022-12-31) in our OTA zips, so you do not need to install that firmware to both your slots on your OnePlus 8 before proceeding through the instructions.

Currently Known Bugs​Occasional 1-2 second freezes when waking the device from sleep​Sometimes, when you wake the device, you can see the display seemingly freeze for 1-2 seconds while it's fading in the lockscreen. Unfortunately, I don't know why that happens, and I don't think I'll be able to fix that myself anytime soon.
Light sensor readings do not filter out light coming from the screen​The light sensor is placed way too close to the top of the screen, so light bleed from the screen ends up affecting light sensor readings. On OOS, they use some algorithm to determine how much of the light detected by the sensor is actually coming from the display itself, and then subtract that value from the reading. We currently don't have anything to handle that for this LineageOS build. Some people have tried developing their own algorithm for this on the OnePlus 7 series of devices, but apparently, it doesn't work that well, so it was never brought over to the OnePlus 8 series of devices. In addition to that, novenary was reverse engineering OnePlus's implementation, but they stopped working on that since they no longer daily drive their hotdogb.
As such, expect Adaptive Brightness to be very much unusable, as the feedback loop caused by the light sensor sensing the light from the screen will result in Adaptive Brightness increasing the brightness all the time.
UDFPS (Under-display Fingerprint Sensor) doesn't work properly in 90° and 270° screen rotations​For both 90° and 270° (both of which are landscape orientations), the HWC layer for the UDFPS circle doesn't get excluded from the dimlayer, and as such, it doesn't end up illuminating bright enough to scan your finger. The circle is still positioned in the right place, so there could still be a possibility that one could figure out how to fix this.
UDFPS (Under-display Fingerprint Sensor) doesn't work properly in 180° screen rotation​For 180° (upside-down), not only is the auth dialog window in the wrong place, but the UDFPS circle doesn't even show up. This will not be fixed.
Mic input volume in speakerphone and video/audio recordings seems quieter than usual​This is still being explored, but it ends up seeming like the top mic's gain is too low or something? More details to come...
Spoiler: Old Bugs
Ambient Display (Always-on Display) may not work properly if panel can't freely switch between 60Hz and 90Hz​(Fixed in 2023-01-21 build)
With Ambient Display enabled, when you "turn off" the screen, the panel will first show the Ambient Display info at normal brightness before trying to switch to LP1 mode. However, for instantnoodle, that mode seems to cause the panel to blank out entirely. It's only when Android decides to switch between 60/90Hz that the panel ends up turning back on, and that usually takes up to 6 seconds for that to happen.
This is under investigation still. Since the LP1 panel command's payloads are specific to this panel (Samsung amb655uv01), and since I have not found a datasheet for this panel, I may not be able to fix this. Either that, or I would need to prevent the LP1 command from running in the first place, and then see if that affects battery life.
EDIT: Fix is up: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8250/+/347184
Thanks to @javelinanddart for taking a look and deducing which part of the LP1 command was causing the screen to blank.
While WiFi calling is enabled, VoIP calls (Google Voice, TextNow, etc.) starts stuttering frequently on WiFi​(Fixed in 2023-01-21 build)
A few hours after turning on WiFi Calling on the OnePlus 8, you'll likely notice that VoIP calls on apps like Google Voice and TextNow will seem to stutter while on WiFi, getting to the point where the call is unstable and neither party can really talk to each other. This bug is related to IMS making the cnd daemon from qcom's CNE request WiFi ext stats every two seconds. A race condition in the qcacmn kernel driver could end up happening during one of these requests, which potentially leads to every subsequent ext stats request timing out after waiting for 1.5 seconds. During that 1.5 second period, VoIP packets seem to get dropped entirely. This issue has been present since LineageOS 18.1, it seems.
I do have code that works around this race condition, but I don't think it's ready to review yet because I'm still trying to learn more about the qcacmn driver. I will update this space with more info when ready.
EDIT: Fix is up: https://review.lineageos.org/c/LineageOS/android_kernel_qcom_sm8250/+/347290
Thanks to Andrea for showing a way to work around this race condition that required fewer code changes.
CPU scheduler becomes reluctant to schedule tasks on the Gold and Prime CPU clusters 15-30 minutes after boot​(Fixed in 2023-01-21 build)
After rebasing on latest qcom sm8250 + Android Common Kernel source, we ended up getting a regression in how the CPU scheduler works. For some reason, 15-30 minutes after booting up, it ends up becoming very reluctant to schedule tasks on the Prime cluster, and (I suppose) somewhat reluctant to schedule tasks on the Gold cluster.
The fix for this is up: https://review.lineageos.org/c/LineageOS/android_kernel_qcom_sm8250/+/347313
Thanks to @V3NK4135H for their help in identifying the fix.
Ambient Display (Always-on Display) appears dimmer than usual if you have at least one fingerprint registered​(Fixed in 2023-03-11 build.)
With Ambient Display enabled, when the panel enters LP1 mode, the screen seems to dim by a significant amount. This is due to the biometrics HAL enabling dimlayer_hbm while listening for a fingerprint. Turning on dimlayer_hbm results in High Brightness mode being enabled, but with a dimlayer overlaying everything except for the UDFPS circle. This allows the UDFPS circle to shine at HBM levels of backlight while everything else remains at the original brightness level. However, if dimlayer_hbm is still on while the panel enters LP1 mode, then High Brightness mode turns off, but the dimlayer still remains. This results in everything being dimmer than it really should be.
I have a bunch of changes in the pipeline that not only fixes that, but also uses the dimlayer to mimic various brightness steps so that the perceived brightness in LP1 mode will match what your display had in ON mode. Will post updates in the thread once it gets merged.

May I ask when can I download lineageOS 20, as I got some problems with my lineageOS 19

YukikazeMywaifu said:
May I ask when can I download lineageOS 20, as I got some problems with my lineageOS 19
Click to expand...
Click to collapse
Hopefully within the next 24 hours... all the lineage-20 devices got their builds triggered today, but it will be some time before instantnoodle build starts running.

Hi! I can't get "File Transfer" to work now when connecting the phone to Windows 11- previously no problems with 19.1.
Seems I now have a unrecognized MTP driver. Any thoughts?

MadCTR said:
Hi! I can't get "File Transfer" to work now when connecting the phone to Windows 11- previously no problems with 19.1.
Seems I now have a unrecognized MTP driver. Any thoughts?
Click to expand...
Click to collapse
ok, turning off USB debugging makes it work with no problem, not sure it this is supposed to be like that. Anyways, awesome job since everything is basically working great!

MadCTR said:
ok, turning off USB debugging makes it work with no problem, not sure it this is supposed to be like that. Anyways, awesome job since everything is basically working great!
Click to expand...
Click to collapse
That's good to hear. In the meantime, EdwinMoq put this up as a potential fix: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8250/+/346680

Maybe a rather stupid question, but if I were to upgrade to 20, would I have to reinstall all my apps or will they automagically carry over?

mtmoretz said:
Maybe a rather stupid question, but if I were to upgrade to 20, would I have to reinstall all my apps or will they automagically carry over?
Click to expand...
Click to collapse
If you follow the upgrade procedure, then all your userdata should remain intact.

I had a fairly seemless upgrade from LineageOS 19 to Lineage 20 following LibeageOS's guide with no data loss.
Lost root and MicroG (no GApps on my phone). I did rename Magisk.apk to Magisk.zip and sideloaded it right after sideloading LineageOS.
To get root back:
Extract boot.img with payload-dumper-go (I use Artix Linux).
Download LineageOS 20 recovery.
Transfer the two image files to the phone.
From the Magisk app on the phone, patch boot.img and the recovery image.
Upload the two patched files back to the computer.
Reboot phone into recovery (adb reboot recovery) and then put it into fastbootd mode (advanced, fastboot - I think)
Now execute the following commands:
1. fastboot devices (note that it's in fastbootd mode)
2. fastboot flash boot_a {your_Magisk_patched_boot_image}
3. fastboot flash boot_b {your_Magisk_patched_boot_image}
4. fastboot flash recovery_a {your_Magisk_patched_recovery_image}
5. fastboot flash recovery_b {your_Magisk_patched_recovery_image}
6. Reboot phone ('fastboot reboot' works)
Always works for me. Your milage may vary.

jabashque said:
If you follow the upgrade procedure, then all your userdata should remain intact.
Click to expand...
Click to collapse
You weren't joking; it didn't even close the apps I had open during the upgrade, absolutely flawless! Thanks again!

Hi. It works almost fine, but I can't connect to the cellular network and when I make a call it tells me to turn off airplane mode. Of course not in airplane mode. Any workaround?

osetiopica said:
Hi. It works almost fine, but I can't connect to the cellular network and when I make a call it tells me to turn off airplane mode. Of course not in airplane mode. Any workaround?
Click to expand...
Click to collapse
Some questions:
Is this the T-Mobile variant of the OnePlus 8?
What were you running prior to LineageOS 20? Give details about what upgrade path you took, because I do recall there is one situation where trying to use the non-T-Mobile modem image on a T-Mobile variant OnePlus 8 will not work.

kokanee1 said:
I had a fairly seemless upgrade from LineageOS 19 to Lineage 20 following LibeageOS's guide with no data loss.
Lost root and MicroG (no GApps on my phone). I did rename Magisk.apk to Magisk.zip and sideloaded it right after sideloading LineageOS.
To get root back:
Extract boot.img with payload-dumper-go (I use Artix Linux).
Download LineageOS 20 recovery.
Transfer the two image files to the phone.
From the Magisk app on the phone, patch boot.img and the recovery image.
Upload the two patched files back to the computer.
Reboot phone into recovery (adb reboot recovery) and then put it into fastbootd mode (advanced, fastboot - I think)
Now execute the following commands:
1. fastboot devices (note that it's in fastbootd mode)
2. fastboot flash boot_a {your_Magisk_patched_boot_image}
3. fastboot flash boot_b {your_Magisk_patched_boot_image}
4. fastboot flash recovery_a {your_Magisk_patched_recovery_image}
5. fastboot flash recovery_b {your_Magisk_patched_recovery_image}
6. Reboot phone ('fastboot reboot' works)
Always works for me. Your milage may vary.
Click to expand...
Click to collapse
Patching boot.img is unnecessary to regain root, no? I have only ever had to sideload the Magisk zip file after sideloading the ROM zip. If you ran into any issues sideloading originally, it could be because you did not reboot recovery after sideloading the ROM (Advanced, Reboot to Recovery). To be safe I do it after sideloading every addon (sideload ROM, reboot to recovery, sideload GApps, reboot to recovery, sideload Magisk, reboot to system), and all data was completely intact through this process.

Just wanted to thank you for the continued support! I saw you wrote that Display Alt should be working again, so I'll check it out as soon as I can get MicroG to work with it!

GregWooledge said:
Patching boot.img is unnecessary to regain root, no? I have only ever had to sideload the Magisk zip file after sideloading the ROM zip. If you ran into any issues sideloading originally, it could be because you did not reboot recovery after sideloading the ROM (Advanced, Reboot to Recovery). To be safe I do it after sideloading every addon (sideload ROM, reboot to recovery, sideload GApps, reboot to recovery, sideload Magisk, reboot to system), and all data was completely intact through this process.
Click to expand...
Click to collapse
It's true that I sideloaded Magisk without rebooting first. I'll have to try that next year! Thank you!

osetiopica said:
Hi. It works almost fine, but I can't connect to the cellular network and when I make a call it tells me to turn off airplane mode. Of course not in airplane mode. Any workaround?
Click to expand...
Click to collapse
I had the same problem when I upgraded from los18 to los19, and after I upgraded to los20 this remains the same. No idea what had happened. It's in2010 I'm using.

jabashque said:
Telegram Chat:​I have a Telegram group that you can join if you prefer to chat that way, as opposed to posting on a forum thread. Join here.
Supported models:​The only officially supported models are the following:
IN2010 (China)
IN2011 (India)
IN2013 (Europe/Asia)
IN2015 ("Global"/NA)
IN2017 (T-Mobile) is unofficially supported, as that's what I did my device bringup against.
IN2019 (Verizon) is not supported. VZW sensor configs are not bundled in this ROM, so accelerometer/gyroscope and magnetometer readings are going to be incorrect. In addition, battery gauge reading seems to be broken, based on one user trying this ROM on their IN2019 despite it being unsupported. I am likely not going to fix this anytime soon, as I do not have an IN2019 to validate my fixes against.
Upgrading from LineageOS 19.1:​If you are coming from LineageOS 19.1 AND using LineageOS 19.1 Recovery, then follow the instructions here to upgrade. Remember to flash Android 13 GApps if you used GApps previously.
We ship the required firmware (OxygenOS 13 11.F.13 as of 2022-12-31) in our OTA zips, so you do not need to install that firmware to both your slots on your OnePlus 8 before proceeding through the instructions.
Installing LineageOS 20 for the first time:​Prerequisites:​Ensure you've installed any version of OxygenOS/ColorOS 12 or 13 on the active slot on your device. The installation instructions recommend you be on OOS/COS 13 because on OOS/COS 12, touchscreen will end up not working while in LineageOS Recovery. However, you can still proceed while using OOS/COS 12 firmware; use the volume keys + power button to navigate recovery.
Instructions:​Once you satisfy the prerequisites above, then follow the instructions here to install LineageOS 20.
We ship the required firmware (OxygenOS 13 11.F.13 as of 2022-12-31) in our OTA zips, so you do not need to install that firmware to both your slots on your OnePlus 8 before proceeding through the instructions.
Click to expand...
Click to collapse
Hello I'm new to this community. I want to switch from a custom ROM known as evolution x to lineage os 20.
I have some questions regarding it.
Can I dirty flash it?
Can I do it without twrp recovery?
Also I want to flash a custom Kernal to fix the performance dip when I flashed this rom. The multicore performance of my OnePlus 8 dropped from 3065 points to 1754 (geekbench 5).
Please someone help me

Flap2004 said:
Hello I'm new to this community. I want to switch from a custom ROM known as evolution x to lineage os 20.
I have some questions regarding it.
Can I dirty flash it?
Can I do it without twrp recovery?
Also I want to flash a custom Kernal to fix the performance dip when I flashed this rom. The multicore performance of my OnePlus 8 dropped from 3065 points to 1754 (geekbench 5).
Please someone help me
Click to expand...
Click to collapse
I am completely void in knowledge on kernels, however I do know that you do not want to simply dirtyflash off of a seperate custom ROM. You should backup all of your data, and then follow the steps to factory reset and flash. I am also not 100% on this, but I do not think that TWRP even works on this version of android, and regardless you are provided with a custom recovery to flash everything necessary.

[LineageOS 20] (Android 13) GSI Install Instructions

Hi all,
i was kinda bored and sick of no Custom ROM development for our beloved S6 so i thought i'd try using a GSI and i've got it booting so i thought i would share the instructions!
As usual all care no responsibility! Nothing here is without risk.
Android 13
5 March 2023 Security Patch Level
1. Unlock your bootloader. (Very easy to do - https://www.hardreset.info/devices/...-s6/faq/bootloader-unlock/samsung-bootloader/)
2. Download the official vbmeta image provided by TWRP > https://dl.twrp.me/gts4lv/vbmeta.tar.html
3. Download TWRP https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
4. Open Odin
5. Put VBMETA.TAR in the CP Slot & TWRP in AP slot and flash. On reboot hold down the Pwr/Up button so it boots straight into TWRP or sometimes it can be overwritten.
3. Format Data, reboot back into TWRP and Full Factory Reset . (Take a backup if you need one).
4. Transfer the LoS image file to the tablet via TWRP then Flash the LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
(might need to use the adb push command to copy the file across) adb push filename.extension /sdcard
5. Flash magisk if you like.
6. Reboot to system and enjoy!
i used the one above which includes GAPPS though there are ones that don't if you prefer
I only just finished installing though - quick summary:
Working:
Fingerprint!
Hardware Buttons
SDCard
Wifi
Bluetooth
Gapps and Google Setup
Tablet is very fast!
Charging
USB File Transfer
Audio
Video out for USB-C
Auto-rotate
GPS
Official Samsung Keyboard Physically attached working fine too!
Themes
Colours
Mic
SPen
Not Working:
Only bottom speakers work
SafetyNet
Workarounds:
To pass SafetyNet (BASIC):
Flash Magisk in TWRP
Use Magiskhide
Turn on Zygist
Install Displax modified SafetyNet-Fix from link below;
hxxps://github.com/Displax/safetynet-fix/releases/tag/v2.4.0-MOD_1.2
Configure your Denylist in Magisk for Google Play Store and Services apps. (And anything else you need to not detect root).
To Fix Brightness:
Go to Settings - Phh - Misc Features - Tick the box for "Use Linear Brightness Slider"
To Help with Fingerprint:
Turn off taskbar in Settings to help alignment with Fingerprint scanner
Hope we can get some community effort behind this so we can bring this tablet back into support since Samsung gave up on it..
Credit to @AndyYan for the builds!
[GSI][13] LineageOS 20 TrebleDroid-based
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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...
forum.xda-developers.com

RESERVED

In my case only bottom speakers work!

Sage said:
Hi all,
i was kinda bored and sick of no Custom ROM development for our beloved S6 so i thought i'd try using a GSI and i've got it booting so i thought i would share the instructions!
5.Install LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
Click to expand...
Click to collapse
Thanks so much for this!
I have built LOS for a couple unsupported devices in the past and would love to dedicate as much time and resources as needed to this project.
Could you share which build trees were used from Github and the extracted blobs?
I would like to replicate this build and put in a request with LOS developer stinX for an official one.

tablet_seeker said:
Thanks so much for this!
I have built LOS for a couple unsupported devices in the past and would love to dedicate as much time and resources as needed to this project.
Could you share which build trees were used from Github and the extracted blobs?
I would like to replicate this build and put in a request with LOS developer stinX for an official one.
Click to expand...
Click to collapse
I am not sure mate about the GIT and Blobs. These are GSI so "generic" so they may not have them. From my understanding they work with the existing Vendor image and take advantage of Treble to ensure everything works.
The source of the files is here:
[GSI][13] LineageOS 20 TrebleDroid-based
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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...
forum.xda-developers.com

m0byn said:
In my case only bottom speakers work!
Click to expand...
Click to collapse
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.

Sage said:
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Click to expand...
Click to collapse
I should add i think this is MUCH faster than stock and battery life is looking great too!

I am happy there are some other people who are using this GSI on a Tab S6. I installed it some time ago and am very satisfied!
Some things I found:
Fingerprint XY coordinates are somehow off. Specifically, the symbol showing on screen and the actual reader are not on the same place. I think it is related to the app bar somehow, since it seems to be off by that. I think this could be fixed by an overlay.
Auto-brightntess is not available as well. Either use an app for that, or don´t use it. This can also be fixed by an overlay as far as I know.
Maybe it is also possible to get the top speakers working by making an overlay? I am not sure regarding this, however.
Obviously, DolbyAtmos is not included. However, I think there exists a Magisk Module. Maybe it would also be possible to integrate this into an overlay? This would be amazing
I am very new to the custom ROM/GSI scene. So, my experience with overlays and so on is basically none. However, I would try to contribute as good as I can if someone feels ready to create an overlay and then getting it implemented into the GSI.
Anyone interested in cooperating?

Sage said:
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Click to expand...
Click to collapse
I will try to do that as well...lets see.
I would explicitly add to the working section that the spen works and also pressure sensitivity of the spen works! At least in the Saber Handwritten Notes app which I use. This is amazing.

Sage said:
1. Unlock your bootloader. (Very easy to do - https://www.hardreset.info/devices/...-s6/faq/bootloader-unlock/samsung-bootloader/)
2. Install TWRP via Odin https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
3. Full wipe thru TWRP. Including format data. (Take a backup if you need one).
4. Reboot back to TWRP.
5.Install LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
6. Boot and enjoy!
Click to expand...
Click to collapse
Didn`t you patch the vbmeta.img, or did you flash the multidisabler zip?
Somehow, one has to disable verified boot such that you can even boot LineageOS...as far as I know!

m0byn said:
Didn`t you patch the vbmeta.img, or did you flash the multidisabler zip?
Somehow, one has to disable verified boot such that you can even boot LineageOS...as far as I know!
Click to expand...
Click to collapse
All I did was what I posted above! I'm surprised how easy it was tbh!

Sage said:
All I did was what I posted above! I'm surprised how easy it was tbh!
Click to expand...
Click to collapse
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...

m0byn said:
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
Click to expand...
Click to collapse
Nope. Started from stock. Literally unlocked bootloader right before moving to GSI. Just like the steps above.
I did install Magisk which may help disable verified boot though

Sage said:
Nope. Started from stock. Literally unlocked bootloader right before moving to GSI. Just like the steps above.
I did install Magisk which may help disable verified boot though
Click to expand...
Click to collapse
Ah, that might make the difference! So I think it is worth to mention to either install Magisk, or to patch the vbmeta.img in order to boot. If coming from stock with the stock vbmeta.img, then Android Verified Boot will not allow booting into a different ROM.

m0byn said:
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
Click to expand...
Click to collapse
OP is wrong.
Be careful flashing the latest TWRP for SMT-860 Wifi with Odin.
This happened to me today after doing it. "Error verifying vmbeta image: Invalid vmbeta header"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The device gets stuck like this and won't boot anymore, but you can get it back to normal by flashing the recovery.img from your firmware files (It's in AP)
You cannot install TWRP on the Galaxy Tab S6 without fixing the vmbeta.img issue.
I tried with the latest Samsung firmware downloaded via SamFirm and an older one.
@m0byn: Do you know what needs to be done with the vmbeta.img on this device, to allow for TWRP to be flashed?
I have found many different prescribed solutions such as patching boot.img with Magisk or just the vmbeta.img , but nothing seems to work.

Tablet, search my post here https://forum.xda-developers.com/t/t865-rooting-with-android-12-bootloop-and-error.4452641/ and try

Hey man, thank you for the suggestion. That post seems to be about Magisk and rooting.
The problem here is the vmbeta.img.
According to older posts from 2021 this can be resolved by flashing vbmeta_disabled.tar , but the latest 2022 version of TWRP should no longer require this. It's weird.

I am sorry. I thought something went wrong when you patched the firmware with Magisk

Probably flashing Magisk automatically patches the vbmeta.img. Not sure though.
Follow the steps below. This is how I did it. It worked.
I am assuming a stock recovery in this process. If you already installed TWRP just try if it works as well. not sure if this is impacting the process.
Unpack firmware using 7Zip tool
Unpack AP.tar.md5 using 7Zip tool
Unpack vbmeta.img.lz4 using 7Zip-ZS tool
Open file in FrhedPortable (HEX editor) to patch it
Go to offset (block) 123 and write 03 and save
Compress vbmeta.img to vbmeta.img.tar using 7Zip tool
Connect device via USB to computer
Hold volume up & volume down buttons
Press volume up button to proceed to download mode
Open Odin -> verify whether device number is added
Untoggle "auto-reboot" in options
Select AP section
Choose patched vbmeta.img.tar file
Click start to flash
When flashing process is done: hold power & volume down button to exit and power off device
IMPORTANT: as soon as device shuts off immediately release volume down button and press volume up button to enter recovery mode
Click factory reset
Click reboot to bootloader

Thanks @m0byn I managed to figure it out with your help.
For anyone else facing the same problem, here is what you need to do:
Download the official vbmeta image provided by TWRP > https://dl.twrp.me/gts4lv/vbmeta.tar.html
Proceed to flash with Odin.
Put the TWRP recovery image in AP and vbmeta.tar in the CP slot.
After this you can boot into the TWRP recovery normally, but for some reason any changed settings in TWRP are not saved. So everytime I reboot into TWRP recovery all previously selected TWRP settings are lost. I wonder if that's normal, but everything else seems to work.
Next step will be flashing the Lineage GSI, i'll keep you guys posted.