/e/OS Frustration, Flash FairPhone OS and Warranty

[ReplaceablePancake]

Hello forum, I hope this post finds you well.

So I have been using my new FP6 bought from its website with /e/OS for 10 days. Now, despite I’m loving the hardware (I have several accessories) I can’t stand de software for my personal use. I will go into detail later but, my questions are:

1. • Would root void the warranty?
2. • Would install FairPhone OS void the warranty?
3. • Would I get regular updates despite installing the software myself?
4. • Do you think it could have any advantage to return the phone on the 14-day return policy and buy a regular FP6 with no /e/OS?

So, I come from using a OnePlus 5 for 8(!) years with LinageOS and I expected this phone to be its successor with all the repairability and software updates.

But, I can’t stand the state of /e/os. Several reasons are:

1. • Privacy Monitor has no system-wide add-block installed.
2. • Default launcher created to be replaced, ultra limited (no icon move-around, no app drawer, no widgets…).
3. • Default Mail app not opening after being configured, based on FOSS K9-Mail which DOES work. It seems in fact like it has an old version of K9, (as I see in the interface) so:
4. • It could be guessed that all FOSS-based apps it has (DAVx5, Open Tasks, music app..) are outdated versions of their counter F-droid available versions.
5. • AppLounge wont let you add or see which repositories are configured, and there is no way to differentiate where are you downloading an app from. I downloaded VLC… from F-droid or Play Store?
6. • And some Play Store apps wont open at all, in a brand new non rooted device with blocked bootloader, and privacy monitor disabled for those apps. I checked with other forums that it is due to Play Integrity meeting ONLY Basic Integrity, which is also my case.
7. • There is a bug when changing from an app to another, where the screen is unresponsive so I have to use the “back” gesture to change what is shown on screen, and then comes responsive again. Happens on every app, so change recent apps is annoying and slow.
8. • Account manager seems to be DAVx5 based. It has an error where org.Tasks can’t be configured as default Task sync app, as it always defaults to Open Tasks (installed by default, not uninstallable).
9. • You know the cool yellow physical switch that FairPhone 6 introduces? On /e/OS it only disables/enables microphone and camera access. No more configuration. And it does not override settings configuration. If the switch is on “disable” position, you can still enable camera for example through settings, so the physical switch has no preference.
10. • This is one among a lot of difference between FairPhone OS and /e/OS.
11. • FairPhone OS software updates are not paired with /e/OS updates, so I would expect /e/OS to not be able to keep up with new functions developed by the stock counterpart.

So /e/OS to me is more like a “broken” LineageOS, the problem is that I paid for it. I could have FairPhone OS, install F-Droid/Neo Store and Aura Store and have the FOSS part of it. Then root it, remove/disable Google apps, install some Magisk Modules, AdAway, and have almost the privacy part I need.

Now, I want a FairPhone 6 but with no /e/OS and, aparently, I could install it myself. However, I don’t know what happens with the warranty if I do install it. Also, I would like to root the phone after that to disable/uninstall some Google apps. Also, I happen to be on the 14-day trial where I could return the phone.

If I could flash FairPhone OS with no consequence, I would do it because it is tiring to have it back, wait for the money, buy a new one… Also more less carbon emissions of course. My guess would be that FairPhone provides support for FairPhone OS shipped phones, and Murena to /e/OS phones, but since I will be using FairPhone OS I don’t know if I would (in the future) get their support.

So, ¿may you help me out with these questions? Any suggestion will be welcome as well. Thank you!

— Edit after responses —

So I will finally:

• Keep the phone.
• Flash original FairPhone OS.
• Root it and install what I need.

Warranty won’t be voided as referenced by @mike_1312 :
https://support.fairphone.com/hc/en-us/articles/14487777708946-Warranty-with-an-Alternative-OS

So I will proceed to carefully read and then follow the steps shared by @yvmuell .

Fairphone 6 unbrick: Trapped in fastboot mode with locked bootloader and corrupted stock ROM

It sure looks like it, although I can’t confirm that, as I waited for the new Fairphone Android update and associated SPL. However, I did see that letting it boot into Android post-flash caused get_unlock_ability to return 0, so it seems likely. Allow me to answer these questions with some (pseudo)code, which I think better highlights the order and results of my actions. Flash the Fairphone (Gen. 6) with the Fairphone Android OS. Locking the bootloader, part one (lock_critical)…

I will try to update about automatic FairPhone OS updates as soon as I had the availability to do the whole process.

I will report the issues with /e/OS to Murena, just to let them know about them.

Thank you!

[KoffieNu]

I’m no user of the fp6 (yet, saving), but what I read here is that you can flash the phone back to fairphone OS, but that you need to ensure the security level is the same when you want to lock the bootloader again.

Advantages of sending it back and getting a regular one would be that you’ll save €50, as the regular one is cheaper (but you get the hastle of sending it back, as you described). You could ask support if they have ideas in this case… sending an e/os back just for an OS swap to fairphone image seems a huge hastle.

As far as I know, rooting or flashing original OS should not void warranty. (at least not in EU)

[yvmuell]

@KoffieNu

I’m no user of the fp6 (yet, saving), but what I read here is that you can flash the phone back to fairphone OS, but that you need to ensure the security level is the same when you want to lock the bootloader again.

At the moment thats not sufficient, so at the moment you can reflash but not lock the bootloader most likelly or only with checking get unlock ability before booting into the system

Fairphone 6 unbrick: Trapped in fastboot mode with locked bootloader and corrupted stock ROM

It sure looks like it, although I can’t confirm that, as I waited for the new Fairphone Android update and associated SPL. However, I did see that letting it boot into Android post-flash caused get_unlock_ability to return 0, so it seems likely. Allow me to answer these questions with some (pseudo)code, which I think better highlights the order and results of my actions. Flash the Fairphone (Gen. 6) with the Fairphone Android OS. Locking the bootloader, part one (lock_critical)…

@ReplaceablePancake you bought where, Fairphone? We here are all user, so what exactly voids warranty is Fairphones decision. Normally you can do what ypu want as long as you can redo to proof its not the cause of the failure you want to claim while I guess having FPOS on the phone should not be any issue at all.

[mike_1312]

Regarding your points 1 and 2 you could have a look here if it answers your questions:
https://support.fairphone.com/hc/en-us/articles/14487777708946-Warranty-with-an-Alternative-OS
For your point 3 I’m not sure. So I won’t give an answer.
And regarding your point 4, if you are not experienced with unlocking, flashing and so on, I would use the return policy and take FPOS version.

No feedback to the /e/os issues, as I’m not familiar with it.

@ReplaceablePancake

I could have FairPhone OS, install F-Droid/Neo Store and Aura Store and have the FOSS part of it. Then root it, remove/disable Google apps, install some Magisk Modules, AdAway, and have almost the privacy part I need.

That’s what I did, and I’m quite confident with it at the moment.

[ReplaceablePancake]

Thank you for your response! Yes that’s the case, I would like to have a “New Stock FairPhone OS” with all that is to it (security, warranty and support).

I would ask support but I think I will not have a response in time for the return policy to be still applicable. I think I will check more responses and either:

• Process the phone return directly.
• Flash FairPhone OS and live with it. - Most likely, since rooting/flashing does not void the warranty as I read. It only voids it if I messed up the process and ended up with a FairToaster.

[ReplaceablePancake]

Thank you for responding!

Thank you for referencing the flash process! Just what I would need, I will save it for later.

I meant that I bought the phone on the official online store. Thank you for assuring that rooting and flashing the FairPhone 6 is not enough to void the warranty, as long as I can go back to the original state. Also makes sense that installing original FPOS should be fine.

[ReplaceablePancake]

Thank you for your time to read everything and responding!

You nailed it with the link, I did not find it before, and it explains perfectly my warranty questions.

Thank you for your feedback with your experience with FairPhone OS, I was thinking about it and now I will do it that way.

Since It solves the main warranty issues, I will set your response as solution. I will update with #3 when I’m done with the process. I will edit my question to clarify my steps.

[Grigi]

On the /e/os issues:
2. Yes, it’s such a downgrade over Trebuchet. Best I found that meets my needs so far is Fossify Launcher, but that has some annoying bugs.
5. Yes, I installed separate fdroid and use that for where I can. Other people seem to complain about AppLounge in much the same way.
6. This appears to be a recognised bug. Apparently to be significantly improved in v3.1 due in August.
7. I don’t have this issue, possibly this is also related to the Bliss launcher?
9. Yes, there is plans to make what it does configurable. It’s a shame that it’s at least not slightly configurable at this stage.
11. This is to be expected, they are separate OS’es. At least it appears /e/ gets some support directly from FP as all the phone hardware appear to be configured, and the older phones use the better FP camera app and get updates there.

Probably the biggest complaint I have re /e/OS is how for a paid re-packaged distribution of Lineage, they have replaced some of the better parts with worse things. It feels very incomplete, especially in it’s rush to try and simplify things that shouldn’t be.

[ReplaceablePancake]

Thank you for sharing your thoughts about my issues with /e/OS, I’m glad I was not alone!
About 7: It happened when I configured the “Long swipe” to the action “Recent App”, to change to the last app I was using. Maybe it has just with this combo.

@Grigi

Probably the biggest complaint I have re /e/OS is how for a paid re-packaged distribution of Lineage, they have replaced some of the better parts with worse things. It feels very incomplete, especially in it’s rush to try and simplify things that shouldn’t be.

Yeah right? They had already good working examples and they did not include them… Even my OnePIus 5 had the 3 position switch on LineageOS to set different notification modes. If the phone is shipped with it, it is expected to be a decent alternative.

[BartMans]

I have no FP6 but an FP4.
I had installed /e/os before. And I did not like this too. Too much buggy, to little to configure or adjust. But, you can install another launcher! Did you know that?
Later I installed LineageOs. Back then with MicroG included, because of Signature Spoofing. Later, as from around LineageOs 20 or 21, Signature Spoofing option was included in the rom. So Then I installed Normal LineageOs, and installed MicroG from F-Droid. Magisk, patched the boot.img and flashed it to have root. Installed Shamiko to be able to hide root for different apps. Then I could use all the apps, everything was working well!
This week I installed stock. Just because of the Camera2 app, included in stock. That is a little better than, the camera’s in Lineageos. That is because of the upcoming holiday
But important! Be very carefull locking the bootloader. I did not on stock, and did not before. The unlocked bootloader is no problem on stock.
In the past, I bricked the phone by locking! This had to do with the securitu patch level. Fairphone fixed it, and costs me 2 weeks without a phone and 35 euro’s.

[Extarion]

@BartMans

But important! Be very carefull locking the bootloader. I did not on stock, and did not before. The unlocked bootloader is no problem on stock.

Should you wish to lock your bootloader in the future, take a look at this thread:

Can't flash stock FP4 ROM

Definitely check fastboot flashing get_unlock_ability immediately before locking. And don’t boot into Android after flashing it, the first boot resets it to 0 (The reason being that’s how you get your phone delivered and there are apps that check for that). Flash → Check → Lock

It helped resolve an identical (or at least similar) issue on the Fairphone 6.

[BartMans]

Yeh, I know, Been there. Link

[yvmuell]

To rather point to the device specific topic around this

/e/OS Frustration, Flash FairPhone OS and Warranty

At the moment thats not sufficient, so at the moment you can reflash but not lock the bootloader most likelly or only with checking get unlock ability before booting into the system @ReplaceablePancake you bought where, Fairphone? We here are all user, so what exactly voids warranty is Fairphones decision. Normally you can do what ypu want as long as you can redo to proof its not the cause of the failure you want to claim while I guess having FPOS on the phone should not be any issue at all. …