Jump to content
218 posts in this topic

Recommended Posts

You need install too: brew install ddcctl - is controller from Keyboard 

 

Fn + F1 or F2 (My Keyboard is Magic Keyboard from Apple) 

 

NativeDisplayBrightness.dmg

 

CapturadeTela2025-09-18s14_10_43.png.d88b86da56adb7ce1399d586c35e97fa.png

 

 

Edited by Max.1974
  • Like 4
7 minutes ago, mnfesq said:

Can anyone recommend a USB WiFi adapter that is Wireless AC, Notebook size and compatible with chris1111's Wireless-USB-OC-Big-Sur-Adapter?  Thanks.

TL-WN725N

I use it without any problems.

  • Like 1
  • Sad 1
7 minutes ago, strangeron said:

TL-WN725N

I use it without any problems.

 

Yes, thanks for the suggestion but it is wireless N and only supports 2.4 GHz wireless. What's the point of setting up USB WiFi if it can't get AC speeds? Does anyone have a suggestion that meets the specs of my original request? (Wireless AC, Notebook size, compatible with Chris1111's Wireless-USB-OC-Big-Sur-Adapter?)  Thanks.

Edited by mnfesq

@Zevgoli I'm sorry to see that you continue to have bluetooth problems.  I took a quick look at your OC config.plist and see the following:

  • You are enabling both Intel and Broadcom Bluetooth kexts.  Pick an architecture and enable only Intel or Broadcom bluetooth.
  • You do not have a corresponding NVRAM Delete for NVRAM > Add > bluetoothExternalDongleFailed and bluetoothInternalControllerInfo.  Add bluetoothExternalDongleFailed and bluetoothInternalControllerInfo to NVRAM > Delete > 7C436110-AB2A-4BBB-A880-FE41995C9F82.  Without these entries, you will have to manually reset NVRAM.

 

Other items I noticed in your config.plist

  • You are completely disabling SIP with csr-active-config <FF0F0000>.  This will cause problems with macOS updates.  It is most likely that you do not need to completely disable SIP for any of your use cases.
  • Since you do not have a corresponding NVRAM > Delete for csr-active-config, you will need to manually reset NVRAM when you change csr-active-config.  Add NVRAM > Delete > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > csr-active-config
  • You are using boot-arg amfi_get_out_of_my_way=1 which causes problems with macOS device permissions.  Better to use AMFIPass.kext (which is in your config.plist but is disabled) and remove the boot-arg.

 

EDIT: @Max.1974 Just noticed your earlier post which provides advice on the Intel and Broadcom bluetooth kexts.  Sorry about that :)

Edited by deeveedee
  • Like 3
29 minutes ago, mnfesq said:

 

Yes, thanks for the suggestion but it is wireless N and only supports 2.4 GHz wireless. What's the point of setting up USB WiFi if it can't get AC speeds? Does anyone have a suggestion that meets the specs of my original request? (Wireless AC, Notebook size, compatible with Chris1111's Wireless-USB-OC-Big-Sur-Adapter?)  Thanks.

I think is working in v3 

  • Confused 1
40 minutes ago, deeveedee said:

@Zevgoli I'm sorry to see that you continue to have bluetooth problems.  I took a quick look at your OC config.plist and see the following:

  • You are enabling both Intel and Broadcom Bluetooth kexts.  Pick an architecture and enable only Intel or Broadcom bluetooth.
  • You do not have a corresponding NVRAM Delete for NVRAM > Add > bluetoothExternalDongleFailed and bluetoothInternalControllerInfo.  Add bluetoothExternalDongleFailed and bluetoothInternalControllerInfo to NVRAM > Delete > 7C436110-AB2A-4BBB-A880-FE41995C9F82.  Without these entries, you will have to manually reset NVRAM.

 

Other items I noticed in your config.plist

  • You are completely disabling SIP with csr-active-config <FF0F0000>.  This will cause problems with macOS updates.  It is most likely that you do not need to completely disable SIP for any of your use cases.
  • Since you do not have a corresponding NVRAM > Delete for csr-active-config, you will need to manually reset NVRAM when you change csr-active-config.  Add NVRAM > Delete > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > csr-active-config
  • You are using boot-arg amfi_get_out_of_my_way=1 which causes problems with macOS device permissions.  Better to use AMFIPass.kext (which is in your config.plist but is disabled) and remove the boot-arg.

 

EDIT: @Max.1974 Just noticed your earlier post which provides advice on the Intel and Broadcom bluetooth kexts.  Sorry about that :)

 

Its ok my dear, don't worry we are try help its matter ;) 

51 minutes ago, Max.1974 said:

I think is working in v3 

 

What is working in v3? And what is v3? Sorry, I don't understand what you are saying.

1 hour ago, strangeron said:

Sorry. I missed it. You might want to check the list on the page.

 

The list doesn't give any specs for the compatible devices. I thought someone here might know so I don't have to look up every device on the list until I find one that meets my specs.  I'll keep my fingers crossed that someone has a similar device working on their laptop.

  • Like 1
2 hours ago, mnfesq said:

 

What is working in v3? And what is v3? Sorry, I don't understand what you are saying.

 

The list doesn't give any specs for the compatible devices. I thought someone here might know so I don't have to look up every device on the list until I find one that meets my specs.  I'll keep my fingers crossed that someone has a similar device working on their laptop.

 

Hi sorry late, TL-WN725N v3 is most compatible with chris1111 patcher ;) 

Firmware version 

 

Spoiler

image.thumb.png.c277e405be0eb5b6cfacef79eccdea92.png

image.png.161d20de2d468d3bde811de8a9e2b216.png

 

 

https://www.tp-link.com/br/support/download/tl-wn725n/

 

 

 

Edited by Max.1974
  • Like 1
4 hours ago, deeveedee said:

@mnfesq Any reason you can't patiently wait for OCLP while you continue to use Sequoia?

 

Not really, but as this is our last go round with macOS, the challenge of getting USB WiFi working while we wait for a Broadcom patch is appealing to me.  That said, I bought a USB WiFi adapter with what was supposedly a supported driver and spent about 6 hours unsuccessfully getting it to work. Hence, my moderate level of frustration. There is a very long list of wireless adapters that are supposed to work but most seem to be very old (wireless N) or have one or more antennas making it unsuitable for a laptop.  I was hoping someone had a tip to send my way but alas, not today.

7 hours ago, mnfesq said:

Does anyone have a suggestion that meets the specs of my original request? (Wireless AC, Notebook size, compatible with Chris1111's Wireless-USB-OC-Big-Sur-Adapter?)

I got one of these Asus AC53

image.png.295ae32c516f6e3b86d502209d3fee6d.png

 

rx/tx 

image.png.6d610edd3ea1271f3f3db6c76cd2a197.png

internet speedtest

image.png.6ca07e01b0cbf79e12bba32c0964d4ab.png

  • Like 2
  • Thanks 1
18 hours ago, eSaF said:

Wow!!!! That is a blast from the past.

I remember such a message as that from Apple Support way back when iMessage was first introduced and Hacks had a problem activating the Service because Security Tokens were not granted to non Mac machines.

 

Then some clever individual had the misguided idea to actually use Data from genuine Macs i.e S/N, MBL, ROM etc and enter these details into the config.plist of the Hack machine.

This ruse worked for a period of time until Apple realised that clones and Macs with the same credentials were using on the Servers and deemed it to be a security risk and blocked both real and cloned machine from the servers.

 

The way to get unblocked was to call Apple Support and hope they don't realise you are talking about a Hackintosh as well as your genuine Mac machine.

Some people even took to various websites trawling for genuine Mac data for Hacks. Back then it was a real mess (Now there is a bit of Hackintosh history for yah :lol:).

 

Uh oh I just realised I have step onto a potential O/T landmine.

Devs/Admin please delete if you deemed o/T.

So the solution for those who do not access iMessage and FaceTime with Apple ID would be to use smbios with sn that is not validated at check if I understand correctly. I am using a valid one and an invalid one but on both I do not access and the request to apple for support is not returned. It looks like an id block then

1 hour ago, eSaF said:

For fear of this topic being flagged as O/T, I will say this just once.

Never use valid data from a real Mac Machine i.e S/N, ROM, MBL etc, etc on a Hackintosh.

 

When checking your Hack data with Apple to validate, it should always come back as 'Unable to Verify Serial Number Please try again'.

This is the correct response you want. Never I repeat never use Serial Numbers from a genuine Mac on a Hack because sooner or later both machines will be blocked.

 

There use to be a consensus that it was ok to use the data on a Hack as long as you own the Mac and it is registered to your account but I still think that is also risky.

Potentially having two machines with the same data on Apple Servers will almost certainly be flagged as suspicious activity.

 

Hope this answer your query (I thought this old query was answered many many moons ago)

Cheers and good luck.

 

Thank you, I'll keep your advice in mind

 

5 hours ago, mnfesq said:

That said, I bought a USB WiFi adapter with what was supposedly a supported driver and spent about 6 hours unsuccessfully getting it to work.

 

If the USB WiFi adapter works on 15.x with Wireless-USB-Big-Sur-Adapter

then it should work on 26.0. with Wireless-USB-Big-Sur-Adapter and OCLP-Mod Tahoe USB patch.

 

 

  Hide contents

01.png.43f214ea53f67bc05cf7c08feb6fbca4.png

 

OCLP-Mod-07.png.cecdd5e2818e34bb4b3a69a2749ab75d.png

 


 

  • Like 2

Well I Bit The Bullet And Installed Tahoe To An External SSD

Migrated My Sequoia To It And Am Restoring It Over Sequoia

Wifi Works, Just Need Sound And Bluetooth

 

I Must Admit I Like Tahoe, Very Flash

 

Edit:

One annoying problem though

On restart it hangs at the DELL screen

Need to power it off and back on

 

Anybody have any ideas on what it could be

Would be greatly appreciated

Edited by STLVNUB
  • Like 1
12 hours ago, deeveedee said:

@Zevgoli I'm sorry to see that you continue to have bluetooth problems.  I took a quick look at your OC config.plist and see the following:

  • You are enabling both Intel and Broadcom Bluetooth kexts.  Pick an architecture and enable only Intel or Broadcom bluetooth.
  • You do not have a corresponding NVRAM Delete for NVRAM > Add > bluetoothExternalDongleFailed and bluetoothInternalControllerInfo.  Add bluetoothExternalDongleFailed and bluetoothInternalControllerInfo to NVRAM > Delete > 7C436110-AB2A-4BBB-A880-FE41995C9F82.  Without these entries, you will have to manually reset NVRAM.

 

Other items I noticed in your config.plist

  • You are completely disabling SIP with csr-active-config <FF0F0000>.  This will cause problems with macOS updates.  It is most likely that you do not need to completely disable SIP for any of your use cases.
  • Since you do not have a corresponding NVRAM > Delete for csr-active-config, you will need to manually reset NVRAM when you change csr-active-config.  Add NVRAM > Delete > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > csr-active-config
  • You are using boot-arg amfi_get_out_of_my_way=1 which causes problems with macOS device permissions.  Better to use AMFIPass.kext (which is in your config.plist but is disabled) and remove the boot-arg.

 

EDIT: @Max.1974 Just noticed your earlier post which provides advice on the Intel and Broadcom bluetooth kexts.  Sorry about that :)

 

This a fine summary indeed.  Thank you for taking the time to compile this.

 

In the end I found a solution by swapping out the adapter with another one I had spare.  I left everything the same and cleared NVRAM on reboot.  I have shutdown, rebooted left it off for several hours and tried again.  It works now without having to clear NVRAM.

Interestingly I put the now homeless ASUS adapter into my separate Windows PC and it works fine there.  Go figure.

 

Cheers, Howard

 

PS I have printed this summary off as a future reference in case of trouble down the road.

Edited by Zevgoli
add text
6 hours ago, eSaF said:

Hi Bro maybe you'll find the answer in the Boot Logs.

There is an instance during boot it hangs for a few seconds in verbose readout but I dare say you meant well past that point.

 

Hope you manage to pin down what is causing the hangup forcing a reboot.

Good luck.

Thanks, restarting takes 2 presses on the power button

I shutdown now, only one press of the power

It’s Got a weird bios, because it actually has as one of the

Boot items as Mac OSX, maybe i try booting Snow Leopard DVD ;)

IMG_1503.thumb.jpeg.ad87ab5c04f841d3d1dd79d369946736.jpeg

 

Edited by STLVNUB
Add picture
  • Like 1
20 minutes ago, Baio77 said:

Tahoe release broke the USB port limit patch on my NUC. Am I the only one having this problem?

 

 

 

Everything is OK on Sequoia

 

Port limit patch is dangerous and not recommended. Forget it and use Usb Map by some of available kexts.

  • Like 3
  • Thanks 1
×
×
  • Create New...