Closed Uj947nXmRqV2nRaWshKtHzTvckUUpD closed 1 month ago
nift4
commented
1 month ago 
Uj947nXmRqV2nRaWshKtHzTvckUUpD
commented
1 month ago thank you for taking time to reply. i liked how it previously was installing microg for me so that i don't have to do it manually. why do i have to install microg before now?.. it doesn't have too much sense. the project itself is literallly called "microg installer". Not to mention that i faced big issues installing microg because was conflicting with gsf no matter what i tried (uninstalling everything in various methods), so i had to revert to v3.4.4.0 to let this module install it. I described here the whole thing i had to do especially that latest microg has location bug: https://github.com/microg/GmsCore/issues/2575
nift4
commented
1 month ago why do i have to install microg before now?
A lot of people shot themselves in the foot by using Play Integrity Fix, Universal SafetyNet Fix, Shamiko, Magisk Hide, Magisk DenyList or KernelSU unmount modules applied to microG, which will cause Magisk to undo all modifications from microG's point of view. Which means, microG won't be able to see it's own APK and will crash because it can't load it's own data. A workaround for this is to also have it installed as user app (which means it'll be an updated system app) because the APK on /data will remain visible, and hence it will find it's data and not crash.
However, I can't automate that because when updating microG, Magisk Manager will be force stopped because it declares a dependency on GMS SSL modules and Android system will restart all dependant apps of an updating app. This means during module installation, Magisk Manager will appear to be crashing, which has confused a lot of people.
The only viable solution is to install the microG APK either before or after the module install. I used to go with latter solution telling people to install the same APK again manually to fix the crashes, but I got very very large amounts of emails and issues due to people not reading the instructions carefully.
Hence, I went with the last route, having people install the APK before installing the module.
Another advantage of this is that incomplete/impromper debloats will stop with APK installation failure instead of random microG crashes, which is a lot better user experience (who likes unexplainable crashes because they used a debloater which doesn't debloat in a sufficient way? It's not intuitive, and again, has caused lots of people to contact me and ask for help).
The error message you posted: "redeclare permission com.google.android.googleapps.permission.GOOGLE_AUTH.writely com.google.android.gsf" also means you failed to uninstall it properly. You need to delete the APK files of GmsCore, GoogleServicesFramework and Play Store from the file system and make sure to install the app in all of Android's user (multi-user, parallel space and work) profiles, then that should go away.
Uj947nXmRqV2nRaWshKtHzTvckUUpD
commented
1 month ago how can i delete those original apks for gms/gsf/vending ? i already found them on storage, but since a while ago (afaik) you cannot remount as rw. Below the original paths i found:
// google services framework = com.google.android.gsf ~~~ microG Services Framework Proxy /mnt/vendor/my_heytap/non_overlay/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk /my_heytap/non_overlay/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
// google play services = com.google.android.gms ~~~ MicroG Services /mnt/vendor/my_heytap/priv-app/GmsCore/GmsCore.apk /my_heytap/priv-app/GmsCore/GmsCore.apk /product/priv-app/GmsCore/GmsCore.apk
// google play store = com.android.vending ~~~ microG Companion (fakeStore) /mnt/vendor/my_heytap/priv-app/Phonesky/Phonesky.apk /my_heytap/priv-app/Phonesky/Phonesky.apk
In the past i was using de-bloater app together with its magisk module to systemlessly remove them and with this trick i was able to install microg through microg installer revived, but for some reason i cannot do this anymore, i think something messed up at some point.
I am on android 12 on oneplus 7t pro.
nift4
commented
1 month ago This is the job of gms_delete.zip, I adapted it for your OnePlus system, please let me know if it works: gms_delete.zip
Uj947nXmRqV2nRaWshKtHzTvckUUpD
commented
1 month ago ok i looked into the new version of gms_delete code (customize.sh) and it finally makes sense for me what it tries to accomplish and how v4.1 is supposed to work. However, for my particular case on OnePlus, gsf resides on a different path as i described above: /my_heytap/non_overlay/priv-app/GoogleServicesFramework ~/GoogleServicesFramework.apk~ instead of /my_heytap/priv-app/GoogleServicesFramework
I tried your gms_delete.zip but didn't work, throwing the same duplicate/permission error. So i think my paths should be added to the .sh script.
LE: tried to craft the zip with this change (tried both folder and full path to apk), but the apk is still in place in that path
nift4
commented
1 month ago So something like this doesn't work either? gms_delete.zip
Uj947nXmRqV2nRaWshKtHzTvckUUpD
commented
1 month ago So something like this doesn't work either? gms_delete.zip
Not working. I tried the same, and also with the path to the apk file. The gsf apk is still there after reboot. Btw i am on latest magisk v28 (updated yesterday). Maybe there's a bug with this one
nift4
commented
1 month ago Are the other APKs gone as intended?
Uj947nXmRqV2nRaWshKtHzTvckUUpD
commented
1 month ago /my_heytap/priv-app/GmsCore/GmsCore.apk /my_heytap/priv-app/Phonesky/Phonesky.apk are also still there, so the module gms_delete doesn't seem to take any effect in my case
Uj947nXmRqV2nRaWshKtHzTvckUUpD
commented
1 month ago i updated the other issue. tldr: it turned out that the problem was the latest version of microg installer revived 4.1. i had to revert to 4.0.2 to make microg and location work again in apps such as uber
what's the point of having to install microg manually before this module, if the whole purpose of this module was to assist microg installation in the first place?
why would this module be needed anymore?