Skip to content

Instantly share code, notes, and snippets.

@ngocdangrby
Created August 30, 2024 12:40
Show Gist options
  • Select an option

  • Save ngocdangrby/e9a515956207c94122615ad7d56126d8 to your computer and use it in GitHub Desktop.

Select an option

Save ngocdangrby/e9a515956207c94122615ad7d56126d8 to your computer and use it in GitHub Desktop.
Bypass Authy integrity with Rooted Android phone

It took me 3 days to pass the error The device does not meet the minimum integrity requirements.

Finally, I exported my Authy from my Android 14 phone on custom ROM.

  • Phone: Realme GT2
  • ROM: custom ROM PixelOS
  • State: Root already
  • Android: 14
  • Integrity: MEETS_DEVICE_INTEGRITY

Here are some steps for you:

  1. Replace Magisk with Kitsune Magisk: https://github.com/HuskyDG/magisk-files/releases/

  2. Install module PlayIntegrityFix: https://github.com/chiteroman/PlayIntegrityFix

  3. Install module MagiskHidePropsConf: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/releases

  4. Reboot

  5. Use https://github.com/TheFreeman193/PIFS to change finger print to pass MEETS_DEVICE_INTEGRITY

  6. Open Kitsune: enable Zygisk, MagiskHide

  7. Enable magisk hide for: com.google.android.gms, com.google.android.gms:unstable, Google Store

  8. Clear Google Store, Google Play Service data then reboot again

  9. Go to Google Store, install latest Authy. DONOT open it (make sure you install from google store, do not install apk)

  10. Go to Kitsune, enable magiskHide for Authy (deny list)

  11. Open Authy, login. ->> should login ok

  12. Use Agis to import from Authy

  13. Use Agis to export to QR HTML

refer: https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93

@pyxelo
Copy link

pyxelo commented Oct 4, 2025

KreAch3R's solution worked for me on LineageOS 22.2 on a Pixel 6a, but:

1. It wasn't clear from the instructions that Zygisk is a setting in Magisk, not a separate app.

2. [PlayIntegrityFix is gone](https://www.reddit.com/r/Magisk/comments/1l4ntfo/news_pif_has_been_discontinued/). I used [PlayIntegrityFork](https://github.com/osm0sis/PlayIntegrityFork) instead.

3. I used TrickyStore 1.3.0 instead of 1.2.1.

4. The link to Integrity Box is broken. It should be https://github.com/MeowDump/Integrity-Box, and I used v22.

Thanks for the help! Aegis successfully imported my passcodes from Authy and I'm never using Authy again.

Thank you very much for this, I tried the original post about a month ago and gave up in frustration, this got me to Device Integrity, which was enough to get Authy synced and then rip the codes out with Aegis. Thank you very much to everyone who worked on this.

When I try to install Integrity Box, it doesn't ask me to allow with volume up button, this is what i see (Downloaded the module from the @alexhenrie 's post) :

cc48d24519b77c119a927bba266a8fdc7f04fdec700646e515d903f57c4f08d7

after that, i reboot device, checked if its worked (it didn't).
And then cleared apps datas, rebooted again, run "Action" of Integrity Box Module again.
I repeated this several times and it still doesn't work. What am i doing wrong?

Device : Redmi Note 9 Pro (Stock ROM)

this is what i see when i run "Action" of the Integrity Box Module second time :
CleanShot 2025-10-04 at 16 41 46@2x

@alexhenrie
Copy link

I did not have to give Integrity Box any extra permissions. I just ran its action and it worked.

@codinggamer-dev
Copy link

codinggamer-dev commented Oct 9, 2025

On my Motorola Moto G10 with LineageOS 22.2 and rooted Magisk, nothing works.... All three Checks still fail. Iam using: (9th October 2025)

  • Magisk v29
  • Play Integrity Fork v14
  • Tricky Store v1.3.0
  • Integrity Box v23

I tried clearing, registering on googles website, playcurlNEXT, PlayIntegrityFix, ReZygisk, TrickyAddonModule, MagiskHidePropsConf, Shamiko, ZygiskNext and many more, but nothing ever work even for one check.... please help! i wanted to use LOS as my main phone/rom and i love google wallet and i need my banking app (DKB),....

KreAch3R's solution worked for me on LineageOS 22.2 on a Pixel 6a, but:

  1. It wasn't clear from the instructions that Zygisk is a setting in Magisk, not a separate app.
  2. PlayIntegrityFix is gone. I used PlayIntegrityFork instead.
  3. I used TrickyStore 1.3.0 instead of 1.2.1.
  4. The link to Integrity Box is broken. It should be https://github.com/MeowDump/Integrity-Box, and I used v22.

Thanks for the help! Aegis successfully imported my passcodes from Authy and I'm never using Authy again.

@alexhenrie
Copy link

Any workaround to make the device integrity check pass on Lineage is going to be fragile at best. Can you use Google Wallet and DKB from a web browser? My personal plan is to get a second phone if I absolutely have to use an app that insists on running on stock Android.

@codinggamer-dev
Copy link

I dont have any problem with reinstaling lineageos on my phone, because i just set it up. I need the DKB App because of when i buy something online i need to confirm with the app. also for wallet i want to pay contactless with my phone.... iam ready for everything!

Any workaround to make the device integrity check pass on Lineage is going to be fragile at best. Can you use Google Wallet and DKB from a web browser? My personal plan is to get a second phone if I absolutely have to use an app that insists on running on stock Android.

@KreAch3R
Copy link

Last time I tried it, you needed LOS (Android 15), and Magisk, PIF, Tricky Store, and Integrity box. Don't use anything else because in my case things clashed. You didn't mention that you enabled Zugisk in Magisk settings and then hid the app. Try my steps with the latest changes from @alexhenrie , don't install anything else on the device (a clean LOS install), do a reboot and play store / services clear data, and check if it works.
In some case, you might be inside the timeframe that one keybox becomes invalid and then a new integrity box will come out. Try to wait a couple of days to check if v24 or whatever will come out.

In my case, I found a lot of invalid keyboxes (inside integrity box or not) and that was messing up the tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment