yashsingh1/xdaforums huggingface dataset:
[Magisk] scottfreeze:
Any chance you had the Active Edge Magisk module installed prior to updating? If so, then you likely have the same problem being discussed in this post: https://xdaforums.com/showpost.php?p=79733736&postcount=34170

I think user ApeironTsuka uploaded a Magisk version that forces core-only mode to fix this problem somewhere later on in the thread.

If that doesn't work for you, I previously had the same problem with the Active Edge module causing failure to boot, which I was able to fix by installing the rescue OTA as described here (this will preserve your apps/data): https://docs.google.com/document/d/1CmHvAzRXOXeNi2nNq9ZxZFudQsOQfhRPY4t19eZY280/

Best of luck!
[Magisk] Estebanium:
I noticed that using Adaway or the Energized Magisk Module for blocking advertisements cause a very high cpu usage.

It doesn't matter if the host file is altered systemlessly or not, but the root process seems to need a lot of resources.

su -c top shows root as top service and also the phone starts to lag. Are there any other with this issue? I am on 19.3. If I disable Adaway the root service is getting normal again.
[Magisk] guest4711:
No problems here with Magisk-19.4 (unofficial daily) and AdAway 4.2.4
[Magisk] wilsonhlacerda:
I haven't seen anything like this. Adaway and Magisk v19.3 now.

Are you using a huge hosts file? Try small one (Energized's Spark for instance) to test.

Do you have pi-hole? Try disable adblocking on your mobile and monitor on pi-hole if you are having tons of blocks....maybe some of your apps are demanding high dns/block.

If you don't have pi-hole, use this new free service: nextdns.io (on lists set advanced and turn on Energized) that you can see logs.
[Magisk] akxak:
After I installed MagiskManager 7.3 by accidently taping on the notification (why isn't there a "do you want to download/install" security question), I ran into the same problems I had with Magisk 19.3. Some apps do not start anymore or just show a white screen. Installing of apps is not possible, so I had again to flash Magisk 19.2.

Both current versions are from my perspective on my OP6 completely instable and unuseable.
[Magisk] Didgeridoohan:
And unless you provide relevant logs and/or precise information on why it's happening, that might never change...
[Magisk] A.lemane:
So ..... Any solution for Huawei (19.3) decryption problem yet ?
[Magisk] akxak:
Well... I know that post... but you state that you require the installation of a canary build... the released version already caused significant trouble... so you expect me to install a canary? Sorry, no.

I had this statement already in the original post but deleted it again, though I expected this reply.

I just got the device back working by getting MagiskManager 7.2 back installed which required some reboots to make 7.2 recognizing that Magisk is in fact installed.

If I know why or what's happening there, I would tell... I just installed MagiskManager 7.3 and after a reboot, some apps (especially those accessing the file storage) did not work anymore. There might be a hanging process during boot causing a lockup or anything else.

If except for installing alphas you can tell me where to look for logfiles I'm happy to provice what I have. I like Magisk and I help, where I can reasonable do so.

Something changed between 18.2 and 18.3 and/or 7.2 and 7.3 which on the OP6 causes these problems.
[Magisk] Xdevillived666:
That worked. Thanks man
[Magisk] Didgeridoohan:
This issue does not require a Magisk log, so the Canary build is not strictly necessary (although when reporting on issues there's always a chance that it's already been fixed of you're not testing on the latest code). I added a small clarification about other apps/system misbehaving.

Remember, a report about issues without any useful information will very likely be ignored...
[Magisk] akxak:
With a message here, I intend to make the author aware that there is a problem and to possibly help others to avoid to run into the same situation I am in.

On this issue, what do you consider useful information?

- Magisk Manager 7.3 installed, reboot (because sound did not work anymore hours later).

- After reboot, many notifications did not show up in the notification list (although the system processed them because my Wear OS watch showed them).

- Apps like RootExplorer, KeePass2Android, Downloads or Filemanager did not start or showed a white blank screen.

- After reinstalling Magisk 19.2 via TWRP the system came up without any further change the system came up so far that I could install MM 7.2 and remove MM 7.3.

- As MM 7.2 did not recognize Magisk, another reboot cleared the situation.

What exactly should I do to retrieve the information you need?
[Magisk] Estebanium:
Thank you for your help. I don't think that I have a pi-hole as the term doesn't mean anything to me.

I use AFWall to use a specific DNS server. This server is only used if I am not in my home wifi. If I am at home the dns server of my provider is used. For now I noticed this issue at home..

If you don't have pi-hole, use this new free service: nextdns.io (on lists set advanced and turn on Energized) that you can see logs.

For what program is your description for?
[Magisk] Didgeridoohan:
Logcat
[Magisk] wilsonhlacerda:
Disable your device adblocker. On AFWall configure the DNS of this service that I linked (for wifi/data). Let it run for some minutes, hours, day....check logs on its website. See if some domain is being requested and blocked lots of times, every second or more. If that's the case, maybe that is what's causing high cpu when your own device is blocking with its host file when adblocker turned on.
[Magisk] maybeme2:
This is probably a very basic question. I just rooted my Moto G7 phone (android pie) using twrp and then Magisk. All went well but

—I now can't access Google play or Yalp. Their screens are totally blank.

—the Magisk hide screen shows a different icon for Google play services. Don't know if I should change it? A circle with a hyphen through it.

Thanks for any help.
[Magisk] XtraWater:
Hi

Clearing Repo cache fixed it... For a while. Did it fix it permanently for you?
[Magisk] bhargavbuddy:
It was temporary for me too. However, I flashed all the modules I wanted when it was showing so it's not much of a concern on that until topjohnwu comes with a fix. My main issue, however, is with the blank superuser window. I can't grant access for Nova for a gesture that requires root. Hoping he'd push a fox fast.
[Magisk] Estebanium:
Thank you for your help it turns out that "fix data leak at startup" in AFWall had some strange impact on Adaway. I turned it off and cpu usage is now normal with Adaway and AFWall enabled.
[Magisk] kotuamoalt:
EVERYBODY has a pie-hole. ?

---------- Post added at 02:53 AM ---------- Previous post was at 02:51 AM ----------

Do not mess with that setting. It is that way by design. Did you try wiping the data and cache on those apps?
[Magisk] maybeme2:
Thank you for replying.

No, I did not wipe data and cache on the playstore or Yalp. I didn't know I was supposed to do that.

As for changing that setting, I unfortunately already changed it in an attempt to fix things. Sorry. Below is the screenshot I took 'before' messing with it. Now Google Play services has only the same option box as all the others only able to be checked or blank. (Second screenshot). No option to restore it the way it was.

What should I do to restore things back to the way it was.
[Magisk] kotuamoalt:
You are not necessarily supposed to do that, it was a suggestion to get your apps working again. Play store should be un-checked. As for Google play services, tap the little arrow next to the circle, and highlight the thing with the word "unstable" at the end.

---------- Post added at 04:05 AM ---------- Previous post was at 04:03 AM ----------

And it's "YELP".
[Magisk] martyfender:
Yes, it will download, but the package installer window should come up and you can choose cancel, instead of install, at least on my Android 6 devices. I'm sure that is the case with newer Android versions.
[Magisk] martyfender:
Magisk Manager v7.3.1 stable and Canary 223 (v7.3.1) have been released.
[Magisk] zgfg:
With v7.3.1 222 and 223 Canary, new bug for me:

- open MM, open SuperUser, list ok

- restart MM, open Super User, MM crashes and restarts itself

- open SuperUser list, MM crashes but does not restart

Then, the same sequence (more or less) repeats: sometimes it survives two restarts with successfully opening SuperUser list, but sometimes it crashes two times in a raw upon restarts and trying to open SuperUser list....
[Magisk] AndrzejDwo:
Hello my friend, I have just tested MM 222 with stable 19.3 and it's working fine for me on my S8 SM-G950F HadesRom v7.

Cheers

Edit: did you try with clean install?
[Magisk] gil80:
I think I now figured out why SaftyNet check and Magisk hide are broken for me.

In my ROM I have to flash SELinux permissive patcher and that seems to break Magisk.

Does anyone know if there's a way for Magisk and SELinux permissive patcher to work well together?

My ROM is: lineage_bacon_userdebug 9 PQ2A.
[Magisk] :
I am using canary debug version magisk (v19.4).....it notified about mm update (v7.3.1 (223)) so I updated and I am facing problem like

When I open magisk and goto superuser it suddenly crashes and then I open again and goto superuser it works and everything else also shows/works but

The sequence repeats itself ---any random 1st time open doesn't work and second time works
[Magisk] zgfg:
I first updated to 223 Canary

After that I was unable to 'downgrade' to 222 stable, so I had to uninstall MM

LateI even cleared MM cache and also wiped Dalwik and Cache in TWRP, did not help

'Funny' video with MM crashes: when opening SuperUser list:

https://mega.nz/#!cosTGSaD!GSGjv9WLfoRUrJ3WhY3E_kLGxpH8TXVrdciGosUxIYM

Zipped logcat with crash also attached here
[Magisk] JudgeDread11:
It was crashing for me after update when opening the su list.

But for me clearing cache in app details fixed it.

Now all works expected.
[Magisk] :
So did you tried cream installing magisk canary debug 19.4 and mm 7.3.1 (223)

As above you quoted me

And tell me if that works

Cause I'm about uninstall mm and flash it from twrp...so

Tell me if this trick also working or not (tell me if possible)

Thanks for A2A
[Magisk] andreacos92:
Uninstalling Magisk Manager also removes all the installed modules?
[Magisk] kryshnakishore:
Yes
[Magisk] garylawwd:
Edit
[Magisk] :
Not helping me

(I used canary debug 19.4 magisk and mm 7.3.1 (223) version)

Tried what you said but nothing...same problem

I guess I should wait for another update ...or something...
[Magisk] zgfg:
Not:

- Uninstalling Magisk removes all modules

- Uninstalling only Magisk Manager does not remove modules - when you install MM again, modules are still there
[Magisk] guest4711:
No. These are stored in /data/adb/modules. /data/adb/magisk.db is preserved also if you uninstall the Manager.
[Magisk] gil80:
Hi [MENTION=7786725]zgfg[/MENTION] do you know if Magisk can work well with Selinux permissive? Seems that when I flash the permissive patch, it breaks magisk hide and magisk safetynet check.
[Magisk] zgfg:
Dunno, it may depend also on your ROM
[Magisk] Pandemic:
Yes and ? Let the dev fix the magisk v19.+ bootloop for our xz2, log is posted but still no news ><"

https://github.com/topjohnwu/Magisk/issues/1537
[Magisk] mammenj:
Random reboot issue in Bootleggers (Samsung Galaxy S7)

Hi All, I am attaching the logs of my phone Galaxy S7. After updating to Magisk 19.3 version on Bootleggers ROM, I am getting random reboots or reboots while using the phone. I dont know if its a ROM issue or Magisk issue. I have posted the same logs in Bootleggers ROM as well but no response from the dev.

Hope someone can look at the attached logs and see if its Magisk issue or not?

TIA.
[Magisk] cameron1292:
Currently on 213. Prompts to update to 222. Seems version 222 doesn't work. App crashes upon opening and sometimes crashes the phone. Downgraded to 213 for now

Edit: oneplus 7pro international firmware
[Magisk] lentm:
PS4 Remote Play with Sony Framework v1 stopped working since Magisk v19.3 & Magisk Manager 7.3.1 as it was able to see the device as rooted.

Uninstalled and reverted it back to 19.0 & included Magisk Manager 7.1.0, now PS4 Remote Play works again.

Hide Magisk Manger and Magisk Hide enabled on PS4 Remote Play and DualShock Manager from Sony Framework module.

The device is Sprint Galaxy S5 with the last Stock Marshmallow firmware.
[Magisk] vonDubenshire:
Can anyone help with this?

I have uninstalled most modules but I noticed on SOME apps I get this green box - with a different error depending on the app.

It does not happen in Chrome or in Telegram, but if I go to log in to the XDA Labs app it will come up with the "smart lock" features and say something about client heuristics.

If I open Messages (Google's SMS), it will pop up with this.

I've changed every setting I can think of. I don't know if it has been doing this all morning or not, I just got Magisk and some things set up this morning.

I thought it was AdAway but I removed that and such and it still happens. Rebooted after every change just for luck.
[Magisk] mindlery:
June security patch. Sorry I fell asleep and in the process sent the message laying on the mouse without finishing.

I was up all night trying to figure out why my ROM was not working with Magisk. (and June update SM-A530W).

I just went back to the 7.2 Manager, 19.3 and there are no issues.
[Magisk] nacos:
Is it just me or "turning a deaf ear" is really happening? I can definitely speak for most others here who have been having nothing but problems with virtually all version after 18.2 and yet, all we see coming from the dev (and other known contributors) is "no, everything is fine, it should be working, it's your phone, just provide the log" type of replies. The dev definitely knows the reasons behind it all, and it's the lack of transparency that really puzzles me. As far as I know there was no communication indicating the Android versions and phone brands which should be compatible with certain Magisk versions - in a way implying they should all be working with the latest Magisk version. Well, that's clearly NOT THE CASE!

I have a Samsung S8, running stock Android 7.0 and after getting boot loops on all, 19, 19.1 and 19.2 I just stopped fooling around and reinstalled 18.2, which is the last version that seems to be working for everyone. Since there is not much feedback I won't be installing.19.3, but the real question is: what is really going on here?
[Magisk] mrsim:
hello the community,i have tried searching the thread for my problem but to no avail.....seems i have the V4A driver instal problem where it just refuses to allow the driver to be installed giving me the 'i/O' error please reboot and try again over and over

i have se linux set to permissive,busy box pro installed and obviously why i am posting here is because i am using the magisk downloaded V4A module...now i originally had this working no probs first time install on OOS,(oneplus 3t), oreo,then i updated to 9.3 pie but that borked my device so much i rolled back to oreo again but now whenever i attempt to install the same mod which is the viper4android_fx_legacy v4.3.zip via TWRP latest release is there any solution for getting the driver to install correctly

thanks a bunch if you have a solution
[Magisk] MaFiBoSS:
Its working in my device.

PS4 Remote Play v2.8.0

Magisk Stable v19.3

Magisk Manager (MM) v7.3.1

Sony Framework v1
[Magisk] kotuamoalt:
Are you somehow being forced to use magisk? Because that would just be wrong.
[Magisk] duh1:
Everyone has to understand that Google play services is continuously being updated to work against us. It's Google's goal to lockdown their OS as much as iOS and thereby convince corporations that it's safe to have their employees use Android, so they can make even more profits, and collect trilliions of data records to create massive AI databases to model human behavior, and eventually make us all redundant and unnecessary.

The fact that this runs over ever restrictive Google play services and dozens of new devices every year, is simply remarkable and a testament to the tenacity of its developer and those who support it. The fact that they do this voluntarily and for free, should mean that it's userbase cuts them some slack as they work out the kinks.

I think what you meant to say is that we all appreciate how much work and effort goes into this, and that we hopefully look forward to compatibility with future Android versions, because there's nothing else out there like this and without it secure apps will no longer run on these devices...

So the actual point is that nobody is forcing you to update. If you have a version of Magisk that is currently working for you, make a nandroid backup, and if a future update is incompatible with your device or system simply restore it, and try again with a later version...
[Magisk] kotuamoalt:
I, for one, welcome my Google overlords... ?
[Magisk] Paschfire:
You're in the wrong thread if looking for support with ViPER4Android.

This is the thread related to V4A-Legacy Magisk module discussion, you'd probably have greater success looking for solutions here;

https://xdaforums.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058/page503

Though, may I suggest you try completely removing the BusyBox Pro installation and install osm0sis BusyBox for Android NDK.(Available as Magisk module)

Also available here within osm0sis Odds & Ends thread;

https://xdaforums.com/showthread.php?t=2239421&page=242

I suspect BBP is the possible cause of the issues you're having with the V4A driver failing to install correctly.

Also.. V4A-v4.3-Magisk-module works perfectly fine with SElinux Enforcing on the OnePlus 3/3T running OOS 5.0.8 Oreo, there's no need for setting SElinux Permissive.
[Magisk] JarMagic:
Pixel 2xl, unlocked pie. Everything was working great. I pushed the hide button and poor...only had 2 setting buttons and lost root. I tried the script provided, no luck. I tried factory reset, wipe to no avail. The app indicates manager installed, but magisk not installed. Very frustrating, there must be an easy fix I'm missing. Any help greatly appreciated.

Thank you
[Magisk] kryshnakishore:
What's this? When I click yes it says " setup failed" & I lost all other settings in magisk
[Magisk] hfam:
Now that you outed the great big conspiracy to make 19,x fail on your platform, you should DEMAND a full refund. Immediately.
[Magisk] hammondegs:
Just noticed Google Chrome doesn't appear in magisk hide anymore.

Has anyone else experienced this?
[Magisk] topjohnwu:
I am not paid to maintain Magisk. I'm currently interning at Apple, which gives me very little free time to work on Magisk.
[Magisk] nebula9:
It's absurd to suggest that John has intentionally made magisk ineffective. This would be both a complete waste of his efforts and his limited time and would provide no benefit to him. If you want to fix things, the source is available. Presumably you have a computer and unlimited free time (after all, you've assumed he does) — why don't you do us all a favor and PR some fixes then?
[Magisk] guhvanoh:
Congrats on the internship. Hope it goes well.
[Magisk] hammondegs:
Thank you for your great work and all the best for your future at Apple.

:good::)
[Magisk] aditya.jain02:
Cant open magisk manager 7.3.1.

Stuck on stating logo.

While v7.2.0 is working fine.

My device :- oneplus 7

Oos :- 9.5.5 rooted with magisk manager 7.2.0
[Magisk] garylawwd:
Is magisk manager installed on internal storage? Make sure it is!

And if that is not the problem just delete data for magisk manager
[Magisk] lm089:
Modules no longer loading

This refers to an ageing Sony Xperia Tablet Z (WiFi only, aka pollux_windy). There are current problems with the compatibility of some Xperia devices and newer versions of Magisk. Some ROM developers have reacted, and their ROMs are now supporting newer Magisk version. My pollux_windy however is running an official version of LienageOS 15.1, and this has not (yet?) implemented the necessary fixes.

That's why I'm still running Magisk v18.1 on that device (alongside Magisk Manager V 7.2.0), and to date it's working fine.

Now over the last weekend ther was a regular update of LineageOS (V 15.1 build 2019-06-16), and since I installed that Magisk isn't loading any modules. I can uninstall and reinstall them through Magisk Manager, and they show up in the list. But after the restart they aren't loaded, and /data/adb/modules is empty. The device is properly rooted so that part of Magisk is working.

I posted something similar at Lineage's subreddit channel, but my first post got removed ("Your post has been removed because: No xposed/microG/supersu/magisk/themes discussion"...), but I tried again today trying to explain to the moderators that I need to ask for help on both sides.

I don't have much faith that this can be solved but who knows, maybe someone has an idea what I could do to solve this (apart from turning to a different ROM...)
[Magisk] aditya.jain02:
Yes its in internal storage. Idk if it a system app or not.

Tried deleting cashe and data.

Magisk keeps stopping.
[Magisk] hfam:
Like catching a glance of a celebrity on Rodeo Drive, TopJohnWu quickly glitches in and out of the thread like a ninja. :laugh:

Eternal thanks for creating a true revolution for Android. I can't even imagine android life without Magisk. Thanks for all your hard work!!
[Magisk] guest4711:
It looks like there is an old Magisk Manager, perhaps as system app? I'd make a backup of all modules, run the uninstaller and flash Magisk.zip again.
[Magisk] djjohnnyblaze:
Hi,

I just got the pixel 3a and flash magisk using patched boot.img

I am rooted but a few things are not working properly in Magisk Manager:

1. Clicking on the superuser tab force closes Magisk Manager app

2. If I try to hide Magisk Manager by repacking the apk, I lose root. Even reboot does not bring back root. However, if I uninstall the "Manager" apk and reinstall the original Magisk Manager apk, things return to normal.

Any help is welcome. I am running the latest Magisk Manager with the current stable Magisk release.

Thanks in advance

EDIT: I was able to fix the first issue by force stopping Magisk Manager, clearing cache/app data, and restarting the phone. I dont reallly have a need for option 2 any longer.
[Magisk] Strephon Alkhalikoi:
For the record, 19.3 is working fine here. Issues with the module catalog in Magisk Manager were, from what I recall, resolved with the latest update to the Manager app.

Now that we have that out of the way, if you really want Magisk to work for you, you need to do some work. Grab the sources and try to fix it yourself, now that we all know [MENTION=4470081]topjohnwu[/MENTION] doesn't really have the time to spare anymore. Do that and be a hero, or keep complaining and be a zero.
[Magisk] wilsonhlacerda:
Does anyone have this bug? Is it happening to everyone with Magisk v19.3 or just me and my girlfriend?

Only thing I haven't tried yet is a completely clean install of ROM and Magisk v19.3. Everything else do not solve the problem.... So to me seems it is really a Magisk v19.3 bug.

Edit: now we are with Magisk Manager v7.3.1 and I tried to install Magisk v19.3 again from it, but same problem (hide does not work on boot).
[Magisk] guest4711:
It"s a known bug on some device since weeks. It occurs on canary and unofficial builds too.
[Magisk] mkdante381:
Additionaly root is detected when app is on adopted storage. On old version Magisk all was ok. Tested on stable, canary and ianmacd builds.

I have Data and Cache formatted in f2fs, but always Magisk hide work properly with f2fs.
[Magisk] wilsonhlacerda:
Thanks for replying. I read both threads but haven't seen that (I did see the loose hide after some time). Well, bad news, but good to know not only me.

---------- Post added at 08:20 PM ---------- Previous post was at 08:16 PM ----------

Thanks for replying. You are saying that with F2FS your device does not have the not Hide on boot bug? (but the bug is present when not F2FS)

Well, if I understood it correctly that could be a tip for a fix. My partitions are EXT4, but I can give F2FS a try.