diff --git a/README.md b/README.md
index bf777bf..09aa01b 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,5 @@
-# Play Integrity Fix
+# Play Integrity Fork
+*PIF forked to bring back the custom.pif.json restore feature and develop more methodically*
 
 A Zygisk module which fixes "ctsProfileMatch" (SafetyNet) and "MEETS_DEVICE_INTEGRITY" (Play Integrity).
 
@@ -7,32 +8,26 @@ To use this module you must have one of the following:
 - Magisk with Zygisk enabled.
 - KernelSU with [ZygiskNext](https://github.com/Dr-TSNG/ZygiskNext) module installed.
 
-[**Download the latest here**](https://github.com/chiteroman/PlayIntegrityFix/releases/latest).
-
-## Telegram group
-
-https://t.me/playintegrityfix
-
-## Donations
-
-- [PayPal](https://paypal.me/chiteroman)
-
-## Official posts
-
-- [XDA](https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/)
-
 ## About module
 
 It injects a classes.dex file to modify a few fields in the android.os.Build class. Also, it creates a hook in the native code to modify system properties. These are spoofed only to Google Play Services' DroidGuard (SafetyNet/Play Integrity) service.
 
-The purpose of the module is to avoid a hardware attestation.
+The purpose of the module is to avoid hardware attestation.
 
 ## About 'custom.pif.json' file
 
-You can create this file in the module directory to spoof custom values to the GMS unstable process. It will be used instead of the included pif.json.
+You can create this file in the module directory to spoof custom values to the GMS unstable process. It will be used instead of any included pif.json.
 
 You can't use values from recent devices due them triggering hardware backed attestation.
 
+<details>
+<summary>Resources</summary>
+
+- [How-To Guide - Info to help find build.prop files, then create and use a custom.pif.json](https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89189572)
+- [gen_pif_custom.sh - Script to generate a custom.pif.json from device dump build.prop files](https://xdaforums.com/t/tools-zips-scripts-osm0sis-odds-and-ends-multiple-devices-platforms.2239421/post-89173470)
+
+</details>
+
 ## Troubleshooting
 
 ### Failing BASIC verdict
@@ -59,14 +54,6 @@ Follow these steps:
 - Clear Google Play Services (com.google.android.gms) cache and data (Optionally skip clearing data and wait some time, ~24h, for it to resolve on its own)
 - Reboot
 
-<details>
-<summary>Guide</summary>
-
-![Google services cache](./wallet-troubleshoot-1.jpg)
-![Removing all data](./wallet-troubleshoot-2.jpg)
-
-</details>
-
 ### Read module logs
 
 You can read module logs using this command directly after boot:
diff --git a/wallet-troubleshoot-1.jpg b/wallet-troubleshoot-1.jpg
deleted file mode 100644
index 416fab7..0000000
Binary files a/wallet-troubleshoot-1.jpg and /dev/null differ
diff --git a/wallet-troubleshoot-2.jpg b/wallet-troubleshoot-2.jpg
deleted file mode 100644
index ff0f671..0000000
Binary files a/wallet-troubleshoot-2.jpg and /dev/null differ