Related
I've read myself to exhaustion trying to understand how this all works with no luck. With articles on the web having no or vague instruction and authors using the terms Magisk and Magisk Manager interchangeably (this one is the worst) I'm totally confused. Additionally there is too much assumed knowledge in the instructions I find. Go do this, go install this with no links, no explanation of what I'm installing, how to install it, where the instruction and files live, how to use it or the actual effect upon install.
Here is my current state and my questions (please excuse the caps, they just express my frustration):
Pixel 4a
Android 11
Rooted with Magisk
Can't use banking apps
MagiskHide doesn't fix the problem
I read that using MagiskHide Props Config can fix my SafetyNet issues but the instructions are very extensive and I want to be sure of what I'm doing before I tackle it.
Does Magisk also live inside Magisk Manger? Do I need both?
Do I need Magisk Manager to load modules?
Hiding root and passing Safety Net:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Why do these instructions tell me to "Make sure that the app in question is selected in the Hide list (Under MagiskHide in the Magisk app)." and there IS NO HIDE LIST! under MagiskHide in the Magisk app?!
OR
"Most Magisk modules can be hidden by MagiskHide, but that depends on exactly what the module does. If you can't figure out what is triggering an app, try disabling all modules." THERE IS NO PLACE TO SELECT OR DISABLE MODULES IN MAGISK!
I am very, very technical and can can follow well written instructions but this android (and linux) stuff is new to me. I just want my Pixel 4a to have root and be able to use my Golden1 credit union software. I apologize for the drama but this task is becoming almost insurmountable.
Thank you very much for any opinion or insight!
Arsenal420 said:
I've read myself to exhaustion trying to understand how this all works with no luck. With articles on the web having no or vague instruction and authors using the terms Magisk and Magisk Manager interchangeably (this one is the worst) I'm totally confused.
Click to expand...
Click to collapse
Totally agree with you: all is based on slopiness of the authors.
Magisk is a software framework- it provides additional low level routines / replaces in parts Android's default system software - what hooks Android's boot and system files, thus you can extend Android's default system features by adding 3rd-party modules.
Magisk Manager is a pure Android app for managing Magisk.
jwoegerbauer said:
Totally agree with you: all is based on slopiness of the authors.
Magisk is a software framework- it provides additional low level routines / replaces in parts Android's default system software - what hooks Android's boot and system files, thus you can extend Android's default system features by adding 3rd-party modules.
Magisk Manager is a pure Android app for managing Magisk.
Click to expand...
Click to collapse
Thank you very, very much. So do you need to have Magisk installed for Magisk Manager to work? If it's like maybe .Net framework then the answer would be "yes" but since I don't know this platform perhaps Magisk is "embedded" in Magisk Manger and you only need it to do all your work. Thanks again jwoegerbauer you filled in a major blank.
Magisk Manager is companion Android application for Magisk framework so it should be obvious that Magisk framework must be installed before.
I know what you mean. I just started trying to install an news magic today instead of lucky passer and I can't even get it installed and authorized because of the tar and the different things that wants to have me do. There's no instruction it's just supposed to be knowledge you're supposed to have. I think I'm just gonna delete it go back lucky.
What version of Magisk and what root hide (module name and version please) people have it fully working for Feb 2022 firmware update (840.2201.226), especially for Google Pay? Thanks
(I'd it all working on the previous firmware release just fine. Then right after applying the above mentioned Feb update, when I tried to execute Magisk (possibly 23.1) to patch the inactive slot, it just wouldn't execute let alone patch; nor would Termux "su" command would execute. So there was no way to patch Magisk over that update. Problem was made worse, when I executed LSPosed, which proceeded to update and auto rebooted the phone! Jumped from the frying pan into the fire.)
nexusnerdgeek said:
What version of Magisk and what root hide (module name and version please) people have it fully working for Feb 2022 firmware update (840.2201.226), especially for Google Pay? Thanks
(I'd it all working on the previous firmware release just fine. Then right after applying the above mentioned Feb update, when I tried to execute Magisk (possibly 23.1) to patch the inactive slot, it just wouldn't execute let alone patch; nor would Termux "su" command would execute. So there was no way to patch Magisk over that update. Problem was made worse, when I executed LSPosed, which proceeded to update and auto rebooted the phone! Jumped from the frying pan into the fire.)
Click to expand...
Click to collapse
Using Latest Magisk and Zygisk-Shamiko.
MagiskHide is no longer available - and Denylist is not effective.
For the patch - First Patch the Boot Image, then Install Magisk again over TWRP as well.
Thanks, I got Magisk 24.2 installed & working fine now.
(Things are super difficult as it is, so I've skipped trying to install/activate TWRP.)
However, Universal SafetyNet Fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases), though installs fine, gets disabled due to "Module suspended because Zygisk is not enabled".
I've confirmed that Zygisk (Beta) is activated in Magisk's settings. What am I missing?
Q: How to "unsuspend" Universal SafetyNet Fix module?
Thanks
(It's so difficult to keep up with all this work that I'm leaning towards relocking the boot-loader. I really don't use any app or feature to benefit from unlocked boot loader or root. I did it only to be ready for injecting mbn, which isn't needed or possible anyway. It was a bad decision then & remains so now. Though I don't know if while relocking the bootloader the phone will get bricked. Decision.. decision... With all the difficulty of keeping up with root, it sounds like a risk worth taking.)
Actually removing the Magisk APK and reinstalling it seemed to have helped. Termux works reliably for su. Gpay is good as well. Magisk log shows no funky messages.
In the end, I had to use this to overcome root detection on two banking apps: https://github.com/vvb2060/magisk_files/blob/alpha/app-release.apk
nexusnerdgeek said:
In the end, I had to use this to overcome root detection on two banking apps: https://github.com/vvb2060/magisk_files/blob/alpha/app-release.apk
Click to expand...
Click to collapse
What's that ?
Leads to a empty GitHub Page ...
Actually official Magisk 24.3 works well for all of the banking apps I need root hide for. So, there's no need for that unofficial alpha build anymore for me; in fact, I got rid of it. Please disregard that link.
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
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!
So a year ago i rooted my OnePlus 8t and i still have oos 13 anyway I'm trying to bypass postfinance root check but anything seems to work (zygisk block , shamiko , securitynet tried) on yasnac it runs the check perfectly and i tried to cancel the cache and the memory many times but anything...
There are any other options or i must deroot the phone?
NewNoSignal said:
So a year ago i rooted my OnePlus 8t and i still have oos 13 anyway I'm trying to bypass postfinance root check but anything seems to work (zygisk block , shamiko , securitynet tried) on yasnac it runs the check perfectly and i tried to cancel the cache and the memory many times but anything...
There are any other options or i must deroot the phone?
Click to expand...
Click to collapse
So I know nothing of OnePlus (I've only experience in Samsung & Pixels), so I don't know if any of the following suggestions work on your phone.....
First of all, safetynet is becoming depreciated and will become completely depreciated by '24; what many apps now use for "safety" detection is Play Integrity API -- in which using the Play Integrity API Checker app or more comprehensive root checker TB Checker is a better way to see how your device passes established safety checks more than YASNAC and passing them (or certain checks) may be required to get your app running with root.
Among Zygisk DenyList and Shamiko as viable root hiding methods, there is also
Magisk Delta [Magisk fork] (which returns Magisk Hide),
UniversalSafetyNetFix [Magisk module] (if main branch isn't successful, Displax's fork often times is more successful),
HideMyApplist (HMA) [LSPosed module],
Bootloader Spoofer [Xposed module] (to spoof locked bootloader) {this method is new}.
Also, hopefully you are employing Shamiko correctly where you configure the Zygisk DenyList but do not enable/Enforce it -- if that interferes, apparently there is a "whitelist" mode for Shamiko.
P.S. Also, I hope you've also made sure to Hide Magisk (essentially renaming the app manager name) in settings -- you never mentioned doing this in the OP...
I've read these other methods have fairly good success particularly on banking apps where Zygisk DenyList and Shamiko don't...
sometimes you have to try/work them in different combinations with each other to get it passed....
Again, I do not know if any of these work with your device, so I suggest going through their respective threads (if they have one in your device's subforum, that would be best) to see if/how they work with your device and/or you could post & inquire if/how they do/might....
simplepinoi177 said:
So I know nothing of OnePlus (I've only experience in Samsung & Pixels), so I don't know if any of the following suggestions work on your phone.....
First of all, safetynet is becoming depreciated and will become completely depreciated by '24; what many apps now use for "safety" detection is Play Integrity API -- in which using the Play Integrity API Checker app or more comprehensive root checker TB Checker is a better way to see how your device passes established safety checks more than YASNAC and passing them (or certain checks) may be required to get your app running with root.
Among Zygisk DenyList and Shamiko as viable root hiding methods, there is also
Magisk Delta [Magisk fork] (which returns Magisk Hide),
UniversalSafetyNetFix [Magisk module] (if main branch isn't successful, Displax's fork often times is more successful),
HideMyApplist (HMA) [LSPosed module],
Bootloader Spoofer [Xposed module] (to spoof locked bootloader) {this method is new}.
Also, hopefully you are employing Shamiko correctly where you configure the Zygisk DenyList but do not enable/Enforce it -- if that interferes, apparently there is a "whitelist" mode for Shamiko.
P.S. Also, I hope you've also made sure to Hide Magisk (essentially renaming the app manager name) in settings -- you never mentioned doing this in the OP...
I've read these other methods have fairly good success particularly on banking apps where Zygisk DenyList and Shamiko don't...
sometimes you have to try/work them in different combinations with each other to get it passed....
Again, I do not know if any of these work with your device, so I suggest going through their respective threads (if they have one in your device's subforum, that would be best) to see if/how they work with your device and/or you could post & inquire if/how they do/might....
Click to expand...
Click to collapse
Ah yes i renamed it too now I'm going home and try all you just wrote i hope it works
Thanks for the help anyway
I don't install any of those apps.
Couldn't you simply login to the banking site using your browser?
blackhawk said:
I don't install any of those apps.
Couldn't you simply login to the banking site using your browser?
Click to expand...
Click to collapse
well in nnot that easy i have to scan a qr code from the app to somehow activate my account? i dont'know for sure i don't know german too well XD anyway is not that easy
NewNoSignal said:
well in nnot that easy i have to scan a qr code from the app to somehow activate my account? i dont'know for sure i don't know german too well XD anyway is not that easy
Click to expand...
Click to collapse
I just use passwords, the KISS principle.
I use a secure browser like Brave.
No issues in over 7 years. Login takes seconds.
simplepinoi177 said:
So I know nothing of OnePlus (I've only experience in Samsung & Pixels), so I don't know if any of the following suggestions work on your phone.....
First of all, safetynet is becoming depreciated and will become completely depreciated by '24; what many apps now use for "safety" detection is Play Integrity API -- in which using the Play Integrity API Checker app or more comprehensive root checker TB Checker is a better way to see how your device passes established safety checks more than YASNAC and passing them (or certain checks) may be required to get your app running with root.
Among Zygisk DenyList and Shamiko as viable root hiding methods, there is also
Magisk Delta [Magisk fork] (which returns Magisk Hide),
UniversalSafetyNetFix [Magisk module] (if main branch isn't successful, Displax's fork often times is more successful),
HideMyApplist (HMA) [LSPosed module],
Bootloader Spoofer [Xposed module] (to spoof locked bootloader) {this method is new}.
Also, hopefully you are employing Shamiko correctly where you configure the Zygisk DenyList but do not enable/Enforce it -- if that interferes, apparently there is a "whitelist" mode for Shamiko.
P.S. Also, I hope you've also made sure to Hide Magisk (essentially renaming the app manager name) in settings -- you never mentioned doing this in the OP...
I've read these other methods have fairly good success particularly on banking apps where Zygisk DenyList and Shamiko don't...
sometimes you have to try/work them in different combinations with each other to get it passed....
Again, I do not know if any of these work with your device, so I suggest going through their respective threads (if they have one in your device's subforum, that would be best) to see if/how they work with your device and/or you could post & inquire if/how they do/might....
Click to expand...
Click to collapse
I MADE IT was suficient to swap magisk and install universalsafetynetfix (i installed directly the displax's one)
thank you very very much
NewNoSignal said:
I MADE IT was suficient to swap magisk and install universalsafetynetfix (i installed directly the displax's one)
thank you very very much
Click to expand...
Click to collapse
GREAT!
Glad I helped you get there! I know how much of a relief it is to not need to unroot and/or relock the bootloader and have the phone be wiped (at least that's how it is on Samsung & Pixels)
Nice to know that USNF and Magisk Delta (I assume that's what you meant with "swap magisk") work well enough on OnePlus...