Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. kgp
    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?
  3. LockDown
    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 😜✌️
  4. Foysal Ahmed
    Foysal Ahmed joined the community
  5. Max.1974
    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
  6. Chlomaki
    Chlomaki changed their profile photo
  7. deeveedee
    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.
  8. Mirone
    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.
  9. Michael M Parker
    Michael M Parker joined the community
  10. MakAsrock
    I am using that on any macOS since Ventura. I couldn't imagine that someone wouldn't know about this trick. 😜
  11. miliuco
    @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.
  12. Today
  13. LockDown
    I am using that on a already installed OS but not during install. Never thought the issue i posted above will fix it
  14. deeveedee
    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.
  15. kaoskinkae
    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.
  16. One Day Movers
    One Day Movers joined the community
  17. deeveedee
    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
  18. Friends Group
    Friends Group joined the community
  19. LockDown
    Not only in Tahoe. Previous OSs now works too👍
  20. Company Registration Consultancy
    Company Registration Consultancy changed their profile photo
  21. Company Registration Consultancy
    Company Registration Consultancy joined the community
  22. Matgen84
    @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.
  23. open88vwin1
    open88vwin1 joined the community
  24. TAYOPH
    TAYOPH joined the community
  25. dangkybong789 com
    dangkybong789 com joined the community
  26. cityocalplumbing
    cityocalplumbing joined the community
  27. kaoskinkae
    Perfect in OLD2: AppleHDA.kext + Wifi Intel OCLP (OpenCore Legacy Patcher) 😄
  28. miliuco
    @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.
  29. MakAsrock
    Yes, it works for me.
  30. IPTV Providers
    IPTV Providers changed their profile photo
  31. kaoskinkae
    perfect NEW: AppleHDA + wifi
  32. LockDown
    adding to what @ThriftLoversaid, seems to work with tahoe 😮 Let me try again later... Have to go for now
  33. MakAsrock
    And this is my interpretation:
  34. 世界
    世界 changed their profile photo
  35. surenmunoo
  36. MakAsrock
    Don't ask how it was installed, I didn't do it. The computer does not belong to me: Motherboard: ASRock Z390 Phantom Gaming 6 iGPU: Intel HD Graphics 630 dGPU: Sapphire Pulse Radeon RX 580 8GB GDDR5 RAM: 32GB DDR4-3000 SSD: 128GB WD Green M.2 Audio: Realtek ALC1220 (Onboard) LAN: Intel I219V + Realtek Dragon RTL8125AG (Dual LAN) I/O: USB 3.0 / 3.1 / 3.1 Gen 2 Monitor: Full HD (via HDMI) macOS Big Sur - Everything is installed and works perfectly. macOS Tahoe - With -no_compat_check Bootloop macOS Tahoe - With SMBIS MacPro7,1 (with -no_compat_check and without it) Everything is installed and works perfectly. config.plist.zip
  37. ThriftLover
    To fresh install Big Sur or later using unsupported smbios, I think you need vmm spoof such as revpatch=sbvmm. For an update, you need to be running on Big Sur or later as vmm spoof won't work in Catalina or older. You need both board-id bypass and vmm spoof to install or update when using unsupported smbios.
  38. chuyennhathq5
    chuyennhathq5 changed their profile photo
  39. Nourish Pet Co
    Nourish Pet Co changed their profile photo
  40. LockDown
    Im referring installation in general, as we are not in Tahoe thread. Note: Pic not mine Last time i did a fresh install ( not nessesarily Tahoe). i only mentioned Tahoe to test the "Repaired feature that SMBIOS choosing automatically according to OS version." If i use unsupported smbios WITHOUT -no_compat_check or "Skip board ID Check", i get this (which is obvious) If i use unsupported smbios WITH -no_compat_check or "Skip board ID Check", i get this (disregard whatever OS version is in the pic) I have yet to try in Tahoe if the latter still accuring on a clean install
  41. luxinhaus

    VoodooHDA 3.x

    luxinhaus replied to Slice's topic in VoodooHDA

    Can you add a .xcodeproj for traditional please
  42. CloverLeaf
    I can provide some feedback using it for the last few days. The sound is great and I don't have issues after sleep like some of you, but I observed something interesting. After sleep the sound bar indicates the volume level before the computer goes to sleep. The moment I touch "Volume UP" it does not continue from let's say 25%, it goes all the way up to a 100%. To me this is something I would not even bother "fixing" as I don't know how exactly works on the backend but so far this is probably the best/easiest sound solution we had in a loooong time Thank you again, MaLdon!
  1. Load more activity
×
×
  • Create New...