yashsingh1/xdaforums huggingface dataset:
[Magisk] konaeru:
ohhhh, i forgot to say, after you install magisk, don't restart ldplayer immediately. Delete the su file before restarting, because if Magisk is already running, the su file cannot be deleted.
[Magisk] konaeru:
install magisk first then delete the su file, then restart.

I hope you understand, because my english is very bad.
[Magisk] famaTV:
YOU ARE A LEGEND!!

A TRILLION THANK YOU MY FRIEND. THAT WAS A GREAT HELP!!
[Magisk] DIXES:
It seems that Ruru is still able to detect the hidden Magisk Manager (I use 25.2-delta-5).
[Magisk] zgfg:
I use HMA and Ruru finds nothing (neither Oprek, TB- Checker nor S-Check)

With congrats to the first semi-finalists👍
[Magisk] famaTV:
Use 'Hide My Applist' app to hide the hidden magisk from any app you need.

Edir: Sorry, answered above.
[Magisk] amritpal2489:
It seems my device is rooted but Magisk is showing Installed status as NA

What should be done in this case?
[Magisk] pndwal:
Man, you pop up everywhere!...

Are you using Delta Magisk?

Did you root using P7P boot.img on P6P in the end?... Cos N/A is what A13 QPR2 Beta 1 users are getting otherwise unless you did a full data wipe (some report success with clean ROM install)...

if you think you really succeeded rooting, a previously hidden Magisk (stub) app that failed to uninstall when you reinstalled Magisk could be the issue; just locate and uninstall that... PW
[Magisk] amritpal2489:
Desperate times buddy :D

I rooted using the 7P boot.img

Pixelflasher shows as rooted. Even banking apps are giving root error but Magisk is showing the N/A error. How do I locate that stub? Any ideas?
[Magisk] pndwal:
It will be what you previously named it... If can't find in launcher, look thru device settings, apps...

To be sure of root, in a terminal emulator app you can type magisk -v to return running daemon version, or

Magisk -V to return running daemon version code... PW
[Magisk] amritpal2489:
Thanks a lot buddy... I don't know how but All is Well all of a sudden..
[Magisk] pndwal:
What did you do before losing N/A? PW
[Magisk] amritpal2489:
I was doing lots of things simultaneously.. flashed P7P boot.img.. installed various versions of Magisk.. etc etc..
[Magisk] xChickens:
Could I also get the link please? Thanks!
[Magisk] Arealhooman:
Oop lmao i forgot to share it. I do not ahve telegram in Thai device, il send tomarrow
[Magisk] AboAnas25:
I can't hide root for this bank app

I tried everything but failed to run it

Other banking apps running smoothly except this app after last update

If anyone can help me to hide
[Magisk] a_khusairi:
app can work
[Magisk] AboAnas25:
Thank you bro

Already I am using Hide myapplist but this bank app still feeling root!

What is this version of Magisk because this is not English?
[Magisk] a_khusairi:
Canary version of Magisk Delta https://huskydg.github.io/magisk-files/
[Magisk] AboAnas25:
Now I have another problem 😁

All apps in magisk hide list are freezing if Zygisk enabled
[Magisk] a_khusairi:
do you use shamiko on magisk module?
[Magisk] AboAnas25:
Yes
[Magisk] a_khusairi:
I don't use the shamiko module
[Magisk] UZP:
My latest Magisk is version 23 (Android 9). Everything was simple there, I had modules based only on Riru :

Riru, Riru-Enhanced mode for Magisk , Riru-LSPosed and Universal SafetNet Fix 2.3.1 ) + Busybox for Android NDK , Move Certificates.

Everything worked without problems.

Now I changed my phone (Android 12), I have TWRP recovery and I want to install Magisk 25.2-delta-5

and here I have a problem: but I don't know which modules to choose: based on Riru or Zygisk?

Something that will be relatively easy to set up

The more I read the forum the less I know what to choose

Can I install a module based on Riru and Zygisk at the same time?
[Magisk] 73sydney:
@huskydg does make efforts to give you choices, based one what you decide to use (zygisk or riru) based on toggle in the magisk manager app.

one especially handy and core module that will install in either context is

GitHub - HuskyDG/safetynet-integrity-fix: A workarround to pass SafetyNet / Play Integrity API on rooted devices with unlocked bootloader

A workarround to pass SafetyNet / Play Integrity API on rooted devices with unlocked bootloader - GitHub - HuskyDG/safetynet-integrity-fix: A workarround to pass SafetyNet / Play Integrity API on r...

github.com

this gets you a good long way into having your device certified for Play Store and as a basis for banking apps/ google pay

its still a personal choice as to which path you go down, zygisk or riru. banking apps are probably the one area where you might find a difference. if in doubt, for easiest setup i would probably go with what the person i know who uses Magisk Delta most goes with, and thats Zygisk:

Zygisk Enabled

MagiskHide Enabled

from there depending on the apps you have, you may wish/need to explore using Hide My Applist (guide here) running under Lsposed Zygisk from here (few builds behind Telegram builds)

So a provisional module list, for easiest install, might be (zygisk):

- Magisk Delta latest

- HuskyDg's Universal SafetyNet Fix (after install of which... put phone in airplane mode, clear data for Google Play Service and Google Play Store, reboot, and take device off Airplane Mode. And confirm Integrity Check. This procedure is standard for new Integrity Check using ANY (current) Universal SafetyNet Fix build, not unique to huskydg's)

- Busybox

- Move Certificates

Optionally:

Lsposed (Zygisk)

Hide My Applist
[Magisk] m0han:
👍 I guess users here would appreciate @huskydg sharing his opinion also on the pros and cons of Zygisk vis-a-vis Riru.
[Magisk] 73sydney:
Absolutely, i was just responding to the "easiest way" portion of the question :) And also based on the usage experience of the most well known user of Delta that i know
[Magisk] S.N.A.P:
First of all, thank you for this great variant of Magisk, from a fellow countryman, also pardon me if my question was already asked somewhere since I can't seem to find any

Do Delta-5 and MIUI really work with each other or not? Since I clean flash ROM, Magisk, kernel before first boot, after a while it just shows like the ss

Device : K20 Pro

Running MIUI 12.5 custom ROM, custom kernel

Same set of modules, same method of flashing as on AOSP but no issues on AOSP

Any help would be highly appreciated
[Magisk] zgfg:
I have two Xiaomi phones, one K20 (not Pro) also with MIUI 12.5 and Delta works fine for me

I always install Magisk by patching and flashing (although installing through TWRP should also work) and it works fine for me

Try again with clean Boot but without installing your custom Kernel - maybe its installation messed up your (patched) Boot, similar things were reported here and there

Also, make sure that there was no left-over hidden Magisk app (causing your new Magisk app to declare Magisk N/A). Although not likely if you clean flashed MIUI (ie, if you did Factory reset) - you could try su from Terminal emulator to see if Magisk is installed but Magisk app not detecting it
[Magisk] martyfender:
This app runs fine for me with Magisk Delta, zygisk lSPosed, hide my applist and and huskydg USF mod. with both zygisk and magiskhide turned on and the app added to the hidelist and added in the app section of hide my applist and using my default template. Of course, I am in the US and don't have an account there, but I do get to the login screen and get a rejected login from the wrong, (of course) user name and password. But I do not get any message that my device is rooted.
[Magisk] mhd_atzh:
I have trouble configuring Magisk Delta.

By Default, After flashing safetynet breaks. I turn on Magisk Hide and it to denylist, without which Momo detects root. And then add the UNSF Modded Module. (Zygisk) - which ofcourse needs Zygisk turned on, for Safety net to pass.

But when both Magisk Hide & Zygisk is enabled, those apps in the denylist when opened crashes, always. Until I disable Magisk hide.

The Only Module - I had is USNF. Adding Lsposed and Using Hide My Applist doesn't solve the problem. I believe they are not part of the problem. But just confirming, that I tried adding and removing application form HMA, and nothing worked.

Unfortunately, I searched the whole thread. And couln't find anyone having this faced earlier. Or reported with a solved.
[Magisk] huskydg:
Lack of imformations, no logs provided. Waste my time. You better not to use magisk delta if you don't even provide me proper information.

Thanks!
[Magisk] huskydg:
PLEASE DO NOT REPORT BUG ON XDA THREAD!
[Magisk] 73sydney:
Sorry, but i dont think you can demand that no one submits a bug report here, my understanding is if you link to your work from here, you need to be willing to provide support here too. For example while I suggest people use my github to report an issue as it probably easier to track (especially for me, and as its easier to search for issues there), but i dont tell anyone its the ONLY way to do it and that they can still post here.
[Magisk] 73sydney:
I havent seen your particular issue either, and thanks for even attempting to search (doesnt always happen)

Can you please provide:

Device name:

Android version/ROM:

And:

Exact versions of Magisk and all modules (be specific) and even where you might have downloaded them from.

The basic working platform to get to is working Magisk and USNF, so leave Lsposed and HMA out of the equation for now

Also Safetynet is (on its way to) being deprecated and a new test Integrity Check is (slowly) replacing it, and we now test for that too with this

Play Integrity API Checker - Apps on Google Play

Get info about your Device Integrity through the Play Intergrity API

play.google.com
[Magisk] m0han:
From what I have seen in discussions on various threads here on XDA, not many people have a GitHub account and not many are comfortable with Telegram app.
[Magisk] 73sydney:
yup, which is why support is still valuable here.
[Magisk] asripath:
See post 1

Clearly says not to report bugs on XDA.

You can't have rules for thee and not for me !
[Magisk] mhd_atzh:
Hey, I'm sorry. Didn't mean to be rude. I appreciate your efforts. I didn't know how to report an error. Couldn't find a link to any Telegram Group or anything in the thread on how to report an error, I searched focusing on the errors I had. And didn't recognize the 1st post, either. Extreme Apologies.

Thanks for the patience. I'm sorry I missed the details. I almost gave up. As people from my device community hadn't faced this either. And didn't know XDA people are active - I mean I wasn't for a very long time. So yeah...sorry again.

Device Name: Poco F1

Android Version: 13

ROM: crDroid 9.0, I also tried in Arrow OS 3.3

Magisk Delta Version: Tried the last 2 latest Canary Build and delta-5 as well

Magisk Modules : UNSF / LSposed / Custom Font Module / Systemless Hosts

This is the issue :

1. Enabled Zygisk & Magisk Hide - Apps Marked in denylist crashes on open

If its fine, I would get the logs and attach them here. Or any medium, that I could. I'm new to Github, but still couldn't find which repo to report on.

As on the Play Integrity API Check:

MEETS_STRONG_INTEGRITY Fails, other pass - And also PlayStore says my Device is not certified - is that the issue?
[Magisk] mhd_atzh:
Hey,

Update :

1. Issue seems to be with Custom Font Module - And I'm not sure, why it fails with that.

2. But this time, I ran Play Integrity Check all fail

3. Momo works fine, doesn't detect su / Magisk / Zygisk

4. YASNAC works - Safetynet Passes

Should I be concerned that Play Integrity API all check fails ?

I'm sorry, I'm posting my updates here. If there's any other medium to post and share messages and on how to do so, I would do there and the same way.
[Magisk] 73sydney:
First things:

1) disable any module except for USNF

2) going on your Integrity Check reuslts, you are likely using a later version of USNF (you really need to list version of modules etc specifically), can you confirm its one of the versions from here:

Releases · Displax/safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk - Displax/safetynet-fix

github.com

If it isnt, please download the latest (mod 2.1) and flash that over the top of the existing one

3) if so, to get Play Store to certify

- put device in airplane mode

- force close and clear data for Google Play Services and Google Play Store (extra warning as a Galaxy Watch owner, if you have a Watch (and i suspect the same is true of the Pixel Watch) once you clear Google Play Services, it will sever the Watch conenction, meaning you will need to reset the Watch, and set it up again. )

- reboot device

- take device off airplane mode

- wait a few minutes and then check Play Store, it will NOT say certified for some time, but as long as it shows version and NOT "not certified", youre fine

The above are the basics to have working root with a certified play store and passing SafetyNet and Integrity, i will NOT promise you it will remedy in any way the crashing youre having when launching the apps as there may be a device/ROM issue, especially on custom ROM's as we dont know what the dev has cooked into them that may help/hinder root or root hiding. We often see LineageOS ROM's sometimes having issues, and CrDroid and most other custom ROM's are based off it. Sadly its not a device i own to be able to test personally

Once you have Play Store certified, try clearing the app data for one of the apps that has crashed and see if that does anything at all
[Magisk] m0han:
From 'just before the op made the post' on, maybe?
[Magisk] 73sydney:
People think font modules are benign, but they can mess with the system, and can give up the presence of root, but not to the point of crashing other apps

Theres only one font module from memory that doesnt give up root detection, but i cant remember which it is, as i long ago abandoned them to keep magisk and root detection apps happy

Also:

- reboot

- force close and then clear cache/data for any testing app before running after you make any changes
[Magisk] m0han:
You

can't

, I suppose. I disabled the font module I was running, but that didn't change the detections.
[Magisk] 73sydney:
Lets just let that slide, maybe, i know ive had enough drama this week....

Yup, sorry another famous typo can=cant (fixed in previous post)

im just pointing out historically font modules have wreaked havoc with root detection....thats why i personally stopped using them nearly 2 years ago...and why generally i try and warn people
[Magisk] mhd_atzh:
I also think not installing proper GAPPS for ROMs, cause issues with Play Integrity.

Also, this is the font module I used : https://gitlab.com/nongthaihoang/oh_my_font - But this is more recent and updated one.

And Initially, I was using Displax's Initial Mod, I downloaded the latest one. Now Play Integrity Check works for all - except that MEETS_STRONG_INTEGRITY Check Fails.

And Device is PlayStore Certified. Maybe, I'll check back again and report on it.

Thanks a ton. Really appreciate it.
[Magisk] zgfg:
You can't pass Strong Integrity (once you unlocked the BL, installed custom ROM, Magisk, etc) but don't worry about
[Magisk] 73sydney:
Cheers, i didnt specifically mention the Strong Integrity non pass being normal earlier, i just commented what he had at the time was correct. but it bears pointing out! :)
[Magisk] 73sydney:
That font module may indeed be the one thats "safe" to use :)

Like i said, you need ot be really specific when posting abotu which modules youre using, especially version numbers e.g. USNF :) We like verison numbers

My last and hail mary on the app crashes might have been to delete the magisk.db at /data/adb, reboot and install the basic modules over and rehide the essential apps again

Which brings me to a shameless plug...if you plan on doing some ROM flashing, i have a couple of magisk modules to backup and restore the superuser and magiskhide/deny list contents over here (magisk fork irrelevent):

https://xdaforums.com/t/73sydneys-magisk-module-museum-of-madness.4533381/
[Magisk] TaZeR369:
What do you mean by that? You don't need to pass hardware attestation as there is a workaround for it to fore basic instead then you get all checkmarks passing safety net. You just need a few modules for Magisk Zygisk (official version) and riru zygisk lsposed.

I'm using MicroG with patched PlayStore, Universal SafetyNet Fix, Shamiko, proper settings in MagiskHide Props Config - then for lsposed you get "Hide My Applist" to block any unwanted detections on a per app basis.

It thnks my custom aosp based android 10 phone is a completely different one, and I can play games like Pokemon GO and use banking apps without issue.
[Magisk] 73sydney:
@zgfg is pointing out you dont need to pass strong integrity to pass the overall integrity test, maybe you misunderstood and you may also not realise that safetynet is being replaced by integrity test, and they are two different things....

hes just highlighting its not a big deal to fail on strong integrity on the integrity test, because its a common thing for people to panic when they only get 2/3 green on the integrity test

trust me when i tell you that @zgfg knows better than most whats possible when it comes to magisk, and lsposed, oh and hide my applist....he taught me everything i know on that last one...which led to my recent guide on it...
[Magisk] pndwal:
Close...

Actually it simply causes a model prop mismatch (uses real model + space chr) to trigger bypassing of hardware evaluation type attestation enforcement for devices on a Google whitelist containing model props for devices they have deemed hardware attestation compatible...

Some modern devices are not on the whitelist and don't need this prop change, but need the attestation type fallback trigger mentioned below... Also, like pre A8 devices, many new devices (eg most OnePlus) are not on the whitelist due to keymaster implementations being incompatible/broken or because of being untested as yet, and don't need this prop change either... For other modern devices it's a simple mismatch that triggers the bypass and nothing to do with spoofing an old phone/model... Nb. This is actually the second function as basic attestation must already be triggered, however the S/N API still enforces HA so won't accept the verdict without the enforcement bypass for whitelisted devices...

Well this is really due to the first function of USNF, ie. a fake keystore provider is registered in Play Services causing it to throw an exception when it attempts to use key attestation. This triggers a the fallback to basic attestation that is key to USNF's operation. Nb. This is not accomplished by simple prop manipulation...

By 'spoof the TEE', guess you mean bypass enforcement of attestation in TEE... (Google know when Hardware backed or Basic Evaluation types are used so TEE based attestation is never actually spoofed.)

Regarding the lack of provision for hardware-backed device model labels with attestations sent via gms, I put something here in regards to its implications for banks and for us:

https://xdaforums.com/t/discussion-play-integrity-api.4479337/post-87868039

... In short, Google seems to be helping the modding community a lot with respect to fooling proprietary apps (and they haven't necessarily needed to) while at the same time placating banks with the ability to implement strongIntegrity attestation (with implied collateral damage, ie. customers on non keymaster 3 compliant devices)... This seems to be at least in part because they don't view even our bypassing of their security model as necessarily nefarious...

🙂 PW
[Magisk] pndwal:
What was stated there was quite correct...

With the new Play Integrity API you cannot fool hardware keystore based attestation (HKA) to achieve a passing strongIntegrity verdict... This basically maps to the old S/N API's CTS Profile Match with Hardware backed Evaluation type. See mapping here:

https://developer.android.com/google/play/integrity/migrate#device_integrity_verdict_mapping

SafetyNet is already deprecated and all apps using it must migrate to PI by June... Most already have... Check you have deviceIntegrity pass with Play Integrity API Checker...

Many A10 devices don't need the prop based HKA enforcement bypass triggers introduced with the @Displax modded/forked USNF which most are using to pass PI deviceIntegrity on A11+ devices. Some don't even need the native USNF model prop adjustment, the fake keystore registration based trigger causing fallback to basic attestation alone being sufficient for passing deviceIntegrity. I put info on the 3 (1 for S/N & PI & 2 for PI only) prop changes (one or more prop mismatches may be needed for bypass purposes) here:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87575455

This means you are likely to simply pass new PI deviceIntegrity verdict until you upgrade a device to Android 11+; you will likely need modded or updated (@kdrag0n has said he's now working on implementing a PI deviceIntegrity fix officially) USNF when you do.

Nb Many custom ROM users are using the @Displax modded USNF for the second prop adjustment (ro.build.fingerprint) even where it's enforcement bypass function (ie. prop mismatch) is not needed as it targets gms and is better than setting fingerprint/security patch levels globally using MHPC fingerprint selection to allow S/N and PI deviceIntegrity to pass...

🤠 PW
[Magisk] pndwal:
A number, especially on Poco F3 w/ crdroid (A13) had issues (different symptoms) that seem to have been a result of conflicts between SafetyNet Fix integrated solution in ROM and Magisk module... Or possibly other bad ROM implementation... This may be fixed in later crdroid now, I don't know... See:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87484949

And more on this (and ROMs that integrate signal spoofing).

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87486193

As I said there, I personally prefer ROMs that are clean of such mods...

Of course, your issue may be something completely different and may not be ROM related at all...

Normal...

Clear Play Store Data...

Also, A12+ devices have recently been getting a new seperated Google Play Prrotect Service app... If you have this (not sure about GApps w/ crdroid, but it's likely you already do), you will likely need to clear its data along w/ data for Google Play Services and Google Play Store to fix device certification etc...

please report what helps... 👍 PW
[Magisk] zgfg:
I just wanted to plastic

But after a dozen of hectic re-editing, I ended up with a too long post that if I would be a reader, I would hardly ever dare to read (you know what I mean😁)
[Magisk] pndwal:
Praps I should just have said manipulating props is not the first/primary function of USNF... (Many devices don't even need the model prop change but still need the fallback - fake keystore - trigger...)

Hope that's better... PW
[Magisk] TaZeR369:
Awesome, thanks for the patient explanation of all this stuff, I had no idea about the new cutting edge stuff being deployed in the near future and it's true I did kind of scim the posts not fully understanding what the meaning was at first.

Glad there are people working on this stuff, gives me hope!
[Magisk] nik_33:
Hello tell me where to download Magisk Delta

past versions, I need 25.0 version
[Magisk] Arealhooman:
Whats points of unlocking blocks? Any other cool cmds for magisk?
[Magisk] Arealhooman:
Get old versions on GitHub history
[Magisk] 73sydney:
His Github history doesnt go back that far, or id have posted a link to it
[Magisk] 73sydney:
Sorry his commit history doesnt go back that far...and i dont personally stockpile old versions (even with official i only keep the last 4 versions), sorry, someone else might have a copy however
[Magisk] huskydg:
That version doesn't exist btw
[Magisk] Nightf0x_007:
Latest canary build here, cant hide magisk manager app it prompts to install proxy app and asks to install and dowload magisk as it doesnt apply above the magisk manager app
[Magisk] huskydg:
Its bad, now some banking apps also detect Magisk Delta package name