If you're fed up with notifications, tracking, and personalized ads and fancy giving your Android phone a good facelift, install /e/OS might be just what you were looking forIf you're looking for similar alternatives, Volla OS It also prioritizes privacy. It's an operating system based on Android, but designed to minimize dependence on Google and regain some privacy without sacrificing ease of use.
In this guide you will find a complete tutorial to install /e/OS step by stepFrom initial preparation to final system setup, including backups, bootloader unlocking, recovery installation, and ROM flashing, we'll cover it all step by step, explaining each step and its implications, so you're always clear on what you're doing and can minimize risks.
What is /e/OS and why is it used to "de-Google" your mobile phone?
/e/OS is a mobile operating system based on Android (specifically AOSP, the open-source part of Android) that aims to offer a very similar experience to what you already know, but without Google's proprietary services or its tracking capabilitiesIt is driven by the non-profit organization Murena (formerly e Foundation), led by Gaël Duval, and its main objective is to improve privacy and reduce dependence on tech giants.
Instead of Google Mobile Services (GMS), /e/OS uses MicroG and other alternative services This allows certain apps to continue functioning, but limits the amount of data sent to third parties. This means you won't have the Google Play Store, Google Play Services, or the typical pre-installed Google apps, but you will have a compatible app store, its own synchronization services (email, contacts, calendar), and a fairly polished system.
In addition, /e/OS comes with a simple launcher-style customization layer, a set of basic apps such as a browser, calendar, email, gallery, and maps, and a dashboard. very well-designed privacy settings where you can control permissions and tracking with considerable granularity. The idea is that you can continue using your phone normally, but significantly reduce the digital footprint you leave behind.
Advantages and limitations of installing /e/OS
Before diving headfirst into flashing anything, it's a good idea to be clear about the real advantages and drawbacks You'll find yourself using /e/OS. It's not a magic bullet, but it's a very interesting step if you want more control over your data.
main advantages
The first obvious advantage is that You completely eliminate most of the integration with GoogleYou will not have a Google account associated with the system, there will be no automatic synchronization with its services or constant sending of data to its servers, unless you explicitly allow it through specific apps or specific settings.
Another important advantage is that /e/OS comes with integrated privacy tools: advanced permissions controlTracker blocking, a notification system for sensitive permissions, a "Privacy" panel where key options are grouped, and settings to limit app access to location and other personal data.
For everyday use, you'll find the interface very familiar if you're coming from Android. You'll have basic pre-installed apps to cover the essentials: phone, SMS, browser, email, calendar, notes, gallery, music player, file manager, etc. Many of them are based on free software and integrate with the Murena cloud if you choose to use it.
It also highlights that /e/OS offers proprietary cloud services (email, contacts, calendar, file storage, notes, tasks) accessible under a Murena account. This is a fairly decent replacement for the Gmail + Drive + Calendar + Contacts combo, maintaining synchronization across devices without needing a Google account.
Finally, being based on Android, app compatibility is broad: you can install most common applications from the integrated /e/OS store, which relies on repositories like F-Droid and a catalog that also includes many popular apps. They are not limited exclusively to Google Play Services.
Limitations and aspects to take into account
The first major limitation is device compatibility: /e/OS only officially supports certain modelsAlthough the list has grown considerably, you won't be able to install it on just any Android phone you want. It's advisable to carefully review the compatible devices page before proceeding with flashing.
It should also be noted that some apps that are highly dependent on Google Play Services may have issues. malfunctions or not working perfectlyGames with DRM, particularly finicky banking apps, some streaming services, or applications that use SafetyNet/Play Integrity certification may behave unexpectedly or simply refuse to work.
In terms of stability, /e/OS is usually quite solid, but it is still a Custom ROM that may have minor bugs Depending on the model and version, you may encounter minor bugs, slightly different battery consumption compared to the original ROM, or specific camera and sensor details that aren't as polished as in the manufacturer's official firmware.
Another key point: the installation process involves unlock the bootloader and flash the device...with the associated risks. If something goes wrong, you could end up with a device that won't boot (soft brick) or, in the worst-case scenario, one that's difficult to recover (hard brick). Furthermore, unlocking the bootloader often voids the warranty or makes it clear that they are no longer responsible for any issues that may arise.
Compatibility check and /e/OS download
The first practical step is to make sure your phone is supported. To do this, you need to go to the official /e/OS website and find the list of supported devices. There you will see that Each model has its own download sheet, usually organized by manufacturer and device codename.
On that page, you can confirm whether there's a stable, beta, or development version for your phone, and which Android version it's based on. It's recommended to opt for the stable branch unless you have a specific need to test very new features and are willing to take the risk of more failures.
Once you've located your model, you need to download the corresponding ROM. It's usually offered in .zip or .img format, along with the specific installation instructions for that deviceIt is essential to follow the method indicated for your specific model, because the procedure may vary slightly between brands and generations.
In addition to the ROM, in many cases you will have the option to download the /e/OS installer for computerA graphical tool that greatly simplifies the process for certain supported devices. If your phone is compatible with the installer, it may be the easiest option for less technical users.
Preparations: backup and prerequisites
Before touching anything on the system, it's advisable to make a good backup of your data. The /e/OS installation process usually involves a complete erase of the phone's internal memory (factory reset and sometimes partition formatting), so anything you don't back up will be lost.
For backups, you can choose from several combined strategies. One option is save photos, videos, documents and other files to your computer You can back up your files using a USB cable, copying the main folders (DCIM, Pictures, Downloads, WhatsApp, etc.). Another option is to use cloud services (preferably encrypted and with a good privacy policy) to back up your most important data.
In the case of messaging apps like WhatsApp or Signal, check the own export or backup methodsWhatsApp allows local and cloud backups; if you want to minimize dependence on Google, you'll want to use the local backup and manually transfer it to the new system, provided that /e/OS and the app itself allow it.
In addition to data backup, make sure you have basic things like USB cable in good condition, a working computer and a charged mobile phone battery at least 60-70%. It's best not to risk running out of battery mid-flash, because that's the perfect time to render your phone unusable.
In many cases you will also need install the appropriate drivers on your computer This allows the phone to be recognized in fastboot or ADB mode. This is especially important on Windows, where it's sometimes necessary to install manufacturer-specific drivers, while on Linux and macOS it's usually more straightforward.
Unlocking the bootloader
To install a custom ROM like /e/OS, it is essential unlock the device's bootloaderThe bootloader is the program that starts the operating system when the phone is turned on and, by default, is usually locked to prevent the loading of unofficial software.
The exact unlocking procedure varies depending on the manufacturer, but generally similar steps are followed: enabling the developer options in Android (by tapping several times on the build number in Settings → About phone), and from there activate “OEM unlocking” and USB debugging.
Next, connect the mobile phone to the computer using the USB cable and use the appropriate command-line tool (usually fastbootto send the unlock command. This is usually done by starting the phone in bootloader/fastboot mode (via a key combination or an ADB command) and running something like “fastboot oem unlock” or “fastboot flashing unlock”, depending on the device.
When the command is launched, the mobile device will display a warning screen indicating that the Unlocking the bootloader will erase all data and may pose a security risk. You will need to confirm the action using the volume keys and the power button. After confirmation, the phone will restart and the bootloader will be unlocked.
It is worth noting that, in many models, unlocking the bootloader activates a warning screen at startup This indicates that the system may not be official or that the device is in a less secure state. This is normal and part of the process; it cannot usually be completely removed, although some ROMs allow you to replace this screen with a less aggressive one.
Installing a custom recovery (TWRP or other)
The next usual step in installing /e/OS is to flash a custom recoverysuch as TWRP or the specific recovery recommended by /e/OS in your device's specifications. Recovery is an environment separate from the main Android system, allowing tasks such as wiping partitions, creating system-level backups, and flashing new ROMs.
To install the recovery, you'll first need to download the file corresponding to your phone model from the official developer's website (TWRP or the relevant one) or directly from the /e/OS downloads section, where the recommended recovery is often linked. Again, it's usually a .img file that is flashed using fastboot.
With the phone in bootloader/fastboot mode and connected to the computer, launch a command from the terminal like “fastboot flash recovery recovery_name.img”, replacing the name with the downloaded file. Some devices require slightly different commands (such as flashing to a different partition), so it's vital to check the correct partition. Follow the specific instructions for your model..
Once the recovery has been flashed, it's best to reboot directly into that mode instead of booting into the Android system, because some manufacturers restore the original recovery on the first boot if they detect changes. Therefore, it's recommended to... Enter the newly installed recovery using the appropriate key combination (usually volume + power) right after flashing.
Data erasure and partition preparation
With the custom recovery up and running, the next step is to prepare the ground for the /e/OS ROM. This usually involves flashing the /e/OS ROM. wipe or deletion of specific partitions to avoid conflicts with remnants of the previous system.
In a TWRP-type recovery, options such as "Wipe" or "Advanced Wipe" are usually offered, from which you can select partitions such as Dalvik/ART Cache, System, Data and CacheThe general recommendation for installing a clean ROM from /e/OS is to erase at least System, Data and Cache, although sometimes additional instructions are included (for example, formatting /data if there is incompatible encryption).
It is crucial not to touch critical partitions not mentioned in your model's guide, such as EFS, Modem, or similar, as they contain essential network information, IMEI, and other low-level dataDeleting them without knowing can leave your phone without coverage or with serious connectivity problems.
After performing the necessary wipes, the device will be without a functional operating system, ready to receive the new ROM. It's normal that if you try to boot at that moment without flashing /e/OS yet, the phone It will not get past the bootloader or recovery screenSo don't be alarmed if you see strange behavior before the process is complete.
Installing the /e/OS ROM
With everything ready, it's time to flash the ROM. There are two main ways to do this: using the .zip file from recovery or via the /e/OS installer from your computer, if your device is supported by that tool.
Installation from recovery using a .zip file
If you choose the traditional method, you will have to Copy the .zip file from /e/OS to the phone's storage (or to a microSD card, if your model supports it) before performing the wipes, or use the ADB sideload transfer function that some recoveries offer.
From the main recovery menu, access the install option (“Install” in TWRP, for example) and Select the .zip file from /e/OS that you copied. After confirming, the recovery will begin the flashing process, which may take several minutes. During this time, status messages will appear on the screen indicating the progress.
When finished, the recovery will display a success message or, if something goes wrong, an error log. If everything went well, simply... Reboot the system from recovery mode. (“Reboot system”). The first boot of /e/OS is usually slower than normal, so it is normal for it to take several minutes to finish configuring and display the welcome screen.
Installation using the official /e/OS installer
On some devices, the most user-friendly way to install /e/OS is to use the Official installer available for Windows, macOS, and LinuxThis tool guides you step by step, detects the model, downloads the appropriate ROM, and automatically performs operations such as unlocking the bootloader (when possible), flashing the recovery, and installing the system.
To use it, download the installer from the /e/OS website, run it on your computer, and follow the on-screen instructions. You will typically need to connect the mobile phone in the different required modes (ADB, fastboot, etc.), accept some confirmations on the device itself and wait for the tool to complete each stage.
This method greatly reduces the risk of making manual errors with commands, but it's still advisable to carefully read the installer's instructions and make sure that The cable is not disconnected and the computer is not turned off during the processOnce finished, the phone will restart with /e/OS installed and ready for initial setup.
First boot and initial configuration in /e/OS
When you turn on your phone for the first time with the newly installed /e/OS, you'll see a welcome assistant that will guide you through the Basic settings for language, time zone, Wi-Fi, and accountsThe flow is similar to that of any Android, but with some important differences related to privacy.
At some point during setup, you will be offered the option to create or log in with an account. Murena's accountUsing this account lets you sync email, contacts, calendar, notes, tasks, and files with the /e/OS cloud. If you want to minimize your reliance on Google while still having cloud syncing, it's often a very attractive option.
If you prefer not to use any proprietary cloud service, you can always skip creating an account and use your phone. either with local storage or by building your own solutions (for example, a Nextcloud server). In any case, the choice is not irreversible: you can add or remove accounts from the settings later.
During the assistant, you will also be asked about global privacy and permissions optionsThe `/e/OS` file allows you to define early on certain behaviors related to sending anonymous statistics, location services, and other sensitive aspects. If your goal is to minimize Google usage, it makes sense to opt for the most restrictive settings.
Installing apps and alternatives to Google Play
With the system now up and running, it's time to set up your daily routine. One of the first things you'll notice is that There is no Google Play StoreInstead, /e/OS integrates its own application store, which allows downloading both free software and popular non-free applications, also offering information about permissions and trackers.
This store draws from various sources and aims to offer an experience as close as possible to a centralized store, but with greater transparency regarding the privacy of each appYou'll see ratings on whether the app contains trackers, what permissions it requests, and other details to help you decide whether it's worth installing.
In addition to its own store, /e/OS is usually prepared to access repositories like F-DroidIt's a free and open-source app store for Android. From there you can install a ton of open-source tools: browsers, password managers, note-taking apps, media players, and much more, all with open source code and, in many cases, a focus on privacy.
If you have very specific apps that are only distributed on Google Play and don't appear in alternative stores, you can resort to trusted APK repositoriesAlways proceed with caution. Ideally, use reputable sources and verify signatures whenever possible, avoiding suspicious websites that might try to sell you modified or malware-infected packages.
Google services, MicroG, and app compatibility
A very common question when installing /e/OS is what happens to apps that depend on Google Play Services. To fill that gap, the system integrates MicroG, a free implementation of some components of Google services, capable of making many applications work without the need for the official Google package.
MicroG offers, among other things, support for Push notifications, location services, and some APIs used by popular appsThis means that many applications that wouldn't start on other ROMs without Google, can start on /e/OS or, at least, work partially.
Even so, it's not perfect: certain apps, especially those that rely on security mechanisms like SafetyNet or Play Integrity, may refuse to work, detect the device as "uncertified," or display Error messages when logging in or playing protected contentThis frequently affects banking apps, some video streaming services, and mobile payment apps.
In those cases, you can try different MicroG configurations from the /e/OS settings, and check if the community has documented them. specific solutions or patches For your model or app, consider using alternatives that aren't so dependent on the Google ecosystem. Sometimes there are progressive web clients (PWAs) or less intrusive apps that perform the same function.
Privacy and security after installation
Installing /e/OS is only the first step; to truly take advantage of its benefits, it is advisable to Take some time to adjust your privacy and security settings.In the Settings panel you will find a specific section where several tools are grouped to control what apps can do.
There you can review, permission by permission, which applications have access to location, camera, microphone, storage, contacts and other sensitive dataIt's a good idea to block anything that doesn't make sense for each app, and only allow what's strictly necessary. /e/OS also integrates mechanisms to detect trackers within applications and limit their activity as much as possible.
In terms of physical device security, don't forget to configure a solid screen lock method (PIN, password, or pattern) and, if your model allows it, activate the fingerprint reader or facial recognition according to your preferences. You can also review the storage encryption options to ensure your data is protected if the device is lost or stolen.
Another recommendation is to maintain the system Updated with the latest versions of /e/OSIn the updates section, you can check for new builds, which typically include security patches, performance improvements, and bug fixes. It's convenient to enable automatic checks, but always review the release notes for each update before installing it.
Maintenance, updates and potential problems
Once everything is set up, using /e/OS on a daily basis isn't that different from a traditional Android, but it's worth keeping in mind some aspects of maintenance To avoid surprises, the first step is to get into the habit of regularly checking for system and app updates to ensure everything stays up to date.
If you notice performance issues, excessive battery drain, or specific function failures after an update, it may be helpful to consult the community and official documentation Check /e/OS to see if there are any known issues with your model or version. In many cases, patches are released or additional settings are recommended to resolve these problems.
It's also possible that a key app you used before might not work correctly under /e/OS. In those cases, you'll need to consider alternatives. look for another app that performs the same functionYou can use the web version in your browser or even keep a second device with stock Android for very specific tasks that require the entire Google ecosystem.
If at any point you want to revert to the original manufacturer's ROM or switch to another custom ROM, the process usually involves reflash the official firmware using specific tools from the manufacturer (Odin in the case of Samsung, for example) or using recovery images. However, unlocking the bootloader and potentially voiding the warranty are not always reversible.
Making the switch to /e/OS means opting for a system that prioritizes your privacy and reduces your dependence on Google, in exchange for accepting certain limitations and a more technical installation process than that of a "factory-made" phone. If you take the time to check your device's compatibility, prepare a proper backup, calmly follow the unlocking, flashing, and installation steps, and then carefully adjust permissions, apps, and security options, you'll typically end up with a phone that remains fully usable on a daily basis but with Much more control over what gets installed, what runs in the background, and what data leaves your pocketThis is especially valuable in an environment where the massive collection of information has become almost the norm.
