macOS 11 Big Sur on Unsupported Macs Thread

[amaze1499]

With Patcher 0.0.19 and the public Beta of Big Sur i get an error during installation.
With the dev betas 2 and 3 it was working...

I am using a Macbook Air 11 Mid 2012.
I downloaded the beta from this post.

View attachment 941569

Had a similar issue. Installation crashed. Tried again. It worked the second time.

 

[highvoltage12v]

I'm using MicroPatcher 0.0.20 And I Still cannot mount The boot disk. I have used zap-snapshots.sh from the install envoirment many times. This is truly becoming frustrating at this point in time. Booting over USB if this makes any difference.

 

[civotit]

I'm using MicroPatcher 0.0.20 And I Still cannot mount The boot disk. I have used zap-snapshots.sh from the install envoirment many times. This is truly becoming frustrating at this point in time. Booting over USB if this makes any difference.

Try either of the following to use the boot disk on a sealed system: (use 'sudo' as necessary)

mkdir ~/MountPoint
mount -o nobrowse -t apfs /dev/disk5s5 ~/MountPoint
mount -uw ~/MountPoint
# do what you want using ~/MountPoint (as an alias for ‘/‘ and /Volumes/Sur)

OR

diskutil mountDisk /dev/disk5s5 # this mounts the subsystem for ‘/‘ as /Volumes/Sur \1
mount -uw /Volumes/Sur\ 1
# do your work using /Volumes/Sur\ 1 or “/Volumes/Sur 1” (incl “, for the latter)

Hope this helps.

 

[maxsp97]

cMP 5,1 mid 2012 testing with Public beta 20A5343j to update Developer beta 4 20A5343i, Big Sur developer beta 4 SSD not format. Update took less than 25 minutes.
I downloaded Public beta 20A5343j, used Barry micropatcher 0.0.20 to update the developer beta 4.
Here are the steps.

1. Download http://swcdn.apple.com/content/down...9ja9cbqfp4scme3bzlaurv8v/InstallAssistant.pkg

2. Download https://github.com/barrykn/big-sur-micropatche

3. Install the “InstallAssistant.pkg”

4. Follow Barry “Quick instruction for use” step 1 - 8.

This all I used in Recovery Terminal “/Volumes/Image\ Volume/set-vars.sh” without quote.
Checked all working fine, accept not show the year of my Mac Pro.

 

[MoHaya]

Hey guys, just wanted to ask if any one has tried Barry's micropatcher with a Mac Pro 3,1?

 

[PiggyGamingYT3]

I turned on Reduce motion on my MacBookPro8,1 and it seems to work a bit better. Would this be a good workaround until full acceleration gets figured out?

 

[maxsp97]

It should work. Get second SSD and try it.
[automerge]1596851435[/automerge]

Hey guys, just wanted to ask if any one has tried Barry's micropatcher with a Mac Pro 3,1?

 

[RITAMA]

Other way around, public beta is newer, since j comes after i in the alphabet (but the two should be extremely similar).

Your Latest Micropatcher 0.0.20 WORK GREAT !!!

 

[highvoltage12v]

Try either of the following to use the boot disk on a sealed system: (use 'sudo' as necessary)

mkdir ~/MountPoint
mount -o nobrowse -t apfs /dev/disk5s5 ~/MountPoint
mount -uw ~/MountPoint
# do what you want using ~/MountPoint (as an alias for ‘/‘ and /Volumes/Sur)

OR

diskutil mountDisk /dev/disk5s5 # this mounts the subsystem for ‘/‘ as /Volumes/Sur \1
mount -uw /Volumes/Sur\ 1
# do your work using /Volumes/Sur\ 1 or “/Volumes/Sur 1” (incl “, for the latter)

Hope this helps.

Thanks for your help, I was still having issues, but the post by @jackluke on page 91 Here has fixed my issue. I can now boot without any SnapShots at all which will further help me develop some fixes for the 2011 iMac, have a nice evening.

 

[Enrico Ferro]

Hey guys where can i find the Big Sure Public Beta?
I would like to try to install it on my unsupported rMBP late 2012... but obviously i can't enroll it for the public beta testing and so i can't download from the beta page!
Thanks

 

[maxsp97]

Hey guys where can i find the Big Sure Public Beta?
I would like to try to install it on my unsupported rMBP late 2012... but obviously i can't enroll it for the public beta testing and so i can't download from the beta page!
Thanks

See post 2982.

 

[ggyenyen]

cMP 5,1 mid 2012 testing with Public beta 20A5343j to update Developer beta 4 20A5343i, Big Sur developer beta 4 SSD not format. Update took less than 25 minutes.
I downloaded Public beta 20A5343j, used Barry micropatcher 0.0.20 to update the developer beta 4.
Here are the steps.

1. Download http://swcdn.apple.com/content/down...9ja9cbqfp4scme3bzlaurv8v/InstallAssistant.pkg

2. Download https://github.com/barrykn/big-sur-micropatche

3. Install the “InstallAssistant.pkg”

4. Follow Barry “Quick instruction for use” step 1 - 8.

This all I used in Recovery Terminal “/Volumes/Image\ Volume/set-vars.sh” without quote.
Checked all working fine, accept not show the year of my Mac Pro.

I had to revert back to Catalina after using BS beta 3 on my cMP 5,1. Some apps like Lightroom CC were just unusable and ridicuously slow. I have 96gb ram super fast nvme ssd's 12 core 3.46ghz and 16gb Radeon VII so it wasn't the hardware that was the problem in slow applications. Any Ideas of what could be causing BS to make some apps unusable? BS looks to much more clean than Catalina but I need Lightroom for my daily work.

 

[Starmina]

Hi everyone,
New day, new issue

I'm on Beta 2, tried to upgrade to Beta 4 with barrykn's micropatcher, but the usb stick never showed up at boot (when pressing alt). So i actually tried to reset the PRAM (Option+ALT+P+R while booting), and now it shows a "forbidden" sign when i try to boot normally. And ofc usb stick still not showing up at boot :/.
Any way to solve that ?

Kinda like this one but reverse the colors and bar :

 

[MacHacJac]

Hi everyone. I spoofed my MacBook Pro 8,1 to Mojave* through OpenCore and want to add patches for it. When I patch with dosdude1's patches, my Mojave drive doesn't boot. Are there any other patches I can apply to my OpenCore Mojave installation, (e.x. sound, graphics, etc.)

*I can and will upgrade to Big Sur eventually (I have updates YAY!) but I want to first use Mojave for a little while.

 

[Enrico Ferro]

Thank you very much to everybody who contribute to make this possibile...
Big Sur is running perfectly on my rMBP late 2012
Some days ago I upgraded my wifi-bluetooth card, so now everything is working smooth...

I manage to install Big Sur after downloading the file linked in post 2982 (so thanks to maxsp97) and using Barry micropatcher 0.0.20

 

[astuermer]

So far I wasn't able to install the public beta with 0.0.20 of the patcher onto my Macbook Air 2012.

What I tried...

1. Created the installer on 3 different OS'es: iMac High Sierra, Macbook Air Mojave and Macbook Air Big Sur Dev4
2. I tried with 4 different USB sticks, all 64 GB and USB 3.0

It aborts at around 12-13 mins left.
Hopefully Barry can find a cure

 

[furdi]

I'll have to try testing it. Maybe later this morning. (I might come back and edit this post.)

Edit: I found a compatibility bug between my patcher and developer beta 4/public beta 1, which I somehow missed when testing v0.0.19. I'm about to release v0.0.20 to fix that bug, but I don't think it's related to the problem you're seeing.

I'd like you to try running this command (on the machine that created the Public Beta bootable USB installer, with the USB stick inserted), and let me know what (if any) output it produces: diff -ruN --speed-large-files /Volumes/Install\ macOS\ Big\ Sur\ Beta/Install\ macOS\ Big\ Sur\ Beta.app /Applications/Install\ macOS\ Big\ Sur\ Beta.app

Just installed the Public Beta 4 on my MBP mid 2012 (9,2) using @Barry K. Nathan's patcher 0.0.20 and it worked like a charm! At the end I have used /Volumes/Install\macOS... from the Big Sur boot and worked perfectly! Thank you @Barry K. Nathan for all the hard work! Have an amazing week-end everyone!

 

[Ausdauersportler]

Just installed the Public Beta 4 on my iMac mid 2011 (12,2) using @Barry K. Nathan's patcher 0.0.20 and it worked like a charm! (this iMac has been modded with a new Nvidia K4100M metal GPU and a BCM942692CDP Wifi ac/BT 4.2 card)

Had to install some additional extensions @highvoltage12v collected and provided to get sleep and some other minor things working.

Thank you for making this possible!

EDIT:

• Sleep is currently not working for unknown reasons (needs normally the AppleIntenHD3000* and AppleIntelSNB*). Both installed and loaded, but crash after putting the system into sleep mode.
• Continuity works pretty well after "whitelisting" the board-id, again.
• To make any changes to the root file system I use the method @jackluke described...

 

[jhowarth]

If I don't get wrong from BigSur normal booting if use the apfs_systemsnapshot tagging an empty string, without deleting snapshot "sudo mount -uw /" should work keeping the apple-UUID snapshots, but snapshots are part of time machine (maybe since APFS time machine) that @civotit already tested:
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28710826
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28712059

in few words when a time machine backup is made or restored, after you can't use "sudo mount -uw /", because it is tagged as snapshot booting regardless of system unsealed.

I finally had time to look at what went wrong with my upgrade install from beta 3 to beta 4 using your installer patcher. This was starting from an unsealed root volume which still had snapshots and had Catalina's IO80211Family.kext and High Sierra's AppleHDA.kext in L*/E* and AppleIntelPIIXATA.kext, telemetrap.kext and LegacyUSBInjector.kext in S*/L*/E*. As I expected, the patched installer overwrote the legacy kext in S*/L*. Where the installation really went off the rails was in its handling of L*/E*. The resulting beta 4 installation, which wouldn't boot even with the usual adjustments to Preboot, had a Big Sur Data volume which only had a Previous Library but no Library directory. So it appears that the upgrade process choked on migrating the changes in L*/E*. IMHO, the big problem with the current patched installer is that it exits in a rather messy state on legacy machines (since it doesn't install a usable prelinked kernel or the required legacy kext).
I was forced to do a clean install of beta 4 and noticed the same odd behavior that I had seen before with your patched installers. When the installation 'completes, it ends up in a failed boot loop due to the absence of the installation of the custom com.apple.Boot.plist, moving aside PlatformSupport.plist, installing the modified boot.efi and the legacy usb prelinkedkernel. The interesting bit is that when you reboot under Catalina and mount the unsealed Big Sur root volume, delete and replace AppleHDA.kext and IO80211Family.kext in S*/E* and reboot, those changes don't survive the reboot (despite the Big Sur root volume allowing 'mount -uw /Volumes/BigSur' prior to the changes being made. It is almost as if the Update snapshot volume is somehow blocking those changes from surviving despite the Update volume showing no directories for /S*/E*.

 

[Payne Mononymous Bachman]

Anybody having any luck with Big Sur on a early 2013 iMac? Interesting in hearing your thoughts or success with running Big Sur on an early 2013 iMac.
I would also like to take the time to thank everyone for all of their hard work that they are doing to create a successful Mac OS Big Sur patcher.

 

[joelw135]

@dosdude1 Are you working on a patcher for Big Sur, sorry if I missed your answer if posted before.

 

[jhowarth]

It seems that installation of packages with kernel extensions may be non-viable on unsupported machines. In particular, if you attempt to install 'Google Drive File Stream', an alert appears indicating that the Security and Preferences panel needs to be opened but, when opened, no request to authorize the loading of the kernel extension is presented unlike on a supported machine. Instead, immediately after the dialog with that request appears an error dialog comes up from Google Drive indicating that it had stopped unexpectedly.

 

[jackluke]

It seems that installation of packages with kernel extensions may be non-viable on unsupported machines. In particular, if you attempt to install 'Google Drive File Stream', an alert appears indicating that the Security and Preferences panel needs to be opened but, when opened, no request to authorize the loading of the kernel extension is presented unlike on a supported machine.

If you used my patched prelinkedkernel, then apply this to fix third party app permissions:
BigSur tccutil fix.command.zip

I usually install kext on /S*/L*/E*/ with "sudo mount -uw /" (without snapshot booting), but they should work also on /L*/E*/ .

 

[jhowarth]

If you used my patched prelinkedkernel, then apply this to fix third party app permissions:
BigSur tccutil fix.command.zip

I usually install kext on /S*/L*/E*/ with "sudo mount -uw /" (without snapshot booting), but they should work also on /L*/E*/ .

I'll have to look at my supported machine to confirm where the kext actually lands there. In the bom files from the Google Drive File Stream install, I see "Google Drive File Stream.app/Contents/MacOS/dfsfuse.kext" but no installed copy in /S*/L*/E* or /L*/E*. Interestingly, Dropbox installs and works fine but it authorizes in the Security and Privacy panel in the Privacy tab rather than in the General tab. Weirdly, I don't see a Dropbox kext loaded but it seems to be working none the less.

 

[jackluke]

I'll have to look at my supported machine to confirm where the kext actually lands there. In the bom files from the Google Drive File Stream install, I see "Google Drive File Stream.app/Contents/MacOS/dfsfuse.kext" but no installed copy in /S*/L*/E* or /L*/E*. Interestingly, Dropbox installs and works fine but it authorizes in the Security and Privacy panel in the Privacy tab rather than in the General tab. Weirdly, I don't see a Dropbox kext loaded but it seems to be working none the less.

I don't use that app, but just found this answer on reddit:

sudo kextload "/Applications/Google Drive File Stream.app/Contents/MacOS/dfsfuse.kext"

1>/dev/null 2>/dev/null /Applications/Google\ Drive\ File\ Stream.app/Contents/MacOS/Google\ Drive\ File\ Stream &