[ROM][EXYNOS] LineageOS 17.1 for S10e|S10|S10+ - v1.4 (UPDATE: 2020-12-17)

[modpunk]

Well, updating is still not too complicated. My suggestion would be:
a) boot into twrp
b) flash latest lineageos version
c) remove the cable and shut down the phone (via twrp)
d) hold the two buttons and plug in the cable to the phone
e) flash those 9 files (in their latest version) mentioned on the first page of this thread
f) done

Edit: I see you want to use Magisk. In that case it could be that further steps are necessary.

I do it this way too, but for c) and d) I just select "download" in the reboot menu to boot into download mode ...

 

[FreeRunner2017]

I do it this way too, but for c) and d) I just select "download" in the reboot menu to boot into download mode ...

How come this ROM won't boot with patched linage recovery?, just bootloops.

 

[modpunk]

How come this ROM won't boot with patched linage recovery?, just bootloops.

Why do you patch the recovery?

 

[FreeRunner2017]

Why do you patch the recovery?

I use patched lineage recovery from Ivan_meter I can't get patched magisk boot to work.

---------- Post added at 08:59 AM ---------- Previous post was at 08:56 AM ----------

I got a weird issue with all ROMs, I can't boot any rom unless I use button combo. Even if I have stock, the stock bootloader says BL: recovery mode set by key.

 

[modpunk]

I use patched lineage recovery from Ivan_meter I can't get patched magisk boot to work.

---------- Post added at 08:59 AM ---------- Previous post was at 08:56 AM ----------

I got a weird issue with all ROMs, I can't boot any rom unless I use button combo. Even if I have stock, the stock bootloader says BL: recovery mode set by key.

Why don't you just flash the magisk boot image? Maybe start with reading the FAQ on the first page!

 

[FreeRunner2017]

Why don't you just flash the magisk boot image? Maybe start with reading the FAQ on the first page!

I do that but I reboot, but I have to push the 3 buttons to boot the phone.

 

[modpunk]

I do that but I reboot, but I have to push the 3 buttons to boot the phone.

You said you patched the recovery. That's not the magisk boot image we provide. Did you read the FAQ?

 

[stm8923]

I do it this way too, but for c) and d) I just select "download" in the reboot menu to boot into download mode ...

ok, thank you. The standard update is clear now.
My original question #1076 was about integration of Magisk-Image in the upgrade procedure:
After flashing lineagos in recovery. Can I flash the Magisk-patched Image in recovery to boot partition.
After this flash the new firmware in download mode with heimdall without the "--BOOTLOADER sboot.img" (because this has already been done in recovery with the Magisk-patched Image).

 

[xawex465]

Great job, amazing rom

 

[Phosphoros]

Hey modpunk,

is it possible to sync the source code for building your rom via the repo command to a specific released version (like 1.3)? I don't see any tags in the git repo, but maybe that's not the right place to look?

Regards,
Phosphoros

 

[Phosphoros]

Another question:

When executing

./extract-files.sh /path/to/mounted/system.img

(I downloaded and extracted the firmware and desparsed the filesystem-images), I get the following error for init.rilmptcp.rc:

./extract-files.sh /mnt/tmp
Cleaning output directory (./../../../vendor/samsung/beyond0lte/proprietary)..
Extracting 90 files in ./proprietary-files.txt from /mnt/tmp:
  - system/etc/init/init.rilmptcp.rc
    !! system/etc/init/init.rilmptcp.rc: file not found in source

In the file proprietary-files.txt the line for init.rilmptcp.rc is:

init.rilmptcp.rc:system/etc/init/init.rilmptcp.rc

And the file inti.rilmptcp.rc is there (in the system.img root directory), just not in the directory system/etc/init.

So: what does the line in proprietary-files.txt do - why is there a colon between the two locations? And how is it possible to get around the error properly?

[EDIT]
Apparently the path after the colon should be the destination (see https://wiki.lineageos.org/proprietary_blobs.html ), but apparently this does not work correctly (my build fails if I ignore the error).

Thanks,
Phosphoros

 

[FOLOL2011]

Did you format the data partition after you installed TWRP?

Yes I formatted my data partition when I installed LOS (post #3 Format data (wipe->format data, use the dedicated button, wipe->advanced does not work) )
I have Magisk and played with Magisk Hide props device fingerprint so I wonder if's a consequence

 

[counti]

Is it "normal" that during Always on Display and e.g. also in Telegram Chat a small dot in the status bar in the upper right corner of the battery percentage display blinks constantly? Is this the Proximity Sensor? I don't know if I always had it or since which version. I now have the latest version 1.3 with up-to-date drivers.

Also I can't backup the data partition with TWRP.

 

[Keule-T]

[...] Is this the Proximity Sensor? [...]

Yes

 

[counti]

But a bug when it blinks almost constantly?

 

[Keule-T]

But a bug when it blinks almost constantly?

No.
Well, you might consider it a bug, but it's the same with every LineageOS (based) build for S10* I know of.

 

[counti]

TWRP Backup of Data

No.
Well, you might consider it a bug, but it's the same with every LineageOS (based) build for S10* I know of.

Ok, thank you.

And what is with TWRP Backup of Data? I have in the middle of backup a Error 255, in the Log file i can see it's a problem with /system_ce/0.

 

[Keule-T]

Ok, thank you.

You're welcome. You could hit the thumbs up button if it helped, but nevermind.

And what is with TWRP Backup of Data? I have in the middle of backup a Error 255, in the Log file i can see it's a problem with /system_ce/0.

Dunno, do I? That's a twrp question, by the way, and definitively unrelated.

 

[Sebasss2683]

TWRP data fails & bootup fail

Good day,

After using v1.2 I wanted to update to v1.3.

I flashed all firmware files necessary, flashed ROM into latest TWRP of modpunks img.

It worked and all, so after that I need to boot magisk img . So I dowloaded latest magisk boot from forum & put in into boot section of twrp, after this lineage logo flashes and randomly turns off my device ( S10E ). When I try to bootup my phone again same thing happens.

Also I can't make backups in latest TWRP ( versions v1.2 & v1.3 ).

Regards

 

[WalterCool]

Another question:

When executing

./extract-files.sh /path/to/mounted/system.img

(I downloaded and extracted the firmware and desparsed the filesystem-images), I get the following error for init.rilmptcp.rc:

./extract-files.sh /mnt/tmp
Cleaning output directory (./../../../vendor/samsung/beyond0lte/proprietary)..
Extracting 90 files in ./proprietary-files.txt from /mnt/tmp:
  - system/etc/init/init.rilmptcp.rc
    !! system/etc/init/init.rilmptcp.rc: file not found in source

In the file proprietary-files.txt the line for init.rilmptcp.rc is:

init.rilmptcp.rc:system/etc/init/init.rilmptcp.rc

And the file inti.rilmptcp.rc is there (in the system.img root directory), just not in the directory system/etc/init.

So: what does the line in proprietary-files.txt do - why is there a colon between the two locations? And how is it possible to get around the error properly?

[EDIT]
Apparently the path after the colon should be the destination (see https://wiki.lineageos.org/proprietary_blobs.html ), but apparently this does not work correctly (my build fails if I ignore the error).

Thanks,
Phosphoros

The problem is system.img by default has very restrictive access to /system/etc/init.init.rilmptcp.rc and the script isn't able to fetch that file (unless you are root). You must give a better permission to that file on your mounted path (/mnt/tmp/system/etc/init.init.rilmptcp.rc) like +r or something it allows your user to read the file.