Hello,
I asked a lot of questions on this forum about the installation of /e/OS (android 14) on my Nothing cmf phone 1 Android 15. The conclusion I drew from these discussions is that there is a kind of rule that advises not to go backwards in Android versions and therefore to wait until the arrival of /e/OS android 15.
But one question is bothering me. What’s the difference with installing an OS on a computer? Because on a computer, I format and then install the system of my choice. Can’t you “format” the phone and then install whatever you want? Is there some kind of memory effect in the smartphone?
I’d got used to the idea of waiting, but a post sowed the seeds of doubt in me [–> … no need to be on specific firmware version.]
maybe I’m misunderstanding what this sentence means, but I didn’t understand the difference with an OS on a computer …
Thanks, have a nice day
even is it still unclear for me in this sentence if @priyansusahoo downgrade to Nothing 2.6 before installing /e/ or use directly the /e/ build to downgrade (as needed parts of the firmware are included), one have to confirm the process…
.
be carrefull about the Android Security Update release date included in the new build
not older than the one already installed is still valuable advising…
.
Settings > About phone > Android version > Android Security Update .
here there are about 20 to 40 partitions depends on the device, most you musn’t touch them
( partition table backup , IMEI , modem drtivers , other hardware drivers )
in short, we will only replace /boot and /system, modify /vendor
as example :
Requirements
Latest TWRP downloaded (to be booted through fastboot) Parted arm64 static binary
Latest fastboot and ADB commands installed
Patience
Well, yes but it is not the general Android way, where users are advised to keep updating and this is enforced by verified boot.
Manufacturers tend to hide from “general users” the type of ROM that could be described as a Fastboot ROM … hidden perhaps as it might be confusing to the “general user” … and advertising such ROMs would undermine the “natural” update process which is designed to be sure to keep the phone “Google safe”.
One significant thing about a Fastboot ROM, it is delivered to the phone while the phone is somewhat inert in Fastboot mode.
This mode of delivery is closer to what we see in a PC or “small boards”, it is possible to make mistakes, but in the case of /e/OS-tetris the job has been simplified by provision of a script within the download. Please download it and have a look before deciding.
Still the best source of info is the XDA development thread
But the “install whatever you want” is limited by a requirement to provide the blobs or vendor parts, which turn out to be very specific for most Android devices.
It think the difference is a computer has a standardized BIOS that’s designed to be accessible. When you install a new operating system on a computer you’re using a setup program that runs directly on top of the BIOS without limitation.
The same level of access to a phone is through a highly constrained bootloader with lots of limitations. A phone technically has a BIOS, but its not accessible. Phone’s are designed that way intentionally to limit access.
I think phones could be hugely better in terms of handling the operating system if they were more like computers, but phones are designed only to support proprietary corporate interests so we get the shaft. I think a lot of that stems from the presence of a carrier acting as a middleman.