V1.04 -> New Features!

1) You can now set your own check interval by specifying the number of minutes inside the file: /data/adb/modules/playcurlNEXT/minutes.txt (minimum 1 minute, maximum 1400 minutes).

2) You can now set whether you want to use a random beta FP from the last month (since multiple are available) or the latest one.
- Follow these steps to configure:
a) Open the file: /data/adb/modules/playcurlNEXT/mode.txt
b) Write random in the file if you want to use a random FP.
c) Write normal or leave the file empty if you want to use the latest one.

Version 1.04 comes with these default values:
- check interval -> every hour
- mode -> normal (latest FP)

If you are okay with these values, do not edit anything.

Hello everyone, from the Citra Integrity Trick chat, I have learned that Osmosis claims that TSUPPORT, Citadvance, and PlaycurlNEXT have taken his code without giving proper credit.

I wrote to him so we can clarify -> https://github.com/osm0sis/PlayIntegrityFork/commit/565d895a968ebb01a261548f9355878ed63a9105

The issue has been clarified and solved!

Google banned the pixel beta fps, I'll see what to do know, sadly I'm at work rn, I'll look when finished.

All fingerprints are banned, I can confirm that PIF is dead.

I have an idea to create a workaround but I will need to investigate further.

Chiteroman did it again😍

Since the fp got banned due to the expiration....

Just a reminder for all, that repo always contains the latest pif

https://github.com/daboynb/autojson

PlaycurlNEXT is still working fine 😉

https://github.com/daboynb/playcurlNEXT

Since some people are encountering problems, I decided to take a deeper look.

A lot of keyboxes are not revoked but won't let you pass strong, so all the bots that compare the serial against the Google revocation list will tell you that it is OK, but it's not.

It's not really clear what Google is doing, since some keyboxes let you pass Strong and others don't.

My guess is that they stopped revoking them; instead, they stop you from getting strong if certain criteria are met.

I'll update this post if I get more info about that issue.

UPDATE:

The banned serial is "6e918661b760821ec0d47876b3f1c241."
If I find other serials, I'll post them here so the bot can crawl them too.
Thanks to @antezero for the support!

FIXED!!
Thanks to osmosis !

Google changed something and the script to pull the beta fp is now broken, I'll fix ASAP.

For those who are unable to pass new checks with a valid keybox:

https://t.me/playfixnext/77526/117629

There's a bug that stops you passing strong
https://github.com/chiteroman/PlayIntegrityFix/issues/529
after requesting integrity two times.

Thanks to @kowx712

*NOT related to play integrity.*

https://github.com/daboynb/Safetycore-placeholder

Many people are concerned about the Safetycore app.

I created a placeholder app to address that issue.

- Uninstall the app from the Play Store: https://play.google.com/store/apps/details?id=com.google.android.safetycore.
- Download the APK from this repository.
- Install it.

Enjoy!

When Google attempts to replace the APK with the updated Safetycore app, it will fail due to a signature mismatch.

An user told me that chiteroman changed again some Pif values....

So if you have updated Pif Playcurl won't work.

I'll fix playcurl asap

Hi, the new version 1.14 should have fixed the issues.

Now, instead of using the autojson repo, the script uses acion.sh from the pif module.

If you encounter a bug please open an issue on my github so I can fix it.

Thank you.

The bot is currently offline because, for some reason, my VPS payment wasn't renewed.

Tomorrow I'll be at home and I'll fix that issue, thanks for your patience.

The issue with the bot is FIXED.

Hi everyone, the bot might be down for a few minutes because I’m migrating it to a new infrastructure. The SSD on my Raspberry Pi died, but thanks to a generous donation from @antezero I was able to buy a VPS!

The bot will be back online soon.
I also want to thank everyone who has donated so far, there have been many of you, and I’m really grateful for your support with the development and the resources needed to keep the bot running.