Anyone with a moto one 5g ace (kiev) that performed OTA update recently and got a boot loop out of it?

I use lineageos for microG, which is based on lineageos, and Today got an OTA update which I can’t matches the same version as the one on lineage, but after attempting the reboot required by the update, the phone gets into a boot loop.

I haven’t found a way to get out of the loop without losing data. Downgrading doesn’t help, no matter if a major upgrade is attempted.

It looks to me this could be rather lineageos issue, since I got a past experience with a pixel 4a (5g), and at that time I lost all data attempting a factory reset that didn’t even help at all. Later there came an update from lineageos, which I manually installed, and got the phone back, though with all data lost. This time I’d like to avoid losing data.

Any help or hint is appreciated.

You are viewing a single thread.
View all comments View context
1 point
% adb devices
List of devices attached
ZY22FKS3NB      recovery

When you say authenticated, do you mean authenticated with google specific keys? I think LOS and LOS4microG both have their own keys, so if in need of google keys I doubt LOS and LOS based ROMs can authenticate.

This is the dmesg grabbed on 20241216 recovery, and this is a /proc/kmsg I attempted to grab…

permalink
report
parent
reply
1 point
*

When you captured that, the device was in the recovery. That’s not particularly interesting; recovery works fine.

We need adb access during boot. You need it to say “device” here while it’s attempting to boot.

If no device shows up, you haven’t enabled the prop to enable ADB properly.

permalink
report
parent
reply
1 point

Yeap, I suspect as you mentioned, with LOS and LOS4uG there are no trusted keys. And you’re right, linux messages on recovery are really not interesting, :(

permalink
report
parent
reply
1 point

This has nothing to do with the ROM. While you can embed trusted keys into a ROM which is useful for debugging, what I mean is the regular trusted ADB keys that get added when you allow ADB access from your computer via the pop-up.

If you’ve allowed your PC ADB access recently (this expires after some time), your key should be trusted. If it isn’t, there is the method to make it trusted I described.

You do need to modify the system partitioni to enable ADB at boot though. Just do what I described.

permalink
report
parent
reply

Community stats

  • 56

    Monthly active users

  • 62

    Posts

  • 49

    Comments

Community moderators