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

Search This thread

madadictromtester

Senior Member
You are writing so much useless posts. Check OP and post your problem with logs/pic of download mode if you have any!
Sure why not I am totally writitng useless stuff. People have been facing issues with vbmeta and that too in your own telegram group multiple people since last oct-nov have complained about vbmeta not working. Please check it once. Anyway about the issue below attached shows the error one gets while flashing the vbmeta.
And also for your ego I am attaching zip of multiple screenshots of various people have complained about the problem.

Just read what i said in my first post here, i never asked you to fix it or anything, it was a simple request to mention below the vbmeta disabler that this might not work for everyone. I have no interest in talking to you but multiple people are getting confused and maybe i dont know you just tend to ignore it.

And no need for further humiliation of me not going to comment here anymore.
 

Attachments

  • photo_2022-01-27_22-06-21.jpg
    photo_2022-01-27_22-06-21.jpg
    40.7 KB · Views: 173
  • Screenshots.zip
    14.2 MB · Views: 80

afaneh92

Senior Member
Jul 31, 2012
3,921
5,241
Sure why not I am totally writitng useless stuff. People have been facing issues with vbmeta and that too in your own telegram group multiple people since last oct-nov have complained about vbmeta not working. Please check it once. Anyway about the issue below attached shows the error one gets while flashing the vbmeta.
And also for your ego I am attaching zip of multiple screenshots of various people have complained about the problem.

Just read what i said in my first post here, i never asked you to fix it or anything, it was a simple request to mention below the vbmeta disabler that this might not work for everyone. I have no interest in talking to you but multiple people are getting confused and maybe i dont know you just tend to ignore it.

And no need for further humiliation of me not going to comment here anymore.
Finally a useful post with something to explain. The error in download mode can explain everything.
That is your device is on v6 and binary is on v5 so you need different vbmeta disabled
 
  • Like
Reactions: madadictromtester

madadictromtester

Senior Member
Finally a useful post with something to explain. The error in download mode can explain everything.
That is your device is on v6 and binary is on v5 so you need different vbmeta disabled
See I know that Samsung changes stuff quite often thats this doesnt work, all I was asking you is to mention there that if you have a newer binary version it wont work and they might use the patched AP method for disabling vbmeta.
 

K2silver

Senior Member
Oct 24, 2016
143
14
I sent back my Canadian version because it was unrootable so now I am looking into getting the International version (exynos) BUT with what I am hearing is that ROOT will not work on Android 12.

Or will it work on Android 12 but you need to be flashing custom ROMs?

My whole plan was to buy outright a device like I did with my S7 and extend my life cycle by using custom ROMs with updated security patches

Anyone similar thoughts or suggestions?

/thanx
 

PhoenixxClaw

Member
May 23, 2021
6
0
I sent back my Canadian version because it was unrootable so now I am looking into getting the International version (exynos) BUT with what I am hearing is that ROOT will not work on Android 12.

Or will it work on Android 12 but you need to be flashing custom ROMs?

My whole plan was to buy outright a device like I did with my S7 and extend my life cycle by using custom ROMs with updated security patches

Anyone similar thoughts or suggestions?

/thanx
Can't really give advices as I just recently gave away my sm-g780f..
But I can assure you that magisk root has been working fine for me on Android 12.
 

3mel

Senior Member
Aug 23, 2012
1,934
629
London
I sent back my Canadian version because it was unrootable so now I am looking into getting the International version (exynos) BUT with what I am hearing is that ROOT will not work on Android 12.

Or will it work on Android 12 but you need to be flashing custom ROMs?

My whole plan was to buy outright a device like I did with my S7 and extend my life cycle by using custom ROMs with updated security patches

Anyone similar thoughts or suggestions?

/thanx
the international S20FE also comes in snapdragon models which can be rooted on Android 12 and below. you would likely struggle to find an Exynos version as they were discontinued and replaced by a 4G snap version.
SM-G780F = Exynos 4G
SM-G780G = Snapdragon 4G
SM-G781B = Snapdragon 5G... all rootable.
it's only variants made for and sold in the US or Canada that can't be bootloader unlocked.
 
  • Like
Reactions: K2silver

K2silver

Senior Member
Oct 24, 2016
143
14
the international S20FE also comes in snapdragon models which can be rooted on Android 12 and below. you would likely struggle to find an Exynos version as they were discontinued and replaced by a 4G snap version.
SM-G780F = Exynos 4G
SM-G780G = Snapdragon 4G
SM-G781B = Snapdragon 5G... all rootable.
it's only variants made for and sold in the US or Canada that can't be bootloader unlocked.
thanx 3mel! its been awhile since ive been rooting (S7 days lol) but I just go the international version SM-G780G/DS running 3.1 UI, i have yet to find a guide since still trying to double check everything
 

3mel

Senior Member
Aug 23, 2012
1,934
629
London
thanx 3mel! its been awhile since ive been rooting (S7 days lol) but I just go the international version SM-G780G/DS running 3.1 UI, i have yet to find a guide since still trying to double check everything
you can follow all guides and even versions of TWRP for the 5G model. switch to the TWRP snapdragon thread now that you've got the G model. you can unlock and flash TWRP and then flash a magisk zip or better yet follow this guide
 
  • Like
Reactions: K2silver

K2silver

Senior Member
Oct 24, 2016
143
14
So with International model I have CSC set to CHO (Chile) but I am in Canada, when I do the dialer + IMIE to go to CSC change menu there is no Canada to select from? How do you go about inputting CSC? Is this done later thru TWRP or Magisk or something?
 

3mel

Senior Member
Aug 23, 2012
1,934
629
London
So with International model I have CSC set to CHO (Chile) but I am in Canada, when I do the dialer + IMIE to go to CSC change menu there is no Canada to select from? How do you go about inputting CSC? Is this done later thru TWRP or Magisk or something?
remember that model number you have doesn't exist in Canada, you don't want to be getting it updated with locked Canadian updates either.
from now on you're in charge of downloading suitable updates and flashing then. once you're rooted you apparently should be able to pick a region you want the phone to be from (that's not Canada or the US) and make it into a phone from there.
still though updates don't always come thru to phones moved outside of their original CSC region. like now, you probably won't get updates when people in Chile get them because your not there yourself.

PLEASE DON'T REPLY, this is the wrong place for this conversation. make a thread or join here... http://t.me/S20FEModding
 
  • Like
Reactions: K2silver

bedofrosesss

Senior Member
Jan 26, 2015
339
81
Unlocking the AVB failed here, too.
Odin always says FAIIL! - "RQT_CLOSE!!"

I then still tried to flash the twrp 3.5.0_10 - for which Odin says "Completed" - but afterwards I'm unable to go to recovery, only Download Mode is available.
Phone says in download mode:
Code:
ODIN MODE (SVB Fail)!
recovery: No footer detected ()
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM RECOVERY
VBMETA G780FXXUIATIL. 34364176A
SW REV. CHECK FAIL(VBMETA) DEVICE: 0x1, BINARY: 0x8
(the error code in the first recovery line is not readable, it's directly "behind" the screen hole)

Is that vbmeta_disabled.tar file for all S20 devices?
What can I do now?

BTW, I was still at Android 10 and have a German S20FE (SM-G780F) CSC is DBT
hi did you manage to solve?
 

ElvisHair87

New member
Apr 2, 2022
1
0
I'm using Heimdall and it's not working for me. Android 12.
I flash vbmeta_disabled as --VBMETA and twrp as --RECOVERY, then this message comes:

SW REV. CHECK FAIL(VBMETA) DEVICE: 0x8, BINARY: 0x0

If I flash back to stock firmware and then try vbmeta_disabled as USERDATA this message comes:

DEBORE: DN_FAIL_PARTITION_ID
 
I'm using Heimdall and it's not working for me. Android 12.
I flash vbmeta_disabled as --VBMETA and twrp as --RECOVERY, then this message comes:

SW REV. CHECK FAIL(VBMETA) DEVICE: 0x8, BINARY: 0x0

If I flash back to stock firmware and then try vbmeta_disabled as USERDATA this message comes:

DEBORE: DN_FAIL_PARTITION_ID
Use ODIN
 

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

    Support:
    Live support is available via #twrp on Freenode with your IRC client or just click this link.

    Telegram group

    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.