How to build GoS?

lyftdelta

I am having difficulty building grapheneos.

1) The Build instructions are layed out in a flat manor that makes it incredibly difficult to decipher what step I am on and if this is necessary.
It is currently:

Build Dependencies
dependencies for fetching
baseline dependecies
download source code
development branch
stable release

  It should be: (including indentation obviously but this forum doesn't have indentation...)

I) Build Dependencies
A) dependencies for fetching
B) baseline dependecies
II) download source code
A) development branch
B) stable release

2) before i ran the following i went in and edited the dialer app with some changes for functionality which is the reason i want to have a custom build.

then ran:
m vendorbootimage vendorkernelbootimage target-files-package
it ran without errors.
Does this mean that i have a useable image to flash my phone with yet?
I need more information on whats happening.

So i keep going I do the generate steps but replace raven with panther and CN with graph
should i have done this? i need more information here on whats going on:
mkdir -p keys/panther cd keys/panther CN=Graph ../../development/tools/make_key releasekey "/CN=$CN/" ../../development/tools/make_key platform "/CN=$CN/" ../../development/tools/make_key shared "/CN=$CN/" ../../development/tools/make_key media "/CN=$CN/" ../../development/tools/make_key networkstack "/CN=$CN/" ../../development/tools/make_key sdk_sandbox "/CN=$CN/" ../../development/tools/make_key bluetooth "/CN=$CN/" openssl genrsa 4096 | openssl pkcs8 -topk8 -scrypt -out avb.pem ../../external/avb/avbtool.py extract_public_key --key avb.pem --output avb_pkmd.bin cd ../..

then: ssh-keygen -t ed25519 -f keys/panther/id_ed25519

and then: script/encrypt-keys keys/panther

Is my image ready yet? Well I have no idea...
So i keep going in the instructions.

Generating signed factory image? doesn't sound right since i made some changes to the build it probably won't work anywayi run it anyway

m otatools-package
script/finalize.sh

then the next one gives me an error:
script/generate-release.sh panther 2025081400
Says that there is no keys in the releases/panther/ folder...
i check in releases there are now two folders one is
2025081400
and another is
2025082300 which has keys inside it...

So i move the keys from 2025082300 to 2025081400
then run again
it runs fine.
at this point i scroll through
It sounds like all the next steps are if you wanted to have a different binary than the one already built.
like kerner, webview, update server.

So where is my image that i can flash and where are the flash_all.sh tool ect...??
No idea.

Please help :)

de0u

lyftdelta The instructions are maybe not as easy to follow as they might be. But part of the situation is that different people want different things. It is not necessary to produce delta updates (the update client and the update server can run fine without them), it is not necessary to run an update server (flashing OTA images via USB works fine too), and it is not necessary to sign builds (if the bootloader is unlocked, then it is possible to just flash builds without doing updates at all). Some people want to build systems that can be booted on devices, but some people are fine with an emulator build. Because different people want different things the build instructions are not structured as a single linear sequence of steps that must be started at exactly the beginning and must be completed until the very end. It is expected that somebody diving into the build instructions has done enough reading to have some idea what they want, and also that before each step is done there is some understanding of what that step is expected to accomplish.

Another issue is that when source build/envsetup.sh prints something it's a good idea to look at what it prints. In particular, the build number may be set to the date that the build was first started, which is generally not the same as the source tag that was used to run repo. What ```envsetup.sh`` does can be adjusted (look within).

MarSOnEarth

lyftdelta I could've written your post myself (or most likely could anyone who comes looking to be guided through the build process). I spend days sifting through those instructions trying to comprehend what belong and what doesn't to a "standard (flashable) build. Those instructions really could use some refactoring/updating.
@de0u BTW, There's a difference between understanding what a given section of build instructions is trying to accomplish (by reading it) vs. understanding whether that section is actually needed or it's optional (by having the knowledge) to complete a given build.

lyftdelta

de0u

hey thanks for the reply.
that being said zero indentation makes it very hard to decipher even if you know what you want ie. update server or not etc...

after the generate signed image step.
the structure seems like its missing a step or two

check the stock folder for flashing:
https://releases.grapheneos.org/panther-install-2025081400.zip

vs what is in the generated:
releases/2025081400/release-panther-2025081400

no flash-all.sh / flashing instructions.
no super_x.img files

What's next?
Is it missing anything from the out/target/product/panther folder?

de0u

lyftdelta I don't have a build tree handy right now (I just wiped my build machine), but I also don't understand the question being asked. For example, I'm not sure that there has been a clear statement of exactly what you are trying to accomplish.