Develop Bugs

[ROM][UNOFFICIAL][12.1][DISCONTINUED] LineageOS 19.1 for Galaxy S10e/S10/S10+/S10 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 12, 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 here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
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/tree/lineage-19.1

Requirements:
Any Q, R or S based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Bixby and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and Lygisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!
I also strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.

Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Known issues
VoLTE/VoWiFi
You tell me

Good job as usual!! So live display and natural (sRGB) profile doesn't work yet?

Hi @Linux4 ,
ROM boots fine, was a little put off by the change back to nice old lineage recovery style. Two issue I have encountered:
- /sdcard won't mount in recovery so I have to sideload
- I can't skip signature verification so no gapps install right now (I have tried bitGapps but to no avail either)
ROM boots unbelievably fast

Is Material You (Monet) included?

No source code? Whaat

Razuuu said:
No source code? Whaat
Click to expand...
Click to collapse
Read the posts... Bottom of first post: "Source Code: Coming soon"
Thanks a lot for your work Linux4!!

So far the Rom is really smooth and has great battery life.
Unfortunately we are getting a 403 forbidden when trying to download Gapps. Also the Rom asks to format the sdcard for some reason.
Other than that great work guys!

mike_app said:
So far the Rom is really smooth and has great battery life.
Unfortunately we are getting a 403 forbidden when trying to download Gapps. Also the Rom asks to format the sdcard for some reason.
Other than that great work guys!
Click to expand...
Click to collapse
He gave us another Gapps link.
Sdcard can't be mounted for some reason...

@Linux4 , great work, thanks a lot!
I was wondering about firmware updates. Do they come with lineageos updates or do we need to update/flash firmware still manually?

Apologies but I don't know how to do logcats, as I am new to this. However I experienced flickering once I use google maps. Also, there is this instance that the banking app I use treats the phone as emulator and not an actual device. And during login in mobile legends, gboard or the built in android aosp keyboard does not pop up whenever I try to tap the field to login my credentials.
So far, these are the things that I encountered. Other than that rom is great and smooth

mcgi5sr2 said:
Hallo @Linux4 ,
ROM bootet gut, war ein wenig abgeschreckt von dem Wechsel zurück zum netten alten Lineage Recovery-Stil. Zwei Probleme, auf die ich gestoßen bin:
- /sdcard wird bei der Wiederherstellung nicht gemountet, also muss ich seitlich laden
- Ich kann die Signaturüberprüfung nicht überspringen, daher werden derzeit keine Gapps installiert (ich habe bitGapps ausprobiert, aber auch ohne Erfolg)
ROM bootet unglaublich schnell
Click to expand...
Click to collapse
you can use the unofficial LOS18.1 recovery to install the mtg package, as well as to install magisk

does it work if i sideload magisk?

efkhai469 said:
does it work if i sideload magisk?
Click to expand...
Click to collapse
Answer at the bottom of the second post... (item number 5 + final note at the end of the post)

Hi Colleagues
everything is fine for me on this room, I don't know how to send logs, the only issue what I see just like comment.
1. Google Maps has a zoom in on A12, this also happens with other ports.
2. at least for me the audio in calls through Bluetooth, don't work it sound like a robot, in both versions, in both apps of Google Phone and on Lineage Phone app.
The rest it is working fine, just I miss advanced restart for don't make always the key combinations hehehehe.
Regards and Thanks really good job.

Thanks alot for your hard work..
Is it just me or the in-call speaker voice is so low at high-level in every AOSP rom in comparison to stock?

kachoman said:
Hi Colleagues
everything is fine for me on this room, I don't know how to send logs, the only issue what I see just like comment.
1. Google Maps has a zoom in on A12, this also happens with other ports.
2. at least for me the audio in calls through Bluetooth, don't work it sound like a robot, in both versions, in both apps of Google Phone and on Lineage Phone app.
The rest it is working fine, just I miss advanced restart for don't make always the key combinations hehehehe.
Regards and Thanks really good job.
Click to expand...
Click to collapse
Second one will be fixed later during 19.0 bringup (lineage had some patch for that which isn't in 19.0 yet)
Also advanced reboot is a lineage feature so that's why it's not there yet.
It's more or less plain AOSP at the moment

Linux4 said:
Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Known issues
VoLTE/VoWiFi
LineageOS specific features like livedisplay (for now)
You tell me
Click to expand...
Click to collapse
Another issue: the apps installed on my device can't access the phone's storage, even if I grant access to it.

ThePS4Gamer said:
Another issue: the apps installed on my device can't access the phone's storage, even if I grant access to it.
Click to expand...
Click to collapse
This isn't an issue is the consequences of the fact that selinux is enforced...

[ROM][UNOFFICIAL][12]LineageOS 19.1 for Galaxy S20/S20+/S20 Ultra 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 12, 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 here
Downloads:
Builds: https://exynoobs.github.io/OTA/
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
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
DeHuMaNiZeD
Linux4
Synt4x.93
Alastor89
Device tree and kernel source code:
Exynoobs github

Requirements:
S based firmware (OneUI4)
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk

Known issues:
VoLTE/VoWiFi
Google maps
Firmware upgrade instructions:
Get the latest firmware for your device here
Follow the provided instruction for flashing with Heimdall

Gonna try this out later. Nice!

Looks awesome!

NOTE: z3s (Galaxy s20 ultra) and y2s (galaxy s20 plus) builds are still uploading, hold tight

Nice ! Thank you so much for the great work and effort put into this
Two questions:
1. Is 5G working as it is not anymore in the "known issues" section ?
2. When using the latest S firmware is a dirty flash from LOS 18.1 possible ?
Cheers !

flunkyball said:
Nice ! Thank you so much for the great work and effort put into this
Two questions:
1. Is 5G working as it is not anymore in the "known issues" section ?
2. When using the latest S firmware is a dirty flash from LOS 18.1 possible ?
Cheers !
Click to expand...
Click to collapse
I am not sure about 5G as i only have a 4G device. Otherwise the devices are same
about 2. Dirty flashing could Theoretically work but i really cannot guarantee it. You can always try updating only the firmware for your device by going here https://github.com/Linux4/firmware-update/releases and finding your device and flashing everything with heimdall with the provided command, then try dirty flashing without wiping.

All three builds are uploaded now, enjoy!

Exelent ROM for people like me that dislike oneui and all its bloatware. Beside that this rom work so mutch better then the current oneui4 that feels slow and sluggish compared with los12.
Thanks Sent from my Nokia 3310 exynos 5g

Do anyone use lineageos rom to eyestrain but rom one ui not eyestrain ?

Impressive! Fingerprint scaner is working better then stock OneUI. Thank you!

DeHuMaNiZeD said:
Known issues:
High refresh rate
VoLTE/VoWiFi
Firmware upgrade instructions:
Get the latest firmware for your device here
Follow the provided instruction for flashing with Heimdall
Click to expand...
Click to collapse
In your personal opinion, will we ever see 120Hz working on Los for S20?

Prosafe said:
Exelent ROM for people like me that dislike oneui and all its bloatware. Beside that this rom work so mutch better then the current oneui4 that feels slow and sluggish compared with los12.
Thanks Sent from my Nokia 3310 exynos 5g
Click to expand...
Click to collapse
how about camera? quality is good? gcam compatible?

Darkstriker said:
In your personal opinion, will we ever see 120Hz working on Los for S20?
Click to expand...
Click to collapse
I cannot say.

I can confirm that 5G is NOT working on the ROM

Also, VOLTE, VOWIFI, and Google assistant responding to my voice, are all broken

Can I get the lineage os 19 rom. It says I need authorization

DeHuMaNiZeD said:
Firmware upgrade instructions:
Get the latest firmware for your device here
Follow the provided instruction for flashing with Heimdall
Click to expand...
Click to collapse
Thanks again to the team for your work.
I'm on G980FXXSCDUJ5 (S20 4G - x1s).
I was trying to upgrade to latest firmware G980FXXSCEUL9 before to load your 'lineage-19.0-20220111-UNOFFICIAL-x1s' but I have a problem.
According to me, two firmwares on your GitHub link are not corresponding to their designation:
-firmware-SM-G980F-G980FXXSCEUL9
-firmware-SM-G980F-G980FXXSCEUL7
(after download, sha256 hash controls are ok)
I've flashed these firmwares and the result for both is:
-G980FXXUCEUL6
-bootloader relocked
-On Download Mode screen, additional Japanese texts appear
I loaded back G980FXXSCDUJ5 from my datas.
Can you have a look ?
Thanks

seujo said:
Thanks again to the team for your work.
I'm on G980FXXSCDUJ5 (S20 4G - x1s).
I was trying to upgrade to latest firmware G980FXXSCEUL9 before to load your 'lineage-19.0-20220111-UNOFFICIAL-x1s' but I have a problem.
According to me, two firmwares on your GitHub link are not corresponding to their designation:
-firmware-SM-G980F-G980FXXSCEUL9
-firmware-SM-G980F-G980FXXSCEUL7
(after download, sha256 hash controls are ok)
I've flashed these firmwares and the result for both is:
-G980FXXUCEUL6
-bootloader relocked
-On Download Mode screen, additional Japanese texts appear
View attachment 5519777
I loaded back G980FXXSCDUJ5 from my datas.
Can you have a look ?
Thanks
Click to expand...
Click to collapse
Baseband version does not correspond to firmware upgrades. That means it doesnt need to be same as the firmware you flashed

[ROM][12L][OFFICIAL] crDroid 8.x FOR MOTO ONE (DEEN)

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
crdroid_features/README.mkdn at 12.1 · crdroidandroid/crdroid_features
our main features (why you love us). Contribute to crdroidandroid/crdroid_features development by creating an account on GitHub.
github.com
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
flash crDroid recovery like every other recovery on this phone
Format data
Flash the ROM zip either from adb sideload or internal storage
Reboot in to recovery
Format data
Flash GApps (If wanted)
Reboot and enjoy!
Update installation:
Reboot to recovery
Flash the ROM in twrp or use adb sideload
Reboot and enjoy!
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_motorola_deen
Download:
ROM https://crdroid.net/deen
Changelog: https://crdroid.net/deen/8#changelog
Known issues:
- Dolby broken
- Adb sideload
- Ota Update
- You tell me
Visit official website @ crDroid.net
crDroid Deen Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

20220810
- ADB: Wireless debugging: turns off frequently
- ADB: Wireless debugging: No debuggable process in Android Studio (but other devices works OK); App Inspection & Profiler not working
- ADB: Enable USB debugging -> device restarts (kernel panic?)
In the Logcat I got something like this:
Code:
I/adbd (533): opening control endpoint /dev/usb-ffs/adb/ep0
E/adbd (533): failed to write USB strings: No such device
20220807
- UPDATE: OTA: not working 20220807->20220810: Could not change profiles (https://paste.crdroid.net/J4u9b6). Is it a problem with permissions or problems caused by Magisk's changes into the system?
- UPDATE: sideload update 20220807->20220810 infinity boot loop with Magisk (without Magisk no problem)
- GAPPS: Device is not certified by Google (to solve this problem just follow: https://www.google.com/android/uncertified/)
But this ROM is still awesome! Thank you so much.

I'm trying to fix the root and debug issues

This looks awesome. I'm waiting for the new display to arrive and I'm rocking this phone back. Would this rom enable VoWifi? Or does it need certain hardware for vowifi?

Will come a Version in near future, that has no issues with OTA functionality?
Last 2 updates did not work with OTA. In Telegram Group Deen Brasil was mentioned, that a server is needed to make twpr download possible, before update is installed, cause there is no recovery patition.
Is there not way to add a recovery pation?

Hi their I was wondering when flashing this rom are these steps required? Like the pixel ROM for the Deen:
1. Download Rom
2. Download TWRP
3. fastboot getvar all
4. fastboot boot twrp
5. Do full wipe
6. Format Data
7. Flash ROM
8. Reboot to Bootloader
9. fastboot getvar all
10. If fastboot getvar all (current-slot label) from step 3 equals this from step 9 change the slot to opposite, if a then b if b then a, command is fastboot --set-active=SLOT
11. Boot to TWRP again
13. Flash Magisk (optional)
14. Reboot to system

I tried booting into recovery but i got this error
Edit : That was a long time ago.
tldr - im stupid and didnt unlock the bootloader properly.

Tobyash said:
I tried booting into recovery but i got this error View attachment 5744289
Click to expand...
Click to collapse
Looks like your bootloader is locked.

baseline2016 said:
Looks like your bootloader is locked.
Click to expand...
Click to collapse
Well thats what it seems at first look, but i have the bootloader unlocked. And i checked a few times to be sure.

Tobyash said:
Well thats what it seems at first look, but i have the bootloader unlocked. And i checked a few times to be sure.
Click to expand...
Click to collapse
Maybe you have to run the command in Windows as an administrator. And the command is fastboot boot recovery c:/....img
I followed the steps I mentioned in my post #6 and the ROM works excellent.

How do you update with twrp? It gives me error no matter what slot I choose. CrDroid recovery or OTA doesn't work.

there is a problem, the microphone is recording very low audios, with this crdroid rom.

Hello,
Gapps link is broken. I tried NikGapps but it stuck my boot...
Could you please fix the link?
Thanks in advance!
EDIT:
Found it here, just in case anyone is wondering:
Release Squeak Releases · ChonDoit/TheGappsInstaller
20220607 | Merged June changes | Unified some Overlays | Updated apns list
github.com

I just installed the latest update 2022-12-19 but unfortunately I hear an echo when I'm in a phone call.
Also echo when calling with Signal or Telegram.
Am I the only one?

whats-in-a-name said:
I just installed the latest update 2022-12-19 but unfortunately I hear an echo when I'm in a phone call.
Also echo when calling with Signal or Telegram.
Am I the only one?
Click to expand...
Click to collapse
Solved by installing stock and from there installing lineage-18.1-20220523-UNOFFICIAL-deen.zip

Hi. I'm trying to build a user version of your rom. The build works but I get an error during update (sideload). This happens at the end, after the vendor is flashed and during `Running backuptool scripts`
Code:
Update_engine_sideload [ERROR: postinstall_runner_action.cc] Failed to set backuptool context
I wonder why this could be ? Perhaps I have not reconstructed your manifest correctly?
note: I'm flashing from Recovery using a USB UTG stick and also flashing from TWRP using the same stick..

I have been using the Motorola One with this rom as my main phone for the past day or two, so far ive been enjoying it! Im hoping for more updates in the future.

Good afternoon,
I wanted to share with you my experience trying to install rom 20230414 for the Moto one tx 1941-3.
Although I was able to install and use the previous version without problems, it was impossible for me with this latest version since it stuck to the android logo. It doesn't flash or reset, it just stays there.
I find this system incredible so I would love to use the update
Thank you

[ROM][UNOFFICIAL][13.0][OTA][Signature Spoofing][Open Source][Encryption] LineageOS 20 for Galaxy S10e/S10/S10+/S10 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 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.
Instructions:
Follow the instructions here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
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/Linux4/android_kernel_samsung_exynos9820/tree/lineage-20.0

Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Bixby and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and Lygisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!
I also strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.

Features
SELinux enforcing
AES-256-XTS FBE encryption
All cameras are working
Ramdisk is working
Known issues
VoLTE/VoWiFi
You tell me
Likely more

My English is not very good, so I don't understand some things. My phone is Samsung Galaxy S10 (SM-G973F), Android 12, (HVG4). The bootloader is unlocked. I am confused by these instructions, and I would like to try this.

ZmisiS said:
My English is not very good, so I don't understand some things. My phone is Samsung Galaxy S10 (SM-G973F), Android 12, (HVG4). The bootloader is unlocked. I am confused by these instructions, and I would like to try this.
Click to expand...
Click to collapse
maybe to write what you don't understand

I don't understand:
Any Q, R or S based firmware installed on your device.
Flash lineage recovery (Get from here)
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
I also strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,

where i can find gapps 13 android?

kolyan2282 said:
where i can find gapps 13 android?
Click to expand...
Click to collapse
Google apps | LineageOS Wiki
wiki.lineageos.org

Thanks so much for working on our device, so exited to see this new version on Android on the s10, I will wait though for it to get more mature.

DOGASP said:
Google apps | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
Thanks... Should I try the one for Lineage 19? Ie (12L)?

Can few screenshots of the interface of this android?

ZmisiS said:
Can few screenshots of the interface of this android?
Click to expand...
Click to collapse
It looks mostly the same as AOSP Android 12-based ROMs.

ThePS4Gamer said:
It looks mostly the same as AOSP Android 12-based ROMs.
Click to expand...
Click to collapse
I never had AOSP installed, and I couldn't get to the images.

Has anyone installed this ROM? If it is, please write something about it for those of us who intend to install it. I hope that's not a problem?

I installed this and I need some samsung apps as well as google apps. I installed Gaaps 12.1. I don't have Google Play Store.

good morning, yes.

I reverted to stock ROM.

ZmisiS said:
I installed this and I need some samsung apps as well as google apps. I installed Gaaps 12.1. I don't have Google Play Store.
Click to expand...
Click to collapse
you can't install gaaps A12.1 on OS Android 13, i.e. you can, but it won't work, you need gaaps 13

ZmisiS said:
I installed this and I need some samsung apps as well as google apps. I installed Gaaps 12.1. I don't have Google Play Store.
Click to expand...
Click to collapse
unfortunately, you cannot have both on the AOSP system, you install gaaps for Google services, and you cannot run Samsung applications on AOSP or a pure Android system

@Linux4 will it work on G977N ?

[ROM][OFFICIAL][gts4lv|gts4lvwifi][13] LineageOS 20

{
"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 organization. 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.
Instructions :
https://wiki.lineageos.org/devices/gts4lv/install
https://wiki.lineageos.org/devices/gts4lvwifi/install
Downloads :
https://download.lineageos.org/gts4lv
https://download.lineageos.org/gts4lvwifi
GPL compliance :
https://github.com/LineageOS/android_kernel_samsung_sdm670
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)
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:

Thank you very much for LineageOS 20! Tried the upgrade from 19.1 following this guide https://wiki.lineageos.org/devices/gts4lv/upgrade (including recovery and gapps). The upgrade process went ok, Android 13 is booting up but I dont have WIFI connection. The WIFI toggle in settings is OFF, if i switch it to ON it goes back to OFF when I close settings and open them again. Will try a factory reset in the next days.

Damned! Made a mistake! I used recovery and lineageos image for the LTE variant of S5E for my update instead of the WIFI variant. Now I made a factory reset and used the correct recovery and lineageos files for installation and it looks like WIFI is working (at least in the google setup wizzard I have WIFI now). Sorry for posting nonsense!

Do I really have to update the Recovery with Odin when going from 19.1 to 20? Isnt't it included in the update-ZIP?

rogers11 said:
Do I really have to update the Recovery with Odin when going from 19.1 to 20? Isnt't it included in the update-ZIP?
Click to expand...
Click to collapse
You can always flash it from fastbootd inside lineage recovery.

LuK1337 said:
You can always flash it from fastbootd inside lineage recovery.
Click to expand...
Click to collapse
I know how to do it from bootloader on other devices like “fastboot flash recovery ./recovery.img”. But how from Recovery itself?

rogers11 said:
I know how to do it from bootloader on other devices like “fastboot flash recovery ./recovery.img”. But how from Recovery itself?
Click to expand...
Click to collapse
advanced -> enter fastboot and then it's the same as with *real fastboot*.

LuK1337 said:
advanced -> enter fastboot and then it's the same as with *real fastboot*.
Click to expand...
Click to collapse
Got it. Thanks a lot.
BTW: A happy new year.

LuK1337 said:
advanced -> enter fastboot and then it's the same as with *real fastboot*.
Click to expand...
Click to collapse
Thank you LuK1337 for lineage os 20
Upgraded with twrp wipe cache and dalvik cache
Downloaded mind the gapps 13.0 installed linage 0s 20. Installed gapps installed magisk apk wipe cache dalvik cache re booted im rooted upgraded all good
Be sending you donation shortly thanks for you hard work god bless
Happy new year from Scotland UK.

Quick question:
Can I go from 18.1 directly to 20, or should I go to 19.1 and then to 20?

What is your--
LineageOS version: lineage-20.0-20230101-nightly-gts4lvwifi-signed
LineageOS Download url: https://mirrorbits.lineageos.org/fu...e-20.0-20230101-nightly-gts4lvwifi-signed.zip
Gapps version: MindTheGapps-13.0.0-arm64-20221025_100653
Did you--
wipe: Yes
restore with titanium backup: No
reboot after having the issue: Yes
Are you using--
a task killer: No
a non-stock kernel: No
other modifications: No
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Connecting my USB-C Ethernet adapter to the tablet does not cause the tablet to use it instead of the wifi. I get a green light on the adapter for power but there is no data transfer. USB OTG Checker app recognizes the adapter as an ethernet adapter and does not detect any issue when connected. Attached is a 60 second logcat portion from when I connected the adapter.
Edit: Doesn't seem like I can attach the file to the post. Here's a link to the file

H
LuK1337 said:
advanced -> enter fastboot and then it's the same as with *real fastboot*.
Click to expand...
Click to collapse
I've updated LOS from 20230101 to 20230102 via Updater some minutes ago but the Recovery was not updated (still showing 01.01.).
"Update Recovery" is enabled in the updater's settings. Is this a bug?

BTW, if moving from 19 to 20, can you update the recovery via fastboot? I thought you could moving 18 to 19.

Mobe1969 said:
BTW, if moving from 19 to 20, can you update the recovery via fastboot? I thought you could moving 18 to 19.
Click to expand...
Click to collapse
Look here.

Hi,
first of all thanks for the port.
I did a revert to stock and then a clean install but wifi dosen't seem to work.

BlackMambo90 said:
Hi,
first of all thanks for the port.
I did a revert to stock and then a clean install but wifi dosen't seem to work.
Click to expand...
Click to collapse
Nevermind that I'm just stupid. I found out today that I have the LTE version. After using the correct package everything works fine. 🫣

Installed and working perfectly, thanks so much.

bart3005 said:
Installed and working perfectly, thanks so much.
Click to expand...
Click to collapse
same here

Good job

Can you update from 19.1 to 20 by simply side loading via Apply from ADB in recovery without doing a factory reset? I'm using the wifi version .