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

Search This thread

Matce

Senior Member
Jul 27, 2008
85
6
bump ...

Been out of the loop for a while....
Is there a guide to go from fully rooted A11 to A12 ? Pretty crucial: without wiping data!

To update within A11 I typically did this:
- download Firmware and extract
- Odin BL/AP/CP/HOME_CSC and USERDATA (TWRP+VBMETA in 1 file)
-- untick auto reboot and flash
- go into TWRP, flash multidisabler, reboot into system
- go into TWRP again, flash kernel, done

is that still true to go from A11 to A12 now? just replace with new TWRP?

Samsung S20 here.

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

Thanks.

My phone is 100% virgin with only the BL unlocked (no accounts, no app or system updates.) From here ... what would you do to get to A12 + rooted - with the least work or complication? I'm good with either TWRP or no TWRP.

Sry, I forgot one thing: You can use TWRP with encrypted data, but you can't do nandroid backups of your data partition. Everything else works.
Thats it.:sleep:
Skysurfer I followed your directions to a T (and have rooted/TWRP other phones; including a bricked j327 emerge I revived + rooted today while I'm at it.)

Here's the result. (S20 5G - SM-981P)
From stock A11, I flashed A12 AV9 (OXM). This works fine. No glitches. (when I upgraded I used TWRP on the first attempt.) I tried both versions of TWRP + VBMETA that you linked to. Neither of them work; right after download mode I try to force boot into recovery instead of system reboot. I can do this with the stock A12 VA9 recovery, but not with the TWRP recovery. I tried these three options in succession more than once. Same results. Even after system reboots, I can't get TWRP recovery.

Two questions.
1. Is the problem that both versions of TWRP+VBMETA are not compatible with A12 VA9? (Is this a known issue?)
2. What would you do next? (perhaps, go back to stock A11 and retry A12 VA9 with TWRP; or downgrade to the previous version of A12 with TWRP; or else??)
 

skysurfer1111

Senior Member
Jul 4, 2016
235
167
Berlin
Two questions.
1. Is the problem that both versions of TWRP+VBMETA are not compatible with A12 VA9? (Is this a known issue?)
2. What would you do next? (perhaps, go back to stock A11 and retry A12 VA9 with TWRP; or downgrade to the previous version of A12 with TWRP; or else??)
Hello, did you flash twrp together with the FW and put it in the ODIN userdata slot? You have to be quick, when you change from DL to recovery mode. You have to hold pwr + volume up for a while and don't release.
  1. I don't know VA9, the TWRP I sent you works with EUL7 fine for me.
  2. I would try TWRP + VBMETA with EUL7.
You find most FW on SamFW.
 
My handset is currently still all stock and fully upgraded with the latest Software Update via OTA recently.

The latest One UI 4.0 and Android 12 FW for my S20 Ultra SM-G988B is the G988BXXUDEVA9 (BTU region for UK handset), downloaded via SamFirm, it's the same on Sam Mobile site. Which is what I believe oaklandz is referring to by "VA9".
Software Information page of the About Phone section of Settings on my device:

Settings.jpg


As you can see from the above image, the Baseband Version ends with EUL6 and the Build Number ends with EUL9

You mention "EUL7" but to what do you refer - Baseband Version or Build Number?
That's fairly important to make clear as there are 2 entries with an EUL suffix lurking in there.
Either way my device does not match this EUL7.

I would like to know if using the TWRP 11-r1-A12 VBMETA ZUKA patched tar, multidisabler-samsung-3.1, and Magisk files will work for my handset.
Have downloaded the G988BXXUDEVA9 firmware (latest available) and the above items, and set them to one side just in case they're the ones for me.

I've spent quite a lot of time reading various indicated posts on a few threads (and extra stuff) to do with TWRP and rooting the S20 Ultra SM-G988B/DS but some clarification wouldn't hurt before I actually do anything.
Overall I'm pretty comfortable using Odin to flash devices. When I'm clear on what files I'm supposed to be using for the task.
 
Last edited:
  • Like
Reactions: oaklandz

skysurfer1111

Senior Member
Jul 4, 2016
235
167
Berlin
I refer the Build Number. EUL7 ist the first stable version of A12. For TWRP read page 20 of this thread #397.
I really don't know, if this TWRP works with VA9, sorry. I'm still on EUL7 with Beyond Rom and TS Kernel.
This works fine.
 
Hello, did you flash twrp together with the FW and put it in the ODIN userdata slot? You have to be quick, when you change from DL to recovery mode. You have to hold pwr + volume up for a while and don't release.
  1. I don't know VA9, the TWRP I sent you works with EUL7 fine for me.
  2. I would try TWRP + VBMETA with EUL7.
You find most FW on SamFW.
"Did you flash twrp together with the FW and put it in the ODIN userdata slot?" # Yes
You have to be quick, when you change from DL to recovery mode. You have to hold pwr + volume up for a while and don't release. # Yes, I did this. It worked with stock only.
I will try TWRP + VBMETA with EUL7.
Thanks
 
The latest One UI 4.0 and Android 12 FW for my S20 Ultra SM-G988B is the G988BXXUDEVA9 (BTU region for UK handset), downloaded via SamFirm, it's the same on Sam Mobile site. Which is what I believe oaklandz is referring to by "VA9".

I would like to know if using the TWRP 11-r1-A12 VBMETA ZUKA patched tar, multidisabler-samsung-3.1, and Magisk files will work for my handset.
I used G988BXXUDEVA9 (BTU region for UK handset) with TWRP 11-r1-A12 VBMETA ZUKA (and another version, mentioned above) and either one did not allow me to launch into TWRP recovery. Stock recovery works with VA9. I will try withA12-EUL7 tonight.
S20 SM-981B/DS.
 
So, if my handset (S20 Ultra SM-G988B/DS) is fully up to date with the latest OTA firmware with no current available updates and the latest available firmware from SamMobile website or via the SamFirm app goes by the designation G988BXXUDEVA9

That would logically seem to indicate (assuming the available latest from SamMobile is the same as the latest OTA software update) that G988BXXUDEVA9 = Build Number G988BXXSCEUL9
Or just EUL9 for short

I could be mistaken as I have nothing other that the above information, tenuous connection with both ending with a 9, and somewhat shakey logic to support this assertion.

I don't currently have an alternate device to operate as a daily driver to enable me to test things out on my S20 Ultra SM-G988B/DS right now, just in case things go sideways and I have to mess about putting things right and setting it up again even with everything backed up - else I'd just jump in, have a go, and see how it turns out with various combinations and report back on bootloop, brick or wotever level of success was achieved if any.
I'd rather avoid using my daily driver for testing while lacking an alternate device though.
 
Last edited:
So, if my handset (S20 Ultra SM-G988B/DS) is fully up to date with the latest OTA firmware with no current available updates and the latest available firmware from SamMobile website or via the SamFirm app goes by the designation G988BXXUDEVA9

That would logically seem to indicate (assuming the available latest from SamMobile is the same as the latest OTA software update) that G988BXXUDEVA9 = Build Number G988BXXSCEUL9
Or just EUL9 for short

I could be mistaken as I have nothing other that the above information, tenuous connection with both ending with a 9, and somewhat shakey logic to support this assertion.

I don't currently have an alternate device to operate as a daily driver to enable me to test things out on my S20 Ultra SM-G988B/DS right now, just in case things go sideways and I have to mess about putting things right and setting it up again even with everything backed up - else I'd just jump in, have a go, and see how it turns out with various combinations and report back on bootloop, brick or wotever level of success was achieved if any.
I'd rather avoid using my daily driver for testing while lacking an alternate device thI
I think go ahead and see how it goes. I would like to know if this combo works for you (same as I tried.) If not, just flash the stock version that you have now to revert back.
 

Matce

Senior Member
Jul 27, 2008
85
6
any update on this?

Has anyone gone from fully rooted A11 to A12 without data reset?

thanks
 

Top Liked Posts

  • There are no posts matching your filters.
  • 67
    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
    12
    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