yashsingh1/xdaforums huggingface dataset:
[Magisk] bunta126:
On my kids phone running a resurrection remix ROM I use the protected apps feature under the privacy settings to prevent access to certain apps.

I was running Magisk 17.3 and just tried updating it but after it installs Magisk Manager 7.3.0(220) when the manager app launches it comes up with a protected app warning (even though it is not enabled as a protected app) and then the app loads but it can't detect that Magisk is installed.

I have flashed the latest Magisk 19.3 from recovery and the old Magisk Manager now shows that 19.3 is installed but the new version of Magisk Manager still does the same thing and won't detect Magisk installed.

I disabled all the protected apps settings so it is disabled for everything but I still get the protected app warning whenever the new manager version launches.

Any ideas what is wrong here and why it won't load correctly?

EDIT: Never mind, I just uninstalled both managers, reflashed 19.3 and then the 7.2 version it came with was loading correctly. Updating then to 7.3 worked fine.
[Magisk] gil80:
Does anyone have magisk hide working for them?
[Magisk] kunaldas65:
new manager update not showing module correctly in download section

tried clear repo cache...rom aex 8.1.0
[Magisk] wilsonhlacerda:
Magisk Manager 7.3 obfuscated here.

Same bug as others: download section fails and so.

If go to settings and clear repo cache the download works fine. But just for the first or second time. Then start failing again. Then clear repo cache and ok....then fail. Can repeat always.

By the way, Magisk 19.3 is _always_ failing magisk hide on boot. My previous 19.1 and 19.2 (and 18.x, 17.x....) was fine, without this bug.

After boot if I turn magisk hide off / on it works fine and never loose it. Problem is only during boot and only with 19.3.

LOS14.1 not encrypted here.
[Magisk] lightdelegate:
Hi,

I've got notification for update. Tried and first time in my life it was blocked.

Please see the attached picture

I had to cancel Google play protect to install it.

Google is blocking Magisk...
[Magisk] martyfender:
Reverting back to MM 7.2.0 is reported by another user to fix the first issue, I'm not sure if it fixes the Magisk Hide issue, though. 19.2 is a good bet for the Magisk Hide Issue, as I have seen this reported by others.

I'm on Canary and Unofficial builds. On Canary, reverting Magisk Manager only, to 214, fixes the first issue. On [MENTION=7187684]ianmacd[/MENTION] unofficial builds, reverting MM only, to 2019052801 fixes the first issue you mentioned.

The first issue has been reported on the github issue area and accepted as a bug to fix.
[Magisk] Didgeridoohan:
Can't replicate any issue with hiding Manager v7.3.0... More info needed (and logs are always expected).

Logs for that freezing issue?

Bugged how? If there's something going on, provide as much info as possible (and logs), or nothing can be done about it.

Of course.
[Magisk] hammondegs:
All works fine on my G925I S6 edge running stock 7.0 nougat rom.

Magisk Manager crashed the first time I selected "superuser", but has worked perfectly since.

Updating has never been a problem, but I keep modules to the bare minimum.
[Magisk] Pandemic:
We hope we get a new update soon for XZ2 on pie of magisk, we still get stick with v18.1 due the bootloop of v19.+ and yes the logs are posted in the magisk report github.
[Magisk] gil80:
I get system error when I try to upload zipped log file.

I'm trying to fix magisk hide on Pie ROM.

Not sure how the latest update broke it.

Here's a link to magisk log: https://mega.nz/#!J5oVxCaC!ykdUQ3qdpuEgCKnJX_FRZoDBH1W1g8TlQLhaTCVo8hQ

Really need help fixing magisk hide.

Apps won't load because they see I'm rooted, even though they are marked in magisk hide.
[Magisk] guest4711:
Did you try to toggle MagiskHide off and on again once before using the apps?
[Magisk] gil80:
I did. Didn't help
[Magisk] Didgeridoohan:
I tested Opal Travel and have no issues hiding root from it (on Pie, Magisk Canary build 19301 and Manager build 221). If you can't, that suggests there's something wrong with your setup rather than a general issue.

And about logs: unless you're on the Canary debug build there won't be much troubleshooting info in there...
[Magisk] djdelarosa25:
Magisk Manager 7.3.0 still isn't updated in the OP
[Magisk] dd721411:
You can upgrade directly from Magisk Manager or download the apk file from the GitHub link in the main thread. It seems OP only updates the main thread when there is a Magisk upgrade, not the Manager's.
[Magisk] gil80:
I have 19.3 and 7.3 freshly installed.

Prior to the latest update, magisk hide was working great.

Also, the Oral B app is not working on root devices.
[Magisk] duh1:
Speaking of logs, missing the new manager change log in the update thread.

Reading over the comments so far, should there be this much trouble with a minor upgrade to the manager in the stable channel?

Btw, with Netflix and other apps not compatible issue that mysteriously appeared one day with all checks and certifications still passing, and then Q beta 4 changing it's structure to do an end run around Magisk, get the feeling Google's about to make root mods much more difficult...
[Magisk] svendsvin:
Same problem here. Reverting back to 7.2 does not solve the problem.
[Magisk] WarriorMax:
My system UI keep rebooting after pattern unlock. I'm on Havoc rom on redmi note 3. Don't know whats causing the issue. This is happening after I selected magisk core only option and changed the manager name option to install my HDFC bank mobile app which doesn't work due to root detection. Anyone else facing system UI issues?
[Magisk] dkoek:
Same problem after updating.
[Magisk] darfri:
Try Magisk 19.1
[Magisk] Didgeridoohan:
Or, a much better idea is to provide a logcat showing why it's happening... That way, if there's an issue caused by Magisk, there's a possibility of a fix. Otherwise, that possibility is very, very slim...
[Magisk] labello29:
Magisk manager 7.3 bug missing download modules downgrade 7.2 visible and working modules. I hope this bug is fixed
[Magisk] Bi0haZarD:
Try in settings, magisk hide switch ->on switch to ->off then back to ->on.
[Magisk] mkdante381:
Stable and Magisk Canary build root is detected by Tesco Clubcard Polska(installed on adopted storage). When Magisk Manager 7.2 was hiding, Clubcard app not detect root. This works on this version, but not on 7.3. Why Magisk force always new Magisk Manager?
[Magisk] Didgeridoohan:
Can't test that one (not available for me), but have no issue hiding root from other Tesco apps.

Does it make any difference if the app is on adoptable store or not?

But, the Manager has no impact on MagiskHide. Sounds more like there was some kind of issue repackaging the Manager with a random name. You can use an app like RootbeerFresh to see if any parts of Magisk are detected.
[Magisk] mkdante381:
Yes after repackaging Magisk Manager to random name, all settings resetting to default. Magisk hide list is restored properly. Tested also on "Allegro" app if is on adopted storage. Allegro detect root.

No problem if app is on internal memory Smartphone. I'm tested ianmacd build and also is problem with detect root.

Edit:

OK I'm mark all from Google Play Services and root is not detected. Default is only 1 service ticked, from Google play services. Now is ok, maybe Google better detect root?
[Magisk] scottfreeze:
Would anyone be willing to take a look at the attached logcat to figure out why my brand new Pixel 3 with Android 9.0 June security update won't boot after installing Magisk 19.3?

Here's what I did:

-Factory reset

-Skipped setup to enable USB debugging

-Fastboot booted to TWRP 3.3.0.0 (also tried 3.2.3.0 with the same result)

-Installed Magisk 19.3, successfully finished

-Reboot to System

The result is a 1-2 minute bootup attempt, after which the phone reboots back to Android Recovery with the message "Can't load Android System. Your data may be corrupt..." and the only choices are Try again or Factory data reset. Uninstalling Magisk with the uninstaller zip allows the system to boot normally again.

The attached logcat contains this little snippet but I am in over my head when it comes to analyzing the logcat for the error that caused it.:

06-16 10:46:57.534 6511 6511 W RescueParty: Noticed 5 events for UID 0 in last 111 sec

06-16 10:46:57.534 6511 6511 W PackageManager: Incremented rescue level to FACTORY_RESET triggered by UID 0

Any help at all would be appreciated!
[Magisk] Didgeridoohan:
Very unlikely. You probably just had to kick-start MagiskHide. Impossible to say with the amount of information at hand though.

For future reference:

https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] aziz.yankee:
I am having an issue installing Magisk 19.3 on my Pixel 3 (PQ3A.190605.003). I've side-loaded updates according to this tutorial but now I can't. Before update I used to have it installed on January 2019 patch (PQ1A.190105.004) with earlier version of Magisk.

I've tried to reinstall the Magisk Manager but still no luck. I am following this in order to get root:

Copy the boot image to your device

Download and install the latest Magisk Manager

Press Install → Install → Select and Patch a File, and select your stock boot image file

Magisk Manager will install Magisk to your boot image, and store it in [Internal Storage]/Download/magisk_patched.img

Copy the patched boot image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:

adb pull /sdcard/Download/magisk_patched.img

Flash the patched boot image to your device and reboot. Here is the command if using fastboot on most devices:

fastboot flash boot /path/to/magisk_patched.img

After flashing my phone I am getting an error where phone claims that system is corrupt and I get Try Again or Reset to Factory Image

Any ideas?
[Magisk] mkdante381:
I tested this on ianmacd build with Google play services ticked and worked. Now after reinstalling again to ianmacd, this method not work. Tesco detect root also with magisk repackaging to random name.
[Magisk] labello29:
I did as you said and it does not work see photo
[Magisk] garylawwd:
Clear repo cache in manager settings and then refresh downloads
[Magisk] scottfreeze:
I'm having exactly the same problem on the Pixel 3 with June update.

https://xdaforums.com/showpost.php?p=79738839&postcount=34210

My best guess is that something changed in the June security update. I posted a logcat log in my post, hopefully someone here will help us sort it out!
[Magisk] labello29:
ok but every time you need to empty to view modules .. and any updates
[Magisk] Bi0haZarD:
Maybe there's something wrong with magisk installation. You can also try to dirty flash magisk and see if it resolves. If it doesn't, you can try to restore your boot partition and flash magisk. Hopefully it will be resolved, i had similar case like you a few builds before 19.3
[Magisk] wilsonhlacerda:
No, nothing related, nothing to do with his / her problem.

This is a known bug of Magisk Manager v7.3. It always have a failed download section. Refreshing REPO CACHE fix for one or two times. This is the only workaround now. Or downgrade Magisk Manager.
[Magisk] mctiew:
I have a problem with Magisk manager now which I don't know when it creeps in.

When I start Magisk Manager and enter the Superuser screen to view which are the apps were granted superuser, it gives me a blank screen.

But there are definitely apps granted superuser. How do I reconstruct back this info ?
[Magisk] Croppable:
Their Is An Issues Of The Latest Version Of The Manager.

It Just Not Detect On My Device. Saying it's not installed but is is? Is It Just Me Or Dose Anyone Have It
[Magisk] Wolfcity:
If you read the posts above this one it seems to be an issue with the new magisk manager 7.3 like the empty download list.
[Magisk] putridfoetus:
While you could do this, it would defeat the purpose of Magisk, which is to keep an unmodified system partition. CM's built-in root is a system modification. The only thing this would affect for CM is SafetyNet checks (Android Pay, some banking apps, a game which shall remain nameless). So if you want to use any of those things which require a clean system, you would need to completely remove CM's root, then flash the Magisk stuff.
[Magisk] thilak devraj:
can i try this on android nougat??
[Magisk] claytoncamilleri100:
I am trying to install this on my Moto G4 but I have no success. I am using Resurrection Remix ROM and can seem to get super su right. When I install Magisk and super su. In Magisk app I get Not Rooted or Improperly installed. I tried everything. I flashed stock boot image many times and the tried to install Magisk again. I tried flashing us-su and tried deleting su from /system/xbin and /system/bin. Still no Luck. It used to work on other roms. Is there something I am missing? How can I completely remove rom included root?
[Magisk] FabioSan:
Hey dev, I have tried Majsk on Android N Aosp (On oneplus x) but the phone stuck with black screen when finish boot. Isn't Majsk ready yet for N, I suppose?

Inviato dal mio X utilizzando Tapatalk
[Magisk] zatp:
I flashed it too successfully on CM14. SafetyNet passes and root works with phh's superuser, but the problem is that mobile data is not working for me. Did you have any problems with it?
[Magisk] JuergenZ66:
have you removed CM build-in root before installing magisk?
[Magisk] JudgeDread11:
Delete.
[Magisk] abuddlah:
How do you remove the build in root? Could you please give me some step by step instructions? please :(
[Magisk] JuergenZ66:
If you are using SuperSU from Chainfire you can use this app to remove root.

Afterwards boot into recovery and install magisk and SuperSU. reboot system.

Unfortunately, OP says root toggle does work with SuperSU only with phh.

But you can try and if toggle still does not work, redo the procedure but use phh root in recovery instead of SuperSU. after reboot you also have to install the phh app.

With phh root toggle works for me, I have no experience with SuperSU. sorry.

An alternative to remove root with SuperSU is unSU.zip which you have to install in recovery before magisk.

You can find it here: http://xdaforums.com/showpost.php?p=63615067
[Magisk] abuddlah:
Which app do you mean? I tried the phh root but when I download the app in playstore, it says the su binary is out of date but no method for me to update.

Are you using CM rom? If yes, can you have a step by step instruction on how did you managed to get it working?
[Magisk] JuergenZ66:
I had the same problem with CM13, ROM was successfully installed but toggle always switched back when unmounted.

I solved this problem by doing this:

1a. downloaded unSU.zip to SD card, direct download link: http://xdaforums.com/attachment.php?attachmentid=3528363&d=1446472307

1b. downloaded phhsuperuser.zip to SD card, direct download link from OP: http://xdaforums.com/attachment.php?attachmentid=3847928&stc=1&d=1471642336

2. reboot into recovery

3. flash unSU, this will remove root

4. flash magisk v6 from OP

5. flash phh superuser for magisk (from step 1b)

6. reboot system

7. install phh SU from play store, https://play.google.com/store/apps/details?id=me.phh.superuser

from then on my toogle didn't switch back
[Magisk] abuddlah:
I did the same just now. But after step 7, when I open the phh SU app, it is empty and when I tried to check if my root is still on (from root checker app, it shows that my root is not verified)

Is there something wrong with the phh SU app?
[Magisk] JuergenZ66:
try SuperSU from Chainfire to remove root and redo installing magisk and phh.zip, JudgeDread mentioned something that are some differences in removing root between unSU and SuperSU, see here http://xdaforums.com/showpost.php?p=68839591&postcount=3375
[Magisk] abuddlah:
do i run the magisk uninstaller first before everything else?
[Magisk] RandomPooka:
Yes. Yes, you can. You can try anything you darn well please. That isn't a guarantee that it will work, but you can try.

That said .. make full backups in TWRP first, just in case. Check EVERY box in the partition selection. I've found that my Nexus 6 lately will misbehave if I try to do a backup that doesn't also include the SystemImage along with the normal boot/system/data/efs backup in TWRP. Not sure if this is because I was switching back and forth between M and N builds, or what. But, it only took a few tries before I got sick of having to do a completely clean flash instead of being able to restore my backup.
[Magisk] Aldideos:
Hi, I installed i in my g4. in base rom, with root or magisk I can use timvision, an application like netflix. Afterinstalled magisk and phh's superuser I can't use this app... I disable successfully the root but hwever this app stop to work. I thiink it can still detect the root.How it is possible?
[Magisk] rajivshahi:
Can I flash magisk on locked bootloader phone (Sony z2). I have twrp and root access...
[Magisk] Tama-kun:
If the main post still applies, Sony devices in general do not work yet.
[Magisk] Turbopuschel:
That's not quite true. What's not working (at least for most Sony devices) is using the stock ROM and trying to install Magisk. I use the Xperia Z1 Compact, flashing Magisk on stock ROM causes it to not boot. But it works with the Resurrection Remix ROM (Marshmallow).
[Magisk] 3Shirts:
I have an Xperia Z5 and magisk is working fine on the latest stock rom.

I do have a problem with Android Pay though. I set it up fine, added my card and have used it successfully but now, even with root switched off and a successful pass of Safety Net test app, it fails when I try to use it.
[Magisk] kotuamoalt:
Try installing the system again.
[Magisk] wilsonhlacerda:
BUG with Magisk v19.3:

during boot Magisk HIDE does not work. It fails only while booting.

Anytime after booting if I switch Hide OFF and ON, then Hide works fine always afterwards. (I never loose hide; my bug is not related to that one of people loosing hide after some time).

Remarks:

Hide works fine on v19.2, v19.1, v18.x,.....first time I have this bug.

No matter if I boot Core Only or not, bug is always present.

Same happens on my girlfriend device (identical to mine) that has different and less modules, different set of apps, different and less hidden apps of mine.

Our devices: LOS14.1, Android 7.1.2, Samsung Galaxy S4 Active, Not encrypted, Magisk Manager v7.3 obfuscated (but also bug with v7.2)

Magisk Logs while booting and then while switching Hide are attached (I only replaced some apps names to "app" due to privacy).

Anyone can help? Report that to official Magisk bugs / issues? Thanks.
[Magisk] scottfreeze:
Great suggestion... that seems to have done the trick! For anyone else having this problem, after installing Magisk through TWRP, I rebooted to bootloader and simply flashed the system.img extracted from the Pixel 3 (blueline) factory image (command: fastboot flash system system.img). Booting to system then proceeded as normal, with Magisk successfully installed.

Thanks to kotuamoalt for the workaround! Hopefully the root cause will be identified and resolved at some point in a future release.
[Magisk] bhargavbuddy:
Oh so this seems to be problem of the manager then. I've been facing the blank superuser section on my app too. Downloads section was showing blank too but clearing repo cache fixed it.
[Magisk] Soumy1234:
I've just built a ROM for my Galaxy tab 3 10.1 with an x86 architecture and Magisk doesn't seem to be working out. I've tried versions 19.3, 19.1 and 18.1 if Magisk and 7.3.0, 7.2.0 and 7.1.2 of Magisk Manager, reinstalling Magisk, uninstalling then reinstalling, dirty flashing the ROM, wiping everything and starting over, but I still get the same result.

This ROM takes WAY too long to boot up, even slower than the first boot, with and without magisk. Like others mentioned the su list is empty. The su logs show that there are apps that request root, but they're not in the actual su list.

Magisk manager also takes sometime to open sometimes. Every now and then Magisk Manager says that Magisk isn't installed so I have to reboot and wipe dalvik and cache.

I haven't tested modules yet, though I did try the lineage add-on su zip and that works with my root apps.

Since I made the ROM, is there anyway I can make it work with Magisk and maybe even reduce the boot times?
[Magisk] kotuamoalt:
You can also re-flash the system using TWRP.

And I don't really think it is a workaround. Sometimes, you just have to re-install your system after installing Magisk for the first time. Just a part of the process.
[Magisk] JudgeDread11:
Sounds more like a problem with your ROM then with Magisk apart for the known manager bugs with su list and download list.

To solve the problems with your ROM tire on the wrong place and even in the right place more information will be needed.
[Magisk] Soumy1234:
I see. Do you know where I can begin to fix my ROM?
[Magisk] kotuamoalt:
Actually, I don't think you see at all. Not only are you not in the proper forum for your question, your question is so vague, no one could answer it anyway. But I'll go ahead and take a stab at it. What is wrong with your ROM, is that you do not know what you are doing and are asking even less qualified people to help you with a problem they don't even know anything about. I hope this helps.
[Magisk] aziz.yankee:
After flashing patched_boot.img file, do I need to flash with stock system.img? Is that what you are referring to? It will keep my files, right?
[Magisk] jcmm11:
As long as all you flash is the system image then yes, you'll keep all your files
[Magisk] ApeironTsuka:
Out of curiosity to everyone who is not missing Netflix from the Play Store... what version of Magisk, Android, and Netflix do you have?

For me, I'm on Android Pie July update, Magisk 19.3/Manager 7.2, and it's missing. However, the last update for it that I got was version 7.21.1 build 26 34268. It crashes immediately on start, or after a few seconds if the data is cleared (doesn't even show the Netflix logo) where as an older 6.26.1 build 15 31696 backup I have works fine. The last update to the Play Store for Netflix was June 14th. I pass Magisk SafetyNet checks and also show as certified in the Play Store. Mario Run also shows up fine, though I'm not sure if that one still goes missing for uncertified devices (I had unrelated Magisk issues that kept me having to boot with the stock boot image for a few days, and it was showing up even though Play Store said I was uncertified). Wondering if it going missing is due to crashing issues with some devices?
[Magisk] nebula9:
LG V30, crDroid (official), magisk 19.3 official, latest Netflix from play store works perfectly fine, 7.13.1build 23 34290. Also, Google pay works fine without the database chmod hack even though the database attests read 10. Worked out of the box. Don't know how to get this Working on any ROM on a Pixel, though.
[Magisk] Ch3vr0n:
Ain't working for me either as I said before on my pixel. Have to use the 6.21 build
[Magisk] Vision:
Latest Magisk Version

Hi I have Sony Xperia Z5 (E6653) Nougat 7.1.1.. I have magisk 17.1 and magisk manager 6.1.0 all good very good.. Now I see it have new version magisk 19.3 and magisk manager 7.3.0.. Work with my phone? Because some previous versions such 18 not working and I think update but not sure because 19.3 is stable but and Beta version and I'm little confused
[Magisk] jcmm11:
Poking around the Pixel 3a forums I ran across this: https://xdaforums.com/pixel-3a/how-to/root-3a-t3929053/post79740382

That's, apparently, a core-only kernel, which should allow you to fix your issue
[Magisk] firstblud:
Had the same problem today.. Same goes for BlackBerry access. Tried all the above and canary build to no avail.
[Magisk] Fentadroid:
Yes, I sent him that file, thanks to [MENTION=4702761]ApeironTsuka[/MENTION] who compiled it :)

Instructions here:

https://xdaforums.com/pixel-3a/how-to/root-3a-t3929053
[Magisk] Soumy1234:
Dang. To be honest, I was kind of hoping there would be someone here that knew of a patch or something to make Magisk more stable or something, but you're right, this isn't the best place to ask. Sorry to bother you all.
[Magisk] aziz.yankee:
I've reflashed with System.IMG on my Pixel 3 - that did not help :( Any ideas?