Google Photos: Can’t load this photo for editing Please try again later
In this guide, we will show you the steps to fix the ‘Can’t load this photo for editing Please try again later’ error in the Google Photos app. This is not your everyday gallery app. Apart from the ability to upload media files to the cloud, it holds a slew of intriguing features. And over the past few months or so, it has been blessed with some nifty editing and AI features as well.
These include the likes of Magic Eraser and Portrait Light, Cinematic Photos, and tons of AI edits. However, a bunch of users have voiced their concern that they are getting the aforementioned error when trying to access an editing feature in the Google Photos app. So why is this happening, and more importantly, how can you fix it? Let’s find out.
- Reason for Google Photos ‘Can’t load this photo for editing Please try again later’
- How To Fix This Issue? Via Magisk Denylist Via Hide My AppList
Reason for Google Photos ‘Can’t load this photo for editing Please try again later’
The reason for this issue can be said in one single word- root. Yes, you’re getting the ‘Can’t load this photo for editing. Please try again later’ error message in Google Photos because your device is rooted. So first off, the banking and payment apps had to face the wrath of root, which was then followed by the likes of Uber and McDonald’s, and now the gallery app from the Silicon Valley giant has made its way to this list. So this now begs the all-important question- how to fix this problem? Let’s find out.
How To Fix This Issue?
We have listed two methods below that will help you get this job done. Go through both of them below and then try out the one that is in sync with your requirements. So with that in mind, let’s get started.
Via Magisk Denylist
Benefits: This is the shorter and easier of the two methods.
Drawback: It has a lower success rate than the other method.
- First off, enable Zygisk in Maigsk or flash Zygisk Next in KernelSU or APatch.
- Then configure the DenyList by adding all components of the Google Photos app to the DenyList.
- This forces Zygisk to prevent the Magisk environment from loading into the Photos process.
- So add the following Package Name: com.google.android.apps.photos
- After applying the DenyList, the Google Photos app needs to re-verify device status.
- So head over to Settings > Apps > Google Photos.
- Go to its Storage & cache section and tap on Delete Data. Deleting the data of Google Photos will not delete your photos and videos; they are either backed up to the cloud or saved in the Internal Storage
- Finally, restart your device and check out the result.
Via Hide My AppList
Benefit: Comes with a much higher success rate than its counterpart.
Drawback: It is a lengthy and complicated method than the first one.
- First off, launch the Magisk app > go to Settings > Hide the Magisk app.
- Now go to Configure Denylist and enable the toggle next to these apps Google Play Services Google Play Store Google Services Framework Google Photos
- Now create a blacklist using Hide My Applist and apply it to Google Photos.
- Then pass at least the Device Integrity , though the Strong will be the best.
- Also, create a custom.pif.json file .
- Now delete the data of Google Play Service, Google Play Store, Google Service Framework, and Google Photos.
- Finally, restart your device and check out the result. If it’s still not working, then proceed with the below steps.
- Now go to the below location and open the target.txt file: data/adb/tricky_store/target.txt
- Then add its app package name [com.google.android.apps.photos] in that text file and save it.
- Again delete the data of Google Play Service, Google Play Store, Google Service Framework, and Google Photos.
- After that, spoof your device’s bootloader status to Locked . Finally, restart your device and check out the result.
- How to Enable ‘Backup New Folders’ in Google Photos
- Hide Memes, Screenshots, GIFs from Google Photos!
- How to Add Google Photos to the Samsung Camera App
- How to Enable Photos Stack in Google Photos
(Cancel Reply)
Δ
How to Get Fingerprint PIF.JSON File using Play Integrity Fork
In this guide, we will show you the steps to get the fingerprint PIF.JSON file using Play Integrity Fork. A week back or so, we got the unfortunate news that the Play Integrity Fix module has been discontinued by the developer chiteroman. We can’t thank him enough for the invaluable work he has done for this community. But going forward, what can be our next course of action?
Well, while this module was up and running, another developer [osm0sis] was also running a fork of this module, which goes by the name Play Integrity Fork. While we wouldn’t say that it was under the shadow of Fix, but it wasn’t being used that much when compared to its counterpart.
However, all that is about to change now, and so there are a few queries that might pop up in your minds. In this regard, one of the most common questions that I have been asked for the past week is how to get the fingerprint PIF.JSON file in the Play Integrity Fork module.
As you might already be aware, the Fix module already has this embedded in its module; you just need to launch it via KSUWebUI, hit the Fetch PIF.JSON option, and you’ll get the file. But that’s not possible via the Fork module via the direct route. Why? Let’s find out, and after that, we will list the plausible steps through which you can get this file using this module. Follow along.
- Why is the PIF JSON Fingerprint File Missing in Play Integrity Fork
- How to Get the Fingerprint PIF.JSON File using Play Integrity Fork
- Direct Download PIF JSON Files
Why is the PIF JSON Fingerprint File Missing in Play Integrity Fork
By default, the module comes with a template of a PIF JSON file that you need to fill in manually. You can get this file from /data/adb/modules/playintegrityfix. Once you fill in the values, simply rename it to custom.pif.json, and your task stands complete. But why hasn’t the dev simply added this file, as was the case with the Fix module? Here’s what he has to say regarding this:
There’s intentionally no pif.json in the module because the goal remains to be futureproof, and including something that may be banned and obsolete within days would be contrary to that goal.
However, finding these files might not be everyone’s cup of tea. Not only are a few of these remains, but finding them is also quite an effort taking task. The developer acknowledges this, and hence, he has added a script to extract the latest Pixel Beta fingerprint along with the module. The script is named autopif2, which generates a random device fingerprint from the latest Pixel Beta. So let’s have a look at the steps to make full use of this file.
How to Get the Fingerprint PIF.JSON File using Play Integrity Fork
Before starting, please take a backup of all the data on your device, just to be on the safe side. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device, and data by performing the below steps.
NOTE: There are quite a few ways of getting this job done, however, I personally found Termux to be the easiest among all of them. But if you want to try out any other method, then run the generation script from a root manager app that supports the module Action button or from a file explorer app that supports script execution.
- To begin with, flash the wget2 module via Magisk / KernelSU / APatch .
- Then, flash the Play Integrity Fork CI module from GitHub Actions .
- Now, download and install the Termux app from F-Droid.
- Then launch it and execute the following three commands: su //you’ll get a SU request, hit Grant cd /data/adb/modules/playintegrityfix //to change the directory to the module’s sh autopif2.sh –preview // this will give you the fingerprint file
- You can also add a few other parameters to the above command, namely: su -c sh /data/adb/modules/playintegrityfix/autopif2.sh -a -m -p -s -a Advanced -m Match -p Preview -s Strong
- Once done, head over to the below location to access the custom.pif.json /data/adb/modules/playintegrityfix
Direct Download PIF JSON Files
If you don’t want to manually carry out the aforementioned steps, then you may directly get the PIF JSON file from our below guide:
Download PIF JSON File from Here
- How to Pass Strong Integrity Using Revoked/Banned Keybox File!
- How to Pass Play Integrity in New Android 13+ Checks
- Guide to Pass Strong Integrity on Unlocked Bootloader & Root!
- How to Spoof/Fake/Hide Bootloader Unlock Status
- How to Pass Play Integrity Test on any Custom ROM [Video]
- Drw 6 months ago Reply Problem solved. Termux wasn’t prompting me to grant su user access. Found where to enable it in the KSU Next GUI under Superuser.
- Drw 6 months ago Reply I’m getting “su program not found.” Rooted with ksu and susfs. Modules installed are BKI, Play integrity fork, shamiko, susfs for ksu, tricky store, wget2, zygisk lsposed, and zygisk next. Nothing tweaked.
- mario 7 months ago Reply sorry, what do you mean with “Then, flash the Play Integrity Fork CI module from GitHub Actions.” ? i have pif v13 flashed in magisk
- Mohamed 7 months ago Reply Hi, can you please help me with a vaild keybox pleaaase 🙏
- Antonis 7 months ago Reply 1) “Then, flash the Play Integrity Fork CI module from GitHub Actions” https://github.com/osm0sis/PlayIntegrityFork/actions what do i download? 2) and then what do i do with custom.pif.json ?
- Antonis 7 months ago Reply “Then, flash the Play Integrity Fork CI module from GitHub Actions” https://github.com/osm0sis/PlayIntegrityFork/actions what do i download?
(Cancel Reply)
Δ
