macOS 11 Big Sur on Unsupported Macs Thread

[jackluke]

I got this:

View attachment 963284

Maybe for me worked because I have "sudo mount -uw /" and snapshot booting disabled, but try from an USB Big Sur Installer it should work because from there the System volume is already mountable:

mount -uw /Volumes/BigSurLabel

/S*/I*/C*/Share*/C*/M*/Share*

 

[MacHacJac]

While I was editing the Utilities.plist for customize menu, I noticed that on the BigSur BaseSystem.dmg there is an apple app indicated as ARM only, but it works also on Intel cpus, you can launch it even directly from an USB BigSur Installer or Recovery terminal: /System/Installation/CDIS/Share*/C*/M*/Share*

this should be the new apple "target disk mode" that they dropped on BigSur but made for ARM , haven't tested it yet but the app launches also from a BigSur normal booting, the app works only on BigSur because build for SDK 11.0 , here is attached.

Any other findings on the utilities menu patching?

 

[jackluke]

Any other findings on the utilities menu patching?

On BaseSystem mounted Applications a "DiagsLoader.app" that is for diagnostics and should let to reboot on BigSur hidden Recovery (currently bootable from opencore).

 

[nasimon-]

Is there a way to fix wifi after complete installation?
I'm using on cable, and OS is working perfectly

 

[justperry]

Is there a way to fix wifi after complete installation?
I'm using on cable, and OS is working perfectly

Read the Micropatcher "Readme"

 

[nasimon-]

Read the Micropatcher "Readme"

My FileVault was turned on, thanks

 

[Aurelio Pertuz]

Failed to locate Big Sur recovery USB stick for unpatching. If all else fails, try specifying the path to the USB stick as a command line parameter to this script. helppp

 

[RITAMA]

I wrote that you should do that from a Big Sur Recovery environment , though it is also doable from normal booting, but with few changes, first requirement is csrutil authenticated-root disable, then from your picture, copy paste one line at once:

sudo -s

csrutil authenticated-root

(check that it is disabled)

diskutil mount disk1s5

mount -uw /Volumes/MacOs\ 1

(because the label MacOs is already in use by disk1s5s1 that is its snapshot)

(this makes writable your BigSur system disk1s5)

cd /S*/L*/File*/apfs*/C*/R*/

./apfs_systemsnapshot -v /Volumes/MacOs\ 1  -r ""

(this tags an empty string to disable snapshot booting disk1s5s1 on your BigSur system disk1s5)

What wrong with this ?

 

[buckrock]

Failed to locate Big Sur recovery USB stick for unpatching. If all else fails, try specifying the path to the USB stick as a command line parameter to this script. helppp

Slow down! Try it again paying close attention to spaces. Try to do it by Barry's drag and drop procedure described in his great README notes at Step 6. I know, unpatching step isn't that one -- just use that technique.

 

[Aurelio Pertuz]

I already did it with great attention, step by step very carefully

 

[buckrock]

What wrong with this ?

Did you mean to skip csrutil authenticated-root after sudo -s?

 

[buckrock]

I already did it with great attention, step by step very carefully

Are you booted in Big Sur or Catalina? Did your usb installer mount? Can you navigate around in your usb stick with your Finder?

... And in the words of Barry (README after Step 12):
"The best way to remove the patch from the USB stick is to redo createinstallmedia, but if you are working on patcher development or otherwise need a faster way to do it, you can run unpatch.sh."
... Amen!

 

[Aurelio Pertuz]

Good night, I created the bootable unit from the terminal, then I write sudo and drag the patch, then the pendrive but no matter how hard I try, that error comes out, as if I did not recognize the pendrive, if I can see the pendrive in the finder, I do it from big sur beta 6

Are you booted in Big Sur or Catalina? Did your usb installer mount? Can you navigate around in your usb stick with your Finder?

... And in the words of Barry (README after Step 12):
"The best way to remove the patch from the USB stick is to redo createinstallmedia, but if you are working on patcher development or otherwise need a faster way to do it, you can run unpatch.sh."
... Amen!

Good night, I created the bootable unit from the terminal, then I write sudo and drag the patch, then the pendrive but no matter how hard I try, that error comes out, as if I did not recognize the pendrive, if I can see the pendrive in the finder, I do it from big sur beta 6

 

[RITAMA]

Did you mean to skip csrutil authenticated-root after sudo -s?

Operation Not Permit after
./apfs_systemsnapshot -v /Volumes/MacOs\ 1 -r ""

 

[buckrock]

Operation Not Permit after
./apfs_systemsnapshot -v /Volumes/MacOs\ 1 -r ""

Ok, here's the manual for apfs_systemsnapshot:

....% man apfs_systemsnapshot

APFS_SYSTEMSNAPSHOT(8)    BSD System Manager's Manual   APFS_SYSTEMSNAPSHOT(8)

NAME
     apfs_systemsnapshot -- create and tag APFS system snapshots

SYNOPSIS
     apfs_systemsnapshot -r snapshot_name -v mount_point
     apfs_systemsnapshot -s snapshot_name -v mount_point
     apfs_systemsnapshot -h

DESCRIPTION
     The apfs_systemsnapshot utility can create or tag a new snapshot of a
     Signed System Volume.

     apfs_systemsnapshot requires disabling the authenticated-root System
     Integrity Protection configuration from recoveryOS.  Once disabled, non-
     sealed snapshots can be created and tagged as the snapshot to be rooted
     from.

     apfs_systemsnapshot should not be used when working on kernel extension
     development, bless(8) should be used instead.

     The mount_point parameter should be the mount point of a Signed System
     Volume.

     The options are as follows:

     -r snapshot_name      Tag snapshot_name as the root snapshot to boot from
                       upon next boot.
     -s snapshot_name      Create a new system snapshot named snapshot_name.
     -h                             Print a usage message.
EXIT STATUS
     apfs_systemsnapshot exits with 0 on success, and >0 if an error occurs.

So, as it says: apfs_systemsnapshot requires disabling the authenticated-root System Integrity Protection configuration from recoveryOS.
Seems that you need to be in recoveryOS and run at least csrutil disable. Can you confirm you did this?

 

[Th3odor3]

I have released Big Sur Micropatcher v0.3.3. Release notes:

GitHub - barrykn/big-sur-micropatcher: A primitive USB patcher for installing macOS Big Sur on unsupported Macs

A primitive USB patcher for installing macOS Big Sur on unsupported Macs - barrykn/big-sur-micropatcher

github.com

I tried the v0.3.3 patcher and I'm getting a NO Strike Thru circle with a slash at boot with macOS Big Sur install...?

 

[David dongfox]

What wrong with this ?

i don’t know? see my post #4848.

 

[Alex-Microsmeta]

Hi @Barry K. Nathan !

Thanks to @jackluke support, Big Sur Beta 9 is quite usable on Mac mini 10, but only wifi and bluetooh are working, usb and internal audio are missing.

I'm trying to patch kexts on Mac mini 2010 (Macmini4,1) using your patcher 0.3.3. Only from dosdude1 Catalina installer I have managed to set csrutil enable and csrutil authenticated, but still on Big Sur I get error 77 and 66 trying
(sudo) mount - uw /

With your BigSur Micropatcher 0.3.2 I have finally activated Wifi, but I get errors inflating other kexts.

Which is the right way to apply you patch-kext? The destination is BigSur EXT

OUTPUT:
"Done changing boot-args and csrutil settings.
csr-active-config appears to be set incorrectly:
csr-active-config w%00%00%00
To fix this, please boot from the setvars EFI utility, then boot back into macOS and try again."

EDIT: After reinstalling micropatcher 0.3.3 I still got errors inflating kexts (connection invalid, watch images attached) do I need an internet connection?) but now I can boot BS B9 without OpenCore and BS loader has been renamed from BigSur EXT - Dati to BigSur!

THANK YOU FOR WHAT YOU ARE DOING FOR US!

 

[Ausdauersportler]

Hi @Barry K. Nathan !

Big Sur Beta 9 is quite usable on Mac mini 10, but only wifi and bluetooh are working, usb and internal audio are missing.

I'm trying to patch kexts on Mac mini 2010 (Macmini4,1) using your patcher 0.30.3. Only from dosdude1 Catalina installer I have managed to set csrutil enable and csrutil authenticated, but still on Big Sur I get error 77 and 66 trying
(sudo) mount - uw /

With your BigSur Micropatcher 0.30.2 I have finally activated Wifi, but I get errors inflating other kexts.

Which is the right way to apply you patch-kext? The destination is BigSur EXT - Dati

THANK YOU FOR WHAT YOU ARE DOING FOR US!

Answering from phone: Search for my first posts on this thread about patching iMac - there I documented a recipe to how to get access to a writable version of SLE ... it is using the snapshots. You could also check the patch-kext.sh script - magically it can do what you want to achieve

 

[telepati]

What wrong with this ?

Operation Not Permit after
./apfs_systemsnapshot -v /Volumes/MacOs\ 1 -r ""

It is normal cause you are not in the Recovery.

What @jackluke said; "Should do that from a Big Sur Recovery environment".

 

[Barry K. Nathan]

Hi @Barry K. Nathan !

Thanks to @jackluke support, Big Sur Beta 9 is quite usable on Mac mini 10, but only wifi and bluetooh are working, usb and internal audio are missing.

I'm trying to patch kexts on Mac mini 2010 (Macmini4,1) using your patcher 0.3.3. Only from dosdude1 Catalina installer I have managed to set csrutil enable and csrutil authenticated, but still on Big Sur I get error 77 and 66 trying
(sudo) mount - uw /

With your BigSur Micropatcher 0.3.2 I have finally activated Wifi, but I get errors inflating other kexts.

Which is the right way to apply you patch-kext? The destination is BigSur EXT

OUTPUT:
"Done changing boot-args and csrutil settings.
csr-active-config appears to be set incorrectly:
csr-active-config w%00%00%00
To fix this, please boot from the setvars EFI utility, then boot back into macOS and try again."

EDIT: After reinstalling micropatcher 0.3.3 I still got errors inflating kexts (connection invalid, watch images attached) do I need an internet connection?) but now I can boot BS B9 without OpenCore and BS loader has been renamed from BigSur EXT - Dati to BigSur!

THANK YOU FOR WHAT YOU ARE DOING FOR US!

Make sure to use the --2010 option with patch-kexts.sh. That should fix USB and sound.

 

[David dongfox]

I wrote that you should do that from a Big Sur Recovery environment , though it is also doable from normal booting, but with few changes, first requirement is csrutil authenticated-root disable, then from your picture, copy paste one line at once:

sudo -s

csrutil authenticated-root

(check that it is disabled)

diskutil mount disk1s5

mount -uw /Volumes/MacOs\ 1

(because the label MacOs is already in use by disk1s5s1 that is its snapshot)

(this makes writable your BigSur system disk1s5)

cd /S*/L*/File*/apfs*/C*/R*/

./apfs_systemsnapshot -v /Volumes/MacOs\ 1  -r ""

(this tags an empty string to disable snapshot booting disk1s5s1 on your BigSur system disk1s5)

cd /S*/L*/File*/apfs*/C*/R*/

./apfs_systemsnapshot -v /Volumes/MacOs\ 1 -r ""

(this tags an empty string to disable snapshot booting disk1s5s1 on your BigSur system disk1s5)[/CODE]
[/QUOTE]this 2 lines not working . try for many many time.

 

[jackluke]

cd /S*/L*/File*/apfs*/C*/R*/

./apfs_systemsnapshot -v /Volumes/MacOs\ 1 -r ""

(this tags an empty string to disable snapshot booting disk1s5s1 on your BigSur system disk1s5)

this 2 lines not working . try for many many time.

Could you check from terminal: diskutil info /Volumes/MacOs | grep Sealed

if Sealed is "Broken" then means you have a sealed System and so you can't do "apfs_systemsnapshot" from desktop but only from a BigSur recovery environment.

 

[Alex-Microsmeta]

@Barry K. Nathan @jackluke Confirmed: Reinstalled BS B9 from scratch instead of unpatching and retrying, using only 0.3.3 patcher. (After installation I had to remake the createinstaller + micropatcher.sh + install-setvar.sh because it was no more accessible (forbidden symbol, also when trying booting BS B9 without OpenCore) Now Wifi works and I can boot it again from Apple Booter without OpenCore but USB mouse and keyboard do not work while USB mic and webcam yes (???) and (sudo) mount -uw / returns error 77 and 66. I really do not understand what is happening, but this report could help you both to fix something on Mac mini 2010 (Macmini4,1) On my previous post you can find the screenshots with errors on patch-kekts.

 

[Maclinux]

One question guys. I am going to install Beta 9 on my MBP 9.2 mid 2012 not retina and I am wondering if I should use the 0.19 micropatcher for the wifi to work (as in previous versions) or can I use the most current micropatcher?