yashsingh1/xdaforums huggingface dataset:
[Android Software Development] christantoan:
Thank you for the info!

Nope, I didn't know this as well (though I never had a case where I want to reset Magisk's settings; always how to retain it when I need to reinstall Magisk). Thank you for the additional knowledge!

Yeah, this is just a shot in the dark as I have no idea on how to repro it unless with a clean install. Though I'm curious as to why I'm so behind on G Play update. I thought the point was to have Google release it every month to all devices.

Thank you again!!

Yeah, I'd like to use an alternative I can find any.

Spoiler content hidden.

Thank you as well for your kind words!

I'll try to edit it a bit then later post it.
[Android Software Development] rodken:
I would agree that TWRP just provides an easy avenue to install ROMs for the legacy devices out there, without requiring a computer along with a few other utilities, like formatting data, and installing mods that would otherwise require root access.
[Android Software Development] 73sydney:
Genuine human interest question: have they let you down out of the bell tower for the holidays?

Rumour has it they may be looking for a new head of the moderator council since The Man doesnt look like returning anytime soon, i remember he specifically said to me last chat we had that if he was in some way indisposed i should step in and keep things pointing in the right direction

Granted thats not verbatim what he said....but i think the gist is enough
[Android Software Development] locolyric:
yes.

maybe need to newer version of shamiko to hide it.

thanox nor hidemyapp can stop this app to detect my hidden "settings" app.

but i still not yet try it on a10.

Check this link for the solution.is so simple to bypass on the latest version.

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-87900057
[Android Software Development] pndwal:
... Was in Broken Hill for 5 weeks a couple of months ago now... 😝 Been back in Sydney, but spent last week in Taree... Great food, not-so-good coffee... Long week, just got back tonight, couple of weeks off with family now... Thanks for asking...

Yup, we're all missing the quasi Aussie (Didgeridoo man from Sweden)... And you may be well suited to hold the fort; you're both walking contradictions... (But praps not the same sort!?) ...

I'll be sorry if he doesn't return too...

I love your license mate... It's like... like poetry!...
[Android Software Development] pndwal:
Good point... I'm using Shamiko 0.6 (126) (and it's working)... PW
[Android Software Development] 73sydney:
you mean youve been down from the bell tower AND back in town for weeks and you wouldnt reach out and let me and the bear buy you a coffee, well if thats not a snub i dont know what is :)

im hoping The Man makes it back in the new year, his guidance is missed in a few key areas
[Android Software Development] ipdev:
Watching for Pigs on the Wing. ;)

Pink Floyd - [ YouTube ] - Animals​

Cheers. :cowboy:
[Android Software Development] frostdragneel:
Can I know what magisk module do you use other than Shamiko?

Bcause I use the same version of Shamiko and tng ewallet didn't work for me (both 1.7.86 and 1.7.87). I had to use v1.7.84 as that the only version that works for me.

This is all the module I use... I'll try to reinstall safetynet-fix back after this... It broke my gms before...

View attachment 5794743
[Android Software Development] pndwal:
I put the details re. TNG eWallet here:

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

... guess you may not have HMA for LSPosed...

Nb. I can use official USNF module for passing deviceIntegrity verdict in new Play Integrity API (it's Android 10 stock ROM device)... I was using @Displax mod/fork when I first tested TNG app, and can confirm detection is bypassed using either on my device...

You haven't given setup / device details, but you will of course probably need @Displax USNF mod/fork currently if using A11+ or a custom ROM...

🤠 PW
[Android Software Development] frostdragneel:
I was using an A12 custom ROM (ig this is the issue?)... I will try the fork USNF version and update any info once I'm done with the testing...
[Android Software Development] pndwal:
Almost certainly need @Displax modded USNF... Use Play Integrity API Checker to test...

Nb. I had also both taken Hide the Magisk app and hidden further using HMA... PW
[Android Software Development] Displax:
Little update of my MOD with adding "Hide "Enable OEM Unlock" setting"

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517
[Android Software Development] wyt18:
Thanks! I'm using your mod 2.3.2, on a Samsung s20. Should I change to 2.3.1 mod 2.1?
[Android Software Development] Displax:
Yep
[Android Software Development] pndwal:
Good inclusion... Just wondering if USNF if Shamiko already does this however (?)... in case it may be doubling up...

I think USNF is generally just for passing Play Services Integrity attestations by allowing basic evaluation type attestations to be used and to pass (I'm assuming OEM Unlock setting doesn't affect these) while Shamiko etc are usually adopted for hiding further traces of root... 🤔 PW
[Android Software Development] ipdev:
I have not checked in a while but..

Shamiko did not hide/adjust sys.oem_unlock_allowed.

It was (is) on my prop watch list but, I only started setting it to 0 thanks to HuskyDG. ;)

Github - Comment

Cheers. :cowboy:

Edit:

I also updated my prop check script.

Github - Commit
[Android Software Development] Displax:
Shamiko does not hide this ¯\_(ツ)_/¯
[Android Software Development] iwearthebelt:
Just wondering, do I need to disable or remove USNF 2.3.1 prior to installing USNF 2.3.1 (Mod 2.1) or do I install it and just leave the other one as is? Thanks!
[Android Software Development] Displax:
Yes. Not need to disable or delete it before installing new version.
[Android Software Development] iwearthebelt:
I was hoping it would pass "strong device integrity" but I guess that's just not possible with the bootloader being unlocked. Otherwise, it seems to be working fine.
[Android Software Development] Displax:
You're right.
[Android Software Development] EastonCo:
Hey there -

I have a Pixel 7 Pro with the following:

-Magisk 25.2

-Safety Net v2.3.1-MOD_2.1

-Running build T2B1.221118.006

I have been running with Magisk for some time now with no issues, until play services updated over night.

I am now unable to access my banking with cred.ai as it is popping up the error that the phone is"Rooted, unlocked bootloader, or custom ROM" and "Cred.Ai will not run".

I have ran into this problem before, were removing the magisk mod, rebooting, reinstalling, and rebooting again fixed it. Not this time. I have not been able to identify the issue here.

The biometrics do not function on Varo either, but this is less of a problem as you can still log in normally.

Any suggestions?
[Android Software Development] 73sydney:
sadly that app is not available to me to test for magisks effectiveness, but heres some things to check

1) are you passing Integrity Check (test with this app) - because you mentioned a google play services update - it *may* be that the bank has moved from the older safetynet model to integrity check

2) do you have biometrics enabled in any other apsp? is it working there?

3) does the previous USNF Mod 2.0 work?

fwiw i have a Pixel 6 Pro and did update to the newer USNF module last night, it did make mention of a biometric change in my bank app, and i had to unlock my bank app and re-enable biometric login, but i put that down to random weirdness (though its never happened before), but since you mentioned it, im just dropping this note in case it becomes "a thing". I know @Displax only made one change, but *maybe* it affects biometrics (some more than others) ?
[Android Software Development] EastonCo:
Hey, thanks for the quick response.

On that test I am passing device and basic, but failing strong.

The varo app has been doing that for a bit, I actually think the varo app has always not allowed biometric on the pixel 7, but the cred AI app just started. I hadn't updated anything yet and it started.

Yes, I do have biometrics working on other apps, even other banking apps and it works.

The previous mod stopped working when Cred AI stopped allowing me to use it.
[Android Software Development] EastonCo:
Well - I did manage to get this working.

I had to completely reinstall the factory image and essentially reinstall magisk and USNF 2.3.1MOD2.1.

BUT - Everything is working now.- Thank GOD. Even Varo. I was getting ready to pull my hair out.

GOOD THING TO KEEP IN MIND: You probably want to use the USB-C cable that came with your Pixel. I have tried many many cables over the years and I almost ALWAYS have problems with other cables. I think this issue actually can be traced back to a third party cable during the transfer of a file at some point. I have completely stopped using any cable that did not come with my Pixels. A majority of cables are not even close to the quality they need to be and the start corrupting when you try and use the throughput of USB-C.
[Android Software Development] 73sydney:
That was probably an extreme way to go, but at least its working! I wonder if a bit of judicious data clearing of the affected bank apps might have resolved the issue?
[Android Software Development] EastonCo:
Well, I didn't wipe my data. Just literally reinstalled the factory image and kept my data.

I did wipe the data from Cred.AI, but I had tried that before doing the factory image.

I had literally tried everything haha. I honestly do believe it came down to bad data transfer between the phone and the PC with a third-party USB-C cable.

It's actually very disappointing when you realize just how many of the USB-C cables made were not made to handle actual USB-C data transfer. I think it mainly comes down to thin wires and little to no insulation, causing cross-talk.

I have a TON of USB-C cables and the only ones I can get an image to transfer in full to my phone with are the ones that have come with my Pixels over the years. The ONLY other cable that works is one that cost $30 on Amazon. Moral of the lesson is - if you want a good USB-C cable, plan to pay out the nose.

Any cable you find at Walmart or a gas station, or only for less than $25ish, it's more of a USB-C "compatible" cable than anything lol.

Anyway, thanks for your input!

Hopefully someone else reads over this and changes out their USB cable!

For those, here is a list of the problems I experienced because of a bad cable:

There are certainly more things that happen with a bad USB-C cable, but these are some of the ones that were obvious when working with ADB. If you are flashing something a bit riskier, I would not trust any cable except the official pixel cable or a very high end one. That's just me though.
[Android Software Development] ipdev:
Cable and ports make a difference but..

Through the years I have used expensive and cheap USB cables.

Factory/OEM and Aftermarket

Currently I use a mix of cables.

ANKER | SABRENT | UNI

The main difference I noticed was the USB port used.

I still use USB-A ports (cheap USB-C Hub) to connect to devices.

The 2.0 port burned out a few months ago so, I have been using the 3.0 ports without issue so far. 🤫

For USB-C devices, I use a UNI cable for adb and fastboot.

Had an issue with ANKER or SABRENT on one device so, I just use UNI on all.​

For USB-Micro devices, I use a SABRENT cable for adb and fastboot.

Had issue with ANKER or UNI on one device so, I just use SABRENT on all.​

The cables I use for charging are mostly ANKER but, there might be a UNI or SABRENT in the mix somewhere. 🤪

Cheers. :cowboy:

Edit:

PS.

I use ANKER cable for charging since some devices (samsung) would not go into rapid-charge with SABRENT or UNI cables. 🙃
[Android Software Development] m0han:
This is useful info. 👍
[Android Software Development] rodken:
I always knew that the rabbit hole regarding Cable and Ports was and still is pretty deep.
[Android Software Development] 73sydney:
Ports indeed do matter, my favourite port story comes courtesy of the Samsung S20+ 5G i just shifted from AND my Asus Zenbook UX410...has 1 USB port on the left, and 2 on the right. I still use USB-A to USB-C cables

To get into download mode, you hold down the Vol+ and Vol- and plug the cable in.

Do not try doing that on the left hand one, its USB3.0 (made this century)

You think id remember i need to unplug gear from one of the right hand ports and use one of them, wouldnt you...wanna guess how many times ive scratched my head before remembering :)

p.s. Pixel 6 Pro doesnt care which port you plug it into to do anything
[Android Software Development] EastonCo:
I only use USB-C <-> USB-C cables anymore, which I have a ton of from being a Pixel fan since the beginning lol.

I wonder who makes the cables for Google, or if they contract that task out.

Yeah, lol... It's simple on the surface...
[Android Software Development] PhantomApollyon:
In case anyone is looking for confirmation, this appears to be working fine on a OnePlus 8T running Lineage OS 20. (Android 13)

EDIT: disregard, I was mistaken. It does however pass using the v2.3.1-MOD_2.1 fork here: https://github.com/Displax/safetynet-fix/releases
[Android Software Development] pndwal:
PSA:

Well it's here! 🎉🎊👍 ...(For those really keen to try it early 😜):

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

... So proper hooks to set fingerprint at runtime only, then revert w/ new dynamic/scoped solution as mentioned... Thanks @kdrag0n! 👍

Guess @ipdev may be first to report on this... At least he won't be (among those) whinging about early release... 🤪 😋 PW
[Android Software Development] Snuuuuupy:
I'm looking for build instructions, does anyone have them? I see in build.sh several dependencies are required, including:

code/android/sdk/ndk/21.4.7075529/ndk-build

java

gradle

I'm not sure if installing those 3 and then running build.sh will work because no build/compile instructions are provided.

Can anyone who has built this before chime in with some instructions or hints? Thanks.
[Android Software Development] pndwal:
Latest Universal SafetyNet Fix (yup, no name change yet... by June? 😝) Release notes:​

v2.4.0 (early access)

Pre-release

Highlights​

Play Integrity bypass without breaking device checks or causing other issues

Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109)

Other changes​

Updated instructions for newer Android and Magisk versions

Better debugging for future development

It's taken a while to find way to bypass Play Integrity that doesn't require spoofing the build fingerprint permanently, but I wanted to make sure this module doesn't cause any unnecessary breakage. Just like the original goal of Universal SafetyNet Fix, this minimizes adverse effects by spoofing dynamically at runtime only when necessary. Enjoy!

👍 PW
[Android Software Development] 73sydney:
/me waits for the usual people asking the forum elders via PM for copies of the early access module....because its happened before

hint: most of us wont/dont have it, so dont do it, any one asking will be reported and get a nice little holiday if not their account closed as this counts as requests for warez....just a tip

everyone will get a copy free when kdrag0n feels like releasing it widely....no one will die if they dont have it right now
[Android Software Development] shorty9210:
Hope everyone's start of the year!! But I just wanted to drop in and just let everyone know how my smt500 galaxy tab a7 is passing SafetyNet and two API levels and just really only using SafetyNet with SafetyNet mod... well hopefully thus helps others so they don't have to use the other modules that could end up bogging down there devices or just haven't been able to get any of modules to work at all!! Well continue to be a wonderful community oh and I use magsik 25 delta
[Android Software Development] ipdev:
Not this time.

No one time donation option this time. 🙁

If there was, I would give it a try. 👍

I do not have a Patreon account nor do I wish to create one. 🙂

---

I am currently using Displax's latest mod version with a slight change.

Still need to clean the scripts up a bit more before I (re)open a PR.

I am still not sure if killing GMS after boot complete would due anything productive. ¯\_(ツ)_/¯​

I still need to work on ASH(ifying) the script(s). 🙃

Magisk PR Comments

Double brackets seem to work in Magisk post-fs-data and service scripts but, better to make the script more compatible.

Years ago, I fixed a warning [: =: unary operator expected by using double quotes in single bracket statements.

Set of scripts I wrote to be compatible with Android, Linux, and MacOS.

mHideGP - commit

That was with text to text statements. Still have to double check format on numeric to numeric statements.

One of the reasons I started using double brackets. 🤪

Cheers. :cowboy:

PS.

I have no problems donating.

I have a donation account in my monthly budget and enjoy giving to support developers.

I am not a big fan of devs trying to buy my support by enticement like early releases and special builds.

- Note: Not the same as a free version and a paid version.

I have been sponsoring two developers on GitHub since the program started.

Jumped on it right away since Microsoft matched 100% for the first year. 🙃
[Android Software Development] pndwal:
Well that's as expected...

W/ Displax fork/modded USNF, this mod is all that's needed for both S/N and new PI deviceIntegrity as it introduces fingerprint prop spoofing targeting gms (read better than using MHPC globally set fingerprint prop)...

Hoping that new official USNF 2.4.0 continues to be a total solution for PI deviceIntegrity; seems it should if "spoofing dynamically at runtime" means every time droidguard/attestation service is called... PW
[Android Software Development] towe96:
Became a patreon to give this a try. Sometimes it passes MEETS_DEVICE_INTEGRITY, sometimes it fails.

Play Protect certification works now, but Google Wallet still says I don't meet security requirements.

OnePlus 8T on LineageOS 20.0, Magisk 25.2 with Zygisk and Universal SafetyNet Fix v2.4.0

Am I missing something? Everything was working fine under OxygenOS 13 before, but it still had the GPay SQLite Fix active (which is supposed discontinued, so I chose not to use that this time - should I have?).

Update: I tried out v2.3.1 MOD 2.1 - works perfectly fine, with no intermittent integrity fails. I delete Wallet and GMS data, and Wallet works fine now. The v2.4.0 is absolutely not worth it (yet?). I still wish Google just grew up and allowed users to opt-out of all this security theater.
[Android Software Development] 73sydney:
Sweet Just, not that thing

GitHub - stylemessiah/GPay-SQLite-Fix: A magisk module that ONCE allowed Google Pay to work on rooted phones

A magisk module that ONCE allowed Google Pay to work on rooted phones - GitHub - stylemessiah/GPay-SQLite-Fix: A magisk module that ONCE allowed Google Pay to work on rooted phones

github.com

I tried for so long to stop people using it, and they still wouldnt take the hint or actual words saying DONT USE IT.....it still triggers me when people mention it :)

your current setup is the correct way to go
[Android Software Development] towe96:
It's still showing up pretty often online. I've been using that for a good few years, so when I found out it had been discontinued / nuked, I was pretty stunned - I thought it had fallen the same way Magisk almost had (bought out by Alphabet to prevent development etc.).

Maybe a link one of the more current answers here; describing how it's supposed to be done with Play Integrity and the MOD versions (or v2.4.0 in the future) would help guide people to the current solution more easily.
[Android Software Development] pndwal:
Interesting... Wondered if might be issues w/ new "spoofing dynamically at runtime" method... I'm sure @kdrag0n will fix any niggles...

Would have been fine originally if you had passing S/N and PI deviceIntegrity and cleared Google Play Services and Google Play Store data, also Google Play Protect Service data if exists (A12+?) after those passed... Guess you didn't?

Cleared data as above, plus cleared Google Pay/Wallet data and rebooted* first?

Will have issues if PI deviceIntegrity is still failing intermittently too...

*Nb. Reboot before first use of GPay/Wallet is important to avoid issues (as some GPay/Wallet updates will install again), eg Activity list failing to populate...

Probably only the need to clear all data as above if detection has been triggered (after fixing PI deviceIntegrity)...

No... Ensure all SQLite modules are removed...

Good; ensure you did reboot after clearing before first use to avoid Activity list issues etc...

Nb. I believe you don't even need main USNF functions w/ your OnePlus model (w/ broken keymaster implementation?)... Will likely need it's 'sensitive props' function only... Nb MHPC module also includes/does this (unconfigured by default), and Shamiko may do the same (according to some users)...

Thanks for reporting your mileage w/ this...

Well perhaps we need to grow up and accept the brand new age of reason!... (That theatre is now just life.)

And G is basically aiding us to 'opt out' anyway by designing a system where strong integrity adoption is prohibitive for banks at present. (They didn't need to, and could have made it pretty much impossible for us if they wanted to as I see it. 😉)...

deviceIntegrity as the primary PI Device Integrity verdict won't last forever however... Enjoy it while it lasts. 😝 PW
[Android Software Development] pndwal:
... I've linked this from here more times than I can count... PW
[Android Software Development] 73sydney:
The problem is people completely ignored the advice of the author even when they were given it directly....when you have to nuke a repo, where the advice was also not to use it, to make your point, the problem isnt the author, its the audience :)

Also, we could do without the Magisk "bought out by Alphabet to prevent development etc" conspiracy nonsense thanks....