{
"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?
Related
{
"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 9 (Pie), 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 :
You tell me
Instructions :
Download the latest build, gapps and nfc fix
Reboot to recovery
Flash the latest build, gapps and nfc fix
Reboot
Downloads :
Lineage Builds : https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/P8 Lite 2017/Pie/LineageOS/
Lineage Recovery : https://sourceforge.net/projects/da...ge-16.0-20201119-recovery-prague.img/download
Nfc fix : https://sourceforge.net/projects/da.../Pie/LineageOS/Nfc Fix LineageOS.zip/download
Root addon : https://download.lineageos.org/extras
Google Apps : 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 /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
LineageOS , ROM for the Huawei P8lite/P8 Lite
Contributors
DarkJoker360
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 16.0
Stable Release Date: 2020-11-17
Created 2020-11-17
Last Updated 2020-11-20
NOTE: Those builds require Emui 8.
Installed using Pretoriano80's TWRP but the pone doesn't boot past the warning screen.
Jhon_Locke said:
Installed using Pretoriano80's TWRP but the pone doesn't boot past the warning screen.
Click to expand...
Click to collapse
Bootloops for me as well.
Installed the rom from TWRP after wiping system and formating data, to no avail.
EDIT: It finally worked for me after a couple of additional reboots, not sure why. Testing right now...
EDIT2: BLE works, even if I received a couple of error messages at the start, it managed to sync my Mi Band 3 with this ROM.
So, the steps that worked for me are:
- Install Haky86's TWRP v3.4.
- From TWRP, wipe system.
- Install Lineage OS + NFC Fix + OpenGApps v9.0 ARM64 Nano.
- Do normal wipe.
- Format /data.
- Reboot into system.
- If it reboots twice and gets into eRecovery, reboot normally again.
So, today Bluetooth Low Energy (BLE) doesn't work, I'm constantly receiving the "Bluetooth keeps stopping" error message.
Tried to reboot the phone, but it didn'help.
I will try to provide logs this afternoon after work.
Hi,
Can you help me. I've stuck on this...
Released a new update with January 2021 security pathces, fixed occasional lags/junks and properly fixed the hwc blur issue !
Hello everyone and thank you for the work you do, especially thanks to DarkJoker360 for this and the other Rom.
Can you help me please I installed the latest Rom on S2 with cyanogenmod it's been some time.
Latest Stock Rom: PRA-LX1 8.0.0.370 (C55)
I installed:
-TWRP_3.4.0-0-prague_DarkJoker360_20200801
-lineage-16.0-20210109-UNOFFICIAL-prague
-Nfc Fix LineageOS
-open_gapps-arm64-9.0-nano-20210110
After rebooting it stops on the home screen and after waiting it enters Huawei eRecovery.
I would like to install this Rom because I read that it is not possible (I have tried and confirmed) to use "sm set-force-adoptable true" in fact I get this "Error: java.lang.IllegalStateException: Adoptable storage not available on device with native FBE", this feature is only available from android 9 (https://source.android.com/security/encryption/file-based).
I would like to install apps on SD by any method (even Stock).
Can you help me solve this problem?
I uploaded some logs I don't know if they are fine.
Thanks again
Ps: sorry but I use goggle translate
Hi, are we flash LineageOS with normal TWRP, or with Lineage Recovery?
İts okay I understand
Oğuz Karagöz said:
Hi, are we flash LineageOS with normal TWRP, or with Lineage Recovery?
Click to expand...
Click to collapse
Hello
1 HAVE STOK
2 INSTALL WITH FASTBOOT lineage-16.0-20201119-recovery-prague.img
3 Wipe cache data system dalvik / art cache
4 INSTALL WITH FASTBOOT TWRP 3.2.1-0_Dil3mm 4
5 TWRP INSTALL lineage-16.0-20210109-UNOFFICIAL-prague
6 without exiting FAI -> wipe -> advanced -> system -> resize (DO NOT FORMAT THIS TIME!)
7 flash Nfc fix, Root addon, Google Apps
8 reboot
Used very little just to see that it was not possible to use Adoptable storage.
Problem I solved by returning to stok with Android 7.
Bay
aragorn2931 said:
2 INSTALL WITH FASTBOOT lineage-16.0-20201119-recovery-prague.img
3 Wipe cache data system dalvik / art cache
Click to expand...
Click to collapse
hi,
are you sure for this one ?
when booting on lineage-16.0-20201119-recovery-prague.img, there is no possibility to wipe
EDIT : I finally found the options.
ask for confirmation for data and system, not for cache so I don't know if it really wiped cache.
and no option for wiping dalvik
after all that, result : I'm stuck on "your device is booting now..."
only difference, I used TWRP_3.4.0-0-prague_DarkJoker360_20200801.img instead of Dil3mm4
I also tried with dil3mm4 : same result
Hello, when I try to pair an external bluetooth device, such as a scale or a smartwatch, the device is recognized by the mobile phone but I cannot pair it
the message "the bluetooth app keeps interrupting" appears
the bluetooth headphones are paired correctly
how could i solve?
does anyone notice that theyre phone starting to get rlly hot after flashin this rom?
Everywhere I go said:
does anyone notice that theyre phone starting to get rlly hot after flashin this rom?
Click to expand...
Click to collapse
yes , my phone was burn. now it's ok
I think this is magisk problem.
disable the magiskhide & re-enable it.
Magiskd high CPU usage. · Issue #1279 · topjohnwu/Magisk
Magiskd is keeping the CPU running high all the time till I disable the magiskhide & re-enable it. Lineage OS 16.0 here, using Magisk canary 19.0. Its observed since 18.0 till latest build. Log her...
github.com
Is it possiible to fix to ise netflix? I had magisk root hide saftynet passes every thing is ok even serticified on play store i can download netflix login but cant watch anything.
Just a noob question
Why is the nfc fix not integrated in the rom
And why is system partition set so small I have to resize system partition or use gapp nano.
Also I am unable to boot this rom, keep saying
your device has been unlocked and can't be trusted
it does not boot custom rom.
B3rtm3n said:
Just a noob question
Why is the nfc fix not integrated in the rom
Click to expand...
Click to collapse
It was before and it still is, but since latest LineageOS updates I wasn't able to get this working anymore.
It can be turned on/off but it's not really working without the fix zip, even if files are the same included.
ok thx a lot for your answers, it has been quiet some years I flashed a smartphone and things have changed.
I have 3 more questions
1) I noticed that not only twrp made specially for the hardeware specs is needed nowadays but also adapted for each rom, is this correct?
2) do I need to be root to install a customs rom on a p8 lite 2017 or is bootloader unlocked enough?
3) does lineage recovery replaces twrp ? and if yes, how do I install it.
Ok found already that root is not needed.
I have a huge problem with resizing system partition, unable to have it resized using twrp. According to another dude I found on Youtube this can happen so I need another version of twrp.
I am using this one
Huawei P8 Lite 2017
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
and resizing does not work so each rom I flash has a too small system partition.
Is there another good twrp I could use?
B3rtm3n said:
ok thx a lot for your answers, it has been quiet some years I flashed a smartphone and things have changed.
I have 3 more questions
1) I noticed that not only twrp made specially for the hardeware specs is needed nowadays but also adapted for each rom, is this correct?
2) do I need to be root to install a customs rom on a p8 lite 2017 or is bootloader unlocked enough?
3) does lineage recovery replaces twrp ? and if yes, how do I install it.
Ok found already that root is not needed.
I have a huge problem with resizing system partition, unable to have it resized using twrp. According to another dude I found on Youtube this can happen so I need another version of twrp.
I am using this one
Huawei P8 Lite 2017
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
and resizing does not work so each rom I flash has a too small system partition.
Is there another good twrp I could use?
Click to expand...
Click to collapse
Download TWRP for prague
Download TWRP Open Recovery for prague
dl.twrp.me
this is good one
will therre be a lineage 17?
{
"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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest recovery image and rom zip
Boot to bootloader
fastboot flash recovery lineage-recovery.img
Boot to recovery
Format data
Sideload LineageOS zip
Optionally flash any addons:
Advanced > Reboot to recovery
Sideload the addons
Reboot
See https://wiki.lineageos.org/devices/obiwan/install for more detailed instructions
Downloads :
Official buids
Archived unofficial builds: sourceforge
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
Downgrading to an Android 10 based rom (stock included) might not work. To be safe backup persist.img to restore when downgrading.
Depending on your carrier, you may need to force a 4G/5G-only connection for VoLTE to register (from the *#*#4636#*#* menu for example)
(minor) Touchscreen may fail to initialize in Lineage Recovery
How do i...
Change the screen refresh rate?
Settings > Display > Advanced > Minimum refresh rate
Contributors
luca020400
aleasto
OrdenKrieger
The LineageOS Team
Source Code: https://github.com/LineageOS
ROM OS Version: Android 11
These builds will include a frankensteined VNDK 29-30 vendor until we get stock Android 11
You can dirty flash over my UNOFFICIAL Lineage 17.1 builds
Please fix VOLTE properly.
aleasto 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.
Instructions :
Update to the latest stock rom
Download the latest recovery image and rom zip
Boot to fastboot
Flash recovery
Boot to recovery
Format data
Flash the latest build
Optionally, reboot to recovery and flash any addons
Reboot
Downloads :
Builds: Google drive folder
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
Fingerprint sensor is not working
(minor) Touchscreen may fail to initialize in Lineage Recovery
How do i...
Change the screen refresh rate?
Drop down the notification shade
Tap the Pencil icon to edit Quick Settings
Scroll to the bottom.
Drag the Refresh rate tile to the top
Make VoLTE work?
This device seems to fail to register to VoLTE unless you force a 4G or 5G only connection.
To workaround that:
Navigate to your SIM options
Advanced
Preferred network type
Select "4G only (enables VoLTE)" or "5G/4G only (enables VoLTE)"
Contributors
luca020400
aleasto
OdenKrieger
The LineageOS Team
Source Code: https://github.com/LineageOS
ROM OS Version: Android 11
Click to expand...
Click to collapse
Thank you very much for your efforts,bro.
one question please, if i have a custom TWRP, do i still need to flash this lineage recovery img before flashing the rom ?
amr elfiky said:
Thank you very much for your efforts,bro.
one question please, if i have a custom TWRP, do i still need to flash this lineage recovery img before flashing the rom ?
Click to expand...
Click to collapse
TWRP should work but I cannot guarantee it does and will (and that's one of the main reasons Lineage makes its own recovery)
amr elfiky said:
Thank you very much for your efforts,bro.
one question please, if i have a custom TWRP, do i still need to flash this lineage recovery img before flashing the rom ?
Click to expand...
Click to collapse
No, TWRP works just fine.
bs3pro said:
You should fix VOLTE properly.
Click to expand...
Click to collapse
aleasto said:
TWRP should work but I cannot guarantee it does and will (and that's one of the main reasons Lineage makes its own recovery)
Click to expand...
Click to collapse
Does the rom already have Gapps.
[email protected] said:
Does the rom already have Gapps.
Click to expand...
Click to collapse
It doesn't. I currently suggest trying NikGapps "core". Opengapps test builds for 11 are very broken still.
bs3pro said:
You should fix VOLTE properly.
Click to expand...
Click to collapse
?
Hi
Will apps like Gpay and other banking apps work after installing this rom?
Thanks for your efforts
darudedudedocta said:
Hi
Will apps like Gpay and other banking apps work after installing this rom?
Thanks for your efforts
Click to expand...
Click to collapse
Gpay, NO.
After trying lineage os 17.1 and omnirom I installed this ROM and have decided to stay on it. ROM is smooth and don't have much issues. Minor issue noted is lack of haptic feedback on navigation gestures. Just for the sake of reporting geekbench scores (950/2850) seems to be bit low than stock, while los 17.1 and omni had stock scores(970/3300).
Thanks a lot aleasto for all the hard work and providing us with android 11 early.
Also would like to ask - Is there a way to hide the status bar in android 11? Earlier on android 10 it was very easy to do with adb commands, seems these commands were removed it android 11.
bs3pro said:
Please fix VOLTE properly.
Click to expand...
Click to collapse
hi rich
@aleasto Ran into a major problem, Need your help. So after trying 18.1 for sometime decided to go back to 17.1. So flashed Asus raw firmware to return firmware to stock before flashing 17.1 again. But the phone got stuck in bootloop, tried several versions of raw firmware , all flashed fine but was stuck on bootloop. Was able to get to recovery so tried 17.1 and omni too only to bootloop. After this was able to boot again by flashing 18.1 .
The problem is now only 18.1 ROM works on my ww rog3 , all other ROMs are bootlooping even flashing the Asus raw firmware is resulting in bootloop.
please advice. Is 18.1 making any change to partitions? Even if it does flashing raw firmware must restore it right?
tuxing said:
@aleasto Ran into a major problem, Need your help. So after trying 18.1 for sometime decided to go back to 17.1. So flashed Asus raw firmware to return firmware to stock before flashing 17.1 again. But the phone got stuck in bootloop, tried several versions of raw firmware , all flashed fine but was stuck on bootloop. Was able to get to recovery so tried 17.1 and omni too only to bootloop. After this was able to boot again by flashing 18.1 .
The problem is now only 18.1 ROM works on my ww rog3 , all other ROMs are bootlooping even flashing the Asus raw firmware is resulting in bootloop.
please advice. Is 18.1 making any change to partitions? Even if it does flashing raw firmware must restore it right?
Click to expand...
Click to collapse
"bootloop" means you get boot animation?
Are you even formatting data?
Hi guys does the back lightning system works with this room or there's any way of making it work or install the armory crate app? Thank you
peixeskim said:
Hi guys does the back lightning system works with this room or there's any way of making it work or install the armory crate app? Thank you
Click to expand...
Click to collapse
Not currently
aleasto said:
"bootloop" means you get boot animation?
Are you even formatting data?
Click to expand...
Click to collapse
The phone keeps restarting at the republic of gamers screen. If i turn it off and restart it stays at fastboot screen.
Yes before trying each ROM install, I had formatted data, Except while flashing stock raw firmware which seems to be formatting everything.
bencozzy said:
Did you have security set up like a pin code or password? Did you remove it before flashing stock firmware? Did you format data after completing the stock firmware flash in the phones recovery?
Click to expand...
Click to collapse
No security (pin or password) was setup. Yes tried formating data from stock recovery after flashing stock raw firmware from PC. But didn't help.
{
"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?
{
"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!
{
"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, 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Information
This ROM uses source built kernel, kernel modules, and vendor image.
This ROM bundles the latest firmware so you don't have to worry about updating firmware.
To use the eSIM you need to have GApps
Instructions
Follow https://wiki.lineageos.org/devices/lynx/install for how to install
Downloads
Official Builds
Optional GApps: MindTheGapps
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/*
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
Face Unlock, because Google doesn't provide an AOSP option.
Contributors
mikeioannina
nicknitewolf
The LineageOS team
Source Code: https://github.com/LineageOS
Great
Great. Thanks. Just got my Pixel 7a today.
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
sumdewd01 said:
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
Click to expand...
Click to collapse
Does the Play Store icon exist?
The GApps package may just install Play Services and the Play Store, from which you can install all optional Google apps.
Such packages avoid installing these apps as system apps, since you wouldn't be able to uninstall them without root.
sumdewd01 said:
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
Click to expand...
Click to collapse
You have to reboot to recovery again for it to install on the correct slot
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Optimissimus99 said:
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Click to expand...
Click to collapse
Hmm I guess the issue is with the partition system on our Pixel 7A so has nothing to do with the A/B partitions but the Pixel 7A uses special partitions for Boot and recovery etc, so I guess that the gapps packages can not detect/handle those partitions and therfor it does not work.
I recognized that when I wanted to flash Magisk, it shows as successfull but was not installed.
So I had to patch the init_boot file and flash that to the init_boot partition so I assume something like that applies for Gapps as well!
This was the issue I had. I tried multiple times and combinations to reflash and reboot, and reboot to recovery while in recovery and I eventually gave up and went back to stock. No Google icons of any sort and it would always say it installed fine.
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
treblechet said:
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
Click to expand...
Click to collapse
You can install Aurora Store and login there with your Google account.
treblechet said:
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
Click to expand...
Click to collapse
sumdewd01 said:
This was the issue I had. I tried multiple times and combinations to reflash and reboot, and reboot to recovery while in recovery and I eventually gave up and went back to stock. No Google icons of any sort and it would always say it installed fine.
Click to expand...
Click to collapse
Wishmasterflo said:
Hmm I guess the issue is with the partition system on our Pixel 7A so has nothing to do with the A/B partitions but the Pixel 7A uses special partitions for Boot and recovery etc, so I guess that the gapps packages can not detect/handle those partitions and therfor it does not work.
I recognized that when I wanted to flash Magisk, it shows as successfull but was not installed.
So I had to patch the init_boot file and flash that to the init_boot partition so I assume something like that applies for Gapps as well!
Click to expand...
Click to collapse
Optimissimus99 said:
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Click to expand...
Click to collapse
Pulled old builds and uploaded new ones. Something went wrong with my build configuration which prevented gapps install. Please use the new pre-install steps and images too
Great work @nicknitewolf .. can i wonder what are the main things needed to clear the road for official LineageOS status? Is it that you're not really in the LineageOS community and expect @mikeioannina (who has official builds for most of the Pixel devices) to eventually do it? Or is it that there's specific issues or things that don't conform well. Either way, maybe mike has any idea if the 7a will get official support any time soon..
I will put this on a family member's new Pixel 7a, and maybe leave some feedback, but i still prefer official
mxz55 said:
Great work @nicknitewolf .. can i wonder what are the main things needed to clear the road for official LineageOS status? Is it that you're not really in the LineageOS community and expect @mikeioannina (who has official builds for most of the Pixel devices) to eventually do it? Or is it that there's specific issues or things that don't conform well. Either way, maybe mike has any idea if the 7a will get official support any time soon..
I will put this on a family member's new Pixel 7a, and maybe leave some feedback, but i still prefer official
Click to expand...
Click to collapse
No promises but we are waiting for June ASB
nicknitewolf said:
Pulled old builds and uploaded new ones. Something went wrong with my build configuration which prevented gapps install. Please use the new pre-install steps and images too
Click to expand...
Click to collapse
This fixed it, thanks. I would like to mention that there are sone UI inconsistencies when it comes to the status bar, there's padding on one side and not the other, and when you go into the notification drawer (I think that's what it's called, swiping down from the status bar) the time and the date are not aligned by a little bit vertically. It's a small problem but still somewhat noticeable.
nicknitewolf said:
No promises but we are waiting for June ASB
Click to expand...
Click to collapse
Ok, cool.. are you working together with people from the LineageOS team?
Also, since i never tried this before with any device - would it require a wipe with clean install to upgrade to official should the time come? Or it's likely to be compatible?
mxz55 said:
Ok, cool.. are you working together with people from the LineageOS team?
Also, since i never tried this before with any device - would it require a wipe with clean install to upgrade to official should the time come? Or it's likely to be compatible?
Click to expand...
Click to collapse
Yes and yes. I am already part of the LineageOS team... Current builds are signed with test keys but official builds are signed with separate keys, hence a full wipe is required. You could try the zip attached but I doubt it works (since I don't really wanna test it).
nicknitewolf said:
Reboot into fastboot (With the device powered off, hold Volume Down + Power)
Flash
Click to expand...
Click to collapse
Just wanna say it should be "Reboot into bootloader", as the bootloader type of fastboot is required to flash some of the images: the dtbo, vendor_boot and vendor_kernel_boot partitions can't be read by pure fastboot (what's usually called fastbootD) mode and will throw this sort of error:
Warning: skip copying .. name .. image avb footer (.. name .. partition size: 0, .. name .. image size: .. ).
Sending '.. name ..' (... KB) OKAY [ 0.404s]
Writing '.. name ..' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Click to expand...
Click to collapse
So anyone that got confused should just use `adb reboot bootloader` instead of reboot fastboot
I've flashed the ROM and so far it looks & feels really smooth, thanks!
Currently using GrapheneOS. Will flash LOS once they release a user build with release keys.