[pre-release] macOS Tahoe

[ori]

Transfers are OK, only Apple does not have gen.5 SSDs written into the system.

 

[Ludox]

On 7/1/2025 at 5:28 PM, deeveedee said:

@Ludox If you're trying to manually install AppleHDA.kext, it's not going to be as easy as you think.  See here for a better understanding.  Best to use OCLP if you are going to install AppleHDA.

I did not write to install in manual I said a procedure.
Did you read that I wrote this?
I know what alternative guides can be adopted to install kext manual I did not arrive yesterday, I had already done it with Big sur to make wifi work on the notebook procedure in recovery with the terminal.

I try to keep the system as genuine as possible.

[asdfghjklzxcvbnm]

Dear everyone, 

 

I have managed to install macOS tahoe on my old thinkpad t460 skylake laptop,

 

However,

 

There is a serious issue with filevault not recognizing my password when I boot up.

 

Is there a way to fix it and keeping filevault active?

 

Is there a way to get AppleHDA without OCLP (like moddified kext in EFI?)

 

Thanks

Edited July 5, 2025 by asdfghjklzxcvbnm

[jlrycm]

1 hour ago, asdfghjklzxcvbnm said:

Dear everyone, 

 

I have managed to install macOS tahoe on my old thinkpad t460 skylake laptop,

 

However,

 

There is a serious issue with filevault not recognizing my password when I boot up.

 

Is there a way to fix it and keeping filevault active?

 

Is there a way to get AppleHDA without OCLP (like moddified kext in EFI?)

 

Thanks

 @asdfghjklzxcvbnm It’s recommended to fix some settings in the config.plist file to overcome this FileVault issue. If not possible to fix it, reinstall macOS Tahoe and load apfs_aligned.efi (a link to this new driver is available in the acidanthera bug tracker issue below) and disable APFS JumpStart setting in the config file as stated in this GitHub issue https://github.com/acidanthera/bugtracker/issues/2499 to avoid the “auto enabling FileVault and password not working” issue. Someone else also said here that to avoid it do a fresh install without entering your Apple ID nor migrating personal data.

Below is the guidance previously shared in this forum on how to deal with the FileVault issue. Since I don’t recall who shared the guidance before, credit to all contributors in this forum who are amazing at helping others.

 

FileVault is macOS's builtin drive encryption, and with OpenCore support for it has been drastically improved compared to the legacy Clover drivers.

To start, you'll need the following .efi drivers:

• OpenRuntime.efi
  • OpenUsbKbDxe.efi (opens new window)
    for DuetPkg users(systems without UEFI support)

Do not use VirtualSMC.efi with OpenCore, its already baked inside. You do however require VirtualSMC.kext still

Setting in your config.plist:

• Misc -> Boot
  • PollAppleHotKeys set to YES(While not needed can be helpful)
• Misc -> Security
  • AuthRestart set to YES(Enables Authenticated restart for FileVault 2 so password is not required on reboot. Can be considered a security risk so optional)
• NVRAM -> Add -> 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14
  • UIScale set to 02 for high resolution small displays
• UEFI -> Input
  • KeySupport set to YES(Only when using OpenCore's builtin input, users of OpenUsbKbDxe should avoid)
• UEFI -> Output
  • ProvideConsoleGop to YES
• UEFI -> ProtocolOverrides
  • FirmwareVolume set to YES
  • HashServices set to YES for Broadwell and older(this includes X99), this is needed for systems with broken SHA-1 hashing
• UEFI -> Quirks
  • RequestBootVarRouting set to YES
  • ExitBootServicesDelay set to 3000-5000 if you receive Still waiting for root device on Aptio IV firmwares(Broadwell and older)

With all this, you can proceed to enable FileVault like on a normal mac under System Preferences -> Security & Privacy -> FileVault

 

# Recover your install if you had FileVault enabled by decrypting it

 

After installing macOS 26, if you had FileVault enabled (be it on the current system being upgraded to macOS 26 or other macOS versions installed next to macOS 26), you might not be able to log in with your password.

 

To fix this, you need to decrypt it from recoveryOS:

0) **make sure you remember your passphrase, which is usually your account password**

1) Reboot to Recovery Mode

2) Open Terminal

3) Run `diskutil apfs list` and locate your `Data` disk (example: I have my system installed on `P50` patition, my data apfs partition should be `P50 - Data`) and remember its identifier (something like `diskXsY`, where X and Y are numbers). You should find `FileVault: Yes (Locked)`

4) run `diskutil apfs unlockVolume /dev/diskXsY` to unlock your encrypted APFS disk, you will be asked to enter your passphrase, you should get `Unlocked and mounted APFS Volume`. disk11s3

5) run `diskutil apfs listcryptousers /dev/diskXsY` to list user UUIDs for the encrypted volume. Note the **Local User** UUID

6) run `diskutil apfs decryptVolume /dev/diskXsY -user UUID_OF_LOCALUSER` and replace UUID_OF_LOCALUSER with the UUID you got from step 5 

7) it will prompt you to enter your passphrase agian, and will tell you that the process is running. To check the progress, run `diskutil apfs list` 

 

To watch the whole thing going, and gets updated live, run ```sh

while true; do diskutil apfs list | grep -B2 -A6 diskXsY; sleep 1; printf "\033"; done```

## Note if your system crashed in the middle of the decryption:

If you're lucky, the decryption would just be paused, reboot to Recovery Mode, and open Terminal:

1) run `diskutil apfs list` and check if your Decryption is `Paused`. 

2) if it is, unlock your volume again by running step 4 from above

3) run again `diskutil apfs list` and check if the decryption resumed

4) if not, open a new Terminal window, andr run `/usr/libexec/apfsd`, you should see the decryption progress again.

Edited July 5, 2025 by jlrycm

[asdfghjklzxcvbnm]

Thanks, 

 

I am currently decrypting my volume again in order to get mac os into working condition again and I will try the steps mentioned however in seoquia 15.5 filevault worked without any issue.

Edited July 5, 2025 by asdfghjklzxcvbnm

[gsxb]

3 hours ago, eSaF said:

Purely cosmetic my friend.

Just trying to make the Apple experience as authentic as possible.

 

I don't think it enhances the performance of the Hack in anyway

I just hate the Generic label and prefer this alternative.

  Hide contents

 

Hi there can you post the kext that fixes this, I’ve seen information regarding using ioexplorer to add the nvme to the properties section of opencore to change generic to apple 

Edited July 5, 2025 by gsxb

[fernando.c.neves]

If you getting poor Geekbench Results, do this in OpenCore Configurator...

Enable => AppleXcpmForceBoost > Kernel>Quirks

 

Before results => 5849

 

 

After => 7780

 

Now in Windows I´m getting => 7980

 

AMD Radeon RX 6600 8GB

 

Regards,

Fernando.

 

Ps: Those results are obtained in GeekBench 6 with ASUS Prime H510M-K R2.0 with an Intel core i5 11400 / XMP II => Dual Channel 3200Mhz DDR4 / AMD Radeon RX 6600 8GB

 

Reference in Geekbench 4 results

 

Edited July 5, 2025 by fernando.c.neves

[Anto65]

I have not used the kext

config.plist.zip

[gsxb]

8 minutes ago, eSaF said:

Hi, it is a dummy kext that you have to alter the kext Info.plist with data formulated from your machine.

My kext would be no good for your machine.

 

Dummy kext and tutorial here - https://github.com/HorizonUnix/GenericNVMeName.

Good luck.

I’m on it thanks looks similar to the post on oliaria 

[deeveedee]

1 hour ago, Ludox said:

I did not write to install in manual I said a procedure.
Did you read that I wrote this?
I know what alternative guides can be adopted to install kext manual I did not arrive yesterday, I had already done it with Big sur to make wifi work on the notebook procedure in recovery with the terminal.

I try to keep the system as genuine as possible.

It appears that I offended you.  Please forgive me for misunderstanding your question.

[chris1111]

For Realtek USB Wifi adapter All pages (Usage) is updated for macOS Tahoe 26

All Release is Update

Enjoy

[Alpha22]

25 minutes ago, gsxb said:

I’m on it thanks looks similar to the post on oliaria 

App Hackintool -PCIe search for ssd as example :

PciRoot(0x0)/Pci(0x17,0x0) compatible string pci8086,9c83

config.plist-DeviceProperties 

<key>your Device Patch/key>
            <dict>
                <key>compatible</key>
                <string>pci8086,9c83/string>
            </dict>

[asdfghjklzxcvbnm]

2 hours ago, jlrycm said:

 @asdfghjklzxcvbnm It’s recommended to fix some settings in the config.plist file to overcome this FileVault issue. If not possible to fix it, reinstall macOS Tahoe and load apfs_aligned.efi (a link to this new driver is available in the acidanthera bug tracker issue below) and disable APFS JumpStart setting in the config file as stated in this GitHub issue https://github.com/acidanthera/bugtracker/issues/2499 to avoid the “auto enabling FileVault and password not working” issue. Someone else also said here that to avoid it do a fresh install without entering your Apple ID nor migrating personal data.

Below is the guidance previously shared in this forum on how to deal with the FileVault issue. Since I don’t recall who shared the guidance before, credit to all contributors in this forum who are amazing at helping others.

 

FileVault is macOS's builtin drive encryption, and with OpenCore support for it has been drastically improved compared to the legacy Clover drivers.

To start, you'll need the following .efi drivers:

• OpenRuntime.efi
  • OpenUsbKbDxe.efi (opens new window)
    for DuetPkg users(systems without UEFI support)

Do not use VirtualSMC.efi with OpenCore, its already baked inside. You do however require VirtualSMC.kext still

Setting in your config.plist:

• Misc -> Boot
  • PollAppleHotKeys set to YES(While not needed can be helpful)
• Misc -> Security
  • AuthRestart set to YES(Enables Authenticated restart for FileVault 2 so password is not required on reboot. Can be considered a security risk so optional)
• NVRAM -> Add -> 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14
  • UIScale set to 02 for high resolution small displays
• UEFI -> Input
  • KeySupport set to YES(Only when using OpenCore's builtin input, users of OpenUsbKbDxe should avoid)
• UEFI -> Output
  • ProvideConsoleGop to YES
• UEFI -> ProtocolOverrides
  • FirmwareVolume set to YES
  • HashServices set to YES for Broadwell and older(this includes X99), this is needed for systems with broken SHA-1 hashing
• UEFI -> Quirks
  • RequestBootVarRouting set to YES
  • ExitBootServicesDelay set to 3000-5000 if you receive Still waiting for root device on Aptio IV firmwares(Broadwell and older)

With all this, you can proceed to enable FileVault like on a normal mac under System Preferences -> Security & Privacy -> FileVault

 

# Recover your install if you had FileVault enabled by decrypting it

 

After installing macOS 26, if you had FileVault enabled (be it on the current system being upgraded to macOS 26 or other macOS versions installed next to macOS 26), you might not be able to log in with your password.

 

To fix this, you need to decrypt it from recoveryOS:

0) **make sure you remember your passphrase, which is usually your account password**

1) Reboot to Recovery Mode

2) Open Terminal

3) Run `diskutil apfs list` and locate your `Data` disk (example: I have my system installed on `P50` patition, my data apfs partition should be `P50 - Data`) and remember its identifier (something like `diskXsY`, where X and Y are numbers). You should find `FileVault: Yes (Locked)`

4) run `diskutil apfs unlockVolume /dev/diskXsY` to unlock your encrypted APFS disk, you will be asked to enter your passphrase, you should get `Unlocked and mounted APFS Volume`. disk11s3

5) run `diskutil apfs listcryptousers /dev/diskXsY` to list user UUIDs for the encrypted volume. Note the **Local User** UUID

6) run `diskutil apfs decryptVolume /dev/diskXsY -user UUID_OF_LOCALUSER` and replace UUID_OF_LOCALUSER with the UUID you got from step 5 

7) it will prompt you to enter your passphrase agian, and will tell you that the process is running. To check the progress, run `diskutil apfs list` 

 

To watch the whole thing going, and gets updated live, run ```sh

while true; do diskutil apfs list | grep -B2 -A6 diskXsY; sleep 1; printf "\033"; done```

## Note if your system crashed in the middle of the decryption:

If you're lucky, the decryption would just be paused, reboot to Recovery Mode, and open Terminal:

1) run `diskutil apfs list` and check if your Decryption is `Paused`. 

2) if it is, unlock your volume again by running step 4 from above

3) run again `diskutil apfs list` and check if the decryption resumed

4) if not, open a new Terminal window, andr run `/usr/libexec/apfsd`, you should see the decryption progress again.

I have checked my config.plist and these values were checked except in the case of authrestart and hashservices (not needed for skylake)

 

So i will just disable filevault for now

2 hours ago, jlrycm said:

 @asdfghjklzxcvbnm It’s recommended to fix some settings in the config.plist file to overcome this FileVault issue. If not possible to fix it, reinstall macOS Tahoe and load apfs_aligned.efi (a link to this new driver is available in the acidanthera bug tracker issue below) and disable APFS JumpStart setting in the config file as stated in this GitHub issue https://github.com/acidanthera/bugtracker/issues/2499 to avoid the “auto enabling FileVault and password not working” issue. Someone else also said here that to avoid it do a fresh install without entering your Apple ID nor migrating personal data.

Below is the guidance previously shared in this forum on how to deal with the FileVault issue. Since I don’t recall who shared the guidance before, credit to all contributors in this forum who are amazing at helping others.

 

FileVault is macOS's builtin drive encryption, and with OpenCore support for it has been drastically improved compared to the legacy Clover drivers.

To start, you'll need the following .efi drivers:

• OpenRuntime.efi
  • OpenUsbKbDxe.efi (opens new window)
    for DuetPkg users(systems without UEFI support)

Do not use VirtualSMC.efi with OpenCore, its already baked inside. You do however require VirtualSMC.kext still

Setting in your config.plist:

• Misc -> Boot
  • PollAppleHotKeys set to YES(While not needed can be helpful)
• Misc -> Security
  • AuthRestart set to YES(Enables Authenticated restart for FileVault 2 so password is not required on reboot. Can be considered a security risk so optional)
• NVRAM -> Add -> 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14
  • UIScale set to 02 for high resolution small displays
• UEFI -> Input
  • KeySupport set to YES(Only when using OpenCore's builtin input, users of OpenUsbKbDxe should avoid)
• UEFI -> Output
  • ProvideConsoleGop to YES
• UEFI -> ProtocolOverrides
  • FirmwareVolume set to YES
  • HashServices set to YES for Broadwell and older(this includes X99), this is needed for systems with broken SHA-1 hashing
• UEFI -> Quirks
  • RequestBootVarRouting set to YES
  • ExitBootServicesDelay set to 3000-5000 if you receive Still waiting for root device on Aptio IV firmwares(Broadwell and older)

With all this, you can proceed to enable FileVault like on a normal mac under System Preferences -> Security & Privacy -> FileVault

 

# Recover your install if you had FileVault enabled by decrypting it

 

After installing macOS 26, if you had FileVault enabled (be it on the current system being upgraded to macOS 26 or other macOS versions installed next to macOS 26), you might not be able to log in with your password.

 

To fix this, you need to decrypt it from recoveryOS:

0) **make sure you remember your passphrase, which is usually your account password**

1) Reboot to Recovery Mode

2) Open Terminal

3) Run `diskutil apfs list` and locate your `Data` disk (example: I have my system installed on `P50` patition, my data apfs partition should be `P50 - Data`) and remember its identifier (something like `diskXsY`, where X and Y are numbers). You should find `FileVault: Yes (Locked)`

4) run `diskutil apfs unlockVolume /dev/diskXsY` to unlock your encrypted APFS disk, you will be asked to enter your passphrase, you should get `Unlocked and mounted APFS Volume`. disk11s3

5) run `diskutil apfs listcryptousers /dev/diskXsY` to list user UUIDs for the encrypted volume. Note the **Local User** UUID

6) run `diskutil apfs decryptVolume /dev/diskXsY -user UUID_OF_LOCALUSER` and replace UUID_OF_LOCALUSER with the UUID you got from step 5 

7) it will prompt you to enter your passphrase agian, and will tell you that the process is running. To check the progress, run `diskutil apfs list` 

 

To watch the whole thing going, and gets updated live, run ```sh

while true; do diskutil apfs list | grep -B2 -A6 diskXsY; sleep 1; printf "\033"; done```

## Note if your system crashed in the middle of the decryption:

If you're lucky, the decryption would just be paused, reboot to Recovery Mode, and open Terminal:

1) run `diskutil apfs list` and check if your Decryption is `Paused`. 

2) if it is, unlock your volume again by running step 4 from above

3) run again `diskutil apfs list` and check if the decryption resumed

4) if not, open a new Terminal window, andr run `/usr/libexec/apfsd`, you should see the decryption progress again.

I have checked my config.plist and these values were checked except in the case of authrestart and hashservices (not needed for skylake)

 

So i will just disable filevault for now

2 hours ago, jlrycm said:

 @asdfghjklzxcvbnm It’s recommended to fix some settings in the config.plist file to overcome this FileVault issue. If not possible to fix it, reinstall macOS Tahoe and load apfs_aligned.efi (a link to this new driver is available in the acidanthera bug tracker issue below) and disable APFS JumpStart setting in the config file as stated in this GitHub issue https://github.com/acidanthera/bugtracker/issues/2499 to avoid the “auto enabling FileVault and password not working” issue. Someone else also said here that to avoid it do a fresh install without entering your Apple ID nor migrating personal data.

Below is the guidance previously shared in this forum on how to deal with the FileVault issue. Since I don’t recall who shared the guidance before, credit to all contributors in this forum who are amazing at helping others.

 

FileVault is macOS's builtin drive encryption, and with OpenCore support for it has been drastically improved compared to the legacy Clover drivers.

To start, you'll need the following .efi drivers:

• OpenRuntime.efi
  • OpenUsbKbDxe.efi (opens new window)
    for DuetPkg users(systems without UEFI support)

Do not use VirtualSMC.efi with OpenCore, its already baked inside. You do however require VirtualSMC.kext still

Setting in your config.plist:

• Misc -> Boot
  • PollAppleHotKeys set to YES(While not needed can be helpful)
• Misc -> Security
  • AuthRestart set to YES(Enables Authenticated restart for FileVault 2 so password is not required on reboot. Can be considered a security risk so optional)
• NVRAM -> Add -> 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14
  • UIScale set to 02 for high resolution small displays
• UEFI -> Input
  • KeySupport set to YES(Only when using OpenCore's builtin input, users of OpenUsbKbDxe should avoid)
• UEFI -> Output
  • ProvideConsoleGop to YES
• UEFI -> ProtocolOverrides
  • FirmwareVolume set to YES
  • HashServices set to YES for Broadwell and older(this includes X99), this is needed for systems with broken SHA-1 hashing
• UEFI -> Quirks
  • RequestBootVarRouting set to YES
  • ExitBootServicesDelay set to 3000-5000 if you receive Still waiting for root device on Aptio IV firmwares(Broadwell and older)

With all this, you can proceed to enable FileVault like on a normal mac under System Preferences -> Security & Privacy -> FileVault

 

# Recover your install if you had FileVault enabled by decrypting it

 

After installing macOS 26, if you had FileVault enabled (be it on the current system being upgraded to macOS 26 or other macOS versions installed next to macOS 26), you might not be able to log in with your password.

 

To fix this, you need to decrypt it from recoveryOS:

0) **make sure you remember your passphrase, which is usually your account password**

1) Reboot to Recovery Mode

2) Open Terminal

3) Run `diskutil apfs list` and locate your `Data` disk (example: I have my system installed on `P50` patition, my data apfs partition should be `P50 - Data`) and remember its identifier (something like `diskXsY`, where X and Y are numbers). You should find `FileVault: Yes (Locked)`

4) run `diskutil apfs unlockVolume /dev/diskXsY` to unlock your encrypted APFS disk, you will be asked to enter your passphrase, you should get `Unlocked and mounted APFS Volume`. disk11s3

5) run `diskutil apfs listcryptousers /dev/diskXsY` to list user UUIDs for the encrypted volume. Note the **Local User** UUID

6) run `diskutil apfs decryptVolume /dev/diskXsY -user UUID_OF_LOCALUSER` and replace UUID_OF_LOCALUSER with the UUID you got from step 5 

7) it will prompt you to enter your passphrase agian, and will tell you that the process is running. To check the progress, run `diskutil apfs list` 

 

To watch the whole thing going, and gets updated live, run ```sh

while true; do diskutil apfs list | grep -B2 -A6 diskXsY; sleep 1; printf "\033"; done```

## Note if your system crashed in the middle of the decryption:

If you're lucky, the decryption would just be paused, reboot to Recovery Mode, and open Terminal:

1) run `diskutil apfs list` and check if your Decryption is `Paused`. 

2) if it is, unlock your volume again by running step 4 from above

3) run again `diskutil apfs list` and check if the decryption resumed

4) if not, open a new Terminal window, andr run `/usr/libexec/apfsd`, you should see the decryption progress again.

I have checked my config.plist and these values were checked except in the case of authrestart and hashservices (not needed for skylake)

 

So i will just disable filevault for now

[AlfredoM]

Now my question: 

Disable Metal Lib Download in Root Patch OCLP 3.0.0 nightly

 

How can I change this?
The root patch is supposed to restore my WiFi and audio.
I realize that Nvidia Keppler isn't working yet because the metallib.pkg is missing.
Do you have any idea how to prevent the metallib.pkg from downloading?

Thanks for the advice.

[Ludox]

1 hour ago, deeveedee said:

It appears that I offended you.  Please forgive me for misunderstanding your question.

Everything is fine, no problems..

[AlfredoM]

3 minutes ago, laobamac_yyds said:

No, no, no, you're completely wrong. That's just because the constant added Tahoe's Darwin version number, so the patch detection error occurred. Wi-Fi is not supported, please be aware of this.I'm not sure where you came to the conclusion that supports Wi Fi patches and graphics card patches, but it makes no sense, it's completely wrong, don't mislead others

Hey, what are you writing?
Who said anything about graphics support working?
I can see that you and Dortania are competitors.

It seems like the world would end if Dortania actually got WiFi working before you.

[strangeron]

24 minutes ago, laobamac_yyds said:

bro, I noticed that many of you like to use USB wireless network cards, but why is the speed of using USB wireless network cards here slow, even around 200Mbps? I am certain that this is not an issue with macOS, as it is also the case under Windows 10😭😭

We shouldn't be defined on this list. Turkey ranks 101st in fixed internet speed with 49.11 Mbps. However, it is still a bit slower in Tahoe than in Ventura and Sequoia.

[arya]

2 hours ago, AlfredoM said:

Now my question: 

Disable Metal Lib Download in Root Patch OCLP 3.0.0 nightly

 

How can I change this?
The root patch is supposed to restore my WiFi and audio.
I realize that Nvidia Keppler isn't working yet because the metallib.pkg is missing.
Do you have any idea how to prevent the metallib.pkg from downloading?

Thanks for the advice.

 

maybe you can check here ...

https://github.com/dortania/OpenCore-Legacy-Patcher/blob/macos-next/opencore_legacy_patcher/sys_patch/patchsets/shared_patches/metal_3802.py

 

and also 

 

https://github.com/dortania/OpenCore-Legacy-Patcher/blob/macos-next/opencore_legacy_patcher/sys_patch/patchsets/hardware/graphics/nvidia_kepler.py

 

OCLP detect your NVDIA Kepler and try to patch it but there are no new public pkg available yet 

[surenmunoo]

9 hours ago, ori said:

 

And can anything be done on the link speed ssd 5th gen?

 

 

My 9100 Pro shows the same with no link speed but I get 10500 write and 10000 read. Maybe Mac does not know how to deal with Gen 5

5 hours ago, chris1111 said:

For Realtek USB Wifi adapter All pages (Usage) is updated for macOS Tahoe 26

All Release is Update

Enjoy

Anyway to get the wifi icon visible when not using Dark mode?

Edited July 5, 2025 by surenmunoo

[Mirone]

17 hours ago, LockDown said:

Can you share please

That would be better to avoid instaling/including kexts that are not AppleHDA dependencies

  

Mandatory Requirements:

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

Disable SIP:

csrutil disable

csrutil authenticated-root disable

 

Disable SecureBootModel in your config.plist.

 

Install the KDK matching your system version.

 

If you experience issues booting the system, you must restore the snapshot by entering Recovery Mode and typing the following commands in the Terminal:

 

mount -uw /Volumes/Tahoe

bless --mount /Volumes/Tahoe --bootefi --last-sealed-snapshot

 

Note: Replace 'Tahoe' with the name of your volume.

There are many things that need improvement, and the application doesn't cover all errors. If people are interested in using it, I can improve it later.

Proceed at your own risk.

MyKextInstaller.zip

 

Edited July 5, 2025 by Mirone
A error was identified in the previous version.

[robi62]

20 minutes ago, strangeron said:

USB Wifi is very slow on Tahoe. However, it is not the same on Ventura and Sequoia. I had to remove OCLP-Mod and switch back to Ethernet. I may not have seen it. What is the situation for those using USB Wifi?

Hi i im ok wtih usb wifi these are my speeds

[robi62]

5 minutes ago, Mirone said:

  

Mandatory Requirements:

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

Disable SIP:

csrutil disable

csrutil authenticated-root disable

 

Disable SecureBootModel in your config.plist.

 

Install the KDK matching your system version.

 

If you experience issues booting the system, you must restore the snapshot by entering Recovery Mode and typing the following commands in the Terminal:

 

mount -uw /Volumes/Tahoe

bless --mount /Volumes/Tahoe --bootefi --last-sealed-snapshot

 

Note: Replace 'Tahoe' with the name of your volume.

There are many things that need improvement, and the application doesn't cover all errors. If people are interested in using it, I can improve it later.

Proceed at your own risk.

MyKextInstaller.zip 114.6 kB · 1 download

Hi you said you were going to create a readme for the app ???

Is this what you have written the readme??

Obrigado

[strangeron]

27 minutes ago, robi62 said:

Hi i im ok wtih usb wifi these are my speeds

I think we cannot even dream of such speed in this country. Let's not exaggerate, please. 😂😉🫣

 

[fernando.c.neves]

I´ve tried to score with Wi-Fi in Tahoe, but it do not pass 3Mbps Download and 3Mbps Upload...

 

Thats my score with Ethernet (Gigabit)...

 

 

My USB TL-WN725Nv3 Wi-Fi is a joke... But In a scenario that is impossible to use ethernet (Gigabit), It´s an option.

Edited July 5, 2025 by fernando.c.neves

[ivak4eto]

I'm glad that the heat dissipated! 🙃

I just wanted to share that I had the same issue with BCM Wifi looking like it's working on Sonoma and Sequoia, but it doesn't seem to find any networks. That's because the kexts for the Wifi are injected but the patch itself isn't working. In order to have wifi working you need both the kexts and the OCLP patch, like Lao said.