OCLP T2

Deutsch

English

Deutsch

English

Erscheinungsbild

← Alle Issues

[Bug]: MacBookPro14,3 stuck at Apple logo after Tahoe 26.6.2 installation with 4.0.0.18003.9

· von @astralchen

Mac model / Mac-Modell

T1 — MacBook Pro 2017, model identifier MacBookPro14,3.

Target macOS version

macOS Tahoe 26.6.2, build 25G83.

OpenCore Legacy Patcher T2 version

4.0.0.18003.9 — 4.0.0 alpha 18.3.9
Release: https://github.com/albert-mueller/OpenCore-Legacy-Patcher-T2/releases/tag/4.0.0.18003.9

Issue type / Typ Fehler

Boot failure / installation does not reach Setup Assistant or the desktop.

Description

After running the macOS Tahoe 26.6.2 installation on my 2017 MacBookPro14,3 using the release above, the machine remains stuck on the Apple logo and progress bar (Photo 1). It does not reach Setup Assistant, the login screen, or the desktop.

I then forced a restart and held Option. Apple's Startup Manager displayed two entries: EFI Boot and macOS Installer (Photo 2). EFI Boot is highlighted in the photo. This photo shows the entries available after restarting; it does not establish what happens after selecting either entry.

Although the installation appeared to have finished from my perspective, I cannot confirm that every installation phase completed, since the machine has not reached the installed system and a macOS Installer entry remains visible.

Steps to reproduce / observed sequence

  1. Download the full Tahoe 26.6.2 installer using softwareupdate --fetch-full-installer --full-installer-version 26.6.2.
  2. Verify SharedSupport.dmg and create a USB installer with Apple's createinstallmedia tool.
  3. Use OpenCore Legacy Patcher T2 4.0.0.18003.9 to build/install OpenCore for MacBookPro14,3. The app reports that OpenCore finished installing to disk.
  4. Run the Tahoe installation on the target MacBookPro14,3.
  5. Observe that the machine remains on the Apple logo/progress bar instead of reaching Setup Assistant or the desktop.
  6. Force a restart and hold Option: EFI Boot and macOS Installer appear, as shown in Photo 2.

Expected behavior

The installation should complete all required restart phases and reach Setup Assistant or the installed system when booted through the appropriate OpenCore entry.

Installer checks already performed

The final installer image was approximately 17 GiB, and hdiutil verified its partition checksums and reported:

checksum of SharedSupport.dmg is VALID

createinstallmedia completed successfully with:

Install media now available at "/Volumes/Install macOS Tahoe"

An earlier incomplete installer was replaced before this installation attempt; the results above are from the replacement installer used to create the USB.

Logs and information not yet available

No verbose boot log, panic log, or EFI archive is attached. The photos do not show a panic message. The exact wait duration, the precise installation phase that stalled, whether OpenCore was selected on every automatic restart, and the final root-patch state have not been confirmed. I am not claiming a specific kernel, GPU, or APFS cause from these photos alone.

Could you advise which boot entry to select at this stage and which logs would help determine why installation/boot is not progressing?

Photos

Photo 1 — Apple logo and progress bar where the machine remains stuck

Photo 1: Stuck at Apple logo and progress bar

Photo 2 — Option-key Startup Manager after a forced restart

Photo 2: EFI Boot and macOS Installer entries

Kommentare

@astralchen · · bearbeitet

image
image
image
image

@Medelcartelinc ·

Hi @astralchen,

Great to see that your MacBookPro14,3 successfully booted to the macOS 26.6.2 Tahoe desktop!

Regarding the root patching failure shown in your photos:

1. Root Cause of the Error

The output hdiutil: attach failed - 权限被拒绝 translates to Permission denied, and 认证错误 is an Authentication error.
On macOS Tahoe, running hdiutil attach on the encrypted Universal-Binaries.dmg from inside /Library/Application Support/Dortania/ is being blocked by macOS TCC / sandbox privacy controls, preventing the payload disk image from unlocking with the automatic passphrase. Because the disk image was prevented from mounting, the patcher could not locate AMD9500Controller.kext at line 998 of sys_patch.py.

2. Developer Mode Requirement

For MacBookPro14,3 (T1) on macOS Tahoe, Developer Mode must be enabled in OpenCore Legacy Patcher T2 (via Settings -> Developer Mode, or by creating ~/.dortania_developer).
Enabling Developer Mode unlocks the T1 experimental patch routines and the Level-D (All-In-One) profile specifically tuned for the dual Intel Kaby Lake + AMD Polaris GPUs and T1 security handling on Tahoe.

3. Step-by-Step Fix

  1. Grant Full Disk Access:
    Go to System Settings -> Privacy & Security -> Full Disk Access and ensure OpenCore-Patcher-T2.app (and Terminal) are enabled.
  2. Clear the Incomplete / Locked Cache and Enable Developer Mode:
    Open Terminal and execute: 
    sudo rm -rf "/Library/Application Support/Dortania"
touch ~/.dortania_developer
  3. Use the Full Package Release:
    Download and run the OpenCore-Patcher-T2.pkg from release 4.0.0.18004.1. The .pkg installer deploys all required payloads and frameworks directly to disk with proper root permissions, avoiding the runtime hdiutil encrypted disk mount issue.
  4. Open OpenCore Legacy Patcher T2, verify Developer Mode is indicated, click macOS Configuration / Post-Install Root Patch, and start root patching.

@astralchen ·

Thanks for your guidance. I followed the steps and completed the process, but the built-in camera and Touch Bar are not working on my MacBookPro14,3 (2017, T1).

Are any additional patches or steps required to get them working? Please let me know which logs or diagnostic information would help investigate. Thank you!

@Medelcartelinc ·

Hey @astralchen,

I have the exact same 2017 MacBookPro14,3 on Tahoe, and I hit these exact same roadblocks. Here is everything you need to get it 100% running:

1. The Password & Missing AMD Kext

You're actually spot on about the password — in Albert's repo / PatcherSupportPkg convention, Universal-Binaries.dmg is indeed encrypted with "password".
However, macOS Tahoe's updated security blocks the GUI app from mounting encrypted disk images cleanly, so hdiutil errors out with permission/auth issues and leaves it unmounted. Because the DMG fails to mount, AMD9500Controller.kext (which lives inside that DMG) shows up as missing during preflight.
Also: seeing Experimental Mode is ON and Version 5.0.0 inside the window is completely normal for our test builds.

2. How to Run Root Patching (Terminal Launch)

To bypass Tahoe's DMG mount restrictions, launch the patcher directly from Terminal:

  1. Close the patcher if open.
  2. Open Terminal and run: 
    sudo "/Applications/OpenCore-Patcher-T2.app/Contents/MacOS/OpenCore-Patcher-T2"
    (Or if running from source: python3 OpenCore-Patcher-GUI.command)
  3. Enter your Mac login password when Terminal asks.
  4. Once the GUI opens, click Post-Install Root Patch -> Start Root Patching.
    Running through Terminal lets macOS handle the sudo session and mount the DMG with the passphrase properly, so the AMD Polaris graphics drivers install smoothly. (Note: in our latest build we also removed the experimental T1 Login Touch ID patch from the list, leaving just the clean native T1 Security Chip patch).

3. Touch Bar — The Ventura Kickstart Trick

If your Touch Bar remains dark, it usually means the embedded T1 firmware partition was wiped or unlinked during the recovery clean install of Tahoe.
There is a proven trick that works every time: attach an external drive or USB with macOS 13 Ventura and boot into it once. Ventura communicates natively with the T1 chip and immediately flashes/initializes the Touch Bar micro-OS at the hardware level. Once initialized, boot back into Tahoe (with the T1 root patch applied) and the Touch Bar will work normally!

4. FaceTime HD Camera & Boot-args

The camera on MBP14,3 is PCIe-based (AppleCameraInterface.kext). When you launch FaceTime or Photo Booth, macOS switches over to the discrete AMD GPU via gMux. To avoid display stalls or black frames during this switch, make sure your OpenCore config.plist includes:

  • AppleCameraInterface.kext in EFI/OC/Kexts
  • These boot-args in NVRAM: 
    keepsyms=1 debug=0x100 -lilubetaall ipc_control_port_options=0 -nokcmismatchpanic amfi=0x80 agdpmod=pikera
    agdpmod=pikera is the crucial argument here to ensure smooth discrete GPU switching for camera apps.

Give the Terminal launch a spin first to finish the root patch, try the Ventura boot to kickstart the Touch Bar, and let me know how it goes!

@astralchen ·

Hi @Medelcartelinc, a quick update on my MacBookPro14,3:

I erased and reformatted the entire drive, performed a clean installation of macOS Ventura, and then installed macOS Tahoe 26.6.2 using OpenCore-Legacy-Patcher-T2 4.0.0.18005 — 4.0.0 alpha 18.5.

The Touch Bar and built-in camera are now working. The only remaining issue I have noticed is that Touch ID still does not work.

Thanks for your help!

@Medelcartelinc ·

Hi @astralchen,

That is fantastic news! Getting the Touch Bar and Camera to work on Tahoe is a huge step forward.

As for Touch ID, don't worry—it is actually expected that it doesn't work right now! We intentionally disabled the Touch ID patches for Tahoe because injecting the old Ventura authentication binaries was causing severe system instability and crashes.

For the time being, we have decided to stick with this stable patchset that safely enables the Touch Bar and Camera without breaking the rest of the OS. We might look into fixing Touch ID in the future, but right now we are prioritizing system stability.

Enjoy the working Touch Bar and Camera!

Dieses Issue auf GitHub diskutieren6 Kommentare

Copyright © Dortania 2020–2025 · T2-Fork © 2026 Albert Müller und OCLP-T2-Mitwirkende