Database Develop

[Guide] Pass Safetynet on a rooted 7.0 AOSP based ROM - Updated 11-01-2016

Update (11/09) - This method no longer works with the november security updates from Google as it causes suhide to break.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
2) Let the system reboot normally.
3) Reboot to recovery
4) If you have Magisk installed, flash the Magisk uninstaller Link
5) If you have suhide installed, flash rm-suhide 0.51 Link
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install suhide 0.55 Link
Reboot into system. Verify that you have root. I'm not 100% sure this is necessary, but I like to do it before proceeding.
Reboot back into recovery.
Flash xsetpropSu.zip (attached to this post) Link
Reboot the system
Install RootSwitch 1.3.3.2 Link
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Optional
Using tasker to automatically disable root when certain applications are run. @NYZack made a little writeup here
Credits:
@NYZack - Helping me figure out how to put all of this together
@Captain_Throwback - For help with xsetprop
@Chainfire - SuperSU + SuHide
@topjohnwu - Magisk

work around found

no longer relevant post..

I don't know if the kernel can be modified to pull that trick. Even if someone does though, it's not going to last long. Every bypass you can find, Google can find. Then they know what to fix. The only way to win, is not to play.
And no, you can't lock the bootloader without wiping data.

Well I got it to work...I will turn this thread into a Guide. Who knows how long it will last, but...at least it's working for now.

Thread updated with instructions. I hope this can help someone!

So there's no way to do this without rooting and magisk?

3dawg said:
So there's no way to do this without rooting and magisk?
Click to expand...
Click to collapse
I want root, so I did not try to do that. If your bootloader is unlocked, I do not think there's a way to do it.

Thanks
skaforey said:
Thread updated with instructions. I hope this can help someone!
Click to expand...
Click to collapse
Yes I just followed these instructions and I am green panel. I have to check at a terminal to pay with phone but it probably will work. One note that was kinda unclear in case others do same....It should read :
Turn the Root switch ON....not OFF....when wanting to use AP. You can turn it back on when you want to do other things that require root permissions. I believe this is dynamic and working with the magisk mount point in addition to tricking the boot process into thinking the bootloader is locked.
Thanks so much for this. I was so angry with Google. And I was just going to say FK it and not use AP.
WORKS! Do all the steps in the order he says above and you can turn root off and on at will and have Android Pay work just fine! YAY!

skaforey said:
This thread started as a plea for help, but thanks to @NYZack I have gotten it to work.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) If you have suhide installed, download rm-suhide 0.51 Link
2) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
3) Let the system reboot normally.
4) Reboot to recovery
5) Flash rm-suhide 0.51
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install Magisk v8.zip Link
Install suhide 0.55 Link
Reboot into system
Install Magisk Manger 2.1 (apk) Link
Open up Magisk Manager app and go to modules. Click on the + button. Add the following zip for xsetprop Link
Install RootSwitch 1.3.1.2 Link
Reboot system
Using Root Explorer (or some other file manager capable of root access), browse to /magisk/xsetprop and modify post-fs-data.sh . Add the following line to the end of the file, save and exit
Code:
xsetprop ro.boot.flash.locked 1
Reboot system
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Click to expand...
Click to collapse
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.

Captain_Throwback said:
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.
Click to expand...
Click to collapse
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.

No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!

Pkt_Lnt said:
http://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
Click to expand...
Click to collapse
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can't get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??

jcrompton said:
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??
Click to expand...
Click to collapse
Yea I know I think it's something to do with either the kernel I've selected or perhaps suhide no longer works...I'm not sure what the deal is. I'm running Franco #55 and even without root, I get failure but inside the testing app ...see attached

Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.

MrBrady said:
Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.
Click to expand...
Click to collapse
I'm using stock Rom and only custom kernel so this should work on Nbd90z....I'd think. Last test was dreaded message but I'm trying to add few things to suhide blacklist. We shall see

I get the green screen. But then when I tap at store nfc terminal...it claims error....I'm going to try hiding nfc service, and what I think is play services based on uid chainfire explained. I'll try a small purchase and remember to screen capture the error if occurs

skaforey said:
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.
Click to expand...
Click to collapse
I built the mod for people that were already using Magisk. If you're not using Magisk, then of course you can try just putting the binary in /su/xbin and put the post-fs-data.sh in /su/su.d and see if that works for setting the props at boot time.
I don't use Xposed, so using Magisk + phh's Superuser was my target for the module. I also did try the su.d method with SuperSU, but it wasn't working on my device. I also didn't want to have to use RootSwitch. But feel free to unpack the zip and try whatever combinations you want.

photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command

skaforey said:
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command
Click to expand...
Click to collapse
I'm using it for android pay not pogo. And I did. I'm sure the prop is right or wouldn't get green go. It's an error from AP saying something about unable to verify and might be rooted....or words to that effect

Magisk v12 loses root after a short while.

I noticed today that I lost root. I searched and tried everything to fix it but I couldn't. So, I wiped out my entire phone and did a clean flash of Resurrection Remix 5.8.3 for the TMobile Note 3. Magisk worked after a clean flash.
Spent hours loading every app back on and now, Magisk isn't working again?
Please help?
Android version is 7.1.2.

Did it really lose root? I've found that randomly when you open Magisk it will claim that it has no root access, but when you close it (exit the app and swipe it away from the recents menu) and reopen it it will start functioning properly again.

Neo3D said:
I noticed today that I lost root. I searched and tried everything to fix it but I couldn't. So, I wiped out my entire phone and did a clean flash of Resurrection Remix 5.8.3 for the TMobile Note 3. Magisk worked after a clean flash.
Spent hours loading every app back on and now, Magisk isn't working again?
Please help?
Android version is 7.1.2.
Click to expand...
Click to collapse
Use un su zip first to remove the pre-installed root that rr has. Don't know if RR has root inbuilt now or not. But if it comes with root uninstall it and flash magisk on top of it and you are good to go

Me too have this problem. Magisk root sometimes gone, and i need to reboot device to make it work agan.
Tested in almost N custom roms like CM14.1, AEX, Omni, ViperOS, etc

exodius48 said:
Me too have this problem. Magisk root sometimes gone, and i need to reboot device to make it work agan.
Tested in almost N custom roms like CM14.1, AEX, Omni, ViperOS, etc
Click to expand...
Click to collapse
Did u remove built in root

shantam3108 said:
Did u remove built in root
Click to expand...
Click to collapse
If you installed magisk it will remove built in root automatically. -_-

Did you turn off magisk busybox ? It would help on fix that.
In another way, some of modules you installed may have potential to make you lose root. Trying to do enable/disable module to test it.

I did some more searching and someone said just flash Magisk again. I did that and it worked! But, then I lost root again several hours later, seems so random? I flashed Magisk again and it worked again.
I can only get two green on Magisk, the third green seems to run forever, I left it on for 10+ minutes and it still showed "testing".
BTW, I didn't flash the uninstall Magisk zip before re-flashing. I tried that way and my phone got into a bootloop. Luckily, I had a TWRP backup.

Kris Chen said:
Did you turn off magisk busybox ? It would help on fix that.
In another way, some of modules you installed may have potential to make you lose root. Trying to do enable/disable module to test it.
Click to expand...
Click to collapse
Thanks! I'll try this and see if it helps!

BTW, is anyone able to install Snapchat? I tried the Hide feature in Magisk and checked Snapchat, but it still knows I'm rooted and immediately closes after opening.
Also, the Sphero BB8 app? Anyone get that working? That one also closes right after opening.

exodius48 said:
If you installed magisk it will remove built in root automatically. -_-
Click to expand...
Click to collapse
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
---------- Post added at 01:21 AM ---------- Previous post was at 01:20 AM ----------
Neo3D said:
Thanks! I'll try this and see if it helps!
Click to expand...
Click to collapse
Also keep in mind do run magisk without any modules first to check

shantam3108 said:
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
Click to expand...
Click to collapse
Then why on AEX still loose root? It has no root prebuilt

exodius48 said:
If you installed magisk it will remove built in root automatically. -_-
Click to expand...
Click to collapse
shantam3108 said:
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
Click to expand...
Click to collapse
I just want to clarify.
If systemless SuperSU is detected, Magisk will use that. If any other root is installed, the installation script will attempt to remove it and install MagiskSU instead (not sure to be successful and might lead to issues). If no root is installed, MagiskSU will be used. To avoid issues, the unSU zip is quite useful.
From v13, Magisk will no longer be compatible with SuperSU.

Didgeridoohan said:
I just want to clarify.
If systemless SuperSU is detected, Magisk will use that. If any other root is installed, the installation script will attempt to remove it and install MagiskSU instead (not sure to be successful and might lead to issues). If no root is installed, MagiskSU will be used. To avoid issues, the unSU zip is quite useful.
From v13, Magisk will no longer be compatible with SuperSU.
Click to expand...
Click to collapse
Wow, this is very informative, thanks!
Which version of unSU.zip is the correct one to use? Is this one okay?
https://forum.xda-developers.com/showpost.php?p=63615067

Neo3D said:
Wow, this is very informative, thanks!
Which version of unSU.zip is the correct one to use? Is this one okay?
https://forum.xda-developers.com/showpost.php?p=63615067
Click to expand...
Click to collapse
That's the one to use. :good:

Neo3D said:
BTW, is anyone able to install Snapchat? I tried the Hide feature in Magisk and checked Snapchat, but it still knows I'm rooted and immediately closes after opening.
Also, the Sphero BB8 app? Anyone get that working? That one also closes right after opening.
Click to expand...
Click to collapse
It is because your device lost safety net.
You need to reflash system and gapps.
Back up data partition then wipe all then flash rom and gaps and then magisk.
After starting device first enable magisk hide.
Then restore backed up /data.
After restart enable magisk hide switches and reboot system.
Profit.
Reply it works or not.

[email protected] said:
It is because your device lost safety net.
You need to reflash system and gapps.
Back up data partition then wipe all then flash rom and gaps and then magisk.
After starting device first enable magisk hide.
Then restore backed up /data.
After restart enable magisk hide switches and reboot system.
Profit.
Reply it works or not.
Click to expand...
Click to collapse
I just flashed magisk again and safety passed!

Neo3D said:
I just flashed magisk again and safety passed!
Click to expand...
Click to collapse
Tell me how much time you have safety net pass?

[email protected] said:
Tell me how much time you have safety net pass?
Click to expand...
Click to collapse
Hi, what do you mean "how much time you have safety net pass?

Neo3D said:
Hi, what do you mean "how much time you have safety net pass?
Click to expand...
Click to collapse
This time after reinstalling magisk is it working till now?
Or root is gone after some time?

Issue with magisk after using triangle away!

So i flashed magisk on my phone 2 weeks ago and everything seemed fine and awesome but then for some reason i decided to use triangle away to reset my flash counter. After doing that i couldn't pass the safetynet test. I tried uninstalling magisk, flashing stock boot and finally flashed magisk zip file but still couldnt pass the safetynet test.
Extra info: i have a Samsung Note 4 N910H 6.0 marshmallow.
Read that disabling usb debugging mode might help but no luck.
Applied other fixes as well
Any help will be appreciated

Not one can help?

majd_90 said:
Not one can help?
Click to expand...
Click to collapse
No answer usually means just that...
When asking for help it's a good idea to include some kind of log. Upload a Magisk log (as an attachment). Maybe it'll show something (but don't hold your breath).

Didgeridoohan said:
No answer usually means just that...
When asking for help it's a good idea to include some kind of log. Upload a Magisk log (as an attachment). Maybe it'll show something (but don't hold your breath).
Click to expand...
Click to collapse
Was hoping for some kind of solution or idea to fix it ! I'll try finding the log and uploading it but i doubt it'll show any issues cause everything installed normally without an error or something

majd_90 said:
Was hoping for some kind of solution or idea to fix it ! I'll try finding the log and uploading it but i doubt it'll show any issues cause everything installed normally without an error or something
Click to expand...
Click to collapse
Install from Google Play the app called "RootBeer Sample", hide it from Magisk Hide, run it and upload a screenshot and upload the Magisk log.

AFAIK Note 4 doesn't have the original flash counter; it uses Knox and you can't revert that. The last device with a flash counter was S3/mini.

Deic said:
Install from Google Play the app called "RootBeer Sample", hide it from Magisk Hide, run it and upload a screenshot and upload the Magisk log.
Click to expand...
Click to collapse
Here you go ! I attached the screenshot and log ! Alot of Xs on the screenshot but it is rooted

Dexxxta said:
AFAIK Note 4 doesn't have the original flash counter; it uses Knox and you can't revert that. The last device with a flash counter was S3/mini.
Click to expand...
Click to collapse
Wish i knew that ! The flash counter (which triangle away indicated) was 21 , when i reset the counter it turned into 1

majd_90 said:
Here you go ! I attached the screenshot and log ! Alot of Xs on the screenshot but it is rooted
Click to expand...
Click to collapse
Okay, first you didn't hide RootBeer and second SafetyNet was update weeks ago. You need try Universal SafetyNet Fix module, I recommend the beta one

Deic said:
Okay, first you didn't hide RootBeer and second SafetyNet was update weeks ago. You need try Universal SafetyNet Fix module, I recommend the beta one
Click to expand...
Click to collapse
Ah ya i forgot ! I'll do it again if you want , And where can i get that module? From magisk manager?

Deic said:
Okay, first you didn't hide RootBeer and second SafetyNet was update weeks ago. You need try Universal SafetyNet Fix module, I recommend the beta one
Click to expand...
Click to collapse
Much better

Deic said:
Okay, first you didn't hide RootBeer and second SafetyNet was update weeks ago. You need try Universal SafetyNet Fix module, I recommend the beta one
Click to expand...
Click to collapse
Ok so i found it on xda , downloaded the beta one and added it to the modules in magisk manager , and then rebooted. Still not passing the safetynet test

majd_90 said:
Ah ya i forgot ! I'll do it again if you want , And where can i get that module? From magisk manager?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=72844209&postcount=633
@majd_90 Did you install F-Droid Privileged module like the posts say?

Deic said:
https://forum.xda-developers.com/showpost.php?p=72844209&postcount=633
@majd_90 Did you install F-Droid Privileged module like the posts say?
Click to expand...
Click to collapse
Yes i followed what the post mentioned

...

majd_90 said:
Yes i followed what the post mentioned
Click to expand...
Click to collapse
Did you have Xposed and can share post-fs-data.log in /magisk/xiaomi-safetynet-fix folder?

Deic said:
Did you have Xposed and can share post-fs-data.log in /magisk/xiaomi-safetynet-fix folder?
Click to expand...
Click to collapse
No never had Xposed on this phone before !

majd_90 said:
No never had Xposed on this phone before !
Click to expand...
Click to collapse
Can't execute /system/bin/sh... Do you can try this in terminal and post the result?
Code:
ls -la /system/bin/sh

Deic said:
Can't execute /system/bin/sh... Do you can try this in terminal and post the result?
Code:
ls -la /system/bin/sh
Click to expand...
Click to collapse
Here u go

Ok so safetynet just passed ! I went to the thread which had the universal safetynet fix module and looked around , i saw a link to another thread which had a lot of suggestions that might work ! So finally i enabled magisk core only mode in the settings, disabled systemless hosts and rebooted..
And vola it passed. Gonna keep monitoring it, i am afriad it might be luck it worked this time. Thanks everyone for your assistance

Losing Magisk Root After Reboot

Hi,
I'm running stock ROM with TWRP recovery.
I've managed to successfully root my Note with Magisk.
Somehow I noticed that my device loses root after a reboot and sometimes even randomly. When I go into the custom recovery and flash Magisk 14 or 14.3 everything works fine for while, till it loses root again.
Could someone shed some light on my issue, please?
Thanks in advance.
I've also themed Magisk Manager with Substratum could that be the issue?

I'm also running stock rom, losing magisk root from time to time.
When root is lost, I'm getting a notification that "new magisk V14 is available.
Reinstalling with TWRP only to lose it again a day or two later.

You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:

Are you using the hide root feature?
If so then that is probably your issue.

opasha said:
You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:
Click to expand...
Click to collapse
This worked for me, thank you!!

ALEXRUSS55 said:
This worked for me, thank you!!
Click to expand...
Click to collapse
Welcome :highfive:

jpasint said:
Are you using the hide root feature?
If so then that is probably your issue.
Click to expand...
Click to collapse
What issue does this cause?

I have the same issue with last magisk beta, 16.4.. have anyone found a fix?

stiffis said:
I have the same issue with last magisk beta, 16.4.. have anyone found a fix?
Click to expand...
Click to collapse
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root

kenpaci said:
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root
Click to expand...
Click to collapse
Looks like that worked, thanks!

stiffis said:
Looks like that worked, thanks!
Click to expand...
Click to collapse
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru

webgurru said:
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru
Click to expand...
Click to collapse
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)

stiffis said:
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)
Click to expand...
Click to collapse
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?

hshah said:
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?
Click to expand...
Click to collapse
Try closing those apps first, I think it goes ok as long you don't start the apps yourself because most off the apps checks root at startup, but I can't guarantee you anything

Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs

hshah said:
Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs
Click to expand...
Click to collapse
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru

webgurru said:
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru
Click to expand...
Click to collapse
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible

hshah said:
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible
Click to expand...
Click to collapse
Any luck or help from this thread to resolve?

webgurru said:
Any luck or help from this thread to resolve?
Click to expand...
Click to collapse
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.

hshah said:
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.
Click to expand...
Click to collapse
Thanks. In my point of view this look to be a bug in Magisk. Did you tried some older version?

Modules not working, can't return to old version, wipe needed on Galaxy S8 / Nougat

Hi,
I was running stock ROM with stock recovery plus Magisk v16 and MagiskManager v5.9.1 on my Galaxy S8 and Nougat. As far as I remember I did install MagiskManager using adb, pushed, patched and pulled the boot.img, flashed it using Heimdall. Both apk and patched_boot.img are available on my hard disk...
I then updated MagiskManager using the in app update. Afterwards I used the "direct install" to update Magisk. That took me to 20.4 / 8.0.2. I don't remember if it asked to install the runtime.
I installed modules busybox, sqlite3 and movecertificates, but with no effect (e.g. there is no /system/bin/sqlite3, no nc in my path, user certs remain user certs). I also can't find any indication in MagiskManager that modules are installed.
I didn't have time to figure out what's wrong and tried to revert back to my old versions.
That's what I did: Full uninstall from MagiskManager 8.0.2. Reboot without Magisk, adb push MagiskManager-v5.9.1.apk. Flash my old patched_boot with Magisk v16 using Heimdall. But unfortunately that gives me Magisk Manager stuck on the splash sceen. No applet can get root access, e.g. su on adb shell blocks (needs ctrl+c). Ok, uninstalled MM.
I installed the stock boot img in the intention to load MM 8.0.2 before I flash M 20.4. That didn't accept my pattern for the "your device is encrypted" screen. Well... I flashed M 20.4 patched boot.img again. After first try it shows an integrity issue and offers to wipe the phone.
* Anyway to go from here besides wipe?
* What residuals might be blocking when returning to the old versions?
* Why are modules not working on current version?
Thank you

urbancubb said:
* Why are modules not working on current version?
Click to expand...
Click to collapse
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
* What residuals might be blocking when returning to the old versions?
Click to expand...
Click to collapse
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
* Anyway to go from here besides wipe?
Click to expand...
Click to collapse
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.

Didgeridoohan said:
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
Click to expand...
Click to collapse
I installed them from within Magisk Manager from the online repo.
I noticed that this might be the case, but as there was updates this year I think on at least two of them and none worked, I think its a general problem and not caused by the module itself. Any module I could use to test wich works for sure?
Didgeridoohan said:
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
Click to expand...
Click to collapse
Which didn't work... We'll see.
Didgeridoohan said:
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Click to expand...
Click to collapse
Good hint, I started a new thread.
Thank you!

For the modules issue, the only way to know for sure what happened is to look at the install logs and the Magisk log for the following reboot.
So if you get things up and running again, and the issue still persists, make sure to provide those.

One thing I didn't think of before: I recently tried the SafatyNet check (which failed), maybe the failed reboot was the first one after checking, I don't remember exactly.