Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
A

Alex-Microsmeta

macrumors 6502
Jul 14, 2018
376
630
Rome
jackluke said:
I just made another installation of BigSur beta 3 on external drive, and as some already mentioned this "weird method" to allow "sudo mount -uw /", I confirm it worked, but the main condition is don't lose sight of "macOS Installer" progress install bar (on some disks can take more than 29 minutes up to one hour):

The BigSur installer has 3 main stages:

stage 1 : the BigSur logo enough quick loading bar "3 minutes remaining"
stage 2 : the apple logo that is the slow loading bar "29 minutes remaining"
stage 3 : the apple logo that is system sealing and snapshot booting

the gimmick is to skip the stage 3 , to do that you need to wait for the "29 minutes remaining" part, then after the auto reboot quickly hold alt-option key and don't select "macOS Installer" but select instead the "BigSur Data" , this should boot directly to desktop from where you can use "sudo mount -uw /" .

If after reboot you were distracted and stage 3 begins, you can force a power-off there, then power-on holding alt-option key and select "BigSur Data".

Since the "macOS Installer" is still in nvram, to avoid that after any reboot it could attempt to seal system (and snapshot booting of it), you have to select from System Preferences Startup Disk any other disk, so that "macOS Installer" is removed from list (maybe also a PRAM reset should work).
Click to expand...
@jackluke Just applying this workaround on BS Beta 4 Mac mini
 
  • Like
Reactions: TimothyR734
furdi

furdi

macrumors regular
Jun 13, 2019
124
196
Bucharest, Romania
Hi guys! Just downloaded the beta 4 and created the boot USB for my MBP mid 2012. ALso got Barry's last patch (0.0.18). Did anybody upgraded to Beta 4 from Beta 3 a MBP mid 2012? Much appreciated!
 
  • Like
Reactions: TimothyR734
MacHacJac

MacHacJac

Suspended
Jun 28, 2020
214
354
If I were to spoof my 2011 13" MBP, I have a few questions:
1) Clover or OpenCore? I see mixed opinions about both.
2) Where can I find the best tutorials for doing this?
3) What model of MacBook Pro would be "best" to spoof to for my model? I know I'll remove the spoofing, but I want to have a model that supports Big Sur but doesn't have stuff like Touch ID, touch bar, or the T2 Security chip. I'm thinking either Late 2013 or early 2015.
 
  • Like
Reactions: TimothyR734
jackluke

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
I release a new upgraded optimized version for unsupported Big Sur Mac :

USBOpenCoreAPFSloader4.app.zip

specifically it allows to boot an USB BigSur Installer and BigSur Installation (either internal or USB external) from any Penryn Core2Duo non-APFS or APFS mac (also Sandy Bridge and Ivy Bridge Mac) and are included some additional useful fixes :
  • @Syncretic AAAMouSSE.kext and telemetrap.kext (for SSE4.2 and AVX emulation and to block the com.apple.telemetry.plugin)
  • @parrotgeek1 LegacyUSBInjector.kext (to allow any legacy USB on BigSur also for non-APFS mac)
  • @ASentientBot nvenet.kext (for use Ethernet on Nvidia Chipset based Mac) and Disable Library Validation
  • preset nvram csr-active-config=%ff%0f%00%00 (that is an already disabled "csrutil authenticated-root" with any dmg support)
  • boot any stock BaseSystem.dmg from legacy USB Mac
  • preset nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"
  • used as default bootloader OpenCanopy (similar to the apple startup manager with VolumeIcon support)
  • allows to continue a BigSur stage2 installer from a non-APFS mac (simply selecting the "macOS Installer")
  • blocks EFI SMC firmware updates when spoofing to a supported mac
  • apple startup key combinations available at opencore menu (CMD+S , CMD+V and so on)
edit:
For those who have a non-APFS or legacy USB Mac that don't applied any prelinkedkernel fix (or BaseSystem fix), this USBopencore version uses an experimental legacyUSB fix on the BootKernelExtensions.kc , so if you don't have usb input output devices after the graphical environment, from OpenCore select your BigSur volume and use CMD+S then type "exit" to continue booting.
 
Last edited:
  • Like
  • Love
Reactions: olad, webg3, abelpinate and 14 others
Lucky736

Lucky736

macrumors 65816
Jan 18, 2004
1,004
679
US
jackluke said:
I release a new upgraded optimized version for unsupported Big Sur Mac :

USBOpenCoreAPFSloader4.app.zip

specifically it allows to boot any USB Big Sur Installer and any BigSur Installation (either internal or USB external) from any Penryn Core2Duo non-APFS or APFS mac (also Sandy Bridge and Ivy Bridge Mac) and are included some additional useful fixes :
  • @Syncretic AAAMouSSE.kext and telemetrap.kext (for SSE4.2 and AVX emulation and to block the com.apple.telemetry.plugin)
  • @parrotgeek1 LegacyUSBInjector.kext (to allow any legacy USB on BigSur also for non-APFS mac)
  • @ASentientBot nvenet.kext (for use Ethernet on Nvidia Chipset based Mac) and Disable Library Validation
  • preset nvram csr-active-config=%ff%0f%00%00 (that is an already disabled "csrutil authenticated-root" with any dmg support)
  • boot any stock BaseSystem.dmg from legacy USB Mac
  • preset nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"
  • used as default bootloader OpenCanopy (similar to the apple startup manager with VolumeIcon support)
  • allows to continue a BigSur stage2 installer from a non-APFS mac (simply selecting the "macOS Installer")
  • blocks EFI SMC firmware updates when spoofing to a supported mac
  • apple startup key combinations available at opencore menu (CMD+S , CMD+V and so on)
Click to expand...

Amazing work everyone. Truly.
 
  • Like
Reactions: Alex-Microsmeta and TimothyR734
furdi

furdi

macrumors regular
Jun 13, 2019
124
196
Bucharest, Romania
Ronald Steven said:
thanks @Barry K. Nathan

Fixed the problem, reboot the nvram (alt+cdm+p+r), then boot in Big Sur shows a crossed circle so boot in Big Sur Recovery mode to fix it and use terminal and type:

nvram boot-args="-no_compat_check"

Then the apps will restore and ask the mic and camera permissions again, and viola!!! this may works for you @Muhammad Faruq
Click to expand...

Hi! Have the same problem with 3rd party apps (skype). After reboot nvram and afer the crossed circle, went for the big Sur Recovery and I have only Over the internet Recovery... Is that ok? Because now it doesn't boot anymore! It's like there is no os installed. I have only EFI... Please help!

edit: Stupid mistake... Sorry... forgot to write the '-' before "no_compat...". Fixed! Thank you @Ronald Steven! @Muhammad Faruq did it worked for you too?
 
Last edited:
  • Like
Reactions: Ronald Steven, TimothyR734 and Barry K. Nathan
alexanderguad

alexanderguad

macrumors newbie
Jun 22, 2020
3
6
Hello All

Im on a MBP Mid 2012 15inch, I used the BigSurOTAswufix to download the Beta 4 update (12.30gb).

I am trying to update from Beta two, To Four.

It's put the installer In my applications folder, which I assume is what is supposed to happen. I can't get past this, Im assuming I'm missing something, Or I have forgotten what to do next, Im very new to this. So any guidance or help would be much appreciated!
Screen Shot 2020-08-05 at 10.04.04 AM.png
 
  • Like
Reactions: dustin2002zh and TimothyR734
A

Alex-Microsmeta

macrumors 6502
Jul 14, 2018
376
630
Rome
@Jakeluke I cannot skip Stage 3 of macOS BS Beta 4 installation, selecting BigSur - data booter, because it is not present on Apple bootloader or OpenCoreLoader3, I have only macOS install. So I have choosen it. Then I will use OpenCoreLoader4 to try to fix usb and internal sound. Is the same of applying your old beta3 fixer?
 
  • Like
Reactions: coolio2004 and TimothyR734
webg3

webg3

macrumors 6502a
Jul 19, 2018
507
774
jackluke said:
On beta 4 Safari.app is crashing, so for now use Chrome or any other internet browser.

Anyway the crash is weird because it reports:

OS Version: Mac OS X 10.16 (20A5343i)

Code: 
due to uncaught exception 'NSInternalInconsistencyException',
reason: 'Invalid parameter not satisfying: image != nil'
terminating with uncaught exception of type NSException

while from beta 3 apple used 11.0 as their SDK naming .
Click to expand...

Safari working for me, no bugs.
 
  • Like
Reactions: dustin2002zh, TimothyR734 and Barry K. Nathan
Barry K. Nathan

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
I just updated my patcher again to v0.0.19. I wanted to get a couple of quick fixes out this morning, in case the public beta is released later today:
  • The Ethernet fix for 2011 Macs now works on beta 4 as well as beta 3 (and will hopefully keep working in the future).
  • set-vars.sh no longer sets amfi_get_out_of_my_way=1; this appears to fix camera and microphone permissions problems. Thanks to Ronald Steven for troubleshooting efforts which led to the discovery of this fix.
If you used a previous version of this patcher, you may want to change your boot-args in nvram. A simple sudo nvram boot-args="-no_compat_check" in Terminal might do the trick. Or nvram boot-args="-no_compat_check" from any macOS installer or Recovery (version doesn't matter). Or you can download this version of the patcher, run unpatch.sh then micropatcher.sh, boot from the patched USB stick, and repeat step 6. Or, if everything is working for you, you can just let the patcher handle it the next time you're updating to a newer Big Sur beta.
[automerge]1596639813[/automerge]
webg3 said:
Safari working for me, no bugs.
Click to expand...
I'm not having any Safari crashes either (on my MacBookPro8,1).
 
  • Like
Reactions: maxsp97, trifero, Ronald Steven and 4 others
furdi

furdi

macrumors regular
Jun 13, 2019
124
196
Bucharest, Romania
Barry K. Nathan said:
I just updated my patcher again to v0.0.19. I wanted to get a couple of quick fixes out this morning, in case the public beta is released later today:
  • The Ethernet fix for 2011 Macs now works on beta 4 as well as beta 3 (and will hopefully keep working in the future).
  • set-vars.sh no longer sets amfi_get_out_of_my_way=1; this appears to fix camera and microphone permissions problems. Thanks to Ronald Steven for troubleshooting efforts which led to the discovery of this fix.
If you used a previous version of this patcher, you may want to change your boot-args in nvram. A simple sudo nvram boot-args="-no_compat_check" in Terminal might do the trick. Or nvram boot-args="-no_compat_check" from any macOS installer or Recovery (version doesn't matter). Or you can download this version of the patcher, run unpatch.sh then micropatcher.sh, boot from the patched USB stick, and repeat step 6. Or, if everything is working for you, you can just let the patcher handle it the next time you're updating to a newer Big Sur beta.
[automerge]1596639813[/automerge]

I'm not having any Safari crashes either (on my MacBookPro8,1).
Click to expand...

Hi Barry. Sorry to bother you. When trying to create the USBboot in order to update to beta 4 from beta 3, creatmedia reports the following:

objc[1001]: Class IASNightInstallSupport is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff8a37cd78) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x10c295ac0). One of the two will be used. Which one is undefined.
objc[1001]: Class IASSystemInformation is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff8a37ceb8) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x10c295bd8). One of the two will be used. Which one is undefined.
Ready to start.

It is not the first time I am using createinstallmedia but it's the first time I see something like this. Any thoughts?

Thank you sir and sorry again...
 
  • Like
Reactions: Barry K. Nathan and TimothyR734
jackluke

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
Alex-Microsmeta said:
@Jakeluke I cannot skip Stage 3 of macOS BS Beta 4 installation, selecting BigSur - data booter, because it is not present on Apple bootloader or OpenCoreLoader3, I have only macOS install. So I have choosen it. Then I will use OpenCoreLoader4 to try to fix usb and internal sound. Is the same of applying your old beta3 fixer?
Click to expand...

You need an already installed BigSur and upgrade (or reinstall) that installation from an USB BigSur Installer to select the "BigSur Data", otherwise only "macOS Installer" is showed.

For BigSur beta4 these still works:

BigSur IvyBridge beta3 prelinkedkernel fix.command.zip

BigSur Penryn beta3 prelinkedkernel fix.command.zip

BigSur beta3 Nvidia Tesla fix.command.zip
 
  • Like
Reactions: Alex-Microsmeta, Barry K. Nathan, ASentientBot and 2 others
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom