Bootloop
If you end up in a bootloop when installing Magisk, flash the Magisk app renamed to uninstall.zip in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over. If the uninstaller fails or you do not have access to a custom recovery on your device, just flash your unmodified copy of the boot image and you should be good to go. There will probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but that shouldn't be an issue.
·
First make sure your system can boot
up without Magisk.
·
Boot to recovery and install Magisk.
Boot up your system without installing any modules. Also see "Module
causing issues" below.
Some devices might need a more hands-on approach
to disable dm-verity, or the device will bootloop when installing Magisk.
See Working with dm-verity and forced encryption for more details.
It is also possible that the device is refusing
to boot because you've added system apps or processes to the MagiskHide list. That's not a good
idea... Only add the apps detecting root to the Hide list. Also see "System instabilities" below.
Another big cause for bootloops are modules that
are incompatible with your device/system. Keep reading below.
Bootloop after
module installation or device update
If your device
bootloops after installing a Magisk module, or after updating your device
(there might be an incompatible module installed), see "Module causing issues".
A/B devices
(Pixel, etc)
Many users are reporting about bootloops on Pixel and other A/B devices.
Often this is caused by having TWRP installed at the same time as installing
Magisk. Since the recovery now resides in the boot image, having these two
modifications to the same partition may cause issues. If you want to use TWRP,
use fastboot to only boot it, don't install:
Android 11
Bootloop on Android
11 is also often caused by having TWRP installed (just as above). Boot it,
don't install.
Custom kernel
If your system
bootloops again and you're using a custom kernel, try starting over without
installing that kernel. If there's still a bootloop your system might just not
be compatible. One possibility is to try finding another custom kernel that is
compatible.
Magisk update
If there’s just been
a new Magisk release it’s also possible that there might be something with
Magisk causing the issue. Just keep calm, restore your device like described
above (also see Updating), but first make sure to provide proper
logs (see "Asking for help/reporting bugs").
DM-verity and
Forced encryption
Another thing to try
if your device ends up in a bootloop when flashing Magisk, is to keep dm-verity
and force encrypt enabled (be very careful when working with modern Android
devices though, you might cause more issues). By default Magisk might remove
these flags from your boot image which on some setups have been reported to
cause a bootloop. See "Working
with dm-verity and forced encryption" for more details.
Module issues
A bootloop might
also be because you’ve installed a module that Magic Mounts new files or
folders to the root of /system, etc. On some devices this will cause a
bootloop. Contact the creator of the module you’re trying to install and let
them know… Also see "Module Issues".
Special cases
Some devices need
special modifications to the boot image to not bootloop with Magisk. Sony is
one of these manufacturers, where you may need to disable RIC.
Magisk not
installed
After installing
Magisk, if the app still reports that Magisk is not installed, check if the app
has been installed to the external or adoptable storage. This is known to cause
all kinds of issues, so make sure that the app is installed to the internal
storage and check again.
This might also be happen when the Magisk app
update doesn't go as planned and you end up with two app installed or the app
doesn't actually update. Something that might lead to issues... See "There are
two Magisk apps" or "Magisk
not installed" for further details.
Some users seems to experience this issue
randomly, where Magisk seems to uninstall by itself. See "Randomly losing root" for more details.
System
instabilities
If your system
suddenly becomes unstable, with reboots and system processes stopping, make
sure you haven't added any system apps or processes to the MagiskHide list. Because of the
way MagiskHide works, it might kill off
some pretty important parts of the running system if this kind of
apps/processes are on the list, causing all kinds of havok.
Only add the apps and processes that actually
detect root to the MagiskHide list.
Apps are force
closing
Apps on the
MagiskHide list
If apps on the MagiskHide list are force closing,
simply remove them from the list. You should only add the apps and processes
that actually detect root. Adding anything else to the list, that doesn't need
to be there, may cause instabilities in your system (also see "System instabilities" above) Note: It's not about
the number of apps on the list, but which apps are added.
WebView issues
If a bunch of apps
suddenly start force closing after installing Magisk, your ROM might have
issues with WebView. More precisely with the signatures for Chrome and Google
WebView. You can take a logcat when one of the apps crash
and see if there's anything about WebView in there. The reason is that MagiskHide sets ro.build.type to
"user" and this enables the signature check. Ask your ROM developer
to fix the signature error... Meanwhile, you can fix it temporarily by
disabling MagiskHide, use the Magisk module MagiskHide
Props Config to revert the
prop value, or use a boot script to revert the MagiskHide prop change (see "Reverting prop values set by MagiskHide").
It's also possible that removing and
reinstalling Chrome stable or Google WebView (or simply installing one of
them if it's not already installed) will fix the issue. If nothing else,
installing Chrome Beta should work. After that you
can go to Developer options -> WebView implementation and select the corresponding
implementation.
It might also be possible to use Chromium. There
are several Chromium installers available both in the Play Store and on
F-Droid.
Other
If it's not an issue
with MagiskHide or WebView, grab a logcat from the crash and post it
together with lots of details in the support thread (also see "Asking
for help/reporting bugs").
Developer
options disappeared from settings
If Developer options
suddenly disappeared from settings after installing Magisk, it's probably
because MagiskHide changes ro.build.type from
"userdebug" to "user" (known "safe" prop value).
On some devices/ROMs this prop need to be set to "userdebug" to show
the Developer options.
You can use the Magisk module MagiskHide
Props Config to revert the
prop value, use a boot script to revert the MagiskHide prop change, or temporarily
disable MagiskHide (also see "Reverting prop values set by MagiskHide")
Or, there's a much better solution... You can
ask your ROM developer to add this commit.
Beginning of
crash
In the Magisk log
you'll sometimes see "--------- beginning of crash". This is
perfectly normal and unless you experience issues with Magisk it is nothing to
worry about. Since Magisk uses Android's logcat for collecting logs this will
appear in the log as soon as there is any kind of crash occuring on your
device, regardless if it has anything to do with Magisk or not.
Wifi stopped
working
If your Wifi stops
working after installing Magisk and you're using a custom kernel, try
reflashing said kernel.
Magisk isn't
working
If you can boot up,
but Magisk isn't working as expected (not detecting the Magisk installation,
loss of root, etc), there are a few things you can try.
1.
Reboot. Sometimes this helps Magisk
mount everything as it should.
1.
Try removing any installed modules to
see if it's a faulty module causing issues. If that seems to fix it, install
the modules one at a time to find which one causes issues.
1.
If nothing else works, try starting
fresh with a new installation.
.
0 Comments