Related
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
I'm using official Omni 8.1. The issue I'm facing is that the Magisk Manager can't seem to remember the apps it has granted Superuser permission. Even in the Superuser tab it shows "No apps found". Result being I have to grant Superuser permission every time when I open an app like Root Explorer.
Please look into this issue.
Magisk Manager: v5.5.2
Magisk Root: v15.1 Stable
I don't have this issue on version 5.5.0 and 15.1 on the latest Omni 8.1 weekly on my Oneplus 3T.
Edit: You didn't mention what device, so I doubt anyone would be able to help you. But I guess you're running a Oneplus 3T or a Oneplus 5 since there are no 8.1 Omni weeklies for any other devices, yet. Maybe you could try to attach some logs.
For me Magisk v15.1 doesn't boot anymore, it just fails and goes back to recovery.
v14.6 works fine.
Omni 8.1 on Oneplus 5T
Same problem here. Any solution?
Look into this issue, doesn't boot, solutions?
Where are the logs?
How do you expect someone to help you without that?
For all the praise Magisk seems to get, it sure does have some issues. Lately, it's been kind of a lottery figuring out which version will work with which ROM... These things never happend to me on SuperSu
Jazavchar said:
For all the praise Magisk seems to get, it sure does have some issues. Lately, it's been kind of a lottery figuring out which version will work with which ROM... These things never happend to me on SuperSu
Click to expand...
Click to collapse
I'd say it has to do with the incredible speed that the Magisk development has been going at. Looking back over the past year, a lot has happened. This kind of speed can cause instabilities...
Now, it's most likely at a point where the focus will be on stability and compatibility development.
Having said that, though, all users experiencing issues can help with that by providing as much details as possible and relevant logs.
I can confirm this. It seems Magisk has a problem opening the sqlite3 database, on OmniROM 8.1 at least.
The Superuser request can be granted, and it goes through (as in the app gets its root access), however nothing is permitted "forever".
Superuser log in Magisk Manager is empty, so is the list of apps granted Superuser access.
From my log:
Code:
sqlite3 open failure: unable to open database file
Either the sqlite3 database is located somewhere else, or Magisk didn't get the correct writing rights during the install. Did something change regarding this in 8.1?
There is also a somewhat unrelated issue with Magisk Hide, where the hidelist-file doesn't exist/wasn't initially created upon installation:
Code:
fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
Full log attached.
debichu said:
I can confirm this. It seems Magisk has a problem opening the sqlite3 database, on OmniROM 8.1 at least.
The Superuser request can be granted, and it goes through (as in the app gets its root access), however nothing is permitted "forever".
Superuser log in Magisk Manager is empty, so is the list of apps granted Superuser access.
From my log:
Code:
sqlite3 open failure: unable to open database file
Either the sqlite3 database is located somewhere else, or Magisk didn't get the correct writing rights during the install. Did something change regarding this in 8.1?
There is also a somewhat unrelated issue with Magisk Hide, where the hidelist-file doesn't exist/wasn't initially created upon installation:
Code:
fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
Full log attached.
Click to expand...
Click to collapse
Two things I'm curious about (at the moment):
What are the permissions for /data/adb/magisk.db?
Do you now have a hidelist file in /sbin/.core/img/.core?
Didgeridoohan said:
Two things I'm curious about (at the moment):
What are the permissions for /data/adb/magisk.db?
Do you now have a hidelist file in /sbin/.core/img/.core?
Click to expand...
Click to collapse
There is no such file in that location. There is a magisk.img in that folder with -rw-r--r--, and a magisk/ folder but not containing any magisk.db file either.
Yes, there is now a hidelist file in /sbin/.core/img/.core with -rw-rw-rw-
Bonus info:
I did a complete wipe (I initially did that but I wanted to be certain), and I got this error while installing Magisk right after OmniROM (also see attached):
Code:
! System installed root detected, mount rw :(
Now, OmniROM doesn't ship with root built in - at least not to my knowledge. So I don't know what this "system installed root" Magisk is detecting.
debichu said:
There is no such file in that location. There is a magisk.img in that folder with -rw-r--r--, and a magisk/ folder but not containing any magisk.db file either.
Yes, there is now a hidelist file in /sbin/.core/img/.core with -rw-rw-rw-
Bonus info:
I did a complete wipe (I initially did that but I wanted to be certain), and I got this error while installing Magisk right after OmniROM (also see attached):
Code:
! System installed root detected, mount rw :(
Now, OmniROM doesn't ship with root built in - at least not to my knowledge. So I don't know what this "system installed root" Magisk is detecting.
Click to expand...
Click to collapse
Number 1 is an issue, because that's the su database... If there is none, it's no wonder why granted superuser requests aren't saved.
Hi, do you have a solution?
@Didgeridoohan i am facing same issue like this . it keeps asking for superuser req .
cpt.macp said:
@Didgeridoohan i am facing same issue like this . it keeps asking for superuser req .
Click to expand...
Click to collapse
As far as I know, so far the only known working solution is to reformat /data as ext4. Or stay on an old version of Magisk.
Didgeridoohan said:
As far as I know, so far the only known working solution is to reformat /data as ext4. Or stay on an old version of Magisk.
Click to expand...
Click to collapse
which version you suggest also my /data is ext4 only .
also i would like to tell you one more thing after tinkering little bit and observed following things
as soon as i dont open the magsik app and using root by simple toast and granting the permission it works but as soon as i open the app , it starts misbehaving . i wonder why .
cpt.macp said:
which version you suggest also my /data is ext4 only .
also i would like to tell you one more thing after tinkering little bit and observed following things
as soon as i dont open the magsik app and using root by simple toast and granting the permission it works but as soon as i open the app , it starts misbehaving . i wonder why .
Click to expand...
Click to collapse
Let me guess: you're not using OmniROM...
Since you're posting in this thread, I kind of assumed you did, so my answer was given accordingly.
If you need help, post all possible details and lots of relevant logs.
I've had the same error. Magisk seems unstable on OmniROM 8.1 on OnePlus 5. Probably an issue with the ROM, but the developer seems like the kind of guy who will tell you to go f*ck yourself if you have a problem like this.
Sometimes it works sometimes it doesn't.
A temporary workaround with the permission issue on /data/adb/magisk.db, even after not working trying 0666 permissions, was to change ownership. None of many other solutions worked for me until I found the user for Magisk. You can use a shell as root or with apps like FX File Explorer with root capability to see which user owns files in "/data/adb/magisk/" . Then I applied that user as the owner of magisk.db. Verified that apps which ask for root permission get saved now. The user of Magisk will be different for you since it is marked as "app_##' which I suppose is up to the amount of apps you have installed.
I have a problem and think it caused by the same reason other users here.. My issue is after installing omni rom and gapps ONLY i can't use my banking apps because ( i guess) it thinks my device is rooted.
Device : oneplus 5
I wasn't planning to root my device to keep those kind of issues away
saidmsb said:
I have a problem and think it caused by the same reason other users here.. My issue is after installing omni rom and gapps ONLY i can't use my banking apps because ( i guess) it thinks my device is rooted.
Device : oneplus 5
I wasn't planning to root my device to keep those kind of issues away
Click to expand...
Click to collapse
No... I don't think so. This thread is about an issue with Magisk and f2fs on Android 8.1 ROMs. Your issue could be that OmniROM sets some sensitive props to triggering values.
That can be taken care of by using Magisk and MagiskHide. Take a look here for more info:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Sensitive_props
If you decide to install Magisk, this part of the guide might also be useful (all of it is useful, really):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Hi, a few questions:
1) How can I check if I have logd enabled or not? I have Magisk 16.2 and my MagiskHide is not loading on bootup, I have to disable and reenable it for it to work and I think it may be due to 16.2 change to have MagiskHide disabled if logd is disabled.
2) Can you enable/disable logd from within android interface without a PC?
3) Is it safe to downgrade from 16.2 beta to 16.0 stable from within Magisk Manager?
Thanks.
If you can enable MagiskHide after booting up, that means you have logging enabled already. On some devices, it's just a bit slower to start...
Don't worry though, it's likely been fixed and should be in the next release (that @topjohnwu is working non-stop on getting out there). Relevant commit, if anyone's interested:
https://github.com/topjohnwu/Magisk/commit/5be035fd44eb6fd5e4e51b53d6105fdad0ef6491
Shouldn't be any worries downgrading. And if you do experience issues, it's just to do a clean install instead...
*XDA self-double-post*
I never manually enabled that logd though. I just got the tablet a few days ago and straight up installed Magisk 16.2. How would I go about enabling/disabling logd though?
The rest of the features of Magisk seem to work, the hidelist file has 666 permissions and seems to save correctly, but I have to manually disable/enable magisk hide after each bootup. I'd really like to solve this...
You don't have to enable logging, it's on by default.
The issue has already been fixed, just not yet released. If you really can't wait, use one of the unofficial snapshots.
I see, do you know what the issue is about? I've read topics about this where people didnt have the hidelist file or it had wrong permissions but mine is there with 666 and seems to save fine. If it's a widespread issue, shouldn't it affect everyone? Some of those users seem to have fixed it.
Other posts discussed magisk not mounting right with an unsupported filesystem but the rest of the features work fine for me.
I've also read about needing kernel >3.8 but mine is 3.18 so that should be fine.
My device is an Alldocube Iplay10 on android 6.0.
I'm not sure what is causing it if I indeed have logd enabled.
But you are confident the next stable release will fix it? Or the next beta release? Does he have a rough timeframe of when it's coming?
Thanks for the help by the way.
@topjohnwu
Its been long i have been experiencing this same problem since magisk v15 and i am not the one who is getting this issue.
When you flash magisk everything is fine and you get su prompt without any issue.
But if you see after sometime maybe like 10 or15days its not sure it comes random and new app you install yoj never get prompt of su request.
Issue in magisk log is same as others
04-26 07:54:08.656 26879 26879 E Magisk : write failed with 32: Broken pipe
04-26 07:54:23.254 27099 27099 W Magisk : su: request rejected (10240->0)
04-26 07:54:57.742 27473 27473 W Magisk : su: request rejected (10230->0)
04-26 07:55:06.003 27527 27527 E Magisk : write failed with 32: Broken pipe
04-26 07:55:12.932 27541 27541 W Magisk : su: request rejected (10262->0)
04-26 07:55:18.934 27571 27571 W Magisk : su: request rejected (10211->0)
04-26 07:55:26.091 27612 27612 W Magisk : su: request rejected (10217->0)
04-26 07:55:26.093 27613 27613 W Magisk : su: request rejected (10217->0)
04-26 07:58:20.432 27670 27670 W Magisk : su: request rejected (10211->0)
Click to expand...
Click to collapse
that 10412 is random number maybe uid
But saved su request apps keeps working as fine they can execute su commands which are saved in magisk manager but new apps never get the prompt.
So i think this issue is somewhat related to magisk manager app which doesnot repond, even though i have made sure magisk manager is in my recent app not killed still no prompts.
Now i am fed up with this so posted this issue.
The only thing which works for me i have taken data backup of magisk manager and restore it so my apps stays working fine.
Temp fix whivh always work for me is i have tk flash system image in twrp backup restore and then after sometime after reboot magisk shows prompt, dont know whats this.
My devices are s7 and s9+ exynos same issue on both since v15 i started using magisk.
Full logs attached.
I think I faced the same issue (or at least something similar) two or three times, I will try to get some logs for the next time.
This needs to be analyzed properly every user gets this but we ignore wven for me it is not working even after jninstalling and installing magisk
Every user is not experience this... As an example, I've never seen it. But, that doesn't mean that there isn't an issue, of course.
You're completely correct that it would need further analysis to know what's going on with your device. To me it sounds like your system is killing of the Magisk daemon (or something similar).
Your mention that you have to reflash the system to get things working, but that sounds a bit drastic. What else have you tried? Have you tried simply force closing the Magisk Manager, etc?
And of course, if you're really serious about analysing things you'll have to grab logs showing exactly what's going on.
Didgeridoohan said:
Every user is not experience this... As an example, I've never seen it. But, that doesn't mean that there isn't an issue, of course.
You're completely correct that it would need further analysis to know what's going on with your device. To me it sounds like your system is killing of the Magisk daemon (or something similar).
Your mention that you have to reflash the system to get things working, but that sounds a bit drastic. What else have you tried? Have you tried simply force closing the Magisk Manager, etc?
And of course, if you're really serious about analysing things you'll have to grab logs showing exactly what's going on.
Click to expand...
Click to collapse
hi this issue has been reported many times in this magisk sections you can search and find this,even google search can brings many issues like this.
i dont know what fixes the issue cus nothing works, but flashing system and starting then popup doesnot come immediately it takes time to come even when you ran app 5mins back then back to normal
full magisk logs attached
BytesReverser said:
hi this issue has been reported many times in this magisk sections you can search and find this,even google search can brings many issues like this.
i dont know what fixes the issue cus nothing works, but flashing system and starting then popup doesnot come immediately it takes time to come even when you ran app 5mins back then back to normal
full magisk logs attached
Click to expand...
Click to collapse
I've seen reports of it, yes, but it's far from a universal issue. The main problem is that the required details for any kind of "fix" generally is missing from the reports (just a plain Magisk log is usually inadequate).
My guess is that it's likely caused by to aggressive OEM implementations of battery optimisation or the likes thereof.
Didgeridoohan said:
I've seen reports of it, yes, but it's far from a universal issue. The main problem is that the required details for any kind of "fix" generally is missing from the reports (just a plain Magisk log is usually inadequate).
My guess is that it's likely caused by to aggressive OEM implementations of battery optimisation or the likes thereof.
Click to expand...
Click to collapse
I have already added magisk manager to unoptimized apps in battery, dont know what is wrong only @topjohnwu can help.
Right now i didnot flashed system because i want to figure jt out whh this is happening, i can test if topjohnwu guides what he needs
hope topjohnwu will fix it soon
I managed to get it work again. Sharing what i did in sequence:
1. Delete all module in magisk. Trash can icon. Reboot.
2. In magisk manager, uninstall > clear images. Reboot.
3. In magisk manager, uninstall > complete uninstall. Reboot automatically.
4. Reboot to recovery. Flash magisk uninstaller .zip. clear dalvik/cache. Reboot to system.
5. Install magisk manager apk. Reboot.
6. Reboot to recovery. Flash magisk 19.1 zip. Clear dalvik/cache. Reboot to system.
Try su at terminal trigger magisksu prompt after step 6.
Hope this helps.
I have a blu dash l 4.4.2 with twrp and I'm also facing this or similiar issue with su request rejected in log, permission denied in terminal, modules flash but magiskhide and superuser do not. I have tried many things with no luck.
No display over other apps, battery, or any other permission settings included. Only 20.4 flashes on my devices others say unsupported image format. 7.1.1 magisk manager seems to be only one which says additional update but then goes to setup failed. Magisk app settings others ok, tried toggling root access, canary settings crash. Have tried to copy and chmod rw 600 to libdirect file from another device to vendor and lib folders because my device does not appear to have it included. Minimal adb fastboot module tip no luck as well as reflashing stock.
Would like to try to add "(sleep) 1 to early_mount " as I read somewhere but not sure how exactly. No luck yet manually updating magisk.db but I am hoping there is someway to have it fully functioning automatically somehow. Any help much appreciated
i have the same issue ,i was rooting my huawei with magisk ..
To resolve this you need to go to magisk manager press install (the first one) ,recovery mode (if needed) and then direct install ,this worked for me
I am hoping that someone can help me. I have had an LG V40 with Android 9, Magisk, TWRP, and some Xposed Mods. At first all seemed fine in all respects. Then I noticed that the date/time in TWRP was not correct at all (2018 instead of 2020, etc). But I am 100% sure that at some point in the recent past it was correct (or at least close enough for me not to notice). So I am looking for the cause of this and how to fix it.
I noticed here that TWRP has some special code (cannot claim to fully understand it) that processes date/time differently on Qualcomm 800 series chips - which my phone has. In looking around at the code, I see that it is looking at ats* files so I have gone looking for them on my device. I find them in several places (nothing is ever easy):
/mnt/vendor/persist/time
/sbin/.magisk/mirror/data/vendor/time
/sbin/.magisk/mirror/persist/time
/data/vendor/time
In /mnt/vendor/persist/time I see:
ats_12 with modify at 2/9/2018 @ 10:39am
ats_13 with same
ats_15 with same
ats_16 with same
In /sbin/.magisk/mirror/persist/time I see the same as above.
in/sbin/.magisk/mirror/data/vendor/time I see:
ats_1 with modify at 5/1/2020 @ 6:09pm
ats_2 with same
ats_12 with modify at 5/13/2020 @ 11:49am
ats_13 with same
ats_15 with modify at 5/13/2020 @ 10:49am
ats_16 with same
And in /data/vendor/time I see the same as above.
What I am not understanding here is if these multiple sets are the result of Magisk and, if so, which are/were "original" and which are "mirrors" and in general what is Magisk doing with all this? I read here, under the heading MagicMount, that Magisk is doing things with /system and possibly with /vendor and /product. So I cannot really explain to myself what I am seeing here or why it is happening.
I apologize for the length of this and for veering off into TWRP a bit. But it is the only way I can describe my situation and conundrum.
I also have no idea how TWRP interacts with Magisk - if at all and how that might play into the date/time problems I am facing.
So thanks for your patience and help.
The files in the mirror directories are used by Magisk for Modules (magic mounting) and MagiskHide.
I'm guessing you found those files while booted up and not in TWRP. Thing is that those Magisk mirror directories won't be there when you boot into TWRP (they're mounted by Magisk during a normal boot) and thus they can't have any effect on what you are describing.
Magisk does not load at all when you boot to TWRP.
Didgeridoohan said:
The files in the mirror directories are used by Magisk for Modules (magic mounting) and MagiskHide.
I'm guessing you found those files while booted up and not in TWRP. Thing is that those Magisk mirror directories won't be there when you boot into TWRP (they're mounted by Magisk during a normal boot) and thus they can't have any effect on what you are describing.
Magisk does not load at all when you boot to TWRP.
Click to expand...
Click to collapse
Thanks for the help. You are correct, I was looking while booted into the system.
Do you happen to know if, while Magisk is doing the mirroring and merging, it fiddles any folder/file permissions/ownerships? Or should these remain identical to the "originals"? Cheers!