NOTICE: We’ve created an archive of all major developments related to the Samsung Galaxy S10 lineup. We are continuously updating that page with latest S10e/S10/S10+ news so that you don’t need to search for information related to the device on daily basis. Head here to access that page.

New updates are being added at the bottom of this story…….

Android users should be familiar with the name ‘recovery’. For an average Joe, they see the glimpses of this special mode of the operating system while installing new OTA update or manually factory resetting the device.

Google Nexus 9 recovery (Image source: XDA Forums)

The recovery mode is nothing but a miniaturized form of the actual Android OS. It is special variant of the stock boot image that can be useful for applying updates or resetting the device, as those operations can not be done while the device is running in normal mode.

The ‘stock’ recovery, i.e. the default recovery image supplied by the smartphone manufacturer, only accepts official update packages from the manufacturer itself. Removing this check was the first major step in the aftermarket development.

ClockworkMod (CWM) recovery: one of the first custom recovery

Eventually developers added tons of extra functionalities in these custom recoveries. It could be possible to flash user made packages (ideal for installing custom kernels and ROMs), backup and restore data – even partitioning SD card.

After the demise of Koushik “Koush” Dutta‘s CWM recovery, the Android modding community got the taste of TeamWin Recovery Project aka TWRP.


The development of this GUI based custom recovery started by Ethan Yonker aka Dees_Troy and others when CWM was quite popular. CWM was abandoned by the lead dev, and TWRP registered itself as the community standard for custom recovery.

TWRP allows the following features:

– Backups of partitions in TAR or raw Image format

– Restore backups from internal storage, external SD storage or OTG devices

– Custom Firmware installation

– Partition wiping

– File deletion

– Terminal access

– ADB Root Shell

– Theme Support

– Possible decryption support depending on device

The 10th anniversary edition of Samsung Galaxy S series is available as two distinct models: the US and Hong Kong S10 phones are powered by Qualcomm Snapdragon 855 SoC. Cherry on top: the US variants feature a permanently locked bootloader.

The global models, however, come with an unlockable bootloader and contain Samsung Exynos 9820 platform. Because of this, the Exynos models can be rooted easily in theory.

As a matter of fact, it is not a theory anymore. The developer of Magisk, John Wu aka topjohnwu, already shared an elaborate guide to root the global Exynos models of Galaxy S10e, S10 as well as the S10 Plus.

Our readers may recall that XDA member geiti94 was collaborating with topjohnwu to bring TWRP support for the Galaxy S10 lineup. He also shared a number of intriguing pictures in past, such as:

TWRP on Galaxy S10 (Click/Tap to zoom)
Booting AOSP Pie GSI on Galaxy S10

Nevertheless, he refused to publish the builds then as Magisk had to be updated to support Samsung’s Pie firmware which came with their own version of system-as-root.

However in Samsung’s case, the bootloader simply does not load anything other than the kernel binary to the memory, meaning no matter what we do the kernel will always use the system partition as root directory. This leaves us no option but to install Magisk onto the recovery partition.

Wait, there’s more. The OEM came up with somewhat weird data encryption policies which should be tackled as well.

Installing to the recovery partition have its own issues: first is that a service called “flash_recovery” will run when the system starts up, which will restore the recovery image back to stock on startup. This is unacceptable because not only does it uninstall Magisk in the process, the data encryption key will also be changed due to fact that Samsung’s data encryption keys are tied to the bootloader status and boot/recovery image signatures, and thus causing the device unable to boot in following reboots unless factory reset.

Merely one day after the announcement from topjohnwu, geiti94 has published unofficial TWRP images for the Samsung Galaxy S10e, S10 and S10+. Interestingly, the mid-ranger Galaxy A50 is also supported, as the phones share similar firmware structures.

Galaxy A50

The current builds are based ASCA kernel, which is the build number of the March update released by Samsung. The kernel sources and the minimal device trees can be found here.

geiti94 has also shared a proper installation guide for first time users:

  1. Go to Developer settings and enable oem unlock
  2. power off the device and boot in download mode
  3. in download mode you see the long press vol up option for unlock bl
  4. unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
  5. after bootloader unlock boot up the phone and make sure it is connected to the internet orhe triggers rmm prenormal
  6. setup the phone without google account etc
  7. reboot the phone in recovery mode and do a factory reset
  8. reboot in download mode and flash the tar with prepatched magisk
  9. hold vol up+ bixby+power until you are twrp. (on a50 only vol up+power)
  10. flash the encryption disable zip (you find it in the download folder too. note he needs to get flashed every time you reflash a vendor partition) MAKE SURE YOU HAVE IT ON EXTERNAL SD CARD SINCE I CANT ADD MTP SUPPORT TO TWRP OR MTP WILL BE BROKEN WHEN SYSTEM IS BOOTED
  11. press reboot to recovery in twrp for boot rooted with magisk.

The necessary packages can be download from this Google Drive folder.

Right now, the recovery comes with preinstalled canary build of Magisk. You should not try to update it, as that update routine is yet to be implemented by the developer. Also choosing the ‘Power off’ option from TWRP will corrupt your data partition.

The developer has posted a good news for those, who are worried about the complex booting process after installing TWRP:

for boot then all other times rooted press vol up+bixby+power button (on a50 only vol up+power) until you see s10/a50 logo and release it. soon i will release a script that let the phone boot byself in recovery mode so the button combination is not needed

I should once again chant the side effects of rooting/installing TWRP for the Galaxy S10 users:

  • Knox will be tripped once you flashed custom binaries to your phone.  (Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
  • Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
    (You can flash custom ROMs if you want to keep the OS up-to-date.)
  • All apps that use Knox like Samsung Pay, Secure Folder and maybe more will no more work.

For more info and troubleshooting, please refer to the XDA support threads:

Are you planning to tinker with your $1,000 Galaxy S10? Let us know by commenting below.

Update (May 11)

Based on the geiti94’s initial development, XDA member ianmacd has brought official support for TWRP on Exynos Galaxy S10 lineup.

  • Galaxy S10e (codename: beyond0lte): Download
  • Galaxy S10 (codename: beyond1lte): Download
  • Galaxy S10e (codename: beyond2lte): Download

The unified support thread can be found here.

PiunikaWeb is a unique initiative that mainly focuses on investigative journalism. This means we do a lot of hard work to come up with news stories that are either ‘exclusive,’ ‘breaking,’ or ‘curated’ in nature. Perhaps that’s the reason our work has been picked by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and more. Do take a tour of our website to get a feel of our work. And if you like what we do, stay connected with us on Twitter (@PiunikaWeb) and other social media channels to receive timely updates on stories we publish.


root S10 twrp

Kingshuk De
896 Posts

I came from a mixed background of Statistics and Computer Science. My research domains included embedded computer systems, mobile computing and delay tolerant networks in post-disaster scenarios. Apart from tinkering with gadgets or building hackintosh, I like to hop on various subreddits and forums like MyDigitalLife and XDA.

Next article View Article

[Updated] Instagram crashing on all Android phones, but there are workarounds

Here's the crux of the article in video form: New updates are being added at the bottom of this story……. Original story from (June 5, 2018) follows: We're...
Jul 10, 2023 6 Min Read