[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos

Search This thread

flortsch

Member
Sep 10, 2014
34
29
Linz
florian-latifi.at
This service.jar: Is is under change - so need to be recreated with each update? Or only if major version is changing? How individually is this (s10, s10e, ...?)
Not an expert here and someone correct me if I am wrong, but as I can see, the services.jar is part of Android and therefore not device specific. So it should be sufficient to update it only when bigger changes happen to underlying Android/LOS.
 

starbright_

Senior Member
Apr 11, 2010
1,304
212
The dk.jens.backup app is outdated. The successor (fork) is https://f-droid.org/repo/com.machiav3lli.backup
But beware the dragons: AFAIK Machiav3lli changed the backup format, so they're not compatible.

Can't find that app - error 404. For me "migrate" does the job well.

Anyone already migrated coming from Ivans LOS, keeping data alive? If someone can remember the steps ... you are welcome. :)

Dirty flash zip and img from TWRP (overwriting it) is ok? Or anything else required?
Spoofing and reinstall microg is next steps?
 
Last edited:

Keule-Tm

Senior Member
Oct 3, 2016
346
135
Berlin
Samsung Galaxy S10
Can't find that app - error 404. For me "migrate" does the job well.

Anyone already migrated coming from Ivans LOS, keeping data alive? If someone can remember the steps ... you are welcome. :)

Dirty flash zip and img from TWRP (overwriting it) is ok? Or anything else required?
Spoofing and reinstall microg is next steps?
Oops... It should be https://f-droid.org/en/packages/com.machiav3lli.backup/ (not .../repo/...).
 
  • Like
Reactions: starbright_

7hr08ik

Senior Member
Oct 8, 2011
258
95
This is the right order:
  1. Flash lineage-18.1-20210415-recovery-beyond0lte.img and vbmeta.img
  2. Boot Recovery
  3. Factory reset using Factory reset in Recovery -> Format data/factory reset
  4. adb sideload lineage-18.1-20210415-UNOFFICIAL-beyond0lte
  5. adb sideload Magisk-v22.0.apk
  6. Boot to LineageOS and finish Installation of Magisk
  7. Boot Recovery
  8. adb sideload spoof_s10e.zip to enable signature spoofing (or install via Magisk)
  9. adb sideload Nanodroid for MicroG
  10. Boot to LineageOS

Hey guys.

So tomor im jumping in 😃 Currently running Modpunks 17.1.

I want to follow the above steps to get Google free 😃, are they still valid?

I know this ROM needs Q or R firmware, do I need to flash back to stock, then flash 18? Or can I just plow forward with the above?
 

UsernameNotRecognized

Senior Member
May 17, 2012
201
34
I'm in the same boat as 7hr08ik here, but coming from pixel experience. The experience is great, but the broken call forwarding is dealbreaking. (And, well, the lack of OTA in general).
 

Spyop3

Member
Jun 29, 2010
24
8
Hey guys.

So tomor im jumping in 😃 Currently running Modpunks 17.1.

I want to follow the above steps to get Google free 😃, are they still valid?

I know this ROM needs Q or R firmware, do I need to flash back to stock, then flash 18? Or can I just plow forward with the above?
You can just go with it

Backup your stuff before as Lineage recovery wipe everything even sd ;)
 

[Legenda]

Senior Member
Dec 27, 2012
280
29
Hey everyone.

I'm on Ambasadii rom 11 (OneUI). But don't know why. Can't find the thread.
Anyway.
What's the difference between this rom custom? and Ivan meler (the spoofing one) or CrDroid from turboluke ? Sorry I'm clearly lost around lineage solutions here.
And I would like to move on wiht lineage but there is any good photos app? (because samsung stock app photo is clearly great).

Thanks.
 

gaglia83

Senior Member
May 7, 2017
75
3
What's the difference between this rom custom? and Ivan meler (the spoofing one) or CrDroid from turboluke ?
And I would like to move on wiht lineage but there is any good photos app?

I can tell you my personal experience but your mileage may vary.
I don't know about CrDroid, but compared to IvanMeler's signature spoofing solution, this one works much better for me. More stable and device encryption works (albeit "only" with Android 11's native solution, file-based encryption rather than full disk encryption, but that's still pretty good). The downside is that you cannot use TWRP (with IvanMeler's build you can) so you are stuck with the default Lineage recovery that is way less functional than TWRP.

TL;DR if you *need* TWRP go for IvanMeler's build, otherwise this one.

Photo app: the best Free one that I know is OpenCamera, works great on this phone.
 
  • Like
Reactions: [Legenda]

UsernameNotRecognized

Senior Member
May 17, 2012
201
34
So I've followed a combination of instructions provided by linux4 and exaveal and the experience is pretty good. The downside is probably mainly nanodroid. I'm have a LOT of apps that are critically misbehaving. Will this improve if I install mindthegapps?

So far google drive backup/restore is broken and I cannot login with some applications (keep asking me to login, but then "this account is already on this device" or something like that...).

Once again, nothing against linux4, the LOS experience feels great so far.

Edit: OK folks, with mindthegapps the experience is great once again. I'll try and see if bluetooth calling is working.
 
Last edited:

[Legenda]

Senior Member
Dec 27, 2012
280
29
I can tell you my personal experience but your mileage may vary.
I don't know about CrDroid, but compared to IvanMeler's signature spoofing solution, this one works much better for me. More stable and device encryption works (albeit "only" with Android 11's native solution, file-based encryption rather than full disk encryption, but that's still pretty good). The downside is that you cannot use TWRP (with IvanMeler's build you can) so you are stuck with the default Lineage recovery that is way less functional than TWRP.

TL;DR if you *need* TWRP go for IvanMeler's build, otherwise this one.

Photo app: the best Free one that I know is OpenCamera, works great on this phone.
I want to test CrDroid, apparently, this rom had a good battery life. The only thing, it's to install custom TWRP (from cornasicu). Nothing complicated.
And I want to keep using TWRP because it's more simple and effecient in my case.
Thanks for your advice mate.
 

arcatarc

Senior Member
Hello
Thank you for your work.

Is it possible to use this Rom with TWRP + SELinuxEnforcing + without FBE?
I DID IT!:
1 Download and install Twrp(official)+vbmeta.img (with Verify Boot disabled) + Rom + Multidisabler + Magisk apk (install it from Twrp)...
and you will get Twrp+Root+SELinuxEnforcing!
Obviously make a backup of your data(you need to format Data partition on Twrp if it is encrypted!)
 
Last edited:
  • Like
Reactions: wdevil12

UsernameNotRecognized

Senior Member
May 17, 2012
201
34
Hmm, not looking great....

Pair from phone:
If I try to pair from the phone to the PC it seems to try and shows me the keys, but immediately disconnects and reconnects, restarting it. Does it a couple times, than craps out silently.
Pair from PC:
It connects fine, but immediately disconnects.

Perhaps interesting to note, is the different way windows registers the device in my bluetooth settings. Below you can find the S10+.
1619985082012.png

Note how they are both "Other devices", not audio, and not paired. That's because they disconnect immediately.
If I press connect it turns into this.
1619985131839.png

But in a second or so it reverts back.

On the Mi 5s plus it does seem to work a bit better, but I'm not sure if it fully works. It did work when I ran default One UI.

I'm a bit out of ideas, if anyone has some suggestions I'm all ears.

Edit: After an hour or so it randomly asked me to connect again, after 2 tries in a row it seemed to stick.
1619993498535.png

And it seems that call forwarding finally worked!
So once it works it works fine. The issue now is making it work by default (and not randomly after an hour).
It's at least progress compared to pixel experience...?
 
Last edited:

kriz_

Member
Apr 2, 2021
10
2
  • Like
Reactions: wdevil12

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I managed to patch the system in order to enable signature spoofing for MicroG by following this guide. Here is a zip file I created for my s10e with a patched services.jar one must flash via Magisk.

    With the latest update of the ROM I get stuck on loading lineage screen with this module activated in Magisk maybe need an update

    @flortsch Do you have the same problem ?

    If you have same problem you can try this version I just made based on @flortsch linked tuto

    And it works fine for me :)
    1
    Well this just got weird. It seems that youtube music (vanced) is removed (as in uninstalled/gone) after such a reboot happens. This does not happen if i manually reboot.

    The reset reason is also system_server...

    The first would hint at a root/vanced issue, but the latter more LOS. Weird stuff. Anyone got some thoughts on this?

    Edit: appears that this is a known bug that should've been fixed, but the fix probably didn't account for this type of reboot. Also happens without vanced installed. I'm just going to hope it doesn't happen when I get a call...
    Instead of youtube/vanced you can give NewPipe a try - from FDroid store. It offers a lot of good OSS stuff.
    1
    @Linux4 Would you be so kind to post your roomservice.xml? I'd like to use your repository to try building LOS18 myself. Thank you!
    Code:
    <project name="LineageOS/android_device_samsung_slsi_sepolicy" path="device/samsung_slsi/sepolicy" remote="github" revision="lineage-18.1" />
    <project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-18.1" />
    <project name="LineageOS/android_hardware_samsung_nfc" path="hardware/samsung/nfc" remote="github" revision="lineage-18.1" />
    
    <project name="exynos9820-dev/android_device_samsung_beyond1lte" path="device/samsung/beyond1lte"  remote="github" revision="lineage-18.1" />
    <project name="exynos9820-dev/android_device_samsung_exynos9820-common" path="device/samsung/exynos9820-common" remote="github" revision="lineage-18.1" />
    <project name="exynos9820-dev/android_kernel_samsung_exynos9820" path="kernel/samsung/exynos9820" remote="github" revision="lineage-18.1" />
    1
    Great,

    Thank you! Question: How do you include vendor files from android_vendor_samsung_exynos9820-common? I dont want to pull those files from the phone but from the repository instead. Any idea on that?

    Just add add the vendor repos for the devices you need to the roomservice.xml like this:
    XML:
        <project name="exynos9820-dev/android_vendor_samsung_beyond1lte" path="vendor/samsung/beyond1lte" remote="github" revision="lineage-18.1" />
        <project name="exynos9820-dev/android_vendor_samsung_exynos9820-common" path="vendor/samsung/exynos9820-common" remote="github" revision="lineage-18.1" />
    1
    Hello,
    i was using S10+ stock with root and magisk and twrp for the last years. Today i flashed Lineago OS recorvery like descripted, but i can't access recovery with Volume up, power and bixby. it just shows the red message. So i flashed https://androidfilehost.com/?w=files&flid=315865 in the hope to make it work, and reflashed LineageOS recorvery like descripted here. Now it's just staring over and over again. Any help possible?

    Edit: in the top left corner there is writen in a text box:
    Rev. Check Fail. Device: 8, Binary:2 (DTBO)
    You were on Pie firmware before by any chance?
    Also on download page there's a link "Firmware update" you could try with this
  • 31
    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:
    • 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
    • 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/exynos9820-dev
    12
    Features

    • SELinux enforcing
    • AES-256-XTS FBE encryption
    • Latest Linux 4.14.x kernel
    • All cameras are working
    • Ramdisk is working

    Known issues

    • Miracast not working (Google removed it in AOSP Pie)
    • VoLTE/VoWiFi
    • You tell me
    9
    Requirements:
    • Any Q or R based firmware installed on your device.

    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 and a disabled vbmeta image
      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
      together with a disabled vbmeta image.
      If using Heimdall use: heimdall flash --RECOVERY recovery.img --VBMETA vbmeta.img --no-reboot
      You can find a disabled vbmeta image attached to this post.
    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 magisk 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!
    7
    LOS 18.1 for our S10 device? SELinux enforcing? FBE? Open-source device tree? Where can I donate for this awesome work?
    6
    Update on feedback on the ROM, its been a couple of days, and this is easily my daily driver. Only issue I encountered was through Gapps not having the dialer app set as the default. Bizarrely the dialer was still semi functional. The finger print sensor is now fixed as well.

    This is a an easy successor to ModPunks great work, and I hope that Linux4 finds the time to become a maintainer for our device. Thanks for the great work