[Root] [guide] Samsung Galaxy A20 rooting guide

[Blain_Cruel]

so it was not clear. can the metro pcs sm-a205u be rooted or not?

 

[physwizz]

so it was not clear. can the metro pcs sm-a205u be rooted or not?

no
sorry

 

[physwizz]

Hi Friends!

I know this thread is already too long, but can anyone tell me if this works with my Samsung Galaxy A20s , Model number SM-A207F/DS ?
Android version 9.

Thank you for your time.

Try this

12. Backup data. It will be wiped.
13. Turn phone off
14. Hold vol- and vol+ and plug in power cable attached to pc then release HOLD DOWN THE VOLUME UP BUTTON to unlock bootloader
15. Follow the instructions to unlock vol + to select yes to confirm.
17. Press power key to unlock bootloader.
18. Reboot and reactivate developer options and enable usb debugging. Don't enter too much data at this stage as you will lose it again later.

 

[MarlonKaye]

Hi! You told me previously that it has been tried on A20s without success.

Try this

12. Backup data. It will be wiped.
13. Turn phone off
14. Hold vol- and vol+ and plug in power cable attached to pc then release HOLD DOWN THE VOLUME UP BUTTON to unlock bootloader
15. Follow the instructions to unlock vol + to select yes to confirm.
17. Press power key to unlock bootloader.
18. Reboot and reactivate developer options and enable usb debugging. Don't enter too much data at this stage as you will lose it again later.

 

[physwizz]

Hi! You told me previously that it has been tried on A20s without success.

I'm not sure if they used the long press bit
It may be a hidden option on your device

 

[as58910160]

Has a way been found to OEM-unlock USA versions?

Specifically SM-S205DL Tracfone on Feb 2020 Security Patch

Sent from my Samsung Galaxy Note 9 using XDA Labs

 

[physwizz]

Has a way been found to OEM-unlock USA versions?

Specifically SM-S205DL Tracfone on Feb 2020 Security Patch

Sent from my Samsung Galaxy Note 9 using XDA Labs

Can you see OEM unlock in the developer options?

 

[as58910160]

Can you see OEM unlock in the developer options?

Unfortunately I cannot. I have tried the mentioned methods to reveal OEM unlock.

I should mention... Even if it's not possible, I only asked because this portion of the guide was misleading...

This method should root your Samsung Galaxy A20 (all models except SM-A205U).

Sent from my Samsung Galaxy Note 9 using XDA Labs

 

[physwizz]

Unfortunately I cannot. I have tried the mentioned methods to reveal OEM unlock.

I should mention... Even if it's not possible, I only asked because this portion of the guide was misleading...

This method should root your Samsung Galaxy A20 (all models except SM-A205U).

Sent from my Samsung Galaxy Note 9 using XDA Labs

I will have to add your model too

 

[hannes22]

no touchscreen after rooting A20e

Hi Guys,

i tried rooting my SM-202F using Magisk 7.5.1 and Odin 3.14 but whenever i boot into the rooted OS, my touchscreen won´t work.
I tried the following two Builds with the correct language code..

A202FXXU3BTD1
A202FXXU3ASL4

both resulting in a not working touchscreen when booting to rooted OS, when i boot regualar OS without root, the touchscreen works fine.

Any Ideas?

 

[physwizz]

Hi Guys,

i tried rooting my SM-202F using Magisk 7.5.1 and Odin 3.14 but whenever i boot into the rooted OS, my touchscreen won´t work.
I tried the following two Builds with the correct language code..

A202FXXU3BTD1
A202FXXU3ASL4

both resulting in a not working touchscreen when booting to rooted OS, when i boot regualar OS without root, the touchscreen works fine.

Any Ideas?

Did you patch the boot.img

 

[hannes22]

Did you patch the boot.img

In my first try, i tried only patching the boot.img with magisk and flashing it but that did not work.
So for the last few rounds i always patched the whole "AP_a202....tar" using magisk which resulted in "successful install" but broken touch functionality.

I opened a new thread to this:
https://xdaforums.com/android/help/galaxy-a20e-sm-202f-touchscreen-magisk-t4128937

 

[physwizz]

In my first try, i tried only patching the boot.img with magisk and flashing it but that did not work.
So for the last few rounds i always patched the whole "AP_a202....tar" using magisk which resulted in "successful install" but broken touch functionality.

I opened a new thread to this:
https://xdaforums.com/android/help/galaxy-a20e-sm-202f-touchscreen-magisk-t4128937

this method works for a20e
https://xdaforums.com/showpost.php?p=80021195&postcount=4

 

[AOSP100]

this method works for a20e
https://xdaforums.com/showpost.php?p=80021195&postcount=4

I'm planning on getting a OnePlus 7T to replace my SM-A205U, but to make it worth keeping for longer enough I tried to install Lineage on it back in May/early June but no matter what I tried (Odin, Magisk, etc) nothing worked. The constant resets from unbricking the phone loosened the load a little bit but it didn't do enough even after having the Evie launcher since then or any other performance-oriented/lightweight launchers.

There's no OEM unlocking option either

So apparently, even managing to root your phone would trip an e-fuse and brick it at the hardware level. Instead of this all I got were constant errors during the flashing process that force me to flash the factory ROM back and try again

 

[rwio]

this method works for a20e
https://xdaforums.com/showpost.php?p=80021195&postcount=4

I can't get it to work without getting an unresponsive touch screen after reboot. I've tried the method in this thread to the letter, but no luck. After I've done the rooting and reboot into android the touch screen doesn't work.

The phone I'm using has Android 10 and U3 bootloader...
My bootloader is unlocked (and OEM-unlocking is visible, grayed out).
I'm patching the same firmware the phone had out of the box (I've also tried later/newer versions).
I've tried patching with both latest magisk manager and the canary version.
I've tried both the method in this thread patching only boot.img (boot.tar) and also tried patching the full AP_XXX.tar file as described by topjohnwu on github (it worked fine on the Samsung A10).

But I just keep getting an unresponsive touch screen after rooting. If I revert back to unrooted/unpatched firmware the touch screen works again.

 

[physwizz]

I can't get it to work without getting an unresponsive touch screen after reboot. I've tried the method in this thread to the letter, but no luck. After I've done the rooting and reboot into android the touch screen doesn't work.

The phone I'm using has Android 10 and U3 bootloader...
My bootloader is unlocked (and OEM-unlocking is visible, grayed out).
I'm patching the same firmware the phone had out of the box (I've also tried later/newer versions).
I've tried patching with both latest magisk manager and the canary version.
I've tried both the method in this thread patching only boot.img (boot.tar) and also tried patching the full AP_XXX.tar file as described by topjohnwu on github (it worked fine on the Samsung A10).

But I just keep getting an unresponsive touch screen after rooting. If I revert back to unrooted/unpatched firmware the touch screen works again.

Ask here
Telegram: https://t.me/ultimate_Pie2

 

[rwio]

I solved it. First I downloaded and flashed the newest firmware _without_ using a patched Boot.img or AP.tar-file. I.E, patching the same firmware the phone had out of the box did NOT work. After the firmware update I could successfully flash a patched Boot.img file and root the phone. I'm guessing it has something to do with Samsung updating the touch screen drivers since the phone was released.

 

[physwizz]

I solved it. First I downloaded and flashed the newest firmware _without_ using a patched Boot.img or AP.tar-file. I.E, patching the same firmware the phone had out of the box did NOT work. After the firmware update I could successfully flash a patched Boot.img file and root the phone. I'm guessing it has something to do with Samsung updating the touch screen drivers since the phone was released.

Great work

 

[physwizz]

I solved it. First I downloaded and flashed the newest firmware _without_ using a patched Boot.img or AP.tar-file. I.E, patching the same firmware the phone had out of the box did NOT work. After the firmware update I could successfully flash a patched Boot.img file and root the phone. I'm guessing it has something to do with Samsung updating the touch screen drivers since the phone was released.

You can create a TWRP here

https://xdaforums.com/android/general/guide-porting-twrp-source-t3843473/amp/

 

[Moogle]

You can create a TWRP here

https://xdaforums.com/android/general/guide-porting-twrp-source-t3843473/amp/

is the SM-A202F/DS still not supported?