AlfaX
Members
- Aug 12, 2024
- 17
- 5
[ro.product.system_ext.model]: [AOSP on ARM64]If xiaomi.eu were AOSP-based, then very likely we wouldn't wait for Xiaomi to release their ROMs...
I suppose this is a lie then... ¯\_(ツ)_/¯
[ro.product.system_ext.model]: [AOSP on ARM64]If xiaomi.eu were AOSP-based, then very likely we wouldn't wait for Xiaomi to release their ROMs...
It comes from Qualcomm/Xiaomi, we don't change it...[ro.product.system_ext.model]: [AOSP on ARM64]
I suppose this is a lie then...
Yes, but it's still based on AOSP. Am I not right?It comes from Qualcomm, we don't change it...
View attachment 53741
I didn't say it was open source, I said it is based on AOSP which is true, you even said it yourself. I didn't say it was AOSP without any modifications obviouslyYes, you are not right. Everything regarding MIUI/HyperOS base is closed source, we don't have any access to Xiaomi sources. Even if system_ext is based on AOSP, there are still many changes on Xiaomi's side (and it's not necessarily to be purely AOSP, Qualcomm also modifies AOSP code).
Your comment makes no sense. Since trickystore works just fine on stock and it seems that XEU way of injecting a fingerprint is what messes up the usage of keyboxes. So you choose to endorse illegal use of fingerprint and condone the use of keyboxes? Kind of hypocritical.Nope, patching engineGetCertificateChain is required and I'm not about to add "persist.sys.pixelprops.pi", this prop has nothing to do with our ROM.
Also, the fact that you said "if source built" means you don't even know that MIUI/HyperOS-based ROMs are not built from source (it doesn't publicly exist).
I'll reiterate what I said: We provide the ROMs as-is, if you're trying to use a pirated keybox to pass Strong Integrity, have fun, we don't endorse it and definitely don't provide support for it. Adding that prop will imply that we endorse illegal usage of leaked keyboxes.
Yes, your ignorance is the reason you don't differentiate between these two things.Your comment makes no sense. Since trickystore works just fine on stock and it seems that XEU way of injecting a fingerprint is what messes up the usage of keyboxes. So you choose to endorse illegal use of fingerprint and condone the use of keyboxes? Kind of hypocritical.
Using a leaked keybox from one phone on another can be considered a form of piracy or unauthorized access. The keybox contains cryptographic keys that are intended to secure a device's data and operations, and using it without proper authorization could be illegal. It can violate intellectual property laws and the terms of service or end-user license agreements set by the device manufacturer.
If you're exploring this topic for legitimate reasons, like security research, it's important to follow the proper legal channels, such as working under a responsible disclosure agreement or in a controlled, lawful environment.
Thank you for the lesson, I understand the difference just fine. No one's asking you to include leaked keyboxes in your build, just so it works the same way as in stock ROM. After that it's up to users to do as they please and no concern of yours.Yes, your ignorance is the reason you don't differentiate between these two things.
That was always my point. For example, I was against adding the inject inside the ROM, but XEU did that, breaking some other stuff in the process even if you never use it and disable/delete it.But maybe a middle ground is to just let the users decide what works?
Yeah saw the other thread too and the props change does seem sketchy - what if G turns around and start blocking that prop. Might just become another rabbit hole from there. Totally see XEU's point - seems good thinking.
But maybe a middle ground is to just let the users decide what works? I mean with the dev branch being discontinued some users might be left strangled with the current non-stock way of removing DG's access. If G suddenly decides to push an update to GMS tomorrow removing passing device altogether it kinda would be extremely unfortunate for normal XEU users. Not a very professional opinion but just my two cents.
Our only priority is unrooted users. If you're rooted, you can patch out anything you want and make a module out of it.That was always my point. For example, I was against adding the inject inside the ROM, but XEU did that, breaking some other stuff in the process even if you never use it and disable/delete it.
It's not only Google Wallet, there are many apps that requires Play Integrity, even ChatGPT for some reason.Our only priority is unrooted users. If you're rooted, you can patch out anything you want and make a module out of it.
Any "solution" you can think of will eventually be blocked. That's why I was always against including ANY kind of workaround in the ROMs.
Oh, and if that would have affected the "popularity" of the ROM, I personally would not care, not trying to be a celebrity.
My solution to Google Pay not working has always been not using Google Pay. I can live with a card, I don't see the problem with that.
This guy already pointed out where the incompatibility with Tricky Store happens.It's not only Google Wallet, there are many apps that requires Play Integrity, even ChatGPT for some reason.
If we're rooted, sure we can patch it and make a module, but we at least need to know where the problem comes from. FP is not an issue because it's included in the app (current one is for sailfish, just need to extract the apk to get the XML so no issue there). Now what's the issue? It's not a question of owing anything to rooted users, as you said, you don't owe us anything. It's a question of kindness.
Imagine being a stranger in a city for vacations and you're lost, you want to ask someone for directions but they reply to you "If you're here for your vacations I expect you to know where you're going" and go away, would you like this? They don't owe you to give directions but they sure can be kind and give you directions. If you're not being kind, you're being rude, which is exactly what you are to root users.
I hope you can understand that and that you don't treat strangers that asks for directions the same way you treat root users.
Thank you! This makes total sense. Actually I used to be an unrooted XEU user who only got on here because of the niceties that come with having things debloated while still being able to use my bank (which detects root sadly). However, the apps started crashing like crazy since three months ago because of the whole debacle with this play integrity. From stuff I read on xda and what the google engineers are saying on twitter, it seemed this will only get worse. Could we not please just fully rid ourselves of the half-working workarounds like how it used to be?Our only priority is unrooted users. If you're rooted, you can patch out anything you want and make a module out of it.
Any "solution" you can think of will eventually be blocked. That's why I was always against including ANY kind of workaround in the ROMs.
Oh, and if that would have affected the "popularity" of the ROM, I personally would not care, not trying to be a celebrity.
My solution to Google Pay not working has always been not using Google Pay. I can live with a card, I don't see the problem with that.
I just hope the devs do it before EOL of my device or I'll be stuck with a broken Play Integrity without a way of fixing it myself because of the way XEU has implemented a workaround. With the only option of switching to other ROM of course. If they don't want to mess with PI, keyboxes and Google, that's completely fine by me. I even welcome this, I'd rather have a clean ROM instead of having to disable inject after install. My only hope is they don't break what's not broken.please just fully rid ourselves of the half-working workarounds like how it used to be?
I would normally say thanks but not this time.This guy already pointed out where the incompatibility with Tricky Store happens.
![]()
Future of Pixel Integrity (Google Pay, RCS chat, bank apps, etc.) and potential adaptations for the EU ROM
As we all know, Google's SafetyNet Team have been disabling the ability to fallback to device integrity for a range of devices recently. They promise to continue this trend until they completely phase out non hardware-backed attestation as per Shawn (@shawnwillden on X) which can happen as early...xiaomi.eu
You don't represent the majority of our users who are not interested in messing with root.I just hope the devs do it before EOL of my device or I'll be stuck with a broken Play Integrity without a way of fixing it myself because of the way XEU has implemented a workaround. With the only option of switching to other ROM of course. If they don't want to mess with PI, keyboxes and Google, that's completely fine by me. I even welcome this, I'd rather have a clean ROM instead of having to disable inject after install. My only hope is they don't break what's not broken.
Oh no, that makes me so so sad.I would normally say thanks but not this time.
Yes, a clean start for me to modify ^^"I'd rather have a clean ROM", but you still root? That makes no sense.
... Womp wompOh no, that makes me so so sad.
Unfortunately, your link does not have much to do with the topic discussed here.If it can help someone https://droidwin.com/how-to-pass-strong-integrity-on-unlocked-bootloader-root/
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation