"We expect Google will begin bootloader locking Pixels." That's from the GrapheneOS project on November 19, a few posts into a thread that opens with the claim that Google is "trying to convince OEM partners not to support GrapheneOS or even bootloader unlocking."
Pixels are the only phones GrapheneOS officially supports right now. If that prediction comes true, GrapheneOS loses its hardware, and the list of phones where an Android bootloader unlock still works gets very short.
I've spent the day reading the thread, the Hacker News fight it started (386 points and 136 comments when I looked), and the GrapheneOS docs. Some of what GrapheneOS says has evidence behind it and some doesn't, so I've tried to keep the two apart. After that I go through the devices GrapheneOS supports today and explain why I'd unlock sooner rather than later.
What GrapheneOS claims Google is doing
The root post and the replies under it make five claims:
- Google is making "a growing number of features and updates exclusive to Pixels."
- Google is "trying to convince OEM partners not to support GrapheneOS or even bootloader unlocking."
- In a follow-up posted just after midnight UTC on November 20: "Google has been repeatedly reaching out to OEMs to question whether they're working with us and threaten them," leaning on "GMS licensing terms found to be illegal by multiple courts."
- Play Integrity and Play Store app protection exist mainly to enforce Google Mobile Services licensing. They don't protect users, since they "deliberately permit devices with a decade of missing security patches."
- The prediction above: Pixels get bootloader-locked.
The thread is careful to separate engineers from executives. GrapheneOS says Google engineers have worked with them directly, for example by making Play services FIDO2 and passkeys work with Vanadium, its browser, and that "Google's engineers are not the problem. Their business people are the problem."
What isn't confirmed
None of this comes with documents. No OEM is named as having been contacted, and no Google employee is named either. The Pixel bootloader lock is GrapheneOS's expectation; Google hasn't announced anything.
That gap is what the Hacker News thread argued about most. One commenter wished they would "lead with evidence and sources" and called the thread "ragebait marketing." Another commenter asked the obvious question back: "Why would any OEM go on the record and put themselves in the crosshairs of Google?" They then pointed to things you can check yourself, like Pixel device trees removed from AOSP and withheld or delayed QPR source releases. Elsewhere in the thread the same person named apps Play Integrity locks people out of: IKEA Smarthome, Volkswagen and some banking apps.
My take is that the specific claim about threats to OEMs is unproven, and I'd like to see a document before I treat it as fact. The general direction isn't something you have to take on trust, though, because it has already happened at other vendors.
Samsung, OnePlus and Xiaomi already locked things down
- Samsung: in July 2025 an XDA contributor found
androidboot.other.locked=1in One UI 8 firmware, which hides the OEM unlocking toggle on non-US models too. Android Authority confirmed its own non-US Galaxy Z Fold 7 had no toggle (Android Authority). US models already lacked it. Rolling back doesn't help either: the wall of shame's Samsung page says you can't go back to One UI 7 unless the rollback protection bit matches, and an April 2026 Galaxy XR update (I610UEU2AZCI) shipped a higher SW REV that blocks downgrading to firmware with an unlockable bootloader. An earlier December 2025 update had already removed unlocking on the headset. - OnePlus: ColorOS 16 in China now requires a "Deep Testing" application, and you can apply once every 30 days. Carrier, enterprise and government units are excluded (Android Authority). It's China-only for now.
- Xiaomi: the same article notes it recently limited unlock requests to one per year.
The community-run Bootloader Unlock Wall of Shame puts Samsung and Huawei in "Avoid at all costs." Xiaomi and Motorola sit in "Just terrible." OnePlus, Sony, Fairphone and Google are in "Proceed with caution." "Safe for now" is mostly small brands like Shift, Teracube and Cubot, plus Nothing.
So whether or not Google is phoning OEMs, the number of phones you can unlock has been falling for over a year.
GrapheneOS supported devices (November 2026)
From the GrapheneOS FAQ. The dates are the end of Google's guaranteed support, and the FAQ recommends the Pixel 8 or newer because those get at least 7 years.
| Device | Support until |
|---|---|
| Pixel 10a | Mar 2033 |
| Pixel 10 Pro Fold | Oct 2032 |
| Pixel 10, 10 Pro, 10 Pro XL | Aug 2032 |
| Pixel 9a | Apr 2032 |
| Pixel 9, 9 Pro, 9 Pro XL, 9 Pro Fold | Aug 2031 |
| Pixel 8a | May 2031 |
| Pixel 8, 8 Pro | Oct 2030 |
| Pixel Fold, Pixel Tablet | Jun 2028 |
| Pixel 7a | May 2028 |
| Pixel 7, 7 Pro | Oct 2027 |
| Pixel 6a | Jul 2027 |
| Pixel 6, 6 Pro | Oct 2026 (extended support only) |
The Pixel 6 and 6 Pro are already past end of life. GrapheneOS keeps them on "extended support" as a stopgap, but it says those builds "cannot provide full security patches." Don't buy one now.
What about Motorola? Motorola announced a long-term partnership with GrapheneOS at MWC 2026 in Barcelona, with a future phone shipping GrapheneOS preinstalled. 9to5Google noted at the time that no current Motorola phone, the Signature included, met GrapheneOS's hardware requirements, and TechRepublic's coverage points to 2027. No Motorola model is officially supported yet. Asked in the Mastodon thread why Motorola hasn't been blocked, GrapheneOS replied: "They're working with us within the rules set by Google," and added that Google is "always around trying to convince OEMs to stop doing it too." It won't be cheap, either. A commenter on HN posting for the GrapheneOS team quoted the project's X account: "Signature 27 is $1599 vs. Pixel 11 Pro XL at $1299."
Carrier locks: the Verizon Pixel problem
This catches people buying used Pixels. Carrier variants get "a non-zero carrier id flashed onto the persist partition" at the factory, and the stock OS then greys out OEM unlocking (install guide). GrapheneOS's advice is to "avoid carrier variants." In the FAQ's words it's "primarily an issue with US carriers." The hardware is identical, but if the toggle is greyed out, you're stuck.
Before you pay for a used Pixel, check:
adb shell getprop sys.oem_unlock_allowed should return 1 once the toggle is on.If the seller won't let you check this, don't buy it.
How to unlock a Pixel bootloader for GrapheneOS
The web installer at grapheneos.org/install/web does all of this from a browser. Here's the CLI version from the official guide, so you know what's happening. You need fastboot 35.0.1 or newer.
# phone: enable OEM unlocking in Developer options first
# then power off, hold Volume Down while booting into Fastboot Mode
fastboot --version # must be >= 35.0.1
fastboot flashing unlock # confirm on device, this wipes everythingAfter flashing, relock:
fastboot flashing lockRelocking turns verified boot back on, now with GrapheneOS's key. The guide also recommends leaving the "disable OEM unlocking" checkbox ticked at the end of setup. If you go back to stock later, run fastboot erase avb_custom_key before you flash Google's images.
Pixel 6a owners: the factory OS image refuses OEM unlocking. Update to the June 2022 release or later and factory reset first.
Why I wouldn't wait
Samsung shows how fast this can go. On phones, one OTA removed the toggle. On the Galaxy XR, one update removed unlocking and a later one bumped the SW REV so you can't roll back. If Google ever does the same on Pixels, I wouldn't count on a warning first.
You don't have to wipe your daily driver tonight. A few cheap steps keep your options open:
- If you're buying a Pixel, buy the unlocked SKU straight from Google or a non-carrier retailer, and check the toggle the day it arrives.
- If you've been meaning to try GrapheneOS, do it on hardware you own now, while the process is still one
fastbootcommand. - If you're buying a non-Pixel, look it up on the wall of shame first.
GrapheneOS has an obvious interest in making Google look bad, and the OEM claims need evidence before I'll call them fact. But I don't need to trust them to see the pattern: Samsung closed unlocking, OnePlus and Xiaomi added hurdles, and Play Integrity keeps spreading into banking and smart-home apps. If I can unlock a phone's bootloader, I can keep it running after the vendor stops caring about it.
So: would you choose your next phone based on whether you can unlock the bootloader, or is that a niche concern nobody outside HN cares about? And which phone are you on? I'd especially like to hear from anyone whose OEM unlocking toggle disappeared after an update.
Sources
- GrapheneOS thread: https://grapheneos.social/@GrapheneOS/117645038299496084
- Hacker News discussion: https://news.ycombinator.com/item?id=50570479
- GrapheneOS FAQ (supported devices): https://grapheneos.org/faq
- GrapheneOS CLI install guide: https://grapheneos.org/install/cli
- Samsung One UI 8 unlock removal: https://www.androidauthority.com/samsung-bootloader-unlocking-disabled-one-ui-8-3581366/
- OnePlus ColorOS 16 restrictions: https://www.androidauthority.com/oneplus-bootloader-unlocking-restriction-coloros-16-3587810/
- Bootloader Unlock Wall of Shame: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame
- Motorola x GrapheneOS: https://9to5google.com/2026/03/01/motorola-confirms-grapheneos-partnership-for-a-future-smartphone-porting-features/ and https://www.techrepublic.com/article/news-motorola-grapheneos-partnership-2027/
