I think I must have been one of the few FP3 users to have installed the previous v0.12 release successfully, and I upgraded to the new release this morning. The status bar reverting back to the “old” design is very welcome - I didn’t like the new design at all!
What’s not so good is that the version of microg still hasn’t been updated. The packaged version is now a year old(!) and there have been three releases in that time. We’re missing Exposure Notifications and all kinds of improvements in mapbox, UnifiedNlp, etc.
Like most reasonable citizens, I see it as a civic duty to participate in suppressing Covid-19. Exposure Notifications are almost essential for day-to-day life now and this situation is getting extremely frustrating.
I have a refurbished galaxy S7 preinstalled. I made an upgrade to /e/OS 0.11-2020082870470 - Android 8.1.0 via TWRP (e-0.11-o-2020082870470-dev-herolte.zip).
Since then, I saw that there was a OTA available = /e/OS 0.12-2020093076269 (789Mo). But if I click on install, it reads “you are about to install /e/OS 0.11 - 30 sept 2020” (OTA downloaded is 0.12).
If I click ok, I get an installation error message.
Does it come from my device or from the last update problems?
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”
Right, I tried to install the last update based on the automatic notification I received on my FP3.
I must admit it was a bit painfull for me to install /e/ on my FP3 at the begining an now I am a bit lost with the suggested procedure to change the booting slot. Is there a tutorial or something likewise?
I think in the post it is described rather clearly. First, connect your device to your PC and start a command window. If you have fastboot/adb installed it is just the two commands that are mentionned in the post, hopefully!
Assuming you have Windows fastboot getvar current-slot
depending on the answer set it to the other one with: fastboot --set-active=a or fastboot --set-active=b respectively.
Is that instructional enough for you to follow or is something still unclear?
Ok your on the right way, I forgot to mention your phone has to be in fastboot mode but you did that anyway
Your device being locked is not standing in the way of changing the slot! It seems to me that your Computer does not recognize your phone somehow you could try the following to list all connected devices and to see whether your computer knows the phone is connected: fastboot devices
and additionally: adb devices
If you tried to boot from both slots about three times and always get this error someone else has to help you as I am also not really advanced in these issues … at all
Apparantly, it sometimes helps to try booting from the same slot several times but that is the last thing that I know could work
Currently there are three different versions of the 0.12 build at: https://images.ecloud.global/dev/FP3/
I do not know which one is suggested if you look for updates on your phone, so OTA, but this morning I succesfully updated from 0.12-20200930… to the newest 0.12-20201029… an it worked perfectly smooth.