Jump to content
30960 posts in this topic

Recommended Posts

6 hours ago, Hnanoto said:

Hi @Slice! 👋

I saw your post regarding the pt-BR translation warning.

I have just fixed it! I updated the 
pt-BR.po
 file adding the missing translations for Drivers, File Systems, and Themes. The translation coverage is now well above the required 74%, so the build warning should be gone and the language included again.

Here is the PR for the fix: https://github.com/CloverHackyColor/CloverBootloader/pull/801

Cheers! 🇧🇷

 

For those who like to compile in their own environment, I recommend using this compiler from my brother, @Max.1974https://github.com/maxpicelli/Clover-Compiler-Builder

 

Big Thanks my brother, God bless you!! New Commit updated!! 

 

IMAGE2026-02-17164330.jpg.b728beed2b3bbe2198904f80bcdf8f45.jpg

 

 

 

 

 

 

image.jpeg.18f8fa70e0e832278807ddd1f6a3d680.jpeg

 

CapturadeTela2026-02-17s17_23_38.thumb.png.3f116ef4e91fda2be0d3de93c6e41e87.png

Edited by Max.1974
  • Like 3

We rushed to produce revision 5168, delete it!

Now revision 5169 with a good menu (@MakAsrock) and with working ModernCpuQuirk (@Hnanoto).

15:499  0:000  ModernCPUQuirks: Auto-detection enabled, detecting CPU...
15:499  0:000  ModernCPUQuirks: Detected CPU Family=0x6 Model=0xBF Gen=14
15:499  0:000  ModernCPUQuirks: Applying recommended quirks (confidence=95%)
15:499  0:000  ModernCPUQuirks: Enabled DisableIoMapperMapping
15:499  0:000  ModernCPUQuirks: Enabled PowerTimeoutKernelPanic
15:499  0:000  ModernCPUQuirks: Enabled AppleCpuPmCfgLock

One note, my CPU model 0xBF is 13400 not 14. Yes, it is RaptorLake Refresh but 13th. It is Intel's confuse. 

  • Like 4
  • Thanks 3
24 minutes ago, Slice said:

We rushed to produce revision 5168, delete it!

Now revision 5169 with a good menu (@MakAsrock) and with working ModernCpuQuirk (@Hnanoto).

One note, my CPU model 0xBF is 13400 not 14. Yes, it is RaptorLake Refresh but 13th. It is Intel's confuse. 

Thank you, my friend, I'm so touched!
May Clover continue to get better and better! 🤝

Spoiler

 

 

  • Like 1
  • Thanks 1
22 hours ago, Slice said:

We rushed to produce revision 5168, delete it!

Now revision 5169 with a good menu (@MakAsrock) and with working ModernCpuQuirk (@Hnanoto).

15:499  0:000  ModernCPUQuirks: Auto-detection enabled, detecting CPU...
15:499  0:000  ModernCPUQuirks: Detected CPU Family=0x6 Model=0xBF Gen=14
15:499  0:000  ModernCPUQuirks: Applying recommended quirks (confidence=95%)
15:499  0:000  ModernCPUQuirks: Enabled DisableIoMapperMapping
15:499  0:000  ModernCPUQuirks: Enabled PowerTimeoutKernelPanic
15:499  0:000  ModernCPUQuirks: Enabled AppleCpuPmCfgLock

One note, my CPU model 0xBF is 13400 not 14. Yes, it is RaptorLake Refresh but 13th. It is Intel's confuse. 

 

Working fast and good my friend!! Congrats to All Devs Team !! 

 

CapturadeTela2026-02-22s12_03_26.thumb.png.42dcfa3361840bed6a7446edf4ff31e3.png

 

 

 

 

 

 

 

Edited by Max.1974
  • Like 2
  • Thanks 1

Clover 5169 (commit c4ce84e20)

 

Screenshot-2026-02-22-alle-09-08-38.png

 

49:230  0:000  ModernCPUQuirks: Auto-detection enabled, detecting CPU...
49:230  0:000  ModernCPUQuirks: Detected CPU Family=0x6 Model=0xB7 Gen=13
49:230  0:000  ModernCPUQuirks: Applying recommended quirks (confidence=95%)
49:230  0:000  ModernCPUQuirks: Enabled AppleXcpmCfgLock
49:230  0:000  ModernCPUQuirks: Enabled AppleCpuPmCfgLock

 

 

  • Like 2
2 hours ago, Slice said:

Hey @MakAsrock,

I got a report at applelife that IOSkywalk is not blocked by KextToBlock. Look please.

I will look too.

Hi @Slice! 👋Just checked. With the switch unchecked, the kernel panics.
By default, the switch is checked and there's no panic.
If users are using the old config.plist, it's not my fault.
The config-sample.plist is included into Installation package.
Even if these items are not in the config, they can be enabled from the Clover graphical interface. 😉
Cheers,
MakAsrock. 🤝

P.S.
If something had been wrong, I wouldn't have been able to load my RIG.

Edited by MakAsrock
P.S. If something had been wrong, I wouldn't have been able to load my RIG.
2 hours ago, MakAsrock said:

Hi @Slice! 👋Just checked. With the switch unchecked, the kernel panics.
By default, the switch is checked and there's no panic.
If users are using the old config.plist, it's not my fault.
The config-sample.plist is included into Installation package.
Even if these items are not in the config, they can be enabled from the Clover graphical interface. 😉
Cheers,
MakAsrock. 🤝

I tested. IOSkywalkFamily blocked in my case. As well I tested to block com.apple.iokit.IOSMBusFamily, and yes, it is blocked too. So the algorithm works.

But I can't inject old IOSkywalkFamily dunno why.

  • Like 2

you put the AmfiPass.kext and to the bootarg -amfipassbeta

 

1 hour ago, Slice said:

I tested. IOSkywalkFamily blocked in my case. As well I tested to block com.apple.iokit.IOSMBusFamily, and yes, it is blocked too. So the algorithm works.

But I can't inject old IOSkywalkFamily dunno why.

image.pngimage.png

  • Like 3
  • Thanks 1
10 hours ago, carlo_67 said:

you put the AmfiPass.kext and to the bootarg -amfipassbeta

 

image.pngimage.png

Because AMFIPass.kext corrupts the kext cache and breaks Clover's kext injection mechanism.

The same thing happens to me in Open Core.
Just move AMFIPass.kext to the EFI/CLOVER/kexts/Off/ folder
And instead of

-amfipassbeta

you need to use

amfi=0x80 ipc_control_port_options=0

 

Edited by MakAsrock
  • Like 2
29 minutes ago, LockDown said:

Never had issue with -amfipassbeta

 

8 minutes ago, MakAsrock said:

Before Tahoe macOS 26.x there was none, but after macOS 26.x and OCLP-mod 3.1.4 and 3.1.5 appeared. 😉

It's probably the way i root patch as i don't use OCLP-Mod package anymore.

I gathered all the kexts,frameworks & binaries needed for my setup from oclp-mod 3.1.0 and do it manually or sometimes with a script

4 minutes ago, MakAsrock said:

Before publishing minor fixes, test the locally compiled tweaked Clover.
It might have developed some hidden bugs.

CLOVERX64.efi.zip 731.1 kB · 0 downloads

Tweaked for?

  • Like 1
6 minutes ago, LockDown said:

 

It's probably the way i root patch as i don't use OCLP-Mod package anymore.

I gathered all the kexts,frameworks & binaries needed for my setup from oclp-mod 3.1.0 and do it manually or sometimes with a script

Tweaked for?

To prevent a potential null pointer dereference.
This doesn't usually happen, but it can happen.

Edited by MakAsrock
  • Like 2
4 hours ago, MakAsrock said:

Because AMFIPass.kext corrupts the kext cache and breaks Clover's kext injection mechanism.

The same thing happens to me in Open Core.
Just move AMFIPass.kext to the EFI/CLOVER/kexts/Off/ folder
And instead of

-amfipassbeta

you need to use

amfi=0x80 ipc_control_port_options=0

 

No differences. The kext and boot-args will work after the OS kernel started while I see kext blocking and injection is not working randomly  at the bootloader level, at the embedded opencore before kernel will started. 

It looks like memory corruption somewhere.

  • Like 3
52 minutes ago, Slice said:

No differences. The kext and boot-args will work after the OS kernel started while I see kext blocking and injection is not working randomly  at the bootloader level, at the embedded opencore before kernel will started. 

It looks like memory corruption somewhere.

amfi=0x80 is a boot argument that globally relaxes AMFI security checks, reducing system-wide code signing and library validation protections.

 

AMFIPass.kext instead bypasses only specific AMFI checks, making it a more controlled and cleaner solution on modern macOS.

 

In short:

amfi=0x80 = global security reduction

AMFIPass.kext = targeted bypass

The boot argument -amfipassbeta is used simply because AMFIPass.kext is not updated yet, and that’s it

  • Haha 1
1 hour ago, carlo_67 said:

amfi=0x80 is a boot argument that globally relaxes AMFI security checks, reducing system-wide code signing and library validation protections.

 

AMFIPass.kext instead bypasses only specific AMFI checks, making it a more controlled and cleaner solution on modern macOS.

 

In short:

amfi=0x80 = global security reduction

AMFIPass.kext = targeted bypass

The boot argument -amfipassbeta is used simply because AMFIPass.kext is not updated yet, and that’s it

This is true up to and including macOS Sequoia 15.
However, for macOS 26.x, AMFIPass.kext is not published, nor is OCLP.
Therefore, if you need working Wi-Fi, there's only two solutions:
1. My
 Unofficial OpenCore Legacy Patcher 3.1.6 - Tahoe Patch Set and amfi=0x80 ipc_control_port_options=0 boot argument.
2.  @laobamac_yyds OCLP-Mod 3.1.5 and amfi=0x80 ipc_control_port_options=0 boot argument.
For macOS 26.4b1. I have no solutions.

Edited by MakAsrock
  • Like 3
  • Sad 1

Emmm, bro, actually you can use -amfipassbeta boot-arg and AMFIPass.kext when patching with OCLP-Mod.Non-need disable AMFI.

26.4B1 can install the wireless network card patch separately for normal operation, and other patches need to wait for KDK.

 

Off-topic: What on earth is Apple doing? Since the XNU version number has been updated, why not follow the new KDK? Shouldn't KDK follow the new version of XNU to be released synchronously?🤬

Edited by laobamac_yyds
  • Like 2
  • Thanks 1
×
×
  • Create New...