I have like many others recently purchased a Fairphone Gen.6 with stock Android on it. I was hoping to use the /e/OS Web Installer to get /e/ running on it, but it appears that the tool is not yet available for the device.
I am not super confident in my android modding abilities and whatnot, so I’m kinda reluctant to use the more hands on approach, especially given that quite a few people have apparently bricked their phone.
I’ve read this thread (Install e/OS on Fairphone 6), and I’m seeing a lot of rather confusing stuff about the security versions, rollbacks etc, which is something I’d rather not deal with.
I was wondering whether there was an ETA for the Web Installer / FP Gen.6 combo, and whether there is a specific place to check for updates on the subject, seeing as Murena already publicly released the official /e/ build for the FP6 a little while ago.
Any info about any potential release date is greatly appreciated, especially given that the stock OS does regularly update.
PS. sorry if I posted this in the wrong part of the forum, I’ll admit I’m a little bit lost…
Until Web Installer is fully documented you will have to consider what you do about locking so it is quite worth reading the official install page yourself.
The very new Web-installer is perfect for anyone who had done the job before as the collection of downloads and sequence is automated. However there seems still no way to collect and share a log from the installer so early adopters without such experience have reported difficulties with which other forum users have found it hard to help.
The manual install is done with a script supplied with the download so once you deal with prior Requirements the install is not so hard.
I’ve already dealt with manual installation of /e/OS on my old daily driver and read the install doc, so I’m relatively familiar with the process.
However, due to the reported problems with security versions and whatnot, as well as some irl stuff, I would much rather simply follow the web installer and not stress over bricking my device / spending a bunch of time in terminal.
I suppose that the web installer will have at least some safeguards against messing up that stuff (when it gets released). It would be extremely strange for the more automatic dedicated tool / process to brick your phone or at least not warn you if it’s meant to be the ‘easier method’ to use. Sure it has downsides but it’s useful for the wider public that either doesn’t have a Linux setup etc. etc.
Also, I believe the easy installer is down because Murena said they were having issues keeping all devices compatible etc., as you mentioned here, so I wasn’t especially planning to use it. I don’t know whether the easy installer and web installer are the same thing or anything like that, but to avoid confusion I am planning to use this tool upon FP6 compat.
I just generally find it more reassuring to use a dedicated tool instead of pasting commands I often don’t really understand into a terminal, with the additional risk, however unlikely and avoidable, of bricking a quite expensive phone. I am not really preoccupied with feeling dissatisfied with the process if I end up getting /e/ loaded without destroying my system
“I am not super confident in my android modding abilities and whatnot, so I’m kinda reluctant to use the more hands on approach, especially given that quite a few people have apparently bricked their phone.”
But then you say:
So what is it?
Then you insinuate
the reported issues you are talking about lie this one?
Maybe you are the same person or entity that made that post (another new user) and creating misinformation. After all this is very possable in this day and age with the help of AI tools and bots.
It seems your real purpose is to create distrust of eOS.
I don’t know what to say except that’s one hell of an interpretation.
To clarify, I am relatively familiar with the process without the rollback protection. I had installed /e/ on an old phone quite a bit ago, accepting that losing a 90 buck phone was fine. I do not have that same policy with a 600 buck one.
As for the whole sock puppet account thing, and to create distrust of /e/, just… no? It’s been my daily driver for 4 years on my S7, and why on earth would I waste my time creating “distrust” of an OS? Not a fan of having idiotic motivations assigned to me, you’re doing a far better job at inciting people to stay away here… You can ask staff to check my account, that’s completely fine by me. Also yes, I have a dumb name. What about it?
I have seen some people talking about bricked phones without any reference to it being /e/'s fault rather than their own. I trust /e/ and Murena if that’s what you’re wondering about.
And I believe my question was quite clear. It was simply whether there was an ETA for the web installer.
In fairness @Jets some might read my contributions as sowing the seeds of doubt!
If I have seen too many forum enquiries pointing to the difficulties of new users with the new Web Installer I might have better spent my time on a documentation-inputs thread.
Repetition in different words I have a real concern that new users are diving into Web Installer as it looks “easy” but (correct me if I am wrong) there has been no adequate briefing within the installer on the anti-rollback hazard nor the warning that the installer will not currently (Edit) relock the bootloader after the install.
Of course it is early days for the installer and I wish it the very best as it matures.
Interesting, I would have assumed that it would have some safeguards. Unfortunately seeing as I don’t have an FP4/5, I can’t really test out the process and see whether or not it warns you about it and such.
I’ll just wait the required time and see once FP6 is compatible. If there is no real safeguards, I guess I’ll read everything 40 times over just to be sure.
Also, just to be sure, when you are referring to the installer not currently doing the lock, are you referring to locking the bootloader after the installation process is done?
Yes, I edited my post, for clarity for future readers, thanks.
Please bear in mind that I have no Fairphone, so my contribution is all “hypothetical” and hence my use of multiple hashtags to encourage others to read what I have seen on the subject.
