Jump to content
767 posts in this topic

Recommended Posts

21 hours ago, deeveedee said:

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)

  Hide contents

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

 

Hmm... Weird. I noticed that they are of a different size because the AirportBrcmFixup.kext from OCLP does not have AirPortBrcm4360_Injector.kext in its PlugIn folder. If you delete AirPortBrcm4360_Injector.kext the size is exactly the same. NO changes in info.plist or the contents of AirportBrcmFixup binary after comparing them in BBEdit.  AirportBrcmFixup.kext from iMac18,3 generated EFI also have a different size which is actually missing both AirPortBrcm4360_Injector.kext and AirPortBrcmNIC_Injector.kext but other than that I didn't notice any difference.

  • Like 2
On 7/29/2023 at 4:03 PM, ThriftLover said:

 

Hmm... Weird. I noticed that they are of a different size because the AirportBrcmFixup.kext from OCLP does not have AirPortBrcm4360_Injector.kext in its PlugIn folder. If you delete AirPortBrcm4360_Injector.kext the size is exactly the same. NO changes in info.plist or the contents of AirportBrcmFixup binary after comparing them in BBEdit.  AirportBrcmFixup.kext from iMac18,3 generated EFI also have a different size which is actually missing both AirPortBrcm4360_Injector.kext and AirPortBrcmNIC_Injector.kext but other than that I didn't notice any difference.

 

EDIT: @ThriftLover - you were right to think this was weird.  I was experimenting with device spoofing and different versions of AirportBrcmFixup.kext as I explain here and misinterpreted my test results.  It was the spoofing and NOT the AirportBrcmFixup.kext version that resulted in successful Wi-Fi patching in Sonoma.  See my mea culpa here.

 

Leaving my comments below for historical purposes, but my conclusions below are wrong.

 

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

 

Good find. 

EDIT: kextstat in Sonoma shows these Brcm kexts on my hack (same as in Ventura)

Spoiler

99884971_Screenshot2023-07-29at4_25_26PM.thumb.png.a1050d4350a79a3f4b6ae0cc7b23b9d5.png

 

EDIT2: The OC config.plist generated by OCLP 0.6.9 does inject the Brcm plugin kext.

Spoiler

770513369_Screenshot2023-07-29at4_37_14PM.png.3e169e89051a3becb758f7eb25c42553.png

 

If the kext change really is just removal of the plugins, why not just remove the plugin from the config.plist (or disable it) instead of modifying the kext?

 

EDIT3: @ThriftLover If I disable the AirPortBrcmNIC_Injector.kext kext injection in my config.plist, Wi-Fi no longer works in Sonoma.  The OCLP Devs are clearly working more magic than we know.  Could it be that somehow, OCLP 0.6.9 post-install patching is partially injecting the plugin kext (thus the removal of the plugins from AirportBrcmFixup.kext) and that OC's Kernel > Add processing is only part of the full kext injection?  I don't doubt that you are correct (that the difference between the two AirportBrcmFixup.kexts is the removal of the plugins).  Without knowing anything about this and I am making a complete guess, I would say that the plugins are removed from AirportBrcmFixup.kext, so that they don't override kext injection which includes a "partial kext injection" by the post-install patches.

Edited by deeveedee
  • Like 2

So, After many trys and many days and nights of Frustrations, I finally got WIFI working and Sonoma booting quickly. I read what @deeveedee posted about getting his wifi working and creating an EFI from OCLP and using that has a reference point to get this going. I did the same and voila, working. Now if someone can look at my config and see why I can't get my usb ports to show in Hackintool. I created all new SSDT's using SSDTTime in windows and just threw all of them in ACPI due to frustration or maybe that amfi.kext is causing the issue 

 

***EDIT *** USB ports now working after some SSDTD changes and a new USB mapping

image.thumb.png.d8ccc1c779dc0abc98a6b7f2019d161f.pngimage.thumb.png.091bc3c5d2b2c82a5c307d7c763c8521.png

config.plist.zip

Edited by surenmunoo
  • Like 4
On 7/26/2023 at 12:15 AM, cankiulascmnfye said:

@surenmunoo In the notes of the Sonoma OCLP Development bracnh it says, that you still have to apply root patches with OCLP 068 afterwards to make it work:

1984206987_Bildschirmfoto2023-07-26um09_14_07.png.fab3511f3c410e0df6ed374fbef1618b.png

 

Source: https://github.com/dortania/OpenCore-Legacy-Patcher/pull/1077#issuecomment-1646934494

 

I disabled AMFI and Firefox and WhatsApp for Mac both stopped working.  Anyone have a possible solution or workaround?

3 hours ago, AppleBreak said:

Please try AMFIPass.kext with -amfipassbeta boot flag and remove amfi=0x80

so i can disable amfi by using AMFIPass.kext + -amfipassbeta boot flag ( then i can remove amfi=0x80 right? )Is it the same function, just disable amfi, right? just a stupid question, thanks a lot

  • Like 1
4 hours ago, mnfesq said:

 

I disabled AMFI and Firefox and WhatsApp for Mac both stopped working.  Anyone have a possible solution or workaround?

 

Same to me. I will try this kext. 

3 hours ago, AppleBreak said:

Please try AMFIPass.kext with -amfipassbeta boot flag and remove amfi=0x80

 

 

Very nice this AMFIPass.kext 

 

Im run executable Patcher program from  @chris1111  page. 

 

https://gist.github.com/chris1111/781e9324bcd9657af294462c0b3f6582 

 

After that drag and drop OpenCore-Patcher on Terminal to finish and get AMFIPass-v1.3.1-RELEASE.zip on Desktop. 

 

Works Airdrop, Wireless, WhatsApp Desktop and Firefox again!!

 

Thanks a LOT to everybody

 

:superman:

 

 

2121057112_CapturadeTela2023-07-30as05_22_54.png

  • Like 2
20 hours ago, deeveedee said:

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.

The difference that I see between the 2 versions of AirportBrcMfixup.kext is the absence of the plugin: AirportbrcM4360_injector.kext

  • Like 2
17 hours ago, emax31 said:

The difference that I see between the 2 versions of AirportBrcMfixup.kext is the absence of the plugin: AirportbrcM4360_injector.kext

Yes - that is what @ThriftLover determined, too.  See my EDIT3 here for a theory.

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

 

@emax31 - you were right  - that is the only difference in the kexts.  I was experimenting with device spoofing and different versions of AirportBrcmFixup.kext as I explain here and misinterpreted my test results.  It was the spoofing and NOT the AirportBrcmFixup.kext version that resulted in successful Wi-Fi patching in Sonoma.  See my mea culpa here.

 

Edited by deeveedee
  • Like 1

@deeveedee sorry for bothering, can you help me a bit. i tried doing the same as you did, however i can't activate the root patch because it's greyed out ( cant press root patch - OCLP 0.6.9 nightly build ). without OCLP wifi can turn on but not find any wifi signal. (i have mapped the usb correctly, did your way in the most accurate way) am i doing something wrong, please help me. below is my EFI, thank you very much! ( my wifi is BCM943602CDP )


image.thumb.png.7325dbdf169ce5b9fa8ae21179f1ff7c.png

image.png.9ab0f57d59a3ffd3ffbec9f2bf8e8616.png

image.png.b8665d240ea31c38bff16796b963a2eb.png

image.png.255d172f2d50fd5f4df0ad718e832460.png 

EFI.zip

Edited by kinhhoang161
23 hours ago, AppleBreak said:

Please try AMFIPass.kext with -amfipassbeta boot flag and remove amfi=0x80

Thank you!  This works!  

 

Since I am multi-booting Big Sur, Monterey, Ventura and Sonoma on my HackBookPro6,2, I have modified my EFI as follows:

  • Remove AMFI and LV kernel patches from OC/config.plist
  • Renamed new OCLP AirportBrcmFixup.kext 2.1.7 to AirportBrcmFixup-Sonoma.kext (in OC/Kexts)
  • Re-added Acidanthera AirportBrcmFixup.kext 2.1.7 to OC/Kexts
  • Added boot-arg -amfipassbeta and removed amfi=0x80 (config.plist)
  • In OC/config.plist, added Kernel > Add > AirportBrcmFixup-Sonoma.kext with MinKernel 23.0.0 and Set MaxKernel = 22.99.99 for AirportBrcmFixup.kext

With these changes, I can boot Big Sur, Monterey, Ventura and Sonoma with a single EFI.  A new sample config.plist is attached.

 

@AppleBreak Where did you learn about boot-arg -amfipassbeta?  Lucky guess?

 

 

Edited by deeveedee
  • Like 1
  • Thanks 1

@kinhhoang161 I took a quick look at your EFI and noticed the following:

  • You use revpatch=sbvmm  where I add revpatch to NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102. I've never used the boot-arg format of this and I doubt this is the problem, but it is a difference
  • You don't have the LV and AMFI kernel patches (Kernel > Patch) (see my sample config.plist attached here)

 

If those suggestions don't work, then you will need to step through my thought process starting here to see what I missed in my final summary.  Unfortunately, you'll need to be patient with reading my guesses that didn't work.

Edited by deeveedee
1 hour ago, deeveedee said:

@kinhhoang161 I took a quick look at your EFI and noticed the following:

  • You use revpatch=sbvmm  where I add revpatch to NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102. I've never used the boot-arg format of this and I doubt this is the problem, but it is a difference
  • You don't have the LV and AMFI kernel patches (Kernel > Patch) (see my sample config.plist attached here)

 

If those suggestions don't work, they you will need to step through my thought process starting here to see what I missed in my final summary.  Unfortunately, you'll need to be patient with reading my guesses that didn't work.

Thank you for your help. i did it again like what you did, add 2 kernel patch for LV and amfi but same result. I don't understand why anymore. I will check it again.
- I realize I don't need SSDT-ARPT to spoof device id because my card already have a support id. try all but i cant start root patching...
image.thumb.png.e469f4c242afa55a30717c026789af91.png

here is my config.plist 

config.plist

Edited by kinhhoang161

EDIT: 1

i try edit sys_patch_detect.py > self.legacy_wifi = True and rebuild OCLP again and althought it show available patches for your system but i still cant start root patching because unsupported host OS 


image.png.733d7a8643665dddd4ad5b6c998ec175.png

@kinhhoang161 I admire your persistence! That is what it will take to solve. When I have time, I will re-install Sonoma from scratch and confirm all my steps. Hopefully you figure it out before waiting for me.

12 hours ago, AppleBreak said:

Please try AMFIPass.kext with -amfipassbeta boot flag and remove amfi=0x80

 

Thanks my friend, this is a GOLD information!!!

 

 

13 hours ago, kinhhoang161 said:

so i can disable amfi by using AMFIPass.kext + -amfipassbeta boot flag ( then i can remove amfi=0x80 right? )Is it the same function, just disable amfi, right? just a stupid question, thanks a lot

https://github.com/dortania/OpenCore-Legacy-Patcher/releases/tag/0.6.8

 

 

 

@Max.1974Merely passing the information.

 

5 hours ago, Max.1974 said:

Thanks my friend

 Directed to OCLP developers for their tremendous work.

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