Yup, didn’t think it was gonna happen… I did a test install on my old Fairphone 4, which is running e/os with no issues. But with the FP6 it got to the last stage and then went in to the dreaded fastboot loop. On reflection I might have done better using the manual install.
In both instances I used the web installer via Windows 11, Microsoft Edge browser. Most recent Android security patches were present on both devices. From memory, both the Android and e/os security patches were dated 5/6/26, which I understood to be a non-issue, after reading the e/os had to be at least the same, if not newer.
The bootloader is still unlocked so I haven’t sent it back to Fairphone just yet. I understand you can flash it back to the stock Android OS if it’s still unlocked. The issue now is I can’t get the FP6 to appear on adb devices. I’ve got the platform tools downloaded, as well as the Android adb/bootloader drivers installed via Device Manager.
Any ideas for helping my PC find the device? Or should I admit defeat and send the handset off?
edit I have been able to locate the device via the fastboot devices command, and the oem device info returned the following:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
Finished. Total time: 0.006s
