yashsingh1/xdaforums huggingface dataset:
[Magisk] Displax:
Looks like there is no need to set the derivative DEVICE_INITIAL_SDK_INT anymore, it works without it. So I cleanup java side (.dex) by removing this code. Anyone can confirm?
[Magisk] ipdev:
Pixel 6: Android 13 (20230705)

Magisk 26104 (6141bb5bb)

PlayIntegrityFix_3.0-test.zip

Labels: [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY, MEETS_STRONG_INTEGRITY]
Build fingerprint: google/oriole/oriole:13/TQ3A.230705.001/10216780:user/release-keys
Brand: google
Device: oriole
Model: Pixel 6
TestId: dGVzdGluZy1jZTAwNzI4OC1jMDA1LTQ4ZTktOGJiYS0xNDAxZjAzYWEzYTg=

Cheers. :cowboy:
[Magisk] chiteroman:
Maybe the props that get through native like bootloader status or first api level don't check Java code.
[Magisk] chiteroman:
View attachment 5960317

Yep, working

EDIT:

OH WAIT HAHAHHAH, in my phone can't check this because I disabled Java injection when you are using a xiaomi.eu custom rom XD 😂😂
[Magisk] acwcanada:
swer45's 3.0 and Displex's 3.0-test both failed even basic and device integrity. I am going back to Displex's 2.4.0-Strong, it is the only one which passed all 3 integrity on my Pixel 6 Pro with A14 Beta 4 Magisk canary-26104.
[Magisk] acwcanada:
Same outcome, failed all! With or without Shamiko.
[Magisk] chiteroman:
Provide logs pls this is very strange 🤔
[Magisk] acwcanada:
See Attached

P.S. Like I mentioned in my previous message, although basic and device integrity are failed, Google Wallet and all of my banking apps are working normally, strange?
[Magisk] Stillhard:
Confirmed, green green green
[Magisk] bansos_indomie:
Can i use microG?
[Magisk] xdauser1620:
All green for me. Motorola G60 Magisk+Shamiko+playintegrityfix.zip on PixelExperience A13 Rom.

EDIT

Strong integrity failed after google patched something now i only have basic integrity.
[Magisk] pndwal:
Yup, your playintegrityfix_3-0-test-zip gives strongIntegrity on Xiaomi RN8T! 👍 ...

Guessing need for DEVICE_INITIAL_SDK_INT setting may just have been an issue resulting from global setting for ro.product.first_api_level:

# Avoid breaking encryption, set shipping level to 32 for devices >=33 to allow for software attestation
if [[ "$(getprop ro.product.first_api_level)" -ge 33 ]]; then
resetprop ro.product.first_api_level 32
fi
}&

like Wifi calling broken (LV A13/33+ devices) etc...

Of course you've now moved this shipping level mismatch for hardware based verdict enforcement bypass from service.sh to Zygisk module to fix issues... Perhaps it fixed DEVICE_INITIAL_SDK_INT behaviour too? PW
[Magisk] pndwal:
Unless you clear data G Pay/Wallet (and sometimes Google Play Services) data, G Pay/Wallet contactless security can take days to check/reset "security" flags... Both to fail after deviceIntegrity fails and to work after deviceIntegrity is fixed...

Banks may also start to fail after clearing data when deviceIntegrity is broken... PW
[Magisk] pndwal:
This?:

https://xdaforums.com/t/module-play-integrity-fix.4607985/post-88786263 🤔 PW
[Magisk] acwcanada:
Oh! I didn't give a thought on this, you are mostly correct, thanks for the hints. Anyway, I have already tried so many times with swer45's and never able to make it work with phone, I am now going back again to Displex's 2.4.0-Mod-2.0-Strong, it just working perfectly with my phone. Until swer45 can figure out what went wrong with my provided log, I will stay with the Displex's.
[Magisk] pndwal:
FWIW, the process com.google.android.gms.unstable, previously referred to by modders (inc. TJW) as the SafetyNet process, is really the DroidGuard (attestation) process... It's probably high time we changed how we refer to it, particularly because SafetyNet is now all but dead but also because we know it's real name and function.

'SafetyNet' process appears to be a misnomer born simply from the fact that device integrity attestations sourced by that gms process from the DroidGuard VM were verified and returned using the SafetyNet API... Really the process facilitates the DroidGuard attestation service; SafetyNet was only ever an API that relied on DroidGuard data...

Details: The manifest file of the GMS application shows a service associated with DroidGuard:

<service android:name=".droidguard.DroidGuardService" android:process="com.google.android.gms.unstable">
<intent-filter>
<action android:name="com.google.android.gms.droidguard.service.INIT"F>
<action android:name="com.google.android.gms.droidguard.service.PING"F>
<action android:name="com.google.android.gms.droidguard.service.START"F>
<category android:name="android.intent.category.DEFAULT"F>
</intent-filter>
</service>

View attachment 5960475​

Credit: "DroidGuard: A Deep Dive into SafetyNet", Romain Thomas

https://www.romainthomas.fr/publication/22-sstic-blackhat-droidguard-safetynet/

-----​

Further, I'm fairly confident that since TMP dir is again fixed to /sbin or /debug_ramdisk (where /sbin is not accessible), we (probably) only need to hide root from the DroidGuard (attestation) process com.google.android.gms.unstable again...

MagiskHide only began adding main gms process com.google.android.gms when /dev/<random_string> was introduced as TMP directory (where /sbin is not accessible) using random seed (from Android 11?).

You may be able to test this but it seems @swer45 is now relying on original targeted hiding code instead of Shamiko for gms per:

anyway... 👀 🙂 PW
[Magisk] westruk:
You decided too soon that his setup was working.
[Magisk] pndwal:
Why?... Think @FredMontteiro is lying?... Or has he said it stopped working on either or both phones?

If either phone still works with UD (and I can't see he's said otherwise anywhere), clearly strongIntegrity is NOT enforced...

This was already clear since he confirmed updated UD was working with Samsung Galaxy A5, but since he got it working on a Xiaomi Mi A3 lacking deviceIntegrity it is also apparent that UD is not using either of these PI API verdicts.... 😬 PW
[Magisk] :
This seems very strange because Galaxy A5 is on Android 6 and the minimal version required for Uber Driver is Android 8...
[Magisk] De_Haos:
Does this module affect Netflix/Disney and Hulu?
[Magisk] pndwal:
Stock Android 8.0 (Oreo) is available for this... Stranger if stayed on A6! 😜 PW
[Magisk] pndwal:
For some time Netflix app has relied only on Widevine security level and stopped using Google device integrity verdicts although they may still affect whether app appears in Play store... You'll just need L1 Widevine DRM pass to decode HD content w/ Netflix... Not sure about the other apps...

🤠 PW
[Magisk] FredMontteiro:
https://xdaforums.com/t/need-help-uber-driver-app-not-go-online.4614295/post-88929179

LineageOS, as i said. 😉

Android 11.

Info about a5y17lte | LineageOS Wiki

wiki.lineageos.org
[Magisk] westruk:
I think this should be confirmed by other users in the community as well
[Magisk] De_Haos:
Except L1 loses when i unlock bootloder (OnePlus 11), so i guess this module won't work on Netflix.
[Magisk] CoinsClassic:
Oneplus 11 keeps Widevine L1 when bootloader is unlocked. (tested with CPH2449EEA)
[Magisk] De_Haos:
No when i first unlocked it was L3 previous Op models would keep L1 but not this model.

Check Op 11 and you will see, nobody got L1 which is a bummer.

I thought bootloader spoofer would work till i saw it doesn't work on OOS broken tree.
[Magisk] CoinsClassic:
Sorry to hear that it's L3 for you, but for my device it was L1 all along, bl unlock and rooted. Two of my friends also have L1 Widevine with unlocked bl. So I guess this is dependant on exact SKU?
[Magisk] De_Haos:
Dunno but had to relock to get L1 back.
[Magisk] pndwal:
I think you should read his saga linked above...

He had UD working on one device and worked on a second device for many days... He then went to lengths to publish the working method in detail to benefit others...

He's tested w/ TJW Magisk, Alpha, Delta and KernelSU it seems... We were all supposing wrongly (I was thinking UD was likely polling key attestation; nb. this is different/independent from Google integrity APIs) but he was able to get UD working on two devices...

If you think he's lying, say it (or other explanation)... I see no benefit or motive so I think you should wait for confirmation by other users in the community rather than cast unfounded doubt...

Other's said 'too soon' that UD is enforcing strongIntegrity AFAICS... Why is reporting this (contrary) success story 'deciding too soon'? 🤔

... I'm sure that you'll be trying this too if you're an Uber driver! 🙃 PW
[Magisk] westruk:
I think it's you, not me, who should wait for confirmation from other users in the community to reasonably claim that his setup is working.

I haven't seen any confirmation from other users about the success of this method.
[Magisk] pndwal:
Clearly it's a first... Of course that's why I reported it... But I had been following, helping with it too...

Further, the 'setup' for Xiaomi A3 is beside the point as it worked with minimal effort on old Samsung device first... That was enough confirmation to make claims of PI strongIntegrity enforcement premature anyway; weeks later and we have success with a second device!... Do we need 3?!

Really don't understand your doubts however... This is the kind of breakthru report most modders appreciate, especially those affected, and there's clearly several here... PW
[Magisk] Ginosius:
With v8.2 still no spoofing for device.

Meanwhile on v7.4:

8-29 09:50:22.041 5808 6051 I SNFix/Java: Spoof device props

08-29 09:50:22.043 5808 6051 I SNFix/Java: Spoof device props

08-29 09:50:22.044 5808 6051 I SNFix/Java: Spoof device props

08-29 09:50:22.078 5808 6051 I SNFix/Java: Spoof device props

08-29 09:50:23.371 5808 5857 D SNFix/Zygisk: Try to spoof first_api_level to 25, original value: 29

08-29 09:50:25.795 5808 5857 D SNFix/Zygisk: Try to spoof first_api_level to 25, original value: 29
[Magisk] pndwal:
Yup, OnePlus seems difficult, but may be able to get L1 security, eg this:

and more clues in that post (and other posts I've made)...

Even without L1, Netflix should still stream low definition video... 🙃 PW
[Magisk] chiteroman:
Try new version 👍
[Magisk] wfred:
Quick question:

I've come across a phone that passes using 5 different API levels, nothing else different.

So far as PI & bans are concerned, are those all the same device or are they treated as five different devices?
[Magisk] osm0sis:
When a print is banned it seems like the first API level doesn't matter, nothing will work, so I guess we could presume changing API level doesn't make for a "different" print, so just find the highest one that will work up to the original donor number.
[Magisk] sawdoctor:
Not only that people who have been critical of burning fingerprints have been reported to telegram for spamming so can't post in the group now
[Magisk] V0latyle:
Links to repos and dumps should be fine because though there's some working prints in there, it's up to the individual to find which ones. Besides, it's all public knowledge - Google has the details of every device that's been CTS approved anyway, and we've discussed at length the criteria for potentially working prints in this thread

What should be avoided is linking to speciific working prints, or collections of working prints. So for example if someone were to collect a batch of prints, test them all for Play Integrity verdicts, then keep only the working ones, it wouldn't be a very good idea to post that list.

However even if it DID happen there are hundreds of working prints out there, and as long as everyone picks a random one, I think we'd be OK. That's assuming that the minions over at Google wouldn't want to go to the time and effort to ban them all; personally I consider it more likely that they're going to update Play Integrity to detect mismatches itself.
[Magisk] Danny1980:
Hello,

thank you for this great project. My phone (Poco F3) is running Lineage with Kernel-SU. The module was working fine until Google bans the fingerprints. But now I have issues with the device_integrity-Check. The basic_integrity working just fine.

I have tried the latest version (currently 14.2) and the DEV v1-version (with spoofed properties from my old phone), but with no success. I also have rebooted several times and reinstalled the module, even checked for file in the module-directory.

Is this a known problem? Is there anything I can do to solve this?

Thanks in advance.
[Magisk] Imnoa:
Use Pixelflasher to create a pif.json and make sure it's in the right directory
[Magisk] Iridule:
I've made my morning hobby mining prints for safe keeping ⛏️
[Magisk] Danny1980:
Thanks for your reply, but there are no changes. The JSOn looks exactly the same as before (except I have filled BUILD-ID field). The properties are used when i watch the log, so there seems no issue with the file location. Shouldn't version 14.2 (without a custom fingerprint) also work, or has Google already blocked something there as well?
[Magisk] V0latyle:
You have to use a custom fingerprint.
[Magisk] Danny1980:
If I understand the latest version correctly, there is a fingerprint inside. It says "Plug and Play-version" So no extra fingerprint needed. The wiki also says:
[Magisk] D€INOS:
Why, you didn't seem to mind V0latyle link for the img dump of Pixel and Nexus phones?
[Magisk] Nodens:
Rare == Some device no one has ever heard before with no fps in online dumps. Get one of these and you'll probably keep using this until old devices become deprecated and HA becomes min requirement. There are a lot of obscure android devices out there. Specially non-phone ones.
[Magisk] Nodens:
One fp that I had that did the same, turns out it just happened to get banned during the 24 hours in between last check and me switching to osm0sis' fork. It's the no3 in his list if you saw it. If your json is correct and you had verified that chitos build was actually using it via logcat instead of the internal one, then I'm willing to bet it's the same case for you too.
[Magisk] D€INOS:
>4900 dowloads of v14.2, and as for as I know, 14.2's print is still working.

That's different oppose to the other +3 releases that went nuclear very early on.
[Magisk] osm0sis:
Only half joking here, but maybe Mr. Play Integrity is off for the holidays? 😛
[Magisk] V0latyle:
Yes, and if that print hasn't been banned, it will be soon. USE A CUSTOM PRINT.

...Which is public knowledge.

The only circumstance under which we might intervene is someone sharing confidential files or access. The Tadiphone dumps and the Google factory images are both publicly available.

He's off mining coal to stuff our stockings with
[Magisk] beeshyams:
Probable that Google is recalibrating their strategy. I am pretty sure they can pull the plug and ban all prints custom or mass downloaded
[Magisk] HippoMan:
If recalibration is indeed going on, I wonder what the chances are that the Googlefrinchians would be recalibrating in a way that will make things *easier* for us.

Anyone want to make a bet?
[Magisk] zgfg:
I think two releases were during the time when Xiaomi.eu users needed/used the PIF

But now they don't anymore
[Magisk] Danny1980:
I will, but this is not the point. If it doesn't work without the custom one(which can be faulty), how should it work with my custom one.
[Magisk] D€INOS:
Yep, and I after some considerations and your reading your I realised this and I agree. Having these repos linked here should mitigate all the posts about not finding prints. Hopefully...
[Magisk] GROOVYJOSHCLARK:
The funny thing now is that I can't update past PIF 14.0, or I fail. Updating to 14.1 fails everything, and I am uncertified, fails SN.

Rolling back to 14.0 works flawless again and I pass both integrity checks plus SN and am certified. I took a screenshot showing I pass both checks (with the date) as a screenshot (within the screenshot) so everyone knows it's real, valid, and taken from today's date/time with no funny business.

Take it with a grain of salt though, because since your post (the one I'm replying to) was like a week ago and 30 or 40 pages of this thread missed. Your post was the last time I read the thread so I'm REALLY outdated and am not planning to catch up with the 40 pages of reading. This could all be answered already and I don't know, but it works great for me using my setup with props. I have props setup and configured with option 1 and option 2, both forcing pixel 6 pro so I haven't bothered reading the forum since yours.

View attachment 6041672

View attachment 6041673
[Magisk] Nodens:
Making an educated guess, I'd say the actual index is the fp string itself and it is matched in the db that google keeps at the time of system image certification when OEMs submit them for that. Depending on the year they were submitted, they are probably at a different revision of the table schema with additional columns added over the years (and possibly omitted optional data (that may not be optional still in later revisions) by the OEM in the image submission process) . When those values are missing, from older devices, they extrapolate them (or at least an aproximation) most likely from the fp string directly with possible floor and ceiling set to safe values. Which is why lowering first_api is possible as if there was a value to check against it would not be. It is also quite probable that first_api is what is used to determine db version used, which in turn determines which values are mandatory and which optional, so dropping api level makes fps pass by reducing the amount of props checked.
[Magisk] osm0sis:
14.0 uses fallbacks for unset security_patch and first_api_level, so does your custom print have those missing? Feel free to PM me and I'll see if I can help you figure it out.
[Magisk] GROOVYJOSHCLARK:
Honestly, I have no idea, and am not sure I am using a custom print (I just used defaults everything). With Christmas upcoming, and end of year projects, I haven't had much free time for droid debugging / droid coding. When I did have time, I setup PIF 14.0, with MagiskProps (options 1 and 2 set to pixel 6 pro), and all works flawlessly with this setup. I am good and happy with GPay working, NF/HULU in Play Store, with being integrity passing for both, so I dont plan or intend to change or modify anything, until it breaks and I have to. I pass both integrity checks so I am happy!

Thanks for the reply and offer though! I am a senior sys engineer by trade, so I tend to live by "if I ain't broke, dont touch it"!
[Magisk] V0latyle:
I don't think you understand.

The module (14.2) includes a fingerprint of its own. This fingerprint is the same for everyone using that version of the module. If it has not been banned already, it will be soon, because Google is either banning prints released in those modules, OR they are banning prints they see a lot of people using.

By using a CUSTOM print - meaning one that you find yourself - you aren't using the print included in the module, and you reduce the possibility that you share a print with other people, meaning it's less likely that your custom print will be banned.

It won't, because out of the thousands using the module, only about 2 dozen have accepted that finding and using custom prints is the way forward. Plus, everyone wants everything handed to them, so as soon as the included print stops working for 14.2, expect a new wave of "PLZ HALP"
[Magisk] osm0sis:
Ah so you've got some sort of weird interaction between MHPC and the default print/fallback values in 14.0 most likely. You'll need to make an actual proper pif .json and stop using MHPC to pass normally.
[Magisk] acwcanada:
Mine is for sure not the case as it is still behaving the same as I am writing: passed with v14.0 and failed with Fork v3. Forgive my ignorance, how to send PM as I want to send it to @osm0sis for testing.
[Magisk] GROOVYJOSHCLARK:
Sounds about right, but until I have to (SN fails / integrity fails), I am runnin her this way as long as I can :cowboy:;)
[Magisk] Nodens:
As I found yesterday, while looking for something else, 1.41 is installation is horribly broken and no spoofing is done at all under certain conditions. You can check this with logcat if you're affected by this, you will see a Json parsing error and no spoofing actually done. I suggest switching to osm0sis fork.
[Magisk] osm0sis:
Tap my name.

Tap Start Conversation.

???

PROFIT.
[Magisk] wfred:
but that is one of the sites I'm pulling from 😢
[Magisk] GROOVYJOSHCLARK:
ahhh, that I didnt know, thank you! Maybe I will test a newer PIF soon then, thanks for the heads up!
[Magisk] osm0sis:
Yeah.. my worry was that Google would automate pulling and banning them all too, which is why I didn't link anything in my guide and just alluded to it... 🤷‍♂️
[Magisk] osm0sis:
He doesn't have a custom print though, so he'll need to get one (and stop spoofing global things unnecessarily in MHPC) before switching to my fork. 👍
[Magisk] GROOVYJOSHCLARK:
I will work on this when I get home tonight / tomorrow. Its mid-December, and almost 50 degrees here in NYC. It will be almost 60 tomorrow and sunny so I plan to ride my Harley as much as I can before end of season. This work will wait until after riding but I will def come back to it and test! Thank you!
[Magisk] xSnowLeopardx:
I have 15 in total, so, at least 15 :P

Nah, I think 2-3 for now should be enough - right?
[Magisk] Danny1980:
Of course I understand and because of this I want to use a custom fingerprint. I think you haven't understand my question or I may have expressed myself unclearly. How is the custom fingerprint ever supposed to work (it is quite error-prone, being edited manually, not everyone works, ...), if even the standard fingerprint from 14.2 doesn't work on my device? And strangely, it only affects the device integrity and not the basic integrity.
[Magisk] osm0sis:
If 14.2 still works for others and isn't working for you then you must have other modules or something interfering.
[Magisk] acwcanada:
Sent but no idea if done it correctly
[Magisk] Oswald Boelcke:
Hello and good evening, @Lord Sithek

Due to a suggestion of my esteemed team mate @V0latyle, I think your post and your "recommendations" are too good that we shouldn't allow it to become somehow "burried" in this very vivid and extensive thread.

How about if I move your post out of here to become its own thread e.g. in this forum

Tasker Tips & Tricks

Tasker is one of the most powerful apps available for Android. Discuss all of its amazing uses here!

xdaforums.com

or any other of your desire?

In case we move your post I'm also open for any suggestion, what title the thread should have.

Regards

Oswald Boelcke
[Magisk] V0latyle:
So?

Some of the device prints may work

Many (most) won't

And we've already publicly discussed the criteria by which working prints can be found
[Magisk] Iridule:
I got 8 in about an hour this morning. I'm good I think. I'm also just curious is it possible to find a rare print that will pass strong integrity? If so what are the benefits?
[Magisk] osm0sis:
No, that was just a mistake on Google's part, they know what they did and they won't do it again. 😉
[Magisk] rseiler:
Your post reminded me to ask about something I was given over in the Telegram chat when I asked about the easiest way to do it using just the phone. I have no reason to suspect it but wanted to run it by you and anyone else here for vetting just in case. It's a Tasker-create APK that does one helpful thing (non-unstable one also because he said that sometimes he found that to make a difference):
[Magisk] DougMG:
I agree with @osm0sis. And if by some miracle someone does find one it would be great if they kept it on the down low as Google would probably have a meltdown and possibly really crack down on all of this.
[Magisk] Nodens:
Open his profile and hit start conversation.
[Magisk] Claus….:
What is the rationale behind 14,2? Is it to test that hypothesis or?
[Magisk] xSnowLeopardx:
With 5 mins of searching, found my 16th. Come on, y'all, it's really not that hard.

EDIT

17th in 20 minutes...
[Magisk] acwcanada:
Done, thanks
[Magisk] D€INOS:
So it may affect you , so it's not okay. Google's images link didn't affect you , so it didn't matter. Okay I get it , nice attitude. 👌