Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
When I use OCLP3.0n to download Tahoe 26.0.1, I got error as below, what can I do?

Extracting macOS installer from InstallAssistant.pkg
Failed to install InstallAssistant
Subprocess failed.
Command: ['/Library/PrivilegedHelperTools/com.dortania.opencore-legacy-patcher.privileged-helper', '/usr/sbin/installer', '-pkg', '/Users/mikezang/Downloads/OpenCore-Legacy-Patcher/payloads/InstallAssistant.pkg', '-target', '/']
Return Code: 166
Likely Enum: OCLP_PHT_ERROR_INVALID_TEAM_ID
Standard Output:
None
Standard Error:
None
 
When I use OCLP3.0n to download Tahoe 26.0.1, I got error as below, what can I do?

Extracting macOS installer from InstallAssistant.pkg
Failed to install InstallAssistant
Subprocess failed.
Command: ['/Library/PrivilegedHelperTools/com.dortania.opencore-legacy-patcher.privileged-helper', '/usr/sbin/installer', '-pkg', '/Users/mikezang/Downloads/OpenCore-Legacy-Patcher/payloads/InstallAssistant.pkg', '-target', '/']
Return Code: 166
Likely Enum: OCLP_PHT_ERROR_INVALID_TEAM_ID
Standard Output:
None
Standard Error:
None
rm -rf ~/Downloads/OpenCore-Legacy-Patcher/payloads

Relaunch oclp
 
Experimented with OCLP 2.4.0 from source, main goal is understanding. If that shows anything, then how well OCLP is written so that a non-specialist user like me can understand something.

First tried to generate the correct USB-Map.kext/Plist.info via OCLP directly. Modifications to several places in source listed in text file. The substantial changes are in the data at payloads/Kexts/Plists/AppleUSBMaps/Info.plist - here made only changes relevant to my MBP11,1 and MBP5,2. Caution, the Info.plist is not taken from here but setting up with Build-Project.command puts it into payloads.dmg so delete this first after changes to info.plist.

This modified 2.4.0 then generated correct EFIs for the 5,2 and 11,1.

Next was trying root patching. No metallib found yet for Tahoe so don't patch graphics. Try to get wifi to work.
Execution has to fail because Universal-Binaries.dmg doesn't contain things for Darwin 25 yet. So tried to use earlier versions (by cp -R 13.7.2-xx 13.7.2-25) and then repeat root patching without leaving OCLP.
Using xx=24 (i.e. Sequoia) executes the patch but patched system won't boot, so restored it.

I may try other xx later, but understanding was the goal.

Edit: with Sonoma (23), same result, won't boot. Referenced from WiFiPeerToPeer, missing symbol __os_trace_zalloc.
Same thing for me, using 3.0.0 nightly from July, 21: __os_trace_zalloc should be in /usr/lib/libSystem.B.dylib, but there is no /usr/lib/libSystem.B.dylib.

Code:
Symbol not found:  _os_trace_zalloc
Referenced from: <D5CF0107-33E0-337B-BA08-5E2854254FD0>    /System/Library/PrivateFrameworks/WiFiPeer ToPeer.framework/Versions/A/WiFiPeerToPeer
Expected in:     <2FAF2E09-0D9C-35C9-A5BD-2DADBEB10472>    /usr/lib/libSystem.B.dylib
AMFI: Denying core dump for pid 1 (launchd)pid 1 exited -- exit reason namespace 6 subcode 0x4, description Symbol not found:  _os_trace_zalloc
Referenced from: <D5CF0107-33E0-337B-BA08-5E2854254FD0>   /System/Library/PrivateFrameworks/WiFiPeerToPeer.framework/Versions/A/WiFiPeerToPeer
Expected in:     <2FAF2E09-0D9C-35C9-A5BD-2DADBEB10472>    /usr/lib/libSystem.B.dylib
panic(cpu 0 caller Oxffffff802ae84b53):  initproc failed to start -- exit reason namespace 6 subcode 0x4 description: Symbol not found:  _os_trace_zalloc
Referenced from: <D5CF0107-33E0-337B-BA08-5E2854254FD0>    /System/Library/PrivateFrameworks/WiFiPeerToPeer.framework/Versions/A/WiFiPeerToPeer
Expected in:     <2FAF2E09-0D9C-35C9-A5BD-2DADBEB10472>    /usr/lib/libSystem.B.dylib
 
rm -rf ~/Downloads/OpenCore-Legacy-Patcher/payloads

Relaunch oclp
Does that actually solve his problem? I thought this was solved by building privileged helper with DEBUG option.

EDIT: @mikezang You do know that Tahoe is still not supported by OCLP 3.0.0 - right?

EDIT2: @sinbad21 OCLP 3.0.0 won't patch without modifications. You can try copying and pasting the missing components (renaming them as needed), but in my case, the mods didn't work.
 
Does that actually solve his problem? I thought this was solved by building privileged helper with DEBUG option.

EDIT: @mikezang You do know that Tahoe is still not supported by OCLP 3.0.0 - right?

EDIT2: @sinbad21 OCLP 3.0.0 won't patch without modifications. You can try copying and pasting the missing components (renaming them as needed), but in my case, the mods didn't work.
Just offering a quick fix. Did it actually work?
 
Last edited:
The fix for OCLP_PHT_ERROR_INVALID_TEAM_ID error is to make privileged helper with Debug argument.

EDIT: See OCLP build instructions here
https://forums.macrumors.com/thread...pported-macs-discussion.2458481/post-34029215

EDIT2: I should clarify - it's the only fix I know. If there's another way to fix short of building with Dortania's Team ID, I'm not aware of it.
There are a lot of contents in link, can you show me the simple way to fix OCLP_PHT_ERROR_INVALID_TEAM_ID error directly?
 
Last edited:
T26 B3/3.0.0n. OTW/OTA

Edit: If you have never heard the old saying "ya godda be kiddin me", just take a peak at the pic. Apple is melding the MacOS and IOS. No wonder the Devs are having a hard time, but someday the wait will be worth it.

The pic is the screen of the Imac, I had to restart to get things really going, after taking a long time to get the mouse on continue, which finally acted like an update on the phone. Now it is back to normal but every thing was stacked in the process. The visuals seem to again be improved.
 

Attachments

  • IMG_1653.jpeg
    IMG_1653.jpeg
    147.3 KB · Views: 102
Last edited:
Due to an increase in the volume of work this time of year, I could not run any tests regarding Tahoe + FileVault (as reported on Issue#1167):

FileVault​

There have been reports of FileVault being turned on automatically with the installation of Tahoe, leading to issues with volume decryption. This is another casualty of the OS only supporting T2 Macs (which handle FileVault through the T2). This should be fixed with using apfs.efi from Sequoia, but remains to be tested.

Does anyone tested if apfs.efi from Sequoia fixed the problem?

Thank you,
 
Due to an increase in the volume of work this time of year, I could not run any tests regarding Tahoe + FileVault (as reported on Issue#1167):

FileVault​

There have been reports of FileVault being turned on automatically with the installation of Tahoe, leading to issues with volume decryption. This is another casualty of the OS only supporting T2 Macs (which handle FileVault through the T2). This should be fixed with using apfs.efi from Sequoia, but remains to be tested.

Does anyone tested if apfs.efi from Sequoia fixed the problem?

Thank you,
I found this methode to disable FileVault in recovery and it worked for me after updating to Tahoe 26 on my Hackintosh and the system was locked.
Anther way is to disable FileVault once the update finish and wait untill it finishes all process then restart as it will lock after first restart.
 
People have no idea how long it takes to fix a single bug and these patches have many.
Please take your time. And in the time you take, can you please also address the glitch in Safari where sites requiring WebGL are black, and a spinning cube doesn't show up in get.webgl.org? It's been happening since I updated to macOS Sequoia and used Safari 18.0, and the situation still hasn't improved in Safari 26.0.1.

Thank you in advance.



Screenshot 2025-10-19 at 11.19.57 am.png
Screenshot 2025-10-19 at 11.18.02 am.png
 
  • Like
  • Love
Reactions: macinfo and OKonnel
If you're repeatedly announcing that you're waiting patiently, you're not waiting patiently.
Where I come from, ladies get more than a pass; even if one thinks she wasn't waiting patiently. But then, I am an old geezer (80+). Repeating herself a few times is far better than berating the developers of OCLP. She's one of the best contributors on this thread. There's nothing objectionable in what she wrote.

BTW, Tahoe 26.1 Beta 4 is out also (Build 25B5072a). Perhaps there'll be OCLP 3.0.x that will work for Tahoe, perhaps not. No matter. It's for a laptop gift, I've been awaiting - patiently - for 5 months. Either Sequoia or Tahoe.
 
Last edited:
Where I come from, ladies get more than a pass; even if one thinks she wasn't waiting patiently. But then, I am an old geezer (80+). Repeating herself a few times is far better than berating the developers of OCLP. She's one of the best contributors on this thread. There's nothing objectionable in what she wrote.

BTW, Tahoe 26.1 Beta 4 is out also (Build 25B5072a). Perhaps there'll be OCLP 3.0.x that will work for Tahoe, perhaps not. No matter. It's for a laptop gift, I've been awaiting - patiently - for 5 months. Either Sequoia or Tahoe.
After using Sequoia for six months, in March I returned to Sonoma for my 27-inch iMac 14,2 , late 2013, but with SSD instead of Fusion Drive, as in my signature.
Since then, Sonoma forever (!!!), because everything works as if my Mac were new.
And since one time we used to buy computers (Mac or PC) for the sole purpose of running applications and working... (and Sonoma does that very well) and not to admire Explorer, Finder or useless aesthetic effects..., I couldn't care less about “liquid glass” (which, incidentally, does not exist in nature).
I left Sequoia because some things didn't work well (including the Preview application, which I consider essential) and because sometimes there were strange behaviors related to new features (which I consider "experiments") linked to security changes and also oriented towards AI and a new Spotlight (useless for Intel Macs) made in Sequoia by Apple in view of Tahoe.
All of these things unnecessarily weigh down many unsupported Macs and somehow make Sequoia a "transitional" system, as was the case with Big Sur and Ventura. (Monterey and Sonoma brought stability and, together with the improvements made by OCLP, represented a milestone.)
This usually happens alternately, but we all know that macOS 27 will bring a lot of stability thanks to all the efforts Apple is making in Tahoe to improve the system and truly integrate it with the so-called Apple Intelligence and with new M5 CPUs, ecc.

Note
I would like to point out that what I write represents only my point of view based on my experience with my Mac and Mac of other friends, and therefore I accept, respect, and do not wish to contradict anyone who thinks differently from me. 🤗
 
I wouldn't be quick too upgrade to Tahoe even if we get a new patcher. All my important files are on a mechanical Hard Drive I've used forever. Tahoe won't read these discs. Also, it won't support legacy peripherals, but that support left long before Tahoe apparently. It's a glitzy operating system, But yesterday I downgraded to Sequoia. If Apple fixes this, I may upgrade...maybe
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.