GrapheneOS is an Operating System with a very comprehensive package of many different subprojects that all work together in harmony to improve the security of AOSP: this includes the Auditor and Attestation Server, Hardened Android bionic standard C library, Vanadium, Camera, PdfViewer, Apps, Hardened malloc much of the specific work in the kernel, it’s right across the entire stack.
For more information please visit GrapheneOS’s Features.
When it comes to GrapheneOS, the term
ROM is frequently misused. I wanted to compile a list of all the occurrences with reasons as to why it is an incorrect term to use. Perhaps a portion of users are just unaware, others may be misinformed, while some maliciously utilize the phrase “GrapheneOS ROM” to propagate misinformation and undermine the project at every opportunity.
For the time being, all I intended to do was disclose the primary sources and educate people on the necessity of not using the term
ROM when referring to the GrapheneOS project.
I hope that individuals whom wish to learn may find these references useful.
GrapheneOS is an OS. Only a tiny portion of the firmware exists as a ROM and the OS is definitely not part of it. It’s not a ROM.
Components tend to have a boot ROM which is a tiny little bit of code responsible for loading the rest of the firmware and verifying the signature.
ROM means that the firmware is read-only and cannot be updated. It’s only the tiny portion responsible for verifying/loading the rest of the firmware, since fixing a bug in a ROM would require a new revision of the hardware. Nearly all firmware isn’t a ROM so it can be updated.
It’s an OS built from AOSP like the stock OS, not a customized stock OS. It’s not described as custom or a ROM in our documentation, and those terms don’t make very much sense. It can be shipped on a device as the stock OS rather than replacing it. It’s not just a replacement OS.
ROMs are a read-only firmware component generally providing a tiny bit of code needed to load the first updatable firmware in the boot chain.
Beyond not being accurate, we don’t use that term because it confuses users and gives them the wrong idea about what it is. It’s an OS.
Minor side note:
We avoid misusing the term ROM to refer to GrapheneOS because it needlessly complicates things for end users and isn’t technically accurate.
ROM refers to read-only firmware/data that cannot be updated and that has never applied to smartphone operating systems.
It’s inaccurate jargon from the Android modding community which is not where GrapheneOS originates. Many users have heard of operating systems. Few users have heard of a ROM and since it’s not technically accurate it only serves to mislead them if they search for the term, etc.
I know that a lot of people who do “Custom ROM” development love to pile on all the buttons, knobs, options, and such and configurations to make their own personal analogue mixing console, but that opens up a horrifying pandora’s box of allowing user error that we definitely don’t want to open
there’s a tiny boot ROM hard-wired into the SoC
ROM means cannot be changed … (GrapheneOS is not a ROM)
Why do people call custom Androids a ROM anyway…writing to the read-only memory is a misnomer lol
because they don’t know what it means
GrapheneOS isn’t a ROM, it’s an OS
the boot ROM on the SoC is a ROM, i.e. tiny a read-only piece of firmware that cannot be updated since it’s baked into the SoC and is what loads the next stage
it’s not a ROM, the only ROMs are the boot ROMs on different components, i.e. read-only firmware built into them used to bootstrap code that can be updated
by definition we cannot ship ROMs as part of the OS since they can’t be written/updated
all firmware that can be updated (the vast majority of it) is updated by GrapheneOS
people misuse that term and it’s confusing/misleading
It doesn’t take the approach of a ‘custom ROM’ where things are hacked together and updates aren’t complete or secure.
It’s not a ‘custom ROM’ and isn’t part of that community / umbrella. I GrapheneOS doesn’t aim to satisfy power users who decide they want an alternative OS on their phone and then seek out an OS for it. That’s a misunderstanding, and leads to a lot of strange complaints about not supporting devices that are clearly unsuitable for it.
GrapheneOS isn’t referred to as a “custom ROM”. The terminology doesn’t make much sense, gives the wrong impression of the project and is simply wrong because the project is in no way limited to users replacing a stock OS.
GrapheneOS is also not a “custom ROM”. It’s a production OS and can be shipped on devices as the stock OS. See the site and the official responses here, not whatever sources you’ve been getting information. GrapheneOS is not aimed at power users and does not add features unrelated to privacy, security or filling in gaps left by not having Play Services (i.e. making AOSP more fleshed out / complete). It’s not about tweaks or modding. It has block-based updates and verified boot just like you stock OS. You can’t modify it aside from making your own builds signed with your own keys, which people are free to do, but that isn’t GrapheneOS.
To clarify something, GrapheneOS is not considered a ‘custom ROM’ by the project or core community. It is not limited to replacing a stock OS and can be shipped on a device. It is not a customization of the stock OS either. It’s a fork of AOSP. It’s just an OS, not a ‘custom ROM’.
It’s not only inaccurate but is in-group jargon that doesn’t make sense to other people. It’s not used by the GrapheneOS project or community. GrapheneOS is an OS. There’s no reason to make things needlessly complicated by misusing the term ROM. If people do use it that way, it’s going to be corrected.
If you say ROM in the Android community everyone will know what you mean. While it may not be technically accurate it’s the nomenclature the community has decided on.
Side note: GrapheneOS isn’t a ROM but rather an OS. A ROM is read-only firmware/data which can’t be updated. We avoid misusing that term particularly since it leads to making things seem more complicated.
AttestationServer: code for use with the Auditor app. It provides two services: submission of attestation data samples and a remote attestation implementation with email alerts to go along with the local implementation based on QR code scanning in the app. Device integrity monitoring describes the process in the About section as well as providing a Tutorial with step by step guide.
Hardened Android standard C library: Some of the past hardening has not yet been ported from Marshmallow, Nougat and Oreo to this Android Pie repository. Most is available via archived tags (check both the most recent Oreo and Nougat tags).
Vanadium browser: is a privacy and security hardened variant of Chromium providing the WebView (used by other apps to render web content) and standard browser for GrapheneOS. It depends on hardening and compatibility fixes in GrapheneOS rather than reinventing the wheel inside Vanadium. Web browsing is covered in our Usage Guide.
GrapheneOS Apps: Our new app repository client is in an early stage of development and will only be included once it’s robust/secure. It will have 3 sections shown as tabs: our own apps, our hardened builds of open source apps and the mirror of Google Play for using sandboxed Google Play. It works already but it needs to have the code for downloading, caching and verifying apps/metadata largely rewritten before we can ship it. Likely at least a few more weeks. Also needs some minor UX improvements too.
GrapheneOS Apps prebuilt repository.
Sources: Tweet Feb 06 (nitter) and Tweet Feb 09 (nitter). Please note this citation will be updated when this is officially released.
Hardened_malloc: Hardened allocator designed for modern systems. It has integration into Android’s Bionic libc and can be used externally with musl and glibc as a dynamic library for use on other Linux-based platforms. It will gain more portability / integration over time.