Build
+Build
Build dependencies
¶
diff --git a/static/contact.html b/static/contact.html
index 0c607701..8cdf54dd 100644
--- a/static/contact.html
+++ b/static/contact.html
@@ -33,7 +33,7 @@
- Contact
+ Contact
You can contact contact@grapheneos.org for topics
related to GrapheneOS. The security@grapheneos.org
address can be used for high priority security issues. The email address of
@@ -43,12 +43,12 @@
which is used for official announcements. The account of the lead developer is
@DanielMicay and is primarily focused on
the privacy and security research/engineering work on GrapheneOS.
- Community
+ Community
The main forum currently used to discuss the project is the official
/r/GrapheneOS subreddit on Reddit.
The main IRC channel is #grapheneos on irc.freenode.net. The #grapheneos channel on
irc.oftc.net is an alternate channel acting as a backup for when freenode is down.
- Reporting issues
+ Reporting issues
- OS issue tracker
- grapheneos.org issue tracker
diff --git a/static/donate.html b/static/donate.html
index 1e0cda51..a683eb44 100644
--- a/static/donate.html
+++ b/static/donate.html
@@ -33,14 +33,14 @@
- Donate
- Bitcoin
+ Donate
+ Bitcoin
You can send Bitcoin donations to the following address to support this project:
3QpKs45BLXirWAgYtV1sTCbAkfUe7HByR5
- PayPal
+ PayPal
PayPal donations can be sent to danielmicay@gmail.com. Please mention GrapheneOS in
the donation description to allow for proper record keeping, since PayPal
diff --git a/static/index.html b/static/index.html
index 7ce5047e..e7afa8e4 100644
--- a/static/index.html
+++ b/static/index.html
@@ -33,7 +33,7 @@
- GrapheneOS
+ GrapheneOS
GrapheneOS is an open source privacy and security focused mobile OS with Android
app compatibility.
Official Releases are available on the releases page and
@@ -51,7 +51,7 @@
support for your own builds.
The sources are available via the
manifest on GitHub.
- Early stage of development
+ Early stage of development
GrapheneOS is a privacy / security research and engineering project that has been
under way for over 5 years. It recently became rebranded as GrapheneOS and is taking a
different direction based on obtaining funding for the research and development work
@@ -67,7 +67,7 @@
applications. It will take more time to organize and deploy these resources in order
for the project to have a strong development team with proper infrastructure behind
it.
- Roadmap
+ Roadmap
Details on the roadmap of the project will be posted on the site in the near
future. In the long term, it aims to move beyond a hardened fork of the Android Open
Source Project. Achieving the goals requires moving away from relying the Linux kernel
diff --git a/static/install.html b/static/install.html
index 11c94ceb..53287bcc 100644
--- a/static/install.html
+++ b/static/install.html
@@ -33,8 +33,8 @@
- Install
- Prerequisites
+ Install
+ Prerequisites
You should have at least 2GB of free memory available.
You need the unlocked variant of one of the supported devices, not a locked carrier
specific variant.
@@ -50,20 +50,20 @@
do not have support for current devices. Very old versions of fastboot
from several years ago are still shipped by Linux distributions like Debian and lack
the compatibility detection of modern versions so they can soft brick devices.
- Enabling OEM unlocking
+ Enabling OEM unlocking
OEM unlocking needs to be enabled from within the operating system.
Enable the developer settings menu by going to Settings ➔ System ➔ About phone and
pressing on the build number menu entry until developer mode is enabled.
Next, go to Settings ➔ System ➔ Advanced ➔ Developer settings and toggle on the
'Enable OEM unlocking' setting. This requires internet access on devices with Google
Play Services.
- Unlocking the bootloader
+ Unlocking the bootloader
First, boot into the bootloader interface. You can do this by turning off the
device and then turning it on by holding both the Volume Down and Power buttons.
The bootloader now needs to be unlocked to allow flashing new images:
fastboot flashing unlock
The command needs to be confirmed on the device.
- Obtaining factory images
+ Obtaining factory images
The initial install will be performed by flashing the factory images. This will
replace the existing OS installation and wipe all the existing data.
You can download the factory images from the releases page.
@@ -71,7 +71,7 @@
gpg --recv-keys 65EEFE022108E2B708CBFCF7F9E712E59AF5F22A
gpg --verify blueline-factory-2019.04.01.19.zip.sig blueline-factory-2019.04.01.19.zip
When this signing key is replaced, the new key will be signed with it.
- Flashing factory images
+ Flashing factory images
Next, extract the factory images and run the script to flash them. Note that the
fastboot
command run by the flashing script requires a fair bit of free
space in a temporary directory, which defaults to /tmp
:
@@ -86,7 +86,7 @@ TMPDIR="$PWD/tmp" ./flash-all.sh
new operating system.
You should now proceed to locking the bootloader before using the device as locking
wipes the data again.
- Locking the bootloader
+ Locking the bootloader
Locking the bootloader is important as it enables full verified boot. It also
prevents using fastboot to flash, format or erase partitions. Verified boot will
detect modifications to any of the OS partitions (vbmeta, boot/dtbo, product, system,
@@ -99,10 +99,10 @@ TMPDIR="$PWD/tmp" ./flash-all.sh
The command needs to be confirmed on the device since it needs to perform a factory
reset.
Unlocking the bootloader again will perform a factory reset.
- Disabling OEM unlocking
+ Disabling OEM unlocking
OEM unlocking can be disabled again in the developer settings menu within the
operating system after booting it up again.
- Replacing GrapheneOS with the stock OS
+ Replacing GrapheneOS with the stock OS
Installation of the stock OS via the stock factory images is the same process
described above. However, before locking, there's an additional step to fully revert
the device to a clean factory state on modern devices with Android Verified Boot 2.0
diff --git a/static/releases.html b/static/releases.html
index 8ee0a46f..09e7c8c0 100644
--- a/static/releases.html
+++ b/static/releases.html
@@ -33,7 +33,7 @@
- Releases
+ Releases
These releases are available as both tags in the source code repositories and
official builds.
The factory images are used for the initial installation and can be verified with
@@ -62,7 +62,7 @@
-
Stable channel
+ Stable channel
Pixel 3 XL
@@ -152,7 +152,7 @@
OTA update url loading...
- Changelog
+ Changelog
List of tagged releases. Snapshot releases without tags such as early releases of
the project and early device support releases are not listed.
diff --git a/static/source.html b/static/source.html
index a3333bc6..7534b094 100644
--- a/static/source.html
+++ b/static/source.html
@@ -33,7 +33,7 @@
- Source
+ Source
- OS issue tracker
- Website repository and issue tracker
diff --git a/static/usage.html b/static/usage.html
index aced3c20..839a4542 100644
--- a/static/usage.html
+++ b/static/usage.html
@@ -33,9 +33,9 @@
- Usage
+ Usage
This page is currently a placeholder and will be filled with lots of content over time.
- Auditor
+ Auditor
See the tutorial page on the site for the attestation sub-project.
Contact
+Contact
You can contact contact@grapheneos.org for topics related to GrapheneOS. The security@grapheneos.org address can be used for high priority security issues. The email address of @@ -43,12 +43,12 @@ which is used for official announcements. The account of the lead developer is @DanielMicay and is primarily focused on the privacy and security research/engineering work on GrapheneOS.
-Community
+Community
The main forum currently used to discuss the project is the official /r/GrapheneOS subreddit on Reddit.
The main IRC channel is #grapheneos on irc.freenode.net. The #grapheneos channel on irc.oftc.net is an alternate channel acting as a backup for when freenode is down.
-Reporting issues
+Reporting issues
- OS issue tracker
- grapheneos.org issue tracker diff --git a/static/donate.html b/static/donate.html index 1e0cda51..a683eb44 100644 --- a/static/donate.html +++ b/static/donate.html @@ -33,14 +33,14 @@
Donate
-Bitcoin
+Donate
+Bitcoin
You can send Bitcoin donations to the following address to support this project:

3QpKs45BLXirWAgYtV1sTCbAkfUe7HByR5
PayPal
+PayPal
PayPal donations can be sent to danielmicay@gmail.com. Please mention GrapheneOS in
the donation description to allow for proper record keeping, since PayPal
diff --git a/static/index.html b/static/index.html
index 7ce5047e..e7afa8e4 100644
--- a/static/index.html
+++ b/static/index.html
@@ -33,7 +33,7 @@
GrapheneOS is an open source privacy and security focused mobile OS with Android
app compatibility. Official Releases are available on the releases page and
@@ -51,7 +51,7 @@
support for your own builds. The sources are available via the
manifest on GitHub. GrapheneOS is a privacy / security research and engineering project that has been
under way for over 5 years. It recently became rebranded as GrapheneOS and is taking a
different direction based on obtaining funding for the research and development work
@@ -67,7 +67,7 @@
applications. It will take more time to organize and deploy these resources in order
for the project to have a strong development team with proper infrastructure behind
it. Details on the roadmap of the project will be posted on the site in the near
future. In the long term, it aims to move beyond a hardened fork of the Android Open
Source Project. Achieving the goals requires moving away from relying the Linux kernel
diff --git a/static/install.html b/static/install.html
index 11c94ceb..53287bcc 100644
--- a/static/install.html
+++ b/static/install.html
@@ -33,8 +33,8 @@
You should have at least 2GB of free memory available. You need the unlocked variant of one of the supported devices, not a locked carrier
specific variant. OEM unlocking needs to be enabled from within the operating system. Enable the developer settings menu by going to Settings ➔ System ➔ About phone and
pressing on the build number menu entry until developer mode is enabled. Next, go to Settings ➔ System ➔ Advanced ➔ Developer settings and toggle on the
'Enable OEM unlocking' setting. This requires internet access on devices with Google
Play Services. First, boot into the bootloader interface. You can do this by turning off the
device and then turning it on by holding both the Volume Down and Power buttons. The bootloader now needs to be unlocked to allow flashing new images: The command needs to be confirmed on the device. The initial install will be performed by flashing the factory images. This will
replace the existing OS installation and wipe all the existing data. You can download the factory images from the releases page. When this signing key is replaced, the new key will be signed with it. Next, extract the factory images and run the script to flash them. Note that the
@@ -86,7 +86,7 @@ TMPDIR="$PWD/tmp" ./flash-all.sh
new operating system. You should now proceed to locking the bootloader before using the device as locking
wipes the data again. Locking the bootloader is important as it enables full verified boot. It also
prevents using fastboot to flash, format or erase partitions. Verified boot will
detect modifications to any of the OS partitions (vbmeta, boot/dtbo, product, system,
@@ -99,10 +99,10 @@ TMPDIR="$PWD/tmp" ./flash-all.sh
The command needs to be confirmed on the device since it needs to perform a factory
reset. Unlocking the bootloader again will perform a factory reset. OEM unlocking can be disabled again in the developer settings menu within the
operating system after booting it up again. Installation of the stock OS via the stock factory images is the same process
described above. However, before locking, there's an additional step to fully revert
the device to a clean factory state on modern devices with Android Verified Boot 2.0
diff --git a/static/releases.html b/static/releases.html
index 8ee0a46f..09e7c8c0 100644
--- a/static/releases.html
+++ b/static/releases.html
@@ -33,7 +33,7 @@
These releases are available as both tags in the source code repositories and
official builds. The factory images are used for the initial installation and can be verified with
@@ -62,7 +62,7 @@
- List of tagged releases. Snapshot releases without tags such as early releases of
the project and early device support releases are not listed. This page is currently a placeholder and will be filled with lots of content over time. See the tutorial page on the site for the attestation sub-project.GrapheneOS
+ GrapheneOS
Early stage of development
+ Early stage of development
Roadmap
+ Roadmap
Install
- Prerequisites
+ Install
+ Prerequisites
fastboot
from several years ago are still shipped by Linux distributions like Debian and lack
the compatibility detection of modern versions so they can soft brick devices.
- Enabling OEM unlocking
+ Enabling OEM unlocking
Unlocking the bootloader
+ Unlocking the bootloader
fastboot flashing unlock
Obtaining factory images
+ Obtaining factory images
gpg --recv-keys 65EEFE022108E2B708CBFCF7F9E712E59AF5F22A
gpg --verify blueline-factory-2019.04.01.19.zip.sig blueline-factory-2019.04.01.19.zip
Flashing factory images
+ Flashing factory images
fastboot
command run by the flashing script requires a fair bit of free
space in a temporary directory, which defaults to /tmp
:Locking the bootloader
+ Locking the bootloader
Disabling OEM unlocking
+ Disabling OEM unlocking
Replacing GrapheneOS with the stock OS
+ Replacing GrapheneOS with the stock OS
Releases
+ Releases
Stable channel
+ Stable channel
Pixel 3 XL
@@ -152,7 +152,7 @@
OTA update url loading...
Changelog
+ Changelog
Source
+ Source
Usage
+ Usage
Auditor
+ Auditor