Jump to content
767 posts in this topic

Recommended Posts

@Stefanalmare

Normal OCLP settings from Sonoma wifi branch work fine.

But @HyperX7 losses the wifi when trying AMFIPass.kext instead of amfi=0x80.

I remember to him the need of -amfipassbeta boot arg until this kext is adapted to Sonoma. 

 

Edited by miliuco
6 hours ago, Stefanalmare said:

 

I'm not sure why you use -amfipassbeta instead a normal OCLP configuration. What is the purpose?

 

Like any boot-arg wit beta in the name, it disables Kernel checks so it's loaded regardless of the currently used kernel.

  • Like 1

@cankiulascmnfye

Right but sometimes these beta boot args are required when the kexts are not adapted to the new macOS. E.g. on Sonoma: -amfipassbeta and AMFIPass.kext or -brcmfxbeta and AirportBrcmFixup.kext. 

Always better this approach than -lilubeta or -lilubetaall, of course.

On 8/12/2023 at 5:18 PM, Stefanalmare said:

 

I use this method on 2 laptops and 1 desktop and after 2 OS updates I think it is reliable.

I have applied this method successfully in my X299 & B85M-G hackintoshs, but always failed in Z97 & Z77 hackintoshs.

Don't know why it was not working in these two hackintoshs.

[Edit]

  • Only these 3 ASUS MB hackintoshs (Z77, Z97 and Z490-H) among my 20 hackintoshs in which DevicePath is too long "PciRoot(0x0)/Pci(xxx,xxx)/Pci(xxx,xxx)/Pci(xxx,xxx)/Pci(xxx,xxx)" and always failed to be spoofed at layer 5.
  • All the others in which DevicePath is correct "PciRoot(0x0)/Pci(xxx,xxx)/Pci(xxx,xxx)" and their IOName can be spoofed successfully at layer 3.
  • Anyone know how to fix this problem ?
Edited by jsl2000
13 hours ago, Leonardo Assunção said:

But, of course, they do want money from hackintoshers (as donations), don't they?

 

Well, whether or you donat is up to you. And: in order to develop patches and cover all the quirks of different chipsets they need access to all types of macs and Wintel Mainboards.

  • Like 1
11 hours ago, miliuco said:

@Stefanalmare

Normal OCLP settings from Sonoma wifi branch work fine.

But @HyperX7 losses the wifi when trying AMFIPass.kext instead of amfi=0x80.

I remember to him the need of -amfipassbeta boot arg until this kext is adapted to Sonoma. 

 

 

Genuine OCLP config is with AMFIPass.kext AND amfi=0x80. I use this configuration in 5 old MBP, 1 old iMac and all my legacy Hacks. OCLP never use -amfipassbeta. I asked because I had the feeling that I miss something.

 

6 hours ago, cankiulascmnfye said:

 

Like any boot-arg wit beta in the name, it disables Kernel checks so it's loaded regardless of the currently used kernel.

 

I know my friend. BTW: X3480 work like a charm on iMac11,3.

Edited by Stefanalmare
  • Like 1

ERROR compilation in hasweel indicated equipment below for the fenvi BCM4360 and using the compiled version 0.6.9 SIP 03080000 Added IOSkywalk.kext, IO80211FamilyLegacy.kext, and AirPortBrcmNIC.kext in this order (Kexts folder and config.plist).AMFIPass.kext + -amfipassbeta boot flag (so I can remove amfi=0x80

 

  Video 

https://we.tl/t-EnoOdTrOpi

 

WhatsApp Image 2023-08-14 at 13.53.43.jpeg

Edited by kaoskinkae
  • Sad 1
5 hours ago, Stefanalmare said:

 

Genuine OCLP config is with AMFIPass.kext AND amfi=0x80. I use this configuration in 5 old MBP, 1 old iMac and all my legacy Hacks. OCLP never use -amfipassbeta. I asked because I had the feeling that I miss something.

 

 

I know my friend. BTW: X3480 work like a charm on iMac11,3.

 

Well, at the time AMFiPass 1.3.1 was released (3 weeks ago) Sonoma beta 5 wasn't out yet. And since Sonoma beta 5 has a higher kernel count it will not load (unless lilubetall is used), which happened on my system.

 

And that's why that "genuine" OCLP config you are referiing to (which doesn't exist because it is everchanging) couldn't account for it!

  • Like 1

Im use Sonoma only on my real macs. Ventura is the best for my work.

 

Thinking buy a MacPro or MacStudio. Hack life is a pure adventure and patience. 😝

  • Haha 1

@kaoskinkae

Don’t compile OCLP. Get it already compiled from developers. Get the nightly sonoma build:

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

 Don’t use AMFIPass.kext neither -amfipassbeta for root patching, only amfi=0x80. 

  • Like 1
2 hours ago, miliuco said:

@kaoskinkae

Don’t compile OCLP. Get it already compiled from developers. Get the nightly sonoma build:

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

 Don’t use AMFIPass.kext neither -amfipassbeta for root patching, only amfi=0x80. 

 

Without AMFIPass.kext a lot of apps crash or don't start. After testing on multiple machines legacy and new, I use this:

1. AMFIPass.kext

2. amfi=0x80 ipc_control_port_options=0

3. 03080000

4. revpatch sbvmm (on legacy can be or not, other revpach and recblock may be present)

5. SecureBootModel Disabled

6. Force FileVault on Broken Seal

7. Block com.apple.iokit.IOSkywalkFamily

8. Modern WIFI:

- IOSkywalkFamily.kext

- IO80211FamilyLegacy.kext

- IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext

+ for non native în Ventura but old Mac wifi:

- AirportBrcmFixup.kext

- AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext

+ for non native on Ventura and non old Mac (ex: BCM94352)

- IOName pci14e4,43a3

Edited by Stefanalmare
  • Like 6
14 hours ago, eSaF said:

Is this now the general consensus?

Like I said already, with this OCLP business, I beginning to not knowing my @$$ from my elbow.

I must add my WiFi works pretty well with the kext and -amfipassbeta boot-arg or just with amfi=0x80.

Every time I see an opinion post with a change, it leaves me wondering which is right. :frantics:

 

  1. AMFIPass is a kext. It allows having AMFI enabled even if SIP is disabled which wouldn't be possible otherwise, because AMFI depends on SIP being fully enabled (csr-active-config: 00000000). AMFI needs to work in order to grant 3rd party apps access to privacy-relevant services/preripherals like external mics and cameras. But if you disabled SIP and/or AMFI in order to apply root patches, then the dialog to grant 3rd party apps access to mics or cameras does not pop-up, so you simply can't use them in 3rd party apps like Zoom or MS Teams for exmple. Otherwise you would have to have to add the apps manually to an .sql database in macOS. Complicated, tedious. If you come from an OS which didnt require disabling SIP or applying root patches where you granted permissions to these 3rd party apps and then upgrade macOS, these permissions will be carried over – otherwise (clean install) they won't. THAT's the main issue this kext addressess! Being able to apply (some) root patches when it's enabled is just a positive side-effect. -amfipassbeta is simply a boot-arg provided by AMFIPass to override the Kernel version check so that it loads regardless of the version of macOS. I required it on my Laptop after installing Sonoma beta 5 because Amfipass wouldn't load otherwise. When in doubt verify which kexts are loaded by running:
    kextstat | grep -v com.apple
  2. amfi=0x80 is a bitmask which basically disables AMFI in general. The flag with the value of 0x80 is called: AMFI_ALLOW_EVERYTHING:
    Bildschirmfoto2023-08-15um12_54_43.png.ac087546b35615c5152b0a372b1287f8.png
  3. My personal recommendation would be: Use AMFIPass. If you cannot apply certain root patches temporarily enable amfi=0x80 boot-arg, patch your system, reboot, disable the boot-arg . Done.

 

I have explained this at least 5 times now!

Edited by cankiulascmnfye
  • Like 5
  • Thanks 1

I know thats its maybe too early to ask about such thing, but...

Is there maybe a chance for more clever solution rather that entire OCLP business?

 

I mean for some injector without that entire root patching, amfi disabling, etc etc.

Edited by Hectorsky
  • Like 1
On 8/14/2023 at 10:48 PM, miliuco said:

@kaoskinkae

Don’t compile OCLP. Get it already compiled from developers. Get the nightly sonoma build:

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

 Don’t use AMFIPass.kext neither -amfipassbeta for root patching, only amfi=0x80. 

On another hard drive without a problem, the installation is completely satisfactory, see photo. The problem may be the available space on the other hard drive which is only 200g. I will use this without OCPL patching
image.thumb.jpeg.dd6837e438683cf8cbe10422f02de0e1.jpeg

  • Like 1
16 minutes ago, kaoskinkae said:

On another hard drive without a problem, the installation is completely satisfactory, see photo. The problem may be the available space on the other hard drive which is only 200g. I will use this without OCPL patching
 

 

Broadcom Wifi without OCLP Patching ! How do you ? Let me know.

14 minutes ago, Matgen84 said:

 

¡Broadcom Wifi sin parches OCLP! Cómo ? Hágamelo saber.

No, the problem I had was that I couldn't apply a patch on a 200g disk on a Hasweel computer, but on the SSD with the highest capacity, the patch was applied perfectly without a problem using this method.

 

 No use AMFIPass.kext ni -amfipassbeta para parchear la raíz, solo amfi=0x80. 

  • Like 1

Good morning. I have noticed that, if I change the SMBIOS model when I have OCLP root patch applied (and Sonoma wifi working), I lose wifi, as if root patch was not applied.

I have to revert root patch, reboot, apply root patch with the SMBIOS in use and, after reboot, wifi works again.
I don't know if it is the expected behavior since OCLP, when applying root patch, in one of the first lines of information it says "Applying root patch for <SMBIOS model>".
Has anyone else observed this behavior?

  • Like 2
30 minutes ago, miliuco said:

Good morning. I have noticed that, if I change the SMBIOS model when I have OCLP root patch applied (and Sonoma wifi working), I lose wifi, as if root patch was not applied.

I have to revert root patch, reboot, apply root patch with the SMBIOS in use and, after reboot, wifi works again.
I don't know if it is the expected behavior since OCLP, when applying root patch, in one of the first lines of information it says "Applying root patch for <SMBIOS model>".
Has anyone else observed this behavior?

 

This is normal behaviour. The root patch is linked to the Model. Similarly, after a macOS update, I was obliged to apply the root patch again.

  • Like 3
1 hour ago, Matgen84 said:

 

This is normal behaviour. The root patch is linked to the Model. Similarly, after a macOS update, I was obliged to apply the root patch again.

 

Thanks!!! I assumed that it was indeed so.

 

Edited by miliuco
  • Like 1
On 8/10/2023 at 2:01 PM, mnfesq said:

 

Thanks for the clarification.  This all started because I have apps that require SIP to be disabled.  Most of those apps will work with FF0F0000 but one app in particular requires SIP to be completely disabled, which is 6F020000.  This latter csr-active-config will not work with OCLP wireless patches, either to apply them or even post install.  However, FF0F0000 will work post install.  That means that I have to change my csr-active-config to 03080000 before applying the OCLP wireless patches after any update. Then I can revert to FF0F0000 to make my apps, such as XtraFinder, work.

 

@deeveedee Good job, my friend.  This seems to be working just fine.  I will report back after the update to beta 6 to confirm that OCLP will detect my wifi device for reapplication of the OCLP wireless patches.

 

@deeveedee I'm back to report that beta 6 installed perfectly and that OCLP detected my wireless device and its need to be repatched.  What surprised me is that I did not need to change my csr-active-config from FF0F0000 for this to happen or to run OCLP.   I couldn't be more pleased.  One small issue remains, however.  I cannot use the most current version of BlueToolFixup.kext.  In Ventura, it will not detect any bluetooth devices.  In Sonoma it does so this issue will likely be resolved by my eventual migration of my main partition from Ventura to Sonoma.  In Ventura, I am still using the version that was created as a fork from the main branch.  Those changes were supposedly incorporated into version 2.6.8 but that version never worked for me either.  Only the forked kext worked.  Thanks again for your help.

  • Like 1
On 8/23/2023 at 6:46 PM, mnfesq said:

 

@deeveedee "What surprised me is that I did not need to change my csr-active-config from FF0F0000 for this to happen or to run OCLP."

 

Well that's because you fully disabled SIP and enabled features usually only required by developers for debugging. You really shouldn't use this value because it's a securty risk. 03080000 is enough to apply root patches.

  • Like 1
×
×
  • Create New...