Related
Hello Everyone,
I recently installed LineageOS 18.1 (build: lineage_kebab-userdebug 11). I have retrieved my Android ID using the ADB commands found here: Device Registration and registered my Android ID a few days ago but Google Play Store still shows: "Device is not certified" under Settings --> About --> Play Protect certification. Is there something I'm doing wrong or something else I need to do in order to get my device certified with Google Play Store?
use magisk hide props config I use the pixel 5 fingerprint and add new props
ro.product.model Pixel 5
ro.product.manufacturer Google
option 5 add those 2 after you change fingerprint you will pass and get stadia discounts just can't run edxposed I do but a few changes in that you fail hope that helps
ecompton59 said:
use magisk hide props config I use the pixel 5 fingerprint and add new props
ro.product.model Pixel 5
ro.product.manufacturer Google
option 5 add those 2 after you change fingerprint you will pass and get stadia discounts just can't run edxposed I do but a few changes in that you fail hope that helps
Click to expand...
Click to collapse
Thank you for the info. So you are saying in order to get my device "certified" with Google Play Store I need to root my device, add new props and change my fingerprint (I assume you mean Android ID)? I'm not sure what you mean by: "stadia discounts" or "edxposed". Also, I do not see where I need to root my device in the LineageOS documentation or the Google documentation so I'm still unclear why this must be done. Does Google block LineageOS devices from getting "certified" or something?
long as you used dual sim oos file to unlock your phone it won't unless you do something like that and Google thinks I have pixel 5 see pics I pass
alteredstate82 said:
Thank you for the info. So you are saying in order to get my device "certified" with Google Play Store I need to root my device, add new props and change my fingerprint (I assume you mean Android ID)? I'm not sure what you mean by: "stadia discounts" or "edxposed". Also, I do not see where I need to root my device in the LineageOS documentation or the Google documentation so I'm still unclear why this must be done. Does Google block LineageOS devices from getting "certified" or something?
Click to expand...
Click to collapse
Unlocking a bootloader breaks SafetyNet passes. This results in the play store as not being certified which usually hides specific apps such as Netflix and some other banking apps and will break them. Magisk is needed to help with spoofing your device to let the play store know your device is certified. Some ROMs have built in patches in which SafetyNet passes fine without root. I believe lineage does not do this with their ROM, so you will need magisk.
This is actually a decent article which describes this if you desire to read it - https://www.hexnode.com/blogs/safetynet-android-security/
azoller1 said:
Unlocking a bootloader breaks SafetyNet passes. This results in the play store as not being certified which usually hides specific apps such as Netflix and some other banking apps and will break them. Magisk is needed to help with spoofing your device to let the play store know your device is certified. Some ROMs have built in patches in which SafetyNet passes fine without root. I believe lineage does not do this with their ROM, so you will need magisk.
This is actually a decent article which describes this if you desire to read it - https://www.hexnode.com/blogs/safetynet-android-security/
Click to expand...
Click to collapse
Okay that makes sense. According to the: Patching Images section of the How to Install Magisk App guide I can install Magisk to the boot ramdisk (see screenshot). However, the LineageOS build I installed does not contain a "boot.img" in the zip file. There is however a "payload.bin" file which according to the: XDA Magisk Installation Guide I need to use "payload-dumper-go" to extract the boot.img from the payload.bin? Does that about sum it up or is there something else I'm missing?
alteredstate82 said:
Okay that makes sense. According to the: Patching Images section of the How to Install Magisk App guide I can install Magisk to the boot ramdisk (see screenshot). However, the LineageOS build I installed does not contain a "boot.img" in the zip file. There is however a "payload.bin" file which according to the: XDA Magisk Installation Guide I need to use "payload-dumper-go" to extract the boot.img from the payload.bin? Does that about sum it up or is there something else I'm missing?
Click to expand...
Click to collapse
Yep. You will need to extract the payload.bin file in which you will use the boot.img, then patch it with magisk, then flash the patched boot.img using fastboot. Then, you will need to use magiskhide to hide magisk itself and use the props spoof module to help with passing safetynet.
I want to say thank you for the help! I successfully installed Magisk and passed the SafetyNet checks! Everything seems to be working good. However, it seems my efforts might be wasted as Magisk is dropping support for hiding root access. This is unfortunate as I have a few job critical apps that will not work unless I hide them from root access in Magisk. Hopefully someone else will pick up the torch and continue development. It's a crime these big tech companies work so hard to prevent us from modifying hardware we own!
Hi, I flashed LineageOS 18.1 to my OnlePlus 8T (KB2003). The device is not rooted.
Since that, he device is no longer Play Protect certified and I am not able to install Netflix or use PayPal anymore.
Therefore I installed Magisk and MagiskHidePropsConf-v6.1.2 and followed the instructions above to change the fingerprint and hopefully hide, that the bootloader is unocked. But the device is still not certified (PayStore App > Settings > Info)
What have I done:
- extracted boot.img from LineageOS payload.bin
- boot.img was patched and fastboot flashed to my device (Patching_Images)
- 2 props added: ro.product.model: "Pixel 5", ro.product.manufacturer: "Google"
Did I forgot something?
But in general, why is it needed to change the fingerprint to Pixel 5? Should not work the default fingerprint of my OnePlus 8T as well?
BR Greg
gregattack said:
Hi, I flashed LineageOS 18.1 to my OnlePlus 8T (KB2003). The device is not rooted.
Since that, he device is no longer Play Protect certified and I am not able to install Netflix or use PayPal anymore.
Therefore I installed Magisk and MagiskHidePropsConf-v6.1.2 and followed the instructions above to change the fingerprint and hopefully hide, that the bootloader is unocked. But the device is still not certified (PayStore App > Settings > Info)
What have I done:
- extracted boot.img from LineageOS payload.bin
- boot.img was patched and fastboot flashed to my device (Patching_Images)
- 2 props added: ro.product.model: "Pixel 5", ro.product.manufacturer: "Google"
Did I forgot something?
But in general, why is it needed to change the fingerprint to Pixel 5? Should not work the default fingerprint of my OnePlus 8T as well?
BR Greg
Click to expand...
Click to collapse
All I needed to do to get Play Protect certified was to change my fingerprint to the OP8T KB2003 fingerprint included in MagiskHide Props Config. No other model spoofing needed.
I am still stuck on Widevine L3, however. Still haven't figured that one out, and may be unrelated.
Did you install and use the Universal SafetyNet Fix module?
If I set the kb2003 OP 8T (EU) fingerprint, it seemed not to work. But I will try again.
Do I need to clear some caches eg: play store, after changing the fingerprint or something else?
cpkelley94 said:
All I needed to do to get Play Protect certified was to change my fingerprint to the OP8T KB2003 fingerprint included in MagiskHide Props Config. No other model spoofing needed.
I am still stuck on Widevine L3, however. Still haven't figured that one out, and may be unrelated.
Click to expand...
Click to collapse
finally I installed Universal SafetyNet Fix and switched to the kb2003 fingerprint and reset all other modification like custom props for the pixel phone. Now it's working. No idea why it fails in previous approach
Strange, on my device. Not on lineage though - I pass safetynet without help from any modules. No props or even USF module. Rooted and bootloader unlocked.
Op8t 5g tmobile.
ykjae said:
Strange, on my device. Not on lineage though - I pass safetynet without help from any modules. No props or even USF module. Rooted and bootloader unlocked.
Op8t 5g tmobile.
Click to expand...
Click to collapse
which image are you using?
I read, that some images like https://evolution-x.org/ pass safetynet out of the box but I did'nt test this.
Finally the unlocked bootloader is the problem.
My daughter got a new phone, after struggling with bootloops and magisk issues. Finally got everything working correctly.
But,
I got root to go fine, only thing is she has had location issues. Google maps, other GPS or location services did not work.
So I uninstalled xprivacylua and seems like services came back, looks like I wasn't hiding anything on it anyways. Or I don't remember what it was.
So instead of reinstalling xprivacylua I decided to look for different answers .
Maybe some other solutions.
Here is a list of apps and modules that are installed. I think some of them overlapped and are kind of messed up. To many that my head is spinning.
Magisk
23.0 (23000)
Magiskhide Props Config.
Riru
Riru LS exposed (Tried switching back and forth to edxposed)
Systemless Hosts
Universal Safetynet fix 1.1.2. (Tried different versions)
LS Esposed one module,
Hiddencore module (enabled Google services Framework and google play services)
Also cleared Data and Cache on google play store.
Rebooted every time
Always safety net failure.
I know its a lot to take in , and do appreciate any feedback or help on this issue.
Is it an 8T? Are you running stock OOS with magisk?
In that case all you need to pass safteynet should be Magisk 23 with magisk hide activated. No need to bother with Magisk hide propconfig, or edexposed or anything.
If you are running a custom rom it is a different matter
I have magisk 23 and magisk hide is active on all google play services, but it still fails.
Its 8t with stock rom.
I think this is why its a little confusing since on my stock 7 pro I have google play services and only android.gms, and android gms unstable hidden and it works fine.
There is not a custom recovery on either of these phones.
Magisk and magisk hide works fine for me, so don't know what to say.
Perhaps try to uninstall Riru and exposed to make sure that they aren't triggering safety net?
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Screens of magisk hide props config
scottlam1 said:
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Click to expand...
Click to collapse
Nope.. Terminal Emulator is actually recommended. With Termux, you are required to use root access for props to work.
with Terminal Emulator, you can just type:
props
and then it'll load. no "su" necessary. That's termux. I've had some issues that these people are talking about with my OnePlus 8T (KB2005, unlocked completely).. I'll try Termux just to rule this out, but this is highly doubtful as to whether or not safetynet passes based on this--it's attempting to modify the same values. Anyway, when I unlocked that bootloader on a stock rom, CTS Profile started showing as false. So I did get the stock on there correctly and it initially passed with a LOCKED bootloader. There's an alpha TWRP that you can actually flash if you want. There's a couple others where you can only boot it.. there's a lot of "only's" here.. and I couldn't get it going with any of the apps mentioned, including ditching EdXposed and deciding to try LSPosed, but that + XPrivacyLau didnt seem to help me. Maybe I'm doing something wrong. From what I can tell I've done everything right and I've got quite a bit of experience attempting/doing this. Sometimes Device SImulation and forced BASIC ATTESTATION can be a lifesaver.
On my OnePlus 6T, I don't have this problem.. then again it's on Android 10. I can't even get a proper root explorer for Android 11. I seriously can't stand what they did to Android 11.. it's so ridiculous how many apps are now incompatible. Root Explorer Pro was possibly the best Root File Manager I've ever used and I've used it since day 1.
Anyway, I'm gonna give all of this a shot in different order.. and this time I'll see if Magisk can do the trick (last time it was on some different firmware and i just now was able to get it going by flashing via Fastboot in Linux). It's the manual way (payload dumper) as opposed to MSMDownloadTool -- which could be used via a VM.. and maybe even better than using Windows tools where you literally have no idea what you're actually doing. I'm just saying. Android is a linux distro, technically.. and we're trying to use just basic root apps for Android 11, and they don't seem to work.. it's insane. They did something with the partitions and it's apparently having issues even mounting R/W even with Magisk giving it root permissions. Btw, Magisk Canary is now outdated, as far as I can tell? Or it's just nowhere to be found when it comes to versions. Either way, I have tried multiple. So I'll try again in a different order.
Sorry for the long post. I've just had it. I've been working on this for a WEEK non stop.. 5-6 days and this is the first sign of progress (reverting via fastboot via Linux, which is the same thing as the MSMDownloadTool ultimately... without the hassle of finding it)
Let me know if there's anything else.. cause I've tried just about everything out there. Remember, for me, so far... unlocked bootloader = CTS Profile failure.. but locked bootloader + stock rom? Passed. I don't know. Before it wasn't passing with a stock rom that came with it so that drove me nuts and made no sense, hence me saying "progress" ... heh. Anyway.. Please let me know if you guys do find anything that works for it. I'm at my wits end. There's basically almost zero support for the 8T but plenty for the 8 and 8 Pro. So that also gets on my nerves. Sorry, once again, for this really long post. Some of it is just venting and I'll update if I get somewhere with it.
.. and now this morning after installing magisk, by just booting twrp (not flashing, but booting) and then using LSPosed/XPrivacyLua (I installed MagiskProps too but I barely did anything aside from pick a fingerprint) --- and it passed? WHAT?
I'm gonna look into this, but I'm not complaining. Let's see if I can find good Android 11 apps for actually browsing the system and being able to r/w any elusive partitions -- wasn't working well with Android 11 before. Not sure if that's around with a simple design anymore. Root Explorer Pro was king of that. Then Android 11 stepped in. I still have to install Lucky Patcher, if it will even work as a module for LSPosed. (Yes, I'm one of those idiots) -- I fully expect it to fail with that but I might be pleasantly surprised. Who knows. So, we'll just call this mixed results. For now -- Passing somehow. I don't understand aside from LSPosed and XPrivLua.. maybe magiskprops. Not sure which one did what first to cause this to go the right direction.
All I can say is all I have is magisk props not the other 2 modules you speak of
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
eracet said:
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
Click to expand...
Click to collapse
Ok asked her what she did. Mentioned updated YouTube vanced. And not sure of anything else.
I'm considering buying this phone but if it lacks support for BASIC attestation would mean that hiding root would be impossible and hence the phone would be useless for me.
Zincoshine said:
I'm considering buying this phone but if it lacks support for BASIC attestation would mean that hiding root would be impossible and hence the phone would be useless for me.
Click to expand...
Click to collapse
As of now with magisk 23.0 on Android 11 I'm able to hide everything g-pay all banking credit card apps working. Magisk is changing in Android 12 so I'm unsure. But I believe there are still some modules we can use to hide su access in magisk canary beta for 12.
There are several modules for Magisk that allow for basic. I have been using them since I bought the phone on release day, and have been able to use all apps. I would recommend sticking to Magisk v23 instead of the newer version, as hide has been removed (for now). You will get conflicting advice on this, and will most likely have to make a decision to move to a12 or keep hide down the line.
Lmk if you would like my list or modules.
mattie_49 said:
As of now with magisk 23.0 on Android 11 I'm able to hide everything g-pay all banking credit card apps working. Magisk is changing in Android 12 so I'm unsure. But I believe there are still some modules we can use to hide su access in magisk canary beta for 12.
Click to expand...
Click to collapse
I have no intention of ever updating to Android 12 so this won't matter. My oneplus 5T has been on Android 8.1 for years (mainly because I wanted that sweet sweet taste of the original rovo89 Xposed framework) and it has worked fine but it's clearly nearing the end of its life and has a slightly broken screen.
OP9 LE2110 with OOS 11.2.8.8.LE25BA rooted with Magisk 23. Working apart of banking app. G Pay is ok
Everything is working great with latest Magisk Alpha, Universal SafetyNet Fix and Zygisk enabled with Deny list (New MagiskHide)
What version of Magisk and what root hide (module name and version please) people have it fully working for Feb 2022 firmware update (840.2201.226), especially for Google Pay? Thanks
(I'd it all working on the previous firmware release just fine. Then right after applying the above mentioned Feb update, when I tried to execute Magisk (possibly 23.1) to patch the inactive slot, it just wouldn't execute let alone patch; nor would Termux "su" command would execute. So there was no way to patch Magisk over that update. Problem was made worse, when I executed LSPosed, which proceeded to update and auto rebooted the phone! Jumped from the frying pan into the fire.)
nexusnerdgeek said:
What version of Magisk and what root hide (module name and version please) people have it fully working for Feb 2022 firmware update (840.2201.226), especially for Google Pay? Thanks
(I'd it all working on the previous firmware release just fine. Then right after applying the above mentioned Feb update, when I tried to execute Magisk (possibly 23.1) to patch the inactive slot, it just wouldn't execute let alone patch; nor would Termux "su" command would execute. So there was no way to patch Magisk over that update. Problem was made worse, when I executed LSPosed, which proceeded to update and auto rebooted the phone! Jumped from the frying pan into the fire.)
Click to expand...
Click to collapse
Using Latest Magisk and Zygisk-Shamiko.
MagiskHide is no longer available - and Denylist is not effective.
For the patch - First Patch the Boot Image, then Install Magisk again over TWRP as well.
Thanks, I got Magisk 24.2 installed & working fine now.
(Things are super difficult as it is, so I've skipped trying to install/activate TWRP.)
However, Universal SafetyNet Fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases), though installs fine, gets disabled due to "Module suspended because Zygisk is not enabled".
I've confirmed that Zygisk (Beta) is activated in Magisk's settings. What am I missing?
Q: How to "unsuspend" Universal SafetyNet Fix module?
Thanks
(It's so difficult to keep up with all this work that I'm leaning towards relocking the boot-loader. I really don't use any app or feature to benefit from unlocked boot loader or root. I did it only to be ready for injecting mbn, which isn't needed or possible anyway. It was a bad decision then & remains so now. Though I don't know if while relocking the bootloader the phone will get bricked. Decision.. decision... With all the difficulty of keeping up with root, it sounds like a risk worth taking.)
Actually removing the Magisk APK and reinstalling it seemed to have helped. Termux works reliably for su. Gpay is good as well. Magisk log shows no funky messages.
In the end, I had to use this to overcome root detection on two banking apps: https://github.com/vvb2060/magisk_files/blob/alpha/app-release.apk
nexusnerdgeek said:
In the end, I had to use this to overcome root detection on two banking apps: https://github.com/vvb2060/magisk_files/blob/alpha/app-release.apk
Click to expand...
Click to collapse
What's that ?
Leads to a empty GitHub Page ...
Actually official Magisk 24.3 works well for all of the banking apps I need root hide for. So, there's no need for that unofficial alpha build anymore for me; in fact, I got rid of it. Please disregard that link.
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.
koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.
Click to expand...
Click to collapse
Can you uninstall Magisk and install the stable or last working canary app?
simplepinoi177 said:
Can you uninstall Magisk and install the stable or last working canary app?
Click to expand...
Click to collapse
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).
koberulz said:
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).
Click to expand...
Click to collapse
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...
simplepinoi177 said:
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...
Click to expand...
Click to collapse
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.
koberulz said:
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.
Click to expand...
Click to collapse
Uninstalling the Magisk Manager app would not affect root; you might not be able to run certain rooted apps properly without granting them root access, but that's because of not having the Magisk app to grant it.
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings") so it's not detected by any root detection. In any case, you should be able to find it in the Apps list in Settings/Apps, and uninstall it that way.
As to what to install over the top of it, installing the latest stable 25.2 would be the best idea -- the Magisk App does not need to match the version that is patched and flashed to your boot partition...
simplepinoi177 said:
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
Click to expand...
Click to collapse
My understanding was that he got hired and they said he had to give it up, there was some negotiation and they let him continue working on it as long as Magisk Hide was removed as a feature.
But this isn't something that really interests me all that much, so I don't keep up with the news on it. I more just check in whenever I get a new phone in order to figure out how to root it.
simplepinoi177 said:
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings")
Click to expand...
Click to collapse
Yes, this is what I was referring to.
koberulz said:
Yes, this is what I was referring to.
Click to expand...
Click to collapse
koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
Click to expand...
Click to collapse
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?
simplepinoi177 said:
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?
Click to expand...
Click to collapse
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.
koberulz said:
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.
Click to expand...
Click to collapse
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.
simplepinoi177 said:
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.
Click to expand...
Click to collapse
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.
koberulz said:
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.
Click to expand...
Click to collapse
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
What's the difference?
koberulz said:
What's the difference?
Click to expand...
Click to collapse
dcarvil said:
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Click to expand...
Click to collapse
The first one is the first, general Magisk thread (that is still active and currently discussed). The second is as it is stated in the headline -- "This is a discussion and help thread for the newer versions of Magisk".
Most likely this is where you should go for your issues -- and to see how actively developed it is currently being.
It's just as you said, you've been away from rooting/Magisk for a while; the newer version of Magisk contains/employs Zygisk -- "Zygisk is new generation Magisk hide...Zygisk is what the Magisk developers call running Magisk in the Zygote Process of Android. The Zygote Process is the first process that the OS starts when it boots up, ... Since zygote starts first after system, it can hide root without sending data to apps." (source) As such, that's why a new thread was created and why it is sub-titled as "The Age of Zygisk"...
*but there are many more methods of hiding root than Zygisk (or in conjunction with); Shamiko, Magisk Delta, HideMyApp, etc.
In the end, I'm sure they'll suggest what I've suggested to you in some fashion -- you'll have to uninstall the Magisk Manager (hidden or not), and re-install the stable or earlier canary versions. But it'll be better coming from the people in that thread...
Good luck!