Sadly, my particular device's flavour of the latest firmware update doesn't allow LineageOS to boot. Unless others with varying fw flavours will also pop up with this issue soon.
I will explain events in sequence. First i updated to lineage-20.0-20230323 while still on the previous firmware version, which was S1RDS32.55-106-3 and it worked as usual.
I got reminded of firmware updates and always want the best, so i went to perform the update, to S1RDS32.55-106-3 after detecting and fetching the flavour for my device with "Rescue and Smart Assistant" Lenovo/Motorola software. Btw, the flavour is one that's not yet listed on lolinet firmware page as of writing: DUBAI_G_S1RDS32.55_106_3_subsidy_DEFAULT_regulatory_DEFAULT_cid50_CFC.xml
and if you need to check, i uploaded it here, as it came from the fetching tool: https://drive.google.com/file/d/1oAImW2amatdm-o1pGx-VySFqCZnm6One/view?usp=sharing
(maybe even lolinet can copy & add it with my help). Note that my device carrier is displayed as "RETEU" versus this DEFAULT DEFAULT, yet lolinet doesn't have a new firmware file for that, it has at most old firmwares from 2022, and the tool fetches that based on my device's IMEI so it's really it.
To keep it simple, i shall say that i flashed the firmware update with both the Lenovo tool and Tiny-Fastboot-Script_v1.9.2 from lolinet. After the firmware update, LineageOS is no longer able to boot. It just loops after the Motorola logo and sometimes says that data is corrupted, prompting a factory reset (which also won't change a thing btw).
It felt like a brick by firmware update, so i investigated, trying many things for hours. I observe:
- To avoid having to clear my phone, i swapped other firmwares in and did other procedures, while preserving the LineageOS data and partitions, hoping to affect the problem so that it resumes booting like nothing happened. This had no results, it remained in bootloop/feeling bricked.
- Reinstalling the firmware (S1RDS32.55-106-3) with that Lenovo tool restores device to the stock Motorola ROM, which works properly under said latest firmware. I expect to be able to install LineageOS from this point onwards.
- Installing LineageOS 20.0-20230323 (from the working stock ROM state, with latest firmware, per the above point) following all install instructions to the letter, and i fall right back into the problem where it won't successfully boot LOS and loops.
So clearly, it wasn't a brick. It's the inability of LOS to boot on my device, with the latest firmware version. I hope you can help me shed a light on this @ThE_MarD
, i can help you investigate (but.. i tried all sorts of ways to get any exception logs, even /sys/fs/pstore/console-ramoops doesn't exist (it does until pstore.. so no kernel panics are stored during the bootloop). I also tried adb pull /
for getting the entire storage to manually search for logs, after mount system and Enable ADB, but all i get is a console spammed full of warning: stat failed for path
and ones like this:
adb E 03-24 18:50:28 7760 4464 errno.cpp:92] failed to convert errno 40 from wire
adb: warning: stat failed for path /proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/proc/thread-self/root/dev/stderr: Input/output error
Which persisted even after flashing rooted boot.img (LOS) despite being unable to boot the phone fully. So now, im not sure how to gather useful diagnostic info, but i will use any steps you can provide.
// Edit while writing post: i managed to pull driver messages log file (dmesg) with the command adb shell dmesg > dmesg.log
, taken after a few unsuccessful boots. Here it is, hope it contains something you can use: https://0x0.st/HoSj.log
Actually, failure to load a specific part of the firmware ("yupik_ipa_fws" / yupik_ipa_fws.mdt) seems to be the only theme in said log file, maybe it already clears up what's going on?