macOS 11 Big Sur on Unsupported Macs Thread

[jackluke]

Let me rephrase it: What testheit posted was, for me, the secret to getting kmutil to build a BootKernelExtensions.kc with a working LegacyUSBInjector.

Actually, there are two other catches, I remember now:

1. kmutil can build both the BootKernelExtensions.kc and the SystemKernelExtensions.kc in one command, but if you do that, LegacyUSBInjector won't work. You have to build the two of them with two different commands.

2. You have to use a chroot. I ran into some weird error with kmutil that magically disappeared once I started using a chroot.

The code that I have that does it is something like this ("$VOLUME" is the path to the Big Sur system volume):

chroot "$VOLUME" kmutil create -n boot \
    --kernel /System/Library/Kernels/kernel \
    --volume-root / \
    --bundle-path /System/Library/Extensions/LegacyUSBInjector.kext \
    --boot-path /System/Library/KernelCollections/BootKernelExtensions.kc
chroot "$VOLUME" kmutil create -n sys \
    --kernel /System/Library/Kernels/kernel \
    --volume-root / \
    --system-path /System/Library/KernelCollections/SystemKernelExtensions.kc \
    --boot-path /System/Library/KernelCollections/BootKernelExtensions.kc
"$VOLUME/usr/sbin/kcditto"
bless --folder "$VOLUME"/System/Library/CoreServices --bootefi --create-snapshot

I ran this on my MacBookPro8,1 then booted the result on my MacBook6,1 and it worked. (I tried something else after that, and that's what caused my current situation where the two MacBooks boot from different snapshots on the same external SSD.)

By the way, you can run strings on the generated BootKernelExtensions.kc and look for "com.parrotgeek" and see that the LegacyUSBInjector is there (or see that it's not there if something went wrong).

I misinterpreted your previous post because I guessed you referred only to the "prelinkedkernel legacy usb".

After you added LegacyUSBInjector with kmutil to BKE do you need to use "CMD+S" and "exit" or even without them ?

Also I didn't know that is possible to rebuild the SystemKernelExtensions.kc (about or more than 500 MB I guess?)

 

[Steven*]

A query. Why do you want to change the WiFi card in a 2012 MBP does not retina? It works perfectly for me in both beta 1 and beta 2 thanks to the help of @jackluke

It's a faster card

 

[jhowarth]

Let me rephrase it: What testheit posted was, for me, the secret to getting kmutil to build a BootKernelExtensions.kc with a working LegacyUSBInjector.

Actually, there are two other catches, I remember now:

1. kmutil can build both the BootKernelExtensions.kc and the SystemKernelExtensions.kc in one command, but if you do that, LegacyUSBInjector won't work. You have to build the two of them with two different commands.

2. You have to use a chroot. I ran into some weird error with kmutil that magically disappeared once I started using a chroot.

The code that I have that does it is something like this ("$VOLUME" is the path to the Big Sur system volume):

chroot "$VOLUME" kmutil create -n boot \
    --kernel /System/Library/Kernels/kernel \
    --volume-root / \
    --bundle-path /System/Library/Extensions/LegacyUSBInjector.kext \
    --boot-path /System/Library/KernelCollections/BootKernelExtensions.kc
chroot "$VOLUME" kmutil create -n sys \
    --kernel /System/Library/Kernels/kernel \
    --volume-root / \
    --system-path /System/Library/KernelCollections/SystemKernelExtensions.kc \
    --boot-path /System/Library/KernelCollections/BootKernelExtensions.kc
"$VOLUME/usr/sbin/kcditto"
bless --folder "$VOLUME"/System/Library/CoreServices --bootefi --create-snapshot

I ran this on my MacBookPro8,1 then booted the result on my MacBook6,1 and it worked. (I tried something else after that, and that's what caused my current situation where the two MacBooks boot from different snapshots on the same external SSD.)

By the way, you can run strings on the generated BootKernelExtensions.kc and look for "com.parrotgeek" and see that the LegacyUSBInjector is there (or see that it's not there if something went wrong).

A few things are unclear.

1) How did you get LegacyUSBInjector.kext installed in /System/Library/Extensions? I assume either you started with an unsealed volume which allowed 'mount -uw /' or you previously mounted the snapshot with something like...

mkdir /tmp/mntpoint
sudo mount -o nobrowse -t apfs /dev/disk7s5 /tmp/mntpoint
sudo ditto /Volumes/Untitled/LegacyUSBInjector /System/Library/Extensions/LegacyUSBInjector.kext
sudo chmod -R 755 /System/Library/Extensions/LegacyUSBInjector.kext
sudo chown -R root:wheel /System/Library/Extensions/LegacyUSBInjector.kext
cd ~
sudo bless --folder /tmp/mntpoint/System/Library/CoreServices --bootefi --create-snapshot

and rebooted to make that modified snapshot the active one. Which was it?

2) Was the $volume passed to chroot for the mounted / filesystem at, for example, '/Volumes/BigSur' rather than a mounted snapshot of it? I ask because if you used a sealed snapshot for $volume then 'chroot' would seem to have broken the seal, no? My experiments with using chroot to create prelinked kernels has been based on passing chroot the mount point of the mounted snapshot so it became writable. Your instructions seem to say that chroot alone can actually make a sealed snapshot writable without mounting it first.

 

[HackMini]

Hi everyone! I'm interested in spoofing my 2009 and/or my 2011 MacBook pro's and I would like to know if/how it is possible to spoof using clover configurator. I found a lot of hackintosh guides but I'm not using a hackintosh and would like to know if there is a way to spoof a real Mac without going through the whole hackintoshing process. Also, if there is a better program for this than clover, please let me know.

 

[Alex-Microsmeta]

You probably meant a bigger target disk.

Edit: You need to copy disk0 with all its partitions.

Edit: Mystery solved: it is the same SSD installatiion bootable from 2 different icons.

Incredible mystery. I have noticed that on mac boots screen there is also a "BIG SUR SSD" external drive icon. I have tried to load it and it works perfectly. After 3-4 hours, when you have told me that I have choosen the wrong /dev/ , I have suddenly stopped the terminal (while harddisk was still blinking) and the drive has continued blinking, then I rebooted Catalina. "dd" is a real Caterpillar, but you have no control on it and it is dangerous because you could damage partitions. But it clones BigSur better that CCC beta 2. @jackluke and other good hackers here, could you investigate and write a script to control the cloning process, or at least the success of the operation? Now Disk Utility on Cat 10.15.6 shows this "AppleAPFSmedia" (that I cannot rename or initialize without deleting full partition data) as 2th container of the internal SSD, instead of "BIGSUR SSD" or "Update", but BS beta 2 is present on mac boots screen with his real name, loads also without OpenCoreLoader3 and works perfectly and the external clone does the same.

 

[jhowarth]

A few things are unclear.

1) How did you get LegacyUSBInjector.kext installed in /System/Library/Extensions? I assume either you started with an unsealed volume which allowed 'mount -uw /' or you previously mounted the snapshot with something like...

mkdir /tmp/mntpoint
sudo mount -o nobrowse -t apfs /dev/disk7s5 /tmp/mntpoint
sudo ditto /Volumes/Untitled/LegacyUSBInjector /System/Library/Extensions/LegacyUSBInjector.kext
sudo chmod -R 755 /System/Library/Extensions/LegacyUSBInjector.kext
sudo chown -R root:wheel /System/Library/Extensions/LegacyUSBInjector.kext
cd ~
sudo bless --folder /tmp/mntpoint/System/Library/CoreServices --bootefi --create-snapshot

and rebooted to make that modified snapshot the active one. Which was it?

2) Was the $volume passed to chroot for the mounted / filesystem at, for example, '/Volumes/BigSur' rather than a mounted snapshot of it? I ask because if you used a sealed snapshot for $volume then 'chroot' would seem to have broken the seal, no? My experiments with using chroot to create prelinked kernels has been based on passing chroot the mount point of the mounted snapshot so it became writable. Your instructions seem to say that chroot alone can actually make a sealed snapshot writable without mounting it first.

ps If you attempt to repeat these steps, it would be very interesting to know if the above instructions to rebuild the kc can be repeated on the booted unsupported machine or if they only work from a supported machine.

 

[laimis17]

Many macs mainly experience performance issues related with gpu, but are equiped with thunderbolt. Enabling eGPU support for those would make sense. What's your take on this @dosdude1 ?

Many thanks for everything You've done

 

[MacHacJac]

Hey everyone! After hours of research, determination, and success, I have successfully found many awesome methods to install macOS on unsupported Macs, as well as hackintoshing. I have created this discord server with both hackintosh and real Mac channels, supporting anyone and everyone with a non-supported computer. It is in its preliminary stages, but rest assured, there will soon be content filling the pages. I know there is already a server for this purpose, but I thought that a more newbie-based Mac and hackintosh server would be nice for people who are just entering this realm. Feel free to give me any suggestions on the server and share it with anyone you know that might be interested. So far, this is the only invite link, so share it around! My discord username is Hack Pro 71. Thank you all for all of the support on this and other channels. See you there!

Discord - Group Chat That’s All Fun & Games

Discord is great for playing games and chilling with friends, or even building a worldwide community. Customize your own space to talk, play, and hang out.

discord.gg

[automerge]1594914590[/automerge]
I will start posting tomorrow.

 

[Cindy_Thornton]

This thread will be used to discuss advancements in getting macOS 11.0 Big Sur running on unsupported Macs.

---
Compatibility List:

Macs officially compatible with macOS Big Sur:

• 2015 and later MacBook
  • MacBook8,1
  • MacBook9,1
  • MacBook10,1
• 2013 and later MacBook Air
  • MacBookAir6,x
  • MacBookAir7,x
  • MacBookAir8,x
  • MacBookAir9,1
• Late 2013 and later MacBook Pro
  • MacBookPro11,x
  • MacBookPro12,1
  • MacBookPro13,x
  • MacBookPro14,x
  • MacBookPro15,x
  • MacBookPro16,x
• 2014 and later iMac
  • iMac14,4
  • iMac15,1
  • iMac16,x
  • iMac17,1
  • iMac18,x
  • iMac19,x
• 2017 and later iMac Pro
  • iMacPro1,1
• 2014 and later Mac mini
  • Macmini7,1
  • Macmini8,1
• 2013 and later Mac Pro
  • MacPro6,1
  • MacPro7,1

Macs officially compatible with macOS Catalina but have been dropped from official support in macOS Big Sur:
- These Macs so far are capable of running Big Sur properly, but Wifi support is currently broken. See FAQ for more information.

• 2012 and Early 2013 MacBook Pro
  • MacBookPro9,x
  • MacBookPro10,x
• 2012 MacBook Air
  • MacBookAir5,x
• 2012 and 2013 iMac
  • iMac13,x
  • iMac14,x
• 2012 Mac mini
  • Macmini6,x
• 2010-2012 Mac Pro*
  • MacPro4,1
  • MacPro5,1

*Not officially supported in macOS Catalina, but are fully capable of running both Catalina and Big Sur with a Metal-compatible GPU and upgraded Wifi/BT card.

Macs capable of being patched to run macOS Catalina properly and potentially can be patched to run macOS Big Sur:
- These Macs so far can boot Big Sur, but do not currently feature Wifi or graphical acceleration support. See FAQ for more information.

• Early-2008 or newer Mac Pro, iMac, or MacBook Pro:
  • MacPro3,1*
  • MacPro4,1*
  • MacPro5,1*
  • iMac8,1
  • iMac9,1
  • iMac10,x
  • iMac11,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs were almost unusable when running Catalina and will be under Big Sur as well.)
  • iMac12,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs were almost unusable when running Catalina and will be under Big Sur as well.)
  • MacBookPro4,1
  • MacBookPro5,x
  • MacBookPro6,x
  • MacBookPro7,x
  • MacBookPro8,x
• Late-2008 or newer MacBook Air or Aluminum Unibody MacBook:
  • MacBookAir2,1
  • MacBookAir3,x
  • MacBookAir4,x
  • MacBook5,1
• Early-2009 or newer Mac Mini or white MacBook:
  • Macmini3,1
  • Macmini4,1
  • Macmini5,x (systems with AMD Radeon HD 6xxx series GPUs were almost unusable when running Catalina and will be under Big Sur as well.)
  • MacBook5,2
  • MacBook6,1
  • MacBook7,1
• Early-2008 or newer Xserve:
  • Xserve2,1*
  • Xserve3,1*

*Not officially supported in macOS Catalina, but are fully capable of running both Catalina and Big Sur with a Metal-compatible GPU and upgraded Wifi/BT card.

Macs that WILL NOT BE SUPPORTED in any capacity:

• 2006-2007 Mac Pros, iMacs, MacBook Pros, and Mac Minis:
  • MacPro1,1
  • MacPro2,1
  • iMac4,1
  • iMac5,x
  • iMac6,1
  • iMac7,1
  • MacBookPro1,1
  • MacBookPro2,1
  • MacBookPro3,1
  • Macmini1,1
  • Macmini2,1
• — The 2007 iMac 7,1 is compatible with Catalina and potentially Big Sur if the CPU is upgraded to a Penryn-based Core 2 Duo, such as a T9300.
  
  
• 2006-2008 MacBooks:
  • MacBook1,1
  • MacBook2,1
  • MacBook3,1
  • MacBook4,1
• 2008 MacBook Air (MacBookAir 1,1)
• All PowerPC-based Macs
• All 68k-based Macs

---

FAQ:

Q: Why did Apple drop support for my perfectly capable Mac?
A: Only Apple can give a definite answer to this. However there is evidence that it is based upon the CPUs being used in the now-unsupported Macs, which was the case last year with the Mac Pro 4,1/5,1. Intel decided to stop releasing firmware security fixes for Ivy Bridge and previous-generation CPUs. While they are technically compatible and supported in Big Sur, Apple has decided it is not worth the risk to continue supporting CPUs that have permanently unpatched security holes, putting users at risk.

While this is also not confirmed, another possibility could be that some of the excluded Macs feature Wifi chips that are no longer deemed fit for the next major release. This decision could be based on the previously mentioned security issues as well. The presence of graphics drivers for some of these newly unsupported Macs in Big Sur Beta 1 suggests this.

Q: Will my unsupported Mac get macOS 11.0 Big Sur?
A: If your Mac had official support in macOS Catalina, they will likely be able to be patched to run Big Sur with minimal issues. As of writing, only WiFi appears to be broken.
If your Mac was unsupported before the release of macOS Catalina, support remains to be seen as graphics acceleration may not be feasible at this time. While Catalina still supported OpenGL (former macOS graphical API) and even used it as a fallback software render mechanism, Big Sur officially drops support and shifts to Apple's Metal API entirely.

Q: When will my unsupported Mac receive macOS 11.0 Big Sur? / ETA when?
A: This is a community driven effort to try and restore support for various unsupported Macs. Community members are working as hard as they can, often in their spare time, to try and add back stable support for these Macs. Based upon changes in macOS Big Sur, it may be possible some Macs that were previously patchable in Mojave, Catalina, and other previous releases of macOS may not be patchable under Big Sur. Please do not harass the patch developers to go faster, release the patcher, etc. Please do not clog up the thread with useless posts asking if your specific Mac will be patchable. Big Sur was only just released in its initial beta form and a lot is still subject to change before the final release. Rest assured, the dedicated community of developers working on these patches are doing everything that they can to re-add support for as many Macs as possible.

Q: Where/how can I download macOS 11.0 Big Sur?
A: For legal purposes, the only official way to obtain a copy of macOS Big Sur is to be a registered Apple Developer and pay a yearly $99 fee to become eligible for downloading beta software. According to Apple, a public beta which does not require a registered Developer account will be released at some point in July and will be free to sign up for. Please remember it is highly suggested that you do not install beta software on your main devices, overwriting any stable releases. Beta software can cause irreparable hardware damage or irrecoverable data loss and should be used at one's own risk.

Apple and all patch developers are not responsible for any potential damage or data loss caused by using pre-release software or unofficial support patches. Please use at your own risk.

the 2006 iMac is compatible I upgraded mine to a penryn core 2 duo and I secessfully installed Big Sur and it work fine but no graphics acceleration

 

[ricoc90]

the 2006 iMac is compatible I upgraded mine to a penryn core 2 duo and I secessfully installed Big Sur and it work fine but no graphics acceleration

The 2006 is 32-bit and therefore only supports up to Lion (or ML with a 32-bit kernel IIRC). The graphic drivers also were 32-bit so there's no way of making these graphics work, hence why it's incompatible.

 

[ResEdit_ResEdit]

I found out about a custom installation. This might help when you need to change something in the system volume. No need for Terminal. Just follow this instruction:

1. create external installation media
2. start installation on target media
3. after the first reboot turn off the Mac
4. connect external drive with 10.14 or 10.15 and boot from it
5. open the target media for the Big Sur installation
6. set the value "DoNotSeal" to "True" in the UpdateOptions.plist in folder macOS install data
7. shut down Mac, remove all unneeded drives
8. continue installation
9. switch off in the country selection
10. connect external drive with 10.14 or 10.15 and boot from it
11. make changes to the Big Sur start volume (delete fonts, etc.)
12. switch off Mac, remove all not needed drives
13. starting, setting up and using

optional:
14. start from the Big Sur installer and go to the disk utility
15. replicate modified start volume with Big Sur (takes about 3 minutes)

Have fun. And never fail with "failed with 66" again.

 

[RogueB]

the 2006 iMac is compatible I upgraded mine to a penryn core 2 duo and I secessfully installed Big Sur and it work fine but no graphics acceleration

Cindy,

Could you share the precise steps you took to install Big Sur On your iMac?

Thank you.

 

[Sjekke]

I already have Catalina on a Mac mini Late 2012 but with DOSDUDE's patcher because of my SSD RAID0 configuration. Can I upgrade the existing configuration too BigSur with the existing procedure or is better to do a fresh install (but I need RAID0).

Grts

 

[Dustman]

A query. Why do you want to change the WiFi card in a 2012 MBP does not retina? It works perfectly for me in both beta 1 and beta 2 thanks to the help of @jackluke

It was my understanding that it’ll be required to run Big Sur. Is this not the case? I just need a few more years out of my MBP until I can replace it with a suitable ARM MBP.

 

[RogueB]

Hello to all,

I am actually typing this message on Big Sur Beta 2 system installed on iMac13,2;
However, installation of BigSur on the MacBook Pro 5,2. (Penryn) still results in crashes.

I did invoke all the commands necessary to disable the “security” items, but that does not seem to be sufficient in the case of my MacBook Pro.

I attached a partial "trace" from last attempted boot into BigSur on the MacBook Pro.

Second picture shows the system data for the iMac (it is a Catalina “native” machine)

If someone can shed a light on the install problem, based on the partial trace, it would be appreciated.

Thanks for any "pointers".

 

[Barry K. Nathan]

I misinterpreted your previous post because I guessed you referred only to the "prelinkedkernel legacy usb".

After you added LegacyUSBInjector with kmutil to BKE do you need to use "CMD+S" and "exit" or even without them ?

Also I didn't know that is possible to rebuild the SystemKernelExtensions.kc (about or more than 500 MB I guess?)

No, I don't need to use Cmd+S then exit. (However, most of my testing so far has been with "-v" in the boot args, for verbose boot.)

Yes, SystemKernelExtensions.kc is a bit over 500MB.
[automerge]1594955600[/automerge]

A few things are unclear.

1) How did you get LegacyUSBInjector.kext installed in /System/Library/Extensions? I assume either you started with an unsealed volume which allowed 'mount -uw /' or you previously mounted the snapshot with something like...

mkdir /tmp/mntpoint
sudo mount -o nobrowse -t apfs /dev/disk7s5 /tmp/mntpoint
sudo ditto /Volumes/Untitled/LegacyUSBInjector /System/Library/Extensions/LegacyUSBInjector.kext
sudo chmod -R 755 /System/Library/Extensions/LegacyUSBInjector.kext
sudo chown -R root:wheel /System/Library/Extensions/LegacyUSBInjector.kext
cd ~
sudo bless --folder /tmp/mntpoint/System/Library/CoreServices --bootefi --create-snapshot

and rebooted to make that modified snapshot the active one. Which was it?

2) Was the $volume passed to chroot for the mounted / filesystem at, for example, '/Volumes/BigSur' rather than a mounted snapshot of it? I ask because if you used a sealed snapshot for $volume then 'chroot' would seem to have broken the seal, no? My experiments with using chroot to create prelinked kernels has been based on passing chroot the mount point of the mounted snapshot so it became writable. Your instructions seem to say that chroot alone can actually make a sealed snapshot writable without mounting it first.

1. Right now I'm doing this from the Recovery environment, which mounts the underlying volume read-only. A simple mount -uw /Volumes/Name-of-System-Volume remounts it read-write. This is basically equivalent to something like your example list of commands. (The reason I've been doing it from the Recovery environment was to work around weird kmutil bugs, but with invoking kmutil inside a chroot, that may no longer be necessary. I might investigate that in more detail after I finish up the upcoming release of my patcher.)

2. The seal definitely gets broken. I'm not sure at what step exactly. As long as csrutil authenticated-root disable is in effect, I've found that the exact same sequence of steps will work whether it's a sealed snapshot or an unsealed snapshot. Now that I think about it a bit more, I don't think it's chroot that's breaking the seal -- I would guess it's either mount or bless, but I would need to do some experiments with csrutil authenticated-root enabled to figure out for sure.

 

[Barry K. Nathan]

ps If you attempt to repeat these steps, it would be very interesting to know if the above instructions to rebuild the kc can be repeated on the booted unsupported machine or if they only work from a supported machine.

None of my Macs are supported machines. (I was expecting that Apple would wait another year before dropping the 2012s.) I've been doing these steps on my (2011) MacBookPro8,1 which comes closer to being supported than my MacBook6,1, so it's still an interesting question.

However, my next step (after my next patcher release -- not sure if it'll be tonight, tomorrow, or Saturday) will probably be to look into actually modifying BaseSystem, so that the installer can actually boot with functioning keyboard and trackpad on my MacBook6,1.

 

[Kahakapao]

11. make changes to the Big Sur start volume (delete fonts, etc.)

Can you please provide a bit more information about this step? Do fonts and other items need to be deleted in order for the installation to boot/work correctly? If so, which ones exactly?

 

[André Diniz Magalhães]

I successfully installed on my iMac 27" mid 2011 but it's running with a few issues. I made the WiFi work on the setup so I could connect to my network but when logged in if I click on the WiFi icon my user will automatically log off. My WiFi is working, I can access websites and everything normal but the icon on top shows as there's no WiFi. There's no sound as well and is really slow when I minimise a window like safari, I believe it's probably because I have a terrible gpu installed.
[automerge]1594957038[/automerge]

 

[Alex-Microsmeta]

I successfully installed on my iMac 27" mid 2011 but it's running with a few issues. I made the WiFi work on the setup so I could connect to my network but when logged in if I click on the WiFi icon my user will automatically log off. My WiFi is working, I can access websites and everything normal but the icon on top shows as there's no WiFi. There's no sound as well and is really slow when I minimise a window like safari, I believe it's probably because I have a terrible gpu installed.

Enable "Reduce transparency" on System Preferences - Accessibility to fix log off bug when you click top right icons.
If you can connect a bluetooth speakers, sound works. Probably it is slow because you lack of GPU acceleration.

 

[MrWeenus]

My MacBook Pro Retina 2012 is stuck on full on GPU mode. I can't seem to switch to the Intel integrated one.

The culprit is displaypolicyd. Can't seem to Force Quit that process because it respawns instantly.

 

[Larsvonhier]

My MacBook Pro Retina 2012 is stuck on full on GPU mode. I can't seem to switch to the Intel integrated one.

The culprit is displaypolicyd. Can't seem to Force Quit that process because it respawns instantly.

You can disable the dGPU and force the use of the iGPU by setting the appropriate NVRAM command.
(This was successfully used on systems with solder problems of discrete GPUs to at least have a stable system again with only having the performance of the integrated GPU).
Try this in single user mode during boot (and exit to resume booting):
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

(all 0 above are zeros, not letter O).

 

[jhowarth]

No, I don't need to use Cmd+S then exit. (However, most of my testing so far has been with "-v" in the boot args, for verbose boot.)

Yes, SystemKernelExtensions.kc is a bit over 500MB.
[automerge]1594955600[/automerge]

1. Right now I'm doing this from the Recovery environment, which mounts the underlying volume read-only. A simple mount -uw /Volumes/Name-of-System-Volume remounts it read-write. This is basically equivalent to something like your example list of commands. (The reason I've been doing it from the Recovery environment was to work around weird kmutil bugs, but with invoking kmutil inside a chroot, that may no longer be necessary. I might investigate that in more detail after I finish up the upcoming release of my patcher.)

2. The seal definitely gets broken. I'm not sure at what step exactly. As long as csrutil authenticated-root disable is in effect, I've found that the exact same sequence of steps will work whether it's a sealed snapshot or an unsealed snapshot. Now that I think about it a bit more, I don't think it's chroot that's breaking the seal -- I would guess it's either mount or bless, but I would need to do some experiments with csrutil authenticated-root enabled to figure out for sure.

So are you saying that, at the end of these commands, the volume, when booted on your unsupported machine, now allows 'sudo mount -uw /' to work? Or are you just saying that the use of chroot in the kmtuil calls allows that alone to slip past the seal?

 

[Arnomacmini]

https://parrotgeek.com/bigsur/ or https://github.com/barrykn/big-sur-micropatcher

Hello, thanks, it works but when i boot with my account, it craches and asks me again my password .
I tried with Parrotgeek.
Any idea ?

 

[André Diniz Magalhães]

Enable "Reduce transparency" on System Preferences - Accessibility to fix log off bug when you click top right icons.
If you can connect a bluetooth speakers, sound works. Probably it is slow because you lack of GPU acceleration.

Yeah, that's what I thought. I really need an upgrade
Thanks