GAMER8736 wrote:
Thanks your your response mate.
If I reduce my security to permissive security, by running “csrutil disable” in the terminal in RecoveryOS, and by installing reFind, which is a boot manager, will that work.
I want to try, but I am afraid that installing a boot manager that can recognise ARM64 burned USB’s will not allow me to uninstall the boot manager and go back to the normal one.
rEFInd does not work like you think it does. The rEFInd "app" just installs the bootloader to the hidden ESP (aka EFI) partition. That is the only time the "app" works (is used except to uninstall the bootloader) within macOS. Once the rEFInd bootloader is placed with the hidden ESP partition, it will appear as another bootable option.
To remove the rEFInd bootloader can be done either through the rEFInd app or just by mounting the hidden ESP partition and deleting the rEFInd folder.
I've never tried to boot an external drive from an Apple Silicon Mac so I'm not entirely sure how things work there, nor do I know whether rEFInd is even compatible with an Apple Silicon Mac. Assuming there is an ARM version of rEFInd compatible with Apple Silicon, then it should theoretically be possible to make the rEFInd bootloader the default Startup Disk option so you have a graphical boot menu to select which OS you want to use.
FYI, if rEFInd is compatible with an Apple Silicon Mac, then you should be able to make a bootable rEFInd USB stick to use for testing to make sure everything is functional. I know there was a standalone rEFInd image available for Intel systems which could be "burned" to a USB stick using Etcher (Mac/Windows/Linux). Of course this will be cumbersome on Apple Silicon Macs due to the One True Recovery boot option, but this rEFInd USB stick would be just for testing anyway.
Edit: I would highly recommend you take any old UEFI booting computer and experiment with rEFInd to see how it works on an Intel/AMD system. Any 2007-2020 Intel Mac will suffice or any non-Apple Windows PC which is configured to boot using UEFI instead of the legacy boot mode.
Edit#2: Do not reduce system security with "csrutil disable". That is a recipe for disaster. Here is what a simple Google Chrome update did to people's systems with "csrutil disabled":
https://arstechnica.com/information-technology/2019/09/no-it-wasnt-a-virus-it-was-chrome-that-stopped-macs-from-booting/
Just adjust the boot settings using the Startup Security Utility as mentioned in the article linked earlier in the thread.