yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
As described in my other post from today, and some from couple of days ago:

- in TheHitMan7 you have working ModulesvRepo

- also MagiskHide (not DenyList)

- but Riru is broken

Currently you must enable Zygisk for MagiskHide but seems he is planning to let Zygisk be optional (MagiskHide working with and without Zygisk)

I reported the issue with WebView to his GitHub and he responded, providing a test build with the fix

Correspondence is in English (he is from India I suppose) and prompt on Telegram, with no troubles and losses in translations between Chinese and English

But there are less number of users/testers

We'll see
[Magisk] rogers11:
Older ctsProfile problems were fixed with this parts: Magisk 23, Riru 26, USNF 2.1.1. Just since today it does not work anymore.

And I know how to use Search and Google. Thanks anyway.
[Magisk] dcarvil:
SafetyNet passes on my Pixel 3 with the latest LOS build with just the MHPC and USNF version 1.2.0 modules - no Riru.
[Magisk] rogers11:
Ok, I will try.
[Magisk] rogers11:
Nope, does not work for me using USNF 1.2.0 and MagiskHide Props with "Force Basic attestation".
[Magisk] Didgeridoohan:
If the only thing that changed between ctsProfile passing and failing was the ROM update, it stands to reason that it's the update that caused the issue...

First thing to try, if you haven't already, would be to toggle MagiskHide off and on again. If things still doesn't work after that it might be something about the ROM itself.
[Magisk] rogers11:
Yes, I tried toggling MagiskHide off and on again in the meantime. Unfortunately no change. Many thanks for your help.
[Magisk] rogers11:
Finaly have success with:

Magisk 23

Riru 26.1.3

USNF 2.1.1

MHPC 6.1.0 (device fingerprint set to Pixel 5)
[Magisk] Didgeridoohan:
Why not use the Pixel 4a print?
[Magisk] rogers11:
Don't know exactly 😀

Changed this now, same result. Thanks again.
[Magisk] ipdev:
OT but, just to clarify..

Didgeridoohan was correct, it is currently on the lineage side. ;)

Checked lineage's Pixel 4a sunfish repo.

LineageOS - GitHub - sunfish make file history - Link

The build fingerprint for sunfish has not been updated yet.

The mismatch between the build fingerprint and security date will fail cts.​

Until the build fingerprint is updated, you will need to use MHPC to set the build fingerprint.

Note: MHPC also sets the security date to match the fingerprint set.

Cheers. :cowboy:
[Magisk] ipdev:
Note from John's repo.

// Riru and its modules are not compatible with zygisk

Magisk - GitHub - module.cpp - Line 704

Before you could disable zygisk and Riru would work but..

Magisk's DenyList would be disabled since it requires zygisk.

With the newest commits (and the shift to zygisk).

Magisk - GitHub - commits - Link

Riru will not run even if you disable zygisk.

Gives error about zygote not running.

Cheers. :cowboy:
[Magisk] zgfg:
There was a similar discussion about the disabled Riru on TheHitMan7 TG channel

But for the matter of fact, in Alpha Riru works and with Zygisk - as posted here previously I use:

- Riru

- Riru-Momohider with isolated option enabled (hiding su in the path)

- Riru-LSPosed with GravityBox-R and CustoMIUizer modules

It worked with the Riru and LSPosed versions from the beginning of the month and with the latest as updated two days ago

And of course, with Zygisk enabled
[Magisk] pndwal:
@ipdev, @zgfg

Yup, Riru and Zygisk coexist again and work well (with exceptions like some MomoHider configurations) in last two Alpha builds since this change:

👍 PW
[Magisk] wilsonhlacerda:
Well, it took a while but I can confirm: Magisk Alpha does have some bug while patching boot (maybe for a few devices?). At least when in comparison to Stable Magisk v23.

> Samsung S4 Mini Dual SIM (I9192)

> Official TWRP 3.5.2_9-0

> I've completely clean flashed LOS 14.1, 16.0, 17.1, 18.1 (Android 7, 9, 10, 11), formatting data and everything. No encryption. Tried both Magisk v23 and Magisk Alpha with all of them just after fresh install, each one.

> It always boots fine with default system (no Magisk yet). All Androids work as expected.

> It always install and boots fine with STABLE Magisk v23 (both flashing zip on TWRP or patching boot.img and then flashing patched on TWRP). All Androids works rooted as expected.

> Magisk ALPHA: seems to install zip fine on TWRP, but CANNOT boot. Freezes on the "Samsung" logo.

> Magisk ALPHA: seems to patch fine boot.img, but after flashing patched image CANNOT boot. Freezes on the "Samsung" logo.

The way Magisk Alpha is patching boot.img is the problem. The patched image freezes the S4 Mini (I9192).

Thanks again @zgfg but it seems Magisk Alpha developers will have to check that.

By the way, there is no /cache/magisk.log with Magisk Alpha. Probably because boot freezes at the very beginning.
[Magisk] rodken:
Is this the same build from September 26th?
[Magisk] zgfg:
Latest Alpha is from TG, Oct 4, and we use that one with Riru
[Magisk] rodken:
Even after updating Riru and LSPosed [Canary Build] to the lastest - I believe that my issue is still ROM/Device specific.
[Magisk] raulci:
Thanks a lot for the hint! It happened the same to me.

Just some questions/comments:

I just installed LsPosed from Play Store without uninstalling first the one from Magisk. Both versions were already 1.6.1 (latest). Don't know if required, but it works anyway. If I look for LsPosed in Settings > Applications, I just find the one installed from Play Store. Is this procedure correct?

If I had uninstalled the previous one, I'd have lost all my LsPosed config?

Ah... Another thing, I noticed that the contextual menu from the Play Store one is showing options while the Magisk one doesn't. Maybe related to our initial issue with CustoMIUIzer?
[Magisk] zgfg:
If both show 1.6.1 (6132), it should be ok (the latest).

One can be the icon, the other shortcut.

For shortcut you have only Remove (on long press).

For icon you have Modules, Log, Repository, plus Share, App Info, Uninstall

Btw, you don't even need the shortcut - you can invoke by 'dialling' the secret code *#*#LSPOSED#*#* (L=5, S=7, P=7, etc)
[Magisk] raulci:
Thanks, as you said, I forgot to create the shortcut, but when I did it and uninstalled the manager, CustoMIUIzer started complaining again regarding no xposed installed... 🤔

How did you manage to use the Parasitic manager without getting CustoMIUIzer warning? Maybe I need first to uninstall LsPosed from Magisk?

Anyway, I suppose Mikanoshi may do something to support Parasitic LsPosed. I will post the suggestion in CustoMIUIzer thread.

Thanks!
[Magisk] zgfg:
For me it's the same. It complains if I uninstall LSPosed Manager but it works.

I can still open the manager from shortcut and by calling its secret code, and the mods I enabled in CustoMIUizer and GravityBox box do work
[Magisk] U600:
Hi, I have a problem with Magisk, I have always used custome DNS plugins ( https://xdaforums.com/t/module-cloudflaredns4magisk.3772375/ ) without problems but with the latest LineageOS updates these modules no longer work. I tried to re-install magist from both TWRP and Manager but the modules still don't work. At boot magisk wants to install an additional configuration but it fails. I attach screenshots. Probably something has changed in the latest releases of Lineage OS but initially I write here to better understand where the problem could be. Any ideas on why? Phone = Redmi Note 8T (Ginkgo).and where the problem could be. Any ideas on why? Phone = Redmi Note 8T (Ginkgo).
[Magisk] pndwal:
Well Redmi Note 8T is Willow, not Ginkgo for one. 😛

Many Ginkgo ROMs work for Willow however, but any stock firmware / vendor etc upgrades should be for Willow.

Haven't tried LOS on my 8T, but note there are a number of issues with LOS 18.1 still current. This one and / or others may be affecting you:

https://github.com/topjohnwu/Magisk/issues/4394 PW
[Magisk] U600:
You are right 8T is Willow. Fortunately for LAOS ginkgo and willow have the same release. I have been using LAOS for many years even when it was called Cyanogenmod and I have always liked it but lately I have a few more problems.It's a fairly light ROM and I like it for that. Back on Magisk I read the linked post and it seems the same problem. However, plugins worked for me before. This summer I used Viper Audio and Cloudflare DNS with 18.1 with no problems with the same Magisk package. The problem arises when doing phone OTA updates. Not only does Magisk no longer work but often the phone does not boot the new release. So if the problem is not on Magisk it could be TWRP or more easily some changes to LAOS that partially invalidate the functioning of Magisk. But at this point I ask in the LAOS discussion.
[Magisk] :
Need Help.

Problem persist on 3 devices.

2 devices dirty flashed ROM, gapps, Magisk and 1 device clean flashed ROM and Magisk (no gapps)

Unable hide magisk app with different package name. I tried different old versions too, but facing similar problem.

I also tried setting "play store security off" and "selinux permissive" from selinux switch app but that also did not helped.
[Magisk] J.Michael:
Search this thread, lots of suggestions.

Simplest probably shut down, boot to Safe Mode, shut down, boot -- all modules should be disabled but Magisk should be running, so you can permanently disable or remove problem module.

Worst case: Wipe data / factory reset, start over.
[Magisk] elong7681:
Thanks for your help it worked.
[Magisk] zgfg:
Clarification comments from LSPosed team (still about the future Magisk)

Attaching as a screenshot since links to TG are not allowed (frankly speaking, this 'purity' in XDA policies becomes pretty annoying to me)
[Magisk] pndwal:
@yujincheng08

Great to see you active here, and especially your early issues for Zygisk and pull request fixes for webview, logging, modules and DSU in TJW GitHub! ...

We're all watching / anticipating new LSPosed / Magisk compatibility also...

Thanks, and love your work! 👍 🙂 PW
[Magisk] 73sydney:
So basically Zygisk is evil and breaks everything as it currently stands, got it :)
[Magisk] pndwal:
So you raise the question of whether evil can be reformed. (Can't resist this. 😛)

If evil as it currently stands, can it ever be good? - If not, the evil will need to be eliminated...

But I suspect Zygisk will win in the end, either existing harmoniously with Riru, or replacing it fully in the long term... and everything broken may well be fixed, at least till G swing their Hardware TEE wrecking ball...

Seems LSPosed rep commenting there hasn't yet considered vvb2060's conclusions:

-cb4361b7-alpha

• [Zygisk] Judging from the current situation, there is no crash report to prove that zygisk is incompatible with riru, temporarily cancel the restriction and observe the situation

-cb4361b7-alpha-2

• [Zygisk] There is no report to prove that zygisk is not compatible with riru, remove the restriction

Some are just now commenting on this in LSPosed Telegram group, and @TheHitMan is now working on overcoming incompatibility...

I think it's too early to stone Zygisk dead personally... If we take the LSPosed statement above at face value, RIRU is dead already!

AFAICS, no such assassination of either Riru or Zygisk may yet occur. - Are they really rivals anyway? I think John is digesting all possibilities, and that unforseen way's of hiding Zygisk (a major difficulty) may well emerge also.

But if you are correct the conundrum is a great one to ponder: Can an Evil entity change stance, become Good, and be considered Evil only as it formerly stood?

- Not sure why you have reduced this to an ethical dichotomy, but my confidence is that Good will win in the end... and you can't lose either, if you have one ounce of NIGEL AFFECT. PW
[Magisk] jons99:
new alpha is out and working fine with riru and zygisk working together fine as well
[Magisk] 73sydney:
Pretty brave paragraphism on a partially tangental reply :)

Just saying, it would be nice to get some good news for a change

Blindly flipping switches on stuff doesnt seem to be working well for most people.

If people are designing one thing (zygisk) to disable the functionality of another thing (riru), it should be made abundantly clear up front, so that people arent wasting their collective time trying to put square pegs in round holes...

As someone who needs momo-hider level hiding in their daily lives, its a lot of work trying to sift through whats going on

Long live (vvb2060) magisk alpha 31, for it still provides...

See you soon in Zygote Game, ill be wearing a tracksuit, and be badly dubbed (even in English)

..Nigel..
[Magisk] 73sydney:
thats more like it...but will webview work with riru mods installed

i await Marvins testing :)

Might have a go myself
[Magisk] xk00l:
How to install abfb3bb3? John says he pushed the build but it's not seen in the app and I can't install it from GitHub manually.
[Magisk] pndwal:
Well he didn't say 'pushed a build'. Said 'the code' (no release yet):

Gotta be close though! 😛

... Gonna build it @ipdev ? 🤗 PW
[Magisk] pndwal:
Pretty brave calling Zygisk Evil too mate! - Look up; it's the biggest ship on the horizon now!

Anyone using Alpha is a maverick who oughta be expert at fitting multiple square pegs in round holes, but you're welcome to keep playing with your peg board. - Just don't miss the good news for a fixation on finances!

I'll be playing Zygote proper soon I hope, wearing winklepickers and a waistcoat; the banks can go jump. 🧀 / 🍰 PW
[Magisk] pndwal:
Latest Alpha report (w/ RN8T):

S/N ✓

LSPosed ✓

Viper4Android FX ✓

Webview ✓

MomoHider w/ all 4 hydetypes X

- breaks widgets, apps, stability.

- next reboot breaks Zygisk

MomoHider w/ initrc, isolated ✓

(w/ or w/o Riru - Enhanced Mode for MH)

Riru - Enhanced Mode for MH only ✓

😛 PW
[Magisk] 73sydney:
Good info Marvin

You beat me to it...in the middle of restoring apps after a clean flash....Momohider config noted, will test same
[Magisk] Newtonsart:
How can I pass safetynet with latest alpha version??

LSposed is working fine with zygist but xprivacylua does not work while trying to pass safetynet as it used to do
[Magisk] zgfg:
What's going on now - SafetyNet in Magisk (Alpha) still passes but all others I tried fail (Signature verification)?

How come that only SN checker in Magisk app does not have a problem?!
[Magisk] ipdev:
Nope.

A quick commit was added after that one.

Just a message line change

The new head is "8276a077" and yes I did. ;)

Cheers. :cowboy:

PS.

MHPC - Post 5,710

Look in the hidden box. :sneaky:
[Magisk] jons99:
new alpha is out and safetynet check is no more

so don't worry about it

I think it's an issue with googles server
[Magisk] Newtonsart:
Latest magisk alpha isn't passing safetynet. I have Safetynet fix installed but it isn't passing basicIntegrity
[Magisk] 73sydney:
Exciting news Marvin, Magisk (abfb3bb3-alpha) (from the Telegram Magisk Alpha group, and hopefully not to confuse folks using the other (mainstream) alpha from the original repo) is workies on my devices of many needy apps

First time in a while anything above (vvb2060's) Alpha 31 that has worked for me.

Even with having to manually denylist apps anew because the old magisk.db wasnt compatible and i couldnt just copy my usual one over, i still managed to get everything working without any apps seeing anything - shall back this magisk.db up for new experiments (and because im lazy)
[Magisk] zgfg:
Latest Alpha 8276a077 does not have SafetyNet checker anymore!

You must be running an older Alpha (maybe abfb3bb3 that was also released today but earlier - now no more the latest)
[Magisk] 73sydney:
fwiw, on the TheHitMan magisk alpha theres still SafetyNet test, and it returns a valid test result (pass), both the other SafetyNet testers i have installed (SafetNet attest' and YASNAC) fail to return a valid reply...response signature invalid...
[Magisk] zgfg:
I suppose that for those here who still run Stable (or Canary), Safetynet checker in Magisk app would also wrongly show SN pass

There is a problem with Certificate expiration (attachemnt below from TG), seems that TJW's implementation does not properly look into the Certificate

But some say that if you wipe Data for Google Play Services), that SN in Magisk will also fail (hence there is some improper caching)
[Magisk] Newtonsart:
I stalling the latest magisk release broke magisk lmao

I'm attaching magisk log
[Magisk] martyfender:
I'm pretty sure something is going on on Googles side. I have one device that is on an older Magisk alpha cb4361b7-alpha-2 and it passes safetynet test in the Magisk app, but fails on 3 third party safetynet tests. This is also true on another, same device, with the latest 2 alphas.
[Magisk] ipdev:
Yep.

Starting today.

SafetyNet is failing across the board for me. :(

PlayStore still shows certified but, I am sure that will change the next time Google scans the device(s).

(Edit. Then again, maybe not. :unsure: See PPS. and my next post.)

Cheers all. :cowboy:

PS.

Just like last time, prepare for multiple reports everywhere about failing SafetyNet. 🙃

PPS.

Then again, this could also just be a change in Google's SafteyNet like last time.

[When SafetyNet checker apps had to be updated.] :unsure:
[Magisk] ipdev:
Quick test on my OnePlus 5T.

Stock OOS 10.0.1

Magisk canary

Even after clearing cache and all app data from PlayServices and PlayStore.

Reboot and give it time for Google to update PlayServices and PlayStore.

Magisk shows passing SafetyNet when other SafetyNet checkers have errors.

PlayStore came back as certified. ;)

Cheers. :cowboy:
[Magisk] zgfg:
There was later today one more Alpha: 8276a077

Anyway, where can I see vvb2060 commits for his Alpha releases on TG?

Bcs, by looking to his commits here, I cannot find any branch with the commits newer than from the last month:

Commits · vvb2060/Magisk

A Magic Mask to Alter Android System Systemless-ly - Commits · vvb2060/Magisk

github.com
[Magisk] purgy:
Re: riru vs zygisk, according to the lsposed tg, they've got an unreleased build that runs on zygisk without the need for riru at all.

Will be interesting to see how it all pans out.

Funnily enough, the services nsw check-in app is more concerned (even before the vaccine proof stuff) with sn status than CommBank.
[Magisk] zulu88:
Everything is fine in the stable version.
[Magisk] martyfender:
3 out of 4 safetynet checking apps are once again working correctly, so the problem appears to have been on Google's end.
[Magisk] pndwal:
Yup, I scoured his GitHub with amateurish skill 🤪 and never found public comitts since he started supplying open source in .7z files. He commented re. this at the time but implications were lost in translation for me...

I haven't checked open source archives, but I guess these substitute for GitHub commits for those able to navigate them... @ipdev may be better able to inform you about checking source code. 😐 PW
[Magisk] pndwal:
For what it's worth, I think Google end issues have simply been a bit of a smokescreen; There is no real issue with recent changes in Magisk, custom, Alpha or otherwise...

Seems YASNAC's timely appearance has been in anticipation of removal of Check SafetyNet Magisk function, and w/ Evaluation type and extra checks Magisk check is really redundant anyway... PW
[Magisk] zgfg:
Now, upon both me and the phone slept over the night, all SN checkers pass for me again - hence, the 'crisis' is over, and something was going on the Google side but now is ok again
[Magisk] archz2:
I have OnePlus 5T running stock Oxygen OS 10.0.1 with Android 10. I have magisk 23.0 and also have magisk hide enabled. I have Universal SafetyNet Fix 1.1.0 flashed via Magisk. I also have EdXposed v0.5.22_4683 (YAHFA) and Riru v.25.3.4.r39984f7084 installed on my phone.

I'm still not able to pass safetynet check. What should I do?
[Magisk] Didgeridoohan:
The OnePlus 5T doesn't need the Universal SafetyNet Fix, it doesn't do hardware backed attestation (I'm using a 5T myself). A likely suspect in your case would be EdXposed, but there can of course be many things that trigger SafetyNet...

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] Newtonsart:
I have a Samsung note 10 lite.

Safetynet fix installed and I did the XPrivacyLua thing, it's not even passing the basic integrity.

Any help?
[Magisk] 73sydney:
@pndwal, all

Just a quick note to say that despite being certified immediately after that (second to?) latest magisk alpha install, when i went to use Google Pay today, it straight up told me that contactless wouldnt work as i was rooted. A quick trip to airplane mode and clearing of Google Pay, Google Play Store and Google Play Services, reboot, airplane mode off and card re-adding, all was well again...

I suspect that when people are getting frustrated with not being able to get Google Pay, and they use my module, this is all thats (needed, and) happening in the background to make it work...

Still happy...this is rare :)
[Magisk] 73sydney:
Not surprised here...
[Magisk] MoL_82:
Oxygen is a custom ROM, so you'll need Magisk Hide Config Props to spoof fingerprint.

Universal SafetyNet Fix needs to be updateted to latest version, 2.1.1.

EdExposed has not been updated for a while and is breaking SafetyNet for some time now as well. I suggest you switch to LSPosed.
[Magisk] MoL_82:
XPrivacyLua via EdExposed or LSPosed? If EdExposed, that explains the Basic Integrity fail.
[Magisk] pndwal:
If on stock (certified) ROM, try with Universal SafetyNet Fix 2.1.1 & Riru modules only (disable ALL others).

Disable the others, toggle MagiskHide off then on again in Magisk App settings and clear Google Play Services data before rebooting. PW
[Magisk] pndwal:
Good points above!...

But I think OxygenOS is OnePlus's stock OS for Overseas market and should come certified (unless some builds were for China region).

I understand their HydrogenOS (for China market) to be uncertified, and that they lately moved to ColorOS for China region. PW
[Magisk] Newtonsart:
LSposed
[Magisk] Newtonsart:
Yep, I did all that. The thing is that I'm using latest alpha update so no way to enable/disable magiskhide
[Magisk] archz2:
I have only edexposed on my phone. I don't have LSPosed. Okay, I installed Universal SafetyNet Fix 2.1.1 before reading your answer and I was still getting the trouble.

So, now can I install LSPosed directly on my phone or should I uninstall edxposed and all its modules first?
[Magisk] MoL_82:
EdExposed should be uninstalled. To be honest, I am not sure if you need to uninstall all the modules, as they also run under LSPosed. Maybe it is possible to just reactivate the modules when you got LSPosed. Different in LSPosed, opposed to EdExposed, is you have to check for which apps the module should be active.

Maybe the best way is to first check if you pass SN without EdExposed and is that works, try it with LSPosed.
[Magisk] archz2:
Okay so I turned off EdExposed with Magisk and rebooted my phone. I was able to pass safetynet flawlessly!

So now I can uninstall edxposed within Magisk UI only, right?
[Magisk] MoL_82:
In Magisk you can uninstall EdExposed. Not sure if the app is also automatically removed, but that can easily be done, if needed, after EdExposed is uninstalled via Magisk.
[Magisk] archz2:
Okay. Thanks!
[Magisk] pndwal:
Ah, you need to say, otherwise it will be assumed you have a TJW build.

In Alpha, you need to manually add the Google Play Services SafetyNet process to the DenyList, and possibly the main Play Services process.

Adding this (or both) to hidelist was a main function MagiskHide toggle. That's been removed for future builds by John, but processes can be easily added to new denylist to achieve at least that function (hiding root from processes) of MagiskHide.

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. To find 'Google Play services', first, click the spyglass symbol at the bottom and select Show system apps.

👍 PW