yashsingh1/xdaforums huggingface dataset:
[Magisk] denzel09:
@osm0sis if i have an old phone with android 10, can i extract from this the keybox.xml?

If YES, how to do that without root permissions, adb maybe?

Thanks
[Magisk] osm0sis:
Why are you asking me? I don't have anything to do with keyboxes, nor do I plan to.
[Magisk] Vision:
View attachment 6117075
[Magisk] denzel09:
I can't understand. No, it's no possible extract from private device or no, there aren't devices with security vulnerability to extract key from secure environment?
[Magisk] Vision:
It's not possible extract.

Only if you have NASA's telescope, to see inside in the Chip.
[Magisk] denzel09:
Ok, so where do all the keybox used by users here come from, for example? Where do they get them from? Where should I look, I don't understand.
[Magisk] Vision:
Unfortunately, is not easy.

Maybe have friends and shared with them, or found it on internet and need and lot of luck.
[Magisk] pndwal:
Shonky OEMs / employees, dark web etc. (ie they're 'leaked' by definition.) 😬 PW
[Magisk] pershoot:
I'll help you further along.

You can target your information gathering based on these (current) scenarios:

1. RCS functional; Wallet / contactless non-functional

2. RCS non-functional; Wallet / contactless functional

3. RCS functional; Wallet / contactless functional.

Based on what you desire, you can target that area.

Happy reading! :)
[Magisk] bou1l3m:
how to explain this @chiteroman ?
[Magisk] DuskGolem:
Is the latest xiaomi.eu fingerprint toast? I can pass basic on play integrity and safety net is fine too. Just the device integrity not working. My device is Galaxy A8 2018 and I have tried both osm0sis' module and chiteroman's as well but device integrity still fails.

It looks to me that google is taking out these xiaomi.eu prints faster than before (or may be I am wrong).

Man, google is trash. What is the point of AOSP now anyway? They should make android closed source since they are showing no restraint whatsoever in crippling the android development and modding scene.

I am thinking about putting rooting on the back burner until I am able to buy a second device 😭😭😭.
[Magisk] zgfg:
I must be missing (I'm trying to catch-up with the last week but after reading twelve pages I'm still on Tuesday and 25 pages behind)

In all those Eureka, passing Strong (fixed then by Google) tons of posts, did anybody tested and found one, two, three apps that worked with that fake Strong, and do not work otherwise

First that we know which apps really need Strong, and second (and more important) to prove that this quest for the spoofed Strong is of the real use

Btw, just few days earlier ppl cried here for RCS. Then, for one day it was possible to spoof Strong with Sailfish and SDK 34 - RCS still did not work but most were happy like kids and didn't care about RCS😁
[Magisk] khusika:
It seems like those are two different things. AOSP was never shipped with GApps and Play Integrity only relates to Google Play Services which is part of Gapps. 🙄
[Magisk] Vision:
Yeah i get your point.

Until now, working good with apps need pass 2/3 as before, but as you say what happens about Strong? Anyone with Strong have test a apps?

I have create a list and i hope users write what need what, to help each other to know.

The only know is Ingress Prime (augmented reality game, need Strong).

Apps&Games need PI (List)

Here you can post what apps&games need to pass 2/3 (Play Integrity) to show it on Google Play. Some apps&games appear and can download but when open (for apps until now) can't use if not pass DEVICE, because required to pass 2/3. Also from now...

xdaforums.com
[Magisk] DuskGolem:
No point in splitting hairs. I am just extremely disappointed and tired of Google's BS. Might as well buy an iphone if everything needs to be kept locked.

I moved to KSA recently and it is a hell to use a rooted device here. Every assinine gov. / banking / wallet app needs either device integrity or locked bootloader. The choices are to either give up rooting or buy a second phone (I am going for the former, for now).
[Magisk] beeshyams:
Really tough to catch up with multiple pages being added everyday and this may have been posted before, but saw this in a Tg group & thought of sharing

Eatventure , a lemonade selling game checks for PI even in OFF-LINE mode :oops:

Out of my 99 installed apps (no games), 20 are in deny list and the list is only growing...Game over for rooting at this rate :cry:
[Magisk] pndwal:
You're using bootloader spoofer with the Key Attestation app selected... That's exactly what's supposed to happen. (It doesn't fool the Play Integrity API's server side evaluation of course.)

The Key Attestation demo apps from vv and Rikka is just that; it demonstrates how key pair attestation data can be parsed (extracted), validated and interpreted including measurements for Boot State. However it does NOT send the certificates to a separate (trusted) server for validation.

Google's own Key Attestation model and documentation shows/states:

Bootloader Spoofer takes advantage of exactly this... The use of hooking/injection to spoof the extension data can succeed since the parsing and validation of the data by the Key Attestation demo is occurring on the compromised device...

This can also work for bank apps that lazily deploy on-device validation too. However it can't work for apps that properly implement Google's "Verify hardware-backed key pairs with Key Attestation" model, ie that send the certificates to a separate (trusted) server for validation.

👀 PW
[Magisk] pndwal:
Further to the above, modders (supposed to be 'ethical' hackers) seeking/using keyboxes signed with the Google Hardware Attestation Root certificate has serious implications and will/should probably be viewed as worse than discussing, posting, soliciting or hosting werez on XDA.

That's because of the serious repurcussionas it can have for users of devices for which the leaked keyboxes are made. Read 'innocent users of locked/stock devices' here...

Our motto should be 'do no harm'

if we're legitimately to be considered an ethical / white hat modding community, but the fact is that prior to the production of devices launched with Android 12 (introducing Remote Key Provisioning) and 13 (making RKP mandatory), if a key was/is leaked/exposed, Google would/will need to revoke it. This means that for any device that has the leaked key injected at the factory, users will not be able to access protected content, functions and services like PI integrity attestations, bank apps, Google Pay/wallet, biometric scanning, Digital Car Key, Identity Credential API etc etc since there's no way to repair revoked or provision new keys (short of affected models all being recalled for fixing by manufacturer)...

Do we want to be responsible for innocent Android device users potentially having their devices crippled this way? Is it even ethical to be contemplating this type of hacking when doing so could ruin some unsuspecting upright connsumer's day?...

Key attestation implementation (and provisioning of keys) therefore requires utmost secrecy from a manufacturer for good reason... Of course, Remote Key Provisioning may lessen the impact of secret keys being misappropriated since only Google will handle 'secrets' for later devices and keys can be both revoked and re-provisioned remotely.

Meanwhile, please be careful what you contemplate doing and what you wish for folks... There's many shades of grey between white and black hat hacking.

🙃 PW
[Magisk] zgfg:
Interesting question

It's not command but a script (calling many commands). It reads build.prop files and it should create custom.pif.json - hence nothing prevents you to try from Terminal in TWRP

Script requires sed and grep Linux utilities - I don't know are they provided in TWRP Terminal (AFAIK, it does not provide 'full' Busybox) but you can always try
[Magisk] intel_core_i7:
The good old model of security: having everything at utmost secrecy. Many people arguing open source software is more secure than closed sourced probably haven't yet learned about the state-of-the-art PI, and those probably will be pissed after they found out how good (and absurd) it is.

I wonder how GrapheneOS's own key attestation work, and if some of their claims in this page are correct (e.g. Android's hardware attestation API provides a much stronger form of attestation than the Play Integrity API, because PI uses just that with STRONG and with keys hidden from everyone else but google and repsective OEMs), it feels like this article is kinda outdated. Though I don't really understand everything stated in it.

GrapheneOS attestation compatibility guide

Guide on using remote attestation in a way that's compatible with GrapheneOS.

grapheneos.org
[Magisk] badabing2003:
All valid points and good things, and we should all want to have it, but have you seen the cries that it was lost and that people would resort to unrooting and locking bootloader, moving to iphone amongst many other things, it's like it's been there for ages and that now that it's gone life stops.

Where were all these people that wanted to move to iPhone all these years, RCS is new, unlike iMessage which has been there for ages, why haven't they used iPhone then?

Furthermore, there are alternative way of achieving everything you listed there, and there have always been available.

To each its own, I love RCS and use it, but if I lose it, I'm not going to cry over spilled milk, I'll continue to use signal and other tools, I much prefer to have my device rooted, Firewall and other tools running and blocking all the behind the scenes tracking that is going on, which is far more valuable than e2ee if you ask me.

But like I said, to each its own, and no insults.
[Magisk] zgfg:
Have the script and build.prop files in the same folder, say Download folder, then select the script file in MiX, choose Execute from the top-right menu and MiX will execute the script. Look for the pop-up output if something failed and for the resulted custom.pif.json created in the same folder

No need for Terminal Emulator (however, MiX must be granted root in Magisk)
[Magisk] zgfg:
Other important considerations:

6) phones with screen-protectors? Can/Yes/No

7) on rainy days? Can/Yes/No

😁
[Magisk] Scholeggo:
Is it just me or does PIFix no longer pass device integrity with the private (or even sailfish) fingerprint? I woke up this morning to find out my private fp has no integrity, so i fell back to sailfish to find out that lost integrity too, so I was freaking out. I switched to PIFork, tested my FPs again and took a couple restarts (and Google Messages force stops and cache clears) for me to get rcs and device integrity back

PIFix may be broken now
[Magisk] markdewet:
I was not going to reply to this, however, since for some reason, you seem to "take" one part of a sentence, out of context I might add, to "mean" something COMPLETELY different, or "mean" what YOU WANT it to mean, then I feel that maybe your grasp of the English language is not as great as you thought it might be.

FWIW, I have also followed this thread from the beginning and MOST of what is being discussed is not only beyond me, but most times very difficult to understand. Again I am just not as smart or as technically inclined as the rest of the people on this thread, but that does NOT give ANYONE the right to make aspersions or assumptions. Please do not bother replying, I have ZERO interest in continuing this conversation. Thank you.
[Magisk] fbirraque:
keybox (SW signed) is pretty easy to find but it is useless if you're trying to get the Strong certified.

keybox (OEM) answer could be found in the previous 3 or 4 pages...
[Magisk] denzel09:
Yes, i got it.. :(
[Magisk] samhhmobil:
I cannot confirm that.

It works.
[Magisk] denzel09:
I am searching in every single leak forum, there is ALL but nothing comes close to being a keybox.xml LOL

Someone talked of DW, but honeslty I'm scared to go there and I wouldn't know where to look anyway...
[Magisk] ScottIsMyName:
I find it incredibly difficult to believe that you have followed this thread from the beginning. You constantly have excuses for why you don't know something or why you can't follow instructions, even when they've been posted ad nauseam and multiple places.

This is just my opinion, but it seems to me that you're one of the people who would much rather been spoon fed information rather than trying to read clearly posted documentation and learning for yourself. All of the questions you have had here have been answered multiple times in this very thread. You cannot blame your lack of technical knowledge for not being able to figure it out.

Also, to be quite blunt, if you really are not as technically inclined as you claim to be, why in the world are you even messing around with rooting your phone, installing custom roms and magisk modules?

I'm not trying to be a jerk, and I don't want to offend you. Just my 2 cents.
[Magisk] markdewet:
Whatever.
[Magisk] HippoMan:
What about the following: 99.9 percent of Android users are not modders, and lots of them are now using RCS. If any of us modders want to communicate with those RCS-utilizing non-modders, we might face the RCS-related problems that are being discussed here.

Telling all of a modder's RCS-using friends, family, and business associates that they cannot use RCS reliably to communicate with that modder is problematic for all of them and for the modder. I already know of some modders who are facing this problem, and I only am aware of a tiny fraction of the world's modders.

As RCS use increases, this will impact more and more modders in the way that I am describing here.
[Magisk] badabing2003:
Valid points, and again I'm not dismissing the issues, but would that make you switch to iPhone or unroot?

You know you can change your settings back to SMS only and live like you lived before RCS, and by the way, that's on Google that it doesn't automatically drop to SMS when RCS is not working, that's a bug not by design, why I say that, because with my limited testing, it immediately dropped to SMS when RCS was not available, and vice versa.

Indeed, I say if there is a will there is a way, no matter the limitations one legitimately might or might not have.

There are many topics way over my head, and when I'm facing problems in those areas, I don't ask to be spoon fed, what I rather do is follow to the point I understand, try to exceute those, and report back exactly at what point the results deviated from the expectations, asking a specific question on the specific point one may have difficulties with is the right way to do, and that makes me learn and understand better.

I think blindly following a well written guide doesn't teach you anything if you don't question why you're performing each and every step, what does it do? what does it achieve? why do I need to do it? can I do it differently? ...

Just my 2 cents.
[Magisk] aliantonio:
@pershoot yeah, no luck either. Sticking with apatch and RCS functionality for now, but my rooting days are coming close to an end sadly. Not to sound too pessimistic, but the Juice isn't worth the squeeze anymore for me.
[Magisk] HippoMan:
Luckily for me, I'm not one of the modders who has RCS-using friends, family, or associates. But if that ever changes, I wouldn't get rid of my modded phone, but I might find myself needing to get a second non-modded Android phone, or perhaps an iPhone.

I seem to recall that one or more modders have reported not even receiving messages sent by RCS-using people, so I'm not sure that we can simply count on RCS messages always getting reliably sent as SMS when one of the communicators isn't using RCS.
[Magisk] BillGoss:
RCS users have the option to enable or disable falling back to SMS.
[Magisk] HippoMan:
Oh, that's good news!

PS: Oh ... but does this mean that all friends, family, and associates would need to enable this option if they want to send an RCS message to a modder without working RCS? Or can the modder set this option (or a similar option) for any incoming RCS message to be automatically changed to SMS?
[Magisk] Vision:
Yeah, if both side have enable this option.

Until now, I have it disable 😂🤣
[Magisk] badabing2003:
If you disable rcs as a receiver, the sender sees that the communication is sms and not rcs.
[Magisk] badabing2003:
It's not needed on both sides, if one side is set to sms, the communication will be sms.
[Magisk] HippoMan:
Oh, that's more good news!
[Magisk] Vision:
What happen, if the rooted device have enable RCS with FP block it for RCS ? When the normal users send a RCS messaging, Google message say can't send and try as sms?
[Magisk] cabagekiller:
Is the fp makes RCS checks fail, at least in my case, the other phone detects it and sends an SMS for the most part.
[Magisk] osm0sis:
It's been reported many times now, RCS will fail silently at first, then start outright failing and fallback to SMS. The problem everyone's having with it is the first part, since what if something important happened and they couldn't be reached?

Added to the FAQ last week as #13 👍

PIF FAQ

PIF FAQ Abbreviations DG = DroidGuard (SafetyNet/Play Integrity) GMS = Google Mobile Services (Google Play Services) PIF = Play Integrity Fix Frequently Asked Questions Q: What is a fingerprint and where does it come from? A: A fingerprint...

xdaforums.com
[Magisk] mac796:
Yes I'm one of those people I didn't get messages for 2 days. I didn't realize I had RCS on. Once I turned it off messages started flooding in. They might have fixed that bug though. Now I see it switch to sms. But who knows.
[Magisk] Vision:
Thanks for all useful info. I appreciate as always.

Sorry if what i asked has already been answered, in past not use RCS, but now I need it (unfortunately) for important conversation.
[Magisk] frank93:
as far as i understand (that option), it’s a fallback only when/if RCS "disconnects" - but the thing when using sailfish, for example, that the status shows "connected" while in fact it is not. so in my understanding there’s no fallback activated.

(though RCS isn’t that important for me either, i’m just saying maybe it’s not that easy unfortunately.)

edit: sorry, i’ve seen this has been discussed already while i typed my reply .. :)
[Magisk] cabagekiller:
My locked bootloader phone does not detect my rooted phone has RCS at all even with it showing as connected. It seems to be a case by case situation. At least, when it first started happening.
[Magisk] HippoMan:
Oh, yes ... now I remember that this is the case that was described by one or more people.

So indeed a modder may very well miss incoming RCS messages.

Oh well ... what I thought was "good news" regarding RCS isn't so good, after all.
[Magisk] cabagekiller:
My locked phone has only sent SMS to my rooted sailfish phone since the RCS ban. No missed messages at all.
[Magisk] Thebear j koss:
And my messages get deleted for being off topic... Always top notch here at XDA. A 4 page convo about RCS and my 2 posts about RCS get deleted. 👏 👏 👏
[Magisk] passionicon:
Any updates about TEE on oneplus devices?
[Magisk] chiteroman:
PIF will never have a fix for broken TEE devices.
[Magisk] Vision:
So this is only for frameworkpatch method? I ask, so users not ask about broken TEE with PIF module.

View attachment 6117252
[Magisk] chiteroman:
Yes, because I can hook system functions, with PIF that's not possible.
[Magisk] USHERROB:
So I just got this random Gemini message and then saw its via RCS, but my RCS hasn't been working.

Passing Device only...and haven't made changes in a week or 2

Using

Kitsune (latest canary)

HMA

Chit's Bootloader module

PFork9

EDIT: My phone is a OPOpen on A14 (broken TEE)

View attachment 6117255

View attachment 6117256

View attachment 6117261
[Magisk] tannerspaw:
Did you get a new fingerprint or something as well? Or did it truly come out of nowhere, since I was only passed Basic today and still can't recieve RCS at all.
[Magisk] USHERROB:
Pretty sure you have to AT LEAST pass "device"

Also, last pif was created on Jun 19 so I could pass device and then didn't mess w/anything since I have an OP device (need to figure out TEE issue)

So no recent update on fingerprint afaik

View attachment 6117274

EDIT: Alright, this is even stranger... Either RCS hasn't updated on other chats, or Gemini is only checking that RCS is on. Regular texts are still not RCS

Gemini Message:

View attachment 6117275

Human Message

View attachment 6117276

But when I see try to send a test RCS to Gemini it still fails:

View attachment 6117282

View attachment 6117283
[Magisk] Captain_Throwback:
Could have something to do with this:

Spoiler content hidden.

EDIT: But I see it actually still fails for you, so nevermind.
[Magisk] USHERROB:
Stupid Google and your false hopes and dreams lol
[Magisk] USHERROB:
Touche sir lol....and good to see you again hope all has been well!
[Magisk] tssroot:
Good evening, which version of Android are you using? kernelsu,?
[Magisk] pershoot:
Ya, I hear you. I'll take note and keep a lookout for this particular use case.
[Magisk] trevtdogg:
I'm shocked at all these replies. I'm thinking maybe you are getting a few different user names mixed up?

because I've seen far, far worse in terms of demanding entitled questions and requests for easy answers by many others in this thread, without the same sort of pile on that this has attracted.

can any of you quote relevant sections where @markdewet was even asking to be spoonfed? let alone even to be the worst offender?

to me it seemed this all started when osm0sis possibly took this comment quite personally (and in my opinion over reacted) to an honest and valid opinion:

as great as osm0sis's guides are, every document has an intended audience and an intended knowledge level of that audience. it's very hard to write a one size fits all knowledge levels guide, and to be honest I don't think that is a realistic goal. markdewet was just saying that they fell under the knowledge pre requisite. and that's ok.

to me, it appears markdewet has done everything right - read everything, tried to learn passively, commented with questions after to plug in the gaps, was trying to continue learning, asked the minimum from others, etc.

I'm honestly shocked at the responses here.

markdewet I hope you still sick around and ask questions whenever you need to.
[Magisk] bigknowz:
Trying to mount system.img from Factory Image and no dice. Not a sparse file

file system.img

system.img: Linux rev 1.0 ext2 filesystem data, UUID=d119a127-f81b-5ba1-a572-e58cbdf5e014 (extents) (large files) (huge files)

simg2img returns:

Invalid sparse file format at header magic

Failed to read sparse file

Does that mean file OK to mount? If so, not working.

sudo mount -t ext4 -o loop system.img sys/

mount: sys/: mount failed: Operation not permitted.

thanks in advance.
[Magisk] majorfigjam:
What brand of phone are you trying to access?