Okay, it can be closed, after installing another ADB Driver it worked

@Stemy I had the same issue. I rescued by bricked phone by installing android 10 (accroding to https://support.fairphone.com/hc/en-us/articles/18896094650513-Install-Fairphone-OS-manually#01HB8ZZ1BMMQNSNMFT3YXDBXA0) and afterwards I installed ubuntu touch via the UBports Snap again. The error still appeared after the installation but now my phone boots without any issue.

@Kjetil you can't browse it. You need to access it through ADB using the terminal. Connect, mount data, transfer data using adb pull. There are some instructions for backups with ADB here in the forum somewhere.

Update : After several tries Ubuntu starts on my FP3. I loved Meego Harmattan and my N9 I used a FP2 with UT, and liked UT I used LineageOS on my FP3 (I don't like Android) Now using SailfishOS on my XA2 (And love SailfishOS) No I can use UT on my FP3, nice. Next PureOS on my Librem 5 and Sailfish/UT/Mobian on my Pinephone

Hello @hehip, for helping we would need to know more information. How long have you been waiting for installer before you decided to turn it off? In some steps there is need to watch your phone and confirm actions the installer made in fastboot. For example you need to confirm "Reboot to recovery" manually on your phone. I think installer claims it is "flashing firmware" but in reality it is waiting for recovery to boot up. Today I successfully flashed FP3 from Linux using installer 0.10.0, maybe you can try Appimage if snap version is older one. You can read my latest experience here: https://forums.ubports.com/post/79146

I managed to take some time and verify my findings. It looks like I made mistake on first installation because today I managed to flash Focal directly over FPOS. So right now my flashing procedure was like this: Download and Fairphone OS based on Android 10 Flash Fairphone OS without locking bootloader Boot into Fairphone recovery and erase user data as requested Reboot to Fairphone OS welcome screen Reboot to Fastboot mode Use Ubports installer and let it do its job with Focal/stable branch

@Br1 oh nice, I will try to make something out of it.

Salut Kristien, Ah, MMS struggles. You aren't alone. I can't speak to Fairphone 3, but I had to play around with settings for a while on my Oneplus 5 before things worked. You could try to find alternate carrier APN information and try different options. Upon searching APN info for MMS Free I see what you typed in, but I also see some sites listing other things, such as: MMSC: http://mms.comee.com Nom du point d'accès: free Nom du point d'accès: free.re It was a struggle for me, but eventually I got mine working after enough trial and error, though I still need to restart MMS once in a while when it suddenly stops working for reasons I don't understand. To restart MMS, open terminal and type: initctl --user restart nuntium

[image: 1694623649850-screenshot20230913_183137396.png] Work with Peltor WS5 Workstyle Headset.

@Homer3 about WiFi: I cannot confirm the loss, of the connection. But I sometimes see, that the WiFi-indicator is displayed as "empty" after some time, like no or week signal. But the connection is still there and I can browse the network/internet still. Besides that, I re-testet the upgrade process myself. It seems that it generally downloads the latest Xenial-devel-build first. After selecting 20.04-devel in the OTA-channel settings. After that, I opened the OTA-channel-settings again and selected the 20.04 devel again and then it downloaded the latest Focal-devel-build. As a result, now two updates were displayed, which I could "install". I selected the second one (Focal, with the lower build number) and the update went well, without any freezes or other issues. Though, one must know that, to not accidentally install the first downloaded xenial-devel-build... I wonder if maybe some migration-processes slowed down your phone, maybe lots of music or similar, which needed to be indexed.

@TypoSpotter Wait! you've reflashed stable and it works?

@Kutzi there is already a focal-port. I am Using it for months now. Just needs an update-channel to make it available to all users.

@luksus thanks for your answers. I have just finished installing UT and the installation was seamless. I'm impressed with this ubports-installer.

It is definitely some hardware-specific issue. I would not go as far as calling it a feature. Maybe because of low power, there is entered some specific bootmode and our halium-stage cannot handle that right or whatever. Though on a quick investigation in the FP3-android-device-source I could not see any obvious passage for this hypothetically case. Maybe someone could investigate differences in dmesg init logs or journalctl with and without low battery. I don't see other possibilities to find the root cause for this behavior. Besides that, that issue is very low priority on my list. It exists from the very beginning and I know how to avoid it, what makes me not putting too much energy into solving it.

I confirm this issue on my FP3+, 100% times when I boot it under 10%. Additionally, it's exactly 10%, so it seems either firmware or UT software. If it were hardware, I would expect this 10% to drift over years (with the battery getting old), or being slightly different on different devices.

@homer there are no bugs about any of that on github, you should report it so more people who develop or work on the app can know about the bugs, and try to fix it.

@luksus I don't think I enabled adb while in developer settings. So this part was probably my mistake

@domubpkm works well for me thanks