Disclaimer
This content is from my own experience. You can’t blame me if your device is catching fire or the FBI is knocking on your door.
Tested OK with at least two devices, Android 12+ & /e/OS 2.x.
Problem
App installed or updated with a third-party store app (such as AppLounge) may not start, with a message like this one (will vary depending on app):
English : “Access to the application is impossible. Uninstall and reinstall your application from Google Play to solve the problem.”
In this case, app was updated using Aurora Store:
What we need to get around
- a build allowing ADB root
- package file(s) for the app, I got it from Aurora Store but you may also get it from less secure sources
Ready to rumble
First, stop & kill the app.
Then connect using ADB, enable root:
Find your package installation file, or bundle:
Note: you may have a single .apk file, I have a .zip file because it’s a bundle
You won’t be able to run install actions from this place, file(s) are to be moved elsewhere!
Easy peasy:
Here, I:
- got location for an install-enabled directory, changed to it
- created a dedicated directory for my operations, moved there
- unzipped my installation bundle
Note: if you have a single .apk file, you may usecp
instead
Now the fun part!
We just have to overwrite the existing installation, faking the Store .
Here comes package manager very handy!
What happened here? Nothing fancy really: we re-installed all the package, as it was installed from “com.android.vending” <= this is the Google Play store app codename!
Enjoy yourself
Fun fact: Google Play Store name has been “hacked” by microG… It’s kind of expected
Afterthoughts
Cleanup your room:
If you use Aurora Store, blacklist the app from updates ( you will have to update it manually!).
Otherwise, you will get into the same trouble with every update… But now, you know how to deal with!
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services