That was made by GameRoof who is in this thread
I just stumbled across this. Maybe it helps?
That was made by GameRoof who is in this thread
I just stumbled across this. Maybe it helps?
Yes, this is true, the BCM94360.kext plugin is not needed in my IO80211Family.kext, this was my wake from sleep issues on the Mac Pro 5,1. However I'm unable to continue testing at the moment because I cannot mount my boot partition (sudo mount -uw /) anymore for modifications, error 66 of course, so can't test or install.
TLDR: IO80211Family now uses AirPortBrcmNIC for the 4360.
I'm looking in Disk Utility, and when a reinstall occurred, it's now using the -Data partition as the boot disk, very strange, I think I need to erase and redo this install.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel Cache</key>
<string>boot\System\Library\KernelCollections\BootKernelExtensions.kc</string>
<key>Kernel Flags</key>
<string></string>
</dict>
</plist>
sudo bless --folder /Volumes/YourBigSurLabel/System/Library/CoreServices --label "YourBigSurLabel"
diskutil apfs updatePreboot /Volumes/YourBigSurLabel/
From USB BS Installer Recovery Terminal:try directly from USB BigSur Installer recovery terminal:mount -uw /Volumes/YourBigSurLabel/
or maybe open first the "recovery DiskUtility" and mount your BigSur System (not Data volume), then close (without exit from recovery) and retry from recovery terminal.
diskutil mount disk2s5
Volume Big Sur on disk2s5 mounted
mount -uw /Volumes/Big\ Sur/
mount: unknown special file or file system /Volumes/Big Sur/.
csrutil status
. I tried running csrutil disable
& csrutil authenticated-root disable
but it was still enabled after reboot.sudo /Applications/Install\ macOS\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/Install\ macOS\ Beta
and cleared the NVRAM variables: nvram -c
.nvram boot-args="no_compat_check amfi_get_out_of_my_way=1"
./Volumes/Big\ Sur/System/Library/UserEventPlugins/com.apple.telemetry.plugin
.From USB BS Installer Recovery Terminal:
diskutil mount disk2s5 Volume Big Sur on disk2s5 mounted
mount -uw /Volumes/Big\ Sur/ mount: unknown special file or file system /Volumes/Big Sur/.
SIP was enabled according tocsrutil status
. I tried runningcsrutil disable
&csrutil authenticated-root disable
but it was still enabled after reboot.
Now, my external BS recovery boots to a circle-backslash ? symbol.
I made new BS recovery with
sudo /Applications/Install\ macOS\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/Install\ macOS\ Beta
and cleared the NVRAM variables:nvram -c
.
Then, proceeded to add the NVRAM boot arguments:nvram boot-args="no_compat_check amfi_get_out_of_my_way=1"
.
USB Big Sur Recovery still won't boot. I can't make the system volume writable anyway, so I'm unable to remove/Volumes/Big\ Sur/System/Library/UserEventPlugins/com.apple.telemetry.plugin
.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel Flags</key>
<string>root-dmg=file:///BaseSystem/BaseSystem.dmg -no_compat_check cs_enforcement_disable=1 cs_debug=1 amfi_allow_any_signature=1 amfi_get_out_of_my_way=1</string>
</dict>
</plist>
From USB BS Installer Recovery Terminal:
diskutil mount disk2s5 Volume Big Sur on disk2s5 mounted
mount -uw /Volumes/Big\ Sur/ mount: unknown special file or file system /Volumes/Big Sur/.
mount -uw "/Volumes/Big Sur"
You beat me to this post by 7 min.Dr. Oakley explains a lot of the observations being made here. - https://eclecticlight.co/2020/06/24/big-sur-and-apple-silicon-interesting-times-ahead/
sudo ~/Downloads/Install\ macOS\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/Install\ macOS\ Beta
boot-args no_compat_check amfi_get_out_of_my_way=1
. I don't know how to fix this one…no need for apologies at all! making the sausage is always ugly... praise to you for a very early method of installing on unsupported devices. Making all of this easy for patcher utilities is just another challenge, but apple crypto is surely not making this any easier.Nope. And just updating them to add the missing symbols isn't sufficient.
I've only barely worked on that though, because I can't figure out how to reliably disable this stupid snapshots/sealing stuff. Getting different results each time I install, posting patcher scripts that turn out not to work... this is frustrating and embarrassing, haha. I'm tempted to switch to the OpenCore method, but would also like to get to the bottom of this.
I sent you a DM and a copy of SKYlight from Catalina and BSno need for apologies at all! making the sausage is always ugly... praise to you for a very early method of installing on unsupported devices. Making all of this easy for patcher utilities is just another challenge, but apple crypto is surely not making this any easier.
BS is a major release, the old CoreDisplay and Skylight wrapper approach for non-metal GPUs may no longer be sufficient. I think Apple has upped the ante even more with full metal support across the entire os - dropping whatever backwards compatibility gl hooks existed in CAT and below. I'm not surprised that old gl frameworks are still distributed , but have you had a chance to otool some critical libraries to check for gl framework links? Would be interesting to know which graphic libs actually still reference the gl dylibs...
Arghhh binaries in dyldcache now! This is looking more and more like iOS iPadOS...I sent you a DM and a copy of SKYlight from Catalina and BS
I hope it does help seeing as I made it hahah
I just stumbled across this. Maybe it helps?
When I run that command replacing ... with the name of my volume, I get "command not found apfs_systemsnapshot".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 callapfs_systemsnapshot -v /Volumes/... -r ""
to boot from the live volume. I haven't seen this published anywhere yet, and the accepted wisdom seems to be that you can't boot the live volume in BS. Hopefully this method will continue to work. It will make patching much easier.
Long version:
- disable SIP, including ARV (funnily enough, my very earlyEdit: posted the new patch)boot.efi
patch with all the 0xffffffffs actually works for this, even though @dosdude1's 0x67 one does not
- boot into Big Sur or a BS recovery/install disk
-diskutil mount diskXsY
the real system volume (not the root snapshot, which will already be mounted atdiskXsYsZ
)
- find the path to the mounted volume (if you're booted into the same system, it will bevolume_name 1
because of the previously mounted snapshot)
-/S*/L*/F*/apfs.fs/C*/R*/apfs_systemsnapshot -v "/Volumes/volume_name" -r ""
- reboot
-mount -uw /
should now work, changes will apply immediately to the live volume, and you can remove all the snapshots withdiskutil apfs deletesnapshot
if desired
(I spent ages reverse engineeringapfs_systemsnapshot
and learning about thefs_snapshot_*
functions before realizing you could just call the tool with an empty string. But if anyone is interested in the code for programmatically managing snapshots, I am happy to share it.)
Thanks to @mac_4eva/this post for the starting point.
One remaining mystery is figuring out how to mount the BS root from Cat. With the sealing/snapshots disabled, I don't see any reason why it shouldn't be possible.
I hope this works for others!
Couldn't agree moreArghhh binaries in dyldcache now! This is looking more and more like iOS iPadOS...
When I saw that part of the release notes, I interpreted it differently -- I figured "temporarily" meant "until the kernel extension developers get their act together and release updated software" (think of 3rd-party hardware or software that requires kernel extensions).You miss the point. Currently Big Sur already requires SIP to be disabled in order to allow unsupported legacy kernel extensions to load. If that gets removed by Apple, one would likely have to hack code that loads very early and which probably has some serious signing requirements imposed upon it. Good luck with that.
Wow. It never occurred to me before that the different components of a Universal binary could be built using different SDKs. (There's plenty of other interesting stuff in that blog post, but I personally found that to be the most interesting bit.)Mr. Kaiser has noticed something very interesting about Universal Binaries and Rosetta 2 in Big Sur. https://tenfourfox.blogspot.com/2020/06/the-super-duper-universal-binary.html
I don't think lack of EFI updates should be a problem. I think the csrutil stuff is being handled by the kernel and not EFI. (For example, as I mentioned in post #725, I can manipulate the csrutil status directly using the nvram command if I reboot into Recovery from Mavericks or earlier. If it was being handled by EFI, I think rebooting into Mavericks recovery wouldn't let me manipulate it using the nvram command.)To fix the "BigSur mount -uw /" I read many (even on other forums) suggested to enter the USB BigSur Installer or Recovery and typing:csrutil authenticated-root disable
My question is, are they sure that this is effective without a BigSur EFI firmware update ?
I mean,csrutil disable
surely works on "El Capitan Supported Mac" because they received an El Capitan EFI firmware update, but about this "new BigSur csrutil", I guess, maybe wrongly, that is useless on unsupported BigSur Mac.
This was a painful fix. But I got to say it worksI've finished my guide on making wifi work with "failed with 66" error.
DO IT ON YOUR OWN RISK. THERE IS HIGH CHANCE OF DAMAGING YOUR OS AND HARDWARE.
NEVER DO IT ON MACHINE THAT HAS IMPORTANT DATA.
I'M NOT RESPONSIBLE FOR ANY DAMAGES, IT ALL ON YOU.
THE PROCESS IS COMPLICATED.
Huge thanks to @mac_4eva, @jackluke and @highvoltage12v for their research and hints.
Enjoy: https://medium.com/@andv/making-wif...d-macs-with-failed-with-66-error-36c98e3f7965
/Applications
.mv ~/Downloads/Hax.dylib ~/
csrutil disable
sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true”
launchctl setenv DYLD_INSERT_LIBRARIES ~/Hax.dylib
. This allows you to force install BS without getting "The operation couldn't be completed (BIErrorDomain Error 3)".sudo nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"
in the Terminal. These boot arguments stop the compatibility being checked and disables AMFI (Apple Mobile File Integrity – stops you running unsigned code)sudo ~/Downloads/Install\ macOS\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume
/Volumes/Install\ macOS\ Beta/Library/Preferences/SystemConfiguration/com.apple.Boot.plist
Open the com.apple.Boot.plist
file, using TextEdit is convenient. Use Shift+Command+Dot to enable/disable the showing of all hidden files (as it is a hidden file). Change the file to be like @jackluke's version, and save:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel Flags</key>
<string>root-dmg=file:///BaseSystem/BaseSystem.dmg -no_compat_check cs_enforcement_disable=1 cs_debug=1 amfi_allow_any_signature=1 amfi_get_out_of_my_way=1</string>
</dict>
</plist>
10 • Boot into your BS external installer. Check the SIP & NVRAM's boot args if needs be.…the boot System volume isn’t protected by SIP any more, but is a cryptographically signed APFS snapshot. You can’t just disable SIP and mount the System volume for writing, and there’s no way to boot a live System volume which you can write to. Instead, if you need to make changes to the contents of the macOS System volume, you’ll need to disable its authentication in Recovery Mode, mount it, make any changes, create an APFS snapshot, then use that to boot from. Step-by-step instructions for doing this will no doubt emerge in coming days…
diskutil list
and mount the BS system volume. In my case, it was diskutil mount disk2s5
. It's probably already mounted, but we're precise mount -uw "/Volumes/Big Sur"
. Use quotation marks (") as @ricoc90 pointed out. Otherwise, it will say the disk is a special or unknown file system. cd /Volumes/Big\ Sur/System/Library/UserEventplugins
. You can delete the file with rm -r
or just rename it mv com.apple.telemetry.plugin com.apple.telemetry.plugin2
diskutil list
to find the volume, and then mount the Preboot volume: diskutil mount diskXsY
.com.apple.Boot.plist
files to match the code below – located at:/Volumes/Preboot/UUID-BigSurData/Library/SystemConfiguration/com.apple.Boot.plist
/Volumes/Preboot/UUID-BigSurData/Library/Preferences/SystemConfiguration/com.apple.Boot.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel Cache</key>
<string>boot\System\Library\KernelCollections\BootKernelExtensions.kc</string>
<key>Kernel Flags</key>
<string>-no_compat_check amfi_get_out_of_my_way=1</string>
</dict>
</plist>
/Volumes/Preboot/UUID-BigSurData/System/Library/CoreServices/
.com.apple.Boot.plist
files:/Volumes/Preboot/UUID-BigSurData/Library/SystemConfiguration/com.apple.Boot.plist
/Volumes/Preboot/UUID-BigSurData/Library/Preferences/SystemConfiguration/com.apple.Boot.plist
/Volumes/Preboot/UUID-BigSurData/System/Library/CoreServices/
<string>boot\System\Library\KernelCollections\BootKernelExtensions.kc</string>
<string>System\Library\PrelinkedKernels\prelinkedkernel</string>
in all 3 plists*Internal Audio Devices & Graphics Acceleration in progress*I just made a new prelinkedkernel fix that should work for any "non-APFS and legacy USB Mac", it works without opencore, it includes the AppleHDA.kext (HighSierra) the patched IO80211Family.kext (for AirPortBrcm4331 Wifi cards) and Ethernet for Nvidia chipset Mac.
To install it directly from BigSur use the "BigSur prelinkedkernel fix4", from other APFS macOS use the "prelinkedkernel fix4 beta1", otherwise you can also replace it manually.
How old are you?That's why I said possibly longer than 2 years. Geez.
Just to say, I'm 18.How old are you?