yashsingh1/xdaforums huggingface dataset:
[Magisk] badabing2003:
Of course it is possible.

For anyone who finds using command line tools challenging or PITA, there's always the UI option to get the xiaomi print and put it in the right place automatically and killl DG.

You just have to do till step 4

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] pershoot:
I have noticed when Wallet has truly ceased functioning, it cannot submit payments, in a non-contactless (i.e. non-NFC) form, also. I use Wallet to submit payments for another application which does fail, when this scenario comes up.
[Magisk] Claus….:
“Now we have just seen the latest examples of Google’s “Play” style of Android becoming ever more like iPhone. According to reports, users with rooted devices—taken outside the semi-walled garden—can no longer use RCS.”

Google Restricts RCS Messaging On Some Android Devices

Why Android is changing forever…

www.forbes.com
[Magisk] esatch:
OT I'm not a native speaker, I had to google it but ROTFLMAO

🤣🤣🤣
[Magisk] zgfg:
Actually, no need for 3rd pty news, RCS issues have been extensively discussed from the first hand, in this thread on the previous pages
[Magisk] HippoMan:
I've read that RCS does still indeed work on unlocked/rooted devices that are successfully spoofing DEVICE integrity.

I don't use (nor want to use) RCS, so I'm not in a position to check this.

Spoiler content hidden.
[Magisk] pershoot:
Yup, RCS apparently now uses Play Integrity and will fail if you do not pass DEVICE. I and others got caught up in this; in a silent fashion might I add, hehe.
[Magisk] vegetaleb:
Flashed a new custom rom today, Magisk, zygisk and lsposed all installed

Magisk hide list done

Magisk hide app done

Installed playintegrity fix module and rebooted

All bank apps are still not working because they detect root

What did I miss?
[Magisk] pershoot:
Try Shamiko (switch off Enforce DenyList):

Releases · LSPosed/LSPosed.github.io

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

github.com
[Magisk] pndwal:
As @beeshyams mentioned, MEETS_BASIC_INTEGRITY seems to be needed for such payments (1/3 pass). I said

You will be able to make those payments with in this scenario also... I think the failing scenario you mention is with loss of BASIC_INTEGRITY also (0/3 pass)... Ie. basic/online payments require 1/3, but contactless payments require a 2/3 level of deviceIntegrity. 👀 PW
[Magisk] pershoot:
I don't believe I have noticed a loss of BASIC when this occurs. However, the next time this happens, I will see if I can take note to re-validate / re-confirm and report back, for completeness.
[Magisk] aimless0079:
Did you wipe cache and data from Google play store, Google play services and wallet? I only have Google play store and wallet hidden and wallet works. Playintegrityfix has only just started working for me on Poco F3 lineageos 20 on the last update. Safetynet has to also pass basic integrity and CTS profile match.
[Magisk] crayoneater:
Happens right away. Just make sure you run killall com.google.android.gms.unstable after you update your print.
[Magisk] crayoneater:
(post deleted)
[Magisk] sawdoctor:
It does get banned. Xaiomi just do what we've all been doing finding our own prints from dump sites. Xaiomi EU just include an app to automatically update the print when it gets banned. Each time it gets banned chiteroman updates his module with the new print from xaiomi
[Magisk] fbirraque:
Let me know if you need to test any RC build after PlayIntegrityFork-CI_#170.zip
[Magisk] jrotaetxe:
Do not know if it is a sensible question, but I wonder if there is any tool to "expand" the folder system from a certain ROM in tar or zip format.

Just to look for a new prit. I have noticed something that indicates I will not succeed hunting in the fields I did previously, so I need more "power" to harvest properly.

Please, refrain to say I need a harvester....

Regards
[Magisk] pndwal:
Just add a rogue character in print value in PIF JSON, force stop Play Services and should have 1/3 before a test...

Guess it's possible that India G Pay (lacking contactless payment facility) does just set the security bar lower (1/3) however, and perhaps G Pay/Wallet builds w/ contactless simply require 2/3 pass for all payments(?)... 😉 PW
[Magisk] Vision:
Yeah, i can confirm, before 1 week i use this feature RCS normal, now i have tested it yet .

Unlocked BL, Magisk and fork v7 and before v14

Edit: Just send a RCS all normal
[Magisk] fbirraque:
Many fallen after the latest wave of block.

GitHub's Pif Repository now archived.
[Magisk] Iridule:
I had an issue where I was stuck in verify loop. Deleted data for messages and now verified.
[Magisk] kingpeppermint:
It seems roughly every 3 months that they update/mass ban so i think there certain 3rd parties like for example the card providers like Visa or mastercard that might be putting pressure and wanting results by purging every 3 months they can show progress with minimal efforts. and because they leave some behind, they can rinse and repeat a few months later.(almost every big companies modus operandus in a nutshell these days)
[Magisk] Iridule:
@badabing2003 can PF dump prints from Android TV or watches?
[Magisk] badabing2003:
Yes if you connect it to PF (USB or wireless, either would do)

View attachment 6075783
[Magisk] droidman1992:
For anyone who is having problems running the autopif.sh script in Termux. Please make sure you have the latest github Termux and you run "pkg upgrade" at least once. You can then run the script directly from the /sdcard/Download directory as su. The final step is to then copy the custom.pif.json to "/data/adb/modules/playintegrityfix". After this, the play integrity should pass when you check. It's not a difficult process and it's the best we currently have.

I'm trying to figure out how to make termux remember command history so I can make this process super streamlined.
[Magisk] Slim2none4u:
after running, 3 dots top right, create shortcut.
[Magisk] badabing2003:
And don't forget to kill DG before testing.

As for history, just type history

You'd get a list of historic indexed commands (most recent last)

Find the number (index) next to your command and just type !n

Where the n is the index.

For example: !17
[Magisk] fbirraque:
I would like to know if it's possible to get/extract build.prop directly from the ROM Fastboot image file and how to do it?

Once GitHub's PIF Repository hasn't any pif.json that works anymore this's my best guess to find a not public one.

Let me know if you have better idea of how to search a new personal pif.json
[Magisk] Nergal di Cuthah:
While i haven't found a working private print, i have learned to make an "oreo dump cake" from a variety of sources

View attachment 6075849
[Magisk] majorfigjam:
Depends on the maker of the "fastboot image" - you need to identify the brand, google for any special tools, or start with 7zip Zs and see what you can find. For example:

Google - 7zip should do

Samsung - 7Zip Zs about 4 times over from odin

HTC - needs RUU decrypt

Moto - sparseconverter to start with, maybe an image mounter.

Other brands may differ.
[Magisk] zgfg:
In addition to the answer above, for Xiaomi Fastboot ROMs you will need Payload dumper to extract images from the payload.bin

Then, if you encounter qti prints in the /system build.prop, use the /vendor prints from the real, certified Xiaomi ROM.

But that would probably apply only to the newer MIUI/Android ROMs that are not suitable for donoring anyway
[Magisk] Umgak:
Some other tools I've found useful:

payload-dumper-go: Extracts payload.bin files, often into EROFS images.

GitHub - ssut/payload-dumper-go: an android OTA payload dumper written in Go

an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.

github.com

erofs-utils: allows for dumping of Enhanced ReadOnly FileSystem (EROFS) images, which 7zip doesn't support.

https://github.com/sekaiacg/erofs-utils

dat2img: Allows for unpacking of system.new.dat and vendor.new.dat sparse images, which sparseconverter does not support.

https://github.com/danielmmmm/dat2img/
[Magisk] jrotaetxe:
Hi, just a mad idea

Is counter-intuitive about the function of a cached image but we know the prints have some persistance once banned... Can we extent their persistance forever playing with the cache?
[Magisk] Claus….:
Thanks @Iridule

And no one thinks that this latest ban is related to RCS? Guys, if it is reported by Forbes that they are preventing RCS, than the ban must be related only to that.

And if that hypothesis is true. Do this information help in anyway? @chiteroman @osm0sis @badabing2003
[Magisk] beeshyams:
You may be right, but

Correlation does not imply causation​
[Magisk] zgfg:
Prints have no persistence.

Only eg Wallet csches the last PI result for some time but after that it will call the Play Integrity checking again

Every time you manually request (through SPIC, PI Checker, etc) or an app requests (Wallet, etc) PI attesting, the app calling PI test will take the timestamp and create a random nonce and will include to the PI testing request.

Final and signed verdict from G server again comes with the timestamp and nonce from original request and the calling app will check do they match

Hence if you submit an old passing verdict (or verdict from another phone), that verdict would include a wrong timestamp and wrong nonce, and originating app will dismiss that fake verdict

Also, you cannot re-sign that old verdict (with your new timestamp and nonce) since the verdict must be signed by the private G key

Similar q have been asked and answered/commented in more details couple of times.

Take a look into the official G PI attesting API for more details
[Magisk] Claus….:
No, correlation do not imply causation. You are right, But, what is the chance of that coincedence?

If you beliave like some of the people on the forum that it is some intern that has notning else to do, is banning without no need for approval? Without it is a task of the company? And where Google layed of people, you think they r not busy with reaching they real tasks of the company?

Or that Google has time to watch this Forum without any true goal?

I know where I will put my money.
[Magisk] beeshyams:
I have no rational answers

Neither an interest in contradicting you

Merely pointing out a possibility
[Magisk] Jirachilover:
Really good answer, thanks.

So from my understanding, the only way that doesn't involve spoofing prints is to decompile apps that are doing this check and rewrite the code to remove the actual API call to PI to begin with...💀

it's over...
[Magisk] 4sz0m:
That Forbes article is pretty much reactive to what's been recently said in various forums and quotes some of our (or our members') conversations. I don't think it has much relevance.
[Magisk] 4sz0m:
To close this topic. My Wallet is back to green after 48 hours. While this now takes much longer after regaining device integrity with a new print, it has zero functional impact on paying with Wallet. So do not worry, if your print gives you 2/3, you will be able to pay instantly.
[Magisk] Claus….:
I think it has more relevance than many other assumptions, but I will leave it here.
[Magisk] okij:
I'm wondering if this random nonce actually might not be fully random, but has e.g. some device props coded within.

This way Google could double-check if a PI request is valid.

So - if my theory is true - maybe also the process that creates the nonces needs to be spoofed.

Please forgive me if I'm totally wrong with my theory. :) But if I'm not, this could be some food for thought @chiteroman @osm0sis @pndwal @zgfg and all other clever guys on this thread.
[Magisk] Umgak:
The returned nonce is required to validate requests. Editing out the check would be the same as a failed verdict, since you wouldn't have a passing nonce to validate with.

Unfortunately, while it is true that it's not fully random (computers and the universe itself never truly are), unless you have a time machine or quantum computer, you'll never break that.
[Magisk] D_JWhite:
So I feel like I maybe a little late to the party here, but I'm trying to get my head around using different FPs.

I've read osm0sis' guide, and get what I'm doing to get hold of the FPs, but how unique are extracted FPs? How does one spoofed FP differ from another? It's ROM release to ROM release? Can you check if it's been banned before applying/extracting?

EDIT: Nevermind, just found the FAQ! 😅
[Magisk] yeswap:
What element of the Wallet app changes to green when certain conditions are met?
[Magisk] zgfg:
deleted
[Magisk] D_JWhite:
I was wondering if I was quick enough to edit my post! 🤣
[Magisk] nrd\:
Just a question, I've tried to find but I don't think I have found an answer or explanation regarding the dump rom? fingerprint.

All this talk about fingerprint I get the gist of it but I'm just trying to understand the actual part about the fingerprint use, the uniqueness and how it's generated.

If you download a rom, is the finger print always the same?

Reason I ask is on the dump sites we are using, if there is one model phone and there is one factory rom dump in the list, for example Google Pixel 5 a14 latest one, how is that fingerprint unique?

Because I and the next person across the world who is also looking for a fingerprint, from the rom dumps will use the same fingerprint ?? No?

If I download the rom from Google or manufacturer source won't that fingerprint be the same as per that dump site? Wont that fingerprint be the same across many users that use it?
[Magisk] wfred:
haven't used my phone to pay for anything for about a week, until I went to buy a granola bar this morning 😢

My original HTC 8 print fought the good fight since 11/21 and it looks like none of my other 32 prints work now.

So autopif.sh to get a working print until the watch I ordered on eBay arrives.
[Magisk] 4sz0m:
By "green" I meant "meets security requirements" and you should be able to pay with Wallet.
[Magisk] kylechen:
I was thinking,

Since the virtual technology is so advanced now,

Maybe one day we can run a virtual machine (or environment) inside the phone, the virtual machine fully clone a locked stock older android phone.

So any app that needs PI check, wallet bank netflix etc, running in the virtual machine "thinks" they are in a safe environment.

While we can hack the actual phone whatever we like.
[Magisk] Vision:
I read for lot users say have 50+ FP working before the mass block it and now almost none.

For that i search and try to find some FP and when found 5 etc. and works, i keep only this and not search again until Google block it one by one.

After the mass ban, i try the same more than 100+, what i understood? Nothing and my eyes hurt
[Magisk] V0latyle:
You're mostly correct. The only unique properties to a particular print are those related to the specific build - but they're only unique to that build, so all devices on that build will have the same print. There's a finite number of Android builds out there in the Androverse. So, if you and another person just happen to choose the same build of the same ROM on the same device, then yes - you'll both be using the same print.

That's why we were trying to make the point, at least before Feb 29th, that it would be best for people to select a print at random, so as to reduce the number of people spoofing the same print. Our theory was that prints in common use (like the current Xiaomi.eu print) would be noticed and broken faster.

We are currently "behind the power curve" so to speak because out of the multitude of previously working prints, very few still do, and as of yet we don't know why. As an example, one of our members had found more than 6,000 prints out of more than 50,000...but retesting after Feb 29th has resulted in less than 5% of those still passing, and we are relatively certain 98% of them were not being used by anyone.

Because some prints still work, it doesn't quite seem like specific prints were targeted, although most of @TheFreeman193's PIFS - at least the ARM, ARMv7, and ARMv8 ones - are all now "broken".
[Magisk] yeswap:
Thanks
[Magisk] batboy00:
Xiaomi fingerprint does not seem to work anymore. Just tried to check PI and I only have basic integrity. Last 3 days it worked, but not anymore for me.
[Magisk] Captain_Throwback:
Still working fine here.
[Magisk] kocsogfax:
I have tried xiaomi pif on MI 9, it's not working now, fail for basic too. It's worked and passed device yesterday!

But i can pass basic with any pif from TheFreeMan193 on MI 9, interesting...

But xiaomi pif's still working on mi 11 ultra....
[Magisk] GabbyWC:
The public fingerprint still passes device integrity here. Restart your phone and check again. It is possible for random and temporary integrity failures to occur on occasion.
[Magisk] kylechen:
I think differently.

I think, if suddenly ban all the root users around the world (a huge number of people), it will backfire and make the headline news.

It will trigger the movements like the "right to root", "right to own device", "android no more freedom" etc. when you can have a rooted phone but no app will not run on it like a Nokia.

In the future more APPs will use PI, it fully disables the adblockers and mods etc. without extra costs. That's their wet dream. No root, no mods, max ads and max profit.

They are working hard on this feature when 0 case bank fund got stolen because of the user root (obvious reason). Like the vape ban all around the world, it is all about money, using the excuse of "for your own good".

If I am a google staff and got the task to block root forever, I will do it like this:

Slowly giving root users more troubles,

Soft-ban root users little by little,

Leave a small window for the die-hard root user, so they try really hard to stay root, but won't go on the street to protest.

More people are tired of wallet/bank randomly stop working, giving up root.

When the root user group is small enough, ban them all.

Making all new phone hardware attestation, making all new APPs with strong check.

"Root" is in history book.

The best way for us to fight this, is not trying harder finding some stupid Fingerprint.

Go protest! Go make the news! Go educate public how google uses these dirty little tricks and their market dominance to secretly wall-up the once-freed android system.
[Magisk] batboy00:
Maybe Google is deploying a new version of Droidguard by region (expected for this beginning of the week), so some could still pass device integrity currently. I literally did not change anything between last days and now. Even after a reboot still pass only basic integrity. Region France and Xiaomi Redmi Note 10 5G. Pretty ****ty this cat and mouse game now..
[Magisk] Vision:
Right now test it Pass 2/3
[Magisk] chiteroman:
v9.7.3 only run resetprop when unstable process is called. Are you sure Starling works after an attestation?
[Magisk] Hkntai:
Yes it was working at first but constantly forcing the app to restart it eventually catches it. Can't say for 9.8 since that doesn't pass device integrity for me
[Magisk] Hkntai:
And 9.8 suddenly started working. Wack lemme try removing the sh
[Magisk] spida_singh:
Thanks, that worked,but only get basic passing,not device.

I'm guessing for my setup the .sh is required but then trips starling.

Assuming that's just what it is right now and there is no way of masking what service.sh does from Starling?
[Magisk] Hkntai:
There's one thing I don't understand though and it's why my device fails device integrity. Even on a stock boot image. Is it possible it is because I am on a QPR beta?

I've attached my props.
[Magisk] Hkntai:
Just when I post my message I find this https://issuetracker.google.com/issues/301354666

If anyone is wondering why safety net is failing on Qpr beta this is most likely why

They say the issue is resolved but I have my doubts
[Magisk] Hkntai:
Nvm figured it out Android 14 QPR beta builds aren't Compatibility Test Suite (CTS)-approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 14 QPR beta builds.
[Magisk] liver20:
Can you fix CaixaBank safesign app ? 9.7 still not work
[Magisk] habtm:
I have installed magisk delta with the crdroid rom on my little X3 pro, the thing is that I can not make safety net pass for nothing, and hide the Google apps, activate zygisk and did everything but only happens safety net a moment after I turn on the phone, and then just fails
[Magisk] Ginosius:
I'm using this module with Magisk Alpha with:

- The Magisk app hidden (renamed to Settings)

- Zygisk enabled

- Almost everything added to the DenyList

- Enforce DenyList turned off (default)

- Shamiko v0.7.4

- No other modules

Everything working fine and I'm still stealth to this day, but all I care about is Google Pay anyways.

I'm on a OnePlus 7T Pro running the official LineageOS 20 with NikGapps.

I've used it with Husky's Magisk Delta before, but that started failing when he switched over from MagiskHide to the mount/unmount stuff.

So Magisk Alpha it is then.

I have the same setup running on the Nintendo Switch running Switchroot Android and Netflix is still showing up in the Play Store :)

Very nice, great success (borat voice)!
[Magisk] oled65cxpua:
I saw these was some discussion of Faceapp earlier. Has anyone figured out how to pass the ingregrity checks and make all the filters work yet? Do you know if the "Face Swap" filters also require the strong integrity check?
[Magisk] zgfg:
There is one filter that requires Strong Integrity - however, Strong Integrity requires locked BL and stock/official certified ROM. No other way

Few other modules require Basic Integrity, so use the module (version that works for you) to achieve

Some filters require subscription - you must subscribe

If I recall correctly, only one (first from the left) was 'free' of all that
[Magisk] son_91:
Please help me.

Android 13 Stock with kernelsu version 0.7

Using PlayIntegrityFix version 9.8

Thanks,
[Magisk] chiteroman:
Latest KernelSU + latest ZygiskNext + latest Shamiko can bypass Native Test v15 and Starling 😁

View attachment 6025208View attachment 6025210View attachment 6025209View attachment 6025207
[Magisk] chiteroman:
Failing BASIC = root or injection detected
[Magisk] spida_singh:
Is this also with your module installed?

Having KSU, ZygiskNext = No Starling Root Detection

Having KSU, ZygiskNext + Shamiko = Starling Root Detection

Having KSU, ZygiskNext + Shamiko + PI Fix 9.8 = Starling Root Detection

Very odd, using the same versions as you :)

I only use Open Webview (for Vanadium Webview), no other modules.

This will always vary device to device i think, its now about what combinaiton works best for the individuals phone / ROM.

Pixel 6 on LOS for me.
[Magisk] iruiz2:
Magisk, Magisk Delta or Magisk Alpha?
[Magisk] pndwal:
🤔... KernelSU... Alternative to Magisk... PW
[Magisk] Hkntai:
Getting same results. Shamiko leaks Zygisk Pixel 7 Stock is 14
[Magisk] iruiz2:
Thank you, just read about it. Too bad it doesn't support my current ROM (OOS 13 for OnePlus 9 pro)
[Magisk] Vision:
I agree with that, i write this before

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com