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.
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.
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?
ADB running at boot never worked, though running whether on normal operation or on recovery works flawlessly.
As the phones were needed, I had to do factory reset them, which worked out. But, that doesn’t prevent me to keep trying to get ADB working at boot, which to be honest I never tried before. It seems important to get it work, so I can get and share the logs that matter. As you mentioned, linux info and logs from recovery are useless, :( But now there’s no rush, since I unfortunately did a factory reset.
I think I got another moto same model, not in use, which has broken mobility data (it doesn’t get internet while on mobile), and I think I can keep trying from it, but without upgrading with this dangerous version, since I want to detect with it if the coming upgrade is as dangerous (lesson learned for me is to try with that broken phone before attempting on the ones in use). This way I don’t take the phones that are already in use. So again, I’ll keep trying the , but now not that pressured.
It’s weird to me that I could use ADB on recovery, with no issue, even to transfer files, which to me it means there were no authorization issues then, and it never worked on boot. As mentioned, I’ll modify the pseudo-broken phone and keep trying the ADB on boot with it…
Please ensure the props are set as I wrote them.
Also note that the props get reset on every system flash.
That’s not weird at all; those are two entirely different operating modes. The recovery isn’t even Android for the most part.
The recovery typically accepts any ADB connection while Android only accepts explicitly trusted ones. ADB also doesn’t typically run by default in regular Android execution.