[GUIDE] [TWRP] [Root] How to install TWRP and ROOT on a20s (SM-A207F) - Samsung Galaxy A20 Guides, News, & Discussion

HEX_101​
Requirements:​[+] Have a Linux distro installed on your pc
[+] A Brain
[+] An A20s and a USB cable
Initial steps:​[+] Unlock the phone's bootloader (won't teach you how since it's the easiest part)
[+] Download GSI from your pc make sure to download system-roar-arm64-ab-vndklite-gapps.img.xz [Note: This is pre-rooted GSI]
[+] Extract it on a folder (make sure to have everything organized)
[+] Download heimdall_flash_file.zip and extract in the same folder
[+] Install heimdall through terminal (sudo apt-get install heimdall-flash -y)
Flashing a GSI:​[+] Reboot your phone into download mode (turn off, hold both volume keys and insert a usb cable already connected to your pc)
[+] Open terminal and go to the files folder
[+] Write "heimdall flash --SYSTEM sysnull.img --VENDOR vndnull.img" (without ""), phone will reboot, go into download mode again (If it doesn't boot to download mode boot it manually)
[+] Write "heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-gapps.img --VBMETA avbnull.img" (without "") Then boot into stock recovery and do a factory reset (to boot into stock recovery unplug your cable and hold both volume+ and power buttons)
Flashing TWRP:​[+] Boot your phone into system and do the initial setup (don't restore any apps or data, only your google account) and download "Termux" apk and install it
[+] Download TWRP file on your phone , make sure it's inside your "downloads" folder and rename to recovery.img
[+] Enter termux and type "su" (without "")
[+] Write "dd if=/sdcard/Downloads/recovery.img of=/dev/block/bootdevice/by-name/recovery" (without "") if twrp image isn't in your downloads folder it will fail so make sure it's there
[+] Turn off the phone and boot into twrp, on your pc download Mutidisable
[+] On twrp wipe Data, Dalvik/ART, Cache and Internal storage, then FORMAT data, reboot to twrp
[+] Move "Multidisabler" from your pc to your phone's internal storage
[+] Flash "Multidisabler" on twrp then do the same wipes as before then reboot.
[ It's not the best guide so if you have any questions please ask. ]
Note: t.ly/Xcxg​

Duplicate of https://forum.xda-developers.com/t/...stall-twrp-and-root-on-a20s-sm-a207f.4293965/
Thread closed

Related

[Q] Please clear me up :)

I have a defy with 2.51 from Red Bull in Austria.
I want to install CM7
what i have done so far:
rooted
recovery installed
nandroid backup done
what i want to know:
If i need to send it in for repair, is everything i need to do to flash back the nandroid? or is this not possible because of the lost of downgradability on 2.51?
it would be nice form you to tell me this things
If you have a nandroid of your system, and a fixed SBF of your 2.51, all you need to do to send it to warranty is restore your nandroid then flash the fixed SBF.
Landroid said:
I have a defy with 2.51 from Red Bull in Austria.
I want to install CM7
what i have done so far:
rooted
recovery installed
nandroid backup done
what i want to know:
If i need to send it in for repair, is everything i need to do to flash back the nandroid? or is this not possible because of the lost of downgradability on 2.51?
it would be nice form you to tell me this things
Click to expand...
Click to collapse
if you don't flash the full SBF, your downgrade-ablility is fine.
here the safe step to install CM7 to keep your downgrade-ability:
FROM ECLAIR
1. get root, install recovery app, reboot
2. place nandroid backup of 3.4.2-177 to your sdcard
3. turn off usb debuging, go to your custom recovery app: tap install recovery (allow root access when needed), tap reboot recovery
4. from custom recovery, wipe data, then wipe cache
5. then restore nandroid
6. choose reboot system now, BUT IMMEDIATELY go to bootloader (press and hold vol.up immeditely after phone reboot)
7. defy is in bootloader state, connect usb (make sure your computer has usb driver installed), open RSD-Lite 4.9 to flash the Fixed SBF of 3.4.2-177
8. let the process begins and wait untill phone fully starts.
now you in Froyo 2.2.2 (build number 3.4.2-177) state, with still have a downgrade-ability.
9. place CM7 beta5 zip and google app zip to sdcard root
10. make sure that nandroid backup rom you just restored is rooted (there is superuser app on there),
and UNINSTALL any custom recovery app you can found (usualy named SD recovery, System Recovery, etc)
11. install bootmenu instead (there's a custom recovery inside that bootmenu)
-download this file (bootmenu), create folder named "bootmenu", and extract zip files into that folder.
-copy "bootmenu" folder to your sdcard root (it should like this /sdcard/bootmenu)
-turn on usb debuging
-do this from terminal emulator or with adb in command prompt:
Code:
$ su [COLOR="Gray"](look up your phone immediately, allow root access)[/COLOR]
# cp -R /sdcard/bootmenu /data/bootmenu
# cd /data/bootmenu
# chmod 755 *
# ./install.sh
[COLOR="gray"]--------- it should says installation done and says please reboot. but don't reboot now.[/COLOR]
# rm -R /data/bootmenu
--------- reboot now
12. you will automaticaly go to bootmenu, choose boot, and set the default boot to 2ndInit
13. go back, go to recovery>custom recovery: wipe data, then wipe cache
14. choose install zip from sdcard, choose CM7 beta5 zip
15. choose install zip from sdcard again, choose google apps zip
16. reboot system now, first boot seems much longer
17. it's done.
if you want to go back to eclair
1. turn off usb debuging,
2. copy nandroid backup of your ECLAIR to sdcard, put it in /sdcard/clockworkmod/YourEclairNandroidFolder (must "clockworkmod" not "goapkrev")
3. reboot phone
4. have a attention, when blue lights is on while motorola logo shows, immediately press vol.down
-you will go to bootmenu, go to recovery>custom recovery
-wipe data then wipe cache
-choose restore, choose your eclair nandroid backup
5. choose reboot system now, BUT IMMEDIATELY go to bootloader (press and hold vol.up immeditely after phone reboot)
6. defy is in bootloader state, connect usb, open RSD-Lite 4.9 to flash the Fixed SBF of your Eclair Build 2.51 Aus Red Bull
(must a same build number with your nandroid backup, i can't find a link for that build number)
7. let the process begins and wait untill phone fully starts
8. it's done.
now you back on Eclair
thank you very much

How to Root the CAT s60 ... ... and more !!!

Since i am afraid, that my Guide will dissapear in the other Thread,
i post this guide in a new Thread !
I have just uploaded a collection of, how i have named it, - s60 essentials - there are ALL files included to flash stock, update to .033, flash twrp recovery and root.
(this is for Win7 x86, you have to check if it works for other versions yourself, sy..)
Here is my collection
HOW TO.... Stock, Update, custom recovery and root your s60 !!!!
Disclaimer: if you brick your phone, it's your fault, i have tested this way of rooting my s60 now for a several times and it works 100%
SO READ TWICE, CHECK TWICE, BEFORE YOU CLICK ONCE !!!!! i will not take any responsibility !!!
Thanks to everybody who contributed here in this thread (Cesarq, OpenMinded, Tuschi, BetonJohn, etc.......) the software in the link
is the collected data, freely available in the net and linked in the original Thread several times, i have only bundled one package and wrote
this, hopefully usefull guide.
in principle do as follows: (I will only explain once how to sideload or load via recovery, afterwards i will only state what kind and what file)
Prerequists
- install USB drivers (for recovery and adb)
- install "minimal ADB and fastboot"
- copy the two updates (update032 & update033) into the folder, where you have installed "minimal ADB and fastboot" (makes live easier later)
- install QPST (the version of QPST is the one from Androidmtk and should be virusfree
(The version of QFIL in my collection is the one without reboot, so you have to reset/reboot your phone manually (resetbutton below hatchdoor on your phone) whenever
stated in this guide.
- format micro SD card in fat32 ! and copy SuperSU.zip onto it.
- connect a WORKING USB cable to your phone (Not to your PC atm !!!)
getting twrp (for saving your old firmware only)
- power off phone.
- start minimal adb on your PC
- start QFIL (part of QPST) on your PC
- press VOL+ & VOL- simultanousely and connect phone with PC (it will vibrate once, top right LED starts blinking red, screen stays black) - DOWNLOAD MODE -
(just in case: to leave Download mode, press and hold power button for apprx. 15 seconds)
- as soon as you connect your phone to the PC, QFIL should show the Phone/port in the topline allready, if not, either try to manually select the port, or you probably still have
a problem with the USB drivers !
- tick in QFIL Flat Build (top left)
- QFIL - select Programmer, "browse" to the saved location of "update-twrp-recovery-nobootpatch" and select the "prog_emmc.blablabla...mbn" file and doubleclick
- QFIL - "load XML" ,select rawprogramm, doubleclick, select patch0, doubleclick
- QFIL - click on "download"
- if everything was OK up till now, it should start download - BE PATIENT- and read the status window on QFIL, when it shows "finish download"....
- disconnect phone from PC
- press and hold simultanousely POWER and VOL+ and use a small tool to push the reset button on the phone under the hatch, while still pressing Power and Vol+ !
- the phone should now be in twrp recovery. If so, do a full backup now to your (allready inserted and fat32 formatted) microSD card!!!
when done
- Power off your phone !
flashing stock 31.02
- enter download mode again (Vol+ & Vol-, connect phone to PC.......)
- this time in QFIL, browse in programmer path to "s60_stockFW_31.02" and select the programmer from there
- load XML's (the onces that belong to Stock31.02)
- start download... this will take a while !!!! BE PATIENT !!!!
- when QFIL status window shows finish download, push the reset button on the phone and let it reboot.
- it is normal, that the phone should restart itself 2, maximum 3 times at the first start, but sometimes it ends up in a bootloop (Cat Logo, reboot, CAT logo, reboot, etc, etc, .......)
(The bootloop mainly happens, if you clear, in twrp recovery, the whole OS, but that's no issue either...)
- if it ends up in a bootloop, no worries, just continue ! Believe me, i did the process now several times ! )
you are back on stock 31.02 !
-Power off your phone again
Updating to 032
- bring up minimal ADB sideload on your PC (start it, if not allready done in previous step (getting twrp)).
- press and hold POWER and VOL+ button on your phone - RECOVERY MODE -
- when in stock recovery select (with Volume keys) "adb sideload" and click the Powerbutton
- connect your phone to the PC
- on PC, type into the black ADB Terminal window "adb sideload update032.zip" and hit enter
- if drivers are there, phone will start downloading the update now.
- when complete, select clear cache, and clear data then reboot your phone.
- again, same as in the step (flashing stock), if bootloop, no worries, just continue, if it boots up, let it boot up and then..
you're on 032 now
- Power off the phone again
Updating to 033
- do the same steps as described under "Updating to 032" only difference, type in adb window " adb sideload update033.zip"
After updating to 033 your phone should boot up normally now, NO MORE BOOTLOOP !
getting twrp
- this is the same step as above "getting twrp" only difference, this time, no backup needed and...
- when in twrp-recovery, select "install" browse to your micro SD-card, and...
- install SuperSU.zip from SDcard.
- once more, clear cache and data and reboot.
The phone should boot up now, you should be on FW 033, with custom recovery and root !!!
That's all !!!
Would a TWRP or fastboot flashable stock recovery let us apply future OTA updates without wiping and starting from stock 031 if we're using systemless root like Magisk?
From stock recovery you can reboot to bootloader which puts us in fastboot (you can select boot mode with Vol +/-), so I'm thinking if we could boot TWRP from fastboot (without flashing, obviously), we could back up the stock recovery. Then when the next update comes around, we flash stock recovery back, apply the update, then reflash TWRP.
I tried fastboot boot recovery.img from update-twrp-recovery-nobootpatch but I got
FAILED (remote: unknown command)
and rebooting into recovery from there just got me stock recovery which makes sense.
QCN please
Hi guys, can anyone share me QCN backup of S60 because i've lost it! Thanks.
Last update for Android 6.0 was from 766 days ago.
Any suggestions on how to patch?
Thanks a million

[Root] Huawei y6 pro tit-u02 (mtk 6582).

The Stages:
1. Unlocking the bootloader. (search goolge: unlock bootloader huawei)
2. Flashing Custom Recovery.
After unlocked bootloader, you download file root and recovery: https://drive.google.com/file/d/1uNu7oQj1Ja7xfKO8nEkQVnkrtjEg8aAF/view?usp=sharing
==> extract file
==> reboot phone into bootloader ( shutdow, then hit and hold power+ volume up, ==> select fastboot)
==> In PC, Click right mouse while holding left Shift. Run the codes bellow:
fastboot flash recovery recovery.img
NOTE: Once the flash is complete Do not reboot into system. Hold VOL+ and run the following command:
fastboot reboot
Then select Recovery and press VOL- to confirm.
3. Flashing SuperSU
a. Download file boot: https://drive.google.com/file/d/1ztmTtl8NiJD431ARfJI-cUomLH9XXyIF/view?usp=sharing
and place it in your SD card.
b. Enter the recovery mode, Select Flash boot Image and browse for Boot.img you have downloaded and placed in SD card. Flash the boot image and clear cache ONLY then REBOOT into system. After that, Place the SuperSU-v2.79.zip in your Sd card.
c. Reboot into recovery and select Install zip then browse for SuperSU-v2.79-SYSTEMMODE.zip and confirm Install. Reboot your system and Voila You had you Huawei Y6 Pro Rooted.
thread closed until the download links will be available

Levovo TB-X606F Rooting Issue

I have a Levovo Tab M10 FHD Plus TB-X606F running android 10.
After having the device for several months and reading everything I coul dfind on rooting it or previous versions. I decided to attempt. (Note: I have route plenty of phone and tablets before)
Steps and Results
Enable USB debugging
Install Magisk 8.0.7
Download Factory ROM
Copy boot.img to device via adb
Run Magisk and patch img.
Copy patched img to PC via ADB
fastboot flashing unlock (fasboot oem unlock erros)
fastboot boot patched_boot.img
Sending 'boot.img' (32768 KB) OKAY [ 1.512s]
Booting OKAY [ 0.063s]
Finished. Total time: 2.807s
Device rebooted on its own.
Rebooted into fastboot.
fastboot flash boot_a patched_boot.img
fastboot: error: cannot get boot partition size
fastboot flash boot_b patched_boot.img
fastboot: error: cannot get boot partition size
fastboot flash boot patched_boot.img
Sending 'boot' (32768 KB) OKAY [ 1.158s]
Writing 'boot' OKAY [ 0.445s]
Finished. Total time: 1.621s
DeviceDevice reboots on its own and boot loops
Use SP Flash Tool to reinstall factory image.
Device boots normally.
Use SP Flash to flash patched boot image.
Device boot loops.
Thoughts? Looks to me that the patched boot.img is invalid. Not sure how to verify or how else to get patched boot.img.
I also tried
fastboot boot patched_boot.img
Device reboots twice and then comes up with stock boot.img.
snickle said:
...
fastboot flash boot patched_boot.img
Sending 'boot' (32768 KB) OKAY [ 1.158s]
Writing 'boot' OKAY [ 0.445s]
Finished. Total time: 1.621s
DeviceDevice reboots on its own and boot loops
...
Thoughts? Looks to me that the patched boot.img is invalid. Not sure how to verify or how else to get patched boot.img.
Click to expand...
Click to collapse
Try installing Magisk using TWRP.
The patched boot.img method is only usually used when TWRP is unavailable.
Make sure you flash the stock boot.img (or the whole stock ROM) before installing TWRP and Magisk.
Got it working using canary version of magisk manager.
Hi, i just wanted to share the exact steps i took to root this tablet.
Funnily enough (for me at least), this was the easiest android device i've rooted out of all the ones i've previously owned. Thanks in part to OP of this thread!
The tablet i have is the following version:
TB-X606F_S300429_211101_BMP
unlock bootloader preparations
1. on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
2. go to Settings->System->DeveloperOptions.
3. Turn on: "OEM unlocking" and "USB debugging".
flash/root/recovery preparation
1. install latest: https://developer.android.com/studio/releases/platform-tools#downloads
2. install MTK_Android_USB_Driver
3. download TWRP for Lenovo Tab M10 Plus x606 (put it in the platform-tools directory)
4. reboot computer
5. run CMD command in the platform-tools directory:
fastboot flashing unlock
6. accept the conditions on the tablet screen
7. turn off tablet
8. turn on tablet into recovery mode with: Vol Up + Vol Down + Power (hold steady for several seconds after it vibrates)
9. choose "boot into bootloader" in the menu = now youre in fastboot mode
10. connect USB cable to computer
11. run CMD commands (wait for each commadn to finish ffirst of course):
fastboot flash recovery [TWRP you downloaded].img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
now youre in TWRP again:
1. finish the decryption in TWRP. (same pin as regular android encryption pin code if you chose one before)
2. do NOT keep read only
3. go to backup tab and make a backup (boot, system, vendor, data)
4. advanced wipe -> wipe "data"
Time to flash root/magisk
1. download Magisk-v23.0.apk
2. rename to zip
3. place the zip in tablet storage via USB cable
4. go to "install" in TWRP
5. select the magisk zip
6. flash magisk
7. reboot into system
8. enable installation of untrusted apk sources in android settings
9. start magisk manager just to check that things are OK
10. download root checker and verify root
11. reboot tablet a bunch of times to see that root is sticking
12. enable developer options again [for some reason it resets this during the flashing/wiping from above steps]
skribb said:
Hi, i just wanted to share the exact steps i took to root this tablet.
Funnily enough (for me at least), this was the easiest android device i've rooted out of all the ones i've previously owned. Thanks in part to OP of this thread!
The tablet i have is the following version:
TB-X606F_S300429_211101_BMP
unlock bootloader preparations
1. on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
2. go to Settings->System->DeveloperOptions.
3. Turn on: "OEM unlocking" and "USB debugging".
flash/root/recovery preparation
1. install latest: https://developer.android.com/studio/releases/platform-tools#downloads
2. install MTK_Android_USB_Driver
3. download TWRP for Lenovo Tab M10 Plus x606 (put it in the platform-tools directory)
4. reboot computer
5. run CMD command in the platform-tools directory:
fastboot flashing unlock
6. accept the conditions on the tablet screen
7. turn off tablet
8. turn on tablet into recovery mode with: Vol Up + Vol Down + Power (hold steady for several seconds after it vibrates)
9. choose "boot into bootloader" in the menu = now youre in fastboot mode
10. connect USB cable to computer
11. run CMD commands (wait for each commadn to finish ffirst of course):
fastboot flash recovery [TWRP you downloaded].img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
now youre in TWRP again:
1. finish the decryption in TWRP. (same pin as regular android encryption pin code if you chose one before)
2. do NOT keep read only
3. go to backup tab and make a backup (boot, system, vendor, data)
4. advanced wipe -> wipe "data"
Time to flash root/magisk
1. download Magisk-v23.0.apk
2. rename to zip
3. place the zip in tablet storage via USB cable
4. go to "install" in TWRP
5. select the magisk zip
6. flash magisk
7. reboot into system
8. enable installation of untrusted apk sources in android settings
9. start magisk manager just to check that things are OK
10. download root checker and verify root
11. reboot tablet a bunch of times to see that root is sticking
12. enable developer options again [for some reason it resets this during the flashing/wiping from above steps]
Click to expand...
Click to collapse
What ADB driver did you use? I cant get a good driver to load in Windows.
@be_the_shooter
Not 100% sure but I think it was Universal ADB Driver 1.0.4 from ClockworkMod. I'm on win7 x64.

[GUIDE] [TWRP] [Root] How to install TWRP and ROOT on a20s (SM-A207F)

HEX_101​
Requirements:​[+] Have a Linux distro installed on your pc
[+] A Brain
[+] An A20s and a USB cable
Initial steps:​[+] Unlock the phone's bootloader (won't teach you how since it's the easiest part)
[+] Download GSI from your pc make sure to download system-roar-arm64-ab-vndklite-gapps.img.xz [Note: This is pre-rooted GSI]
[+] Extract it on a folder (make sure to have everything organized)
[+] Download heimdall_flash_file.zip and extract in the same folder
[+] Install heimdall through terminal (sudo apt-get install heimdall-flash -y)
Flashing a GSI:​[+] Reboot your phone into download mode (turn off, hold both volume keys and insert a usb cable already connected to your pc)
[+] Install Heimdall sudo apt-get install heimdall-flash
[+] Open terminal and go to the files folder
[+] Write "heimdall flash --SYSTEM sysnull.img " (without ""), phone will reboot, go into download mode again (If it doesn't boot to download mode boot it manually)
[+] Write "heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-gapps.img --VBMETA avbnull.img" (without "") Then boot into stock recovery and do a factory reset (to boot into stock recovery unplug your cable and hold both volume+ and power buttons)
Flashing TWRP:​[+] Boot your phone into system and do the initial setup (don't restore any apps or data, only your google account) and download "Termux" apk and install it
[+] Download TWRP file on your phone , make sure it's inside your "downloads" folder and rename to recovery.img
[+] Enter termux and type "su" (without "")
[+] Write "dd if=/sdcard/Downloads/recovery.img of=/dev/block/bootdevice/by-name/recovery" (without "") if twrp image isn't in your downloads folder it will fail so make sure it's there
[+] Turn off the phone and boot into twrp, on your pc download Mutidisable
[+] On twrp wipe Data, Dalvik/ART, Cache and Internal storage, then FORMAT data, reboot to twrp
[+] Move "Multidisabler" from your pc to your phone's internal storage
[+] Flash "Multidisabler" on twrp then do the same wipes as before then reboot.
[ It's not the best guide so if you have any questions please ask. ]
Note: Adb Not Working​
Problem after installing gsi:​[!] Google play: This device isn't play protect certified ​
How to fix it​
RealVelosh said:
1. Find Device ID:
- Download Device ID by Evozi
+ Link (APK): here (https://evozi-deviceid.en.uptodown.com/android)
+ Open Device ID
2. Copy GSF (Google Service Framework) ID
3. Register your device here (http://www.google.com/android/uncertified)
4. Reboot and wait a minute
5. Clear Google Play Store data
6. Done
I pick this from my TrebleExperience's group, maybe will fix.
Click to expand...
Click to collapse
[Modified]
Hi. Thanks for the instructions.
Can I trouble you in providing those TWRP recovery.img and the multidisabler.zip files here on xda?
I do not have a Telegram account nor do I intend to sign-up for that. If you can't, then that's okay.
Slim K said:
Hi. Thanks for the instructions.
Can I trouble you in providing those TWRP recovery.img and the multidisabler.zip files here on xda?
I do not have a Telegram account nor do I intend to sign-up for that. If you can't, then that's okay.
Click to expand...
Click to collapse
Links are now Updated​
Hex_101 said:
​[!] Google play: This device isn't play protect certified ​
Click to expand...
Click to collapse
1. Find Device ID:
- Download Device ID by Evozi
+ Link (Google Play Store): here (https://play.google.com/store/apps/details?id=com.evozi.deviceid)
+ Link (APK): here (https://evozi-deviceid.en.uptodown.com/android)
- ADB Method:
+ adb root, then adb shell, press enter, and at the new prompt, inside adb shell, do sqlite3 /data/data/com.google.android.gsf/databases/gservices.db 'select * from main where name = "android_id";'
2. Copy GSF (Google Service Framework) ID
3. Register your device here (http://www.google.com/android/uncertified)
4. Reboot and wait a minute
5. Clear Google Play Store data
6. Done
I pick this from my TrebleExperience's group, maybe will fix.
RealVelosh said:
1. Find Device ID:
- Download Device ID by Evozi
+ Link (Google Play Store): here (https://play.google.com/store/apps/details?id=com.evozi.deviceid)
+ Link (APK): here (https://evozi-deviceid.en.uptodown.com/android)
- ADB Method:
+ adb root, then adb shell, press enter, and at the new prompt, inside adb shell, do sqlite3 /data/data/com.google.android.gsf/databases/gservices.db 'select * from main where name = "android_id";'
2. Copy GSF (Google Service Framework) ID
3. Register your device here (http://www.google.com/android/uncertified)
4. Reboot and wait a minute
5. Clear Google Play Store data
6. Done
I pick this from my TrebleExperience's group, maybe will fix.
Click to expand...
Click to collapse
Adb will not work on this gsi [Not working on my DEVICE] and play store also [After fixing this problem it will work] so you have to install DEVICE ID apk to fix play store problem
Hex_101 said:
Adb will not work on this gsi [Not working on my DEVICE] and play store also [After fixing this problem it will work] so you have to install DEVICE ID apk to fix play store problem
Click to expand...
Click to collapse
Are you sure? Just enable USB debugging.
Hex_101 said:
HEX_101​
Requirements:​[+] Have a Linux distro installed on your pc
[+] A Brain
[+] An A20s and a USB cable
Initial steps:​[+] Unlock the phone's bootloader (won't teach you how since it's the easiest part)
[+] Download GSI from your pc make sure to download system-roar-arm64-ab-vndklite-gapps.img.xz [Note: This is pre-rooted GSI]
[+] Extract it on a folder (make sure to have everything organized)
[+] Download heimdall_flash_file.zip and extract in the same folder
[+] Install heimdall through terminal (sudo apt-get install heimdall-flash -y)
Flashing a GSI:​[+] Reboot your phone into download mode (turn off, hold both volume keys and insert a usb cable already connected to your pc)
[+] Open terminal and go to the files folder
[+] Write "heimdall flash --SYSTEM sysnull.img --VENDOR vndnull.img" (without ""), phone will reboot, go into download mode again (If it doesn't boot to download mode boot it manually)
[+] Write "heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-gapps.img --VBMETA avbnull.img" (without "") Then boot into stock recovery and do a factory reset (to boot into stock recovery unplug your cable and hold both volume+ and power buttons)
Flashing TWRP:​[+] Boot your phone into system and do the initial setup (don't restore any apps or data, only your google account) and download "Termux" apk and install it
[+] Download TWRP file on your phone , make sure it's inside your "downloads" folder and rename to recovery.img
[+] Enter termux and type "su" (without "")
[+] Write "dd if=/sdcard/Downloads/recovery.img of=/dev/block/bootdevice/by-name/recovery" (without "") if twrp image isn't in your downloads folder it will fail so make sure it's there
[+] Turn off the phone and boot into twrp, on your pc download Mutidisable
[+] On twrp wipe Data, Dalvik/ART, Cache and Internal storage, then FORMAT data, reboot to twrp
[+] Move "Multidisabler" from your pc to your phone's internal storage
[+] Flash "Multidisabler" on twrp then do the same wipes as before then reboot.
[ It's not the best guide so if you have any questions please ask. ]
Click to expand...
Click to collapse
I'll add 2 things to this:
1.- after flashing twrp you won't be able to set a screen lock method
2.- this twrp is NOT a way to get magisk so don't flash it, you'll end up with a soft brick
Fristover said:
I'll add 2 things to this:
1.- after flashing twrp you won't be able to set a screen lock method
2.- this twrp is NOT a way to get magisk so don't flash it, you'll end up with a soft brick
Click to expand...
Click to collapse
Yes
RealVelosh said:
Are you sure? Just enable USB debugging.
Click to expand...
Click to collapse
Yes because after flashing gsi I tried to install termux using adb but my device was not listed in adb and I was also not able to explor my device file on windows file explor SAME IN LINUX
[=] USB debugging was on
[=] Restarted Device multiple time
I tried 2 times but after flashing second line " heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-gapps.img --VBMETA avbnull.img " and it finished flashing my device reboot automatically to download mode when i goto recovery and wipe data and cache and reboot its gose to download agine and cant goto setup menu to complete the steps ( install twrp etc )
Idont know what i did wrong !!
Using virtualbox 6.1 kali linux
Device : Samsung a20s sm-a207f/ds
Android 10
The image you suggest to download is not in sparse format, which is wrong according to AOSP Source.
Also, flashing GSI is not recommended, because it is not device-specific and many features may not work (like ADB for our case)
So, this guide is technically incorrect and may get people false hope of root on Galaxy A20s.
Anything we can try is flashing custom recovery. Nothing more at the moment, sadly.
Even getting TWRP on this is hard. Blame Samsung for a broken bootloader, beacuse it should not check partitions when disable VBMETA is flashed and bootloader is unlocked.
TheAirBlow said:
The image you suggest to download is not in sparse format, which is wrong according to AOSP Source.
Also, flashing GSI is not recommended, because it is not device-specific and many features may not work (like ADB for our case)
So, this guide is technically incorrect and may get people false hope of root on Galaxy A20s.
Anything we can try is flashing custom recovery. Nothing more at the moment, sadly.
Even getting TWRP on this is hard. Blame Samsung for a broken bootloader, beacuse it should not check partitions when disable VBMETA is flashed and bootloader is unlocked.
Click to expand...
Click to collapse
for now this is only method
BTW a20s community/developers tried every thing and we are stilling trying
Hex_101 said:
for now this is only method
BTW a20s community/developers tried every thing and we are stilling trying
Click to expand...
Click to collapse
Maybe patching the original system and flashing it using the null image bypass?
P.S. Most users of A20s don't care about root beacuse they are normal users. Most of developers use A20
TheAirBlow said:
Maybe patching the original system and flashing it using the null image bypass?
P.S. Most users of A20s don't care about root beacuse they are normal users. Most of developers use A20
Click to expand...
Click to collapse
We have tried patching method
Hex_101 said:
We have tried patching method
Click to expand...
Click to collapse
Try Android 9 (ATB firmware) aboot.mbn + vaultkeeper.mbn bypass, it may work
Hex_101 said:
We have tried patching method
Click to expand...
Click to collapse
Also, is there's any way to flash custom recovery without pre-rooted GSI?
TheAirBlow said:
Also, is there's any way to flash custom recovery without pre-rooted GSI?
Click to expand...
Click to collapse
nope
Hex_101 said:
nope
Click to expand...
Click to collapse
Hav you tried Android 9 aboot.mbn + vaultkeeper.mbn bypass thta may work? If you're lazy to download the firmware (jk), I can send it to you
Hex_101 said:
nope
Click to expand...
Click to collapse
Also, we need a good way to contact - maybe you can PM me your discord, for example?

Categories

Resources