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.
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, :(
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.
Ohh, well, I followed your instructions…
So what part doesn’t work now? Is ADB running at boot or not? If it is running, are you authorised or not?