[Root] [TWRP] [More] Android 10 (Q) Complete Guide for the A20 (A205xx)

[physwizz]

1. ROOT
The following procedures worked for me but I can't guarantee they will work for everyone.
Use them at your own risk

Save Your Data
Copy files to SD card or to usb or to computer
Use sms backup and restore app to save texts and phone calls

If Something Goes Very Wrong
Go here: https://forum.xda-developers.com/galaxy-a20/how-to/crash-recovery-t4068369


To Upgrade to Android 10
https://forum.xda-developers.com/galaxy-a20/how-to/upgrading-a20-to-android-10-t4087577


To Root and install TWRP
WARNING: Rooting your phone may be dangerous.
Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing!

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

For A20e (A202) go here

A20e Root,Kernel, TWRP and custom ROM

Root & TWRP from Xyn XDotnest https://forum.xda-developers.com/galaxy-a20/development/recovery-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767 Orange Fox Recovery from @Royna...

forum.xda-developers.com

For A20s (A207) a root method has not yet been devised.
They are working on it here
t.me/GalaxyA20SS


1. On phone developer options in settings allow OEM unlocking and enable usb debugging by moving both
sliders RIGHT


If you don't see the OEM unlock
-Disable Auto System Update
-Then disable Automatic date and time (Found in General Management) > then set the time back 14 days
-Go to software update then check for update and wait till it registers the device on server
-Once it's registered the OEM Unlock should be visible in the Developer Options

then connect phone to PC
2. Reboot into download mode by holding down both Vol up and Vol down
(You might need to long press vol up to unlock bootloader)
then press vol up to continue
3. Use Odin to flash recovery.tar into the AP slot.
Android Q recovery v3: https://mega.nz/folder/w5syHQbb#vm7XzXKlbRaDl1nDTMuuCg
Black themed recovery with mtp
https://mega.nz/file/twERlKSL#RsZttve-GBKBDVYpZYFoTUNQ3jQ7bLTOYkvLH6xVE2M

Android R recovery

78.9 MB file on MEGA

mega.nz

4. Reboot the A20 into TWRP and mount everything you can.
5. Click Wipe then Format Data (not just wipe) - don't restart
6. Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip (https://forum.xda-developers.com/attachment.php?attachmentid=4975463&d=1584732187)
7. Wipe both caches and Reboot into Recovery (for Android 10 you will need to flash Magisk 20.4)
8. Reboot system and enter all your data



To reboot into TWRP, hold down"vol up" and "power" during reboot.
Backup boot, data and system so you can restore them if you need to.



Note: restore may not work on Stock ROM. In that case you may need to use the hybrid back and restore method. (https://forum.xda-developers.com/galaxy-a20/how-to/backup-restore-hybrid-method-t4076437)

2. RECOVERIES

To Change to SkyHawk Recovery
1. download file https://mega.nz/file/AolzUJpR#ptySg13zpobaDZjagatNkDKQdnAgVPt2I_C2k-ecqPk
2. unzip img file
3. flash img file into Recovery slot from TWRP
4. reboot into TWRP
Boot & data will backup and restore but system is missing from the Sky hawk backup list
MTP works at the OS level and can be activated at the recovery level using the cloud icon in the mount section of Sky Hawk recovery.


Modified Recoveries (TWRP 3.3 System backup)
I modified these recoveries so that the backup list has only boot, data and system
They are all TWRP 3.3 and backup /system
Modified TWRP from @crazo7924 original : https://mega.nz/file/J9lFXYRK#fztwPbunC0PMZW3IUBpYUFobTxhsm3Kp1KFUvrM4N7o
Modified SkyHawk from @crazo7924 original : https://mega.nz/file/MoshGSTY#U1SDjiUqYoFPMIOHuQSx6wKoXAzoP4_UCYWkA9F-9rk
Modified black mode TWRP with MTP from @Agrim720 original: https://mega.nz/file/k8VXhAiD#6jSiapRoYJo1cxeoPvu9Yz6pF8zJr0D5lfeI4CBXPAA
TWRP with Vendor included in backup list: https://mega.nz/file/E8cVmKKT#U-_GnsISW1Rmdj4NU9R7ucUxA5QpPaXbc0oYnP935RM
TWRP built on physwizz_kernel_v1. 49
https://mega.nz/file/4o9gBSDA#hWA020SdvqJ9XEIf4TAZI9tiqjlsd2HfQGbQCI30Gjw

Download the one you want
Reboot to recovery
Install => img => recovery
Reboot to recovery.
Boot, data & system will now work.


TWRP 3.4
https://forum.xda-developers.com/galaxy-a20/development/twrp-3-4-a20-t4144327

3. Custom ROMs

Installing Custom ROMs

1. Backup calls and texts using sms backup and restore .
2. Reboot into twrp.
3. Backup boot, data, system, vendor, product to sd card in case you want to go back to your current system
4. Wipe caches, data, system
5. Install Rom and your kernel
6. Format data (not just wipe) and then Install dmverity
7. Wipe caches. Don't reboot
8. Go to main menu. Select reboot. Select recovery
9. Reboot to system
10. Wait a long time (up to 10 minutes?)
Select your language
11. Restore data from smart switch or Google restore
or
Skip through setup and Restore data from twrp
12. Install Magisk if you want root
13. Install dmverity (in case step 8 didn't work)

If you need to install GApps
14. Wipe, advanced wipe
15. Select system, repair or change
16. Resize file system
17. Install GApps

To backup ROM before you go to a new system
Backup boot, data, system, product, vendor

Find custom ROMs here
Samsung Galaxy A20 ROMs, Kernels, Recoveries, & Ot


Jumping between ROMs
I recently discovered that there is an easy way to jump from one ROM to another.
For example if you are on S20 Port6 and you want to jump to S10+ or to Stock.

You need to have backups that include Vendor because each of these runs with a different Vendor.
This isn't needed to jump from Port 6 to a GSI and back because GSIs are usually independent of Vendor.
To restore to a previous ROM
1. Wipe both caches, data & system
2. Restore boot, data, system & vendor.
3. flash Magisk uninstaller
4. Reboot

You need to use this TWRP which includes Vendor in the backup list.
https://mega.nz/file/E8cVmKKT#U-_GnsISW1Rmdj4NU9R7ucUxA5QpPaXbc0oYnP935RM


4. KERNELS

Custom kernels here
Samsung Galaxy A20 ROMs, Kernels, Recoveries, & Ot

physwizz Latest
physwizz collection https://t.me/physwizz2

5. TWEAKS

To remove unwanted system apps
Use a root explorer to delete the apps you don't want from
/system/app
And
/system/priv-app

Reboot to recovery
Wipe caches
Reboot

Some apps might need to be deleted from app tray
You could also use file manager from TWRP but you have to go to
system/system/app
and
system/system/priv-app


For more debloating.
https://forum.xda-developers.com/ga...debloat-final-samsung-a20-android-10-t4171307


Swapping Kernels
If you want to run your current ROM with a kernel you had on a previous ROM just restore the boot (only) from the previous ROM. If you go from Magisk 20.4 back to Magisk 19.3 flash Magisk uninstaller first.

To Hide Root
Some apps don't work if your phone is rooted
Go to Magisk hide
Tick the app that won't work in root

To Improve Performance and Battery Life of Stock ROM
Use the Android Q tweaks from @hooooossamq here
https://forum.xda-developers.com/ga...erformance-build-prop-v1-0-stock-rom-t4073303

6. GSIs

List of all GSIs:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Always choose Android Q arm64 ab GSIs
Install guide: https://forum.xda-developers.com/showpost.php?p=80184282&postcount=2

Pixel Experience, EvolutionX & Havoc:
https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457

Installing a GSI

1. Begin with stock ROM
2. Reboot into TWRP ( then mount product - system - vendor)
Back boot data and system
3. Wipe both caches, data & system
4. Install GSI
5. Flash Magisk and physwizz GSI kernel from here https://forum.xda-developers.com/t/kernel-physwizz-kernel-for-the-galaxy-a20.4180107/
6. Reboot.
7. Installing GApps
Some GSIs come with GApps. If you're doesn't and you want to have GApps, then use this method.

a.-Resize system partition so you can install OpenGAPPS, go to wipe, advanced wipe, select system, select repair or change file system and select resize file system. If you get error 1 unmount and mount the system partition and try again
b. Install GApps

Credits:
Ultimate Q : @shumway66 & @Gollo99
Kernel:
Minh's: @minhka98 (https://forum.xda-developers.com/galaxy-m30/development/custom-kernel-galaxy-m20-galaxy-m30-t4094369)
Quantum: CarlosBurelo
Recoveries:
@Agrim720
@crazo7924 (A30 dev. co-opted by shumway66)

Development of new ROMs and kernels is happening here
Telegram
Series A: https://t.me/ultimate_Pie2
A20/A20e: https://t.me/Galaxy_A20_official
physwizz collection https://t.me/physwizz2

physwizz collection

A collection of guides, kernels and ROMs. Guides Complete Guide to the A20 GSIs for the A20 Quick Root and TWRP for the A20 Making my First Kernel for the A20 A20 Rooting Guide Making Your Own ROM Making Your Own Version of QwizzROM-a20...

forum.xda-developers.com

 

[physwizz]

Kernel Frequency Ranges MHz

Stock
Big: 936 - 1560
Little: 449 - 1352
GPU: 343 - 676

Minh's 14.6
Big: 208 - 2184
Little: 208 - 1690
GPU: 343 - 1300

Quantum v2
Big: 936 - 2184
Little: 449 - 1690
GPU: 343 - 676

Eureka 4.3
Big: 208 - 2184
Little: 208 - 1690
GPU: 343 - 1300

physwizz_kernel_v1.45
Big: 208 - 2080
Little: 208 - 1690
GPU: 343 - 676

CPU Benchmarks

Stock
244 900

Minh's 14.6
Standard 267 909
SamsungDeviceHealthManager removed 272 933
Overclocked 314 1032
View attachment 5031615View attachment 5031605View attachment 5031607

Quantum v2
Standard 238 721
Overclocked 261 751
View attachment 5031521View attachment 5031523

GPU Benchmarks

Stock
682 - 696

Minh's 14.6
Minh's 14.6 standard 1080
Minh's 14.6 with SamsungDeviceHealthManager deleted 1266
Minh's 14.6 overclocked 1316
View attachment 5019857View attachment 5019859

Quantum v2
Quantum v2 standard 673
Quantum v2 overclocked 707
View attachment 5019947View attachment 5019949

Eureka 3.0
Standard 1080
Overclocked 1391


How to Overclock[/I]
Use a root explorer to
Cut and paste /system/priv-app/SamsungDeviceHealthManager on to a different folder. (In case you want to put it back later)
Reboot to recovery
Wipe caches Reboot
Use Hktweaks to set minimums to highest stable values and leave it running in the background.

A20 KERNEL COMPARISON ON ZROM V2

Minh 14.7 with Magisk 20.4
GPU 1306
CPU 313 1059
GPU reverts to 1300 343
Antutu 139824

Eureka 3.0 with Magisk 20.3
GPU 1391
CPU 282 997
GPU stays at 1300 1300
Antutu 140482

Eureka 3.7
Install Magisk Uninstaller
Install kernel
Install Magisk 20.3
Reboot
You can install Magisk 20.4 later

Benchmarks
GPU 1395
CPU 276 975
Antutu: 140720

Eureka R4.3
GPU 1396
CPU 315 1099


Minh GPU fix
If you want the GPU to stay on your settings you need to apply this fix

sys/devices/platform/11500000.mali/dvfs
sys/devices/platform/11500000.mali/dvfs_min_lock
Chmod 000 (use a root explorer to remove all ticks in properties)

Don't restart
This process must be repeated if you do.

GPU benchmark increases from 1306 to 1379

Spectrum in post #3

 

[physwizz]

SPECTRUM
Both Minh14.7 and Eureka 3.0 have Spectrum Support but Minh 14.6 works best because Spectrum can fit GPU settings.

@minhka98 has given us a Spectrum installer.
Install, reboot.
Access the pull down menu
Tap 3 dots
Tap button order
drag the spectrum icon into the pull down menu.
Reboot

It gives you 4 kernel profiles on Hktweaks which can also be accessed from the pull down menu.
1. Balanced :
2. Performance:
3. Battery:
4. Gaming:
Installer
https://drive.google.com/file/d/17v...8840FSPc6_1yRxlT2YWgQNbrTTJb/view?usp=sharing

GPU CONTROL

Spectrum can control the GPU settings in Minh 14.6 but not in Eureka 3.0 or Minh 14.7.

You can change the GPU settings in Eureka 3.0 but not in Minh 14.6 or 14.7 unless you apply the GPU fix.

 

[Engineer_Virus]

Great work

 

[physwizz]

Sky hawk recovery now available

 

[jajk]

@physwizz Like magic, Sky Hawk Recovery falls out of the sky with no information on who built / ported it for A205 and no credit to the original developer. Themes don't save but no idea if that is peculiar to the A20 build, a fault in all Sky Hawk recoveries or who to report that to??? Don't get me going on the lack of Minh kernel source code or change logs..... Maybe this info is available on Telegram but it is not available here on this forum which is where it is meant to be.

 

[physwizz]

A big thank you to all of these developers who have donated their time and energy to keep the A20 at the cutting edge as we move into Android Q

Ultimate Q : @shumway66 & @Gollo99
Kernel: @minhka98
Recoveries: @crazo7924

 

[physwizz]

A big thank you to all of these developers who have donated their time and energy to keep the A20 at the cutting edge as we move into Android Q

Ultimate Q : @shumway66 & @Gollo99
Kernel: @minhka98
Recoveries: @crazo7924

 

[physwizz]

Sky hawk recovery now available

Some users have reported a faster backup and restore.
I haven't tested yet
MTP not working in recovery mode

 

[jajk]

@minhka98 Is there a possibility of patching your kernel to support MTP at recovery level in the same way the previous afaneh Pie kernel was patched to achieve this? @crazo7924 Themes settings do not save in your A205 Sky Hawk recovery.

 

[crazo7924]

@crazo7924 Themes settings do not save in your A205 Sky Hawk recovery.

Yes, applied themes don't persist after a reboot back to recovery. I'll look into the issue.

 

[Gollo99]

A big thank you to all of these developers who have donated their time and energy to keep the A20 at the cutting edge as we move into Android Q

Ultimate Q : @shumway66 & @Gollo99
Kernel: @minhka98
Recoveries: @crazo7924

Thanks bro

 

[physwizz]

@minhka98 Is there a possibility of patching your kernel to support MTP at recovery level in the same way the previous afaneh Pie kernel was patched to achieve this? @crazo7924 Themes settings do not save in your A205 Sky Hawk recovery.

Is the MTP at recovery level due to the kernel inside recovery?

 

[jajk]

@physwizz If you go back to when it was fixed for Pie TWRP, it was the afaneh kernel that fixed it, not TWRP. You can still see what he did in his github but unfortunately, we cannot see anything of the minh Q kernel alterations as the link provided just shows the original cloning of afaneh's project.....

 

[physwizz]

@physwizz If you go back to when it was fixed for Pie TWRP, it was the afaneh kernel that fixed it, not TWRP. You can still see what he did in his github but unfortunately, we cannot see anything of the minh Q kernel alterations as the link provided just shows the original cloning of afaneh's project.....

I thought the 2 kernels operated at different times.
The os kernel is running at os level and the recovery kernel operates at recovery level.

 

[jajk]

@physwizz Could be right???? So who made the Q version of TWRP and what kernel does that use?

 

[physwizz]

@physwizz Could be right???? So who made the Q version of TWRP and what kernel does that use?

Crazo7924 did both

 

[physwizz]

@physwizz Could be right???? So who made the Q version of TWRP and what kernel does that use?

Why do you need it at recovery level?

 

[jajk]

@physwizz I have some GPS mapping files that are locked while at O.S level so I can't copy these unless in recovery. I do this on a regular basis to transfer these files across to other devices so it is much easier not to have to go through an intermediate process of copying to USB OTG or SDCard.

---------- Post added at 08:45 AM ---------- Previous post was at 08:45 AM ----------

[/COLOR @physwizz I have some GPS mapping files that are locked while at O.S level so I can't copy these unless in recovery. I do this on a regular basis to transfer these files across to other devices so it is much easier not to have to go through an intermediate process of copying to USB OTG or SDCard.

 

[physwizz]

@physwizz I have some GPS mapping files that are locked while at O.S level so I can't copy these unless in recovery. I do this on a regular basis to transfer these files across to other devices so it is much easier not to have to go through an intermediate process of copying to USB OTG or SDCard.

---------- Post added at 08:45 AM ---------- Previous post was at 08:45 AM ----------

[/COLOR @physwizz I have some GPS mapping files that are locked while at O.S level so I can't copy these unless in recovery. I do this on a regular basis to transfer these files across to other devices so it is much easier not to have to go through an intermediate process of copying to USB OTG or SDCard.

Oh