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.
Contact the device maintainer on Matrix
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.
Thanks !
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 foundYou won’t get a log early in the boot process without a prop being set. Although, if your ADB key is already trusted, this might also be possible using the LOS recovery.
Flash the previously working version, get
adb shellaccess in the recovery and mount the system partition read-write somewhere.Then append this to
/system/build.prop:persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adbIf your key is trusted, you should now be able to access the device via ADB during boot and can do
adb logcatbefore starting the device.If your key is not trusted, you’ll see the device as unauthorised and will have to get your public key (
~/.android/adbkey.pub) into/data/misc/adb/adb_keyssomehow. I’ve never been able to mount the userdata partition in LOS recovery do be able to do that though but I haven’t bothered to debug why that is. It might just work for your device though.I’d recommend you to redirect the log to a file and let it reach the boot loop point. When it reboots, terminate
adb logcat(or perhaps it does that on its own).Now you’ll have to scour the log for the actual exception thrown. It will be quite a ways up in the log and IIRC you should see zygote freaking out around the point where the actually interesting error is.
% 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 devicesand also check whether the USB device is even visible to your kernel viadmesg.% adb devices List of devices attached ZY22FKS3NB recoveryWhen 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…
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.
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 recentlyMy bad, my knowledge seems to be way out of date
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.
In the future it may be worth taking a backup
