This is interesting and potentially useful, but by far the most depressing part is the last instruction, when faced with a wall of never-ending logs:
At this point, your best shot is to gather all the data like I hinted at above, and to intelligently engage with the support community of your Android distribution or custom ROM that you would want to fix on your device. Channels to do that could be any of Internet Relay Chat (IRC), an on-topic Subreddit, some bulletin board on the Word Wide Web, a discord server… it’s on you to figure that out.
This is the story of my life since 10 years. I always stick(ed) to Android and, with all my phones, evventually with ADB debugging, customs roms or at least an opened bootloader. ADB is a lovely tool, works on Linux without problems and saved my data quite sometimes.
In >90% of the cases, my phones stuck to a boot loop due to no (internal) memory left. Moving data to the SD card or deleting them with ADB is the cure. I don't know why Android still has these problems. This happened to me last time last week with a 2018 Pocophone F1.
3 comments
[ 2.6 ms ] story [ 17.0 ms ] threadThe Internet is still decentralized/distributed — this is a Good Thing™ — and most projects list the primary "hangout" on their landing page =]
In >90% of the cases, my phones stuck to a boot loop due to no (internal) memory left. Moving data to the SD card or deleting them with ADB is the cure. I don't know why Android still has these problems. This happened to me last time last week with a 2018 Pocophone F1.