Anders Lund<p>Today I updated my two android devices to the shiny new <a href="https://expressional.social/tags/e_os" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>e_os</span></a> v 3.0.</p><p>The <a href="https://expressional.social/tags/fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fairphone</span></a> <a href="https://expressional.social/tags/FP3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FP3</span></a> was just following the normal procedure, and apart from the weird habit of /e/OS requiring the screen to be on while finishing package updating, that went smooth and fast. This is an official build, and the phone was at 2.9.something previously.</p><p>My <a href="https://expressional.social/tags/Samsung" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Samsung</span></a> Galaxy S6 lite was a different story. It was running a user build of /e/OS, which stopped updates at v. 1.19, and I had to upgrade the firmware to latest android 13 before proceeding with the community version of /e/OS 3 that is available. I found this nice resource making it a bit easier: <a href="https://lineage.linux4.de/fw_update/gta4xlwifi.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">lineage.linux4.de/fw_update/gt</span><span class="invisible">a4xlwifi.html</span></a></p><p>After that I first thought I got stuck in a boot loop, but just being patient while starting in download mode fixed that, so I could install the /e/OS recovery, and then boot into recovery mode. These first two steps was achieved using <a href="https://expressional.social/tags/heimdall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>heimdall</span></a>, installed from archlinux extra repo.</p><p>See comment for continuation.</p>