Stuck on EXITBS:START

[spakk]

On 6/2/2026 at 11:54 AM, Dofik Dofran said:

i used the config that you send (

 

 

You're absolutely right, the config.plist was poorly edited. I'm working on the corrections. This will take some time.

 

Edit:

Replace SMBIOS data with GenSMBIOS
Validate the configuration: ocvalidate config.plist
Check BIOS settings (VMD, RST, Secure Boot, CFG Lock)
Boot and report the result
If errors occur, send me the ocvalidate output or the OpenCore log.

 

EFI_new1.rar: https://fileport.io/TueF2fwnvxsc

 

[deeveedee]

@spakk Recent site issues have restricted the upload limit for everyone.  I haven't tested recently, but it may be that this is still not fixed.

[Dofik Dofran]

19 hours ago, spakk said:

You're absolutely right, the config.plist was poorly edited. I'm working on the corrections. This will take some time.

 

Edit:

Replace SMBIOS data with GenSMBIOS
Validate the configuration: ocvalidate config.plist
Check BIOS settings (VMD, RST, Secure Boot, CFG Lock)
Boot and report the result
If errors occur, send me the ocvalidate output or the OpenCore log.

 

EFI_new1.rar: https://fileport.io/TueF2fwnvxsc

 

 

To the admins:

As a moderator, my ability to upload data is apparently restricted, a requirement I increasingly find to be a very bad joke. This limitation forces me to resort to external servers, which significantly complicates the workflow and impairs the efficiency of my moderation work.

I request clarification as to why this restriction exists and how quickly a solution can be expected.EFI_new1.rar

opencore-2026-06-03-125731.txt

[spakk]

3 hours ago, Dofik Dofran said:

opencore-2026-06-03-125731.txt 256 kB · 0 downloads

use the corrected config.plist. I found and fixed a few errors in the config.plist and hope that you can now boot.

 

If the system boots, then I would still need the following information that you can easily find under Windows. Proceed as follows:

 

Unknown Audio Codec
You have "alcid=1" in your boot-args. This could be wrong?

 

Please find your Audio Codec under Windows:

 

1. Open Device Manager
2. Expand Sound, Video and Game Controllers
3. Look for your audio device (e.g. Realtek Audio ?)
4. Write down the exact name

 

Or use AIDA64 → Multimedia → HD Audio

 

Unknown WiFi Chip!
You are using AirportItlwm.kext – this only works with Intel WiFi.

 

Please find your WiFi Chip under Windows:

1. Open Device Manager
2. Expand Network Adapters
3. Look for your Wireless Adapter
4. Write down the exact name
 

config.rar

[Dofik Dofran]

1 hour ago, spakk said:

use the corrected config.plist. I found and fixed a few errors in the config.plist and hope that you can now boot.

 

If the system boots, then I would still need the following information that you can easily find under Windows. Proceed as follows:

 

Unknown Audio Codec
You have "alcid=1" in your boot-args. This could be wrong?

 

Please find your Audio Codec under Windows:

 

1. Open Device Manager
2. Expand Sound, Video and Game Controllers
3. Look for your audio device (e.g. Realtek Audio ?)
4. Write down the exact name

 

Or use AIDA64 → Multimedia → HD Audio

 

Unknown WiFi Chip!
You are using AirportItlwm.kext – this only works with Intel WiFi.

 

Please find your WiFi Chip under Windows:

1. Open Device Manager
2. Expand Network Adapters
3. Look for your Wireless Adapter
4. Write down the exact name
 

config.rar 4.16 kB · 2 downloads

Still stucks at exitbs.. I sorry about your time you spend on me. Codec: Realtek Audio Wi-Fi chip: Intel Dual Band Wireless-AC 8265

[spakk]

3 minutes ago, Dofik Dofran said:

Still stucks at exitbs.. I sorry about your time you spend on me. Codec: Realtek Audio Wi-Fi chip: Intel Dual Band Wireless-AC 8265

Can you disable the E-Cores in BIOS?

 

Check here:

Advanced → CPU Configuration → E-Cores → Disabled

Or: Intel Thread Director → Disabled

[spakk]

1 hour ago, spakk said:

Can you disable the E-Cores in BIOS?

 

Check here:

Advanced → CPU Configuration → E-Cores → Disabled

Or: Intel Thread Director → Disabled

Let's do another test.

 

All about OpenCore

BIOS remains unchanged, do not disable E-Cores or Intel Thread Director.

The entire configuration runs via OpenCore:

• SSDT-PLUG-ALT.aml for Alder Lake Hybrid architecture
• CpuTscSync.kext for TSC synchronization
• CpuFriend.kext for frequency management
• RestrictEvents.kext for CPU information
   

Boot args:

„-v keepsyms=1 debug=0x100 -wegnoigpu -revpatch=sbvmm“
 

BIOS → Advanced:

• Intel VT-x → Enabled
• Intel VT-d → Disabled

Everything else remains at default.

 

EFI_new4

 

 

Edit:

 

 

Download USBToolBox!

You need to configure the USB ports correctly.

The USBToolBox tool is a USB mapping tool that supports Windows and macOS. It allows you to create a custom injector kext on Windows and macOS.

 

Steps:

Download USBToolBox:

https://github.com/USBToolBox/tool/releases

Run the tool and scan the USB ports:

Start USBToolBox.exe

 

Click "Detect Ports"

Connect USB devices (USB flash drive, mouse, keyboard, etc.) to EACH port and scan again

Create UTBMap.kext

 

Install the kext:

EFI/OC/Kexts/UTBMap.kext

Import the new drivers using OCAuxiliaryTools and modify the config.plist accordingly.

 

[FirstCustomac]

As far as Alder Lake is concerned, I think you would still need to spoof its cpuid to something that the macOS recognizes. It can also cause a hang at EXITBS:START even though it may not be the only reason. 

[spakk]

3 hours ago, Dofik Dofran said:

Still stucks at exitbs.. I sorry about your time you spend on me. Codec: Realtek Audio Wi-Fi chip: Intel Dual Band Wireless-AC 8265

 

1 hour ago, FirstCustomac said:

As far as Alder Lake is concerned, I think you would still need to spoof its cpuid to something that the macOS recognizes. It can also cause a hang at EXITBS:START even though it may not be the only reason. 

Spoofing the CPU ID for Alder Lake

 

You're right, Alder Lake (12th Gen) isn't natively supported by macOS. The CPU ID needs to be spoofed.

 

 

Method 1: RestrictEvents.kext (already located in EFI/OC/Kexts)

RestrictEvents.kext does this automatically.

RestrictEvents is already included in his config.plist.

 

Add to boot-args:

-revpatch=sbvmm

(This is already in his boot-args)

 

 

Method 2: Cpuid1Data / Cpuid1Mask (Manual)

If RestrictEvents isn't sufficient, he can manually spoof the CPU ID.

 

In config.plist under Kernel → Emulate:

<key>Emulate</key>
<dict>
    <key>Cpuid1Data</key>
    <data></data>
    <key>Cpuid1Mask</key>
    <data></data>
</dict>

 (Values for Alder Lake → Comet Lake spoof)

 

<key>Cpuid1Data</key>
<data>AYYIA/yJBQAAAA==</data>
<key>Cpuid1Mask</key>
<data>//////8AAAAA</data>

(This spoofs the CPU as Comet Lake (10th Gen) – macOS knows this.)

 

Method 3: FakeCPUID (Alternative)

 

<key>FakeCPUID</key>
<integer>0x0A0601</integer>

(This is Comet Lake's CPU ID)

 

What else he can do:

Step 1: Check if RestrictEvents is sufficient

Your boot arguments already contain -revpatch=sbvmm.

 

Step 2: If EXITBS:START hangs

Add Cpuid1Data/Cpuid1Mask:

 

<key>Emulate</key>
<dict>
    <key>Cpuid1Data</key>
    <data>AYYIA/yJBQAAAA==</data>
    <key>Cpuid1Mask</key>
    <data>//////8AAAAA</data>
    <key>DummyPowerManagement</key>
    <false/>
</dict>

 

 

Step 3: Check ProvideCurrentCpuInfo

In Kernel → Quirks:

 

<key>ProvideCurrentCpuInfo</key>
<true/>

 (This is already active)

 

 Try it like this first. If EXITBS:START hangs → Add Cpuid1Data/Cpuid1Mask.

 

[Dofik Dofran]

18 hours ago, spakk said:

 

Spoofing the CPU ID for Alder Lake

 

You're right, Alder Lake (12th Gen) isn't natively supported by macOS. The CPU ID needs to be spoofed.

 

 

Method 1: RestrictEvents.kext (already located in EFI/OC/Kexts)

RestrictEvents.kext does this automatically.

RestrictEvents is already included in his config.plist.

 

Add to boot-args:

-revpatch=sbvmm

(This is already in his boot-args)

 

 

Method 2: Cpuid1Data / Cpuid1Mask (Manual)

If RestrictEvents isn't sufficient, he can manually spoof the CPU ID.

 

In config.plist under Kernel → Emulate:

<key>Emulate</key>
<dict>
    <key>Cpuid1Data</key>
    <data></data>
    <key>Cpuid1Mask</key>
    <data></data>
</dict>

 (Values for Alder Lake → Comet Lake spoof)

 

<key>Cpuid1Data</key>
<data>AYYIA/yJBQAAAA==</data>
<key>Cpuid1Mask</key>
<data>//////8AAAAA</data>

(This spoofs the CPU as Comet Lake (10th Gen) – macOS knows this.)

 

Method 3: FakeCPUID (Alternative)

 

<key>FakeCPUID</key>
<integer>0x0A0601</integer>

(This is Comet Lake's CPU ID)

 

What else he can do:

Step 1: Check if RestrictEvents is sufficient

Your boot arguments already contain -revpatch=sbvmm.

 

Step 2: If EXITBS:START hangs

Add Cpuid1Data/Cpuid1Mask:

 

<key>Emulate</key>
<dict>
    <key>Cpuid1Data</key>
    <data>AYYIA/yJBQAAAA==</data>
    <key>Cpuid1Mask</key>
    <data>//////8AAAAA</data>
    <key>DummyPowerManagement</key>
    <false/>
</dict>

 

 

Step 3: Check ProvideCurrentCpuInfo

In Kernel → Quirks:

 

<key>ProvideCurrentCpuInfo</key>
<true/>

 (This is already active)

 

 Try it like this first. If EXITBS:START hangs → Add Cpuid1Data/Cpuid1Mask.

 

I do everything that you said, still stucks on exitbs, same log.

[spakk]

51 minutes ago, Dofik Dofran said:

I do everything that you said, still stucks on exitbs, same log.

 

To better understand the issue and provide targeted help, we need a detailed description of the steps you've taken so far.

Please describe as thoroughly as possible:

1. Creating the macOS Installer

• Which tool did you use to create the macOS installer?
• What exact version did you use?
• On which system (Windows, macOS, Linux) was the installer created?
• What specific steps did you take? (Please list them step by step.)

 

2. USB Drive / Boot Medium

• Which program did you use to create the bootable USB drive?
• Was the drive formatted beforehand? If so, in which format?
• Was the drive checked for errors or recreated multiple times?
• Have you tried testing the installer with another USB stick?

 

3. BIOS / UEFI Settings

• Which BIOS settings did you change?
• Was Secure Boot disabled?
• Was UEFI or Legacy Boot used?
• Was the boot order adjusted?
• Were there any other changes (e.g., AHCI, Fast Boot disabled)?
• Please provide a screenshot of each BIOS page and subdirectory so we can assist you.

 

4. Boot Attempt

What exactly happens when you try to boot from the USB drive?

Does the screen stay black, show a logo, or display an error message?

Is there a reboot loop, or does the system freeze?

Do you have any photos or a video of the boot process?

The goal is to precisely reconstruct the entire process so we can narrow down the possible issue step by step.

The more detailed your description, the faster we can identify the cause and provide a working solution.

 

[Dofik Dofran]

10 hours ago, spakk said:

 

To better understand the issue and provide targeted help, we need a detailed description of the steps you've taken so far.

Please describe as thoroughly as possible:

1. Creating the macOS Installer

• Which tool did you use to create the macOS installer?
• What exact version did you use?
• On which system (Windows, macOS, Linux) was the installer created?
• What specific steps did you take? (Please list them step by step.)

 

2. USB Drive / Boot Medium

• Which program did you use to create the bootable USB drive?
• Was the drive formatted beforehand? If so, in which format?
• Was the drive checked for errors or recreated multiple times?
• Have you tried testing the installer with another USB stick?

 

3. BIOS / UEFI Settings

• Which BIOS settings did you change?
• Was Secure Boot disabled?
• Was UEFI or Legacy Boot used?
• Was the boot order adjusted?
• Were there any other changes (e.g., AHCI, Fast Boot disabled)?
• Please provide a screenshot of each BIOS page and subdirectory so we can assist you.

 

4. Boot Attempt

What exactly happens when you try to boot from the USB drive?

Does the screen stay black, show a logo, or display an error message?

Is there a reboot loop, or does the system freeze?

Do you have any photos or a video of the boot process?

The goal is to precisely reconstruct the entire process so we can narrow down the possible issue step by step.

The more detailed your description, the faster we can identify the cause and provide a working solution.

 

So, i created a usb stick with installer from r-drive. I downloaded a .rdr file from macwin telegram channel, downloaded r-drive, go to r-drive and selected restore to usb drive. I have kingston 32gb usb drive. After process complete, i mount the efi partition on the usb drive to put there the opencore, cause original the clover on the efi partition(but i tried to boot from config-600series.plist and its not stuck on exitbs, it stuck on kdp_core zlib memory, but when i try new clover, it stucks too on exitbs). I tried too the method with BaseSystem.dmg and BaseSystem.chunklist but its stucking on same error. I create all installers on windows. I tried other usb stick. I checked it, and bo errors occured, i formatting before doind something with disk management, or diskpart when its cant be formatted. Yes i recreated usb drive many times. Secure boot is disabled, VT-d disabled,  E cores cant be disabled, uefi, fast boot disabled. For some reason i cant attach photos, so the other settings like default, intel vmd disabled, and other settings that you said is correct.