yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Partitions such as this may need reflashing if they've been altered / messed up / corrupted by (custom) ROM Installation, use of certain mods etc, so if you suspect this has occurred it may be valuable.

However there is no reason I'm aware of that this would be caused by Magisk installation or use. Ie. Seems to be an unrelated fix. PW
[Magisk] bobbarker2:
I didn't see any real changes in the denylist additions so I didn't think much of them. It's prep for commits to come. I'm all for giving it a chance but I think it more likely that third parties like kdragon will provide safteynet solution rather then denylist.

I'm not in the "Magisk is dead" camp. It's laughable that such a group even exists.

Magiskhide was designed with the goal of hiding the presence of Magisk and the functionality it provides. The denylist sounds like a way for apps to operate as if Magisk isn't there but not to keep the apps from detecting it's presence. Total speculation on my part other than deductive reasoning that TJW creating another incarnation of magiskhide would undermines his job is responsiblilties.

I hope chainfire got paid well for his application. He talked a lot about not being able to pursue other projects because of SuperSU and now that it was off his plate he would be able to but to my knowledge, and I could be wrong, I haven't seen him do much of anything.
[Magisk] ipdev:
Hi all. :)

A bit OT but..

Since there are a few mentioning SuperSU recently.

SuperSU was only a root solution. Nothing about it was hiding.

Chainfire did create a separate app suhide (later suhide-lite) for hiding the su binary.​

So by removing hide from Magisk, it will actually be more similar to SuperSU.

Save for the awesome overlay implementation that allows the easy use of Modules.

+1,000 points to Magisk. ;)​

Chainfire sold SuperSU to CCMT in good faith that they would continue the work..

As far as I know, CCMT only released one update on their own.

It was broken so Chainfire stepped in (took two days for him to fix) and a new release was pushed to PlayStore.

I forgot they put their apology in the SuperSU OP.​

After that, CCMT and support for SuperSU started to disappear.​

Magisk is still fully suported.

Quick highlight of Magisk's growth and development..

Magisk was originally just a Magic Mask.

The systemless overlay that allowed us to modify systemlessly.

Since it requires root, you had to install a root solution.

SuperSU or superuser​

Magisk includes a root solution.

This starts off basic and grows into what is now the magisk su binary.​

Magisk can now hide itself.

This grows into what is/was MagiskHide.​

The next step of growth and development. :unsure:

Every step along the way has lead to an improvement.

As someone who used Magisk with SuperSU.

I am a bit anxious but, more excited to find out. :D​

Note:

This was a quick highlight.

I skiped A LOT.

For a while, the official MagiskManager app was installed from PlayStore.

I do not remember.. Did we pay for it?​

Cheers all. :cowboy:
[Magisk] pndwal:
Yup, WIP, but denylist may simply be a re-badged hidelist and may still be leveraged by hiding solution modules while working out of the box within userspace.

Just meant USNF could be that solution. It's a WIP and so far has adapted with TJW changes / commits. It's certainly the most versatile / resilient / comprehensive hiding solution currently available with proper GitHub repos for other devs to contribute too.

I have no reason to believe that the dynamic nature of USNF will change in the near future, so can't see why we'll need some new 'MagiskHide' module while @kdrag0n is adapting to the changes.

He's apparently indicated his intention to utilise upcoming Zygisk (replacing Riru) as soon as is practical which will likely allow more robust hiding methods to be added also (thanks to TJW changes 😜).

Exactly, but hidelist did have the effect of hiding Magisk's presence and there are not yet any commits or real reasons to believe denylist won't do the same; just no longer a 'hiding' feature per se.

With MagiskHide's requisite additional spoofing / subterfuge gone, the emphasis is simply (properly) being placed on denying ability to make privileged modifications rather to hide Magisk from probes... so far. 😛

Of course I don't know for sure that denylist won't change further, but that would be in the realms of speculation also... Time will tell.

It was a good time (for him and for others) to let young blood in!

He still maintains some interesting projects.

Liveboot (with Magisk support!) is cool:

https://www.xda-developers.com/chainfire-liveboot-cf-lumen-android-11-support/

😜 PW
[Magisk] AndDiSa:
I just installed riru and safetynet-fix-2.1.0 on my Pixel 3a, cleared play store data ... but unfortunately safetynet is still failing (cts profile failure) with eval-type "hardware"! I was expecting "basic" as eval-type here ...

Did I miss something?

Edit: my fault - module was installed, but not enabled :-(
[Magisk] tronderbataljon:
I have tried the latest fix, but cts profile match is failed... What should I do?
[Magisk] pleasetouchmenot:
Goodbye Magiskhide, Hello Enforce DenyList
[Magisk] pleasetouchmenot:
There's a new update which MagiskHide says goodbye for good.
[Magisk] jons99:
safetynet pass for me as well on android 12
[Magisk] Click Beetle DX:
It wasn't. :cry:

Fortunately, after spending a long time searching through various firmware archives, I was lucky enough to find the exact same version of the firmware installed on my phone. Did a "dirty flash" of it, aaaaand... voilà, my phone is up and running again, with all my data intact. Phew!
[Magisk] dewa5227:
1. Toggle on the enforce denyList

2. Click on Configure denyList

3. Choose "Google Play Service" and checklist on "com.android.gms" and "com.android.gms.unstable"

Should do the trick for safetynet. Hope it helps out with the Hysteria of magiskhide is no more.
[Magisk] pndwal:
alpha update log​

Magisk (b6298f86-alpha)​

[General] Based on b6298f86, the content that has been merged upstream is no longer listed

[App] Correctly process any data from magiskd

[App] Support SharedUserId

[App] Delete the backup file after restoring the boot image

[App] Built-in current version update log

[App] Use the local version when the stub cannot be downloaded, now it can be used completely offline

[busybox] Fix the default shell path

[App] Allow the log page to be opened when Magisk is not installed. Although there is no content, clicking the save button will save the app log

[App] Switch to the modern time API of Java 8

[Core] Handling suspicious props

[App] Update the SafetyNet extension, update the version of snet.jar to 18

https://github.com/vvb2060/Magisk/b...b8deb1ce5f4/app/src/main/res/raw/changelog.md

👍 PW
[Magisk] pndwal:
Nb. For devices where Magisk resides in /sbin (many pre. Android 11), only com.google.android.gms.unstable in Google Play Services is needed in hidelist / denylist. PW
[Magisk] tronderbataljon:
What am I doing wrong?

Device, Xiaomi Mi 10t

Rom, Evox A11

Modules, RiRu v26. 1.2 + USNF v2. 1.1
[Magisk] bobbarker2:
@pndwal I think we basically said the same things, just in different ways lol.

For the people posting screenshots of safetynet passing using the denylist, it would be helpful to know what device you are on and what, if any, modules you're using.

OnePlus owners can thank @osm0sis for PR #90. Safetynet fix is v2.1.1 now.
[Magisk] pndwal:
I think we're on the same page too.

It was only really this notion that I saw differently:

because rather than suggesting 'devices would lose ability to run apps / not be certified' due to Magisk and root being unable to be hidden, John himself said:

and he said it from the getgo.

So far things are shaping up this way. Such devices will still be perfectly (maybe more perfectly) able to run those same apps and be 'certified' w/ new denylist.

I / others have been at pains to dispell the negative idea that traditional MagiskHide functionality has been killed off. This is in part because John himself has as good as said it hasn't, will be trivial to restore, and that he's '10000% sure' some 'hiding module' will also 'pop up as soon as possible'.

It's looking more and more as if denylist is and will likely remain pretty much a change in name only while old MagiskHide overt subterfuge and spoofing functions for working SafetyNet have been offloaded (to be easily restored by 3rd party modules). 😀

Yeah! 😛 👍

PW
[Magisk] pndwal:
TJW Commits since Alpha:

Commits on Sep 16, 2021

- Update denylist config implementation

Commits on Sep 15, 2021

- Support enable/disable Zygisk

- Enable Zygisk

Enough said? 😛 PW
[Magisk] zgfg:
I finally updated my Xiaomi Mi 9T, running Xiaomi.eu_Stable, A11 (MIUI 12.1) to the latest Alpha b6298f86.

Thanks @pndwal for encouraging me

With this ROM and with the old Magisk v23 (incl. the previous Alpha versions) I didn't need any modules, spoofing or so - it was simply passing SafetyNet with MagiskHide enabled (and my SN was not affected by the recent Google move on Sep 2 or so)

Now, cat has changed the color (Deng) but it still catches the mice - with DenyList enforced and the usual two GMS processes enlisted, it happily passes the SN again
[Magisk] 73sydney:
Even i got in on the act and updated to latest Alpha, decided not to be lazy. Enable System Apps, a few ticks for Google Play Services, a list of Samsung gear...my bank.

Look Marvin, I can haz Magisk Deny and SafetyNet:)

Now reinstalling modules...

Updated:

Failed to kill anything, even after a full Magisk uninstall and a data/adb/ wipe...all my wearables and Samsung Pay, and bank and Google Pay still work..happy days
[Magisk] zgfg:
Btw, I've slso played with. There is one MIUI app that was not possible to enable for MagiskHide in Magisk v23 official - it was not showing in GUI.

It was only possible through the Terminal, by using magiskhide command line

Ofc, magiskhide applet is no more available (and there is no command-line applet for DenyList), but by enabling OS apps in Filter I was able to see and check-in that Security center app for DenyList

And I tested with MagiskDetector, having the same results as with previous Alpha versions (no better or worse)

And yeah, it says that "Maisk Hide works properly" 🤩
[Magisk] jons99:
there's already a newer one

in the new one you need to enable zygisk and reboot to pass safetynet
[Magisk] 73sydney:
Why of course theres a new one, its been 15 minutes :)

Interestingly, on the changelog, the latest alpha has not got the alpha suffix....im going to leave all that muck to Marvin, the resident release tease to post :)

Yup, Magisk Detector same same here
[Magisk] Eng.Raman:
Magisk 706a4922-alpha Released on the official Telegram channel.

Finally added Zygisk in the Settings.
[Magisk] zgfg:
All modules that I had installed work with no problem for me (only that Repo is removed but IyMHO the old Repo is frozen and there will be no more updatets and new module releases there)
[Magisk] 73sydney:
Ive always loaded form local storage, the only modules that frequently update anyways are MHPC and ACC, maybe Riru...
[Magisk] rodken:
Please share attachment?
[Magisk] zgfg:
Screenshot was in his post:
[Magisk] jons99:
actually it's still getting updates

Magisk-Modules-Repo

The repository hosting Magisk Modules. Magisk-Modules-Repo has 101 repositories available. Follow their code on GitHub.

github.com
[Magisk] pndwal:
Latest @vvb2060 Magisk Alpha (Chinese Translated):​

​

alpha update log​

Magisk (706a4922-alpha)​

[General] Based on 706a4922, the content that has been merged upstream is no longer listed

[App] Correctly process any data from magiskd

[App] Support SharedUserId

[App] Delete the backup file after restoring the boot image

[App] Built-in current version update log

[App] Use the local version when the stub cannot be downloaded, now it can be used completely offline

[busybox] Fix the default shell path

[App] Allow log page to be opened when Magisk is not installed

[App] Switch to the modern time API of Java 8

[DenyList] Dealing with suspicious props

[App] Update the SafetyNet extension, update the version of snet.jar to 18

https://github.com/vvb2060/Magisk/b...7cdf29262b3/app/src/main/res/raw/changelog.md

Telegram OP Notes:

- All ptrace code has been deleted.

- Switch to zygisk to execute the exclusion list, magiskhide has been completely removed. Restart to take effect after changing the switch state of zygisk. Major changes, some problems may occur, temporarily not pushed to the update channel.

👍 PW
[Magisk] 73sydney:
Latest alpha

see @pndwal's post above (which he added while i was uploading) for details
[Magisk] 73sydney:
Anyone else?

Latest magisk alpha doesnt prompt me for su for Viper4Android....even running it ends in no prompt and black screen, severe lag, and needing to reboot

Have tried removing, deleting data folder and reinstalling...

update:

this alpha is doing weird stuff, like putting up the "needs additional setup" prompt, and failing - this after it was working ...

lag on opening already root approved (magisk denied) apps

im reverting to the previous build.....too bleeding edge for me

update #2:

reverted to previous alpha

removed and reinstalled viper4android

rebooted

nope, viper4android still hosed - i didnt test on this alpha after upgrading from the alpha i was holding out on

seem the last alpha is borked for viper as well..

it at least throws up an su prompt on previous alpha...

asks to install driver? wtf? and if you try it says "installation failed at patching system"

oh well, going back to my safety alpha...why did i upgrade again? whos fault is it...ill find someone to blame...

another revert about to happen....
[Magisk] zgfg:
@rodken - You messed something while posting, that were not my words (but yours) - see the screenshot of your post

About the mentioned screenshot with Zygisk - I don't see anything like that on the Alpha Telegram channel (maybe I'm missing something or you refer to another Telegram channel)
[Magisk] zgfg:
I'm still on yesterday's Alpha b6298f86 and V4A works flawlessly (I didn't reinstall but kept all modules that I had before updating the Alpha)
[Magisk] rodken:
I'm having one of those days where I'm trying to jog while I run.
[Magisk] 73sydney:
i decided to full uninstall and clean install...maybe that was the issue, or maybe it got so fudged up by the latest, that when i rolled back to that same build youre referring to it just couldnt cope....im heading back to Magisk-1eb83ad8-alpha-31 for now....i just need stuff to work...

Damn thing has hosed my system totally, not even uninstalling and flashing via TWRP can get me back to it seems, the app says magisk isnt installed....sometimes i hate Magisk....

This is after i:

1) Removed the previous one and flashed the 32 alpha via TWRP...

2) Tried the replace original boot.img and boot patch method

Completely screwed....

Later today ill be doing a backup and clean flashing again...

Actually scratch that, without root, i cant do a backup...

Did i mention i want to kill Magisk about now...

Update:

On a hunch i decided to go back and wipe /data/adb via TWRP...yup, it was still populated

Installed the patched boot image of alpha 31 while i was in there....win...magisk is back

So, yeah, beware the "backwards" (and forwards) compatibility folks with these alphas....

update #2:

All that also borked my google pay and contactless setup, so had to clear Google Play Store/Services and Google Pay and re-add. Luckily it didnt bork my wearables and Samsung Pay.

Id rather be shot than go through all that again anytime soon
[Magisk] klemi71:
Is it possible to rename MagiskAlpha.apk to *.zip and flash it from TWRP like it was on "regular" Magisk?
[Magisk] 73sydney:
Yes, its still the way i do it...

Just be aware you will then need to install the apk after rebooting to system to have the full app

I always have a copy of each

Note:

If you have any bank or root-sensitive apps, after rebooting into system you should remove or rename the TWRP folder
[Magisk] pndwal:
"CRACK"

We have a problem Nigel!

Same same:

- Everything 'keeps stopping'

- Standard clock widget broken

- Magisk needs further setup / fails

- No root apps open incl. Viper

- Other apps fail too

- Screenshot broken

etc.

But wadaya spect? First iteration of Zygisk on bleeding edge Alpha w/ untold TJW added-then-reverted commits...

I'm reverting too for now...

Still, it was worth a crack Nigel! ... just part of life!

Nigel?...

...You don't like talking to me do you?

I'm not getting you down at all am I?... I wouldn't like to think that I was getting you down...

... Life... Don't talk to me about life....

It's the people you meet in this job that really get you down... The best conversation I had was over forty million years ago ... And that was with a coffee machine... Sigh.

☹️ Marvin.

Edit: Revert to previous Alpha went fine for me.. Had to clear Play Store / Play Services for Device certification... Viper driver still enabled / normal...

Coulda been a Zygisk conflict w/ Riru?...

I'm lonely... where's that coffee machine...
[Magisk] 73sydney:
You'll keep Marvin, you'll keep :)

I want points for stopping short of blaming it all on you, you terrible release tease :P

I dunno what the issue was because there was nothing in the magisk log to show any drama, i even read it, and i never read logs :) Note: I stopped short of looking at catlog and finding anything useful, but i want points for just considering it :)

Yours,

Nigel
[Magisk] ipdev:
Not an applet but, you can still do it by command line. :sneaky:

magisk --denylist add com.google.android.gms com.google.android.gms
magisk --denylist add com.google.android.gms com.google.android.gms.unstable

Magisk - Multi-purpose Utility

Usage: magisk [applet [arguments]...]
or: magisk [options]...

Options:
-c print current binary version
-v print running daemon version
-V print running daemon version code
--list list all available applets
--remove-modules remove all modules and reboot
--install-module ZIP install a module zip file

Advanced Options (Internal APIs):
--daemon manually start magisk daemon
--stop remove all magisk changes and stop daemon
--[init trigger] start service for init trigger
Supported init triggers:
post-fs-data, service, boot-complete
--unlock-blocks set BLKROSET flag to OFF for all block devices
--restorecon restore selinux context on Magisk files
--clone-attr SRC DEST clone permission, owner, and selinux context
--clone SRC DEST clone SRC to DEST
--sqlite SQL exec SQL commands to Magisk database
--path print Magisk tmpfs mount path
--denylist ARGS denylist config CLI

Available applets:
su, resetprop

DenyList Config CLI

Usage: magisk --denylist [action [arguments...] ]
Actions:
status Return the enforcement status
enable Enable denylist enforcement
disable Disable denylist enforcement
add PKG [PROC] Add a new target to the denylist
rm PKG [PROC] Remove target(s) from the denylist
ls Print the current denylist
exec CMDs... Execute commands in isolated mount
namespace and do all unmounts

Cheers. :cowboy:
[Magisk] klemi71:
Thanks a lot. That's the way it's done so far.
[Magisk] Chandru123:
So it's best to avoid the latest Magisk Alpha version. Thanks for the heads up @pndwal

Same story in the telegram channel comments section too.
[Magisk] jons99:
new alpha is working fine on my end
[Magisk] pndwal:
706a4922-alpha?

Just curious; which USNF are you using? PW
[Magisk] Chandru123:
I also tried the latest alpha everything was fine. The attestation failed after install, so I installed the latest USNF 2.1.1 and then the SN was passed but all sorts of application were failing. Something to do with the SN fix then?
[Magisk] pndwal:
Thanks for confirming.

Thats what I'm suspecting. Possibly a conflict between Riru Zygote injection and Zygisk's, but I didn't have time for testing.

I'll give it another crack with USNF 1.x series (no Riru) when I get time, (or someone may like to try) since my RN8T is not affected by September Google server end changes anyway.

If this hunch is correct, @vvb2060 may need to fix Riru compatibility, and @kdrag0n will likely move USNF to Zygisk soon anyway. And fwiw, latest USNF seems to be producing stability issues for some w/o Alpha Magisk. PW
[Magisk] jons99:
yes

usnf 2.1 on pixel 5 a12 beta 5
[Magisk] hkdoublecat:
Coukd you hints me where can I find the denylist?

Was not able to search in modules. Really need this to deal with safetynet cts things....

Safetynet fix v2.1.1 didnt work on my oneplus 3t... gonna need to give a go on denylist.

Thanks
[Magisk] zgfg:
Yesterday I posted screenshots

Anyway, Alpha app, Settings, right below Systemless hosts option, you have Enforce DenyList (check-in) and then click on Configure
[Magisk] pndwal:
As mentioned in your quoted post, it's in Magisk App settings assuming you have one of last two Alpha builds.

Nb. You'll need both USNF and the correct processes(s) in Google Play Services (search back) hidden / denied to pass ctsProfile.

If you tell us your ROM and results for evalType and basicIntegrity we may be able to help you further. PW
[Magisk] hkdoublecat:
Thanks but it doesn't work.

Previously my failure was that I installed the Magisk boot iamge but not the App part, now I get both install and now be able to find the denylist. And I look for your post and finish the denylist setting (screenshot 2). Then reboot the devices, still not able to pass the test.

Not sure which part goes wrong. My device is oneplus 3T (A3003) on RR rom V7.0.2.
[Magisk] Stillhard:
Something's wrong with the new alpha handling isolated procs, or is it only me lol
[Magisk] Didgeridoohan:
You don't need Universal SafetyNet Fix on a OP3T... It doesn't have the hardware to do a hardware backed key attestation check.

You might need to use a certified fingerprint though if you're using a custom ROM.
[Magisk] zgfg:
You probably need USNF or so for OP (not familiar with your device), pndwal can probably help you
[Magisk] hkdoublecat:
My device is oneplus 3T (A3003) on RR rom V7.0.2.

basicIntegrity is ok;

evalType is Basic; just the ctsProfile failed.

Play Protect certification: device is certified.
[Magisk] pndwal:
OK, so I've managed to narrow latest Alpha issue down to a compatibility issue with Riru (breaks basicIntegrity) as follows:

- Since my RN8T is unaffected by September Google server end changes, I downgraded USNF to 1.2.0 and disabled all Riru-dependant modules and Riru (still passing ctsProfile).

- updated again to 706a4922-alpha --> SafetyNet passing, system completely stable! 😀

- Enabled Riru (only) / reboot --> basicIntegrity failed, system completely stable.

- Enabled Riru-LSPosed and Riru-MomoHider / reboot --> basicIntegrity failed, system completely stable, LSPosed working.

- Installed USNF 2.1.1 / reboot --> basicIntegrity failed, system completely stable. (Very strange as I'm back to precisely same precisely the configuration i had initially, but somehow it is now completely stable. 🤪)

- Disabled Riru (only) / reboot --> basicIntegrity passes, ctsProfile fails (as expected), system completely stable.

- Disabled Riru dependant modules, Installed USNF 1.2.0 / reboot --> SafetyNet passing, system completely stable.

I only did all this to have something to keep my mind off things. It didn''t work. I have an exceptionally large mind... I guess it beats parking cars...

If this helps someone I shall be slightly less depressed... but no one ever listens.

😐 Marvin.
[Magisk] traversone:
sorry for my question (maybe already discussed): I am not able to install Alpha Version on LOS 18.1 on Samsung S4.

Either flashing in TWRP or flashing patched boot, a bootloop happens.

Am I doing something concettualy wrong?

Thank you.
[Magisk] pndwal:
Likely you had modules installed from a previous Magisk installation that are incompatible. If so, try booting to safe mode (must have Magisk patched boot image installed) to disable modules... PW