[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon)

Search This thread

josephgrab

Member
May 19, 2019
37
1
Killeen, TX
I did not know the SM-G9810 was Snapdragon. I thought it was Exynos. I did get root, so the bootloader can be unlocked. I trust there is no TWRP for that. Now I will try

twrp-3.4.0-1_afaneh92-x1q.tar​

Thank you for your help!
 

josephgrab

Member
May 19, 2019
37
1
Killeen, TX
I was finally able to get this done on SM-G9810. I thought it was Exynos and was using x1s twrp, now I am using x1q. However, the system_root folder is read only. I have root with Magisk and set it to allow root for apps and adb. When I am in adb shell, whoami returns root. However, I cannot overwrite /system_root/system/framework/services.jar with a modified one to allow signature spoofing for microg. I could not use twrp-3.4, I had to use twrp-3.6.0_11-4_afaneh92-x1q.tar.

I have tried file manager in twrp, it says error. Terminal says resource is busy. adb on windows computer says file system is read only. I am trying to remount, but that is not working.
 

josephgrab

Member
May 19, 2019
37
1
Killeen, TX
I did this process on S10 and S10e (both Exynos). I had no trouble overwriting the system_root folder. What keeps this folder as read-only? Is it the vbmeta (I don't know what that does), or do I need to write some modified fstab (I don't even know what that means)? How would I go about doing this? I am not a developer, I don't know the computer languages, but I am fairly good at following instructions.
 

afaneh92

Senior Member
Jul 31, 2012
3,310
4,857
I did this process on S10 and S10e (both Exynos). I had no trouble overwriting the system_root folder. What keeps this folder as read-only? Is it the vbmeta (I don't know what that does), or do I need to write some modified fstab (I don't even know what that means)? How would I go about doing this? I am not a developer, I don't know the computer languages, but I am fairly good at following instructions.
Code:
# mount r/w in twrp
adb shell mount /dev/block/mapper/system /system_root
adb shell mount /dev/block/mapper/vendor /vendor
# mount r/w in  twrp terminal
mount -o remount,rw /vendor
mount -o remount,rw /system_root
# mount r/w in booted system
adb shell su -c mount -o remount,rw /vendor
adb shell su -c mount -o remount,rw /
 

josephgrab

Member
May 19, 2019
37
1
Killeen, TX
Thank you so much for your help. I am rooted with magisk. I do not have superuser installed (is there one?). I cannot find a comma in twrp terminal, so I typed the twrp terminal commands in adb shell. It looked like this:

C:\Program Files (x86)\Minimal ADB and Fastboot>adb root

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell mount /dev/block/mapper/system /system_root
mount: /dev/block/mapper/system: need -t

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell mount /dev/block/mapper/vendor /vendor
mount: /dev/block/mapper/vendor: need -t

C:\Program Files (x86)\Minimal ADB and Fastboot>mount -o remount,rw /vendor
'mount' is not recognized as an internal or external command,
operable program or batch file.

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
x1q:/ # whoami
root
x1q:/ # mount -o remount,rw /vendor
x1q:/ # mount -o remount,rw /system_root
x1q:/ # su -c mount -o remount,rw /vendor
/system/bin/sh: su: inaccessible or not found
127|x1q:/ # su -c mount -o remount,rw /
/system/bin/sh: su: inaccessible or not found
127|x1q:/ #

I don't know what the need -t means, and I probably need su. As you can see, I do have root enabled in adb commands in magisk.
 

josephgrab

Member
May 19, 2019
37
1
Killeen, TX
Even though I don't understand this and these errors are present, when I went to file manager in TWRP and moved services.jar from the sd card to system_root/system/framework, it completed! Thank you very much!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    home.png



    backupname.png

    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    Code:
    * Your warranty is now void.
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or your getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    Note: My TWRP builds are free I take no money or selling them, The new builds support US devices unlocked before 9 november or added upon request.

    Supported Models:
    Galaxy S20 Ultra G9880, G988N, G988U, G988U1 and G988W.
    Galaxy S20 plus G9860, G986N, G986U, G986U1 and G986W.
    Galaxy S20 G9810, G981N, G981U, G981U1 and G981W.

    US/Canada bootloader unlock thread:
    here

    Download & Guide:
    1. Unlock your bootloader.
    2. Download S20: x1q, S20+: y2q or S20 Ultra z3q.
    3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
    4. Put the TWRP tar for your device with Odin in the AP slot and click start.
    5. Reboot to recovery via recovery key combo.
    6. Disable encryption:
    Or:
    - Go to Advanced > Terminal, type: multidisabler.​
    If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​
    - Type: multidisabler again. will see - Finished. when done.​
    7. Go back to Wipe > Format Data > type yes.
    8. Reboot to recovery.
    9. Flash magisk apk in twrp.
    10. Reboot to system, Enjoy.

    Note:
    To disable encryption manually:
    You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
    To avoid stock recovery restoration manually:
    Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
    Support:
    Live support is available via #twrp on Freenode with your IRC client or just click this link.

    Telegram group

    Bugs:
    - Encryption not fully working.

    Thanks:
    TWRP team
    @jesec for kernel source and unlock guide
    @ianmacd for multidisabler
    @sac23 and @elliwigy for testing on S20 Ultra G988U and G986U

    Sources:
    Kernel tree
    Device Tree:
    x1q
    y2q
    z3q
    3
    New builds Changelog:
    12.12.2020 - R build: Initial release for android 11.0.
    12.12.2020 - Q build: Update to latest TWRP source, Fix fastbootd.
    2
    Changelog:
    02.06.2022 - Update to Android 12 kernel source
    - Fix mount issues
    - Update to TWRP 3.6.2
    29.11.2021 - Update to TWRP 3.6.0
    - Add Symlinked dynamic partitions to fstab
    - Updated to latest kernel source
    - Update multidisabler
    - fstab clean up
    - Fix haptic feedback
    03.03.2021 - Update to latest TWRP source
    - Add terminal multidisabler script
    - fstab cleanup.
    12.12.2020 - Update TWRP to 3.5.0
    12.12.2020 - R build: Initial release for android 11.0.
    12.12.2020 - Q build: Update to latest TWRP source
    - Fix fastbootd.
    15.11.2020 - Add TWRP fastbootd support
    - Clean up fstab
    - Move kernel to gz format.
    24.09.2020 - Update prebuilt kernel and dtb's for more dynamic partitions compatibility.
    15.09.2020 - Update to latest TWRP source with more dynamic partitions support.
    03.09.2020 - Initial Release.
    2
    Thanks @afaneh92. For others' help, if anyone finds it useful, I flashed TWRP on my G986U1 using this sequence:
    • Unlocked bootloader as I described here.
    • Flashed vbmeta from this thread using patched Odin.
    • Flashed TWRP using patched Odin but did not auto-reboot.
    • Rebooted into TWRP using key combination.
    • Format data
    • Flashed multidisabler from OP in TWRP.
    • Format data again, just to be safe.
    1
    So, the bootloader unlock process is a paid service? I'm confused, can't we do it ourselves? Is the only solution to pay for it?
    Ok you can do it yourself. Buy international device.