I think that stuff is needed when you drop into an emergency shell, not in this case.
I see now and agree with the comment of @Bro or even start from scratch: download a new ISO, verify checksum, burn it one the USB possibly with Ventoy, fast boot and secure boot disabled in the BIOS, boot ISO and install.
If I can give you also a general advice, I suggest you always make clear in your posts what you have done, provide the relevant input and output whenever possible (eg when in terminal or chroot), otherwise it becomes difficult to follow and understand the actions and what's going on.
and change every occurrence of force to removable (there should be 4).
Save, exit and try installing…
By-the-way, if I remember correctly, --removable just does not write in the NVRAM, so could do the trick anyway, just in a different way.
I was honestly hoping for some clarity in that thread.
My interpretation is that the Debian ISO was being used to manually create an entry in the UEFI boot menu.
In the Debian USB, after mounting sda1 onto /boot/efi, I would:
Take care. you need two backslashes for the path not forward slashes and it need to be two of them as shown above.
However, this is the example when you have a standalone Garuda installation on your Macbook otherwise you may have to provide. a different disk and or at least a different partition by the -p option.
With this the Macbook did boot into grub after a restart, however you will end up on the grub command line. So there are of course several possibilities how to fix this. What I did was i entered the garuda instalation USB stick and on “Garuda Welome” I choose “Garuda Boot Repair” and there I did choose the second option “Repair GRUB configuration file”.
And another reboot now from disk and you should be done.
Then when I reboot I still fall back to the Grub terminal, I booted with the Garuda live usb multiple times repairing the Grub bootloader, updating it, and even reinstalling it on fish terminal but it still boots up to grub.
First thing to check is, if there are other entries in your NVRAM and if the one you want to use is the right one. Just to avoid that there are other boot loaders on your disk and you are repairing the right one but you boot into a different one.
Do you have only one installation on your disk? Or do you have multiple operating systems on your disk?
you can see the harddisks, the partitions and the UUIDs of your computer.
You can see all your NVRAM entries together with the UUIDs. So check whether the UUID in the NVRAM (BOOT0001 in your case) is identical with the partition that is meant to be your /boot/efi partition (per default in a stadard installation this should be on /dev/sda1). And check whether the BOOT0001 is the first in the BootOrder.
This is to make sure that the GRUB boot loader which is loaded when you start your computer is the right one and probably the only one.
If all of this is correct then there might be a problem in the GRUB configuration. However, for me it did work with the “Repair GRUB configuration file” of the “Garuda Boot Repair” tool. So this is why it may make sense to do the checks above.
you can list all your partitions and there partition type. If there is only one operating system on your computer then there should be exactly one and only one “EFI System” partition (usually this is /dev/sda1 as said before) and this should be the one whose UUID is listed in the NVRAM.