yashsingh1/xdaforums huggingface dataset:
[Magisk] locolyric:
WoW! thanks for that !

---------------------------------

just test to remove using unSU but safetynet check show the last result is fail and pokemon still uncompatible.

I think the developer setting were only disable root but not remove it from system.

Hope there is another way to settle this because AICP is a good rom.
[Magisk] rgawenda:
Mind sharing trhat module?
[Magisk] Simone98RC:
Hi guys,

installed via TWRP recovery SuperSU v2.78SR1 > Magisk v8 > Xposed Systemless v86.6

All seems work fine, but after many hours (or a reboot) I lose root access, even with Phh's Superuser happens that.

However, since Magisk v8 I've checked the Magisk Hide option.

Maybe that the cause of root losing?
[Magisk] AbiDez:
Hello, thanks a lot it works... Normally I use Suhide but last days no safety no pogo :(

So I test Magisk V8 for 1st time...

Make unroot with SuperSu, flash stock boot.img, flash magisk V8, flash phh superuser... Reboot... Install Magisc Manager, activate Magisc Hide Mode, reboot... Install phh superuser app from store...

Nice [emoji41]

CarHDRom V.24.7 by Carotix S6e
[Magisk] zgfg:
But they say there is LSPosed directly for Zygisk. Expecting the same cade with Canary
[Magisk] klemi71:
YASNAC finds basic integrity is passed, CTS isn't.

Pixel 3, Android 11, Kirisakura Kernel, latest canary Magisk, Riru/USNF 2.1.1

Should it be solved by using MagiskHidePropsConfig module?
[Magisk] pndwal:
To address inevitable concerns re. MagiskHide removal here, I thought it appropriate to reproduce John's succinct clarification (from his Twitter)... Hopefully It'll do something to quell the tide of naysayers also...

My key takeaways:

- The latest Magisk is arguably more capable (feature wise) to hide things if any module developer really wants to

- There is no practical way to defeat HWKA big hammer

- Those who are still passionate about hiding can start "doing their job"

- DenyList feature of upcoming Magisk versions is John preserving portions of the of hiding codebase

- Denylist can easily be utilised for "hiding" purposes

- Google staff incl. John are brainstorming solutions on how to deal with the "root detection abuse" situation. 👍👍 (Macca's?)

- John is spending time defending the community within Google.

- Naysayers can do much to ruin things for all of us and alienate a fine advocate... or do much to make amends...

- Enjoy hiding while you can!

😬... 👏👏👏 PW
[Magisk] pndwal:
For 'Zygisk Module' builders:

Develping Zygisk Modules

https://github.com/topjohnwu/zygisk-module-sample#develping-zygisk-modules

Is John just making it TOO easy? 👍 PW
[Magisk] peikojose:
Where can I get it? Will it work the A12 and phones that need to disable verity?
[Magisk] pndwal:
Seems Riru breaks with Zygisk (probably on purpose) in latest Canary (as well in latest Alpha)...

Does anyone have it working? PW
[Magisk] zgfg:
As written on Alpha TF, you have to use LSPosed for Zygisk (didn't try)

However, then you can't use e g. Riru-Momihider anymore, only LSPosed modules
[Magisk] pndwal:
Alpha Telegram group, link in vvb2060's GitHub, check (copy / translate thread there for latest build to see current issues etc).

Works with A12... But new TJW Canary should also as it builds basically the same recent commits... I'd try that with your devices disabled verify requirements.

Nb. While previous Alpha had Riru and Zygisk coexisting happily, seems Zygisk breaks Riru in both latest Alpha and Canary... PW
[Magisk] pndwal:
Yeah, understood that.

I was asking (for confirmation) if Riru is working for anyone in new Canary W/ Zygisk... (Seems it also breaks in new Canary). PW
[Magisk] jons99:
zygisk lsposed

LSPosedArchives

t.me
[Magisk] ionuutzuu:
Hello, can any1 help me with a bootloop problem?

I have a Poco F2 Pro which had working magisk module on MIUI 12.2.6.0.RJKEUXM and I received update to 12.5.2.0.RJKEUXM and now when I patch the boot.img it cause a bootloop. If i put the original boot.img it works good, if I wipe data from a custom recovery it also boots.

Does any1 know the cause of my bootloop? Why it works with factory reset and doesn't with all my data? I just don't want to loose and get over from all my stufff. Too many apps and customization to redo. The bad part is that I can't do a rollback... The phone doesn't boot also.
[Magisk] pndwal:
I believe that's an upgrade from Android 10 to Android 11.

Most likely you didn't disable modules before updating and one or more are incompatible in Android 11.

Research disabling modules using Safe Mode or placing file flags in data/adb/

Eg:

https://topjohnwu.github.io/Magisk/faq.html#q-i-installed-a-module-and-it-bootlooped-my-device-help

Or:

https://www.didgeridoohan.com/magisk/MagiskModuleIssues#

😎 PW
[Magisk] ionuutzuu:
Nope. I haven't. What can I do now? Magisk manager is uninstalled. How modules could load without manager installed?
[Magisk] pndwal:
Sorry, wrong.

App data in Magisk App only affects a few app specific settings.

data/adb/ directory stores modules, SU settings, hidelist (now denylist) etc etc, and these survive App uninstall... Magisk still functions with all settings without App...

Adding links in post above. PW
[Magisk] ionuutzuu:
@pndwal - I can't boot in safe mode also...
[Magisk] jons99:
in twrp go to data/adb/modules and delete all folders
[Magisk] ionuutzuu:
Thank you very much dude. It was smali patcher! Deleted it and now phone started. No bootloop anymore. Thank you a lot.
[Magisk] edzamber:
What about Saftynet fix with latest Magisk zysisk ?
[Magisk] peikojose:
Thanks, yeah I'm sure we will have to disable verity again, what a pain in the *ss
[Magisk] klemi71:
For me uninstalling Riru and USNF 2.1.1 modules and installing version 1.2.0 from GitHub works as a temporary solution until Universal SafetyNet Fix may be available as zygisk module.
[Magisk] pndwal:
Ok, Alpha Dev explains this (Chinese translated):

Seems latest Zygisk tweeks for new Zygisk LSPosed module now cause unresolved conflicts with Riru (likely due to using the same resources simultaneously I guess).

John committed code to ensure these couldn't coexist some time ago, and vvb2060 reversed this in a few Alpha builds.

Anyway, looks like Riru's fate is sealed going forward.

I'm guessing most Riru modules will move to Zygisk in short order now. Users who want to use Riru modules for any reason will need to forgo Zygisk it seems...

FWIW, I have SafetyNet passing with old USNF 1.2.0 and the Google Play Services SafetyNet process added to the DenyList in new Canary on Redmi Note 8T.

I'll.post Notes for passing SafetyNet for others next. 👍 PW
[Magisk] pndwal:
Notes for passing SafetyNet in new Magisk

For TJW builds going forward you will need to add Google Play Services process(es) to denylist until a solution for hiding root associated modifications from GPS SafetyNet processes is incorporated in a module. For devices where Magisk resides in /sbin (many pre. Android 11), only deny SafetyNet process, com.google.android.gms.unstable. For Android 11+ etc (non /sbin), deny Main process, com.google.android.gms also. Nb. Once a solution for this is incorporated in Universal SafetyNet Fix (or other), users will likely need to remove the manually added process(es) for the fix to work as intended.

You also need solutions to edit keystore and possibly need to cause model mismatch etc to trigger fallbacks to basic attestation for various types of hardware attestation used if device is equipped for Hardware TEE.

Universal SafetyNet Fix (+Riru) was the best (all in one) solution for this and it even fixed 'sensitive' props issues, but with with Zygisk active we don't have a proper solution yet. (See above.)

Using old USNF 1.2.0 does needed Keystore changes for pre Android 12 ROMs not 'heavily skinned'... Samsung and other users may have issues with the older solution, and could try reverting to pre-Ruru test module here:

https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-767863635

This will Shim the keystore service instead of replacing it; it doesn't work for all heavily skinned ROMs, but various custom solutions are linked from same thread. Also, this solution works for some Android 12 ROMs. 🙂

This may be enough to pass, but some devices may need a fix for 'sensitive' props set to 'trigering' values in addition. Just installing MHPC module does this as an alternative to USNF 2.x.x series; it is enabled by default.

If your device is affected by September 2021 Google server end changes, you need to alter model prop (eg by using MHPC w/ Force Basic Attestation configured) in addition to cause fallback to Basic (a simple mismatch causes) for this particular hardware attestation.

-Nb. there are several fallbacks needed but it seems any one type gives Evaluation type = basic, so basic evalType is misleading.

-Nb.2. This early method can cause issues with OEM specific functionality like Galaxystore, camera functions etc as change is seen globally even if close model is selected as is recommended; 2.x series USNF w/ Riru (or Zygisk) can target Google Play Services only.

(See Universal SafetyNet Fix GitHub and notes for individual releases.)

You will also need to spoof a certified fingerprint if ROM is not certified (using a certified fingerprint). - MHPC with a certified fingerprint configured is the best solution.

Enjoy while it lasts! 🤠 PW
[Magisk] peikojose:
I just tried and yep, still you have to disable verity again. I suppose with the P6 there could be a workaround...
[Magisk] gorilla p:
I woke up this morning to a Magisk app update notification for the first time in a long time.

Ive never had an app update have a problem.

The app updated and now it doesnt work, it crashes as soon as I open it.

Cant open it. Cleared data, rebooted, no luck. Reinstalled previous magisk apk but its not detecting magisk installed.

Any ideas?
[Magisk] Qnorsten:
An alternative to using USNF 1.2.0 for devices that wasn't affeted by September google server end changes is to just use MHPC and enable it to spoof the magisk hide props (https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props) and enable com.google.android.gms and com.google.android.gms.unstable in the deny list works for me.
[Magisk] pndwal:
Did you have App hidden???
[Magisk] KaaMyA:
Welcome to the party!

Please read the last 13 posts before yours.
[Magisk] pndwal:
Guessing your device doesn't need Customised Keystore (fake provider) and wasn't affected by either January 12, 2021 or September 2, 2021 Google server end changes then as altering props is not the same. Ie device is old enough to lack required hardware for HKSA (Hardware TEE).

But you're right that this will work for some older devices... A Keystore altering mod will be needed for most however. PW
[Magisk] Qnorsten:
It is a oneplus 8T, but I think you are right. Just offering and alternative for some people.
[Magisk] pndwal:
Haha - recent device!

But you brand may well be why Google haven't fully switched on Hardware TEE!

They messed up TEE Attestation implementation so Google switched it off at server end in March 2020 (?) and have since been waiting for OEMs like OnePlus to fix it on their devices apparently... Google selectively applies it ATM, and I'm not sure if any OnePlus users see evalType HARDWARE.

Don't think you actually need the sensitive - props fix offered by MHPC in place of USNF to pass SafetyNet; I'm fairly sure the same props fix is not implemented in USNF till 2.x.x series, so I shouldn't have this now and still pass.

Of course you may need this as I believe props set to 'trigering' values is devices dependant... You could simply disable MHPC to see if you still pass, but only if you don't also require fingerprint spoofing in addition. (You may have tried this).

I'll edit my post above to indicate that some devices may need sensitive props fix in addition! 😁 PW
[Magisk] Qnorsten:
Yea I saw Hardware evaltype for my old oneplus 5 in 2020, but then they changed it back. I know it probably won't last forever, but right now I am happy as long as I don't need to bother with custom keystores or anything. Lets hope the OEMs take their sweet time in fixing the attestation implementations

The props fixes are already included in the latest USNF, so you don't need to use MHPC for these in that case. Not sure if they were included in USNF 1.2.0 or not.

Was just offering an alternative for some devices that don't need USNF at all.
[Magisk] ipdev:
USNF v1.2 did not support Android 12 so, a no go for those that updated to 12. :(

While I was messing around this morning, I rolled my Pixel 5 back to Android 11.

Stock Google (Android 11 October build).

Magisk canary.

USNF v1.2 module.

MHPC module (activated the sensitive props).

MagiskHide Props Config v6.1.0
by Didgeridoohan @ XDA Developers

=====================================
MagiskHide props (active)
Select an option below:
=====================================

Set/reset MagiskHide sensitive props.

Note that only props that originally are
set to sensitive values will show in the list.

1 - ro.boot.vbmeta.device_state (active)
2 - ro.boot.verifiedbootstate (active)
3 - ro.boot.flash.locked (active)
r - Reset all props
s - Boot stage
b - Go back to main menu
e - Exit

Enabling Zygisk, adding com.google.android.gms.unstable and com.google.android.gms to the DenyList.

Was enough to pass SafetyNet and keep Play certification.

No need to use MHPC's Force BASIC key attestation option.

Cheers. :cowboy:
[Magisk] pndwal:
Thanks for that...

I've already edited the post to indicate old test module for 'Shim Keystore' is better for Samsung etc w heavy skins...

This also is reported to work for some Android 12 (Pixel 3xl reported) devices, so may be worth trying on P5.

I'll add note regarding Android 12. 😉 PW
[Magisk] gorilla p:
Yup
[Magisk] zgfg:
Yes, no other way, but LSPosed Zygisk version runs fine

It means that you must sacrifice Riru-Momohider (since Riru is sacrificed) and therefore you can no more hide su from the path (maybe there will be a new Momohider for Zygisk, if possible)

However, Zygisk itself is easily detectable, hence the hunting season for banking and similar apps is now open (SafetyNet can still pass but the apps long ago started to evaluate other methods to detect root, and the Zygisk detection code is open source)

But generally, with the new Magisk, Google got what they approved
[Magisk] pndwal:
Here you go:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85761971 PW
[Magisk] J.Michael:
If all you are doing is trying to replace / insert files in /system, I don't think you need anything other than "system" in the module directory. Try removing the "auto_mount" and "module.prop".
[Magisk] zgfg:
module.prop is metadata (open as text and you can read), to display info about the particular module
[Magisk] pndwal:
It's early days, but while I have no real insight into effective hiding of Zygisk and acknowledge that some have said it can't be hidden I've yet to see any convincing proof or reasoning to support this.

Given its close resemblance to Riru, I wonder if we may see a Zygisk hiding module down the track, or if such efforts will come to light.

I'd love to hear from any with more understanding of how Zygote forks (clones?) processes, how apps detect Magisk-in-Zygote (Zygisk), difference with Riru etc.

Current Riru method for injecting into zygote using the "native bridge" is from Canyie (author of Riru-Momohider) and the hidden mechanism for hiding this by making the memory of Riru and module "anonymous memory" hidden from /proc/maps string scanning is from Haruue Icymoon (+ his 22 contributors?)

Is Zygisk injection method essentially the same? And could a similar memory hiding mechanism achieve effective Zygisk hiding?... PW
[Magisk] prot-:
So there's no point updating magisk today if it's just gonna break things and it's already working as is right ?
[Magisk] pndwal:
It's only broken Riru as far as I can tell to date, and there are fixes / workarounds for most functions that relied on Riru already. See this re. Universal SafetyNet Fix 2.x series stop-gaps till we get Zygisk USNF for example:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85825005

Going forward, many modules will likely be built for Zygisk (John already gave tutorial:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85824367 ), and a fix is desirable for current Zygisk detection, but nothing else is broken including Bank apps as yet unless you cannot now hide as effectively from these w/ Zygisk...

The fact that Bank apps will likely build in Zygisk detection as new Magisk gains traction is a valid concern however. PW
[Magisk] martyfender:
A second Magisk alpha was released today and it has been good so far, with one exception, before I re-hid the Magisk app, zygisk did not show as active. Also, after you install the Magisk apk and open it, you now get the update box showing that a Magisk update is available. That is strange, since I can find no evidence of new updates on vvb2060's github page, so where is his alpha channel hosted?
[Magisk] dcarvil:
There is no point in updating if everything works for you. Updating at this time is very likely to break things.
[Magisk] pndwal:
I had similar behaviour w/ TJW build; I didn't hide, just force closed app and opened it again and it detected Zygisk... I think there are issues with new in ap Zygisk detection across builds.

I think Alpha recently only ever showed last GitHub hosted Alpha (b6298f86-alpha here: https://github.com/vvb2060/magisk_files/tree/9f13418f7ce6a47305801ba02433f61d76fd28a4 ) as 'Latest'; It never showed 'Update'...

Is your Update Channel set to Alpha?... May be set to Canary or other...

Also, do App Installed and Magisk Installed versions match? PW
[Magisk] LSS4181:
If MagiskHide is already working for you, don't update to the latest canary. MagiskHide is no more with this version, and Zygisk is still experimental and not compatible with Riru.

I have a few apps that give me a slightly annoying warning if I'm rooted, but do not stop me from using them. Before updating, hiding root with MagiskHide works, that they did not show me the warning, but after updating to latest canary, they do, even after adding them to Zygisk+DenyList. I also tried Riru MomoHider and Riru Unshare but no avail (Momo can see everything), either they need real MagiskHide (which is no more), or I didn't configure them properly, since I only started using Riru very recently (for LSPosed).

Should say that these apps' root detection has nothing to do with SafetyNet, as I'm using microG (with NanoDroid) on which SafetyNet does not work correctly, and I don't need it to pass. SafetyNet is not equal to root detection.

It's not really an issue as I'm not really being prevented from using any apps at the moment, just some minor annoyances. I know it's kind of a transitional period at present, and I'm looking forward to whatever new approaches that aim to achieve what MagiskHide was able to do, and improve it.

EDIT: It seems the most recent Magisk Alpha at the time of writing re-added MagiskHide as a mutually exclusive option to Zygisk, and that works just like before. Don't know how things would work in the future, though.
[Magisk] martyfender:
It is set to the alpha and now I am on alpha 43d11d87 (23010). After updating the apk to alpha 43d11d87 and launching it, the blue update button for the first time in a while, showed up on the upper right, as normal, as in the past, when an update is available.
[Magisk] pndwal:
So you seem to have a network issue if N/A shows rather than b6298f86-alpha w/ Alpha channel set IIANM.

Do you still have blue update button for Magisk? Do you have 43d11d87-alpha for both Installed App and Installed Magisk? Screenshot? PW
[Magisk] martyfender:
My mistake, I did not get N/A with the alpha channel setting, I had looked at the channel settings and changed it to custom channel and forgot to change it back to alpha. (I was just looking at the channel settings as you suggested.)

This was after I had installed the second alpha of today, 43d11d87. And yes it shows 43d11d87 in both the app and Magisk area. And to clarify, if you are not on the latest, 2 alphas were released today: 7496d515 and 43d11d87. The blue update button was gone, as normal, after updating Magisk itself to 43d11d87.
[Magisk] zgfg:
Is there anything essentially new/different in today's latest 43d11d87?

Asking because there are some strange comments on TG about the come back of MagiskHide, but you can never be sure with translating
[Magisk] J.Michael:
I don't think ownership or permissions are your current problem.

The one time I made a "module" to replace some files, I got the permissions / ownership wrong the first time. What I wanted did not work, but the file structure got overlaid -- I could see the files where I wanted them. In fact, when I corrected the permissions under /data/adb/modules/mymodule, the new permissions were immediately visible in the /system tree -- I did not have to reboot.

I don't remember having to "enable modules". Are you sure you have Magisk installed? What does the Magisk Manager app say?
[Magisk] pndwal:
Ah, ok, so all is / was actually working as expected with the exception of App showing no Zygisk until app is shut down / reopened (just fixed reply re. that I messed up above: https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85827451 ) but that seems to be common to new TJW build also ATM.

What you may not have fully understood is that since 'Manager --> App' release v22.0 "the Magisk app (renamed from Magisk Manager) includes everything it needs within the APK itself, making installation a 100% offline process."

https://topjohnwu.github.io/Magisk/releases/22000.html

Ie. since this change "[General] Magisk and Magisk Manager is now merged into the same package!", the Update Channel only affects the App.

After that is updated it won't matter what channel is set to; Install (Or Update) Magisk (mask itself) option simply calls version already downloaded in the same package! - It's not looking for json file / Magisk binary hosted separately any longer... No network access is needed to install Magisk (mask) either.

Nb. John's statement above was not totally accurate at the time as this change initially didn't include stub file, but that has subsequently been included also making it truely "a 100% offline process" now. PW
[Magisk] zgfg:
On the other hand, correct me if wrong, I don't recall a must reason for Magisk switch to Zygisk or at least a decisive explanation about the reasonable advantage of Zygisk model (to validate the issues as introduced)

Ofc, TJW does no more care about detections, hence from his shoes there are no troubles with
[Magisk] Didgeridoohan:
@jnshk I haven't seen you post a single Magisk log. That will probably better show what's going on.
[Magisk] m0han:
installed Zygisk-LSPosed fine. but, don't have (can't get) LSPosed app in drawer. how to get the app running? do i have to extract apk from zip and run it?

edit 1: did this and got things working. but, now i have SafetyNet failing. can you suggest a solution, maybe more on configuring denylist or something? already tried several things mentioned here. my earlier post here.

edit 2: reinstalling MHPC module and rebooting did the trick. passing basic integrity and and cts profile match now. evaluation type - basic.