de0u also, when I see this:

HOST_OS=linux
HOST_OS_EXTRA=Linux-6.8.0-1018-azure-x86_64-Ubuntu-22.04.5-LTS
HOST_CROSS_OS=windows

it sounds like he is running the build env on Microsoft Azure? That introduces a whole other set of unknowns.

    eagle13 PLATFORM_VERSION=14

    I've never built from source, but should this be 15?

      well I was using it without any issues to build A14 , downloaded the latest manifest (15) and synced the project

      however , I am trying to build a specific manifest using the tag and syncing the project

      well , using the tag of the latest release doesn't make a difference ,
      this is the first error I see : lunch aosp_oriole-ap2a-userdebug
      cat: /vendor_boot.modules.load: No such file or directory
      In file included from build/make/core/config.mk:394:
      In file included from build/make/core/envsetup.mk:368:
      In file included from build/make/core/board_config.mk:239:
      In file included from device/google/raviole/oriole/BoardConfig.mk:41:
      device/google/gs101/BoardConfig-common.mk:347: error: vendor_boot.modules.load not found or empty.
      07:16:35 dumpvars failed with: exit status 1
      (PS : sync was successful and files are there)

      • de0u replied to this.

        same with AP4A or AP3A as release

        eagle13 cat: /vendor_boot.modules.load: No such file or directory

        But there should not be a file called vendor_boot.modules.load in the system's root directory! That output suggests that some environment variable may be unset.

          yes that's my suspicion, some env variables aren't set , or not being set when doing the lunch command
          I had to hardcode some paths though to bypass the lunch command and move to make command and get the error above

          even more , kinda hardcoded everything , I know it's risky , and ofc the image isn't booting , it's a bootloop

          Just did my first build and it worked fairly well (development branches). Hopefully the detail below help more than being annoying. It went surprisingly smooth, unlike compiling OpenWRT, except for one thing. I was a bit confused about signing and generating the certificates (I tried to explore the options); I will recompile after repo diff/ syncing and removing all the changes that I may or may not have done while trying to understand what I was doing. I was able to flash my phone with no issue. And I did made sure that the automated update were disabled as per the warning in the instruction.

          My setup is a debian 12 vm using virsh with no graphics installed. What I did was (after following the instructions specific for Debian 12 and yarnpkg) to download repo from Google (manual method) and the required packages listed in "Install required software". Then for adevtool I followed the instruction from (what I hope is the) official github page. Since it mentioned minimum I installed node.js 22 using npm.

          The repo tool and the .jar file from adevtool were all installed in the bin directory that I created in the home directory (~/bin). I then exported the path and added it to .bashrc . That's it. That and I found that I needed to restart from the beginning with lunch command if I were to exit the current session.

          https://source.android.com/docs/setup/start/requirements
          https://github.com/kdrag0n/adevtool/tree/main

          And with this setup (no windows involved) I also saw the HOST_CROSS_OS=windows .

          I am using ubuntu server on cloud computing , so it's not related to that as I have been using this server for 2 years now , ( 5 years of aosp experience here)

          I was building fine gOS android 14

          Then I am the only N00b here. And to correct myself I was better off using yarnpkg to install adevtool because I couldn't repeat what I just did. I tried before with a gui and the whole android studio installed (and some more) and I was stuck in a loop of error or missing packages that I couldn't understand. I thought that maybe you were in a similar situation.

          eagle13 updates ?

          I think it's possible that you are not getting replies that move you forward because the questions you are posting do not contain sufficient detail for the readers of the thread to guess what might be going wrong.

          Given the number of people who are successfully building GrapheneOS, I suspect that whichever issue(s) you are running into are somehow specific to your setup. Without access to your setup I suspect people here aren't going to be able to help diagnose what is going wrong with it.

          Two things you might try:

          • The developer chat room on Matrix/Discord/etc.
          • Starting over, i.e., downloading the GrapheneOS sources from scratch using repo, etc., and trying to build that.
              2 months later

              GOS team: seriously ? it is still presistant and no fix ? How do you build there ? Maybe need to update the build guide?

              • de0u replied to this.

                • Dde0u

                  • Post #27

                  eagle13 Can you report on which things suggested in the previous post (de0u) have been tried?

                      new build env , old build env , sync the source code again , tried with both oriole and panther devices .. gone through the files to try to fix the path ... it is just not working