Removing root, resetting your data and restoring the manufacturer’s operating system are three different jobs. Start by deciding which one you need. Deleting the Magisk app or performing a factory reset does not by itself restore a modified boot image.
Technical content reviewed against the linked project documentation on 28 September 2026. Follow the project’s current instructions for your exact device and software build.
Choose the right route
- The phone boots and Magisk works: start with the uninstallation option inside Magisk.
- The phone will not boot: use the recovery procedure for the exact model and installed firmware. A random stock image is not a recovery plan.
- You want to sell the phone as stock: removing Magisk alone is insufficient if a custom kernel, recovery or ROM is still installed. Restore the complete official software using the manufacturer’s instructions.
- You used KernelSU or APatch: follow that project’s removal instructions. Magisk’s uninstall action does not remove a different root implementation.
Before you change anything
Record the model, current build number, root method and any custom ROM or kernel. Copy personal files and app exports off the phone, and check that you can sign into your accounts from another device. Keep the exact matching official firmware and a working USB connection available. Use the pre-flash backup checklist.
If Android still starts
- Open the installed Magisk app and review its uninstall choices. Follow the complete-uninstall flow documented for your release; simply uninstalling the APK from Android Settings only removes the interface.
- Allow the process and reboot to finish. If Magisk cannot restore its saved images, stop and use the model-specific stock-restoration procedure instead of borrowing a boot image from another build.
- After restarting, confirm the operating system starts normally and root is no longer granted. Check calls, Wi-Fi and the apps that prompted you to unroot. An app icon disappearing is not proof that the firmware is stock.
Returning fully to stock
For a Pixel, use Google’s official restoration instructions and read the anti-rollback notice for that generation before selecting a build. For Samsung, use the complete model-appropriate firmware procedure: Magisk’s Samsung documentation explicitly warns against restoring individual boot-related partitions in isolation. Other manufacturers need their own recovery instructions.
Do not relock a bootloader while patched images or an unsupported custom operating system remain installed. Relocking is a separate step, can wipe data, and must be supported by the software you have restored. Keep a successful normal boot and the vendor’s relocking instructions as prerequisites.
What unrooting cannot promise
- It does not reset Samsung’s tripped Knox Warranty Bit.
- It does not guarantee that every bank, wallet or work app will accept the device.
- It does not automatically restore every manufacturer warranty or remove account, finance or carrier restrictions.
- A factory reset erases user data; it is not a universal firmware repair.
