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

[modpunk]

Hi @modpunk,

trying to build an LOS based ROM using your github repos (thanks a lot for your work btw).

All went fine for S10 and S10e. But for the S10+, I am facing the issue below:
https://del.dog/alofeethyp.txt

Seems a vendor file is needed, but it's not existing on your Github (did not find in any other github repo).

Could you please help me get through this issue?

Thanks,

Edit: I found it in the vendor partition of your zip. But I guess this is not an elegant method.....

Edit 1: I also noticed that on the builds I've made, my vendor.img are much smaller than in your builds. Is it normal?

Edit 2: Even for beyond2lte, for which before building, I copied the entire vendor content into my build directly under /vendor/samsung/beyond2lte/proprietary/vendor (up to 390Mo). But in my zip, final vendor.new.dat.br is about 17.4M only.

I mount system and vendor from stock and copy the files to a directory then turn ./extract-files.sh /path/to/system

 

[Anghirrim]

I mount system and vendor from stock and copy the files to a directory then turn ./extract-files.sh /path/to/system

Thanks, that's what I did (with your LOS zip) but with partial luck. The output vendor files in my final zip file are smaller than yours.

Just for the sake of clarity. If I understood well.

If I sync your sources (kernel, device and vendor), it is not enough? I still have to run extract-files.sh?

And if yes, just to be sure, what is exactly /path/to/system? You mean the root of my build directory. Right?

Thanks again for your time and help.

 

[stm8923]

Flashing just those few files for a necessary firmware upgrade might not be enough if you come from a stock rom with locked bootloader. Best solution would be now to reflash the whole rom, boot into the phone, unlock the bootloader, and installing LOS as per instructions. As it seems that you're using Linux, Virtualbox is working just fine for flashing the stock rom to a Samsung phone. You need to set up your virtual machine with USB3 support enabled for the guest OS. Then install the Samsung USB drivers. It works, I did it a few times already.

Cool, thank you
The solution was to install the Oracle-Extension-pack for Virtualbox and enable USB3!
Now Odin connects to the S10

 

[guguxfr]

In the installation instruction #3 I read: first check and update firmware to the correct one. So I neither opened the bootloader nor installed los....

Ah ok, I get it.
Which version did you have before ?
Maybe try to reflash the version you were having with heimdal ?
On my side I did it with previous version.

 

[stm8923]

Ah ok, I get it.
Which version did you have before ?
Maybe try to reflash the version you were having with heimdal ?
On my side I did it with previous version.

Hey, thank you for your help. I solved the issue.

Starting with an original Firmware I flashed the required firmware for los, described in #3. There had been missing some parts to flash, so my device went broken.

Finally I got Odin working in a Visualbox Environment and could flash the whole firmware. Now everything is fine

 

[guguxfr]

That's good news. Happy to help !

 

[modpunk]

New release is up!

 

[angela5246]

@modpunk, thanks for the update!

What would actually happen in terms of firmware updates if LOS gets official for the S10? I mean how would that be solved? As of now, we need to flash that manually with every new release you provide. How would that be automated later?

 

[trancinguy]

Hi, always on still missing, and cannot be turned off, beyond 2

edit. found it, AOD has to be added to tiles.

 

[hamzih]

Can you increase the always on display brightness?

 

[[Legenda]]

Can we disable "always on" mode please? I Found the option but don't work at all !

 

[trancinguy]

;83935951]Can we disable "always on" mode please? I Found the option but don't work at all !

Add the tile, then see that it is not high lighted, turned on.

 

[[Legenda]]

Add the tile, then see that it is not high lighted, turned on.

Sorry, I dont' understad what you mean.

 

[trancinguy]

;83939083]Sorry, I dont' understad what you mean.

The tile on the far right, add it and then deactivate.

 

[[Legenda]]

The tile on the far right, add it and then deactivate.

Perfect thanks a lot !

 

[stm8923]

Update to new Firmware/lineageos

Hello,
I am now on lineagos v1.2 with firmware DTI8 and Magisk.

Is it a valid update procedure like this:
1. Reboot to Recovery an flash new lineageos (v1.3) like #3 "How do I update LineageOS?"
2. Flash Magisk-Image to boot partition (with the patched Magisk-Image of #3 "How do I install Magisk?")
3. Reboot to download and flash with heimdall (without the --BOOTLOADER sboot.bin, this has already flashed with Magisk in step 2 ) like #3 "How do I update the firmware manually?"
4. Reboot to System

All the steps will be:
x Backup all important files optional, but very helpful if something goes wrong)
x Remove any pin/password/pattern to prevent "retry after 86400 seconds"
x Copy the ROM ZIP file an external SD card or internal storage; download the new firmware files to PC (if needed)
x Boot into the recovery, do not reboot until you've installed the new ROM and firmware
x Flash the ROM (install -> select storage -> micro SD card and select the .zip file)
x Flash the Magisk Boot Image to BOOTLOADER inside recovery-mode
x Wipe dalvik and cache
x Reboot to download
x Flash new firmware with instructions:

heimdall flash     --PARAM param.bin --UP_PARAM up_param.bin --CM cm.bin \
                               --KEYSTORAGE keystorage.bin --UH uh.bin --DTB dt.img \
                               --RADIO modem.bin --CP_DEBUG modem_debug.bin

(Missing --BOOTLOADER, has already benn flashed with Magisk-Image)
x Reboot to system

Thanks
Martin

 

[Keule-T]

Hello,
I am now on lineagos v1.2 with firmware DTI8 and Magisk.

Is it a valid update procedure like this:
1. Reboot to Recovery an flash new lineageos (v1.3) like #3 "How do I update LineageOS?"
2. Flash Magisk-Image to boot partition (with the patched Magisk-Image of #3 "How do I install Magisk?")
3. Reboot to download and flash with heimdall (without the --BOOTLOADER sboot.bin, this has already flashed with Magisk in step 2 ) like #3 "How do I update the firmware manually?"
4. Reboot to System
[...]
Thanks
Martin

First you update the firmware, then you flash the images. If you do it the other way around the installation will be aborted.

 

[stm8923]

First you update the firmware, then you flash the images. If you do it the other way around the installation will be aborted.

Thank you for your response. But #3 "How do I update LineageOS?" describes a diffrent approach:
First flash lineagos and then without System-reboot flash the firmware...???
Which one correct?

 

[Keule-T]

Thank you for your response. But #3 "How do I update LineageOS?" describes a diffrent approach:
First flash lineagos and then without System-reboot flash the firmware...???
Which one correct?

Well yea, you're right. Maybe I remembered wrongly, and it doesn't abort the installation but hangs in a bootloop without the new firmware.

 

[wora92]

Thank you for your response. But #3 "How do I update LineageOS?" describes a diffrent approach:
First flash lineagos and then without System-reboot flash the firmware...???
Which one correct?

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.