[RECOVERY][OFFICIAL][3.5.0-x] TWRP for Galaxy S10/e/+/5G Exynos

[waterpolo]

My guess is you used to backup 'system' which is smaller in size than 'system.img' and your external card is formatted in fat32 which doesn't allow to store larger files than 4gb. If I'm right, formatting it to exFAT would fix your issue.

Cheers

Thanks for your suggestion to use exFAT instead of fat32.
I will backup first the data and then format to exFAT -> restore the data -> (re)install latest twrp 3.5 -> try again if the system image backup will be succeed.

UPDATE: exFAT solved my issue. Thanks @AndrzejDwo

UPDATE2: exFAT is much slower than FAT32 or do I have to set some parameters?

 

[AndrzejDwo]

Thanks for your suggestion to use exFAT instead of fat32.
I will backup first the data and then format to exFAT -> restore the data -> (re)install latest twrp 3.5 -> try again if the system image backup will be succeed.

UPDATE: exFAT solved my issue. Thanks @AndrzejDwo

UPDATE2: exFAT is much slower than FAT32 or do I have to set some parameters?

I never noticed exFAT to be slower than fat32, in fact, it should be faster... Maybe it's the matter backup size. Glad it worked tho.

Cheers

 

[xdagee]

update alert
twrp-3.5.0_9-3 released

changelog
not yet known

if you are flashing newer twrp then i supposed you flash the latest.

[update 2/22/21]
this breaks after flashing... at least on my s10e SM-G970F. It takes you directly to download mode with vbmeta signing errors.
more on this error here here
advise; don't flash now. stick to your previous version. wait for a fix, or a update.
@corsicanu can you please check on this?

[update 2/24/21]
screenshot

Spoiler

 

[AndrzejDwo]

[update 2/24/21]
screenshot

Spoiler

View attachment 5231415

Flash with odin bl/cp.tar from Corsis repo and don't use TS kernel next time.

 

[xdagee]

Flash with odin bl/cp.tar from Corsis repo and don't use TS kernel next time.

am not using TS kernel.
am on DTL1 (Android 10) I supposed the issue is the FW. I will have to upgrade to Android 11 FW or?

 

[AndrzejDwo]

am not using TS kernel.
am on DTL1 (Android 10) I supposed the issue is the FW. I will have to upgrade to Android 11 FW or?

lol, then use android 10 recovery not 11 one

 

[xdagee]

lol, then use android 10 recovery not 11 one

that's the conclusion.
check this out here

 

[MOMOOUTLOOK111]

G

 

[starbright_]

Can TWRP3.5 handle encrypted data? I understand you have to wipe data first and install that multidisabler. But can data be encrypted again so that TWRP can read it?

 

[yuri76]

Someone tried the latest recovery on this version G975FXXU9FUBD?

 

[AndrzejDwo]

Someone tried the latest recovery on this version G975FXXU9FUBD?

Yes, working just fine on my s10+.

 

[starbright_]

Want to create a backup. What partitions are recommended to backup?
Do I need a backup of the bigger ones system/vendor/product image? (What is product image btw?)

 

[xdagee]

Want to create a backup. What partitions are recommended to backup?
Do I need a backup of the bigger ones system/vendor/product image? (What is product image btw?)

backup boot, system image, and data

 

[gsmdb]

createTarFork() process ended with ERROR: 255 when trying to recovery data...

If anyone does get this error when updating from android 10 to 11, the issue is related to the created link (to a folder) in sdcard/android/data to root/data/data. The permission isn't allowable in android 11.
I can reproduce the error in several times. Backup goes smoothly, but restoring ends always with error 255

 

[gsmdb]

How to Cold Boot into Recovery Mode on Samsung’s One UI 3.0 (Android 11)

Note: This method for Exynos variant & old method for Snapdragon variant.

1. Hold the Power button of your device till the power menu pops up and select Power Off.

2. Wait for your device to turn off completely.

3. Plug-in a USB-C data cable connected to your PC or USB-C earphones in your device.

4. Now, check if your device has a Bixby Button (Such as Galaxy S10/Note10):

- Without Bixby Button: Press Volume Up + Power Button for a few seconds.

- With Bixby Button: Press Volume Up + Bixby Button + Power Button for a few seconds.

EDIT: until the boot screen/ first screen is up and release all the buttons (as for a few seconds above)

5. And you will boot into Recovery mode.

 

[starbright_]

...
3. Plug-in a USB-C data cable connected to your PC or USB-C earpho nes in your device.
...

This is (more or less) known - but do you have at any time some USB-C cable with you? And something to connect to, I guess it is not enough just to plug in cable without any counterpart?
A reboot can happen every once a while, although software is mostly stable.

 

[gsmdb]

This is (more or less) known - but do you have at any time some USB-C cable with you? And something to connect to, I guess it is not enough just to plug in cable without any counterpart?
A reboot can happen every once a while, although software is mostly stable.

I will consider unnecessary change in android 11 since the old combo works fine in android 10. Btw. OTG USB key works too

 

[Philnicolls89]

I will consider unnecessary change in android 11 since the old combo works fine in android 10. Btw. OTG USB key works too

A very unnecessary and annoying change!! I have made sure that I have a custom kernel installed now so that I don't need to reboot to recovery partition anymore. Also I use a root power menu app to reboot to twrp when needed. FYI I also discovered that I could boot to twrp by connecting the phone to my car aswell

 

[starbright_]

backup boot, system image, and data

Recovery might be important too, right? Isn't that the place where Magisk/TWRP is?

 

[xdagee]

Recovery might be important too, right? Isn't that the place where Magisk/TWRP is?

you can always patched recovery and flash when there's update. You asked what to back up if you want to restore. And these are critical for your restoration to be successful and boot.