macOS 11 Big Sur on Unsupported Macs Thread

[nasimon-]

One question guys. I am going to install Beta 9 on my MBP 9.2 mid 2012 not retina and I am wondering if I should use the 0.19 micropatcher for the wifi to work (as in previous versions) or can I use the most current micropatcher?

I used the last one, working fine (I have the same mbp)

 

[David dongfox]

Could you check from terminal: diskutil info /Volumes/MacOs | grep Sealed

if Sealed is "Broken" then means you have a sealed System and so you can't do "apfs_systemsnapshot" from desktop but only from a BigSur recovery environment.

I do it from a BigSur recovery environment. also a same.
i reformatted a whole hard disk and reinstall OS BigSur. and everything is back to normal now.
Thank you for all the help . Thanks again.

 

[Barry K. Nathan]

@Barry K. Nathan @jackluke Confirmed: Reinstalled BS B9 from scratch instead of unpatching and retrying, using only 0.3.3 patcher. (After installation I had to remake the createinstaller + micropatcher.sh + install-setvar.sh because it was no more accessible (forbidden symbol, also when trying booting BS B9 without OpenCore) Now Wifi works and I can boot it again from Apple Booter without OpenCore but USB mouse and keyboard do not work while USB mic and webcam yes (???) and (sudo) mount -uw / returns error 77 and 66. I really do not understand what is happening, but this report could help you both to fix something on Mac mini 2010 (Macmini4,1) On my previous post you can find the screenshots with errors on patch-kekts.

The errors seem to be normal for beta 9, just ignore them. However, if those screenshots are still representative, then you're still forgetting the --2010 option on patch-kexts.sh. (A future patcher release will add automatic Mac model detection so that the --2010 option won't be necessary.)

 

[Barry K. Nathan]

One question guys. I am going to install Beta 9 on my MBP 9.2 mid 2012 not retina and I am wondering if I should use the 0.19 micropatcher for the wifi to work (as in previous versions) or can I use the most current micropatcher?

Use the current one. WiFi still has some problems but it should be better than any of the previous releases.

 

[Alex-Microsmeta]

The errors seem to be normal for beta 9, just ignore them. However, if those screenshots are still representative, then you're still forgetting the --2010 option on patch-kexts.sh. (A future patcher release will add automatic Mac model detection so that the --2010 option won't be necessary.)

In my last installation I have added --2010, too. I'm available for all tests you need, I'm really curious about why I cannot use mount -uw /, while SIP and authenticated-root are correctly accepted using your 0.3.3 patcher. Maybe csr-active-config w%00%00%00 ? And why now I can boot installer and BS B9 without OpenCore? Error 66 on mount -uw / also using Cmd + S terminal
PS: I have also a working BS B4 on SSD if it can help to fix BS B9.

 

[MrWeenus]

@Barry K. Nathan The only problem I’ve got with the WiFi patch on a MacBook pro 10,1 is iPhone hotspot not connecting Avis handoff. I have to manually go to iPhone settings before clicking on my hotspot in the menu bar

 

[CuchoM]

Use the current one. WiFi still has some problems but it should be better than any of the previous releases.

I've used on catalina this command line

sudo nvram boot-args="-no_compat_check cs_enforcement_disable=1 cs_debug=1 amfi_allow_any_signature=1 amfi_get_out_of_my_way=1" kext-dev-mode=1

then I've installed from catalina and after install I used the USB install patched to copy kext's files it works fine on MBP mid2012 wifi working, airdrop and hands-off great jo Barry K. Nathan yor patch work's fine for me.

At Big Sur I've only have to do this command after install

sudo nvram boot-args="-no_compat_check cs_enforcement_disable=1 cs_debug=1 amfi_allow_any_signature=1 amfi_get_out_of_my_way=1"

 

[Fran Frin]

Hi all, work in a iMac 21,5” mid 2011 2,5ghz i5?? With Radeon hd 6750m??
Thanks

 

[Maclinux]

I used the last one, working fine (I have the same mbp)

I used the last one and everything has worked perfectly. Thank you very much for the great work. @jackluke @Barry K. Nathan

 

[Barry K. Nathan]

In my last installation I have added --2010, too. I'm available for all tests you need, I'm really curious about why I cannot use mount -uw /, while SIP and authenticated-root are correctly accepted using your 0.3.3 patcher. Maybe csr-active-config w%00%00%00 ? And why now I can boot installer and BS B9 without OpenCore? Error 66 on mount -uw / also using Cmd + S terminal
PS: I have also a working BS B4 on SSD if it can help to fix BS B9.

I always found making mount -uw / work to be too difficult; I made remount-sysvol.sh to be a substitute for that. However, I've neglected that script recently, so right now it doesn't work. I'll probably fix the bugs and make it work again before my next patcher release (unless Apple releases a new beta later today and an urgent fix is needed for the patcher).

There's output near the beginning of the patch-kexts.sh script that's missing from your screenshots and would make troubleshooting easier for me. Also, make sure you're specifying the --2010 option before the volume name and not after (so, for example, do /Volumes/Image\ Volume/patch-kexts.sh --2010 /Volumes/Macintosh\ HD and NOT /Volumes/Image\ Volume/patch-kexts.sh /Volumes/Macintosh\ HD --2010).

It might be easiest to wait until I add automatic Mac model detection to patch-kexts.sh, and then try again at that point. (Maybe I'll write the code later today, in which case it'll be in the next patcher release.)

 

[Alex-Microsmeta]

I always found making mount -uw / work to be too difficult; I made remount-sysvol.sh to be a substitute for that. However, I've neglected that script recently, so right now it doesn't work. I'll probably fix the bugs and make it work again before my next patcher release (unless Apple releases a new beta later today and an urgent fix is needed for the patcher).

There's output near the beginning of the patch-kexts.sh script that's missing from your screenshots and would make troubleshooting easier for me. Also, make sure you're specifying the --2010 option before the volume name and not after (so, for example, do /Volumes/Image\ Volume/patch-kexts.sh --2010 /Volumes/Macintosh\ HD and NOT /Volumes/Image\ Volume/patch-kexts.sh /Volumes/Macintosh\ HD --2010).

It might be easiest to wait until I add automatic Mac model detection to patch-kexts.sh, and then try again at that point. (Maybe I'll write the code later today, in which case it'll be in the next patcher release.)

OK, I'll wait your next patch. I have BS B9 full working on iMac 2013, so I could wait the GM or final. I search if I have the first screenshot on smartphone, but I remember it patched succesfully SIP and authenticated-ROOT, followed by the list of the kexts to patch.

 

[Machist]

Mac Mini 2012 -> so there is "only" wifi issues?
What is reasonable way to fix that?
USB wifi adapter? What model/brand is compatible?

 

[Alex-Microsmeta]

@Barry K. Nathan Reinstalled patch-kexts.sh to show you first two screenshots, using
sudo nvram boot-args="-no_compat_check cs_enforcement_disable=1 cs_debug=1 amfi_allow_any_signature=1 amfi_get_out_of_my_way=1" kext-dev-mode=1 on your BS B9 micropatcher 0.3.3 (Thanks @CuchoM !) :

AUDIO OUT NOW WORKS!

 

[Barry K. Nathan]

@Barry K. Nathan Reinstalled patch-kexts.sh to show you first screenshot

OK, that first screenshot looks correct this time. See if you're still having USB and audio problems. If you are, then boot back into the installer USB and try running the following:
/Volumes/Image\ Volume/zap-snapshots.sh /Volumes/BigSur\ EXT
Then reboot and see if the problems are still present.

 

[Alex-Microsmeta]

OK, that first screenshot looks correct this time. See if you're still having USB and audio problems. If you are, then boot back into the installer USB and try running the following:
/Volumes/Image\ Volume/zap-snapshots.sh /Volumes/BigSur\ EXT
Then reboot and see if the problems are still present.

D

OK, that first screenshot looks correct this time. See if you're still having USB and audio problems. If you are, then boot back into the installer USB and try running the following:
/Volumes/Image\ Volume/zap-snapshots.sh /Volumes/BigSur\ EXT
Then reboot and see if the problems are still present.

Done! Snapshot removed succesfully: bluetooth, wifi, usb mic and webcam (no Siri), internal audio ALL OK, but still USB mouse and keyboard not detected (using iMac magic mouse and keyboard).

 

[Barry K. Nathan]

Done! Snapshot removed succesfully: bluetooth, wifi, usb mic and webcam (no Siri), internal audio ALL OK, but still USB mouse and keyboard not detected (using iMac magic mouse and keyboard).

At some point I need to try my 2009 white MacBook again and see if that has any USB problems (after patch-kexts.sh of course).

Meanwhile, I've run into a new error that I need to investigate now... Edit: I suspect I managed to cause some kind of disk corruption through a weird sequence of events. Later on I'll try recreating it and figuring out how to recover from this scenario, but I expect that other people are unlikely to run into this, so I won't worry about it right this moment.
Can't use last-sealed-snapshot or create-snapshot on non ARV volume

 

[air.man]

About Legacy USB and non-APFS Mac BigSur installer or recovery, I noticed that apple from beta 9 is seriously intentioned to remove the Extensions (kext), now the beta 9 BaseSystem.dmg size is 661 MB (on beta 4 was 840 MB , beta 8 was 750 MB ), so they have reduced even more the BaseSystem.dmg, but I just made an updated BaseSystem Legacy USB fix for beta 9 , moreover it adds the Wifi (so you can use Safari) on BigSur recovery installer and sound (press CMD+F5 to enable it on recovery).

First requirement is that from any macOS Recovery terminal at least set csrutil disable

Then get an "Install macOS Big Sur Beta.app" (currently beta 9 InstallAssistant.pkg) making a stock apple USB BigSur installer with this method:

sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/ createinstallmedia --volume /Volumes/YourUSBLabel

then apply the "BigSur BaseSystem b9 legacy usb fix" , after unplug and plug again your USB drive and apply the "BigSur BaseSystem b9 legacy usb fix2".

After made you can boot from a Penryn Core2Duo non-APFS or legacy USB Mac the USB BigSur Installer from apple startup manager or USBopencore, then upgrade or install it on BigSur unsupported Mac, simply typing from Recovery Utilities terminal this: /V*/I*/H*

(that is abbreviation for /Volumes/Image\ Volume/Hax3.sh based on ASentientBot Hax3.dylib)

It should work on any BigSur capable Mac but is aimed to Legacy USB and non-APFS Penryn Core2Duo, to continue stage2 installer or to boot after installation you need a non spoof version of USBOpenCoreAPFSloader4s1.zip (to detect the "macOS Installer") and for Legacy USB to use CMD+S and exit (this check is required to have responsive usb input devices and concurrently a BigSur USB external installation).

Instead for other recent USB Mac this BaseSystem fix should work without efforts and could be also combined with Micropatcher.

Hi jackluke, I tried your method on my MB5,1. I patched the USB stick with fix and fix2, successfully booted the USB installer and execute the terminal command. I launched the BigSur installation that completed the stage1 and the installer rebooted. I got the forbidden sign as expected. So I reboot the EFI provided by your OpenCore4s1 and got a new scenario as in pic 2. I reboot the "macOS Installer" but still I got the forbidden sign.
Any idea where I was wrong?
Thanks a lot for all your contributions.

 

[jackluke]

Hi jackluke, I tried your method on my MB5,1. I patched the USB stick with fix and fix2, successfully booted the USB installer and execute the terminal command. I launched the BigSur installation that completed the stage1 and the installer rebooted. I got the forbidden sign as expected. So I reboot the EFI provided by your OpenCore4s1 and got a new scenario as in pic 2. I reboot the "macOS Installer" but still I got the forbidden sign.
Any idea where I was wrong?
Thanks a lot for all your contributions.

View attachment 963937 View attachment 963938

That is a Legacy USB non-APFS Mac, so if you are installing BigSur on an internal SATA disk to continue the "macOS Installer" you should boot without USBopencore, but from a macOS Recovery or an USB Catalina Installer (patched by dosdude1), open a recovery terminal and type:

nvram boot-args="-no_compat_check"
csrutil disable

This should continue the BigSur stage2 installer targeting an internal SATA disk.

While instead if you intend to install BigSur on an external USB disk you should use USBopencore, due to non-APFS legacy USB issues , then from Catalina copy my BigSur patched BaseSystem.dmg overwrite to this path: /Volumes/BigSur Data/macOS Install Data/

and my patched prelinkedkernel rename to BootKernelExtensions.kc and copy overwrite in this path: /Volumes/BigSur Data/macOS Install Data/Locked Files/

The "Locked Files" is a locked folder, so from Catalina (or Mojave) Finder "Get Info" on the "Locked Files" folder and give to admin and everyone read and write permissions.

This should continue the stage2 installer on a non-APFS Mac targeting an external USB disk.

edit:
About continue stage2 installing on external USB disk, you could try even without replacing BaseSystem.dmg and prelinkedkernel , to use USBopencore and boot the "macOS Installer" with CMD+S and exit to continue booting (that is for Legacy USB injector on KernelCollections).

 

[Fabian Schön]

Hello does this work on Beta 9 BigSur Penryn beta3 prelinkedkernel fix

 

[jackluke]

Hello does this work on Beta 9 BigSur Penryn beta3 prelinkedkernel fix

Penryn beta3 prelinkedkernel still works but only for the USB BigSur beta 9 installer (BaseSystem patched), after installation BootKernelExtensions.kc are used and currently USBopencore can inject on KernelCollection the parrotgeek1 LegacyUSBInjector.kext with CMD+S and exit .

The reason why I still used a prelinkedkernel is that can swap it easily through a simple UUID matching with Extensions kext folder, instead the new BKE require an UUID match with an updated SystemKernelExtensions.kc (that is I guess a zlib compressed Extensions folder) , but essentially they are both kernel caches and embed the kext and kernel.

 

[Caeed]

Hello
I have a Mac 2011
And my graphics are a bit weak compared to Big Sur
But on Windows computers
There are ways
Which can be used on loan from Ram to help graphics
For example, this is possible in the BIOS
Or there is special software for this
But it does not have BIOS on Mac
And software is not as extensive as Windows
I did not find a solution
You have a way to add graphics or use RAM
Thankful
I apologize if it was translated badly

 

[Ausdauersportler]

Hello
I have a Mac 2011
And my graphics are a bit weak compared to Big Sur
But on Windows computers
There are ways
Which can be used on loan from Ram to help graphics
For example, this is possible in the BIOS
Or there is special software for this
But it does not have BIOS on Mac
And software is not as extensive as Windows
I did not find a solution
You have a way to add graphics or use RAM
Thankful
I apologize if it was translated badly

This is surely off topic, take a look at this thread...

 

[Caeed]

This is surely off topic, take a look at this thread...

I think it 's a fake number change
And it does not change the process of graphic work

 

[jackluke]

I think it 's a fake number change
And it does not change the process of graphic work

This instead should work on BigSur too but instead of kextcache it requires a kmutil snapshot kext installation and @Barry K. Nathan could test it: IntelHD3000 VRAM increase pre-patched HighSierra/Mojave/Catalina

after kext patch to verify the VRAM increase just use this app: https://apps.apple.com/br/app/opengl-extensions-viewer/id444052073?l=en&mt=12

 

[air.man]

That is a Legacy USB non-APFS Mac, so if you are installing BigSur on an internal SATA disk to continue the "macOS Installer" you should boot without USBopencore, but from a macOS Recovery or an USB Catalina Installer (patched by dosdude1), open a recovery terminal and type:

nvram boot-args="-no_compat_check"
csrutil disable

This should continue the BigSur stage2 installer targeting an internal SATA disk.

While instead if you intend to install BigSur on an external USB disk you should use USBopencore, due to non-APFS legacy USB issues , then from Catalina copy my BigSur patched BaseSystem.dmg overwrite to this path: /Volumes/BigSur Data/macOS Install Data/

and my patched prelinkedkernel rename to BootKernelExtensions.kc and copy overwrite in this path: /Volumes/BigSur Data/macOS Install Data/Locked Files/

The "Locked Files" is a locked folder, so from Catalina (or Mojave) Finder "Get Info" on the "Locked Files" folder and give to admin and everyone read and write permissions.

This should continue the stage2 installer on a non-APFS Mac targeting an external USB disk.

edit:
About continue stage2 installing on external USB disk, you could try even without replacing BaseSystem.dmg and prelinkedkernel , to use USBopencore and boot the "macOS Installer" with CMD+S and exit to continue booting (that is for Legacy USB injector on KernelCollections).

Hi jackluke, I followed your instruction to reboot to USBOpencore and then boot to "macOS Installer" with CMD+S and I got what you see in pic 1.

Thanks.