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.
If you boot into bootloader mode with the hardware buttons like volume up and power or whatever, you might be able to dirty flash the phone again and get it to boot. But that would probably at least if nothing else wipe out Google Play Services unless you tried all the flashing instructions again. I want to say you might be able to put in the pin somewhere and possibly even access the data from the hard drive, but I won’t swear to that.
I attempted already installing by hand, meaning doing an adb sideload. That’s what I meant when I said I attempted to downgrade, of course I also tried sideloading the same version that lead to the boot loop just in case. I haven’t tried doing a factory reset, but I really would like to avoid it.
I don’t use google play, I use lineageos for microg, and even so, I avoid google services, since most my apps come from f-droid. Regardless, losing the data is really a bad thing, and all apps configurations and such.
Does your phone have TWRP? On a TWRP phone you can decrypt and transfer data over USB without booting the OS. I had to do this on an older device recently
My bad, my knowledge seems to be way out of date
Downgrading doesn’t help, no matter if a major upgrade is attempted.
What do you mean by this?
A downgrade to the previous version should by all means fix this.
well, I tried installing through adb both recovery and lineageos image version 21.0-20241115, and also version 20.0-20240719, and I got the same boot loop after each install. I suspect the 21.0-20241216 installed something new which doesn’t get replaced or removed when downgrading. I guess a major downgrade (notice I went back to 20) doesn’t help a bit, so I guess downgrading any further wouldn’t help.
You cannot downgrade to 20. Doing so might actually have broken something but that’s not given.
Downgrading to the previous nightly should have worked though. In which order did you try this?
To get to the bottom of this, you need to read out the ADB logcat. Do you have TWRP?
I tried first same version, then prior version, then the one before which on lineage for microg is the latest 20. So it didn’t work for immediate prior version.
I use the lineage recovery image that comes bundled with lineageos. I looked to see if twrp has support for this phone, and it doesn’t, not officially at least.
I wasn’t aware of adb logcat, but:
% adb logcat
/system/bin/sh: logcat: inaccessible or not found
Sounds like a good question for the [ROM]-[13]-[KIEV]-LineageOS-20-[OFFICIAL] XDA thread. It says LineageOS 20, but the later replies only talk about LineageOS 21.
Contact the device maintainer on Matrix