Xiaomi - Bootloop when updating to newer version

[lp55]

Hi,

When I tried installing on tissot a version newer than lineage-16.0-20190724-microG-tissot it doesn't work, and if I install this version it works fine, but if I try to do a OTA update afterwards I get a bootloop, which is only fixed by flashing the older version. I saw an issue about bootloop [here](https://github.com/lineageos4microg/android_prebuilts_prebuiltapks/issues/13) but it says it was fixed, so I image this is another issue.
Other than that, LineageOS + microG is great :)

[Ezwen]

I tried to make a fresh install of the last version of lineage-microg on a Xiaomi Mix 2 (chiron), which is lineage-16.0-20190805-microG-chiron.zip, but I end up stuck on the bootloader splash. Maybe this is a similar problem?

EDIT: I also encountered this problem when following the official guide to migrate from a vanilla Lineage OS 16.0 to a lineage-microg build.

[ghost]

This also happens with a clean installation.

[lp55]

Hi,

Have any of the developers been able to reproduce this issue? Can I upgrade to the latest version and not have my os stuck on boot loop? Thanks

[ghost]

@corna

Have you looked into this? This doesn't happen on default LineageOS.

[corna]

A week ago (a couple of days before the DCMA removal) our TheMuppets/xiaomi repo went out of sync, which caused a lot of issues for many Xiaomi devices. For now I'll just remove the broken images, I'll try to see if the issue is solved as soon as the TheMuppets repo comes back. If you experience issues with other XIaomi smartphones, let me know here.

[ghost]

https://www.xda-developers.com/lineageos-builds-back-online-xiaomi-devices/

[ghost]

@corna Now the Xiaomi Mi A1 LineageOS build is back again.

[Iey4iej3]

@corna For the moment, none of Xiaomi builds of LOS for microG is back, while official LOS builds were back a week ago. I am pretty confused since it seems to me that we handle the collection of build targets manually instead of automatically tracing build targets of official Lineage OS? Xiaomi builds were removed and recently back but builds of LOS for microG do not synchronize with that?

By the way, several users on xda and reddit suggest public build log. Is that possible?

[corna]

The problem is that https://github.com/TheMuppets/proprietary_vendor_xiaomi is still down, so the automatic builds failed. I will have a look to see if I can make them succeed.

[Iey4iej3]

@corna Thanks for a very rapid reply. I think it is better to ask LineageOS Team to understand how they came up with a solution, after all they succeeded to build.

[corna]

They probably have their own internal TheMuppets mirror, from which they have removed the problematic components. However it is proprietary code in a grey area, so it is unlikely that they will provide us access to that repo.

[Iey4iej3]

Theoretically we can extract blobs from LOS nightly builds, but it is pretty treating and maybe unpleasant. Seemingly better to ask them anyway. In the news, it is worded as "The branch containing Xiaomi device BLOBs was taken offline while the LineageOS team looked for an alternative". I think that it is very unlikely that you could work this out on your own without their indications or even helps, given that they spent a month solving this issue.

[ghost]

They probably have their own internal TheMuppets mirror, from which they have removed the problematic components. However it is proprietary code in a grey area, so it is unlikely that they will provide us access to that repo.

@corna

https://gitlab.com/the-muppets/proprietary_vendor_xiaomi This is the "new" TheMuppets repo that you can use. LineageOS also uses it.

Tagging also @Iey4iej3 just in case you are interested.

[corna]

@Korsola Thank you, I wasn't aware of that repo. I just have to assert somehow the authenticity of that repo, then I can add it to our mirror.

[ghost]

I just have to assert somehow the authenticity of that repo

I found the repo via recognized contributor's khusika's comment on XDA. He's a well-known person. He commented the following:

As far as i know the Xiaomi vendor files are now migrate to the gitlab https://gitlab.com/the-muppets/propr..._vendor_xiaomi

https://forum.xda-developers.com/mi-a1/development/rom-lineageos-16-0-xiaomi-mi-a1-t3885100/post80251862#post80251862

I'm also sure that if you contact LineageOS Team about the authenticity of the repo, they will answer.

[corna]

I have compared the old themuppets/proprietary_vendor_xiaomi with the one that you have linked and it appears that they have rewritten the (now) 9106d91a commit (and the history after that), removing a single file containing a license file related to a "FaceAuth" product from SenseTime, which matches the DCMA complaint on GitHub. Funny, a single 2kB license file caused the removal of all the Xiaomi devices for almost two months.

Anyways, the repo seems legit, let me dig a bit deeper and then I'll add it to our build system.

[Iey4iej3]

I would like to suggest publicizing in some degree build logs or details of building process. As a reddit post suggests, ArrowOS has some machinery to do so. It would probably help you and us understand where issues situate. For example, berkeley is missing and we still don't know why. By publicizing, maybe somebody will figure out the obstruction.

[Iey4iej3]

@corna Does it work as expected? If so, then we can inform the OP and close this issue.

[corna]

I've tried to build for dipper but it failed with a different error, I still have to look at it.

[Iey4iej3]

@corna In general, it seems better if we can cooperate better with Lineage OS Team. Do you know that recent Lineage OS builds (maybe only of Xiaomi devices?) ship with OSS vendor images? I don't know where is an official claim, but here is an answer from a maintainer. (By the way, I am suffering from a similar issue therefore I am waiting for a new build with OSS vendor images.)

[corna]

Do you know that recent Lineage OS builds (maybe only of Xiaomi devices?) ship with OSS vendor images?

Yes, I have noticed the extra vendor partition in the zips but I haven't got the time to dig.

I have built LineageOS for microG for dipper with the Gitlab's The-Muppets repo and everything seems to work nicely. I'll try to contact the LineageOS team to obtain more guarantees on the authenticity of that repo, then I'll merge the patches and restart the builds for the Xiaomi devices.

[ghost]

I'll merge the patches and restart the builds for the Xiaomi devices.

Will the build(s) normally come via OTA update?

[corna]

Yes

[Iey4iej3]

After having received confirmations from LineageOS Team, I think that we can close this issue.

[ghormoon]

is there another one to watch for when the builds will be back online? if not, why not keep it until they are?

[Iey4iej3]

@corna Did you receive any official confirmations from Lineage OS Team? I believe that bgcngm works for various Xiaomi devices.

[corna]

I have already tried to contact bgcngm, but I have received no reply. I have added the GitLab repository to the docker build scripts, new Xiaomi builds shoud come soon.

[Algram]

@corna Thanks for working on this. Is it possible that chiron and polaris are both still failing? Do you know of any reason?

EDIT: Nevermind, polaris just showed up.

[ghost]

@corna tissot isn't showing up. Is it failing or is there another reason?

[corna]

@AnthonyKL I forgot to include it in the manual build, doing it now ;)

[Iey4iej3]

polaris works now. Thanks for your efforts. Wait for the OP to confirm, and then this issue could be closed.

[ghost]

@corna

My device is tissot. The OTA update to lineage-16.0-20191006-microG-tissot worked flawlessly. So I think the OP's issue is solved.

But the OTA Updater shows lineage-16.0-20191006-microG-tissot.zip build is available even though it is already installed? Can anyone else confirm this? Referencing to this (closed) issue: https://github.com/lineageos4microg/docker-lineage-cicd/issues/59

Also an off-topic question, is it normal for "Android security patch level" to show September on October build?

[lp55]

@corna

My device is tissot. The OTA update to lineage-16.0-20191006-microG-tissot worked flawlessly. So I think the OP's issue is solved.

Hi my device is also a tissot (Mi A1) and it didn't event show the lineage boot logo before it rebooted. I had to go back to lineage-16.0-20190724-microG-tissot.

[simplefied]

I have a tissot too. And I have bootloop on all versions after 20190320, haha. Think deal can be in firmware, on weekends stuck roll back on the latest stock. Has anyone encountered this?

[Iey4iej3]

@lp55 @simplefied Do you encounter similar bootloops in official LOS builds?

[braniii]

Also an off-topic question, is it normal for "Android security patch level" to show September on October build?

This is normal. The bulletin is always published on the first Monday in a month, so in this case today October bulletin. Further, it can takes roughly up to 7 days (at least for an older Android version like LOS 16) to be merged into LOS. Having only weekly builds, you should only wonder if it is not merged by the mid to end of the month. Or you can check the changelogs, e.g. here.

[simplefied]

@lp55 @simplefied Do you encounter similar bootloops in official LOS builds?

I tried. Hmmm, official LOS 20191006 works fine. So it's not the firmware?

[simplefied]

Haha, after official LOS had to wipe cache, data and system. BUT. After this latest LOS for microG works fine, bootloop disappear. Thanks!

[ghost]

Hi my device is also a tissot (Mi A1) and it didn't event show the lineage boot logo before it rebooted. I had to go back to lineage-16.0-20190724-microG-tissot.

@lp55

Please flash the latest stock firmware/build from here and then clean flash the latest LineageOS for microG build.

[ghost]

Hey, @simplefied

Could you confirm that are you experiencing the problem that I'm experiencing?

But the OTA Updater shows lineage-16.0-20191006-microG-tissot.zip build is available even though it is already installed? Can anyone else confirm this? Referencing to this (closed) issue: lineageos4microg/docker-lineage-cicd#59

[Iey4iej3]

Hey, @simplefied

Could you confirm that are you experiencing the problem that I'm experiencing?

But the OTA Updater shows lineage-16.0-20191006-microG-tissot.zip build is available even though it is already installed? Can anyone else confirm this? Referencing to this (closed) issue:

It seems to me that this is deliberate by design. As far as I remember, I encounter the same situation since long before (I cannot remember even whether that was in cyanogenmod).

[simplefied]

Hi, @ghost I confirm. https://ibb.co/64zN25g

[ghost]

@corna I think this issue can be closed now as the recent versions are working now.