Can't install microG from OFox (error 30) (error 1)

[TheGreatUnknown-One]

I've tested install mini microG from FNS and it fails
Same with installer from ale5000

Latest CI build: error 1
microG: MinMicroG-Minimal-UPDATELY-20250820010418

Nightly alpha: error 30
microG: microg-unofficial-installer-v1.3.2.22-alpha-g6d9bce9c_-oss-by-ale5000-signed

I using
GSI: DerpFest 16.0 | A16 QPR0 | TREBLE GSI OFFICIAL-signed
Device: RN 13 4G ###
OS: Stock ROM HOS 2.0 OS2.0.201.0.VNGMIXM
Recovery: OFox R11.3 Official
Xiaomi Redmi Note 12 4G Topaz
Xiaomi Redmi Note 13 4G Sapphire/Sapphiren

Details

Details

Details

Details

Details

[ale5000-git]

Hi,
this is the repo of the "app" microG, my installer (microG unofficial installer) is here: https://github.com/micro5k/microg-unofficial-installer

[TheGreatUnknown-One]

Hi, this is the repo of the "app" microG, my installer (microG unofficial installer) is here: https://github.com/micro5k/microg-unofficial-installer

Hey how are you?

I know, but Omni tolds me to open an issue ticket here

[ale5000-git]

The issue of being unable to remount as read/write is usually device/ROM specific.
Some file systems are made to be ONLY read-only.

More info here: https://android.stackexchange.com/questions/220892/system-partition-locked-to-read-only-in-android-10

[ale5000-git]

Hey how are you?

Fine, thanks :-)

[TheGreatUnknown-One]

The issue of being unable to remount as read/write is usually device/ROM specific. Some file systems are made to be ONLY read-only.

More info here: https://android.stackexchange.com/questions/220892/system-partition-locked-to-read-only-in-android-10

OK, but I don't understand that 🤔
I'm rooted and have RW

Beforehand I had using ROS Revived 7.0 ROM and no issues

I've made it RW with RO2RW-v3.7.2.1_fullRW
But the GSI from Doze-off is RW

[TheGreatUnknown-One]

Hey how are you?

Fine, thanks :-)

Nice to hear that 😉👌
I haven't seen you at the microG Group for a long time 🤷‍♂️😢

[ale5000-git]

Hey how are you?

Fine, thanks :-)

Nice to hear that 😉👌 I haven't seen you at the microG Group for a long time 🤷‍♂️😢

I'm just a bit busy but I will return soon.

[Sapiosenses]

I know, but Omni tolds me to open an issue ticket here

This is my Github account.

No I did NOT tell you to open an issue here for reporting problems with 3rd-party installers, that would be pointless and annoying for the people here who generally have nothing to do with 3rd-party installers.

microG makes some APKs, they do not make flashable installers that use recovery.

If those installers are reporting issues with the intended destination partition, then either that partition is locked in some way within recovery when the installer tries to access it, it is short of free space, or there is some other esoteric aspect of that device's partitions that the recovery or flashable package cannot handle properly.

The first person you should talk to about such problems is your ROM maintainer, to see if the issue is unavailable disk space on that partition, an incompatibility with the recovery tool you are using etc.

Then if that provides no insight, you can take it up with the 3rd-party installer maintainer. (Alex is here obviously and has his own repo/site for support, but currently MinMicroG is unmaintained even though its repos and websites are still up)

[ale5000-git]

The issue of being unable to remount as read/write is usually device/ROM specific. Some file systems are made to be ONLY read-only.
More info here: android.stackexchange.com/questions/220892/system-partition-locked-to-read-only-in-android-10

OK, but I don't understand that 🤔 I'm rooted and have RW

Beforehand I had using ROS Revived 7.0 ROM and no issues

I've made it RW with RO2RW-v3.7.2.1_fullRW But the GSI from Doze-off is RW

A test you can do is to try to push a file in the system partition using adb when the phone is in the recovery.
If you want to further debug the problem please do it here: https://github.com/micro5k/microg-unofficial-installer