Did you have anything connected previously to the GPIO header?
Something that maybe had you reconfigure / setup some GPIO pins for a specific function?
On further inspection I am booting into Raspbian, just nothing on the Hyperpixel.
Desktop appears split between DSI/HDMI with the Hyperpixel boot code enabled.
Previously connected to a breadboard (via ribbon cable & T-cobbler) to an RFID reader and OLED screen for my first project.
I was careful to include the GPIO.cleanup() line at the end of the code for the reader.
Other than that, I’ve only connected to the GPIO extension within the Agon one case. I’m currently testing without the case.
If enabled I would turn off i2c and SPI etc. My best guess is something from before may have left a line in your config.txt or turned something on that messes with the hyperpixel. The hyperpixel uses all of the GPIO and repurposes those pins.
The only other thing I can think of was attempting to connect the display to the Agon case’s GPIO extension, though I’ve no idea why that would be an issue.
It will likely be easier to just start over with a fresh image / install. I have no idea what the Hyperpixel install enables etc. A lot of GPIO connected displays use SPI, I don’t think the Hyperpixel does though, not in the standard way anyway.
The pinout is here, Hyperpixel4 at Raspberry Pi GPIO Pinout