• We are moving to xdaforums.com!

    Posts made between now and when the migration is complete will not be carried over.
    You will be automatically redirected once the migration is complete.

[ROM][UNOFFICIAL][13.0][OTA][Signature Spoofing][Open Source][Encryption] LineageOS 20 for Galaxy S10e/S10/S10+/S10 5G Exynos

Search This thread

7hr08ik

Senior Member
Oct 8, 2011
298
115
Samsung Galaxy S10
OnePlus 9 Pro
I've been on linux4 editions since LOS18, and in previous versions linux4 has updated the Official AND the unofficial simultaneously.

From what I know the 2 are the same, except for the signing keys. So staying on the unofficial is the same as swapping over.

The only issue is a full reinstall to swap over. Then when/if LOS21 comes out.... A full reinstall to go back to unofficial (if that's your thing). I will be staying on unofficial.

Side note. There's not been any updates for a few months, but linux4 is active on the telegram group
 
  • Like
Reactions: zpunout

Nosepull

Senior Member
Jan 9, 2015
269
53
I've been on linux4 editions since LOS18, and in previous versions linux4 has updated the Official AND the unofficial simultaneously.
Thanks for the assessment. I also know from previous Linux4 ROMs that an update to" official" needs a reinstall, but the unofficial version was always still maintained for some time.
I just was wondering because in this case there seems to be no more activity on the unofficial ROM, and there is no more information by Linux4 in this forum. The fact that the ROM got official is also only discernible from looking at the LineageOS download page (which seems to be down ATM).
 

zpunout

Senior Member
Aug 26, 2015
404
93
Samsung Galaxy S5
Moto G5 Plus
[edit: issue resolved. For some reason, under USB settings, the toggle for "Convert videos to AVC" was activated. After switching it off, the issue was resolved. ]

Possible bug report for OFFICIAL LOS on G973F:

Issue: MTP not working

LOS version: 20-20230428-NIGHTLY-beyond1lte

Steps to reproduce: Connect phone to PC via USB, select "File transfer" under USB settings on the phone, use file manager to view directory structure (viewing file names and directories works), attempt to copy a file.

Result:
message on PC (Linux Mint 20.3): "libmtp error: Could not get file from device."

message on (same) PC (Windows 11): "unspecified error"

File fails to copy.

Some notes which led me to suspect a possible bug in LOS:

Issue didn't exist prior to update from LOS 19.1 official to LOS 20 official

I also have a Galaxy S10 5G G977B beyondx which has no MTP issues before and after updating to LOS20 official

Other possibilities: My G973F has recently a developed a USB hardware defect?

MTP hasn't been tested on other computers yet, but will report back when I get the opportunity to test this and see if the issue only exists on this one particular PC (Asus TUF laptop)

I searched forums about libmtp on Linux which suggested updating the libmtp package (I have version 1.1.17-3 installed), I doubt this is where the cause of the issue exists because the issue exists also in Windows and only with one of the two phones I have here.

If I find a solution, I'll post an update here.
 
Last edited:

euphore

Senior Member
Jun 16, 2017
83
19
Can anyone help me out, if I can switch from unofficial to official with the migrating script provided by lineage?

I was not able to flash the linked zip (https://blunden.se/migration), i think because I'm unable to mount /data. (ended with an error: packages.xml not found..)

I would rather run:
adb push ./lineage/scripts/key-migration/migration.sh /data/local/tmp/migration.sh
adb shell sh /data/local/tmp/migration.sh official

is this safe?

I asked allready in the telegram support group, but no one responding.

thanks!
 

Kong2000

Senior Member
Aug 15, 2012
151
43
Yes, correct for all Samsung devices running a custom OS I think. (except maybe some really old examples)
What a shame. So custom ROMs are completely useless for me. I need my phone as a hot spot and must be able to call at the same time. Without VoLTE, the phone switches to 2G while calling. Time to buy an S23. Unfortunately, it is not so small as my S10e. FE models are usually bigger than standard S models, aren't they? So no need to wait for S23 FE.
 
Last edited:

zpunout

Senior Member
Aug 26, 2015
404
93
Samsung Galaxy S5
Moto G5 Plus
What a shame. So custom ROMs are completely useless for me. I need my phone as a hot spot and must be able to call at the same time. Without VoLTE, the phone switches to 2G while calling. Time to buy an S23. Unfortunately, it is not so small as my S10e. FE models are usually bigger than standard S models, aren't they? So no need to wait for S23 FE.
There are other non Samsung phones in the official LineageOS supported devices list which support VoLTE. Or maybe try out BeyondROM for your S10e which I think does support VoLTE.
I won't talk any further about this here though as it is becoming off topic.
 
  • Like
Reactions: Kong2000

illiadin

Member
Dec 17, 2011
6
2
OnePlus 3
Samsung Galaxy S10
I have been having a weird issue with my phone screen for a while now, about 2 years ago the colors of the screen suddenly started going way off, but sometimes when i lock and re-unlock the phone it would just fix itself, then that even stopped working and now the screen colors are always off.

Funny enough by random chance i turned AOD (always on display) on my phone, and now whenever the screen colors go off i just lock the phone and wait a couple of seconds while AOD is active and magically the screen colors just return back to normal.

That being said the CPU for some reason almost never enters deep sleep when locking the phone, it always stays active at the lowest frequency which results in horrible battery life, once i turn AOD off the phone enters deep sleep normally when locked but that breaks the screen colors again, so i though maybe thats how AOD works but then i stumbled upon this https://github.com/Descendant/bug_tracker/issues/8, can the same fix be applied for this rom?
 

d3viou5

Senior Member
Jun 4, 2007
277
73
Xiaomi Mi 10 Ultra
Anyone experiencing a black screen when rotating YouTube to full screen?

I tried various apps, official, Vanced, revanced etc..... All with the same issue.
 

nardellu

Member
Jan 5, 2011
8
2
hi guys (and devs too)

I just installed official version (WIPED ALL DATA, so it's a fresh install) and everything is working very well except push notification in some app. Everything is ok on common apps like whatsapp or signal messenger.

For instance:

Paypal (I use magisk + safetynetfix module for make it work)
ING Banking App

Notification arrives 1 or 2 hours later...

Tried:
- Unlock settings for unlimited data on apps

Nothing changes...

It's a bug? Any workaround?
Thanks :)

Myphone: SM-G970F + lineage 20 + magisk (hidden + safetynetfix module)
 

zpunout

Senior Member
Aug 26, 2015
404
93
Samsung Galaxy S5
Moto G5 Plus
hi guys (and devs too)

I just installed official version (WIPED ALL DATA, so it's a fresh install) and everything is working very well except push notification in some app. Everything is ok on common apps like whatsapp or signal messenger.

For instance:

Paypal (I use magisk + safetynetfix module for make it work)
ING Banking App

Notification arrives 1 or 2 hours later...

Tried:
- Unlock settings for unlimited data on apps

Nothing changes...

It's a bug? Any workaround?
Thanks :)

Myphone: SM-G970F + lineage 20 + magisk (hidden + safetynetfix module)
Does the notification only arrive 1 or 2 hours later when you open the app? Official LineageOS is a "vanilla" Android OS which doesn't use Google's Cloud Messaging notification service. I suspect your banking app makes use of that if available. Maybe you could experiment and try LineageOS MicroG edition for your "beyond0lte" phone.
(I assume that edition of LineageOS is off topic for this thread so I won't discuss it any further)
 
Last edited:

kevin#34

Senior Member
Sep 23, 2017
51
7
Rome
Samsung Galaxy S10
hi guys (and devs too)

I just installed official version (WIPED ALL DATA, so it's a fresh install) and everything is working very well except push notification in some app. Everything is ok on common apps like whatsapp or signal messenger.

For instance:

Paypal (I use magisk + safetynetfix module for make it work)
ING Banking App

Notification arrives 1 or 2 hours later...

Tried:
- Unlock settings for unlimited data on apps

Nothing changes...

It's a bug? Any workaround?
Thanks :)

Myphone: SM-G970F + lineage 20 + magisk (hidden + safetynetfix module)
me too with ING app and paypal, notifications arrive within seconds after operation, no problem
 

Nosepull

Senior Member
Jan 9, 2015
269
53
@Linux4: Any update for this unofficial ROM? If not, at least maybe some hint in the first post that only the official variant is still in active development would be great.
 

Top Liked Posts

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


    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:

    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
    17
    Pre-Install Instructions

    Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.

    1. Connect the device to a Wi-Fi network.
    2. 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.
    3. 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”.
    4. Your device will reboot, you may now unplug the USB cable from your device.
    5. The device will demand you format userdata, please follow the onscreen instructions to do so.
    6. Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
    7. 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
    1. 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
    2. 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.
    3. Factory reset using Factory reset -> Format data/factory reset
      Warning: Unlike TWRP this will also erase internal storage!
    4. Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
      Then run adb sideload <path to your lineage.zip> on your PC
      Optional:
    5. 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.
    11
    Features

    • SELinux enforcing
    • AES-256-XTS FBE encryption
    • All cameras are working
    • Ramdisk is working

    Known issues

    • VoLTE/VoWiFi
    • You tell me
    • Likely more
    7
    Updated with September securitypatch and more lineage features
    6
    For everyone who upgraded to HVJ1 firmware, for all models there's a HVI4 build that has binary version 'G' too, at least for some CSCs, you should be able to downgrade to that and have it working again.
    I'd recommend to use samfw.com over sammobile tho since that one has faster free download.
    FYI that problem cannot be resolved without first getting new kernel sources from samsung... and next time: Don't update your firmware manually anymore, I will take care of it on 20.