macOS 11 Big Sur on Unsupported Macs Thread

[LaEnsalada]

Is it possible to do a clean install with the Micropatcher automator?

 

[justperry]

cMP mid 2012 successfully installed BS 11.2 (20D64) 12.21 GB with Barry 0.5.1.
If your cMP GPU and BT/WiFi card updated. After boot from USB installer, open Terminal (in the Utilities menu) then run without quote "/Volumes/Image\ Volume/set-vars.sh" and install the BS as normal.

You can do this before, after installing Big Sur installer to the USB run micropatcher.sh and set-vars.sh in Terminal, IIRC set-vars.sh should be run as root, so sudo set-vars.sh

 

[IbrahimFmc]

still wifi bug and I have to manually connect to the wifi

 

[amaze1499]

cMP mid 2012 successfully installed BS 11.2 (20D64) 12.21 GB with Barry 0.5.1.
If your cMP GPU and BT/WiFi card updated. After boot from USB installer, open Terminal (in the Utilities menu) then run without quote "/Volumes/Image\ Volume/set-vars.sh" and install the BS as normal.

Out of curiosity: Did you ever experience bluetooth audio dropouts with a JBL Flip4? In case you ever tested that or heard about it

 

[ca$hman]

Just updated the MBP M1 8/512 and MBP x86 16/512 to BS 11.2 and the update took 3 times more time on the x86. Went super fast on the M1. Running smoothly on both one cold and one hot machine

 

[maxsp97]

Out of curiosity: Did you ever experience bluetooth audio dropouts with a JBL Flip4? In case you ever tested that or heard about it

I don't have JBL Flip4 but Bluetooth audio is working fine with my Bose QuietComfort Earbuds.

 

[maxsp97]

You can do this before, after installing Big Sur installer to the USB run micropatcher.sh and set-vars.sh in Terminal, IIRC set-vars.sh should be run as root, so sudo set-vars.sh

Just followed Barry's Micropatcher instructions and I don't have any problem.

 

[n0rt0nthecat]

Using micro patcher on the released 11.2 did a successful upgrade from 11.1 on my late iMac 2013.. Now, if we get OTA to work, then it'd be great. OpenCore seems way over my head atm to understand

 

[MrMacintoshBlog]

Using micro patcher on the released 11.2 did a successful upgrade from 11.1 on my late iMac 2013.. Now, if we get OTA to work, then it'd be great. OpenCore seems way over my head atm to understand

OpenCore is great when setup and the OTA updates work. The only problem is, the OTA updates were causing a bunch of problems for some users (macs not booting requiring battery removal or iMac efi flash). I'm not sure where this is currently.

 

[alphascorp]

Hi all,

macOS Big Sur 11.2 (20D64) successfully installed on cMP5,1 with micropatcher 0.5.1 (clean install then data migration from 11.1)

Everything seems to work fine

 

[Xavier]

Updated my late 2013 iMac 27" successfully to 11.2. Thanks for all the guidance in this post!

 

[Tockman]

del

 

[Tockman]

Successfully updated using Patched Sur 0.0.4.

 

[El gamer]

Here is a very good video to install Macos big sur 11.2 on unsupported macs:

 

[Tockman]

Here is a very good video to install Macos big sur 11.2 on unsupported macs:

But all those steps are clearly stated on Patched Sur page at Github.

 

[oldmacs]

Hi all. I have a Mid 2012 13 inch MacBook Pro running 11.1 using the Micropatcher. What is the easiest way to update to 11.2?

 

[andyhone]

Check this to enable handoff and airdrop with our BCM94311CD card (I guess you have it), put in your micropatcher USB and open a Terminal and enter line by line (without the leading user@myMac %)

user@myMac % /Volumes/Install\ macOS\ Big\ Sur/remount-sysvol.sh
user@myMac % MYBOARD=`/usr/sbin/ioreg -l | grep board-id | awk -F\" '{ print $4 }' | grep Mac`
user@myMac % echo $MYBOARD
user@myMac % cd ../Frameworks
user@myMac % /usr/libexec/PlistBuddy -c "Set:$MYBOARD:ContinuitySupport true" "IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"
user@myMac % chown -R 0:0 IOBluetooth.framework
user@myMac % chown -R 755 IOBluetooth.framework
user@myMac % cd ../Extensions
user@myMac % /usr/bin/perl -pi -e "s/\Mac-00BE6ED71E35EB86/$MYBOARD/" IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360
user@myMac %  /usr/bin/perl -pi -e "s/\Mac-00BE6ED71E35EB86/$MYBOARD/" IO80211Family.kext/Contents/PlugIns/AirPortBrcmNIC.kext/Contents/MacOS/AirPortBrcmNIC
user@myMac % chown -R 0:0 IO80211Family.kext
user@myMac % chown -R 755 IO80211Family.kext
user@myMac % "$REBUILD_KC"

You came in late and missed all the problems with WIFI, the long comment within the README.md of the micropatcher has been added on purpose, I guess.

This code has been added to my fork of the micropatcher and will be called with this command line option of the patch-kext.sh --whitelist.

If you have success I will add the OLCP kext to the micropatcher for your MacBookPro10,1.

Note (the Mac-00BE6ED71E35EB86 is the iMac13,1)

Thanks for your quick help.
Unfortunately, I do not have BCM94311CD card.
Actually, AirDrop, handover works well under Micropatcher, but not in OpenCore Patcher.
After I replaced AirPortBrcm4360 with the one in OpenCorePatcher, the personal hotspot and airDrop works now, but not handover and BT to iPhone. The switching between wifi AP and iPhone is not as smooth as Catalina, I have to switch on/off the wifi before successful connection.

Is there any other way can detect the driver correctly without reinstall?

 

[David dongfox]

just updated to 11.2 (20D64) from micopatcher 5.1 on my Mac mini late 2012.
everything go fine. enjoy !

 

[holiday786]

Hi many thanks for your help. I have a stock MacBook Pro 15 classic with 1tb hard disk drive 8gb of ram and a high resolution display. I haven’t upgraded the ram or the drive yet.

 

[Ausdauersportler]

Thanks for your quick help.
Unfortunately, I do not have BCM94311CD card.
Actually, AirDrop, handover works well under Micropatcher, but not in OpenCore Patcher.
After I replaced AirPortBrcm4360 with the one in OpenCorePatcher, the personal hotspot and airDrop works now, but not handover and BT to iPhone. The switching between wifi AP and iPhone is not as smooth as Catalina, I have to switch on/off the wifi before successful connection.

Is there any other way can detect the driver correctly without reinstall?

My guide is called whitelisting - it works (or should work) with other cards, too. If you do not try and just post questions again and again nothing will happen. This is no reinstallation, it is some minor patching.
And reinstallation over the existing Big Sur will not delete your personal data, it will just restore the macOS part. It is your system not working, you will have to do the experiment.

 

[webg3]

Just updated OTA to 11.2 (20D64) from OpenCore 0.6.6 on my MacBook Air (11-inch, Mid 2012)
Wi-Fi 802.11ac (new Air 2013-2017)
No bugs, no freeze, working perflect.
everything go fine. enjoy !

 

[amaze1499]

MacBookPro9,2: full installer + MP 0.5.2 = 20D64 . No issues, but bluetooth audio drop outs continue. Cant use any bluetooth speaker with BigSur.

 

[amaze1499]

deleted

 

[webg3]

MacBookPro9,2: full installer + MP 0.5.2 = 20D64 . No issues, but bluetooth audio drop outs continue. Cant use any bluetooth speaker with BigSur.

I use it perfectly, Airdots (Redmi), and a PagSeguro (BR) bluetooth speaker. No problems for me.

 

[Bmju]

Using micro patcher on the released 11.2 did a successful upgrade from 11.1 on my late iMac 2013.. Now, if we get OTA to work, then it'd be great. OpenCore seems way over my head atm to understand

OpenCore is great when setup and the OTA updates work. The only problem is, the OTA updates were causing a bunch of problems for some users (macs not booting requiring battery removal or iMac efi flash). I'm not sure where this is currently.

I've successfully used OC to apply OTA delta updates to get my MacBookPro10,2 all the way to 20D64.

I still got one more black screen, but then I was playing around manually with OC settings, which I am almost certain was the reason...

@n0rt0nthecat - OpenCore Legacy Patcher should make OC much easier to use now.

@ClassicII - the black screen problem is (I believe!) fixed now, by a patch to OC specially for this which the OCLP developers provided. Multiple people (including me, when I'm not fiddling around with the settings!) are reporting that the fix works.

OC/OCLP advantages: 1. OTA/delta updates available. 2. Perhaps arguably a 'cleaner' install than with micropatcher? 3. Finally (you do not need this last one for basic use of OCLP, and it is more fiddly to do, so maybe still only for enthusiasts!), but it is still possible to use OC for installing updates only, and have it not intervene at all, booting BS from completely unpatched files, day to day. This makes most sense on an upgraded unsupported Mac, where the upgraded h/w actually fully supports BS. This gives the cleanest possible boot! (The methods I posted earlier for this, which was just spelling out @jackluke's method in detail, still work using the build of OC which OCLP makes for you.)

Disadvantage: One which I don't like, OCLP fakes all your system ids. While this is required for non-Apple hardware (which, obviously, OC can support!), it is not required on Apple hardware: it is possible to configure OC to detect and use all your original system ids and serials. (This is relevant to just continuing as the same machine, as far as Apple products (iCloud, iMessage, FaceTime) are concerned, and similarly for Windows registration if you have e.g. Bootcamp on your hardware.) I don't know the status of this in the micropatcher (I haven't used it), but I would guess it does not fake your system id or machine serials? (Anyone?)