Yea, eagerly waiting for the final OCLP for my 5,1.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Tahoe 26 on Unsupported Macs Discussion
- Thread starter jshayya0184
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
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
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
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
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.
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.
Last edited:
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?
@mikezang That link with 'a lot of contents' lists the build steps. How did you build OCLP 3.0.0?
I used updateoclp.sh to update OCLP 3.0.0, then run it by python OpenCore-Patcher-GUI.command .
cat updateoclp.sh
cd ~/Downloads
rm -fr OpenCore-Legacy-Patcher
git clone --branch macos-next --single-branch https://github.com/dortania/OpenCore-Legacy-Patcher
cd OpenCore-Legacy-Patcher
pip install -r requirements.txt
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.
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
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):
Does anyone tested if apfs.efi from Sequoia fixed the problem?
Thank you,
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,
Upgrade from Tahoe 26.1 Beta 2 -> Beta 3 completed via OTA without issues. Still waiting patiently for OCLP 3.0.0 post-install patches and am happy that this old rig is still alive and kicking.
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.
3 Ways to Turn Off FileVault on Mac with/Without macOS
How to disable FileVault on Mac in System Settings/Preferences, using Terminal, or in Recovery Mode. Find solutions if you can't turn off FileVault on Mac.
www.drbuho.com