TL;DR: A degoogled phone is an Android device with Google's apps and Google Mobile Services (GMS) removed or replaced, so it works without a Google account or constant background Google tracking. In 2026 the simplest route is flashing a privacy-focused OS — GrapheneOS, CalyxOS or /e/OS. It needs an unlocked bootloader, not root, and unlocking wipes the phone.
By the PrivacyPortal team · Last updated June 2026.
So, what is a degoogled phone in plain English? It's an ordinary Android handset — usually a Google Pixel — where the Google layer that normally sits underneath every app has been taken out or swapped for open-source stand-ins. You still get apps, messaging, maps and a camera; you just get an Android without Google quietly logging your location, contacts and activity in the background. People choose a de-Googled phone to cut tracking, escape ad profiling and actually own the device they paid for. Below we cover how it works, the main 2026 options compared, whether you need root (you don't), a real step-by-step to remove Google from Android on a Pixel, and the pitfalls that trip people up.
What is a de-Googled phone, exactly?
Stock Android is really two layers: the open-source base (the Android Open Source Project, or AOSP) and a proprietary Google layer on top — the Google apps plus Google Mobile Services (GMS), the background framework that handles push notifications, location, sign-in and app verification. A de-Googled phone keeps the open base and removes or replaces that Google layer.
In practice that means one of two things:
- Replace GMS with microG, an open-source reimplementation, so apps that expect Google's libraries still run.
- Sandbox Google Play as an ordinary, unprivileged app (the GrapheneOS approach), so you can use Play Store apps without giving Google system-level access.
The result is a google free phone: no mandatory Google account, no forced Google sign-in, and no GMS phoning home by default. You decide what, if anything, gets to talk to Google.
A de-Googled Pixel home screen running GrapheneOS, with F-Droid and Aurora Store in place of the Google Play Store.
What you gain — and what you give up
De-Googling is a trade, not a free lunch. Knowing both sides up front saves disappointment.
What you gain:
- No background Google tracking or ad profiling tied to your account.
- Far fewer pre-installed apps and telemetry, plus granular control over network and sensor permissions.
- On hardened systems, genuine security upgrades — stronger sandboxing, hardened memory allocation and faster patching than many stock phones.
What you give up (or have to work around):
- Some Google conveniences: seamless Google Wallet tap-to-pay, Find My Device and instant RCS messaging may not work or need extra setup.
- Push notifications can be less reliable through microG than through full GMS.
- Some banking, social or DRM apps may refuse to run on a modified OS — and no project can promise otherwise.
- You become responsible for updates, so choose an OS with a strong security-patch record.
The main de-Googled phone options in 2026
Four projects dominate de-Googling in 2026. They differ mainly in which phones they run on, how they replace Google, and how hardened they are by default.
| OS | Supported devices (2026) | Google replacement | Hardened by default? | Best for |
|---|---|---|---|---|
| GrapheneOS | Google Pixel only (Pixel 6 series and newer) | Optional sandboxed Google Play, no special privileges | Yes — the strongest | Security-first users on a Pixel |
| CalyxOS | Pixels plus a small number of other models — check the list | microG (optional), or no Google at all | Moderate | Privacy with a gentler learning curve |
| /e/OS (Murena) | Wide range: Fairphone, many Samsung, Pixel and more | microG built in, plus an optional de-Googled cloud | Light | Beginners wanting a turnkey google free phone |
| LineageOS | Very wide, including older devices | None by default (add a microG build or Google apps yourself) | No — general purpose | Tinkerers and reviving old hardware |
GrapheneOS supports only Google Pixel phones, citing their verified boot, hardware-backed security and years of guaranteed updates as requirements it won't compromise on.
If you want maximum hardening and own a recent Pixel, GrapheneOS is the usual pick. For a de-Googled phone on a Fairphone or Samsung, /e/OS has the widest reach. LineageOS is the most flexible but is not privacy-hardened on its own — treat it as a clean android without google, not a security product.
microG vs sandboxed Google Play: how your apps still work
The big worry is always: "will my apps run on an android without google?" Usually yes, through one of two mechanisms.
microG is an open-source reimplementation of Google Play Services. It speaks the same language apps expect — push messaging, location, maps — but it isn't Google's code, and you control what it's allowed to do. CalyxOS, /e/OS and microG builds of LineageOS use it.
microG is an independent, open-source reimplementation of Google Play Services — not Google's software — letting apps that depend on Google's libraries run on a phone with no Google apps installed.
Sandboxed Google Play is the GrapheneOS approach: you can optionally install the real Play Store and Play Services, but they run as ordinary apps in the standard sandbox with no special system privileges. You get strong app compatibility while Google gets no more access than any other app you install. You can read how the microG project documents its compatibility goals on its own site.
For apps that don't use Google libraries, you need neither: install F-Droid for open-source apps and Aurora Store (an anonymous front-end to the Play Store) for everything else.
microG's settings panel lets you toggle exactly which Google-compatible services — such as push notifications — are switched on.
Does a de-Googled phone need root? No — and here's the difference
De-Googling and rooting are two different things, and confusing them causes a lot of grief.
De-Googling needs an unlocked bootloader so you can flash a new OS — but the privacy OSes then ask you to re-lock the bootloader for verified boot. You do not get, or need, root access.
Rooting (with tools such as Magisk, KernelSU or APatch) gives you superuser control to modify the running system. It's a separate, riskier choice that weakens verified boot and is far more likely to break banking apps.
Google retired the legacy SafetyNet Attestation API in favour of the Play Integrity API by early 2025; apps now use Play Integrity to check whether a device is "certified", which is why some banking apps reject rooted or heavily modified phones.
Plenty of banking apps work fine on a stock-but-de-Googled GrapheneOS install with sandboxed Play; many stop working once you root. We can't promise any setup will pass a specific bank's Play Integrity checks — banks change the rules often. If banking is critical, test before you commit, and read our guide to Play Integrity and banking apps.
How to de-Google a Pixel with GrapheneOS: step by step
This is the most beginner-friendly way to remove Google from Android in 2026, because GrapheneOS has a browser-based installer. It works on a supported Pixel from any computer with a Chromium-based browser (Chrome, Edge, Brave or Vanadium). Set aside about an hour.
The GrapheneOS web installer runs in your browser and walks you through unlocking, flashing and re-locking the bootloader.
Before you start — real risks: unlocking the bootloader wipes the entire phone, so back up everything first. A carrier-locked Pixel (some US carrier models) may refuse to unlock the bootloader, and a wrong step can leave the phone temporarily unbootable. Confirm your exact Pixel is on the official supported-devices list before buying or flashing.
Prerequisites:
- A supported Google Pixel (currently the Pixel 6 series and newer — verify on the GrapheneOS device list).
- A good-quality USB-C cable and a computer (Windows, macOS, Linux or ChromeOS).
- A Chromium-based browser with WebUSB support.
- A full, tested backup of your data.
- Back up everything — photos, messages, app data and 2FA seeds. The process erases the device with no undo.
- Charge the phone to at least 50% to avoid a mid-flash shutdown.
- Enable Developer options: Settings → About phone → tap Build number seven times. Then Settings → System → Developer options and turn on OEM unlocking and USB debugging.
- Open the web installer: on your computer, go to the official GrapheneOS web installer and connect the Pixel with the USB-C cable.
- Boot into the bootloader: follow the installer's prompt (power off, then hold Volume Down + Power) until the phone shows the fastboot/bootloader screen.
- Unlock the bootloader: click Unlock bootloader in the installer and confirm on the phone. This wipes all data.
- Flash GrapheneOS: click Download release, then Flash release. Let it finish without unplugging — it downloads and writes the OS.
- Re-lock the bootloader: click Lock bootloader and confirm on the phone. This re-enables verified boot, which protects you against tampering. Do not skip this step.
- Boot and set up: start GrapheneOS and complete the setup wizard. Optionally install sandboxed Google Play from the built-in Apps app if you need Play Store apps.
Verify it worked: after first boot you'll see the GrapheneOS welcome screen, and Settings → About phone lists the GrapheneOS build. For extra assurance, the built-in Auditor app confirms verified boot is active and the OS is genuine. There's no Google account prompt anywhere in setup — that's your sign the phone is truly de-Googled. Direct links to GrapheneOS, F-Droid, Aurora Store and Auditor are in the files section at the end of this guide.
Common de-Googling pitfalls (and how to avoid them)
- Buying the wrong phone: some carrier-locked Pixels can't unlock the bootloader. Buy an unlocked model, or a phone that's already configured.
- Skipping the backup: unlocking wipes everything, and there is no recovery.
- Leaving the bootloader unlocked: it disables verified boot and weakens security. Always re-lock when the OS supports it.
- Expecting every app to work: some banking, social or DRM/streaming apps misbehave on microG or refuse modified devices. Test the apps you can't live without.
- Choosing LineageOS for privacy: it's a clean android without google, but it isn't hardened. Pick GrapheneOS or CalyxOS if security is the goal.
- Neglecting updates: a de-Googled phone is only as safe as its patch level. Favour projects shipping monthly security patches.
- Losing tap-to-pay: Google Wallet generally won't work, so plan to use a physical card or your bank's own NFC, if supported.
Which de-Googled phone path is right for you?
Use this quick decision guide:
- You own a Pixel and want the strongest privacy and security: install GrapheneOS.
- You want hardening but a gentler setup, on a Pixel: consider CalyxOS.
- You have a Fairphone or Samsung, or want something turnkey: /e/OS by Murena.
- You're reviving an old phone or love to tinker: LineageOS (add a microG build for app compatibility).
- You'd rather not flash anything yourself: buy a phone that arrives ready to go.
That last option is where we come in: PrivacyPortal sells de-Googled phones flashed, hardened and tested, so you skip the bootloader steps entirely. Prefer to do it yourself? Our GrapheneOS vs CalyxOS comparison goes deeper on picking an OS.
Frequently asked questions
Is a de-Googled phone legal?
Yes. Modifying a device you own — unlocking its bootloader and installing a different operating system — is legal in the UK and most countries. You're changing your own property, not bypassing anyone else's security.
Will my banking apps work on a degoogled phone?
Often, but not always. Many UK banking apps run on GrapheneOS with sandboxed Google Play, while microG-based systems and rooted phones are more likely to fail Google's Play Integrity checks. No one can guarantee a specific bank will work, so test the apps you depend on before switching fully.
Does de-Googling delete WhatsApp, my camera or maps?
No. You can still install WhatsApp (via Aurora Store), use the camera, and run maps apps such as Organic Maps or even Google Maps. You're removing Google's background services, not your ability to install apps.
Do I need to root my phone to remove Google from Android?
No. De-Googling only needs a bootloader unlock to flash the new OS, and you re-lock it afterwards. Root is a separate, riskier step that you don't need and that can break more apps.
Can I go back to stock Android later?
Usually yes. On Pixels you can re-flash Google's official factory image to return to stock — though it wipes the device again. Keep your original backup just in case.
What's the easiest de-Googled phone for a beginner?
A Pixel with GrapheneOS, thanks to its browser-based installer, or a phone that arrives pre-configured. /e/OS is the friendliest if you want a wide choice of non-Pixel hardware.
Modules, apps & files to try
Here are the actual tools the rooting community uses for this, each linked to its official source. They're third-party community projects, so download only from the official page below, back up your boot.img first, and follow each project's own instructions. PrivacyPortal isn't affiliated with these projects and can't guarantee third-party files — flash at your own risk.
| File | What it is & how to use it safely |
|---|---|
| Magisk (GITHUB) | The original and most widely used Android root manager; systemless root via boot-image patching, with built-in Zygisk, a module system and a DenyList for hiding root. Download ONLY from the official repo github.com/topjohnwu/Magisk — its README states GitHub is the sole official source, and third-party "Magisk Manager" sites/APKs are frequently repackaged with malware. Rooting trips Play Integrity and can brick a device: back up your stock boot.img before patching/flashing, and never flash a Magisk ZIP/APK obtained from a Telegram link or random mirror. |
| KernelSU (GITHUB) | The original kernel-based root manager — implements root as a kernel module rather than patching the boot ramdisk like Magisk; needs a GKI 2.0 or KernelSU-supported kernel. Official open-source (GPL) project, actively maintained — latest KernelSU v3.2.4 (Apr 2026). Kernel-level root requires a GKI 2.0 / kernel 5.10+ device (older 4.14+ kernels need a manually built kernel). Only download from the official GitHub Releases page (github.com/tiann/KernelSU/releases), never a Telegram link or mirror; verify the .apk/kernel matches your exact device and back up your boot.img before flashing, as a bad kernel image can bootloop the device. The companion KernelSU-Next fork (github.com/KernelSU-Next/KernelSU-Next) is also legitimate and supports wider kernel ranges (4.4–6.6). |
| APatch (GITHUB) | Kernel-level Android root manager that patches the kernel image directly and provides its own KPM (Kernel Patch Module) system; an alternative to Magisk and KernelSU. APatch is a legitimate open-source, kernel-level root manager (built on KernelPatch; UI/module code derived from KernelSU). Only download the APK from the official GitHub Releases page (github.com/bmax121/APatch/releases) or the official docs at apatch.dev — avoid third-party APK mirrors. Because it patches the kernel directly, ALWAYS back up your boot.img before flashing, and choose a strong SuperKey: the SuperKey has higher privileges than root, so a weak or leaked key can hand full control of your device to an attacker. Rooting voids warranties, can trip banking/Play Integrity checks, and a bad patch can bootloop the device. |
