Jump to content
3741 posts in this topic

Recommended Posts

2 hours ago, Matgen84 said:

 

Unfortunately not working 🥲 After enter the password, always stuck at login screen, with cursor. 

 

@Matgen84, If you are using latest official release of WhateverGreen.kext, try to boot with boot argumentagdpmod=pikera 😉

Edited by KGP-iMacPro
  • Like 2
31 minutes ago, Takiller said:

Yes, my Matebook X Pro laptop is currently on MP7,1 as a workaround for Apple Music audio issues in Teaho and you might be correct as it does have an unsupported Nvidia eGPU 🤔. It's true indeed that we learn till our last breaths 😜

 

I performed a quick test on my iGPU-only HackMini8,1.  I didn't test much, but after changing SMBIOS from MM8,1 to MP7,1, it boots Tahoe Beta 3 without issues.

 

Screenshot2025-07-09at12_20_39PM.png.e392061ac8a29653c95ef1092f4ad6ce.png

 

To change SMBIOS from MM8,1 to MP7,1, I did the following:

  • Use CorpNewt's GenSMBIOS to generate the PlatformInfo attributes for MP7,1
  • Modify USBPorts.kext/Contents/Info.plist: change two instances of MacMini8,1 -> MacPro7,1

 

Note that I have never found it necessary to "re-map" USB ports after changing SMBIOS.  I've seen others state this necessity, but I think it is only necessary to change the SMBIOS in the USB kext Info.plist.  Much easier in my opinion.

 

EDIT: I thought this was funny... About This Mac shows a MacPro7,1 with a MacMini8,1 identifier.  This is because I have modified com.apple.SystemProfiler.plist to show "HP EliteDesk 800 G5 Mini."

Spoiler

Screenshot2025-07-09at12_34_24PM.png.87098912d129761d75bafa8a0c529ec0.png

 

Edited by deeveedee
  • Like 5
  • Thanks 2
1 hour ago, deeveedee said:

 

I performed a quick test on my iGPU-only HackMini8,1.  I didn't test much, but after changing SMBIOS from MM8,1 to MP7,1, it boots Tahoe Beta 3 without issues.

 

Screenshot2025-07-09at12_20_39PM.png.e392061ac8a29653c95ef1092f4ad6ce.png

 

To change SMBIOS from MM8,1 to MP7,1, I did the following:

  • Use CorpNewt's GenSMBIOS to generate the PlatformInfo attributes for MP7,1
  • Modify USBPorts.kext/Contents/Info.plist: change two instances of MacMini8,1 -> MacPro7,1

 

Note that I have never found it necessary to "re-map" USB ports after changing SMBIOS.  I've seen others state this necessity, but I think it is only necessary to change the SMBIOS in the USB kext Info.plist.  Much easier in my opinion.

 

EDIT: I thought this was funny... About This Mac shows a MacPro7,1 with a MacMini8,1 identifier.  This is because I have modified com.apple.SystemProfiler.plist to show "HP EliteDesk 800 G5 Mini."

  Reveal hidden contents

Screenshot2025-07-09at12_34_24PM.png.87098912d129761d75bafa8a0c529ec0.png

 

Thanks a lot @deeveedee as I now have lossless apple music audio in Teaho after a successful change to the MP7,1 smbios 🫡

  • Like 5

@Takiller Congratulations! I don't use AppleMusic and am not a DRM expert, so forgive the remedial question: Are you able to play DRM-protected content via AppleMusic on your iGPU-only hack (UHD630) after changing SMBIOS to MP7,1?   Do you have any boot-args/DeviceProperties or did you need to execute any commands from terminal?

 

EDIT: And just to confirm, the same DRM-protected music does not play when your SMBIOS is MM8,1 - Correct?

Edited by deeveedee
  • Like 3
35 minutes ago, deeveedee said:

@Takiller Congratulations! I don't use AppleMusic and am not a DRM expert, so forgive the remedial question: Are you able to play DRM-protected content via AppleMusic on your iGPU-only hack (UHD630) after changing SMBIOS to MP7,1?   Do you have any boot-args/DeviceProperties or did you need to execute any commands from terminal?

 

EDIT: And just to confirm, the same DRM-protected music does not play when your SMBIOS is MM8,1 - Correct?

Yes, Apple Music DRM is working without any boot-args, no DeviceProperties and no terminal commands. I am using your EFI as is, just changed SMBIOS and disabled the no board check patch.

Edited by Takiller
Yes, that's correct no DRM music with MM8,1 on Sequoia going back and no sound with Teaho which forced me to adventure to MP7,1. The 1st time I encountered this was with my laptop on Teaho with MBP16,4 where music was playing with no sound in apple music
  • Like 3

@Takiller  If more discussion is necessary, let's move this discussion to the HackMini8,1 thread here.  I don't think there is a need to change the SMBIOS.  Details below...

 

I just ran a quick test and find that music purchased in Apple Music plays without issues on my hack with SMBiOS MacMini8,1.  With my SMBIOS set to MacMini8,1 (booting Tahoe Beta 3 with Skip Board ID patch and fixing audio with VoodooHDA.kext 3.0.2) I only needed to

  • Open Apple Music in Tahoe Beta 3
  • sign-in to my Apple Account
  • Authorize my hack for Apple Music
  • Purchase a song
  • Play the song

I did not find it necessary to change SMBIOS from MacMini8,1 -> MacPro7,1.

 

Also, I'm using VoodooHDA.kext 3.0.2 and audio quality is outstanding.

  • Like 3
  • Thanks 1

Update beta 2 -> beta 3 with no issues.

OC 1.0.5 / MacPro7,1 / iGPU disabled in BIOS / RX 6600 XT / RestrictEvents + revpatch=sbvmm,pci / no WhateverGreen.

 

Things that work well:

  • Sleep and wake (nothing special on my part, they work fine as is).
  • Apple Music, DRM protected songs play with no issue (Sound Blaster Play! 3 by USB).
  • Intel AX210 (only wifi): itlwm.kext v2.3.0 + Heliport v2.0.0 alpha.
  • Ethernet I219V7.
  • Start-up and shutdown times (similar to Sequoia / Sonoma).

Things that partially work:

  • Xcode 26 beta 2 (issues compiling some projects).
┌┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┬┐
├┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┴┤
│ OS         │ macOS Tahoe 26.0 x86_64                  │ 
│ KERNEL     │ Darwin 25.0.0                            │ 
├────────────┼──────────────────────────────────────────┤
│ HOSTNAME   │ MACPRO                                   │ 
│ MACHINE    │ Mac Pro (2019)                           │ 
├────────────┼──────────────────────────────────────────┤
│ PROCESSOR  │ Intel(R) Core(TM) i9-9900K               │ 
│ CORES      │ 8 PHYSICAL CORES / 16 THREADS            │ 
│ CPU FREQ   │ 3.60 GHz                                 │ 
├────────────┼──────────────────────────────────────────┤
│ MEMORY     │ 9.04 GiB / 32.00 GiB [28%]               │ 
│ USAGE      │ ███████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │ 
├────────────┼──────────────────────────────────────────┤
│ VOLUME     │ 88.49 GiB / 465.54 GiB [19%]             │ 
├────────────┼──────────────────────────────────────────┤

Thanks to everyone in this thread, you're helping me successfully test Tahoe.

 

Edited by miliuco
Typo
  • Like 7

I installed the Rx590 without WEG and then updated to Beta 3 without any problems. Afterward, sound and USB Wi-Fi worked with OCLP mode. The system plays without any problems. Question: Why do you enable WEG, and can you access the recovery disk when you do? Because I can't access it when WEG is enabled.

  • Like 3

Without full graphics support (in my case, nVidia Kepler) in the iMac late 2013 (27 inches), it's not worth experimenting with it any further.

I'm watching the further development on my supported MBPro 2019 (16 inches) and the beta3 already works almost the same as the Sequoia 15.5,

apart from the look of the Tahoe, which I don't like, and I hope that the Liquid theme will be changed to make it more user-friendly.

Edited by AlfredoM
  • Like 1
1 hour ago, strangeron said:

Question: Why do you enable WEG, and can you access the recovery disk when you do? Because I can't access it when WEG is enabled.

 

My hack needs WEG for UHD630 framebuffer patching (I don't use headless iGPU) and my RX560x boots to blackscreen without WEG. I can access Recovery in Tahoe Beta 3 (and previous versions of macOS) with WEG.  So far, the only time I need to disable WEG dGPU (using boot-arg -wegnoegpu) is when I install / upgrade Tahoe.

Edited by deeveedee
  • Like 4
  • Thanks 1
1 hour ago, deeveedee said:

@jsl I'm away from my hack and can't view your config.plist, but this thread may help.

Thanks but following this thread and edit my config.plist it still not working for my Ryzen 1700X hackintosh !

 

 

 

 

config.plist

Edited by jsl
  • Like 1

Are you test OC with another macOS ? Show CPUID? If with Clover works, keep with this boot loader, is awesome use too !! I have 8-10 sec to boot easy!! OC Its awesome too, but if one works, use it :) 

  • Like 2
1 minute ago, Max.1974 said:

Are you test OC with another macOS ? Show CPUID? If with Clover works, keep with this boot loader, is awesome use too !! I have 8-10 sec to boot easy!! OC Its awesome too, but if one works, use it :) 

Thanks.

I just try to figure out the reason why it only happened to OpenCore bootloader and try to fix it as soon as possible.

My M5A FX-6300 hackintosh had the same issue which let me think it only happened to AMD CPU hackintoshs.

No such an issue in my Intel hackintoshs.

  • Like 3
On 7/9/2025 at 11:45 AM, fusion71au said:

Maybe @laobamac_yyds can comment on what exactly gets root patched into /S/L/E besides AppleHDA.kext with OCLP-Mod?  If I am not mistaken, there is more than just inserting AppleHDA, repairing kext permissions and rebuilding kext caches, creating and then blessing the snapshot?

 

Finally nailed it!!!

kmutil create --allow-missing-kdk --volume-root "$SnapShotMountPoint" --update-all --variant-suffix release --no-authentication --no-authorization

You can skip this arguement  if SIP is disabled: (from OCLP Doc)

--no-authentication --no-authorization
Edited by LockDown
  • Like 4
24 minutes ago, pico joe said:

Has anyone experienced this, the administrator account becomes the standart account afte update beta3?

 

 

2025-07-10 16.36.02.jpg

 

No, in my case it remained as it was.

You can try creating a new account as Admin (your name and password)
and then delete the other one.

  • Like 2

Hello everyone,

 

I’ve successfully installed macOS Tahoe Beta 3 on my AMD Beelink SER5. Everything is working smoothly except for Bluetooth, which isn't working.

I’ve tried several suggested methods, including adding bluetoothExternalDongleFailed: 00 and bluetoothInternalControllerInfo: 00000000 00000000 00000000 0000 to NVRAM, but none of them worked.

 

Any suggestions would be greatly appreciated. Thank you!

AMD SER5 macOS-Tahoe.png

  • Like 3
Guest
This topic is now closed to further replies.
×
×
  • Create New...