Boot macOS Sequoia and macOS Sequoia Misc/Entries

[kaoskinkae]

Boot macOS Sequoia and macOS Sequoia Misc/Entries

 

Is it possible to boot macOS Sequoia and macOS Sequoia beta like I do with Windows 11 and Linux Mist? I've tried to do this by locating the FS08 and FS11 locations of the two Mac systems, their PciRoot, and their boot location /boot/BOOTx64.ef. Curiously, only one of the two FS files has the BOOTx64.ef.

You can add the entry as shown in the photo, but without success.

I've long thought it was impossible to do this because of the OpenCore and Mac operating systems, but I asked ChatGPT and Grok just out of curiosity, and both say it's possible.

 

[Anto65]

In the case of OSX (Sequoia Beta / Release)
No need to add any Entry in Misc ... they are detected by Default 

If you notice the Entries in my plist there is nothing related to Sequoia

I hope I understood the issue well

 

Spoiler

 

 

 

 

Edit :

 

From what I understand from your screenS. the 2 volumes with the Sonoma icon are the Entries you created right ?
While the other 2 with the Sequoia icon are actually those detected by default ( Sequoia Release / Beta )
Delete the new Entries you created, and rename the M2 and SSD volumes
in Sequoia Release and Sequoia Beta ... you solved it

Edited May 25, 2025 by Anto65

[kaoskinkae]

42 minutes ago, Anto65 said:

En el caso de OSX (Sequoia Beta/Lanzamiento)
no es necesario agregar ninguna entrada en Misc... se detectan por defecto 

Si observas las entradas en mi plist no hay nada relacionado con Sequoia

Espero haber entendido bien el tema.

 

  Revelar contenidos ocultos

 

 

 

 

Editar :

 

Según entiendo en tus pantallas, los dos volúmenes con el ícono de Sonoma son las entradas que creaste, ¿verdad?
Mientras que los otros dos con el ícono de Sequoia son los que se detectan por defecto (Sequoia Release/Beta).
Elimina las nuevas entradas que creaste y cambia el nombre de los volúmenes M2 y SSD
en Sequoia Release y Sequoia Beta... lo solucionaste.

Exactly, the ones with the hard drive name are the entries I've always had, the ones I've assigned the names of the mounted systems. It's the same method as Windows 11 and Linux Mint.

[Anto65]

Ok I still don't understand but
Why do you have to create ENTRIES for Sequoia Beta and Release when there are already M2 and SSD disks ?

[kaoskinkae]

4 minutes ago, Anto65 said:

Ok, todavía no lo entiendo, pero
¿por qué hay que crear ENTRADAS para Sequoia Beta y Release cuando ya hay discos M2 y SSD?

Just curious, and being able to assign a name to the entry instead of using the name I assigned to the hard drive. I should know that the method I used with Windows 11, which could also do what you're saying, was done through Misc.

[Anto65]

If you like to have 4 volumes at the end of which 2 are duplicates, ok  🤷‍♂️

[kaoskinkae]

9 minutes ago, Anto65 said:

Si te gusta tener 4 tomos al final de los cuales 2 son duplicados, ok   🤷‍♂️

No, because I then remove the entries in the Policy Scan just like I removed the Windows 11 entry.

[Anto65]

If for educational purposes, to experiment ok
there was no doubt that by setting any entry
in Misc by inserting the PciRoot and the boot file it worked and assigning the name you want
But for practical purposes it is enough to simply rename the volumes (SSD and M2) without doing the work from the Shell, scanpolicy etc...

Edited May 25, 2025 by Anto65

[kaoskinkae]

6 minutes ago, Anto65 said:

Si para fines educativos, para experimentar ok
no había duda que con poner cualquier entrada
en Misc insertando el PciRoot y el archivo boot funcionaba y asignando el nombre que se quiera
Pero para fines practicos basta simplemente con renombrar los volumenes (SSD y M2) sin hacer el trabajo desde el Shell, scanpolicy etc...

Of course, but I don't want to rename the hard drives every time a new system comes out. It wouldn't be logical, and well, that would be fine. But we're diverting attention from the issue. As they say, "To be or not to be is the question." Is it possible? ChatGPT tells me it is.

[FirstCustomac]

To boot to macOS(APFS) via OpenCore custom entries, you need to set the path to Preboot volume/\UUID\System/Library\CoreServices\boot.efi where your system's boot.efi resides.

 

ex.

 

PciRoot(0x0)/xxxxxxxxx/\xxxxxxxUUID.xxxxxxxx\System/Library\CoreServices\boot.efi

 

You'll need to find UUID of your each respective operating system, you can do so by following @Anto65 post here which also includes solution to easily change Picker's entry name. 

 

As I understand, you want to change the name of the entries at Picker from the config.plist with custom entries. It can be done but this may create duplicate entries.  For that, you can place .contentVisibility(Disabled) file in UUID\System/Library\CoreServices\boot.efi to hide these entries auto created by OpenCore.

[Anto65]

Yes I'm trying various combinations this is the example from the clover log for the Sequoia beta disk ... still without success ...probable syntax error

 

Spoiler

PciRoot(0x0)\Pci(0x1B,0x4)\Pci(0x0,0x0)\NVMe(0x1,D2-A8-9C-46-8B-44-1B-00)\HD(3,GPT,F6C3B6D7-C19C-4061-B17B-E2D2F719AD03,0xEEC34C0,0xEE5F498)\VenMe dia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,2F2B63B2F00DC241982619C882771EED) \211448AC-4DD5-4E76-A6BE-394A15AAFDE7\System\Library\CoreServices\boot.efi

 

 this is the last test done in the plist

PciRoot(0x0)\Pci(0x1B,0x4)\Pci(0x0,0x0)/NVMe(0x1,D2-A8-9C-46-8B-44-1B-00)/(211448AC-4DD5-4E76-A6BE-394A15AAFDE7)/\System\Library\CoreServices\boot.efi   but nothing

5 hours ago, kaoskinkae said:

Of course, but I don't want to rename the hard drives every time a new system comes out.

 

Curiosity how often does a new operating system come out in Spain
Here in Italy once a year, with this frequency it shouldn't be a problem for me to rename the disk  

Edited May 25, 2025 by Anto65

[FirstCustomac]

@Anto65 Oops, I've noticed this 

 

[kaoskinkae]

24 minutes ago, Anto65 said:

Sí, estoy probando varias combinaciones, este es el ejemplo del registro de clover para el disco beta de Sequoia... todavía sin éxito... probable error de sintaxis

 

  Revelar contenidos ocultos

PciRoot(0x0)\Pci(0x1B,0x4)\Pci(0x0,0x0)\NVMe(0x1,D2-A8-9C-46-8B-44-1B-00)\HD(3,GPT,F6C3B6D7-C19C-4061-B17B-E2D2F719AD03,0xEEC34C0,0xEE5F498)\VenMe dia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,2F2B63B2F00DC241982619C882771EED) \211448AC-4DD5-4E76-A6BE-394A15AAFDE7\System\Library\CoreServices\boot.efi

 

 Esta es la última prueba realizada en el plist.

PciRoot(0x0)\Pci(0x1B,0x4)\Pci(0x0,0x0)/NVMe(0x1,D2-A8-9C-46-8B-44-1B-00)/(211448AC-4DD5-4E76-A6BE-394A15AAFDE7)/\System\Library\CoreServices\boot.efi pero nada

 

Curiosidad cada cuanto tiempo sale un nuevo sistema operativo en España
Aquí en Italia una vez al año, con esta frecuencia no debería ser un problema para mí renombrar el disco  

Really, as they say in Spain, it's just messing around and trying without any concern for the subject, but since I used artificial intelligence to ask and they told me it was possible, I tried it, but I already knew it was impossible.

[Anto65]

oops yes I hadn't noticed thanks, and now I've reached a hundred reboots and various combinations in the plist but I can't get it to go the way it wants @kaoskinkae

[kaoskinkae]

Just now, Anto65 said:

ups si no me habia dado cuenta gracias, y ya he llegado a cien reinicios y varias combinaciones en el plist pero no consigo que salga como quiere@kaoskinkae

I already asked this question here a long time ago and no one answered, but as I said, it was just a waste of free time to see if it was possible.

[FirstCustomac]

@Anto65 Sorry, another one.

 

 

@kaoskinkae I just tried custom entries for macOS and it's working well on my end.

 

 

This is how mine looks by the way

 

Edited May 25, 2025 by FirstCustomac

[Anto65]

@kaoskinkae I was joking of course
Even though I don't have a good relationship with ai I think it's doable, in clover this is possible ... I'm using the wrong path or syntax
However the entries you added Bootx64.efi probably from the EFI partition of the disk are wrong it will recall   OC again 
the file to boot is   .....System\Library\CoreServices\boot.efi

 

Spoiler

 

Edited May 25, 2025 by Anto65

[Anto65]

20 minutes ago, FirstCustomac said:

This is how mine looks by the way

 

 

can you upload the plist? even just the misc part without all the rest... i can't understand from the image

[FirstCustomac]

@Anto65 Here you go.

 

 

Edited May 30, 2025 by FirstCustomac

[Anto65]

sorry I don't understand these xxxx
did you want to hide them or do you have to put the x's?

 

in this way the entry disappears completely

Spoiler

PciRoot(0x0)/Pci(0x1B,0x4)/Pci(0x0,0x0)/NVMe(0x1,D2-A8-9C-46-8B-44-1B-00)/HD(3,GPT,F6C3B6D7-C19C-4061-B17B-E2D2F719AD03,0xEEC34C0,0xEE5F498)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,2F2B63B2F00DC241982619C882771EED)/\211448AC-4DD5-4E76-A6BE-394A15AAFDE7\System/Library\CoreServices\boot.efi

 

Edited May 25, 2025 by Anto65

[kaoskinkae]

This is my part of the miscconfig.plist

[Anto65]

Is it working for you now?

Edited May 25, 2025 by Anto65

[kaoskinkae]

2 minutes ago, Anto65 said:

¿Te está funcionando ahora?

With mine it doesn't work as you said, it sends you back to the opencore menu.

[Anto65]

no but that way it will only work for Win , Linux
for osx you have to start the preboot volume and 

..... System\Library\CoreServices\boot.efi

[kaoskinkae]

13 hours ago, Anto65 said:

no but that way it will only work for Win , Linux
for osx you have to start the preboot volume and 

..... System\Library\CoreServices\boot.efi

The boot is not in that folder, and the path or directory is incorrect. I still think it's impossible to do it this way.