yashsingh1/xdaforums huggingface dataset:
[Magisk] intel_core_i7:
Not that concerning since telegram forks are allowed and there are no GMS versions. I think we will be fine.
[Magisk] westruk:
Crdroid without integrated bl spoofer
[Magisk] beeshyams:
Thanks. I've always had it disabled (ever since I bought the phone) because Play Protect "silently" uninstalled apps (one was XPrivacyLua) on my previous device (Pixel 4a)

So, does clearing Play Store data matter?
[Magisk] pndwal:
... I don't think he means 'separate Play Protect app disabled' however (?)

Disabled what? The app itself or just turned off app scanning in Play Protect settings within Play Store?

Re. the Play Protect verdict in PI API, it "lets you know whether Play Protect is enabled on the device and whether it has found known malware" and is contained in the new environmentDetails field, not the deviceIntegrity field... I therefore think disabling PP app scanning will be totally unrelated to PP Device certification. 👀 PW
[Magisk] beeshyams:
Sorry, guilty of not communicating clearly

1. Play protect app is a separate app on Pixel 6a

2. App is not disabled but scanning is

I realize now that what I said earlier and what I clarified above are entirely two different things

@osm0sis , sorry
[Magisk] osm0sis:
Does your Play Store show Certified? If Play Protect app was ever enabled before you signed into Play Store for the first time then it might be from that.

The true test would be to leave Play Protect app disabled, then clear Play Store cache+data, then see if Certified comes back. It'll either stay blank, show "not certified", or fallback to the older internal Play Store Play Protect and show Certified that way.
[Magisk] beeshyams:
Yes, it does show certified

I kind of understand "true test" but honestly I'd rather continue with the current state rather than falling a victim to Google tricks. Thanks much
[Magisk] osm0sis:
Just for your knowledge Play Store wipe has never had any adverse side effects. 🙂
[Magisk] beeshyams:
You're absolutely right. It shows blank after disabling Play Protect app and lo & behold, I paused sending this message to report the status after enabling it, only to discover that the app was enabled on it's own and device is certified 🤔

Pixel 6a
[Magisk] pndwal:
As he said, Play Protect app was never disabled; only app scanning in settings... That won't affect device certification whether enabled or not... We can disable that on locked devices and still have STRONG_INTEGRITY and PP Device is certified!

??... What, did you freeze the app this time?... Or just force close? [Edit: Oh; just disabled it!] 🙃

Yeah, it comes back but this is a completely different circumstance to having Play Protect app disabled or only a hypothetical fake one w microG (which was what was being discussed)... I'm betting you haven't disabled it!!... [Edit: I see it just re-enabled itself!].It's not coming back because of 'fallback to [some] older internal Play Store Play Protect and show[ing] Certified that way' either... 😜 PW
[Magisk] beeshyams:
Thanks, just to clarify I am on Stock ROM and I did disable Play Protect app. Very sure
[Magisk] pndwal:
Please say how... Frozen? Uninstalled? Or just force-closed? Edit : Guess you just disabled it! 🙃 PW
[Magisk] beeshyams:
Force-closed

Edit: I mean by the disable option
[Magisk] sonek231:
Hi guys

I forget that my NFC is not working since few months maybe. Now I'm abroad and my revolut doesn't work :(

Is it possible to deal with integrity check without laptop?

I have pixel experience rom

Xiaomi mi mix 2S
[Magisk] casouzaj:
Download the files you need to your phone, reboot to recovery and install them from there (select to install from storage, not adb).
[Magisk] sonek231:
I downloaded play integrity check fix 200kB file.

I understand that I need to install magisk manager also? If yes I kindly ask for some instructions without laptop. I have PE recovery I guess
[Magisk] ThePioTug:
Signed the GSI rom and back to working playintegrity

hopefully the maintainer will sign the next release

View attachment 6109777
[Magisk] casouzaj:
You need root privileges. Use either Magisk (I used Kitsune Mask some time ago, with Zygisk, MagiskHide and SuList enabled), KerrnelSU (my current setup. You'll need the ZygiskNext and Zygisk Assistant modules, too), or APatch (haven't used it yet). All of them are either APK or zip, which you can install from recovery. Modules (like the PI one) you install from either Magisk or KerrnelSU Manager.
[Magisk] Starkshade:
Please elaborate... Where does one get GSI source code in first place? How does one go about compiling it? Any links to guides/tutorials?
[Magisk] zgfg:
So you can work on your own module for that😀

Frankly I also shortly searched (just for curiosity) and didn't find

I answered you only the ideas that came to my mind

However, I'm really not interested in. To the opposite, I don't want that if I loose my phone (once I did in a pub on Sat and I had to wait till Mon to pick it up) to be afraid that somebody could just swipe up and do whatever he wants with my phone, to access and use all my apps and data on the phone. Seriously

And that I would have to immediately call the bank to disable my cards, etc.

And that I would have to frantically change my passwords everywhere, etc

That somebody could make the booking.com reservations and who knows. Is this really worth of?

Of course, you can always use (probably you're also against of enabling it) Find My Device to wipe the phone

But sometimes you forget the phone at work or similarly, and you find it later (and you can take a risk of an hour or so till you find the phone). If it would be unlocked, I'd have to immediately wipe it by Find my device (and it would be terrible then to reinstall and re-configure everything back when I find the phone half an hour later in the car or so)
[Magisk] Bladius:
On version 12.1 you cannot check the status in the Play Integrity API Checker application. An error about too many tasks being sent to the server appears
[Magisk] chiteroman:
You literally answered yourself....
[Magisk] 130ryokohama:
just wanted to update everyone that google wallet is now working!

i think clearing data and cache may have contributed(?) but in the end, all i did further was remove the "magisk config prop hide" module and rebooted. so if anyone has that module, disabling it won't fix it - you need to remove it and reboot!

straight after that, google wallet shows i meet the security requirements!

android 12, magisk 26401 with PIF v12.1
[Magisk] zgfg:
It has nothing about the module, but with too many ppl using Play Integrity API checker and running over their quota

Scroll above to read about the other ways (TB Checker, Playstore app by enabling Developer options) to run the SAME Play Integrity test
[Magisk] cangurob:
Hi all.

Device attestation failed today for google wallet, so I went looking for solutions.

I'm running Pixel Experience (which comes with KernelSU preinstalled). So I did the following:

Installed KernelSU Manager (https://github.com/tiann/KernelSU/releases)

Installed ZygiskNext (https://github.com/Dr-TSNG/ZygiskNext/releases/)

Installed Play Integrity Fix (https://github.com/chiteroman/PlayIntegrityFix/releases/)

Cleared Play Store data.

However play store still says Device is not Certified.

Am I missing something?

Edit: TB Checker play integrity check says:

Basic integrity PASS

Device integrity FAIL

Strong integrity FAIL

Virtual integrity FAIL

I assume the problem is the device integrity... right?
[Magisk] Nergal di Cuthah:
That's not the fault of the mod, too many people are frantically checking with the checker app and the app's access to the API check is throttled. Use play store or wait til less people are checking
[Magisk] zgfg:
Every time you attest PI you attack Google servers. Hence every app that calls PI API testing must subscribe for a quota with Google

Free quotas are limited, for more you have to arrange with Google

Hence don't expect that a free app like PI API Checker would have a quota for zillion attest per day like going on today
[Magisk] alfian89:
what happened?

View attachment 6030951
[Magisk] zgfg:
It has been answered several times above

I wonder, is it really so hard to to spend few minutes to read (recent) posts before asking
[Magisk] Nergal di Cuthah:
Literally the conversation before you posted spells this error out
[Magisk] 130ryokohama:
i managed to solve my issue by reading the previous pages of replies and comments. use the function in play store not the separate app
[Magisk] sir_bazz:
Root based AdAway user here so thanks for the tip.

Had to update blocklists and, (temporarily), disable AdAway prior to checking wallet setup settings to regain functionality.

And @chiteroman deserves Employee of the Month
[Magisk] Marvin732:
i used to get auto updates though
[Magisk] V0latyle:
No.

He's talking specifically about checking your Play Integrity responses.

The native way to do this is by enabling Developer Options in the Play Store (Settings > About > tap Play Store version 8 times), under the General section of Play Store Settings.

Play Store may report that your device is certified even if you aren't passing DEVICE_INTEGRITY
[Magisk] BillGoss:
Thanks!

This was already mentioned in https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89152559 and https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89152562 😄
[Magisk] intel_core_i7:
No wonder many banks would just use their own custom root detection method, it's probably cheaper and easier to manage since it was developed in-house. Imagine your banking app become unusable just because google's servers went down.

One example is those apps requiring locked bootloader only attest locally, so quite easily to be bypassed.
[Magisk] iruiz2:
View attachment 6030996

PlayStore Play Integrity also doesn't work?
[Magisk] Nergal di Cuthah:
As it says transient error, I'd say let it alone for a bit and it may work. I just checked with mine (pixel 6p) and it worked, so either something is different on yours (playstore in deny list?) or as it said it was a transient error.
[Magisk] pndwal:
They probably will fix it however...

I don't follow Igor's posts, but his comments are quite correct and only reflect frustration at the lack of user understanding in this case...

XiaomiEU has led the field when it comes to including integrated spoofs for passing SafetyNet and PI DEVICE_INTEGRITY out of the box (without root)... And if I'm not mistaken, the recently working USNF/PIF 'fixes' for STRONG_INTEGRITY (based on Google's embarrassing fake MEETS_STRONG_INTEGRITY for early Pixel 2's) originally derived from XiaomiEU ROM's integrated spoofing!

Clearly the main Dev was just saying he wouldn't give an ETA on such an update however... Also it's not a bug since it originally worked to 'fix' integrity attestations, but, just like PIF module, the solution needs fixing whenever Google changes need to be accommodated... The 'fix' simply became outdated since Google changes simply can't be predicted and can only be bypassed retrospectively.

Further, while ROMs like this are great for users who just want custom ROMs with banking etc working and no root, I personally prefer to use a 'clean' ROM (that never spoofs/manipulates expected signals) like any official LineageOS ROM (see their policy) and to use root for integrity attestation fixes as solutions like PIF are generally updated well before ROM updates become available and such 'clean' ROMs won't introduce conflicts with root solutions...

Rather than requesting 'bug' fixes, I think it would be far more profitable to ask ROM Devs who integrate SNF or other Integrity attestation fixes/spoofs to publish additional 'clean' ROM builds for those who prefer to use root solutions... Realistically however, 'No' will likely be the answer for logistical/other reasons...

Another possibility may be to request adjustments to the integrity attestation spoofs to make them less 'strange' and to prevent conflicts with current root solutions... Many custom ROMs, including many from XiaomiEU, don't conflict even when they themselves become outdated...

🤠 PW
[Magisk] sonek231:
Ok I will try to install magisk from recovery

Does it delete any data?
[Magisk] zgfg:
No.

And there are Installation Instructions on GitHub and a dedicated Magisk General thread here on XDA
[Magisk] generalculprit:
No. But a backup to SD card or USB stick is always a good idea. 🙂
[Magisk] alekyiv:
Mod edit - translated by https://translate.google.com/. Oswald Boelcke, Senior Moderator.

Hi, who knows to hide these two lines, who discovered momo, all others and bee hide, root, se, etc. Thanks for the answer!💛💙

*********************************

Привіт, хто знає, що потрібно приховати ці два рядки, хто виявив momo, усі інші i bee hide, root, se тощо. Дякую за відповідь!💛💙
[Magisk] casouzaj:
No, it doesn't. Bear in mind that there are some phone/makers for which root access doesn't appear after installation from recovery. If you face this issue, submit your boot.img to be patched by the Magisk app. You'll get a file named magisk_patched...img in the Download folder, on your internal storage. If your recovery is TWRP, you'll get a button to install img files, instead of zip. Select the boot partition to install the patched file.
[Magisk] Oswald Boelcke:
Hello and good afternoon, @alekyiv

As a one-time courtesy I've translated your above post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Ukrainian posts.

Spoiler content hidden.

Regards

Oswald Boelcke

Senior Moderator
[Magisk] sonek231:
Ok I will try

Custom Recovery​

Method from instruction to install magisk because I probably have Pixel experience recovery.

Unfortunately I can't do it through recovery without command from PC :/

Any ideas?
[Magisk] alekyiv:
Sorry i am write into english my google chrom automatically retranslated in my language, i dont see that and reconfig browser for only hand translate from xda-forum. My eng is middle, but i use auto translate english to ukraine.
[Magisk] casouzaj:
Rename the Magisk's extension from apk to zip. Enter the recovery you have and install the renamed Magisk zip. Boot to system. Launch the Magisk app. In the main screen, in the upper part, do you see its core part installed?
[Magisk] sonek231:
I renamed the files but in my PE recovery I have only option to update from adb but that requires command form laptop i think.
[Magisk] casouzaj:
Do you have an SD card slot in your phone? Mine has (Sony Xperia 1 II). I think PE recovery is based on the LineageOS one. And LOS recovery has an option. When I select 'Install Update', two options are presented: from adb sideload and from SD storage.
[Magisk] zgfg:
As instructed, please read Installation instructions for Magisk on GitHub

Find there how to install Magisk (recommend method !!!!!) without cudtom recoveries - by patching and flashing the (init) boot img

Suggestinh also to continue about installing Magisj in the Magisk General thread here on XDA - see right above the Search icon or google
[Magisk] mierdaseca:
Where exactly can ROM developers get the proper keys from?

Got a device using crdroid failing to pass pi because it's using test keys, and want to point him in the right direction so he can sign the rom.
[Magisk] osm0sis:
It's literally any signing key they want to generate for themselves. Just can't be the AOSP testkey anymore.
[Magisk] gentano:
Maybe this is helpful for the one or the other, its a script for signing LOS and crDroid builds.

I read the last 20 pages and it looks like it has not been posted yet.

crDroid.net - Sign your crDroid builds and keep Play Integrity happy

A guide to using signed keys for crDroid builds

crdroid.net

GitHub - 306bobby-android/crDroid-build-signed-script: Build script for creating signed crDroid OTA packages

Build script for creating signed crDroid OTA packages - 306bobby-android/crDroid-build-signed-script

github.com
[Magisk] sonek231:
Unfortunately not :(

@zgfg

I don't have access to pc/laptop
[Magisk] pndwal:
Ah... I see I missed that you said

after being disabled... Now it makes sense again! 😜 PW
[Magisk] zgfg:
Hmm, bad

But if you have a second Android with Magisk installed and a double USB cable, you can use NDK ADB and Fastboot module from Osm0sis from that second Android device and then use that second device to run Fastboot (flash) instead of from the (Windows/Linux) PC
[Magisk] sonek231:
Yeah, bad. That's why my question was tricky. Unfortunately I don't see any chance to solve my problem until I back home.

Solution with second android device is interesting but no chance for me to check this.

Maybe some developers will read this issue and prepare solution if it's possible.
[Magisk] testit2000:
Hi,

I installed the module but all integrity checks are still red.

I have a Samsung S21+ and have not set any custom pif values, I also tried with the values of my old S8 but this falls to HARDWARE_BACKED type which I guess will not work.

Do I miss anything?

Thanks!
[Magisk] Nergal di Cuthah:
Stock rom? Stock kernel?
[Magisk] testit2000:
sorry forgot to write that directly ... yes both is the latest official firmware just patched with magisk, zygote is enabled and using the default hide list (added Wallet & GSF) (not enforced) + Shamiko)
[Magisk] Nergal di Cuthah:
GSF? GOOGLE service framework, yeah take that out of your deny list and you'll at least get basic
[Magisk] testit2000:
The Google Service Framework
[Magisk] sensui123:
Would there be a script like this for other roms that aren't Lineage based? Thanks.
[Magisk] trevtdogg:
which module? including the version number will help too.

some versions have the fingerprint data included, and some versions require you to add that separately.

you don't need anything in the hide list or in the deny list for device integrity to work.

if you are having issues, removing all from those lists and disabling any other modules is a good starting point.
[Magisk] Nergal di Cuthah:
See my edit in the quoted post i must've been editing when you answered

Remove gsf from denylist
[Magisk] AlexS2412:
google broke it again. i pass integrity and still cant rcs
[Magisk] GeTex:
Just lost RCS with chiteromans current pif

Edit: Oh no....
[Magisk] YHMWU7Rc9TkDAtu4NT6:
Yep broken again. Basic Integrity PASS, checked with YASNAC

Currently using Chiteroman PID PIF v15.9.9 https://github.com/chiteroman/PlayIntegrityFix/releases

Will test with the latest Osmosis fork and report back later.

Edit : Tested by Swapping Osmosis Fork for Chiteroman PIF ... Did not fix it. RCS was broken with both of them.

Tested with Play Integrity Fork v8 release date March 10 https://github.com/osm0sis/PlayIntegrityFork/releases
[Magisk] wilsonhlacerda:
BASIC + DEVICE here are ok yet with newest PIF. RCS is not used in my country.
[Magisk] Vicep83:
RCS broken
[Magisk] JonanomisK:
Literally just came here to check if others experienced it. Stock ROM, passing device and basic integrity but rcs is borked. Why can't we have nice things Google?

Edit: also verified that swapping between chiteroman and osmosis forks makes no difference in case that was in question
[Magisk] 0ctobot:
Can confirm on the public sailfish print, RCS is cooked despite passing device integrity. However, I have a private print with no such issue.
[Magisk] wilsonhlacerda:
So probably within a few hours Sailfish FP will be banned. Google usually does that on Tuesday morning (my time), it seems it will do it again one more time.
[Magisk] majorfigjam:
Then this must be country specific, or Google is a/ b testing again, as RCS is still working for me with sailfish

There was a glitch earlier, messages received twice (sms and rcs), but now back to normal.

The expected June QPR later today from Google may change all that.
[Magisk] testit2000:
I only have the newest version installed of this module: https://github.com/chiteroman/PlayIntegrityFix

I also removed all apps of Google from the Deny List

Thank you I removed the Google Service Framework from the Deny List, but also after Restart it does not even show the Basic passing :(

Reading the other posts I'm not sure if its cause of the maybe banned fingerprint or cause of my problem that still exists
[Magisk] Nergal di Cuthah:
If it were fingerprint, to my understanding, would still allow basic just not device. Do you have a fingerprint (pif.json) if so, though my reading of your prior posts i saw you say you do not, delete it/them the latest pif has the current working print built-in. However i don't think that's the case as i said you'd still pass basic.
[Magisk] Nergal di Cuthah:
You don't say any other modules you run (lsposed boot loader spoffer xlua and more) you said you have shamiko are there blocks blocking gsf?

Did i assume you use official magisk or do you say it somewhere. You said
[Magisk] mew1033:
Busted for me. Man Google, why do you have to be like this?
[Magisk] GeTex:
Switched to my private print and RCS is indeed back up. Google I swear. I'm making a plan to go back to locked stock because the crippling anxiety attacks that leave me physically on the floor I've been having are starting to do bad things for my fragile mental health. I might actually go to an iPhone if I'm losing the modding scene anyways. All I care about is RCS, don't even care for wallet or anything else. But RCS is important to me
[Magisk] zetsumeikuro:
On some older prints that don't pass device and just basic RCS still works. So if you don't care about wallet etc can just keep doing that for the time being.
[Magisk] testit2000:
I have the original pif.json of the repository (I also checked the content with a root file manager) additionally I created a own one with the fingerprint data of my old s8, but then it falls back to hardware so I returned to the original google sailfish one from the repository.

I'm really sorry and so thankful, it works now - I thought I disabled all the modules but when I wanted to list all the disabled modules somehow lsposed was still enabled. When I disable the XPrivacyLua module in lspoed I pass both checks. Thank you so much for your help!
[Magisk] zetsumeikuro:
Apparently there are some reports of RCS not working for people that are BL locked and 100% stock. Google gonna Google.
[Magisk] soa008:
RCS down again. I didn't pass integrity but I had RCS with sailfish. Today they're gone
[Magisk] pndwal:
Good you got that sorted... For now... Looks like sailfish 'ban' may be imminent... Note, some banks detect XPrivacyLua even after it's uninstalled (as it doesn't clean directory on uninstall)... Check for data/system/xlua directory and remove manually. 👍 PW
[Magisk] pndwal:
Just like last time! 😂 ... Maybe be all a red herring... Or not... 🙃 PW
[Magisk] zetsumeikuro:
Guess we'll just have to wait and see. Searching for prints has become quite tiring.
[Magisk] GeTex:
Thanks for the suggestion!
[Magisk] soa008:
Can you suggest one that RCS works ?
[Magisk] zetsumeikuro:
Nope. It's trial and error but should in theory be easier to find one.
[Magisk] alekyiv:
View attachment 6110004Тhis it means that the arc is working? I am not using rca have viber, tg, whatsapp, etc...
[Magisk] soa008:
This means RCS is connected. Try sending a message. If it is not delivered and keeps disappearing then RCS is not working.
[Magisk] angrypizza:
Can't get device integrety check and wallet wont pay, at the following link it says I need signing keys for my custom rom.

crDroid.net - Sign your crDroid builds and keep Play Integrity happy

A guide to using signed keys for crDroid builds

crdroid.net

at this link

GitHub - 306bobby-android/crDroid-build-signed-script: Build script for creating signed crDroid OTA packages

Build script for creating signed crDroid OTA packages - 306bobby-android/crDroid-build-signed-script

github.com

it says I need to "run the script"... "build as usual".... have no clue on how that is done. can someone explain with some details please.

as for now the module "universal safety Fix" apparently installs under magisk but doesn't appear in the modules afer restarting the phone.