[RECOVERY][EXYNOS] TWRP 3.4.0-0 for S10e|S10|S10+ (UPDATE: 2020-06-12)

modpunk

Recognized Contributor
Oct 14, 2011
1,701
6,535
143
[RECOVERY][EXYNOS] TWRP 3.4.0-0 for S10e|S10|S10+ (UPDATE: 2020-06-12)

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?

  1. Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
  2. Download the recovery.img.xz and recovery.img.xz.asc.txt file
  3. Rename the recovery.img.xz.asc.txt file to recovery.img.xz.asc
  4. Verfiy the signature using the following command:
    Code:
    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!

XDA:DevDB Information
twrp-beyondXlte, Tool/Utility for the Samsung Galaxy S10

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
 

modpunk

Recognized Contributor
Oct 14, 2011
1,701
6,535
143
FAQ

How do boot into the bootloader/download mode?

Here are the steps:

  1. Turn off your phone
  2. Press and hold the volume down and bixby keys
  3. Connect a USB cable attached to your computer

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

How do boot into recovery mode?

  1. Turn off you phone
  2. 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:

  1. Go to Settings -> About Phone and find the "Build Number"
  2. Tab the build number several times till it tells you that you unlocked the Deverloper Settings
  3. Go to Settings -> System -> Advanded -> Developer Settings
  4. Enable "OEM Unlock"
  5. Reboot to bootloader mode (see above)
  6. Follow the instruction displayed on screen and unlock your device

How do I flash the recovery?

After you unlocked the bootloader:

  1. Boot into download mode (see above)
  2. 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.
 
Last edited:

modpunk

Recognized Contributor
Oct 14, 2011
1,701
6,535
143
Alright so what are the differences between this and the already available twrp by ian?
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.
 
Last edited:

angela5246

Senior Member
Mar 27, 2020
62
13
0
@modpunk

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.
 

modpunk

Recognized Contributor
Oct 14, 2011
1,701
6,535
143
@modpunk

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.
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.





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.
Take a look at https://github.com/whatawurst and check the corresponding twrp-9.0 branches (Kernel, platform, device).
 
Last edited:

angela5246

Senior Member
Mar 27, 2020
62
13
0
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?