crwdns2933423:0crwdne2933423:0

Potential Work-Arounds Guide #5

  1. Potential Work-Arounds Guide #5, Introduction: crwdns2935265:01crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • Time to figure out what's wrong with your Mac, and how we're going to fix it.

    • I am going to try my best to include every single fix possible in this guide. If you have some issue that is not included in this guide, please drop a comment and I will continue to add to this guide in the future.

  2. Potential Work-Arounds Guide #5, Issue #1 - System Integrity Protection: crwdns2935265:02crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • SIP (along with the graphics) is one of the main issues your Mac will encounter. With SIP enabled, you cannot run any root patches. Yet, with it disabled, you cannot give apps permission.

    • For example, let's say you download Shazam from the Mac App Store. Shazam needs the microphone to work. When you open Shazam on a native Mac, a warning will appear asking if you will allow Shazam to access the microphone. Yet, when SIP is disabled, this warning never appears, and therefore you cannot access the microphone.

    • There are two work-arounds for this issue:

    • First, launch Shazam (or any other application that needs access to camera, microphone, photos, etc.) with Terminal.

    • Second, allow access to microphone with root patching disabled only temporarily.

    • Let's start with launching an application using terminal...

  3. Potential Work-Arounds Guide #5, Method #1 - Using Terminal: crwdns2935265:03crwdnd2935265:01crwdnd2935265:03crwdne2935265:0 Potential Work-Arounds Guide #5, Method #1 - Using Terminal: crwdns2935265:03crwdnd2935265:02crwdnd2935265:03crwdne2935265:0 Potential Work-Arounds Guide #5, Method #1 - Using Terminal: crwdns2935265:03crwdnd2935265:03crwdnd2935265:03crwdne2935265:0
    • If you try to launch Shazam, you'll probably get a notification like this, yet no way to fix it in System Preferences.

    • So, open your applications folder and find Shazam (or any app that is giving you issues).

    • Right-Click the app and choose "Show Package Contents"

    • Go to Contents > MacOS > Shazam

  4. Potential Work-Arounds Guide #5: crwdns2935265:04crwdnd2935265:01crwdnd2935265:03crwdne2935265:0 Potential Work-Arounds Guide #5: crwdns2935265:04crwdnd2935265:02crwdnd2935265:03crwdne2935265:0 Potential Work-Arounds Guide #5: crwdns2935265:04crwdnd2935265:03crwdnd2935265:03crwdne2935265:0
    • Search for Terminal in Spotlight.

    • Open Terminal and drag the Shazam file into the Terminal window as seen in the picture.

    • Press the Return key.

    • This time when you try to access the microphone, Terminal will ask for permission.

    • This is because apps built into macOS (not apps downloaded afterwards like in the App Store) don't need SIP to ask for permission to access. So, Terminal can gain permission while Shazam cannot.

    • Unfortunately with this method, you face two main issues. One, this is not a permanent fix. You will have to do this every time you open the application. So, if you use the application a lot, opening it through Terminal may get old. The other issue is that you cannot close Terminal while the app is running. That would quit the app.

  5. Potential Work-Arounds Guide #5, Method #2 - Reverting Root Patches: crwdns2935265:05crwdnd2935265:01crwdnd2935265:03crwdne2935265:0 Potential Work-Arounds Guide #5, Method #2 - Reverting Root Patches: crwdns2935265:05crwdnd2935265:02crwdnd2935265:03crwdne2935265:0 Potential Work-Arounds Guide #5, Method #2 - Reverting Root Patches: crwdns2935265:05crwdnd2935265:03crwdnd2935265:03crwdne2935265:0
    • The second method will take a while, but it allows for a much more pleasant experience while using apps.

    • Open up the OpenCore application and revert root patching.

    • Before you reboot the Mac, however, go back to the main menu and choose "Settings."

  6. Potential Work-Arounds Guide #5: crwdns2935265:06crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • Head over to "Security" and uncheck everything under "System Integrity Protection."

  7. Potential Work-Arounds Guide #5: crwdns2935265:07crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • Go back to the main menu and choose "Build and Install OpenCore."

    • Once completed, you can then reboot your Mac.

    • WARNING HERE! Make sure you are 100% positive that you have reverted Root Patching before rebooting. The Mac WILL NOT BOOT if patches have not been reverted, and therefore you will have to fix the issue in Safe Mode. But may I warn you now, you may not be able to install OpenCore while booted in Safe Mode, you would need another Mac.

  8. Potential Work-Arounds Guide #5: crwdns2935265:08crwdnd2935265:01crwdnd2935265:03crwdne2935265:0 Potential Work-Arounds Guide #5: crwdns2935265:08crwdnd2935265:02crwdnd2935265:03crwdne2935265:0 Potential Work-Arounds Guide #5: crwdns2935265:08crwdnd2935265:03crwdnd2935265:03crwdne2935265:0
    • Your Mac will act much, much worse upon rebooting, because no patches are installed.

    • But, once booted, open every application that you downloaded and get all access possible.

    • Some applications may not work at all without Root Patching, for example image editors that need metal graphics to run. Without Root Patching, you cannot open applications like these and get access to the camera or whatever it needs access to.

  9. Potential Work-Arounds Guide #5: crwdns2935265:09crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • Once you have opened every application and requested all access, head back into OpenCore.

    • Build OpenCore again, but with SIP disabled (more information on Guide #3).

    • Reboot your Mac.

  10. Potential Work-Arounds Guide #5: crwdns2935265:010crwdnd2935265:01crwdnd2935265:02crwdne2935265:0 Potential Work-Arounds Guide #5: crwdns2935265:010crwdnd2935265:02crwdnd2935265:02crwdne2935265:0
    • After rebooting, head back into OpenCore again, and apply Root Patches (more information in Guide #4).

    • Reboot your Mac.

  11. Potential Work-Arounds Guide #5: crwdns2935265:011crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • At this point you're probably tired of rebooting, patching, rebooting again, etc. But, that is last time you'll need to reboot. Once all patching is complete, your Mac will be back in working order, and most of your applications should now have access to your microphone or camera.

    • Unfortunately with this method, you have two main issues: One, not all apps will open without Root Patching, and therefore you cannot get all access. Second, if you download a new app that needs access to the microphone, you will need to go through this entire process again... yikes.

    • Another small issue you may encounter is that if you face a problem in the future with Security and Privacy and must run tccutil reset All in Terminal, you will have to go through this whole process again.

    • The good news is that the Terminal method is a failsafe method. Anytime you absolutely need access to something quickly, you can launch the app through Terminal.

  12. Potential Work-Arounds Guide #5, Other issues with SIP: crwdns2935265:012crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • The nice saying "I don't need an antivirus program because I have a Mac" kind of dies once you disable SIP. So, SIP is definitely not a bad thing. But, if you want to steer clear of malware, I would recommend you crank up your internet security.

    • Block all cookies if possible (yes, some websites absolutely need access to cookies to work for whatever reason)

    • Turn on Privacy Relay if you have iCloud+

    • Turn Gatekeeper to App Store only (allows downloads only from the App Store, you can find this in the Privacy and Security tab in System Preferences).

    • Steer clear of any shady websites. Avoid clicking on advertisements, and avoid opening links from spam emails.

    • Simply clear your cache on normal occasions.

    • And, just download a simple antivirus program for free for extra safety (there are hundreds out there).

  13. Potential Work-Arounds Guide #5, Graphics: crwdns2935265:013crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • Ah yes, the unfortunate graphics will be the main issue that you will face in the future. Sadly, graphics are only ever getting better, which means that older Mac's simply can't keep up with the newer technologies. If your Mac has metal graphics, you have a chance. Yet, if you are running on non-metal graphics, your Mac will probably be unusable.

    • Good news, OpenCore has developed significantly and running non-metal isn't entirely impossible. There are several work-arounds.

    • We'll start with non-metal graphics fixes

    • Then we'll talk about legacy metal graphics fixes.

  14. Potential Work-Arounds Guide #5, Non-metal Graphics: crwdns2935265:014crwdnd2935265:01crwdnd2935265:03crwdne2935265:0 Potential Work-Arounds Guide #5, Non-metal Graphics: crwdns2935265:014crwdnd2935265:02crwdnd2935265:03crwdne2935265:0 Potential Work-Arounds Guide #5, Non-metal Graphics: crwdns2935265:014crwdnd2935265:03crwdnd2935265:03crwdne2935265:0
    • First of all, running macOS Big Sur or newer on non-metal will slow down performance drastically. To speed up you Mac, you can disabled several things that use up the graphics performance.

    • Head into System Preferences > Accessibility > Displays.

    • Choose "Reduce Transparency."

    • Sure, this will make the UI less pretty. If your Mac seems to be running fine with transparency enabled, you don't have to disable this. But, try running your Mac without transparency for a while and see if the performance improves. If your Mac does seem to spring back to life, it may not hurt to leave transparency off.

  15. Potential Work-Arounds Guide #5: crwdns2935265:015crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • While in Accessibility, you can also check "Reduce Motion," which will also may the UI less pretty, but may increase performance.

    • Like I mentioned, OpenCore has developed drastically over the years, and you may not notice a performance increase at all! In fact, running macOS Big Sur or Monterey on a non-metal Mac is nearly perfect now.

  16. Potential Work-Arounds Guide #5: crwdns2935265:016crwdnd2935265:01crwdnd2935265:02crwdne2935265:0 Potential Work-Arounds Guide #5: crwdns2935265:016crwdnd2935265:02crwdnd2935265:02crwdne2935265:0
    • There are some other issues that may be simply unfixable:

    • On macOS Ventura and newer, Stage Manager is completely unavailable. Along with showing the Desktop using the trackpad gesture. The best work-around for this is to simply downgrade to macOS Monterey.

    • Some screen savers don't work at all. In fact, they just show a black screen. "Drift," "Monterey," "Ventura" are examples of screen savers that don't work.

    • Note here, the aerial screen saver on macOS Sonoma and Sequoia somehow works; but it's not pretty. You may also notice that the screen saver that has worked since the iMac G3 age called "Flurry" doesn't work very well on macOS Ventura or newer. The screen saver engine changed, and therefore requires much more energy to run.

    • Some blurs may remain broken; even when you've checked "Beta Blur" inside of OpenCore. There are some blurs (like notifications) that will still remain broken.

    • You may also notice that absolutely no blur will work on macOS Ventura and newer. I personally have had no issues with the blurs while running macOS Big Sur only.

  17. Potential Work-Arounds Guide #5: crwdns2935265:017crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • Let's talk for a second on some work-arounds for these issues using OpenCore

    • Inside of OpenCore settings (I'm assuming you're pretty comfortable with the OpenCore UI by now), head to the "Root-Patching" tab. Under the "Non-Metal Configuration," you can activate things to make your Mac run better.

    • Dark Menu Bar - This changes the text color on the menu bar depending on the desktop background. (Beta Menu Bar must be enabled for this to work.) (Also, by enabling Reduce Transparency, Dark Menu Bar does absolutely nothing.)

    • Beta Blur - In some application windows, the sidebar has that nice translucency blur. If your window seems to act weird, try toggling this and see which one works better for you. (Also does absolutely nothing with Reduce Transparency enabled.)

    • Beach Ball Cursor Workaround - Supposedly this makes the loading cursor actually spin (though this has never worked for me).

    • Beta Menu Bar - This is a custom built menu bar. It changes colors and rounds the edges for menu items just like on a native Mac. (This is the one feature that is still in beta, it has been in beta for years now. If you have issues with the menu bar, disable this.)

    • Disable Beta Rim - Honestly, I'm not entire sure what this does. My Mac has acted the same both with and without this checked. But, I believe it adds edges to the windows so they look more like a native Mac. If someone else knows, drop a comment down below because I'm not entirely sure.

    • Disable Color Widgets Enforcement - In macOS Sonoma and Sequoia, you can add widgets to the desktop. If the colors do not change while looking at the desktop or an application, you can check this. This gives the Mac one less thing to do. If the colors to change, you can leave this unchecked so the UI is nicer.

  18. Potential Work-Arounds Guide #5: crwdns2935265:018crwdnd2935265:01crwdnd2935265:02crwdne2935265:0 Potential Work-Arounds Guide #5: crwdns2935265:018crwdnd2935265:02crwdnd2935265:02crwdne2935265:0
    • There are some issues that you will face using built-in applications. We'll talk about these first, and then we'll talk about applications that you download later from the App Store.

    • All DRM Content is unavailable in macOS Big Sur and newer. This includes things like DVD Player, Music Videos, Movies, DRM Content is Safari, etc. Good news, there are a few work-arounds for the DVD Player and DRM Content in Safari.

    • For the DVD Player, you can get a third-party application. I recommend Final Video Player: Final Video Player in the App Store

    • As for issues in Safari, I would recommend using a third party browser that doesn't require metal graphics to run. Firefox is an excellent example of this. Firefox Download

    • There are still no work-arounds for music videos and movies. If you need these, stick with macOS Catalina or older.

  19. Potential Work-Arounds Guide #5: crwdns2935265:019crwdnd2935265:01crwdnd2935265:02crwdne2935265:0 Potential Work-Arounds Guide #5: crwdns2935265:019crwdnd2935265:02crwdnd2935265:02crwdne2935265:0
    • Maps simply don't load in macOS Monterey and newer, because they require metal graphics to work (this includes MapKit, so any application that requires maps [like Find My] will not work). The best work-around for this if you want to use the app is to stay on macOS Big Sur.

    • If you are okay to not use the app, you can use Google Maps directly on the web, and this does not require metal graphics to run.

  20. Potential Work-Arounds Guide #5: crwdns2935265:020crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • Photos may act a little strange. First off all, they will not curate (organize each photo into a nice organized grid). If you use iCloud Photos, the colors will be muted until you download them (they will remain muted even after downloaded in macOS Ventura and newer).

    • There's no patch to fix this, so you have to know that photos may not behave as normal...

  21. Potential Work-Arounds Guide #5: crwdns2935265:021crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • As far as I know, these are the issues and potential work-arounds for built-in applications, but if you have an issue with some other application, drop a comment down below.

    • So, let's dive into some applications that you will download, starting with Apple's Applications.

    • GarageBand simply doesn't work. It requires Metal Graphics to load the timeline. If you want to use GarageBand, you must download an older version.

    • iMovie also simply does not work. It too requires Metal Graphics to render video playback. You will also have to download and older version if you want to use it.

    • Pages, on the other hand, works flawlessly. I personally have not experienced any issues with running the latest version of Pages.

    • Numbers, too, works flawlessly. I have not had much experience using Numbers, but I have not encountered any issues.

    • Keynote works great until you want to present it. The app (or maybe even the computer) will crash when you try to preview a transition or present the keynote itself. You can edit fine, but if you want to present the keynote from the Mac, you will have to download an older version.

    • Older versions work great, you just may not have all of the new features. But, since most older versions still worked on OpenGL graphics cards, they should run fine on your machine. You can download older versions by signing in to the App Store while running macOS High Sierra, and download using the Purchased page.

  22. Potential Work-Arounds Guide #5, Legacy Metal: crwdns2935265:022crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • We covered almost everything in non-metal. Now, let's turn our focus to legacy metal.

    • What is Legacy Metal? Think of "Legacy" as "Old." In other words, Old Metal graphics.

    • Throughout the years, Metal has changed and become better and more power efficient. In 2022-2023, Apple shifted gears with macOS Ventura and eliminated all machines with the older Metal Graphics system. Therefore macOS Ventura and newer have many bugs that are graphics related.

    • Most of these bugs, however, have many work-arounds. The main thing you will need to remember is that running macOS Ventura and newer will slow down a machine with Legacy Metal.

  23. Potential Work-Arounds Guide #5: crwdns2935265:023crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • There are nine graphics systems that fall into this category:

    • Intel: Ivy Bridge (HD4000) - Haswell (HD4400/4600/5xxx) - Broadwell (HD6xxx) - Skylake (HD5xx)

    • Nvidia: Kepler (GTX 6xx, GTX 7xx)

    • AMD: GCN 1-3 (HD 7xxx/8xxx/9xxx, R7/R9, FirePro D300, D500, D700) - Polaris (RX 4xx/5xx) - (Hosts lacking AVX2.0) - Polaris (Radeon Pro 4xx/5xx & MacBookPro13,3/14,3) - Vega (RX 56/64/VII _ Hosts lacking AVX2.0)

    • This chart was taken from the OpenCore legacy metal guide.

  24. Potential Work-Arounds Guide #5: crwdns2935265:024crwdnd2935265:01crwdnd2935265:02crwdne2935265:0 Potential Work-Arounds Guide #5: crwdns2935265:024crwdnd2935265:02crwdnd2935265:02crwdne2935265:0
    • To determine which version you have, simply check out About this Mac

    • In Overview, you can see the model number. Verify that number with the chart above to determine which system your Mac has

    • For example, this MacBook Air has Intel HD Graphics 4000. According to the chart, (HD4000) is Intel Ivy Bridge.

  25. Potential Work-Arounds Guide #5: crwdns2935265:025crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • Most of these issues I have pulled from the OpenCore Legacy Metal Guide. So, let's go through each graphics system: starting with Intel Ivy Bridge:

    • Photos app fails to edit portrait photos on macOS Sonoma and macOS Sequoia. (Best work-around is to downgrade to macOS Ventura)

    • Safari fails to reproduce DRM content (Best work-around is to use a third-party browser {I highly recommend using FireFox}).

    • Paravirtualized Graphics is unavailable on macOS Sonoma and macOS Sequoia {This system is mainly used on high graphics demanding games} (Best work-around is to downgrade to macOS Ventura)

    • Live Text is broken (You can use third-party OCR software)

    • Metal's Mesh Shader feature set unavailable {This is a developer feature for graphics intensive content} (There are no work-arounds for this)

    • Green Artifacts on QuickTime Timeline for .mov (There are no work-arounds for this)

  26. Potential Work-Arounds Guide #5: crwdns2935265:026crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • Intel Haswell

    • This Graphics system has the same issues as Intel Ivy

    • You may notice that Native Metal 3 eGPUs may report as Metal 2 (This has no affect on your Mac)

  27. Potential Work-Arounds Guide #5: crwdns2935265:027crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • Intel Broadwell

    • Safari fails to reproduce DRM content (Best work-around is to use a third-party browser {I highly recommend using FireFox}).

    • Metal's Mesh Shader feature set unavailable {This is a developer feature for graphics intensive content} (There are no work-arounds for this)

  28. Potential Work-Arounds Guide #5: crwdns2935265:028crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • Intel Skylake

    • Same issues as Intel Broadwell

  29. Potential Work-Arounds Guide #5: crwdns2935265:029crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • MacBookPro14,3 has been tested by the OpenCore developers. They have proven that this MacBook model has not had any of these issues. So, great news for those who have this model!

    • This is the MacBook Pro (15-inch, 2017)

  30. Potential Work-Arounds Guide #5, Conclusion: crwdns2935265:030crwdnd2935265:01crwdnd2935265:01crwdne2935265:0
    • We've reached the end...

    • If you have been left with an issue that is not covered in this guide, PLEASE drop a comment down below. It takes everyone to keep these old Macs up and running.

crwdns2915888:0crwdne2915888:0

Hopefully this will cover most of the issues that your Mac is facing. If you still have issues, drop any comments in this guide, and we will keep adding fixes to this guide.

Jadon Lyon

crwdns2935283:009/05/23crwdne2935283:0

4,151 crwdns2915208:0crwdne2915208:0

crwdns2935297:08crwdne2935297:0

crwdns2947412:00crwdne2947412:0

crwdns2917038:0crwdne2917038:0

crwdns2936625:0crwdne2936625:0:

crwdns2936751:024crwdne2936751:0 0

crwdns2936753:07crwdne2936753:0 2

crwdns2936753:030crwdne2936753:0 8

crwdns2942667:0crwdne2942667:0 41