This document details my experience with attempting to update Magisk on my Google Pixel 4a running Android 15. While Magisk was initially functional, I encountered issues during update attempts to version 28, 29, and the canary debug build. I observed unexpected version rollbacks and failed downloads, ultimately leading to the app seemingly getting stuck on version 8. Here's a breakdown of the steps I took and the observations I made:
**Initial Setup and Stable Functioning:**
I successfully used Magisk up to version 27, with root working correctly and the Magisk app functioning as expected, even after OTA updates. Magisk properly preserved root access.
**Update Attempts and Version Rollbacks:**
- I downloaded newer versions of Magisk (28, 29, and canary debug) and attempted to update. These attempts, whether through downloading the new APK or using the app's update function, consistently failed.
- Several times, the app reported a successful update, but the displayed version remained unchanged, and it constantly indicated a newer version was available.
- Even after uninstalls and reinstalls, the Magisk app consistently reverted to version 8.
**Detailed Troubleshooting Steps:**
- I observed that the app seemed to reinstall itself upon reboot even after uninstalling. This led me to believe some mechanism within the patched boot image was responsible for this behavior.
- In an attempt to bypass this, I skipped the reboot step after uninstalling and installed the latest canary debug version.
- While the app installed and appeared functional initially, with a higher version code, it quickly reverted back to version 8 upon launch.
- A dialog prompted me to upgrade to the full Magisk, with the promised download and installation. However, despite the notification, no download progress was observed, and the version remained 8.
**Logs and Further Analysis:**
- I captured the `magisk.log` file, which seemed to reflect outdated information about the version (version 27).
- Grepped `logcat` for 'magisk' and attached the filtered output along with the full `logcat` logs to provide additional information.
- The combination of version rollbacks and failed downloads suggests a complex issue related to updating, potentially stemming from the way the app interacts with the patched boot image.
**Conclusion:**
While I eventually managed to resolve the issue by patching the boot image with version 29 (stable), this experience raises concerns about Magisk update stability and suggests potential improvements to the update process within the app. The attached logs might provide valuable insights for investigating this issue further.
Ultimately, I hope this detailed account helps to identify and address potential problems within the Magisk update mechanism.
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.