Rpi4 not booting from freshly made USB disk unless hassos-boot partition code is changed to 0700

Today i decided to upgrade my setup and move away from my SDcard and fully onto my USB disk. For this i then flashed the “USB boot” bootloader setting using the rpi-imager to my SDcard and thus upgraded the firmware to the newest version as well.

I then downloaded haos_rpi4-64-9.5.img, and flashed it to my USB disk.

However when trying to boot from the USB without any SDcard in the rpi, it complained about not being able to find any valid partitions.

GPT: No bootable partitions

After finding issue #130, I updated the partition code of the hassos-boot partition from 0C01 to 0700, and it booted straight up.

This was fixed in #847 but shortly after reverted in #852.

How are anyone able to get this to work, when the rpi4 doesn’t seem to boot the default released .img file when flashed to a USB?

Seeing this too but can’t figure out from the issue you referenced how you deduced the partition codes required. fdisk haos_rpi4-64-9.5.img shows the partition type uuid is E3C9E316-0B5C-4DB8-817D-F92DF00215AE i.e. “10 Microsoft reserved”. The partition type numbers stop at 89 decimal, the codes you are quoting here convert from hex into decimal like so: 0c01==3073, 0700==1792.
What am I missing here? Can you explain what the english name for 0700 is? Or perhaps simpler, run fdisk -l on your working disk and post that?

edit: Nevermind. ‘sgdisk’ is the program that uses these weirdo partition type numbers.
0700 == 11 Microsoft Basic Data
0c01 == 10 Microsoft Reserved

# fdisk -l haos_rpi4-64-9.5.img 
Disk haos_rpi4-64-9.5.img: 2 GiB, 2147483648 bytes, 4194304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C8A6AF58-9CE7-46E6-B59E-22678F743729

Device                  Start     End Sectors  Size Type
haos_rpi4-64-9.5.img1    2048   67583   65536   32M Microsoft basic data
haos_rpi4-64-9.5.img2   67584  116735   49152   24M Linux filesystem
haos_rpi4-64-9.5.img3  116736  641023  524288  256M Linux filesystem
haos_rpi4-64-9.5.img4  641024  690175   49152   24M Linux filesystem
haos_rpi4-64-9.5.img5  690176 1214463  524288  256M Linux filesystem
haos_rpi4-64-9.5.img6 1214464 1230847   16384    8M Linux filesystem
haos_rpi4-64-9.5.img7 1230848 1427455  196608   96M Linux filesystem
haos_rpi4-64-9.5.img8 1427456 4048895 2621440  1.3G Linux filesystem

In this state the image boots up just fine.