[ROM][OFFICIAL] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos

Search This thread
Dec 19, 2012
28
19
San Jose
First off, thank you for the great work on this ROM! @Linux4

I am here to report an issue and get some advice/ help to unbrick or recover by decrypting /data of my S10e.

TLDR; upgrade to LOS18.1 official 20220127 (from 20211216) w/ Magisk v24.1 is causing bootloop.

Details:
Code:
What is your--
LineageOS version: lineage-18.1-20220127-nightly-beyond0lte-signed.zip
LineageOS Download url: https://mirrorbits.lineageos.org/full/beyond0lte/20220127/lineage-18.1-20220127-nightly-beyond0lte-signed.zip
Gapps version: Unsure (I think I had the latest since this isn't fresh install)

Did you--
wipe: No
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: Magisk v24.1 (w/ Zygisk enabled) and installed safetynet-fix-v2.2.1 (https://github.com/kdrag0n/safetynet-fix/)

Steps that landed me in this mess:
  • The phone was initially on official LOS18.1 20211216. OTA upgrade to official LOS18.1 20220127.
  • Flashed Magisk v23.0 through adb sideload. Installation was successful, but upon boot Magisk app doesn't see Magisk was installed.
  • Downloaded 20220127 recovery + ROM from https://download.lineageos.org/beyond0lte, rebooted to recovery and then to fastboot mode and installed recovery, reboot again to recovery (verified version string is correct on screen), then adb sideload 20220127 ROM.
  • adb sideload Magisk v24.1
  • Reboot successful, Magisk app sees Magisk installation. Learned this version uses Zygisk, so enabled that option for MagiskHide. Also learned there's no module repo, so downloaded safetynet-fix-v2.2.1 (https://github.com/kdrag0n/safetynet-fix/) and installed through app UI and issued a reboot.
  • Bootloop

What I've tried:
  • Format Cache and System through LOS recovery.
  • Reinstall 20220127 recovery + ROM + boot.img (from the ROM zip explicitly from fastboot)
  • mount /data and move /data/adb folder so that Magisk modules won't load (as an extra measure since original boot.img doesn't have Magisk anyways to load).
  • mount /data and move /data/dalvik-cache since the LOS recovery doesn't have dalvik-cache wipe option.

Logs that are pulled after RescueParty triggered recovery boot after the above mitigation steps:
  • dmesg.txt (probably useless?)
  • last_kmsg.txt (/proc/last_kmsg)
  • recovery_last_log.txt (/cache/recovery/last_log)
  • recovery_last_kmsg.txt (/cache/recovery/last_kmsg)

Things I've noticed:
  • /data seems intact, unable to chkdsk since e2fsck is missing in /bin (as noted in logs).
  • adb logcat/ wait-for-device never connects even after putting back /data/adb folder (unable to start system?).
  • Flashing Magisk v23.0 with latest recovery also didn't work.
  • Various ro.boottime.init.* prop weren't set because readonly property was already set.
Any help is appreciated!
 

Attachments

  • logs.zip
    496.1 KB · Views: 4
Last edited:
Dec 19, 2012
28
19
San Jose
Hello again! I've been reading up on FBE and going through kmsg log file and learned that there's metadata partition. Unsure if our S10 devices have it since we didn't launch with Android 11 and no entry in fstab.

kmsg log notes:
Code:
selinux:
<14>[    2.192837]  [7:           init:    1] init: Running restorecon...
<11>[    2.195864]  [7:           init:    1] selinux: SELinux: Could not get canonical path for /metadata/ota/rollback-indicator restorecon: No such file or directory.
<11>[    2.195873]  [7:           init:    1] selinux:
<11>[    2.195883]  [7:           init:    1] selinux: SELinux: Could not get canonical path for /metadata/gsi restorecon: No such file or directory.
<11>[    2.195888]  [7:           init:    1] selinux:

The actual SIGTERM triggering recovery:
Code:
<14>[  102.511718]  [5:           init: 3888] init: Received sys.powerctl='reboot,recovery' from pid: 9667 (system_server)
<14>[  102.513412]  [5:           init:    1] init: Clear action queue and start shutdown trigger
<14>[  102.513450]  [5:           init:    1] init: Entering shutdown mode
<14>[  102.513603]  [5:           init:    1] init: processing action (shutdown_done) from (<Builtin Action>:0)
<14>[  102.513628]  [5:           init:    1] init: Reboot start, reason: reboot,recovery, reboot_target: recovery
<14>[  102.513642]  [5:           init:    1] init: Shutdown timeout: 6000 ms
<14>[  102.513648]  [5:           init:    1] init: Create reboot monitor thread.
<14>[  102.514265]  [5:           init: 9732] init: shutdown_timeout_timespec.tv_sec: 408
<11>[  102.519584]  [4:           init:    1] init: Could not open '/metadata/bootstat/persist.sys.boot.reason' to persist reboot reason: No such file or directory
<14>[  102.520155]  [4:           init:    1] init: starting service 'blank_screen'...
<14>[  102.521780]  [5:           init:    1] init: Stopping 107 services by sending SIGTERM
<14>[  102.521833]  [5:           init:    1] init: Sending signal 15 to service 'setup-bcb' (pid 9705) process group...
<14>[  102.522229]  [5:           init:    1] init: Sending signal 15 to service 'wificond' (pid 9608) process group...
<14>[  102.522528]  [3:           init:    1] init: Sending signal 15 to service 'netd' (pid 9606) process group...
<14>[  102.523079]  [1:           init:    1] init: Sending signal 15 to service 'media' (pid 9605) process group...
<14>[  102.525141]  [3:           init:    1] init: Sending signal 15 to service 'vendor.audio-hal' (pid 9604) process group...
<14>[  102.525776]  [3:           init:    1] init: Sending signal 15 to service 'cameraserver' (pid 9603) process group...
<14>[  102.529307]  [3:           init:    1] init: Sending signal 15 to service 'audioserver' (pid 9602) process group...
<3>[  102.530108]  [2:     android.ui: 9685] binder_alloc: 9603: binder_alloc_buf, no vma
<6>[  102.530126]  [2:     android.ui: 9685] binder: 9667:9685(system_server:android.ui) transaction failed 29189/-3, size 80-0 line 3385
<14>[  102.532088]  [5:           init:    1] init: Sending signal 15 to service 'zygote_secondary' (pid 9601) process group...
<14>[  102.532430]  [5:           init:    1] init: Sending signal 15 to service 'zygote' (pid 9600) process group...
<14>[  102.533357]  [1:           init:    1] init: Sending signal 15 to service 'bootanim' (pid 5821) process group...
<14>[  102.534068]  [5:           init:    1] init: Sending signal 15 to service 'vendor.fps_hal' (pid 5717) process group...
<14>[  102.538616]  [2:           init:    1] init: Sending signal 15 to service 'gatekeeperd' (pid 5709) process group...
<6>[  102.538655]  [0:[email protected]: 5534] panel_bl_set_brightness bl-0 dim:flash plat_br:0 br[0]:0 nit:2(2.00) acl:on(5)
<14>[  102.539245]  [5:           init:    1] init: Sending signal 15 to service 'media.swcodec' (pid 5708) process group...
<6>[  102.539386]  [3:panel-bl-thread: 3139] [SSP] panel_notifier_callback PANEL_EVENT_BL_CHANGED 0 9809
<14>[  102.541917]  [3:           init:    1] init: Sending signal 15 to service 'sec_gnss_service' (pid 5700) process group...
<14>[  102.542564]  [7:           init:    1] init: Sending signal 15 to service 'ril-daemon1' (pid 5697) process group...
<14>[  102.543490]  [3:           init:    1] init: Sending signal 15 to service 'ril-daemon' (pid 5695) process group...
<14>[  102.544091]  [3:           init:    1] init: Sending signal 15 to service 'gpsd' (pid 5694) process group...
<6>[  102.544600]  [4:           SINR: 5796] drb: misc_poll: poll done by SINR (0)
<14>[  102.544946]  [0:           init:    1] init: Sending signal 15 to service 'lhd' (pid 5691) process group...
<14>[  102.546000]  [5:           init:    1] init: Sending signal 15 to service 'cpboot-daemon' (pid 5690) process group...

Could anyone post:
  • List of partitions by running this command through adb shell? The 13d60000 could be differrent in your phone:
    Code:
    beyond0lte:/ # ls -alh /dev/block/platform/13d60000.ufs/by-name/total 0
    drwxr-xr-x 2 root root 680 2022-02-02 04:02 .
    drwxr-xr-x 3 root root 800 2022-02-02 04:02 ..
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 boot -> /dev/block/sda14
    lrwxrwxrwx 1 root root  15 2022-02-02 04:02 bota0 -> /dev/block/sda1
    lrwxrwxrwx 1 root root  15 2022-02-02 04:02 bota1 -> /dev/block/sda2
    lrwxrwxrwx 1 root root  15 2022-02-02 04:02 bota2 -> /dev/block/sda8
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 bota3 -> /dev/block/sda24
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 cache -> /dev/block/sda28
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 cp_debug -> /dev/block/sda30
    lrwxrwxrwx 1 root root  15 2022-02-02 04:02 cpefs -> /dev/block/sdd1
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 dqmdbg -> /dev/block/sda22
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 dtb -> /dev/block/sda12
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 dtbo -> /dev/block/sda13
    lrwxrwxrwx 1 root root  15 2022-02-02 04:02 efs -> /dev/block/sda3
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 keydata -> /dev/block/sda21
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 keyrefuge -> /dev/block/sda20
    lrwxrwxrwx 1 root root  15 2022-02-02 04:02 keystorage -> /dev/block/sda6
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 misc -> /dev/block/sda19
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 nad_refer -> /dev/block/sda17
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 omr -> /dev/block/sda29
    lrwxrwxrwx 1 root root  15 2022-02-02 04:02 param -> /dev/block/sda4
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 persistent -> /dev/block/sda18
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 product -> /dev/block/sda27
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 radio -> /dev/block/sda16
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 recovery -> /dev/block/sda15
    lrwxrwxrwx 1 root root  15 2022-02-02 04:02 sec_efs -> /dev/block/sda7
    lrwxrwxrwx 1 root root  15 2022-02-02 04:02 steady -> /dev/block/sda9
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 system -> /dev/block/sda25
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 uh -> /dev/block/sda10
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 uhcfg -> /dev/block/sda11
    lrwxrwxrwx 1 root root  15 2022-02-02 04:02 up_param -> /dev/block/sda5
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 userdata -> /dev/block/sda31
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 vbmeta -> /dev/block/sda23
    lrwxrwxrwx 1 root root  16 2022-02-02 04:02 vendor -> /dev/block/sda26
  • kmsg by running the below after reboot device twice (so that the kmsg is clean):
    Code:
    adb shell cat /proc/last_kmsg > last_kmsg.txt
I am hoping to check if I still got all the partitions and how my kmsg differs from a successful boot. Thanks! 🙏
 
Last edited:

mu1989

Senior Member
Feb 22, 2020
118
47
First off, thank you for the great work on this ROM! @Linux4

I am here to report an issue and get some advice/ help to unbrick or recover by decrypting /data of my S10e.

TLDR; upgrade to LOS18.1 official 20220127 (from 20211216) w/ Magisk v24.1 is causing bootloop.

Details:
Code:
What is your--
LineageOS version: lineage-18.1-20220127-nightly-beyond0lte-signed.zip
LineageOS Download url: https://mirrorbits.lineageos.org/full/beyond0lte/20220127/lineage-18.1-20220127-nightly-beyond0lte-signed.zip
Gapps version: Unsure (I think I had the latest since this isn't fresh install)

Did you--
wipe: No
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: Magisk v24.1 (w/ Zygisk enabled) and installed safetynet-fix-v2.2.1 (https://github.com/kdrag0n/safetynet-fix/)

Steps that landed me in this mess:
  • The phone was initially on official LOS18.1 20211216. OTA upgrade to official LOS18.1 20220127.
  • Flashed Magisk v23.0 through adb sideload. Installation was successful, but upon boot Magisk app doesn't see Magisk was installed.
  • Downloaded 20220127 recovery + ROM from https://download.lineageos.org/beyond0lte, rebooted to recovery and then to fastboot mode and installed recovery, reboot again to recovery (verified version string is correct on screen), then adb sideload 20220127 ROM.
  • adb sideload Magisk v24.1
  • Reboot successful, Magisk app sees Magisk installation. Learned this version uses Zygisk, so enabled that option for MagiskHide. Also learned there's no module repo, so downloaded safetynet-fix-v2.2.1 (https://github.com/kdrag0n/safetynet-fix/) and installed through app UI and issued a reboot.
  • Bootloop

What I've tried:
  • Format Cache and System through LOS recovery.
  • Reinstall 20220127 recovery + ROM + boot.img (from the ROM zip explicitly from fastboot)
  • mount /data and move /data/adb folder so that Magisk modules won't load (as an extra measure since original boot.img doesn't have Magisk anyways to load).
  • mount /data and move /data/dalvik-cache since the LOS recovery doesn't have dalvik-cache wipe option.

Logs that are pulled after RescueParty triggered recovery boot after the above mitigation steps:
  • dmesg.txt (probably useless?)
  • last_kmsg.txt (/proc/last_kmsg)
  • recovery_last_log.txt (/cache/recovery/last_log)
  • recovery_last_kmsg.txt (/cache/recovery/last_kmsg)

Things I've noticed:
  • /data seems intact, unable to chkdsk since e2fsck is missing in /bin (as noted in logs).
  • adb logcat/ wait-for-device never connects even after putting back /data/adb folder (unable to start system?).
  • Flashing Magisk v23.0 with latest recovery also didn't work.
  • Various ro.boottime.init.* prop weren't set because readonly property was already set.
Any help is appreciated!
oh no, not this module again xD This module is nothing but trouble



2 things:

SafetyNet (LineageOS 19.0) and zygisk

1) Enable "Zygisk" option (in Lygisk/Magisk app)
2) Reboot your device
3) Enable "Enforce DenyList" option
4) Go in "Configure DenyList"
5) Tap on the Magnifying Glass button
6) Enable "Show system apps" option then search 'Google Play Services' and tap on it (but NOT on the tick box!) to expand activities
7) Enable both "com.google.android.gms" & "com.google.android.gms.unstable"
8) install MagiskHide Props Config(Magisk module)
9) Open the terminal
10) su
11) Type "props"
12) Edit 1 fingerprint of the device
13) Choose a certified fingerprint
14) 7 Google
15) Find an Android 12 device (Pixel 5 = 26 and 2)
16) Follow the instructions
17) Restart
18) Clear Google Play Store Data
19) Check SafetyNet (should pass)
20) Open MagiskHide (Magisk -> Tap on the Shield symbol)
21) Check all apps that do not require root privileges

If you go to 18.1 you just have to use Android 11 FP


And 2nd has the linear recovery wipe cache, It's the 2nd point when you go into factory reset

I also recommend you to use this github.com/programminghoch10/Lygisk
This is a fork of magisk made for lineage restoration to make addon.d work
 
Last edited:
  • Like
Reactions: lakkimsetty.baba

Linux4

Recognized Developer
Disabling FBE (which you clearly did - see the following) is not supported - you are on your own (in the end this is what caused your issues!).

  • mount /data and move /data/adb folder so that Magisk modules won't load (as an extra measure since original boot.img doesn't have Magisk anyways to load).
  • mount /data and move /data/dalvik-cache since the LOS recovery doesn't have dalvik-cache wipe option.

  • List of partitions by running this command through adb shell? The 13d60000 could be differrent in your phone:

They will not be different in any case.
 
  • Like
Reactions: sieghartRM
Dec 19, 2012
28
19
San Jose
Hi Linux4, I didn't disable FBE, the stuff inside /data/data (and /data/adb) are all random strings as one would expect. I am not entirely sure if you meant, I disabled FBE by installing the addon?
 
Last edited:
So, I bought another S10e G970F today. I updated the stock firmware which now is up to Android 12. Can anyone confirm that LOS18.1 works on top of this? If not, I'll try myself and report back here.
[Edit: confirmed working]
I have similar case. I bought a used S10e. It is updated to Android 12 G970FXXUEGVA4.
As I didn't want to to break stuff flashing everything, I tried LineageOS 19. It basically works, but I don't get microG installed. See here. Can I just try the official LineageOS 18.1? What is the bad case scenario to expect? "Just" a none booting Android where I can still get in recovery and flash LineageOS19 again or a brick?
 

zpunout

Senior Member
Aug 26, 2015
225
39
Samsung Galaxy S5
Moto G5 Plus
I have similar case. I bought a used S10e. It is updated to Android 12 G970FXXUEGVA4.
As I didn't want to to break stuff flashing everything, I tried LineageOS 19. It basically works, but I don't get microG installed. See here. Can I just try the official LineageOS 18.1? What is the bad case scenario to expect? "Just" a none booting Android where I can still get in recovery and flash LineageOS19 again or a brick?
It works fine, but remember there is no VoLTE connectivity solution yet for any custom OS.
 
  • Like
Reactions: Yokurt815
It works fine, but remember there is no VoLTE connectivity solution yet for any custom OS.
Thanks. Yes, I read the no VoLTE part. But I think I can live with it. I flashed lineage-18.1-20220116-microG-beyond0lte recovery and rom + lygisk v13.015. Start works and microG self test looks good. I'll set up the rest now and take it into use :)
 
  • Like
Reactions: zpunout

woaloo

Retired Forum Moderator
Jun 23, 2006
455
46
Fairphone
Samsung Galaxy S10e
Hi,
I upgrade to magisk V24.1 and get my first update of lineageOS yesterday. At the end of update, I reboot system once and then want to reboot in recovery to install Magisk. There was no option with power menu to boot in recovery. Only restart or shutdown. I shut down, restart with power and vol +, no result. No recovery anymore. I also tried with magisk, but failed, too.I did not try with adb yet (no pc for the moment ) .
Is there another solution?
Thanks for your answer

UPDATE : Finally, I found a PC, run adb and manage to boot in recovery. Magisk is now installed, I can boot in recovery with power button, but I don't know, what happened.
Is every LineageOS update will be similar ?
 
Last edited:
Hi,
I upgrade to magisk V24.1 and get my first update of lineageOS yesterday. At the end of update, I reboot system once and then want to reboot in recovery to install Magisk. There was no option with power menu to boot in recovery. Only restart or shutdown. I shut down, restart with power and vol +, no result. No recovery anymore. I also tried with magisk, but failed, too.I did not try with adb yet (no pc for the moment ) .
Is there another solution?
Thanks for your answer

UPDATE : Finally, I found a PC, run adb and manage to boot in recovery. Magisk is now installed, I can boot in recovery with power button, but I don't know, what happened.
Is every LineageOS update will be similar ?
For me it works after ones activating "System -> Gestures -> Power Menu -> Advanced restart"
I can choose "Power -> Restart -> Recovery" and it boots into recovery.

For "manually" getting in recovery, you need USB cable connected:
Recovery: Reboot and immediately hold Volume Up + Bixby + Power while the device is connected to a PC via USB cable.
See "Special boot modes": https://wiki.lineageos.org/devices/beyond0lte/
 

daoxuat

Member
May 18, 2013
39
4
Can i install this rom from stock 12 without pc? I'm so confused with whole recovery parts. Twrp already installed on my device.
 
Can i install this rom from stock 12 without pc? I'm so confused with whole recovery parts. Twrp already installed on my device.
Can you boot to recovery witout PC? I don't have a stock rom anymore, but as mentioned in the post before yours, lineage description mentions you need phone connected to PC. And I don't think stock rom has an option to reboot to recovery.

Did your recovery installation survive the boot to stock rom?
After my first recovery installation I was too slow to connect USB and press the buttons and it was overwritten by stock as mentioned in the installation instructions

If you get to custom recovery, you should be able to install the rom from sd card.

Note, that twrp is not recommended by maintainer of this rom. Better to use lineage recovery. Once you're in twrp, you should be able to update to lineage recovery. With both (twrp or lineage recvoery) you can install the rom.
 
  • Like
Reactions: daoxuat

daoxuat

Member
May 18, 2013
39
4
Can you boot to recovery witout PC? I don't have a stock rom anymore, but as mentioned in the post before yours, lineage description mentions you need phone connected to PC. And I don't think stock rom has an option to reboot to recovery.

Did your recovery installation survive the boot to stock rom?
After my first recovery installation I was too slow to connect USB and press the buttons and it was overwritten by stock as mentioned in the installation instructions

If you get to custom recovery, you should be able to install the rom from sd card.

Note, that twrp is not recommended by maintainer of this rom. Better to use lineage recovery. Once you're in twrp, you should be able to update to lineage recovery. With both (twrp or lineage recvoery) you can install the rom.
I'm able to boot to recovery just fine by plug my cable to anything other than charger. Btw, i know that i would be able to install lineage rec using twrp.
As you mentioned about sdcard, i forgot since i haven't been using cwm recovery like for years. You reminded me of the old days.
 

gandoo

Member
Aug 9, 2021
33
16
Any ETA of Android 12 going official?
Will a fresh installation be required?
I'm on microG, I'm guessing, if a fresh installation isn't required for the LOS upgrade from 11 to 12, it won't be required for microG

Thanks for your work @Linux4
 

DemotionFR

Member
Feb 8, 2021
10
2

"Hey google"feature is currently unavailable for this language.​


I installed lineage OS 18.1.

I try :

-Lineage recovery and TWRP.
-Install from SDcard and ADB Sideload.
-OpenGapps ,MindGapps ,NikGapps and FlameGapps .

Everything installs normally but I get this message in the google assistant: "Hey google" feature is currently unavailable for this language or this device .

Apart from this I was able to assign the menu button to the google assistant and it works normally...
There's just the hey google option, which is greyed out.

I'm going crazy.

Thanks for your help .

My Reddit Post Here.
 
Last edited:

Mint Julep

Senior Member
Aug 31, 2017
259
68
Hello all ! Has anybody tried this ROM on G977N ? G977N and G977B seem to be striclty the same hardware side, but I would be reassured if anybody has succesfully tried this before me
 
Last edited:

mat_pav

Senior Member
Mar 16, 2008
156
5
Hallo. I need help with Magisk. I have the version 24.2 installed but don't see the magisk-hide option under settings and because of that safetynet don't pass.
Any suggestion to resolve this issue?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 41
    1607247455067.png


    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:
    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:

    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
    7
    my safetynet fails, is there any way to make it pass? s10 exynos

    First you need to install magisk and then:


    1) Enable settings MagiskHide
    2) install MagiskHide Props Config(Magisk module)
    3) Open the terminal
    4) su
    5) Type "props"
    6) Edit 1 fingerprint of the device
    7) Choose a certified fingerprint
    8) 21 Oneplus
    9) Find an Android 11 device (OnePlus 8T global 44)
    10) Follow the instructions
    11) Restart
    12) Clear Google Play Store Data
    13) Check SafetyNet (should pass)
    14) Open MagiskHide (Magisk -> Tap on the Shield symbol)
    15) Check all apps that do not require root privileges
    5
    Any way around it? I like this rom but if updater is gonna get stuck because I'm using magisk I had to change back kraken rom 🥲 not that I prefer aoskp

    You could join the telegram group to find some early access build of some magisk fork that has addon.d working with FBE (topjohnwu is not even willing to merge an already existing fix as seen here: https://github.com/topjohnwu/Magisk/pull/3037)
    Other than that you could install magisk by just patching boot.img in the app instead of sideloading it in recovery (for now) which should make it not install addon.d.
    5
    First of all, I appreciate your work a lot. I've been waiting quite a long time for an official lineageos build for the s10, and you nailed it, you're even fixing the few bugs remained.
    Anyway, why are you saying TWRP would brick a device? I followed your suggestions of installing lineageos recovery and it works great, but I had TWRP in my previous device for about 2 years and I never had a problem

    Hi Linux4,
    Just a bit curious about you thoughts on TWRP. Indeed, it has been around for a while, has many features and is very popular, and your statement looked quite strong for me, but probably for good reasons. Is it simply not adapted to your ROM, or is it not adapted to the s10 phones, or has it gone bad generally? I am still using TWRP for all the added features that the Lineage recovery doesn't have, but will switch based on your advice.
    TWRP is way too bloated for a recovery IMO - it's more likely to break something than help you nowadays
    Especially that it's heavily touching /data isn't good on devices with FBE, like on this ROM, TWRP randomly messes up FBE policy (especially on OTAs it seems) rendering the device unbootable without wiping (which is why OP says using TWRP = data loss) which is what I referred to with (soft)"brick"
    Not to talk about that crap not even properly formatting data on standard "factory reset" which makes it not boot on this ROM.
    Also applies to other devices using FBE encryption including Tab S6 Lite and S20 series.
    Older devices that use legacy FDE instead don't seem to have similar issues afaik.

    PS: TWRP looses most of it's "features" with encrypted userdata.
    4
    I do the same with every OTA: let the system install it, seeing that it does not finish in 2-3 or so minutes, reboot (but not to recovery, just a simple reboot via holding power&vol- for >7s) - and there's the viola! A hack for sure, but it works.

    Being stuck is caused by magisk's broken addon.d just in case you wonder why it happens