Google Pixel Root 指南：镜像和分区选对，比步骤看起来简单更重要

非受限版本有官方 Fastboot 和工厂镜像路径，便于安装与恢复。但运营商受限设备是重要例外。

不能这样理解。Root 是否可用与应用是否接受设备是不同问题，硬件安全状态可能影响证明和凭据。

Different tools for different goals. (1) Magisk root grants superuser access — install AdAway, Tasker with system-level automation, Greenify deeper, Titanium Backup, custom kernels, Magisk modules. The user retains stock Pixel Android with root added on top. Banking-app compatibility moderate (with hiding stack). (2) GrapheneOS replaces stock Android with a privacy-and-security-hardened distribution — hardened memory allocator, sandbox-based Google Play services (apps run with reduced permissions), per-app network and sensor permissions, expanded permission controls, hardened browser. The user gets significantly better privacy + security + better-than-stock permission model, but loses root access (GrapheneOS does not support concurrent root by design — root would weaken the security model). For most users wanting customization + power-user features, Magisk root is the right path. For users with elevated threat models prioritizing privacy + security, GrapheneOS is the right path. The two are mutually exclusive on a given device — pick one.

需要超级用户、模块与修改时考虑 Magisk；优先安全和隐私、接受不使用 Root 时评估受支持的 GrapheneOS。

Manufacturer warranty: yes, in policy — bootloader unlock voids Google's manufacturer warranty. Practical reality: (1) Google service centres are often more accommodating than Samsung for hardware-defect claims on previously-unlocked Pixel devices; varies per service centre and per region. (2) US Pixel — Google service via mail-in is variable; some claims accommodated, some refused based on inspection. (3) UK/EU Pixel — EU consumer law (Sale of Goods Directive) requires Google to honour hardware-defect statutory rights independent of bootloader status for EU purchases for the legal warranty period. (4) Out-of-warranty paid repair unaffected. (5) The Pixel warranty experience post-unlock is generally less restrictive than Samsung's, but more restrictive than the ‘relock and reflash will hide it' optimistic narrative — Google can detect previous unlock through firmware metadata even after relock + stock reflash. The right framing: assume manufacturer warranty is gone; rely on EU consumer law for hardware defects in EU; budget for paid repair elsewhere.

Both root cleanly with current Magisk. Differences: (1) Pixel 5 and older — pre-Titan-M2; simpler from a Play Integrity perspective; some banking apps work without Tricky Store; older hardware so eventual security-update sunset matters. Currently still receives Android 14 OTAs but software support timeline shorter. (2) Pixel 6/6a — first Titan-M2 generation; some early-Titan-M2 quirks resolved by Magisk + community by 2023; mature rooting target. (3) Pixel 7/7a — refined Titan-M2; mature target; significant value at used-market prices. (4) Pixel 8/8a — newer Tensor G3; longer software support (7 years from launch per Google's policy); still mature rooting target by 2026. (5) Pixel 9/9 Pro/9 Pro Fold — newest; longest software support runway; current generation as of 2026. For most rooters in 2026-2026, Pixel 7a or Pixel 8a are the value sweet spots — mature Titan-M2, full software support runway, cleaner banking-app compatibility post-root than newer Pixel 9 (less time for community to refine integrity stack).

Depends on threat model and use case. (1) For users with elevated threat models — journalists handling sensitive sources, activists in adversarial regions, dissidents under state surveillance, executives in high-value-target industries, security professionals — yes. GrapheneOS provides industry-leading consumer Android security and privacy. (2) For users who value privacy as a principle but face mainstream threat models — variable. GrapheneOS provides meaningful privacy benefits over stock Pixel but at the cost of some compatibility (banking apps, Google Pay, some apps). (3) For users who want customization (Tasker automation, AdAway, custom kernels) — no, GrapheneOS does not support root by design; choose stock-Pixel + Magisk instead. (4) For users who want both privacy + customization — pick the priority; you cannot have both on the same device simultaneously. The honest framing: GrapheneOS is the right choice for elevated threat models; Magisk on stock Pixel is the right choice for power-user customization on a single device.