i’m also affected by this issue, although i use a different kind of mobile phone.
i think, it’s caused by a wrong server certificate, because the letsencrypt server certificate is only valid for images.ecloud.global but the update process tries to open an https connection to ota.ecloud.global. that’s why it will stop on a 403 error.
update from 0.12-2020093076095 to 0.12-2020102981459 went fine.
The status bar issue from the previous version has been solved (Go to System > Status bar > System Icons)
Some default apps like phone, contacts, tasks are not yet adjusted for dark style, others (Calendar, Message, Files, calculator) are okay in Dark theme.
Trying to verify for a new update results in an error about the internet connection (which is actually OK)
For me it worked out well, too. Could download the update this morning and installed it without problems, now on 0.12-2020102981459 and came from 0.12-20200930…
I have made the automatic update on my FP3 when I received the notification.
However, after the restart, I got the normal fairphone screen loading and then black screen message with “recovery” written and also “Can’t load Android system. You continue to get this message factory data reset and erase a device”
From your build date (0831 = August 31) I assume you bought your Fairphone 3 with /e/ preinstalled and with that would be on the “stable” channel of OS updates, because there’s a “dev” channel build from August 28 and the “stable” channel gets updates some days later with more testing by the “dev” channel users, who have installed /e/ on their phones themselves.
The latest update just got rolled out to “dev” channel users.
If my assumption is correct, you’ll just have to wait a bit.
Thanks for the hint! I thought you always have to flash magisk again with adb. I forgot to uninstall Magisk before the update but it still worked just fine.
You don’t need to uninstall Magisk. It does need to be installed into the new slot but MagiskManager can do that for you by copying it over. I also have a rooted FP3+ with the development version of /e/ q and I am waiting to see if the same thing works on that.