LineageOS for microG

[Steve Graham]

I followed the LineageOS instructions and successfully went from 18.x to 19.x on my Pixel 5a (barbet). However, subsequant OTA updates have not installed. I can download them, but the install always fails immediately with the notification "Install error".
Now, as far as useful error messages go, that isn't one.
So I'm looking for tips about what the cause may be. Or is there another way to install the updates, via ADB, for example?

 

[kurtn]

I followed the LineageOS instructions and successfully went from 18.x to 19.x on my Pixel 5a (barbet). However, subsequant OTA updates have not installed. I can download them, but the install always fails immediately with the notification "Install error".
Now, as far as useful error messages go, that isn't one.
So I'm looking for tips about what the cause may be. Or is there another way to install the updates, via ADB, for example?

Update LineageOS on barbet | LineageOS Wiki

wiki.lineageos.org

 

[humpty321]

I uninstalled Magisk and flashed the original unpatched boot.img (to set the “Patch vbmeta in boot image” option had been a mistake anyway). But the OTA would not succeed after that either. So Magisk obviously was not the culprit. Therefore I started from scratch with the latest factory image. There is no new OTA yet, so I'll have to wait and see if the next one will work.

Just as a followup, this time the OTA update worked (lineage-19.1-20220804-microG-bramble). But after that root did only work with interruptions. This felt like a loose connection. Finally it stopped working altogether. So I had to install Magisk afresh.

Should I maybe disable "Update recovery" in the Updater options in order to avoid damaging root on a monthly basis, with every new update?

 

[kurtn]

Just as a followup, this time the OTA update worked (lineage-19.1-20220804-microG-bramble). But after that root did only work with interruptions. This felt like a loose connection. Finally it stopped working altogether. So I had to install Magisk afresh.

Should I maybe disable "Update recovery" in the Updater options in order to avoid damaging root on a monthly basis, with every new update?

Bramble is an a/b device. After installing the update in the other partition, you can tell magisk to install in that partition. Then reboot.

 

[heinhuiz]

So you somehow blocked connection of updater to microG.org or it's sub-domains.

Now that a new build has been released, the update check is working again. Maybe something was wrong on the server after all.

Edit: I have to be more precise. I still get the message stating that the update check failed, but the latest updates are actually listed.

 

[humpty321]

Bramble is an a/b device. After installing the update in the other partition, you can tell magisk to install in that partition. Then reboot.

Thank you for drawing my attention to this option! I've found now these OTA Upgrade Guides (https://topjohnwu.github.io/Magisk/ota.html). The steps necessary on A/B devices seem clear to me.
But there are also 2 Non A/B devices running LineageOS in the family. The guide says "you must have your stock recovery installed on your device". Is in this case the LineageOS recovery "stock" or would that be the one from Google?

 

[heinhuiz]

Thank you for drawing my attention to this option! I've found now these OTA Upgrade Guides (https://topjohnwu.github.io/Magisk/ota.html). The steps necessary on A/B devices seem clear to me.
But there are also 2 Non A/B devices running LineageOS in the family. The guide says "you must have your stock recovery installed on your device". Is in this case the LineageOS recovery "stock" or would that be the one from Google?

These are basically non LineageOS for microG questions that are off-topic here, and that you will be better answered in your devices' LOS threads. But for me TWRP has always worked on any supported device, as did LOS recovery on the few I tried it with.

 

[kurtn]

These are basically non LineageOS for microG questions that are off-topic here, and that you will be better answered in your devices' LOS threads. But for me TWRP has always worked on any supported device, as did LOS recovery on the few I tried it with.

You should add: you use custom recovery method for installing magisk. Boot image method doesn't survive lineageOS updates.

 

[budmerman]

Im on ocean. when i upgraded to lineagemicrog 19 my external DAC's would no longer work. anyone have same problem? anyone still able to connect to USB audio? any solutions?
thanks.

 

[kurtn]

Im on ocean. when i upgraded to lineagemicrog 19 my external DAC's would no longer work. anyone have same problem? anyone still able to connect to USB audio? any solutions?
thanks.

Doesn't sound like a microG issue. But highly device dependent. You can try to reproduce the bug with original lineageOS and file a bug report.

 

[Bracher]

Hello, in the past I've used LineageOS for microG and additional - to get for example the patched Google Store - MinMicroG Installer from FriendlyNeighbourhoodShane. With MicroG version 19 this is no longer possible - MicroG is already fully installed - unfortunately without the patched Store. On most issues Aurora works fine and I hoped I could work without Google. Unfortunately it does not work for DWD Warnwetter. The app has GMS registration, but it does not recognise my in-app-purchase via Google. Is there any solution to get an patched Google Store?

 

[kurtn]

Hello, in the past I've used LineageOS for microG and additional - to get for example the patched Google Store - MinMicroG Installer from FriendlyNeighbourhoodShane. With MicroG version 19 this is no longer possible - MicroG is already fully installed - unfortunately without the patched Store. On most issues Aurora works fine and I hoped I could work without Google. Unfortunately it does not work for DWD Warnwetter. The app has GMS registration, but it does not recognise my in-app-purchase via Google. Is there any solution to get an patched Google Store?

We don't talk about piracy here. But is it really piracy, if you make warnwetter useable for you alone without play store? You already played for it. - and dwd doesn't want the meney. They got forced by court to take it.

 

[Bracher]

We don't talk about piracy here. But is it really piracy, if you make warnwetter useable for you alone without play store? You already played for it. - and dwd doesn't want the meney. They got forced by court to take it.

Yes for sure I paid and I would have no problem to pay ones more but it's not possible, I wrote as well to Warnwetter to ask them about this problem they have not reacted so far.

 

[heinhuiz]

Yes for sure I paid and I would have no problem to pay ones more but it's not possible, I wrote as well to Warnwetter to ask them about this problem they have not reacted so far.

With Aurora you can log in with your own Google account. That should allow you to download purchased items.

 

[Bracher]

The problem is I can download this app but despite his registration with GMS and beside the fact that I paid it and it worked till MicroG LOS 18.1 it now no longer accepts the payment or let me pay ones more - it seems a problem with in-app-purchases, but ok I have to find an alternative

 

[Psk.It]

The problem is I can download this app but despite his registration with GMS and beside the fact that I paid it and it worked till MicroG LOS 18.1 it now no longer accepts the payment or let me pay ones more - it seems a problem with in-app-purchases, but ok I have to find an alternative

download mickgapps core
open It, in /appset/core there is the GooglePlaystore.zip
copy "___etc___permissions" to /system/etc/permissions and "___priv-app___Phonesky" to /system/priv-app/phonesky

if unable to keeps changes.persistent you can build a magisk module on the fly

on reboot, you will have a working PlayStore, and your purchaised apps will work

 

[humpty321]

You should add: you use custom recovery method for installing magisk. Boot image method doesn't survive lineageOS updates.

Thank you both for answering my question. The non A/B devices I mentioned are both cheeseburger. This phone has a ramdisk and no separate vbmeta partition. Therefore following the installation guide I have to patch boot.img.

While these devices still were on 18.1 I used TWRP. When I had patched boot.img for the first time in 18.1 I let TWRP make a backup of it, placed on the phone. For all the following updates I used OTA only to download them. To install them I manually rebooted to recovery, installed the update from /data/lineageos_updates/, made TWRP restore the backup of that first patched boot.img and then rebooted to system. Never had a problem with this procedure.

When I installed the upgrade to 19.1 I guessed OTAs might become even easier to handle for the users of those two phones, if I installed the stock (?) LineageOS recovery. And I had always felt unsure if the updates might bring along changes in boot.img. These would have been discarded by always restoring that very first patched one.

So my question is: How often does LineageOS for microG updates contain modified boot.imges, especially if a device like cheeseburger has ceased to receive updates from the manufacturer? If changes to boot.img are not to be expected I'd return to TWRP and that previous procedure for updates.

 

[kurtn]

Thank you both for answering my question. The non A/B devices I mentioned are both cheeseburger. This phone has a ramdisk and no separate vbmeta partition. Therefore following the installation guide I have to patch boot.img.

While these devices still were on 18.1 I used TWRP. When I had patched boot.img for the first time in 18.1 I let TWRP make a backup of it, placed on the phone. For all the following updates I used OTA only to download them. To install them I manually rebooted to recovery, installed the update from /data/lineageos_updates/, made TWRP restore the backup of that first patched boot.img and then rebooted to system. Never had a problem with this procedure.

When I installed the upgrade to 19.1 I guessed OTAs might become even easier to handle for the users of those two phones, if I installed the stock (?) LineageOS recovery. And I had always felt unsure if the updates might bring along changes in boot.img. These would have been discarded by always restoring that very first patched one.

So my question is: How often does LineageOS for microG updates contain modified boot.imges, especially if a device like cheeseburger has ceased to receive updates from the manufacturer? If changes to boot.img are not to be expected I'd return to TWRP and that previous procedure for updates.

Keeping old boot.IMG is no good idea. The updates contain mainly security patches. Many of them are for the Linux kernel. The kernel is in boot image.

Rename magisk.apk to magisk.zip and flash it in recovery. If it doesn't work, use older magisk or lygisk.

Lygisk is a Magisk fork correcting addond's requirement of decrypted data in recovery.

GitHub - programminghoch10/Lygisk: Your Lie in Android

Your Lie in Android. Contribute to programminghoch10/Lygisk development by creating an account on GitHub.

github.com

 

[kurtn]

download mickgapps core
open It, in /appset/core there is the GooglePlaystore.zip
copy "___etc___permissions" to /system/etc/permissions and "___priv-app___Phonesky" to /system/priv-app/phonesky

if unable to keeps changes.persistent you can build a magisk module on the fly

on reboot, you will have a working PlayStore, and your purchaised apps will work

We are talking about in app purchases. For that use case nanolx patched a play store. That is still part of many microG installers. But not shipped with nikgapps.

I prefer methods I can't talk about in XDA

 

[Psk.It]

We are talking about in app purchases. For that use case nanolx patched a play store. That is still part of many microG installers. But not shipped with nikgapps.

I prefer methods I can't talk about in XDA

What I experienced (since I have been flashothic) is about PlayStore and A12
the patched PlayStore does not work proprtly
that's the reason i suggested to use a most recent version
(you can just try, or find a differenti way)