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
Is anyone else having trouble with video playback in the TV app? On streamed videos It will play a second or 2 of the video and then just drop back to the main app screen. For downloaded videos in my library it is audio only and black screen. This is on a 2011 IMac with an 860M video card. Everything else seems to work fine including youtube videos.
I copied the download link, next pasted it in Brave, downloaded without any delay, Safari bug...!!!???
Hi !
I just want to give a Heads-up that BS works perfectly on my 2012 Macbook Pro.
So, a big thank you to @Barry K. Nathan and everyone else who has helped to let BS run on unsupported macs.
I followed his guide, and it worked faultlessly.
Regards
IB
I just want to give a Heads-up that BS works perfectly on my 2012 Macbook Pro.
So, a big thank you to @Barry K. Nathan and everyone else who has helped to let BS run on unsupported macs.
I followed his guide, and it worked faultlessly.
Regards
IB
I tested the engineering version on an unsealed system volume and it worked.Carbon Copy Cloner 5.1.23 should FINALY make bootable clones of Big Sur! Download 5.1.22 then check beta updates.
Just trying to clone @jackluke patched BigSur SSD 11.0.1 (20B29) on internal iMac 2013 hard disk
TL/DR:
Three times in a row I have (almost but not quite) 'bricked' my 2012 13" retina display MacBook Pro 10,2; and three times in a row disconnecting the battery, then holding the power button for a bit, then reconnecting the battery, reassembling and restarting has fixed it - completely and immediately.
So I'd say this is definitely a real fix for this model of Mac. It can't just fix my specific Mac, surely?! In fact at least a couple of other people have fixed the same problem by discharging their battery - which I guess amounts to the same thing. Unfortunately, others are reporting that this approach definitely doesn't work for them. :-(
More info:
I'm persisting in doing OTA updates using @jackluke's sideloader. 🤣 Which is why this is happening, and is no longer considered a recommended or safe approach for general use - I do understand that. However, apart from this problem it's still working just fine. 😊
Just as a reminder, the symptoms (which sound to me exactly the same as in a lot of supported 2013-2014 MBPs out there) are: the screen goes black on the first reboot of the install, the machine will then power up and power down, but only as far as the blank screen, it won't make a boot chime and won't move off the black screen - and no standard NVRAM/PRAM reset key combination will bring it back.
Also, for info:
Three times in a row I have (almost but not quite) 'bricked' my 2012 13" retina display MacBook Pro 10,2; and three times in a row disconnecting the battery, then holding the power button for a bit, then reconnecting the battery, reassembling and restarting has fixed it - completely and immediately.
So I'd say this is definitely a real fix for this model of Mac. It can't just fix my specific Mac, surely?! In fact at least a couple of other people have fixed the same problem by discharging their battery - which I guess amounts to the same thing. Unfortunately, others are reporting that this approach definitely doesn't work for them. :-(
More info:
I'm persisting in doing OTA updates using @jackluke's sideloader. 🤣 Which is why this is happening, and is no longer considered a recommended or safe approach for general use - I do understand that. However, apart from this problem it's still working just fine. 😊
Just as a reminder, the symptoms (which sound to me exactly the same as in a lot of supported 2013-2014 MBPs out there) are: the screen goes black on the first reboot of the install, the machine will then power up and power down, but only as far as the blank screen, it won't make a boot chime and won't move off the black screen - and no standard NVRAM/PRAM reset key combination will bring it back.
Also, for info:
- This time 11.1 beta caused the issue.
- I already have the firmware update (assuming that having the new 'no entry' screen means I have the firmware update), but that isn't stopping the problem from happening.
Last edited:
And mine
👍 A tip (if you're interested)
Your about this mac page shows that you are running the Nvidia card, as was mine. It seems it's stuck on that card but there is a workaround from post 3255 in this thread by member @ribero (thanks to him)
If you run the following in a terminal
Code:
sudo launchctl stop com.apple.displaypolicydHowever you'll have to run that command after every reboot.
If you ever want to reverse this then the command is
Code:
sudo launchctl start com.apple.displaypolicydSee this...And mine
A tip (if you're interested)
Your about this mac page shows that you are running the Nvidia card, as was mine. It seems it's stuck on that card but there is a workaround from post 3255 in this thread by member @ribero (thanks to him)
If you run the following in a terminal
it will revert to the Intel graphics and graphics switching is restoredCode:sudo launchctl stop com.apple.displaypolicyd
However you'll have to run that command after every reboot.
If you ever want to reverse this then the command is
Code:sudo launchctl start com.apple.displaypolicyd
Guess what, you can edit the plist file so that it doesn't run at load.
I am a bit rusty but pretty sure that's the case.Oh that's brilliant
So just change the YES to a NO and it's done?
Thanks!
BUT..., it might be a bit harder than former OS versions, keep in mind that the system is read only.
I confirm that installation from "Basesystem fix" (createinstallmedia from 11.0.1 20B29 to a USB media, then BigSur BaseSystem legacy usb fix+fix2) works well to an installation target SSD on internal SATA.
I've removed my workhorse Catalina SSD from the internal SATA connector and put it aside, connected my BS SSD to SATA with an erased partition that I used for installation.
Booted the USB installer, used Hax3 from the green button on the main installer window, confirmed Hax3 with the button upper right.
Then started installation to the empty partition on internal BS SSD. Proceeded automatically through all three stages, then tried to boot BS (reboots due to missing patches).
Applied all patches, in my case via micropatcher 0.5.1 patch-kexts.sh (slightly modified to also contain night shift and USB mouse/keyboard usage without single-user booting). This is equivalent to using Legacy USB, framebuffer, snapshot and Frameworks fixes of "Basesystem fix" installer.
BS installed and post-install patched this way on an internal SSD boots and works fine. This is for a legacy USB MBP5,2.
The other option I have used successfully is with USB3 provided by a nanoTECH expresscard. One can't boot from these, so booting anything needs to start on on-board USB port, and when an installer stage then hangs due to legacy USB power problen (after 10-15sec), hot-swap to USB3 from where it continues.
Other MBP users have used a 2nd SATA port if available (e.g. for the internal DVD drive) for an additional SSD for BS.
At present there seems no software means working yet for continuing stage3 installation to a SSD connected to on-board USB of legacy USB machines.
Next is to check installation with a micropatcher-patched installer, to internal SSD. I guess I'll need to resort to USB3 for booting the USB installer itself, and for giving keyboard input to it.
I didn't use OpenCore in the process, maybe it will help with legacy USB as well, as it did for Catalina OTA updates.
Thanks jackluke and BarryKN for all your work. That provides BS installation even on legacy USB machines. Using the result in production of cause requires graphics acceleration.
Last edited:
@Ausdauersportler :
to be sure to have a good system, I reinstall everything. I erased the target disk and even recreated the USB key.
but I have an error in the script patch-kexts.sh
Code:
[...] /patch-kexts.sh: line 747: zip: Command not foundit's the line:
Code:
zip -q -r -X AppleGraphicsControl.kext.zip AppleGraphicsControl.kextHere is the beginning and the end of the shell script for information:
and some others errors:
Thank for your help
Me
Checking
https://swscan.apple.com/content/ca...ion-snowleopard-leopard.merged-1.sucatalog.gz
Over and over and over and over.over.over.again and again and again.again.again.again....
No (11.1) dice yet. 😢
Checking
https://swscan.apple.com/content/ca...ion-snowleopard-leopard.merged-1.sucatalog.gz
Over and over and over and over.over.over.again and again and again.again.again.again....
No (11.1) dice yet. 😢
This was no clean install. For some reason you already patched and unpatched and deleted somehow (patcher bug) the AppleGraphicsControl.kext. The script tried to recover from the archive which failed because there was no archive any longer.@Ausdauersportler :
to be sure to have a good system, I reinstall everything. I erased the target disk and even recreated the USB key.
but I have an error in the script patch-kexts.sh
Code:[...] /patch-kexts.sh: line 747: zip: Command not found
it's the line:
Code:zip -q -r -X AppleGraphicsControl.kext.zip AppleGraphicsControl.kext
Here is the beginning and the end of the shell script for information:
and some others errors:
Thank for your help
Please do a fresh installation and let the script run only once.
If you want to patch several times please just undo patching by
patch-kext.sh -u.And use the script I attached here. It has some error fixes...
In case you miss your AGC take this.
Ignore the other errors...I have seen them since Beta 3.
P.S.: Version 0.5.2 will fix these errors...
As an FYI..... 11.1 just installed on my 2019 16" MBP. Was a 3.4GB download.
I'm also getting the same error reports from kmutil when executing patch-kexts.sh. They seem not to harm, the resulting system is always fine in my case.@Ausdauersportler :
to be sure to have a good system, I reinstall everything. I erased the target disk and even recreated the USB key.
but I have an error in the script patch-kexts.sh
View attachment 1672777
Code:[...] /patch-kexts.sh: line 747: zip: Command not found
it's the line:
Code:zip -q -r -X AppleGraphicsControl.kext.zip AppleGraphicsControl.kext
Here is the beginning and the end of the shell script for information:
View attachment 1672780
and some others errors:
View attachment 1672783
View attachment 1672784
Thank for your help
That's a Delta, unsupported macs very likely have to update with the full installer for the foreseeable future.
However :
- I delete the patched install USB key
- I recreate the patched install USB key
- I delete the disk use to receive Big Sur installation
anyway, I will try tomorrow with your new file 👍
Thank, i try tomorrow and I will post the result
best regards
Try installing on another Mac USB drive and use carbon copy clone to raid0 on destination Mac. I was able to do it that way,
Has anybody tried to install Big Sur on Macbook Pro (mid 2012) will it have HW Acceleration on the nVidia GeForce GT 650M GPU?
EDIT:
I ask, because according to this page:
It says the 650M is compatible with latest Big Sur, but this page (at the very bottom) says it isn't:
EDIT:
I ask, because according to this page:
It says the 650M is compatible with latest Big Sur, but this page (at the very bottom) says it isn't:
macOS Sequoia
macOS Sequoia brings effortless window tiling, web browsing with fewer distractions, new iPhone Mirroring, and support for Apple Intelligence.
www.apple.com
Last edited:
Thanks to @Glemp, @pyedog, and everyone else on this forum of their assistance. My MacMini late 2012 runs like a charm on Big Sur and I must say that I don't understand why it is not supported officially. I have 16GB RAM, which makes a bigly difference, but I have yet to experience any glitches and everything works smoothly and is fast.