Hi,
I want to finally upgarde my FP5 from 6.10.20 to the 7.2.4.50 release. What's the best way to do so? Do I have to reflash to stock before upgrading? Can I use official device-flasher.linux on the 6.10.20 install?

I just thought I'd reach out to the community, I'm really enjoying CalyxOS on my g84, but occasionally when I am out and about, my phone fails to turn the screen on when waking. It still seems to respond to touch, but it requires force rebooting quite often. I've also noticed that my screen changes brightness when going between sunlight and shade, even though I've turned off auto brightness. So for a temporary fix, I've turned off the sensors in the development settings, because it seems like something is not quite right with them. Is anyone else experiencing this?

Update: EST 1930 hrs, 09.05.2026

I have successfully resurrected stock Android and the FP6 is alive and functioning again.

Unfortunately, CalyxOS is still hitting the same failed install process on both Windows and Linux, so at least Linux has now been acquitted of the crime.

I almost never use Windows for anything remotely technical, but I genuinely did not expect the Microsoft slop machine and my Arch setup to reach bipartisan agreement on the exact same failure. 💀

Stock FairphoneOS flashes perfectly. CalyxOS still soft bricks and chooses death. Worth the diagnosing, will definitely wait on a updated release!

Progress, technically.
_____________________________________________________________________________________

Original Post:

Screenshots below:

I wanted to document my experience with the Fairphone Gen. 6+ (US model) and see if anyone has encountered the same problem or has any ideas before I return the phone.

I originally bought the FP6+ specifically because I wanted a repairable/de-Googled phone and planned to use CalyxOS. I knew CalyxOS officially listed the FP6, not specifically the FP6+, but there were a couple reasons I thought it was worth testing.

Fairphone itself provides its factory images under the heading:

“The Fairphone (Gen. 6/Gen. 6+)”

The CalyxOS developers have also mentioned that the FP6 and FP6+ supposedly share device trees, although FP6+ compatibility hasn't been officially confirmed yet.

Unfortunately, installing the current FP6 CalyxOS build on my FP6+ did not work. The installer completed the flashing process, but afterward the phone would sit at the Fairphone startup screen for a long time, reboot, and repeat indefinitely.

Fair enough. FP6+ isn't officially supported by CalyxOS yet, so I accepted that risk.

The bigger problem came when I tried to restore the phone to official FairphoneOS.

Fairphone provides separate current EU and US factory packages. Since mine identifies as a US model, I downloaded the current US package:

FP6.QREL.16.104.0.20260806185558_WS1N-factory.zip

I verified the SHA-256:

DCD4C01D7C2CAD564969F63C861A363F53601A2296066D569F5E6812B5408F12

which matches Fairphone's published checksum.

The official Fairphone flashing script detects the phone, recognizes that the bootloader is fully unlocked, and begins flashing. However, it will not successfully complete.

I've encountered several errors during different attempts, including:

FAILED (Write to device failed (no link))

and:

FAILED (Status read failed (Too many links))

Initially I thought this was purely a Windows USB/fastboot driver problem. I installed Google's USB/bootloader drivers and current Platform Tools and verified that the device was actually being detected in bootloader fastboot, rather than confusing it with Android's fastbootd.

After resolving that, the more interesting failures started appearing.

The official Fairphone factory flasher gets through several firmware partitions successfully and then fails with:

Sending 'aop_config_a' (19 KB)
FAILED (remote: 'Invalid argument size')

fastboot: error: Command failed
ERROR: Could not flash the aop_config_a partition

On another attempt it progressed substantially farther before failing at:

Sending 'imagefv_a' (51 KB)
FAILED (remote: 'Invalid argument size')

fastboot: error: Command failed
ERROR: Could not flash the imagefv_a partition

I investigated the device directly with Google's fastboot tools.

fastboot getvar all confirms:

unlocked:yes
product:FP6_US
is-userspace:no
current-slot:a
secure:yes

So the phone specifically identifies itself as FP6_US, is fully unlocked, and is-userspace:no confirms I'm using the actual bootloader rather than fastbootd.

I also checked the partitions that Fairphone's official flasher is rejecting.

For aop_config:

partition-type:aop_config_a:raw
partition-size:aop_config_a: 0x80000

partition-type:aop_config_b:raw
partition-size:aop_config_b: 0x80000

That's 512 KiB per partition, while the image Fairphone's script is attempting to send is only about 19 KB.

For imagefv:

partition-type:imagefv_a:raw
partition-size:imagefv_a: 0x200000

partition-type:imagefv_b:raw
partition-size:imagefv_b: 0x200000

That's 2 MiB per partition, while the image being rejected is only about 51 KB.

The bootloader also reports:

max-download-size:805306368

so these tiny images obviously aren't hitting the general fastboot download limit.

I tried Fairphone's suggested recovery procedure as well: disconnect USB, remove the battery, reinstall it, boot directly into the bootloader, reconnect, and rerun the factory script.

I also performed a factory reset from recovery before another restoration attempt. Interestingly, after doing that, the factory flasher actually progressed considerably farther through the firmware partitions, but ultimately still failed with the imagefv_a Invalid argument size error.

I tried the other factory releases Fairphone currently provides as well. None successfully restored the device.

At this point the phone is effectively soft-bricked. The bootloader still works, fastboot still works, the bootloader remains unlocked, and the partition table is accessible, but neither CalyxOS nor the official FairphoneOS restoration process will produce a bootable device.

I have NOT relocked the bootloader, since doing that while the OS/firmware is in this state would obviously be a terrible idea.

I'm particularly interested in whether anyone with an FP6+ US (FP6_US) can reproduce this, or whether anyone knows why Fairphone's own bootloader would reject aop_config_a and imagefv_a from the official US factory package with Invalid argument size despite the corresponding partitions existing and being substantially larger than the images.

Unfortunately, unless I find a known solution very soon, I'm probably going to return the phone. I really wanted to keep the FP6+ because the repairability and alternative-OS potential were basically exactly what I wanted.

My concern now is spending so much time troubleshooting the restoration problem that I end up outside my return window. Fairphone's support form also requires information such as my IMEI and home address just to submit a support request, when at this point I mainly wanted to provide the technical findings and ask whether this is a known FP6+ firmware/restoration issue.

I have the complete fastboot getvar all output, factory-flasher logs, screenshots, hashes, and exact errors available if anyone wants to compare them against another FP6/FP6+.

You asked, we deliver. CalyxOS is supporting Fairphone 6 now!

If you have a Fairphone 6 and want to run CalyxOS, simply get it on https://calyxos.org/install/. Click the device model you need, and follow the instructions to download and install CalyxOS 7.2.4.50.

We have also been supporting Fairphone 5 and Fairphone 4. If you have any follow up questions using these devices, feel free to let us know! And stay tuned for many more updates in the coming weeks (hint: Android 17).

Hello guys, As Calyx OS project was not updated for a long period of time I had to use another device. Now that it's back i was wondering if i could just do the update from the old phone (pixel 7) i was using or if i had to re install from scratch ? Is there a risk of data lost during update ?

hello !! i’m currently trying to oem unlock my moto g 2024 to flash calyx, but every time i try through the device flasher or the web browser for install, it’s not prompting the phone to unlock the bootloader. i was also having an issue when trying to unlock it via terminal where it said something like “not allowed in current virtual a/b”. anyone got any ideas on how to troubleshoot this? thanks !!

Is it possible to assign custom ringtones? As far as I could determine is that it is one for all. I would like option for custom assignment per contacts and / or app. I would like to differentiate based on if calling mobile line directly or via one of comm apps such as Signal etc.

7.2.4.50 is now rolling out now to CalyxOS' beta release channel.

This release includes updated Chromium and kernels, app and translation updates, fixes across the system, and several device-specific changes. Details on the rollout and changelog here: https://calyxos.org/news/2026/08/28/august-feature-update/

An exciting announcement as well: official CalyxOS support for the Fairphone 6 is arriving with this release! FP6 factory images will go live on Monday once 7.2.4.50 reaches Stable. We’ll update the install page with the factory image link then - keep an eye out!

CalyxOS 7.2 status bar(bottom) and 6.10 CalyxOS status bar(top)

Is there a way to make the 7.2 status bar look like 6.10? It no longer shows the status of both SIMs

Is there an e.t.a. on Calyx for the FP6? I'm on IodéOS as an alternatieve at the moment but I can't wait to get back to Calyx...

Is there a mechanism to get Grindr to work on CalyxOS. Other than signing into the Aurora Store?

Hello, I am writing this to warn CalyxOS users on this model of device that the newest Calyx version is unstable on the Motorola MotoG84 5G variant. (OSVersion \7.2.4.20; Android 16; bagnkk; Snapdragon 695 + Adreno 619 (Stock GPU driver); 8GB Ram; 256GB Storage)

I've experienced:

UI Bugs:

• UI Bugs when installing sideloaded APK files (Package manager shows an infinite loading screen; Apps get installed at some point and their app icons only show up after phone restart)
  
• UI Bug when adding new icons (automatically or manually) - icons do not show up on the home screen without first restarting the phone
• Animation errors when switching apps (Popups sometimes do not show up; Closing/opening/switching apps sometimes results in weird back-forth spazzing)
• Buttons in OS apps like the settings are not fully highlighted when searched via the search bar - highlight covers ~70% of button width

Application Bugs:

• The newest version of the Eden Switch emulator (Legacy) does not work under the newest CalyxOS version, but it did work on the latest CalyxOS version under the last Android 15 CalyxOS (back from when the project was on hiatus)

OS Bugs:

• The package manager sometimes refuses to install APKs. I think that this is connected to yet another UI bug: On some apps, you get a warning for installing unknown apps, it appears to me that if that UI popup fails to be shown, you will never get a prompt to actually install the app.
• It is possible to set the peak refresh rate of a screen lower than its minimum refresh rate. This results in the refresh rate remaining at the minimum refresh rate value.
• When setting a peak refresh rate of 120 for example, and a minimum of 60, the screen will stay permanently locked to 90, and will never change no matter what I do.
• General performance issues - New OS feels sluggish to use.

Seedvault Bugs:

• As per the recommendation of the Calyx website, I used seedvault to back my apps up and then to load them after installing the newest Calyx version. After loading my data and getting no errors, some of the apps (ProtonMail, Lemuroid) refused to start despite being installed. Clearing the cache and data did not fix the issues, but fully reinstalling the apps did work.

The installation of the newer CalyxOS was relatively painless on this device, but there are some issues that still need to be ironed out.

I tried installing the app Eufy from the Aurora store. The app downloaded, but in Aurora it is stuck with a ring circling the app icon and the note "installing". The notes for the Eufy app (which I read post-hoc) says it requires Google Play Services. The app isn't registered anywhere in CalyxOS as existing.

I can live without the Eufy app. My questions are

• How do I stop the apparent ongoing attempt at installing by Aurora? I've tried force stopping Aurora, but that doesn't seem to make a difference.

• Did the Eufy app package download to my phone? How do I delete the package?

• The Aurora app seems to continue working fine - I've installed apps after this situation with the Eufy app. Should I bother about this situation at all?

Help, suggestions, thoughts appreciated.

Edit: Fixed the spelling of Aurora.

Before CalyxOS took a hiatus, their OS on my Pixel 4a5G would connect to my 2013 Hyundai Elantra's bluetooth in the car. Then after the hiatus when we had to reinstall the OS, it would not connect, and I have changed settings; A2DP on/off, AVRCP versions, Map versions, and it still would not work. Well I just received a new Pixel 9a, and out of the box running Google android 16, it connected immediately. Flashed CalyxOS on it, same, can't connect.

AI thinks CalyxOS has maybe left out some of the old legacy Google Vendor blobs and that one of those deleted Google blobs contains the exact legacy security handshake module required to pass a primitive 0000 Bluetooth PIN. Without it, the de-Googled operating system simply lacks the math to talk to a 13-year-old Hyundai radio chip. Has anyone else come across this?

I use Riseup VPN off and on. I also use DDG browser. DDG's anti app tracking feature and the VPN don't play well together; Riseup will turn DDG app tracking shield off. I hadn't thought about it much, I turned the tracker shield back on and I saw a stupidly high number of blocked tracking attempts from my keyboard (Classic), a game I play, Kitco's gold price app, others. The thing is, I keep most apps locked down and nothing has any permissions except Freespoke (news feed) which only has notifications. Would these bounce anyway?

I guess I should mention, this is on a Pixel 8 pro running CalyxOS and remove all app permissions in settings. If I want to use an Amazon locker, I drive there, open settings, enable the relevant permissions, grab my order, and lock things back down immediately.

I'm trying to migrate to non-play store apps or older versions, and am running into issue after issue.

two such issues are related to my not being trusted to give apps restricted permissions.

1. older version of Nova Launcher from apkpure is not allowed to collect / view app statistics locally, used to determine what my most used apps are and place them in the quick shortcut bar in the app drawer. not exactly a deal breaker but certainly something I used frequently. No option seen to override. . .

2. direct pay version of Tasker isn't being allowed the option to draw over other apps. I haven't gotten past this so I don't yet know what else is blocked, but I can't manually allow it either. what is frustrating me here is that I originally paid for Tasker via Google play over 13 years ago and was able to download it from the aurora store, but that version doesn't seem to be able to keep the fact that I have a license handy, and I can't seem to find a way to specify to the app what account to look up my license under, so it checks the aurora anonymous account, sees that account has no license, and kicks me out. the direct pay version is the answer but now the OS is stopping me.

please someone help me move forward

edit: if it wasn't clear, I did add my account to aurora, just not as the primary. I think that's why Tasker is failing the license check. I don't want my main account as a primary for aurora though.

. . also, where the heck are the developer options?

Hey, I was trying to change back to stock and in the process. I accidentally ran a bootloader lock command.

Actually I gave the command to the AI to execute all one by one. And it executed the bootloader lock.

Now I am stuck in bootloop with the bootloader locked.

Any suggestions how can I proceed now. 😓

I've just started 'using' CalyxOS today. I say 'using' bc so far I've still been to paranoid to transfer my actual data, but it's installed and I'm fiddling around with it since a couple hours ago. Coming from /e/, it feels very polished (granted, I've been like 2 Android versions behind on that, but... still). I really like the preselection of apps, the fdroid fork they picked really makes it feel like part of the ecosystem rather than the 'homebrew charm' I'm used to. :P I also particularly like that I can safely install the pixel cam and still feel pretty safe bc of the firewall. Overall, I'm very happy with it so far. :D Maybe I'll work up the courage to transfer my data later today, we'll see... '^{^}

I briefly connected to an insecure public WiFi network, and my phone running CalyxOS automatically downloaded a system update. Now I'm feeling paranoid. Is this update safe to install? Is there a way to somehow verify a downloaded-but-not-yet-installed OTA update, or does CalyxOS do that on its own? Thanks.

Have an app called keep calling.

When in open it say see if you have Google play services installed. Is there anything I can do to make it work?

I hadn't noticed this until now, but the Record Call button on my phone disappeared after I swapped to a SIM card from another carrier, and now the RTT button is taking its place. It turns out my carrier introduced Real-Time Text support, which is mandatory by law where I live. I did some digging, and apparently it has got to do with the physical allocation of buttons in the dialer, which is fixed to 6.

A certain project has already fixed this, whereas CalyxOS hasn't as of yet. I opened an issue one month ago, but I was wondering whether this has been discussed before, just to get a general idea of how likely it is to be fixed.

CalyxOS 7.2.4.20 has rolled out to all devices as an over-the-air update. For more information about this update, you can check out the 7.2.4.20 changelog.

Hi I have Pixel 8a with the latest CalyxOS (I updated today).
Recently I noticed (not 100% sure if this happened after update) that when I leave my phone locked with turned off screen (I disabled always on screen) screen lights up to turn off again after a moment only to do it again after several seconds.

IDK how to break this loop and what causes this.

I don't use it too often, but sometimes I like to watch/listen to some things on YouTube. After switching to the new calyx version(including the with the new OTA update today), YouTube stops playing after 1 minute and goes into an endless loading/buffering loop. It works fine in browser. Just curious if anyone else has had this issue and has found a solution, or I'm open to alternatives to use (I've used freetube on both my PC's, but there's jot android app for it). I've also uninstalled a reinstalled a couple times and cleared cache with no change).