macOS 11 Big Sur on Unsupported Macs Thread

[David dongfox]

It was in the middle of the night when you replied to me, you know...MR is read globally.

XXX is the System disk, the one you start up from normally, as in your norma working environment disk.

Hi, this my disk In Disk Utility (see attack pic) so which one is it ? and what is this one "com.apple.os.update-39.." it came out after install Big Sur.

Thanks.

 

[borp99]

I keep getting a Pub Beta 9 install loop - using either Barry's 0.31 & 0.32 patcher or the Hax3 method. The USB installer or direct installer adds the 'macOS Install Data' folder to a freshly erased partition but the move from black, to dark grey, to light grey screens only moves the progress bar about 5% along before automatically rebooting endlessly doing the same thing. None of the expected system folders and files are laid down or expanded for a full install. I'm stumped (after routine B1-6 installs) this time around. No_compat nvram was added back manually as required. Any suggestions?

 

[djr004]

Mine is perfect, only a bit slow due to the infamous internal hardisk.
I will install the final over my Beta 3 still working fine on external USB 3.0 SSD, keeping all programs already installed

Same here, Adobe Photoshop, Lightroom, Microsoft Office and other installed software working like a charm. Beta 3 was working so well I decided to try updating my Catalina installed on my main SSD drive. Everything has been working great and Beta 9 has been really snappy. I would say both Beta 3 and now Beta 9 have been running faster than Catalina. Haven't had any issues with hardware (wifi, bluetooth, airdrop, etc all working as it should).

 

[Joonyv]

Successfully installed beta 9 on a MacBook Air 2012 with patcher 0.3.2. Everything is working, WIFI, Airdrop, Continuity, etc.
But there is something new.
Disk utility is showing a snapshot volume taking 101 Gb. Usually there is only 2 volumes, Big Sur and Big Sur data.
In storage those 101 GB show as "other volumes in container".
I mean, the OS is taking 33gb and there is this usage space of around 100 GB being used. Is this normal?

Anyone else having this issue please?
Thanks

 

[justperry]

Anyone please, I have spent fair amount of time to fix this, now I need some expert advice. I am familiar with cusom build Hackintosh and all but this is driving me crazy.

What's wrong with your car...
Seriously, how do you expect people to help you if you don't say what is wrong, and on what platform.

If you have a Hackintosh you should look somewhere else, this thread is for installing Big Sur on unsupported Macs.

 

[justperry]

Hi, this my disk In Disk Utility (see attack pic) so which one is it ? and what is this one "com.apple.os.update-39.." it came out after install Big Sur.

Thanks.

David Mac Mini

So:
In Terminal from your Big Sur USB Installer you type exactly like below, including spaces.
/Volumes/Image\ Volume/patch-kexts.sh /Volumes/David\ Mac\ Mini

 

[thatsmeonlyme]

Hi, this my disk In Disk Utility (see attack pic) so which one is it ? and what is this one "com.apple.os.update-39.." it came out after install Big Sur.

Thanks.

/Volumes/Image\ Volume/patch-kexts.sh /Volumes/David\ Mac \ Mini

Type in exactly as I wrote --> case sensitive

 

[nandor690]

Was just dropping by to report that I was able to update my 4,1 to beta 9 using the OC method that has been posted here and also using BarryKn method. Thanks for the time you guys are putting into this to make it easier for us.

a side note: this also happened in Catalina. When I first install macOS I can do normal things like drag and drop files from the downloads stack directly to the trash. But after a few updates it no longer lets me. I have to actually go into the downloads folder and right click and choose trash. But then it doesn’t go to the trash. Instead it ask me if I want to permanently delete the file. Which gets annoying when it ask for every single damn file.
Anyone know an easy way to fix this? Thanks

 

[MacPeet]

@jackluke

Unfortunately, your information did not help with the direct updates.
After all attempts, a macOSInstall folder with UpdateOptions.plist was not seen in any phase.

With Fullinstaller DP9 I'm back with the MacPro3,1.
DoNotSeal and delete telemetry and change the AppleHDA again no problem. Everything else works natively again.

 

[akki_nd]

What's wrong with your car...
Seriously, how do you expect people to help you if you don't say what is wrong, and on what platform.

If you have a Hackintosh you should look somewhere else, this thread is for installing Big Sur on unsupported Macs.

I'm really sorry if if I misinterpret in any way, I am trying to install Big Sur 9 on my Mac book pro Mid 2012 (before that I was using version 6 as as a daily driver with dual boot with win 10 for SQL without any isssue). Now I followed Berry's latest patch and I I am getting this error. I am not even able to get back to DB6. What should I try. I am not a freeloader, looking for solution on this forum. I will definately try to contribute in future.. Thanks.

 

[jackluke]

@jackluke

Unfortunately, your information did not help with the direct updates.
After all attempts, a macOSInstall folder with UpdateOptions.plist was not seen in any phase.

With Fullinstaller DP9 I'm back with the MacPro3,1.
DoNotSeal and delete telemetry and change the AppleHDA again no problem. Everything else works natively again.

View attachment 962309

UpdateOptions.plist should be present in two paths or can be manually copied after making the "macOS Install Data" folder here:

/Volumes/APFS Data Volume/macOS Install Data/UpdateOptions.plist
/Volumes/APFS Data Volume/macOS Install Data/Locked Files/UpdateOptions.plist

"Locked Files" is hidden and locked and should be unlocked with read and write permissions to admin before editing.

but reinstalling on a sealed System with an USB BigSur full installer (through ASentientBot Hax3.dylib or Micropatcher) also removes the System volume sealing keeping the Data.

 

[thatsmeonlyme]

David Mac Mini

So:
In Terminal from your Big Sur USB Installer you type exactly like below, including spaces.
/Volumes/Image\ Volume/patch-kexts.sh /Volumes/David\ Mac\ Mini

Sorry @justperry I see we wrote the same time. hope he´ll get it now working

 

[jackluke]

To those who tested this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28973673

and got prohibitory symbol after made the patched BaseSystem legacy USB Installer, there was a minor issue on the fix2, that I noticed after @Alex-Microsmeta send me a log of the patch, due since I used a previous folder for that, I ignored that apple from beta 9 has completely removed the PrelinkedKernels, and so also with the stock createinstallmedia (beta 9) Big Sur installer there wasn't any folder for this, but now it's fixed.

So maybe if @Ausdauersportler could retry the BaseSystem legacy USB fix beta 9 too.

Because using my BaseSystem fix you should get a bootable Big Sur installer without using opencore, from apple startup manager directly, and when in the recovery installer menu you will get also Wifi to use Safari and Sound to enable with CMD+F5 .

Here is the updated fix (also attached on previous post): BigSur BaseSystem legacy usb fix b9.zip

 

[thatsmeonlyme]

@kabaldan

I have checked this out on my cMP and can confirm this. Exactly the same with my machine. interesting that at the usb 3.1 port it pulls down to USB 2.0 although the connected devices are 3.0. Working on the hub connected devices I get higher speeds than 2.0.
Checking with other USB 3.0 device has the same effect. It is shown as USB 2.0 bus connected device.

 

[thatsmeonlyme]

update
made some tests. Also USB 3.1 only mounting devices attached during boot are working. iPad pro showing twice. Speed for 3.1 (Sonnet USB 3.1 card) only 480 MBit/sec.
USB sticks are mounted everytime.
looking for a sonnet driver

 

[alphascorp]

Hi to all,
I couldn't update cMP5.1 from Beta 6 to Beta 9.
Beta 6 worked very well, I created a USB installer, I patched it with micropatcher v0.3.2 (a big thank you to @Barry K. Nathan and all those who contribute in any way...) This is the first time I use micropatcher because from Beta 1 to Beta 6 I had used the ParrotGeek's Patcher.

I booted on the USB installer, opened Terminal and ran: /Volume/Image\ Volume/set-vars.sh
The Beta 9 installation went well but at the 3rd reboot I got bootloop with KP (so fast, impossible to read...)
I re-did another patched USB installer, reinstalled Beta 9, same bootloop with KP.
I wanted to go back by reinstalling Beta 6 (of which I had kept the USB installer in case...) but also after the 3rd reboot I obtained bootloop with KP!!!!

So I had to perform a clean installation:

I formatted my SSD, ran: /Volumes/Image\ Volume/set-vars.sh, and after 45 minutes I finally got MacOS Setup Assistant and then the desktop.

I didn't understand what was causing these KPs, I hadn't made any changes except adding "Lilu 1.4.7" + "Innie 1.2.1".

After several hours of testing, Beta 9 seems to work well...

EDIT: Handoff not working but Airdrop yes

 

[jackluke]

I keep getting a Pub Beta 9 install loop - using either Barry's 0.31 & 0.32 patcher or the Hax3 method. The USB installer or direct installer adds the 'macOS Install Data' folder to a freshly erased partition but the move from black, to dark grey, to light grey screens only moves the progress bar about 5% along before automatically rebooting endlessly doing the same thing. None of the expected system folders and files are laid down or expanded for a full install. I'm stumped (after routine B1-6 installs) this time around. No_compat nvram was added back manually as required. Any suggestions?

Try this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28973673

it should work even without USBopencore (except with Penryn Core2Duo for telemetry and legacy USB), you can use a stock BigSur beta 9 USB installer already made with createinstallmedia or micropatcher, then apply the two BaseSystem legacy USB fix, when apply the fix2 answer typing "y" or "A" to replace patched files on the USB BigSur Installer.

This fix uses my patched prelinkedkernel to boot and allows even on beta 9 to embed Wifi (only Broadcom 802.11n) and Sound (CMD+F5) on BigSur Installer Recovery, but after stage2 installer the stock apple BaseSystem and BootKernelExtensions.kc is used, so you need to apply Micropatcher kext patches, or eventually tag an empty snapshot to use "sudo mount -uw /" (also skipping the stage3 installer should allow mount -uw /).

 

[44quattrosport]

iMac 2012, now with upgraded WiFi - everything went fine (from Beta 6).

Thanks again!

 

[alfon_sico]

iMac 2012, now with upgraded WiFi - everything went fine (from Beta 6).

Thanks again!

I have Mac mini 2012 too but I'm waiting till Final Version go out
Could you bring the link of the method you use for install it?

 

[furdi]

After testing for a full day Beta 9, I can tell you that all my apps are working fine including... Adobe Acrobat DC!!!! So happy!!! Last beta that was working on was Beta 4, after that it just stopped working, it was just crushing... Now, I am a happy camper! Have a great one everyone!

 

[justperry]

Sorry @justperry I see we wrote the same time. hope he´ll get it now working

No worries, I might have typed a bit faster then you.

I have Mac mini 2012 too but I'm waiting till Final Version go out
Could you bring the link of the method you use for install it?

Confused: You contradict yourself, you 1st say you're gonna wait for the final version and then ask for a link how to install the (current) beta./Confused

 

[Ausdauersportler]

To those who tested this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28973673

and got prohibitory symbol after made the patched BaseSystem legacy USB Installer, there was a minor issue on the fix2, that I noticed after @Alex-Microsmeta send me a log of the patch, due since I used a previous folder for that, I ignored that apple from beta 9 has completely removed the PrelinkedKernels, and so also with the stock createinstallmedia (beta 9) Big Sur installer there wasn't any folder for this, but now it's fixed.

So maybe if @Ausdauersportler could retry the BaseSystem legacy USB fix beta 9 too.

Because using my BaseSystem fix you should get a bootable Big Sur installer without using opencore, from apple startup manager directly, and when in the recovery installer menu you will get also Wifi to use Safari and Sound to enable with CMD+F5 .

Here is the updated fix (also attached on previous post): BigSur BaseSystem legacy usb fix b9.zip

Update:

Hardware: I have an iMac 2011 with an AMD Polaris card using OpenCore to offer boot screen.

- made an Beta9 installer on an SSD partition, applied the 0.3.2 micro patcher enhanced with our iMac 2011 patches.
- applied your new two USB patches on this installer
- rebooted into my own OpenCore and chose the double patched Beta 9 installer
- it booted succesfully into the installer screen
- used the @jackluke version to enable the HAX3 libs calling /V*/I*/Hax3.sh
- started installation using the 250GB APFS partition prepared using Catalina
- stage 1 copying files to target
- several reboots, some end on the OpenCore boot loader where I had manually to chose the correct partition
- finally got the setup screen!
- added the AMD GPU and iMac 2011 specific patches
- reboot and everything is fine!

This is a real success I would say.

Using a BCM943602CDP card here gives me Airdrop, WIFI, Handoff and Continuity right from the start!

No we have for both GPU types native installers. Thanks to @jackluke and @Barry K. Nathan, again!

 

[jackluke]

Without formatting to HFS , to install directly on APFS or update a previous BigSur, after "BaseSystem legacy usb fix b9" you could have used from an Installer recovery Utilities terminal simply this: /V*/I*/H*

anyway try booting with CMD+S targeting BigSur then type (if you use opencore make sure you have at least csrutil disable) :

mount -uw /
mount -P 1
mount -P 2
kmutil install --update-all
kcditto
reboot

Otherwise try boot also in safe mode from opencore .

 

[thatsmeonlyme]

No worries, I might have typed a bit faster then you.



Confused: You contradict yourself, you 1st say you're gonna wait for the final version and then ask for a link how to install the (current) beta./Confused

as for this case told @Barry K. Nathan to take it to his readme because some people don´t know how to use terminal commands correctly

 

[akki_nd]

I'm really sorry if if I misinterpret in any way, I am trying to install Big Sur 9 on my Mac book pro Mid 2012 (before that I was using version 6 as as a daily driver with dual boot with win 10 for SQL without any isssue). Now I followed Berry's latest patch and I I am getting this error. I am not even able to get back to DB6. What should I try. I am not a freeloader, looking for solution on this forum. I will definately try to contribute in future.. Thanks.

so I formatted the drive in Internet recovery mode, reboot again from DB9 usb and everything is working fine now MBP Mid 2012 ?.. before that I tried formatting the drive from DB6 installer but that didn’t work. ✌?