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

@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.

@DooM3P
Copy link

DooM3P commented Dec 3, 2025

I did follow all @KreAch3R steps and @alexhenrie. Worked flawlessly. Just had to do this at the end, as advised :

to clear Google Playstore, Google Play Services, Google Play Framework data, reboot, then run the "Action" of the Integrity Box module again.

Then it switched from red checks everywhere to three green checks. Strong integrity

Used latest available software : Magisk v30.6, Integrity-Box V27, Play Integrity Fork v15, TrickyStore 1.4.1. Note that ZygiskNext isn't needed seems to be included in this Magisk version.

I was on an old Oneplus 6 (A6003) flashed with MSMdownloadtools to stock OOS 10 (basically whatever dodgy stuff I could find on XDA since Oneplus doesnt provide anything 100% official), then patched with builtin OOS update soft.

It was still invalid for Authy and google play (device integrity problem, basic integrity ok.. in spite of full stock ๐Ÿ˜  ) I then switched to latest lineage os 22.22 as advised and then followed instructions above.

Don't forget to flame Authy on play store or anywhere else on your way out once you are rid of that plague ๐Ÿ‘

Congrats to all, you are heroes ๐Ÿ’ช ๐Ÿ‡ฎ๐Ÿ‡ณ ๐Ÿ‡ฌ๐Ÿ‡ท ๐Ÿซก ๐Ÿ‡บ๐Ÿ‡ธ

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