Skip to main content


Don't just Degoogle,
Zero Google.

As Google shifts to put AI and "Find my device" in the hardware itself, who knows if this corrupt and evil company secretly has backdoors in Pixels. We just don't know.

Introducing the first of our "Zero Google" non-Pixel Phones,
LineageOS OnePlus 9
Carrier Unlocked
No Battery Cycles, Brand New
Mint condition, Black
3 Month Warranty from us
Secured by a binding arbitration XMRBazaar deposit
Optional 6-month VPN subscription as well.
$320 in Bitcoin or Monero.

In theory, the "find my device" needs a google account to be activated. And if you trust that, then we offer Pixels with GrapheneOS.

But if you don't, and you want to completely separate your ties from Google, then this is an easy, low-cost way, to keep your name off the IMEI for geolocation tracking from celltowers, save time with Lineage's setup, and get an amazing price for a mint condition brand new device.

Reach out either way for Graphene or Lineage. It's not for me to decide, it's your device:
simplifiedprivacy.com/contact.…

in reply to SimplifiedPrivacy

OnePlus 9 is end-of-life without basic driver/firmware patches. LineageOS misleads users with an inaccurate Android security patch level. Devices without basic privacy and security patches do not provide users with the bare minimum for privacy. LineageOS itself significantly lags behind on providing patches and does not maintain the standard privacy/security model.

Aside from that, it's absolutely not "Zero Google" in any sense.

in reply to GrapheneOS

No need for backdoors when those devices and the OS have known serious unpatched privacy and security vulnerabilities. OnePlus 9 end-of-life was March 2025.

The software is near entirely written by Google and it's still using Google's work at a hardware and firmware level too. LineageOS always connects to multiple Google services and gives highly privileged access to Google apps and services. How is that "Zero Google"?

in reply to GrapheneOS

Quite strange to make unsubstantiated claims about backdoors while selling devices with serious known unpatched security vulnerabilities.

GrapheneOS isn't going to take the shortcut of supporting insecure devices to expand usage share while misleading people. That's why we're working with OEMs towards their devices meeting reasonable security standards.

Profiting from our work while spreading FUD about us is an interesting move.

in reply to GrapheneOS

Look. Graphene OS does security very well. But it is supporting only Pixel phones. Other OS's like lineage are maby really barebone and have the goal to help every smartphoneuser to extend its lifetime.

The war you are fighting against ROM's is no help to the privacy space. You need to accept, that different solutions tackle different problems. With all its downs and ups. You paint all in black and white. And through this you always missrepresent reality very badly.

in reply to freemymind 🇨🇭

> Look. Graphene OS does security very well.

GrapheneOS is a privacy project. The bare minimum required for privacy is providing important privacy and security patches.

> Other OS's like lineage are maby really barebone and have the goal to help every smartphoneuser to extend its lifetime.

No, this is an unsafe device without basic patches. It's not extended.

in reply to GrapheneOS

The main issue with this device is that it has serious known vulnerabilities which are not patched and not going to be patched. It has been end-of-life since after March 2025. LineageOS sets an inaccurate Android security patch level. Selling users a blatantly insecure device without informing them is in fact selling them a backdoorred device.
in reply to GrapheneOS

> The war you are fighting against ROM's is no help to the privacy space.

We're doing no such thing, and you should also use the correct terminology. These are not ROMs. They're operating systems.

> You paint all in black and white.

It's a clearly insecure and non-private device. Basic patches are the bare minimum. It is black and white in this case.

in reply to GrapheneOS

> And through this you always missrepresent reality very badly.

We've done absolutely no such thing. This device is end-of-life since after March 2025. It doesn't get driver and firmware privacy/security patches. It's vulnerable to known remote code execution vulnerabilities which will not be patched. Using LineageOS does not provide the patches. It 's unsafe.

in reply to freemymind 🇨🇭

They are reacting to claims of selling devices that should be somehow secure by "zero Google", which is no longer the case.

This use case is not about extending life span of your device but about somehow selling you a device with claims of increased privacy that are completely wrong

in reply to Juraj

But noone is advertising security. The article is very explicit in helping to avoid Google tracking.

So I actually would say this is a fair transparent offer. That Lineage has security concerns can be a good additional information. But it does not take away any of the value of the original offer.

Therefore I see @GrapheneOS comment as agressive and no real support of #grapheneos nor #privacyand #security .

It is attacking claims that have not been made. Like when I would say to drink a coffee and then you want me not to drink it because of the bad effects of smoking on my health. Complete misdirected critique.

in reply to freemymind 🇨🇭

> But noone is advertising security. The article is very explicit in helping to avoid Google tracking.

They're advertising devices with serious known privacy and security issues as being private. They're advertising devices which heavily involve Google as "Zero Google". They're not "Zero Google".

in reply to GrapheneOS

LineageOS connects to multiple Google services by default. AOSP is almost entirely made by Google. Linux kernel is heavily made by Google. OnePlus hardware is in partnership with Google to their specifications, includes their attestation root, includes Google code at a firmware level, etc.
in reply to GrapheneOS

> it does not take away any of the value of the original offer.

The product is not what it's claimed to be. Selling people highly insecure and non-private devices without basic patches without informing them is wrong. Strange to make unsubstantiated claims about backdoors when doing it.

in reply to GrapheneOS

Providing accurate info is not aggression or harassment as you keep claiming. Informing people is not wrong.

They were the ones to make unsubstantiated claims about backdoors while selling devices known to have serious unpatched vulnerabilities which won't be fixed. Which is backdoored again?

in reply to GrapheneOS

OnePlus 9 never provided a reasonable level of security. It never provided proper support for securely using an alternate OS either. However, after March 2025, things are much worse because it's not getting important patches anymore. It has serious vulnerabilities which will never be patched.
in reply to GrapheneOS

Do you think it's right to sell people a device with known vulnerabilities with an OS setting an inaccurate Android security patch level and downplaying the important of those? What do you call hiding and downplaying known vulnerabilities if not selling people a backdoored device?
in reply to GrapheneOS

> Do you think it's right to sell people a device with known vulnerabilities with an OS

No. It is not ok. And important to be corrected.

Same counts for upplaying a threat. Is also harmful to security and privacy. Since every person has an individual threat level. When we can improve the basic security and privacy level, this is great, when it comes at no cost. And in every other case it is up to the reader to decide what level of security and privacy is the best for her/him.

in reply to freemymind 🇨🇭

> No. It is not ok. And important to be corrected.

Yet you're repeatedly misrepresenting our statements and attacking us for doing so with accurate and verifiable information.

> Same counts for upplaying a threat.

We're doing no such thing. Basic privacy and security patches are very important.

in reply to GrapheneOS

The topic is people being sold an insecure end-of-life device missing important privacy and security patches. These missing patches will continue to massively grow over time. Nearly all privacy and security experts will tell you the importance of patching known vulnerabilities. It's the basics.
in reply to GrapheneOS

in reply to freemymind 🇨🇭

> Look, you really fail at bringing in threat levels.

No, we don't. Lack of basic privacy and security patches fails to meet even the most basic threat level. Someone using a device without those is putting their contacts and the health of the overall internet at risk, not only themselves.

in reply to GrapheneOS

A device not patching serious known privacy and security patches for very long periods of time is not doing the bare minimum. It has atrocious privacy and security. This is part of the absolute bare minimum baseline which everyone should expect and should receive from every product they purchase.
in reply to GrapheneOS

It's bad enough for a company like Walmart to be selling people laptops, phones and embedded devices without basic privacy and security patches for a reasonable time period. It should not be happening. When a product without that is specifically marketed to people who care about privacy, that's worse.
in reply to GrapheneOS

> discuss.grapheneos.org/d/14304…

This shows us steering people away from extraordinarily insecure and non-private options. No one should be using devices without basic privacy and security patches. It's the bare minimum every product should provide. A $50 phone from Walmart SHOULD provide it for years.

in reply to GrapheneOS

> And since you fail with this consistantly, I have a very hard time to beliefe anything you say.

We do no such thing. You continuously posts these irrational appeals to emotion where you misrepresent what we have said and done. You do not actually try to read and understand what we've posted.

in reply to GrapheneOS

You keep attacking us with false claims and misinformation in response to accurate and verifiable info which goes against your beliefs. You think if something doesn't align with your beliefs, then it isn't true. You choose which things you think are true based on what you want to be true. It's silly.
in reply to GrapheneOS

Hey @GrapheneOS thanks for writing in. Can you elaborate on which CVEs are unpatched that you feel are a critical threat for the OnePlus 9 hardware or LineageOS? Especially regarding remote access
in reply to SimplifiedPrivacy

Here are Qualcomm's security bulletins:

docs.qualcomm.com/product/publ…

Here are Android's security bulletins:

source.android.com/docs/securi…

Each Android Security Bulletin is divided in 2 parts. The first YYYY-MM-01 part has AOSP userspace patches. The second YYYY-MM-05 part has kernel, driver and firmware.

in reply to GrapheneOS

OnePlus 9 with LineageOS is not receiving any of the driver and firmware patches anymore. It only has those up to the last patch level provided by OnePlus. You can look through the bulletins and see the many issues which are not getting patched. OnePlus declared it end-of-life in March 2025.
in reply to GrapheneOS

Android Security Bulletins are backports of a SUBSET of the Android privacy/security patches to older releases of Android. You can see everything listed in the Android Security Bulletins has High or Critical severity because they don't backport the Low or Moderate severity patches in general.
in reply to GrapheneOS

Android Security Bulletins are the subset of AOSP privacy/security patches backported to older releases and a small subset of driver/firmware related patches for the small scope they cover. For a Snapdragon device, Qualcomm lists the main set of additional driver/firmware related patches.
in reply to GrapheneOS

There are also additional patches required for other drivers and firmware for other components not made by Qualcomm.

Here's the Pixel June 2025 Update bulletin listing the additional driver/firmware patches:

source.android.com/docs/securi…

Only around 1 patch there is actually Pixel specific (TPU).

in reply to GrapheneOS

Modem/RIL/rild refer to Samsung Exynos cellular. DRM LDFW refers to an Exynos component. Bluetooth and WLAN refer to Broadcom or Qualcomm Wi-Fi/Bluetooth. NVT is for the display/touchscreen. Fingerprint sensor is self explanatory. All devices have components with driver/firmware patches tied to them.
in reply to GrapheneOS

Full Android Open Source Project privacy and security patches requires being on Android 16. Low and Moderate severity patches are not backported to Android 15. High and Critical severity patches are nearly all backported but often with 1-2 month delay. Android Security Bulletins are what's backported.
in reply to GrapheneOS

LineageOS on a OnePlus 9 is fully missing the ongoing driver and firmware patches listed in the Qualcomm security bulletin, Android security bulletin and relevant ones listed elsewhere. The device is end-of-life, so it doesn't receive them. LineageOS doesn't provide them another way.
in reply to GrapheneOS

LineageOS incorrectly raises the Android security patch level based on shipping the AOSP security backports despite Android security bulletins requiring more than that. Devices also each extend the patch level based on the hardware they use, but the Android security bulletin does cover a little bit.
in reply to GrapheneOS

Based this is true, this can be a concern for phones with alternatives, which deliver same or better update levels. When there is no competition, still better to go for LineageOS than staying completely without patches.
in reply to freemymind 🇨🇭

The topic is not someone having an insecure, end-of-life device where they want to make it less bad. The topic is someone selling people devices marketed as a privacy product. People do not already have these devices but rather are buying them. You're going so far to misrepresent and spin things.
in reply to GrapheneOS

> The topic is not someone having an insecure, end-of-life device where they want to make it less bad.

When you critique LineageOS as a whole you are including the end of life devices. And this is what you did in the first comment.

You seem to not care about reputation at all. Show me a comment, where you publicly claim to be wrong or missrepresented.

in reply to freemymind 🇨🇭

The device being sold is an end-of-life OnePlus 9 with LineageOS. That was the topic. LineageOS lags behind on shipping patches including on Pixels where it will likely miss the driver and firmware security patches for at least 3 to 4 months, possibly longer. That's a serious problem, not a niche one.
in reply to GrapheneOS

> You seem to not care about reputation at all. Show me a comment, where you publicly claim to be wrong or missrepresented.

You've repeatedly misrepresented our statements and lied about us in this thread. Most of your replies are example of it. You use our work but desperately try to harm us.

in reply to GrapheneOS

As we said previously, we're not interested in engaging with your trolling much further. We'll be switching to responding to it through publishing more accurate information about this across platforms. We plan to make a Nostr account and can simply stop this one being bridged there.
in reply to GrapheneOS

I went through this again and the Qualcomm list did not sway me. But more careful review of the android one does. CVE-2025-27363 changed my mind. I knew about easier access without locked bootloader and such, however remote access is a different animal. You're correct that speculation about backdoors in Google hardware are meaningless in the face of known remote access vulnerabilities. I will pull the offer.

Ultimately though I do believe that neither you, nor I, should decide if everyone is forced into a Pixel. We offered this to let the end-user decide. I see from your posts in general, that you are looking to and working with other hardware in the future. I hope that works out. Graphene software is top notch.

But while you have changed my mind today with this particular OnePlus 9/Lineage offer, in the long-term, if we're having this same discussion 2-3 years from now, we will offer alternatives. The end user should have choices.

in reply to SimplifiedPrivacy

We weren't only referring to the July 2025 bulletin at docs.qualcomm.com/product/publ… but rather their bulletins in general. The July 2025 one we linked lists multiple remote code execution vulnerabilities impacting the OnePlus 9. OnePlus 9 has a Snapdragon with Qualcomm cellular, Wi-Fi, Bluetooth and GNSS.
in reply to GrapheneOS

That July 2025 Qualcomm bulletin has a critical severity remotely exploitable GPS vulnerability. It also lists a bunch of relevant High severity vulnerabilities.

June 2025 Qualcomm bulletin has a remotely exploitable GPU vulnerability and a bunch of relevant High severity ones.

There are more.

in reply to GrapheneOS

Many of those vulnerabilities in the Qualcomm bulletins are remotely accessible. They consider attacks via proximity through Wi-Fi, Bluetooth, etc. to be less severe than ones remotely exploitable over the internet or cellular without direct access to the local cellular network.
in reply to GrapheneOS

CVE-2025-27363 is one of the remote vulnerabilities fixed in the userspace AOSP code so LineageOS does eventually ship them but often with weeks of delay.

There are already multiple relevant remote vulnerabilities in Qualcomm drivers and firmware. There will be far more of them. They won't be fixed.

in reply to GrapheneOS

OnePlus does not take security very seriously and does not allow another OS to be installed securely with the hardware-based security like verified boot intact.

Aside from that, your claim that a OnePlus device is somehow more trustworthy and less likely to have backdoors simply doesn't make sense.

in reply to GrapheneOS

> Graphene software is top notch.

GrapheneOS depends on hardware-based security features used by Android and GrapheneOS. It also depends on driver and firmware security patches. A highly private and secure OS with insecure hardware/firmware underneath isn't a highly private and secure device.

in reply to GrapheneOS

Our work wouldn't properly protect users if we did it on top of OnePlus devices. We'd be missing not only a bunch of our core features but also standard Android security protections and patches. The reason we don't support their devices or others is because they don't meet basic security standards.
in reply to GrapheneOS

People do have many choices. We aren't saying people shouldn't have the option to use LineageOS or a OnePlus 9. What we're saying is that it has poor privacy or security.

We're aware having a non-Pixel device would make people happy and are working towards a secure one, which is not yet available.

in reply to GrapheneOS

I am excited for when this is available/comes out. thanks for your team's work
in reply to SimplifiedPrivacy

As long as it goes well, the initial device should hopefully be available in 2026 or 2027. It will be a regular mainstream Android device with a flagship Snapdragon SoC meeting our currently documented requirements. We can't guarantee it will work out but it's proceeding. It's still early right now.
in reply to GrapheneOS

Pixel is made by Google. I understand what you're saying, but why is there no graphene like alternative ROM for non google phones?
in reply to mister_monster

OnePlus devices are Google Mobile Services devices made in partnership with Google. Android Open Source Project is made by Google.

There isn't a similar OS in the same space as GrapheneOS made for other devices and there cannot be one.

This entry was edited (5 months ago)
in reply to GrapheneOS

Pixels are currently the only devices meeting the very reasonable and important security requirements we have listed at grapheneos.org/faq#future-devi…. It's not possible to provide something comparable to what we do on other devices yet.
in reply to GrapheneOS

GrapheneOS is not going to take the shortcut of adding insecure devices where we can't properly protect users to expand our usage share. We're working with a major Android OEM towards some of their devices meeting these requirements.
in reply to GrapheneOS

You can see from the high quality third party comparison at eylenburg.github.io/android_co… other Android-based OSes are far different and not focused on privacy and security in the same way. That's why they support devices with poor security.
in reply to GrapheneOS

GrapheneOS only supports Pixels because Pixels are currently the only devices where an alternate OS can provide a high level of security. Other devices with the listed security features don't allow another OS either at all or securely.
in reply to mister_monster

We list our hardware requirements at grapheneos.org/faq#future-devi…. Other devices don't provide the expected security features and updates. Most devices don't allow using another OS securely but rather if they do allow it, cripple security.
in reply to freemymind 🇨🇭

Lineageos connects to Google servers immediately. Which @GrapheneOS account also pointed out. It's especially not good against Google tracking.
in reply to Juraj

This is great to point out. For me a person needs to argue fine grained, so I could think they understand of what they are speaking. And this I have never seen from @GrapheneOS account.

I am always open to change this view, when I see finegrained well explained critique, including sources.

These kind of critique just seems like the user is not working scientifically at all. And when he leads to people thinking that nonscientific work would be accepted within the graphene project, then it takes away a lot of credibility of the project.

in reply to freemymind 🇨🇭

> This is great to point out. For me a person needs to argue fine grained, so I could think they understand of what they are speaking. And this I have never seen from @GrapheneOS account.

We provided that information above in what you replied to. You do not read and try to understand our posts.

in reply to GrapheneOS

> I am always open to change this view, when I see finegrained well explained critique, including sources.

We provided accurate and verifiable information. We linked to the 3rd party table at eylenburg.github.io/android_co… with highly accurate info vetted by many people publicly. They accept corrections.

in reply to GrapheneOS

> These kind of critique just seems like the user is not working scientifically at all.

You dislike the accurate and verifiable information we provide, so you disregard it. You pretend we've said and done things we haven't. Info we've provided here and elsewhere about this is accurate/verifiable.

in reply to GrapheneOS

I just checked the whole thread. And this link you posted now. Can you refer to the post you linked this link in our thread? Or are you so dishonest to just lie in my face and hope this would recuperate your underground reputation?
in reply to freemymind 🇨🇭

> Or are you so dishonest to just lie in my face and hope this would recuperate your underground reputation?

Jul 21, 2025, 01:24 AM:

grapheneos.social/@GrapheneOS/…

Jul 21, 2025, 06:11 AM:

grapheneos.social/@b7cf9f42a79…

The fact is that you repeatedly make false claims including about what we've said.


LineageOS connects to multiple Google services and gives privileged access to Google apps and services:

eylenburg.github.io/android_co…

LineageOS Is based on AOSP, which is nearly entirely written by Google. OnePlus devices are made in partnership with Google to meet their specifications and use Google's work at a lower level below the OS too. Hardly "Zero Google".


in reply to GrapheneOS

This is within an other branch. Same main note but an other branch of it.
I hope you do not expect people, to read all your comments spread to different threads and branches?

> The fact is that you repeatedly make false claims including about what we've said.

Go on with your unproofen claims and go on digging your grave of distrust. I keep on calling you out, when you fail to correct. Even opensource projects have to be user-centric to have success. When you understand this, you can start to add value to the project.

in reply to freemymind 🇨🇭

We expect you to actually try to read and understand what we've written instead of glancing at it and then attacking us claiming we've said and done things we haven't. You're responding to someone lauding them for providing information we provided in this thread, including in this branch of it.
in reply to GrapheneOS

Here's from this branch of the thread:

grapheneos.social/@GrapheneOS/…

We explained how LineageOS always connects to multiple Google services and gives highly privileged access to Google apps and services.

It is also clearly based on AOSP and the device in question is a Google Mobile Services device.


No need for backdoors when those devices and the OS have known serious unpatched privacy and security vulnerabilities. OnePlus 9 end-of-life was March 2025.

The software is near entirely written by Google and it's still using Google's work at a hardware and firmware level too. LineageOS always connects to multiple Google services and gives highly privileged access to Google apps and services. How is that "Zero Google"?


in reply to GrapheneOS

> Go on with your unproofen claims and go on digging your grave of distrust.

All of the information we've provided is accurate and verifiable. You aren't responding to us with facts or rational arguments. Instead, you make false claims about what we've said and irrational emotional appeals.

in reply to GrapheneOS

You're demonstrating you've hardly read anything we've written or looked at any of the provided sources because we link eylenburg.github.io/android_co…, privsec.dev/posts/android/choo… and other content as part of standard templates we copy and then modify before posting. We've linked it to that hundreds of times.
in reply to GrapheneOS

There is Leneage with MicroG, which replaces most needed Google services quiet well.

I really do not feel, as if you are intrested to help people. You herrass solutions without proposing better ones. When ones concern is Google, than de-Googeling the phone actually helps a lot in this regard.

in reply to freemymind 🇨🇭

> There is Leneage with MicroG, which replaces most needed Google services quiet well.

LineageOS always uses multiple Google services:

eylenburg.github.io/android_co…

microG is also primarily an implementation of Google services.

> You herrass solutions without proposing better ones.

We're providing accurate information. Devices without basic patches aren't private.

in reply to GrapheneOS

The idea that somehow providing accurate information which is inconvenient to your beliefs is harassment is ridiculous.

A device which does not have High/Critical severity patches for the drivers and firmware along with the OS significantly lagging behind on those patches for AOSP is not private and secure.

This lacks working disk encryption for most users too.

in reply to SimplifiedPrivacy

A Pixel with @GrapheneOS is far more secure than some other device with LineageOS. Just 'removing' Google doesn't improve your privacy or security, it just restricts what Google know about you and will almost uncertainly leave your device vulnerable.
in reply to gruff

OnePlus 9 has been end-of-life since after March 2025 so firmware and driver bugs are no longer getting patched:

oneplus.com/us/psti

Neither those devices or particularly Lineage OS on them ever had decent security in the first place. Now they're having serious security vulnerabilities remain unpatched for good. The front door is wide open, no need for more.

in reply to GrapheneOS

LineageOS connects to multiple Google services and gives privileged access to Google apps and services:

eylenburg.github.io/android_co…

LineageOS Is based on AOSP, which is nearly entirely written by Google. OnePlus devices are made in partnership with Google to meet their specifications and use Google's work at a lower level below the OS too. Hardly "Zero Google".

in reply to gruff

True, but if your goal is privacy and the choice is between an old phone you can install LineageOS on VS stock android I would go LineageOS all day
in reply to SaberhagenTheNameless

LineageOS doesn't keep up with basic privacy and security patches properly. An end-of-life device is going to be missing driver and firmware patches. End result is a device with severe known privacy and security vulnerabilities that are increasingly easy to take advantage of by apps, remotely, etc.
in reply to GrapheneOS

The context is someone selling devices end-of-life since after March 2025. People will be buying and starting to use a device where important privacy and security patches are now unavailable. This is far from the only choice people have available.

Aside from that, it's not at all "Zero Google".

in reply to GrapheneOS

LineageOS uses multiple Google services itself and provides privileged access to Google apps and services. AOSP is mostly made by Google. A huge part of the Linux kernel especially when it comes to security protections is made by Google. OnePlus 9 is a Google Mobile Services device certified by them.
in reply to GrapheneOS

OnePlus themselves has significantly worse privacy practices than Google for their own software and services.

If it's entirely about specifically avoiding Google, then why not use an iPhone? iPhones and iOS have dramatically better overall privacy and security than OnePlus and LineageOS.

in reply to GrapheneOS

Thanks for the thorough response. What if you only had an old non-pixel android? Any other alternative? Or would you just go with stock?
in reply to SaberhagenTheNameless

It depends on the details. End-of-life devices not receiving high and critical severity patches for their drivers and firmware shouldn't be used. This won't be addressed by using an alternate OS. People shouldn't buy an end-of-life or near end-of-life device even if privacy isn't important to them.
in reply to GrapheneOS

If someone already has an end-of-life device and cannot afford to replace it with a secure, used device then that's a far different situation than buying an insecure device to start using it. There are cheap used devices which have at least a couple years of privacy and security updates ahead of them.
⇧