[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 FE (Exynos)

Search This thread

Gromit94

Member
Dec 9, 2019
10
0
I'm getting the VBMETA check fail, any advice? I'm currently on Android 12, tried multiple vbmeta_disabled files.
 

danjac

Senior Member
Feb 4, 2012
199
122
I'm getting the VBMETA check fail, any advice? I'm currently on Android 12, tried multiple vbmeta_disabled files.
No need to flash vbmeta anymore.
Just flashed a patched (via magisk) android 12 factory image .
Then download newest twrp and put it in the ap slot in odin.
 

Gromit94

Member
Dec 9, 2019
10
0
No need to flash vbmeta anymore.
Just flashed a patched (via magisk) android 12 factory image .
Then download newest twrp and put it in the ap slot in odin.
I tried everything that day, a full stock Android 12 through Odin, tried twrp, I would get some error and get stuck in download mode. The error I had was something about the bootloader
 

danjac

Senior Member
Feb 4, 2012
199
122
I tried everything that day, a full stock Android 12 through Odin, tried twrp, I would get some error and get stuck in download mode. The error I had was something about the bootloader
As I said, I could successfully install TWRP after flashing a patched / prerooted Android 12 factory image. I think Magisk takes care of vbmeta as well, so then you are able to just flash TWRP via ODIN without vbmeta in 'userdata'.
At least that worked for me.

How to patch your AP file can be found here (see the Samsung section):
https://topjohnwu.github.io/Magisk/install.html
 

Gromit94

Member
Dec 9, 2019
10
0
As I said, I could successfully install TWRP after flashing a patched / prerooted Android 12 factory image. I think Magisk takes care of vbmeta as well, so then you are able to just flash TWRP via ODIN without vbmeta in 'userdata'.
At least that worked for me.

How to patch your AP file can be found here (see the Samsung section):
https://topjohnwu.github.io/Magisk/install.html
Can you link me the patched android 12 you used? I'm very familiar with odin. I just can't successfully boot after patching TWRP.
 

Gromit94

Member
Dec 9, 2019
10
0
did it myself, there's no link. just use frija or sth similar to download the needed factory image and use magisk to patch it.
did it myself, there's no link. just use frija or sth similar to download the needed factory image and use magisk to patch it.

did it myself, there's no link. just use frija or sth similar to download the needed factory image and use magisk to patch it.
Oh right, confused me with the pre patched business. Is the clean is worth it? I tried for hours, I kept getting check fail and everything, so give up and debloated stock Android rom myself.
 

MrGentlemen

Senior Member
Apr 6, 2011
59
4
Samsung Galaxy S20 FE
Hi,
I have an SM-G780G/DS with Android 12
After flashing the twrp file with odin and restarting the phone in recovery mode, the stock recovery is still there.
I have followed the tutorial in the first post.
Any Help?
 

afaneh92

Account currently disabled
Jul 31, 2012
3,909
5,296
Hi,
I have an SM-G780G/DS with Android 12
After flashing the twrp file with odin and restarting the phone in recovery mode, the stock recovery is still there.
I have followed the tutorial in the first post.
Any Help?
You are lucky to lose twrp, dont flash exynos twrp on snapdragon. Use your correct twrp. In snapdragon section.
 

Gully.Moy

Member
Nov 16, 2011
24
3
Please help, I'm bricked after trying this!!

I have an exynos S20 FE and was on android 12. I followed the instructions but it didn't work and now my device just says "An error occurred while updating the device software", with "debore : on_fail_unsupported_version" in top left.

I can see no one else with this same error online, lots of people have posted a similar screen which also says "Use the Emergency Recovery Function in the Smart Switch PC software" after. I don't see that!!

Smart Switch emergency software recovery won't list my device and I've tried flashing stock firmware with latest Odin, or reflashing twrp with or without vbmeta...

Odin and Smart Switch will recognise the device is plugged in but won't flash it. After trying to flash with Odin I get another line under the debore one, top left, saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 0xa, BINARY: 0x9"

Any ideas, pleasseeeee

Edit: I managed to get into normal looking download mode but it still fails the same in Odin and Smart Switch.
 
Last edited:

afaneh92

Account currently disabled
Jul 31, 2012
3,909
5,296
Please help, I'm bricked after trying this!!

I have an exynos S20 FE and was on android 12. I followed the instructions but it didn't work and now my device just says "An error occurred while updating the device software", with "debore : on_fail_unsupported_version" in top left.

I can see no one else with this same error online, lots of people have posted a similar screen which also says "Use the Emergency Recovery Function in the Smart Switch PC software" after. I don't see that!!

Smart Switch emergency software recovery won't list my device and I've tried flashing stock firmware with latest Odin, or reflashing twrp with or without vbmeta...

Odin and Smart Switch will recognise the device is plugged in but won't flash it. After trying to flash with Odin I get another line under the debore one, top left, saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 0xa, BINARY: 0x9"

Any ideas, pleasseeeee

Edit: I managed to get into normal looking download mode but it still fails the same in Odin and Smart Switch.
reflash stock firmware with same bootloader version
 

Gully.Moy

Member
Nov 16, 2011
24
3
Great, thanks. Is it possible to tell what bootloader I need to match whilst my phone is in it's bricked state?

I was planning to try installing the latest stock carrier specific (Three) firmware for my phone (I tried unbranded already). This should be the firmware the phone was on before bricked so the same bootloader?

Edit: I tried to flash the latest carrier specific firmware but I get the same error...

I presume the line "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 0xa, BINARY: 0x9" means I currently have the 0xa bootloader and I am trying to flash the 0x9 binary which it won't accept? How can I find a stock firmware with the 0xa bootloader?

Edit 2: I found a firmware with the right bootloader version. Turns out Sammobile doesn't have the latest firmware in my region. Samfw does and helpfully lists the bootloader version (BIT (BINARY/U/SW REV.)=A in this case). But it still fails in Odin. Phone goes blank whilst flashing and goes back to the error screen.

So still bricked with "debore : on_fail_unsupported_version" in top left. What does this mean? Any other way to save my phone?

Edit 3: I figured " on_fail_unsupported_version" sounded like a problem with the Odin version. So, I tried 3.13.3 and... It worked! Not sure if that was the problem or just better luck this time but unbricked, Phew!
 
Last edited:

Gully.Moy

Member
Nov 16, 2011
24
3
So now I'm unbricked, next question is, what is the correct process for flashing this TWRP onto a phone with android 12 stock firmware?

I see people are saying Vbmeta is not required because you can flash a patched stock firmware instead, but what if you want to flash a custom rom (I'm looking at the Project X Rom)? Do I need to flash a patched stock firmware first or can I just flash the rom?
 

Gully.Moy

Member
Nov 16, 2011
24
3
Right, for anyone trying to do this who was stuck like me, this is how I got it working on Android 12 / ONEUI 4:
  • Unlocked bootloader as per guides no problem
  • Downloaded latest stock firmware from Samfw and extract
  • (Don't extract AP file to get boot.img as per some guides)
  • Copy the AP_blahblahblah.tar.md5 file to phone storage
  • Install Magisk manager on your phone via browser
  • Open Magisk manager, select 'install' next to Magisk, select the .tar.md5 file and patch it
  • Copy newly created magisk .tar file from phone download folder to computer
  • Flash via Odin 3.13.3 with standard BL CP and CSC from Samfw download, but the magisk .tar file in AP slot.
  • (I used CSC not Home CSC).
  • Boot into android and reenable USB debugging (not sure if necessary).
  • Pick up instructions on page one from point 3
  • (Recovery mode combination is volume up + side button with USB plugged in)
(y)

Maybe someone could update the OP?
 
Last edited:
  • Like
Reactions: Kaloak

isisky

Senior Member
Nov 18, 2010
112
12
Rennes
Hello, anyone have working version for android 13, I see there is a custom rom out there so I assumed there should be a twrp ?
 

Tungstwenty

Senior Member
Nov 1, 2011
1,830
4,512
It looks like the kernel sources for Android 13 are available.
@afaneh92 would it be possible to provide the recovery for this version?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    home.png
    backupname.png

    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    Code:
     * Your warranty is now void.
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or your getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * 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.

    Supported Models:
    Galaxy S20 FE G780F.

    Download & Guide:
    1. Unlock your bootloader.
    2. Download S20 FE: Mod edit: DL link removed
    3. Reboot to download mode
    4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar Or from attachment in USERDATA slot and click start.
    5. Reboot to recovery via recovery key combo.
    6. Disable encryption:
    - Go to Advanced > Terminal, type: multidisabler.​
    If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​
    - Type: multidisabler again. will see - Finished. when done.​
    7. Go back to Wipe > Format Data > type yes.
    8. Reboot to recovery.
    9. Flash magisk apk in twrp.
    10. Reboot to system, Enjoy.

    Note:
    To disable encryption manually:
    You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.exynos990
    To avoid stock recovery restoration manually:
    Rename system/recovery-from-boot.p to recovery-from-boot.p.bak



    Bugs:
    - Encryption not fully working.
    - Haptic feedback is currently not working.

    Thanks:
    TWRP team
    @jesec for unlock guide
    @ianmacd for multidisabler
    @lieske19372 for testing on S20 FE G780F

    Sources:
    Kernel tree
    Device tree
    4
    Changelog:
    29.11.2021 - Update to TWRP 3.6.0
    - Add Symlinked dynamic partitions to fstab
    - Update multidisabler
    - fstab clean up
    01.06.2021 - Update to latest TWRP source
    - Update kernel to oneui 3.1.
    03.03.2021 - Update to latest TWRP source
    - Add terminal multidisabler script
    - fstab cleanup.
    01.01.2021 - Update TWRP to 3.5.0.
    20.12.2020 - Initial Release.
    3
    Be careful - the Samsung Android 11 firmware update which includes OneUI 3.1 again provides a new and incompatible kernel and therefore another TWRP would be needed (which is not available atm).

    If you try to use the one for OneUI 3.0 it leads to a boot loop - which happened here...
    --> you have to use the original recovery part from Samsung's firmware in that situation
    I reflashed that on my phone, so I currently don't have a TWRP (until afaneh92 gets the newer kernel source code from Samsung and is able to build a new TWRP for that new kernel ;))

    What I miss in the story: are the TWRP versions with newer integrated kernel compatible with the older firmwares (e.g. is TWRP Android 11, OneUI 3.0 working for Android 10 firmware versions?) or do we need a special TWRP version for each firmware?
    2
    Hi everybody,

    Last night, my phone converted into a beautiful (an expensive) brick, in an aeternal loop.

    I don't know why, because I did everything as it is in the guide. See the video below.

    I tried everything, but nothing worked.

    Happily for me, I download the last ROM official from sam sung, and copy the BL, AP, CSC and CP in latest version of Odin 3, and my phone came back to life.

    I hope that this info can help to somebody with the same situation.

    Finally, I want to know why the installation of twrp failed, if I did everything what appears en the guide. (usb debug, oem unlocker, copy all the files, etc).

    Thanks a lot to all for you contribution to phones!!
    2
    Having the same issue, cannot disable AVB on Odin
    Unlock bootloader first then check kg state in download mode its must be checking not prenormal.
    And this work only on android 10. Not yet ready for android 11.