Kernel for AOSP /A11/12/13/14/15

Before flashing any kernel always take dtbo and boot img backups from recovery

Kernel for MIUI/HOS1/HOS2/A11/12/13/14/15

Before flashing any kernel always take dtbo and boot img backups from recovery

By @Tobrut_Eksotis

RIP legacy checks in Play Integrity API 🕊️

Now Device verdict is like old Strong.

A lot of people have questions that I'm going to try to clarify here:

- Google already warned about this, and you all should have been prepared.
- No, you can't create your own keybox, so stop sending weird noscripts in the chat because none of them will work for you. All keyboxes are created by Google (as they are the only ones with the private key to generate them) and distributed to the various OEMs.
- PlayIntegrityFix is 50% "obsolete"; it's still "working," but it needs another workaround to get the Device verdict (e.g., TrickyStore).
- No, I'm not going to share any keyboxes. There are already many channels dedicated to this, and all they'll accomplish is getting all those keyboxes revoked. Then come the regrets...

I'm not sure whether to continue with the module... Google keeps putting up more and more obstacles, and it's quite exhausting having to search for solutions that will end up being useless in a few months... 😭

Is there any 100% effective and permanent method? Yes, by installing the stock ROM and locking the bootloader.

All the keyboxes you're going to find on Telegram channels will be used by hundreds of users and will eventually be revoked within a few weeks...

Another alternative is to spoof the SDK_INT value in the Play Store process and force a legacy attestation; I implemented this back in the day in PIF, and it wasn't usually very stable... For some, the Play Store would crash; others would get logged out... PlayIntegrityFork still has it.

From what I understand, those with Android 12 or lower are not affected by this change, but I haven't been able to confirm it myself yet.

I'll repeat it as many times as necessary: most users want a simple, one-click solution. When you unlock your device's bootloader, you know what you're getting into. If you don't want to spend hours digging through forums and learning, then it's best not to do it.
I think we all agree that what Google does is unfair, but it is what it is.

RIP Play integrity and custom ROM🫡

The End Of The STRIX Chronicles

ReSTRIX 20250512 EOL For MIUI (KSUN only)
STRIX-Revived 20250520 EOL For AOSP (NoSU only)

Changelogs:
ReSRTIX-MIUI: Fixed the heating issues (if I remember correctly) of the previously leaked 20250510 build and other changes I forgot
STRIX-Revived-AOSP: Same as 20250323 but with the new bpf changes to boot A16 QPR1.

I am done with STRIX base now and I don't wanna mess with it anymore. I'd like to move on and do something I'd wanted to do for a long time. ReSTRIX is a failed experiment to me and is not what I wanted to do.
I don't care about the fate of STRIX now.

Stay tuned for whatever next now

By:- @vbajs

For my opinion strix better , 120hz more stable

Android 16🔥😃 So Many Changes After Android 12

https://x.com/GrapheneOS/status/1925716345892528401

Based.