[GUIDE] Catalina, Big Sur, Monterey, Ventura, Sonoma, Sequoia, Tahoe on HP EliteDesk 800 G4/G5 Mini - The perfect MacMini8,1 Hackintosh

[deeveedee]

@ird the "flex-io" threw me off at first, too.  Then I realized that it's just another DP port installed in the Flex-IO slot (which I also use).  With my posted EFI, all 3 DP ports (including the DP port installed in the Flex-IO slot) are active and working.

 

EDIT: When Open Core Legacy Patcher (OCLP) creates macOS installers, it may inject kernel patches for unsupported Macs that are not suited to this hack.  OCLP should NOT be used to generate an installer for this hack.  We'll be in a better position to diagnose issues when the USB installer is created without OCLP and the Open Core EFI is posted for our review.

Edited April 27, 2025 by deeveedee

[InfiniteBSOD]

On 4/27/2025 at 7:01 PM, deeveedee said:

@ird the "flex-io" threw me off at first, too.  Then I realized that it's just another DP port installed in the Flex-IO slot (which I also use).  With my posted EFI, all 3 DP ports (including the DP port installed in the Flex-IO slot) are active and working.

 

EDIT: When Open Core Legacy Patcher (OCLP) creates macOS installers, it may inject kernel patches for unsupported Macs that are not suited to this hack.  OCLP should NOT be used to generate an installer for this hack.  We'll be in a better position to diagnose issues when the USB installer is created without OCLP and the Open Core EFI is posted for our review.

 

Appreciate it.

I followed the instructions in your post and recreated the USB-installer.
100% done using Apples "AppStore" (to download Sequoia) and the terminal-command to create the installer.

However still the same problem as before.

 

I tried to switch to the built-in DP, still the same result.

 

Posting the zipped EFI here.

EFI.zip

[deeveedee]

@InfiniteBSOD I won't have time to review your posted EFI for a while, but there are plenty of others who can help. Also, please post the exact model of your DP->HDMI adapter so we can make sure that it is an active adapter.

 

EDIT: Also, you probably stated this in a previous post, but please add resolution details about the HDMI display that you're driving with your DP->HDMI adapter.

 

EDIT2: @InfiniteBSOD I was reviewing your case here to be sure I understand your predicament and realize that I am confused about the problem you are experiencing.  You started this thread claiming that you encountered a "Prohibited symbol" when attempting to boot, so I recommended a couple of changes including SMBIOS and NVMe SSD.  You then posted this indicating that your problem is "the same as before," but it appears to me that your problem changed from "Prohibited symbol" to "black screen" : 

 

 

Could you please confirm that the problem that you are seeing is a black screen and is not a prohibited symbol?  "Prohibited symbol" and "black screen" are not the same problem.  The solutions to the two problems (Prohibited sign vs. black screen) are going to be different for each problem.  Thank you.

Edited April 29, 2025 by deeveedee

[InfiniteBSOD]

18 hours ago, deeveedee said:

@InfiniteBSOD I won't have time to review your posted EFI for a while, but there are plenty of others who can help. Also, please post the exact model of your DP->HDMI adapter so we can make sure that it is an active adapter.

 

EDIT: Also, you probably stated this in a previous post, but please add resolution details about the HDMI display that you're driving with your DP->HDMI adapter.

 

EDIT2: @InfiniteBSOD I was reviewing your case here to be sure I understand your predicament and realize that I am confused about the problem you are experiencing.  You started this thread claiming that you encountered a "Prohibited symbol" when attempting to boot, so I recommended a couple of changes including SMBIOS and NVMe SSD.  You then posted this indicating that your problem is "the same as before," but it appears to me that your problem changed from "Prohibited symbol" to "black screen" : 

 

 

Could you please confirm that the problem that you are seeing is a black screen and is not a prohibited symbol?  "Prohibited symbol" and "black screen" are not the same problem.  The solutions to the two problems (Prohibited sign vs. black screen) are going to be different for each problem.  Thank you.

 

@deeveedee 

 

Prohibited symbol vs screen going black

 

Sorry for any confusion, now when I re-read my posts I understand the cause of the confusion.

The very first time I followed this guide I entered "iMac19,1" instead of the default value of "Macmini8,1".
I did this because I followed the instructions in Dortania's guide here which had the following info:
 

SMBIOS	Hardware
iMac19,1	For Mojave and newer
iMac18,3	For High Sierra and older

 

I then received a reply that I should indeed use "Macmini8,1" (which is the default value in your "config.plist") as the value for "SystemProductName" when I use your EFI-configuration and not "iMac19,1".

 

I did the following tests just now with the following results:

 

#1: Entering "iMac19,1" as the value for "SystemProductName" and other associated values  (serial, board serial etc.) generated by GenSMBIOS. Booted with my USB-drive, "Reset NVRAM" > Reboot > "Install Mac OS X (external)".

Result: Apple logo is displayed, progress bar goes beyond 15% and around perhaps 40% suddenly shows the "prohibited"-symbol

 

#2 Entering "Macmini8,1" as the value for "SystemProductName" and other associated values  (serial, board serial etc.) generated by GenSMBIOS. Booted with my USB-drive, "Reset NVRAM" > Reboot > "Install Mac OS X (external)".
Result: Apple logo is displayed, progress bar stops at around 15%, screen goes purple and then black. Unable to get any input from my source ("HDMI 1") and have to do a hard shutdown (holding the power on/off button until my HP EliteDesk shuts down).

 

So the cause of the "prohibited symbol" was that I initially used "iMac19,1" as "SystemProductName".

The problem I experience now is with the correct value ("Macmini8,1") of "SystemProductName" - Apple logo is displayed > After around 15% my screen goes purple and I then can't recieve any signal when using my HP EliteDesk's source on my monitor.

 

Further information regarding display and HDMI>Displayport cable

 

My monitor is a "Philips 34M2C8600" and I use the following cable (as previously stated, not an adapter but a Displayport > HDMI-cable )
deleyCON 1,5m Displayport to HDMI (Amazon)

 

Thoughts about troubleshooting

 

Now I don't want to do anything which would cause further confusion (like following the part in Dortania's guide which stated "iMac19,1" when you expect "Macmini8,1") but I was thinking of swapping out the files and changing the values of the properties mentioned in the link below:

OpenCore Debugging | OpenCore Install Guide

in order to provide further information for debugging.

Would that be helpful?

 

Misc

 

I just wanted to say I appreciate the help, suggestions and feedback.
I understand that people (you especially) are doing this on their free time and really appreciate just receiving replies no matter how long they might take.
Like other people here I also work 9-5 and some days I'm just beat and don't feel like tinkering with this project when I get home so my updates might be somewhat infrequent.
Whereas other days I have more energy and feel more motivated of troubleshooting this particular project.
So, thank you everyone who contributes and hopefully if / when this gets sorted it can help someone else who has the same issue.

 

Edited April 29, 2025 by InfiniteBSOD
Unwanted sad smiley due to formatting

[deeveedee]

*** Please create a new thread for your "EliteDesk 800 G5 Mini with Philips 34M2C8600" and document your progress there.  I think this is going to require multiple iterations of experimentation and testing.  Thank you.  *****

 

@InfiniteBSOD If I understood the specs of your display, it has a DP 1.4 port.  I would strongly recommend that you use DP->DP for best performance.  The use of the DP->HDMI is going to complicate your graphics patching and may compromise video quality.

 

If you use a high-quality DP->DP cable (instead of the DP->HDMI cable), you will need to change the DisplayProperties in your config.plist (to a much simpler list of properties for DP ports).  See here.

 

In addition, you may need to research hi-res display configuration with UHD630, like this thread for example.

 

 

EDIT: If you do not want to replace your DP->HDMI cable, then you will likely need to experiment with different graphics patching solutions.  Try using the different DeviceProperties mentioned here, starting with the patching the DeviceProperties for 3 DP ports.  Since your experiments and test results could potentially generate a lot of posts, please create a new thread that is specific to your "EliteDesk 800 G5 Mini with Philips 34M2C8600" to document your progress.  I would be happy to help you, as will others, in that separate thread.

•  

Edited April 29, 2025 by deeveedee

[ird]

8 hours ago, InfiniteBSOD said:

 

@deeveedee 

 

Prohibited symbol vs screen going black

 

Sorry for any confusion, now when I re-read my posts I understand the cause of the confusion.

The very first time I followed this guide I entered "iMac19,1" instead of the default value of "Macmini8,1".
I did this because I followed the instructions in Dortania's guide here which had the following info:
 

SMBIOS	Hardware
iMac19,1	For Mojave and newer
iMac18,3	For High Sierra and older

 

I then received a reply that I should indeed use "Macmini8,1" (which is the default value in your "config.plist") as the value for "SystemProductName" when I use your EFI-configuration and not "iMac19,1".

 

I did the following tests just now with the following results:

 

#1: Entering "iMac19,1" as the value for "SystemProductName" and other associated values  (serial, board serial etc.) generated by GenSMBIOS. Booted with my USB-drive, "Reset NVRAM" > Reboot > "Install Mac OS X (external)".

Result: Apple logo is displayed, progress bar goes beyond 15% and around perhaps 40% suddenly shows the "prohibited"-symbol

 

#2 Entering "Macmini8,1" as the value for "SystemProductName" and other associated values  (serial, board serial etc.) generated by GenSMBIOS. Booted with my USB-drive, "Reset NVRAM" > Reboot > "Install Mac OS X (external)".
Result: Apple logo is displayed, progress bar stops at around 15%, screen goes purple and then black. Unable to get any input from my source ("HDMI 1") and have to do a hard shutdown (holding the power on/off button until my HP EliteDesk shuts down).

 

So the cause of the "prohibited symbol" was that I initially used "iMac19,1" as "SystemProductName".

The problem I experience now is with the correct value ("Macmini8,1") of "SystemProductName" - Apple logo is displayed > After around 15% my screen goes purple and I then can't recieve any signal when using my HP EliteDesk's source on my monitor.

 

Further information regarding display and HDMI>Displayport cable

 

My monitor is a "Philips 34M2C8600" and I use the following cable (as previously stated, not an adapter but a Displayport > HDMI-cable )
deleyCON 1,5m Displayport to HDMI (Amazon)

 

Thoughts about troubleshooting

 

Now I don't want to do anything which would cause further confusion (like following the part in Dortania's guide which stated "iMac19,1" when you expect "Macmini8,1") but I was thinking of swapping out the files and changing the values of the properties mentioned in the link below:

OpenCore Debugging | OpenCore Install Guide

in order to provide further information for debugging.

Would that be helpful?

 

Misc

 

I just wanted to say I appreciate the help, suggestions and feedback.
I understand that people (you especially) are doing this on their free time and really appreciate just receiving replies no matter how long they might take.
Like other people here I also work 9-5 and some days I'm just beat and don't feel like tinkering with this project when I get home so my updates might be somewhat infrequent.
Whereas other days I have more energy and feel more motivated of troubleshooting this particular project.
So, thank you everyone who contributes and hopefully if / when this gets sorted it can help someone else who has the same issue.

 

 

I will say this is progress to go from the error screen to a blank screen! Just so I understand this right, what you did is:

 

1) Grab the EFI deeveedee posted in the first post of this thread

2) Used GenSMBIOS tool to generate a serial, ROM etc. with MacMini8,1 as the product and replaced those entries accordingly in the EFI from (1)

 

Did you also patch iGPU framebuffer to enable displayport > HDMI connections as described in the first post? See this section in deeveedee's post:

 

Quote

UHD 630 Framebuffer Patching

• See here and here to understand my graphics properties for use with WhateverGreen.kext

• Read this to see my attempt at graphics patching without WhateverGreen.kext (WEG) to get a better understanding of what WEG is doing

 

If you've come this far, then I suspect the issues to be either one or a combination of below when mixed with Opencore + macOS:

 

1) iGPU framebuffer not correctly patched for right DP/HDMI interfaces. While I don't use this EFI, you may find others in the thread who use something similar that you could try experimenting with

2) DP>HDMI adapter issue (could be functional or it could be that your setup needs an active adatper); if possible try a different DP > HDMI cable, preferably active

3) An issue with your monitor (I searched online and found that firmware updates are possible for your monitor, you may want to try that). Try a different lower resolution monitor with a displayport connection if possible

 

If (2) and (3) above as possible and you have cable/monitor at hand (or can borrow) to test, that may help rule out other issues.

 

[InfiniteBSOD]

On 4/29/2025 at 9:04 PM, deeveedee said:

*** Please create a new thread for your "EliteDesk 800 G5 Mini with Philips 34M2C8600" and document your progress there.  I think this is going to require multiple iterations of experimentation and testing.  Thank you.  *****

 

@InfiniteBSOD If I understood the specs of your display, it has a DP 1.4 port.  I would strongly recommend that you use DP->DP for best performance.  The use of the DP->HDMI is going to complicate your graphics patching and may compromise video quality.

 

If you use a high-quality DP->DP cable (instead of the DP->HDMI cable), you will need to change the DisplayProperties in your config.plist (to a much simpler list of properties for DP ports).  See here.

 

In addition, you may need to research hi-res display configuration with UHD630, like this thread for example.

 

 

EDIT: If you do not want to replace your DP->HDMI cable, then you will likely need to experiment with different graphics patching solutions.  Try using the different DeviceProperties mentioned here, starting with the patching the DeviceProperties for 3 DP ports.  Since your experiments and test results could potentially generate a lot of posts, please create a new thread that is specific to your "EliteDesk 800 G5 Mini with Philips 34M2C8600" to document your progress.  I would be happy to help you, as will others, in that separate thread.

•  

Appreciate it!
Created a new post / thread here - HP EliteDesk 800 G5 DM with Philips 34M2C8600 - General Discussion | InsanelyMac

Will delve into changing values in the config.plist and try different DeviceProperties and document these in my new thread above after I've received and tried using an active Displayport to HDMI-adapter which arrives on Sunday.

 

On 4/30/2025 at 4:20 AM, ird said:

 

I will say this is progress to go from the error screen to a blank screen! Just so I understand this right, what you did is:

 

1) Grab the EFI deeveedee posted in the first post of this thread

2) Used GenSMBIOS tool to generate a serial, ROM etc. with MacMini8,1 as the product and replaced those entries accordingly in the EFI from (1)

 

Did you also patch iGPU framebuffer to enable displayport > HDMI connections as described in the first post? See this section in deeveedee's post:

 

 

If you've come this far, then I suspect the issues to be either one or a combination of below when mixed with Opencore + macOS:

 

1) iGPU framebuffer not correctly patched for right DP/HDMI interfaces. While I don't use this EFI, you may find others in the thread who use something similar that you could try experimenting with

2) DP>HDMI adapter issue (could be functional or it could be that your setup needs an active adatper); if possible try a different DP > HDMI cable, preferably active

3) An issue with your monitor (I searched online and found that firmware updates are possible for your monitor, you may want to try that). Try a different lower resolution monitor with a displayport connection if possible

 

If (2) and (3) above as possible and you have cable/monitor at hand (or can borrow) to test, that may help rule out other issues.

 

 

 

Thank you for the reply.

Yes that is correct, I downloaded the EFI from the main post and used GenSMBIOS to generate necessary information for "Macmini8,1" that needs to be inserted into the "config.plist".
I have not patched the iGPU framebuffer, appreciate the suggestion and I will look into that after I've tried with a newly purchased active Displayport to HDMI-adapter.

 

I will post updates and further posts in my new thread - HP EliteDesk 800 G5 DM with Philips 34M2C8600 - General Discussion | InsanelyMac

[deeveedee]

This is going to be my last post in this thread and one of my final posts at InsanelyMac.  There are rumors about macOS 26 (the next major release after Sequoia macOS 15).  The rumor mill indicates that MacMini8,1 is being dropped from official macOS support.  If MacMini8,1 is dropped in the next major macOS and Apple hasn't changed too much, we should be able extend the life of this hack by switching to SMBIOS iMac19,2 (which is rumored to have continued support) with the following changes:

• OC/config.plist: generate new PlatformInfo for SMBIOS 19,2
• OC/kexts/USBPorts.kext/Contents/info.plist: Change SMBIOS macMini8,1 -> iMac19,2

If this doesn't work, I suspect that Open Core Legacy Patcher (OCLP) will provide continued support for the MacMini8,1 (provided that Apple does include at least one Intel Mac in the next macOS).  For those who don't mind using OCLP and who understand the reduced security of OCLP relative to their use cases, that might also be an option.

 

I have thoroughly enjoyed working with those who contributed to this thread.  Thank you and good luck to all.

[ird]

It is now official and all but iMac20,1 and MacPro7,1 have been dropped from macOS 26. Those 2 models might be our last bet to extend the life of these miniPCs, though I have to admit that I’m not sure the iGPU or the dGPU in these miniPCs can handle the all new translucencies and transparencies with Metal 4 considering the RX560 only supports Metal 2.

 

https://arstechnica.com/gadgets/2025/06/macos-tahoe-signals-that-the-end-is-near-for-intel-macs-dumping-all-but-four-models/

[deeveedee]

Ok - this really will be my last post at InsanelyMac.  I felt guilty about leaving InsanelyMac just when we could be upgrading to the last macOS that officially supports Intel, so I have uploaded my latest EFI to Post #1.  This EFI, based on Open Core 1.0.5 Beta, installs and boots the first Tahoe Beta, but does not yet have working built-in Ethernet.  I'm using a USB-C Ethernet dongle until IntelMausi.kext (or whatever the issue) is fixed.  For working Ethernet,  see this.

 

The new EFI has the changes below.  It should serve as a tutorial for how to run unsupported macOS on our hack and give a good foundation for the changes that will be needed to run future versions of Tahoe.

 

OC 1.0.5Beta EFI R01 (based on Open Core 1.0.5 Beta)

•   Upgrade BOOT/BOOTx64.efi
•   Upgrade OC/OpenCore.efi
•   Upgrade OC/Drivers/*.* (except HfsPlus.efi)
•   Upgrade OC/Tools/*.*
•   OC/config.plist
  • Booter > Patch: Add "skip board id check" patch
  • Kernel > Add: Add USBMap.kext with MinKernel 25.0.0
  • Kernel > Add; Set MaxKernel 24.99.99 for USBPorts.kext
  • NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > boot-args: add -lilubetaall (and -v)
•   OC/Kexts
  • Add USBMap.kext (generated by CorpNewt's USBMap Beta for Tahoe)
•   OC/ACPI
  • Minor refactor of SSDT-WAK.aml

 

CorpNewt (and possibly others, not sure) figured out the XHC USB mapping required for Tahoe.  It is different from Sequoia and earlier macOS versions.  You'll notice that my new EFI injects the old USBPorts.kext up to MaxKernel 24.99.99 (Sequoia) and injects USBMap.kext starting with MinKernel 25.0.0 (Tahoe).  

 

The USBMap.kext is generated with CorpNewt's USBMap Beta for Tahoe.  Download it using "git clone https://github.com/corpnewt/USBMap.git --branch tahoe-test" and then run USBMap.command.  The USBMap.kext in my posted EFI does not enable port HS14 which is required for Bluetooth.  If you want Bluetooth or a different USB map for macOS Tahoe, you'll need to generate your own USBMap.kext.  Note that the USBMap.kext changes the port names from their original names with USBPorts.kext.  I didn't bother to fix this, so that's something else you can do if you want to.

 

My posted EFI boots Tahoe without changing the SMBIOS (still MacMini8,1), because it uses the Booter > Patch > "Skip Board ID Check" employed by Open Core Legacy Patcher.  With this Booter patch, there's no need to spoof a newer, supported SMBIOS.  This hack with SMBIOS MacMini8,1 runs Tahoe like a Supported Mac (albeit, without built-in Ethernet (yet)).

 

Note that I added "-lilubetaall" to boot-args.  This is because Acidanthera kexts had not yet been updated for Tahoe when I posted this.

Note also that I added "-v" boot-arg so that I could watch verbose boot messaging to debug my EFI.

 

Remember that Ethernet is not working yet.  I think a new IntelMausi.kext is needed, but I haven't investigated. If you need working Ethernet, see this.  You will need to modify config.plist in my posted EFI to set Kernel > Quirks > DisableIOMapper = true.

 

This should get you started.  Good luck!

 

About This Hack: Tahoe Beta

Spoiler

 

Edited June 13, 2025 by deeveedee
Added note about working Ethernet

[BALDY_MAN]

sorry your leaving. best of luck in all you do

[LockDown]

@deeveedee is Booter > Patch > "Skip Board ID Check" better than -no_compat_check flag?

[deeveedee]

@LockDown I'm using the "skip board ID check" patch because it's what I've used on my HackBookPro6,2 since Big Sur.  It's the same technique employed by Open Core Legacy Patcher.  I did use -no_compat_check when I was running Mojave and Catalina on my HackBookPro6,2 (when I was patching with DosDude's patcher), but I switched techniques to be consistent with OCLP. I'd suggest that you use what you prefer and what works for you.

 

Note that with the "Skip Board ID Check" patch, you may not automatically be notified when a new macOS version is available.  In this case, just manually check for the macOS update via System Settings > General > Check for Updates.

Edited June 12, 2025 by deeveedee

[logyon]

@deveedee 

Please don't leave us until Tahoe is fully released by the Autumn. Your work is valuable. Then, that will likely be our last Hackintosh, as support for security patches for Intel will, I believe, stop next year.

On a side note, can you post your previous EFI as well, since my hack mini boot drive died? I will have to do it fresh, but I want to use your last EFI and not the beta one.

 

[deeveedee]

Thanks to @lorys89 comment here, built-in Ethernet is fixed.  Kernel > Quirks > DisableIOMapper must be set (true).  With this change, Tahoe Beta is amazingly solid on this hack.  Not bad for an SMBIOS that is no longer "supported" in this latest macOS.

[miliuco]

@deevee

I'm sorry to read what seems like a farewell, although I hope you continue reading the forum and commenting from time to time. Your contributions have been very valuable.

I appreciate your comments about the USB ports and your internet. I haven't tried Tahoe yet because I've been busier than usual lately.

A big hug. And don't hesitate to share whatever you wish.

 

Edited June 12, 2025 by miliuco

[hiphopboy]

on Tahoe Beta 2, sound not work anymore  

[deeveedee]

I'm still checking in occasionally.  See sound fix for Tahoe Beta 2 here.

[hiphopboy]

on VoodooHDA to fix sound on Tahoe Beta 2, i can using the sound port on back, before must using the rear :V

[deeveedee]

How interesting is it that this hackintosh emulating MacMini8,1 is running macOS Tahoe easier than a real MacMini8,1.  See this from OCLP Dev User NeonBall over at MacRumors:

 

In real Macs, many basic things are handled by the T2. It works as an SSD controller, audio device (hence why AppleHDA was yanked, as the remaining models route audio through T2), media encode/decode, Security Enclave Processor (SEP), hardware Root of Trust for Secure Boot and bunch more I may be forgetting. It really is a taste of Apple Silicon on an Intel platform with a lot of tasks offloaded to it.

If the T2 challenge is not remedied, they won't be usable starting from the fact that the SSD won't be accessible at all. It may be possible to circumvent it with an external disk but that's not a good solution.

Edited July 2, 2025 by deeveedee

[deeveedee]

*** Caution: Before upgrading to macOS Tahoe, see warning here in next post ***

 

I have uploaded a new EFI based on Open Core 1.0.5 (Release) to Post #1.  The EFI has the following changes from my previous EFI based on Open Core 1.0.5 (Beta) and boots macOS through Tahoe Beta 3.

 

• Upgrade BOOT/BOOTx64.efi
• Upgrade OC/OpenCore.efi
• Upgrade OC/Drivers/*.* (except HfsPlus.efi)
• Upgrade OC/Tools/*.*
• OC/config.plist
  • Kernel > Add: Remove USBMap.kext
  • Kernel > Add; Remove MaxKernel 24.99.99 from USBPorts.kext
  • Kernel > Quirks > DisableIoMapper: True (required for Intel Ethernet in Tahoe)
  • NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > boot-args: remove -lilubetaall
  • NVRAM > Delete > 7C436110-AB2A-4BBB-A880-FE41995C9F82: Add csr-active-config
• OC/Kexts
  • Remove USBMap.kext
  • Modify USBPorts.kext to be compatible with macOS Tahoe (add usb-port-type, usb-port-number to each port definition in USBPorts.kext/Contents/Info.plist)
  • Upgrade AppleALC.kext 1.9.4 -> 1.9.5
  • Upgrade/change IntelMausi.kext 1.0.8 (Acidanthera) -> IntelMausiEthernet.kext v2.5.5d0 (Mieze)
  • Upgrade Lilu.kext 1.7.0 -> 1.7.1
  • Upgrade NVMeFix.kext 1.1.2 -> 1.1.3
  • Upgrade RestrictEvents.kext 1.1.5 -> 1.1.6
  • Upgrade VirtualSMC.kext 1.3.6 -> 1.3.7
  • Upgrade WhateverGreen.kext 1.6.9 -> 1.7.0
• OC/Kexts/SampleUsbKexts
  • Modify sample USB kexts to be compliant with macOS Tahoe (add usb-port-type, usb-port-number to each port definition)
• OC/ACPI
  • No changes

 

Note that the original USBPorts.kext (and the sample USB kexts in OC/Kexts/SampleUsbKexts) has been modified to be compatible with Tahoe, so that only one USBPorts.kext is required for Tahoe and previous versions of macOS.  A separate USB kext is no longer required for Tahoe.

 

Note also that starting with Tahoe Beta 2, AppleHDA has been removed from macOS, so sound no longer works with AppleALC.kext.  My preference is to use VoodooHDA as described here.  Others are using OCLP to restore AppleHDA.  I don't use OCLP on my "production" hacks because it requires that macOS integrity protection be partially disabled to allow unrestricted FS and unauthenticated root, requires AMFI to be disabled and OCLP roots macOS breaking the APFS Snapshot Seal.

 

About this Hack: macOS Tahoe Beta 3

Spoiler

 

Edited July 8, 2025 by deeveedee

[deeveedee]

*** Warning about macOS Tahoe Beta2 and later ***

On some of the hacks that I have upgraded to macOS Tahoe Beta 3 (possibly Beta 2 as well) the upgrade automatically enabled FileVault.  When I tried to login after FileVault was enabled, my hack would not accept my password (which required me to boot Recovery and manually decrypt the FileVaulted volume).

 

To avoid problems with FileVault, do the following immediately after upgrading Tahoe:

1. Open System Settings > Privacy & Security and scroll down to FileVault.  If FileVault is On, do the following...
2. Allow FileVault to finish encrypting your volume if it hasn't yet finished
3. After FileVault has finished encrypting your volume, change the FileVault "On" Slider to "Off"
4. Allow FileVault to decrypt your volume.  When decryption is complete, FileVault will be Off.

 

EDIT: If FileVault locks you out of your hack, see this that worked for me.

Edited July 8, 2025 by deeveedee

[ird]

3 hours ago, deeveedee said:

Note also that starting with Tahoe Beta 2, AppleHDA has been removed from macOS, so sound no longer works with AppleALC.kext.  My preference is to use VoodooHDA as described here.  Others are using OCLP to restore AppleHDA.  I don't use OCLP on my "production" hacks because it requires that macOS integrity protection be partially disabled to allow unrestricted FS and unauthenticated root, requires AMFI to be disabled and OCLP roots macOS breaking the APFS Snapshot Seal.

 

I guess I was wrong about AppleHDA and Beta 3. So, it's gone afterall. I now wonder if Intel HDA codec was ever used on esp. in the last few years or was audio completely offloaded to T2. Perhaps a mix of both as iMac19,x does not have T2?

[deeveedee]

@ird You were right about Polaris.  I am seeing that some are copying AppleHDA.kext from Tahoe Beta 1 into /Library/Extensions on Tahoe Beta 2+.  I haven't yet tried it, but if it works, that's another option.  Installation would be the same 'sudo cp -R ...' as with VoodooHDA.kext with csr-active-config = <03080000> and then csr-active-config = <01000000> after AppleHDA.kext is installed and working.

 

EDIT: The success with AppleHDA.kext -> /Library/Extensions was misreported or I misunderstood.  AppleHDA requires a solution like OCLP.  I'll stick with VoodooHDA.

Edited July 8, 2025 by deeveedee

[ird]

3 hours ago, deeveedee said:

@ird You were right about Polaris.  I am seeing that some are copying AppleHDA.kext from Tahoe Beta 1 into /Library/Extensions on Tahoe Beta 2+.  I haven't yet tried it, but if it works, that's another option.  Installation would be the same 'sudo cp -R ...' as with VoodooHDA.kext with csr-active-config = <03080000> and then csr-active-config = <01000000> after AppleHDA.kext is installed and working.

 

Understood, so the common exercise is to enable unsigned Kexts and use AppleHDA.kext from beta 1 instead of voodooHDA. At this time, I hope Apple retains the audio APIs used in Apple/VoodooHDA in the final version. While I personally do not use onboard audio (I use a USB audio interface), I can see how it would be unwieldy having yet another adapter sticking out.

 

Having said that, has anybody tried using Apple's USB-C DAC that is expected to work natively? If it does, there would be no need to change SIP settings. It's fairly affordable at $9, sleek and I've heard really good things about its audio quality. Intel MacMini/iMac/MacPros are officially supported.

 

Edit: Fixed link https://www.apple.com/shop/product/MW2Q3AM/A/usb-c-to-35-mm-headphone-jack-adapter

Edited July 8, 2025 by ird
Link