macOS 11 Big Sur on Unsupported Macs Thread

[Ausdauersportler]

Hi!
I just installed Big Sur on my mac pro 2008 using starplayrx's bigmac patcher.
Everything went smoothly during the installation and everything work well.
Except when I go into settings and then software update, its stuck at "checking for updates" and won't move past that.
Is this just because there are no updates available? (I have 11.1 installed, so its the latest version)
Or is it disabled with the patch maybe? It's not a real problem for me but I do want to be able to download updates in the future, can I still do that and re-patch the system afterwards?

This is because you have an unsupported Mac and Apple blocks us all from updates. Welcome to the machine! The problem could be that there will be no more full installers, only updates. Start reading the last 3-5 pages to get an idea.

 

[naylom11]

Hi I was discussing OLP/OC off-thread with @BenSova , and he was pointing out that apparently there can be iCloud issues with OC - i.e. if you use your own, real, valid machine serial number, but are running inside OC with a faked hardware id then this can eventually cause iCloud account issues.

Anyone got any more info or links about this? (I saw that @naylom11 already posted mentioning it as a problem.)

I'm still using OC to 'cloak' my machine, just to get updates (as @Ausdauersportler suggests) and then booting unpatched (boot-args="-no_compat_check" only required) the rest of the time. So, as expected, I'm not seeing this problem (since I'm not mainly running with that problem configuration) - but it would be good to understand if it really would be problematic to boot via OC with faked hardware info all the time, for the reason I'm asking about.

If it was a problem, but OC could otherwise inject all the fixes a given machine needs, then it sounds like it might be an idea to have TWO OC boot disks: one for fetching updates, with faked hardware info; and one for day-to-day use without faked hardware info. That's not necessary on machines which need no day-to-day patches or injection (i.e. ones where you can boot and run Big Sur fine with no OC for day-to-day use, like I can on my slightly upgraded MBP), but then from the above-mentioned post and another recent post by @Ausdauersportler I'm not sure whether there are any/many machines where such a dual-OC setup would be needed and able to do the job?

Really the only concern with authorization are those that are A: Running multiple legitimate Macs/PC's with iTunes authorized content. Or B: Those who aren't careful when upgrading their config.plist, and spoofed different serial numbers. This makes it look like you've authorized different Macs to use your content every time you've upgraded and signed into Music/iTunes/TV

Heres an article from apple about the 5 system limit: https://support.apple.com/en-us/HT201251 (And I believe there is deauthorization limit as well)

In terms of the "dual setup" you're running. **Assuming you access purchased content. I wouldn't be too concerned as long as you carry over the same serial number when you eventually update OpenCore. I've been switching back and forth from OC to the MicroPatcher with no issues in terms of iCloud services. In fact iCloud will actually recognize my system as 2013 mbp when in OC, and switches my system back to a mid 2012 when using the micropatcher (with slight delays depending on the time I'm using each system).

Two final thoughts. Running two OC systems is unnecessary and complicated in that scenario, what you're doing sounds perfectly fine. And Deauthorizing through iTunes/Music is a good practice before ditching a system.

 

[BenSova]

Hi I was discussing OLP/OC off-thread with @BenSova , and he was pointing out that apparently there can be iCloud issues with OC - i.e. if you use your own, real, valid machine serial number, but are running inside OC with a faked hardware id then this can eventually cause iCloud account issues.

To clarify: Using your real serial number does not cause the problems, but using the spoofed serial number might (depends on a trust system).

 

[Rob1n]

This is because you have an unsupported Mac and Apple blocks us all from updates. Welcome to the machine! The problem could be that there will be no more full installers, only updates. Start reading the last 3-5 pages to get an idea.

ok, thank you! In previous mac versions patched with dosdude1's patcher updates would appear, is this just a big sur thing then? And are there also no manual updates anymore? (via the apple download page)

 

[jav26]

You are welcome! As of now I have only added features. Since the most 2012/13 Macs do not need patching at all this work is of no use then. The USB patcher itself is only used to make the installer booting your Mac and it gracefully quits unless it detects an older WiFi card. A notable exception might be Night Shift - I have commented before on this.

Of course a backup of the firmware is useful. And of course I would have to open even my iMac and use a CH341A clip programmer to flash the firmware back - this is the tool I was talking about.

Hello, may I ask a question about my iMac? I have a late 2012 imac, could I just install Bigsur without any patch/flash? If so, could you tell me how to do that? I sticked with Catalina since I was afraid to brick my mac since I don't have any tool to restore its original firmware. Thanks in advance

 

[Tockman]

could I just install Bigsur without any patch/flash?

Just try to. And after that come back here and read the first page of the thread.

 

[jav26]

Just try to. And after that come back here and read the first page of the thread.

Thank you for your suggestion, I had already read it, I am concerned about flashing since it talks about wifi problems and I don't know if updates will work without flashing.
Edit: Do you know what wireless models do not work well in order to check if mine is one of them?

 

[Ausdauersportler]

Thank you for your suggestion, I had already read it, I am concerned about flashing since it talks about wifi problems and I don't know if updates will work without flashing.
Edit: Do you know what wireless models do not work well in order to check if mine is one of them?

Try at least to search the thread for success stories of other users owning the same model yourself.

Unsupported means self support or use Catalina.

 

[jav26]

Try at least to search the thread for success stories of other users owning the same model yourself.

Unsupported means self support or use Catalina.

Thanks, I did that but all I find is users that patched/flashed their late 2012 iMac. I did not find any about what wifi cards work. That is why I asked my questions...I won't bother you anymore, thanks for your work.

 

[Bmju]

Thanks, I did that but all I find is users that patched/flashed their late 2012 iMac. I did not find any about what wifi cards work. That is why I asked my questions...I won't bother you anymore, thanks for your work.

You are going to have to use Google to find out about upgrading your Wi-Fi card. That said, by searching this thread for "imac 2012 wifi" for you, I have already turned up e.g. this post. (I do not have your Mac so I do not know for sure if that is a valid recommendation; but more and similar Googling, both on and off this forum, let me successfully upgrade the Wi-Fi card for my own MBP 2012 ready for Big Sur.)

I think you're confused about flashing? Flashing is making a permanent change (usually upgrade) to the firmware of one of the chips of your Mac. AFAIK there's no flashing at all required to install Big Sur (esp. not on a reasonably recent Mac like yours).

You can't "just" install Big Sur, as you asked about, because the installer will refuse to run without you running something to at least temporarily change (by patching or injecting; not flashing) at least the reported hardware, on unsupported Macs.

@Ausdauersportler said that 2012 Macs work with OpenCore. I don't have your Mac, but let's assume that applies to yours. There was a problem with many Macs (included supported Macs, using the supported update procedure!) where you might have to re-flash them - or replace some hardware - after a failed update to get out of a permanent black-screen state. (NB On some machines, just temporarily disconnecting the battery of the powered-down machine was enough to fix this - until the next update.) Now, OpenCore 0.6.6 upwards, if configured correctly, can prevent this. Therefore the recent version of OCLP, which uses that version of OC, fixes this. But all this is unsupported or self-supported, i.e. at your own risk. E.g. the fix in OC might not work with some future Big Sur update - and that applies to all of us who are using it. So if you aren't prepared or able to take on the responsibility of potentially doing the just described kind of work to recover your own Mac if things go wrong (and/or taking on the risk of entirely losing your usable Mac), then yes, unfortunately, you should not install the unsupported OS on your machine.

 

[jav26]

You are going to have to use Google to find out about upgrading your Wi-Fi card. That said, by searching this thread for "imac 2012 wifi" for you, I have already turned up e.g. this post. (I do not have your Mac so I do not know for sure if that is a valid recommendation; but more and similar Googling, both on and off this forum, let me successfully upgrade the Wi-Fi card for my own MBP 2012 ready for Big Sur.)

I think you're confused about flashing? Flashing is making a permanent change (usually upgrade) to the firmware of one of the chips of your Mac. AFAIK there's no flashing at all required to install Big Sur (esp. not on a reasonably recent Mac like yours).

You can't "just" install Big Sur, as you asked about, because the installer will refuse to run without you running something to at least temporarily change (by patching or injecting; not flashing) at least the reported hardware, on unsupported Macs.

@Ausdauersportler said that 2012 Macs work with OpenCore. I don't have your Mac, but let's assume that applies to yours. There was a problem with many Macs (included supported Macs, using the supported update procedure!) where you might have to re-flash them - or replace some hardware - after a failed update to get out of a permanent black-screen state. (NB On some machines, just temporarily disconnecting the battery of the powered-down machine was enough to fix this - until the next update.) Now, OpenCore 0.6.6 upwards, if configured correctly, can prevent this. Therefore the recent version of OCLP, which uses that version of OC, fixes this. But all this is unsupported or self-supported, i.e. at your own risk. E.g. the fix in OC might not work with some future Big Sur update - and that applies to all of us who are using it. So if you aren't prepared or able to take on the responsibility of potentially doing the just described kind of work to recover your own Mac if things go wrong (and/or taking on the risk of entirely losing your usable Mac), then yes, unfortunately, you should not install the unsupported OS on your machine.

Thank you very much for your long explanation. Since I read that some iMacs 2012 were bricked with a black screen I thought that it was because of flashing. I don't mind to try it if I can go back if something is wrong, thats was my concern and why I want to avoid any flash or firmware patch. I have a 2015 macbook pro where I can make any recover usb.

 

[Bmju]

Thank you very much for your long explanation. Since I read that some iMacs 2012 were bricked with a black screen I thought that it was because of flashing. I don't mind to try it if I can go back if something is wrong, thats was my concern and why I want to avoid any flash or firmware patch. I have a 2015 macbook pro where I can make any recover usb.

Yes, you are right, when those Macs are bricked it is because of flashing - not because of anything you have to flash, in order to do the update (if that's what you were thinking, as I think it sounded?) but yes, indeed, flashing done incorrectly/inappropriately by the Apple updater during the update.

Be aware (really, be aware!) that there's still no guarantee that that won't happen if you run the update now - even though it definitely shouldn't happen with OC 0.6.6. The developers of OCLP - who added the relevant fix to OC - would want to know about it (on GitHub) if it did still happen, and you might be able to get help here, or there, if it did. That is, I'm sure people would try - but (really!) there are no guarantees! Maybe you would have to go to a Mac store, and pay them. You still need to be prepared to recover your Mac yourself, perhaps up to and including re-flashing it to fix problems caused by this or a future update, or paying Apple, and/or still having the risk of losing it completely, in case anything does go wrong, unfortunately.

 

[Danwilderspin]

So can someone tel me on an unsupported iMac how I enable night shift? I used the 6th patcher from the list everything works except this and airplay. If it’s not possible I’ll shut up just need to know

 

[KennyW]

Yes, you are right, when those Macs are bricked it is because of flashing - not because of anything you have to flash, in order to do the update (if that's what you were thinking, as I think it sounded?) but yes, indeed, flashing done incorrectly/inappropriately by the Apple updater during the update.

Be aware (really, be aware!) that there's still no guarantee that that won't happen if you run the update now - even though it definitely shouldn't happen with OC 0.6.6. The developers of OCLP - who added the relevant fix to OC - would want to know about it (on GitHub) if it did still happen, and you might be able to get help here, or there, if it did. That is, I'm sure people would try - but (really!) there are no guarantees! Maybe you would have to go to a Mac store, and pay them. You still need to be prepared to recover your Mac yourself, perhaps up to and including re-flashing it to fix problems caused by this or a future update, or paying Apple, and/or still having the risk of losing it completely, in case anything does go wrong, unfortunately.

The bricking is due to the Apple Updater trying to flash a new efi into your Mac Bootrom if its Mac ID is spoofed and masquerade as another Mac to effect the update that is meant only for SUPPORTED Mac.

Many a time, the recovery requires re-flashing your Mac Bootrom with a EEPROM programmer, like the ch341a, by clipping your Mac logic board Bootrom chip to do the flashing. Thus, you are strongly strongly advised to save your Bootrom content with Dosdude1's ROMTOOL to another computer or USB flash drive to prepare for such mishap.

 

[CuchoM]

MBP 9,2 non retina - just updated macOS Big Sur 11.2 (20D62) - OC legacy 0.0.9 - OC 0.6.6 everything working fine no issues .
Opencore works really fine easy installation and no issues thanks for https://github.com/dortania/Opencore-Legacy-Patcher - dortania

 

[Ausdauersportler]

MBP 9,2 non retina - just updated macOS Big Sur 11.2 (20D62) - OC legacy 0.0.9 - OC 0.6.6 everything working fine no issues .
Opencore works really fine easy installation and no issues thanks for https://github.com/dortania/Opencore-Legacy-Patcher - dortania

Was it 11.2 (20D53)? At least this is what my systems show here

 

[StephN999]

Bonsoir,

same with big-sur-micropatcher fork by Ausdauersportler and OpenCore 0.6.6 build a7f1d33.

Same error with it snapshot:

snapshot fsroot/file key rolling tree corruptions are not repaired; they'll go away once the snapshot is deleted

According to my research it's normal, it seems to be a bug in DiskUtil, to be confirmed.

Edit: Ausdauersportlerit is indeed the 20D62 (RC2).

 

[Earl Urley]

Does anyone have the link to the post about flashing BootROMs from the update package with a manual Terminal command? I've been trying to run searches for it but I keep getting negative results..

 

[Bustycat]

Was it 11.2 (20D53)? At least this is what my systems show here

Yours is RC 1, and what he/she mentioned is RC 2.

 

[jav26]

Yes, you are right, when those Macs are bricked it is because of flashing - not because of anything you have to flash, in order to do the update (if that's what you were thinking, as I think it sounded?) but yes, indeed, flashing done incorrectly/inappropriately by the Apple updater during the update.

Be aware (really, be aware!) that there's still no guarantee that that won't happen if you run the update now - even though it definitely shouldn't happen with OC 0.6.6. The developers of OCLP - who added the relevant fix to OC - would want to know about it (on GitHub) if it did still happen, and you might be able to get help here, or there, if it did. That is, I'm sure people would try - but (really!) there are no guarantees! Maybe you would have to go to a Mac store, and pay them. You still need to be prepared to recover your Mac yourself, perhaps up to and including re-flashing it to fix problems caused by this or a future update, or paying Apple, and/or still having the risk of losing it completely, in case anything does go wrong, unfortunately.

Thanks for your reply, I fully understand it now how it works

 

[LavaTech]

Ummm, no. The NVidia GTX 10xx series cards aren't properly driver supported in anything newer than High Sierra.

I suppose thats fine. Im receiving the thing for free and have really no use for it. In about a week im gonna purchase a metal supported quadro 4000 with 2 gigs of vram. Im hoping it will run big sur fine, but I fell in love with high sierra, thats what im using now, altho id like to run Mojave. Can I do dual cards? like the quadro and the gtx 1050? oc?

 

[borp99]

This (now-edited) post was to do with the sudden duplication of my non-Apple apps in 11.1, where new larger folders (named the same as the apps and containing the package Contents folder and all other files inside) sponsaneously appeared next to the apps in Applications, despite not writing any more data to the volume.

Thank you for those who responded or postulated the problem and considered a solution. However, I think that the error arose when I was trying to fix a permissions problem, encountered after installing a new app but it wouldn't launch...with the message 'You do not have permission to open the application. Contact your system administrator'. I tried the 'brew install upx / sudo upx -d /Applications/my_app.app/Contents/MacOS/my_app' fix (didn't work) and then some chmod ideas. I thought that I'd always singled out the one new app in my terminal commands but maybe I slipped up and applied a certain permissions change to all of my 11.1 - Data apps by mistake. Therefore, I'm now assuming that it's not a new fault in Big Sur (which I think is a terrific new OS on my cMP 2010).

I erased my weirdly duplicate-folders 11.1 volume and cloned a recent CCC backup back into place. All is well in BS land again.

 

[amaze1499]

Hi All,

Something very odd just happened to me while running BS 11.1 as my main OS on my cMP 2010 (it's been running 'normally' as expected for many months now). I returned to my Applications folder and suddenly all of my non-Apple apps have 'similtaneously around the same time' sprouted an extra folder with the app's usual Contents folder and other/expected nested files inside. The original apps still have their usual Contents folder inside their packages and launch just fine from their icons, but the new similarly-named folders are often reported by the Finder as larger than the original app's Contents folders do, even though no more free space has been written to, compared with before the folders suddenly appeared.

View attachment 1719831

I went into Recovery mode and did a Disk Utility repair of the OWC 1TB Aura P12 NVMe SSD as a whole and on 11.1 specifically but no errors were found or reported.

Has anyone else ever experienced this 'Twilight Zone' phenomenon running Big Sur? I did a Google search but nothing similar seemed to pop up. I'm not sure if I can simply manually delete these weird new folders or what else to do. Would reinstalling 11.1 over the top correct this issue?

Out of curiosity: Does VMware Fusion has access to these files/folders via Networksharing? Same issue with different user?

 

[borp99]

Out of curiosity: Does VMware Fusion has access to these files/folders via Networksharing? Same issue with different user?

My screenshot including the VMware Fusion app was only a coincidence. I usually keep any virtual machine OS's ring-fenced away from Mac OS file sharing. I only have myself setup as the Admin/only User on my cMPro.

 

[ggyenyen]

Try at least to search the thread for success stories of other users owning the same model yourself.

Unsupported means self support or use Catalina.

I’m sorry to say but unsupported doesn’t mean self support. It means Apple no longer supports certain mac models. developers who keep writing programs for us to keep using the latest OS workimg on our outdated macs are truly doing miraculous work. But comments like yours are just alienating others to try their best at making big sur run as best on their machines. Trust me when I say I dont mean to offend. But please be respectful to others who don’t have as much knowledge as yourself.