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

Search This thread

TeslaSerb

Member
Jul 5, 2021
12
5
Hi Guys,
I need one information. It seems to me that there is a lot of fuss regarding TWRP and LOS. Could someone be kind enough to explain why is there so much repulsion towards TWRP

(I did a little reading and i came across some possible problems. Please feel free to add to this information i may be wrong, trying to figure out)
*TWRP could try's to decrypt internal storage which can be problematic and possibly corrupt data
(So in case we are not using encryption it is still safe to use TWRP with LOS?)
*Recovery should not be the tool for manipulating files/folders on storage
(This is really sad because i did some astonishing backups with this tool. Always made me feel safe)
 

expressluke

Senior Member
Hi Guys,
I need one information. It seems to me that there is a lot of fuss regarding TWRP and LOS. Could someone be kind enough to explain why is there so much repulsion towards TWRP

(I did a little reading and i came across some possible problems. Please feel free to add to this information i may be wrong, trying to figure out)
*TWRP could try's to decrypt internal storage which can be problematic and possibly corrupt data
(So in case we are not using encryption it is still safe to use TWRP with LOS?)
*Recovery should not be the tool for manipulating files/folders on storage
(This is really sad because i did some astonishing backups with this tool. Always made me feel safe)
As long as you use the roms that do not use encryption or disable it yourself, you are safe to use twrp.

It's purely the fact twrp is unable to decrypt data.

Hope that helps.
 

PokeRekoP

Member
Jul 16, 2021
37
1
11
EDIT: Solved, sort of. Went brave and went on re-flashing through ODIN the full stock FW but made sure to keep "re-partition" off (!) and use "Home_CSC" for the CSC Slot. That kept "storage" untouched and I can now at least pull files in TWRP. (Longer story; followed instructions from the thread on my actual custom rom how to get twrp flashed together with stock FW).


---------original post -----------
SNAFU. Sorry guys, urgently need some advise plz.

In short: can I restore a previously used "known good" twrp 3.4.0-3.img (after tar'ing it) through ODIN AP slot?

What happend?
Was prepping to upgrade my A10 based rom to an A12 based version.
My TWRP was a magisk-patched 3.4.0-3_ianmacd version (still have a backup of that file at hand).
Downloaded latest twrp-3.6.1_9-1-beyond2lte and patched it on the phone with latest canary magisk manager.
Booted phone into TWRP (3403ianmcd, magisk patched) and flashed that now magisk-patched 3.6.1 into recovery.
That way to update twrp worked like always coming up to 3.4.0-3(_ianmacd) twrps, done several times in preparation of a rom upgrade.

Not today :( Now have the device nicely in the "download mode" boot loop complaining something about vbmeta. Damn.

I'd love to get back to my A10 rom for once (or into my twrp 3403) to pull some files from storage (to SD, or via adb). Thought I can backup from TWRP AFTER upgrading it... though WRONG.

Can I simply re-flash the 3403ianmacd via ODIN AP?
Do I have to give along vbmeta? Guess not, only needed for newer (A11, A12) roms, right?.
Or do I now have to flash all stock A12 parts through ODIN once (losing data+storage?).
 
Last edited:
Apr 15, 2014
7
2
I've followed the instructions for Odin in the OP multiple times now exactly as written, and every time, when trying to flash TWRP and vbmeta, I get this RQT_CLOSE! error in Odin. Have also tried different USB cables, ports, and versions of Odin. From what I can tell it should be working.

Thoughts?
 

Attachments

  • 2022-05-02 15_47_26-Window.png
    2022-05-02 15_47_26-Window.png
    81.2 KB · Views: 74

Philnicolls89

Senior Member
Jun 28, 2019
715
321
33
A.C.T
Samsung Galaxy S10+
I've followed the instructions for Odin in the OP multiple times now exactly as written, and every time, when trying to flash TWRP and vbmeta, I get this RQT_CLOSE! error in Odin. Have also tried different USB cables, ports, and versions of Odin. From what I can tell it should be working.

Thoughts?
Is OEM unlock turned on in developer settings and did you unlock your bootloader?
Also what version of Odin did you use?
 

corsicanu

Recognized Developer
I've followed the instructions for Odin in the OP multiple times now exactly as written, and every time, when trying to flash TWRP and vbmeta, I get this RQT_CLOSE! error in Odin. Have also tried different USB cables, ports, and versions of Odin. From what I can tell it should be working.

Thoughts?
My apologies if this is too soon, but, bump.
The file you flash is for snapdragon S10e. The error can happen from 2 reasons only - either you have a locked snapdragon phone (US/Canadian - U/U1/W/V/R1/R4 etc) which can't be flashed, either you're flashing that file on Exynos phone. So what's the phone you're flashing on?
 
  • Like
Reactions: Philnicolls89
Apr 15, 2014
7
2
The file you flash is for snapdragon S10e. The error can happen from 2 reasons only - either you have a locked snapdragon phone (US/Canadian - U/U1/W/V/R1/R4 etc) which can't be flashed, either you're flashing that file on Exynos phone. So what's the phone you're flashing on?
Ah, indeed it is the Exynos variant. This confuses me a little, as the title for this thread states that it is for the Exynos variant, so why include a file that is only for the Snapdragon variant?

Regardless, how should I go about flashing TWRP on the Exynos variant correctly?
 

corsicanu

Recognized Developer
Ah, indeed it is the Exynos variant. This confuses me a little, as the title for this thread states that it is for the Exynos variant, so why include a file that is only for the Snapdragon variant?

Regardless, how should I go about flashing TWRP on the Exynos variant correctly?
I did not include a snapdragon file anywhere which makes me curious how did you end up on snapdragon download page, maybe from google? The difference in codename can be a bit confusing as the only difference between them is the letter q in the device name (i.e. beyond0lte - beyond0qlte).
So to sum up, if you own an exynos device (G970F / G970N) just follow the links from the first page.
 
Apr 15, 2014
7
2
I did not include a snapdragon file anywhere which makes me curious how did you end up on snapdragon download page, maybe from google? The difference in codename can be a bit confusing as the only difference between them is the letter q in the device name (i.e. beyond0lte - beyond0qlte).
So to sum up, if you own an exynos device (G970F / G970N) just follow the links from the first page.
Ahhh, I see. Yes, that is likely where I went wrong. I got vbmeta from here, but TWRP directly from their site, without realising that there was a one letter difference in the codename. Just double-checked, and I do currently have TWRP for "beyond0qlte" which is the wrong one.

Thank you! And my apologies if I came off as rude, I was just a bit confused.
 

Alex_x90

Member
May 14, 2018
12
1
Hello, just wanted to ask a couple questions before I try to move on w/ any installations. Im currently running android 10 and have ianmacd's unofficial twrp installed (magisk patched). If I flash the img I downloaded (twrp-3.6.1_9-3-beyond2lte) via my existing twrp, will it be magisk patched? If I flash via twrp will I need to flash the vbmeta & multidisabler? Will the fact that I'm currently on android 10 cause any issues w/ that specific twrp version (and if so which version do I need)?

I want to get set up w/ the newer twrp so I can update my rom from hyperom v5 for Q to v3.5 for R, so I can then get a newer version of the thunderstorm kernel (which I haven't yet installed any version of).
 

Alex_x90

Member
May 14, 2018
12
1
Hello, just wanted to ask a couple questions before I try to move on w/ any installations. Im currently running android 10 and have ianmacd's unofficial twrp installed (magisk patched). If I flash the img I downloaded (twrp-3.6.1_9-3-beyond2lte) via my existing twrp, will it be magisk patched? If I flash via twrp will I need to flash the vbmeta & multidisabler? Will the fact that I'm currently on android 10 cause any issues w/ that specific twrp version (and if so which version do I need)?

I want to get set up w/ the newer twrp so I can update my rom from hyperom v5 for Q to v3.5 for R, so I can then get a newer version of the thunderstorm kernel (which I haven't yet installed any version of).
Bump
 

Top Liked Posts

  • There are no posts matching your filters.
  • 44
    Ae08b8N.png


    Official TWRP 3.6.1-* 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-3.* 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-3.* zip to disable security and encryption.

    Sources:
    Credits:
    • TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
    As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
    16
    Compatibility and changelog:

    07.03.2022 - TWRP 3.6.1
    • Security patch: 2022-02-01
    • Compatibility: only GVA*/GVB* firmwares, OneUI 4.0

    09.01.2022 - android 12 support
    • Security patch: 2022-01-01
    • Compatibility: only GUL* firmwares, OneUI 4.0
    08.01.2021 - android 11 support
    • Security patch: 2020-12-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
    05.12.2020 - Initial release
    • Security patch: 2020-11-01
    • Compatibility: DTJ* firmwares

    Misc links:
    Further reading:
    11
    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.
    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!
    6
    TWRP 3.6.0_9-2 is up and it has full A12 support.
    First posts got updated too, i strongly suggest you to use from now on my updated fork of multidisabler for A12 compatibility, code and downloads are available here.

    Regards!