Once installed, in the next betas you only have to update from the configuration?
What is the point of eliminating telemetry?
What is the point of eliminating telemetry?
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
You should make from the "Install macOS Beta.app" createinstallmedia an external USB BigSur Installer, that is a recovery environment that includes the new csrutil and the new kmutil, and maybe other new BigSur terminal commands.
Code:
sudo /Applications/Install\ macOS\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/USBLabel/Only Penryn Core2Duo cpus needs to remove it due to a kernel panic loop.
I've successfully installed Big Sur on my late 2013 iMac with 1TB Fusion Drive. It seems to work just as well as Catalina. Wifi works, GPU works, Audio works, AirDrop works, AirPlay works.
It even still supports Enable HiDPI Mode
sudo defaults write /Library/Preferences/com.apple.windowserver.plist DisplayResolutionEnabled -bool true
so I can run at 1280 x 720 HiDPI resolution on my 1920x1080 21.5" iMac. I enable this resolution with Retina display manager. https://github.com/avibrazil/RDM
So I cannot understand why they dropped support. I've booted back into Catalina to make this post just to make sure it still runs. It does.
It works so similar to Catalina it even has the same quirks such as Safari rendering bugs on a few sites like MacRumors. Just happens randomly. Most of the time it's fine.
Overall it seems like it's just Catalina under the hood as far as Intel is concerned with a face lift. Shame really, I was hoping for some major fixes to Catalina's rough performance. They've gone for a slightly retro look with hints of Mac OS 7,8,9.
A few issues I've noticed:
DVD player I just get a grey screen. The TV app and YouTube on Safari both work perfectly in HD resolutions. So it isn't a graphics issue. I suspect its a mpeg codec license issue.
Updates
Does swscan.apple.com block updates for unsupported Macs?
iMac Late 2013 Install
Here's how I managed to install on my iMac 2013 with Fusion Drive. All credits to previous posters.
Original by rapsong11
"Here are the steps I used to get the beta installed on a 2013 27 inch iMac
(I made a new partition for this install I recommend you guys do the same!) I also highly recommend this step. Don't add a new volume to the APFS Container which holds your Catalina install. Can cause problems with Catalina. Use Disk Utility to create a new partition, give it time to resize your APFS Container - took about half hour for me. I gave Big Sur partition 200gb to be on the safe side.
1. Download pkg from http://swcdn.apple.com/content/down...kxzj3zjshu1srsh4n74a41n4/InstallAssistant.pkg
2. Download https://forums.macrumors.com/attachments/really-simple-installer-hack-zip.926156/
3. Copy hax.dylib to home folder (important for step 8 terminal command that uses $PWD present working directory default is your home folder)
4. Boot into recovery - hold CMD-R at boot
5. Run csrutil disable in Terminal in recovery. You can check in Catalina by running csrutil status
6. Also run this command in the terminal in recovery: nvram boot-args="-no_compat_check"
7. Reboot and run this in Terminal while on current OS -
sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true
8. Run this in terminal
launchctl setenv DYLD_INSERT_LIBRARIES $PWD/Hax.dylib
If you get BIErrorDomain error 3 when running the install macOS Beta app at the select disk stage.
"BIErrorDomain 3" is the new installer (written in Objective-C and part of an InstallAssistant internal framework, rather than JavaScript in OSInstall.mpkg/Distribution as previously) check's way of saying that the system is unsupported. In the context of my (rather ridiculously named) Hax.dylib, it means that didn't get injected into the relevant InstallAssistant daemon for some reason (probably Library Validation is enabled).
You probably rebooted without running the Install macOS Beta.app so you will have run the previous two terminal commands steps 7 and 8 again before trying the installer again. This error happened to me as well and this fixed it.
9. Run the InstallAssistant.pkg which creates Install macOS Beta.app and then run /Applications/Install macOS Beta.app
10. The installer will run and ask you for the disk to install on. Choose the partition you created earlier in disk utility. The installer will begin and reboot a couple of times then finally boot in Big Sur. I ran it late at night when sleeping. I can only say it took less than two hours to install on my Fusion Drive.
It even still supports Enable HiDPI Mode
sudo defaults write /Library/Preferences/com.apple.windowserver.plist DisplayResolutionEnabled -bool true
so I can run at 1280 x 720 HiDPI resolution on my 1920x1080 21.5" iMac. I enable this resolution with Retina display manager. https://github.com/avibrazil/RDM
So I cannot understand why they dropped support. I've booted back into Catalina to make this post just to make sure it still runs. It does.
It works so similar to Catalina it even has the same quirks such as Safari rendering bugs on a few sites like MacRumors. Just happens randomly. Most of the time it's fine.
Overall it seems like it's just Catalina under the hood as far as Intel is concerned with a face lift. Shame really, I was hoping for some major fixes to Catalina's rough performance. They've gone for a slightly retro look with hints of Mac OS 7,8,9.
A few issues I've noticed:
DVD player I just get a grey screen. The TV app and YouTube on Safari both work perfectly in HD resolutions. So it isn't a graphics issue. I suspect its a mpeg codec license issue.
Updates
Does swscan.apple.com block updates for unsupported Macs?
iMac Late 2013 Install
Here's how I managed to install on my iMac 2013 with Fusion Drive. All credits to previous posters.
Original by rapsong11
"Here are the steps I used to get the beta installed on a 2013 27 inch iMac
(I made a new partition for this install I recommend you guys do the same!) I also highly recommend this step. Don't add a new volume to the APFS Container which holds your Catalina install. Can cause problems with Catalina. Use Disk Utility to create a new partition, give it time to resize your APFS Container - took about half hour for me. I gave Big Sur partition 200gb to be on the safe side.
1. Download pkg from http://swcdn.apple.com/content/down...kxzj3zjshu1srsh4n74a41n4/InstallAssistant.pkg
2. Download https://forums.macrumors.com/attachments/really-simple-installer-hack-zip.926156/
3. Copy hax.dylib to home folder (important for step 8 terminal command that uses $PWD present working directory default is your home folder)
4. Boot into recovery - hold CMD-R at boot
5. Run csrutil disable in Terminal in recovery. You can check in Catalina by running csrutil status
6. Also run this command in the terminal in recovery: nvram boot-args="-no_compat_check"
7. Reboot and run this in Terminal while on current OS -
sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true
8. Run this in terminal
launchctl setenv DYLD_INSERT_LIBRARIES $PWD/Hax.dylib
If you get BIErrorDomain error 3 when running the install macOS Beta app at the select disk stage.
"BIErrorDomain 3" is the new installer (written in Objective-C and part of an InstallAssistant internal framework, rather than JavaScript in OSInstall.mpkg/Distribution as previously) check's way of saying that the system is unsupported. In the context of my (rather ridiculously named) Hax.dylib, it means that didn't get injected into the relevant InstallAssistant daemon for some reason (probably Library Validation is enabled).
You probably rebooted without running the Install macOS Beta.app so you will have run the previous two terminal commands steps 7 and 8 again before trying the installer again. This error happened to me as well and this fixed it.
9. Run the InstallAssistant.pkg which creates Install macOS Beta.app and then run /Applications/Install macOS Beta.app
10. The installer will run and ask you for the disk to install on. Choose the partition you created earlier in disk utility. The installer will begin and reboot a couple of times then finally boot in Big Sur. I ran it late at night when sleeping. I can only say it took less than two hours to install on my Fusion Drive.
Last edited:
I tried to install it on a MacBook Air 13" 2012.
The install process worked, (reboot, update the EFI or something (big progress bar), reboot, 9minutes left, reboot) and got the screen below unfortunately.
Any idea what's this mean and/or if there is a way to get Big Sur on MacBook Air?
I'm going to do a recovery, and re-install macOS for now
The install process worked, (reboot, update the EFI or something (big progress bar), reboot, 9minutes left, reboot) and got the screen below unfortunately.
Any idea what's this mean and/or if there is a way to get Big Sur on MacBook Air?
I'm going to do a recovery, and re-install macOS for now
hey, I can't manage to mount the system as read write, even after I disabled the csrutil authenticated-root thing. it gives me an error 66 help!!
How about look and feel without graphic acceleration in macOS 11
ok for me so for, everything to do with native appage works! now for the bad news some third party apps just don't works? yet at least. either when one clicks on the app nothing happens or apple asks you you to send an error report. any who, i will be sticking with the Big Sur. i attached a pic of one app that i use rarely that doesn't work. I'm sure all it needs and update. happy hunting
Attachments
Hi!
Edit.. After a reboot now It works, but now It gives me the BlErrorDomain error 3... I'll search the workaround here ?
Following your Big Sur install tutorial, after disabling SIP and rebooting, install Catalina Beta.app in Applications folder starts, but after a while a messagebox alerts me: ":Installation requires downloading important content. That content can't be downloaded at this time. Try again later" Any Idea about how to fix?
Regards, Alex
Last edited:
Hello everybody,
how long do you think will be supported let's say current Intel Macs, I mean even these in stores right now? I mean they are pretty obsolete already, right?
how long do you think will be supported let's say current Intel Macs, I mean even these in stores right now? I mean they are pretty obsolete already, right?
I got Big Sur installed on my Late 2012 Mac Mini. I used the A1425 guide. Everything seems to work except for wifi.
Why would you be installing Catalina Beta when this is Big Sur Beta?
Intel Macs should be supported for at least a couple more years and probably longer than that.
I take it the lack of Wifi means no Airdrop support then?
Sorry, guys, I'm new to the world of unsupported Macs. I've got a 2012 MacBook Pro no Retina...when's the patcher coming out? I don't want to throw it away because I just put in a 1TB SSD. Thanks, have a good day
Well, if it is only two years, I can picture all those who bought the 2019 macpros, having spent five figures, foaming, getting possessed by the devil...
Everyone who can't solve "failed with 66", start making bootable Big Sur USB installers, wifi guide is in progress
Although I can confirm that Mac mini (Late 2012, i5 with 16GB RAM) is capable running macOS Big Sur - with hardware acceleration working without further driver migration task, I decided to just go back to Catalina just because the process called 'secd' keep (wastes) uses nearly 80% of CPU. This keep happens even if I clean install, so maybe it is something to do with the unstableness of beta version.
And I found the only thing that is not working in the Mac mini is Wi-Fi so far, but in my case, I couldn't really confirm the patches and custom .kext driver as my system drive stays read-only status even though I've tried basically everything I can possibly do (also perhaps I wasn't really as desperate as I would normally do as the OS itself looks somewhat iPad-ish which I won't really like that much).
Thinking to install on MacBook Pro (Retina, Mid 2012, i7 with NVIDIA 650M, 16GB RAM) or hopefully MacBook Pro (Mid 2009, 15 inch, Core 2 Duo with NVIDIA 9600M GT, 8GB RAM), so if anyone needs outcome in here, so please feel free to let me know so then I can test and confirm first before you take the risk.
(Thanks for all of your efforts anyway, really appreciate it.)
And I found the only thing that is not working in the Mac mini is Wi-Fi so far, but in my case, I couldn't really confirm the patches and custom .kext driver as my system drive stays read-only status even though I've tried basically everything I can possibly do (also perhaps I wasn't really as desperate as I would normally do as the OS itself looks somewhat iPad-ish which I won't really like that much).
Thinking to install on MacBook Pro (Retina, Mid 2012, i7 with NVIDIA 650M, 16GB RAM) or hopefully MacBook Pro (Mid 2009, 15 inch, Core 2 Duo with NVIDIA 9600M GT, 8GB RAM), so if anyone needs outcome in here, so please feel free to let me know so then I can test and confirm first before you take the risk.
(Thanks for all of your efforts anyway, really appreciate it.)
Last edited:
I am wondering will features like icloud lock en find my work, on my unibody mbo 2012, when running unsupported macos releases.. ?
And will filevault still work.. ?
anyone has experience with this.. ?
And will filevault still work.. ?
anyone has experience with this.. ?
Thanks for your reply.
That's a good news! but it is about CPU. Mine shows this way...
