macOS 11 Big Sur on Unsupported Macs Thread

[Pachnes]

Does Apple employ developers, who have the task to make hackintoshs and actual macOS on older Macs as difficult, as possible?

 

[GSXB]

Make sure you try that. I just know from doing hackintoshes for the past 10 years that weird things can happen all the time. Even on the same machine from one install to the other.

no joy, three reboots and still boot loops

 

[Alex-Microsmeta]

@Barry K. Nathan this time I feel that BS will install fine with your patcher 0.0.20 ?. I think I missed something last time... If you note, partition name is BigSurB ....as Barry, to thank you!

Edit: after install I have been obliged to boot via @jackluke OpenCoreLoader4 then I have used prelinked kernel fix for beta 3 to boot from Apple booter.

@Barry K. Nathan @jackluke
Same result of old method installation: bluetooth, wifi, usb enabled, No ethernet and internat sounds.



Edit 2: DEEP MYSTERY - If I access BSBarry recovery from OpenCoreLoader4, csrutil status is disabled, from BSBarry normal booting SIP is still enabled. I cannot access recovery with command + R (it starts internet recovery and after this now it continues to enter dosdude1 Catalina Patcher (I note macOS Post Install option) also selecting Catalina SSD and while dosdude1 Patcher USB stick has been removed!!! (like if it is in memory)

EDIT 3: Before leaving BSBarry I have selected Catalina SSD 400 as startup, now from Recovery I have selected Catalina backup... Same result CLICKING ON ALL SYSTEMS IN APPLE BOOT OR OPENCORELOADER4, It opens dosdude1 Patcher Recovery, ALSO IF USB STICK ISN'T INSERTED ?

EDIT 4: Resetting PRAM finally solved the issue, I'm in Catalina SSD ?
And also BSBarry loads normally, but as always without internal sounds and Ethernet



@ASentientBot I have noticed that, probably for a bug, menubar starts transparent and passing over it with the mouse fix the issue, "painting" a white background (watch last image)

 

[LuisN]

Does Apple employ developers, who have the task to make hackintoshs and actual macOS on older Macs as difficult, as possible?

Ask Tim Cook

 

[Sveto]

Well, well, well. A MacBook Pro 2010 (with fixed cap) is working ok on Mojave, but unable to activate the camera on zoom, so worthless under macOS for zoom sessions. However under Windows 10 latest, with drivers from 2011 it is running like a champ. And zoom is a joy. I will never go past Mojave. In a year max Mojave will be nothing more than abandonware, so I'll clean the SSD and have it fully dedicated to Windows 10. What a spectacular performance. Goodbye apple/macos.

 

[Sveto]

Does Apple employ developers, who have the task to make hackintoshs and actual macOS on older Macs as difficult, as possible?

Most likely. For many years already Apple has been all about ripping off the simpletons and making the biggest cash possible for the shareholders. Hardware quality, which was never spectacular, is now down the drains. You MUST be brainwashed into buying every year at least one of Apple's junk "products"! So a lot is being invested also into making break hardware, that is 2 or more years old.

 

[MacHacJac]

UPDATE on my patcher:
1) I have successfully automated the ENTIRE process of patching the USB stick while also creating the big Sur install media. With the press of a button, your USB drive will be loaded with the installer and all of the patchers!
2) I am working on a website that will house this patcher, along with links to dosdude1 and 0403979's patchers. Eventually, there might even be a hackintosh section, but I am not too fond of hackintoshing and am debating whether or not I should post hackintosh guides on my site.
3) I created a temporary name for myself: MacHacJac. Once the patcher is released, I will rename myself to MacHacJac on Macrumors AND on Discord.

I have two questions:
1) What is the best free online source for shortening domains? (e.x. Let's say my full domain is macmacmac2342349sdfhsdkjasdfhjksdfhghuiewr.com and I want to shorten it to macmacmac.com)
2) Is it possible to run terminal commands externally without opening a terminal window? I think it would be nice to cut out terminal if the whole patching process is automized.

 

[Barry K. Nathan]

You are spot-on, it’s variant (c). ??

So what could be the next steps there, or would it be easier to first install the patched version on another machine (also have a MacBookPro8,2 (early 2011) lying around, where I could also do further experimentation.

The easy way is to hook up an external USB SSD to the MBP8,2, install onto the USB SSD, patch it using patch-kexts.sh like normal (but with the --all command line option), run zap-snapshots.sh (same syntax as patch-kexts, but no --all option) to delete all but the latest snapshot (to make sure the MBP4,1 doesn't somehow boot an old snapshot from before the kext patching). Then shut down the MBP8,2, unplug the drive, move it over to the MBP4,1, and hold down Option at startup to choose the USB SSD.

The high-performance way is to swap internal SSDs instead of using a USB SSD. If you've done hard drive/SSD replacements on both machines before (or possibly even if you haven't), this will increase performance enough that, in terms of time, it will pay for itself before Big Sur even finishes installing.

It just occurred to me, it's possible that this won't work -- I know that the MacBook4,1 needs legacy USB kexts above and beyond the LegacyUSBInjector, and I don't know if the MacBookPro4,1 falls into the same category. (The --all option for patch-kexts installs LegacyUSBInjector, but not other legacy USB kexts at this point.)

By the way, a future release of the patcher is going to rename the --all option, because at some point it won't be all of the kext patches anymore -- but I will announce that in the patcher release notes when the time comes.

 

[Barry K. Nathan]

UPDATE on my patcher:
1) I have successfully automated the ENTIRE process of patching the USB stick while also creating the big Sur install media. With the press of a button, your USB drive will be loaded with the installer and all of the patchers!
2) I am working on a website that will house this patcher, along with links to dosdude1 and 0403979's patchers. Eventually, there might even be a hackintosh section, but I am not too fond of hackintoshing and am debating whether or not I should post hackintosh guides on my site.
3) I created a temporary name for myself: MacHacJac. Once the patcher is released, I will rename myself to MacHacJac on Macrumors AND on Discord.

I have two questions:
1) What is the best free online source for shortening domains? (e.x. Let's say my full domain is macmacmac2342349sdfhsdkjasdfhjksdfhghuiewr.com and I want to shorten it to macmacmac.com)
2) Is it possible to run terminal commands externally without opening a terminal window? I think it would be nice to cut out terminal if the whole patching process is automized.

For question #1, if the shortened domain is one that you own, it seems like the logical thing to do would be to run your own URL shortener at that domain. (Maybe someone else who knows more about issues related to web hosting will have a better idea, and it's also possible that I'm misunderstanding some aspect of the situation.)

For question #2, there's the system() function in the C standard library, which might do the trick. (Note that if you're planning on running nvram or csrutil commands in the background, csrutil authenticated-root disable can fail outright if any macOS installation has FileVault enabled.)

 

[macinfo]

Thanks @Barry K. Nathan, for your very welcome assistance, will have to digest what you are saying.

For now, I succeeded in creating a booting installer USB flash drive of Big Sur beta 4, by applying these two scripts by @jackluke (Thanks for all your work!):

BigSur BaseSystem legacy usb fix.command
BigSur BaseSystem legacy usb fix2.command

(zip archive containing these commands and more detailed explanation in post: BigSur BaseSystem fix)

I first tried to apply the patches from within a El Capitan system, but the resulting USB flash drive did not fully boot up.
After that, I tried it again, running from Mojave (put the shell into #root-mode with: 'sudo su -' before executing the above 2 commands), this time the patched installer flash drive did fully boot up on my MacBookPro4,1!

I’ll report on the further outcome later, after trying to install on a APFS partition of my internal ssd.

 

[gbrot001]

UPDATE on my patcher:
1) I have successfully automated the ENTIRE process of patching the USB stick while also creating the big Sur install media. With the press of a button, your USB drive will be loaded with the installer and all of the patchers!
2) I am working on a website that will house this patcher, along with links to dosdude1 and 0403979's patchers. Eventually, there might even be a hackintosh section, but I am not too fond of hackintoshing and am debating whether or not I should post hackintosh guides on my site.
3) I created a temporary name for myself: MacHacJac. Once the patcher is released, I will rename myself to MacHacJac on Macrumors AND on Discord.

I have two questions:
1) What is the best free online source for shortening domains? (e.x. Let's say my full domain is macmacmac2342349sdfhsdkjasdfhjksdfhghuiewr.com and I want to shorten it to macmacmac.com)
2) Is it possible to run terminal commands externally without opening a terminal window? I think it would be nice to cut out terminal if the whole patching process is automized.

Extremely grateful for your undoubtedly hard work. CAN'T WAIT to see the patcher release, and will be lined up to test it for you on my 2009 white MacBook. That I've been able to run Mojave and Catalina on it without issue speaks to the quality of the work done around here. ? This ol gal is still perfectly functional for the kinds of tasks for which I use it, so I'm happy she might have a chance to hang in the fight for another year.

 

[MacMestres]

UPDATE on my patcher:
1) I have successfully automated the ENTIRE process of patching the USB stick while also creating the big Sur install media. With the press of a button, your USB drive will be loaded with the installer and all of the patchers!
2) I am working on a website that will house this patcher, along with links to dosdude1 and 0403979's patchers. Eventually, there might even be a hackintosh section, but I am not too fond of hackintoshing and am debating whether or not I should post hackintosh guides on my site.
3) I created a temporary name for myself: MacHacJac. Once the patcher is released, I will rename myself to MacHacJac on Macrumors AND on Discord.

I have two questions:
1) What is the best free online source for shortening domains? (e.x. Let's say my full domain is macmacmac2342349sdfhsdkjasdfhjksdfhghuiewr.com and I want to shorten it to macmacmac.com)
2) Is it possible to run terminal commands externally without opening a terminal window? I think it would be nice to cut out terminal if the whole patching process is automized.

I am very grateful to do this for the community, I can't wait to install MacOs Big Sur on my imac 2009 10.1

 

[GSXB]

Can a usb installer be created using the bare minimum patches possible, IE no
Kexts just enough to get it to boot and install. Just a thought

 

[LuisN]

Can a usb installer be created using the bare minimum patches possible, IE no
Kexts just enough to get it to boot and install. Just a thought

Use Barry K. Nathan's method and just don't execute the scripts.

 

[Vyzantion]

No, the issue is the so-called 1st gen Intel Core CPU. The previous (Intel Core 2 Duo Penryn) and subsequent (2nd gen Intel Core, a.k.a. Sandy Bridge) generations work, but not that generation. Edit: It's some kind of kernel incompatibility, basically.

DO you think Bir Sur shall be able to run on this hardware (of course, with the proper patches and such)?

Intel® Core™2 Duo Processor E8500 (6M Cache, 3.16 GHz, 1333 MHz FSB) Product Specifications

Intel® Core™2 Duo Processor E8500 (6M Cache, 3.16 GHz, 1333 MHz FSB) quick reference guide including specifications, features, pricing, compatibility, design documentation, ordering codes, spec codes and more.

ark.intel.com

 

[jackluke]

Thanks @Barry K. Nathan, for your very welcome assistance, will have to digest what you are saying.

For now, I succeeded in creating a booting installer USB flash drive of Big Sur beta 4, by applying these two scripts by @jackluke (Thanks for all your work!):

BigSur BaseSystem legacy usb fix.command
BigSur BaseSystem legacy usb fix2.command

(zip archive containing these commands and more detailed explanation in post: BigSur BaseSystem fix)

I first tried to apply the patches from within a El Capitan system, but the resulting USB flash drive did not fully boot up.
After that, I tried it again, running from Mojave (put the shell into #root-mode with: 'sudo su -' before executing the above 2 commands), this time the patched installer flash drive did fully boot up on my MacBookPro4,1!

I’ll report on the further outcome later, after trying to install on a APFS partition of my internal ssd.

If you have a non-APFS firmware to continue BigSur stage2 installer you need to use USBOpenCore selecting the "macOS Installer" label, then after installation apply from Mojave this (that allows to boot without opencore): BigSur Penryn beta3 prelinkedkernel fix.command.zip

After you applied the prelinkedkernel fix you can also use the BigSur installation as external USB booting from legacy USB Mac .

 

[jackluke]

Thank you for your response. So tell me if I’m understanding your information correctly. I would have to load the 2 mentioned kext flies after installing BS in order for the installed WiFi to work or for the usb WiFi adapter to work?

For Ivy Bridge Mac you can use the stock BigSur AppleHDA.kext, while the working patched IO80211Family.kext for "Wifi n cards" is from Mojave 10.14.5 (mixed with some HighSierra plugins kext) posted here: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28595200

Anyway the new fixed version won't add AirDrop for "Wifi n cards" based on AirPort Broadcom 4360 driver, so I'd use the previous version if you need AirDrop .

 

[GDMSR]

Did you upgrade yours from single to dual? I have a w3690 in mine right now. I’m looking to get the dual cpu tray for mine

No, it was already a dual cpu when I bought it new from Apple, but with the old W cpus which caused crashing on sleep with Catalina, if I remember right. This issue only affected the dual cpu config, apparently.
I don't know if you can 'upgrade' from a single cpu to a dual cpu config; I would research it heavily. You will in any case need the X cpus with a dual.

 

[GSXB]

No, it was already a dual cpu when I bought it new from Apple, but with the old W cpus which caused crashing on sleep with Catalina, if I remember right. This issue only affected the dual cpu config, apparently.
I don't know if you can 'upgrade' from a single cpu to a dual cpu config; I would research it heavily. You will in any case need the X cpus with a dual.

You can upgrade a single cpu tray to a dual cpu but it has to be a 4.1 dual tray not a 5.1 dual cpu tray

 

[Larsvonhier]

Well, well, well. A MacBook Pro 2010 (with fixed cap) is working ok on Mojave, but unable to activate the camera on zoom, so worthless under macOS for zoom sessions. However under Windows 10 latest, with drivers from 2011 it is running like a champ. And zoom is a joy. I will never go past Mojave. In a year max Mojave will be nothing more than abandonware, so I'll clean the SSD and have it fully dedicated to Windows 10. What a spectacular performance. Goodbye apple/macos.

Well, well, well: The zoom issue has long been solved under Mojave & Catalina (there´s a patch for that). So, not useless at all... ;-)

 

[GDMSR]

Well, well, well: The zoom issue has long been solved under Mojave & Catalina (there´s a patch for that). So, not useless at all... ;-)

In Big Sur, I used tccplus to allow Skype and Zoom access to the camera and microphone.

 

[darthgeekonius]

UPDATE on my patcher:
1) I have successfully automated the ENTIRE process of patching the USB stick while also creating the big Sur install media. With the press of a button, your USB drive will be loaded with the installer and all of the patchers!
2) I am working on a website that will house this patcher, along with links to dosdude1 and 0403979's patchers. Eventually, there might even be a hackintosh section, but I am not too fond of hackintoshing and am debating whether or not I should post hackintosh guides on my site.
3) I created a temporary name for myself: MacHacJac. Once the patcher is released, I will rename myself to MacHacJac on Macrumors AND on Discord.

I have two questions:
1) What is the best free online source for shortening domains? (e.x. Let's say my full domain is macmacmac2342349sdfhsdkjasdfhjksdfhghuiewr.com and I want to shorten it to macmacmac.com)
2) Is it possible to run terminal commands externally without opening a terminal window? I think it would be nice to cut out terminal if the whole patching process is automized.

once The drive is formatted and ready do you have to reboot from the usb and do you need to see the boot screen ie install original or flashed card? I still have my gt card I just hate the whole switching out gpu thing

 

[Ausdauersportler]

I try to install Big Sur using the very same installer I had successfully used with my other Nvidia iMac 2011 to do a clean new installation directly onto an iMac modded with an AMD card.

To have a boot screen with this model we have to use OpenCore. So booting the USB installer with OpenCore let me successfully survive stage 1 (copy files to disk), it reboots into OpenCore, I manually select the correct partition (internal disk with separate partition using APFS), but after a few minutes it ends with the same error message, photo and logs attached.
It complains about wrong hash code, did the installation several times recreating the partition every time. So no old data. And I used a second USB installer with the same result.

What Do I miss here?

Spoiler: error from log file

Aug 11 11:59:45 iMac OSInstaller[228]: Operation: Install Mobile Software Update failed, Failure Reason: Error Domain=com.apple.osinstall Code=-81 "Beim Vorbereiten des Softwareupdates ist ein Fehler aufgetreten." UserInfo={NSLocalizedDescription=Beim Vorbereiten des Softwareupdates ist ein Fehler aufgetreten., NSUnderlyingError=0x7f8eccf17730 {Error Domain=MobileSoftwareUpdateErrorDomain Code=21 "package contents did not verify." UserInfo={target_update=20A5343j, NSLocalizedDescription=package contents did not verify., NSUnderlyingError=0x7f8eccf17700 {Error Domain=MobileSoftwareUpdateErrorDomain Code=7 "SHA-1 mismatch for /Volumes/Update/softwareupdate.315.Ty9AOe/source/boot/EFI/EFIPayloads/IM191.fd: 0c491e1d96178aa77aa00395cfff7aacb1b5dfa1 should be 4259dc695da62b7737cc9b633260cd44bb8d3fca" UserInfo={NSLocalizedDescription=SHA-1 mismatch for /Volumes/Update/softwareupdate.315.Ty9AOe/source/boot/EFI/EFIPayloads/IM191.fd: 0c491e1d96178aa77aa00395cfff7aacb1b5dfa1 should be 4259dc695da62b7737cc9b633260cd44bb8d3fca, target_update=20A5343j}}}}}

Edit:
I guess it is this: csr-active-config=67080000
Using OpenCore the scripts provided by Barry could not change the NVRAM, new run right now.

No, the same problem after 25 minutes it stops in stage 2 showing the error message from the photo below and producing an error log like this.

 

[Larsvonhier]

Any hint from "senior patchers" here why the micropatcher does not produce a bootable result for a MP3,1?
I tested recent versions with beta 3 and beta 4 and the result is always that some time into booting, the kernel crashes with a dump (verbose) that reminded me of the telemetry issue (but way before login). I also removed the telemetry plugin, so that is not the cause.
What has to be done in addition or perhaps left out to get it running to the installer menu?

edit:
Also, when moving a perfectly working BS beta 4 install over to the MP3,1, it seems to crash at a very similar point with that verbose dump as well.

 

[MacHacJac]

once The drive is formatted and ready do you have to reboot from the usb and do you need to see the boot screen ie install original or flashed card? I still have my gt card I just hate the whole switching out gpu thing

Unfortunately, you will have to boot into the usb. There really isn't much of a workaround.