[ROM] LineageOS 16.0 for S10E/S10/S10+ Exynos

Search This thread

NexxusDE

Member
Nov 19, 2018
18
5
Dont get Magisk to work with LineAgeOS 16

Did someone get Magisk to work on LineAgeOS16?

What i do:

  1. Flashing Stock Firmware downloaded with Sam Tool in ODIN
  2. Boot
  3. Install Magisk Manager and patch TWRP 3.3.1-11 and AP from stock firmware with magisk manager, replace recovery.img in patched AP File
  4. Flash Patched AP File with Odin
  5. Boot directly in Recovery and flash multi-disabler_1.7, wipe, flash vbmetadisabler, wipe dalvik cache, flash LineageOS16, Gapps and Magisk v20
  6. Reboot

Do i forget something?
Need help:confused:
 

Midyr

Senior Member
Nov 19, 2011
88
6
Mainz
Thanks Ivan for updating the ROM to ASIG :good:

If anyone wants to dirty flash from v20190830 to v20191101, you can try this procedure:


Code:
unzip G970FXXU3ASIG_G970FOXM3ASIE_PHN.zip -d firmware && cd firmware
5. Delete the CSC file (if you don't you'll end up with a factory reset phone)

.

Hi,

thanks for that!
But I have zwo CSC files:
HOME_CSC...
and
CSC_OM...

Have I both to delete?

Thanks

Midyr
 

byteXpression

Senior Member
Aug 31, 2017
66
128
Frankfurt
Did someone get Magisk to work on LineAgeOS16?

What i do:

  1. Flashing Stock Firmware downloaded with Sam Tool in ODIN
  2. Boot
  3. Install Magisk Manager and patch TWRP 3.3.1-11 and AP from stock firmware with magisk manager, replace recovery.img in patched AP File
  4. Flash Patched AP File with Odin
  5. Boot directly in Recovery and flash multi-disabler_1.7, wipe, flash vbmetadisabler, wipe dalvik cache, flash LineageOS16, Gapps and Magisk v20
  6. Reboot

Do i forget something?
Need help:confused:

Did not work for me either. Magisk Manager still shows "not installed" - even though I flashed Magisk via TWRP. This is a major problem at the moment with the current version of this ROM.
Without Magisk you can not use Edxposed either. You can not restrict the quick settings menu or the power off buttons in the lock screen, etc. which (in my opinion) are core requirements for installing a custom ROM like LOS in the first place.
However, addonsu works fine (but is no comparison to Magisk). Encryption (FDE) also works fine (if you allocate the 4K slot for the encryption keys accordingly).
Magisk works with the Samsung stock rom and Samsung recovery (if you flash theMagisk patched AP file) or the TWRP recovery (if you are going with the Magisk patched TWRP file instead of the standard stock recovery).
After all I am also not quite sure if I stay with this version of LOS or rather going back to the standard Samsung stock ROM with Magisk because of the incompatibility issues of Magisk with this current version of LOS.
Maybe Ivan will make it work in the future (which would be great) or it will become available with LOS 17...?
 

Chulain

Member
Feb 3, 2017
15
4
Antwerp
How is the battery life?

lU0x2GK.png



It's much better for me than stock firmware.

Camera seems to be leeching battery? or is this normal? @Ivan_Meler

not video recording just pictures
 
Last edited:
  • Like
Reactions: htw1 and sm4rk0

flunkyball

Senior Member
May 20, 2019
80
65
Signature Spoofing and Magisk

First of all, a big thx to @Ivan_Meler for the great work ! :good:
I used LOS16 with my S7 for quite a time with much pleasure and now I am trying to setup up my newly aquired S10.

Though I am in ASII firmware everything works pretty smooth and the process described worked flawless.

However, in order to use the phone productivly I need to get the following things to work before:
- Root support with Magisk
- Signature Spoofing in order to use MicroG.


(I know, both issues are only indirect related to the ROM; Since many people here are trying the same tings I decided to post here anyway)

TWRP with Magisk:
- I used "twrp-beyond1lte-3.3.1-11_ianmacd.img" available here (https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856)
- Patched the image via latest Magisk Manager.
- Flashed it into recovery with heimdall.
- Booted directly into recovery flash multi-disabler_1.7, wipe, flash vbmetadisabler, wipe dalvik cache, flash LineageOS16.
=> No positiv result.
Question: The howto about getting TWRP with Magisk to work on stock ROM describes, that besides the recovery.img also the firmware itself needs to be patched by Magisk Manager.
How do I do that in this case since patching only recovery is not sufficient ?


Signature Spoofing:

- Examining the LOS16 firmware I found the "classes.dex" file inside the "services.jar". Thus the ROM is deodexed already.
- Booted into recovery and flashed "Nanodroid-Patcher" (https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928)
- The patcher recognizes the deodexed state successfully but aborts with "patches not applied" no further error message available.
Question: Essentially I have no idea how to proceed. Did anyway successfully enable signature spoofing in LOS16 ?


Thx everyone for hints and advices.
 
  • Like
Reactions: sm4rk0

WalterCool

Senior Member
Jan 15, 2012
141
26
First of all, a big thx to @Ivan_Meler for the great work ! :good:
I used LOS16 with my S7 for quite a time with much pleasure and now I am trying to setup up my newly aquired S10.

Though I am in ASII firmware everything works pretty smooth and the process described worked flawless.

However, in order to use the phone productivly I need to get the following things to work before:
- Root support with Magisk
- Signature Spoofing in order to use MicroG.


(I know, both issues are only indirect related to the ROM; Since many people here are trying the same tings I decided to post here anyway)

TWRP with Magisk:
- I used "twrp-beyond1lte-3.3.1-11_ianmacd.img" available here (https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856)
- Patched the image via latest Magisk Manager.
- Flashed it into recovery with heimdall.
- Booted directly into recovery flash multi-disabler_1.7, wipe, flash vbmetadisabler, wipe dalvik cache, flash LineageOS16.
=> No positiv result.
Question: The howto about getting TWRP with Magisk to work on stock ROM describes, that besides the recovery.img also the firmware itself needs to be patched by Magisk Manager.
How do I do that in this case since patching only recovery is not sufficient ?


Signature Spoofing:

- Examining the LOS16 firmware I found the "classes.dex" file inside the "services.jar". Thus the ROM is deodexed already.
- Booted into recovery and flashed "Nanodroid-Patcher" (https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928)
- The patcher recognizes the deodexed state successfully but aborts with "patches not applied" no further error message available.
Question: Essentially I have no idea how to proceed. Did anyway successfully enable signature spoofing in LOS16 ?


Thx everyone for hints and advices.

For Signature Spoofing try https://github.com/Lanchon/haystack , works fine to me. For root, just use su patcher and manage superuser under developer options.
 
  • Like
Reactions: sm4rk0

wora92

Senior Member
Sep 19, 2019
61
27
First of all, a big thx to @Ivan_Meler for the great work ! :good:
I used LOS16 with my S7 for quite a time with much pleasure and now I am trying to setup up my newly aquired S10.

Though I am in ASII firmware everything works pretty smooth and the process described worked flawless.

However, in order to use the phone productivly I need to get the following things to work before:
- Root support with Magisk
- Signature Spoofing in order to use MicroG.


(I know, both issues are only indirect related to the ROM; Since many people here are trying the same tings I decided to post here anyway)

TWRP with Magisk:
- I used "twrp-beyond1lte-3.3.1-11_ianmacd.img" available here (https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856)
- Patched the image via latest Magisk Manager.
- Flashed it into recovery with heimdall.
- Booted directly into recovery flash multi-disabler_1.7, wipe, flash vbmetadisabler, wipe dalvik cache, flash LineageOS16.
=> No positiv result.
Question: The howto about getting TWRP with Magisk to work on stock ROM describes, that besides the recovery.img also the firmware itself needs to be patched by Magisk Manager.
How do I do that in this case since patching only recovery is not sufficient ?


Signature Spoofing:

- Examining the LOS16 firmware I found the "classes.dex" file inside the "services.jar". Thus the ROM is deodexed already.
- Booted into recovery and flashed "Nanodroid-Patcher" (https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928)
- The patcher recognizes the deodexed state successfully but aborts with "patches not applied" no further error message available.
Question: Essentially I have no idea how to proceed. Did anyway successfully enable signature spoofing in LOS16 ?


Thx everyone for hints and advices.

Hello. I guess you could use adb in TWRP to see debug output. As for Nanodroid - I recently tried it with LOS16 on another device and it worked. It might help to pull the source from github and build the latest version yourself. However, I guess it would be better to wait for Ivan_Meler to release the source and patch in signature spoofing by using the microg patches. Signature spoofing is too dangerous the way how Nanodroid provides it. It cannot be disabled and it cannot be denied when patched with Nanodroid. So basically every app could potentially use spoofing without asking and without any way to stop that.
 
Last edited:

flunkyball

Senior Member
May 20, 2019
80
65
For Signature Spoofing try https://github.com/Lanchon/haystack , works fine to me. For root, just use su patcher and manage superuser under developer options.

Thx for the advice, I will look into it and report back how it went.

---------- Post added at 10:15 PM ---------- Previous post was at 10:10 PM ----------

For Signature Spoofing try https://github.com/Lanchon/haystack , works fine to me. For root, just use su patcher and manage superuser under developer options.

Well, if it would be only for root I would agree. However magisk provides more functionality via its modules which I got used to.

Hello. I guess you could use adb in TWRP to see debug output. As for Nanodroid - I recently tried it with LOS16 on another device and it worked. It might help to pull the source from github and build the latest version yourself. However, I guess it would be better to wait for Ivan_Meler to release the source and patch in signature spoofing by using the microg patches. Signature spoofing is too dangerous the way how Nanodroid provides it. It cannot be disabled and it cannot be denied when patched with Nanodroid. So basically every app could potentially use spoofing without asking and without any way to stop that.

Having signature spoofing patched into the source would be of course the better solution. Since I do not know when that will be or even if ever I am looking for alternatives. I will try to dig into the issue using the adb debuging...

Thx !
 

PaulCombuse

New member
Jan 4, 2018
4
6
Dresden
Hi,

thanks for that!
But I have zwo CSC files:
HOME_CSC...
and
CSC_OM...

Have I both to delete?

Thanks

Midyr
@Midyr: You only need to delete the "CSC_OM..." file.

Thanks to the instructions by eelcohn I justed updated my SM-G973F successfully from ASG8 firmware with Ivan's August build to ASII with the latest November LOS build.
I used unofficial TWRP build by ianmcd for that, which was twrp-beyond1lte-3.3.1-11_ianmacd.img for my device.
After reboot into TWRP recovery, I installed multidisabler-samsung-1.7.zip, followed by vbmeta_disabler.zip from Ivan's GoogleDrive link and then wiped Cache/Dalvik before installing lineage-16.0-20191101-UNOFFICIAL-beyond1lte.zip and OpenGapps pico. Finally I unmounted System partition in TWRP prior to installing addonsu-16.0-arm64-signed.zip and then rebooted into the updated system.
Works like a charm AND thanks to Ivan the camera is now working without any trouble (wideangle as well) using OpenCamera. :good:
My biggest concern regarding this update was if my banking app would make trouble when updating the firmware - but this is not the case, it still works as expected. Galaxy watch (Galaxy wearable app) is working as well, when setting ro.product.brand=google and ro.product.manufacturer=google in build.prop file (root/system/) as discussed by
 
Last edited:

regimail

Member
Mar 24, 2017
17
1
do NFC payments work?

Hello,
Does Google Pay/samsung pay/NFC payments work on this Rom?
I'm still a newbie, so please forgive me if my question has been already answered elsewhere (I searched this thread and found nothing).
 

flunkyball

Senior Member
May 20, 2019
80
65
Hello. I guess you could use adb in TWRP to see debug output. As for Nanodroid - I recently tried it with LOS16 on another device and it worked. It might help to pull the source from github and build the latest version yourself. However, I guess it would be better to wait for Ivan_Meler to release the source and patch in signature spoofing by using the microg patches. Signature spoofing is too dangerous the way how Nanodroid provides it. It cannot be disabled and it cannot be denied when patched with Nanodroid. So basically every app could potentially use spoofing without asking and without any way to stop that.

Just had a look at the TWRP logs which are revealing the following:

Code:
********************************
 NanoDroid                      
 Framework Patcher              
 Powered by DexPatcher          
 22.5.20191029                     
********************************
 
 INFO: #1 [SLOT] 
 INFO: #2 [SLOT] 
 INFO: #4 [system_tmp] /dev/block/by-name/system
 INFO: #5 [SYSTEM_BLOCK] /dev/block/sda25
mount: losetup failed 1
 INFO: #6 [vendor_tmp] /dev/block/by-name/vendor
 INFO: #7 [VENDOR_BLOCK] /dev/block/sda26
ln: cannot create symbolic link from '/system/vendor' to '/vendor/vendor': Read-only file system
 
rootfs on / params: (rw,seclabel)
tmpfs on /dev params: (rw,seclabel,nosuid,relatime,size=3787244k,nr_inodes=946811,mode=755)
devpts on /dev/pts params: (rw,seclabel,relatime,mode=600,ptmxmode=000)
proc on /proc params: (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys params: (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux params: (rw,relatime)
tmpfs on /mnt params: (rw,seclabel,nosuid,nodev,noexec,relatime,size=3787244k,nr_inodes=946811,mode=755,gid=1000)
none on /acct params: (rw,relatime,cpuacct)
tmpfs on /tmp params: (rw,seclabel,relatime,size=3787244k,nr_inodes=946811)
none on /sys/kernel/config params: (rw,relatime)
adb on /dev/usb-ffs/adb params: (rw,relatime)
mtp on /dev/usb-ffs/mtp params: (rw,relatime)
pstore on /sys/fs/pstore params: (rw,seclabel,relatime)
/dev/block/sda28 on /cache params: (rw,seclabel,relatime,i_version,data=ordered)
/dev/block/sda31 on /data params: (rw,seclabel,relatime,resgid=1065,i_version,data=ordered)
/dev/block/sda31 on /sdcard params: (rw,seclabel,relatime,resgid=1065,i_version,data=ordered)
/dev/block/mmcblk0p1 on /external_sd params: (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/sda25 on /system_root params: (rw,seclabel,relatime,block_validity,delalloc,barrier,user_xattr,acl,i_version)
/dev/block/sda26 on /vendor params: (ro,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr,acl,i_version)
 
 INFO: #8 [prop]
-rw------- 1 root root 3031 2008-12-31 18:00 /system/build.prop
 INFO: #9 [build_props] /system_root/system/product/build.prop
/system_root/system/build.prop
/vendor/build.prop
 > preparing environment
 > Android 7.0 - 9.0 (SDK 29) detected
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
 > device architecture: arm64
   
 ++
 ++ services.jar status: DEODEX
 ++
 
 > patching signature spoofing support
 
 >> patching services.jar
[COLOR="Red"]CANNOT LINK EXECUTABLE "/system/bin/dalvikvm": library "libnativehelper.so" not found
linker: CANNOT LINK EXECUTABLE "/system/bin/dalvikvm": library "libnativehelper.so" not found[/COLOR]

 
 !! failed to apply patches
 
Updater process ended with ERROR: 1
I:Install took 1 second(s).

So my next try will be to get the manuelly but a version of the libnativehelper.so where it is expected.
 

mikk150

Member
Oct 29, 2008
30
4
Tartu
Hello,
Does Google Pay/samsung pay/NFC payments work on this Rom?
I'm still a newbie, so please forgive me if my question has been already answered elsewhere (I searched this thread and found nothing).

Short answer: No
Longer answer: NFC payments are disabled by default on custom roms
Even longer answer: Nfc payments CAN be enabled on custom roms, and should be supported, but since no-one has gotten Magisk working yet, then unfortunately no.
You can use Magisk hide to hide fact that you have rooted phone, that way NFC payments start working. You also have to fix build.prop file
 

Top Liked Posts

  • There are no posts matching your filters.
  • 115
    k5tUT1V.png

    LineageOS 16.0 for Galaxy S10 Series

    Code:
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */


    Working:
    - Wifi
    - Sound
    - mali drivers
    - USB tethering
    - Video Playback
    - Fingerprint Sensor
    - Ril (Mobile data,calls, sms and stuff)
    - Sensors
    - Bluetooth
    - Wifi HotSpot
    - MTP
    - 2D and 3D gpu acceleration
    - HW encoding/decoding
    - GPS
    - Cameras (All of them)
    - HWcomposer (HWC)
    - Signal indicator
    - Double tap to wake
    - Wireless PowerShare

    Not Working
    - VoLTE and VoWiFi will not be implemented (for now) as they heavily depand on samsungs framework


    To properly report a bug (Please dont report things already on the Not Working list)
    a) Logcat
    b) /proc/last_kmsg (or /proc/kmsg)
    c) /data/tombstones
    d) dmesg

    Please do not report bugs if you have performed any system modifications excluding gapps and addonsu installation


    Installation instructions

    Make sure you are on ASIG firmware (ASII and ASJG are untested as samsung didnt release kernel source yet (ASII should work tho))
    Download official twrp from twrp.me
    flash twrp as per given instructions
    Once in twrp flash multi-disabler
    format data
    flash vbmeta_disabler.zip from gdrive link below if you dont already have vbmeta disabled
    wipe cache dalvink system
    flash LineageOS
    If you want to have gapps flash them right after flashing the rom before first booting
    Install addonsu if you want root (make sure system is not mounted before flashing addonsu)
    Reboot the device

    If you are updating from previous release just flash the rom on top of old one and wipe cache/dalvik(art) cache

    Downloads:
    Google Drive
    (Select build coresponding to your devices codename, S10e = beyond0lte | s10 = beyond1lte | s10+ = beyond2lte)


    OpenGapps
    Root

    I do this in my free time so bear that in mind when you notice I didn't fix known bug in next available build, Currently i work on this alone and i am not one of those kangers that just copy source and claim it as their own work,
    if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler



    Based On Android 9 Pie
    Changelog

    01.11.2019.
    - Updated to ASIG kernel source (master_asig branch)
    - Cleaned up kernel source
    - Merged October system patch
    - Misc performance and stability updates
    - Sycned with LOS source

    30.08.2019.
    - Added double tap to wake (Settings -> display -> Advanced)
    - Added Wireless PowerShare (Add quick settings toggle for it)
    - Added extra wide angle camera app (Stand alone install it manually)
    - Fixed cooldown value for brightness sensor so its less bouncy in direct sunlight
    - Made bixby key mapable
    - Removed unused backlight setting entry
    - Synced with LineageOS source

    19.08.2019.
    - Added support for ASH1 firmware
    - Tuned light sensor debounce values to prevent random brightness changes
    - Fixed permissions for HotwordEnrollment (Googles off screen assistant)
    - Added support for exfat formated sdcards
    - Fixed issue where kernel couldnt be cross-compiled with newer version of host kernel

    12.08.2019.
    - Improved auto brightness debounce values
    - Properly fixed signal indicator
    - Fixed Proximity sensor in calls (Note that it works same way as on stock so not every app can use it just like on stock)
    - Added SSENSOR permission for sensors/services using it (see system/etc/permissions/privapp-permissions-ssensor.xml)
    - Ficed issue where wrong power hal would be loaded
    - General stability improvements
    - Improved installer handling

    12.08.2019.
    - First public release



    XDA:DevDB Information
    [ROM] LineageOS 16.0 for S10E/S10/S10+ Exynos, ROM for the Samsung Galaxy S10

    Contributors
    Ivan_Meler
    Source Code: https://github.com/ivanmeler/android_kernel_samsung_beyondlte

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 4.x
    ROM Firmware Required: ASG8 or ASH1
    Based On: LineageOS

    Version Information
    Status: Beta
    Current Stable Version: 1.0.1
    Stable Release Date: 2019-11-01

    Created 2019-08-12
    Last Updated 2019-11-01
    27
    Progress update, i got q booting on day that it source was released with almost everything working, I just need to clean up few hacks that are in place right now and after that ill release first test aosp release based on it, its pretty bare bone right now as no lineage features have been merged yet
    25
    Since i realized i never posted any proper teasers from q here are some screenshots, Just need to do some final testing before i feel like posting the rom since i want to be sure there isnt any regression compared to pie

    PVvKJZ3.png

    I6leP51.png

    9DTloOc.png

    21
    New builds are up here is a brief changelog
    - Added double tap to wake (Settings -> display -> Advanced)
    - Added Wireless PowerShare (Add quick settings toggle for it)
    - Added extra wide angle camera app (Stand alone install it manually)
    - Fixed cooldown value for brightness sensor so its less bouncy in direct sunlight
    - Made bixby key mapable
    - Removed unused backlight setting entry
    - Synced with LineageOS source

    Also as a sidenote You can manually install wide angle camera app available at gdrive link and it will make use of wide angle lense (On s10+ both front and back)

    Wireless powershare can be added as a quick settings toggle just like on stock (As of right now there is no led indicator on the back as i need to find sysfs node for it but wireless powershare itself works completely fine and you can check its status from icon status (Its always disabled after reboot and icon has a lot of failsafe checks))

    Double tap to wake is available from Settings -> Display -> advanced -> double tap to wake

    And please stop complaing by issues you got into by using magisk patched twrp its not rom related bug so this is not place for discussion about it

    Next update will probably add support for 5g and note 10 series of devices if i find testers for note thats why i didnt push device tree yet (I really dont want people just taking it changing literally 10 lines and claiming it as their own work as this has happened in past a lot of times)

    I would also like to thank donators as i do this in my free time and donations help with build server cost and get me a coffee.
    Anyway hope you all enjoy the build
    21
    Hey guys quick update on status of updates, I had a little accident and ended up in a hospital, While i do have my laptop with me all of the source for q is at my home pc, Im really sorry i didnt have a chance to post update before this happened But ill do it as soon as i get back home, Once again really sorry for delays but project will continue really soon hopefuly
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone