It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.
koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.
Click to expand...
Click to collapse
Can you uninstall Magisk and install the stable or last working canary app?
simplepinoi177 said:
Can you uninstall Magisk and install the stable or last working canary app?
Click to expand...
Click to collapse
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).
koberulz said:
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).
Click to expand...
Click to collapse
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...
simplepinoi177 said:
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...
Click to expand...
Click to collapse
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.
koberulz said:
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.
Click to expand...
Click to collapse
Uninstalling the Magisk Manager app would not affect root; you might not be able to run certain rooted apps properly without granting them root access, but that's because of not having the Magisk app to grant it.
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings") so it's not detected by any root detection. In any case, you should be able to find it in the Apps list in Settings/Apps, and uninstall it that way.
As to what to install over the top of it, installing the latest stable 25.2 would be the best idea -- the Magisk App does not need to match the version that is patched and flashed to your boot partition...
simplepinoi177 said:
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
Click to expand...
Click to collapse
My understanding was that he got hired and they said he had to give it up, there was some negotiation and they let him continue working on it as long as Magisk Hide was removed as a feature.
But this isn't something that really interests me all that much, so I don't keep up with the news on it. I more just check in whenever I get a new phone in order to figure out how to root it.
simplepinoi177 said:
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings")
Click to expand...
Click to collapse
Yes, this is what I was referring to.
koberulz said:
Yes, this is what I was referring to.
Click to expand...
Click to collapse
koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
Click to expand...
Click to collapse
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?
simplepinoi177 said:
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?
Click to expand...
Click to collapse
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.
koberulz said:
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.
Click to expand...
Click to collapse
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.
simplepinoi177 said:
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.
Click to expand...
Click to collapse
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.
koberulz said:
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.
Click to expand...
Click to collapse
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
What's the difference?
koberulz said:
What's the difference?
Click to expand...
Click to collapse
dcarvil said:
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Click to expand...
Click to collapse
The first one is the first, general Magisk thread (that is still active and currently discussed). The second is as it is stated in the headline -- "This is a discussion and help thread for the newer versions of Magisk".
Most likely this is where you should go for your issues -- and to see how actively developed it is currently being.
It's just as you said, you've been away from rooting/Magisk for a while; the newer version of Magisk contains/employs Zygisk -- "Zygisk is new generation Magisk hide...Zygisk is what the Magisk developers call running Magisk in the Zygote Process of Android. The Zygote Process is the first process that the OS starts when it boots up, ... Since zygote starts first after system, it can hide root without sending data to apps." (source) As such, that's why a new thread was created and why it is sub-titled as "The Age of Zygisk"...
*but there are many more methods of hiding root than Zygisk (or in conjunction with); Shamiko, Magisk Delta, HideMyApp, etc.
In the end, I'm sure they'll suggest what I've suggested to you in some fashion -- you'll have to uninstall the Magisk Manager (hidden or not), and re-install the stable or earlier canary versions. But it'll be better coming from the people in that thread...
Good luck!
Related
I've been rooting my Android phones since about 2012, but today I got a point of sale card reader for my business and I'm not having any luck hiding root from the app (square reader app). The app wont work at all so I tried a number of options in magisk manager (magisk hide the app, hide magisk manager, enable core mode only) rebooting between each try and clearing the square reader app data and setting it up fresh each time, but still no luck
I tried to uninstall magisk but the app still didn't work. So I eventually flashed back to stock and got rid of magisk all together, now the app works but I don't have root...
I tried installing magisk again after I got the app to work and hiding root from the app before I opened it up again, but it still somehow knew the device was rooted
Can anyone suggest anything I haven't tried? Or is there an alternative to rooting the OnePlus 6 (other than magisk) and hiding root? I had a bit of a look around but didn't find anything.
Thanks
I had to go back to 18.0, heard 18.2 works as well.
qbanlinxx said:
I had to go back to 18.0, heard 18.2 works as well.
Click to expand...
Click to collapse
Thanks for your reply. I tried with 18.0, damn, it still doesn't work, it still picks up that the phone is rooted
I tried the 18.2 canary build as well (18.2-e72c6685) no luck either
This app must be looking somewhere out of the ordinary for evidence of root in the phone
I have a bank application and facing the same problem. Hope someone can help us to make applications run by hiding the root
I think recent applications are looking for if knox security is tripped !! so in this case Magisk will not help
Ooohhh had to subscribe to this as I face the exact same issue!! Been trying to get my Square reader to work for a while with root and could never figure out how they are detecting root. Using Pixel XL here
Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.
Skreelink said:
Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.
Click to expand...
Click to collapse
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.
Idledev said:
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.
Click to expand...
Click to collapse
I agree, I have no problem hiding magisk and root from other apps, the square reader app must be somehow different. I've even gone through my storage and deleted any files or folders that might suggest the phone is rooted, but still no luck...
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
I've found a temporary workaround to my problem anyway, I realized that I can share my internet (wifi hotspot) with my ipod touch, this way square reader works as the ipod touch isn't jailbroken or modified. It just means I have to carry around my ipod touch with me, which is a better trade off for me than having a stock, non root phone
Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try
Idledev said:
Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try
Click to expand...
Click to collapse
That's awesome! What canary build did you use?
I tried the latest build a few weeks ago and it didn't work for me
Build 18120
Idledev said:
Build 18120
Click to expand...
Click to collapse
No luck for me...
I updated to the latest canary build, cleared all data from square reader app, selected magisk hide, rebooted the device. After it booted up I tried to run it and it still detected root. I have a feeling that the OnePlus OS does something that doesn't totally allow me to hide root from the square reader app. It's annoying because for other apps root can be hidden
Maybe there's something in the Android Q build that lets you hide root better
Something that seems reliable right now on 18.1, Pixel Experience and OOS :
Combine Magisk Hide with Magisk "Core Mode". This seems to do the trick for now, Google Pay is triggered with normal mode, but works in Core Mode. Same for Snapchat and banking apps like N26.
But within this, you can't use any module.
kage00 said:
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
Click to expand...
Click to collapse
This is always a good idea, on OOS at least, Magisk being optimized sometimes prevents the granting of root rights to apps, it never reacts to kernel applications requesting root on startup for example.
There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616
DaveW1972 said:
There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616
Click to expand...
Click to collapse
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes
kage00 said:
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes
Click to expand...
Click to collapse
Ummm yeah.. then the problem doesn't lie within Google pay it lies within the modifications that you are using.
I have to say I have never had any issues with Google pay or Android pay or any banking app using magisk. I don't even have to hide anyting. Of course I'm also not using any modified ROMs or kernels either
Hi guys,
I have this issue for a couple years now and I just cannot find a solution!
Google Pay, and 4 banking app from two different countries work fine with my 1+6 (stock ROM OOS 9.0.9 with magisk 19.4 - 7.3.4) but Square does not.
Did anyone find a solution?
Magisk config:
Magisk hide
Two modules OOS phone record and youtube
No core mode
All banking app and Square hidden
I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Ahh... Me too. I'm sure this somewhere in the extensive Magisk coverage here. Is it too lazy to ask for a pointer to how to
--- downgrade the manager? That's probably easy if I know where to get the apk. Which version should I go for?
--- install the new magisk over the existing version, preferably without wiping the phone?
Sure, I'll search. But it is quite a while since I did anything with magisk, or anything that involved flashing, and I feel a bit lost.
Thad E Ginathom said:
Sure, I'll search. ... ... ...
Click to expand...
Click to collapse
OK, so there's a wiki and stuff. Whilst being babied would be nice, people have better things to do, and I guess I'll just start in reading that wiki and... stuff.
SOLUTION
Deathnes said:
I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Click to expand...
Click to collapse
Delete the Magisk Manager app as you would do with any other, download the proper version in .apk (check the official thread) and install it.
In the thread, under Sources, you have the link to the GitHub repo. Scrolling down you will find the README.MD file and the link to the Downloads page where all past releases are available.
From https://www.xda-developers.com/how-to-install-magisk/ you can read:
The Magisk framework is now installed on your device. To manage it, you’ll need the aptly named Magisk Manager. This is what will allow you to install modules. Download the latest Magisk Manager APK here and make sure you have “Unknown sources” enabled in the Settings. Install the app and open it up.
The Manager app allows you to adjust root settings and also install modules, which are installable mods. The app doubles as a repository for a bunch of great modules that can easily extend the functionality of your device. Using the Manager app is an important part of getting the most out of this root method.
Click to expand...
Click to collapse
That is, the app Magisk Manager is independent from the Magisk framework you have installed. Deleting the app does not affect Magisk.
vomae said:
... ... ... the Downloads page where all past releases are available.
Click to expand...
Click to collapse
I'd reached there, although not done it yet. As you say, my phone is still working, Magisk is still working, it is just the manager app that needs dealing with. None the less, I appreciate your time and effort. You paint a clear picture for others who come this way.
Thanks.
Open the updated app & ignore the error, then checkout the option showing update magisk(not manager), go for it, dont select any preservations & click on direct install(which is recommended by app itself).
Flashing of the update will begin, then after reboot your problem is solved.
Magisk Manager has many improvements and features over the last year...
I have been reading GitHub about SafetyPatch and it says to flash from magisk. Magisk 20.1 does not have a flash option. What were they taking about? My safety check is failing and SafetyPatch is supposed to fix that. I have Magisk hide on yet I read that if you turn it on and off that fixes the safety check but I have no on off button in magisk for hide. I click hide and I get a list of apps with a check mark. So, does the check mark mean hidden or not hidden. Don't know how to check that. I don't know if Magisk has incorporated SafetyPatch in Magisk 20.1. Using bootleggers Pie on OnePlus One.
On another question. How hard is it for a developer to pick up an abandoned app, like from 2015, and write it for Android 8 +. I don't want to use Google sync or cloud sync. There are old apps out there that did Phone to PC sync just fine so why not keep them updated. CheetahSync was one. Can some one explain what happened? I Google CheetahSync and no published reason for dropping app.
Hello, I have moved your thread questions and answers belong in the q/a section. Thanks!
All,
I've been fighting with this for a while and I swear that I'm doing everything right (at least, I think I am).
Here's what I'm running:
1. euro build
2. magisk 23.0 (canary build)
I go through the setup, oem unlock and reboot again. I always run into a problem with magisk patched img and safety net failing.
The threads out there have gotten too thick and off-topic with folks asking for other stuff unrelated to the task at hand. I'm beyond confused with all the threads and need a clean and cohesive approach. Again, people, I need a better direction on this. No one-liners and smart ass answers.
Thank you to those that respond with a solid tutorial. Go layman if need be. =)
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
I recommend following this YouTube tutorial step by step. Also, The Magisk 23.0 build STILL has MagiskHide at the moment, so you may want to enable that.
TL;DR, you'll have to install Riru, LSposed, and XPrivacyLua and their respective magisk modules. While the video showed how to pass SafetyNet and get Google Play "Device is Certified", you can implement the same processes to ANY app having issues with root.
dude6595 said:
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
Click to expand...
Click to collapse
Once again: Everything that counts is money!
There will be other devs presenting solutions for root and hiding root so that we won't need Magisk any longer.
Until then I'll stay with 23.0
I have zero interest in rooting my phone, but because 5G/VoLTE/VoWiFi are not supported in my country (Slovakia) I had to root it. After successful root, passing SafetyNet and pretty much make everything to work as expected, my Company Portal is detecting root when running Teams and Outlook provisioned by my Company Portal despite having them in DenyList. Is there anyone who managed to pass this?
Thank you.
Happened to me as well. I used Shamiko magisk module and it's all good now.
@chaos193, did you use Riru along?
Or maybe even better question if you don't mind - what modules are you using to successfully pass SafetyNet and hide root?
Can you list them one by one, please?
Either use Shamiko or MagiskHidePropsConf to mask additional properties. I can confirm that InTune Company Portal works fine with SafetyNetFix + Shamiko
p4ra said:
@chaos193, did you use Riru along?
Or maybe even better question if you don't mind - what modules are you using to successfully pass SafetyNet and hide root?
Can you list them one by one, please?
Click to expand...
Click to collapse
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
chaos193 said:
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
Click to expand...
Click to collapse
Quick question @chaos193 - I haven't updated Shamiko to 0.6 as the update states that it requires Magisk 25205+. Reckon that would be magisk canary? Or as you using 0.6 with Magisk stable?
WhoIsJohnGalt1979 said:
Quick question @chaos193 - I haven't updated Shamiko to 0.6 as the update states that it requires Magisk 25205+. Reckon that would be magisk canary? Or as you using 0.6 with Magisk stable?
Click to expand...
Click to collapse
I used it with magisk stable 25.2. I think we are all using magisk stable to root our phone right?
I have tried your suggestions, but still does not seem to work. Adding screenshots.
Can you help me, please? What is wrong with my setup?
Following steps work 100% - I had the same issue.
1. Use magisk canary.
2. Install universal safetynet fix MOD 2.0 from displax (Google for "displax github")
3. Use latest shamiko module
4. Activate zygisk
5. Don't enforce denylist
6. Go to denylist and chose all Microsoft apps and tick ALL options for each app.
7. Hide magisk app
I had issue with a specific banking app which detects root by most of the methods. I made it working by using shamiko + airfrozen which i was not really liking.
Now i wnded up with a forked project of magisk bu Husky called magisk delta which brought back magisk hide along with zygisk. With this i don't need shamiko, magiskpropshide, airfrozen or any modules for hiding the root from apps. Yes for safetynet you can use the modded veraion by D. Below is the link. If you are interested have a look at Magisk Delta by HuskyDG... I use the magisk delta canary builds...
I have made it work with first approach. I did a restart of the phone and it worked.
What I am wondering though is the following - I have used the VoLTE/VoWiFi/5G Magisk module, but I don't see the "HD" icon during the call, even though I can browse the internet (when I am not on WiFi). And despite 5G coverage of my current carrier in my area, I don't see 5G icon.
Is there any other module I am missing for this last piece of puzzle?
And last but not least. What scares me the most is that next OTA will completely screw me over after setting everything up. I wish there was a clear tutorial on how to OTA and keep the root without wiping everything out.
p4ra said:
I have made it work with first approach. I did a restart of the phone and it worked.
What I am wondering though is the following - I have used the VoLTE/VoWiFi/5G Magisk module, but I don't see the "HD" icon during the call, even though I can browse the internet (when I am not on WiFi). And despite 5G coverage of my current carrier in my area, I don't see 5G icon.
Is there any other module I am missing for this last piece of puzzle?
And last but not least. What scares me the most is that next OTA will completely screw me over after setting everything up. I wish there was a clear tutorial on how to OTA and keep the root without wiping everything out.
Click to expand...
Click to collapse
I'm not quite sure which VoLTE/VoWiFi/5G Magisk module you are referring to, but I believe enabling 5G requires modified mbn files specific to your country/region.
Regarding OTAs, there are two "How To" guides here with all the details you need.
Blaze1001 said:
Following steps work 100% - I had the same issue.
1. Use magisk canary.
2. Install universal safetynet fix MOD 2.0 from displax (Google for "displax github")
3. Use latest shamiko module
4. Activate zygisk
5. Don't enforce denylist
6. Go to denylist and chose all Microsoft apps and tick ALL options for each app.
7. Hide magisk app
Click to expand...
Click to collapse
I have done exactly this but it still detects
Oneplus 7 pro
LineageOS 19.1 Nov 27th nightly build
This should be all that's needed to pass the compliance checks for Intune
1. Magisk (Zygisk mode)
2. SafetyNet v2.3.1-MOD_2.0
3. Shamiko v0.5.1 (or higher)
4. Magisk deny-list for the following apps (without Enforce deny-list)
a. Company Portal (Intune)b. Microsoft Authenticator (if you use it)c. Microsoft Defender (if you use it)5. Make sure you clear app data for the apps in the deny list after adding them to the deny list
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
craigacgomez said:
This should be all that's needed to pass the compliance checks for Intune
1. Magisk (Zygisk mode)
2. SafetyNet v2.3.1-MOD_2.0
3. Shamiko v0.5.1 (or higher)
4. Magisk deny-list for the following apps (without Enforce deny-list)
a. Company Portal (Intune)b. Microsoft Authenticator (if you use it)c. Microsoft Defender (if you use it)5. Make sure you clear app data for the apps in the deny list after adding them to the deny list
Click to expand...
Click to collapse
s3axel said:
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
Click to expand...
Click to collapse
Still doesn't work. Its weird because it worked for one night and the next morning it stopped.
UPDATE: its LSPosed I think. But this is the only way to force dark mode on some apps....
UPDATE 2: I disabled forced dark mode on all Microsoft apps in LSPosed plugin and its looking good so far...
UPDATE 3: Had a full day with not a single root detection notification. Looks solid!
s3axel said:
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
Click to expand...
Click to collapse
one of the worse parts of it, if not the worst, is that nobody knows what it detects and there's no guide that applies to each and every device,
I tried in 3 devices, the exact same steps and files, etc, it worked on the 1st one, but on the other two.. no!
For all those who still got issues as another idea: Does Google Wallet work ? Is the device play protect certified ?
I ask because to get Wallet to work (and presumably other apps that rely on Safetynet and/or Play Protect certification) the additional step after #5 in the list above is: clear data for Google Play Services and Google Play Store, then reboot (your device will ask for Google backup configuration again).....
I got the same issue with an App called "SwissID". It recognizes magisk for some reason. All other Apps work (like banking, google wallet etc.)
chaos193 said:
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
Click to expand...
Click to collapse
Its work to me!!! Thanks