Samsung recently released the kernel sources for the Galaxy S22 series shortly after the devices were released. Obtaining kernel sources is essential for any third-party development on Android devices. Thanks to XDA member killprocess, an unofficial TWRP support for Samsung Galaxy S22 series is now available. TWRP, for those who don’t know, is required for custom ROMs and other device modifications.
TWRP support for Samsung Galaxy S22 available
When it comes to aftermarket development, a custom recovery like TWRP is required for a variety of reasons. Its main aim is to recover your device if any custom software flashing goes wrong, as stated in the name. Without a modified recovery, flashing a custom ROM without a PC is nearly difficult, as the OEM recovery normally prevents unapproved software from being flashed.
When it comes to the release, the sole constraint is that the TWRP builds are currently exclusively for the Galaxy S22 Exynos edition (model number SM-S90xB). A Snapdragon-compatible version has yet to be released by the developer, however, it is scheduled to be released soon. However, the current development still leaves a large number of users in the United States (as well as Canada) in the dark. This is because the bootloaders of North American Snapdragon Galaxy devices are more difficult to unlock than the international Exynos and Snapdragon models that come straight from Samsung.
Even if you have an unlocked Galaxy S22, take in mind that downloading a third-party binary (e.g. TWRP) disables subsequent OTA updates and irrevocably trips the KNOX warranty bit, therefore voiding the warranty. There is no way to reverse the situation, which means you will lose access to Samsung Pay and other Knox-based features for good. Click the TWRP link if you’re ready to deal with the risk.
To avoid a bootloop or other problems, make sure you read through the installation instructions step by step. The custom recovery’s default UI language is Chinese, however, you may change it to English using TWRP settings. Notably, to remove the stock encryption, you need to delete your phone’s whole user data sector, so make a backup first.
