How did you manage to do that. I keep getting the BIE error thing
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
I've updated my script, run "git pull" in the script folder and try running it again.
This was right thing to happen and you are meant to trick NVRAM to not check the compatibility! Could be done via Terminal from macOS Catalina reinstall drive or perhaps - recovery option.
Just let it reboot, then push option key and open Terminal from recovery option and type nvram boot-args="-no_compat_check" would fix the issue.
Progress was made. Thank you
Attachments
Big picture question. If we are able to install the Big Sur beta using the method discussed here, will future updates from Apple be applied automatically via System Update or will we have to patch it every time there is a new beta or release?
I am currently using patched Mojave software and have used patched Catalina and High Sierra but in my experience, I needed to patch manually whenever there's new update available (and I prefer that way anyway, just for in case. If the software update method has risk messing around with the drivers, NVRAM or such, it will waste such a time to be figured out.)
I could either transfer my data from another Mac or create the time machine shadow and those two methods have restored my data perfectly so far - although it is just a personal opinion based on experience.
I'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
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
This is absolutely remarkable! Thanks very much
Will perhaps try on one of my MacBook anytime soon.
Finally after all the errors it threw at me. It took about 15 minutes to install. Runs pretty damn good on a mid 2012 MacBook Pro. WiFi doesn’t work. But I still don’t understand why Apple would kill these devices if these devices can handle the software
Attachments
Sound on my 2011 MacBook Pro now works with external speakers. Internal speakers are not currently working. This also means USB works.
Checked AirDrop, iMessage and Facetime, all working.
Imac 2010 with upgraded gpu to GTX 770m
After installing Mac OS Big Sur to the hard drive the screen turns black with no responds
Can you please help, thank you.
After installing Mac OS Big Sur to the hard drive the screen turns black with no responds
Can you please help, thank you.
I have same error, start recovery, open terminal and enter "nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1" Then reboot and install will continue.
If Apple called it PowerPC 2, PowerMac G5 owners would come out of the woodwork and demand support! HAHA!
I just installed it on my iMac Late 2013 and got it working completely at the first attempt without doing any extra steps apart from using the script mentioned before in this forum. It is working really well for now and it has given me an extra bit of hope since apple should reconsider including this model on the final release.
Thanks for the link. Yes, Windows 10 runs on ARM PCs, like Microsoft's Surface Pro X, so it should run fine on Apple Silicon based Macs. So those who Boot Camp should have nothing to fear. The Boot Camp utility is still present in Big Sur.
Meet the new Surface Pro 11th Edition, a Copilot+ PC | Microsoft Surface
New Surface Pro 11th Edition, a Copilot+ PC is designed to pack ultra-powerful AI-acceleration into an ultra-portable laptop. Get to know the most powerful 2-in-1 laptop.www.microsoft.com
Sorry, but unless Apple changes its current plans, the Bootcamp Utility will no longer work on Apple Silicon, only x86 Macs. As for Windows on ARM, well, none of your existing x86 Win10 apps will work unless you can purchase the same program from the developer or Microsoft on ARM. This will be too much of a burden for most corporations to bother to trust Apple again in my opinion and they will stop allowing purchases of Macs. I'm talking about companies that rely heavily on a Windows environment.
@ASentientBot @jackluke @Darkdes @TimothyR734 @libneko Managed to start installation of Big Sur on Macmini 2010, but USB mouse (wired or not) and keyboard do not work while changing on black screen (macOS 11 keeps asking me to connect them) They are ok with Catalina and during boot selection (pressing ALT) I have read other on reddit with the sane issue,... Any fix to suggest? Thanks ?
There was some info in the topic about kext required for it
[automerge]1593014968[/automerge]
Updated my mac mini 2012 guide with info about wifi:
How to install Big Sur to Mac Mini Late 2012
With the new release of Big Sur, apple have dropped my “brand new” Mac Mini Late 2012, so that’s how I made it work with the help of…
Lol I was thinking thank you and put thanks on the end of that ?big-sur-plz
[automerge]1593015147[/automerge]
I’ll be trying this again on my 2009 MacPro when I get home from work. Thanksbig-sur-plz
2009 may require telemetry removal and a little bit different boot args, lurk on the first pages
For enabling Wifi 802.11n on any 2012 Mac or any other unsupported Big Sur but supported Catalina Mac (in few words those who use the AirPortBrcm4360 driver), this will work:
macOS 11 Big Sur on Unsupported Macs Thread
Here is my IO80211Family kext version 12.0 if you wan to try it. Of course I'm using an Atheros card at the moment, all my MBPs have been upgraded to the BCM94360 from @troop231 i'll try a Mac mini once I get ahold of one. A New (Fixed) Airport Kext has been updated to fix BCM94360/BCM943602...forums.macrumors.com
To install it properly, simply open a BigSur terminal and copy paste (one line at once) :
Code:sudo mount -uw / ; killall Finder cd /System/Library/Extensions/ sudo mv IO80211Family.kext IO80211Family.backup open /System/Library/Extensions/ copy using Finder the IO80211Family.kext from the link attached return to BigSur terminal and continue typing: sudo -s chown -R 0:0 /System/Library/Extensions/ chmod -R 755 /System/Library/Extensions/ kmutil install --update-all kcditto
At next reboot you should have a working Wifi 802.11n and a working AirDrop channel.
Great news, exactly what I've been waiting for. Thanks! Will join the party now with the @ASentientBot method.
Attachments
Your description of the the issue is vague, but like with Catalina AppleGraphicsControl/AppleGraphicsDevicepolicy you needs patching for the board IDs. You can use AppleBootPicker to boot the OS and extract/edit/reinstall the Kext.
I'm not going to plz-Bro everyone for the next 9 Beta Releases and repatch/upload the Kext for everyone, it's an easy Kext edit, you will see where you need to re-add your Macs board ID.
Oh and this isn't the MXM thread either.