[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] medoko:
UPDATE 1: This is a installation guide if you re coming from stock rom and was written for the november release of Ivans LOS 17. It should still work - but double check download links and use the right (latest!) firmware

UPDATE 2: I also did a update from Ivans november release (LOS 17) to the februar realease (LOS 17.1) with BSKO firmware. If you are interested - heres my guide: https://xdaforums.com/showpost.php?p=81740475&postcount=533

Hi there!

Successfully installed this LOS 17 ROM from a stock (untouched, unrooted) S10 with Android 9.

The XDA forum helped me A LOT (!) with this (and past) projects with custom ROMs.

So i thought, i give something back. The least bit i can do, is post my steps, which gave me full LineageOS 17 (Android 10) on the S10.

Thanks Ivan Meler for your great work.

My steps to LOS17:

1. unlocked bootloader with this instructions (from John Wu - https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)):

-Allow bootloader unlocking in Developer options → OEM unlocking

-Reboot your device to download mode. Either use adb reboot download, or use the key combo (VolDown+Bixby and parallel quickly inserted (connected) USB cable!) for your device.

-Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot. Wait for device to do its thing...

-Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!

-Enable developer options, and confirm that the OEM unlocking option exists and grayed out! The VaultKeeper service will unleash the bootloader after it confirms that the

user has the OEM unlocking option enabled.

>>>Your bootloader now accepts unofficial images in download mode.

2. A i had the wrong firmware version, i updated firmware from ASJG down to ASIG (check baseband which firmware you have)

If you search for downloads of firmware: I used updato.com as sammobile.com was down for some reason. As XDA is writing some (neutral) things about Updato.com - i thought they should be reliable for downloading. Hope so.... I could not manage to find another source of a past (old) firmware...

With these instructions (in German only sorry): http://android-hilfe_de/forum/root-...einer-firmware-mit-odin-4-teilige.907406.html

3. TWRP installation:

(Ianmacd s thread: https://xdaforums.com/galaxy-s10/development/recovery-twrp-3-3-0-galaxy-s10-exynos-t3924856))

Since i had a "untouched" S10, i followed the sentence from Ianmacd ([RECOVERY] [OFFICIAL] TWRP 3.3.1 for Galaxy S10 Exynos [G970F/G973F/G975F/G977B]) :"

If your device is currently still unrooted and running stock firmware, you are strongly advised not to proceed with installing TWRP. First root your device with Magisk, using John Wu's excellent Samsung system-as-root-instructions " (again see John Wus instructions https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)

I first did not understand, why i had to install Magisk, but you have to install Magisk, in order to get a proper working TWRP

Here s the instruction i followed ( from John Wu):

-Download the firmware for your device.

-Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5

-Install the latest Magisk Manager (the Manager, not Magisk itself) on your mobile phone

-In Magisk Manager go to "Install Magisk": Install → Install → Select and Patch a File and select the AP tar file.

Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar

-Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not (!) use MTP as it is reported to corrupt files.

-Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files.

Never flash only an AP file, as Odin can shrink your /data file-system if you do.

Important: Uncheck “Auto Reboot” in Options!

Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.

We now want to boot into the stock recovery to factory reset our device:

-Full data wipe is mandatory! Do not skip this step.

-Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby +

Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.

Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.

-This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning

screen, release all buttons so it can boot to the system.

-The device will automatically reboot for the first time it boots. This is completely normal and done by design.

-After the device is booted up, do the usual initial setup. The following steps will need an internet connection.

You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded in step 3 and continue to the next step. The app would be a stub and it shall

automatically upgrade to the full Magisk Manager when you open it.

Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.

Voila! Enjoy Magisk :)

But still some steps on the way to TWRP!

- Jump back to https://xdaforums.com/galaxy-s10/development/recovery-twrp-3-3-0-galaxy-s10-exynos-t3924856) and proceed with "Image preparation".

Again use Magisk to patch a second file - this time the (correct for your device) TWRP by "ianmacd"

- Like before, patch the TWRP file with Magisk, save it onto a SD card (as MTP is corrupting files maybe)

- Convert this file with these two (Linux) terminal commands from .img to .tar (as Odin tool needs this file format):

$ mv magisk_patched.img recovery.img

$ tar cf new_patched_with_magisk_file.img.tar recovery.img

(or search for a windows solution to convert the "magisk_patched.img" to a Odin usable .tar file)

- Flash this .tar file with Odin tool as "AP"

- Reboot to TWRP (Hold "Vol. Up" + "Bixby" + "Power Button" as long as TWRP turns up)

Proceed with Ivan s instructions from post #1:

4. Flash Multi-Disabler (https://xdaforums.com/galaxy-s10/sa...xynos/g97xf-multi-disabler-encryption-t391971)

- flash it with TWRP with "install from ZIP"

- format DATA (in TWRP) - no reboot needed this time!

- wipe "cache", "dalvik" and "system"

5. Flash "Vendor Image" (from Ivan) you can find vendor image inside of a zip in the same folder on mega that contains the ROM

- Once you have downloaded vendor zip file extract it from zip and in twrp select Install Image

- Select Image file and flash it on vendor partition

6. Flash LineageOS 17 (i used "lineage-17.0-20191126-UNOFFICIAL-beyond1lte.zip") from Ivans Mega-Share

- Install ZIP he provides to download

7. You want Gapps? Install it now. Use BitGapps or whatever you prefer...

8. Reboot device

Now you should have a working LOS 17 with TWRP (Magisk is not active in my case, as i did not choose to install Ivan s "Magisk patched ROM" - if you need Magisk - install this patched ROM)

As only TWRP > or < Magisk can exist besides LOS 17 (this will change with next release of Ivan as he announced prviously) i choose to go with TWRP and wait for the next release...

Conclusion:

Read, read and read all of the content - also in linked sites/threads as this will give you all information you need. Because i read a lot, i identified some parts (even if they are described pretty good) which would have brought me into trouble. In the end i could search for solutions and managed to get it done...

This ROM installation is getting complex. I m using ROMs for nearly 7 years now and installed a lot of them. But Samsung ROMs (TWRP, Magisk, ROM) are getting harder and harder to install.

Thanks again Ivan - great work!