Bootloops reported for several devices with December 21.0 builds

[petefoth]

Affected devices include

1. Moto one 5g ace kiev: see moto one 5g ace (kiev) December version OTA upgrade (21.0-20241216) made the phone get into a boot loop #717 Worked after wipe
2. Xiaomi Mi 11 Lite 5G renoir: December build run status #710 (comment) Worked after wipe
3. Google Pixel 4a sunfish: see issues/710#issuecomment-2564300420
4. OnePlus 11 5G salami CPH2451 variant: OnePlus 11 (salami) 20241227 build bootloops for CPH2451 variant #719 (but not for all devices - see here & working for CPH2449 variant: here )

I have no idea what the issue is, or whether it is different issue on different devices. There is no way the project can investigate as we don't own or have access to an of these devices. But very happy to collate any information or boot logs or any other information others can provide.

[Carlos-Rocha]

Maybe related to microg signature spoofing?
I had no problems with the upgrade but microg was updated to 0.3.6 before it. Could it be a factor?

[petefoth]

Could be, but I don't understand why thst would cause problems only for some devices, or for some variants of some devices

[vs49688]

Maybe related to microg signature spoofing? I had no problems with the upgrade but microg was updated to 0.3.6 before it. Could it be a factor?

I forgot to mention in #718 (comment), that's what I did too - the breakage in 0.3.6 is what caused me to look for an update.

[Lealchimie]

Hello, i finally managed to install on redfin after failed attempts. It is a bit weird, but maybe it can help to just tell what happened :

• first original OTA failed and caused bootloop. I had magisk installed and tried to reapply before rebooting, which (I believe) made it impossible to just boot on the other slot.
• trying a clean install after that also caused bootloop
• decided to try iodeOS and used your unofficial build found here (clean install of course)
• upgraded microG to last stable version
• tried (because why not) to dirty flash the lineage4microg december build on top of iodeOS : it boots and works !

I'm unsure of wether I want to stay with a dirty install like this, maybe I can try updating microG in the november build before dirty flashing the december build to see if that works. Or do you think I wouldn't run into too much problems like this ?

[Carlos-Rocha]

Wow...I didn't know about pf-custom-roms based on iodeOS, and there's even a rom for surya, tho microg signature is outdated, right?

• upgraded microG to last stable version

This is what unironically made the installation work without bootlooping, you have to update to microg v0.3.6.244735 before updating otherwise it just bootloops, a fresh installation of 20241227 would bootloop for some reason.

To update correctly to the december builds you must install an older build, update microg then install the december build otherwise it bootloops.

Magisk doesn't affect the outcome although some modules might break due to android changes.

[petefoth]

Thanks all. Your input has allowed me to find the root of the problem.

It looks like the problem was caused when I updated the microG GmsCore component in the android_vendor_partner_gms repo. I believe that there are errors in the permissions file(s), which don't match the permissions in the .apk, causing the devices to fail to boot. If microG was updated before updating, then the updated version (and its permissions files) will take priority over the 'bit-in' version, the permissions will match and the device will boot.

It may take a while to fix, but thanks again for all your help

[petefoth]

Problem fixed in this PR in the android_vendor_partner_gms repo 'Sort out permissions for updated microG GmsCore #38

There's a new build for xz2c containing the fix. Fixes for the remaining devices will be along in the next couple of days.

Thank you for your patience :)

[pokulo]

Thanks for fixing @petefoth ! My Xiaomi Mi 6 (sagit) was also stuck in a bootloop with the December update. I hope sideload-updating my phone with next version will simply fix the bootloop. Looking forward to install it.

[pokulo]

I just flashed the new update https://download.lineage.microg.org/sagit/lineage-21.0-20241231-microG-sagit.zip to my device, but the bootloop is still looping.

[petefoth]

I'll look into that this evening.
In the meantime, please can you try running the following for one boot cycle
adb logcat > bootlog.txt and upload the resulting file?

[pokulo]

@petefoth thanks for your efforts. I tried adb logcat already, but never got any connection during the bootloop. It worked in the past on a running LOS, but only after confirmation.
Is there an easy way to get the logs from the recovery shell? I guess for logcat to work I have to change boot config to enable usb debugging by default. But how.. I still have to find out.

[petefoth]

I tried adb logcat already, but never got any connection during the bootloop.

I originally made an eng build for debugging, rather than the normal userdebug, but then I reverted to the earlier userdebug build and it just worked:

• before the 'spinning circles' animation appeared, adb logcat said waiting for device
• once the 'spinning circles' were visible, lg messages started appearing

Is there an easy way to get the logs from the recovery shell?

There probably is, but I don't know what it is :(

I guess for logcat to work I have to change boot config to enable usb debugging by default. But how..

Maybe

• install the last working version from November, but don't update microG, stick with the default 0.2.27
• enable developer options, USB debugging and rooted debugging
• start adb root
• dirty flash the new build, either via the Updater app, or recovery and adb sideload
• reboot with the USB still connected
• start adb logcat while the device is booting

If that doesn't work, then I'm fresh out of ideas :( Time to go searching the internet!

The latest builds have been working for me on all the devices I own (xz2c, sunfish) so I don't think it's a general problem for all devices as the earlier builds were.

Good luck!