Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
Hallo, Big Sur don‘t boot with the micropatch. Can I do something? iMac 9,1 I have installed Catalina on AFPS
You have to go this route applying the @jackluke patches to boot a core2duo system - this looks complicated but following exactly his post I got a bootable USB installer.

You probably will not have a lot of fun with a system not offering a Metal GPU...and you need in any case a separate partition (not a container) to install Big Sur Beta 9 unless you plan to overwrite the existing Catalina installation. Start with a 100GB APFS partition.
 

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
Hallo, Big Sur don‘t boot with the micropatch. Can I do something? iMac 9,1 I have installed Catalina on AFPS
I have just updated the README:
Currently not supported by this patcher, but future support may be possible:

  • Macs which have a Penryn CPU but which do not officially support High Sierra: These include pre-2008 iMacs with upgraded CPUs, as well as most 2008 and many 2009 Mac models. All of these require "legacy USB" support, just like (for instance) 2010 white MacBooks. Once support for those MacBooks is improved in a future patcher release, perhaps support for some of these Macs will be worth revisiting.
  • Without a Metal GPU upgrade (certainly possible on 2008 Mac Pros, not sure about the iMacs, not possible on the MacBooks and Mac Minis), these are expected to be unusably slow.
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
Hello, I can't handle jackluke instructions? Are there detailed instructions? Best in German ?
Oh, yes you can! Make a clean USB installer, plug it in, download the attached zip file from the post I mentioned before, apply both commands one by one just by clicking on it. These will load a lot of files from a remote server and patch your newly made USB installer. Half an hour later you can boot the patched installer following the instructions in the post and on the pictures.
 

buckrock

macrumors 6502
Jul 24, 2020
297
424
Fresno, California
I have just released Big Sur Micropatcher v0.4.1.

This release fixes bugs in the 2011 --iMac Metal GPU option in patch-kexts.sh. Thanks again to Ausdauersportler for the code contribution. There are also some corrections and updates in the README.

Note that there are USB problems on many 2010 and earlier Macs, which are being tracked as GitHub issue #68. I plan to fix these problems in another release, perhaps later this week.

@Barry K. Nathan: Thanks for this newest micropatcher. Regarding README Step 7:

------------------------------------------Quote starts--------------------------------------
" - As of Big Sur Micropatcher v0.4, `install-setvars.sh` will now install a version of setvars which enables Apple's System Integrity Protection (SIP) and Authenticated Root Volume (ARV) security features if it is run on a Late 2013 iMac, or a version of setvars which disables both of these features if it is run on any other model of Mac. You may add a `-d` option to force the installation of the setvars version which disables these features (for instance, if you are creating the USB on a Late 2013 iMac but you will be using it on another Mac). You may also add a `-e` option to for the installation of the setvars version which enables these features (for instance, if you are installing Big Sur on a 2012 or 2013 Mac that has been upgraded with an 802.11ac WiFi card and therefore does not need a WiFi patch)."
------------------------------------------End Quote----------------------------------------

Does this mean the '-e' option is redundant if installing on a 15" MBP mid-2012 retina 10,1 that has an 802.11ac card? It seems that the 'install-setvars.sh' will sense and install with SIP and ARV disabled without the '-e'.

I suppose the line that confuses me is: "... WiFi card and therefore does not need a WiFi patch." Does the 'install-setvars.sh' now by default install a series of kexts, especially those regarding WiFi, and enable SIP/ARV?

... and, in short, would it be good for the MBP mid-2012 (above) have SIP/ARV enabled? ... or am I reading this wrong?
 
Last edited:
  • Like
Reactions: TimothyR734

SUGAR RAY WONKA

macrumors regular
Oct 1, 2019
104
93
@Barry K. Nathan: Thanks for this newest micropatcher. Regarding README Step 7:

------------------------------------------Quote starts--------------------------------------
" - As of Big Sur Micropatcher v0.4, `install-setvars.sh` will now install a version of setvars which enables Apple's System Integrity Protection (SIP) and Authenticated Root Volume (ARV) security features if it is run on a Late 2013 iMac, or a version of setvars which disables both of these features if it is run on any other model of Mac. You may add a `-d` option to force the installation of the setvars version which disables these features (for instance, if you are creating the USB on a Late 2013 iMac but you will be using it on another Mac). You may also add a `-e` option to for the installation of the setvars version which enables these features (for instance, if you are installing Big Sur on a 2012 or 2013 Mac that has been upgraded with an 802.11ac WiFi card and therefore does not need a WiFi patch)."
------------------------------------------End Quote----------------------------------------

Does this mean the '-e' option is redundant if installing on a 15" MBP mid-2012 retina 10,1 that has an 802.11ac card? It seems that the 'install-setvars.sh' will sense and install with SIP and ARV disabled without the '-e'.

I suppose the line that confuses me is: "... WiFi card and therefore does not need a WiFi patch." Does the 'install-setvars.sh' now by default install a series of kexts, especially those regarding WiFi, and enable SIP/ARV?

... and, in short, would it be good for the MBP mid-2012 (above) have SIP/ARV enabled? ... or am I reading this wrong?

Same question from me too, Barry, in relation to Mac mini Late 2012 *without* upgraded wifi card please and thanks!
 
  • Like
Reactions: TimothyR734

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
@Barry K. Nathan: Thanks for this newest micropatcher. Regarding README Step 7:

------------------------------------------Quote starts--------------------------------------
" - As of Big Sur Micropatcher v0.4, `install-setvars.sh` will now install a version of setvars which enables Apple's System Integrity Protection (SIP) and Authenticated Root Volume (ARV) security features if it is run on a Late 2013 iMac, or a version of setvars which disables both of these features if it is run on any other model of Mac. You may add a `-d` option to force the installation of the setvars version which disables these features (for instance, if you are creating the USB on a Late 2013 iMac but you will be using it on another Mac). You may also add a `-e` option to for the installation of the setvars version which enables these features (for instance, if you are installing Big Sur on a 2012 or 2013 Mac that has been upgraded with an 802.11ac WiFi card and therefore does not need a WiFi patch)."
------------------------------------------End Quote----------------------------------------

Does this mean the '-e' option is redundant if installing on a 15" MBP mid-2012 retina 10,1 that has an 802.11ac card? It seems that the 'install-setvars.sh' will sense and install with SIP and ARV disabled without the '-e'.

I suppose the line that confuses me is: "... WiFi card and therefore does not need a WiFi patch." Does the 'install-setvars.sh' now by default install a series of kexts, especially those regarding WiFi, and enable SIP/ARV?

... and, in short, would it be good for the MBP mid-2012 (above) have SIP/ARV enabled? ... or am I reading this wrong?
No, you should use the -e option in your case. Right now the automatic detection is based on the Mac model, not by actually detecting the WiFi card. (I probably should change that, now that I think about it. However, it was easier to implement it by detecting the Mac model instead of the WiFi card. Edit: Just realized WiFi card on its own isn't enough for detection -- 2011 MacBook Pros for example need ARV disabled for other reasons even with upgraded WiFi.) And on any Macs that don't need a WiFi patch, it's better to keep SIP and ARV enabled -- better security.


By the way, I noticed that a lot of the information in the first post was getting outdated, so earlier today I did some editing. I didn't fix everything (especially things that will become outdated again once the final Big Sur release happens), but hopefully it's better than before.
[automerge]1602631735[/automerge]
Same question from me too, Barry, in relation to Mac mini Late 2012 *without* upgraded wifi card please and thanks!
Without upgraded WiFi card, DO NOT use the -e option, ARV needs to stay disabled.
 

thatsmeonlyme

macrumors regular
May 30, 2018
222
303
Loewenstein Germany
I have just released Big Sur Micropatcher v0.4.1.

This release fixes bugs in the 2011 --iMac Metal GPU option in patch-kexts.sh. Thanks again to Ausdauersportler for the code contribution. There are also some corrections and updates in the README.

Note that there are USB problems on many 2010 and earlier Macs, which are being tracked as GitHub issue #68. I plan to fix these problems in another release, perhaps later this week.

I can confirm the USB problem on cMP 5.1 mid 2010.
1. USB drives are connected without any problems and also can be ejected without crash.
2. Drives to mount with for example VMs crash connecting and disconnecting
3. USB Hubs crash when connecting (Hot plug). They get accepted when booting with hardware connected
4. USB 2 connections (original USB Ports of the machine) do not mount when connected in running machine

These are my experiences. In the developer forums the bug is filed but there is no solution until now. I think that there are more users not have experienced this because as me having noticed this very late. There´s one hint of a user having experienced this up from DP 7.

Maybe my description cab be helpful for your examination and diagnosis.
 

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
I can confirm the USB problem on cMP 5.1 mid 2010.
1. USB drives are connected without any problems and also can be ejected without crash.
2. Drives to mount with for example VMs crash connecting and disconnecting
3. USB Hubs crash when connecting (Hot plug). They get accepted when booting with hardware connected
4. USB 2 connections (original USB Ports of the machine) do not mount when connected in running machine

These are my experiences. In the developer forums the bug is filed but there is no solution until now. I think that there are more users not have experienced this because as me having noticed this very late. There´s one hint of a user having experienced this up from DP 7.

Maybe my description cab be helpful for your examination and diagnosis.
This is completely unrelated to the USB problem that I'm going to fix in an upcoming patcher release (the problem I was referring to can affect MacPro3,1, but not 4,1 or 5,1), but thank you for the information.
 

Franky1971

macrumors member
Sep 29, 2020
30
35
First of all, thank you for your support. So far, so good. I could install the boot. In the terminal then /V*/I*/H* comes "no execute binary file" what's going on?
 
  • Like
Reactions: TimothyR734

Franky1971

macrumors member
Sep 29, 2020
30
35
Hello, I'm ready. But when installing when there are only 12 minutes left, the iMac 9.1 reboats. I can't get anywhere with step 2. What do I have to do? Thank you
 
  • Like
Reactions: TimothyR734

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
Hello, I'm ready. But when installing when there are only 12 minutes left, the iMac 9.1 reboats. I can't get anywhere with step 2. What do I have to do? Thank you

If you can't continue the stage2 installer (apart a non-APFS Legacy USB Mac) means that:

- you are not installing BigSur on an internal SATA disk (installing on internal SATA, stage2 is automatic for Legacy USB Mac)

- you are installing BigSur on an external USB hard disk, then it's required a concurrently Legacy USB injector for USB root disk and USB input devices (mainly USB mouse and keyboard but also internal trackpad and keyboard, webcam and bluetooth are USB internal device, wifi is instead a mini pci-express internal device)

- you are installing on a non-APFS Mac so to select the hidden "macOS stage2 Installer" you need USBOpenCoreAPFSloader4b

Anyway if you have Mojave or Catalina, boot from there and use this: BigSur BaseSystem stage2 installer fix.zip

This should fix and continue the stage2 installer on Legacy USB Mac when targeting an external USB macOS Installer.
After stage2 you need USBopencore to boot with CMD+S and exit , anyway if apple releases today beta 10 , I try to simplify this step.
 
Last edited:

Franky1971

macrumors member
Sep 29, 2020
30
35
I've come that far, but I can't enter it. Mouse/keyboard doesn't work. What to do? iMac 9,1
 

Attachments

  • EACD93DE-7E44-4EE2-857B-B0155ABA54EE.jpeg
    EACD93DE-7E44-4EE2-857B-B0155ABA54EE.jpeg
    452.2 KB · Views: 132
  • EACD93DE-7E44-4EE2-857B-B0155ABA54EE.jpeg
    EACD93DE-7E44-4EE2-857B-B0155ABA54EE.jpeg
    452.2 KB · Views: 123

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
I've come that far, but I can't enter it. Mouse/keyboard doesn't work. What to do? iMac 9,1

Try my customised USBopencore (for Legacy USB it's 4b version): https://github.com/jacklukem/USBOpenCoreAPFSloader/releases/tag/4.3

you can install it on any FAT32 USB device, then reboot, hold alt-option key select the EFI Boot with its custom opencore icon, then another bootloader shows and with keyboard arrows select the BigSur Preboot or Data label, press CMD+S then Enter key, after a short verbose mode with some messages "HID: Legacy Shim 2" simply type exit and it should boot to BigSur desktop with responsive mouse, keyboard, bluetooth, usb audio, iSight webcam and ethernet network.
 
Last edited:

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
I created a two partitions and installed Big sur on it. How do I get the usb Kexst installed?

It's not a BigSur USB kext replacement issue, rather parrotgeek1 LegacyUSBInjector.kext incompatible with BigSur beta 9 kmutil's UUID KernelCollections, currently I don't know a way to install properly that kext, but only to inject it through USBopencore on the BootKernelExtensions.kc with CMD+S and exit .
 
Last edited:
  • Like
Reactions: TimothyR734

Franky1971

macrumors member
Sep 29, 2020
30
35
That's how I did it. Thank you very much for your support. You guys are great. Is it possible to get Wi-Fi on board?
 

Attachments

  • image.jpg
    image.jpg
    653.6 KB · Views: 239
  • Like
Reactions: jackluke

SUGAR RAY WONKA

macrumors regular
Oct 1, 2019
104
93
No, you should use the -e option in your case. Right now the automatic detection is based on the Mac model, not by actually detecting the WiFi card. (I probably should change that, now that I think about it. However, it was easier to implement it by detecting the Mac model instead of the WiFi card. Edit: Just realized WiFi card on its own isn't enough for detection -- 2011 MacBook Pros for example need ARV disabled for other reasons even with upgraded WiFi.) And on any Macs that don't need a WiFi patch, it's better to keep SIP and ARV enabled -- better security.


By the way, I noticed that a lot of the information in the first post was getting outdated, so earlier today I did some editing. I didn't fix everything (especially things that will become outdated again once the final Big Sur release happens), but hopefully it's better than before.
[automerge]1602631735[/automerge]

Without upgraded WiFi card, DO NOT use the -e option, ARV needs to stay disabled.

Cheers, Barry, will do. I’m waiting for the GM release before using it.
 
  • Like
Reactions: Barry K. Nathan
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.