macOS 11 Big Sur on Unsupported Macs Thread

[TimothyR734]

https://github.com/chris1111/Kext-Droplet-Big-Sur coming coming soon

 

[jhowarth]

https://github.com/chris1111/Kext-Droplet-Big-Sur coming coming soon

And what happens when you drop LegacyUSBInjector.kext on it?

 

[Ronald Steven]

You should re-install from Catalina your BigSur using this: Hax2.dylib
then you can remove telemetry from BigSur single user mode.

Otherwise you can make from Catalina this: USBOpenCoreAPFSloader3.app.zip

If you use an external USB that contains an Installer or MacOS installation use "Near an USB device without erasing"

If you use an external empty USB drive without any multi-partition scheme example a 16 USB drive then use the second option, don't use second option on a multi-partition USB disk.

After reboot, hold alt-option key select usbopencore (with its icon) and pick your "Big Sug - Data" label to boot BigSur on unsupported mac.

@jackluke how can I use Hax2.dylib on beta.app? thanks

 

[Ronald Steven]

Mid 2012 unibody MacBook pro doesn’t need Siri kext fixes it instantly works and finally my wifi works
[automerge]1593531365[/automerge]

[automerge]1593531421[/automerge]
View attachment 929364

@Allan Fox please can u tell me the steps to do in my mbk pro mid2012 please????

 

[TimothyR734]

And what happens when you drop LegacyUSBInjector.kext on it?

I don't have it installed yet as he is still working on it

 

[Martin Eastwood]

where can I find the link to the discord server?

 

[Minh_Ton]

Tried that, I used these steps to modify BaseSystem.dmg (that from BigSur is an APFS with Preboot):

cd /Volumes/USBInstallerBigSur/BaseSystem/

hdiutil attach -owners on BaseSystem.dmg -shadow

Customize (directly from Finder) BaseSystem adding patched files

hdiutil detach /dev/diskX (or eject/unmount the "MacOS Base System" volume from Finder)

hdiutil convert -format UDZO -o BaseSystem2.dmg BaseSystem.dmg -shadow

mv BaseSystem.dmg BaseSystembackup.dmg

mv BaseSystem2.dmg BaseSystem.dmg

But even using the patched boot.efi still getting kernel panic (booting single user mode at least the legacy usb are responsive after added LegacyUSBInjector to the BootKernelExtensions.kc).

In few words I can't get a patched BigSur BaseSystem.dmg to boot.

I didn’t get a KP when using patched BaseSystem with replaced boot.efi. (I got responsive LegacyUSB for the first time and didn’t work again for some reasons...) Can you send me the BootKernelExtension.kc file that you’re using for me to find out a different approach?
[automerge]1593561197[/automerge]

where can I find the link to the discord server?

Join the Unsupported Macs Discord Server!

Need help with running modern macOS on your old mac? This is the place for you. | 18764 members

discord.gg

 

[chris1111]

https://github.com/chris1111/Kext-Droplet-Big-Sur coming coming soon

Hi. @TimothyR734
Ready but not For Hackintosh
Works only on real Mac, Not testing on Unsupported Mac
You can make test on your Unsupported if the kmutil management works
On my MacBook Pro I don't have any issue, works good

 

[Allan Fox]

@Allan Fox please can u tell me the steps to do in my mbk pro mid2012 please????

well for what @Ronald Steven installing Big Sur or wifi?

 

[Ronald Steven]

well for what @Ronald Steven installing Big Sur or wifi?

@Allan Fox booth please!

 

[Allan Fox]

oh boy I'm getting my 2009 iMac to Catalina and its stuck at estimating time remaining at like 90%
[automerge]1593562190[/automerge]

@Allan Fox booth please!

well for the Big Sur I used an external 500gb hard drive and tested that it booted miraculously it booted so I made a partition and restored the partition from the content of the hard drive and voila Big Sur was running on my computer
[automerge]1593562230[/automerge]
with the installer hack and the installer obviously
[automerge]1593562337[/automerge]
im gonna let the iMac do its thing and check on it tomorrow sadly I don't have any firewire cables so no target disk mode

 

[Ronald Steven]

oh boy I'm getting my 2009 iMac to Catalina and its stuck at estimating time remaining at like 90%
[automerge]1593562190[/automerge]

well for the Big Sur I used an external 500gb hard drive and tested that it booted miraculously it booted so I made a partition and restored the partition from the content of the hard drive and voila Big Sur was running on my computer
[automerge]1593562230[/automerge]
with the installer hack and the installer obviously

@Allan Fox i have a hard drive too, what kind the partition that you used can I use?

 

[Allan Fox]

I mean I had 200 gigs of data on the drive I just used disk util on Catalina and did the installer hack and installed Big Sur there
[automerge]1593562845[/automerge]
do you have SIP disabled?
[automerge]1593562883[/automerge]
just made a 280 gig partition and installed there

 

[Ronald Steven]

I mean I had 200 gigs of data on the drive I just used disk util on Catalina and did the installer hack and installed Big Sur there
[automerge]1593562845[/automerge]
do you have SIP disabled?
[automerge]1593562883[/automerge]
just made a 280 gig partition and installed there

yes I did installed on a ssd internal disk form catalina, but I can't activate the wifi drivers using sudo -uw, I have the 66 error. the apfs disk is encrypted and its only in read mode

 

[Allan Fox]

install on an external drive and try again

 

[Ronald Steven]

install on an external drive and try again

what format I have to made the partition?, in apfs or Mac OS plus ?

 

[Allan Fox]

apfs
[automerge]1593565091[/automerge]
well it has to be guid partition table
[automerge]1593565115[/automerge]
if it isn't it ain't gonna work

 

[Ronald Steven]

ok, i will try it and them comment u, thanks!

 

[Allan Fox]

if it doesn't work just erase and try again

 

[Ronald Steven]

oh boy I'm getting my 2009 iMac to Catalina and its stuck at estimating time remaining at like 90%
[automerge]1593562190[/automerge]

well for the Big Sur I used an external 500gb hard drive and tested that it booted miraculously it booted so I made a partition and restored the partition from the content of the hard drive and voila Big Sur was running on my computer
[automerge]1593562230[/automerge]
with the installer hack and the installer obviously
[automerge]1593562337[/automerge]
im gonna let the iMac do its thing and check on it tomorrow sadly I don't have any firewire cables so no target disk mode

@Allan Fox please the link for the installer hack where I found?

 

[Allan Fox]

@Allan Fox please the link for the installer hack where I found?

go to page 13 on gameroof's post there is the installer hack

 

[Barry K. Nathan]

I replaced the AppleHDA & IO80211Family kexts with the High Sierra versions through a Big Sur USB recovery terminal, but I still have the same Wi-Fi/audio situation too.
I did kextcache -i / kmutil install --update-all kcditto but I presume now, that I have to do this from single-user mode. However, I'm getting error 66 when mounting system volume as writable — and I'm not sure how to disable/delete snapshot booting to circumvent the error.
I don't fully understand snapshots tbh…it's difficult to grip an understanding of.

I know this won't help you with your immediate problem, but my understanding from various previous posts in this thread is that you'll need to use highvoltage12v's IO80211Family.kext instead of the one from High Sierra. (High Sierra is a good place to get AppleHDA from, however.)

 

[TimothyR734]

Big Sur’s Signed System Volume: added security protection

From SIP to a protected read-only System volume, macOS 11 takes system protection a big step further with cryptographic verification.

eclecticlight.co

you have to boot in Recovery Mode, use the command csrutil authenticated-root disable to turn cryptographic verification off, then mount the System volume and perform its modifications. To make that bootable again, you have to bless a new snapshot of the volume using a command such as sudo bless --folder /[mountpath]/System/Library/CoreServices --bootefi --create-snapshot You can then restart using the new snapshot as your System volume, and without SSV authentication.

 

[Alex-Microsmeta]

@jackluke Just reinstalled BS on internal SSD (I have read on forums that often It fails to boot from external USB) removed SIP, telemetry, compat-check... It boots, the screen becomes black from white, it continues loading, when the bar is almost at the end of the run it crashes... 🙃 PS: Next time, when beta 2 will be available, I'll also reset the NVRAM then restart using the new snapshot, if the dosdude1 official automatic patcher will not be already available.

 

[Ronald Steven]

Big Sur’s Signed System Volume: added security protection

From SIP to a protected read-only System volume, macOS 11 takes system protection a big step further with cryptographic verification.

eclecticlight.co

you have to boot in Recovery Mode, use the command csrutil authenticated-root disable to turn cryptographic verification off, then mount the System volume and perform its modifications. To make that bootable again, you have to bless a new snapshot of the volume using a command such as sudo bless --folder /[mountpath]/System/Library/CoreServices --bootefi --create-snapshot You can then restart using the new snapshot as your System volume, and without SSV authentication.

@TimothyR734 that is for error 66 to fix wifi?