LineageOS for microG

Search This thread
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

Senior Member
Jan 28, 2017
4,625
2,050
Small town in Bavaria
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?
 

humpty321

Member
Jun 12, 2015
35
6
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

Senior Member
Jan 28, 2017
4,625
2,050
Small town in Bavaria
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.
 
  • Like
Reactions: humpty321

heinhuiz

Senior Member
Nov 26, 2011
1,215
1,065
Xiaomi Mi A1
Redmi K20 / Xiaomi Mi 9T
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.
 
Last edited:

humpty321

Member
Jun 12, 2015
35
6
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

Senior Member
Nov 26, 2011
1,215
1,065
Xiaomi Mi A1
Redmi K20 / Xiaomi Mi 9T
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.
 
  • Like
Reactions: humpty321 and kurtn

kurtn

Senior Member
Jan 28, 2017
4,625
2,050
Small town in Bavaria
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

Member
Oct 10, 2020
6
1
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.
 

Bracher

Senior Member
Sep 18, 2009
218
50
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

Senior Member
Jan 28, 2017
4,625
2,050
Small town in Bavaria
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

Senior Member
Sep 18, 2009
218
50
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.
 

Bracher

Senior Member
Sep 18, 2009
218
50
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
 
  • Like
Reactions: kurtn

Psk.It

Senior Member
Mar 6, 2016
279
66
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

Member
Jun 12, 2015
35
6
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

Senior Member
Jan 28, 2017
4,625
2,050
Small town in Bavaria
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.
 
  • Like
Reactions: humpty321

kurtn

Senior Member
Jan 28, 2017
4,625
2,050
Small town in Bavaria
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
 
  • Wow
Reactions: heinhuiz

Psk.It

Senior Member
Mar 6, 2016
279
66
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)
 

Attachments

  • GooglePlayStore.zip
    21.3 MB · Views: 2

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    LineageOS for MicroG updates depend on the official LineageOS builds continuing for the device, and the official LOS policy is to only support two versions at any given time: the latest and the one before that. So when LOS 19 builds started in mid-February, LOS 17 was dropped.

    It's not really a great arrangement since there are no security updates as you noted but it's up to LOS project maintainers to decide this, and they say they're strained for resources. At least the LOS for MicroG repository keeps the latest builds for discontinued devices available for download, while they're simply deleted from the official LOS as if they never existed. Example: https://download.lineageos.org/davinci doesn't even tell you there used to be builds at any given point, the page for a nonexistent device looks just the same: https://download.lineageos.org/blahblahblah
    No. Lineage.microg.org does not depend on official lineageOS building ROM's. Lineage.microg.org can build 17.1 - and there are security patches in lineageOS source code for 17.1

    The only problem: It's too much work for a one-man-show to keep building.
    2
    As far as I know, LineageOS for MicroG only adds the signature spoofing patch: other than that, no changes are made to the source coming from the official LineageOS for the device. And no builds are made for devices discontinued by the official LOS. I've never claimed it was theoretically impossible, just that it doesn't happen in practice (because it's out of scope for the project as I understand it). Now I might be wrong but if that's the case, can you point to a counterexample of a device that got a LineageOS for MicroG build with updated security patch after it was already discontinued by the official LineageOS? If not, then I believe what we're saying effectively amounts to the same, just using different words.
    2
    Interesting, and good to know. That's still 15.1 by the way.

    All the more respect to the LineageOS for MicroG team then! They're doing even more than I thought.
    1
    Is there a reason lingeage.microg was not updated for Assu Zenfone 8 (sake) since August 26?
    The other phones seem to have gotten updates in the meantime.
    1
    19.1 builds often seem to stop after dipper and after some days of silence older builds are resumed.
  • 160
    Android experience relies heavily on Google's Play Services. The microG project creates an alternative to installing Gapps, which install and execute closed-source blobs on our phones. MicroG however requires a patch called "signature spoofing", which allows microG's apps to spoof themselves as Google Apps. LineageOS currently does not include the patch due to different opinions among the developers. (further information can be found here)

    This makes microG installation difficult on LineageOS and other ROMs. Our ROM is a fork of LineageOS with just the necessary changes to have microG built-in. We ship weekly builds for all the LineageOS supported devices..

    You can find us on https://lineage.microg.org

    XDA:DevDB Information
    LineageOS for microG, ROM for all devices (see above for details)

    Contributors
    Simon94, ncorna, n1zzo, LineageOS, MaR-V-iN
    Source Code: https://github.com/lineageos4microg

    ROM OS Version: Android 10
    Based On: LineageOS

    Version Information
    Status: Nightly

    Created 2017-11-06
    Last Updated 2020-08-28
    24
    Just to give a small heads up. As you may noticed some of the project members the priorities have shifted to other projects.

    I was and am still willing to take over some of the tasks, but as microG lacked some bugfixes and support for LineageOS 17.1 i was not sure whether its worth it to spend more time into LineageOS for microG. Once marvin released the new microG update, we still had to check with our team, how we'll proceed.

    For now i've taken over the responsibility of the Android Build process, merged some of the fixes and integrated LineageOS 17.1 support. New builds are on their way, both LineageOS 16 and 17.1 based.


    Best
    Simon
    15
    Hey guys. You are right with your findings. We were testing yesterday LineageOS 15.1. But we rolled it back. Now we have almost everything ready for Lineage 15.1 - In fact there is one minor change outstanding before we're going to release. After release we'll start building the complete LineageOS weekly build roster again.
    14
    Current device list which will be built tomorrow:
    Code:
    a6020,angler,armani,athene,bacon,bullhead,cancro,capricorn,cheeseburger,clark,condor,crackling,d855,
    deb,dragon,falcon,flo,flounder,gemini,h815,h850,hammerhead,harpia,herolte,here2lte,hlte,i9100,
    i9300,jfltexx,kenzo,klte,libra,lux,m8,mako,mido,oneplus2,oneplus3,onyx,osprey,otus,paella,pme,
    serranoltexx,shamu,thea,titan,victara,wt88047,yuga,Z00L
    13
    today i got my weekly(?) update with november security patches via ota notification.
    thanks for that!

    Yes they are rolling out new builds again :) Thank you everyone who is contributing to this :good:

    Oops. They only build Oreo right now.

    We have decided to build every device weekly (like before), as we don't have the capacity to build for ~75 devices daily and nightlies are quite useless to the end users. We will build for all the ~200 devices, ~30 devices per day, from top to bottom of the usual hudson devices list (which means that 15.1 builds will appear in the first part of the week and 14.1 in the second one).

    As usual, new devices will be automatically added to the build list, no need to ask for them, just wait some days.