Gigabyte Z390 M Gaming build with working NVRAM

[lumax]

There is also the chance that Clover has been installed in both Legacy and UEFI mode.
Check the root of the system disk for a folder named /EFI.

I couldn't find a folder named /EFI

When you are in BIOS, what are your boot options?

Those are all the drives that have bootloaders.

strangely there are 2 boot options but from the same drive one named UEFI OS and the other one is named Clover start bootmgfw.efi at EFI
so I tried booting from both the UEFI OS one still had the issue of not having agdpmod=pikera and the other one I couldn't even boot from

 

[Stork]

In the Terminal

diskutil list

 

[lumax]

this is what I get in terminal with diskutil list

 

[pastrychef]

this is what I get in terminal with diskutil list

So there are two drives in the computer... You can mount the EFI partitions of both by entering the following in Terminal:

sudo diskutil mount /dev/disk0s1
sudo diskutil mount /dev/disk1s1

You can put your working EFI/config in one or both.

In BIOS, select which ever drive has a working EFI folder as first boot priority.

 

[lumax]

So there are two drives in the computer... You can mount the EFI partitions of both by entering the following in Terminal:

sudo diskutil mount /dev/disk0s1
sudo diskutil mount /dev/disk1s1

You can put your working EFI/config in one or both.

In BIOS, select which ever drive has a working EFI folder as first boot priority.

disk1s1 already has the EFI with the config.plist you said was OK and in BIOS I am always booting from this drive.
The other drive has nothing in EFI at all.

 

[pastrychef]

disk1s1 already has the EFI with the config.plist you said was ok and in bios I am always booting from this drive
the other drive has nothing in EFI at all

If /dev/disk1s1 has a config.plist with the boot arguments you need and it is selected as the boot volume in BIOS, there's no reason why it doesn't show up when you press the Space bar in the Clover boot menu.

 

[lumax]

If /dev/disk1s1 has a config.plist with the boot arguments you need and it is selected as the boot volume in BIOS, there's no reason why it doesn't show up when you press the Space bar in the Clover boot menu.

disk1s1 is the only disk I can boot from and I only have the one config.plist with the boot arguments still they don't show up when I press space and I can't boot except when I type in the extra boot arguments in clover options

 

[pastrychef]

disk1s1 is the only disk I can boot from and I only have the one config.plist with the boot arguments still they don't show up when I press space and I can't boot except when I type in the extra boot arguments in clover options

Replace the entire EFI with a working one.

 

[maxmonte]

Are you using Clover or OpenCore?

I'm using Clover.

The App Store login got fixed after logging out of my appleID a couple of times... bah

Thanks.

 

[lumax]

Replace the entire EFI with a working one.

I redownloaded the EFI folder from your post and only added agdpmod=pikera dart=0 and darkwake=0 to the boot arguments in the config.plist and it didn't change anything they still don't show up at the clover boot screen
could it be that the boot arguments are also stored somewhere else ?