[Discussion] Magisk Delta - Another unofficial third-party Magisk fork

Pavilo-Olson said:

If official magisk lets you disable zygisk,

It does...

Pavilo-Olson said:

then yes. You literally just make sure you are hiding root from starling (on official magisk you can do this with denylist i think, but shamiko won't work without zygisk so be sure to enable magisk's own denylist toggle,

...but Denylist requires Zygisk too.

Pavilo-Olson said:

on delta it's "MagiskHide") and reboot with zygisk disabled. Log into starling then when you're in, reboot with zygisk enabled again. When starling gets to one day left on their timer, redo the process.
I did have the Firebase url blocked in adaway, unsure if that's strictly required now but it's probably doing no harm to have it blocked.

FWIW, I've already tried this with my current Alpha Magisk setup which is a POC for the upcoming native bridge Zygisk loading refactoring. It seems it's not yet enough to hide Zygisk from this app, but even initial work is not yet completed

and native bridge compatible Shamiko is also brand new.

I suspect when the final function above and testing are completed and NB Zygisk hits official Magisk (expected with 27.0) Zygisk may be properly hidable finally just as NB based Riru was.

Of course Riru had integrated RiruHide, but Zygisk will always rely on third party hiding going to forward so some further compatibility tweaks for Shamiko will probably also be required for proper Zygisk hiding...

Meanwhile, someone else might be interested in trying official Magisk with firebaseremoteconfig.googleapis.com blocked and @huskydg's p-trace based portable MagiskHide...

Please say if passing PI deviceIntegrity verdict is also needed... (I suspect it will be, but some banks don't check this.) If it is, @huskydg's (improved) forked Riru build and his Riru-based forked safetynet-fix build could also be applied to TJW Magisk...

I may try this when time permits, but real Starling users may have more motivation.

PW

Edit:

Tried this with current Alpha w/ MagiskHide instead of Denylist (Zygisk disabled), and voilà!: ... I can confirm PI deviceIntegrity is not checked as it is failing and blocking firebaseremoteconfig.googleapis.com was not required either... (12 May 2023 update.)