[RESOLVED] FP6 Sim 1 Not allowed in e/os 3.1.2 EDIT: NOW FIXED

[jeremyet]

Hello

Got the 3.1.2 update this morning. After rebooting my fairphone 6 showed a ‘Sim 1 not Allowed’ notification and I can’t access my mobile network. All worked fine before update and I haven’t changed network settings. :

EDIT: Added bug report in github

EDIT: 3.1.2 Build dated 3 Sep rolled out in the early hours and fixed this issue.

Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online services

[Raxay]

Yep same problem here.

It’s also in the feedback thread: Feedback for v3.1.1 - #121 by Raxay

You might want to check the IMEI numbers in the SIM card settings. That may be the cause based on the discussion in the above thread.

Suggested mitigation steps were tried but nothing has worked so far. IIRC FP6 also doesn’t support a rollback of the update to a previous version, so it’s a waiting exercise for the time being.

EDIT: Adding my initial report from here.

@Raxay

        Vendor Name: Fairphone
        Device name: Fairphone (Gen. 6)
        Device CodeName: FP6
        Version of /e/OS or Stock which existed previously: 3.0.4-a15-official
        Not rooted

Received an OTA update for 3.1.2-a15-20250828521531-official-FP6, device rebooted after installation.

Since then the Slider button has no functionality and both IMEI codes are not read correctly.

IMEI1 (before update): 3590**********
IMEI2 (before update): 3590**********

IMEI1 (after update): 004400152020000
IMEI2 (after update): 004400152020000

Needless to say, after this the network provider rejects any registration of this device, leaving me without phone functionality.

When checking the bootloader via a power on + Volume down, I can see that the IMEI is still shown correctly.

On the good news side of things, Revolut works again. But I cannot log in cause I cannot get the SMS anymore.

Any input for the IMEI problem is appreciated!

[satse]

In these situations roll back would be great. Many cases it might be good security feature, but right now it makea my life harder.

[mihi]

Are you part of the testing group?

If yes then please don’t post informatuon about it. It confuses others and create lots of unnecessary posts.

If you are not part of testing group, then let us know if there was something available which should not have been.

[Raxay]

Hey @mihi , I’m not part of the testing group and the testing option is specifically disabled in the Developer options.

Based on your comment I’m assuming that 3.1.2 was not supposed to be publicly available? The update came to me over the normal Update application.

EDIT#1: Full e/os version: 3.1.2-a15-20250828521531-official-FP6

EDIT#2: The official image download page also shows this image as the latest one. /e/OS official FP6 download

EDIT#3: Confirmed that 3.1.2 is supposed to be in the testing channel only: Install e/OS on Fairphone 6 - #82 by mihi

[jeremyet]

Not part of any testing group - update appeared this morning in system updates

[Antti]

Got the update to 3.1.2 half an hour ago. Now I have the ‘SIM 1 not allowed’ notification. I have the e/OS that came with the Fairphone 6 purchase, I am not part of any testing root nor have I customized the OS.

Disappointing. Can’t use my phone anymore.

[mihi]

Oh I see, the official release today surprised me kinda, I did not check the available images. Or better, I checked the community page which I used yesterday to install on FP6. So no mistake as it looks like.

[AnotherElk]

If /e/OS 3.1.2 has a security patch level of August 1, 2025 (has it?), and if anybody affected is feeling adventurous … (if you don’t instantly know what the following means, you are not feeling adventurous) …

• The /e/OS recovery can do ADB sideload.

• /e/OS install files on the documented FP6 download pages don’t work with ADB sideload, as they use fastboot to install. However, OTA files fit for ADB sideload are available on the OTA server (it’s what the updater uses to update) … https://ota.ecloud.global/api/v1/FP6/official/ for official or https://ota.ecloud.global/api/v1/FP6/community/ for community.

• /e/OS 3.1.1 is available on the OTA server and according to https://gitlab.e.foundation/e/os/releases/-/releases has the security patch level of August 1, 2025. If (big IF) 3.1.2 also has August 1, 2025, Android rollback protection shouldn’t apply.

I don’t have an FP6, and I don’t know whether the bug was already there in 3.1.1.

Edit: Also … different phone, but why not …

Calls are no longer possible

I found a solution to my problem. I set the APNs to default and then configured them manually according to the provider’s specifications! Nevertheless, it could have been caused by the update!

Edit 2: Nevermind, doesn’t seem to work …

@uzay

Still doesn’t work.

@luggage

no luck

Edit 3: ADB sideloading 3.1.1 doesn’t work either …

@Raxay

So that path is unfortunately a no go too.

[uzay]

Just got this update on the stable channel as well. Now my eSIM doesn’t work anymore. This needs a hotfix very badly, i.e. making sure the broken testing build isn’t pushed to more devices on the stable channel, and pushing out a fixed build for people who already installed it. I hope this gets resolved quickly because I can’t just put my eSIM in a different device and not being able to use my phone puts me in a pretty bad spot.

[luggage]

Created an account to add to this thread.

Same issue, no root on phone, no testing permissions etc., OTA update.

I have noticed that at least 3 people including me in this thread appear to be located in Finland, not sure if that might somehow be relevant.

[knowfrontiersmanroad]

same here:

Mobile data issues on FP6 'e-3.1.2'

Hi, I recently bought an FP6 and chose to have it preinstalled with /e/OS/. Everything was fine until today, where my phone suggested that I install the latest update of /e/OS, which is 3.1.2-a15-20250828521531-official-FP6. Being used to keeping my device up-to-date whenever requested (and absolutely not being an expert), I installed the update. Since then, my mobile data connection is very unstable and slow, H+ at best when it doesn’t completely disconnect. With the previous version (3.0.4 …

I’m not located in Finland. This seems to be affecting everyone.

[koki_123]

I have the same issue. I am not part of the testing group. I have a Fairphone 6.
My SIM is recognized including phone number but SIM is not allowed since the new update.
I cant get any connection to the SIM provider such that I can send or recieve sms or call someone or recieve calls or use mobile data.
Actually that is a major thing because actually the mobile phone is more or less useless besides using Wifi.
I am not located in Finnland.

[mihi]

Did all of you try to adjust APN? Not sure that is the root cause but worth a try

[uzay]

Just tried it. Reset to default (which is none), then put in the options as per the providers instructions, same as they were before. Still doesn’t work.

[luggage]

Just tried resetting and reentering the details, no luck.

[knowfrontiersmanroad]

https://community.e.foundation/t/mobile-data-issues-on-fp6-e-3-1-2/74510/13?u=knowfrontiersmanroad

[Raxay]

@AnotherElk

If /e/OS 3.1.2 has a security patch level of August 1, 2025 (has it?), and if anybody affected is feeling adventurous … (if you don’t instantly know what the following means, you are not feeling adventurous) …

• The /e/OS recovery can do ADB sideload.
• /e/OS install files on the documented FP6 download pages don’t work with ADB sideload, as they use fastboot to install. However, OTA files fit for ADB sideload are available on the OTA server (it’s what the updater uses to update) … Builds – Django REST framework for official or Builds – Django REST framework for community.
• /e/OS 3.1.1 is available on the OTA server and according to Releases · e / os / 🚀 Releases · GitLab has the security patch level of August 1, 2025. If (big IF) 3.1.2 also has August 1, 2025, Android rollback protection shouldn’t apply.

I don’t have an FP6, and I don’t know whether the bug was already there in 3.1.1.

So I was feeling adventurous and tried to sideload the package via adb & recovery, for anyone else, let me save you your time.

Misc information:

• The Security patch level of 3.1.2 is August 1st.

The update fails while verifying.

Update package is older than the current build, expected a build newer than timestamp 1756393669 but package has timestamp 1756281487 and downgradwe is not allowed

So that path is unfortunately a no go too. Theoretically it should be possible to do this with a fresh build of 3.1.1 though.

[AnotherElk]

Bummer. As if Android rollback protection wasn’t enough.
Thanks for testing.

[aibd]

@Raxay

I was feeling adventurous

One would have to be seriously adventurous to attempt to switch slots on a very expensive new phone. This thread does attempt to highlight the downsides [GUIDE] How to manually switch the active slot.