[RECOVERY] [UNOFFICIAL] TWRP 3.4.0-0 for Galaxy A20e (A202F)

Search This thread

Xyn XDotnest

Member
Jul 21, 2015
21
12
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:
#include <std_disclaimer.h>
/*
 *
 * We are 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 ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *
 */

I’d recommend to read everything in this post, if you care about your phone.
  1. If you already unlocked your bootloader, start with step 3.
  2. First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
  3. Flash Galaxy A20e TWRP.tar via Odin or heimdall
  4. Reboot into TWRP AS SOON AS THE FLASHING PROCESS IS DONE because otherwise TWRP will get replaced with the stock Android recovery
  5. If you want to flash a GSI, skip to step 7
  6. Factory reset in TWRP and reboot to stock
  7. Wipe everything in TWRP excluding SD Card / USB OTG
  8. Put a GSI image file onto an SD Card, alongside GSI_Fix_boot.zip and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
  9. Flash the GSI image, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, flash GSI_Fix_boot.zip, wipe cache and reboot.
  10. Enjoy :)

Current bugs
  • Encryption/Decryption on stock does not work, you cannot read the internal storage while using the stock firmware
  • ADB and USB connection / USB OTG does not work

Latest release: https://drive.google.com/file/d/1Nbrmn7BgA3BxA1bqnLXYMuCY4KjpR0Vn/view?usp=sharing

Social media
 

Attachments

  • Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
    3.4 MB · Views: 1,997
  • GSI_Fix_boot.zip
    376.3 KB · Views: 1,838
Last edited:

ZemoDroid

Senior Member
Feb 27, 2015
61
7
Biecz
I'm stuck at GSI (PixelExperience) installation. I've extracted the img file on sd card and the wizard is asking which partition should be used to flash image (boot,recovery,product image,system image,vendor image).
 

moogle

Member
Oct 30, 2007
32
4
A few Questions about the process

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:
#include <std_disclaimer.h>
/*
 *
 * We are 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 ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *
 */

I’d recommend to read everything in this post, if you care about your phone.
  1. If you already unlocked your bootloader, start with step 3.
  2. First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
  3. Flash Galaxy A20e TWRP.tar via Odin or heimdall
  4. Reboot into TWRP AS SOON AS THE FLASHING PROCESS IS DONE because otherwise TWRP will get replaced with the stock Android recovery
  5. If you want to flash a GSI, skip to step 7
  6. Factory reset in TWRP and reboot to stock
  7. Wipe everything in TWRP excluding SD Card / USB OTG
  8. Put a GSI image file onto an SD Card, alongside GSI_Fix_boot.zip and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
  9. Flash the GSI image, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, flash GSI_Fix_boot.zip, wipe cache and reboot.
  10. Enjoy :)

Current bugs
  • Encryption/Decryption on stock does not work, you cannot read the internal storage while using the stock firmware
  • ADB and USB connection / USB OTG does not work

Latest release: https://drive.google.com/file/d/1Nbrmn7BgA3BxA1bqnLXYMuCY4KjpR0Vn/view?usp=sharing

Social media
,
Hey thanks for this, I´ve got a few questions about the process that might also help others.
Do you recommend this method of rooting still over the new method using Magisk?
Do we still need to wipe everything in TWRP after first boot? And what specifically steps should we take to wipe?
Can you recommend any specific GSI images that are known to boot on the A20e (A202F) because so far I've tried LineageOS 17.1 / AOSP system -quack-arm64-ab-gapps.img and system -quack-arm64-ab-vanilla.img / Crdroid and nothing gets past the loading icon.
Do we still need to flash Disable_Verity_ForceEncrypt and GSI_Fix_boot.zip if not installing a GSI ?
 

moogle

Member
Oct 30, 2007
32
4
a few notes

for anyone else. It helps if you boot into the rom and install magisk manager via APK (recent version is fine) before installing it via TWRP. After I did that rooting worked properly.
Lost ADB for some reason though, might be unrelated.

I also think that the a20e (SM-a202f) is an A device and not an A/B partition device at least according to treble check app.
ADB and USB connection / USB OTG does not work
oh.....right. that stinks
 

physwizz

Senior Member
Sep 16, 2013
3,484
755
Sydney
,
Hey thanks for this, I´ve got a few questions about the process that might also help others.
Do you recommend this method of rooting still over the new method using Magisk?
Do we still need to wipe everything in TWRP after first boot? And what specifically steps should we take to wipe?
Can you recommend any specific GSI images that are known to boot on the A20e (A202F) because so far I've tried LineageOS 17.1 / AOSP system -quack-arm64-ab-gapps.img and system -quack-arm64-ab-vanilla.img / Crdroid and nothing gets past the loading icon.
Do we still need to flash Disable_Verity_ForceEncrypt and GSI_Fix_boot.zip if not installing a GSI ?
1. This method does use Magisk
The tar file contains boot.img patched with Magisk
It also contains recovery.img and vbmeta.img
2. The boot.img is from Android 10 firmware so you need to upgrade to Q first.
3 there is a step missing in the instructions
It should say

6. Reboot the A20e into TWRP and mount everything you can.
Click Wipe then Format Data (not just wipe) - don't restart
Flash Disable_Dm-Verity_ForceEncrypt
Reboot to recovery and wipe both caches
Reboot system .

You can then backup boot, data and system for stock.
You can then install GSIs
 
Last edited:

moogle

Member
Oct 30, 2007
32
4
I'm having some major problems with sd cards not being recognized by google play store as external storage and whatsapp unable to download images. any idea what it might be?
 

moogle

Member
Oct 30, 2007
32
4

Already have, and LOS 17.1 and AOSP system-quack-arm64-ab-vanilla
all of them got stuck at boot icon for an hour. Thats why I went back to stock.

I'm more interested in why I cannot seem to install discord or firefox from the app store, or whatsapp cannot download images.
 

physwizz

Senior Member
Sep 16, 2013
3,484
755
Sydney
Already have, and LOS 17.1 and AOSP system-quack-arm64-ab-vanilla
all of them got stuck at boot icon for an hour. Thats why I went back to stock.

I'm more interested in why I cannot seem to install discord or firefox from the app store, or whatsapp cannot download images.

Go into magisk and hide any apps that misbehave
 

moogle

Member
Oct 30, 2007
32
4
Go into magisk and hide any apps that misbehave

Tried it, no change, there's no apps misbehaving, just strange sd storage card behaviour

Is the SM-A202F/DS supported by these methods, I noticed in some other threads it wasn't working back in March, that's the unit I have.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    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:
    #include <std_disclaimer.h>
    /*
     *
     * We are 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 ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at us for messing up your device, we will laugh at you.
     *
     */

    I’d recommend to read everything in this post, if you care about your phone.
    1. If you already unlocked your bootloader, start with step 3.
    2. First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
    3. Flash Galaxy A20e TWRP.tar via Odin or heimdall
    4. Reboot into TWRP AS SOON AS THE FLASHING PROCESS IS DONE because otherwise TWRP will get replaced with the stock Android recovery
    5. If you want to flash a GSI, skip to step 7
    6. Factory reset in TWRP and reboot to stock
    7. Wipe everything in TWRP excluding SD Card / USB OTG
    8. Put a GSI image file onto an SD Card, alongside GSI_Fix_boot.zip and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
    9. Flash the GSI image, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, flash GSI_Fix_boot.zip, wipe cache and reboot.
    10. Enjoy :)

    Current bugs
    • Encryption/Decryption on stock does not work, you cannot read the internal storage while using the stock firmware
    • ADB and USB connection / USB OTG does not work

    Latest release: https://drive.google.com/file/d/1Nbrmn7BgA3BxA1bqnLXYMuCY4KjpR0Vn/view?usp=sharing

    Social media
    1
    I'm stuck at GSI (PixelExperience) installation. I've extracted the img file on sd card and the wizard is asking which partition should be used to flash image (boot,recovery,product image,system image,vendor image).

    System
    1
    The A202F is an A/B device, despite what Treble Checker apps say. Only A/B GSIs will boot on it, as far as SD Card issues go, I cannot reproduce them, SD Cards work perfectly well in any GSI I've tried.

    Yes
    The a205xx is a fake ab (a plus SAR)
    Glad to hear the GSIs are working for you.
    Any custom ROMs for your device?
    1
    Possibly... Although this guide written in the Q timeframe so... Give it a go if you wish. Btw @KineSight, where are the A20 instructions?
    Custom Vendor for Android 11 has not been created for A20/A20e yet. That's why everyone is still on Android 10 Based Vendor for Android 11 ROMs.

    Since you are on Android 11 and an A20e user, I am not familiar with your issues as I am an A20 user on Android 10 .

    _ _ _

    Not sure if this will help but when you are flashing the Custom ROMs - make sure that you are NOT using the OneUI Vendor.

    IF there is NO 'Vendor.img' in the Custom ROM zip then download the A20 Custom Vendor from here and flash with the Custom ROM when installing in TWRP.