[HOW-TO][EXYNOS/SNAPDRAGON] Root S20 series and upgrade firmware

Search This thread

kevinwu128

Senior Member
Jun 24, 2014
151
22
Samsung Galaxy S20 FE
Thanks from Australia. This guide worked perfectly. I actually patched the whole AP file but have always done that coming from an s10 and installing it on the recovery.

For upgrading, if i patch the full AP from the old running OS, i should be able to just update it once instead of having to upgrade to nonroot and patching boot.img after right?

Thanks again :)
 

ErriK89

Senior Member
Oct 19, 2010
74
18
Milan
I updated s20 ultra exynos (g988b) to the latest fw following usual procedure that always worked but something goes wrong: the phone does not boot anymore resulting in bootloop. I tried also to don't flash vb_meta but nothing changes. Does something changed in latest samsung fw?
 

GeeAyeZee

Senior Member
i see, Interesting.
i search on the net and it said that if you flash a frimware of another model your phone will softbrick, that's why i still didn't try it yet, and another problem is there is so few info about the japanese model even if i tried to search it in japanese article.

appreciate for the response!
Im in Australia and ive flashed UK, Germany, and Australia firmware on my s20u heaps of times, no problem ever
 

stebrick

New member
Aug 24, 2021
3
0
Sorry I'm new to this. I'm planning to buy a korean version of S20 (SM-G981N) and flash it with Hong Kong firmware. First of all, would this be possible to pull off? Can I just download the official Hong Kong firmware from the official website here (https://www.sammobile.com/samsung/galaxy-s20/firmware/SM-G9810/TGY/#SM-G9810), and flash it in my Korean S20?

Secondly, is there any drawback in doing this? I'm wondering if Samsung Pay (and other HK localized feature like smart octopus) would become available to use in Hong Kong despite that I'm having a Korean version of S20.

Thirdly, how would the support of 5G change if I flash it this way?

Thanks :)
 

karmarrara

Member
Jun 27, 2008
5
0
hello guys, i have this model S20 Plus SM-G985F and unlock OEM not show.
I've tried all possible methods, I would like to know what is blocking the option to appear.
 

Attachments

  • 2021-09-25_180611.jpg
    2021-09-25_180611.jpg
    59.7 KB · Views: 48
  • 2021-09-25_180803.jpg
    2021-09-25_180803.jpg
    67.2 KB · Views: 48

Shyning

New member
Nov 22, 2021
4
1
Worked wonders for mine, thank you for the detailed walkthrough! Other smaller guides weren't as comprehensive as this one, it's a real treat for someone who has not rooted anything in ages.

SM-G9880 TGY (DUJ2 update, will take the chance to jump to DUK1).
 

gorthon

Senior Member
Oct 13, 2012
146
17
In my opinion, there should be separate threads for bootlocker unlocking and for firmware updating (with unlocked BL). Not that the procedure differs so much, but the problems and therefore the discussions do. In this thread everything is mixed now.

I followed the instructions to update from DUC7 to DUJ5. Internal storage of my phone is encrypted. After update, system doesn't boot, stays for a very long time at Samsung logo and then bootloops. After formatting data I can boot, but of course I don't want to reinstall and reconfigure everything.

Does the update not work with encrypted internal memory? And how can I restart encryption after factory reset (auomatic encryptiion is disabled, and if I start it manually from settings, I get the screen with the green droid and the nav bar disappears, but it's not showing any progress and encryption doesn't start)?
 

serajr

Recognized Developer / Recognized Themer
Apr 21, 2011
5,058
18,674
São Paulo - SP
Will this work on Android 12, OneUl4.0?
Rooted A12 here.

Edit: Procedure to update from A11 to A12 - Fresh install

Try it at your own risk:
1. Extract boot.img.lz4 and vbmeta.img.lz4 from AP > Pack both as a single tar file with 7-zip > Patch the tar file with latest Magisk canary app > magisk_patched-23016.tar file will be created

2. Flash full A12 firmware with Odin: BL + AP + CP + CSC (full data wipe) + magisk_patched-23016.tar in USERDATA

3. Reboot and you're done
 
Last edited:

ElmirBuljubasic

Senior Member
Feb 9, 2012
1,901
412
Rooted A12 here.

Try it at your own risk:
1. Extract boot.img.lz4 and vbmeta.img.lz4 from AP > Pack both as a single tar file with 7-zip > Patch the tar file with latest Magisk canary app > magisk_patched-23016.tar file will be created

2. Flash full A12 firmware with Odin: BL + AP + CP + CSC (full data wipe) + magisk_patched-23016.tar in USERDATA

3. Reboot and you're done
You can just patch the vbmeta and boot file in magisk canary and only use that patched file in userdata, no need to reset phone or update entire firmware
just tested
 

serajr

Recognized Developer / Recognized Themer
Apr 21, 2011
5,058
18,674
São Paulo - SP
You can just patch the vbmeta and boot file in magisk canary and only use that patched file in userdata, no need to reset phone or update entire firmware
just tested
You are right if you are already on the A12.
I've edited my post. Thx!

Also you will need to set magisk zygote in magisk settings,reboot, and update Universal Saftynetfix Zygote to pass saftynet
Sure, also zygisk's LSPosed module (if you want it too)

And btw, my Debloat Script v1.1 has also been updated for A12 compatibility (v1.1)!
 
Last edited:
  • Like
Reactions: 1jkan

1jkan

Senior Member
Jul 16, 2012
455
64
60
Thank you very much for the tutorial. I will definitely try. For me, it is also very important to have TWRP as well, and apparently there is a problem with that.
 
  • Like
Reactions: serajr

simpleandhumble01

New member
Dec 17, 2021
1
0
Hi I'm grateful for this thread.

Jost got my a galaxy s20 + SM-G985F/DS dual sim It's an exynos version. For some reason, I am having difficulties unlocking bootloader, because the OEM unlocking isn't available in the developer options. I already tried connecting to a wifi and modifying the date. Any ideas? Any insights will surely help. Thanks
 

tagor

Senior Member
Jul 3, 2008
52
19
Rooted A12 here.

Edit: Procedure to update from A11 to A12 - Fresh install

Try it at your own risk:
1. Extract boot.img.lz4 and vbmeta.img.lz4 from AP > Pack both as a single tar file with 7-zip > Patch the tar file with latest Magisk canary app > magisk_patched-23016.tar file will be created

2. Flash full A12 firmware with Odin: BL + AP + CP + CSC (full data wipe) + magisk_patched-23016.tar in USERDATA

3. Reboot and you're done
Thanks for the procedure. It is working perfectly for me.
I downloaded fresh A12 SEB for my S20+, prepared magisk_patched.tar according to your procedure. From the file I am attaching (downloaded from TWRP Telegram channel) I extracted recovery.img and added to the magisk_patched.tar archive. Flashed from USERDATA slot and rebooted. Now I have fresh A12, rooted with TWRP.

*I lost the track to the place I downloaded attached file and I am not sure if attaching the file is a violation of copyrights. If so, please ignore attachment and look for twrp-z3s-3.6.0_11-r1-A12_VBMETA_ZUKA_patched.tar on Telegram TWRP channel for yourself.
 

Attachments

  • twrp-z3s-3.6.0_11-r1-A12_VBMETA_ZUKA_patched.tar
    55.6 MB · Views: 785

1jkan

Senior Member
Jul 16, 2012
455
64
60
Do I understand well? Is this finally the first TWRP for A12, OneUl 4.0?
 

serajr

Recognized Developer / Recognized Themer
Apr 21, 2011
5,058
18,674
São Paulo - SP
Thanks for the procedure. It is working perfectly for me.
I downloaded fresh A12 SEB for my S20+, prepared magisk_patched.tar according to your procedure. From the file I am attaching (downloaded from TWRP Telegram channel) I extracted recovery.img and added to the magisk_patched.tar archive. Flashed from USERDATA slot and rebooted. Now I have fresh A12, rooted with TWRP.

*I lost the track to the place I downloaded attached file and I am not sure if attaching the file is a violation of copyrights. If so, please ignore attachment and look for twrp-z3s-3.6.0_11-r1-A12_VBMETA_ZUKA_patched.tar on Telegram TWRP channel for yourself.
Oh great!
EDITED!!
 
Last edited:
  • Like
Reactions: 1jkan

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Yes, it's absolutely normal. You'll see that message every time you reboot.
    2
    I just unlocked the bootloader on my galaxy s20 ultra SM-G988B /DS on the latest firmware, reflashed with the vb_disabled file in the userdata although now at the bootup it says this phone is not running samsung official software though sure boots successfully, just wanted to know if that is normal?

    This makes it look less alarming (if you have TWRP installed):

    1
    Thank you for sharing this, appreciate it. Only problem is that I just started using this galaxy s20 ultra and since I wanted to set it asap and couldn't find the recovery I just went ahead with patching the boot image manually and rooting.

    Now the phone is all set and so I just wanted to know if there is a magisk alternative to this or if you or anyone here can link me to a working recovery for SM-G9880 /DS on A12, the latest firmware. Edit: I did find the twrp+vbmeta tar from the older posts. Just need to know if there's a way for me to just simply flash the twrp on this already rooted with odin (on userdata/ap?) without having to reset the phone or is the reset a must?

    Hi,

    If you havent already installed TWRP, then yes you would have to wipe data to decrypt it along with installing TWRP (which is why i put the "if you have TWRP installed" caveat in there)

    The link and patch is only a cosmetic thing, its not worth upsetting your current install just for that

    If you have to reflash stock at some point, then maybe revisit it.

    Theres no way to do the same thing in magisk as it isnt mounted at this stage of events
  • 66
    Applicable Models:
    All Exynos models including but not limited to:
    SM-G980F or SM-G980F/DS (S20)
    SM-G981B or SM-G981B/DS (S20)
    SM-G985F or SM-G985F/DS (S20+)
    SM-G986B or SM-G986B/DS (S20+)
    SM-G988B or SM-G988B/DS (S20 Ultra)
    All BL-unlockable Snapdragon models including but not limited to:
    SM-G9810 (S20, Hong Kong, Taiwan, China mainland)
    SM-G9860 (S20+, Hong Kong, Taiwan, China mainland)
    SM-G9880 (S20 Ultra, Hong Kong, Taiwan, China mainland)
    SM-G981N (S20, Korea)
    SM-G986N (S20+, Korea)
    SM-G988N (S20 Ultra, Korea)

    Japanese model (SC-*) also use Snapdragon but I can't not confirm that its bootloader is unlockable.
    It is known that bootloader can NOT be unlocked on U.S. models (U/U1) .

    Frequently used key combinations of S20 series:
    FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
    DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
    RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.

    Some facts:
    1. S20 series uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
    3. S20 series uses A-only partition which means there is only one set of system partition.
    3. S20 series uses 2 stage init (2SI).
    4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
    5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).

    Tools needed:
    On your computer:
    1. Odin 3.14.4 or newer
    2. Samsung Android USB driver
    3. SamFirm or other tools/websites to download official firmwares
    4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
    On your device:
    1. Magisk Manager

    Stage 1: Know your model and carrier code (CSC)
    1. Open "Settings"
    2. Go to "About phone" -> "Software information"
    3. Pay attention to "Service provider SW ver."
    4. Starting with "SM-", for example "SM-G9810", that's the model of your phone.
    5. Immediately after that, there are two 3-letter code, for example "OZL_CHC". The second 3-letter code "CHC" is your CSC.
    6. Remember your model and CSC.
    Screenshot_20200409-191910_Settings.jpg

    Stage 2: Unlock the bootloader
    WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
    1. Open "Settings"
    2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
    3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
    4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
    Screenshot_20200409-191950_Settings.jpg
    5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
    6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
    7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
    8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
    9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
    10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
    11. Repeat step 6.
    12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
    13. You will see "Downloading" screen. On the top left, there are some important info.
    14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
    IMG_0226.jpg

    Stage 3: Disable Android Verified Boot
    1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
    2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
    3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
    4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
    5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
    6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
    View attachment 4990053

    With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.

    If a recovery is available and you don't want to go through the process of downloading official firmware, go to #2.

    You can also download a KERNEL TAR archive of your version here:
    Exynos: https://github.com/jesec/proprietary_vendor_samsung_xyzs/releases
    Snapdragon: https://github.com/jesec/proprietary_vendor_samsung_xyzq/releases
    and then skip to Step 6.

    Stage 4: Obtain the official firmware and upgrade
    1. Open SamFirm
    2. Type in your model and your region (CSC) and click "Check Update"
    3. "Download" and you will get a zip file.
    View attachment 4990061
    4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
    5. Check the version code, for example (G9810ZCU1ATD1). The last 4 letters (ATD1) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
    Your data will be preserved if you do it right but it is good to have a backup.
    6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
    7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
    8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
    9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
    10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
    View attachment 4990063

    Stage 5: Extract boot (kernel) image from firmware
    If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
    1. Extract boot.img.lz4 from the AP file.
    2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
    View attachment 4990065View attachment 4990067View attachment 4990069View attachment 4990071

    Stage 6: Patch the boot (Kernel) image via Magisk
    1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
    2. Open Magisk Manager.
    3. Click top-right "Install" button
    4. Make sure "Recovery Mode" is off in Options.
    5. Click "Next" and select "Select and Patch a File" in Method.
    6. Select the file you transferred to your phone in step 1.
    7. Click "Next" and "LET'S GO".
    Screenshot_20200415-223750.jpgScreenshot_20200409-192424.jpgScreenshot_20200409-192430.jpgScreenshot_20200409-192447.jpgScreenshot_20200415-085506.jpg
    8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
    9. Reboot the device to DOWNLOAD mode.
    10. Open Odin, put patched file to AP slot and then click "Start".
    11. After reboot, Magisk is installed and you will have the root access.

    HOW TO upgrade the firmware
    Repeat stage 4-6.

    XDA:DevDB Information
    Root S20 series and upgrade firmware, Tool/Utility for the Samsung Galaxy S20

    Contributors
    jesec

    Version Information
    Status: Stable

    Created 2020-04-08
    Last Updated 2020-04-08
    16
    Other Methods:

    You still need to unlock bootloader and disable AVB. (check Stage 2-3)

    Recovery Magisk installation:
    1. Open Odin on your computer.
    2. Reboot your device to DOWNLOAD mode.
    3. Put the recovery TAR flashable into AP slot.
    4. Click start.
    5. Use Volume Up + Power to reboot into recovery mode.
    6. Install Magisk via recovery.
    My recovery usually includes Magisk in "Select from root" -> ".builtin" folder. Or you can sideload the ZIP flashable of your choice via adb or https://flash.jesec.io/.

    Flash pre-patched boot (Kernel) image:
    Basically others have done stage 4-6 for you. Be aware that it is always safer to DIY.
    You are welcomed to share your patched image to the community by replying to this thread.
    Naming convention: model + firmware version (last four letters of build number) + magisk version .tar
    1. Make sure that the model and firmware version of the pre-patched image is the exact SAME as yours.
    2. Open Odin on your computer.
    3. Reboot your device to DOWNLOAD mode.
    4. Put pre-patched image into AP slot.
    5. "Start"

    SM-G9810_ATD1_ef9d077c.tar:
    https://drive.google.com/open?id=1SxKXWHqR0aM_g457Yp7pk524_6aqp1k5
    11
    Some Interesting Things:

    Change your CSC (carrier code):
    You have to root your device. There might be some secret codes to trigger the menu without root, though.
    Note that you can only change it to carrier configurations already included in your firmware.
    WARNING: Your device will be reset to factory settings.

    In a local terminal, type:
    su
    am start -n com.samsung.android.cidmanager/.preconfig.PreconfigActivity

    Screenshot_20200409-100230.jpg
    10
    The situation in US:
    As long as the model is shared with Verizon and ATT, it is highly unlikely that it will be BL unlockable. Verizon and ATT have strong desire to keep the phone BL locked. Samsung wants unlockable by default but they don't argue with Verizon/ATT on this. T mobile and Sprint are OK with unlock but they don't have strong desire to make it unlockable.

    Anyways, for Snapdragon users, now the Lineage Recovery is available. You can now root your device without downloading the full firmware.
    https://forum.xda-developers.com/galaxy-s20/samsung-galaxy-snapdragon-s20--s20--s20-ultra-roms-kernels-recoveries--other-development/recovery-lineage-recovery-s20-series-t4084977

    I will also take a look into Exynos devices if there are enough interest. (however i can only do blind development)

    I am also working on TWRP Android 10 branch. It is still early stage, though.
    image.jpg
    6
    Anyone tried on Android 11?
    Working here (s20+ exynos), stock android 11, plus twrp and edxposed (y)
    AP patched with latest magisk canary, which will also patch the vbmeta (to disable Android Verified Boot).

    Screenshot_20201206-134109[1].jpg Screenshot_20201206-134117[1].jpg Screenshot_20201206-134126[1].jpg Screenshot_20201206-134134_EdXposed_Manager[1].jpg