yashsingh1/xdaforums huggingface dataset:
[Magisk] HippoMan:
My following editorial is OT here, and hence it's been moved to the other thread:

https://xdaforums.com/t/discussion-...ding-cat-and-mouse-game.4425939/post-89582968
[Magisk] JazonX:
True!

The days I joined XDA with an i-mate JasJam .. Things were more freely available, people were cooperative, and even the users were very humble. We took time to read forums, threads (and we never complained!) and heck there wasn't even any resources available like today to understand things. But still we were grateful for whatever we got. The rom culture, and even the devices were super exciting and everyday there was a new change to experience.

Then the days of the first Galaxy i9000 where when you open up XDA, you had a plethora of roms to choose from, and each having unique features. I think I switched roms every other day testing something new and finding bugs on some other. The time I wasted on all those .. Wish I had such free time now.

Then we slowly transferred to an age where things started to get blocked by paywalls, a paid exploit or some other means where a payment is required. Great Devs who did everything for free slowly started dissapearing (I still wonder where and what happened to Chainfire, Arter97, Whiskey, Codewokx is) ..

This payments were also bearable as we grew up along the times, got jobs and made means to afford things we needed -, and we managed to get through the rough days of Huawei Paid Bootlaoder unlocking, Roms with Pro keys, PowerMP3, etc ..

Now when things started to get illegal - that's a whole other grey area which is slowly becoming black and making this root process more like a chore rather than a hobby. It's no longer worth because the process has become awfully stressfull time and time consuming. I was speaking to @majorfigjam yesterday .. I find out my PIF is burned when I pick up my coffee in the morning from Mc'Donalds because that darned app doesn't work with broken integrity. If my PIF is burned, I end up paying in full for the coffee, or if the PIF is active - I can use the rewards to redeem it. When It's burned, You have to come home, sit on the laptop and spent hours testing the freeman database. I did it once, and it got tiring. I even thought of locking the bootloader and moving on .. But Ahh .. Samsung - Once unlocked, forever unlocked - you cant fix the Health apps, watches on the stock roms. Pixel 8 Pro is fine so far, But I lose spam screening and caller recording.

So it's a hassle to even think of living without root.

Sorry. Went a bit OT there with @HippoMan s sentiments above.
[Magisk] HippoMan:
I moved my own sentiments to the other thread where they aren't OT. See the changes I made to my post above. We should continue this rant discussion in that other thread.
[Magisk] bombadier:
Is anyone else using the GoogleOne VPN replacement VPN by Google ? As of today I am getting an error Check your router and firewall settings with my unlocked/rooted Pixel 7a, my dad's locked/not rooted pixel 7a connects fine on the same network.

This happened before with the free GoogleOne VPN, for me it only worked with a paid subscription on my unlocked P7a.

I am using PIF Fork with the Sailfish print so wallet is working but RCS not, still passing Device and Basic but google now seem to be enforcing the same restriction that caused the free GoogleOne VPN to fail on unlocked bootloaders,hope this is not an indication of google tightening things up again .......
[Magisk] ninjakira:
Has anyone got rcs working at all? I get we got to be a bit more discreet and or private so like I do accept DMs.... I just want my rcs man lmao, it's either that or I'm just giving up here and buying a new phone and keeping it locked lmao
[Magisk] badabing2003:
Wrong thread, but I have read that it doesn't work on bootloader unlocked / rooted devices.
[Magisk] bombadier:
Couldn't find a thread but thought this thread was the best place to post given it has been spoken about in the past,it has been working up until today.
[Magisk] HippoMan:
https://xdaforums.com/t/discussion-...ding-cat-and-mouse-game.4425939/post-89583035
[Magisk] badabing2003:
The guide threads are best place to ask for these type of issues, or start a new thread.
[Magisk] TotallyAnxious:
My android 15 print works lol
[Magisk] Tamsta_T:
Here's your answer ;-)
[Magisk] TheOct0:
Hey, I've been reading through the thread for the past few weeks and it's been a tremendous help, but today RCS has started acting up even with my private print.

It might be my carrier, since I'm getting toast messages for some 332 error for several messages before it starts working again and sending the whole backlog, then starting to act up again... But it coincides with the arrival of Gemini in my Messages app, which doesn't function, so i thought it best to report it here. Here is my setup :

- Google Pixel 8 Pro

- Device and basic are passing

- Stock Android 15 Beta 3

- Unlocked bootloader

- APpatch root

- PlayIntegrityFork

- Cherish Peekaboo module

- Zygisk Next

- Zygisk Assistant

- Private print

EDIT: I figured it out, whenever a Gemini Message fails to send, it tries to revert to SMS but obviously can't, and it seizes up the whole RCS and SMS capabilities of the app until the Gemini message is canceled and deleted. Hope this helps anyone in this same situation !
[Magisk] osm0sis:
Yeah it died on the 22nd despite me still being on my Google One free trial until July 2nd. Tried adding some more things to the Shamiko'd DenyList but no luck.
[Magisk] badabing2003:
Do we know if it is detecting unlocked bootloader / root? Or is it expecting strong PI?
[Magisk] pershoot:
@TheOct0 Gemini via RCS works fine here.
[Magisk] osm0sis:
No idea. Good questions. I only have my daily driver Pixel 8 Pro and I don't plan on pushing the limits too hard for testing on it since I don't want it to break.

Google certainly knows it's unlocked where they only serve the QPR Full OTAs to it via System Update now. 🤔
[Magisk] Captain_Throwback:
Does it have anything to do with this? https://support.google.com/googleone/answer/7582172

Or are you talking about something different?

EDIT: And this: https://support.google.com/googleone/answer/14806901
[Magisk] osm0sis:
Yes and no. At the risk of getting too off topic, we're talking about the replacement for "VPN by Google One", which now runs on-device, is just for Pixels and called "VPN by Google for Pixel".

If we determine it's not related to Strong then I guess it'll definitely be off topic. 😅
[Magisk] TerryS2K:
Hi, I have one of the forks installed. To uninstall it. Do I simply disable it in magisk and remove it?

Then I should be okay to reboot and install the latest version? I just don't want to break anything and end up in a boot loop.
[Magisk] devaponnadsm:
I have a doubt for Samsung devices. Even if we get a valid keybox and print, will Strong Integrity work as Knox is broken?

I have no intention of achieving Strong, but only want to make RCS and some apps work. Anyone here using Tata Neu (India)? The app has stopped working for me since the last month and I doubt if it is now requiring Strong, bcz all other methods I have tried.
[Magisk] TheOct0:
Could you elaborate on your setup a bit, please? I'm curious to see what the difference might be :)
[Magisk] pershoot:
APatch (10763) + Zygisk Next (106-2) + PIF (Fork; v9) + LSPosed (mod; 7295) + Pixel Xpert (332) + Zygisk Assistant (currently not used but activated; 211).
[Magisk] Captain_Throwback:
I just installed this app from APKPure, and it opens and seems to function fine here.

I'm using APatch for root, and tested with PIFork v9 with public (sailfish) print, with Device Integrity passing.
[Magisk] devaponnadsm:
Seems like Magisk is the culprit then. Thank you
[Magisk] generalculprit:
That's generally my part.
[Magisk] TheOct0:
Are you using sailfish? I imagine not
[Magisk] pershoot:
I am not.
[Magisk] generalculprit:
Actually your husky A15 Beta3 print is rumored to be working itself?
[Magisk] TheOct0:
I can't see what might be causing this issue for me apart from my carrier then, since I'm getting those 332 status codes back whenever the issue arises. Thanks for your input!
[Magisk] aliantonio:
What apps are you hiding by the way?
[Magisk] pershoot:
none, atm. i haven't found any that detect, from previous; still observing.
[Magisk] cabagekiller:
Is there a way to check what fp you're using? I loaded my private print into pif but still unable to use RCS. Maybe I'll have to try osmosis PIF fork to check it and ensure it.
[Magisk] CZ.Kostra:
Module log
[Magisk] JazonX:
Isn't it being buried by Google ?

View attachment 6117890
[Magisk] Captain_Throwback:
This was already asked and answered here: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89583248
[Magisk] bombadier:
Its the free replacement which is called VPN by Google that is available on pixel 7+ devices, back when it was googleone vpn the free version did not work on unlocked phones, if you had a paid subscription it did, this replacement came with the June update was until today working, google have done something as it no longer works on my unlocked phone. It's off topic so nothing more to say on the subject as its not pif related
[Magisk] BarackMitzvah:
Edit - pointless post, we fix things around here
[Magisk] majorfigjam:
You probably need to replace the new pif.json with your working one, and clear Play Services cache again.

And maybe add in the extra new fields.

Or move to a more stable fork?
[Magisk] AlexS2412:
never add messages to deny list on kitsune magisk! i had to go back to apatch because it consistently broke RCS. it was a shame.
[Magisk] BarackMitzvah:
Yep, did just that. Worked like a charm, thank you!
[Magisk] Devilix:
I see lot of updates but i continue to get:

red

green

red

What is a possible solution?
[Magisk] majorfigjam:
Maybe put it in drive, and move past the traffic lights?

Alternatively, why not give some detail of your set up, so people might be able to help?
[Magisk] badabing2003:
He probably means

Does not meet device integrity (red)

Meets Basic integrity (green)

Does not meet strong integrity (red)

But yeah, without context, even if we know the state, we can't help out.
[Magisk] osm0sis:
But which of those worked? 😯

"As the light changed from red to green to yellow and back to red again, I sat there thinking about life. Was it nothing more than a bunch of honking and yelling? Sometimes it seemed that way." - Jack Handey, Deep Thoughts, SNL
[Magisk] Devilix:
DEVICE_INTEGRITY is RED

I have a Samsung Note 9 with android 9, rooted stock rom with magisk 27.

Active modules: Shamiko, zygisk-detach and play integrity fix... about this last, i have flashed via magisk and reboot.

Should i change some file, some settings?

I dont know exactly what you mean with "my setup"
[Magisk] Devilix:
Yes exactly
[Magisk] crypticc:
Hello

Am I doing something wrong?

I pasted content from a build.prop but all I got was this...

{

"DEVICE_INITIAL_SDK_INT": "21",

"TYPE": "user",

"TAGS": "release-keys"

}

Not posting the prop text itself which I got from online tadi store. But any ideas?

If someone wouldn't mind confirming with a prop they know did work I would appreciate that, thanks.

As far as the one I was looking at, I can refer to how I got the prop either directly or in riddle, as needed.

Thanks

Chris

(Edit, reading the source.js looks like the fields it did get were all added by the script. Meaning none of the text I pasted in was parsed)

(Edit2: I think I see why. The script parses for example

ro.product.model=xxxxx

Or

ro.system.product.model=xxxxx

And so on

ro.build.fingerprint=xxxxx or ro.system.build.fingerprint=xxxxx

But the content is

ro.product.product.model=xxxxx

ro.product.build.fingerprint=xxxxx

Presumably I've extracted the wrong build.prop
[Magisk] badabing2003:
Use @osm0sis gen_pif.sh or PixelFlasher and process the props again.
[Magisk] zgfg:
JSON file has different format than build.prop file - you cannot copy/paste blatantly from build.prop to custom.pif.json

Instead, find the latest version of gen_pif_custom.sh script from Osm0sis and use that script to create custom.pif.json from your system-build.prop, product -build.prop and vendor -build.prop

Look into his script to make sure how the input build.prop files should be named (like above or slightly different)
[Magisk] crypticc:
Will do

Thanks both of you
[Magisk] majorfigjam:
Read the OP and the linked FAQ, and the linked Osm0sis hints on solving integrity fails. There's lots of things that can go amiss.

If your rom is stock, as you indicate, it should be signed and not have test keys.

You don't seem to have LSposed modules, so it's probably not that which is interfering.

You have Shamiko, so you have Zygisk enabled. Is Deny List disabled, as it should be for Shamiko?

Did you try disabling modules other than Shamiko and Play Integrity?

Do you have anything in your deny list that maybe shouldn't be there?

If you are using Chiteroman 16.4, is the pif.json the right one (Sailfish or other known working print) and in the right place? Is it in the right format? If using Osmosis fork, is it named custom.pif.json and in the right place in the right format?

Have you at any point cleared the cache and / or data of Play Services? If not, try it. It shouldn't matter if you rebooted, but worth a try.

Probably other questions could be asked, if none of this works.
[Magisk] BarackMitzvah:
Extracted the build prop, remade the pif.json with PixelFlasher, replaced the file and was good to go

No need to clear cache or modify the json with extra fields or swap to another PIF implementation. Still on chiteromons
[Magisk] lpedia:
RCS is back for me! For the moment, at least. 🤞

I finally found a working image. Installed pif.json generated by PixelFlasher from that image's build.prop. Device was meeting Device and Basic Integrity, so I rebooted - and RCS was up.

My setup:

Pixel 5 (redfin) with official LineageOS 21

Magisk 27 + chiteroman PIF 16.4

Zygisk on, Enforce DenyList on

DenyList contains only Messages, Carrier Services, Wallet, and my phone company's app.

RCS is working. Wallet is working. Phone company app is working.

Many thanks to @chiteroman, @osm0sis, @badabing2003, @pndwal, and the many others who've added to the sum of knowledge in this thread one way or another. 🙂

BTW, 7-Zip 23.01 on Windows 11 can unpack .img files. I didn't need to mount system.img via WSL2.
[Magisk] AlexS2412:
but do you get detections in native detector and root checking apps? on apatch with cherish peekaboo kpm you will get at most 1 single injection detected that normal apps will never look for. check here. magisk kitsune i had working nearly same with zygisk assistant but that itself gets detected. and when i made the **** mistake of adding messages to the magisk hide list for zygisk assistant it imploded and rcs was persistently broken until i switched back to apatch and reset the app so it would "validate" correctly again.
[Magisk] Captain_Throwback:
[rant]

I say this with the utmost sincerity: who cares?

The user clearly has everything working that they need, so why does it matter what a detector app says? When did users become so enamored with these detector apps that they'd rather see a clear detection app rather than worry about whether the apps they actually need work?

[/rant]
[Magisk] intel_core_i7:
There has been claims that Strong will pass if you relock the bootloader even after you broke Knox, but the Knox features still will be permanently lost. Seems like Knox is a separate thing.
[Magisk] lpedia:
I have no reason to try any of those, given that (at present) everything I need is working.

Did you have a specific reason for asking? Your setup seems a lot more complex than mine, so I don't think I could be much help to you.
[Magisk] jakell888888888:
1
[Magisk] drfsupercenter:
I am also trying to do the strong integrity thing. How do I get a private key (or fingerprint, I'm unsure of the difference) - can I get one from a phone that passes strong integrity? I installed the Key Attestation .apk and see all the info there, but am unsure what to do with it. It lets me export as a .p7b.

I'm not asking for one, just want to know how to get my own. I own many Android phones, most of them are not unlocked or modified in any way so they pass strong integrity.
[Magisk] oopsgeneration88:
For my RCS works without any issues. I haven't used any fingerprints or whatsoever
[Magisk] shadowstep:
It shouldn't be an issue...

...unless we get a takedown notice from Google, which I don't see coming even if you shared keyboxes here in the forum. They'll just revoke them and carry on with their day.
[Magisk] pndwal:
🤔 Don't think it works that way; >29 will just get the print set out of a range of initial API values 'banned' / invalidated for some prints... (33 may be even more universal for STRONG assuming it works with prints from old devices).

Seems 16.3 always uses spoofed .xml, either the provided one in modules folder or private one if user puts in /data/adb... Key attestation on device can't see what's being spoofed to DroidGuard/GSM back end so probably always returns real device values...

Yup yup. 👍...

Does this mean that Framework Patch will effectively spoof to whole system (not just DroidGuard/S/N and PI APIs) so Key Attestation app and others see spoofed certificates and presumably extension data w/ Verified boot state?... I'm assuming so. 🙃 PW
[Magisk] pndwal:
Knox affects Samsung special functions, 'enterprise' stuff like a secure storage directory (which will be lost if was used) mainly I believe. Won't affect Google attestations at all...

Modern Knox uses a SOC E-fuse and once triggered (eg by unlocking/rooting) Knox security and features are gone forever. However if you re-lock the B/L you'll meet STRONG_INTEGRITY again.

Assuming you have DEVICE_INTEGRITY, the TaTa app might be detecting Zygisk in Magisk... @Captain_Throwback is likely using ZygiskNext (or Zygisk_mod) with APatch... Less banks are detecting ZygiskNext's (and derivatives) ptrace+fuse injection than Magisk's inbuilt native bridge method, especially when coupled with Shamiko.

Note: Magisk users can disable inbuilt Zygisk and use ZygiskNext etc as an alternative.

Note 2: Even ZygiskNext + Shamiko can now be detected, but ptrace+fuse seems to have the advantage over native bridge ATM.

🤠 PW
[Magisk] Vision:
Yeah exactly.

With Framework Patch, users can have Strong (if have a valid keybox) and spoof the BL to show as locked.

This is important because some apps still detect the BL if is unlock, regardless if can pass 3/3.
[Magisk] jakell888888888:
I searched for relevant information about strong, which went back a few years ago. I found that I had been dealing with the problem of strong a long time ago. It has been so long now, and there is still no good solution. The key box is basically not accessible to ordinary people. Yes, even engineers with certain skills may not be able to find it. I posted on this forum 20 hours a day for 3 weeks, expecting a miracle to happen, until someone told me. Even if there is a good method, they are afraid of being discovered by Google (it may not be released in a short time)

I'm still looking forward to @chiteroman

There are other ways to bypass this verification. For example, if the app requires strong verification, let the APP hook (of course I am not a professional) look forward to it.
[Magisk] Spartacus500:
Today update Play integrity fix 16.4, but only MEETS_BASIC_INTEGRITY ✅

🤷
[Magisk] osm0sis:
Why must you try to argue semantics with me about everything? You haven't even tested it, where I actually did (on a device I don't care about...). 🙄

Raising the sailfish print to 30 got Strong working in 16.3. A beta print with >29 natively also worked for Strong without changing the print and lowering that one to 25 would disable Strong. All passed Device, with and without the keybox in place.

Strong only worked for a day though, and the keybox cert serials still don't appear to be on the revoked list, so maybe that's what @chiteroman meant by "Remove keybox.xml parsing due DroidGuard detections"?
[Magisk] denzel09:
Oh it's incredible! RCS suddenly today starts to work on my Pixel 4XL, i still can't believe!

I have always the same config: standard Magisk with the same modules posted before here, deny list enabled, lsposed mod, and the same "private" pif.

I want to remember that with this pif (and other pif), until today, my pixel always passed basic and device but never had RCS working, never. I don't know now what is happened.

The only thing changed by me but i don't know if this it's the culprit is that this night i switched from osm0sis module to last chiteroman module and added the 2 "new" parameters board and hardware to that same "private" pif.json, nothing else. And today when i tried to open Messages app i have seen this:

I still can't believe it! Maybe a bug from google? Really weird...

:love::love::eek::eek:
[Magisk] cabagekiller:
You stole mine! Lol. Mine was working until this morning and died on my private print. Trying to pinpoint where it went wrong.
[Magisk] pndwal:
Like props or fields arguement? Potato potahto?... (I always mention fields now cos potahto is good.)

Anyway, we both agree/said raising API level to 30 gets STRONG going. But 'triggers the keybox to be used'?

"16.3 always uses spoofed (keybox).xml" is actually relevant to

... Raising prop or field API level value simply won't change values shown for keybox... Neither could it "trigger the keybox to be used". (It was actually already using the added keybox as expected)... Sorry boss.

🤷

Yeah, maybe. 👍 PW
[Magisk] osm0sis:
It's most likely just luck with you waiting long enough for Messages to clear its cached result or something now that you're on a private print.
[Magisk] oopsgeneration88:
@osm0sis For me to RCS works out of the box. Just configured it today itself. Verified my number & it worked flawlessly. I ain't using anything. Just kitsune magisk+zygisk+lsposed+PIF no additional things at all
[Magisk] pndwal:
So have DEVICE_INTEGRITY using public Sailfish or a private print (prop/field set)? 🤔 PW
[Magisk] oopsgeneration88:
I just used the module from the the creator of this thread nothing else. I don't even have strong integrity still it's working flawlessly for me
[Magisk] badabing2003:
I don't know what you mean by "trigger keybox to be used"

I believe the simple and clear answer was already provided by @Vision
[Magisk] pershoot:
El Goog giveth and they a taketh! ;)
[Magisk] Captain_Throwback:
I just tested RCS with Gemini using the Sailfish print, and it seems to be working. I suppose it could just be a cached thing, or it could be Google's "time of the month" to play with our feelings...:unsure:
[Magisk] TotallyAnxious:
I didn't know you could test with Gemini. Thanks!
[Magisk] D€INOS:
This is the last week day before 29th, so yeah, might be the G at play.
[Magisk] Vision:
Your answer.

So can chat with RCS with Gemini ? :unsure:

🔧 [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] killertown1611:
My cts profile match is failing also play integrity is not certified can anyone help
[Magisk] pndwal:
Wasn't me who said it, but correct, doesn't happen.

Exactly! 😜 PW
[Magisk] thefinger:
Yup. Gemini is available to chat with on Google Messages and is a good test to see if RCS is working.
[Magisk] GabbyWC:
As the owner of a new Poco F6, I can finally put my defective Redmi Note 9 Pro with PixelOS to rest. Xiaomi's HyperOS runs smoothly and works better than I expected. Perhaps I'll unlock the F6's bootloader after AOSP-based custom ROMs become available. Even if I stay with a locked bootloader and strong integrity, I'll continue to keep up with the important developments in this thread. To the users who still manage to work around Google's technical countermeasures (or at least try to), I commend your persistence through the challenges.