Magisk General Support / Discussion

[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.
  
  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. ​

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.

 

[pndwal]

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.

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.

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.

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 ).

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.

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.

Total speculation on my part other than deductive reasoning that TJW creating another incarnation of magiskhide would undermines his job is responsiblilties.

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.

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.

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

 

[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 :-(

 

[tronderbataljon]

I have tried the latest fix, but cts profile match is failed... What should I do?

 

[pleasetouchmenot]

Goodbye Magiskhide, Hello Enforce DenyList

 

[pleasetouchmenot]

There's a new update which MagiskHide says goodbye for good.

 

[jons99]

safetynet pass for me as well on android 12

 

[Click Beetle DX]

If it's available still it'll be in /data and if you have a recent Magisk version it should be in a folder named magisk_backup_<checksum>.

It wasn't.

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!

 

[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.

 

[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

 

[pndwal]

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.

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

 

[tronderbataljon]

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.

What am I doing wrong?
Device, Xiaomi Mi 10t
Rom, Evox A11
Modules, RiRu v26. 1.2 + USNF v2. 1.1

 

[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.

 

[pndwal]

@pndwal I think we basically said the same things, just in different ways lol.

I think we're on the same page too.

It was only really this notion that I saw differently:

bobbarker2 said:
... from a practical POV, Magiskhide was/is a required component of rooting and Magisk. Without Magiskhide, a device with Magisk will no longer be able to run a plethora of apps and it will not be Google Play Store Certified.

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:

... it is important to me that Magisk is able to “get out of the way”, so a minor subset of the MagiskHide infrastructure will remain. Users will be able to assign a denylist of processes where Magisk denies further modifications and reverts all changes it had done.

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).

OnePlus owners can thank @osm0sis for PR #90. Safetynet fix is v2.1.1 now.

Yeah!

John Wu

The beauty of open source!

PW

 

[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

 

[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

 

[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

 

[zgfg]

Even i got in on the act and updated to latest Alpha, decided not to be lazy. Enable System Apps, a few ticks for that, a list of Samsung gear...my bank.

Look Marvin, I can haz Magisk Deny and SafetyNet

View attachment 5411513

Now reinstalling modules...

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"

 

[jons99]

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

View attachment 5411513

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

there's already a newer one
in the new one you need to enable zygisk and reboot to pass safetynet

 

[73sydney]

there's already a newer one
in the new one you need to enable zygisk and reboot to pass safetynet

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

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 availbe (and there is no command-line applet for DenyList), but by enabling OS apps I was able to see that Security center apo 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"

Yup, Magisk Detector same same here