yashsingh1/xdaforums huggingface dataset:
[Android Software Development] pndwal:
It's most certainly not the same!

Perhaps you're looking at Master forked branch... These often represent the clean forked commits only... Change to Integrity branch... 10 commits ahead... Can use either of two releases for most devices... Mod 2 needed only for Pixel 7 series or devices launching with A13, but does seem to address fingerprint scanners and other issues further...

This fork may well fix your fingerprint issue...

You'll find OnePlus/fingerprint/A12+ specific changes (some due to experimenting) here:

Move safetynet props to boot completed to fix fingerprint not working… …

… on OOS12

here:

Bypassing forced STRONG integrity …

* SafetyNet/Play Integrity (bypassing forced STRONG integrity for devices that shipped with 13+) by drop "first_api_level" to <33

* Some cosmetics/fixes

and here:

Move "ro.is_ever_orange" out of boot_completed

The last commit may be critical for you meaning Mod 2 release may be best for OnePlus users even on devices other than P7 / A13 LV devices...

Great info/discussion on @Displax's "A universal fix for SafetyNet and Play Integrity API on Android 8–13 devices with hardware attestation and unlocked bootloaders" fork/proposal for official fix in official PR here:

Play Integrity Api bypass

👀 PW
[Android Software Development] pndwal:
I'm playing catch-up and may have missed something, but it appears you may still only be passing SafetyNet...

Just in case you aren't aware, S/N is now deprecated and apps are migrating to new Play Integrity API... They're looking for MEETS_DEVICE_INTEGRITY verdict at this stage; no apps I'm aware of using MEETS_STRONG_INTEGRITY found in the wild yet...

If you've overlooked this fundamental in the palava, you'll likely need @Displax's forked and modded USNF w/ hardware verdict enforcement bypasses for Play Integrity instead of official USNF... Just posted re. this above...

Check device passes PI deviceIntegrity with Play Integrity API Checker... 🙃 PW
[Android Software Development] Atharkhan101:
@zgfg

73sydney​

I found a work around (no Lsposed, HMA, shamiko needed, they did not work too).

So,

1. I have cleared data and uninstalled the RTO, Medibuddy app which were detecting root and were not working.

2. Uninstalled Magisk

3. Reboot phone

4. Installed Magisk latest 25.2 > Settings > Enabled 'Zygisk' and Checked 'Enforce DenyList'

5. Hide Magisk (need to do this before installing those root detect apps from PlayStore)

6. Reboot

7. Installed RTO and other root detect apps from PlayStore (did not open them yet).

8. Magisk > Settings > Cofigure DenyList > Checked RTO and other root detecting apps.

9. Went back back to my phone's home screen.

10. Reboot.

11. Launched those RTO and other root detect apps and they worked!

I would say most root detecting apps would work with the above method however for me out of 5 Root detecting apps, 4 worked except HDFC bank app. It was working fine on Magisk Manager v23.0 with Magisk.zip v22.1.
[Android Software Development] bombadier:
Its not in a repository of its own

GitHub - LSPosed/LSPosed.github.io

Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.

github.com

Shamiko Releases
[Android Software Development] zgfg:
Few comments:

4) If using Shamiko then must not be Enforce DenyList.

If not using Shamiko then must be Enforced.

That was many times debated in this thread and so.

Most of ppl use Shamiko, hence they have disabled Enforce

5) Fine if it worked for you just with Hide Magisk App.

However, Hide Magisk app is not enough for some other 'banking' apps and that's why I tested with HMA instead

Actually, many of us already have LSPosed installed with some modules - they are detected by banking apps and we MUST hide them by HMA.

That's why I tested with HMA, but I asked you to test by Hide Magisk app instead (since you don't have LSPosed module)

Good that you tested and that Hide Magisk app was enough for you

8) RTO or other apps you want to hide root MUST be in DenyList.

You had to have it from the beginning

Even if Enforce Denylist is disabled cos of Shamiko, those apps must be checked in DenyList.

Regarding the old Magisk v22, you probably had it:

- also Hide Magisk app

- instead of now in DenyList, you had then RTO in MagiskHide list

One must checkmark in DenyList (Magisk v24/25) all those 'banking' apps that he previously had checked in MagiskHide (Magisk v22 or earlier)
[Android Software Development] Atharkhan101:
I know that and thank you as you informed. I read that Shamiko, HMA thing. I disabled DenyList of Magisk, Shamiko failed. I also tried Lsposed and enabled HMA (disabled DenyList of Magisk) that too failed. Just wanted to update you that out of 5 root detect apps including 2 banking apps, 4 apps worked and with Shamiko, HMA, Lsposed only one app could work, not the other 4. I think just for one banking app I should not screw all the 4 working apps.

Apps are:

HDFC Bank- Did not work

Axis bank - Works

RTO - Works

Medibuddy - Works

Rapido Captain - Works

I'm confident that if I use Shamiko, HMA, Lsposed I may get HDFC work but other 4 apps will not work. Just for one HDFC app I don't want to go installing other apps like Lsposed, Shamiko and their too many settings.
[Android Software Development] Atharkhan101:
I want to follow Shamiko properly so I need your help please. I'm sorry I read shamiko thing and I did not understood.

My condition now: I have magisk (hide mode) with Enforce denylist enabled and those 5 root apps selected already. Only the HDFC is not working and still detecting root.

So do I need to do below steps? Please correct the steps if you feel they are wrong:

-I have to disable the enforce denylist in magisk

-Flash shamiko.zip

-Then open magisk and enforce denylist and select root detect apps right?
[Android Software Development] zgfg:
HMA is not substitute for DenyList.

Nobody ever said to disable DenyList when using HMA

Putting a 'banking' app in DenyList is the FIRST thing every user must do, before asking here for help.

Otherwise we really waste time of our lives repeating the same BASIC FACTS

There are many other posts in this and other threads and there are threads here on XDA with guides in the OP posts about Zygisk, DenyList, Shamiko, USNF, HMA and the techniques of hiding

There are eg good guides in the OP posts in the following threads:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/

Hide My Applist - A Brief Guide

Hide My Applist Guide Hide My Applist is a LSPosed module by Dr-TSNG (nullptr). Often referred to as HMA. In the simplest terms HMA aims to stop one app detecting a list of other installed apps. - It can often help stop your banking app(s) from...

xdaforums.com

I specially like Standard 73Sydney Disclaimer (about asking things instead of taking own time to search and read) - hence I will no more continue this debate
[Android Software Development] 73sydney:
Similar to this episode yesterday, where the root detection was ultimately being caused by the users TWRP folder (always check, and umm, recheck the basics folks) :) where i disabled Shamiko to prove, along with @zgfg that it must be something the user overlooked as we were doing the least amount of work to get his problem appto hide...i dont disable Shamiko for most examples, but it was warranted in this case...because nothing was adding up, and it needed to be shown that he must be overlooking something :)

We dont ALWAYS suggest HMA and Shamiko etc, i usually point out that Shamiko is always enabled on my device when im replying to a post and testing stuff for people though. We all like to use the least amount of gear where possible :)
[Android Software Development] 73sydney:
When using shamiko = DISABLE "Enforce Deny List"

When NOT using shamiko = ENABLE "Enforce Deny List"
[Android Software Development] 73sydney:
We really have to stop meeting up and tag teaming the same old points from people at 4am-5:00am my time (not sure what time it is where you are :) This is getting a bit much :)

Rehashing stuff where a search or even as im always saying "read the last 6-12 pages of a thread people, usually already answered" is getting exhausting....
[Android Software Development] Atharkhan101:
Thank you very much. I can confirm that both did not make my HDFC bank app work. I literally invested hours on this and I think I have to live with it. All other 4 root detect apps working fine. Thank you and thank you @zgfg I cant imagine having phone without root though haha
[Android Software Development] 73sydney:
Im going to say this just like i did yesterday at 4am...only its now 6:38 Aussie time

at any point after changing anything in trying to defeat root detection and before opening the apps again, did you clear the data for the affected apps..

any time youre messing with root detected apps and you make a change in trying to defeat the app detecting root, you should clear the apps data

theres an outside chance if you didnt do this you may find it works

also like yesterday, did you try running a detection app like Ruru to see if your were failing anywhere?

Releases · byxiaorun/Ruru

An android sample app of detecting suspicious apps like magisk manager - byxiaorun/Ruru

github.com

and now i have to sleep

update:

Just before i headed to bed, i realised that that banking app rang a bell, becuase i only tested it weeks ago....we (a fe wof us) tested a few of them in a row, that was one of them, and it does work, using Hide My Applist....in fact when i just started up my Hide My Applist app, there it was still in the Effective App list...i installed it again from the play store just now, added it to the Deny List, and ran it....opened first go

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-87714843
[Android Software Development] pndwal:
Wasn't able to pass on my MIUI device (RN8T, A10) however... Remember this:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-87715143

... Think we're taking Redmi Note 9 Pro Max here(?)... Anyone had success on MIUI?... I'd love to know what extra leaks need hiding and how... 😃 PW
[Android Software Development] Atharkhan101:
Yes I did clear cache and data.

Installed Ruru, not sure what to check there. Its too much of geek for me. I like what you said earlier like everybody likes to have few gears :)

That HDFC Banking app appears to work but not actually. When you in real, enter the Customer ID and Password, it crashes and takes you browser picker. When I select Chrome, nothing happens. I have Titanium Backup and also checked with the previous version of HDFC app Still no success will use the website instead of app. Just don't want to install other apps Lsposed, HMA and configure so many settings just to make this ONE app work and can fail the OTHER 4. I'm good with Magisk Enforce denylist. Refer the attached screen record

https://drive.google.com/file/d/1IDDmPlHPgl59MeeksxzkI0vflO7Qj8zl/view?usp=drivesdk

If some dev take over Magisk/Zygisk then the enforce deny list/deny list can be improved.
[Android Software Development] pndwal:
There are already Devs/forks that do just that, allowing use of either hidelist or denylist as well as special tweaks (many experimental) for better Zygisk hiding etc etc...

Don't expect this happen in official Magisk however...

John has been following his own roadmap for Magisk and has said he has not plans to abandon it. In 2020 he said:

https://topjohnwu.medium.com/state-of-magisk-2020-21de32721d65

And in 2021:

https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458

Also, while he won't now state it plainly, code injection (Zygisk project) was always about providing a better framework for 'proper ways to "hide" root and Magisk Manager/App'... See these comments back in 2020:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84104161

He's said it's up to other Devs to 'step up' and 'start doing their job', ie making zygisk based hiding modules if they're passionate about that... He's also said he wishes people wouldn't fork Magisk for restoring MagiskHide however...

So the future of root hiding is very much in the hands of 3rd party Devs (John has stated as much for a while now too), and it must be said that this makes the whole exercise, including choosing individual hiding solutions, necessarily more complex and challenging than it used to be... but there are also many more options and more effective methods... Such is the modern cat and mouse game of root hiding... 🙃 PW
[Android Software Development] 73sydney:
I notice youre never around for the 4-5am shift, you terrible pedant .... :)
[Android Software Development] digger16309:
@Atharkhan101 Are you running an ad-blocker at any level? For example, I've found that some of these "detect root" scenarios are actually AdAway blocking the sign-in domain as unsafe.
[Android Software Development] pndwal:
FYI: Looks like we may finally be getting official Universal PI deviceIntegrity Fix in USNF!

It'll be nice to have a working fix linked from OP here again too...

... So seems @kdrag0n has found proper hooks to set and revert the fingerprint used for mismatch trigger for PI hardware based verdict enforcement bypass making this proposition less of a stop-gap fix with far less likelihood of breaking print prop related stuff... He'll also implement the additional @anirudhgupta109 shipping API level prop mismatch needed for Pixel 7 and other A13 LV devices (already adopted by @Displax in his forked USNF mods)... See here:

https://github.com/kdrag0n/safetynet-fix/pull/207#issuecomment-1340460803

Watch this space! 😛 ... And thanks for efforts @kdrag0n. 👍

👀PW
[Android Software Development] Atharkhan101:
Does anyone know why it doesn't select all items in oo

Yes I use Adaway and I'm confident that it is not cause any issue because I tried to freeze it in Titanium backup and additionally it used to work in 22.1 Version of magisk WITH Adaway ON.
[Android Software Development] zgfg:
If you have Systemless hosts enabled and you freeze AdAway, /data/adb/modules/hosts/system/etc/hosts file will remain, and Magisk will still mount it (even upon reboot) to the /system/etc/hosts, ie blocking will be still in place

Only if you use AdAway in the non-root/VPN mode, then freezing will really stop blocking

Nevertheless, I don't understand why complicating

AdAway has Pause/Resume button. Just Pause, reboot and then you're sure that AdAway is no more blocking until you Resume and reboot again (reboots not needed if using AdAway in the VPN mode)
[Android Software Development] Atharkhan101:
Already done all you said. Still nope!
[Android Software Development] m0han:
... even running it for the first time, may I add?

I thought I read somewhere: Turn ON airplane mode, Clear cache and data of the apps, Reboot and Turn OFF airplane mode before running the apps again.

If the latest official Shamiko-v0.6-126-release.zip here does not work, you might like to try Shamiko-v0.6-130 (see screenshot). For more, see/use the Telegram channel.
[Android Software Development] bombadier:
Which telegram channel?
[Android Software Development] kamilchno:
|ZH/EN|\|SFW| シャミ子が悪いんだよ

ZH/EN	禁止阴阳怪气/No sarcasm；	严禁涉政、机场、广告/ No ads or politics；	不得私聊管理/ NO pm admins；	提问前请先看所有置顶/ Read all pins first；	反馈问题请带日志 / Must report with log；	严禁社工 / No dox；	严禁开挂 / No Cheat；	提问时自称小白会被警告。	Channel: @LSPosed	CI Builds: @LSPosedArchives

t.me
[Android Software Development] 73sydney:
some of us recommend doing the airplane mode thing for Google Play Store/Google Play Services when trying to pass the Integrity test after installing Magisk

not necessary for the average app
[Android Software Development] Arealhooman:
Is this better than original
[Android Software Development] Arealhooman:
@pndwal is it?
[Android Software Development] zgfg:
Did you read what you quoted?

It was developed to pass Play Integrity API when Google switched from SN to PI.

For many, it was needed to pass PI

Besides, you can easily switch back and force from the 'original' to this one. Modules are systemless - you disable or uninstall, all their changes will be gone

Hence nothing is stopping you to try. Btw, if the 'original' works for you, why changing the winning team.

But if you're not passing PI, then definitely try
[Android Software Development] 73sydney:
He's possibly still asleep as its 5:30AM Sydney time, or starting his walk up his belltower on the way to work

USNF MOD v.2: Bypassing DEVICE_INTEGRITY for devices that shipped with Android 13+ (Pixel`s 7 )

It functionally makes no dfifference if youre

a) already passing with the non-modded one

or

b) whether you use v1.0 or v2.0 of the Modded version, if the non-modded one doesnt work, unless youre on a device launching with A13...

All the above will be moot within days when kdrag0n rolls out his updated official one
[Android Software Development] Arealhooman:
Wait this module will be updated ”within days”?
[Android Software Development] 73sydney:
Think of the impending new release as the "one to worry about next time you flash or have an issue with root detection".

In the meantime use the modded v2.0 one if youre still fence sitting
[Android Software Development] Arealhooman:
Okay! Will the release be announced here?
[Android Software Development] zgfg:
Will it rain next year on the same day?

Btw, if/when the new official or unofficial will be released, users will start discussing it here

But I really think you should not install because that may cause a thermonuclear war😁
[Android Software Development] varunpilankar:
I'm trying to make Paytm Tap to pay work using Mod2.. But still no luck.

Check the screenshots.
[Android Software Development] pndwal:
You may be missing the point of this module.

It's simply to allow you to pass PI deviceIntegrity when you don't!... If you already pass, updating won't help you further (except that it does help OnePlus and some other device users with other issues however, but I believe only if running A12+ w/ official USNF which combination can break fingerprint scanners etc; the @Displax mod builds some updated fixes for these devices/issues connected with spoofing props), and in your case running A10, it may not be needed at all as many devices pass PI deviceIntegrity w/ A10 or less and official USNF...

To put it simply, if you weren't passing deviceIntegrity before installing, then the @Displax USNF mod/fork is doing its job perfectly... There are simply other detected traces of root or apps, folders or other signals associated with custom modding that are being detected by your app and need addressing...

The basics are:

- Zygisk = Yes on Magisk home screen.

- (Bank/other) app in denylist. (Enforce DenyList enabled.)

- PI deviceIntegrity passing.

- Full Magisk App replaced with hidden stub App

Next things to try:

- Shamiko module. (Enforce DenyList disabled.)

- LSPosed module and configure Hide My Applist Xposed module properly.

- Check for and remove/rename folders associated with TWRP etc.

- Run detection apps like Momo to determine what else may be detected on your device...

Nb. Clear app's data after any detection/failure and before any new test...

Hope it helps. 🙂 PW
[Android Software Development] Arealhooman:
There is no way to pass strong integity ona rooted device.
[Android Software Development] pndwal:
... Unless you have an Asus ROG Phone 3 (others?)... 😜 PW
[Android Software Development] Arealhooman:
Im surprised it wasn’t fixed
[Android Software Development] pndwal:
🤔 ... By whom?... PW
[Android Software Development] Arealhooman:
Google? The company that made the phone? Isn’t it software?
[Android Software Development] shoey63:
Hang on, I'll just check
[Android Software Development] shoey63:
Still all good on rooted ROG 3😋View attachment 5781257
[Android Software Development] pndwal:
Very low level firmware... Looks like broken droidguard implementation to me, but OEM is responsible to implement keymaster functions...

Rog Phone 3 seems to be unique in allowing strongIntegrity to pass (specifically AVB always reports Device Locked = True / Bootloader Locked)...

Many others have broken keymaster implementations, most famously OnePlus, and I'm not aware of any that have been fixed with updates!... This appears, at least in part, to be the reason for Google's apparent whitelisted-device based system of bypassing hardware based verdict enforcement which, of course, is the only reason we can thwart integrity attestations on our modded devices!... 😛

It seems that the recent emphasis on Google projects like Treble, Mainline and others, with all their GSI/GKI/other complexities (ostensibly to address fragmentation and improve compatibility for Long-Term Supported updates, uninhibited Android platform release upgrades, ability to contribute kernel changes back to upstream Linux etc) may also be to facilitate easier fixes for broken / buggy droidguard, keymaster implementations, Widevine DRM, generic TrustyTEE or custom TEE OS and any number of other critical firmware components however... Time will tell, but it's precisely the time all this takes that is giving modders the extra leases-of-life we are enjoying!...

I, for one, am in no hurry to see such 'issues' fixed! 😁 PW
[Android Software Development] bombadier:
Am looking for some help trying to work out what method my banking app is using to detect root, up until I updated the app yesterday everything was working great with this banking app, Play integrity API Checker reports a tick for Device and basic integrity but a cross for Strong which if I understand right is to be expected, I have a Pixel 4a running Android 13.

I have the Magisk app hidden, am using Shamiko to hide, had to use props config to spoof an andoid 10 fingerprint to get Basic integrity and the banking app is in the deny list, everything has been set up correctly and Google Wallet and Netflix are still working, the bank app was working until the update, as of version 104.03 it detects root.

Now the MOMO checker says my environment is abnormal, found executable file "su", found files modified by Magisk Module and it found Magisk, also debugging is enabled and an unlocked bootloader, I am struggling to find much about MOMO or how to deal with what its reporting, ie how to hide Magisk better from MOMO.

I know its not really relevant for this thread as I am passing safetynet but I know there are plenty knowledgeable sorts that frequent this thread that know a lot more on the subject as I, anybody got any ideas for me to try ?

Thanks in advance,
[Android Software Development] 73sydney:
Step 1: Disable MagiskHide Props Config

Step 2: Install Universal SafetyNet Fix (mod 2):

Releases · Displax/safetynet-fix

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

github.com

Step 3: Reboot

Step 4: Test

And also check with this (over Momo):

Releases · byxiaorun/Ruru

An android sample app of detecting suspicious apps like magisk manager - byxiaorun/Ruru

github.com
[Android Software Development] bombadier:
Thanks for the suggestions, have done as you said, Ruru is still detecting magisk and su and the banking app is also still detecting I am rooted, this was a fresh install of the banking app and adding it to the deny list before running for the first time, any ideas how I can better hide magisk and su ? got a feeling the banking app is checking for an unlocked bootloader, with the modded safetynet fix, wallet and netflix is still working, still failing Strong integrity but the fingerprint now matches the release keys, both are android 13 as when I rebooted there was a system update, something play related which I assume is to do with the fingerprint
[Android Software Development] 73sydney:
My Ruru detects Su, Busybox, Magisk, and have developer options enabled and unlocked bootloader but my banking apps still work fine...so its not impossible for most banking apps

Have you:

Force closed and cleared data for your bankign app at any point during this?...worth a try

Ever used TWRP on that device?

Which banking app, so i can test?

p.s. as for the update yes, when you change your fingerprint you can find yourself missing updates....and you definitely want to stay on your proper fingerprint where possible to get things like monthly security patches...