Jump to content
366 posts in this topic

Recommended Posts

I hope God bless you my friend, my EFI is already too, with only keychain no password, doble click, ARM/intel Arch, start only in Menu Bar, etc... but your is too much superior, I hope people like and enjoy it much is I am 

 

:thumbsup_anim:

 

Spoiler

image.png.8f5cd5ec1488e2fb8f55722f1f14c0c6.png

Captura de Tela 2025-08-18 às 02.50.59.png

Edited by Max.1974
  • Like 7

Hi @Cyberdevs thank for your app very useful

i have a little problem with it

i have two identical Disks 2 Tb Kingston Nvme one for macOs <Ventura one for macOS Sequoia

Opencore is on Sequoia One

I set from my bios Sequoia as boot disk (inside there is ESP with EFI)

if i choose then macOS Ventura EspMounter recognize the wrong disk for ESP:

image.thumb.png.d117a3a59415ffe15b528009066c399a.png

 

This ESP has an empty EFI obviusly 

If i boot on Sequoia ESPMounter is correct and i can mount the correct ESP with my booting EFI

 

Have you some advice or could be useful some tests to debug this my problem?

 

Thank you

Edited by fabiosun
  • Like 2

@fabiosun

Hi, you're welcome.

if the ESP on the Ventura is empty there will be no bootloader indicator when you mount it the app will simply detect the filesystem, e.g, macOS, Windows, etc.

You can mount both EFI partitions and send me the screen shot, and you can also run "diskutil list physical" and send me the results as the text and I'll check and see disk identifiers.

Since the bootloader is on one disk and I'm assuming you use that EFI folder for both macOSes, I guess the logic gets confused and detects the disk that opencore has booted from.

Did I get the problem right?

  • Like 2

Ok, I'll look into it.

The OC next to the Boot disk indicates that disk has OpenCore as the bootloader and the Boot Disk is the disk macOS has booted from.
I guess that's were you get confused, I assume you thought that's the disk that has OpenCore in the EFI partition.

  • Like 1
  • Thanks 1

I just published a new version 1.1 with the suggested fix by @fabiosun to detect OpenCore's boot path if system has booted from OpenCore on a disk which is not the same as the macOS boot disk.

In this case I've booted the system for SanDisk Ultra Fit Media but macOS has booted from Samsung SSD 980 Pro disk.

Also added a feature to Disable Auto Open Finder in app's settings.

01.png

I hope it's bug free but if you've found any issues just let me know.

  • Like 9
  • 2 weeks later...
34 minutes ago, LockDown said:

Hi @Cyberdevs

Just curious... In terminal, how to get the booted EFI?

Hi,

You can use several commands:

diskutil info / | grep "Part of Whole"

This command will return the disk identifier of the disk that the system has booted from.

You can also use these commands to determine OpenCore's boot path:

u=$(nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path | sed 's/.*GPT,\([^,]*\),.*/\1/'); \ 

  if [ "$u" != "" ]; then sudo diskutil mount $u ; fi

and

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path

 

  • Like 2
5 minutes ago, LockDown said:

I forgot to mention the it was for Clover

Clover is so tricky, as far as I know it doesn't expose the boot-path in the nvram like OpenCore, the only way to find which EFI partition it has booted from is to check the bootlog. The path to the EFI partition is available in the boot log.

  • Like 2
  • 2 weeks later...
  • 2 weeks later...

Bro @Cyberdevs! One more good thing!

FAT32 created on Windows for easy dual boot in same SSD with Shrink Volume option and DiskGenius don't work. Procedure HEREThis way we have independent EFI partitions.

image.png

With EFI Agent work fine and appear EFI macOS created on WIndows.

 

image.png

  • Like 5
×
×
  • Create New...