Transfer the file (the renamed Magisk v25.2 file) to your device's internal storage or an external SD card/USB OTG drive. Power off your device completely.
There is an often-discussed alternative where you rename the Magisk APK file directly on the device using a file manager and then flash it via an app like EX Kernel Manager without booting into recovery. While this can work, it is generally less reliable than the methods described above. The official recovery or in-app methods are always the most dependable.
: Ensure your file manager is displaying file extensions so it is not accidentally named uninstall.zip.apk . magisk uninstaller zip 25.2
A pop-up menu will present two choices: or Complete Uninstall . Select Complete Uninstall .
If your device boots normally into the Android OS and you just want to unroot, you do not need a custom recovery. You can handle the entire process directly inside the Magisk App interface. Open the on your Android device. Transfer the file (the renamed Magisk v25
: Boot your device into a custom recovery like TWRP and flash this uninstall.zip . The script inside will detect the name and trigger the uninstallation process rather than an install. Key Considerations Download Magisk Uninstaller | Unroot Android Safely 2026
This article dives deep into version 25.2—why it remains a critical tool even after newer releases, how it differs from other uninstallation methods, and a step-by-step guide to using it without losing your data. While this can work, it is generally less
| | Possible Solutions | | :-------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | I'm stuck in a boot loop. | - First, try booting into Safe Mode (method varies by device). If you get in, open Magisk and disable all modules. - If that fails, boot into TWRP and navigate to /data/adb/modules . Rename the folder of a problematic module (or all of them) to something like module_name.bak . This disables them, allowing you to boot and uninstall properly. - If all else fails, flashing your device's stock boot image (and potentially system) is the nuclear option. | | I can't access /data in TWRP. | This often means your internal storage is encrypted and TWRP can't decrypt it. You will likely need to use Method 1 from within the working OS or try ADB Sideload if your recovery supports it. | | TWRP says "Unable to find config file" | This is a common, harmless message when flashing the uninstaller. It simply means the uninstall script is setting up its environment. It does not indicate a failure. | | My device is soft-bricked after uninstall. | If your phone won't boot at all after an uninstall, your system partition may be corrupted. The most reliable fix is to flash your device's stock firmware using a tool like Odin (for Samsung) or Mi Flash Tool (for Xiaomi). Research the specific method for your exact phone model. |
Magisk App remains after boot. Solution: The uninstaller removes the binary and boot image , but it may not always remove the Manager App. Manually uninstall the Magisk app from your Android settings > Apps.
Do you have installed, or are you working with a stock recovery?
Android 5.0 (Lollipop) through Android 13 (the target range for Magisk 25.2). Not tested or recommended for Android 14+.