Database Develop

Magisk is consistently causing my Settings app to hang after booting

I have no proof of this, but this has been happening on my Note 4 (SM-N910T) ever since v13.3, and now on v14.0. I also bought a Huawei Honor 6X about a week ago, it's now happening there too. I didn't feel that this was worth posting about, figuring it might be device-specific or ROM-specific. But now that it's happening on 2 devices I've changed my mind.
Note 4:
Android 7.1.2 (CMRemix)
Xposed unofficial by PurifyOS (system mode)
Kernel sets SELinux to permissive on boot
Magisk v14.0
No Magisk modules installed
Honor 6X:
Android 7.1.2 (Resurrection Remix)
Xposed (systemless Magisk version)
Kernel sets SELinux to permissive on boot
Magisk v14.0
No Magisk modules installed
Description of the issue:
After powering on/rebooting, I can't open system Settings app for up to a minute or so. It just hangs on a white screen. It then either gives a message stating that Settings isn't responding, or, if I manually close Settings with the Recent button then try to reopen it, it repeats the same behavior but will eventually open. Sometimes I need to access Settings immediately after boot to make changes. Device is otherwise responsive, Magisk appears to work fine.
I have tried clean ROM installs on both devices, with full wipes beforehand, and latest stable Magisk. I've also tried with and without Xposed, results are the same. This didn't happen before v13.3, v11.x and v12.x didn't exhibit this behavior. But back this I was using systemless SuperSU in conjunction with Magisk. I suspect that MagiskSU may be the culprit.
MagiskSU is also noticeably slower (when compared to SuperSU or non-Magisk Phh's Superuser) at responding to SU requests, even with a setting of auto-grant and the lowest possible timeout (10 seconds), and global mount namespace. This may be due to the fact that does more than just rooting, it is logical to assume that it has more background processes running since it is also a systemless framework, whereas the other 2 solutions only manage root access.
Last, my file managers oftentimes won't let me delete/modify certain files/folders in the system partition, with a message like "device or resource busy", or flat-out denying access. System is remounted as RW. This only happens with Magisk, but never with SuperSU or Phh. I do use Magisk for systemless mods, but sometimes I want to make direct midifications to /system. Magisk, as a root solution, shouldn't be denying my ability to do this, since I own my devices, not Magisk.
Right now I'm primarily concerned with the Settings issue, but I figured the other issues are worth mentioning. I'm still on the fence, I may return to SuperSU, or Phh, trying Magisk again after a few more stable releases. But if this can be resolved then I'll give it another chance.
I'm posting the logs for my Honor 6X, one is the Magisk log from /cache, the other is /data/anr/traces.txt. Attempts to get a logcat during boot were unsuccessful.
Thanks for any help!

Magisk saves a log during boot that you might find useful. It's /data/magisk_debug.log. A logcat from when the device has booted up and you're trying to open up the Settings might also be interesting.
Have you tried on a stock ROM? Both those ROMs you're using are related and may have similar ROM specific issues...

dont open setting immediately after reboot. open it after a minute. not really a problem

It is not Magisk problem that cause this problem but it is the rom...i'm also using RR 7.1.2 on bacon and Magisk v14 and have no problem at all but we bacon user does encountered this problem in RR build in July and the devs fixed this on August build....
Sent from my A0001 using Tapatalk

@all: I've been super busy lately, not much time to post anywhere. But getting back to this.....I doubt this is a ROM issue. My reasoning is that it would occur with or without Magisk if that were the case. I don't get this issue when using SuperSU or non-Magisk Phh Superuser (regular). This only occurs when Magisk is installed, since v13.3, but not before that version. It has also occurred on Huawei stock EMUI firmware.
@24imelqui: Just because you don't consider something to be a problem doesn't mean it isn't a problem for others. I have a need to be able to access my Settings app immediately after booting. Your comment isn't useful in the least, if you can't post something helpful then don't post at all. /Ignored.....
@iPusak Gaoq™: isn't Bacon a Nexus device (not sure, never owned one)? Can you reference something where this has been reported? And fixed? Like something on XDA or GitHub or whatever? If this can be proven to be ROM issue then I'll post something to my devices' devs to see if it can be fixed in later releases.
I'm attaching several logs, this time a logcat as well. No such debug log exists in /data, and Magisk v14.0 has no options in the Manager app for debug logging.

AnonVendetta said:
@all: I've been super busy lately, not much time to post anywhere. But getting back to this.....I doubt this is a ROM issue. My reasoning is that it would occur with or without Magisk if that were the case. I don't get this issue when using SuperSU or non-Magisk Phh Superuser (regular). This only occurs when Magisk is installed, since v13.3, but not before that version. It has also occurred on Huawei stock EMUI firmware.
@24imelqui: Just because you don't consider something to be a problem doesn't mean it isn't a problem for others. I have a need to be able to access my Settings app immediately after booting. Your comment isn't useful in the least, if you can't post something helpful then don't post at all. /Ignored.....
@iPusak Gaoq™: isn't Bacon a Nexus device (not sure, never owned one)? Can you reference something where this has been reported? And fixed? Like something on XDA or GitHub or whatever? If this can be proven to be ROM issue then I'll post something to my devices' devs to see if it can be fixed in later releases.
I'm attaching several logs, this time a logcat as well. No such debug log exists in /data, and Magisk v14.0 has no options in the Manager app for debug logging.
Click to expand...
Click to collapse
There have been issues previously, where it seems like it's a Magisk thing but it's really a ROM issue. Some things Magisk does (and it does a few more things than just root your device) can sometimes bring problems out into the light...
I believe bacon refers to the OnePlus One (Nexus devices are all named after aquatic creatures). Looking in the RR thread over in those forums I'd guess you'll find your information somewhere around here: https://forum.xda-developers.com/on...tion-remix-t3507102/post73283623#post73283623
About your logs: I'm not too good at reading logcats, so no help from me there. But, I see something there in your Magisk log... Have you tried disabling Xposed?
There are things going on when a device with Magisk starts, so depending on your setup it might take a short while (30-ish seconds for me on my daily driver) before root requests start being accepted. If the ROM settings require root, that might be the reason why it won't open straight away when booting up your device.

OK, back again, Xposed disabled this time in the app (but still installed), so not active.

Here is the full changelog on the build where the devs fixed the issues on settings freeze/fc on startup....
https://forum.xda-developers.com/showthread.php?p=73304715
Sent from my A0001 using Tapatalk

Raiffeisen Twint (https://play.google.com/store/apps/details?id=ch.raiffeisen.twint)

Hi everyone,
I am using the application Raiffeisen Twint (version 1.2.16.0, https://play.google.com/store/apps/details?id=ch.raiffeisen.twint) on my Magisk's rooted Google Pixel (Android 8.0, Nov. 2017) without problems for a while, but since Magisk 14 versions, the application stopped working and the application reports that root is detected.
I have successfully updated to Magisk 14.5 (from 14.2), but root is still detected by the application, even with Magisk Hide activated for the application and the Magisk Manager package moved to a random name (could also be related to the updated application).
I have cleared the data of the application several times and it doesn't help and root is still detected by the application...
Anyone has a idea?
Thanks for your answers!

Like I said in the Magisk support thread, I can hide Magisk from that app just fine (on Magisk v14.5 beta)...
You don't happen to have any other mods that might trigger an app looking for root (like Xposed)? Can your device pass SafetyNet? Have you previously been rooted with any other root method and do you have any remnants of that left (root management apps, etc)? Do you have any apps that are known to be used for questionable purposes. By "questionable purposes" I mean getting access to paid features without paying, etc. Not necessarily that you use the app for this, but that the app might be used in such a manner... Etc, etc, etc. Every little detail might count.

Hi Didgeridoohan,
Thanks for helping me!
I do not have any mods installed in Magisk and also no Xposed. My device is passing SafetyNet!
I have performed a factory reset last week and since that I only rooted my device with Magisk 14.2, so no other rooting applications used. For details, I have unlocked bootloader, TWRP recovery installed and developer options and USB debugging activated.
My settings in Magisk are:
I have following applications installed on my device:
https://pastebin.com/pmt4jBMV
Do you see any applications with "questionable purpose"?
I get this message in the application:
Thanks a lot!

At a quick glance everything looks ok...
I did some experimenting with the other Raiffeisen apps you have installed, in case they also detect root and "tell" on you. At least one of them did detect root, but from what I could see it didn't make any difference for Twint.
I also tested installing a few of the root apps you had installed (in case the app looks for certain known apps), but that didn't make any difference either. I could still successfully hide root.
My guess is that it's something along these lines tough. That it's using another app or detecting a root app. You could start experimenting with that. Clearing data for the other Raiffeisen apps and adding them to MagiskHide and also removing root apps. Try disabling USB debugging and developer options as well (didn't make difference for me, but worth a shot).

Simple. Change name of package from settings in Magisk Manager, then MAKE SURE you add twint app to magisk hide list, then ERASE DATA of twint app, change package name once again and run twint. Working with Magisk 14.5. Screens if u want available. Or video.

Hi Didgeridoohan, Hi Mamama07,
Thanks for your help, but sadly none of your suggestions did worked... until the update of the application released yesterday, to fix problem related to rooted devices! [emoji3]
Thanks anyway again for your help! [emoji106]

I had the same problem (with BCV Twint) and after a few tries, changing Magisk Package Name worked!

How to remove MagiskManager

I'm on Ressurection Remix Mod, which comes with Magisk installed by default. It was working just fine before, but recently I've noticed it may have caused issues with battery drain. So I decided to remove Magisk - I ran magisk-uninstaller, which removed Magisk itself but the MagiskManager stayed. As I don't have su/root now I can't use Titanium Backup to remove it.
I was under the impression, that magisk-uninstaller should remove the manager as well.
How should I remove the manager altogether?

.wojtek said:
I'm on Ressurection Remix Mod, which comes with Magisk installed by default. It was working just fine before, but recently I've noticed it may have caused issues with battery drain. So I decided to remove Magisk - I ran magisk-uninstaller, which removed Magisk itself but the MagiskManager stayed. As I don't have su/root now I can't use Titanium Backup to remove it.
I was under the impression, that magisk-uninstaller should remove the manager as well.
How should I remove the manager altogether?
Click to expand...
Click to collapse
If the ROM creator has included the Manager as a system app (which is just stupid), the uninstall script can't remove it... You'll have to do it manually, either by re-rooting or from recovery.

I'm not sure if it's included as system app (seems so, can't uninstall, only 'disable'). I've tried running 'full uninstall' from Magisk Manager witout success.
Can I install SuperSU as root to remove Magisk Manager? Or will there be any conflict?

.wojtek said:
I'm not sure if it's included as system app (seems so, can't uninstall, only 'disable'). I've tried running 'full uninstall' from Magisk Manager witout success.
Can I install SuperSU as root to remove Magisk Manager? Or will there be any conflict?
Click to expand...
Click to collapse
If you only have the option to disable the app, it's installed as a system app (why, oh why :crying. There's nothing the Manager or Magisk uninstall zip can do about that.
If you've uninstalled Magisk otherwise (you've run the uninstall zip), there shouldn't be any conflict with another root solution. The Manager is only that, a manager for root and modules.

So, installing SuperSu and then uninstalling Manager with TitaniumBackup will eliminate it completely - correct?
Bonus questions:
* why is it a bad idea to install manager as a system app (vide your comment)?
* is it possible to only install MagiskSU (and have the superuser/su/root) without whole Magisk (I don't need modules and it seems that Magisk Manager is draining my battery - lot's of screen wakelock - totalling in 1h30m in 2h45m total time according to wakelock detector, however screen seems to be off)

Magisk is a systemless interface... Having any part of it installed to /system just grinds my gears. :laugh:
But, it's not only that, of course. The feature to hide the Manager is completely nonfunctional if the Manager is a system app and there are possibly other issues... It's perfectly possible that your issue with battery draining is caused by it. I don't even see the Manager on any battery usage list, and I've been using my device quite heavy today.
If you don't want modules and that part of Magisk, you can enable Core Only Mode, but you'll still needed the Manager for managing superuser requests.

Well, what you say about /system and being system-less totally makes sense now!
As for battery drain - calculation done by Android are weird quite often, but on the clean system it popped right at the top with the screen wakelock…
As for "Core mode" - I'm wondering what was causing the wakelocks - unfortunately I don't have currently screenshot with MagiskManager extended in WLD, which would show the information, but there were only 5 screen wakelocks. At any rate - given that the Manager itself was listed as the cause for the wakelocks (https://www.dropbox.com/s/aj0e6hj77cfwyw6/WLD_magisk.png?dl=0) I'm kinda reluctant to install it again.
It's quite possible that there is different culprit that drains my battery but I'm currently running quite bare-bone (even no gapps and I'm using NewPipe instead of YouTube application )

All I can say is that the Manager causing that kind of wakelock is very wrong. Possibly caused by having it installed as a system app (wild guess). I'd try with removing the system installed Manager and try again with a proper, clean install.

Went with superSu for the time being and will observer how it goes.

Oh fun:
https://www.dropbox.com/s/6aidw5czlrzpo93/WLD_supersu.png?dl=0
I'm... confused...

You could have some app spamming su requests. Check the superuser requests log.

After I posted I had similar though and the registry was spammed with ForceDoze every couple of minutes... so I guess instead of helping it was doing disservice Will see how it goes in the long run.

Root detected by GO MOBILE banking app

I've been scratching my head for weeks now this app keeps on detecting root on my device. I've previously tried canary build, but currently on 20.1 and it still detects it. App is MagiskHided, Magisk Manager repackaged, both SafetyNet basicIntegrity and ctsProfile is passed. My other banking app that also checks for root works, even the rootbeerFresh is showing all green and this app still detects root. I don't know what else to try.
Device Info:
OnePlus 6T running Evolution X rom (Android 10), I also tried on OOS pie, doesn't work as well.
Magisk 20.1
This app used to work just by MagiskHide and repackaging Magisk Manager, since the update, I think they changed something. Any help is appreciated.

I tested it right now and had no issues starting the app once added to the Hide list. OnePlus 3T, Android 9 (ArrowOS), Canary build 20302 with hidden Manager build 269.
That means Magisk can hide from the app just fine and there might be something about your specific setup that's being detected. Could be an app, could be a directory on your storage, could be the ROM itself (this is the second time lately that I've seen a user having issues with root detection on Evolution X, on a Poco F1 though. May be unrelated.).
As always, there are a lot of hiding tips available here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Didgeridoohan said:
I tested it right now and had no issues starting the app once added to the Hide list. OnePlus 3T, Android 9 (ArrowOS), Canary build 20302 with hidden Manager build 269.
That means Magisk can hide from the app just fine and there might be something about your specific setup that's being detected. Could be an app, could be a directory on your storage, could be the ROM itself (this is the second time lately that I've seen a user having issues with root detection on Evolution X, on a Poco F1 though. May be unrelated.).
As always, there are a lot of hiding tips available here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously

terraflops said:
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously
Click to expand...
Click to collapse
I made sure that it could detect root first, so I opened it once without adding it to MagiskHide (got the same screen you showed above). And, I did not have to clear any data for the app after adding it to the list, it just started up without issue.

terraflops said:
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously
Click to expand...
Click to collapse
any luck for this problem?

I also have this issue. Any luck?!

I have the same issue and finally found a solution for it ! Change the folder twrp name on internal storage was a trick but don't forget to hide the aplication go mobile from magisk hide then boom I can use the banking aplication on my root devices .
I'm not using any xposed so if you are on xposed try rename the folder of it usually it store on folder download on the internal if that doesn't work try to uninstal the xposed application on your mobile menu(you can instal it again after you're done with banking)
Another trick that I found latelly was I change the recovery ....any recovery besides the twrp (orangefox,pitchblack,batik etc)

Aldino21 said:
I have the same issue and finally found a solution for it ! Change the folder twrp name on internal storage was a trick but don't forget to hide the aplication go mobile from magisk hide then boom I can use the banking aplication on my root devices .
I'm not using any xposed so if you are on xposed try rename the folder of it usually it store on folder download on the internal if that doesn't work try to uninstal the xposed application on your mobile menu(you can instal it again after you're done with banking)
Another trick that I found latelly was I change the recovery ....any recovery besides the twrp (orangefox,pitchblack,batik etc)
Click to expand...
Click to collapse
Awsome maaan, like that simple trick could be solve the pricky app

Magisk appears to be installed but no root

Hi
I have magisk installed but my phone is reporting not rooted.
My setup:
Xiaomi Redmi Note 7
Ressurection remix
Magisk 23.0
Things I've tried:
Disabled battery optimisation for magisk app
Reinstalled magisk a couple of times from twrp
Other root requiring apps (no change)
I've attached the logs from Root Checker, magisk and snip of my magisk. Please let me know if there is more info I can provide.
Thanks in advance for any suggestions!

re-flashing latest stable magisk.zip with the custom recovery then reboot to system and open the magisk wait to downloading requested resources and see..

Hi
Thanks for your reply.
I just downloaded this and flashed it with twrp: https://magisk.me/
Rebooted and found the same issue. Any other ideas?
Cheers
Oliver

arahknxs said:
Hi
Thanks for your reply.
I just downloaded this and flashed it with twrp: https://magisk.me/
Rebooted and found the same issue. Any other ideas?
Cheers
Oliver
Click to expand...
Click to collapse
1 - Don't use that website. The only place for verified and safe Magisk downloads is on John's Github:
https://github.com/topjohnwu/Magisk
2 - Exactly what is it that's reporting that your device isn't rooted? Because Magisk quite clearly says it is, according to your screenshot...

Didgeridoohan said:
1 - Don't use that website. The only place for verified and safe Magisk downloads is on John's Github:
https://github.com/topjohnwu/Magisk
2 - Exactly what is it that's reporting that your device isn't rooted? Because Magisk quite clearly says it is, according to your screenshot...
Click to expand...
Click to collapse
Hi
Thanks for the reply.
Okay so I went to Git and downloaded this file https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk I then renamed it to .zip and flashed it via TWRP. Is this correct?
When I reboot I find the same situation. Magisk appears installed correctly however no app can access root. No popup appears to accept/reject the su request and apps behave as if no root access. I've tried Root Checker, Titanium Backup and am happy to try any others.
Do you have any suggestions please on what else I can try?
Cheers
ara

Ah... So the problem is not that you do not have root access The problem is that there's no superuser prompt when an app requests root.
IIRC there's a Xiaomi settings to allow apps to display popup messages (should be under app permissions). The Magisk app also need to be allowed to auto start. Of course, this is for MIUI and you're using RR so I have no idea if there is such a setting on your device currently...
Could of course be something completely different though.

Didgeridoohan said:
Ah... So the problem is not that you do not have root access The problem is that there's no superuser prompt when an app requests root.
IIRC there's a Xiaomi settings to allow apps to display popup messages (should be under app permissions). The Magisk app also need to be allowed to auto start. Of course, this is for MIUI and you're using RR so I have no idea if there is such a setting on your device currently...
Could of course be something completely different though.
Click to expand...
Click to collapse
Yes I suspect this is the issue - the notification is being blocked somehow.
Under app settings -> Magisk, I believe the settings are right:
Battery optimisation = off
Notifications = all allowed
There are plenty of guides out there of using RR with Magisk and no mention of any special settings to make it work.
I am also using nova launcher, I wonder if this could affect the notification somehow?
All suggestions welcome!
Cheers
ara

I noticed in Magisk under the Superuser tab, it just says "no app has asked for superuser permission yet." So perhaps not a notification issue after all?
I downloaded another app, "root checker basic". It also generated no popup, said I do not have root, and nothing appeared in the Magisk logs.
I feel like I am doing something wrong here but missing what it is.
Cheers
ara

arahknxs said:
I noticed in Magisk under the Superuser tab, it just says "no app has asked for superuser permission yet." So perhaps not a notification issue after all?
I downloaded another app, "root checker basic". It also generated no popup, said I do not have root, and nothing appeared in the Magisk logs.
I feel like I am doing something wrong here but missing what it is.
Cheers
ara
Click to expand...
Click to collapse
One thought: make sure that nothing is restricting the Magisk app from autostarting and running in the background.
Also, have you checked with other users of your ROM? Might be a good place to get help for stuff like this...

This happened to me before. I had to rename the same zip to "uninstall.zip" and flash it, reboot, and then rename the zip to something else like Magisk.zip and flash again.

dsiva said:
This happened to me before. I had to rename the same zip to "uninstall.zip" and flash it, reboot, and then rename the zip to something else like Magisk.zip and flash again.
Click to expand...
Click to collapse
Thanks for the suggestion, I tried this but no change afterwards unfortunately.
Also good idea @Didgeridoohan, I will cross post this on the forum for RR.

extract the boot.img and copy to phone. in Magisk, install and pick boot.img. copy the result file to pc, and flash using fastboot flash boot magi....img
if unlocked bootloader, flash direct and reboot.

arahknxs said:
Hi
I have magisk installed but my phone is reporting not rooted.
My setup:
Xiaomi Redmi Note 7
Ressurection remix
Magisk 23.0
Things I've tried:
Disabled battery optimisation for magisk app
Reinstalled magisk a couple of times from twrp
Other root requiring apps (no change)
I've attached the logs from Root Checker, magisk and snip of my magisk. Please let me know if there is more info I can provide.
Thanks in advance for any suggestions!
Click to expand...
Click to collapse
Rename the file to uninstall.zip then flash the firmware then flash the magisk it will work for sure i was also facing the same problem