i noticed on the n100 you have to start up msm and have it ready use "adb reboot edl" and quickly hit start in msm before your phone reboots

Looks like this is probably the fix? https://github.com/mer-hybris/ofono-binder-plugin/pull/53

I had to install back a second time Android on my Fairphone 4, this time I've took some notes shared below. TLDR: LineageOS developer options pane allows you to enable Rooted debugging. This allows you to use the adb root command which start a rooted debugging session. Then you can use adb shell to open a console on the device and run restorecon -FR /mnt/vendor/persist to restore the SELinux permissions. From Ubuntu Touch, the easiest way to go to the fastboot mode, is to open the terminal application and run: sudo reboot -f bootloader Then, I used the Android 11 factory reset image provided by Fairphone (but don't do like me, see below). Then, I wanted to install LineageOS and they require to have Android 13/15. So, I opened Android 11, go to phone information in the settings application, repeatedly touch the build number until the developer mode is enabled. Go, to the system panel in the settings application, open the developer mode and enable the ADB debugging. On my computer, I go back to the fastboot mode with: adb reboot bootloader I've installed Android 13 factory reset image provided by Fairphone as I already have downloaded it for another experiment. Then I boot Android 13 and enabled usb debugging with same steps than Android 11 (see above). Then I've followed LineageOS instructions to install it step by step: https://wiki.lineageos.org/devices/FP4/install/ Then, with LineageOS, you can enable developer options with same procedure. The LineageOS developer options have two options: USB debugging and Rooted debugging, you need the last one to be able to run commands to reset correctly permissions on the hardware drivers. Then, on my computer I was able to run, adb root to start rooted debugging, open a shell on the phone with adb shell and run in this shell restorecon -FR /mnt/vendor/persist: $ adb root restarting adbd as root $ adb shell FP4:/ # restorecon -FR /mnt/vendor/persist SELinux: Loaded file context from: /system/etc/selinux/plat_file_contexts /system_ext/etc/selinux/system_ext_file_contexts /product/etc/selinux/product_file_contexts /vendor/etc/selinux/vendor_file_contexts /odm/etc/selinux/odm_file_contexts FP4:/ # Then you need to reboot and you can check this worked by enabling the automatic rotation feature: open an application and rotate your phone, the application should follow the movement

@gpatel-fr Weirdly that does work somewhat, but the process seems to be rather convoluted. Rebooting to the bootloader/fastboot from the adb shell allows the installer to detect the device, but while installing it eventually reboots to recovery and shows a 'failed installation message (error 256)', and then it auto-reboots into the 'System Updater' screen you'd expect from an OTA update. So something about the installer 'unblocked' my previous update attempts (?).

Hi guys, I'm truying to build Sota4ever_k repository for a Samsung Galaxy S20 FE (r8s, SM-G780F/DS, with Exynos) Is it still usable? Right now, it fails with lot of warning in openssl + make O=/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/KERNEL_OBJ CC=clang -j16 scripts/kconfig/conf -s --syncconfig Kconfig /home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/extract-cert.c: In function ‘display_openssl_errors’: /home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/extract-cert.c:46:9: warning: ‘ERR_get_error_line’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 46 | while ((e = ERR_get_error_line(&file, &line))) { | ^~~~~ In file included from /home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/extract-cert.c:23: /usr/include/openssl/err.h:426:15: note: declared here 426 | unsigned long ERR_get_error_line(const char **file, int *line); ......... lot of warning, and then..... 1 warning generated. /home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/drivers/video/fbdev/exynos/panel/sysfs.c:2358:21: warning: unused variable 'panel_data' [-Wunused-variable] struct panel_info *panel_data = &panel->panel_data; ^ 1 warning generated. /home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/drivers/video/fbdev/exynos/dpu30/decon_core.c:1200:38: error: use of undeclared identifier 'prev_state' decon_doze_first_frame_black(decon, prev_state, next_state); ^ 1 error generated. make[6]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/Makefile.build:333: drivers/video/fbdev/exynos/dpu30/decon_core.o] Error 1 make[6]: *** Attente des tâches non terminées.... make[5]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/Makefile.build:638: drivers/video/fbdev/exynos/dpu30] Error 2 make[4]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/Makefile.build:638: drivers/video/fbdev/exynos] Error 2 make[3]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/Makefile.build:638: drivers/video/fbdev] Error 2 make[2]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/Makefile.build:638: drivers/video] Error 2 make[2]: *** Attente des tâches non terminées.... make[1]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/Makefile:1144: drivers] Error 2 make: *** [Makefile:146: sub-make] Error 2 What can I do?