If you're fed up with your phone turning into a data collection machine for GoogleDe-Google your smartphone with /e/OS is one of the best decisions you can make. It's not something you can do in five minutes, but with a good guide, a little patience, and the right device, you can have a much more privacy-friendly Android experience without giving up most of your favorite apps.
In this article you will learn How to unGoogle your smartphone step by step with /e/OSWhat exactly does this operating system offer, how does it differ from traditional Android, what problems you might encounter during installation, and what advantages (and drawbacks) you'll notice in day-to-day use? All explained clearly and concisely, with a practical approach and all the important details you need to know before you jump in.
Why it makes sense to un-Google your mobile with /e/OS
The current mobile phone landscape It's dominated by operating systems that thrive on your data: every screen tap, every search, and every app you use feeds massive advertising profiles. Android, as it comes pre-installed on most brands, is deeply integrated with Google services, and that implies a level of tracking that many users are no longer willing to accept.
/e/OS was born precisely as a response to that problem: it is a mobile operating system based on Android but without GoogleBuilt on AOSP (Android Open Source Project) and LineageOS, and maintained by the e Foundation and the company Murena, its goal is clear: to offer an experience as similar as possible to Android, but minimizing data leakage to large corporations, replacing proprietary services with open-source alternatives, and reducing trackers to a minimum.
Instead of the classic combination of Android + Google Mobile Services (GMS), /e/OS uses microGIt's a suite of tools that mimics many features of Google services (push notifications, synchronization, geolocation, etc.) but without the massive data collection associated with the Mountain View company. Furthermore, it focuses on services such as Mozilla Location Service instead of Google's location systems to resolve the device's position from WiFi networks and antennas.
Another key point of /e/OS is its vision of “de-Googling” the digital ecosystem: it doesn't just stop at the phone's operating system, but proposes a suite of its own cloud services (Murena Workspace / Murena Cloud) with email, contacts, calendar, storage, notes, office suite and more, all designed to minimize dependence on Google, Microsoft and company.
For those already immersed in the privacy culture, /e/OS fits perfectly with movements like the “Wikipedia of de-Googling” (collaborative lists of alternatives to each Google service) or the use of repositories like F-Droid, privacy-focused browsers, and open-source ROMs like LineageOS or GrapheneOS. /e/OS positions itself within this ecosystem as a well-balanced option between privacy, usability, and compatibility with Android apps.
What exactly is /e/OS and who is behind it?
/e/OS is a mobile operating system open source and without GooglePrimarily driven by Gaël Duval (the creator of the well-known GNU/Linux distribution Mandrake) and developed under the umbrella of the e Foundation. Technically, it is based on LineageOS, but with a strong focus on de-Googling and its own ecosystem of services and applications.
The project started in 2019 as a spin-off of “LineageOS for MicroG”, with the idea of remove Google services of the system and replace them with privacy-respecting alternatives. Over time, it has evolved into /e/OS, a fairly mature system that today supports more than 200 devices through official and unofficial support, and is also sold pre-installed on Murena smartphones (based on popular devices such as Fairphone, Pixel, etc.).
The philosophy behind Murena goes beyond software: the name itself refers to a cognomen of ancient Rome Linked to the plebeians, a class of free citizens who opposed the patrician elites, Murena draws inspiration from this idea of freedom and the fight against the concentration of power to "liberate" users from the control that large corporations exert over their personal data.
When you buy a Murena phone with /e/OS pre-installed, you not only get the non-Google operating system out of the box, but you also have Integrated access to Murena WorkspaceEmail, calendar, cloud storage, online office suite, notes, etc. All managed by Murena's servers, with a privacy policy focused on data minimization.
For those who prefer tinkering, /e/OS can also be installed as a custom ROM on many existing models, extending the lifespan of devices that would otherwise be discarded. This makes /e/OS a very attractive alternative for reviving old mobile phones and give them a second life free of bloatware and mass tracking.
Key features of /e/OS: privacy, control and its own ecosystem
One of the key aspects of /e/OS is that it doesn't just remove Google apps: it builds a set of privacy-oriented features and tools which, in many cases, you won't even find in the official Android app. The idea is for the user to have a clear view of what their apps are doing and to truly control what happens to their data.
At the heart of the system we find the so-called Privacy Dashboard or “Advanced Privacy,” which centralizes the management of permissions and sensitive behaviors. From there you can see which apps access your location, contacts, storage, or other sensitive data, and modify or revoke permissions on the fly with just a few taps.
Another important function is the ad blocker and trackers It's integrated, filtering out much of the intrusive advertising and common trackers that sneak in through websites and some apps. This not only improves privacy but can also reduce data consumption and make browsing smoother.
As an open-source project, /e/OS allows anyone to audit the code, which adds an extra layer of transparency and securityThe fact that the community has access to the system's core makes it more difficult to hide dubious behavior, and facilitates the rapid correction of potential vulnerabilities.
At the application level, /e/OS includes a selection of pre-installed apps Designed to cover everyday needs: email, calendar, browser, file manager, camera, weather app, notes, etc. All of them are open source or based on open projects to which Murena applies a layer of redesign and improvements to make them more pleasant and easier to use.
Key new features of /e/OS 2 and /e/OS 3: a leap forward in privacy and functionality
With each version, /e/OS has incorporated advanced features to compete in comfort with traditional Android, but maintaining its privacy philosophy. The two major recent releases are /e/OS v2 and /e/OS 3.0, which introduce significant changes both at the ecosystem level and in terms of data control.
Version 2 was a significant step forward, consolidating the system and expanding the number of supported devices to over 200. Among its most notable changes was the so-called “Wall of Shame” (Wall of Shame), a system that identifies and highlights apps with the worst privacy practices so that users know, before installing or using them, what they are exposing themselves to.
In addition, /e/OS v2 brought a more granular advanced privacy settingsA revamped launcher with improved notification management and live wallpapers, Android Auto compatibility (although this integration still relies on Google Maps in many cases), and a significant improvement in file synchronization via an updated and more stable eDrive. QR code reading was also integrated into the camera app itself.
With /e/OS 3.0, Murena has taken another leap forward. They've reinforced the message that your phone should work for you, not for advertisers, and have added features designed to give even more control over digital life without complicating the user experience. This version is especially interesting if you have a family or if you want a detailed view of how your apps behave.
One of the major additions of /e/OS 3 is the Enhanced parental controlsThe system allows for much more precise management of screen time and app access for children, with restriction levels adapted to different age groups. Apps marked as subject to Parental Guidance require a security code to be installed, and parents can activate this same control for any app installation if they want a highly secure environment.
Advanced Privacy, weekly reports and geolocation tailored to your needs
The function of Advanced Privacy In /e/OS 3.0, this feature has been enhanced with new weekly reports that provide a comprehensive overview of your privacy status. Each week, the system generates a summary detailing the most invasive apps you have installed, the most aggressive trackers detected, and an overall privacy score to help you understand if you're on the right track.
These reports don't just focus on numbers: you can share them on social networks If you want to raise awareness about the number of trackers used by some seemingly harmless apps, this is a way to make visible something that is usually invisible to the average user.
Another powerful improvement in /e/OS 3.0 is the ability to customize geolocation behavior on an app-by-app basisYou can decide which apps see your real location and which receive a fake location (mock location), allowing you to use certain services without giving away your exact position all the time. This is perfect for those who want to use social media, weather apps, or business applications without being geolocated down to the last detail.
Along with these privacy improvements, /e/OS 3.0 has also enhanced the large-screen experience with a tablet mode which adapts the interface to make it more comfortable on large-format devices, while maintaining the same principles of respect for privacy.
In the field of search, Murena has introduced Murena FindA search engine based on Qwant technology, which by default operates in "no-tracking" mode. This means you can search the internet without generating an associated advertising profile, keeping your queries away from traditional advertising giants.
Murena Vault, Find My Device via SMS and cloud services
One of the most interesting aspects of /e/OS 3.0 is its integration with Murena VaultAn end-to-end encrypted vault available within the Murena Workspace environment (at murena.io). This tool, currently in beta, allows you to store sensitive files with strong encryption, even for real-time editing and collaboration, leveraging CryptPad technology.
The idea is that the user can have a kind of digital "safe" where they can store documents, contracts, personal data, or any sensitive files without even the service provider being able to access their contents. It's a key tool for organizations, remote workers, and anyone who takes the confidentiality of your files oh really.
Another practical addition is the function of Find my device by SMSUnlike traditional Google solutions that rely on an internet connection and a Google account, /e/OS 3.0 offers a system that uses standard SMS to remotely locate your phone. You send a message in a specific format, and the device responds with location information, even without active mobile data.
This system is especially useful for parents who want locate your children's phone numbers This can be used on an as-needed basis, and also as a backup if you lose your phone in an area with poor data coverage but with available GSM network. All of this, again, without involving Google's infrastructure or other major providers.
For Murena Workspace Premium users, the company has added the feature Murena Voice to textThis feature allows you to dictate messages privately using voice recognition. You can compose texts without typing, but without sending your voice to massive advertising analytics systems. It's designed to increase convenience without sacrificing privacy.
/e/OS compatibility with Android apps and services
One of the common fears before un-Googling a mobile phone is: "Will my apps still work?"/e/OS aims to get the answer as close to "yes" as possible, albeit with some nuances. The system is compatible with the vast majority of Android apps, as it is based on AOSP and maintains compatibility with APK files and the usual development ecosystem.
The replacement for Google Mobile Services are the libraries of microGThese services replicate many of the APIs necessary for apps to function (push notifications, maps, login, etc.) without requiring the installation of official Google services. Thanks to this, you can log in with your Google account to some apps if you wish (for example, to sync contacts or use a specific app), but with additional layers of protection and masking.
As an app store, /e/OS integrates its own App LoungeThis gives you access to both open-source apps and many popular Android applications, including those from the Play Store, but without forcing you to install the Google Play Store itself. You can also add repositories such as F-Droidwhich is the reference for free software for Android, and use alternatives like Aurora Store if you need to.
In the realm of Google services, it's important to understand what's being replaced. The GMS suite includes apps like the Play Store, Gmail, Google Maps, YouTube, Chrome, Drive, Calendar, Photos, Google Assistant, and YouTube Music, as well as hidden services such as Google Play Services, Account Services, Location Services, SafetyNet or Cloud Messaging/e/OS attempts to replace all of this with open components, although certain functions that are highly dependent on SafetyNet or proprietary APIs (for example, some banking or mobile payment apps) may cause problems or simply not work.
In practice, many users use /e/OS without missing much, especially if they rely on alternatives: F-Droid for free apps, browsers like Firefox or Chromium-based derivatives without tracking, privacy-friendly cloud services (either their own or third-party), and messaging tools that aren't tied to the Google ecosystem. However, it's important to assume that Leaving the Google ecosystem requires flexibility and a certain tolerance for manual adjustments.
How to install /e/OS step by step on your smartphone
If you don't want to buy a Murena terminal with /e/OS pre-installed, you have the option of install the ROM yourself on a compatible phone. The process isn't trivial, but it's well-documented and can be completed in about 30-40 minutes if you follow the steps carefully. In short, the procedure involves unlocking the bootloader, flashing a custom recovery, preparing partitions, and finally installing the /e/OS image.
First of all, you should go to the official /e/OS website and Check if your device is on the compatibility listIf your model is not listed as supported (officially or unofficially), it's best not to continue, as you could end up with a bricked or unstable system. If it is listed, download the specific files for your model: usually a recovery file, a formatting/partition copying package (if necessary), and the ROM image in ZIP format.
You will need to have the tools installed on your computer. ADB and FastbootWhile in GNU/Linux they are usually found in the repositories (for example, android-tools-fastboot and android-tools-adb in Debian/Ubuntu and derivatives, or android-tools in Arch, Fedora, openSUSE, etc.). In Windows and macOS they are installed using the Android SDK Platform-Tools package provided by Google.
On the phone itself, the first step is enable developer optionsGo to Settings, then About device, and tap Build number several times until you see the message confirming you are now a developer. Then, in the new Developer options menu (sometimes within Additional settings), enable “OEM unlocking” and “USB debugging”.
Connect your mobile phone to your computer using a USB cable and select the option on your mobile phone to file transfer (MTP) to ensure ADB detects it. Open a terminal on your PC and run the command to reboot into bootloader mode, something like “adb reboot bootloader”. The device will reboot into Fastboot mode, where you can verify it's properly connected with “fastboot devices”.
Unlocking the bootloader, recovery, and partitions
To flash /e/OS it is necessary unlock bootloader of the device. This step completely erases the phone's data, so before doing anything, back up anything you don't want to lose. Once in Fastboot mode, the typical command (it varies slightly depending on the manufacturer) is something like “fastboot oem unlock”. The phone will display a warning, erase the data, and restart.
After that reboot, you'll likely see a message at startup indicating that the bootloader is unlocked, which is normal. You should complete a basic initial setup (without adding accounts or Wi-Fi if you want to speed things up), then re-enable Developer Options and USB Debugging, just like you did before. This will allow you to continue using ADB for the following steps.
Next up flash the recovery Recommended by /e/OS for your model. Again, reboot into the bootloader (using a key combination or "adb reboot bootloader") and, in your PC's terminal, navigate to the directory where your recovery file (.img) is located. The usual command would be something like "fastboot flash boot recovery-name.img". If everything goes well, upon rebooting you will enter a recovery environment with the /e/OS interface.
On some modern phones with A/B partitions, it is mandatory to use a special package of partition copy This ensures the system installs correctly in both slots and prevents boot issues. This package is usually called copy-partitions.zip and is flashed from recovery using "Apply update" – "Apply from ADB", followed by the command "adb sideload copy-partitions.zip" on the PC. Once finished, you will typically need to reboot back into recovery (for example, from the advanced options section).
With the /e/OS recovery already booted, it's time to format data and prepare the device For the new ROM, in the recovery menu select “Factory reset” and then “Format data / Factory reset”, confirming when prompted. The process is quite quick and returns the phone to a clean state, ready to flash the system.
Installing the /e/OS ROM and getting started
The last technical step is to install the image from /e/OS that you downloaded. From recovery mode, select “Apply update” and then “Apply update from ADB”. On your computer, make sure you are in the folder containing the ROM ZIP file and run a command like “adb sideload system-name.zip”. You will see a progress bar both on the device and, in many cases, on the phone's screen.
Sometimes the percentage on the computer freezes around 47%, but the phone screen displays a message like “Script succeeded result was”. As long as the recovery indicates that the process has finished successfully, don't worry about this. It's a quirk of the sideload method.
Once the installation is complete, simply select the option to reboot the system From recovery mode. The first boot may take a little longer than usual, so be patient. You'll see another notification about the unlocked bootloader, and if everything went well, the /e/OS welcome screen will appear, with a setup assistant similar to any Android device, but without Google's omnipresence.
In the setup wizard, you can configure the language (the system is available in perfect Spanish), Wi-Fi connection, accounts (such as the Murena Cloud account), and some basic preferences. Later, you can customize the level of privacy protection, activate or deactivate MicroG functions, review pre-installed apps and access the /e/OS app store to install what you need.
If you later decide that /e/OS isn't for you or you want to try a different ROM, no problem: simply download the new compatible ROM, boot back into recovery, and repeat the "Factory reset" and "ROM installation" steps with the new ZIP file. However, every system change will erase your data, so backups are still essential.
Common problems when installing /e/OS and how to deal with them
Since it is a somewhat technical process, it is normal to encounter minor obstacles during installationOne of the most common problems is that the computer doesn't recognize the device when connected via USB. In many cases, the reason is as simple as not having selected "File Transfer" mode on the mobile device, or a lack of suitable drivers in Windows.
Another common problem is that the phone doesn't boot correctly into bootloader or recovery mode using ADB/Fastboot commands. In these cases, it's advisable to resort to... physical button combinations (For example, press and hold the volume and power buttons) and repeat the process several times if necessary. Many users report that with a little persistence, the device eventually enters the desired mode.
It is also important to assume that the entire process may take between half an hour and forty minutesEspecially the first time you do it. Carefully reading the official /e/OS documentation for your model, following the order of the steps, and not improvising with files intended for other devices is essential to avoid getting into trouble.
During the first few days of use, you may also notice some strange behavior: notifications that arrive late, certain apps that don't work the same as on the factory Android, or occasional screen refresh failures when scrolling very quickly, which are sometimes more related to the specific hardware than to the ROM itself.
The good news is that the community around /e/OS is quite active, so There are usually solutions or patches. For most issues, the versions are fine-tuned with each update. If something isn't working correctly, it's a good idea to check the forums and documentation before giving up.
Advantages and disadvantages of living with a de-Googleized mobile phone
The main benefit of opting for /e/OS is a significant improvement in privacyBy removing Google services from the core of the system and replacing them with open alternatives, the amount of personal data shared with large platforms is drastically reduced. Furthermore, Advanced Privacy tools, tracker blocking, and granular permission management put you in control for the first time.
Added to this is the transparency inherent in open sourceThis allows you to audit what the system is doing and have greater confidence that there are no hidden processes of aggressive telemetry. Simply put: what you see is what you get, or at least you're much closer to that reality than with a closed system.
The privacy dashboard, the Wall of Shame, weekly reports, and the ability to spoof locations app by app give the user a fairly clear picture of which apps perform well and which don'tThis encourages more informed decisions and gradually pushes developers to improve their practices.
On the other side of the scale are the compatibility and maturity limitationsAlthough the list of supported devices is extensive and growing over time, not all mobile phones on the market can run /e/OS. Furthermore, certain applications that rely heavily on Google Play Services, SafetyNet, or very specific APIs may refuse to function or produce errors, which is especially noticeable in banking apps, mobile payments, or some games with aggressive DRM.
It should also be noted that /e/OS, despite being quite polished, may not feel as well-rounded as ultra-optimized commercial systems that have been iterating for over a decade. There may be minor bugs, minor graphical glitches or performance differences depending on the device. For most users who prioritize privacy, this is an acceptable trade-off; for those seeking a completely polished and seamless experience, it may be more annoying.
Going beyond /e/OS: ecosystem and alternatives
Although /e/OS is a huge step towards a Google-free mobile phone, complete de-Googleization also involves review the other services you useEmail, cloud storage, maps, browsers, media players, photo storage, etc. This is where resources like the "Wikipedia of De-Googling" come into play, a collaborative list of alternatives to each Google product.
For this type of resource, repositories such as F-Droid To install free apps, Aurora Store as an alternative client for the Play Store, privacy-focused browsers (Firefox, clean Chromium derivatives, Vivaldi, etc.), and operating systems like LineageOS, GrapheneOS or postmarketOS for those who want to experiment beyond /e/OS.
In terms of hardware, there are proposals such as FairphoneA European manufacturer that focuses on repairable devices with a long lifespan and an ethical approach, and which also sells its Murena Fairphone range with /e/OS pre-installed. There are also projects like Ubuntu Touch, Sailfish OS, and postmarketOS that explore the idea of bringing "real" Linux to mobile phones, albeit with significant sacrifices in Android app compatibility.
The common thread running through all these initiatives is the same: to offer users a realistic way out of Google's clutches and from other tech giants, without having to completely give up the convenience of a modern smartphone. /e/OS fits very well as an intermediate solution: neither as radical as abandoning Android completely, nor as complacent as official Android with Gmail, Drive, Photos and company integrated to the core.
For those who want to drastically reduce the amount of data they give away to large corporations and, incidentally, extend the life of their mobile phone with a clean and updated ROM, /e/OS has earned its reputation as “Android without Google” the most accessible and complete of the moment, especially with the maturity achieved in /e/OS 2 and the qualitative leap that /e/OS 3.0 represents with its suite of privacy tools, parental control, Murena Vault and integrated cloud services.
