yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
It was working a year ago for me too on official Magisk... I'm on Alpha ATM, but won't be for long...

Just checked and it's still fine, but needed to hide suspicious apps using HMA LSPosed module or it closes with error message...

Of course I'm on Alpha w/ Shamiko hiding module, so it could be detecting official Zygisk now also; Alpha builds the WIP lsposed/metagisk native bridge loaded Zygisk with anonymous/hideable memory (like Riru had)... But it's also likely it's just detecting some app... If you have TWRP or ever had Xprivacylua installed it could also be detecting a directory created...

If it turns out to be Zygisk, as with many banks apps, the next official Canary or public Magisk build (with 'massive' refactoring, particularly move to native bridge loaded Zygisk from Metagisk fork like Alpha) will also fix that... Merged already:

Refactor zygisk to use native bridge to inject …

Co-authored-by: vvb2060 <vvb2060@gmail.com>

Co-authored-by: topjohnwu <topjohnwu@gmail.com>

3 people committed 2 days ago

And just now got:

Zygisk refactoring part 2

topjohnwu committed 3 hours ago

(Fun fact: Original native bridge implementation, which was actually a first for Android code full stop, was from @canyie and used by @RikkaW for Riru.)

... As long as we still have working USNF/PIF, 27.0's gonna be HUGE folks!... Coming to a device near you... Soon(ish)...

Will also fix a raft of other Magisk issues, even 'wontfix' ones... Eg Zygisk should now start working on Samsung devices like S7 and S8 with stock kernel/ROM as kernel won't be incompatible any longer... These are the advertised reasons for NB-Z adoption...

🤠 PW
[Magisk] chiteroman:
I'm using MIUI 14 and it's working...
[Magisk] marcopit-92:
Seems the only visible things are 2 xposed module according to application detector. Xlua was uninstalled and directory traces eliminated but still the app is able to see the root. No twrp.

Anyway I solved using old version and resigning it to prevent auto update from play store
[Magisk] kergekecske:
It is working here too on MIUI14
[Magisk] dobi3:
Working on my 7 Oneplus phones..

Thanks 👍 👍
[Magisk] passionicon:
Can you share your working fp?
[Magisk] manjaroid:
Makes perfect sense, thanks! I figured my messing around had something to do with it.
[Magisk] angrypizza:
again, there are no signed roms for the s7.

I haven't got the skills to sign/compile my rom, if I knew that was required I wouldn't even have asked.

I'll wait some time if no noob proof how to will popup on the web I will format and revert back to rooted stock nougat. as having a stable bt connetion might be more useful than gpay + unreliable bt (at least for me).

no further help is required.

thanks for everyone.
[Magisk] generalculprit:
I just edited my post, RCS is dead. It still says RCS chat, but messages simply disappear now, even after clearing carrier cache.
[Magisk] Zaxx32:
Wish goog would utilize a different method for stopping rcs spam/scams. Maybe a like a 5 min. time out if more than 3 or 4 texts are sent in 1 minute or something like that...at least for strock roms. Wishful thinking I reckon...:rolleyes:
[Magisk] Nergal di Cuthah:
Likely need to sign rom, i don't use custom rom so i don't know for sure
[Magisk] BarackMitzvah:
So if I completely disable PIF, I'll get RCS back but lose access to things like certain banking apps/wallet?

I'll test that right now, more reasonable then everything but RCS working
[Magisk] passionicon:
Did this work for your RCS
[Magisk] BarackMitzvah:
Not yet, going to leave it for a day or so
[Magisk] chasehammer:
Confirm RCS is dead again
[Magisk] chiteroman:
Can someone test if RCS works using another fingerprint with PIF installed ? Even if it only passes BASIC.
[Magisk] s1dest3pnate:
What exactly is known? Is it because of Hyper being his OS? How come other people that are rooted with no modules and using stock fingerprint don't work?
[Magisk] pershoot:
It would appear that Google has (some) control over which prints are not allowed to be used with RCS independent of Wallet / contactless. This was reported on last occurrence, can be seen by the inoperability of cur. pub. print against RCS (which does pass DEVICE and Wallet / contactless is operable) and is also functional for those with private prints (which pass DEVICE and have RCS / Wallet | contactless operable).
[Magisk] Khnome:
Could it be that google detects pif module? I installed pif and extracted fp of hyper os I currently was on, rebooted and as without pif only DEVICE passed but after re-enabling rcs it would fall back to rcs. Then I disabled pif, rebooted and re-enabled rcs and magically rcs working again.
[Magisk] GeTex:
I can confirm I have RCS on a private print. The public print does not work
[Magisk] passionicon:
Can you teach me how to extract fp ? I have 2 working stock devices here so i can extract. Pls
[Magisk] Khnome:
PIF json from build.prop file
[Magisk] cabagekiller:
It appears it does from what I have seen on reddit
[Magisk] passionicon:
So i get build prop from the device, paste in that webpage and download the file. So once i have that file, how do i use/test it to know if working?
[Magisk] majorfigjam:
You are obviously very late to this party.

Start by reading the most liked posts in this thread, and move on from there.

BUT, expect to be disappointed along the way, as apart from using the publicly available print, there are very few working prints out there.
[Magisk] yoplaboo:
if I can help, RCS works for me with the following module :

GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com
[Magisk] wilsonhlacerda:
If I'm not wrong the success ratio is something like 0,2% (1 good of 500 tested). But you may be a lucky guy!

When reading old tutorials, tips, as already pointed, be sure to try/force all SDK versions on props and different ROM releases for your devices. The FP is per ROM in fact, not device.
[Magisk] s1dest3pnate:
But with what fingerprint?
[Magisk] KidCarter93:
This is XDA, more importantly this is the internet, so it could never be the users fault when things don't work. Always gotta be the fault of someone or something else 😂

Just to stay on topic in here - RCS 😏
[Magisk] awtompson:
RCS is working for me. P7Pro with stock ROM, Pif 15.9.9. Does the fact that I'm in the US using T-Mobile have anything to do with it? I think T-Mobile uses their own servers for RCS.
[Magisk] soa008:
With what fp ?
[Magisk] cabagekiller:
T-Mobile used to use their own RCS server but the switched to googles within the past few years.
[Magisk] ScottIsMyName:
So it seems to me that one fingerprint is working with rcs while another is working with google play. I understand droidguard is used by both wallet and RCS. I wonder if it's possible to spoof a different fingerprint based on who called the droidguard check (not sure if that information is available in the droidguard service)
[Magisk] pndwal:
🤔... Did anyone say you asked for that? Cos I know I didn't. 🤷

🤷

🤣 PW

Well there are, but only Android N it seems...

🙃 PW
[Magisk] pndwal:
Are these OP12 and P8?... Prints from these will almost certainly do you no good anyway 🙃 ...

Generally you'll need prints from pre Keymaster 3 (pre A8 launch version) devices or those with broken keymaster implementations for spoofing... Or some Google may simply have overlooked or taking time getting to. Devices with broken keymaster/chain of trust did include many later OnePlus devices, but Google got tougher with OEM compliance and can even remotely fix/provide new keys/implementations since A13 LV...

Basically (and people forget this), the DroidGuard targeted prop/field spoofs are to bypass server end enforcement of HARDWARE_BACKED evaluationType, so even if PIF is working (ie causing an exception triggering on-device fallback to BASIC-only attestation by it's injection of fake keystore registration data or similar method), we still need to spoof devices that Google knows simply can't achieve MEETS_DEVICE_INTEGRITY w/ hardware backed attestations so they don't/can't enforce the H_B evalType. 👀 PW
[Magisk] passionicon:
huawei p9 lite and samsung s8
[Magisk] passionicon:
pif.json file size i got from this link is 80b, pif.json file size i got from pixel flasher is 10kb.

why the difference?
[Magisk] mac796:
I don't think so. I have pixel8 pro on t Mobile and my rcs isn't working. I need to try the pif fork though I haven't yet.
[Magisk] pershoot:
PIF Fork will not change your outcome (it doesn't even come with an in-built print).
[Magisk] osm0sis:
That's intentional because they frequently need to change. 😉

But I agree, specifically with the current issue of RCS, there should be no difference to what fork works better.
[Magisk] pershoot:
Yup :)
[Magisk] pershoot:
I am on Google FI which is an MVNO on TMO. RCS is awall (as it should be; I am on the cur. pub. print). Try initiating a new conversation (not an existing one; although those should have bombed by now) via RCS to someone.
[Magisk] freeza:
Anyone try using a very old version of messages to see if rcs works
[Magisk] pershoot:
Uncertain of the innards of what measures Google has deployed, thus far, but they wouldn't really need to as they can see what is being presented to them, upon use of their service.
[Magisk] osm0sis:
People tried that last time with both Messages and Carrier Services and I do believe they had some success.
[Magisk] ThatOneGuyOverThere:
Would an extracted fingerprint from an old Oneplus 6t I have work?
[Magisk] pndwal:
... Huawei p9 print may (possibly) work/be "un-banned"... Non-HKA device... 🤠 PW
[Magisk] pndwal:
... That'd be on the 'possibly' list... No need to get print sets from owned devices however. 🙃 PW
[Magisk] passionicon:
Well it's stock. Gotta unlock bl first😒
[Magisk] casouzaj:
I tried the pif.json file generated by chiteroman's webpage, out of my LineageOS 21 build.prop, but I failed device integrity with it. Back to the Sailfish one.
[Magisk] Nergal di Cuthah:
Why would it? It's a custom rom and android 14.
[Magisk] pndwal:
Why? You want to root that device?... Thought you wondered if you could use it's props for spoofing purposes... You can extract from ROM, or use archived device info on many other ROMs linked already here... 🙃 PW
[Magisk] pndwal:
Should be signed release if official LOS... Unofficial will generally be test-key signed unless Devs made a special effort... 🤠 PW
[Magisk] passionicon:
Didn't know i could do that😬 i thought props was specific to device, didn't know it was ROM specific
[Magisk] Nergal di Cuthah:
Right but that doesn't make a working fingerprint which is supposed to refelct a non "jailbroken" (for lack better term) device of a certain age. Or am i reading wrong?
[Magisk] HippoMan:
Hmm ... seems like an interesting idea, but I don't think it's likely to be possible. There is only one DroidGuard that gets utilized for each integrity check, and its bytecode gets loaded dynamically onto the device each time the integrity check is being performed. Then, that bytecode gets executed, and at that time, as part of the work that DroidGuard performs, it looks up relevant properties and attributes of the device. Some of those attributes and properties pertain to things related to RCS, and other attributes and properties pertain to things related to Wallet.

Given that DroidGuard doesn't make more than one pass to perform property checks, that's why I currently wouldn't bet on such a dual-fingerprint-file approach being workable.

Also, some of these attributes and properties that are checked do not come from the properties that are getting spoofed via the fingerprint file. Some are characteristics of the device itself and the ROM itself. That seems like another show-stopper for this dual-fingerprint-file idea.

But there are other people here who understand this whole DroidGuard thing better than I do, and perhaps there might actually be a way that such a dual-fingerprint-file thing could indeed work, that I just am not aware of.
[Magisk] majorfigjam:
Then please read the most liked posts and linked faq. You'll save yourself a lot of time in the long run.
[Magisk] pndwal:
Ah yeah... I'd missed the point that it was only lifted from LOS!... (Focussed on difference between stock and custom ROM). 😁

But not really spoofing non-jail broken device with the prop/field set required; that's done by setting globally spoofed props to non-suspicious values and by hiding root from DroidGuard process, and those are separate functions of PIF... In original USNF neither of these root-hiding functions were done at all because MagiskHide did them; 24.0+ DenyList cannot work however, so root hiding was integrated with Zygisk builds...

Spoofed prop/field set is needed simply to reflect a device that doesn't meet the DroidGuard/PI API requirements (ie. Keymaster 3+, mandatory for A8+ although various OEMs broke it for some time) for hardware key backed attestations so that Google doesn't enforce a HARDWARE_BACKED evaluationType at the server end for PI MEETS_DEVICE_INTEGRITY...

So technically, it's not that it's a custom ROM that's the critical factor for the print set; it's the device it's built for. If built for a device that launched with Android 7 or earlier or a later OnePlus etc w/ broken keymaster implementation, the LOS properties "may possibly" work/be "un-banned" despite the ROM being A14... If for later devices it'll be on the "highly unlikely" to work list.

In this case it seems it's LOS for Sony Xperia 5 II (launched with Android 10), so "highly unlikely" to work. 🙃 PW
[Magisk] menuisier3:
Can we have a digital signature if we change installation mode on rom Beyond for s20 Ultra?
[Magisk] angrypizza:
yep sawdoctor page 816 (which you quoted/remarked previuously)

"There's really nothing anyone in here can do short of downloading the roms source code and compiling it for you "

again, no futher Help is needed in my case. you can assist other members if you wish to.

thanks you
[Magisk] sawdoctor:
I never said you asked for it i only said it was one of your options
[Magisk] pndwal:
Rubbish!...

Nothing there says you asked for someone to compile for you!... There's just a comment from the other member... Then you asked me to quote where you asked for what no-one ever said you asked for. 🤷

I won't say what I'm thinking, other than I think you chose your handle well, and I should have seen this coming. ☹️ PW
[Magisk] K_a_m_i:
I can pass Basic and Device integrity but Playtore still shows Device is not certified. How can I fix it?

Just for my curiosity because everything works that I need including bank apps.

(SM-996B/DS, RisingOS vanilla GSI, minMicroG, Playstore, osmosis PIF v8, Sailfish, Shamiko 1.0.1, Playstore and MicroG storage cleared and rebooted)View attachment 6110961View attachment 6110962
[Magisk] chiteroman:
I tried building Lineage and signing it using this tutorial and it makes my device bootloop 😅

I think you should follow the official Lineage guide.
[Magisk] angrypizza:
I believe you're off topic Sir
[Magisk] dknight178:
I tried an end-April version and RCS still doesn't work
[Magisk] immortalwon:
that guide doesn't work either, seems like everyone is giving out misleading information. Those guides don't show people how to sign the apexes correctly with a 4096 rsa key

Maybe the guide works for Lineage, but for other custom roms, nope.
[Magisk] osm0sis:
Wipe Play Store and Play Protect Service data+cache to force it to update the status.
[Magisk] deepongi:
is 15.9.9 working for someone? it stopped working on my signed build.
[Magisk] chiteroman:
Working on stock ROM.
[Magisk] immortalwon:
Still working, both sailfish and other priv print which in actuality is not private since Google / NSA knows all.
[Magisk] pndwal:
Does Sammy have PPS app? PW
[Magisk] passionicon:
What's sailfish pls? I keep seeing it everywhere
[Magisk] markdewet:
On my SM-G955F, there is no PPS, however, I am runnig RisingOS with NikGapps, so not sure if stock ROM has it.
[Magisk] pershoot:
A public device print in wide use which allows for Wallet operability and did allow for RCS alongside it, but that is now history.
[Magisk] passionicon:
Thanks
[Magisk] fbirraque:
No Play Protect Service on MIUI14 or HyperOS

🤷
[Magisk] dicamarques:
Can you share what it detects? I also can't open Repsol Move on my device with magisk
[Magisk] tom1807:
Wiping Play Store is enough and certification comes back which can take a few minutes up to a few hours

Cheers

Tom
[Magisk] beardedwonder:
Got my second print today, so that's a return of 2 working prints out of 835 attempts. I think I'm going to stop, for now.
[Magisk] passionicon:
Can you share? 😌
[Magisk] passionicon:
This is getting serious and intense. My 2 delivery work apps stopped working because of failed device integrity 😭. I'm helpless
[Magisk] sonek231:
Finally I manage to get laptop. I installed magisk manager and play integrity fix but I pass only basic integrity. Device integrity still on red, what else should I install?

Fix is enable in modules.
[Magisk] chiteroman:
Install this app and send screenshot
[Magisk] sonek231:
Rom sign is testkey

Is it bad?

@chiteroman
[Magisk] az45211:
what exactly makes a device viable for a valid print? ive tried making prints from loads of devices, all not in the tadi dumps page. there's no way the zte axon M print got used enough to be burned, so what exactly makes it not work?
[Magisk] casouzaj:
Two things to consider: 1 - has your current ROM been signed at building time (ask your ROM maintainer)? 2 - Is your current kernel already banned (what's the results of command 'uname -r' - after 'su' - from either a terminal emulator app or after 'adb shell)?
[Magisk] chiteroman:
Yes, your ROM is signed with testkeys so you won't never pass Device 😢

Ask your maintainer about signing it or rebuild by yourself.
[Magisk] casouzaj:
Yes, it's bad. It should be release keys.
[Magisk] HippoMan:
There is no deterministic test which will definitively show that any given fingerprint will work. Each one just needs to be tried.

As has been discussed here numerous times, most of the fingerprints which used to work have now been banana-ed by the Googlefrinchians. Out of many hundreds which previously were working a few months ago, only a very small handful now are still usable.
[Magisk] sonek231:
For su uname -r I got error "invalid option -- r" (using magisk su)

For uname -r in terminal I can see

4.9.337-Etude-Op.13-No.2-gdce351ed is it ok?

I will check if there is any update for my ROM.

Is there any guide how to do it by my self?

My ROM is not supported anymore, tbh is unofficial pixel experience. I think i need to do it by myself! Is is complicated?
[Magisk] az45211:
right, but what minimum properties does a device need to have to be a candidate for a valid fingerprint? I know it needs to have launched on android 7 or below, does the fingerprint need to be from an android 8+ update on that device?

Is there a way to switch fingerprints without rebooting so I can test them faster?
[Magisk] sawdoctor:
There's approximately 70 working fingerprints left out of over 100,000+ firmwares tested. There's a reason 99% of people are using the print chiteroman kindly donated, most of us have had all our working prints banned and have tested 100s of possible firmwares since with no joy.

Needle in a haystack doesn't do it justice
[Magisk] immortalwon:
that wouldn't have happened if the people who pimped out their autopif or fetching mods didn't leak hundreds of keys for google to insta ban. But I am sure Google has A.I scripts that can find all public prints easily
[Magisk] HippoMan:
If I'm not mistaken, those 70-or-so fingerprints were re-tested recently, and now, only 3 of them are working.

... unless you and I might be talking about different sets of 70-ish fingerprints.
[Magisk] sawdoctor:
Tbh we don't actually know, there was a massive cull in Feb that wiped out 1000s of prints that hadn't been publicaly released
[Magisk] pershoot:
If you want to pass DEVICE integrity, that is still possible. Use osm0sis's PIF fork and then use autopif to procure the latest public print or chiteroman's PIF 15.9.9. Then, you can try Zygisk Assistant or Shamiko to hide elevated priv. from those apps.
[Magisk] freeza:
Tried one from January and it didn't work either
[Magisk] fbirraque:
Which apps (screenshots)?
[Magisk] passionicon:
To better understand the first part of the message, I'm supposed to have osmosis pif fork module plus autopif or just pif 15.9.9?

Also I don't know what you mean by auto pif, is that playcurl?
[Magisk] passionicon:
Not sure i should mention or post that publicly 🤔
[Magisk] fbirraque:
Does it confidential who delivery for you?

:unsure:
[Magisk] pershoot:
osm0sis PIF fork w./ autopif or chiteroman's.

I've not used playcurl, but if you use that, you may need to convert the print it pulls to whichever PIF module you use. Someone else may be able to further comment on the use of playcurl.
[Magisk] K_a_m_i:
Thanks for all of you trying to help! I wiped Play Store and MicroG services cache and storage several times, rebooted, waited for hours and device is still not certified in Play Store however I can pass basic and device integrity. Maybe it is because of microG?
[Magisk] osm0sis:
Not on devices that have the separate Play Protect Service app. They need to wipe both or "Device is not certified" will keep coming back, as the user reported.
[Magisk] K_a_m_i:
I don't have separate Play Protect Service app. :(
[Magisk] osm0sis:
Then your passing DEVICE at the same time doesn't make any sense. Are you sure you don't have the app? It may show up only as a System app when you're searching. 🤔

You can also try wiping Play Store data+cache and then reopening it, multiple times rapid fire until it seems to stick, since that was my previous advice for everybody. 🤷‍♂️
[Magisk] Magik_Malfici:
Greetings everyone!

Maybe I'm a bit stupid, maybe I didn't read the whole thread or did everything correctly... but I'm in the same situation as everyone else, i.e. my RCS Messages are no longer being sent.

I'm on Xiaomi Redmi 9T with Root and Bootloader unlocked - MIUI 14

At least, they're being sent, but they're disappearing right away, and iPhone users are being blocked too! (It says that it's impossible to send the message?)

I've just looked at a few things: in Magisk, it's up to date, as is the root image.

In Zygisk, I've configured the list of exclusions such as: Android Service Library, MIUI Components; Doctolib, Google One Time Init; Google Parter Setup; Google Play Store : Google Wallet; MIUI Home; Banks, Google Messages : NFC SG; QDCM-FF ; QTR ; Resources of Safety Center Google , SDK MIUI ; Security MIUI : Track System

I just looked in Simple Play Integrity Checker, it shows me :

0 RED: No Integrity; 1 DARK ORANGE: Meets Basic Integrity; 2 LIGHT ORANGE: Meets Device Integrity; 3 GREEN: Meets Strong Integrity; ROUND EMPTY VIOLET Meets Virtual Integrity

Google Play Store indicates that the Play Protect Certificate is certified.

I've already got clear Google Play Store, any idea what else I can do?

(Strangely enough, it's iPhone Messages blocked! I don't understand...)
[Magisk] majorfigjam:
For now, turn off rcs and use sms only?
[Magisk] K_a_m_i:
Agree, that's why I asked it. Now I found that if I switch off "Enable GMS spoof" in settings app (which belongs to the ROM) then I can't pass the Device integrity (even with Sailfish), and if I switch it on then I can pass Device integrity even if there is no any pif.json in data/adb. Maybe there is a spoof built in the ROM but it doesn't explain to me why Playstore shows device is not certified when Device integrity passed. (Of course I checked system apps too and I don't have Play Protect service as separate app. Cleared cache, storage of Playstore and MicroG multiple times and rebooted too.)
[Magisk] Erecik:
No RCS on rooted devices with unlocked bootloader, no workaround as for now - just disable it so You won't miss any messages
[Magisk] Magik_Malfici:
So for the moment play-integrity-fix is temporarily out of order.

Boring... Because of course, it wouldn't be funny, you can't relock a bootloader with root and the RCS works again ahah... (Satirical)