yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Old Viper installations used permissive selinux but I believe that even builds flashed in system were later fixed to run enforcing...

In any case, Magisk module based enforcing Viper4AndroidFX has been available for some time, works without issues, and most users running Magisk use a systemless solution/package...

Original is old but still works fine:

https://zackptg5.com/android.php#viper

This (much larger but not really necessary) repackaged ViPER4Android module works well for many here currently too:

https://github.com/programminghoch10/ViPER4AndroidRepackaged

Re. original Viper4AndroidFX module, you just need to reset Neon driver when selecting legacy mode (ie. when Status=Abnormal)... When you install, reinstall or for any other reason have abnormal status, just set legacy mode, disable the module, reboot, re-enable module and reboot again; driver should reset and status should now be Normal... You'll generally only have issues with Neon driver when installing/changing mode...

I'll give this a whirl for you soon...

🙂 PW
[Magisk] pndwal:
... Works for me with WIP native bridge Zygisk loading to properly hide Zygisk and module memory... It's expected in official Magisk 27.0+ but current Alpha fork is a POC and I have many troublesome apps working with this.

For this app, HMA was not needed; I do have root hidden from app using Shamiko however...

See this post and the one above it and follow links back from this post:

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

for more information incl. my device configuration... 🙂 PW
[Magisk] lieblingsbesuch:
Hey,

I decided to completely start from scratch with my OP8 Pro, means I reset it via Qualcomm edl and put the latest PE on it.

The phone is rooted via magisk and the only module I loaded is this patched usnf, with zygisk enabled and only hid 3 apps without enforcing.

No shamiko or sth else

I do not have strong integrity, but all banking apps, gwallet etc. work.

Thank you for this great mod!
[Magisk] chiteroman:
Which version did you use?
[Magisk] lieblingsbesuch:
Of pe? The latest one from July 2023.

Of the mod? 2.4.0 2.0 (not strong)
[Magisk] Johnny Eng:
Working flawlessly on S23 Ultra One UI 5.1 June 2023 security patch.
[Magisk] gajo_luso:
Hey Man, I changed the ROM, and follow your instructions. Thank bro

I'm using a ROM based in Android 13.
[Magisk] Bladius:
I don't know what could be the cause. On two Redmi Note 10 with ArrowOS 13.1 ROM, the verification works. Everything is ok. However, the problem is that one device has correct verification all the time, and the other loses it very quickly and the verification stops working. I also noticed that it crashes instantly when Lucky Patcher is launched. Sometimes, however, I don't have to do anything and it also stops passing verifications.
[Magisk] pndwal:
Workarounds:

1) https://github.com/nongthaihoang/custom_font_installer/issues/1#issuecomment-994832687

2) Shamiko

Seems Shamiko fixes issue for items in denylist since:

Shamiko v0.7...

• 2. Fix font loading

Even though Shamiko hiding itself is not needed for gms (as I have said), having Google Play Services (at least the Droidguard/attestation process, com.google.android.gms.unstable and main process, com.google.android.gms) in denylist, not enforced with Shamiko 0.7+ (ie as Shamiko hidelist), seems to fix issues for some (all?) with this problem preventing the font module from breaking system UI items...

After reading this comment:

it occurs to me that inbuilt USNF hiding (root from droidguard + main GMS processes) is likely doing the same, ie. inbuilt hiding conceals font modules from Google Play Services but not font.xml...UI etc can't access font files, -> crashed!

I don't know how Shamiko v0.7, ' • Fix font loading' works, but guess it somehow passes on the font files or makes that particular Magisk modification an exception when hiding...

If others could test that this does work consistently, I guess a similar fix could/should be built into USNF / (Partial) PIF if possible... ( @Displax )

Praps some of you learned gents/ladies could test/comment... 🙂 PW
[Magisk] pndwal:
Do you have the same versions of this (@Displax modified USNF) module on both devices?... Sounds like you may have official (broken) build...

And who knows what the Taboo LP is do... 😬 PW
[Magisk] kouzelnik3:
Why was the STRONG build version deleted? Was it causing any major issues? I didn't encounter one on my Oneplus 10 pro (except that the "normal" build, not the STRONG one doesn't pass MEETS_STRONG_INTEGRITY) 😄
[Magisk] Bladius:
The same
[Magisk] chiteroman:
https://xdaforums.com/t/module-play-integrity-fix.4607985/

🥰
[Magisk] calmfish:
I have no idea what is going on here - google attest that my device does not fail strong integrity checks.

Re-tested today as I regularly do because of a problematic banking app (starling) - and I receive a meets strong integrity result (which is impossible). I have a Poco F3 running Arrow 11 Final - no root, but very much unlocked bootloader.

Prior to today It has met basic integrity only (as expected) and google pay etc and all the other banking apps I use have worked fine. Starling broke in May with whatever device detection changes they made. I have been periodically re-testing their newer builds to see if they had decided to revert their complaints about "your device does not meet our security requirements" and now suddenly having made no changes other than update their app to the new version I can sign back in.

TB checker knows the bootloader is not locked but apparently SN and PI do not. It is not just the checking apps reporting incorrect results either because it has the meaningful effect that an app that relies on those responses now works again...

Screenshots attached.

Device IDs redacted (unknown if sensitive).
[Magisk] V0latyle:
Which PI fix module are you using?
[Magisk] calmfish:
Whatever is baked into the ROM by Arrow or the maintainer (palaych). And it certainly has had no changes since 2022/09/20.

https://xdaforums.com/t/rom-11-0-0-alioth-aliothin-arrowos-11-0-official-closed.4279481/

I can only assume this a server side bug by google at the present moment?
[Magisk] V0latyle:
Maybe? Hard to say. If it hasn't been updated in the past 10 months, it's entirely possible it's Google side
[Magisk] calmfish:
Thought I'd report it anyway in case it helps any developers gather info or help with future fixes.
[Magisk] V0latyle:
Probably better for either of these threads:

[MODULE] [MOD] Universal SafetyNet Fix

Universal SafetyNet Fix [MOD] Magisk module Hello. This is my modification [FORK] of the original Universal SafetyNet Fix module from @kdrag0n. Created for the (temporary?) restoration of working capacity in the conditions of constant change...

xdaforums.com

https://xdaforums.com/t/module-play-integrity-fix.4607985/

Please don't copy/paste posts, if you want your posts moved to a different thread use the Report button.
[Magisk] ykjae:
I'm using a custom font and luckypatcher and haven't had any system errors. I also haven't changed any shamiko settings or hma. I just disabled other magisk modules such as usnf original and hide system props etc. Before I disabled all those modules I was stuck at system is loading. Pixel 6 pro.
[Magisk] Nergal di Cuthah:
Lucky patcher is evil and is detectable by apps looking if you're rooted, just saying. Not sure what your actual question is because your post looks like you're answering someone but the converstion chain is broken by your lack of reply quote
[Magisk] Jonog:
DMd you. If u had a second, would really appreciate it. Thanks
[Magisk] calmfish:
I've read back a few pages but admit I am lost with whether anyone else has success with a shipping api level <33 but my first_api_level reports as 30.
[Magisk] rmccurdy:
https://xdaforums.com/t/poc-safetynet-bypass-for-emulators.4607061/ ❤️❤️❤️❤️
[Magisk] RobinKara:
hope it helps: Got it running.

have now installed:

Magisk: d390caf (26104)

Zygisk: Yes

Ramdisk: Yes

Update Channel: Canary

Systemless Host file

Zygisk: enabled

deny list:

- Carrier Services (Google)

- google

- Google play services

- Google wallet

- Google service framework

Modules:

- !!!! L Speed --> THIS MADE THE TROUBLE I GUESS - de-installed it and WALLET is running without issues.

- Systemless Hosts

- Universal SafteNet Fix v2.4.0-Mod_2.0

- Youtube ReVanced

Phone: Pixel 7 Pro

Android 13

Build: TQ3A.230605.012
[Magisk] pndwal:
👍

You don't need

- Carrier Services (Google)

- google

- Google play services

- Google service framework

in denylist... Play Services should be removed on reboot with denylist enforced if you're denying Magisk modifications to Droidguard ('...unstable') process as it breaks USNF primary code injection function...

Only use for P!ay Services in denylist is to use Shamiko 7+ font module fix to fix UI issues when using custom fonts (with Denylist NOT enforced)...

👍 ... Thanks for the heads-up! 🙂 PW
[Magisk] MrCavity:
Looks like this fixed my Pixel2XL Gwallet, thanks!!

:D
[Magisk] burritoman12321:
Hello, about a week ago safetynet stopped passing and I don't know how to make it work again. I've tried the original mod made by kdrag0n, this mod and the play integrity module but no matter what safetynet still doesn't pass, does anyone else have the same issue and has anyone found any way to fix?
[Magisk] sawdoctor:
Need a bit more information. What device do you have, how are you rooted (magisk version etc), what modules you have installed, do you have any xposed/lsposed mods?

Certainly not an expert but for me it's always been a xposed module that's caused me issues
[Magisk] burritoman12321:
Pixel 7 pro, magisk 26100, LSposed with the modded safteynet fix, only xposed module is fakegapps by whewinc. If an xposed module was an issue how would I disable it without causing more issues
[Magisk] abobobilly:
I'm running a OP7TPRO with Magic 26.1 app and module installed. Recently upgraded the safetynetfix to 2.0.

While everything is working fine, there's this one dreaded banking app called "ENBDX" has stopped working, as it says 'device is rooted'. (FYI, this was working fine earlier, but after a recent App update, this issue has started).

I wanted to know if there's anything we can do about it?

DenyList is active, and working. Google Services, Wallet etc everything works. All other banking apps working. Except this one dreaded app.
[Magisk] WhoIsJohnGalt1979:
You can try using magisk alpha. I am on the latest Canary and added that app to deny list as well as HMA. It still detects phone as rooted. So use magisk alpha which has native bridge or something or wait till magisk 27
[Magisk] calmfish:
Google have at least partially fixed this as of today - Arrow 11 once again reverts to reporting failing strong checks.
[Magisk] innit:
Stopped working for me too just few minutes ago. Google Wallet fails, some apps (Revolut, DeutschlandCard) show up in Play Store as incompatible. Integrity Checker throws an error.

Using 2.4.0-MOD_2.0-test3 on Pixel 7 Pro with july firmware.
[Magisk] phoberus:
Hello. I was nearly 3 years away from magisk and root/modding in general, because there was no way to use my banking apps (UBS banking) with it.

I know that the banking app is very strict and already refuses to start when I installed a modded app (without root).

What is the current status? Do you think I could try again or are there still many problems with modded phones?
[Magisk] sawdoctor:
I'm using this one from @Stillhard on the pixel fold and it's still passing all 3

Universal SafetyNet Fix [MOD]

Magisk module

Hello. This is my modification [FORK] of the original Universal SafetyNet Fix module from @kdrag0n.

Created for the (temporary?) restoration of working capacity in the conditions of constant change... https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88775173
[Magisk] chiteroman:
Still passing Strong ?
[Magisk] sawdoctor:
It was but none will pass strong once your device receieves the play services update that patches the exploit. I still pass the 1st two and all my bank apps still work
[Magisk] Displax:
This fix does not depend on the version of the services, the fix is on the server side
[Magisk] zgfg:
They don't need to push update for Google Play Services. Mind about the DroidGuard named "the.apk" (exactly as that, it was written about here in these threads)- you receive its updates several times a month, actually they don't even delete the old ones, you can find like a dozen of the older versions on your phone

And even that the.apk is just a messenger - it connects to the Google server, Google server sends the bytecode (hence, they can just update the bytecode on the server whenever they want, and you will not know) and that bytecode then inspects your device and the apk sends it back to the G server for the final verdict

Hence you don't need to wait for new Google Play Services - Google Play Services is just a frame around. The other parts do the job and they are more faster to be changed and fixed, it's just a matter of what and when they want to do (or do not want - and we don't know and don't understand their reasons)
[Magisk] addsfsds:
Hello, I'm using the latest safetynet-fix-v2.4.0-MOD_2.0-test4 on my oneplus 8 pro with android 11 but I'm getting "phone is starting" and stays there in loop. Any idea? I had no problem with the version on first post (but it's not working with my bank app). Magisk 26.1 stable. Thank you
[Magisk] Stillhard:
It just like it

I saw @에어 론 리 post above and try to proved it, and in my test, yes it was happened after reboots

So, it might google have planted their nails in the device :D
[Magisk] supermansaga:
Google so evil. Now I can't use Google One VPN again. I am rooting for Displax.
[Magisk] Nergal di Cuthah:
Just wondering and not to derail but why would you use an ad company's vpn esp if you find them "evil".
[Magisk] supermansaga:
They touted their technology is better than the rest.
[Magisk] kevinco1:
Obviously you don't know what irony is
[Magisk] Nergal di Cuthah:
I apologize for the derail time to go back to mod 2.0
[Magisk] supermansaga:
their US ip addresses are said to be purer than others for streaming media purposes. You won't appreciate that unless you travel to a country where it's extremely hard to connect to a server that works for HBOMax or Disney+ or netflix
[Magisk] Jon8RFC:
My Pixel 7 Pro no longer passes as "strong", too bad. Android team is very [redacted] in their thinking and morals/ethics.

The Android team values disallowing integrity spoofing so that we can actually use apps, WAY MORE than they value disallowing apps from abusing the ability of checking root status, scanning all installed applications, or checking adb/usb debugging status, when the overwhelming majority of apps have no business poking and prodding any of those.

Papa Murphys app, for example (or the person whose local garbage collection app showing the calendar and status during inclement weather, which disallows the schedule from being seen on rooted devices). Papa Murphy's checks left, right, up, and down for any signs of root, adb, and disallows function if I stop it from scanning my phone's apps list. Why? Because, that's why. My Windows computer is arguably far less secure, yet they allow me to order a pizza on there and aren't scanning to see which programs I have installed on my computer. There's a way around it, but I shouldn't have to jump through 23 hoops to order a pizza.
[Magisk] intel_core_i7:
The irony. I can transfer money from a windows xp machine, but can't if I have an app using accessibility services on my phone.
[Magisk] pndwal:
Yeah?

Spoiler content hidden.

🙃 PW
[Magisk] Arcline:
Is there a MicroG variant for the new version?
[Magisk] beeshyams:
Spoiler content is 👌

Aside, instead of two phones, one phone with one slot rooted other unrooted is possible thanks to @badabing2003 Pixel Flasher.. May not suit many but for me it looks too be a very doable thing unless unlocked bootloader means the rat is swallowed!
[Magisk] pndwal:
Sadly, BL is start of AVB root of trust so for this approach you would need dual bootloaders... Very doubtful you could repartition and duplicate proprietary low level stuff with working implementation, and certainly no universal solution even if you could reverse code and duplicate BL etc on one device by some miracle... Nice to dream about it though!... Maybe you could team up with @HippoMan and do it! 😜 PW

... Rats...
[Magisk] beeshyams:
Me just am optimistic NOOB
[Magisk] pndwal:
It appears not... @Displax? PW
[Magisk] badabing2003:
Why does he need dual bootloaders?

Aren't there already dual bootloaders? and both intact to be precise?
[Magisk] sawdoctor:
If we could have both A and B partitions bootable on the fly that would be fantastic, 1 rooted the other not. Some apps detect an unlocked bootloader and put us in the same position as them detecting root. Is there anyway to circumvent that
[Magisk] beeshyams:
On the fly is possible from rooted to unrooted slot. For vice-versa you need a Pac
[Magisk] badabing2003:
Yes, as @beeshyams said, it's possible to have rooted and unrooted bootable system,

however you can go from rooted to unrooted on the phone, however going from unrooted to rooted you would need a PC.
[Magisk] frenksisco:
Really grateful!!!!!!! Even for a newbie like me, who had failed every other attempt, it was possible to solve the SafetyNet "CTS profile match: Fail" simply by following the 4 instructions on page 1.

I just need to ask you a couple of things:

1) I see that it was not indicated to activate Zygisk or include the google and banking apps in Denylist. I still have both active from a previous attempt with kdrag0n Universal SafetyNet Fix 2.4.0. Can I turn them off? I am terrified of screwing it up.

2) On "Play Integrity API Checker app" I pass "device" and "basic" integrity but not the "strong". Do I have to pass that as well toavoid problems on play store or banking apps?

Thanks
[Magisk] jons99:
I can switch slots with or without root using my phone only with twrp

won't hide the fact that your bootloader is unlocked
[Magisk] zgfg:
1) 'Banking' apps use various techniques to detect 'root'. By passing SN/Play Integrity it absolutely doesn't mean that you will pass detections from all of them. Don't even expect - something like that is nowhere 'guaranteed' in this thread

You usually must put them to DenyList, you may need to use Hide My Apps module for LSPosed (it might have been mentioned here but it's Out Of Topic for this thread). There are also other modules that may help (eg, Bootloader Spoofer for LSPosed, etc)

For for some 'banking' apps all that wouldn't be enough. Might be needed to use special Magisk fork Alpha (or wait for Magisk v27 if that would really help)

Nevertheless, it is and always will be a cat and mouse game. You hide today, tomorrow it won't work and you will need to update your hiding methods

2) You cannot spoof Strong Integrity with the unlocked Bootloader. Certain spoof worked for about a week, but Google quickly fixed about a week go

Expect that Google and 'banking' app developers also monitor what's going on the other side (like here)
[Magisk] frenksisco:
When I think that a week ago I had a 100% original phone with a locked bootloader and without any problem.... And that I destroyed this just because I was bored...............

Anyway I got it, thank you very much
[Magisk] badabing2003:
twrp is not available for all phones.

The question was not about bootloader being locked or not, the question was about being able to switch from an unrooted system to a rooted system without a PC.

Of course if the app detects that your bootloader is unlocked, no amount of slot switching is going to matter.
[Magisk] sawdoctor:
Once banking apps have detected root even after you apply safety net fix or whatever hiding method you use you normally have to wipe data from the banking app and clear play services data before the root detection clears
[Magisk] pndwal:
Well as I understand it we have only one 'bootloader' for the purpose of this discussion although it consists of several partitions/sub-bootloaders, a primary bootloader (/rpm partition), secondary bootloader (typically /sbl1) application bootloader (/aboot)... When you unlock your bootloader, you are technically not “unlocking” anything, rather just bypassing the locked bootloader (/rpm), and the Android OS boots on instructions from the secondary bootloader (which is unlocked) and /aboot, the application bootloader...

Bootloader functions include:

1) Load and initialize memory.

2) Verify the device according to Verified Boot flow.

3) Verify the boot partitions, including boot, dtbo, init_boot, and recovery, according to the Verified Boot flow. As part of this step, check the boot image header version and parse the header accordingly.

4) If A/B updates are used, determine the current slot to boot.

5) Determine if recovery mode should be booted.

6) Load the boot images, such as boot.img, vendor_boot.img, init_boot.img, and other proprietary vendor boot images. These boot images contain the kernel and ramdisk images.

https://source.android.com/docs/core/architecture/bootloader

A/B-capable bootloaders must implement the boot_control HAL to make A/B system updates work, but one bootloader still controls both slots...

https://source.android.com/docs/core/ota/ab/ab_implement

So to answer, dual bootloaders will be needed to have a rooted system + a fully stock system (passing strongIntegrity or even deviceIntegrity)... Nb with unlocked B/L a stock A8+ system with good keymaster implementation won't even pass deviceIntegrity...

🙃 😬 PW
[Magisk] badabing2003:
Ok got it, you're talking about the Boot Rom and not the bootloader that is flashed.

which cannot be modified or even interrupted.

Thanks for the clarification.
[Magisk] pndwal:
Sorry, I was definitely talking about the bootloader, part of which (primary bootloader) is stored in the boot ROM... But "not the bootloader that's flashed"?... Well, yes, some devices get bootloader updates as part of OTA, especially when Google/OEM tries to patch a vuln and prevent rollback (downgrading) thereafter... But generally modders don't ever flash bootloader (either as a whole, or any specific bootloaders (bootloader parts))...

... You're not meaning "boot image that's flashed" are you?... Of course bootloader is not a boot image... bootloader 'Loads the boot images, such as boot.img, vendor_boot.img, init_boot.img, and other proprietary vendor boot images' as a principal function (no. 6 above), hence the designation bootloader (boot image loader).

A note for the less experienced also: Something that often causes confusion - recovery.img is of course a boot image too... There are many more boot images than just boot.img. 🙂 PW
[Magisk] Nergal di Cuthah:
Nope bootloader like what pixel series 6 users had to flash to both slots when 13 came out.
[Magisk] zgfg:
You won't be bored and you have the opportunity now for a lifelong education about hiding the root🤪
[Magisk] pndwal:
Can you give me a link?... I remember reading about this and considerations re anti rollback for P6 series somewhere....

Just don't understand what bootloader parts or partitions would be duplicated... Don't think /rpm, /sbl1 or /aboot are duplicated... Could be wrong...

I can understand why boot images must be flashed to both slots after a bootloader update however... These must be compatible with new bootloader (and both sets of existing boot images become incompatible)... And that's also why we can't roll back after B/L update; images are generally B/L specific and you usually can't roll back B/L.

Still, if we do have 'bootloader_a' and 'bootloader_ b', it might be just what we need! (Seems hidden if in Google documents however); Fully independent dual boot! 🤞PW
[Magisk] zgfg:
There was a discussion with explanation from badabing2003 in the Pixel Flasher thread (although I think it started in the Magisk General thread)
[Magisk] mihalis1983:
Hello,

I need help with Play Integrity/ safetynet, none passing. (Photos attached)

Poco F1, Android 10, Miui 12.0.3 (SELinux permissive), magisk 26.1, Shamiko ( Enforce DenyList OFF), Universal SafetyNet Fix 2.4 Mod 2.0, Zygisk-LSposed 1.8.6 with some modules and HMA properly configured.