Always check the "Known Issue" section before reporting, it will be updated regularly as soon as a new issue is identified.
These beta releases are built with the debug flag enabled, so keep in mind that it will do a lot of verbose logging.
I expect users reporting to at least have basic debug skills, this thread is heavily moderated so refrain from spamming with "useless" reports!
Bundled Magisk Manager: v5.2.0
Release Note | Changelogs | Download
Magisk v13+ is NOT compatible with Magisk Manager lower than v5.0.0
Magisk Manager v5+ is NOT compatible with Magisk lower than v13.0
Both have to be upgraded together in order to work properly
Use the uninstaller in the main thread to uninstall any verison of Magisk installation
These beta builds are already tested with the following: AOSP 5.0, 5.1, 6.0, 7.0, 7.1, 8.0 (O DP4)Known Issues:
Devices with near AOSP behaviour "should" work just fine (e.g. HTC, OnePlus, LG etc.)
Oddballs like Samsung, and OEMs using non-standard boot image formats are the main target for this thread
- None yet
Symptoms and Diagnose Procedure:
- Flashing the zip in custom recovery fails:
Upload the recovery logs (pull the file /tmp/recovery.log, or select "Advanced > Copy Log" in TWRP and upload)
- The device got stuck in the splash screen for nearly a minute:
This means either the magisk daemon had crashed, or some SELinux issue had occurred.
Reboot to custom recovery soon after the device is fully booted up. Pull the log located in /data/magisk_debug.log and upload them here.
- Root is not working:
Please open two terminal (console)
On the first one call:
# Clean up logcat buffer adb logcat -c # Dump logcat output to file adb logcat > magisksu_log.txt
# Access adb shell adb shell # Try call root su
- MagiskHide doesn't start on boot / system.prop in modules aren't loaded / resetprop doesn't work:
All these issues are "resetprop issues". Please open two terminal (console)
On the first one call:
# Clean up logcat buffer adb logcat -c # Dump logcat output to file adb logcat > resetprop_log.txt
# Access adb shell adb shell # Root access su # Test call resetprop resetprop -v ro.test 1 resetprop -v ro.test 2 resetprop -v --delete ro.test
- SafetyNet / CTS / XXX app won't work after enabling MagiskHide:
Unless you can specify how to improve MagiskHide, for example: what additional boot props to patch? What does the app detect? Or else
Please do NOT report ANYTHING related to these kind of issues!
I spent endless hours to create Magisk. If you like my work, feel free to donate.