If both of the above methods fail, or if your custom recovery cannot decrypt your storage, the absolute foolproof method to remove Magisk 25.2 is to manually overwrite the modified boot partition using Fastboot. Step-by-Step Instructions:

This is the safest and easiest method if your phone is currently running and you have access to the app. Magisk App on your device. Uninstall Magisk button (usually located at the bottom of the home screen). Complete Uninstall

: Ensuring the device is back to a "stock" state before selling or returning it. Fixing Bootloops

If removing Magisk did not fix your bootloop, the issue might be caused by deep system modifications left behind by older modules, or a corrupted dalvik cache.

Type the following command and press Enter: fastboot flash boot boot.img (Note: If your device uses a separate init_boot partition, use fastboot flash init_boot init_boot.img instead).

There are three primary methods to run the uninstaller, depending on your device's current state. The table below summarizes the advantages and disadvantages of each approach.

Before diving into the uninstaller, let's briefly cover what Magisk does:

The .apk file is the standard Android app installer. The .zip file is a flashable package meant to be installed via a custom recovery like TWRP to patch the boot image and install root. Interestingly, the .apk file can be renamed to .zip and flashed in TWRP to uninstall Magisk.

Deducted 1 point for the lack of safety checks and its potentially catastrophic failure mode if no stock boot image is found. But when used correctly, it is the gold standard for root removal on Magisk 25.2.

Open the Magisk app, navigate to the Modules tab, and toggle off or delete all active modules. Reboot your phone once after doing this. This prevents leftover module scripts from causing conflicts after root is removed.