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

[ROOT] [Magisk] [Galaxy S6] - Magisk-root uninstalls automatically?

Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
(I don't want to install a Custom ROM!)
Thank you
Larry

larrythil said:
Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
Thank you
Larry
Click to expand...
Click to collapse
I had the same problem with my Nexus 6P.
I was on stock ROM and stock kernel and it happened twice.
Now I'm on stock ROM and EX Kernel and problems seemed go away.
Inviato dal mio Nexus 6P utilizzando Tapatalk

CyberZeus1977 said:
I had the same problem with my Nexus 6P.
I was on stock ROM and stock kernel and it happened twice.
Now I'm on stock ROM and EX Kernel and problems seemed go away.
Inviato dal mio Nexus 6P utilizzando Tapatalk
Click to expand...
Click to collapse
Tell me somthing about "stock kernel" and "EX Kernel" what is that and how can i install that? or change that?

I have the same problem, galaxy S6.

I noticed losing root randomly and fixed it by going install patch boot img then you flash the boot img in recovery. So far it's been a day no root loss
Lineage 14.1 for lg stylo 2 plus

Hi ! I have sale problem with my S8+ with custom rom and Custom kernel

Hello.
I am having the same issue with my S6. I have tried all of the advice from previous threads with regard to different versions of Magisk.. (Removing Busy Box / Not using the Magisk Hide feature... etc etc..). I have also been through as many extra options as I can think of, getting all of the "Update" patches from the other developers who have helped with the Magisk project.
Each time, I have run through all of the aditional scripts to make sure SU and Magisk have been completely removed prior, and then used Odin to do a recovery back to my Original ROM (a complete system backup image I previously saved).
The other interesting observation i have at the moment is that i can not get to the Log cat files to post them anywhere. I can see where they are supposed to be but the directory is empty "no files". I have even been as far as downloading one of the many "Mobile Forensic" software kits to try and see if there is anything wrong with my phone.
There is only one observation to report. It seems that after installing Magisk (even if you just install the main ROM and not the manager). Google play starts to download straight away... I am not sure what it is downloading as it doesn't ever seem to complete and all of my versions of the apps are up to date.
I hope I will be able to get some more usefull information for you soon (LogCat etc etc.). If any one has an answer or suggested options it would be good. I am particularly interested in getting the Busy Box feature to work with Root as I am working on an app for my job that needs both options (I work offshore and am trying to adapt a piece of Seismic QC software (unix based) to run on phones / tab's - Android).
I will sign up properly and start to follow the threads more closely.
Cheers... Andy
-Samsung S6 - Full Magisk Module (with recommended zeroflte TWRP).

AndyQVT said:
Hello.
I am having the same issue with my S6. I have tried all of the advice from previous threads with regard to different versions of Magisk.. (Removing Busy Box / Not using the Magisk Hide feature... etc etc..). I have also been through as many extra options as I can think of, getting all of the "Update" patches from the other developers who have helped with the Magisk project.
Each time, I have run through all of the aditional scripts to make sure SU and Magisk have been completely removed prior, and then used Odin to do a recovery back to my Original ROM (a complete system backup image I previously saved).
The other interesting observation i have at the moment is that i can not get to the Log cat files to post them anywhere. I can see where they are supposed to be but the directory is empty "no files". I have even been as far as downloading one of the many "Mobile Forensic" software kits to try and see if there is anything wrong with my phone.
There is only one observation to report. It seems that after installing Magisk (even if you just install the main ROM and not the manager). Google play starts to download straight away... I am not sure what it is downloading as it doesn't ever seem to complete and all of my versions of the apps are up to date.
Click to expand...
Click to collapse
So long story short, there's no definitive solution to the problem. Im using a g920p with a custom kernel built by a genius dev, and i still lose root once a day.
Basically what it comes down to is modules. If you have zero modules, you'll have better luck... But that's not the point of magisk, so you need to be picky with modules. Use osmosis's busybox from the magisk repo, but other than that, install modules 1 at a time and see if it affects root.
Another tip: uninstall all updates of the "device maintenance" app, and find it in Google play and turn off automatic updates. Then go to device maintenance > battery > unmonitored apps and magisk manager to the list of unmonitored apps... Then go back the battery screen, battery usage > 3 dots in top right > optimize battery usage, and make sure magisk manager is not optimized... That should help some. (Note: some models don't have device maintenance, but you'll still have the "optimize battery usage" option some where.)
The Google play thing you're seeing is likely "instant apps" updating. I believe that should be unrelated to all this, but some aspects of instant apps is a mystery.
As for the logcat thing, i believe you're getting logcat confused with the magisk_debug.log located in /data ? If that's the case, you need to be using the beta version of magisk. Go to magisk and set the update channel to beta, you'll get a notification to update magisk, download it and flash. (Or if the recommended native install is an option, use that)
I recommend just using he normal 14.3 magisk... You'll have issues, but they will be predictable and easy to solve with a simple reboot. There's really no final solution for us unfortunately, just making it as stable as possible.
Lastly, it helps if once every once in a while you fully uninstall magisk with the uninstall.zip, reboot (you might not get a bootloop, in which case hold volume up +power+ home to boot into recovery), reflash magisk 14.3, and then wipe cache and art/davik.
---------- Post added at 04:12 PM ---------- Previous post was at 04:12 PM ----------
larrythil said:
Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
(I don't want to install a Custom ROM!)
Thank you
Larry
Click to expand...
Click to collapse
See above

Thanks to all for the help
Nye-uhls said:
So long story short, there's no definitive solution to the problem. Im using a g920p with a custom kernel built by a genius dev, and i still lose root once a day.
Basically what it comes down to is modules. If you have zero modules, you'll have better luck... But that's not the point of magisk, so you need to be picky with modules. Use osmosis's busybox from the magisk repo, but other than that, install modules 1 at a time and see if it affects root.
Another tip: uninstall all updates of the "device maintenance" app, and find it in Google play and turn off automatic updates. Then go to device maintenance > battery > unmonitored apps and magisk manager to the list of unmonitored apps... Then go back the battery screen, battery usage > 3 dots in top right > optimize battery usage, and make sure magisk manager is not optimized... That should help some. (Note: some models don't have device maintenance, but you'll still have the "optimize battery usage" option some where.)
The Google play thing you're seeing is likely "instant apps" updating. I believe that should be unrelated to all this, but some aspects of instant apps is a mystery.
As for the logcat thing, i believe you're getting logcat confused with the magisk_debug.log located in /data ? If that's the case, you need to be using the beta version of magisk. Go to magisk and set the update channel to beta, you'll get a notification to update magisk, download it and flash. (Or if the recommended native install is an option, use that)
I recommend just using he normal 14.3 magisk... You'll have issues, but they will be predictable and easy to solve with a simple reboot. There's really no final solution for us unfortunately, just making it as stable as possible.
Lastly, it helps if once every once in a while you fully uninstall magisk with the uninstall.zip, reboot (you might not get a bootloop, in which case hold volume up +power+ home to boot into recovery), reflash magisk 14.3, and then wipe cache and art/davik.
---------- Post added at 04:12 PM ---------- Previous post was at 04:12 PM ----------
See above
Click to expand...
Click to collapse
Hello again.
So in response.
I followed the advice given... (just as a note previously the root issue would happen within an hour of restarting the device). I have been to the beta thread and read through all advice. Before jumping to the Magisk 14.3, I started with Magisk 14.2, there was a post recommending this as a critical update to Magisk 14.0.
I had no issues with this install (I had once again used my backup to revert the phone back to all original).
I then added any of the modules i wanted one at a time waiting over an hour before looking at adding any additional modules.
So far, I have not lost root and the phone is working as expected (alot better infact). I have all the Busybox modules +add-on's running, still no issues.
The upgrade to v14.2 seems to have fixed all for my uses.
Thanks to all for help and advice.
Andy

AndyQVT said:
Hello again.
So in response.
I followed the advice given... (just as a note previously the root issue would happen within an hour of restarting the device). I have been to the beta thread and read through all advice. Before jumping to the Magisk 14.3, I started with Magisk 14.2, there was a post recommending this as a critical update to Magisk 14.0.
I had no issues with this install (I had once again used my backup to revert the phone back to all original).
I then added any of the modules i wanted one at a time waiting over an hour before looking at adding any additional modules.
So far, I have not lost root and the phone is working as expected (alot better infact). I have all the Busybox modules +add-on's running, still no issues.
The upgrade to v14.2 seems to have fixed all for my uses.
Thanks to all for help and advice.
Andy
Click to expand...
Click to collapse
Glad everything is good! Sometimes magisk will get messed up, so just updating or even reinstalling will fix things.
Just keep in mind, its very likely you'll have problems again down the road... Samsung phones do a lot of weird stuff under the hood, and eventually symlinks will get broken, files deleted etc... So when that does happen, the best you can do is uninstall, reflash, update, and watch your modules.

Today updated to 15.3 and install James DSP root losed...When open magisk ask for installation reboot to recovery twrp install latest zip reboot open magisk it close it self and root lost again ?! Any advice from @topjohnwu

Do you guys mind posting a resource that shows how to root the S6 using magisk? I'm very rusty, last time I dealt with rooting was 8 years ago. Any help is appreciated. Thanks

Magisk V16 can't install on Android 5.0

Has anyone has success in installing this on Android 5.0 samsung S4 ? I followed the instructions and the manager just says not installed.

Unless you provide more details and installation logs it's gonna be hard to help...

Didgeridoohan said:
Unless you provide more details and installation logs it's gonna be hard to help...
Click to expand...
Click to collapse
What details would you like to know? I flash it and then later restart but the manager was not there so I tried to install it from saving the apk file that I downloaded. But it just said it was not installed and later I found out I lost root from trying to flash Xposed on my phone.
I am very new to this and tried to follow the tutorials and videos but its not working cause I thought using Magisk I can install the seamless Xposed.

Those recovery/installation logs would be a good start.
You're muddling up the details a bit...
Was the Manager not installed or did it report that Magisk wasn't installed? And you lost root? But you said you couldn't install Magisk... Are you already rooted? That might cause issues.
Being nice and clear and detailed (what is being flashed, version numbers, what's already done, what works, what doesn't work, with logs, etc) in your descriptions would help.

Didgeridoohan said:
Those recovery/installation logs would be a good start.
You're muddling up the details a bit...
Was the Manager not installed or did it report that Magisk wasn't installed? And you lost root? But you said you couldn't install Magisk... Are you already rooted? That might cause issues.
Being nice and clear and detailed (what is being flashed, version numbers, what's already done, what works, what doesn't work, with logs, etc) in your descriptions would help.
Click to expand...
Click to collapse
I hope this is clearly for you!
1. I flash the file with TWRP with success
2. The phone got stuck on samsung logo
3. Root was removed.
4.I had to re flash stock and it is working again.
5. How do I get the logs of Magisk if my phone keeps looping?
I wanted to use Magisk to see if Xposed would work but it looks like i can't even get Magisk to work on my samsung i9500 with original rom. This same thing happens with Xposed where everything goes smoothly with flashing it in recovery and then a boot loop on the logo. Others on this forum have been complaining about this too and perhaps the developer might have not considered odexed rom like samsung for these wonderful apps to work?
I am going back to Kitkat where i don't have these issues and I can use Xposed.

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.

Magisk Update from 2.30 to 2.4.1 Guide for dummies

The new Magisk is here and with it some major changes. One of the most important is the removal of support for "MagiskHide". There are many advanced users who have figured this all out already and few (maybe more) like me who are just kind of lost not knowing what should be exactly done to be able to update and be able to use Magisk as they were, before the update.
I was hoping that a kind soul would put up an easy step by step guide to help these users and at the same time it will avoid a lot of repetitive questions on the main thread. I personally spent a long time reading many pages and was not able to fully understand what should be done.
In my case all I want to achieve is to update and be able to hide Magisk like it was in the previous version. Should I start by un-hiding it first before doing the update?
(what and how and from where) should I add something that will replace the hiding function? Viola! these are the kind of simple questions that will help some of us get going
I hope that someone will bring his precious help

Yeah I unfortunately did my upgrade and fought with the whole process for 6 hours straight (lol) and I still don't know what I did exactly to even begin to write any instructions - other than 6 hours straight of reading and trying and hoping .....
Not sure if you have been able to refer to this which helped me.... But, I also have an very basic understanding of how my device (OnePlus 7T) works with Magisk... Hope this helps. May be see if your specific device has the instructions already posted in the device specific forum here?
Installation
The Magic Mask for Android
topjohnwu.github.io
I've not used the Magisk hide cause I haven't needed it - BUT, it's still available in the latest Magisk Manager (24.1) in the Magisk Manager settings. I'm only using the systemless hosts module (included in Magisk manager settings) for Adaway, and the universal safety net fix to get Google Play store to say my device is certified.
But I don't know what device you have nor do I know the specific ROM you are using.
Sounds like you have root already so I'm thinking that's the worst of this behind you if you've already done that much yourself. Sounds like it's a basic case of update the Magisk Manager app from itself then determine the method appropriate for root to update which could be through the Manager app or like I chose to use the boot IMG then patch that then install since my device has no working TWRP. That, and once I updated the manager app and panicked so I uninstalled it to try and downgrade to v23 .... Good luck and may be just don't update just yet if there is no specific need to at this time. Take your time and read and proceed when comfortable.
Please:
Start with your preferred method of backing up everything first.
Also, may be consider if it's necessary to update and why??? I'm on stock Andriod 11 and this Magisk update make me think it's intended to be more for those on Android 12 - but I could also assume wrongly.
[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
That's the thread I'm reading now...

Thanks a lot for your reply wugga3. I also on my side found two very helpful posts. They explain the basics (just to get started) and to make the update . I hope with the information gathered I will be able to do the update without messing things up!
[Discussion] Google Pay Magisk Discussion Thread
This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads. Please use this to discuss issues with Google Pay and possible solutions. There's a...
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

Good and good luck...
One problem and probably the only problem I really had was self inflicted for not following the instructions properly and that was to uninstall any Magisk modules first or at that the appropriate step.
Other than that... still don't know your device or rom etc. Your device specific or rom specific forums may be able to provide you with much better assistance from members that have the same rom/device as you.

wugga3 said:
Good and good luck...
One problem and probably the only problem I really had was self inflicted for not following the instructions properly and that was to uninstall any Magisk modules first or at that the appropriate step.
Other than that... still don't know your device or rom etc. Your device specific or rom specific forums may be able to provide you with much better assistance from members that have the same rom/device as youI
Click to expand...
Click to collapse
I am using LineageOS 18.1 Android 11 for Samsung Galaxy Note 3 and I have twrp as recovery. Magisk 2.30 is already installed and device is rooted. I have no modules installed and in Magisk settings I have only MagiskHide enabled. All other settings are set to default. On Samsung Note3 forum there is no talk about this (understandable as the device is very old).

Ok great and is there any discussion for lineage 18.1 and root/update?
Since it's lineage 18 and based on Andriod 11 - I have to wonder if there is even the need to update Magisk as my limited understanding is that the Magisk update is aimed at Andriod 12? Other than that... I should expect from my prior understandings of Samsung that nothing much has changed with respect to root and updates of Magisk. Not much help but hopefully enough. May be best to wait until for now and usually I do also wait until all the facts are in and the bugs are sorted out (if any...) before I update if unnecessary.

Thanks wugga3,
I disabled "Check for updates" in Magisk app and decided to keep the older 2.30 version for now. Everything is working fine and so there is no reason to fix something which is not broken. The only reason I thought That I should update was a real advantage over the older version or a security weakness being fixed in the new one.
I am even seeing some people asking for help on how to downgrade! Anyway as you said wisely, it;s not after all a bad idea to wait a little to see how things work out for those who have upgraded and have new issues fixed before taking the jump.

Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot (Magisk) to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want

mingkee said:
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
Click to expand...
Click to collapse
Thanks a lot for your post mingkee,
I am sure many like me will be happy and appreciate reading this instead of having to go through many pages and still not be totally sure what to do
Allow me to just ask one question as I did not understand the second option of your instruction:
I update Magisk from the application itself. Once updated what do you mean by update boot to 24.1? This is to be done in Magisk itself?

rezpower said:
Thanks a lot for your post mingkee,
I am sure many like me will be happy and appreciate reading this instead of having to go through many pages and still not be totally sure what to do
Allow me to just ask one question as I did not understand the second option of your instruction:
I update Magisk from the application itself. Once updated what do you mean by update boot to 24.1? This is to be done in Magisk itself?
Click to expand...
Click to collapse
After updated app to 24.1, you will see another update on top of the app (Magisk). Direct install would be the simplest method

mingkee said:
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot (Magisk) to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
Click to expand...
Click to collapse
this should be pinned somewhere, very simple and worked fine on my Poco F3 using miui.eu & android 11
thanks a lot