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

Search This thread

1jkan

Senior Member
Jul 16, 2012
455
64
60
I also confirm. Managed to. I have Android 12 rooted and with TWRP. However, after installing it, it turned out that some of my favorite applications (Button Remaper, GravityBox, FireFds and something else) do not work on A12 and unfortunately I went back to A11.
 

Mucky2

Senior Member
Jan 7, 2013
439
83
Could someone dump me a param.bin file for a G986B? (DBT)
Extracted files and couldn't find it anywhere?

Trying to flash with Heimdall, latest MacOS not supporting (J)Odin.

ls *.bin *.img
boot.img modem.bin tzar.img
cache.img modem_debug.bin tzsw.img
dqmdbg.img optics.img uh.bin
dtbo.img prism.img up_param.bin
harx.bin recovery.img userdata.img
keystorage.bin sboot.bin vbmeta.img
ldfw.img ssp.img vbmeta_samsung.img
misc.bin super.img

Entry Count: 43
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21324
Unknown 4: 14665
Unknown 5: 13112
Unknown 6: 48
Unknown 7: 5
Unknown 8: 0


--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1024
File Offset (Obsolete): 1
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:


--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 100
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 1
File Size (Obsolete): 0
Partition Name: UL_KEYS
Flash Filename: ul_key.bin
FOTA Filename:


--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 90
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 768
File Offset (Obsolete): 2
File Size (Obsolete): 0
Partition Name: BOOTLOADER2
Flash Filename:
FOTA Filename:


--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 91
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 768
Partition Block Count: 256
File Offset (Obsolete): 2
File Size (Obsolete): 0
Partition Name: DDI
Flash Filename:
FOTA Filename:


--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 6
Partition Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: -
FOTA Filename:


--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:


--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1024
Partition Block Count: 5120
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:


--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 6144
Partition Block Count: 5120
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SEC_EFS
Flash Filename: sec_efs.img
FOTA Filename:


--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 11264
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin

FOTA Filename:


--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 13312
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UP_PARAM
Flash Filename: up_param.bin
FOTA Filename:


--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 15360
Partition Block Count: 10240
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA
Flash Filename:
FOTA Filename:


--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 25600
Partition Block Count: 128
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KEYSTORAGE
Flash Filename: keystorage.bin
FOTA Filename:


--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 25728
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEADY
Flash Filename: steady.bin
FOTA Filename:


--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 26752
Partition Block Count: 768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HARX
Flash Filename: harx.bin
FOTA Filename:


--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 27520
Partition Block Count: 512
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UH
Flash Filename: uh.bin
FOTA Filename:


--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 28032
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UHCFG
Flash Filename: uhuh.bin
FOTA Filename:


--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 29056
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DTBO
Flash Filename: dtbo.img
FOTA Filename:


--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 31104
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BLCMD
Flash Filename: blcmd.bin
FOTA Filename:


--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 31120
Partition Block Count: 15104
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:


--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 46224
Partition Block Count: 16848
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:


--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 63072
Partition Block Count: 17920
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:


--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 80992
Partition Block Count: 1280
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CP_DEBUG
Flash Filename: modem_debug.bin
FOTA Filename:


--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 82272
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: NAD_REFER
Flash Filename: nad_refer.bin
FOTA Filename:


--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 82528
Partition Block Count: 128
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSISTENT
Flash Filename:
FOTA Filename:


--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 82656
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MISC
Flash Filename: misc.bin
FOTA Filename:


--- Entry #25 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 82912
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KEYREFUGE
Flash Filename:
FOTA Filename:


--- Entry #26 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 87008
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KEYDATA
Flash Filename:
FOTA Filename:


--- Entry #27 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 91104
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DQMDBG
Flash Filename: dqmdbg.img
FOTA Filename:


--- Entry #28 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 95200
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: VBMETA
Flash Filename: vbmeta.img
FOTA Filename:


--- Entry #29 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 24
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 95216
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: VBMETA_SAMSUNG
Flash Filename: vbmeta_samsung.img
FOTA Filename:


--- Entry #30 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 25
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 95232
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: METADATA
Flash Filename: metadata.img
FOTA Filename:


--- Entry #31 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 26
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 103424
Partition Block Count: 2304000
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SUPER
Flash Filename: super.img
FOTA Filename:


--- Entry #32 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 27
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 2407424
Partition Block Count: 256000
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PRISM
Flash Filename: prism.img
FOTA Filename:


--- Entry #33 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 28
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 2663424
Partition Block Count: 7680
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OPTICS
Flash Filename: optics.img
FOTA Filename:


--- Entry #34 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 29
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 2671104
Partition Block Count: 153600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:


--- Entry #35 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 30
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 2824704
Partition Block Count: 12800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OMR
Flash Filename: omr.img
FOTA Filename:


--- Entry #36 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 31
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 2837504
Partition Block Count: 12800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SPU
Flash Filename: spu.img
FOTA Filename:


--- Entry #37 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 32
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 2850304
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained


--- Entry #38 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 33
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 6
Partition Block Count: 1536
File Offset (Obsolete): 3
File Size (Obsolete): 0
Partition Name: CPEFS
Flash Filename:
FOTA Filename:


--- Entry #39 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 34
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1536
File Offset (Obsolete): 4
File Size (Obsolete): 0
Partition Name: LDFW
Flash Filename: ldfw.img
FOTA Filename:


--- Entry #40 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 35
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1536
Partition Block Count: 384
File Offset (Obsolete): 4
File Size (Obsolete): 0
Partition Name: TZSW
Flash Filename: tzsw.img
FOTA Filename:


--- Entry #41 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 36
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1920
Partition Block Count: 1920
File Offset (Obsolete): 4
File Size (Obsolete): 0
Partition Name: TZAR
Flash Filename: tzar.img
FOTA Filename:


--- Entry #42 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 37
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 3840
Partition Block Count: 256
File Offset (Obsolete): 4
File Size (Obsolete): 0
Partition Name: SSP
Flash Filename: ssp.img
FOTA Filename:
 
Last edited:

serajr

Recognized Developer / Recognized Themer
Apr 21, 2011
5,058
18,674
São Paulo - SP
Yes root it works :love: thank you serajr and Tagor.I did it like @tagor and it worked :D


My Fon:
SM-G985F (20+) without 5G
carrier o2 Germany / Drillisch

Android Version 12 Stock -DBT - with ThunderStorms-Kernel-R-v2.0 : 08.01.2022 für OneUI4.x
Congrats, mate!

I've also created and xposed module to get Secure Folder working on A12 (and it is), even after Root and my Debloat Script (ROOT version). Gonna release it soon.
 

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.
Thank you!!
Just give provided twrp (from the zip) a try and... it's working (ofc it doesn't decrypt /data, unfortunately).
 

Runner85sx

Senior Member
Apr 18, 2012
419
957
Berlin
HTC One (m7)
In Germany OneUI 4.0 and Android 12 are official for a few days now.
 

Attachments

  • Screenshot_20220110-213339_Settings.jpg
    Screenshot_20220110-213339_Settings.jpg
    402.3 KB · Views: 38
  • Like
Reactions: Mucky2

Mucky2

Senior Member
Jan 7, 2013
439
83
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.
Tried this method.

Patched my boot.lz4 and vbmeta.lz4 with magisk.
Added the recovery.img to the tar file.
Flashed boot.img recovery.img vbmeta.img with Heimdall.

This led to a bootloop, but TWRP was installed.
Switched back to original stock fw imgs and hat to factory reset lmao.

What did I miss?
 

skysurfer1111

Senior Member
Jul 4, 2016
235
167
Berlin
2 questions:
1. Which of twrp to use with newest eul7 firmaware
https://t.me/s/samsung_twrp_announce
2. Is this possible to update from rooted A11 with installed twrp as dont want to start all from scratches with modules for magisk and google pay solutions....
Any help welcome
1. read #397 and use the attached file.
2. I think not. I tried this without success. I had to wipe data and start from scratches.
Good luck:sneaky:
 
  • Like
Reactions: lukjod

altojd

Senior Member
Dec 11, 2009
1,207
662
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
how to pack boot.img and vbmeta.img as a single tar file?
 
Last edited by a moderator:

73sydney

Senior Member
Trying to follow the guide

Already previously updated to A12

FRP and OEM Unlock are both OFF

When flashing vbmeta_disabled i get the following error on S20+ 5G screen:

"only official released binaries are allowed to be flashed (VBMETA)"

Update:

Resolved....OEM Unlock wasnt showing in Dev Options, a quick check for a software update then revealedthe missing OEM Unlock in Dev Options

Rebooting to Download mode and flashing vbmeta_disabled afterwards worked fine
 
Last edited:
I have a brand new Exynos S20 5G (intl, KN). I have unlocked the BL. I did not root or do anything else, yet. I did not allow any system SW updates. I am in the US. I am confused...!!

Four questions:

1. Will the unlocked BL prevent the A12 OTA upgrade?

2. Should I allow all system SW updates before I root? Or should I root first, and then allow all system SW updates?

3. Should I wait for the OTA upgrade to A12 before I root?

4. Is it possible to root after OTA to A12? Are there any new problems with A12 that A11 did not have?

* From my current status, what is the best (least complicated) path ahead to get both root and OTA to A12? *

Thanks.
 

Attachments

  • IMG_20220126_084833.jpg
    IMG_20220126_084833.jpg
    401.8 KB · Views: 13

skysurfer1111

Senior Member
Jul 4, 2016
235
167
Berlin
I have a brand new Exynos S20 5G (intl, KN). I have unlocked the BL. I did not root or do anything else, yet. I did not allow any system SW updates. I am in the US. I am confused...!!

Four questions:

1. Will the unlocked BL prevent the A12 OTA upgrade?

2. Should I allow all system SW updates before I root? Or should I root first, and then allow all system SW updates?

3. Should I wait for the OTA upgrade to A12 before I root?

4. Is it possible to root after OTA to A12? Are there any new problems with A12 that A11 did not have?

* From my current status, what is the best (least complicated) path ahead to get both root and OTA to A12? *

Thanks.
1,2,3,4: yes
Rooted devices never get any OTA updates, only manual. With open BL no OTA.
So if you upgrade to A12 via Odin and install TWRP, you have to wipe data partition anyway to decrypt it.
No reason to root A11 before, when you start from the scratch anyway. So backup everthing you need.
Restoring your apps on A12 will get you problems sometimes. For me, A11 worked a litttle bit better, but you'll get no security updates in the future.
 
  • Like
Reactions: oaklandz

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
  • 65
    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