yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] f.silva:
Good news everyone. I got it!! Was doing 2 things incorrectly in case anyone needs to know:

1. My carrier is Cricket. Just needed to move the sim card over to the new phone and after a few mins and it worked fine. No activation needed as long as it's the same number. That was too easy.

2. The bootloader was not properly unlocked because of a missed a step. After unlocking the first time in Dev Options, I wasn't holding down the vol up button to finish unlocking the bootloader when entering download mode. Once done, the phone reset again and the Bootloader option was then grayed out. It literally took 30 seconds to flash TWRP and another minute for both LOS and Gapps via TWRP. What made it frusting about resetting this particular phone, is that it defaulted to Korean language so I had to learn how to skip thru the initial setup quickly and go into settings to swap back to English. Fun stuff LOL

I'm one happy campah right now :D :D :D :D
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AndrOdin:
When you insert a sim card, the phone automatically registeres on the GSM network, and it updates the Android clock. So yes, a regisration is needed :cowboy: :good:

Glad to know that :victory:

Thanks to [MENTION=4297219]modpunk[/MENTION] for making it all possible :cool::highfive:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
Is it possible to run a C-program from the TWRP terminal? I tired and I get a "No such file or directory". Currently I trying to get a simple Hello World program to run to see if it's possible. Any help would be appreciated.

Thanks
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Yes, it is. Just build it for android, copy it to the device and run it.

adb push /path/to/mytool /tmp
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
*deleted*
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
Building the Wurst TWRP

I'm trying to build this version of TWRP to see if I can do it. Here are my steps. It's not building because I keep getting errors after my lunch statement

Here is the error

error: Product "omni_beyond1lte" ambiguous: matches device/beyond1lte/omni_beyond1lte.mk device/samsung/beyond1lte/omni_beyond1lte.mk.

Here are my steps,

What am I missing/messing up?

1 Create a folder, then go into it

$ mkdir twrp

$ cd twrp

2 To initialize a shallow clone

$ repo init --depth=1 -u https://github.com/omnirom/android.git -b android-10

3 Add remotes to .repo/manifests/omni-aosp.xml

<remote name="TeamWin" fetch="https://github.com/TeamWin" />

<remote name="beyond1lte" fetch="https://github.com/whatawurst"/>

4 Add needed repos into .repo/manifests/omni-default.xml

<project path="bootable/recovery" name="android_bootable_recovery" remote="omnirom" revision="android-9.0"/>

<project path="device/samsung/beyond1lte" name="android_device_samsung_beyond1lte" remote="beyond1lte" revision="twrp-9.0"/>

<project path ="external/magisk-prebuilt" name="external_magisk-prebuilt" remote="TeamWin" revision="master"/>

5 Comment out the following

bootable recovery in .repo/manifests/default.xml because it is now a duplicate

omni-private.xml in the .repo/manifests/omni-default.xml

6 Then sync

$ repo sync

7 Then to build:

$ cd <source-dir>;

$ export ALLOW_MISSING_DEPENDENCIES=true;

$ . build/envsetup.sh

$ lunch omni_beyond1lte-eng

$ mka recoveryimage
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
I just tried to use TWRP with my FDE encrypted version of ivans LOS 17.1 without success. Instead of a prompt to enter the password to decrypt the partition I see an error message that /data could not be mounted as it was to be expected if FDE is not supported.

Are there any further steps necessary to make it work or was you post just a typo and you meant FBE to be working by the time of writing ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
Not sure if you can mount it in TWRP. But anyways you need to use your old fstab to be able to boot. The fstab that comes with Modpunks LOS is not working if you have been using Ivan Melers LOS with FDE before.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
a) Use https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni

b) Sync twrp-9.0 (twrp-10.0 is not ready yet!)

c) Sync beyond1lte (uses the twrp-9.0 repo)

d) extract blobs

c) lunch ...

There is no need for Magisk, you can just flash a boot image provided for LinegeOS with Magisk included.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
You currently cannot mount it in TWRP which is the problem with it :)

On my Galaxy S7 for instance I can use the latest TWRP version 3.3.1 togther with LOS 17.1 and have full FDE encryption support. When booting into recovery TWRP asks me for the password to decrypt and sucessfully mounts the data partition.

Just to be clear, I am not confused between the two LOS projects being developed at the moment and I am fully aware, that modpunks LOS implementation supports FBE and Ivans FDE (with additional steps).

In the end FBE is the less secure concept though it has advantages in terms of usability. Only FDE ensures that all data is securely locked away if the partition is not decrypted in full. No way to run programs as User0 without decrypting etc.

Without FDE support in TWRP, after encrypting your device, there is literally no way of upgrading your LOS version anymore since you are not able to mount /data in recovery.

So my question is if there is any chance to have that functionality available in TWRP for S10x ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
Yes, being not able to mount /data within TWRP is a problem for some use cases. However, it's not a problem in regard of updating LOS. Of course you can update LOS even if you have FDE or FBE enabled. Because the update only touches /system.

In regard to the debate FBE vs. FDE. Both have their advantages and disadvantages. Even security researchers are not agreeing on what to use. For a nice debate you might want to have a look here: https://blog.cryptographyengineering.com/2016/11/24/android-n-encryption/
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
FBE is not less secure than FDE and has been improved a lot in the last year. The next Android version will support for inlinecrypt, this means it can offload encryption and our device supports that already. This will make storage access a lot faster.

See https://source.android.com/security/encryption/file-based
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
Well, I guess that depends on the point of view you have on that and usually leads to an endless debate :)

Just two thoughts from my side:

1. FBE supports direct boot which is meant to enable direct boot aware applications to be able to run without the need to decrypt anything.

That is actually not an advantage it is risk for data and privacy. Imagine direct boot aware alarm clocks revealing personal information on the lock screen connected with the alarm or your favourite network operator app being able to spy on you directly on startup or, or...

2. Though the data files of apps are encrypted on a per folder basis there is still a lot of meta data available just by seeing the folder structure and understanding which apps are installed etc.

=> Only a fully encrypted device can pervent anyone or anything (=app) from accessing (meta-)data or being operable without proper decryption which is in this case the ultimate legitimatisation.

Yep, multiuser situations with individual keys are not possible and it might me less performant... Okay, for the multiuser part I could imagine some usecases (family tablet etc.) but the performance argument is not really one. We are talking here about making that ferrari go 320km/h instead of 312km/h while we are driving mostly 80km/h during daily operation.

Don't get me wrong, everyone can use FBE and be happy with that. I just was asking if it is possible to include dmcrypt support in TWRP for those who prefer to use FDE for what ever reason.

Cheers.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Wether FDE or FBE is used, is a mount option in fstab. You would need a new TWRP for that which has the right fstab. At least I'm not aware of another way.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
Wouldn't it be a nice step to retrieve the fstab from the vendor partition of possible and just use the default one if not available ?

That way modifications to the vendor fstab which is necessary for FDE to work under LOS17.1 are automatically recognized and used. If the current TWRP implementation would read the option "encryptable=footer" instead of "encryptable" would it work right out of the box ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I'm looking forward to a patchset for TWRP which supports this :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
I built your TWRP from source. In the out directory was the recovery.img file. I bundled that with your vbmeta.img into a .tar file and flashed that to my rooted and unlocked S10 using ODIN. Here is the error I am getting. Any idea what I am doing wrong. I have flashed on your release versions with no problems. Thanks for any help

BIN MODE (DT Load Fail)

[OTH] dt table header check Fail: <unknown error>

load_kernel: Could not do Normal boot (DT LOAD Fail)

vbmeta: Error verifying vbmeta image OK_NOT_SIGNED (3)

CUSTOM VBMETA

VBMETA : No Sign info

VBMETA .
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Looks like something is wrong with the recovery.img it looks like it can't find the dtbo image.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
[MENTION=4297219]modpunk[/MENTION], would you take a look at my fstab? Do you see any reason why your TWRP is not able to mount /data? As you can see, I am using FDE. Thanks

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#/dev/block/platform/13d60000.ufs/by-name/system	/system ext4 ro wait
#/dev/block/platform/13d60000.ufs/by-name/vendor	/vendor ext4 ro wait
/dev/block/platform/13d60000.ufs/by-name/cache	/cache	ext4	noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic	wait,check
# /dev/block/platform/13d60000.ufs/by-name/userdata	/data	ext4	noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic	wait,check,fileencryption=ice,quota,reservedsize=128M,length=-20480
/dev/block/platform/13d60000.ufs/by-name/userdata	/data	ext4	noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic	wait,check,encryptable=footer,quota,reservedsize=128M,length=-20480
/dev/block/platform/13d60000.ufs/by-name/efs	/mnt/vendor/efs	ext4	noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic	wait,check
#/dev/block/platform/13d60000.ufs/by-name/persistent /mnt/vendor/persist ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic wait,notrim
/dev/block/platform/13d60000.ufs/by-name/misc /misc emmc defaults defaults
#/dev/block/platform/13d60000.ufs/by-name/recovery /recovery emmc defaults defaults

# VOLD:fstab.beyond2lte
/devices/platform/13d00000.dwmmc2/mmc_host* auto auto default voldmanaged=sdcard:auto
/devices/platform/10c00000.usb* auto vfat default voldmanaged=usb:auto

# Samsung ODE
# /dev/block/platform/13d60000.ufs/by-name/keydata	/keydata	ext4	noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic	wait,check,fileencryption=ice,nofail
/dev/block/platform/13d60000.ufs/by-name/keydata	/keydata	ext4	noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic	wait,check,encryptable,nofail
# /dev/block/platform/13d60000.ufs/by-name/keyrefuge	/keyrefuge	ext4	noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic	wait,check,fileencryption=ice,nofail
/dev/block/platform/13d60000.ufs/by-name/keyrefuge	/keyrefuge	ext4	noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic	wait,check,encryptable,nofail
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
You need to modify the fstab of TWRP and rebuild the recovery. The file for the recovery is here:

https://github.com/whatawurst/andro...9820-common/blob/twrp-9.0/recovery/twrp.fstab
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
[MENTION=4297219]modpunk[/MENTION] Here are the steps I am using to build you TWRP. I think what I am puting in the manifest.xml might not be correct. What do you think?

1. To initialize a shallow clone

repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-9.0

2. Add to the .repo/manifest.xml

<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-17.1" />

<project name="LineageOS/android_device_lineage_sepolicy" path="device/lineage/sepolicy" revision="lineage-17.1" remote="github" />

<project name="LineageOS/android_device_samsung_slsi_sepolicy" path="device/samsung_slsi/sepolicy" revision="lineage-17.1" remote="github" />

<project name="Linux-4/android_vendor_samsung_beyond1lte" path="vendor/samsung/beyond1lte" revision="lineage-17.1" remote="github" />

<project name="whatawurst/android_device_samsung_beyond1lte" path="device/samsung/beyond1lte" remote="github" revision="twrp-9.0"/>

<project name="whatawurst/android_kernel_samsung_exynos9820" path="kernel/samsung/exynos9820" remote="github" revision="twrp-9.0" />

<project name="whatawurst/android_device_samsung_exynos9820-common" path="device/samsung/exynos9820-common" remote="github" revision="twrp-9.0" />

3. Then sync

repo sync

4. Then to build:

cd <source-dir>;

export ALLOW_MISSING_DEPENDENCIES=true;

. build/envsetup.sh

lunch omni_beyond1lte-eng

mka recoveryimage
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Should be .repo/local_manifest/roomservice.xml

All you need is

<project name="whatawurst/android_device_samsung_beyond1lte" path="device/samsung/beyond1lte" remote="github" revision="twrp-9.0"/>

Then lunch should get the required repositories for you. I think I should write a README.md to document the steps ...

cd device/samsung/beyond1lte

./extract-util.sh /path/to/unpacked/stock-rom/
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Joel2701:
Dos this recovery work With CTD1? In may patch?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
Yepp.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
[MENTION=4297219]modpunk[/MENTION] I built this TWRP based on you recommendations. I was able to build it successfully. I created a tar file with the recovery image and your vbmeta image. When I try to flash it on using ODIN. When the phone restarts it goes back to download mode with this message. Any idea what it means? Thanks

BIN MODE (DT Load Fail)

[OTH] dt table header check Fail: <unknown error>

Load_Kernel: Could not do Normal boot (DT LOAD Fail)

vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED (3)

CUSTOM VBMETA

VBMETA : No sign info

VBMETA .
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Did you also falsh a vbmeta-disabled?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
Building What a Wurst! TWRP

I verified that vbmeta-disabled.img has the same MD5 hash.

I renamed vbmeta-disabled.img to vbmeta.img and I TAR'd that and recovery.img into TWRP.tar file. (So TWRP.tar only has two files vbmeta.img and recovery.img). I used ODIN to flash TWRP.tar. After restating the phone it boots back to Download mode. Unfortunately I get the same error message displayed on the Download Mode screen

Error verifying vbmeta image OK_NOT_SIGNED (3)

I also tried flashing the original TWRP to the phone, then flash multidisabled-samsung-2.3.zip, then flash vbmeta-disabler.zip, then finally flash your TWRP.tar over the original TWRP. Now the phone only boots into TWRP.

I'm sure I am missing one step to build and flash your TWRP. Any additional help would be appreciated.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
You really have an unlocked bootloader?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
Did you extract the recovery IMG after download?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
I do not need to extract the recovery.img file because I'm trying to build this TWRP from source.

---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------

The bootloader is unlocked and I have root privileges from installing Magisk.

What are your steps to build this TWRP project so I can build it for my self?

Thanks.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
The build steps are documented here: https://github.com/whatawurst/android_device_samsung_beyond0lte/tree/twrp-9.0

Are you sure the recovery.img is correct? Did you inspect the boot image? The android source comes with a unpack_bootimg.py ...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
Building TWRP

[MENTION=4297219]modpunk[/MENTION] Here are the steps I take to build this TWRP and the three errors I encounter.

Initialize the repo:

repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-9.0

Create a local manifest:

vim .repo/local_manifests/roomservice.xml

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="whatawurst/android_device_samsung_beyond0lte" path="device/samsung/beyond0lte" />

</manifest>

Sync the repo:

repo sync

Error 1:

After the repo sync I get an error

Checking out projects: 4% (9/224) platform/dalvikerror: Cannot checkout whatawurst/android_device_samsung_beyond0lte: ManifestInvalidRevisionError: revision refs/tags/android-9.0.0_r47 in whatawurst/android_device_samsung_beyond0lte not found

error: in `sync`: revision refs/tags/android-9.0.0_r47 in whatawurst/android_device_samsung_beyond0lte not found

Error 1 fix:

I changed the <project> tag to

<project name="whatawurst/android_device_samsung_beyond0lte" path="device/samsung/beyond0lte" remote="github" revision="twrp-9.0"/>

Extract vendor blobs

cd device/samsung/beyond0lte

./extract-files.sh

Error 2:

Some of the blobs will not transfer because you need permission to move them.

Error 2 fix:

I copied them manually one by one based on what is in the proprietary-files.txt, proprietary-files-twrp.txt, and proprietary-files-vendor.txt

Then put them in the correct place.

Setup the environment

export ALLOW_MISSING_DEPENDENCIES=true

source build/envsetup.sh

lunch lineage_beyond0lte-userdebug

Error 3

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_beyond0lte".

Lunch gives these options, none of them is lineage_beyond0lte-userdebug

Lunch menu... pick a combo:

1. aosp_arm-eng

2. aosp_arm64-eng

3. aosp_mips-eng

4. aosp_mips64-eng

5. aosp_x86-eng

6. aosp_x86_64-eng

7. omni_emulator-userdebug

Error 3 fix

I don't know what to do here. Does anyone have any idea? Are there previous 2 error fixes correct?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Meemo23:
This is the only recovery that works and goes to the menu but the recovery thinks my S10 plus is a Beyond1lte when it is a Beyond2lte and gives me error 7 saying this device is not a beyondlte2 device to flash your Beta 2 for the samsung galaxy s10 plus and I cannot flash any other firmwares because it thinks it is a beyond1lte. Please can you help me.

Edit: never mind I am an idiot I figured it out sorry and thank you!!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I don't think that this will work. The script creates several .mk files. You can mount the images of the stock rom and copy together the tree and then run ./extract-utils.sh /path/to/rom/[/QUOTE]
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Donkeykong307:
How to build TWRP

Steps i used to build TWRP

Make a workspace:
mkdir -p ~/twrp/repo
cd ~/twrp/repo

Initialize the repo:
repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-9.0

Create a local manifest:
vim .repo/local_manifests/roomservice.xml

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="whatawurst/android_device_samsung_beyond0lte" path="device/samsung/beyond0lte" remote="github" revision="twrp-9.0" />
<project name="whatawurst/android_device_samsung_exynos9820-common" path="device/samsung/exynos9820-common" remote="github" revision="twrp-9.0" />
</manifest>

Sync the repo:
repo sync

Extract vendor blobs
cd device/samsung/beyond0lte
./extract-files.sh

export ALLOW_MISSING_DEPENDENCIES=true
source build/envsetup.sh
lunch omni_beyond0lte-userdebug <--- NOTE omni NOT lineage

mka recoveryimage
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Fixed, thanks
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JohnDandel:
Building TWRP

[MENTION=4297219]modpunk[/MENTION] [MENTION=7967411]Donkeykong307[/MENTION]

I finally built this project.

My issues was when I manually copied the proprietary files off the phone. I put two files in the wrong folder.

Now when I try to flash the TWRP.img file using ODIN, containing the recovery.img. and vbmeta.img file. I try to go into recovery mode, but the phone goes back to download mode with an error message

Error verifying vbmeta image: OK_NOT_SIGNED (3)

Any idea on this error?

I have noticed that there is a difference in file size between the one ModPunk built at 65,328kb and the one I built at 66,048kb. Any idea on this file size difference?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I've released a new TWRP. Update to 3.4.0 of TWRP and to the latest Linux Kernel we use in LineageOS. I also fixed a small adb bug.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
If you use lunch omni_beyond0lte-userdebug the recovery works but then you don't have access via adb. It throws you an error about vendor key not set.

If you want to have adb access you need to build like this:

lunch omni_beyond0lte-eng

---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------

I did. My twrp.fstab looks like this:

/data ext4 /dev/block/platform/13d60000.ufs/by-name/userdata flags=fileencryption=footer,length=-20480

However, logcat throws this error when I try to mount /data:

06-09 11:47:16.143 4983 4983 F linker : CANNOT LINK EXECUTABLE "/sbin/android.hardware.keymaster@4.0-service.samsung": cannot locate symbol "sk_pop_free_ex" referenced by "/sbin/libkeymaster_helper_vendor.so"...

What might be the reason for that? Could it have to do with the lenght?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Oh, you should throw out the keymaster and gatekeeper stuff in the init file.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
Not working on my s10+. Always get a error message while booting to recovery with invalid kernel length.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Ouch, that means that the the size is too big.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Could you test https://xor.cryptomilk.org/android/recovery.img.xz ???
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
Works without problems on my S10+
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
The same. Got the same error message. [MENTION=10682177]Stef4n82[/MENTION]

How do you flashed it?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
I flashed it with heimdall:

heimdall flash --RECOVERY recovery.img --no-reboot

Here you can see it is the 3.4.0:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
Didnt tried odin yet, but ive tried it directly in twrp and tried flashify, still the same.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] [Legenda]:
I tried with Odin. Impossible to me to update.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Uploaded new versions! Thanks for testing ...