nift4 / microg_installer_revived

Install microG GmsCore, GsfProxy, FakeStore (or Play Store if you want so) and MapsV1 to /system/
GNU General Public License v3.0
782 stars 43 forks source link

Install process crash when install microg update #72

Closed DeepBlueBubble closed 1 month ago

DeepBlueBubble commented 1 year ago

When install new version from Magisk, or manually install new version of GMS core App. All rhe install process, the Magisk, the package installation, will crash. This happened all my 3 devices (A12L-A13) with Microg installed, across three different microg revived installer versions (because.I am only using microg 3-4 versions ago).

urgali commented 1 year ago

It goes on but with invalido apk errore

You can find screen attached, will try to get more useful logs as soon as I get to a pc Screenshot_20230414-133006_Magisk

nift4 commented 1 year ago

https://github.com/nift4/microg_installer_revived/releases/download/v3.2.0-0-test1/microG_Installer_Revived-t4.zip

urgali commented 1 year ago

All seems good now! Only thing is that it is not installing play store even if it says that it had success finding it in adb data

nift4 commented 1 year ago

you mean there is no "Success" message? don't worry, that's normal. I'm releasing 3.3 with the fix

DeepBlueBubble commented 1 year ago

3.3.0 don't have this issue but 3.3.1 does. I am using Magisk-Delta stable

DeepBlueBubble commented 1 year ago

By the way it is on Crdroid 9.2

nift4 commented 1 year ago

does this happen with custom installer like FoxMMM?

DeepBlueBubble commented 1 year ago

Yes, happened with R-安装组件 (R-installation Component).

yennor commented 1 year ago

I'm installing it directly out of magisk. And with 3.3.1 I get that issue again. 3.3.0 Was alright. Cr-droid 9.3

7ff04da4aa6ac37197e249299066ac30 commented 1 year ago

Getting a crash again after 3.3.0 solved it, installing it directly on Magisk. On LineageOS 20, if it means anything.

cris0899 commented 1 year ago

I just had this problem in lineage 20 with magisk delta when installing the 3.3.1-0, the last thing it shows before crashing is installing microg gmscore

DeepBlueBubble commented 1 year ago

The module is actually installed, but won't show in Magisk after the crash. I checked the data/adb/module_update it is there. And it will be showing up to date in Magisk after reboot.

nift4 commented 1 year ago

Hello, for everyone's information:

  1. "3.3.0" actually broke APK installation due to a typo, and APK installation causes the crash
nift4 commented 1 year ago
  1. It seems like so far it has not been and never was fixed, and as I still cannot find any common ground of all reporters, nor can I reproduce this issue on my own phone, I have no idea how to fix this.
  2. Can this be reproduced in some specific GSIs I could flash on my phone?
  3. I will soon release a few more test builds regarding this issue.
downtoground commented 1 year ago

+1 crash on the latest 3.31 but 3.30 is running fine instead.

Procedure:

Installed first 3.31 without phonesky placed in /adb without any harm. Than added phonesky and reinstall 3.31: crashed while Installation.

3.30 install went thru with success.

Im on LOS 20. installed directly in Lygisk.

groszdaniel commented 1 year ago

It appears to me that this happens if there is a microG Services Core app left behind from an earlier microG installation. After I uninstall that, Magisk doesn't crash any more during installation.

nift4 commented 1 year ago

https://github.com/nift4/microg_installer_revived/releases/download/v3.2.0-0-test1/microG_Installer_Revived-t5.zip

mfulz commented 1 year ago

I've the same issue 3.3.0 working with Playstore added to /data/adb/Phonesky.apk 3.3.1 is crashing with or without playstore

https://github.com/nift4/microg_installer_revived/releases/download/v3.2.0-0-test1/microG_Installer_Revived-t5.zip

This one is closing directly after execution but I was able to read "Success" and it seems to work for me with and without playstore added to /data/adb/Phonesky.apk

I'm using a Pixel 7 LOS 20

mawoka-myblock commented 1 year ago

For me, it crashes when installing the core component on Poco X3 NFC (surya) on latest CrDroid, both with the test-file and the regular latest release. I got version 3.3.1-0 (that's what Magisk says) of your installer installed.

DeepBlueBubble commented 1 year ago

OK, so with the new update 3.3.2. The installation showed "Find real Play store Installing Micro G core success, xxxx (sorry I forgot)" and then crashed.

I am on Magisk 26.1 btw. Is anyone has the same issue?

j0110 commented 1 year ago

Same here with latest

gcvl commented 1 year ago

Me too but 3.3.0 works fine.

DocSniper commented 1 year ago

Had the exact same problem but was able to solve it. When installing 3.3.2 with microg 0.2.8 the installer crashed. After that I first uninstalled the Magisk module, then reboot. Then the microg 0.2.8 app was still there, so uninstalled it and rebooted again. Then 3.3.2 could be installed and the reboot button appeared.

Off-topic note. Don't be surprised because the Unified NLP modules are no longer available in the app (so you can uninstall all the NLP modules). As of version microg 0.2.8, UnifiedNlp modules are no longer supported, see: https://github.com/microg/GmsCore/releases/tag/v0.2.28.231657

pvagner commented 1 year ago

Hello, I have a similar issue. Originally I was on Android 12 aosp GSI. That rom had microg included and playstore included too. Since the rom is no longer available I have updated to lineageos 20 light GSI. Of course I had MicroG GmsCore on my data partition and I have got this issue. However GmsCore is working perfectly for me, there is nothing to reset, push messages are arriving, location is working fine too. But the playstore is crashing for me and I can't figure out which version of playstore to get. Can you give me some hints?

DeepBlueBubble commented 1 year ago

My solution is uninstall the modded playstore and install the newest one from apkmirror, and then reboot. Even if you get the modded playstore working, then if it update itself, it will crash some apps periodly, because Google made some changes prevents you use that.

pvagner commented 1 year ago

okay, so the playstore does not have to be inside the /system/priv-apk folder? Apk mirror has split packages to install. Should I allow this module to install fake store and then install the original playstore on the top of that? Currently on the data partition I do have no mention of com.android.vending.

DeepBlueBubble commented 1 year ago

Yes, at least mine doesn't

pvagner commented 1 year ago

Can you please try to explain in slightly more details how you have installed the real play store? I am on android 13 and I have tried the following. Retrieved the Phonesky.apk from the older rom I was using. Presumably that was a patched play store and while it has installed along with this magisk module it crashes as soon as I have tried to start it. Then I have tried to retrieve the playstore from the NikGapps. It installed successfully along with this module, I was able to allow permissions through the settings app, play store has started but it was unable to login. Then I have tried to just install fake store and wanted to install latest play store downloaded from apk mirror. However that has not worked since play store downloaded from APK mirror has a different signature than the fake store. I have no other ideas.

nift4 commented 1 year ago

this aosp commit broke it https://github.com/aosp-mirror/platform_frameworks_base/commit/93c2c2a292ea8695038afdd044bcb51e2e366780

Magisk Manager loads SSL library from GmsCore, which causes AOSP to register GmsCore as Magisk Manager dependency and kill Magisk Manager when GmsCore is updating, previous workaround broke in Android 13 due to that commit, I'm not sure how to proceed with a fix

DocSniper commented 12 months ago

Does this alternative installer have the same problem? And if so, have they found a solution? Then perhaps one could adopt this solution.

Link: https://github.com/FriendlyNeighborhoodShane/MinMicroG_releases/ and: https://github.com/FriendlyNeighborhoodShane/MinMicroG

nift4 commented 5 months ago

I plan to address this one by simply requiring microG to be installed as user app before flashing the module as it's the only feasible way.

nift4 commented 1 month ago

fixed in https://github.com/nift4/microg_installer_revived/releases/tag/v4.0.0-0