macOS 11 Big Sur on Unsupported Macs Thread

[justperry]

No b11 today?!

 

[Mark Meretz]

I guess I patched the HighSierra AppleGVA.framework to use it on BigSur, maybe @Ausdauersportler could try it, since currently I cannot test it on an IntelHD3000 GPU .

The attached for beta10 should be replaced here: /System/Library/PrivateFrameworks/

To replace this framework follow the conditions I wrote on previous post, but mainly requirements are: AMFI disabled, csrutil disable, with sudo mount -uw / replacing the framework is much easier, but also with snapshot booting can replace it from a BigSur macOS Installer then make a new snapshot with framework replaced (as when replace kext).

So your patch doesn't work for me .... no H264

 

[Ausdauersportler]

I guess I patched the HighSierra AppleGVA.framework to use it on BigSur, maybe @Ausdauersportler could try it, since currently I cannot test it on an IntelHD3000 GPU .

The attached for beta10 should be replaced here: /System/Library/PrivateFrameworks/

To replace this framework follow the conditions I wrote on previous post, but mainly requirements are: AMFI disabled, csrutil disable, with sudo mount -uw / replacing the framework is much easier, but also with snapshot booting can replace it from a BigSur macOS Installer then make a new snapshot with framework replaced (as when replace kext).

me@iMac ~ % sudo nvram -p | grep boot-args
Password:
boot-args    -no_compat_check amfi_get_out_of_my_way=1
me@iMac ~ % sudo nvram -p | grep csr      
csr-active-config    %7f%08%00%00
me@iMac ~ %

With this setting I have no success. Tried the same framework before with different NVRAM settings, no AMFI...

 

[jackluke]

So your patch doesn't work for me .... no H264

me@iMac ~ % sudo nvram -p | grep boot-args
Password:
boot-args    -no_compat_check amfi_get_out_of_my_way=1
me@iMac ~ % sudo nvram -p | grep csr  
csr-active-config    %7f%08%00%00
me@iMac ~ %

With this setting I have no success. Tried the same framework before with different NVRAM settings, no AMFI...

I used that patched framework for h264 on Mojave with Nvidia and IntelHD Arrandale non Metal GPUs, but to check if you replaced properly that framework, could you try also this fix for night shift: patched BigSur CoreBrightness.framework.zip

chown and chmod are not required for BigSur Frameworks (only for kext), so simply copy paste without merge, take a backup of your CoreBrightness.framework too and keep AMFI disabled to use ad-hoc signed framework exec.

So I guess maybe using a Mojave or Catalina AppleGVA binary patched could work better with BigSur, because I repeat the previous file used a stock HighSierra AppleGVA that has less IOKit in common with BigSur, while Mojave and mainly Catalina do have.

Then about AppleGVA I just noticed this: https://forums.macrumors.com/threads/activate-amd-hardware-acceleration.2180095/post-27442938

So I ask what's the condition to enable H264 on an hybrid dual GPUs Metal GPU and IntelHD3000, maybe a simply whitelisting of machine board-id inside the AppleGVA exec ?

 

[Ausdauersportler]

Then about AppleGVA I just noticed this: https://forums.macrumors.com/threads/activate-amd-hardware-acceleration.2180095/post-27442938

So I ask what's the condition to enable H264 on an hybrid dual GPUs Metal GPU and IntelHD3000, maybe a simply whitelisting of machine board-id inside the AppleGVA exec ?

This method works the other way around. If you have installed within your Mac Pro a new AMD Polaris GPU and want the AMD 4K H.284 acceleration working without spoofing the iMacPro1,1 ID using OpenCore you can binary patch the exec file and change back the iMacPro1.1 ID with the native Mac Pro ID. Drawback of this patching is you cannot get AMD 4K HEVC working. This is only possible with OpenCore and the iMacPro1,1 ID. So we AMD owners use OpenCore (mostly in form of the older Catalina Loader package on an SD card....)

With Nvidia GPUs you have no such H.264 support and the best you can get (only) in iMac 12,X is the Sandy Brigde HD3000 iGPU offering a limited version of H.264.

This has been achieved by just changing the recent Mojave and Catalina AppleGVA.framework with the older High Sierra version. Currently I cannot tell you where to binary or plist patch the newer AppleGVA.framework to get back HD3000 support. I am afraid Apple pulled that code simply out of the newer versions.

 

[Ausdauersportler]

I used that patched framework for h264 on Mojave with Nvidia and IntelHD Arrandale non Metal GPUs, but to check if you replaced properly that framework, could you try also this fix for night shift: patched BigSur CoreBrightness.framework.zip

chown and chmod are not required for BigSur Frameworks (only for kext), so simply copy paste without merge, take a backup of your CoreBrightness.framework too and keep AMFI disabled to use ad-hoc signed framework exec.

So I guess maybe using a Mojave or Catalina AppleGVA binary patched could work better with BigSur, because I repeat the previous file used a stock HighSierra AppleGVA that has less IOKit in common with BigSur, while Mojave and mainly Catalina do have.

Yes, your CoreBrightness.framework patch works for me on my Nvidia based iMac 12,2, had to install and deinstall and now install to check this. @Barry K. Nathan, this framework you need to add to your micro patcher.

So the settings are okay on this machine, including the NVRAM, only the AppleGVA.framework does not want as we would like...

 

[webg3]

I need some help, I created a partition for OpenCore, how to mark it to be the first one when I start the Mac? I would like to do this, because then I don't have to hold Option every time I have to restart or turn on the device. When we install Windows via Bootcamp, it takes first place at boot, it is the same behavior that I would like here.

 

[Barry K. Nathan]

@Barry K. Nathan about your newer micropatcher Legacy USB fix to use the kmutil binary from beta 3, (I also use for my patched prelinkedkernel a beta 3 kernel and its beta 3 kext), you use the --bundle-path (@testheit method) to build BootKernelExtensions.kc with @parrotgeek1 LegacyUSBInjector.kext embedded and also SystemKernelExtensions.kc with that kext ?

(I ask this because from my test for "UUID kernelcache Preboot matching" is sufficient to update BKE)

I mean LegacyUSBInjector.kext is bundled on both the kernelcollections or BKE only ?

If you put it also in SKE, instead of rebuild SKE, could you try to include it to build on the AuxiliaryKernelExtensions.kc ( /Library/Extensions/ ) ?

About the use of CMD+S and exit (on next beta 11, I release an updated basesystem fix for that), I guess this required HID: Legacy Shim 2 "booting delay" through single user mode is due to when with a non-APFS Mac simultaneously occurs:

1) BigSur is installed on an external USB hard disk and plugged for booting to a Legacy USB port (there are also USB 2.0 legacy port not only USB 1.1 )

2) As input devices are used:
- internal trackpad and internal keyboard (I guess both use an internal Legacy USB Hub)
- USB mouse and USB keyboard (both plugged to Legacy USB ports, or one USB port with a keyboard USB hub port for mouse or both plugged to an external USB 2.0 hub)
- bluetooth mouse and bluetooth keyboard (if internal bluetooth hardware version is 2.1+EDR then it's an internal Legacy USB Hub)
- mixed situation for example a bluetooth mouse and USB keyboard or an USB bluetooth for wireless mouse and internal keyboard

so in this particular case when root device and input devices are plugged to Legacy USB ports, I guess CMD+S and exit is required even using your newer micropatcher Legacy USB fix, but I could be wrong.

My patcher only adds LegacyUSBInjector.kext to BootKernelExtensions.kc. As far as I can tell, kmutil makes sure that all kexts which are in BootKernelExtensions.kc are excluded from SystemKernelExtensions.kc so that there is no overlap.

I tried adding LegacyUSBInjector.kext to AuxiliaryKernelExtensions.kc a couple months ago (sometime in the beta 3 timeframe I think) and it failed to work.

Before I try to answer any more questions regarding legacy USB stuff, I'd like to make more progress with v0.4.4 development. I might know more of the answers at that point.

 

[Barry K. Nathan]

I guess I patched the HighSierra AppleGVA.framework to use it on BigSur, maybe @Ausdauersportler could try it, since currently I cannot test it on an IntelHD3000 GPU .

Right now my patcher intentionally makes sure that H.264 acceleration absolutely does not happen on HD3000. I'll do something about this at some point soon. I'm not sure whether that will be for v0.4.4 or if it'll have to wait for v0.4.5 or v0.4.6.

(Without a Metal GPU, at least, it leads to some really disruptive kernel panics. If I didn't disable H.264 acceleration to get rid of the kernel panics, I was going to have to completely drop support for 2011 Macs. The kernel panics were that bad.)

Some advises to use patched frameworks on BigSur :

- amfi disabled (amfi_get_out_of_my_way=1 in nvram or in com.apple.Boot.plist or ASentientBot Disable Library Validation plist)

I know that disabling AMFI (on the installed Big Sur system) was causing TCC problems in earlier betas. I was hoping to revisit it if and only if it was part of making non-Metal GPUs work... I'm sure I'll adopt a more reasonable attitude toward it soon, maybe after I release v0.4.4, but first I need to try reproducing the TCC problems myself (so I'll be able to quickly and reliably test for them).

 

[Barry K. Nathan]

Tried also Micropatcher 0.4.3 on beta 9
but failed again as usual. Please see photo

i tried it twice booting from usb and from macOS

First, make sure you've done a Time Machine backup, as I've mentioned in a few previous posts.

Next, try doing the following:

Boot from the patched installer USB. Open Terminal. Then run the following commands:

cd /Volumes
mount -uw "Volume Name" (such as "MY KINGSTON SSD" or "Macintosh HD" or whatever your Big Sur volume is)
cd "Volume Name"
cd System/Library
mv Extensions Extensions.old

Then quit Terminal, start the Installer, and reinstall Big Sur. See if you're able to make WiFi and Ethernet work afterward.

 

[akki_nd]

I noticed on Beta 9 and 10 MacBook Pro mid 2012 is taking 1-2 Minutes booting, which is significantly high. On Beta 6 it was like 20 seconds. Performance is also not that good on beta 10 so I am going back to Beta6 again. BTW with @Barry K. Nathan latest patch installation went so smooth, without any error / glitch. I have not faced any grey screen freeze (as reported by others) or anything like that. Thanks Barry

 

[hvds]

Yes, your CoreBrightness.framework patch works for me on my Nvidia based iMac 12,2, had to install and deinstall and now install to check this. @Barry K. Nathan, this framework you need to add to your micro patcher.

So the settings are okay on this machine, including the NVRAM, only the AppleGVA.framework does not want as we would like...

CoreBrightness.framework (and nightshift with it) also working on MBP5,2 with BS beta10. *

Many things in good shape on this legacy USB machine.

I had the problem of Photos.app crashing with all BS betas, but I had always used migration assistant to populate it with all my photos from Catalina. There seem to be one or more with problematic data among them. Without migration (just importing quite a few photos from iPhone) no problems.

* patch-kexts.sh is so well structured that I didn't replace CoreBrightness manually, but found it easier to make a small temporary change/addition to micropatcher 0.4.3 instead.

Thanks Barry K. Nathan and jackluke!

 

[jackluke]

Yes, your CoreBrightness.framework patch works for me on my Nvidia based iMac 12,2, had to install and deinstall and now install to check this. @Barry K. Nathan, this framework you need to add to your micro patcher.

So the settings are okay on this machine, including the NVRAM, only the AppleGVA.framework does not want as we would like...

I just read that Barry disabled rightly the H264 for IntelHD3000 non metal BigSur due to kp without video acceleration , but if you have Metal swapped GPU and IntelHD3000 is secondary, I guess you could retry to use that AppleGVA from HighSierra and rebuild a new kernelcollection adding these: AppleIntelSNBVA.bundle and AppleIntelHD3000GraphicsVADriver.bundle

 

[jackluke]

I know that disabling AMFI (on the installed Big Sur system) was causing TCC problems in earlier betas.

Right, "disabling AMFI" third party app permissions needs to be added manually through tccplus (/Library/Application Support/com.apple.TCC/TCC.db is on Data Volume so writable from snapshot), but using this @ASentientBot method:

sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true

it will work easily with snapshot booting because that plist is written on the Data Volume, can be used also as simple file copied (that plist is binary encoded), so through that method stock TCC.db will work and ad-hoc signature modified frameworks exec are allowed too.

 

[Mark Meretz]

I just read that Barry disabled rightly the H264 for IntelHD3000 non metal BigSur due to kp without video acceleration , but if you have Metal swapped GPU and IntelHD3000 is secondary, I guess you could retry to use that AppleGVA from HighSierra and rebuild a new kernelcollection adding these: AppleIntelSNBVA.bundle and AppleIntelHD3000GraphicsVADriver.bundle

Where do they have to go? And where should you get these from HS? Do file rights have to be repaired here?

 

[jackluke]

Where do they have to go? And where should you get these from HS? Do file rights have to be repaired here?

/System/Library/Extensions/ and for kext replacing is required chown and chmod otherwise the kernelcollection goes kp , those stock from HighSierra should work, I guess it's also required a SystemKernelExtensions.kc rebuild for those, not only BKE , if you have working sudo mount -uw / you can use kmutil install --update-all .

 

[Ausdauersportler]

I just read that Barry disabled rightly the H264 for IntelHD3000 non metal BigSur due to kp without video acceleration , but if you have Metal swapped GPU and IntelHD3000 is secondary, I guess you could retry to use that AppleGVA from HighSierra and rebuild a new kernelcollection adding these: AppleIntelSNBVA.bundle and AppleIntelHD3000GraphicsVADriver.bundle

Here they are...

 

[Ausdauersportler]

I report that this my earlier patched framework (based on Catalina framework 10.15.6): BigSur patched CoreBrightness exec

still works correctly on BigSur beta 10, as I explained earlier even if BigSur frameworks exec are packaged in dyld shared cache, if you replace manually it inside the target folder (typically /System/Library/Frameworks/Name.framework/Versions/A/ ), the kernel will try to load your patched framework exec before the one in dyld shared cache.

Just found an exception:

Installing your patched CoreBrightness.framework caused a lot of pain. It gave me a grey screen after 1/3 of the progress bar and no full boot at all. Restoring the original framework from recovery did not work, had to unpatch using the original collections and patch it again.

While doing this I found another incompatible extension (patched AGC does not play nicely with AMD cards, only for AMD iMac 2011) and could repair this. Both files caused the same symptoms ....

 

[jackluke]

Just found an exception:

Installing your patched CoreBrightness.framework caused a lot of pain. It gave me a grey screen after 1/3 of the progress bar and no full boot at all. Restoring the original framework from recovery did not work, had to unpatch using the original collections and patch it again.

While doing this I found another incompatible extension (patched AGC does not play nicely with AMD cards, only for AMD iMac 2011) and could repair this. Both files caused the same symptoms ....

I guess your issues are instead due to a reset of "AMFI or SIP enabled" (especially if you use Opencore those variables reset often) and your patched AppleGraphicsControl kext with its plugins incompatible with kernelcollections (I'd exclude CoreBrightness), anyway if patched CoreBrightness caused issues don't use it, my post was just to point that frameworks exec patching is still feasible also without extracting the BigSur dyld shared cache. Because essentially when are required patched frameworks, the previous macOS exec are used, as with kext, they are almost all from HighSierra (and Mojave).

To remove a patched framework on BigSur, is suffice to remove its exec on /Versions/A/ folder (so the dyld shared cache one is used), if you have working sudo mount -uw / simply replacing it (from another macOS or recovery because frameworks exec are constantly in use by macOS) at next reboot will work, with snapshot booting instead you have to create a new snapshot with replaced framework and possibly rebuild at least BootKernelExtensions.kc to tag the new snapshot for UUID matching with Preboot.

 

[akki_nd]

I did a clean install on my MBP Mid 2012 again with latest micro patcher, reformatted the SSD but still its taking like 2 minutes while booting and its kind of laggy, even YouTube is giving errors on safari (An error occurred. Please try later - playback ID: uXoRiF345v). Whats wrong with Beta 10? Can I do something to make it fast like Beta 3 or 6? I just followed the micro patcher 0.4.3 instructions and everything went so smooth without any error, but after installation its whole different story. Did anyone else encountered this issue.

 

[amaze1499]

I did a clean install on my MBP Mid 2012 again with latest micro patcher, reformatted the SSD but still its taking like 2 minutes while booting and its kind of laggy, even YouTube is giving errors on safari (An error occurred. Please try later - playback ID: uXoRiF345v). Whats wrong with Beta 10? Can I do something to make it fast like Beta 3 or 6? I just followed the micro patcher 0.4.3 instructions and everything went so smooth without any error, but after installation its whole different story. Did anyone else encountered this issue.

Same machine here. No startup issues with B10. Got the same Youtube error with Safari though. Systemwide issue. Seems to be a bug. As for the launch time, start with cmd + v and see whats happening during the launch sequence. Also, the HDD cable is well known for failing often. Pop in a new one.

 

[akki_nd]

Same machine here. No startup issues with B10. Got the same Youtube error with Safari though. Systemwide issue. Seems to be a bug. As for the launch time, start with cmd + v and see whats happening during the launch sequence. Also, the HDD cable is well known for failing often. Pop in a new one.

Thanks for the reply, in verbose mode "Mounted VolumeAPPLE SSD-Data" is taking lot of time, plus there were some keybag errors. which came and disappear in seconds. BTW SSD health is 100%.
Thanks Again...

 

[thatsmeonlyme]

Same machine here. No startup issues with B10. Got the same Youtube error with Safari though. Systemwide issue. Seems to be a bug. As for the launch time, start with cmd + v and see whats happening during the launch sequence. Also, the HDD cable is well known for failing often. Pop in a new one.

The Safari error can be solved:
Go to Safari preferences, enable developer in the menu bar. under experimental features disable V9 decoder. Restart Safari and youtube should be working again.

 

[akki_nd]

The Safari error can be solved:
Go to Safari preferences, enable developer in the menu bar. under experimental features disable V9 decoder. Restart Safari and youtube should be working again.

THANKS !!!!, YouTube is working fine now. Still stuck with the booting time. I think its something to do with snapshots or mounting volumes.

 

[Mark Meretz]

I'm about to have a seizure, don't get the two bundles in S / L / E. In PrivateFramework it works too, I don't understand why it doesn't work with S / L / E in S / L / PF but it does

Edit:

I have now been able to insert the 2 bundles now it no longer boots ^^