all return normal thank
Ok I’ll check Mac with asf tomorrow
what is the good version for 4,1>5,1?
Actually I have 3s132 and I don’t remember if was for 4,1 or 5,1
thank you
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Ok I’ll check Mac with asf tomorrow
what is the good version for 4,1>5,1?
Actually I have 3s132 and I don’t remember if was for 4,1 or 5,1
thank you
For MP4,1>5,1 you have to use the MP5,1 version, 3S149. Btw, this is totally off-topic, if you need to further discuss it, please open a dedicated thread.
I tried your suggestion to spoof the MacBook mid 2010 as MacBookPro9,2 through OpenCore, it booted but I was unable to use any usb input devices (internal keyboard, trackpad, internal bluetooth, usb mouse, and so on), instead I tried to spoof as the next model MacBookPro11,1 (the retina one also "Haswell") and everything worked as my previous iMac14,2 spoofing test.
Probably for MacBookPro9,2 spoofing I needed to rebuild a new prelinkedkernel.
I add that in config.plist I don't used any target machine Serial number, instead I left empty and the spoofed machine inherits mine, probably that's why in "about this Mac" my machine is still shown, however even typing from terminal:
ioreg -l | grep "board-id" | awk '{print $4}'I get this output: Mac-189A3D4F975D5FFC
While the default MacBook7,1 is: Mac-F22C89C8
So the supported machine spoofing while keeping my original serial number worked correctly.
edit:
I attempted also a funny experiment, spoofing MacBook7,1 as a Catalina supported Macmini7,1 late 2014 (Haswell not Ivy Bridge spoofing a Macmini6,1 same situation usb input devices unresponsive), even if a laptop LCD uses the LVDS port, it works without issues.
current spoofed board-id output: Mac-35C5E08120C7EEAF
After a simple reboot, without any PRAM reset, just holding alt-option key, picking an OSX, I get this again: Mac-F22C89C8
OpenCore spoofing MacBook7,1 c2d penryn as a Broadwell MacBookAir7,1 (the 11" inch early 2015 version) also worked with a spoofed board-id output: Mac-9F18E312C5C2BF0B
OpenCore spoofing MacBook7,1 c2d penryn as a KabyLake MacBook10,1 (the retina 12" inch version) also worked with a spoofed board-id output: Mac-EE2EBD4B90B839A8
OpenCore spoofing MacBook7,1 c2d penryn as a CoffeeLake iMac19,1 (the retina 5k ddr4 ram 2019 version) also worked with a spoofed board-id output: Mac-AA95B1DDAB278B95
Good work OpenCore.
Attachments
Last edited:
You may study the BootROM thread, then you should have some idea about how and why it can happen.
MP5,1: BootROM thread | 144.0.0.0.0
For MacPro5,1 BootROM upgrades, please read the first post of the thread below to know how to do the firmware upgrade: https://forums.macrumors.com/threads/mp5-1-what-you-have-to-do-to-upgrade-to-mojave-bootrom-upgrade-instructions-thread.2142418/ For MP4,1 to MP5,1 cross firmware flashing...
forums.macrumors.com
@tsialex this is your post from another thread, as you can verify when I spoofed my MacBook7,1 as different supported Catalina machines (I marked blue in your BootROM table), the OpenCore 0.5.2 latest version that I used spoofed automatically the latest machine firmware, so when a new OpenCore version will be released, spoof automatically the latest BootROM right ?
I have another question to @cdf and to others that used OpenCore, how can I avoid the opencore*.txt log files in the EFI partition, because they are created at every OpenCore boot, and each one of them is sized 262 Kb even if empty (example if in a day I run OpenCore 10 times they become 2,6 MB), so they are too big in my case for a small EFI 200 Mb partition, is there an OpenCore setting in config.plist to don't save the logs, or using one only txt file ?
Last edited:
In automatic mode, yes (provided that the OC database is up to date).
Make sure that Debug Properties, Target does not have bit 6 set.
No, this depends on a list of BootROMs versions saved into OpenCore. This will be always behind, since you need to update the OpenCore release to get the new table of saved EFI versions. It's a nice idea, but on paper only because Apple is frequently updating BootROMs since High Sierra.
One stupid trick works, for example, if you are spoofing MP6,1 that currently have BootROM 133.0.0.0.0 you can tell OpenCore to spoof 134.0.0.0.0. This way you never even get the Firmware.scap saved. Obviously this demands manual configuration of several SMBIOS parameters.
Thanks that worked, probably before I added a 6* digit during my early experiments because I needed the log since couldn't boot or bootlooping from OpenCore, without the "6", no more opencore*.txt in the EFI partition.
[automerge]1573394568[/automerge]
If I run into an OTA Catalina update, without spoofing the latest firmware, if before the OTA reboot, I delete the /EFI/APPLE/EXTENSIONS/Firmware.scap , this should also avoid an unwanted BootROM update ?
Last edited:
According to the manual, you may want to set Debug Properties, DisableWatchDog to true.
In my experience you need debug build not release build.
Also 200ish KB is tiny. The EFI partition should be about 200MB
Also 200ish KB is tiny. The EFI partition should be about 200MB
If I want to do this what parts of the code do I supplement with my system information, do I put my system serial number and MLB serial number?
No. You generate serial numbers matching the motherboard. In opencore configurator and in Clover configurator there is a generate button which you have to press several times (for both serial numbers). Then there is another option check coverage, which takes you to an Apple serial number check. There you SHOULLD NOT see valid configuration as that means you picked an existing machine. But the same serial number should validate in the everymac database as a valid serial number.
This guide is amazing! but I feel OP should update post #1 it with the warnings and workarounds regarding the SMC control and the findings regarding the DisplayPorts and including the guide @h9826790 did regarding AMD hardware acceleration. Scrolling a lot of posts here to find the right way to update is getting confusing with that many workarounds, hahah
In addition to this, basically what I am hoping to achieve correctly is:
1. Having a working Catalina drive on my upgraded 4,1>5,1 cMP. And my current Mojave one to boot in case I have to do a NVRAM reset and OpenCore is disabled.
2. enabled HEVC support to use my iPad Pro for Sidecar with no issue + AirDisplay on my Apple TV 4k.
3. Making sure nothing goes wrong in the future for system updates and Catalina does not, for some reason, attempt to push a firmware update (a warning that should be included here)
1. Having a working Catalina drive on my upgraded 4,1>5,1 cMP. And my current Mojave one to boot in case I have to do a NVRAM reset and OpenCore is disabled.
2. enabled HEVC support to use my iPad Pro for Sidecar with no issue + AirDisplay on my Apple TV 4k.
3. Making sure nothing goes wrong in the future for system updates and Catalina does not, for some reason, attempt to push a firmware update (a warning that should be included here)
By sticking to the guide, you will be able to achieve 1 and 3. The configuration is very minimal, and there should be no danger of unwanted firmware updates. As for 2, how to properly achieve hardware acceleration is currently under study.
We are just starting to get all pieces of the decode puzzle while for encoding we still have to find what Apple really requires. The current solution is blunt and have unintended consequences, for now it's useful to debug/investigate.
Sidecar depends not only on HEVC encoding, but AirPort Extreme that supports 802.11ac, iCloud, board-ids validation and more. It's a long way…
Thankfully I already have installed a Macbook Air Bluetooth4.1/802.11ac card. But as you say still kinda a long way, but not impossible at least
Yes. I never tried to test if EFI flasher really tries to write the firmware.scap to the SPI when spoofing, but with your Mac with NVIDIA chipset that is very susceptible to bricking it's better to not risk.
Running Catalina with no issue! But I had to erase one of my disks because I see 120gb are not enough for Catalina to be loaded on.
Does anyone have the thread about installing Windows 10 on legacy mode? I remember installing bootcamp on UEFI on cMP can lead to corrupt the bootrom
Does anyone have the thread about installing Windows 10 on legacy mode? I remember installing bootcamp on UEFI on cMP can lead to corrupt the bootrom