Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. I use the same config during installation and subsequent use. 😉🫠
  3. After switching back to my BCM943602CDP, the Broadcom/OCLP setup works under macOS 26.6 beta 4 as expected. AppleHDA, Wi-Fi, native Bluetooth, AirDrop, AirPlay, Screen Mirroring, Continuity Camera, Personal Hotspot and sleep/wake appear to be fine. I have not observed any macOS 26.6 beta 4-specific regression with the BCM943602CDP/OCLP setup so far.
  4. @miliuco, many thanks for your immediate feedback! 🤗 First, one observation I already observed quite a while ago: when downloading About.This.Hack-4.3.9-glass.zip. the included app is also named About\ This\ Hack.app and no longer About\ This\ Hack-glass.app. Nevertheless, the included version is definitely the glass version. What worked for me after downloading the app: 1.) codesign --force --deep --sign - \ About\ This\ Hack.app/Contents/Frameworks/Sparkle.framework codesign --force --deep --sign - \ About\ This\ Hack.app 2.) Subsequently dropping the app into the Sentinel.app or Xattr-remove.app This solved my issue with the app under macOS 27 beta 3. The same approach also worked for Download Full Installer 4.5.3:
  5. Today
  6. @LockDown Yes, I have read it too, but also the contrary. I’ve tried both commands with no difference, Xattr-remove runs the whole command, I’ll test it again.
  7. That's exactly what I'm saying in the post, but I asked to see if it's possible somehow, but I don't think so.
  8. I read somewhere to avoid --deep when targeting Sparkle🤔
  9. Many thanks for the clarification and comments on my original post, @Mirone! You are right that the placement of the KDK note directly before the Bluetooth regression description may have unintentionally suggested a connection between the two. That was not my intention. The KDK information was only meant as general update context for the macOS 26.6 beta 4 OTA report, as I usually document the selected KDK after each sequential update. It was not intended to suggest any connection between the KDK selection or OCLP root patches and the Intel Bluetooth regression. The Bluetooth issue is unrelated to both and should be treated separately, as it has been handled so far anyway. The Bluetooth part was meant as a separate observation: after booting macOS 26.6 beta 4, my AX210 Bluetooth side fell back from the previously working THIRD_PARTY_DONGLE state to the broken BCM_4350C2 / Address NULL / State Off state. Your comment that you know why Bluetooth devices show up as BCM_4350C2 when Bluetooth stops working is actually very helpful. If you find the time, I would be very interested in understanding what exactly causes this fallback state, since it matches the old pre-fix failure mode I had observed before. Maybe you also know whether there is a way to recover from this state without replacing the card with another one?
  10. Well. Im used to installing an OS on a running OS. And since my running OS already has the svbmm flag, i never thought i would be needing it on a USB install method 😀 Do you consider that as a trick? Dont think so 😜✌️
  11. Hello my dear friends, @miliuco I used VS Code with Copilot to compile About This Hack with Xcode because I prefer the hidden serial number to open as a native option. I only had to grant permission in Sentinel and didn’t need to sign the application. It opened normally on Golden Gate Beta 3. Regards
  12. If you're using Open Core, just create GUID formatted USB with a custom EFI and boot from the USB for your test. If you're using CLOVER, you can add another config.plist and select at boot.
  13. You didn't explicitly say that the KDK affects Bluetooth, but that's clearly the impression your reply gave. You stated, "Apple has not yet released a Kernel Debug Kit for macOS 26.6 beta 4 (25G5057c). OCLP correctly selects Kernel Debug Kit 26.6 build 25G5052e, corresponding..." and then immediately went on to describe your Bluetooth issue. It's only natural that someone would connect the two. It may have been just a misunderstanding, but that's not really the point here. I haven't had the time to look through that GitHub link or the changes made to the IntelBT kext yet, although I do know why Bluetooth devices always show up as BCM_4350C2 when Bluetooth stops working. In any case, thanks for sharing it. Hopefully it'll be fixed soon and your Bluetooth will be working again.
  14. I am using that on any macOS since Ventura. I couldn't imagine that someone wouldn't know about this trick. 😜
  15. @kgp Indeed, xattr quarantine removal is not enough to run the app, but re-signing app and Sparkle does the job. Checking re-sing the app in Xattr-remove, I am able to run ATH as expected. This does the same as code signing Sparkle and app in your own machine: codesign --force --deep --sign - \ About\ This\ Hack-glass.app/Contents/Frameworks/Sparkle.framework codesign --force --deep --sign - \ About\ This\ Hack-glass.app I suppose that you must have at least one Apple account in Xcode settings or in the Keychain to this task to work.
  16. I am using that on a already installed OS but not during install. Never thought the issue i posted above will fix it
  17. Interesting. This might offer a clue about how to fix. Since I'm not observing the sleep/wake audio "pop" with VoodooHDA.kext 4.0, VoodooHDA must have solved this as well. I will be able to extract new logs later today. Thank you.
  18. I need to test it, but it will be after the holidays. I have three computers where it works perfectly. My question is: On all three computers, I have both Tahoe and Tahoe beta with the corresponding AppleHDA patches and both Intel and Broadcom Wi-Fi. My question is, is there any way to disable AppleALC and PCI or boot-arg injection so that it only loads on the system where I installed the kext? Or is my only option to create a bootable USB drive to test it on the hard drive of one of the three computers where I have the operating system installed? I'm not sure if this is the right question.
  19. I have needed to use revpatch=sbvmm in my config.plist since Sonoma. I thought everyone was using it for their hacks - no? EDIT: This helped me for enrolling unsupported hack in Tahoe Beta
  20. Not only in Tahoe. Previous OSs now works too👍
  21. @MakAsrock and All. I confirm too. Using long time ago, revpatch=sbvmm as Arguments is working fine on my Z390 (Coffee Lake-R) with MacPro7,1 SMBIOS.
  22. Perfect in OLD2: AppleHDA.kext + Wifi Intel OCLP (OpenCore Legacy Patcher) 😄
  23. @kgp I already mentioned to @fantomas that Golden Gate is clearly more demanding than Tahoe with Gatekeeper, but until now Xattr-remove (sometimes requiring you to select "Re-sign app") or Sentinel (signing the app or disabling Gatekeeper) solved this issue. I'm worried after reading you that Apple has further tightened this system because then... what will we do with all the free, open-source apps that aren't notarized? What a problem! However, I see that @surenmunoo has uploaded a screenshot of ATH with GG beta 3. I haven't downloaded beta 3 yet; I'll do it later and comment.
  24. Yes, it works for me.
  25. perfect NEW: AppleHDA + wifi
  26. adding to what @ThriftLoversaid, seems to work with tahoe 😮 Let me try again later... Have to go for now
  27. And this is my interpretation:
  1. Load more activity
×
×
  • Create New...