3.0 was withdrawn due to an issue, 3.0.1 was/is released for Community builds and should follow for Official builds soon.
The release date was changed by a short amount for Official builds if I recall correctly.
You won’t find the withdrawn 3.0, but 3.0.1 after it is available.
That issue was critical (rebooting systems directly after entering unlock / pincode), so the withdrawal was quite necessary.
Hi,
Fairphone 5. currently on 3.0.
Before the update I had an app installed and normally used (1&1 control center). Now after the update the same app complains, that the Phone is rooted and refuses to start.
The phone is not rooted.
Any idea?
Oliver
P. S. The bootloader is open since last year when I installed EOS. Does it make sense to close the bootloader?
Closing the bootloader will erase all data, you will need to restore. Then it could work or it can’t.
Are you sure that the system update caused the issue and not some app update you made because of auto update?
Hi,
You are right - there was an update of that app.
To bad, that I didn’t save the old version.
I will remove this app for now.
I can deal with deleting the data. The question is, how can I safely lock the booloader. I didn’t do that last year to make sure, that the anti rollback ,feature’ will not destroy my phone. But as this is now long over this should not be a problem.
Regards
Oliver
Yes did see some devices with serious problems.
S7 was not one of them, but better save than sorry.
Hi Oliver,
You can use Aurora Store to install older versions: search the app and select ‘Manual download’ (‘Version auswählen’ in German). The only problem is that you have to provide a version code.
Guessing a valid code might be time consuming, but you can use apkpure for research:
Open apkpure.com in any browser, search your app. Scroll down to section ‘Old Versions of 1&1 Control-Center’. Current version is 6.17, let’s try version 6.16.2. Click on the desired version (NOT the download button) and scroll down to the All Variants section. The version code is displayed behind the version number: 5024.
You can determine the version code for other versions the same way, i.e. Version 6.16.1 has version code 5016.
Now back to your phone and Aurora Store: enter the version code of your preferred version and click on ‘Install’ - done.
A direct app downgrade will probably fail - you have to uninstall the current version first and set up the app from scratch afterwards.
Regarding the bootloader: Personally I would wait until version 3.0.1 Official will be available for FP5 - the staggered release of official builds starts tomorrow. Locking the bootloader on a system version where other users have massive problems is not worth the risk.
Good luck!
What about current data on the phone?
Locking is pretty easy if you have proper cable and fastboot installed
Thank you for clarifying post #203 and for pointing out that a phone with a locked bootloader should, in theory, be able to accept a proper OTA update automatically.
However, here’s what actually happened in my case, step by step:
Along the way:
fastboot set_active works (my bootloader is locked, so I can’t manually flash partitions).adb sideload does work, but the problem seems deeper (system corruption? Slot mismatch? Build conflict?).So even if OTA updates should automatically handle the active slot switching, the reality is that moving to any version of 3.x has severely broken my system, and my phone is now completely unusable, stuck in a boot loop.
I’m essentially left with a soft-bricked phone. I can’t flash anything, can’t access the OS, and I’m unable to retrieve some important data. It’s a deeply frustrating situation.
Hi @WikiTang I am sorry to hear that your situation is still unresolved. You do know that as a Customer you could use the Contact us form at the foot of this page Contact Us.
Vendor Name Asus
Device nme Zenfone 8
Device CodeName Sake
Version of /e/OS or Stock which existed previously 2.9 T
device Not rooted
Everything works good so far.
Question: where is the OTA update on our second device? It is an FP3+ running 2.9-t. My own device (FP3, then also 2.9-t) had the OTA update already six days ago. Why the difference?
Hi,
thank you. I didn’t know, that Aurorastore can be user to install older versions. I will check that out.
As for the bootloader - I will wait for 3.01 to be sure.
Best regards
Oliver
Yes, thank you, but I think it’s more useful to keep an eye on things here.
The “contact us” will just offer to send my phone to be factory reset. I can do that myself.
Samsung
Galaxy S7 (SM-G930F)
herolte
before: 2.9-s-20250321478216-official-herolte
for a short while: 3.0-s-20250528496287-official-herolte
now: 3.0.1-s-20250609498926-official-herolte
not Rooted
Only thing is that Parental Control still cannot be activated, issue 8625 persists for the time being. Not a showstopper for me as I do not need it anyways.
Thanks a lot for keeping that hardware alive!
Factory reset is the only option I can think of because I cannot think of a method to extract any data while your phone is in a “locked, always fastboot” loop. I hope that perhaps someone here might offer some help.
However “Contact us” will get your issue to the devs who have worked on the problem and they might have an idea.
I suppose your Bootloader screen does confirm that the device is still locked?
The traditional way out of a loop is to try to boot to Fastboot mode but ask nothing else. Will your phone achieve this?
I doubt it is your case but a loop can be caused by the phone wanting to complete some impossibility loaded in memory. In this case removal of battery can bring you back to stable Fastboot.
These two suggestions do not lead directly to a solution, but knowing that the loop can be eliminated might lead to something else.
Incidentally switching between official and community on FP3 at this time (I think) should be an impossibility with a locked bootloader so perhapsl I suggest do not try that particular manipulation again.
v3.0.1 official builds rollout has started. Again it will be staggered across the devices. Which means not all official builds will be released at once.
OTA-upgrade to 3.0.1
1st and 2nd device:
3nd device:
Everything looks fine so far.
Thanks /e/-Team 
I’ll get back to you. Well, I have a good news. I don’t know what happened but last night I was on internet and my battery level started to discharge. I noticed that the battery drain was slow now. I will check again today. If you don’t hear from me about this issue, that means it’s okay.
However, I can’t use your browser with my IP address exposed. I have to enable IP address hiding to be able to connect and browse the internet with your browser. If I disable the option in Advanced Privacy, I don’t have an internet connection. Is this normal ?
Otherwise, I haven’t encountered any problems so far.
Regards.
Have you checked VPN-settings related to Advanced Privacy? Maybe something fishy can be found there?
Yes.
VPN settings → Advanced Privacy Connected → Permanent VPN (grayed out) and Block connections without a VPN (grayed out). I can’t modify these options.