macOS 10.15 Catalina on Unsupported Macs

[nobullone1964]

Hi

When I check for SIP I get this:

System Integrity Protection status: unknown (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
BaseSystem Verification: disabled
This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Is this normal?


When I check for updates, it says I am not connected to Internet and it does not show updates for safari.
Should I apply CatalinaOTAFix?

Also when I check for patch updates it does not prompt anything, not even installing night shift.

Any insight will be appreciated, I searched the thread first. But I am not tech savvy like lots here, so I am newbie. sorry.

Yeah, that is normal with the patcher. Updates are only gotten by re-installing over the existing installation AFAIK...

 

[AlexyFoxy]

Yeah, that is normal with the patcher. Updates are only gotten by re-installing over the existing installation AFAIK...

But Can I get to install night shift, it does not show me the option.

Also Can I enable SIP?

I can't use apps that need permission in security.

 

[nobullone1964]

But Can I get to install night shift, it does not show me the option.

Try contacting @dosdude1 about that. Do you have a monitor that is supported for that function? I've found that people reach for what they can't use and make an issue of it for no reason. Also. try searching for that topic within these forums. An answer may be there for you. Personally, using the patcher has limitations compared to using a vanilla installation with OpenCore and having the proper hardware (bluetooth, WiFi, etc.) to function directly after installation. What has been accomplished far exceeds the patched version at least for cMP. All props to @dosdude1 for all his effort, but all praises to the OpenCore community for what has saved the cMP again.

 

[AlexyFoxy]

Try contacting @dosdude1 about that. Do you have a monitor that is supported for that function? I've found that people reach for what they can't use and make an issue of it for no reason. Also. try searching for that topic within these forums. An answer may be there for you. Personally, using the patcher has limitations compared to using a vanilla installation with OpenCore and having the proper hardware (bluetooth, WiFi, etc.) to function directly after installation. What has been accomplished far exceeds the patched version at least for cMP. All props to @dosdude1 for all his effort, but all praises to the OpenCore community for what has saved the cMP again.

I agree with you. I don't need night shift, I only was asking cause I want to know how to get future updates if my updater does not work. Just wanted to make sure if it works or not. So how can I check for that?

Sorry, apparently I had a connection problem, though my network was fine. Now it connects to the patcher.


Can you enlighten me more regarding the Vanilla thing please? is it possible on unsupported Macs(I don't have metal compatible card)?

-sorry for me being a newbie.

 

[marvin_h]

Boot back to the USB installer and choose disk utility instead of post install patches. Does it correctly show your internal hard drive and mount the partitions or are they greyed out and not able to be mounted?

Thanks for your patience. Good call. I wasn't aware of that solution / situation.

Your post made me look at the disk utility. Sure enough, there was the disk....grayed out.

I had to use the disk utility to mount the disk. It wasn't mounted because it needed a password.

And that did the trick. I did that, then used the patch process.

I was able to install the patches. All seems good now: Wifi, more bluetooth, and being able to select HDMI output for audio all work....and that is great.

(My dumb AKG headphones won't pair, which is actually normal when trying to connect them to any recent MacOS. But that seems to be an AKG problem. And other folks report the same issue with many different Mac models and OS.)

Anyway, thanks again! Much appreciated.

I think I'll pause now before trying to update to Big Sur. This has been enough excitement for now.

 

[nobullone1964]

I agree with you. I don't need night shift, I only was asking cause I want to know how to get future updates if my updater does not work. Just wanted to make sure if it works or not. So how can I check for that?

Sorry, apparently I had a connection problem, though my network was fine. Now it connects to the patcher.


Can you enlighten me more regarding the Vanilla thing please? is it possible on unsupported Macs(I don't have metal compatible card)?

-sorry for me being a newbie.

I haven't seen your setup. Tell me about your machine.

 

[ralfbergs]

Weird WiFi Issue -- need help​

Hi guys.

I have a weird issue with the WiFi on my MacBookPro6,2 (MacBook Pro (15-inch, Mid 2010)), running Catalina 10.15.7 (19H2), thanks to @dosdude1 's "Catalina Patcher" (1.4.4).

My WiFi/Bluetooth functionality was defunct for about two years (if not more), due to the "ribbon cable" known issue. In the meantime I had been using the Mac just stationary, connected to my LAN via Ethernet. I finally fixed the problem by replacing the cable (part no. "821-0961-A"), and the WiFi/BT module is now (kind of) "working" again.

And here comes my problem:

I cannot join my home WiFi anymore. :-(

I have multiple access points in my house (because it's big), and the Mac used to be able to join all of them with no issues. In the meantime I have updated my access points multiple times, to the latest OpenWrt version.

All other devices (and I have many) continue to be able to access the WiFi, just this Mac can't. :-(

And it gets even more bizarre: For testing, I activated the WiFi hotspot on my Google Pixel 4 XL, and the Mac was able to join it and surf just fine.

In my view that gives proof that the hardware must be ok. The ribbon cable is a bus extension, not just some radio/antenna-related connection so that one could argue "Yeah, maybe still something wrong with the cable, so that it has bad reception." No, that can't be it. The antennas are connected to the small WiFi/BT module under a plastic cover, and the ribbon cable connects this daugherboard to the mainboard. So it must be a "bus extension/connection," meaning if the Mac can see the WiFi device and talk to it (and it obviously can, because I can join my Pixel's hotspot), then all must be fine hardware-wise.

Also, I can see many WiFi networks (including my own), with the network strengths I would expect (mine are "excellent"), so again that points to the hardware being ok.

I can only guess that it must be some weird software issue. Remember, I had not been using my WiFi for two years (maybe it was even longer, 2.5 or 3?). In the meantime I had updated the macOS version multiple times, including probably two major macOS updates (probably from High Sierra to Mojave to Catalina). Can it be that some internal database is corrupt?

What I did already:

• Try to manually rejoin the WiFi -- got an error message immediately saying "The WiFi network 'foobar' could not be joined."
• Deleted my WiFi network in macOS, recreated it from scratch. Then tried to rejoin it -- same error message as above.
• In "Network Preferences," deleted the "Wi-Fi" service, and recreated it. To no avail. :-(
• Reset the SMC.
• Tried a different user account.
• Deleted ControlPlane (as I thought it could be somehow interfering, especially as it was a very old version that I didn't update for years) -- to no avail.
• Booted from "Catalina Patcher" SD card: WiFi icon not even present! (But I could(!!!) log into my home WiFi on the "Startup Disk" selector screen that I get when I press "Option" during boot, before I select the SD card to be booted for the Catalina Patcher...)

I'm now pretty much out of ideas.

Can this be some incompatibility of my WiFi adapter with Catalina (and possibly even Mojave already, remember that I probably never ran the Mac under that OS!)?

Other Macs in my household (I have 4, all roughly 3 years apart) can still join the WiFi just fine (different macOS versions, one is as old that it still runs Sierra, IIRC, it's a 2007 MBP, which I can't update due to the WiFi module built in...), as all the other devices (I have probably around 40 devices which all work fine).

So, anyone got any idea what could be going on here? How can an issue like this be debugged? The "Wireless Diagnostics" didn't help at all. Is there no way to see low-level WiFi messages that could point me into the right direction?

Many thanks in advance for anybody who might be able to help.

Kind regards,

Ralf

 

[schtever]

Weird WiFi Issue -- need help​

Hi guys.

I have a weird issue with the WiFi on my MacBookPro6,2 (MacBook Pro (15-inch, Mid 2010)), running Catalina 10.15.7 (19H2), thanks to @dosdude1 's "Catalina Patcher" (1.4.4).

My WiFi/Bluetooth functionality was defunct for about two years (if not more), due to the "ribbon cable" known issue. In the meantime I had been using the Mac just stationary, connected to my LAN via Ethernet. I finally fixed the problem by replacing the cable (part no. "821-0961-A"), and the WiFi/BT module is now (kind of) "working" again.

And here comes my problem:

I cannot join my home WiFi anymore. :-(

I have multiple access points in my house (because it's big), and the Mac used to be able to join all of them with no issues. In the meantime I have updated my access points multiple times, to the latest OpenWrt version.

All other devices (and I have many) continue to be able to access the WiFi, just this Mac can't. :-(

And it gets even more bizarre: For testing, I activated the WiFi hotspot on my Google Pixel 4 XL, and the Mac was able to join it and surf just fine.

In my view that gives proof that the hardware must be ok. The ribbon cable is a bus extension, not just some radio/antenna-related connection so that one could argue "Yeah, maybe still something wrong with the cable, so that it has bad reception." No, that can't be it. The antennas are connected to the small WiFi/BT module under a plastic cover, and the ribbon cable connects this daugherboard to the mainboard. So it must be a "bus extension/connection," meaning if the Mac can see the WiFi device and talk to it (and it obviously can, because I can join my Pixel's hotspot), then all must be fine hardware-wise.

Also, I can see many WiFi networks (including my own), with the network strengths I would expect (mine are "excellent"), so again that points to the hardware being ok.

I can only guess that it must be some weird software issue. Remember, I had not been using my WiFi for two years (maybe it was even longer, 2.5 or 3?). In the meantime I had updated the macOS version multiple times, including probably two major macOS updates (probably from High Sierra to Mojave to Catalina). Can it be that some internal database is corrupt?

What I did already:

• Try to manually rejoin the WiFi -- got an error message immediately saying "The WiFi network 'foobar' could not be joined."
• Deleted my WiFi network in macOS, recreated it from scratch. Then tried to rejoin it -- same error message as above.
• In "Network Preferences," deleted the "Wi-Fi" service, and recreated it. To no avail. :-(
• Deleted ControlPlane (as I thought it could be somehow interfering, especially as it was a very old version that I didn't update for years) -- to no avail.

I'm now pretty much out of ideas.

Can this be some incompatibility of my WiFi adapter with Catalina (and possibly even Mojave already, remember that I probably never ran the Mac under that OS!)?

Other Macs in my household (I have 4, all roughly 3 years apart) can still join the WiFi just fine (different macOS versions, one is as old that it still runs Sierra, IIRC, it's a 2007 MBP, which I can't update due to the WiFi module built in...), as all the other devices (I have probably around 40 devices which all work fine).

So, anyone got any idea what could be going on here? How can an issue like this be debugged? The "Wireless Diagnostics" didn't help at all. Is there no way to see low-level WiFi messages that could point me into the right direction?

Many thanks in advance for anybody who might be able to help.

Kind regards,

Ralf

I had the same issue after upgrading to 10.15.7. I found that I could manually attach to the wifi network using

sudo networksetup -setairportnetwork en1 SSID PASSWORD

. This article helped reset the Wifi settings so it would join my home network automatically again.

 

[windrider42]

I finally updated my Catalina with the supplemental update 10.15.7 (19H15) , and I must say this is the best Catalina has worked for me.
I used the MD5 tool to download it, and dosdudes patcher to make the installer. Worked perfectly.

 

[ralfbergs]

I had the same issue after upgrading to 10.15.7. I found that I could manually attach to the wifi network using

sudo networksetup -setairportnetwork en1 SSID PASSWORD

.

Many thanks for your response.

Unfortunately that command doesn't help:

Error: 22  The operation couldn’t be completed. (com.apple.wifi.apple80211API.error error 22.)Failed to join network foobar.

This article helped reset the Wifi settings so it would join my home network automatically again.

I will try that now.

Many thanks again, really appreciate your help.

 

[ralfbergs]

This article helped reset the Wifi settings so it would join my home network automatically again.

Unfortunately that didn't help either... :-(

Still any ideas?

Thank you.

 

[ralfbergs]

Unfortunately that didn't help either... :-(

Still any ideas?

Thank you.

Another thing I tried (with surprising partially-successful result!):

Booted from "Catalina Patcher" SD card: WiFi icon not even present!

But now it comes: I could(!!!) log into my home WiFi on the "Startup Disk" selector screen that I get when I press "Option" during boot, before I select the SD card to be booted for the Catalina Patcher...

IMHO that's very strong evidence that the hardware must be ok, and that something in macOS must be hosed up.

Maybe I'll do a clean macOS Catalina install on an external HD and try that?

 

[AlexyFoxy]

I haven't seen your setup. Tell me about your machine.

MacBook Pro late 2011 13'

 

[AlexyFoxy]

I am writing this as a guide for those who gonna try Catalina on their unsupported machines.

I have a MacBook Pro 8.1 model and I did a fresh Catalina install.

The only thing that broke is the camera I tried SMC and PRAM reset and it didn't help. if anyone knows anything regarding this. please do help me!

1-I downloaded MDS (here). I downloaded the 19H15 Build. PS. it does not show percentage. Wait until it is complete.
Then I downloaded Dosdude1 patcher (here), mounted it and followed instructions to make a usb installing drive.
2-I booted from the usb and installed Catalina. Went through setup process and did not sign in iCloud.
UI Improvements
3-Once the machine worked I applied this patch to improve the UI (here).
Continuity (I did this and it worked, if it did not for you then I don't know why.)
4-Download and run catalinacontinuityfix.command.zip
5-Download the latest beta of continuity activation tool (Download latest beta).
5-Open terminal and type: sudo contitool.sh -f (you can grab contitool.sh from "Continuity-Activation-Tool-beta/Continuity\ Activation\ Tool.app/Contents/Resources/contitool.sh")
6-Continue through the installation until it tells you to restart, and restart.
7-Open terminal and type:
sudo mount -uw / ; killall Finder
8-Then type:
ioreg -l | awk -F\" '/board-id/ { print $4 }'
9-It will show your bluetooth card number. Copy it, paste it in the bellow codes and apply them in terminal:

sudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\your bluetooth card number/" /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360

sudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\your bluetooth card number/" /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcmNIC.kext/Contents/MacOS/AirPortBrcmNIC
10-Then apply these codes:
sudo chown -R 0:0 /S*/L*/E*/

sudo chmod -R 755 /S*/L*/E*/

sudo kextcache -i /
11-Untick then tick handoff option in preferences.
11-Restrart
12-log in your iCloud
13-Continuity should be working now.If not restart both your iPhone and Mac.
Security and privacy
Some apps will ask for permissions and you won't be able to give them some permissions. download (this) to solve it.
Run the script and it will ask you to choose the app that asks permission and then choose the permission it asked for.
VRAM
I used (this) already patched kext to increase the VRAM up to 1024mb.
Safari Extensions
When Using Safari 14, Extensions won't work and you won't be able to activate them.
I followed the instructions (here), and it worked.
Disclaimer
PS. I am a newbie I don't claim to have much of knowledge. I followed the instructions that were given by the kind members of this forum.
Thank you all for your guidance and work.

References
1 2 3 4 5 6 7

 

[DatAppleGuy99]

Hi, is there a way to increase the vram on a White MacBook 7,1 using the Nvidia 320M. And is there a way to do it on a MacBook Pro 8,1 with the Intel HD Graphics 3000?

 

[AlexyFoxy]

Hi, is there a way to increase the vram on a White MacBook 7,1 using the Nvidia 320M. And is there a way to do it on a MacBook Pro 8,1 with the Intel HD Graphics 3000?

Hello there. I am not sure for 7.1. But I have 8.1 and on Mojave and Catalina I used this to increase it.

 

[BigSmileMan]

Hi, is there a way to increase the vram on a White MacBook 7,1 using the Nvidia 320M. And is there a way to do it on a MacBook Pro 8,1 with the Intel HD Graphics 3000?

Try this. I'm not tested it but... on your choice How to increase vRAM for HD3000 graphics | MacRumors Forums

 

[Lucky736]

Another thing I tried (with surprising partial result!):

Booted from "Catalina Patcher" SD card: WiFi icon not even present!

But now it comes: I could(!!!) log into my home WiFi on the "Startup Disk" selector screen that I get when I press "Option" during boot, before I select the SD card to be booted for the Catalina Patcher...

IMHO that's very strong evidence that the hardware must be ok, and that something in macOS must be hosed up.

Maybe I'll do a clean macOS Catalina install on an external HD and try that?

It won't work. I had similar issues. Mine partially works now by having done the following, and what I mean by partially works is the network list is still pretty flaky and sometimes shows none other than my own when connected and I click the icon and other times shows many more. Goto your system preferences-> network-> wifi-> advanced-> uncheck auto join on them all. ALL. restart. join the one you want from the list and see if this behaves better.

 

[Rami Ashqar]

I know this question is repeated many times here, but this is really annoying!
Hi, I switched back before 6 months at least to Mojave due to the random crashes on Catalina, Now I came back to Catalina 10.15.7 and it still present, Please Is there is any fix for that? thanks.
Note: I am using a MBP 13' mid 2009, 2.53 GHz Intel Core 2 Duo, 8 GB 1333 MHz DDR3, NVIDIA GeForce 9400M 256 MB, Catalina 10.15.7 19H2, latest Dosdude Patcher.

 

[DerrickO]

I haven't seen your setup. Tell me about your machine.

Not to hijack the thread, but could you answer a few questions on how to get OpenCore up and running on a 2009 iMac 27" with the i7, 16GB RAM, and Samsung 860 EVO 1TB SSD?

I'm currently running DOSDUDE's patcher w/ 10.15.7, but would like to get OpenCore installed with 10.15.7.

I've reviewed the Dortania OpenCore for Legacy Macs and understand most of what I'm reading. Is this the best guide to use to get OpenCore up on my 2009 iMac?

 

[K two]

I know this question is repeated many times here, but this is really annoying!
Hi, I switched back before 6 months at least to Mojave due to the random crashes on Catalina, Now I came back to Catalina 10.15.7 and it still present, Please Is there is any fix for that? thanks.
Note: I am using a MBP 13' mid 2009, 2.53 GHz Intel Core 2 Duo, 8 GB 1333 MHz DDR3, NVIDIA GeForce 9400M 256 MB, Catalina 10.15.7 19H2, latest Dosdude Patcher.

Your MBP will never be stable no matter what OS is installed with the 1333 MHz. modules in there. S/B 1066 MHz. which are now cheap.

 

[K two]

I know this question is repeated many times here, but this is really annoying!
Hi, I switched back before 6 months at least to Mojave due to the random crashes on Catalina, Now I came back to Catalina 10.15.7 and it still present, Please Is there is any fix for that? thanks.
Note: I am using a MBP 13' mid 2009, 2.53 GHz Intel Core 2 Duo, 8 GB 1333 MHz DDR3, NVIDIA GeForce 9400M 256 MB, Catalina 10.15.7 19H2, latest Dosdude Patcher.

 

[K two]

I know this question is repeated many times here, but this is really annoying!
Hi, I switched back before 6 months at least to Mojave due to the random crashes on Catalina, Now I came back to Catalina 10.15.7 and it still present, Please Is there is any fix for that? thanks.
Note: I am using a MBP 13' mid 2009, 2.53 GHz Intel Core 2 Duo, 8 GB 1333 MHz DDR3, NVIDIA GeForce 9400M 256 MB, Catalina 10.15.7 19H2, latest Dosdude Patcher.

Your MBP will never be stable no matter what OS is installed with those 1333 MHz modules. S/B 1066 MHz DDR3. https://eshop.macsales.com/shop/memory/Apple_MacBook_MacBook_Pro/Upgrade/DDR3

Oops! Sorry for the post swarm. ?

 

[ralfbergs]

It won't work. I had similar issues. Mine partially works now by having done the following, and what I mean by partially works is the network list is still pretty flaky and sometimes shows none other than my own when connected and I click the icon and other times shows many more. Goto your system preferences-> network-> wifi-> advanced-> uncheck auto join on them all. ALL. restart. join the one you want from the list and see if this behaves better.

I tried this, and it didn't help. ;-(

Any more ideas? Or am I SOL here?

I even have a spare WiFi/BT daughterboard which I might try...

 

[Rami Ashqar]

Your MBP will never be stable no matter what OS is installed with those 1333 MHz modules. S/B 1066 MHz DDR3. https://eshop.macsales.com/shop/memory/Apple_MacBook_MacBook_Pro/Upgrade/DDR3

Oops! Sorry for the post swarm. ?

That's a bummer, but Thanks maybe I'll give these RAMs a try ☺️