Troubleshooting Installing CalyxOS in FP5 from Windows

CalyxOS install on a FairPhone 5 from a Windows PC

Follow: CalyxOS FP5 Windows Install Guide

Calyx OS installation issues:

IF ANDROID BRICKED at any stage, revert and start again: Fairphone OS Manual Reinstall Guide

Make sure to use a proper USB port and cable (see forum threads):

  • https://forum.fairphone.com/t/phone-stuck-in-fastboot-mode-unable-to-install-fairphone-os/114054/4
  • https://forum.fairphone.com/t/i-hate-it-how-to-install-calyxos-on-a-fp5/115656/15

Easy steps → Enabling debugger options → Enabling USB debugging. Then enabling OEM takes us to:

Unlocking bootloader

Enabling OEM settings asks for a UID and internet connection, the UID depends on some hash given by the SIM card slot 1 IMEI and the model and hardware. Get the code from the official Fairphone site:
https://www.fairphone.com/en/bootloader-unlocking-code-for-fairphone/

If stuck at any point of the process waiting for fastboot

Using the Google USB Driver (https://developer.android.com/studio/run/win-usb) in windows may be a nightmare. To unlock the bootloader (and fix any other getting stuck issues) follow the driver update steps, you should find the driver for the FP5 in Windows Drivers with a warning sign:

In Device Manager, right-click the problematic device entry → "Update driver" → "Browse my computer for drivers" → "Let me pick from a list…" → Find "Android Device" if listed, select "Android Bootloader Interface". If "Android Device" isn’t listed, choose "Show All Devices" → "Have Disk…" → browse to the android_winusb.inf file within the unzipped Google USB Driver folder. Select "Android Bootloader Interface" from the list that appears.

Basically, tell Windows to understand the FairPhone again. If it happens multiple times, rinse and repeat.

General the more reliable way is this

1 Like

Yes, this can also achieve that, great job!

Although there really is no need for anything other than the win_usb android files. Correct me if I’m wrong, but what you suggest is more than what is needed, isn’t it?

No its not more than needed, its just the most reliable way to install fastboot driver. Updating through device manager was often reported to not help/work

1 Like

ah I see, probably because you need to do it more than once to keep the installer going, so it’s cumbersome and unintuitive… But that’s windows for ya! lol

what steps would I need take to determine this?

I’d say toggle between different ports and use a different cable. This is based on the mentioned posts, other users report changing and having success. USB ports are a world in and of itself, there’s different bandwidths, power directions and capacity… etc. I think I used a USB 2.0 port (the one with the grey / white flap) but other users seem to report success using USB
3.0 (the one with the blue flap). Users that had issues usually went from the 3.0 one to the 2.0 one. Usually 3.0 ones are at the front part of computers (for data devices) and 2.0 ones are at the back (for things like keyboard and mouse, that don’t need the increased capabilities).

Here are two pictures for further reference: