macOS 11 Big Sur on Unsupported Macs Thread

[ASentientBot]

As before, DP9 (20A5384c) has no full installer, but it's possible to get an "asset bundle" with a full copy of the OS and swap it into a DP6 install. Direct link (11.32 GB): http://updates-http.cdn-apple.com/2.../60bc4f9bbe760a327193b3bafd04eaf746a3e371.zip

 

[Jose C. Salazar]

As before, DP9 (20A5384c) has no full installer, but it's possible to get an "asset bundle" with a full copy of the OS and swap it into a DP6 install. Direct link (11.32 GB): http://updates-http.cdn-apple.com/2.../60bc4f9bbe760a327193b3bafd04eaf746a3e371.zip

Will this work with micro patcher by Barry?

 

[rMBP2013china]

Copy paste won't work, you should run the patch-kexts.sh from terminal after booting from your installer USB stick.
The kext is already installed in a Folder on the installer USB stick when you used Micropatcher, running the command will install the Kext.

Thank you very much.
I installed Big Sur not using Micropatcher, but big_sur_plz.rb. In the installation process, no installer USB stick was needed. After installing big_sur_plz.rb, I clicked big sur beta6 dmg and then followed the installation method. Big Sur was installed. Now wifi is not working. Can I fix it with other method?

 

[ASentientBot]

Will this work with micro patcher by Barry?

No, you'd have to use the method I outlined here. You'll probably be best off just waiting for the GM.

 

[Ladin007]

its posible update from catalina 10.15.7 to BigSur beta 9??

 

[justperry]

Thank you very much.
I installed Big Sur not using Micropatcher, but big_sur_plz.rb. In the installation process, no installer USB stick was needed. After installing big_sur_plz.rb, I clicked big sur beta6 dmg and then followed the installation method. Big Sur was installed. Now wifi is not working. Can I fix it with other method?

Yes , make a USB stick with beta 6 on it and run micropather, then run the command in Terminal from the USB Installer.

its posible update from catalina 10.15.7 to BigSur beta 9??

No, not directly.

 

[Ladin007]

Yes , make a USB stick with beta 6 on it and run micropather, then run the command in Terminal from the USB Installer.



No, not directly.

OK, and what is way? When I on 10.15.7 start upadting..."some beta big sur 12 GB downloading..."???

 

[justperry]

OK, and what is way? When I on 10.15.7 start upadting..."some beta big sur 12 GB downloading..."???

Get Micropatcher.
And thank Barry K. Nathan, jackluke, highvoltage12v and ParrotGeek for their work.

 

[Ladin007]

Get Micropatcher.
And thank Barrykn for his work.

Need this if i am on suported mac??

 

[justperry]

Need this if i am on suported mac??

Nope, this thread is for unsupported macs, if you want it on a supported mac you can join the beta program.

https://www.macrumors.com/how-to/install-macos-big-sur-public-beta/

 

[justperry]

its posible update from catalina 10.15.7 to BigSur beta 9??

BTW, we are here to help anybody, glad to help, what you shouldn't do and is actually against MR rules is that you ask in several threads.
I see you asked in this thread as well:

48 minutes ago

 

[IbrahimFmc]

How can i update From beta 6 to beta 9 if there is no full installer ?

 

[justperry]

How can i update From beta 6 to beta 9 if there is no full installer ?

Just wait for the full release, it's getting quite complicated, I am still on b6, too much of a hassle to update to >b6

 

[IbrahimFmc]

Just wait for the full release, it's getting quite complicated, I am still on b6, too much of a hassle to update to >b6

Ok , I will wait , thank you

 

[Vital L]

How can i update From beta 6 to beta 9 if there is no full installer ?

macOS 11 Big Sur on Unsupported Macs Thread

I uploaded my opencore EFI folder (also updated to 0.6.1) to spoof a supported BigSur Mac in order to detect OTA updates: USBOpencore4s1 to make it working simply copy the EFI folder to any FAT32 formatted volume, at reboot hold alt-option key to select it from the apple startup manager. But...

forums.macrumors.com

 

[rMBP2013china]

Yes , make a USB stick with beta 6 on it and run micropather, then run the command in Terminal from the USB Installer.



No, not directly.

Thanks a lot. I will give it a try now. Hope wifi will work.

 

[Husseinabd40]

From USBopencore kexts folder, try to remove them (that are mainly for legacy USB Mac hence not required for recent Mac).

Otherwise outside of opencore retry with CMD+S and type this: mount -P 1 ; mount -P 2 ; kcditto

It worked well with : mount -P 1 ; mount -P 2 ; kcditto. I could update to Beta 9.
Thank you very much.

 

[jackluke]

Thanks again to this @ASentientBot method: Replacing BigSur Beta Assets bundle in macOS Install Data

I understood more how OTA updates and any full stage 2 installer (that are almost identical), are handled by apple:

when the "macOS Install Data" is ready prepared, in nvram it sets bootable that temporary volume with label "macOS Installer", booting from there the ramdisk used is at this path:

/macOS Install Data/BaseSystem.chunklist
/macOS Install Data/BaseSystem.dmg
/macOS Install Data/Locked Files/BootKernelExtensions.kc
/macOS Install Data/Locked Files/Boot Files/boot.efi

Moreover there is also com.apple.Boot.plist: https://github.com/jacklukem/BigSurfixes/blob/master/legacyusb installer fix/com.apple.Boot.plist

Note I edited it as generic BigSurDataUUID that is your APFS Data Volume UUID different for any machine.

diskutil info diskXs1 | grep UUID or ls /S*/V*/P* from BigSur.


Booting from "macOS Installer" the System Volume becomes unsealed and mountable rw (because apple during the stage 2 installer unseal and disable snapshot booting), overwritten (using a delta update) or erased (using a full installer but the Data volume content are kept), all the "Assets Bundle" /macOS Install Data/UpdateBundle/ payload packages are extracted to the System Volume, then follows a stage 3 installer where system is sealed or not, and a stock apple snapshot booting is created with a kernelcollection UUID and Preboot target.

About non-APFS or Legacy USB Mac, @hvds previously tested a kind of legacy usb installer where replaced the BaseSystem.dmg (prelinkedkernel patched with BaseSystem legacy usb fix) and BootKernelExtensions.kc with my prelinkedkernel fix renamed to BKE to cheat the apple installer and this allowed to continue the installer until a certain point, I guess till the stage3 where this other ram disk is loaded: https://github.com/jacklukem/BigSurfixes/blob/master/legacyusb installer fix/com.apple.Boot2.plist

Skipping this "x86_64SURamDisk.dmg" (I called it the stage3 installer) should not make or tag any snapshot and let use mount -uw / from single user mode, and from normal booting too, selecting "BigSur Data Volume" at apple startup manager.

Moreover I noticed that UpdateOptions.plist (DoNotSeal) is present either in /macOS Install Data/Locked Files/ and "Locked Files" folder should be unlocked with read and write permissions to everyone.

edit:
@ASentientBot seems beta 9 kernel (compiled by apple on September 25 ) can boot Penryn Core2Duo, so it's no more required a downgrading to beta 6.

 

[Ausdauersportler]

Out of curiosity:

Have just subscribed to the public beta program, have no valid subscription to the developer program any more.

Q: Will the Beta 7, 8, and 9 updates be visible to me if I follow this route using the USBopencore route? Or is this access limited to the subscribed developers, only?

P.S.: I have seen the download links to get the single packages...

 

[jackluke]

Out of curiosity:

Have just subscribed to the public beta program, have no valid subscription to the developer program any more.

Q: Will the Beta 7, 8, and 9 updates be visible to me if I follow this route using the USBopencore route? Or is this access limited to the subscribed developers, only?

P.S.: I have seen the download links to get the single packages...

In combination with USBopencore spoofing you can try this (works also on sealed snapshot booting): BigSurOTAswufix.app.zip

but use only the "Software update fix" button.

 

[Barry K. Nathan]

Out of curiosity:

Have just subscribed to the public beta program, have no valid subscription to the developer program any more.

Q: Will the Beta 7, 8, and 9 updates be visible to me if I follow this route using the USBopencore route? Or is this access limited to the subscribed developers, only?

P.S.: I have seen the download links to get the single packages...

As far as I can tell, the latest public beta is still beta 8, not 9 yet. (The instructions in jackluke's post should let you download developer beta 9, however.)

 

[stevecc]

Will @dosdude1 even release a patcher this time?

you will release one a dosdude1?...no hurry of course!..Maybe let us know dos?..if you read this post tks for all your time and hard work dos!..we all appreciate it!

 

[sinbad21]

I don't know why but beta 9 is not proposed to me. I managed to upgrade from beta 6 with OpenCore, but I was offered version 8, not 9. Once 8 was installed I immediately searched for updates, but the system tells me I'm up to date.

 

[justperry]

I don't know why but beta 9 is not proposed to me. I managed to upgrade from beta 6 with OpenCore, but I was offered version 8, not 9. Once 8 was installed I immediately searched for updates, but the system tells me I'm up to date.

Probably because you're on the Public beta and not the Dev beta, Public beta 9 is not out yet.

 

[Alex-Microsmeta]

As before, DP9 (20A5384c) has no full installer, but it's possible to get an "asset bundle" with a full copy of the OS and swap it into a DP6 install. Direct link (11.32 GB): http://updates-http.cdn-apple.com/2.../60bc4f9bbe760a327193b3bafd04eaf746a3e371.zip

@ASentientBot @jackluke Once you have updated your Core 2 Duo Penryn Mac, is possible to boot from Apple booter or you always need USBOpenCoreLoader4s like with beta 5,6,7 and 8? If OpenCore is necessary it would be nice to have an internal EFI booter instead of the pendrive. Thank you!