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.
% adb logcat |& tee logcat.txt
- waiting for device -
And now the boot hangs forever it seems…
That means you didn’t actually get an ADB connection yet. Either the install is fscked to the point where even ADB doesn’t work (I doubt that), ADB doesn’t actually run (did you follow the steps I provided?) or you’re not actually authenticated. Please confirm with adb devices and also check whether the USB device is even visible to your kernel via dmesg.
% 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…
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.
got back to the same by sideloading latest, and then went back to previous working version. Previous working version, is boot looping faster though, and after a couple of trials it goes the recovery (this doesn’t happen on latest), this was like that before, so there’s a difference between latest and prior working version, on latest the loop never ends, and each iteration is somehow long compared to the prior working version.
I’ll go get some rest.