macOS 11 Big Sur on Unsupported Macs Thread

[brandonsierra]

View attachment 928270
It’s been stuck like this, do I force reboot?

It rebooted

 

[joanbcn91]

Try this (give me some minutes to type):

mount -uw /Volumes/BigSur/

cd /Volumes/BigSur/System/Library/Extensions/

mv IO80211Family.kext IO80211Family.kext2

cp -R /Volumes/Image\ Volume/IO80211Family.kext .

kmutil install --update-all --volume-root /Volumes/BigSur/

diskutil mount Preboot

cd /Volumes/Preboot/

ls

cd /Volumes/Preboot/UUID-BigSur/boot/System/Library/KernelCollections/

cp /Volumes/BigSur/System/Library/KernelCollections/BootKernelExtensions.kc .

reboot and check if Wifi is working.

Notice that during copying from recovery terminal you need to add the dot for the current folder:
cp -R /Volumes/Image\ Volume/IO80211Family.kext .

"Image Volume" is exactly the label for any BigSur USB Installer drive root folder so it's common to any mac.

Thanks for your help!
With your instructions... See the image: the Big Sur its frozen on the loading screen.

 

[brandonsierra]

I’m stuck here and the drive I was booting from had the label “macOS Installer”... Is this the right drive I’m booting from?

 

[jackluke]

Thanks for your help!
With your instructions... See the image: the Big Sur its frozen on the loading screen.
View attachment 928276

Hi

I have finally managed to install BS without errors. Now, pressing ALT, togheter with Catalina SSD and Windows 10 Efi Boot, I have also a bootable MacOS 11 volume (external 160 GB USB drive APFS partitioned before using Install MacOS beta.app with all patches suggested) Catalina mounts it as "Update" volume, warning that is non fully compatible with the partition. Since I have a Mac mini 2010 (Macmini4,1) with Core 2 Duo Penryn P8600 2.4 ghz I must remove telemetry. BS starts, but when switches to the white screen, after a while of mouse coloured circle spinning, crashes and restarts. How can I access to macOS BS Recovery? If I press command + R it goes to Internet Recovery (the one with spinning Globe) so I cannot access to Terminal to try to remove telemetry.

Thank you for all your very appreciated help! (...I don't know, maybe you could write an automatic script for your elegant solution?)

Regards, Alex

Try this other method:

https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28611501

 

[brandonsierra]

Now I hard rebooted and I think I messed up

 

[jackluke]

Thanks for your help!
With your instructions... See the image: the Big Sur its frozen on the loading screen.

Reboot to the USB BigSur Installer then and copy back the stock BigSur Wifi kext (otherwise you need to re-install):

mount -uw /Volumes/BigSur/

cd /Volumes/BigSur/System/Library/Extensions/

mv IO80211Family.kext2 IO80211Family.kext

kmutil install --update-all --volume-root /Volumes/BigSur/

diskutil mount Preboot

cd /Volumes/Preboot/

ls

cd /Volumes/Preboot/UUID-BigSur/boot/System/Library/KernelCollections/

cp /Volumes/BigSur/System/Library/KernelCollections/BootKernelExtensions.kc .

 

[brandonsierra]

Now I hard rebooted and I think I messed up

I will restart install process from beginning

 

[joanbcn91]

Reboot to the USB BigSur Installer then and copy back the stock BigSur Wifi kext (otherwise you need to re-install):

mount -uw /Volumes/BigSur/

cd /Volumes/BigSur/System/Library/Extensions/

mv IO80211Family.kext2 IO80211Family.kext

kmutil install --update-all --volume-root /Volumes/BigSur/

diskutil mount Preboot

cd /Volumes/Preboot/

ls

cd /Volumes/Preboot/UUID-BigSur/boot/System/Library/KernelCollections/

cp /Volumes/BigSur/System/Library/KernelCollections/BootKernelExtensions.kc .

I now deleted the partition. I Will try all again from zero. I Will told you later Thanks!

 

[antony34]

Try this (give me some minutes to type):

mount -uw /Volumes/BigSur/

cd /Volumes/BigSur/System/Library/Extensions/

mv IO80211Family.kext IO80211Family.kext2

cp -R /Volumes/Image\ Volume/IO80211Family.kext .

kmutil install --update-all --volume-root /Volumes/BigSur/

diskutil mount Preboot

cd /Volumes/Preboot/

ls

cd /Volumes/Preboot/UUID-BigSur/boot/System/Library/KernelCollections/

cp /Volumes/BigSur/System/Library/KernelCollections/BootKernelExtensions.kc .

reboot and check if Wifi is working.

Notice that during copying from recovery terminal you need to add the dot for the current folder:
cp -R /Volumes/Image\ Volume/IO80211Family.kext .

"Image Volume" is exactly the label for any BigSur USB Installer drive root folder so it's common to any mac.

Thank you very much @jackluke
I got same problem with @joanbcn91 during replacing the kext.
After followed your command and the wifi still not work in 13” MBP 2012...
Can I just clean install the system through the USB install disk?

 

[jackluke]

Thank you very much @jackluke
I got same problem with @joanbcn91 during replacing the kext.
After followed your command and the wifi still not work in 13” MBP 2012...
Can I just clean install the system through the USB install disk?

If you have an IO80211Family.kext backup you could re-use it, but that's weird because I replaced manually BootKernelExtensions.kc on Preboot and it worked on different machine, anyway you can't re-install from USB install disk, unless spoofing with opencore, but ASentientBot Hax.dylib method is safer, only thing you need Mojave or Catalina to use it.
[automerge]1593258464[/automerge]

I now deleted the partition. I Will try all again from zero. I Will told you later Thanks!

After you re-installed check from BigSur desktop if you can use from terminal "sudo mount -uw /", because if it works replacing the kext is much more easier.

 

[antony34]

If you have an IO80211Family.kext backup you could re-use it, but that's weird because I replaced manually BootKernelExtensions.kc on Preboot and it worked on different machine, anyway you can't re-install from USB install disk, unless spoofing with opencore, but ASentientBot Hax.dylib method is safer, only thing you need Mojave or Catalina to use it.
[automerge]1593258464[/automerge]


After you re-installed check from BigSur desktop if you can use from terminal "sudo mount -uw /", because if it works replacing the kext is much more easier.

Thanks a lot!
But I can’t use "sudo mount -uw /" in BigSur desktop because got the error 66.

Let me reinstall to Cat and try again.

 

[Alex-Microsmeta]

View attachment 928270
It’s been stuck like this, do I force reboot?

No! Wait after 30-60 minutes it will finish installation without erros!
[automerge]1593259018[/automerge]

View attachment 928277
I’m stuck here and the drive I was booting from had the label “macOS Installer”... Is this the right drive I’m booting from?

yes

 

[Lucky736]

Just fyi: I have got the absolutely same prob with a Mid 2009 MBP, with a patched ROM so it does boot Catalina from APFS natively. Hope somebody can figure out how to patch that.

One of my machines is very similar so waiting as well, the patched ROM from Dosdude1 has been great I have to say.

 

[jackluke]

Thanks a lot!
But I can’t use "sudo mount -uw /" in BigSur desktop because got the error 66.

Let me reinstall to Cat and try again.

Before re-install you could try to remove the BigSur snapshots (this should fix "sudo mount -uw /" too):

macOS 11 Big Sur on Unsupported Macs Thread

Hey everyone! After wasting half the day on this, I finally figured out one piece of the snapshots/error 66 puzzle. The TL;DR is that you can just call apfs_systemsnapshot -v /Volumes/... -r "" to boot from the live volume. I haven't seen this published anywhere yet, and the accepted wisdom...

forums.macrumors.com

Many reported that also from the USB BigSurInstaller recovery terminal should be used:
csrutil authenticated-root disable

But really don't know, I've installed and re-installed BigSur multiple times and I can still use "sudo mount -uw /" and even mount the BigSur System Volume from HighSierra.

 

[jhowarth]

One of my machines is very similar so waiting as well, the patched ROM from Dosdude1 has been great I have to say.

Just to be clear, this has nothing to do with patched ROM but instead the absence of official Apple ROMs with APFS support.

 

[muppetlover]

I have been following along since Wednesday and really enjoyed the spirit of how this thread works. Thanks to all of you I have BS installed on my mac mini 2012: I did a parallel install to Catalina, but in a separate container. I got as far as error 66 and needed to get on with 'regular stuff', so switched back to Catalina. I now get 'incompatible disk' error and Disk Utility crashes when I browse the containers...

I am not alone - https://forums.macrumors.com/threads/help-disk-issue-now.2242584/post-28614599

Some people likely put BS in same container, by the looks of it. I believe from the other thread that I am not alone in having done separate container, but still get issue.

I ran diskutil verifyVolume from the Recovery Terminal on my Cat system volume (the non data volume). I get the following:

warning: container has been mounted by APFS version 1640.0.0.111.2, which is newer than 1412.120.2

This seems to be the only issue verify finds. I don't believe I even launched DU in BS, pretty much went with the advice in this thread unto I got the error 66 issue and then I stopped.

Does anyone here know a remedy for remounting container using Catalina command line?

 

[jackluke]

I have been following along since Wednesday and really enjoyed the spirit of how this thread works. Thanks to all of you I have BS installed on my mac mini 2012: I did a parallel install to Catalina, but in a separate container. I got as far as error 66 and needed to get on with 'regular stuff', so switched back to Catalina. I now get 'incompatible disk' error and Disk Utility crashes when I browse the containers...

I am not alone - https://forums.macrumors.com/threads/help-disk-issue-now.2242584/post-28614599

Some people likely put BS in same container, by the looks of it. I believe from the other thread that I am not alone in having done separate container, but still get issue.

I ran diskutil verifyVolume from the Recovery Terminal on my Cat system volume (the non data volume). I get the following:

warning: container has been mounted by APFS version 1640.0.0.111.2, which is newer than 1412.120.2

This seems to be the only issue verify finds. I don't believe I even launched DU in BS, pretty much went with the advice in this thread unto I got the error 66 issue and then I stopped.

Does anyone here know a remedy for remounting container using Catalina command line?

I guess this issue (that I don't have) of can't mounting APFS BigSur System Volume from Catalina is due to the fact the BigSur installation hasn't completed properly so the apfs nodes (and permissions) are mismatched.

But, not sure if relevant, I erased the APFS container to install BigSur from HighSierra, meaning through its HighSierra /System/Library/FileSystems/apfs.fs/Contents/Resources/
apfs driver version: 748.51.0

And I can "sudo mount -uw /" from BigSur normal booting even after making some manual BigSur snapshots, anyway I guess that installing BigSur on a separate APFS container (meant using another disk and another EFI external) will work without issues and BigSur System volume is mountable and writeable even from HighSierra.

 

[muppetlover]

I guess this issue (that I don't have) of can't mounting APFS BigSur System Volume from Catalina is due to the fact the BigSur installation hasn't completed properly so the apfs nodes (and permissions) are mismatched.

But, not sure if relevant, I erased the APFS container to install BigSur from HighSierra, meaning through its HighSierra /System/Library/FileSystems/apfs.fs/Contents/Resources/
apfs driver version: 748.51.0

And I can "sudo mount -uw /" from BigSur normal booting even after making some manual BigSur snapshots, anyway I guess that installing BigSur on a separate APFS container (meant using another disk and another EFI external) will work without issues and BigSur System volume is mountable and writeable even from HighSierra.

Forgive me, I am not sure I follow.

I thought the incompatible disk was my Catalina volume - the verify that gives the APFS version warning was done against the Catalina volume.

 

[joanbcn91]

Thanks a lot @jackluke!!
After reinstalling from zero again, sudo -uw did not work again. But, I have followed the guide from This guide. This time, it has NOT given me an error generating the snapshot. The whole process has been quick and easy. Wi-Fi already works !! Thank you.

 

[Lucky736]

Just to be clear, this has nothing to do with patched ROM but instead the absence of official Apple ROMs with APFS support.

I understand, but it made updating much easier on my end in Catalina and hoping it will do the same once Big Sur is working, was more commenting on the fact that their and my machines were very similar and am watching and waiting patiently.

 

[rayd8or]

Hi all, back here for the next round of tweaks and patches! I have an early 2011 15" Macbook Pro running Catalina beautifully thanks to dosdude1's excellent patcher. I have GPU disabled due to the well known GPU failure on these models.

I managed to install Big Sur Beta 1 in a new APFS volume. The Macbook will boot into both Catalina & Big Sur no problems.

However, I assume due to being a non-metal GPU, under Big Sur I have no Wifi, no sound, no sleep functions and when I try to use the menu bar at the top I get logged out everytime. Also some apps that came with Big Sur log me out too.

I'm sure the community will iron these out over time. It is only Beta 1 afterall.

Just so pleased I was able to at least boot into Big Sur on such an old machine. Here's to progress in the coming months.

 

[antony34]

Before re-install you could try to remove the BigSur snapshots (this should fix "sudo mount -uw /" too):

macOS 11 Big Sur on Unsupported Macs Thread

Hey everyone! After wasting half the day on this, I finally figured out one piece of the snapshots/error 66 puzzle. The TL;DR is that you can just call apfs_systemsnapshot -v /Volumes/... -r "" to boot from the live volume. I haven't seen this published anywhere yet, and the accepted wisdom...

forums.macrumors.com

tried. But it show “operation not permitted”

will it be cause in Disable ARV? Because I don’t know if I success to disable it or not..

 

[jackluke]

tried. But it show “operation not permitted”

will it be cause in Disable ARV? Because I don’t know if I success to disable it or not..

I guess ASentientBot refers to csrutil authenticated-root disable from an USB BigSur Installer recovery terminal.

Anyway I still can "sudo mount -uw /" (and mount BigSur System from HighSierra) even with that value enabled (I haven't neither disabled it from bigsur recovery after install).

 

[antony34]

I guess ASentientBot refers to csrutil authenticated-root disable from an USB BigSur Installer recovery terminal.

Anyway I still can "sudo mount -uw /" (and mount BigSur System from HighSierra) even with that value enabled (I haven't neither disabled it from bigsur recovery after install).

If there is, I think I better to reinstall system and try again from zero

Too many strange things need to figure out...and after that, need to test if Chinese and Japanese input still work in Penryn CPUs Mac

 

[brandonsierra]

I have a usb but its dead. Its the only usb we have and I don't have money for a new one, how will I create the Big Sur USB?