macOS 11 Big Sur on Unsupported Macs Thread

[justperry]

Tried in my mid 2012 MacBook Pro and still no wifi

Same on my 2012 Mac Mini
This command also does not work, I get no error, seems to be loaded but no Wifi.

sudo kmutil load -p /Library/Extensions/IO80211Family.kext

I get this in Network-Wifi, after a few seconds the button switches to Turn on, clicking
the button does not work.
This is the same behaviour as before installing the kext with Kext-Drop.App

 

[TimothyR734]

its a drag and Drop
marvelInjectos is just an exemple of draging kext

Its not test on unsupported Mac I wait for @TimothyR734 result
so don't use

so far I haven't made any progress on my mid 2009 iMac I created a bootable usb and OpenCoreAPFSloader booted into it reset the nvram then booted back into it selected the Big Sur usb got the black screen with apple log and progress bar then followed by the black screen white circle

 

[antony34]

Thanks all!

Finally got success to install Big Sur in MBP9,2 with clean installation.
But still got error -66 and manually fix the WiFi in recovery.

Will keep test with this machine 1st.

 

[justperry]

Here's the problem, it does not load, Kext loaded is from /System/Library/Extensions, it's the 1200.12.2b1 instead of the one installed in /Library/Extensions.
Top is /Library/Extensions, the one from Catalina
Second from top is /System/Library/Extensions
Bottom is System Report

 

[sinbad21]

Sorry for my English, in my iMac late 2012 macOS 11 is working very well. The only thing that does not work is the wifi, what file would I have to download and where to replace it to activate it? I have tried a Wifi AC USB and it works! but I don't have AirDrop and Handoff, I imagine these devices are not compatible to have AirDrop and Handoff. I would like to activate the wifi of the Mac to see if I have AirDrop and Handoff available. Thank you very much.

Hello, you have to copy the IO80211Family.kext of Catalina, which is in /System/Library/Extensions of Catalina, into the /System/Library/Extensions of Big Sur.

Follow this guide to mount Big Sur in r/w, then before replacing IO80211Family.kext of Big Sur rename it in IO80211Family.kext.backup :

cd <path to your mount point of Big Sur>/System/Library/Extensions
mv IO80211Family.kext IO80211Family.kext.backup

 

[jackluke]

so far I haven't made any progress on my mid 2009 iMac I created a bootable usb and OpenCoreAPFSloader booted into it reset the nvram then booted back into it selected the Big Sur usb got the black screen with apple log and progress bar then followed by the black screen white circle

Currently you can't boot an USB BigSur Installer (or continue a BigSur stage2 external USB installation) from a Mac with legacy IOUSB devices, instead you should install it with ASentientBot Hax3.dylib on internal disk, and then use my prelinkedkernel fix through usbopencore, or cloning a BigSur install on an external USB disk, and then you also can use prelinkedkernel fix on external already installed BigSur, it works even with legacy IOUSB .

 

[justperry]

Can't unload the System Kext
$ kmutil unload -p /System/Library/Extensions/IO80211Family.kext
Error: Kernel request failed: (libkern/kext) not privileged

 

[Payne Mononymous Bachman]

Mine too.

Followed basic steps to disable Library validation, used HAXDIB and Updated Catalina to BigSur. Natively, Every single thing works just better than Catalina. Late 2013 iMac 21.5"
[automerge]1593365837[/automerge]
Everything Works NATIVELY. Updated Catalina to Big Sur. Late 2013 iMac 21.5"
Superb!!!!! Why Apple doesn't support this Mac by default is my first question!!!
[automerge]1593366095[/automerge]



STEPS

1. Download InstallAssistant.pkg from http://swcdn.apple.com/content/down...kxzj3zjshu1srsh4n74a41n4/InstallAssistant.pkg

2. Download hax.dylib and copy to home folder https://forums.macrumors.com/attachments/really-simple-installer-hack-zip.926156/

3. Boot in recovery and disable sip with the " csrutil disable " command

4. Boot back into Catalina and open terminal then run " sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true "

5. Then Run " launchctl setenv DYLD_INSERT_LIBRARIES $PWD/Hax.dylib " in same terminal window

6. Then Run " sudo nvram boot-args="-no_compat_check" "

7. Open macOS Big Sur Installer

So glad to hear this works on the 21 inch iMAC 2013. Thanks also for putting the steps to do it.

 

[Payne Mononymous Bachman]

Just want to take a minute and thank everyone for there hard work. All of you and the work you do is amazing. Everyone keep up the great work and lets get this thing has a stable patcher just like dosdude1 catilina patcher. Also want to thank everyone for not giving up after all these years and continuing this project. It's also too bad I do not work for apple or I am not a high up person at Apple because if I was I would hire each and every one of you.

 

[justperry]

Disabling authenticated-root without USB or Big Sur recovery.

I have Big Sur installed, could not disable it in recovery, my mac does not have a recovery disk, I do have a TimeMachine backup recovery but even here the csrutil authenticated-root disable did not work, the command is not working on pre Sur installations.
What I did is rather complicated/convoluted.
I do have the Big Sur Installer downloaded, so...

1. I Mounted the BigSur Installer package contents/Contents/Sharedsupport.dmg
2. I then navigated to the com_Apple_mobileasset_MacsoftwareUpdate folder
3. Inside is a zip file, open it/expand it
4. Go to AssetData/Restore Inside the zip created folder
5. Mount the Basesystem.dmg
6. Copy csrutil from usr/bin and place it in a disk that you can acces from recovery
7. Restart into recovery (Catalina restore on my Timemachine)
8. Open terminal in recovery
9. Type /Volumes/Disk where you put the file/path to the csrutil binary* authenticated-root disable
* is a space
10. Done

****This is really not for noobs.

 

[Bravo2zero]

I've ran into a problem today.

I've installed Big Sur already on another HDD in the same machine ( internal SSD ) so i know how to install.

Right , I did a fresh install of catalina on USB SSD and the 2nd Internal SSD and both issue, I even did a time capsule and had same effect .

1. installed the OS fresh via USB installer & backup

2. did the utility dissable in recovery mode

3. checked in the OS to see if it was dissabled and it was

4. patched the Home with the file

5. coppied the text to terminal after entering password

6. machine locks up with spinning beach ball on installing the 20mb beta installer.

7. force restart of machine ( power button 10 seconds )

8. Beta installer now works

9. do all the terminal text again

10. run beta installer and the HDD's are greyed out

11. terminal still showing protection dissabled

12. try to access Home and spinning beachball again and nothing opens , safari displays no internet pages, system won't open , the machine is almost bricked feeling.

13. force restart press boot selection and boot from BS on the other HDD installed and all is fine.

 

[Alex-Microsmeta]

From your device list I don't notice any USB flash drive plugged, if your "Install macOS Beta" is a BigSur installer then try to make USBopencore selecting it and use this option "Near an USB device without erasing"

Thank you, The USB patcher worked renaming the 16 gb USB pendrive from macOS Beta installer to USBOpenCore Now I use it to try to install BS for the 6th time.

 

[jackluke]

Thank you, The USB patcher worked renaming the 16 gb USB pendrive from macOS Beta installer to USBOpenCore Now I use it to try to install BS for the 6th time.

If you have BigSur already installed, no need to re-install just replace these files (from Catalina):

diskutil mount Preboot
diskutil apfs list
open /Volumes/Preboot/

locate your UUID for "BigSur - Data Volume", then replace these:

patched prelinkedkernel.zip beta1

And replace it here: /Volumes/Preboot/UUID-BigSur/System/Library/PrelinkedKernels/

together with this BigSur prelinkedkernel fix.zip

to copy here: /Volumes/Preboot/UUID-BigSur/System/Library/CoreServices/

Then after power-on alt-option key and select usbopen to boot your "BigSurLabel - Data".

These should work even with a sealed BigSur system with snapshot booting.

 

[justperry]

The mount point is anything you choose. Once you've got the live mount at /path/to/mntpoint

I try to mount the filesystem, it says I can use anything I want, nothing seems to work.
What is .../path/to/mntpoint
What should I put there?

$ sudo mount -o nobrowse -t apfs /dev/disk2 /Users


Password:


mount_apfs: volume could not be mounted: Resource busy

 

[jackluke]

$ sudo mount -o nobrowse -t apfs /dev/disk2 /Users


Password:


mount_apfs: volume could not be mounted: Resource busy

from BigSur terminal type: mount to detect the root mount point of your BigSur System (snapshot) example a generic "diskXsYsZ"

so since "sZ" is a "locked snapshot" (from where you are booting) you should type:
sudo mount -o nobrowse -t apfs /dev/diskXsY /Volumes/AnyDiskLabel/AnyEmptyFolder/

You can't use /Users/ folder as mount point because is busy of course it's using your current user and "disk2" is incorrect also /dev/disk2 is busy (I guess it's your BigSur APFS container), you should specify the partition example "disk2s3".

Once you mounted the System Volume (non-snapshot), then you can replace your kext and make a new snapshot of it.

 

[Allan Fox]

just found something out any other application that asks for camera or microphone access doesn't appear on big sur
system preferences

 

[Cindy_Thornton]

I updated my 2006 to catalina so why can’t it run big sur why is it under unsupported machines

 

[nitinnk]

Thank you very much to everyone, I finally managed to fix the wifi on my macbook pro 13 "mid 2012 following the method in this link: https://medium.com/@andv/making-wif...d-macs-with-failed-with-66-error-36c98e3f7965

THANK YOU VERY MUCH TO EVERYONE!!!🥵😬🤟🎊🎉

 

[TimothyR734]

[automerge]1593658739[/automerge]
I removed my ssd from my MacBook 5,2 and hooked it up to my iMac 13,1 successfully install macOS Big Sur used the Kext-Droplet for the 1080211Family.kext but still not detecting my wifi card but I am happy I got installed

 

[maxsp97]

I updated my 2006 to catalina so why can’t it run big sur why is it under unsupported machines

You should wait for dosdude1 Big Sur patch.

 

[Minh_Ton]

@jackluke For the getting BaseSystem to boot with LegacyUSBInjector.kext embedded in BootKernelExtensions.kc method, the USB Installer cannot reach the "RecoveryOS" when using a BootKernelExtensions.kc file from the complete install of Big Sur. It simply mounts and boots from BaseSystem when the computer startup (because using ls / in single-user mode shows the BaseSystem root files), and somehow after typing exit, it tries to draw the UI of the "RecoveryOS" thing after a couple of seconds, but unable to and it keeps trying again until a timeout and got hang there. I tried replacing the BootKernelExtensions.kc file in /Volumes/USBInstaller/System/Library/KernelCollections as well as modifying BaseSystem.dmg or trying to add it to the BaseSystem Preboot volume, but still got a timeout. I think BootKernelExtensions.kc file from the complete installation of Big Sur can't be replaced the one in the USB installer or BaseSystem.... So somehow we have to embed LegacyUSBInjector.kext inside the BaseSystem BootKernelExtensions.kc file instead of the one from the complete installation.

Correct me if I'm wrong (just base on verbose log)

 

[Barry K. Nathan]

I removed my ssd from my MacBook 5,2 and hooked it up to my iMac 13,1 successfully install macOS Big Sur used the Kext-Droplet for the 1080211Family.kext but still not detecting my wifi card but I am happy I got installed

I would expect the Kext-Droplet to work for 3rd party kexts in general, but not for replacing Apple's own. It's definitely not going to work for IO80211Family or AppleHDA. It's not so much that it doesn't work on unsupported Macs as it simply does things the wrong way for the kinds of kext installations we unsupported Mac users generally need.

Edit to clarify: I wouldn't be surprised if the Kext Droplet works for adding a driver for USB WiFi, but I don't think it'll work for any of the internal devices that Apple dropped in Mojave/Catalina/Big Sur. (I'll have a lot more to say soon, probably in the next few days, about this topic of kext installation.)

 

[TimothyR734]

I would expect the Kext-Droplet to work for 3rd party kexts in general, but not for replacing Apple's own. It's definitely not going to work for IO80211Family or AppleHDA. It's not so much that it doesn't work on unsupported Macs as it simply does things the wrong way for the kinds of kext installations we unsupported Mac users generally need.

Edit to clarify: I wouldn't be surprised if the Kext Droplet works for adding a driver for USB WiFi, but I don't think it'll work for any of the internal devices that Apple dropped in Mojave/Catalina/Big Sur. (I'll have a lot more to say soon, probably in the next few days, about this topic of kext installation.)

I even found an ethernet cable long enough to reach my router but in Catalina as well as Big Sur it says I have a self assigned IP address therefore I can't connect to the Internet. I can turn on my wifi in Big Sur but its not seeing the network which is Eero

 

[Barry K. Nathan]

I even found an ethernet cable long enough to reach my router but in Catalina as well as Big Sur it says I have a self assigned IP address therefore I can't connect to the Internet. I can turn on my wifi in Big Sur but its not seeing the network which is Eero

Have you tried restarting the router? I know that sounds dumb but I've seen cases where routers start doing weird stuff with DHCP reservations after a while and restarting the router fixes it, and your Ethernet cable symptoms sound like they might be consistent with that scenario. (That might not fix WiFi, but having the Ethernet cable working would be better than nothing.)

 

[jackluke]

just found something out any other application that asks for camera or microphone access doesn't appear on big sur
system preferences

That's a tccutil issue, but easily fixable, from BigSur terminal type: nvram boot-args

if you have "-no_compat_check amfi_get_out_of_my_way=1", you should remove "amfi_get_out_of_my_way=1" that is only required to use the hax.dylib or eventually kext and framework patches for non-metal mac.

From a macOS Recovery type : nvram boot-args="-no_compat_check"

Otherwise you could add manually the third party app permissions using this: tccplus wrapper
[automerge]1593671279[/automerge]

@jackluke For the getting BaseSystem to boot with LegacyUSBInjector.kext embedded in BootKernelExtensions.kc method, the USB Installer cannot reach the "RecoveryOS" when using a BootKernelExtensions.kc file from the complete install of Big Sur. It simply mounts and boots from BaseSystem when the computer startup (because using ls / in single-user mode shows the BaseSystem root files), and somehow after typing exit, it tries to draw the UI of the "RecoveryOS" thing after a couple of seconds, but unable to and it keeps trying again until a timeout and got hang there. I tried replacing the BootKernelExtensions.kc file in /Volumes/USBInstaller/System/Library/KernelCollections as well as modifying BaseSystem.dmg or trying to add it to the BaseSystem Preboot volume, but still got a timeout. I think BootKernelExtensions.kc file from the complete installation of Big Sur can't be replaced the one in the USB installer or BaseSystem.... So somehow we have to embed LegacyUSBInjector.kext inside the BaseSystem BootKernelExtensions.kc file instead of the one from the complete installation.

Correct me if I'm wrong (just base on verbose log)

Do you restored the BaseSystem.dmg (740 MB) to an empty Volume before using the patched boot.efi and BootKernelExtensions.kc ?

I guess after restoring BaseSystem could be possible to rebuild a kextcache (kmutil) from BaseSystem single user mode.

Since on / BaseSystem.dmg mounted / macOS Base System / System / Library / KernelCollections /

there are also BaseSystemKernelExtensions.kc maybe are used also these.

Anyway the fact that BaseSystem has its Preboot Volume makes it harder, also to make a BigSur Patcher.