yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
[RECOVERY][EXYNOS] TWRP 3.5.2_9 for S10e|S10|S10+ (UPDATE: 2021-06-07)

This project provides the TWRP recovery for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G975F, beyond2lte).

This recovery supports FBE decryption of AOSP based ROMs like LineageOS, OmniROM etc. There is no support for Samsung ODE in TWRP yet. If you're interested, help to provide it is welcome.

FEATURES

File-Based Encryption (FBE) support

MTP and ADB support

EXT4 support

F2FS support

EXFAT support

Provides unzip

Additional languages

KNOWN ISSUES

If you decrypt /data with TWRP, the trustzone thinks this is a failed unlock attempt and will lock the storage for 1d

'adb sideload' doesn't work

DOWNLOAD

Make sure you download the .img.xz and corresponding .asc.txt file (see INTEGRITY)! You can decompress the the recovery image using p7zip or xz.

You can always find the latest version of the recovery under the follwing links:

S10e

S10

S10+

INTEGRETY

The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.

How do you do that?

Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.

Download the recovery.img.xz and recovery.img.xz.asc.txt file

Rename the recovery.img.xz.asc.txt file to recovery.img.xz.asc

Verfiy the signature using the following command:

gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.xz.asc

A good tutorial is: How to verify signatures for packages from the Tor Project.

SECURITY ADVICE

Don't flash ROMs or Magisk modules which set SELinux to permissive or you open your device for malware!​

What a Wurst!

Contributors

modpunk, derf elot

Source Code: https://github.com/whatawurst/android_device_samsung_beyond0lte/tree/twrp-9.0

Version Information

Status: Stable

Current Stable Version: 3.4.0-0

Stable Release Date: 2020-06-12

Created 2020-03-16

Last Updated 2020-06-12
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
FAQ

How do boot into the bootloader/download mode?

Here are the steps:

Turn off your phone

Press and hold the volume down and bixby keys

Connect a USB cable attached to your computer

The 'Bixby' button is the button below the volume keys.

How do boot into recovery mode?

Turn off you phone

Press and hold the volume up and bixby and power key

You can also do the above when you reboot the phone, once the screen turn black press the buttons.

How do I reboot my phone?

Press and hold the volume down and power key for at least 7 seconds.

How do I unlock my device?

Not that if you unlock your device, your phone will be factory reset! Make sure to make backups.

To unlock your device:

Go to Settings -> About Phone and find the "Build Number"

Tab the build number several times till it tells you that you unlocked the Deverloper Settings

Go to Settings -> System -> Advanded -> Developer Settings

Enable "OEM Unlock"

Reboot to bootloader mode (see above)

Follow the instruction displayed on screen and unlock your device

How do I flash the recovery?

After you unlocked the bootloader:

Boot into download mode (see above)

Flash recovery.img and vbmeta-disabled.img using Odin or Heimdall.

What is VBMETA?

Your phone has a partition for storing cryptographic hashes to verify the validity of the flashed software to all the partitions on your system. This is called Android Verified Boot.

In order to flash a recovery.img you need to replace the VBMETA image with a custom image to disable the checks. You can find a vbmeta-disabled.img here.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
CHANGELOG

2020-07-24

Update to Linux Kernel 4.14.189

Updated to CTF3 blobs

Removed TWRP app

2020-06-09

Update to TWRP 3.4 (Fixes for SAR and multi user decryption)

Update to Linux Kernel 4.14.183

Fixed ADB only mode
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ExtremeGrief:
Good Job!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Thank you :)

I'm working on S10 and S10+.

If someone is interested to get it working with stock we could look into Samsung ODE. I don't need it for LineageOS.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ExtremeGrief:
I don't think TWRP supports Samsung FDE.

By the way for S10(+) just change kernel.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] stefan243546:
Alright so what are the differences between this and the already available twrp by ian?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
See the features list, this recovery has support for FBE decryption on AOSP based ROMs. Also USB is working correctly and not making your phone so hot that you can fry an egg on it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
It should be possible to format /data and use FDE encryption now.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
[MENTION=4297219]modpunk[/MENTION]

Thanks a lot. I was waiting for this for some time now.

Two questions:

1) FBE: Do i need to come from stock to have FBE working? Or is it ok to format /data from within TWRP to activate FBE with the right settings in fstab? I am using Lineage. Did you try that combination? I tried to keep FBE in the past but upon rebooting LineageOS TWRP kept stuck in the splash screen because it was not able to handle FBE.

2) Would it be possible to provide the build steps or would you consider pushing your work on FBE into the official repo? As i can see Ianmac's TWRP version isnt capable of dealing with FBE yet so it would be great to have it official.

Thanks for all your hard work. Much appreciated.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Normally, LineageOS sets up FBE by default if the fstab is configured to use FBE. I'm currently working on a LineageOS ROM for the S10e and FBE is working just fine. Normally all you have to to is to format /data. I dunno which ROM you're using and if it has FBE turned on by default.

Take a look at https://github.com/whatawurst and check the corresponding twrp-9.0 branches (Kernel, platform, device).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] angela5246:
I see.

So just for clarification: Do you say FBE should work in theory with LOS or did you try it actually? Let me tell you about my experience.

I came from stock to LOS 17 provided by Ivan. Kept the original fstab which has FBE enabled. Didnt format /data so FBE was kept. After flashing LOS from within TWRP i booted into LOS. All fine. But on the first reboot or shutdown the phone automatically goes to TWRP. And there it stucks at the splash screen. At that point only flashing to stock is helping. So Ianmac's TWRP is not able to handle FBE. Are you sure this is different with yours?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I've added TWRP for more devices.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
With the current release MTP isn't working. However I think I have a fix.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] mcgomfer:
Will this twrp work with one ui 2.1?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
I dont think so. But the ctc9 sources are up now.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Why shouldn't it work?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I don't see what the recovery has to do with CTC9 kernel sources at all.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I've uploaded new versions which fixes MTP.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lâm1990:
Can you support Note10+ devices?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Eidluci:
Can I just flash the .img using ian`s twrp since that I currently on it to make yours as the boot?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
You can flash the image to recovery slot with every twrp recovery. Or use flashify ro the twrp app.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Eidluci:
Thanks
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doublediamond:
When I check the integrity, I get:

Should that be the output?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lini-linux01:
3722

...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] slauzinho:
I think I got a problem, I'm stuck at teamwin logo when press vol down + power button it restarts and I get stuck again.

Since it auto boots into recovery and gets stuck in the logo I don't know how to get into Download Mode.

Anyone has any tips?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] funiewski:
Power off, vol- + Bixby + plug in your USB cable from your computer
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] slauzinho:
The thing is I can't power off my device. If I hold the power button it does nothing. If I press vol down + power button it restarts my phone.

I guess my only option right now is to let the battery drain and hopefully that way I will be able to go into download mode
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] funiewski:
When you restart you phone you have to be quick, still hold vol-, press bixby and plug in usb
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] slauzinho:
It worked! Guess I wasn't being quick enough previously.

Thanks :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
It says "Good Signature" :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doublediamond:
I Know but the warning confused me, thanks for clearing this up.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Cynalight:
Hey Everyone,

i dont really got how to Integrety works..... Can someone explain me? i also checked the Tor Link ... but still same knowledge to be honest..

Mod edit: "hide tags added"
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] GabrielSousa:
i this this steps

To flash modpunk's TWRP and vbmeta on S10e SM-970F Exynos international version, you need to:

1) Download the latest TWRP here.

2) Download vbmeta disabled image here.

3) Extract twrp-3.3.1-0-android-10.0-beyond0lte-5.img from the twrp-3.3.1-0-android-10.0-beyond0lte-5.img.xz with 7zip to fx. Desktop. 7zip can be found here.

4) Rename twrp-3.3.1-0-android-10.0-beyond0lte-5.img to recovery.img.

5) Rename vbmeta-disabled.img to vbmeta.img.

6) Place vbmeta.img in same place as recovery.img.

7) Open 7zip, and navigate to where vbmeta.img and recovery.img is placed.

8) Archieve vbmeta.img and recovery.img in one arhieve of .tar format (fx. TWRP.tar), and use "Compression level": Store.

9) Turn of your device

10) Press and hold the volume down and bixby (Not power!), and keep holding it, while connecting the USB cable between phone and PC.

11) When the download mode warning screen appear, release all buttons, and follow the instructions on the download mode warning screen.

12) Open up Odin3 v3.13.1 as admin, and you should se a message saying "Added" in the log, and a blue flag above ID:COM, together with a port number. Odin can be found here, or direct link here.

13) Press on AP in Odin, and navigate to where TWRP.tar is placed, and select it, so AP becomes checked, and the path to TWRP.tar is viewable in the AP slot.

14) Navigate to options in Odin, and make sure that "Auto Reboot" is NOT selected, and navigate back to the Log tab.

15) Press start to flash TWRP.tar.

16) When a success message is stated in the log, then exit download mode by pressing volume down and power.

17) When the screen turns of, you need to immediately press the recovery combo (VolumeUp, Bixby and Power), and keep holding it, until the secondary warning appears (The one with warning about unlocked bootloader), then release Bixby and Power, but keep holding volume up, until the TWRP logo is seen.

the phone is looping, how i go to the recovery ? PLEASE HELP

EDIT: i flash this one twrp-beyond2lte-3.4.0-3_ianmacd.img and now i can go to recovery :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ongxa:
Hi All:

Can this method can root model SM-G975N??? Thank you.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flotsch1:
i followed this great guide and could successfully flash twrp, lineagos and magisk. Unfortunatelly, in LOS fingerprint and selfie cam is not working, so i want to try another custom Rom or stock again.

As i am a noob to this, please excuse my stupid questions i have now. this 3 things are unclear to me:

If i want to switch to another custom rom (and have magisk), all i have to do is:

- go to twrp

- Wipe cache + dalvik, format data

- flash new rom

- Wipe cache + dalvik, format data

- optional: flash gapps

-reboot system

- install magisk manager apk

is this correct???

if i want to go back to stock:

do i have to flash full stock firmware via odin and start the steps of the guide from bulletpoint 1 again?

or can i flash stock OS via twrp? how? or via odin? if via odin, how can i kep magisk boot image wit vbmeta-disabled and twrp?

when having stock with twrp an magisk:

is it better to use this twrp (with vbmeta-disabled) or is it better to have ians twrp?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] PortentousLad:
Hi everyone,

Ran into some trouble and was hoping to find some help here.

I flashed twrp with Odin on my s10e, but must have f'ed up at some point.

I'm stick in download mode now, can't eben turn the device off without draining the battery. As soon as I plug in the charger it goes back into download mode again.

Is it possible to revert back to a stock bootloader somehow?

Any advice is appreciated.

PL
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] spartanz51:
Can we manualy mount /data encrypted with fstab "encryptable=footer" ? (without rebuilding TWRP with new fstab)

using something like :

mount -t ext4 -o 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/userdata /data

I can't understand how we can pass the password to decrypt files
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] nugeganteng:
Hello,

My twrp doesnt seem to recognize that i have PIN so the internal storage is encrypted and has folders with strange name
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] counti:
I have a problem 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.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
I also have the same problem of TWRP not recognizing that I have a PIN, and the internal storage remains encrypted (i can see folders with strange names).

I've been posting some messages about this problem on modpunk's LOS 17.1 post, and I've tried pretty much everything, but so far I've not been able to find the solution to allow TWRP to decrypt the internal storage :(

@nugeganteng Have you found any solution since last time you posted your message, in October ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
I guess your message is related to the same issue I'm experiencing. Have you found a way to pass the password to TWRP to decrypt the files ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doeternietoe:
I've been posting in the LineageOS 17.1 thread, along with

sappounet on a problem I have with twrp and which possibly relates to this.

In short: I have the latest version (3.4.0-0-android-10.0-beyond0lte-3) installed since august. I've used it regularly to update my ROM and backup my data. When I ran it earlier this week it didn't ask for my pin and will not decrypt my data. It can read /system just fine. I cannot for the life of me understand what's going on... :confused:

I've booted to recovery and from adb ran:

twrp decrypt ***password***

Result:

Attempting to decrypt data partition or user data via command line.
Failed to decrypt data.

Anybody any idea?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] iceyou:
I can't seem to be able to boot into this recovery, the device gets stuck on samsung boot screen, while i could do that with the official 3.3.1 one. Samsung Galaxy s10 exynos
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] VoLTz4Dayz:
No mirror found for the vbmeta-disabled.img download.

Thanks for fixing.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lakkimsetty.baba:
Below is some info on TWRP decryption issue. Relevant log:

I:Done processing fstab files
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:File Based Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false <- notice this?
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using SKeymaster(Keymaster MDFPP) from SKeymaster team for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: android.hardware.keymaster@4.0::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /data/unencrypted/key
upgrade_key failed, code -38
e4crypt_initialize_global_de returned fail
...
<repeating log message chunks, perhaps retries>
...
I:Trying wrapped key.
I:File Based Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = true <- property seem to change
Wrapped key supported on /data
calling retrieveAndInstallKey

The problem seems to be from Keymaster

This issues puts all of us in a tough spot; we can't take full backup and can't restore existing ones. Complete /data backups had saved me more number of times than I can count since the early beta stages.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lakkimsetty.baba:
I was able to build the recovery image from the source that modpunk has linked in the first post and decrypting works for v1.4 LOS 17.1 ROM. I used SM-G970F_TCE_G970FXXS9DTK9 firmware proprietary blobs. I haven't deep dived to see whats causing the problem, yet.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flortsch:
Nice! So you simply built the recovery and used that firmware in the "Extract vendor blobs" steps? Would be nice if you could share a flashable image :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] fishnetfancy:
thank you, @lakkimsetty.baba I looked at the Github page but it specifies Samsung S10e. Will this also work for S10+ if I build from source?

I have never done it and am wondering how to extract the proprietary blobs.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lakkimsetty.baba:
Hi @fishnetfancy, here is the source for beyond2lte. Sorry, I don't know for sure if it will work and I am unable to test it since I don't have an S10+, but I have faith it will work.

Here(1, 2) is some info, apart from S10e's readme file, on how to extract the blobs and build the image.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] fishnetfancy:
Thank you, @lakkimsetty.baba Whilst you answer is brilliantly helpful I am too unskilled to be attempting compiling the TWRP image at this point. There are too many hurdles for me right now - starting with my inability to mount the system.img and vendor.img files on Linux (I am a n00b, lol).

Seeing how much time I have wasted invested learning new things it is time to cut my losses and attempt a re-install of 1.0 with the option of later moving to 1.4
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] fishnetfancy:
As I am writing this @lakkimsetty.baba do you think it will be possible to install the 1.4 ROM and coresponding TWRP and later replace TWRP with one I have compiled myself in order to be able to decrypt /storage (enabling TWRP backups)?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lakkimsetty.baba:
Yes, I think it will work @fishnetfancy

I ended up uploading the S10e image on the ROM thread here. 😅
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flortsch:
Thank you for the links! I managed to build a recovery myself. Extracting the files from a firmware was not that easy. Also, the readme in the TWRP GitHub repository lacks an entry in the manifest file:

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

Nevertheless, thank you for the info :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lakkimsetty.baba:
For S10+, the repo's recovery partition size that was set is smaller than the image that is being generated.

FAILED: /home/saitejal/twrp/repo/out/target/product/beyond2lte/recovery.img
/bin/bash -c "(/home/saitejal/twrp/repo/out/host/linux-x86/bin/mkbootimg --kernel /home/saitejal/twrp/repo/out/target/product/beyond2lte/kernel --ramdisk /home/saitejal/twrp/repo/out/target/product/beyond2lte/ramdisk-recovery.img --cmdline \"androidboot.selinux=permissive buildvariant=userdebug\" --base 0x10000000 --pagesize 2048 --recovery_dtbo device/samsung/beyond2lte/prebuilts/recovery_dtbo --os_version 10.0 --os_patch_level 2025-12-31 --kernel_offset 0x00008000 --ramdisk_offset 0x01000000 --tags_offset 0x00000100 --header_version 1 --board SRPRI28A004RU --output /home/saitejal/twrp/repo/out/target/product/beyond2lte/recovery.img --id > /home/saitejal/twrp/repo/out/target/product/beyond2lte/recovery.id ) && (size=\$(for i in /home/saitejal/twrp/repo/out/target/product/beyond2lte/recovery.img; do stat --format \"%s\" \"\$i\" | tr -d '\\n'; echo +; done; echo 0); total=\$(( \$( echo \"\$size\" ) )); printname=\$(echo -n \" /home/saitejal/twrp/repo/out/target/product/beyond2lte/recovery.img\" | tr \" \" +); maxsize=\$(( 67633152 -69632)); if [ \"\$total\" -gt \"\$maxsize\" ]; then echo \"error: \$printname too large (\$total > \$maxsize)\"; false; elif [ \"\$total\" -gt \$((maxsize - 32768)) ]; then echo \"WARNING: \$printname approaching size limit (\$total now; limit \$maxsize)\"; fi ) && (/home/saitejal/twrp/repo/out/host/linux-x86/bin/avbtool add_hash_footer --image /home/saitejal/twrp/repo/out/target/product/beyond2lte/recovery.img --partition_size 67633152 --partition_name recovery )"
error: +/home/saitejal/twrp/repo/out/target/product/beyond2lte/recovery.img too large (67653632 > 67563520)

If the size is increased in BoardConfig to finish the build, then flasing may fail since the image size is larger than the partition size on the phone, I think.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] El Dun:
delete because of misplaced post
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ThePS4Gamer:
Did someone try all of the TWRP builds available for the Exynos S10e (the official corsicanu build, the Geiti94 build and the modpunk build)?

What should I flash Dot OS with to avoid bootloop issues?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] LordHornyPanda:
Hello, thank you for your great work!

I'm trying to check the files integrity, but I'm getting invalid signature...

> gpg --keyring .\gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify .\recovery.img.xz.asc
gpg: assuming signed data in '.\recovery.img.xz'
gpg: Signature made 4/6/2020 9:00:24 AM Pacific SA Standard Time
gpg: using RSA key 8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D
gpg: BAD signature from "Andreas Schneider <asn@cryptomilk.org>" [unknown]

I also tried Cleopatra (see attached screenshots).

What am I doing wrong?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I've released twrp-3.5.2_9-beyondXlte-v1.img.xz which requires a firmware >=

XXU9ETLJ!