• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

Xiao-Zii

Member
Jun 13, 2019
6
0
Australia
So.... i didnt read this part because i was following another guide which unfortunatly made me mess up somehow.

"If you wish to install TWRP without rooting, there are numerous pitfalls to consider. For example, a stock device is protected by Android Verified Boot. This is implemented as a vbmeta partition that contains cryptographic digests for verifying the integrity of boot.img, recovery.img and other partitions/images. Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot."

I successfully rooted a galaxy device before with limited knowledge ( this is still mostly the same) and assumed it wouldn't be any different. I had difficulty with the last one but eventually had it smooth sailing and got the hang of it. i reinstalled the os cuz i assumed it was deleted and its sort of working but now its stuck on "starting android..." and how would i go about root? i see a lot of people saying you need to patch the twrp file with magisk, how would you do that? thanks!

TWRP for Samsung Galaxy S10 5G (Exynos)​

 

CntrlAltDel45

Senior Member
May 7, 2015
132
18
Cape Town
Does anyone know how to resolve the recovery issues below? I've formatted many times, tried different versions of TWRP but still this is the issue I get when backing up or flashing. I am fully rooted.
 

Attachments

  • Screenshot_2021-09-08-06-16-53.png
    Screenshot_2021-09-08-06-16-53.png
    313.5 KB · Views: 74
  • 2021-09-08 06_21_02-Screenshot_2021-09-08-06-16-49.png - Windows Photo Viewer.png
    2021-09-08 06_21_02-Screenshot_2021-09-08-06-16-49.png - Windows Photo Viewer.png
    79.6 KB · Views: 74

bara solyman

New member
Apr 24, 2021
4
0
when i try to flash twrp with vbmeta , i tried without vbmeta the same thing happens any solution? im on the latest oneui 3 and my bootloader is unlocked
 

Attachments

  • fail.PNG
    fail.PNG
    91 KB · Views: 31
Last edited:

expressluke

Senior Member
Does anyone know how to resolve the recovery issues below? I've formatted many times, tried different versions of TWRP but still this is the issue I get when backing up or flashing. I am fully rooted.
You're likely using a rom that has encryption, only way to solve this is to move to one without encryption and format /data
 

sepo27

Member
May 27, 2017
8
0
Hi.

I have a question.

My setup is:
- Sam Galaxy S10
- Lineage OS 18 (vbmeta fixed already obviously)
- Lineage custom rexovery
- Magisk rooted

Now if I want to install TWRP, can I just flush it using `heimdal` ?

Or do I need to "patch" it with Magisk fist ?

I'm little confused about this part. Will TWRP / Magisk coexist together if I just flush it.

And do I have to erase my data.
 

ThePS4Gamer

Senior Member
Dec 20, 2015
264
85
Samsung Galaxy S10e
Redmi Note 10
Hi.

I have a question.

My setup is:
- Sam Galaxy S10
- Lineage OS 18 (vbmeta fixed already obviously)
- Lineage custom rexovery
- Magisk rooted

Now if I want to install TWRP, can I just flush it using `heimdal` ?

Or do I need to "patch" it with Magisk fist ?

I'm little confused about this part. Will TWRP / Magisk coexist together if I just flush it.

And do I have to erase my data.
Yes, you can just use Odin or Heimdall to install TWRP. Just make sure to enter into it after install because if you boot normally, Lineage OS erases TWRP and re-installs its own recovery.
 
  • Like
Reactions: sepo27

thetys

Member
Oct 27, 2020
18
0
The steps to install root (magisk) are quite simple, so I'm not sure why it isn't working for you. Just to clarify these are the steps you took:
1. Unlock developer options and turn on OEM unlocking.
2. Turn off phone, boot to download mode and unlock boot loader. This will do a data format (wipe everything on ur phone)
3. Turn on phone, set up phone and install magisk manager
4. Download firmware from frija or sammobile
5. patch the AP file with magisk
6. Download the correct twrp for ur firmware and patch twrp with magisk (different TWRP versions are needed for different firmware versions)
7. Rename patched twrp to 'recovery', then open patched AP file using 7zip, replace stock recovery with new recovery file
8. Flash AP file using odin along with the other bl,cp and csc or home_csc files
9. Restart to twrp using key combo and flash multi disabler
10. Using twrp select restart to recovery and allow phone to boot
11. Open magisk manager, magisk should now be installed or ask you to finish the set up process.
12. Enjoy

Hello, thanks for the help.

I followed all these steps, after step 10 I had to go through the phone setup process again and then saw that I didnt have Magisk installed.

Then I installed Magisk app but the phone isnt rooted.

Any idea what can I do now?

Maybe flash Magisk from TWRP?
 

Philnicolls89

Senior Member
Jun 28, 2019
654
288
32
A.C.T
Samsung Galaxy S10+
Hello, thanks for the help.

I followed all these steps, after step 10 I had to go through the phone setup process again and then saw that I didnt have Magisk installed.

Then I installed Magisk app but the phone isnt rooted.

Any idea what can I do now?

Maybe flash Magisk from TWRP?
Did you make sure that when booting your phone from TWRP that you selected reboot to recovery and not reboot system? If you boot normally then root will not be present.
 
  • Like
Reactions: thetys

Philnicolls89

Senior Member
Jun 28, 2019
654
288
32
A.C.T
Samsung Galaxy S10+
You are right, now I'm rooted. :) Thanks a lot for the quick help! ;)
No worries, always glad to help. remember that whenever you restart or power off/on your phone you must boot to the recovery partition.
This can be done either using the button combo, or there is also a reboot to recovery option in the magisk manager app. Remember that booting to TWRP and booting to recovery are 2 separate things.
 
  • Like
Reactions: thetys

thetys

Member
Oct 27, 2020
18
0
No worries, always glad to help. remember that whenever you restart or power off/on your phone you must boot to the recovery partition.
This can be done either using the button combo, or there is also a reboot to recovery option in the magisk manager app. Remember that booting to TWRP and booting to recovery are 2 separate things.
If I don't boot to recovery when rebooting I wont have root for the time being that's all?
Or anything else bad could happen?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi.

    I have a question.

    My setup is:
    - Sam Galaxy S10
    - Lineage OS 18 (vbmeta fixed already obviously)
    - Lineage custom rexovery
    - Magisk rooted

    Now if I want to install TWRP, can I just flush it using `heimdal` ?

    Or do I need to "patch" it with Magisk fist ?

    I'm little confused about this part. Will TWRP / Magisk coexist together if I just flush it.

    And do I have to erase my data.
    Yes, you can just use Odin or Heimdall to install TWRP. Just make sure to enter into it after install because if you boot normally, Lineage OS erases TWRP and re-installs its own recovery.
    1
    Hello, thanks for the help.

    I followed all these steps, after step 10 I had to go through the phone setup process again and then saw that I didnt have Magisk installed.

    Then I installed Magisk app but the phone isnt rooted.

    Any idea what can I do now?

    Maybe flash Magisk from TWRP?
    Did you make sure that when booting your phone from TWRP that you selected reboot to recovery and not reboot system? If you boot normally then root will not be present.
    1
    Yes, I rebooted first to recovery again and then booted to system.
    If you booted to system after being in TWRP then that is your problem. Once you are in TWRP, you need to select the reboot to recovery option and let your phone restart.
    1
    You are right, now I'm rooted. :) Thanks a lot for the quick help! ;)
    No worries, always glad to help. remember that whenever you restart or power off/on your phone you must boot to the recovery partition.
    This can be done either using the button combo, or there is also a reboot to recovery option in the magisk manager app. Remember that booting to TWRP and booting to recovery are 2 separate things.
    1
    If I don't boot to recovery when rebooting I wont have root for the time being that's all?
    Or anything else bad could happen?
    No nothing bad will happen, when you do eventually reboot to recovery you MAY have lost WiFi and Bluetooth pairings but that would be the worst that could happen.
  • 32
    Ae08b8N.png


    Official TWRP 3.5.0-* For Galaxy S10/e/+/5G
    Only for exynos variants - G970F / G973F / G975F / G977B (Europe - Global, Single/Dual-SIM), G970N / G973N / G975N / G977N (South Korea)
    Disclaimer
    I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
    Please do some research if you have any concerns about features included in this recovery before flashing it!
    YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.


    Kernel Features:
    • latest kernel source release
    • disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
    • spoofed config for firmware checks
    Recovery Features:
    • built in full 64 mode
    • toybox/busybox support
    • compatible with Android 10.0 and above
    Downloads:
    Instructions:
    Odin (Windows)

    Prerequisites: Samsung USB drivers, Odin v3.14.1
    If you already have the bootloader unlocked you can skip to step 6.

    1. Make sure OEM Unlock is ON in developer settings;
    2. Turn off the phone;
    3. Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode;
    4. Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
      * Please be aware all your data will be erased including internal storage and phone will reboot!!
    5. Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
    6. Make sure OEM Unlock is ON in developer settings;
    7. Turn off the phone;
    8. Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
      * If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
    9. Download appropriate TWRP .tar file according to your device
    10. Download avb disabled vbmeta .tar
    11. Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + bixby + power to force it boot straight in TWRP after flashing
    !! Only if coming from full stock firmware
    • In TWRP home screen press wipe - format data - yes
    • Download and flash multidisabler-samsung-3.* zip to disable security and encryption.

    Heimdall (Linux)
    Install heimdall & additional required packages:
    Code:
    sudo apt-get update
    sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
    If you already have the bootloader unlocked you can skip to step 6.

    1. Make sure OEM Unlock is ON in developer settings;
    2. Turn off the phone;
    3. Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode;
    4. Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
      * Please be aware all your data will be erased including internal storage and phone will reboot!!
    5. Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
    6. Make sure OEM Unlock is ON in developer settings;
    7. Turn off the phone;
    8. Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
      * If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
    9. Download appropriate TWRP .img file according to your device
    10. Download avb disabled vbmeta .img
    11. Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
      Code:
      sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
      and press enter - once you press enter grab the phone and press vol up + bixby + power to force it boot straight in TWRP after flashing
    !! Only if coming from full stock firmware
    • In TWRP home screen press wipe - format data - yes
    • Download and flash multidisabler-samsung-2.* zip to disable security and encryption.

    TWRP

    • Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery

    dd (Requires root)

    • Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
      Code:
      su
      dd if=/sdcard/twrp.img of=/dev/block/platform/13d60000.ufs/by-name/recovery
    !! Only if coming from full stock (magisk patched) firmware
    • In TWRP home screen press wipe - format data - yes
    • Download and flash multidisabler-samsung-2.* zip to disable security and encryption.

    Sources:
    Credits:
    • TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
    10
    Compatibility and changelog:
    08.01.2021 - android 11 support
    • Security patch: 2020-01-01
    • Compatibility: only ETL* firmwares, OneUI 3.0
    27.12.2020 - TWRP 3.5.0 bringup - december release
    • Security patch: 2020-12-01
    • Compatibility: only DTK* and DTL* firmwares
    09.12.2020 - december release
    • Security patch: 2020-12-01
    • Compatibility: only DTK* and DTL* firmwares
    18.11.2020 - november DTJ* kernel sourcecode
    • Security patch: 2020-11-01
    • Compatibility: only DTJ* firmwares
    22.10.2020 - Initial release
    • Security patch: 2020-10-01
    • Compatibility: DTI* firmwares
    Misc links:
    Further reading:
    9
    Android 11 TWRP is up already for a while, in case you didn't notice it yet grab it from twrp.me.
    Don't forget to use targeted TWRP for your android version and release, read more about compatibility in second post of this thread.
    Regards!
    8
    FAQ
    Q: Can i use this recovery with other firmware then mentioned in compatibility?
    A: Only with same Android version and only if you don't plan to boot rooted with TWRP (some kernels deliver root prebuilt in kernel), or Rollback protection will kick in and you won't be able to pass the lockscreen.

    Q: Where do i get vbmeta.img?
    A: From here, download the one you need according to install instructions.

    Q: TWRP can't mount data partition, what to do?
    A: Make sure you formatted data partition.

    Q: Phone is not booting even after 20 minutes
    A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.

    Q: How to format data partition?
    A:
    ymlnQUE.jpg


    Q: Phone is showing only Samsung logo
    A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.

    Q: Why do i need to format data partition?
    A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
    5
    update
    twrp-3.5.0_9-4 released
    remember this is for Android 11 FW only*
    Firmware: FUBD* EUB1* EUA4*

    changelog
    not known yet*
    obviously merges with the March security patches

    note
    if you are looking for twrp for Android 10 use twrp-3.5.0_9-0 and if you're on 10 and wants to update twrp to the latest then you have to upgrade to Android 11 FW before.