Stop on Opencore boot menu

[Deleted member 22707]

I'm trying to install sonoma 14.5
CPU: 7500F
MB: Asus B650 TUF plus-wifi
GPU: RX 6800
RAM: XPG Lancer 16x2 6000mhz

 

[Edhawk]

Post a copy of your whole EFI folder so we can see what you are using. The config.plist doesn’t tell us the whole story.

 

[Deleted member 22707]

Yes, of course

 

[leesurone]

Yes, of course

Among other issues you are missing from your config.plist any Booter/Mmiowhitelist entries essential to boot. See the attached, USB configuration is going to be wrong so be prepared to try various USB ports and ethernet or wireless/bluetooth its not configured. Those can be added later if you can install.

 

[Deleted member 22707]

thx, now it works but I have a new error "You may not install to this volume because the computer is missing a firmware partition" when I try to choose a disk

 

[leesurone]

thx, now it works but I have a new error "You may not install to this volume because the computer is missing a firmware partition" when I try to choose a disk

Okay, good. Did you open disk utility once the installer loads and format your target disk properly?

 

[Deleted member 22707]

Okay, good. Did you open disk utility once the installer loads and format your target disk properly?

Yes, I tried to format to mac os and got this error. With apfs I have this problem too

 

[craighazan]

Yes, I tried to format to mac os and got this error. With apfs I have this problem too

I've also erased my HD as macOS Extended Journaled, I let the Installer set the format.

 

[Deleted member 22707]

I've also erased my HD as macOS Extended Journaled, I let the Installer set the format.

I think something with EFI because I was installing mac os ventura today and I had not this problem

 

[Deleted member 22707]

I tried to install ventura again and got error, so I dont know where I shoud find solution

 

[leesurone]

I think something with EFI because I was installing mac os ventura today and I had not this problem

@Nestovsky were you using the same EFI I uploaded to install Ventura? If so you can always use software update to move to Sonoma.
Another option is to try this version of the EFI, it should have ethernet enabled.

 

[Deleted member 22707]

@Nestovsky were you using the same EFI I uploaded to install Ventura? If so you can always use software update to move to Sonoma.
Another option is to try this version of the EFI, it should have ethernet enabled.

No, I used another EFI which started in Ventura but crashed in sonoma. With both efi I have (You may not install to this volume because the computer is missing a firmware partition)

 

[Deleted member 22707]

No, I used another EFI which started in Ventura but crashed in sonoma. With both efi I have (You may not install to this volume because the computer is missing a firmware partition)

The same error is with external disk and sd card

 

[Deleted member 22707]

I dont know how, but I fixed it after 10 restart of my pc

 

[parlin]

thx, now it works but I have a new error "You may not install to this volume because the computer is missing a firmware partition" when I try to choose a disk

I have the same cpu and motherboard and when I shut down macOS, it immediately restarts

 

[leesurone]

I have the same cpu and motherboard and when I shut down macOS, it immediately restarts

That is usually a symptom of improperly mapped USB ports believe it or not.

 

[parlin]

That is usually a symptom of improperly mapped USB ports believe it or not.

I used USBToolBox to export the USB driver, Hackintool to remove redundant ports, and then exported USBPorts.kext. Restart immediately after shutdown still occurs

 

[leesurone]

I used USBToolBox to export the USB driver, Hackintool to remove redundant ports, and then exported USBPorts.kext. Restart immediately after shutdown still occurs

I’m not saying you did it wrong but I’ve read more than my fair share of posts with similar comments only to find errors in the port mapping.The best course for you is to zip and post your EFI for review.

 

[parlin]

I’m not saying you did it wrong but I’ve read more than my fair share of posts with similar comments only to find errors in the port mapping.The best course for you is to zip and post your EFI for review.

 

[leesurone]

Wow, hard to know where to start with your EFI as it is a complete mess. Decide what is working for you and delete the entries you don't need for start.
Your USB Map is wrong, these are the ports Asus says that board has:
USB
Rear USB (Total 8 ports)
1 x USB 3.2 Gen 2x2 port(s) (1 x USB Type-C®)
3 x USB 3.2 Gen 2 port(s) (2 x Type-A + 1 x USB Type-C®)
4 x USB 2.0 port(s) (4 x Type-A)
Front USB (Total 7 ports)
1 x USB 3.2Gen 1 connector (supports USB Type-C®)
1 x USB 3.2 Gen 1 header(s) support(s) additional 2 USB 3.2 Gen 1 ports
2 x USB 2.0 header(s) support(s) additional 4 USB 2.0 ports

I don't know which ports you enabled but your Type C ports are probably type 9, not 10. You also seem to be labeling USB 3 ports as 0 and 3. If it's USB 3 then both HS and SS ports should be type 3. You should also be able to map and use all the ports mentioned above and stay under the 15 port limit because of the different controllers used, 15 ports each is how they add up.
EDIT: You also do not have any internal USB ports mapped for your Bluetooth controller and your LED controller
I would clean up your EFI, turn off any port mapping you have previously tried, turn on the XHCIPortLimit quirk and then try to use CorpNewts USB Map Master to configure your ports.

GitHub - corpnewt/USBMap: Python script for mapping USB ports in macOS and creating a custom injector kext.

Python script for mapping USB ports in macOS and creating a custom injector kext. - corpnewt/USBMap

github.com