Keeping your Magisk installation up-to-date is essential for security and functionality. However, update processes can sometimes lead to unexpected issues. Recently, I encountered a challenging situation while attempting to update Magisk on my Xiaomi Mi9T PRO running LineageOS 18.0. I initially tried a direct install of Magisk v28, but after the reboot my phone was stuck at the MI logo, with ADB failing to respond. Fortunately, I was able to boot into fastboot mode.

After several attempts to flash both patched and unpatched boot images without success, I decided to boot into TWRP recovery. Remarkably, after rebooting from TWRP, my phone unexpectedly booted into the system! This might have been a temporary hiccup cleared by TWRP. I was then able to flash the patched Magisk v27 boot image, allowing me to regain access to the Magisk app. I patched the boot.img again and flashed the patched v28 boot image, finally resolving the issue.

This experience highlights the importance of understanding the different recovery modes available and how they can be helpful in troubleshooting Magisk updates. While direct install is often the preferred method, having a backup boot image and the ability to enter recovery are essential for navigating potential problems.

This article is created by nurl and is licensed under the Creative Commons Attribution 4.0 International License.
All articles on this site, unless otherwise specified as reprints or sources, are either original works or translations by this site. Please ensure proper attribution before reprinting.