Trying to compile old GrapheneOS build but Vanadium tag is missing

Bangpusi

Hi everyone,

I’m trying to compile a very old GrapheneOS build (specifically around the SP1A.210812.016.C2.2022081800 release), and I’ve run into a dead end with Vanadium sources.

Before anything else:
I fully understand this build is long out of support and likely vulnerable. This is purely a hobby / educational project, I’m trying to revive an old Pixel device for offline / local testing only, not for any daily or security-sensitive use.

My manifest references:

<project name="platform_external_vanadium" path="external/vanadium" remote="grapheneos-gitlab" revision="d1bb30cd9c81ca302a0fa8d302541a03eaa0d9f5" upstream="refs/tags/SP1A.210812.016.C2.2022081800" dest-branch="refs/tags/SP1A.210812.016.C2.2022081800" clone-depth="1"/>

But I cannot find that tag anywhere,
no such tag on GitHub archive (platform_external_vanadium)
on GrapheneOS GitLab tag doesn’t seem to exist (or history is incomplete)

It looks like some history may not be preserved publicly or is simply lost.
Can you point me in the correct direction? would help a lot.

Thanks!

GrapheneOS

Bangpusi The repository with Vanadium prebuilts grew too large and stopped working so we had to rebase the legacy releases out of the history and remove all of the legacy tags. You can backport a recent release to use instead by replacing the current Android build system integration with legacy integration compatible with a much older release.

likely vulnerable

It's extremely insecure and really shouldn't be either internet connected or have the radios turned on, but many people use Android devices with no security patches for years so it wouldn't be abnormal.

You could obtain a cheap used device for development especially if you look for devices with damage which would deter people using them as a daily driver. It would be a lot more useful having a device that's still supported where you can use current GrapheneOS.

Bangpusi

GrapheneOS Yeah, I had a feeling that might be the case. No worries then.
Anyway, thanks a lot for the clarification.