Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.
i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too
rf9992003 said:
i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too
Click to expand...
Click to collapse
Exactly this, bank apps can't detect the new zygisk, at least for now, just hide magisk app, delete TWRP folder and use SNF zygisk module and the black list
hi
MisiekDP said:
Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.
Click to expand...
Click to collapse
Hello, were you able to solve this?
maycomathias93 said:
hi
Hello, were you able to solve this?
Click to expand...
Click to collapse
No. You have this same problem (phone not turning on)?
yes, the only solution in this case is to run uninstall magisk and install again without lsposed. For now use edxposed without safetynet (sorry for my google translate english)
Man, I solved this problem, going from Android 9 (custom ROM where I had the problem) to 10 (also custom ROM). I hope it helps you, greetings.
Related
pretty much title.
sometimes i lose root twice a day, sometime 3day without lose, reboot/reflash magisk fix it
Same here
Enviado de meu LG-D295 usando Tapatalk
Just experienced the same issue. After installing some modules and rebooting
I am experiencing the same thing.. but when or how I don't know... I just take reboot and again root will be back. Might be some other app like clean master or auto killing apps kills magisk services???
I had the issue too, but it stopped when I disabled MagiskHide. That of course is only a solution if you don't actually need it.
Not being an expert, I never found a way to debug the issue or contribute otherwise.
I can confirme. Also when MagiskHide is on, I experience random reboots, which is bigger problem. Any fix for it?
Karls0 said:
I can confirme. Also when MagiskHide is on, I experience random reboots, which is bigger problem. Any fix for it?
Click to expand...
Click to collapse
Just a thought: have you added any system apps/processes to the Hide list?
No, i didn't. I don't use android pay, and i don't think that hiding root may be necessary for any other system app. When I turn MagishHide I have maybe 1 min before reboot. All was fine first few hours after installation, before first root losing.
If it will help, I'm on AOSP 6.0 custom ROM. My device is i9505. What's interesting it happens only if mobile data is on. Wi-fi doesn't do any troubles.
I will throw my experience into this thread as well. I am running Magisk 11.1 with DarkRom on my Nexus 5. Everything seems to work very smooth outside of randomly loosing root. I don't have to reflash, just reboot and it comes back. I do have MagiskHide enable for Android Pay. I also have the AppSystemizer model installed to covert Action Launcher 3 to systems. No random reboots, but loosing root is annoying. I may try to disable MagiskHide and see if that solves the root drop issue. Android Pay is handy though.
Ok Folks my 2 cents in regards to this trouble, i have did some work in reproducing this Magisk Root Loss.
say i have few apps like 1) SafetyNet Sample: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en & 2) RootChekerPro app and both these apps are hided them from root using MagiskHide.
So when i launch Magisk Manager app and checked safetynet Status and then opened app1 (safetynet Sample) ran the test and then immediately did Forcestop the Magisk manager app and launched back Magisk Manager app boom the root is lost and did a reboot everything is back fine again.
I've been trying to find the cause of this issue for a couple of weeks. This is what works for me so far
1. Open Magisk Manager when root is working (either immediately after rebooting or after disabling Magisk Hide).
2. Does Magisk BusyBox and Magisk Hide.
3. Reboot
4. Enable Magisk Hide, but keep Magisk BusyBox disabled.
5. Reboot
Check if root disappears anymore.
I think Magisk Hide is causing the issue, disabled the Magisk Hide and the root stays.
It may also be releated with GApps package - it could explain why some people have this issue with losing root/stability but others no. You can try with smaller package (picko/nano).
Magisk 11.5 seems to fix the issue for me
craigacgomez said:
Magisk 11.5 seems to fix the issue for me
Click to expand...
Click to collapse
No, it's just randomly occurring.
I was having the same problem with 11.1 and flashed the 11.5. It doesn't fixed.
Then flashed the ROM and 11.1 again the root is still there.
I don't know what exactly triggers the root to hide but there is something going on.
works on first flash of 11.1, then the next reboot breaks it again. uninstalling and reinstalling magisk fixes it again until the next reboot
I switch on MagiskHide only when I need it. So far it's quite good option, doesn't require any reboots.
did more testing, I don't lose root at all when I have MagiskHide disabled. Deleting /magisk/.core/magiskhide in recovery returns root.
Mostly a "me too" post. Issue still occurs on 11.6.
I tried replacing MagiskSU with SuperSU. But still the issue remains.
Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Adios2nd said:
Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Click to expand...
Click to collapse
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Can confirm that this works, thanks.
For me, it started getting detected on 17.x even before updating to 18, right after the banking app (Sparkasse) was updated.
LG G6.
hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This didn't work for me. I had to downgrade back to 17.1 to get my banking app working again. Appears that the root detection prevention is a regression in this latest version.
-- SSS
hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Click to expand...
Click to collapse
This doesn't work for me.
Did all of these...still got detected.
I have the same problem. Magisk says: ctsProfile: False and Google Pay don't work. Also my Banking App detects root.
I flashed today the latest Los 15 build and the crt false error is till there after flashing magisk 18. The same error is also with 17.4...
Tell me if I'm wrong but I believe we have two different reports: the original report where root is detected, and the ctsProfile/basicIntegrity failing. The second one is a regression fixed by rebooting device (however, it is annoying to reboot 10 times a day because suddenly SafetyNet fails for no reason).
I am using Magisk Hide Props module, and after 18.0 update Santander App detects root, even with Magisk Manager says I pass safetynet
It's happened with my bank app as it detected root & saftynet false and have to downgrade to ver.17.2
Sent from my SM-C900F using Tapatalk
See in install app delete old magisk manager, after install magisk 18.0 new magisk manager rename to manager.
I have same problem. After install v18 magisk, same bank app can detect the system is rooted. Downgrade to v17.2, all bank app become normal.
Same here since Magisk 18 my BankApp (Intesa Sanpaolo) start and says that there is a safety problem and it close, if I choose Magiskhide it doesn't start at all.
SafetyNet check spin without an end.
With Magisk 17.1 and 17.3 no problem at all.
Same problem here, after upgrading to Magisk 18 claiming to better hide root in the history, apps now suddenly detect root.
This affects also the Safety Net check and Google Pay... so far, Root Hiding in 18.0 seems COMPLETELY broken.
A solution would be great.
Later... after downgrading to Magisk 17.2, MagiskHide is working for me again and Safetynet checks succeed. The dev is aware of the problem, an issue is open on the Magisk Github (#907)
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
I can confirm the v18 update breaks something and BOTH safety net checks fail. So all apps detect you are rooted, especially bank apps and Get Pay. Downgrading back to v17 restored everything to normal.
The only thing I could think of is the installation method. I did the direct install rather than installing the zip via recovery. Not sure if it makes a difference but I will wait for next release.
I am on a Pixel 2 with Android Pie updated to the Aug 2018 release.
---------- Post added at 12:47 PM ---------- Previous post was at 12:43 PM ----------
Harlock1978 said:
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
Click to expand...
Click to collapse
I did not uninstall but tried clearing bank app data and cache and the problem persisted. Magisk still showing all red for safetyNet. Just sharing testing feedback.
@Djtrip83 Did you try just toggling MagiskHide off and on once after updating to v18? Sometimes MagiskHide simply needs a restart after an update...
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Djtrip83 said:
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Click to expand...
Click to collapse
We might be misunderstanding each other, but what I'm talking about is simply to go to the Manager settings and change the toggle for MagiskHide to off and then on. No need to do anything to the Hide list or anything else... Did you do that? As I said, that's sometimes something you the to do after an update, but it's rare.
I'm running, on a Huawei Mate 10 PRO, an official Huawei ROM BLA-L29 8.0.0.157 (C432) with no custom kernel or script installed via TWRP. I only have Magisk 18 running with a couple of modules such as Android Pie Fonts, Busybox, DNSCrypt-Proxy 2, Pixel Experience, Youtube Vanced. Root works perfectly on the device with many applications. Now I'm struggling with two things that don't work at all:
- SafetyNet check: it takes many minutes to complete and at the end I get an "Invalid answer"
- Magisk Hide: as soon as I register an application in Magisk Hide I can no longer launch it. Clicking on the icon doesn't do anything.
FYI: On Magisk I have the "Keep forced encryption" set and "Keep AVB 2.0/dm-verity" unchecked. I tried with "Keep AVB 2.0/dm-verity" set and re-installed Magisk but problem is still there.
I looked at Magisk's log but can't see any outstanding issue or error message.
Can someone help me to solve this issue since some banking applications are now blocking me? Thanks a lot.
PS: I tried to use an alternativel fingerprint via the MagiskHide Props Config module but that didn't help.
SafetyNet with Magisk 18.0
alphazo said:
- SafetyNet check: it takes many minutes to complete and at the end I get an "Invalid answer"
- Magisk Hide: as soon as I register an application in Magisk Hide I can no longer launch it. Clicking on the icon doesn't do anything.
Click to expand...
Click to collapse
Hi alphazo,
I had the same problem with my Huawei Mate 10 Pro since I went from 17.3 to 18.0.
I tried several solutions like you, but nothing worked. The only thing that worked was to downgrade to version 17.3, there, everything was functional.
For my part, I completely uninstalled Magisk from my phone and then reinstalled it. After that, everything works perfectly and I have no problems with SafetyNet.
You just have to reconfigure the Magisk Manager application and choose which applications you want to hide.
I hope it will work for you too ! :good:
Thanks a lot for your pointers. I finally got it working and thus even with Magisk 18
It was a combination of many factors.
Here is what I did first:
Fully uninstalled Magisk 18
Installed Magisk 17..3
Selected applications lilke a simple Safetynet checket app under Magisk Hide
Started the Safetynet checker app and it worked.
Then I started to re-install my Magisk modules including Pix3lify (former Pixel Experience module) for an alternate launcher and found out that this was causing the issue.
I uninstalled this module and then decided to upgrade to Magisk 18. Magisk Hide didn't work at first since a simple Safetynet checker app wouldn't pass.
I had to go back to Magisk Hide panel and unselect all the apps that were previously registered before selecting them again and this time it worked.
Thanks again for your pointers and I hope the above will help other people.
PhilippeSX4 said:
Hi alphazo,
I had the same problem with my Huawei Mate 10 Pro since I went from 17.3 to 18.0.
I tried several solutions like you, but nothing worked. The only thing that worked was to downgrade to version 17.3, there, everything was functional.
For my part, I completely uninstalled Magisk from my phone and then reinstalled it. After that, everything works perfectly and I have no problems with SafetyNet.
You just have to reconfigure the Magisk Manager application and choose which applications you want to hide.
I hope it will work for you too ! :good:
Click to expand...
Click to collapse
Details: Huawei P20 Pro running 9.0. Magisk Manager v7 (latest), Magisk v18.2 (latest canary) original package name. Safety net passed.
I tested to make sure that magisk hide is working properly on my device. https://play.google.com/store/apps/details?id=com.revolut.revolut&hl=en_GB. This app does not have fingerprint login enabled without magisk hide. Hence when I turn off magisk hide, you can't use fingerprint to login into the app. When I turn it back on, fingerprint login works. Also my bank app works.
Here is the problem. https://play.google.com/store/apps/details?id=com.starlingbank.android&hl=en_GB. This app does not seem to run even when magisk hide is on. Here's the kicker, even though magiskhide has been toggled and confirmed working, upon opening this app it will show the usual "device not secure/rooted" message. After this it somehow disable magiskhide as my revolut app no longer prompts for fingerprint and my bank app stops working.
I have to go back into magisk and retoggle magisk hide for it to work again. (However the starling bank app still fails the root check)
I'm really really frustrated now and will appreciate any help.
UDPATE: I did some stuff from https://forum.xda-developers.com/apps/magisk/how-to-bypass-lloyds-root-detection-t3837206, the adaway host list. Added MagiskHide Props Config. I also set tasker to toggle magiskhide whenever I turn on my screen. Seems to work more consistently for now
Check the Magisk main thread and Github, there is a known problem with Magisk Hide in the 18.x. I went back to 17.x which work for me without any problems.
lambstone said:
Details: Huawei P20 Pro running 9.0. Magisk Manager v7 (latest), Magisk v18.2 (latest canary) original package name. Safety net passed.
I have to go back into magisk and retoggle magisk hide for it to work again. (However the starling bank app still fails the root check)
I'm really really frustrated now and will appreciate any help.
Click to expand...
Click to collapse
If Magisk Hide Of Magisk 18.x Is Working Intermittently (Which Means Also The Device Will Not Pass The SafetyNet Sometimes), Try To Use The Module Of Microsoft Intune Company Portal Hider Which Includes Also The Functionality Of Re-Enabling Magisk Hide Every 5 Min. For Magisk 18.x From This Thread https://forum.xda-developers.com/apps/magisk/module-microsoft-intune-company-portal-t3780451. Awaiting Your Feedback.
Dreamer(3MF) said:
The Functionality Of Re-Enabling Magisk Hide Every 5 Min
Click to expand...
Click to collapse
Doesn't this cause battery drain?
akxak said:
Check the Magisk main thread and Github, there is a known problem with Magisk Hide in the 18.x. I went back to 17.x which work for me without any problems.
Click to expand...
Click to collapse
Hi, some questions. Do I have to install also the Manager v6.10 to install Magisk v17.3? Or can I leave the last Manager? Then, I uninstall Magisk from the app and them I flash the v17.3 from (temporary) TWRP, is it correct?
Simone_ASR said:
Hi, some questions. Do I have to install also the Manager v6.10 to install Magisk v17.3? Or can I leave the last Manager? Then, I uninstall Magisk from the app and them I flash the v17.3 from (temporary) TWRP, is it correct?
Click to expand...
Click to collapse
The latest Magisk Manager dropped support for Magisk 17 or older, you need the matching Manager..
akxak said:
The latest Magisk Manager dropped support for Magisk 17 or older, you need the matching Manager..
Click to expand...
Click to collapse
Thank you so much for your fast reply!
In the exact same situation as OP P20 Pro (maybe except im on LOS 16)
Magisk seems to be working fine passing safteynet and Root Beet finding nothing but yet the Starling Bank app and the Arriva Ticket app both figure out my phone is rooted after a while and lock out.
Had exact problem with Starling app with magisk hide and app on hide list. Turned out to be a direct build.prop modification so after resetprop -p all good now.
gkornaks said:
Had exact problem with Starling app with magisk hide and app on hide list. Turned out to be a direct build.prop modification so after resetprop -p all good now.
Click to expand...
Click to collapse
Can you expand on this a bit?
I've downloaded Magiskhide props config, and what do I have to do now?
For me, starling always works for couple of days and then it locks me out via the root screen.
republicj said:
Can you expand on this a bit?
I've downloaded Magiskhide props config, and what do I have to do now?
For me, starling always works for couple of days and then it locks me out via the root screen.
Click to expand...
Click to collapse
I modified a build.prop directly before magisk install so compromised the system partition. I've used resetprop to mask it. Like you I'm occasionally getting root warning as well and have to re-authorise so magisk hide in 18.1 not perfect as mentioned a lot in a forum.
Hi,
it seams that the problem is still there. I have to retoggle Magisk Hide at every reboot of the phone.
Is there any workaround or any ETA on the fix?
Thank you.
No one?
Never ask for ETAs...
https://github.com/topjohnwu/Magisk/issues/1654
Didgeridoohan said:
Never ask for ETAs...
https://github.com/topjohnwu/Magisk/issues/1654
Click to expand...
Click to collapse
Ok, I'm sorry about that , I just needed a confirmation that the problem was still there. Thank you for the reply!
Yes it's till here. I cannot login to Arriva bus app with Magisk 20.1.
Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
JayTheKid said:
Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
Click to expand...
Click to collapse
The reason I'm having this issue is because Snapchat randomly signed me out today and my restore point in titanium backup was too old
I had it too. Sign out clear data and cache and forced stop
Go hide in Magisk.
Reboot.
Clear data and storage again m
Open MM & turn off Magisk Hide.
Wait a few seconds.
Toggle Magisk Hide back on.
Force stop and clear Snapchat again.
Now before rebooting go ahead give it the permissions you want it to have.
Theory: don't give it the "phone" permission at first it at all if you can help it.
Reboot
Let everything finish loading and settling in, wait a couple minutes then try again.
If it's still messed up, is the account locked on their end until you call?
Let me know.
JayTheKid said:
Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
Click to expand...
Click to collapse
vonDubenshire said:
I had it too. Sign out clear data and cache and forced stop
Go hide in Magisk.
Reboot.
Clear data and storage again m
Open MM & turn off Magisk Hide.
Wait a few seconds.
Toggle Magisk Hide back on.
Force stop and clear Snapchat again.
Now before rebooting go ahead give it the permissions you want it to have.
Theory: don't give it the "phone" permission at first it at all if you can help it.
Reboot
Let everything finish loading and settling in, wait a couple minutes then try again.
If it's still messed up, is the account locked on their end until you call?
Let me know.
Click to expand...
Click to collapse
I turned off xposed in magisk and the installer, retoggled magisk hide for Snapchat and rebooted. Account was locked, what triggers this? I was using snap with Xposed undetected for months and then it randomly acts up. You mentioned not giving it phone permission, is that how they catch you? The only other thing I could think of that caught me was my cable app (spectrum TV) makes me disable usb debugging to use it
JayTheKid said:
I turned off xposed in magisk and the installer, retoggled magisk hide for Snapchat and rebooted. Account was locked, what triggers this? I was using snap with Xposed undetected for months and then it randomly acts up. You mentioned not giving it phone permission, is that how they catch you? The only other thing I could think of that caught me was my cable app (spectrum TV) makes me disable usb debugging to use it
Click to expand...
Click to collapse
The phone permissions allows the app to see the phone's IMEI code. I think maybe that detected you are on a rooted phone using that information.
How to use Snapchat with magisk (After Ban)
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ultimate Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX
No such item in xbin
I tried that too but i dont find any item such as busybox my Snapchat account can't be locked because its has been open in different phones
So give a solution what should i do i uninstall edxposed tried everything root switch root clock hut none of them really works its say oh on your temporarily login fails please try again later help needed seriously its been days
Running
Magisk 20.4 stable
Ed xposed 0.4.5.6 justins forks snadhook
Android 10