yashsingh1/xdaforums huggingface dataset:
[Android Software Development] immortalwon:
Damn something is off with your firmware then lol. I never have this issue. If I was you, I would format all data and downgrade my firmware unless you like OOS 13.1.

Make a full backup of everything and format all data using twrp. Make sure to flash the new firmware immediately after format. Which device are you currently using? I actually don't have too much time right now I G2G, but hopefully you figure it out.
[Android Software Development] Nhatlienhoan:
Thank you so much for spending that time trying to help me. I really appreciate it. I'll try and mess around. (One more thing I noticed is that for some reason, in my local updater app, it shows I have F24 as my firmware while it showed 13.1 EXO001 before. I did fool around but forgot what I did and usually, those things I did often and shouldn't make any major change). Thanks again!
[Android Software Development] pndwal:
Did you try my suggestion?:

Also, remove everything Google from denylist (only exception would be G Pay/Wallet)... Zygisk-USNF hides root from gms itself; Nb. zy-USNF can work with gms processes in denylist only if it's disabled, including w/ Shamiko but that is still double-hiding and not recommended... Enforced Denylist necessarily breaks zy-USNF as it prevents the basic function, ie. running code in gms Droidguard/attestation process to register fake keystore...

Also, please confirm ROM is fully stock, selinux is enforcing and you have run no other mods (eg from TWRP)...

If all above is correct and no dice, I'd try dirty flashing current ROM (will fix any corruption unless in /data); Use fastboot type full ROM as these are often more complete than recovery type...

🤠 PW
[Android Software Development] Abhishek.0:
how do i pass cts profile match fail in miui china rom
[Android Software Development] mslezak:
This helped me out - my issue was having Enforce DenyList turned on in Magisk. My device attestation is busted, Universal Safety-Net Fix (USNF) modded by Displax worked. Magisk settings: Zygisk, Configure DenyList (NOT ENFORCE DENYLIST!) add GPay to DenyList, add Google Wallet to DenyList. Install USNF in Magisk, reboot. Force stop Play Store, clear cache. Clear GPay cache and data. Setup GPay.
[Android Software Development] pndwal:
Do you still have any Google Play Services processes in denylist? PW
[Android Software Development] mslezak:
Only GPay and after I added it, Google Wallet. Nothing else for Google Pay.
[Android Software Development] pndwal:
Official USNF Magisk module (here) is still largely broken...

Use this fork:

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88149053

Check have Play Integrity deviceIntegrity using Play Integrity API Checker or similar... Nb. SafetyNet API is deprecated. 🤠 PW
[Android Software Development] pndwal:
Not sure why enforced denylist is an issue then... Generally works fine for G Pay/Wallet (without Shamiko)... Of course gms in denylist breaks this... PW
[Android Software Development] Abhishek.0:
i use this but not pass

and also show

basic integrity fail

and cts profile fail

without module only show cts profile fail

what happen i do
[Android Software Development] zgfg:
Does Zygisk show enabled on the Magisk app, main screen, top?

Make sure you have no SELinux Permissive

Also no Riru modules and no XLua (you must manually clean remaining sh... files after removing XLua)

Or, if you prefer Riru, search on TG for alternative solutions instead of the Zygisk USNF here
[Android Software Development] pndwal:
... Further, please say device / ROM...

Have you tried with nothing Google in denylist except G Pay/Wallet, and all modules disabled except @Displax modded USNF after clearing Google Play Services data?

Especially, try it with MagiskHide Props Config module disabled or removed despite what @kdrag0n says. 😬 PW
[Android Software Development] voetbalremco:
On MIUI it's the other way around, Displax his mod breaks safetynet while the original module still works.
[Android Software Development] pndwal:
Please give details... I have Redmi Note 8T, stock MIUI... PW
[Android Software Development] zgfg:
Maybe if you have Xiaomi.eu

In that case you pass Play Integrity (that's relevant, not the deprecated SN, but you will also pass SN) without a need for USNF (although your Bootloader is unlocked) - but only if you don't have Magisk

With Magisk, you then also need USNF, but you can try instead SafetyNet Sensitive Props (eg, I use instead of USNF) - screenshot

That's bcs some versions of Xiaomi.eu already have USNF implemented to the ROM.

Otherwise, users would not be able to use Wallet, since they had to unlock BL to be able to flash the custom ROM Xiaomi.eu

However, that's specific to Xiaomi.eu - with the official MIUI and unlock BL, you can not pass PI/SN without Magisk and USNF
[Android Software Development] voetbalremco:
Yeah good point, thanks for the details.

I do indeed use Xiaomi.eu
[Android Software Development] pndwal:
Yup, @Displax mentioned issues with (some?) XiaomiEU custom ROMs (specifically) not playing nicely w/ USNF...

I guess you also have root hidden from Google Play Services attestation/Droidguard process com.google.android.gms.unstable and likely main gms process com.google.android.gms (added in denylist)...

Out of interest, do you still need the main gms process added to pass now, assuming your tmpfs mount path has become debug_ramdisk?

Also, I assume this won't work without a sensitive props solution even though the ROM itself will adjust some... Can you say S/N and PI checker results with only root hidden from gms (ie. Sensitive Props module disabled)?

And does MHPC module active (with nothing configured) also allow S/N / PI deviceIntegrity to pass (as alternative to SafetyNet Sensitive Props module)? 👍 PW
[Android Software Development] zgfg:
Xiaomi.eu, MIUI 13/A12 (since Nov 2022)

Magisk Delta latest 25210 with SuList

Its been long ago since I installed Sensitive Props module (at that time I really needed but seems that Husky had later implemented something directly to Delta)

Now I tested with Sensitive Props disabled and even uninstalled (and of course, with rebooting) and I can still pass PI, SN and all checkers I have (except Momo as usually) - I know that I really needed Sensitive Props for Ruru or SCheck but no more now

Hence I removed Sensitive Props

Second, since I don't have DenyList and by SuList everything except the root apps are implicitly in MagiskHide, I performed the mirrored test:

- I checked GMS unstable in SuList and after that SN and PI fail
[Android Software Development] pndwal:
Good to know it does work just by hiding root from gms after adding Magisk...

This is fully expected... Root must always be hidden from the attestation/droidguard ('unstable') process!

Can you confirm tmpfs mount path is debug_ramdisk w/ Delta Magisk and do the 'mirrrored test' with all gms processes checked in sulist except 'unstable' process?...

I'm still interested to know If debug_ramdisk mount path removes need for hiding root from GMS processes other than 'unstable' process* (DroidGuardService). In xbin tmpfs mount path days there was no need to hide root from GMS Core.

*Nb. service android: name=".droidguard.DroidGuardService", android process="com.google.android.gms.unstable"... This spawns new DroidGuard VM process if not already running, collects and communicates attestation data to DroidGuard and returns DroidGuardResult value to GMS.

👍 PW
[Android Software Development] zgfg:
Since Delta is Magisk v25, magisk --path is still /dev/<something>

and nothing is mounted to /debug_ramdisk, mirror is on different path - see the screenshots

Screenshots are after different reboots, hence /dev/<something> is always different
[Android Software Development] zgfg:
Btw, results are pretty strange:

- SN fails, tested both with YASNAC and SCheck

- PI passes, tested both with PI API Checker and TBChecker
[Android Software Development] pndwal:
Wow... Would expect all fails w/ old but post xbin path... Can you show YASNAC Jason?

Maybe hiding root from GMS Core was for some specific S/N check/anomaly only... Failure at basicIntegrity level (unless unevaluated?) Did seem strange it was needed at all, but I never saw/don't recall comments from John...

Will have to test w/ debug_ramdisk as path later... Thanks, PW
[Android Software Development] Zatrerr:
Hello,

Does this project also aims to pass emulator checks ?

Also, instead of fooling safetynet api, why can't we simply modify the applications' codes to change all binary values returned by Safetyet api ?

Please be indulgent, i'm new to this field ^^
[Android Software Development] JazonX:
Displax Mod of SafetyNet 2.400 New 1.3 version released

Releases · Displax/safetynet-fix

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

github.com

With the latest of Delta by Husky (Which is still on 25210) - Samsung S23 Ultra June Patch doesn't boot.

Works fine with official TJW Magisk 26.1

With Husky things used to work pretty much on its own, just USNF was required.

Now switching back to Official Magisk, So if anyone can do a quick summary, I'd be very greatful!

(eg - Which modules needed / shamiko needed again or not etc)

Thanks a ton!
[Android Software Development] Nergal di Cuthah:
Depends on your purpose and apps. For me everything is fine with just usnf 2.4.0 mod 1.3 and deny list. For others they need shamiko or HMA or both. Still for others Magisk fork "alpha" is required with its native zygisk bridge.
[Android Software Development] JazonX:
Thanks a ton, Absolutely loud and clear - That was a good catchup.

By Magisk Alpha - do you mean Magisk Canary on the TJW GitHub?
[Android Software Development] Nergal di Cuthah:
No "alpha" is a fork (someone else's project based on the magisk source code). I don't know much about it but, it's maintained by developers who contribute what they've learned, in alpha, to TJW magisk.
[Android Software Development] JazonX:
Absolutely clear and Thank you so much for the keywords.

I've found the TG Group and successfully installed Alpha.

Just my last question - With Shamiko running;

Should I add Google Play Services and Playstore to the Deny List?
[Android Software Development] Nergal di Cuthah:
Someone else will have to answer that as i have not yet the need for shamiko and have neither in my deny list. (am playstore certified, can get netflix and my 2 bank apps don't seem to care)
[Android Software Development] JazonX:
That's some Mad luck!

Congrats Mate :)

And thanks a lot for the help so far !

Anyone else here;

Just a quick question -

With Shamiko running on Magisk Alpha latest Build;

Should I add Google Play Services and Playstore to the Deny List?
[Android Software Development] WhoIsJohnGalt1979:
---posted in incorrect forum
[Android Software Development] pndwal:
Private group? Or public channel?

Not sure if 26101 Alpha built Native Bridge from Metagisk... My tests have been with 26102 for private group testing...

Never with Zygisk based USNF...

Not needed... PW
[Android Software Development] JazonX:
I don't think I came across the Private group. I got it from a channel where all discussions are only in English.

I'm currently on the attached version. Had to change the package name because RURU kept seeing it.

View attachment 5935791

Tested this on Fold 4 and S23 Ultra both, Both are working fine.

Will switch the Pixel 7 Pro as well, when I get time - since that too is still on Delta.

Too bad that Delta has ceased it's development.
[Android Software Development] u_no_fr:
Hi all

Is there any pb Foxmmm ?

I have installed the New release from Androidacy and I have java error message 😱
[Android Software Development] dagaco:
Good morning, let's see if you can help me.

I have magisk in version 26.1 with my denial list activated, I have also tried the Shamiko module and everything works fine except the "Bankinter" app, is a bank.

Tries to open the app and closes and reopens it constantly, it keeps flickering the screen until I close it from the task manager.

I don't know how to fix it.

Thanks in advance.
[Android Software Development] cemoibob:
message supprimer
[Android Software Development] zgfg:
Good for you that it works but it must be an old device with the writable System
[Android Software Development] cemoibob:
I mentioned in my message, my phone is the s4 mini i9195i (serranovelte).

to write in the system I rooted and used "total commander" to write in the system, then I removed the root.
[Android Software Development] zgfg:
Ok, you wrote but I'm not familiar with Samsung models

And I wanted to emphasize that System is not writable if you would have newer phone (like most others)
[Android Software Development] pndwal:
AFAIK, system is still able to be mounted R/W in most custom ROMs! 🤔 Maybe I've missed something but...

Apart from that, some info that may be useful for you or others...

ro.build.tags is among sensitive props that MagiskHide used to set to a 'safe' value, and from 24.0+ has been handled by MagiskHide Props Config, Universal SafetyNet Fix, Shamiko and other modules/ solutions for Magisk root...

ro.build.tags=test-key is not exactly a sign of root, but banks, Rootbeer, Microsoft and other apps have used that as an indicator of compromised/modified runtime environment since many custom ROMs leave this set to the generic/default AOSP public test keys supplied... As discussed here however:

https://source.android.com/docs/core/ota/sign_builds#release-keys

this is bad practice;

When an AOSP based ROM, custom or stock, is ready for release, builds should be signed using proper keys and ro.build.tags=release-keys will be properly set...

I don't know if you have official or unofficial PixelExperience ROM or if it's old, but I hope current official ROM Devs have better practices...

Anyway, while you're solution may work as apps often simply scan for "test-keys" rather than "release-keys" per code like

public boolean checkRootMethod1(){
String buildTags = android.os.Build.TAGS;

if (buildTags != null && buildTags.contains("test-keys")) {
return true;
}
return false;
},

your value ("true") could probably be successfully changed to "cream-cheese". 😜

Also, while 'root hiding' modules accommodate such ROMs (where Devs have really been negligent with signing) by spoofing build tags, users should be aware of the ROMs shortfalls incl. security holes, Dev's inexperience or care less attitude, and that better choices are usually available.

In official LineageOS for example, all the released builds are signed with LineageOS' private keys as had also been CM practice... Further,

https://en.m.wikipedia.org/wiki/LineageOS

Anyway, there's hacks and there's ROMs... And there's hacked together ROMs... 🤪 PW
[Android Software Development] cemoibob:
most roms are unofficial.

I'm looking for an official android 10 or 11 custom rom, but I can't find it.
[Android Software Development] dagaco:
Good morning, I would like you to help me make the Bankinter app work as root.

aplicación de Bankinter

I have tried with magisk 26.1 with shamiko, safetynet fix, hma in addition to hiding the magisk app.

Magisk delta with zigisk, sulist and shamiko in addition to hiding the magisk app and there is no way.

It goes into a loop of starting the application with a continuous screen flickering and a message is glimpsed that the device is rooted.

Video

I don't know what else to try.
[Android Software Development] WhoIsJohnGalt1979:
Sorry to hear that, I had read your earlier post and had tried the app and it really doesn't open and freezes the phone for a micro second or so. There is another banking app starling which doesn't work through the trusted channels of usnf shamiko hma bootload spoofer, devoptshide etc. At least starling opens and gives an very elaborate notification about the phone being insecure but bank inter doesn't even open. For the time being hang in there until something changes in the magisk world.
[Android Software Development] d8389:
It looks like Google changed something today :(

Can't add credit card to wallet.

CTS profile fail in test.

Yesterday added 2 cards and successfully used one today.
[Android Software Development] pndwal:
Are you using official USNF (broken for most) or @Displax's modded build (with fixes)?...

BTW, need your pass newer Play Integrity deviceIntegrity verdict since SafetyNet is deprecated... 🤠 PW
[Android Software Development] iwearthebelt:
I went back to USNF 2.3.1 MOD 3.0 by kdrag0n, MOD by Displax and everything is working fine. Just flash the module right over whatever version you're on . Once you have it installed it will show there's an update but just ignored it .
[Android Software Development] pndwal:
Do you have problems with latest 2.4.0_mod-1.3?... Fixes issues for most... PW
[Android Software Development] iwearthebelt:
yeah for some reason I couldn't get google wallet working properly . It was showing that i lost root.
[Android Software Development] pndwal:
Seems to work for me with new native bridge loaded Zygisk and all apps associated with root hidden with Hide My Applist LSposed module...

View attachment 5948993

See this post, and see post above:

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

Latest unofficial Alpha:

https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-88706505

... Of course native bridge loaded Zygis is how Riru was loaded since Riruhide was a thing. It's been tested in Shana's Metagisk fork since March and is built in Alpha, but should come to Official Magisk at any tick of the clock... 👀 🤠PW
[Android Software Development] GoJo ^^:
Thanks for this, by reading, it seems there are many version of this app (modded)? Anyway, i installed last one, 2.4, and after ticking google play and playservices in the magisk denyliste + reboot, i could finally get the app missing in the store.
[Android Software Development] pndwal:
Wow... Hadn't seen problems with June 18 update... Saw plenty had issues with v2.4.0-MOD_1.0, v2.4.0-MOD_1.1 and v2.4.0-MOD_1.2 however... Perhaps you could report problems in his thread... PW
[Android Software Development] pndwal:
@kdrag0n seems to have been too busy to fix issues (with new part-time spoofing from 2.4.0)... Many have no problems with general bank apps, but since G Pay/Wallet monitors device security issues even when not in use, Pay contactless setup will often fail... @Displax's latest modified build is what most are now using... 🤠 PW
[Android Software Development] mhrussell1:
Apparently it is already addressed here. I flashed the July update and when I tried to patch the boot.img file with 26103 it failed saying it was unable to patch the ramdisk:

- Device platform: arm64-v8a
- Installing: a8c4a33e (26103)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [4]
KERNEL_SZ [25038869]
RAMDISK_SZ [0]
PAGESIZE [4096]
CMDLINE []
KERNEL_FMT [lz4_legacy]
VBMETA
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Pre-init storage partition: metadata
Add file [init] (100750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add file [overlay.d/sbin/magisk32.xz] (100644)
Add file [overlay.d/sbin/magisk64.xz] (100644)
Add file [overlay.d/sbin/stub.xz] (100644)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Loading cpio: [ramdisk.cpio.orig]
Failed to process cpio: No such file or directory (os error 2)
! Unable to patch ramdisk
! Installation failed

I dropped back to 26102 and everything seems to have worked.
[Android Software Development] zgfg:
Yeah, reported also to Magisk gen thread and to GitHub.

If you already had root, Direct Install should have worked, as well as re-patching the previously patched boot.img.

Supposing, you have Ramdisk 'No' reported device
[Android Software Development] mhrussell1:
So, with 26102 applied, I have Ramdisk: Yes on the app. Are you saying if I now update to 26103 and do a direct install, it will work?
[Android Software Development] d8389:
WOW !!

the mod works.
[Android Software Development] zgfg:
I can only say that for me, on my phone worked
[Android Software Development] zandatsu06:
Is this module works in kernelsu?
[Android Software Development] pndwal:
Apart from the fact that this official USNF is more or less broken (@kdrag0n seems to be to busy to build fixes in PRs) and users generally use @Displax's forked builds now, USNF should in theory work with @Dr-TSNG's ZygiskOnKernelSU...

That should also work as standalone Zygisk with late official Magisk too, but I haven't succeeded with this on my Android 11 MIUI device yet... May try with latest Magisk Alpha fork soon...

🤠 PW
[Android Software Development] pndwal:
@Dr-TSNG , others

... Just tried latest ZygiskOnKernelSU w/ latest Magisk Alpha, and still no dice... All Zygisk modules fail...

Xiaomi Redmi Note 8T, stock A11 MIUI, latest @Displax USNF modded build, latest Shamiko, latest LSPosed... 🙁 Maybe Shamiko still conflicts... 🤔 PW
[Android Software Development] zandatsu06:
I'm on F3 Global Stock, Global Miui. I think that's a con for using KernelSU in the stock rom; you can't pass safetynet and play integrity even though you have USNF module. In custom roms, it's different; last time I checked, kernelsu could pass playintegrity without using USNF, maybe because of a built-in locked bootloader spoofer inside custom roms. For the meantime, i'm currently using magisk 26.1 with USNF mod by @Displax and it works great.
[Android Software Development] pndwal:
That's interesting as I can't see why USNF shouldn't work on stock as long as ZygiskOnKernelSU module and Zygisk modules incl. USNF are working per:

I assume you tried ZygiskOnKernelSU (+ USNF with KernelSU)... Which version?... (Latest fixes were only 3 weeks ago.)

... I've only tried it as a standalone Zygisk loader w/ MagiskSU... PW
[Android Software Development] zandatsu06:
@pndwal Yes, Zygiskonkernelsu+USNF by Displax in KernelSU manager, but i tried this like 2 months ago and didn't pass playintegrity in Stock MIUI Global... But i didn't tried the latest kernelsu yet and Zygiskonkernelsu+USNF to test if it passes playintegrity or not, maybe it's different now.
[Android Software Development] jacobyo7:
[removed]
[Android Software Development] zandatsu06:
@pndwal

I just tried now the Zygiskonkernelsu+USNF by Displax and it works great in stock global miui14

View attachment 5953083

View attachment 5953079

View attachment 5953081
[Android Software Development] pndwal:
Thanks... It's not clear, is that using KernelSU or Magisk? PW
[Android Software Development] zandatsu06:
KernelSU Manager using Realking kernel
[Android Software Development] zgfg:
Have you tested with (primarily) TB Checker, then also Ruru, Oprek and SChecker (RootBeer is old and limited)
[Android Software Development] googleDich:
Hello.

I am using samsung galaxy note 9 phone and i want to hide root. I've tried everything that I know of and still can't hide it completely. When opening the momo application to check for root, the message is "SELinux rules are modified" and "init.rc is modified" displayed. Please show me how to fix it, please.

View attachment 5953319View attachment 5953321
[Android Software Development] zgfg:
Used magiskboot tool to unpack boot.img, replaced kernel with the kernel from that KSU for Lisa (but for AOSP), repacked by magiskboot

Tried the repacked new-boot.img by:

fastboot boot new-boot.img

it did boot but the keyboard did not work and I was not able to enter the pin

Hence that KSU kernel was not good for my Xiaomi eu ROM
[Android Software Development] pndwal:
You don't need initrchider... You have Shamiko...

You don't need MHPC module w/ USNF incl. fixes for Play Integrity...

Do you have PI deviceIntegrity passing verdict?

Custom ROM?... Selinux permissive?

🤠 PW
[Android Software Development] googleDich:
just yesterday i used custom rom. and more bug reports, here's a screenshot from

momo app. Please show me how to fix it.