• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

Linux4

Senior Member
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.
 

fil3s

Senior Member
Aug 30, 2014
1,314
186
42
bendigo
www.mobiledevices.cc
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.

Awesome 👍 I will try Lygisk later today.

Cheers
 

kwtf

Member
Dec 21, 2010
47
4
Updated a few days ago, today the info view (where you can set permissions, see useage etc.) was working intermittently and after a reboot i am stuck at the animated bootlogo.
- Going back to older builds only yields the "Wipe data if reboot does not work"
- Reflashing just the rom or rom+magisk yields being stuck at the logo too.

Any of you know a good, in depth guide how to debug the boot sequence/fix errors?
Got /proc/last_kmsg file, see appended.

Edit: Screw it, reflashed everything
 
Last edited:

raggatip

Member
Dec 13, 2007
15
3
There are a couple of ways to make complete image backups of the phone. The simplest is to use adb.

On my phone the following files are the actual partitions:

a) /dev/block/sda25 - system
b) /dev/block/sda31 - userdata

First check your phone to see where your partitions are mapped. i.e.:

Navigate to: /dev/block/platform

Open each folder in the platform folder till you find a folder named "by-name" (There may be only one folder)

On my phone it's "13d60000.ufs". Thus I issue this command from a terminal or adb shell:

ls -al /dev/block/platform/13d60000.ufs/by-name

This will give you list of all the partitions and the files they are mapped to. (make sure you use those mappings not mine)

Thus, to backup my phone:
a) Boot into recovery
b) enable adb
c) I run these commands:

adb pull -z any /dev/block/sda25 system.img
adb pull -z any /dev/block/sda31 userdata.img

This creates two image files on my computer (system.img & userdata.img)

To restore:
a) Boot into recovery
b) enable adb
c) I run these commands:

adb push -z any system.img /dev/block/sda25
adb push -z any userdata.img /dev/block/sda31

Note: The userdata image backup contains the data on your sdcard (internal storage). So restoring that will delete (overwrite) all your data too. (copy that separately)

p.s. Make sure you check the partition mapping on your phone or it could be disastrous.
p.p.s You can obviously backup any of the other partitions too (e.g. recovery, boot, etc.).
Thanks for this tip.

Could you explain what -z and any do please?

My userdata.img had reached over 50GB before I pulled the plug due to limited hdd space. Is there anyway this command can select only written data within the partition or is the only option to copy the entire userdata partition?
 
Jun 9, 2012
42
17
-z: enable compression with a specified algorithm (any, none, brotli)

i.e. It compresses the data before sending it to reduce network backup time. Does not compress the final userdata image stored on the disk.

There is no way to separate out the data because the partition is encrypted.

The userdata.img will be big because it makes a complete clone of the userdata partition including internal storage.

What I do to reduce backup size is to set the backup target folder flag (in Windows) to compress. This makes a massive difference to the file size and even the backup time. In my case the uncompressed userdata.img is 110GB, but the space used on the hard drive is 2.1 GB. Total backup time is around 12 mins.

You can also use "dd" with "gzip" to make the backup and compress the data too.
 
Last edited:

raggatip

Member
Dec 13, 2007
15
3
-z: enable compression with a specified algorithm (any, none, brotli)

i.e. It compresses the data before sending it to reduce network backup time. Does not compress the final userdata image stored on the disk.

There is no way to separate out the data because the partition is encrypted.

The userdata.img will be big because it makes a complete clone of the userdata partition including internal storage.

What I do to reduce backup size is to set the backup target folder flag (in Windows) to compress. This makes a massive difference to the file size and even the backup time. In my case the uncompressed userdata.img is 110GB, but the space used on the hard drive is 2.1 GB. Total backup time is around 12 mins.

You can also use "dd" with "gzip" to make the backup and compress the data too.
So, I tried using dd using these commands (same partition no.s as you)

adb shell dd if=/dev/block/sda25 | gzip -c > /path/to/file/system.img.gz

-Outputs a 5.6GiB partition to a compressed file 680MiB in size @ 26M/s (Just under 4mins), adb pull was @ 70M/s uncompressed.

adb shell dd if=/dev/block/sda31 | gzip -c > /path/to/file/userdata.img.gz

-Outputs a ~120GiB partition to a compressed file 3.4GiB in size @ 34M/s (Just over 55mins)

To restore I think it's the following though I haven't tested this yet:

adb shell gzip -dc /path/to/file/system.img.gz | dd of=/dev/block/sda25

adb shell gzip -dc /path/to/file/userdata.img.gz | dd of=/dev/block/sda31
 
Last edited:
  • Like
Reactions: starbright_
Jun 9, 2012
42
17
You will see a massive improvement in backup speed (up to 10 times) if you increase the block size of the dd command. e.g.

adb shell dd if=/dev/block/sda25 /bs=65536 | gzip -c > /path/to/file/system.img.gz
 

raggatip

Member
Dec 13, 2007
15
3
You will see a massive improvement in backup speed (up to 10 times) if you increase the block size of the dd command. e.g.

adb shell dd if=/dev/block/sda25 /bs=65536 | gzip -c > /path/to/file/system.img.gz
Yes I increased it albeit to 1000 with only a minute time saving on the larger partition. I read somewhere that there's an increased chance of introducing errors with larger block sizes, though it is tempting. Are my restore commands correct?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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.
    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
    3
    ok, thanks, I guess no countermeasure can be adopted... (?)
    Try installing this as a system app, by making a folder /system/app/SamsungDAP and putting the APK inside
    3
    First off, thank you for making this.
    Been using the microg fork for a couple of days, so I thought I'd share a list of things that I had/have issues with or that don't work.
    Most of these issues should also be present on this official ROM, as it's just the google services backend that's different.
    I'm also new to modern smartphone ROMs, so please don't bash me if I say something dumb.

    Using on an S10+ Exynos. SM-G975F
    Installation went just fine on Arch Linux.

    Lockscreen/locked related:
    Always on Display doesn't shift the clock every minute, so there's a chance of burn-in.
    Always on Display has a clump of maybe 5 pixels next to the front cameras that constantly blink green.
    Wave to wake up doesn't work.

    Microg related, had to install DroidGuard Helper from FDroid to get the fingerprint sensor working. Works well and much quicker than on the stock Samsung ROM.

    Random issues:
    Status bar doesn't change to a dark font with a light wallpaper. Works just fine in apps.
    Adaptive brightness seems to be having issues actually doing anything, very often.
    There are no built-in torch intensity settings.
    Most likely microg related, doesn't automatically pick up auth codes from SMS as there's no daemon for it.

    Frequently asked about features:
    Wireless hotspot working just fine.
    5GHz wifi working just fine.
    Bluetooth working just fine. No issues with wireless earbuds, paired instantly.
    LTE working as expected, signal is fine. Central EU. TMobile network.

    Camera:
    Stock camera app doesn't let you change lenses or video framerate to 60 fps.

    Using the GCam fork mentioned somewhere above "MGC_8.1.101_A9_GV1r_MGC"
    Wide angle lens working, normal lens working, no telephoto.
    Both front cameras working
    Takes some time to switch between any of these.
    You can force [email protected] video with stabilization and all the nice things in the settings.
    No 4K video for the front cameras, it caps at [email protected]

    Not tested:
    NFC/Contactless Payments.
    Dual sim
    SD card slot
    USB hotspot.
    Sensor that checks for liquid in the charging port.
    Samsung's pointless oxygen levels in blood / heartbeat sensor.
    "Pedometer".
    Gyro/etc. for VR.
    2
    Depends of whether you have a Snapdragon or Exynos variant of an S10e I think. Here's one link to the Exynos SM-G970 F compatible version called ZGCAM https://forum.xda-developers.com/t/gcam-zgcam-for-exynos-s10-e.4176265/
    Since you added GApps to your LOS install, you shouldn't need a services spoof apk to get GCam to work, but here is the link to info about that anyway: https://www.xda-developers.com/google-camera-port-hub/
    He definitely has the exynos variant as snapdragon doesn't have unlockable bootloader and lineage. Also, the best gcam atm is BSG MGC (https://www.celsoazevedo.com/files/android/google-camera/dev-bsg/f/dl49/)
  • 29
    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
    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.
    5
    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
    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