a magisk module has caused a bootloop. I can enter safe mode. how do I remove the module whilst in safe mode? thre's no sign of magisk? have I lost root in safe mode?
whatsisnametake2 said:
a magisk module has caused a bootloop. I can enter safe mode. how do I remove the module whilst in safe mode? thre's no sign of magisk? have I lost root in safe mode?
Click to expand...
Click to collapse
If you are in safe mode, then just reboot. Your Magisk mods will be disabled and then you can remove the offending module in the Magisk app.
thanks for the reply, yes I figured that out in the end. ha! came very close to resetting the phone!
After reboot my nacisk modules are still active and installed.
I thought ones phone is rebooted in save mode modules will be disabled.
Am I doing something wrong?
netgar said:
After reboot my nacisk modules are still active and installed.
I thought ones phone is rebooted in save mode modules will be disabled.
Am I doing something wrong?
Click to expand...
Click to collapse
Safe mode disables all Magisk Modules. Rebooting after entering safe mode, all Magisk Modules will remain disabled until you individually re-enable any of them.
You're following the correct directions to get into safe mode? It's tricky and temperamental, and also, at least if you use a third-party launcher, all widgets will need setting up again, but not sure if the same thing happens with Pixel Launcher after entering safe mode, too.
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Click to expand...
Click to collapse
roirraW "edor" ehT said:
Safe mode disables all Magisk Modules. Rebooting after entering safe mode, all Magisk Modules will remain disabled until you individually re-enable any of them.
You're following the correct directions to get into safe mode? It's tricky and temperamental, and also, at least if you use a third-party launcher, all widgets will need setting up again, but not sure if the same thing happens with Pixel Launcher after entering safe mode, too.
Click to expand...
Click to collapse
Thank for your response.
Yes, in save mode I can see that everything is disabled even magisk, ones I reboot to system my modules are still installed. Weird...
I don't use any custom launcher.
Do I need to have broken module that actually make my phone blootloop? And than save mode will disable all modules?
Thank you again for help
netgar said:
Thank for your response.
Yes, in save mode I can see that everything is disabled even magisk, ones I reboot to system my modules are still installed. Weird...
I don't use any custom launcher.
Do I need to have broken module that actually make my phone blootloop? And than save mode will disable all modules?
Thank you again for help
Click to expand...
Click to collapse
You're welcome. The modules won't be uninstalled, only disabled - there's a toggle on every module to re-enable it again. No, you don't need to have a broken module that makes your phone bootloop in order for safe mode to disable all Magisk Modules.
roirraW "edor" ehT said:
You're welcome. The modules won't be uninstalled, only disabled - there's a toggle on every module to re-enable it again. No, you don't need to have a broken module that makes your phone bootloop in order for safe mode to disable all Magisk Modules.
Click to expand...
Click to collapse
So something doesn't work for me.
My modules are still enabled.
Picture is posted right after rebooting from save mode.
Edit
I noticed that my widgets are only disabled
netgar said:
So something doesn't work for me.
My modules are still enabled.
Picture is posted right after rebooting from save mode.
Edit
I noticed that my widgets are only disabled
Click to expand...
Click to collapse
I believe you. I have no idea. The last time I used safe mode was probably 7-8 months ago or more. It definitely didn't behave like that for me.
Is it actually a problem, since you're not boot looping - since you're able to boot normally anyway?
roirraW "edor" ehT said:
I believe you. I have no idea. The last time I used safe mode was probably 7-8 months ago or more. It definitely didn't behave like that for me.
Is it actually a problem, since you're not boot looping - since you're able to boot normally anyway?
Click to expand...
Click to collapse
I am just testing just in case installing bad magisk module.
Couple months ago I needed reinstall all my phone because of it.
I guess I still can't risk.
netgar said:
I am just testing just in case installing bad magisk module.
Couple months ago I needed reinstall all my phone because of it.
I guess I still can't risk.
Click to expand...
Click to collapse
Do you just disable them manually before updating, or you just don't update? I disable all mine manually before updating, although certainly once you enable any again, yes, it's possible for it to start boot looping. Usually by then I'll hear about these certain modules causing bootloops on the latest update, though.
roirraW "edor" ehT said:
Do you just disable them manually before updating, or you just don't update? I disable all mine manually before updating, although certainly once you enable any again, yes, it's possible for it to start boot looping. Usually by then I'll hear about these certain modules causing bootloops on the latest update, though.
Click to expand...
Click to collapse
I always disable all modules before system update. I don't have a problem with that.
I got a blootloop after installing "bad" magisk module. That's why I installed bootloop saver module but it doesn't seems to work for me.
netgar said:
I always disable all modules before system update. I don't have a problem with that.
I got a blootloop after installing "bad" magisk module. That's why I installed bootloop saver module but it doesn't seems to work for me.
Click to expand...
Click to collapse
Yeah, I gave up on Bootloop Saver Module. I see you still have it installed. I suggest uninstalling it - I wonder if it's interfering with the stock Android experience after rebooting from safe mode.
roirraW "edor" ehT said:
Yeah, I gave up on Bootloop Saver Module. I see you still have it installed. I suggest uninstalling it - I wonder if it's interfering with the stock Android experience after rebooting from safe mode.
Click to expand...
Click to collapse
I will test it. Thank you for your suggestion.
If all else fails you can just get rid of them all in adb
Code:
magisk --remove-modules
Source
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io
Related
I found the smart lock did not work after root, no matter using beta magisk 14.5 or stable 14. I would like to make sure if this is a problem of my own, or a general case, so that I can decide whether to report this to the developers. Thank you.
I'm using beta 14.5 and when I open smart lock it asks for a pin and then shows a blank white screen. No options to add devices. I've been using face unlock so I didn't notice until I checked after seeing this.
Try this.
Oneplus forums
It worked for me.
shadeau said:
I'm using beta 14.5 and when I open smart lock it asks for a pin and then shows a blank white screen. No options to add devices. I've been using face unlock so I didn't notice until I checked after seeing this.
Click to expand...
Click to collapse
Exactly the problem I have, so this should be a problem of magisk. I guess magisk is not compatible with 5t now, some other people report they have problem with their wifi after root (I also found wifi is slower).
I tried supersu as well, but it can cause a battery drain. So there is no perfect root for 5t till now.
Beaster said:
Try this.
Oneplus forums
It worked for me.
Click to expand...
Click to collapse
It will become blank again after reboot... It's perfect if I uninstall magisk or use supersu instead.
simonand said:
It will become blank again after reboot... It's perfect if I uninstall magisk or use supersu instead.
Click to expand...
Click to collapse
I second that, it turns blank again after reboot. or sometime during use. So irritating.
I just found out that Magisk itself doesn't seem to be the problem.
I did a fresh install, installed magisk without any problem. The problem started after installing a module from within Magisk...
After that Smart Lock blanked out and removing the module doesn't change anything.
Bart1981 said:
I just found out that Magisk itself doesn't seem to be the problem.
I did a fresh install, installed magisk without any problem. The problem started after installing a module from within Magisk...
After that Smart Lock blanked out and removing the module doesn't change anything.
Click to expand...
Click to collapse
What module did you install? I seem to get this problem even with out magisk. Maybe twrp is the cause?
tyrone1 said:
What module did you install? I seem to get this problem even with out magisk. Maybe twrp is the cause?
Click to expand...
Click to collapse
I guess I was mistaken... A later attempt I also got a blank screen after a while.
Not shure why. In the beginning it seems all ok also after a couple of reboots, but then after a certain time and a reboot it's there. again.
Hi all,
I have installed Magisk 16.0 based on Maik93's post, and Xposed Framework SDK27 90.2-beta3 (Systemless), through Magisk modules.
When I enable the Xposed module, the phone first shows endless boot animation, and when restarting it again, it boots, but the Xposed app seems not installed (not listed in Settings->Apps and its icon is not present in chooser), although, in Magisk, it is visible in the Modules and it's checkbox is checked.
Did anybody successfully installed Xposed with A2 Lite? What can be the problem?
Thanks a lot,
Circum
Did you install the apk of xposed?
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
https://forum.xda-developers.com/attachment.php?attachmentid=4393082&d=1516301692
Here is the link from xda
No, sorry, I was not aware that it is a separate thing.
Now I have installed, but it says that no Xposed Framework is installed. If I try to install a framework from inside the installer (90-beta3), it -- obviously -- reports an error that /system/framework/XposedBridge.jar already exist...
Because of this, I cannot enable any module from Xposed Installer.
Any tips what do I do wrong?
I want to use Xposed too but we will have to wait for TWRP I guess.
Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine
mik.y said:
I want to use Xposed too but we will have to wait for TWRP I guess.
Click to expand...
Click to collapse
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img
HoangP05 said:
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img
Click to expand...
Click to collapse
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless
mik.y said:
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless
Click to expand...
Click to collapse
Not all are working apparently, but if it is bootloop, you so try to let it boot again, press power and volume down as the same time while it bootloop, the second boot always work for me
There is TWRP for Mi A2 Lite.
Search on google.
NOTICE: For now there isn't official TWRP. There'w unofficiak fork which can you install using fastboot. :good:
Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
HoangP05 said:
Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine
Click to expand...
Click to collapse
Xposed's Gravity box module works on Mi A2 lite?
Yes, GravityBox is working, although as I mentioned, there are issues with boot - I have to reboot several times until it succeeds...
performace drops significantly when i install the xposed module for magisk. i hope they fix it.
So far everything works fine on my end, I'm not noticing any performance drops in my day to day use. Then again I haven't used it much without Magisk + exposed but from what i'm seeing it's working well, no noticeable lag or stuttering.
I have gravity box, Amplify and Greenify modules running.
circum said:
Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
Click to expand...
Click to collapse
Magisk alone didnt give me boot problems. What rooting guide did you follow?
fake__knv said:
Magisk alone didnt give me boot problems. What rooting guide did you follow?
Click to expand...
Click to collapse
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...
circum said:
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...
Click to expand...
Click to collapse
I can assure you @BubuXP's guide is good. Used his rooting guide, followed the steps for updates and its good to go. I rooted my phone when Im on August update. Now Im in September update
Anyone able to get Viper4Android to process? I have it installed through Magisk and it works when first installed but eventually stops. Only way to get it working again is to reboot.
I think it stops when changing output forms. Instead of rebooting fully, try hitting the 3 dots on the top right of the app and hitting exit and then relaunching the app.
I tried that and force closing it. Didn't work but what seems to have fixed it was uninstalling the driver...it then asked for root permission to do that. After a restart everything is working even when changing apps. We'll see if it's permanent or not. Thanks for the reply though.
Try this: uninstall your current module, reboot, and install this apk. It's an unofficial material design 2 viper that auto generates a magisk module when you install it for your device. I got mine working properly.
Thanks, I'll try that. Been having to reboot again.
Well along with the acp and aml modules that method worked. Hopefully this sticks. Thank you for your help!
TENN3R said:
Try this: uninstall your current module, reboot, and install this apk.
Click to expand...
Click to collapse
That's what I have, and it worked at first but not any longer on Pixel 3a.
Are there other modules that should be installed, or can't be, as well?
-G
ggibby said:
That's what I have, and it worked at first but not any longer on Pixel 3a.
Are there other modules that should be installed, or can't be, as well?
Click to expand...
Click to collapse
I only know about that module, and the one from ahrion and Zackptg5 (here).
Have you tried in this module enabling the compatibility mode and reboot?
TENN3R said:
Have you tried in this module enabling the compatibility mode and reboot?
Click to expand...
Click to collapse
Compatibility mode was enabled, so I disabled it and now it seems to be working.
Thanks for the hint!
I'm using a Pixel 6 Pro rooted and after 1 minute of using the device the device completely freezes and reboots. This happened one day after I rooted my phone and I rebooted my device and it completely stopped working. The logs provided in Magisk don't seem to be useful nor point to the main issue. Safe mode doesn't have this issue, but I'm looking to see how to fix this issue. I'm running TQ1A.230105.002 build. I can try and install a module to help diagnose the issue if it's useful.
Magisk modules installed: Universal Safetynet
Zygisk: Enabled
Rooted apps: Greenify, GoogleDialerMod, Shizuku, Storage Isolation, BBS
fillwithjoy1 said:
I'm using a Pixel 6 Pro rooted and after 1 minute of using the device the device completely freezes and reboots. This happened one day after I rooted my phone and I rebooted my device and it completely stopped working. The logs provided in Magisk don't seem to be useful nor point to the main issue. Safe mode doesn't have this issue, but I'm looking to see how to fix this issue. I'm running TQ1A.230105.002 build. I can try and install a module to help diagnose the issue if it's useful
Click to expand...
Click to collapse
Do you have any Magisk mods installed? If so, one of them may be causing it given you don't have any problems in safe mode.
Lughnasadh said:
Do you have any Magisk mods installed? If so, one of them may be causing it given you don't have any problems in safe mode.
Click to expand...
Click to collapse
My bad, I'll edit the post right now. The freezing does occur even after denying all of them permissions
If it is a module just type in adb magisk –remove-modules
there's also a magisk module that disables misbehaving modules at boot to protect against bootloop it's called magisk bootloop protector
fillwithjoy1 said:
My bad, I'll edit the post right now. The freezing does occur even after denying all of them permissions
Click to expand...
Click to collapse
I've seen another person who had similar problems while using Greenify, so maybe try to uninstall that and see if the problem persists.
Also, if you booted into safe mode and rebooted your modules should be disabled. Does the problem persist with those mods disabled?
Lughnasadh said:
I've seen another person who had similar problems while using Greenify, so maybe try to uninstall that and see if the problem persists.
Also, if you booted into safe mode and rebooted your modules should be disabled. Does the problem persist with those mods disabled?
Click to expand...
Click to collapse
No safe mode is completely fine, but I will look into uninstalling Greenify and see if the problem is fixed.
Thank you! Greenify is the issue!
Lughnasadh said:
I've seen another person who had similar problems while using Greenify, so maybe try to uninstall that and see if the problem persists.
Click to expand...
Click to collapse
I'm not sure why Greenify has been so problematic recently, it even crashes on non-root devices. Maybe it's out of date for such a long time?
fillwithjoy1 said:
Thank you! Greenify is the issue!
I'm not sure why Greenify has been so problematic recently, it even crashes on non-root devices. Maybe it's out of date for such a long time?
Click to expand...
Click to collapse
Excellent! Glad you got it straightened out.
I find Greenify and similar apps aren't really needed these days.
I've got magisk in recovery installed, but it's quite annoying to reboot to non-rooted mode.
To reboot to recovery mode, I need my headphones plugged in, but the reboot works fine.
When I want to reboot to unrooted mode, I have to reboot to download mode, then cancel out of it for it to work. I've tried shutting down and rebooting, using the magisk app to reboot, but all just reboot to rooted recovery mode instead. Is this intentional or something I'm doing wrong?
See Magisk in Recovery
Why are you trying to reboot to non-rooted mode? If you're having issues with certain apps, simply having an unlocked bootloader may be causing the issue. See this thread.
V0latyle said:
See Magisk in Recovery
Why are you trying to reboot to non-rooted mode? If you're having issues with certain apps, simply having an unlocked bootloader may be causing the issue. See this thread.
Click to expand...
Click to collapse
Nah. The apps that are locked during root work fine in unrooted mode. Kinda weird, but they work fine with an unlocked bootloader. It's mostly government apps and banking apps which are locked when in recovery root mode.
Also, yes I saw the magisk in recovery page, and I tried booting from power off, but it somehow goes into recovery root mode instead of unroot. Which is why I'm so confused.
FreSchDude said:
Nah. The apps that are locked during root work fine in unrooted mode. Kinda weird, but they work fine with an unlocked bootloader. It's mostly government apps and banking apps which are locked when in recovery root mode.
Also, yes I saw the magisk in recovery page, and I tried booting from power off, but it somehow goes into recovery root mode instead of unroot. Which is why I'm so confused.
Click to expand...
Click to collapse
I would still check your Play Integrity verdicts to see if that might be part of the problem. It's also possible that the apps in question are able to detect the SU binary; there are Magisk modules that can help hide this such as Shamiko
V0latyle said:
I would still check your Play Integrity verdicts to see if that might be part of the problem. It's also possible that the apps in question are able to detect the SU binary; there are Magisk modules that can help hide this such as Shamiko
Click to expand...
Click to collapse
Alright. So I should check play integrity for root and non-root, and then what is that other test?
Alright, so, non-root mode only passes basic whilst failing device and strong. Root recovery mode fails all 3 checks.
Is there a magisk module to pass the basic check? Or there might be something else besides that that the apps check for when verifying root...
FreSchDude said:
Alright, so, non-root mode only passes basic whilst failing device and strong. Root recovery mode fails all 3 checks.
Is there a magisk module to pass the basic check? Or there might be something else besides that that the apps check for when verifying root...
Click to expand...
Click to collapse
Read the OP, I linked a Magisk module that should fix BASIC and DEVICE verdicts
V0latyle said:
Read the OP, I linked a Magisk module that should fix BASIC and DEVICE verdicts
View attachment 5890551
Click to expand...
Click to collapse
Shamiko, Universal SafetyNet Fix and zygisk has been enabled. Most apps are working, but some still don't work.
Configuring them was sure a pain, I've got over 30 banking/government apps, and a handful still don't work.
I pass the device and basic now, and Momo doesn't detect SU and magisk anymore. I'm curious how some apps are still able to detect root. Probably has the strongest security because it's a government app.
Sorry about all this trouble, I remember that I once tried back when magiskhide was a thing, but couldn't get some apps to work. I then settled for just booting into non-rooted mode and kinda just stuck with it. As of now, around 5 apps of the 30 still refuse to work and are blocked, detecting root, even with shamiko and the other stuff configured.
Hmmm. Try TB Checker and run the root check.
V0latyle said:
Hmmm. Try TB Checker and run the root check.
Click to expand...
Click to collapse
root management apps, SU binary, 2nd SU Binary, Root via native and Magisk specific checks failed.
After setting up the denylist for Shamiko, it only fails the first test, the Root Management Apps one.
FreSchDude said:
root management apps, SU binary, 2nd SU Binary, Root via native and Magisk specific checks failed.
After setting up the denylist for Shamiko, it only fails the first test, the Root Management Apps one.
Click to expand...
Click to collapse
Update: I activated magisk hide and now all checks pass.
I'll be goin off to bed now, I'll be back in the morning.
Thanks for all the help so far mate
No problem.
I'd suggest bringing this up in the Magisk General Support/Discussion thread as the wizards over there might be able to help. Make sure you mention the specific app you're having trouble with.