yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
For the benefit of others reading, you're indeed catching on! (Or maybe you just stumbled on the discovery by good fortune?)... Users of other devices can certainly benefit too...

Re. STRONG, official testers may well have root certificate signed valid keyboxes and STRONG will therefore work with default prop/field settings... The interesting thing is the lack of any range of initial API levels causing failure, and tests of others have shown that this goes for both higher ranges invalidating DEVICE and lower ranges invalidating STRONG verdicts... Ie. These prints can thus work out of the box (as 'stock') without adjustment and can also bypass restrictions other than for RCS too. (I just put such a hint in post above for some custom ROM users; I'll say no more... 😉 )

Re. OS coming out of beta, these will likely be 'banned' entirely for spoofing purposes or working initial API levels restricted at best well before that. (Just think what else could limit the duration of intended use for these builds for a clue above longevity.)... You can probably guess what options you have after that however.

🤠 PW
[Magisk] Usama-CW:
We all may not get strong integrity but if we...

stay strong and keep repeating those questions which are already being answered, we will reach 1000 pages soon UwU
[Magisk] Devilix:
Sorry but already read OP post, and i don't find any FAQ about PIF and Osm0sis hints on solving integrity fails!

Now I'm using PlayIntegrityFix by Osm0sis v9... tryed via adb to create a custom.pif.json, success. Result: DEV_integrity always RED...

Is still my fault?
[Magisk] glennza:
I've got two Samsung S9's. The battery is failing on the one I use every day, so I've switched to the backup S9 until I can replace it. I thought I'd be clever and do a backup of Data in TWRP on the dying one and restore it to the S9 I want to use.

All good except I have lost RCS (even though it is basically a clone of the working one).

When I log into my Google account and go to Personal Info/Phone, I see this...

View attachment 6118664

My original S9 must have been "Verified" but the backup S9 just stays on "Pending".

I haven't seen anyone else mention this and I don't know if it is coincidence? Can some of you guys check and see if it's "Pending" when RCS isn't working and "Verified" when it is. That info might be useful!

I am on A13 with Apatch/Zygisk Next/Play Integrity Fix v16.0. Got Basic and Device and Wallet is working.

Was Using Play Integrity Fork for a long time but lost Device for some reason and "Fix" got it working again. Maybe I should try it again.

Anyway, just thought I'd mention this.
[Magisk] pndwal:
FAQ is still there... Scroll down... 😉 PW
[Magisk] Devilix:
Yes sorry, im reading the FAQ just now....
[Magisk] Aregtheeditor:
We need hope. Also is it possible to sue google for their practices against rooted phones?
[Magisk] zgfg:
Really?

Btw, many industries (financial, etc) require secure, not-modded phones - you will sue all of them?

And governments for digital ID apps that require secure devices
[Magisk] Aregtheeditor:
No, but mostly google is responsible for the API
[Magisk] zgfg:
You are responsible for your modding and the consequences

If you don't apps that test Play Integrity, who cares for that

For those apps, buy the second phone, use as not modded and secure

Or play the game - install PIF, fish for the private prints (only if you need RCS)
[Magisk] Aregtheeditor:
But like in early 2010s there weren't stupid limitations for modding/rooting your phone.
[Magisk] majorfigjam:
Where are the Mods when you need them?

Like in the early 2000s, there weren't phones to mod or root. Phone phreaking threads, anyone?

Edit: unless you count adding ringtones to your nokia as modding
[Magisk] flobo09:
Thank you all for finding that loophole.

It's all working again on all devices 🥳
[Magisk] pndwal:
Go for it!

Spoiler content hidden.

😬 PW
[Magisk] zgfg:
Back in 2010 you didn't have RCS and you didn't pay by phone in lieu of plastic

If you still need the phone just for calls and SMS, you can use an old (rooted) Lollipop from those days

Anyway, there is another thread for anti Google philosophical sentiments
[Magisk] Aregtheeditor:
ok. Sorry for dumb opinions.
[Magisk] pershoot:
Take note of the verify bit:

🔧 [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] TotallyAnxious:
If we can't read the forum easily. Neither can Google!
[Magisk] manjaroid:
Yep, I bet this particular door slams shut sooner than later. I'm expecting it to happen the same day my last custom print stops working.
[Magisk] Usama-CW:
Use xda search filter when?
[Magisk] TotallyAnxious:
Right after I ask this question that was answered/asked in the post above mine. I promise to use it next time! For example:

When will people start using xda search?
[Magisk] bobpiesz:
Running kitsune, lsposed, PIF module, on pixel 7 A13 and using a custom/private PIF has RCS working again for me! Plenty of good hints in this thread.
[Magisk] Wolfcity:
Ask chatGPT. I think that question will be to much even for AI's....,sorry for being OT.;)
[Magisk] cabagekiller:
I had the same setup and my RCS died randomly.
[Magisk] zulu88:
Maybe only when it starts working properly.
[Magisk] 306bobby:
Don't speak too soon, the one doggo print works fine still, the other doggo print was banned for integrity about 2 days ago and lost RCS yesterday
[Magisk] BillGoss:
https://xdaforums.com/search/71295449/?q=When+will+people+start+using+xda+search%3F&o=relevance
[Magisk] Nergal di Cuthah:
Getting a little OT but search breaks in app, tells us neo broke the site, must use web to search
[Magisk] Iridule:
Yeah the new "updates" broke everything on my moto edge lineage 20. I went back to 27002 debug.
[Magisk] zgfg:
Preferences, Style, change to XDA-Dark or so

I know, it's a nonsense but play with that

And indeed, one more reason for some ppl not to use Search in this thread
[Magisk] jakell888888888:
keybox test

493c497f24984e2988174dfe65775a5c.pdf - kb_b.xml 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 <?xml version=

Document 493c497f24984e2988174dfe65775a5c.pdf, Subject Computer Science, from Indonesia Institute of Arts, Surakarta, Length: 4 pages, Preview: kb_b.xml 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51...

www.collegesidekick.com

：

adb push 文件 /sdcard

adb shell

su

cp /sdcard/keybox.xml /data/adb
[Magisk] casouzaj:
Key Attestation app says that the first two attached files are not trusted, and the last one (keybox2.xml) is the AOSP one, which seems to be the same one present in chit's PIF v16.3 zip file.
[Magisk] jakell888888888:
OK Thanks. There is also a keybox in the connection have you tested? I don't know how to download. I asked friends to download these for me. I'm not very skilled in development.
[Magisk] denzel09:
What you mean with "in the connection"?
[Magisk] jakell888888888:
Does this prompt mean that I have found the keybox and can use it? My problem is that I enabled: Framework Patcher GOv1.1.1 by changhuapeng

If this module is turned off, verification will be performed.

I'm not a developer. Can anyone help me answer this question? (I found the keybox but I'm not sure if it works (I'm having trouble figuring out my key info if it works.)

View attachment 6119048

View attachment 6119050

open

View attachment 6119049
[Magisk] majorfigjam:
Signed by the AOSP Software Authentication Root Certificate The private key of the authentication key is known to be tampered with, and the certificate chain can be tampered with.

Probably on Google's list.
[Magisk] Claus….:
I have not followed the thread as much lately, but I really hope that you stay on this thread! Your contribution is highly appreciated! And in hunt for the integrity, we sometime forget to thank all the people making effort, and you are one among them!!
[Magisk] dr.ketan:
View attachment 6119164

Why Gemini why?
[Magisk] aliantonio:
So as it stands right now, is unrooting enough to regain RCS and wallet functionality or do we have to re-lock bootloader as well?
[Magisk] pershoot:
If you want both RCS and Wallet and want to get out of the cat and mouse game: unroot -> re-lock bootloader -> data will be wiped.
[Magisk] aliantonio:
Ugh I was hoping to avoid the data wipe :( thank you
[Magisk] cabagekiller:
Or find a private print that works for both.
[Magisk] aliantonio:
Unfortunately I don't have the time or patience for that lol
[Magisk] osm0sis:
I can confirm that STRONG integrity gets VPN by Google for Pixel working again with no other changes to my setup. 😵😓🤯

Thanks to @badabing2003 for the help. 🙌🙏

Edit: Could be it just thinking the bootloader is locked now... We'll need to test further to know if it's actually that part or the passing STRONG part. 🤔

Edit 2: Nope! Seems like it is actually just the STRONG pass! Now we know! Thanks Google! 🫠🙄
[Magisk] jakell888888888:
Yeah, I'm still trying to figure out how to replace the key. It's too hard for me,
[Magisk] crypticc:
Dunno if it was something I did but my wallet started failing with the default print, so I dusted this off, followed the scent trail laid out several times, and redid properly...

Interesting side effect matching what others reported is that RCS now works. It's the print that does not pass STRONG.
[Magisk] badabing2003:
The print is expected not to pass strong, unless other measures are taken, but for the purposes of this thread, if the print is a not banned print (passes device) different than Sailfish, it is expected that RCS should work and wallet should work.
[Magisk] crypticc:
Yep. BTW and anticipating the train slowing down I've just sent a few € / CAD to Osmosis and Chiteroman using deets from their git and profile. I often note your stance on your tool that I use regularly, but I just want to say thank you!!
[Magisk] Spacebar_21:
Hey guys, very long thread, too much for me to read through.

Can someone please tell me if RCS is still broken? On Google Pixel 8. It's been broken for weeks now. Is this the end of RCS with root?
[Magisk] Nergal di Cuthah:
Edit: thought i was in another thread oops.

You need a non sailfish print to get rcs working
[Magisk] Spacebar_21:
How do you get one of those?
[Magisk] BillGoss:
What other measures? Surely not the illicit keyboxes that @osm0sis is, rightly so, against using?
[Magisk] pershoot:
You can use RCS with your own device's print (shiba). Disable PIF if you have it installed. If you use LSPosed, disable it, if you run in to issue.

If you want RCS + Wallet, please refer to the other poster(s) advisement.
[Magisk] osm0sis:
To be clear, I tested for science because I wanted to know about the VPN by Google for Pixel situation, but I do still maintain that keyboxes are not super above board. 🤷‍♂️
[Magisk] badabing2003:
Yes, the other measures should remain above board, that's why I didn't directly refer to what / how.
[Magisk] BillGoss:
I didn't know whether to "like" your reply or "laugh" at the slippery justification. So here's the 🤣
[Magisk] osm0sis:
Acknowledged. 😬😛
[Magisk] Nergal di Cuthah:
By reading the first post and its links to start with
[Magisk] Vision:
All for the Science 🔭 🧪 🧬 🤓
[Magisk] specialk3585:
Do you need to do anything after you disable PIF to get back to the devices print? Also unrelated, but I'm curious if anyone uses the My Hyundai Blue Link app on their rooted android. All of a sudden it's no longer working even when added to magisk deny list and passing verification.
[Magisk] sawdoctor:
Google has just pushed a new beta update so we'll find out soon if a print is going to die
[Magisk] pershoot:
Nope, that would be it.
[Magisk] Nergal di Cuthah:
Yeah probably those using beta custom fp will need to update in next few days. Is chit using a similar, built-in in, fp in latest version?
[Magisk] jakell888888888:
Thanks
[Magisk] BarackMitzvah:
Weird, PIF 16.5 broke RCS for me on a custom print

Rolling back seems to have fixed it, interesting
[Magisk] sawdoctor:
Maybe 16.5 was using the embedded print rather than your custom one
[Magisk] BarackMitzvah:
I'd have to assume so

I did have it in the proper location as pif.json, but yeah not sure

If it ain't broke, don't fix it I guess, RCS has been nice
[Magisk] zgfg:
Why guessing

Check the PIF logcat and read which prints are really used
[Magisk] BarackMitzvah:
If I didn't already have it fixed by rolling back + wasn't working right now I would
[Magisk] cabagekiller:
What version are you running now?
[Magisk] kornball:
Wow, the VPN by Google One always worked for me even with unlocked bootloader/root, but the new VPN by Google does not. Thank you for demonstrating STRONG pass is now necessary. Guess I'll simply move to another VPN provider.
[Magisk] osm0sis:
Yeah, it used to still work while unlocked as long as you had a Google One subscription, but clearly they've decided they don't want to do it that way anymore now that it's on-device. 🫤
[Magisk] chiteroman:
It was a (very) bad idea to release FrameworkPatch and keyboxes to public, now I only have 1 keybox working but for how long...

Google has really gotten quite angry....
[Magisk] geokilla:
To be honest, I've been following this thread and I have no clue what files I need to mod or where to find a print to get RCS working. All I know is that I need PIF v16.5 by chiteroman to start. Maybe we can update the OP with the latest instructions?

Btw, is there any reason why Magisk would keep on disabling PIF v16.5?
[Magisk] BlackSoulxxx:
Keybox price is half of bitcoin nowaday :rolleyes:
[Magisk] cabagekiller:
You just need an unburned FP for RCS. It's just going to take a lot of time and patience. Not much else you can do.
[Magisk] majorfigjam:
Really?

It takes about 15 minutes with a fast internet connection, the patience to read and understand this page and the OP , and the ability to follow the instructions linked from the OP.
[Magisk] fbirraque:
I totally agree with what you said but the 15 minutes estimate is pretty optimistic, isn't it?

🤔
[Magisk] majorfigjam:
Nope, I just OTA'd the new beta to my spare device.

I needed to test the new pif, so I also downloaded the image, unzipped it and created a new pif with Osm0sis script, all in 15 mins.

I guess gigabit fibre helps, but the rest is straightforward.
[Magisk] intel_core_i7:
I don't think it's such a bad idea. You said before that BootloaderSpoofer can be easily detected by third party apps, so FrameworkPatch is necessary for some people who uses app which its developers is lazy or being cheap and not to use STRONG but local hardware attestation, and is smart enough to have some sort of zygisk and LSPosed detection.
[Magisk] fbirraque:
Okay then I misunderstood what you said.

You're using the public PIF (Sailfish) and not a private one. I thought you said that found a private one in 15 minutes...
[Magisk] majorfigjam:
No - I'm not using Sailfish since the original Osm0sis hint. I downloaded a new image and created a "private" pif from that image. Hardly "private" now though, given the comments on the previous page!
[Magisk] fbirraque:
Yeah if know which fp's source is good
[Magisk] TotallyAnxious:
Google just released another working print today. Doesn't take much time at all.
[Magisk] D€INOS:
Why should that beta print be "denied" just because they are a new beta build? That won't make a difference.
[Magisk] Nergal di Cuthah:
Becsuse they'll burn it once enough real betas are on new bc they know how many and, though it'll do nothing to the real devices that held back, they can tell how many of us are using the print(s)

Remember it's a cat and mouse game the cat lets us have our fun but takes many of us each time it wants (which will probably be after the US holiday)
[Magisk] majorfigjam:
Agreed, and earlier 15 betas have already been blocked.
[Magisk] D€INOS:
Because of the amount of users using, and NOT because it's a print from a beta build, then I agree
[Magisk] Aarif goku:
Why can't we use Frida to bypass all integrity checks? Can't we spoof the results.?

Or it's because we cannot decrypt something from the verdict response?
[Magisk] acwcanada:
Perhaps dump question:

I have the Pixel 6 Pro and the Pixel 8 Pro, both are on Google 15 beta 3 (will update to 3.1 later), I don't have my own "private" print for them. Right now both devices are on chiteroman's PIF v16.5 and the default prints come with it are disabled to force both devices to use thier own prints. They both passed "basic" and 'device" integrity. With such setup, I have no problem on RCS and Wallet, plus all of my needed apps. I don't need "Strong" for apps such as Google VPN (it is useless to me as I piad for NordVPN which believe is better).

So my questions are:

How long can my present setup last, such as on A15 beta 4 and when it becomes official etc.?

Are my devices losing anything without using a "private" print?
[Magisk] Nergal di Cuthah:
The "beta loophole" has only recently been discovered but i, and others, think as long as it's the current beta(s) it will pass. This is a non-baseless guess, nobody really knows.
[Magisk] geokilla:
Oh I read them. But I don't understand what is being said in the FAQ post.
[Magisk] pershoot:
replace shiba with panther, in the verbiage, if you are using the device in your sig.

🔧 [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] cabagekiller:
What do you not understand? Maybe you can PM your questions.
[Magisk] flyoffacliff:
Has anyone found a way to automate the testing to see which ones are burned, without manually swapping them over and over?

Has anyone found out yet why the beta prints are working? Especially given that all devices that support the beta have a working TEE. There's no logical reason why they should pass.
[Magisk] BarackMitzvah:
16.4
[Magisk] flyoffacliff:
Yeah it should be updated I think. Difficult for us normal people that don't check in every day, with all this rapidly changing information floating around. Lol

Was not aware Google VPN still even existed. They claim it was discontinued a couple weeks ago. I guess they're trying to make it a pixel exclusive and moving it from the Google one app directly to the device firmware
[Magisk] geokilla:
majorfigjam sent me a PM with some instructions. Thanks for the offer. If I need additional assistance, I'll be sure to reach out to you.
[Magisk] majorfigjam:
1) ZGFG post 13262 has a script that runs on your phone using a folder of jsons. I used it back in the day to find prints that worked. Sadly they are all now banned.

2) Seems that the latest 15 Betas are working - maybe Google beta testers need to have ia way of checking against Device Integrity, or maybe its a parallel test to Strong Integrity testing.

Edit: earlier ZGFG link seems dead. Over to @zgfg.
[Magisk] Nergal di Cuthah:
Afaik TEE is only relevant to strong. Betas imho are working because some devs need broken trust to see things working (read logcats, see internal workings, figure out a way of stopping us from circumventing their app's security), only a guess but that's what i believe
[Magisk] Nergal di Cuthah:
It shouldn't be easy peasy, reading comprehension is a must for this site, imho @osm0sis keeps it up to date with the important stuff, for those who can't follow day to day. It should not need to be dumbed down, again imho.
[Magisk] CZ.Kostra:
And I thought they hired a good person at Google. :ROFLMAO:
[Magisk] osm0sis:
Speaking of which, the script to automate json testing has been listed in Resources under Scripts in my README for almost a month now. 😛😶‍🌫️

PlayIntegrityFork/README.md at main · osm0sis/PlayIntegrityFork

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

github.com
[Magisk] cambunch:
I decided to try and get a beta fingerprint to work today. Never messed with a custom fingerprint before, and can confirm it does not take very long to at least figure out what to do if you read these posts and know how to use Google search. I had RCS working for a few hours before it broke again, so I must have been close. 🤬

In the meantime, I have been mentally prepping myself to try an unrooted phone when the Pixel 9 comes out. So far Adguard has been a great replacement for AdAway, and Wavelet a great replacement for V4A. Really my only 2 uses for root these days.

I have been a rooted user since the days of the OG HTC Droid Incredible. RCS compatibility is really pushing me to stop using root, especially with RCS support coming to iOS 18 and improving communication for those I talk to that are not Android users. Seems like the juice might not be worth the squeeze anymore if Google is going to continue breaking fingerprints whenever they feel like 😔
[Magisk] TheRomRooster:
Updated to one of the July Beta PIFs and it gives device
[Magisk] zgfg:
What would be the use of encrypted verdict - how would then apps that asked for the PI verdict read the verdict?!

Click to open the (Verdict) JSON in TBChecker or PIC and read the plain JSON verdict - nothing is encrypted in the verdict

For the rest (communication between the requestor app, through Play Integrity gms unstable, Droid guard app, Trust Execution Environment) Google servers and back through gms to the requestor app), what is SIGNED by private Google and OEM keys (not encrypted - its not about encryption), and why you cannot spoof, all that has been extensively discussed and explained here with the presented technical documentation

If interested, you can search. Of course, it's not really of use for the average Joe who wants to pass (Device) PI, hence it's not in the FAQ or so, but definitely IT WAS here in the thread
[Magisk] majorfigjam:
It broke of its own accord, or you added something (eg lsposed or another module) that broke it?
[Magisk] zgfg:
If you refer to Dedyn, there are still working prints in the folders there (and they are not coming and going like Pixel beta prints, and they are used by smaller audience) hence they still last for months
[Magisk] majorfigjam:
No, I was referring to my own stash of prints found from various places, not from one of the repositories. I had managed to score around 30, but they were obviously too "similar" and they all were banned eventually. I used the script to weed out the banned ones.

In any case, I see Osm0sis has made your script available in his resources link.
[Magisk] zgfg:
There are still publicly available places (Specs, Tadi) with build.prop files from various major (and smaller) OEMs.. There are scripts to make JSON files (Osm0sis, I had mine too) and by testing you will also find the working prints

Ex: It might be worth to RE-test prints from other manufacturers but for Pixel phones
[Magisk] cabagekiller:
When I had my last working print, it died after a few hours for some odd reason. Anything I did could not bring it back. I even switched to apatch to try to bring it back. But now I'm on sailfish so no RCS at all. :(
[Magisk] majorfigjam:
Hopefully others will follow your leads.

It's been 7 long months since the custom print hunt began, and we're still seeing and answering the same old questions, despite there being Osm0sis and others' excellent guides as reference. Unfortunately the range of targets is much smaller now.

For me, I'm good for now on my main phone with non-15beta prints, and a Samsung Classic 6 as backup for wallet.
[Magisk] NightRuS:
ctsProfileMatch не проходит проверку