Jump to content
61 posts in this topic

Recommended Posts

2 hours ago, cankiulascmnfye said:

 

Oh, you were talking about Intel… I am using these on my Lenovo T490:

 

Bildschirmfoto2024-12-15um20_12_46.thumb.png.94cba266b50846194d659da6393506cc.png

Thanks for sharing. I believe I was not using the injector kext and instead the IntelFBPatcher, but it has been working without it before until I updated to macOS 15.2. I have a EDUP PCIE WiFi 6E Card AX210 Bluetooth 5.2 AX5400M 802.11ax Tri-Band 6G/5.8G/2.4GHz Heat Sink 6dBi Antenna PCI-E Wireless Network Card.

Edited by jlrycm
  • Like 1

Updated from 15.1.1 with no issues.

iMac19,1 + OC 1.0.3 + no RestrictEvents + OCLP root patch so full package update this time.

 

As @matxpa commented, scripts run slower in Terminal than in Sonoma or Ventura. Do you have the same behavior?

 

I don't want to be left behind so I'll put up a picture too 😀

 

Spoiler

Neofetch.thumb.png.f3a36af3c1eb0f081e01026d485f377d.png

 

And the script uploaded by @MaLd0n 😀

 

Spoiler

VDADecoder.png.81ca6125af445aab5020a2e66c35f537.png

 

Edited by miliuco
Add image
  • Like 6
5 hours ago, cankiulascmnfye said:

 

Oh, you were talking about Intel… I am using these on my Lenovo T490:

 

Bildschirmfoto2024-12-15um20_12_46.thumb.png.94cba266b50846194d659da6393506cc.png

@cankiulascmnfye the issue was solved by setting in nvram:

sudo NVRAM bluetoothExternalDongleFailed=%00
sudo pkill bluetoothd

 

If someone else got this issue after updating to macOS 15.2, you just need to check what's going on in nvram using 'NVRAM -p’ in terminal and if you have  bluetoothExternalDongleFailed=%01 up there, use the commands above.

  • Like 1
5 hours ago, jlrycm said:

Thanks for sharing. I believe I was not using the injector kext and instead the IntelFBPatcher, but it has been working without it before until I updated to macOS 15.2. I have a EDUP PCIE WiFi 6E Card AX210 Bluetooth 5.2 AX5400M 802.11ax Tri-Band 6G/5.8G/2.4GHz Heat Sink 6dBi Antenna PCI-E Wireless Network Card.

 

Well, if you look at my screenshot again, you will notice that MaxKernel is set to 20.9.9 for intelBluetoothInjector.kext, so this kext is not loaded past macOS Big Sur (it even says so in the comment)!

Edited by cankiulascmnfye
  • Thanks 1
35 minutes ago, cankiulascmnfye said:

 

Well, if you look at my screenshot again, you will notice that MaxKernel is set to 20.9.9 for intelBluetoothInjector.kext, so this kext is not loaded past macOS Big Sur (it even says so in the comment)!

@cankiulascmnfye yeah, I noticed that after I replied. Kept searching for possible solutions and found a quick fix in nvram that after applied solved my intel Bluetooth issue as reported in my last post.

  • Like 1
8 hours ago, jlrycm said:

@cankiulascmnfye yeah, I noticed that after I replied. Kept searching for possible solutions and found a quick fix in nvram that after applied solved my intel Bluetooth issue as reported in my last post.

 

On my case with Intel BT (that is part of AC8260 Wireless combo); it works under 15.2 just fine with only BlueToolFixup & IntelBluetoothFirmware

(+ those 2 NVRAM entries)

ScreenShot 2024-12-16 at 17.25.42.png

Edited by Badruzeus
  • Like 2

@cankiulascmnfye - The only Bluetooth issue I experienced with Intel Bluetooth after installing Sequoia 15.2 (upgrade from Sequoia 15.1.1) was that Bluetooth was On but could not connect to devices during the first boot following the upgrade.  A reboot fixed the issue.

Edited by deeveedee

I honestly think it’s time to hang my hat as far as the hackintosh scene goes. I don’t have the time or patience for this anymore and to make it even more difficult mines an AMD machine so more patching etc plus with having to use OCLP (wifi) and the onboard Ethernet (i211) not working correctly i think it’s time to say enough.
I don’t use it for a daily driver it was more just for fun and tinkering. I’m posting here because yes I have updated to this release but when I can’t even access my home server from my home machine with the web browser I choose I think it’s time to call it quits. The hack scene will be dead soon enough anyway.
It’s been fun. Good luck all.


Sent from my iPhone using Tapatalk

  • Like 1
  • Sad 2
17 hours ago, SavageAUS said:

I honestly think it’s time to hang my hat as far as the hackintosh scene goes.

 

Not going to try to talk you out of your very personal decision.  Just want to say that I don't switch to the next macOS on my "production" hack until my current version of macOS no longer  provides the XCode support that I need.  This typically means that I don't switch to the new macOS until the new macOS reaches .4 or .5 and by then, others have worked out the kinks.  For those who don't rely on XCode updates and won't be required to switch to Sequoia for XCode, you'll continue to receive Apple's Sonoma Security updates for much longer.

 

Sometimes the excitement around the new macOS can feel like pressure to switch.  Don't feel pressured.  My "production" macOS is still Sonoma.

  • Like 4

Hello guys and girls

Sorry for OFF-Topic:
I'm using latest OCLP on my old Ivybridge SMBIOS macPro6,1. On macOS 15.2: I installed Photoshop 2025 v26.1 with no problems. Unfortunately I can't for Indesign 2025. Both apps require AVX2 support.

Any ideas. Please.

  • Like 1

I have discovered a problem with CCLP 2.2.0 in Sequoia 15.2 Build 24C101.

I have to repeat the OCLP patch almost every day.

What's going on? It only affects the graphics on my iMac late 2013 (27 inch). WLAN remains intact.

Are there reports from other users about this?

It's not like that with 15.3 Beta1, the OCLP patch always remains intact (graphics + WLAN)

  • Like 1
3 hours ago, AlfredoM said:

I have discovered a problem with CCLP 2.2.0 in Sequoia 15.2 Build 24C101.

I have to repeat the OCLP patch almost every day.

What's going on? It only affects the graphics on my iMac late 2013 (27 inch). WLAN remains intact.

Are there reports from other users about this?

It's not like that with 15.3 Beta1, the OCLP patch always remains intact (graphics + WLAN)

My ASUS B85M-G hackintosh got different problem: it only affects BCM4352 WiFi while HD4600 remains intact.

  • Thanks 1

@cankiulascmnfye I used once BCM4352, and I remember that I fixed with Device Properties compatible with BCM4360 device.

 

<key>PciRoot(0x0)/Pci(0x1B,0x3)/Pci(0x0,0x0)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Internal@0,27,3/0,0</string>
                <key>compatible</key>
                <string>pci14e4,43a0</string>
                <key>device_type</key>
                <string>Airport Extreme</string>
                <key>model</key>
                <string>DW1560 (BCM4352) 802.11ac Wireless</string>
            </dict>	

 

Try use without BlueToolFixup and others. Today i use Broadcom BCM4360 Bluetooth native without any kexts.

 

 

 

 

  • Like 2
  • 2 weeks later...

04012025  
- Fix all USB port via port mapping 
- Fix WiFi and Bluetooth as notes below 

 

Kudos to youtuber - ikip and @miliuco - insanelymac for sharing how to fix the WiFi and Bluetooth.
 
Check out working EFI

 

Notes
How to get BCM94360CS2 to work with macOS Sequoia
0. Set SMBIOS in order for Compatibility with Sequoia eg MacBookPro16,4 for HP 850 G7
1. Mount ESP, select EFI folder, copy below kext to OC/kexts folder:
AMFIPass.kext
IOSkywalkFamily.kext
IO80211FamilyLegacy.kext
IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext
2. Open config.plist, run OC Configurator, click Add tab to add below:
BundlePath: IOSkywalkFamily.kext
BundlePath: IO80211FamilyLegacy.kext
IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext
MinKernel: 24.0.0
3. Click Block tab to block below:
Arch: Any
Identifier: com.apple.iokit.IOSkywalkFamily
Comment: Allow IOSkywalkFamily Downgrade
MinKernel: 24.0.0
Strategy: Exclude
Enabled: YES
4. Select Misc, click Security tab to disable Secure Boot Model:
Set dropdown list to Disabled
5. Select NVRAM, add boot Args:
Select last entry "7C....F82", add "-v keepsyms=1  -lilubetaall revpatch=sbvmm" to boot-args key
6. Disable SIP for root patching
Set csr-active-config to 03080000
7. Save config.plist
8. Reboot system and reset NVRAM
9. Patch System Volume
Run OCLP and select Post-install Root Patch
Click Start Root Patching
Click Yes to relaunch as root
10. Reboot system and reset NVRAM

 

Sequoia running on HP850G7.png

Edited by yahgoo
  • Like 2
14 minutes ago, eSaF said:

I may be wrong in your case but try booting without it and see.

If you are using the latest Lilu.kext release version and the release version of macOS, then you are of course right. In any case, there is no harm from this boot-arg.

Edited by verdazil
  • Like 1
  • Thanks 1
×
×
  • Create New...