Installing Magisk and Play Integrity Fix


I am done chasing integrity fix solutions.... All the solutions here doesn't work anymore.

I give up...
I have rooted to my 13Pro to flash xiaomi.eu Roms mainly....
Going to make some effort to flash back to stock rom and lock the bootloader.
Try Curve first. You can pay contactless, just hide root in magisk and you're good to go. No more fighting with Google.
Don't have Curve? You can sign up here (aff link)
 
Try Curve first. You can pay contactless, just hide root in magisk and you're good to go. No more fighting with Google.
Don't have Curve? You can sign up here (aff link)
Do you know if curve works like gpay? So you can make contactless payments directly just by unlocking your phone without first starting the curve app? At the moment I use the PayPal app to pay, but the app always has to be started first.
 
Do you know if curve works like gpay? So you can make contactless payments directly just by unlocking your phone without first starting the curve app? At the moment I use the PayPal app to pay, but the app always has to be started first.
All you need to do is unlock your phone with your fingerprint. You don't need to launch the app, just set Curve Pay as your default payment method in the NFC settings.
 
  • Like
Reactions: Smaritz
Somebody have find solution for strong Integrity ?
I don't think there will be a long term solution again. Google is screwing up a lot of things. It's so strange how they decide to change or disable useful features.

Especially the most recent changes to Google photos. Off topic so not discussing that though.
 
Dear Devs, this might be a stupid question from a dev perspective, but is it possible to include keybox.xml loader option just like infinityx or YAAP rom to pass the integrity? and thanks for this great project
 
Sadly, I forced to unroot and reverted back to stock.

Had used the APatch method, it works, but unstable, changes to it or its module caused bootloops and after multiple reset and retries, I gave up....thanks guys.
 
  • Like
Reactions: Smaritz
Sadly, I forced to unroot and reverted back to stock.

Had used the APatch method, it works, but unstable, changes to it or its module caused bootloops and after multiple reset and retries, I gave up....thanks guys.
try with sukisu
 
Sadly, I forced to unroot and reverted back to stock.

Had used the APatch method, it works, but unstable, changes to it or its module caused bootloops and after multiple reset and retries, I gave up....thanks guys.
No issues here on Apatch and Miro. Probably skill issues.
 
Hi, some has Google wallet working?

I have kernelSU, and modules, strong integrity OK, banking app is working.
But Google wallet still say that my phone is rooted.
I haven't installed susfr for now.
Any clue? APatch is better?
 
Hi, some has Google wallet working?

I have kernelSU, and modules, strong integrity OK, banking app is working.
But Google wallet still say that my phone is rooted.
I haven't installed susfr for now.
Any clue? APatch is better?
nothing works
 
Hi, some has Google wallet working?

I have kernelSU, and modules, strong integrity OK, banking app is working.
But Google wallet still say that my phone is rooted.
I haven't installed susfr for now.
Any clue? APatch is better?
If key attestation demo and play integrity shows all good. Give it a day or two without tinkering the PIF thing again. Also try update FIDO and IFAA cert.
 
For avoiding "losing root" when updating: You can just "exclude" the boot.img from the update package by renaming it, then your modified partition won't be overwritten during the update, meaning, you won't need to setup root/modules all over again.
 
For avoiding "losing root" when updating: You can just "exclude" the boot.img from the update package by renaming it, then your modified partition won't be overwritten during the update, meaning, you won't need to setup root/modules all over again.
It may result in boot-loop if the old boot.img is not compatible with the upgraded ROM

So, as I described above (for APatch, but same for Magisk):

Before upgrading:
- unzip to copy out the boot.img
- patch that new boot.img

Then either:
- replace the original boot.img with the patched one (keeping the name boot.img), and flash that from Fastboot (using the appropriate script)

Or:
- Flash the original upgrade but disable automatic rebooting by the end in the script,
flash that patched boot img and then reboot to the system

Once you reboot, you will have upgraded ROM and the root with the previous modules (there might be only a problem with specific LSPosed modules if they patch Framework - they would have to be reinstalled to patch the new Framework)
 
  • Like
Reactions: ciubex