Jump to content
767 posts in this topic

Recommended Posts

*** Deleted ***

 

I thought you were replying to me - sorry about that.  AirportBrcmFixup.kext renames PXSX to ARPT.  The binary rename (in config.plist) should not be necessary if you are using AirportBrcmFixup.kext (and the binary rename did not help in my case).

 

@Max.1974 The "Base" in your binary rename is wrong.  The Base should not include ARPT (should be \_SB.PC00.RP05 if that is indeed the path for your Device ARPT).  Note that my binary rename includes COUNT=1 (to limit the number of binary changes to 1) (just to be safe).

Edited by deeveedee
  • Like 1
  • Thanks 1
18 minutes ago, deeveedee said:

Just in case you were wondering whether the OCLP Devs support hackintoshes 😂

 

929969421_Screenshot2023-07-28at4_55_52PM.png.acb3c04074c013c48cc099795d1b56e0.png

 

 

I "think" (completely blind) its my DSDT show me GRPT

 

So I guess its correctly ?

 

Its just for prevent used in the future

 

 

Captura de Tela 2023-07-28 às 18.11.46.png

Captura de Tela 2023-07-28 às 18.14.42.png

13 minutes ago, Max.1974 said:

 

I "think" (completely blind) its my DSDT show me GRPT

 

So I guess its correctly ?

 

Its just for prevent used in the future

 

 

Captura de Tela 2023-07-28 às 18.11.46.png

Captura de Tela 2023-07-28 às 18.14.42.png

Do you have the window os?. You can check ACPI path by going to Device Manager > Right Mouse to your wifi > Properties > Details > BIOS DEVICE NAME > you can see the acpi path of your wifi

  • Like 2
47 minutes ago, kinhhoang161 said:

Do you have the window os?. You can check ACPI path by going to Device Manager > Right Mouse to your wifi > Properties > Details > BIOS DEVICE NAME > you can see the acpi path of your wifi

 

Thanks a lot, im can't use Windows and this machine, but I will try. Its just for fun and learn edit compiled my SSDTs

 

 

I have Wi-Fi working with BCM 94352HMB. I'm not sure that this is all necessary, but here is what I did:

 

EDIT: I have not yet finished reviewing my solution, but early indications are that the key was replacing AirportBrcmFixup.kext.  I am using the attached kext and Wi-Fi is working perfectly with my BCM 94352HMB device.  This is the kext that is included with OCLP 0.6.9 07.28.23 nightly build.

 

EDIT2: Device spoofing is required for application of OCLP post-install wi-fi patches on my HackBookPro6,2 with BCM 94352HMB.  See here.  I am leaving this post for historical purposes, but my new post supersedes this post.

 

  • Replace AirportBrcmFixup.kext 2.1.7 in OC/Kexts with the AirportBrcmFixup.kext 2.1.7 in the OCLP-Generated EFI (they have the same version, but have different sizes) *** This is not necessary.  I am leaving this for historical purposes.  See my corrected conclusions here.  ****
    Spoiler

    1580259427_Screenshot2023-07-28at7_05_16PM.png.de98ffadf5791e6c99459f7c85887e18.png

     

  • config.plist should not have VMM kernel patches and should have revpatch=sbvmm (for RestrictEvents.kext 1.1.2) (this may not be necessary or may be specific to my SMBIOS MBP6,2 - not sure yet)
    (Reference the attached sample config.plist)
  • AMFI should be disabled with amfi=0x80 and kernel patch (reference the attached sample config.plist)
  • Implement ACPI patch (SSDT) to spoof device "pci14e4,4353" (not sure this is necessary - My SMBIOS is MBP6,2 and this is the actual device in a real MBP6,2) *** Deleted - Not necessary ***
  • Implement ACPI binary rename (config.plist) RP02.PXSX -> RP02.ARPT *** Deleted - Not necessary ***
  • Your EFI must include RestrictEvents.kext 1.1.2 for the revpatch=sbvmm property
  • Apply legacy wi-fi post-install patches with 0.6.9n 07.28.23 (use nightly build, not custom build.  No python mods necessary).  For some reason, the latest OCLP 0.6.9 nightly build was able to patch my hack.  Previous versions did not have any patches available.  I am not sure if this is a change in the OCLP build (I don't see any commits, so I don't think so) or because I spoofed Wi-Fi device.  Maybe the new AirportBrcmFixup.kext was necessary?  Maybe revpatch=sbvmm was necessary?

I am posting this with FireFox in Sonoma 14.0 Beta 4 on my hack over BCM94352 Wi-Fi 😀

AirportBrcmFixup.kext.zip

 

sample-oclp-config.plist.zip

Edited by deeveedee
  • Like 2
  • Thanks 2

To me work very fine with OCLP Patcher

 

But im not give up until wait a new solution only for Wi-FI

 

Thanks thanks thanks I will test* (edit) your Broadcom kext 

 

 

Captura de Tela 2023-07-28 às 22.00.22.png

Edited by Max.1974
  • Like 1

After revert OCLP and use your AirportBrcmFixup.kext above my iPhone appears !!!!

 

image.thumb.png.ce5a5226f69e9831ba6abd48a9d65141.png

 

Im thinking its close a little bit to get this works without OLCP Rooting. 

 

 

  • Confused 1
18 minutes ago, Max.1974 said:

Im thinking its close a little bit to get this works without OLCP Rooting. 

 

OCLP post-install patches install the Apple Wi-Fi framework for legacy Wi-Fi (the framework that was removed in Sonoma).  I will be very surprised if you have working legacy Wi-Fi without OCLP post-install patches.

  • Like 3
1 hour ago, deeveedee said:

 

OCLP post-install patches install the Apple Wi-Fi framework for legacy Wi-Fi (the framework that was removed in Sonoma).  I will be very surprised if you have working legacy Wi-Fi without OCLP post-install patches.

 

My dear brother, im sure that will be the way to works this wireless. Recognize everything. But im not install ACLP.

 

New and fresh install 

 

 

Captura de Tela 2023-07-28 às 20.05.24.png

4 hours ago, deeveedee said:

I have Wi-Fi working with BCM 94352HMB. I'm not sure that this is all necessary, but here is what I did:

 

EDIT: I have not yet finished reviewing my solution, but early indications are that the key was replacing AirportBrcmFixup.kext.  I am using the attached kext and Wi-Fi is working perfectly with my BCM 94352HMB device.  This is the kext that is included with OCLP 0.6.9 07.28.23 nightly build.

 

  • Replace AirportBrcmFixup.kext 2.1.7 in OC/Kexts with the AirportBrcmFixup.kext 2.1.7 in the OCLP-Generated EFI (they have the same version, but have different sizes)
      Reveal hidden contents

    1580259427_Screenshot2023-07-28at7_05_16PM.png.de98ffadf5791e6c99459f7c85887e18.png

     

  • config.plist should not have VMM kernel patches and should have revpatch=sbvmm (for RestrictEvents.kext 1.1.2)
  • AMFI should be disabled with amfi=0x80 and kernel patch
  • Implement ACPI patch (SSDT) to spoof device "pci14e4,4353" (not sure this is necessary - My SMBIOS is MBP6,2 and this is the actual device in a real MBP6,2) *** Deleted - Not necessary ***
  • Implement ACPI binary rename (config.plist) RP02.PXSX -> RP02.ARPT *** Deleted - Not necessary ***
  • Apply legacy wi-fi post-install patches with 0.6.9n 07.28.23 (use nightly build, not custom build.  No python mods necessary).  For some reason, the latest OCLP 0.6.9 nightly build was able to patch my hack.  Previous versions did not have any patches available.  I am not sure if this is a change in the OCLP build (I don't see any commits, so I don't think so) or because I spoofed Wi-Fi device.  Maybe the new AirportBrcmFixup.kext was necessary?  Maybe revpatch=sbvmm was necessary?

I am posting this with FireFox in Sonoma 14.0 Beta 4 on my Mac over BCM94352 Wi-Fi 😀

AirportBrcmFixup.kext.zip 18.37 kB · 2 downloads

Thanks for your help and this new kext which enable my BCM4352 working at Sonoma now !

Screenshot 2023-07-29 at 11.09.47 AM.png

Screenshot 2023-07-29 at 11.10.49 AM.png

  • Like 4
8 hours ago, deeveedee said:

I have Wi-Fi working with BCM 94352HMB. I'm not sure that this is all necessary, but here is what I did:

 

EDIT: I have not yet finished reviewing my solution, but early indications are that the key was replacing AirportBrcmFixup.kext.  I am using the attached kext and Wi-Fi is working perfectly with my BCM 94352HMB device.  This is the kext that is included with OCLP 0.6.9 07.28.23 nightly build.

 

  • Replace AirportBrcmFixup.kext 2.1.7 in OC/Kexts with the AirportBrcmFixup.kext 2.1.7 in the OCLP-Generated EFI (they have the same version, but have different sizes)
      Reveal hidden contents

    1580259427_Screenshot2023-07-28at7_05_16PM.png.de98ffadf5791e6c99459f7c85887e18.png

     

  • config.plist should not have VMM kernel patches and should have revpatch=sbvmm (for RestrictEvents.kext 1.1.2)
  • AMFI should be disabled with amfi=0x80 and kernel patch
  • Implement ACPI patch (SSDT) to spoof device "pci14e4,4353" (not sure this is necessary - My SMBIOS is MBP6,2 and this is the actual device in a real MBP6,2) *** Deleted - Not necessary ***
  • Implement ACPI binary rename (config.plist) RP02.PXSX -> RP02.ARPT *** Deleted - Not necessary ***
  • Apply legacy wi-fi post-install patches with 0.6.9n 07.28.23 (use nightly build, not custom build.  No python mods necessary).  For some reason, the latest OCLP 0.6.9 nightly build was able to patch my hack.  Previous versions did not have any patches available.  I am not sure if this is a change in the OCLP build (I don't see any commits, so I don't think so) or because I spoofed Wi-Fi device.  Maybe the new AirportBrcmFixup.kext was necessary?  Maybe revpatch=sbvmm was necessary?

I am posting this with FireFox in Sonoma 14.0 Beta 4 on my Mac over BCM94352 Wi-Fi 😀

AirportBrcmFixup.kext.zip 18.37 kB · 5 downloads

Greate work, thank you very much, but once we have AirportBrcmFixup.kext, do we still need IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext? can you show kext folder or config.plist please

  • Like 1

If you are experiencing the same WiFi problem as me, where the connection to the WiFi router is working but you cannot seem to connect to the internet, there may be a solution. I discovered that the App "little snitch" was still running and blocking my internet access. (Thoug I uninstalled it) To resolve this issue, I had to go to Settings -> Network -> VPN&Filters -> Filters&Proxies and delete "little snitch". After doing so, I was able to go online immediately.

  • Like 1
3 hours ago, kinhhoang161 said:

Greate work, thank you very much, but once we have AirportBrcmFixup.kext, do we still need IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext? can you show kext folder or config.plist please

 

See attached. Others have their own techniques, but for me, I find it easiest to generate an Open Core EFI with OCLP (use the option "Build and Install Open Core" and then I examine the resulting OCLP-Generated EFI.  That is how I discovered the change in AirportBrcmFixup.kext.

Spoiler

1566205525_ScreenShot2023-07-29at6_48_38AM.thumb.png.9cef7c27a9ab1fb1d1e74cb27424c821.png

 

Edited by deeveedee
  • Like 2
  • Thanks 1

@deeveedee thanks. but i dont understand why we need add revpatch=sbvmm. i thought  it just allowing OTA updates for unsupported models on macOS 11.3 or newerand if i use the installer in the usb to install do i need revpatch=sbvmm?

Edited by kinhhoang161
  • Like 1

@kinhhoang161 You are watching my work in progress.  I may have done more than I needed to.  I only just discovered the working solution.  It is very possible that I did more than necessary, so I'm sure my solution will be refined.  Even if revpatch=sbvmm (with RestrictEvents.kext) is not needed, it is my preferred approach over the VMM kernel patches that I need for my hack (SMBIOS MBP6,2).  Your approach may be different.

 

EDIT: Also see this.  With my MBP6,2, I need VMM kernel patches to perform a clean macOS install (not an upgrade).  There are still some things about this legacy hacking that I'm learning, so I won't be surprised if some of my steps are unnecessary or overly complicated.

Edited by deeveedee
  • Like 2
2 minutes ago, deeveedee said:

@kinhhoang161 You are watching my work in progress.  I may have done more than I needed to.  I only just discovered the working solution.  It is very possible that I did more than necessary, so I'm sure my solution will be refined.  Even if revpatch=sbvmm (with RestrictEvents.kext) is not needed, it is my preferred approach over the VMM kernel patches that I need for my hack (SMBIOS MBP6,2).  Your approach may be different.

now i understood, thanks for your work and the explanation

  • Like 2

EDIT: Leaving this post below for historical purposes, but the post below is incorrect.  See my revised conclusion here.

 

=========================================

 

It does appear that the key to working Sonoma Wi-Fi with the BCM 94352HMB was replacement of the Acidanthera AirportBrcmFixup.kext 2.1.7 with AirportBrcmFixup.kext 2.1.7 included with OCLP 0.6.9 (different kexts, same version).  See here.  I don't see any commits in the Acidanthera repo (yet).  I'd be curious to know the change if anyone knows.

 

EDIT: Maybe in the Dortania nightly builds?  I haven't checked yet. *** Nope - not yet.

Edited by deeveedee
3 minutes ago, MacWill said:

Z590 Vision G. SMBIOS 20.2. All the recipe made, when applying the OCLP root patch came the message "Unsupported Host OS".


What is missing?

 

Follow my steps here.  I saw the same error at some point during my attempts.  I think it may be that sbvmm is required (with RestrictEvents.kext 1.1.2) or the new AirportBrcmFixup.kext is needed.  I haven't tested further to determine the exact cause of the error, but my posted steps resolved this for me.

  • Like 2
  • Thanks 1
3 hours ago, deeveedee said:

 

See attached. Others have their own techniques, but for me, I find it easiest to generate an Open Core EFI with OCLP (use the option "Build and Install Open Core" and then I examine the resulting OCLP-Generated EFI.  That is how I discovered the change in AirportBrcmFixup.kext.

  Reveal hidden contents

1566205525_ScreenShot2023-07-29at6_48_38AM.thumb.png.9cef7c27a9ab1fb1d1e74cb27424c821.png

 

Thanks for sharing my friend!!

 

It's possible you share config steps on OCLP that you did? 

 

Very helpful 

 

 

 

Edited by Max.1974
3 hours ago, MacWill said:

Z590 Vision G. SMBIOS 20.2. All the recipe made, when applying the OCLP root patch came the message "Unsupported Host OS".


What is missing?

 

You need the 0.6.9 nightly build if you want to patch Sonoma.

  • Like 1
  • Thanks 1
6 hours ago, Max.1974 said:

It's possible you share config steps on OCLP that you did? 

 

I have attached a sample config.plist here.  Just follow the steps I outline in the post and reference the attached sample config.plist.  Please understand that the config.plist is based on my work with my own hack (SMBIOS MBP6,2) and is specific to what I needed to do for BCM 94352HMB Wi-Fi, so there may be elements of my solution that do not apply to your own solution.  If you generate an OC EFI with OCLP 0.6.9 (Use OCLP's "Build and Install Open Core" and then choose "View Build Log" (thank you @cankiulascmnfye for the tip to "View Build Log" instead of "Install"), you will find the required Kexts.  Use OCLP 0.6.9 Nightly build to apply post-install patches after you boot with your new EFI.

 

EDIT: Note that before you can "Build and Install Open Core," you may need to set an SMBIOS Model "Target" if OCLP doesn't automatically detect one (OCLP never detects the SMBIOS model on my hack).   To set an SMBIOS Model Target, choose Settings in OCLP GUI 

Spoiler

1815785210_Screenshot2023-07-29at3_21_21PM.png.54ac91b5f740c3bf59bd2f7d43edaac1.png

 

and then select your Target SMBIOS model from the pull down menu.

Spoiler

789254242_Screenshot2023-07-29at3_21_36PM.png.0304fe7a4d0aa70f7a53b1b6ccece3c3.png

 

Then click "Return" 

Spoiler

767625712_Screenshot2023-07-29at3_25_24PM.png.ed5abd75b61b3c30c31411f6e44aa4d9.png

 

and then "Build and Install Open Core."   When prompted, select "View Build Log" and follow the path to the OCLP-generated OC EFI.

 

*** OCLP is designed for Real Macs.  Never use OCLP to generate an OC EFI for your hackintosh.  I only use OCLP's generated OC EFI as a reference ***

Edited by deeveedee
  • Like 2
  • Thanks 2
×
×
  • Create New...