I thought the official version was not available. There is no link in the documentation. That’s why I was waiting for this version.
I have now found the link here /e/OS official tetris download
I thought the official version was not available. There is no link in the documentation. That’s why I was waiting for this version.
I have now found the link here /e/OS official tetris download
If I understand correctly, if I want to switch to the official branch, I have to reinstall with the data wipe. Is it necessary to install the stock ROM first?
e-2.7-u-20250109*-official-tetris.zip
e-2.7-u-20250111*-community-tetris.zip
I think because it is ‘Alpha’ they don’t show it
And yes switching to official will resolve in data loss
I don’t care which branch release first. Official branch policy suits me better than Community one, that’s all.
Can anyone confirm, that even with this smartphone it is necessary to install the stock ROM first?
@piero knows what I was talking about, but you don’t! However, that’s meaningless to me.
Really? I was just asking politely about a technical detail that had nothing to do with the release date. You just missed my point.
At one point you wrote ‘testing community’. To what community you were refering I am not sure. But testing can be done for ‘official’ and also ‘community’ builds. That is what @Xxpsilon and @piero were talking about.
And I take back my data loss comment when switching build types, as Piero suggested you can (did it myself also before) if bootloader is unlocked (e/OS/-Team doesn’t recommend it)
Acording to this article Different Build Types, I want to run Official build. I understand that currently they may be identical builds, but this may not be the case in the future. I prefer a more tested build before an earlier release date.
Can you please provide me a link with instructions how to switch to another branch? Data loss i OK for me. But according to this post, that’s not possible Switch from s-dev branch to s-stable branch? - #5 by Manoj. That’s why I asked about the stock ROM.
I have no idea what is currently installed for you.
If e/OS/ with community, you could sideload the official one, stay on the same version or newer is even better. I did it once years ago and it worked (I know not recommended but if you know what you do and aren’t afraid you can risk it)
If you are on stock then you could use the installation guide and use the official zip rather then the community one. The link for the official one you found.
yes it is called “dirty-flash” when flashing without “factory-reset” (formating /data) or “clean-install” when flashing applying the “factory-reset” step.
@joelp you are saying that you want the best of official and would like stable; so Format data and treating it as Fresh install is the clean way to do that.
I have successfully installed /e/os on my cmfphone 1 after playing around with nothing-os for a short while. Install process was spot on.
First impression is good. I have the following remarks
Perhaps some of these issues will be addressed in the final version
For the rest i am super excited about this. Great work!
in the coming months I intend to do a clean install of the official branch. Do I need install stock ROM first?
As you are performing the Clean install without any change in Android version, I can see no essential need to go via Stock ROM.
As said I feel it is unnecessary as this is a fairly well established build. However if one once had a build marked “alpha” then one might add this extra precaution, especially if the build used later was no longer marked “alpha”.
I want to install /e/OS on my CMF phone 1, but the question is, currently I’m using Nothing OS 3.0 which is android 15 and /e/OS is android 14, Will there be a problem if I install /e/OS.
It is unusual that a is not shown on the install page, so it is possible that this might be possible.
I would not attempt it without input from someone_who_has_done_it.
In older Android versions it was always imperative to use the manufacturer ROM and method to downgrade Android version.
@aibd
Only install CustomROM images with an AOSP version that is higher than or equal to the version of stock Android that came with your device. Or in other words: Only install the /e/OS-U with an Android API level A14 that is equal to the Stock Nothing OS 2.6 (A14) version.
An Android 15 bootloader (Nothing OS 3.0) will not accept a CustomROM bootloader with A14 (/e/OS-U).
I didn’t wait and tried it myself, and it totally WORKS. Previously I was using Nothing OS 3.0 which is android 15, and downgraded to android 14 which comes with /e/OS. Faced no issue.
@priyansusahoo
I’m surprised, because that is contrary to what I have learned and practiced so far. But you never stop learning. Nevertheless, I’m sticking to my tried and tested installation sequence.