Would love to see examples of these binary blobs and impacted nvram areas under basic use of OpenCore, ie. VMM flag to boot/update Catalina, as I could not find any differences in my binwalk dumps (I know, binwalk isn't the right tool).
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 Obsolete, Use OpenCore instead | What you need to do to make Catalina work with MacPro5,1
- Thread starter tsialex
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
- Status
Would love to see examples of these binary blobs and impacted nvram areas under basic use of OpenCore, ie. VMM flag to boot/update Catalina, as I could not find any differences in my binwalk dumps (I know, binwalk isn't the right tool).
Let’s not get this misconstrued. If I remember correctly, the edit to post #673 was changing “OpenCore spoofing” to “OpenCore VMM flag spoofing.” Therefore, the concern that has been raised appears to be from OpenCore configurations other than VMM flag spoofing. This is my understanding. Please correct me if I have misunderstood.
I'm still investigating, it's a complex procedure to track everything. Since the NVRAM areas where the binary blobs are have private/personal data (like iCloud credentials), I can't even post a screenshot. I'll need to create a test iCloud account with bogus data to show this down the road.
Binwalk is a toolkit to facilitate/automate searches, it only shows something if you previously inserted the signature of what you want to research. It will never be useful for this type of primary research.
Yes, exactly. VMM flag spoofing seems to be safe and nothing is written to the NVRAM, besides the bless changes.
Binary blobs appear inside the private stream/stores of the NVRAM after spoofing iMacPro1,1/MP7,1. We don't know why this is happening or what is doing it.
Last edited:
is this perhaps just macOS doing the writes expecting those areas to be writable for a real 1,1/7,1?
Is there any evidence this is detrimental to the functionality of the machine?
can you emulate NVRAM like in the hack scene and see more clearly who/what/why more safely vs the native NVRAM implementation?
furthermore if we go emulated NVRAM, could that be a solution all on its own to bypass the concerns here?
Also using --nextonly in the bless command is very useful to avoid wasting a lot of time testing things so that only your next boot attempts OC and then it reverts to whatever you did previously (refind in my case)
I don't think so, a T2 Mac have a totally different way to access the SPI flash.
Clover does the same and bricked various MP5,1, @startergo had one bricked with the same type of binary blobs.
I don't think this is the way to go, the less we deviate from the standard MP5,1, the better.
VMM spoofing for updates and finding/implementing what is needed to overcome the soft block Apple implemented for hardware encoding is the way to go, not full blown hackintoshfy the MP5,1.
We already know that HEVC, and probably what depends on it like Sidecar, works when spoofing a iMacPro1,1/MP7,1, now we need to find exactly what is needed to activate without the blunt way that is spoofing. We already have a Mac, we need a fine tuned and intelligent way to accomplish this.
Last edited:
For now I need controlled dumps, starting from a BootROM image with the NVRAM filled with just the 3rd and 4th streams, then after one boot, after iCloud configuration, after some reboots and then after OpenCore iMacPro1,1/MP7,1 spoofing. @h9826790 and I already did it for our Macs and now I'm tracking and evaluating what is a valid binary blob (like the SPD dumps for each DIMM and some other things) from what OpenCore is doing. I don't have much free time nowadays, but I'm progressing a little everyday.
Last edited:
Holy crap 28 pages, I just firmware upgraded a 4,1 to 5,1 and I have it running High sierra, ordering a metal compatible GPU (MSI Gaming Radeon RX 560 128-bit 4GB GDRR5) via https://support.apple.com/en-us/HT208898 to get it updated to mojave. Without reading through 28 pages, do you think mojave+ will be possible on the MacPro 5,1? Or will it be a complete faff
Mojave is native in Mac Pro 5.1 .If you mean Catalina, runs like a charm in 5.1, with the help of @dosdude1 and more others.
Oh yeah sorry Catalina! tongue tied!
Is there a how-to buried somewhere in these 28 pages?
macOS 10.15 Catalina on Unsupported Macs
How to update Catalina Machine Support Video Card Support Pre-Metal AMD video cards (Radeon HD 6xxx series and older without acceleration, Radeon HD 4xxx series and older with acceleration.) Pre-Metal Nvidia video cards (GeForce 5xx series and older without acceleration, GeForce 3xx...
forums.macrumors.com
Just a few more pages.
Don´t get mad . Just follow instructions on page 1
[automerge]1573137272[/automerge]
For Catalina, you mean?
macOS 10.15 Catalina on Unsupported Macs
How to update Catalina Machine Support Video Card Support Pre-Metal AMD video cards (Radeon HD 6xxx series and older without acceleration, Radeon HD 4xxx series and older with acceleration.) Pre-Metal Nvidia video cards (GeForce 5xx series and older without acceleration, GeForce 3xx...
Just a few more pages.
Don´t get mad . Just follow instructions on page 1
[automerge]1573137272[/automerge]
For Catalina, you mean?
Yes, for Catalina (of course
)
Apple requires a supported Mac to do point updates (10.15.0 to 10.15.1, for example). The only workaround Apple provided is to use a VM, since when Apple tests if your Mac is supported, the code checks if it's running inside a VM and then permit the update. OpenCore VMM flag spoofing makes Catalina think that is running inside a VM.Yes, for Catalina (of course
You can't update a Catalina install with MP5,1 without a VM or VMM flag spoofing, dosdude1 way is to install over every time an update is released.
These are the four ways to update Catalina with a MP5,1:
- connect your Catalina disk to a supported Mac,
- use a raw disk VM to update
- spoof the VMM flag with OpenCore
- install dosdude1 new version over
If you have the file from Mojave I am currently on Catalina and it would be awesome if you could send it my way! The only relevant kexts I can find using Google seems to be this one from this GitHub repo: https://github.com/LukaJankovic/10.12-zenbook-ux303u/tree/master/IO80211Family.kext/Contents/PlugIns
Sorry, I can't send you Apple proprietary files. Extract it from the Mojave installer, if you need BCM94322MC support or from Sierra if you need BCM94321MC.
/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4331.kext
Thank you so much for your reply!
Do you know where or have an idea of where this file could be on the Mojave installer?
I just went and scoured the installer.
I mean, seriously? @tsialex was even nice enough to tell you the exact location of the file in two different OS versions
There is really no issue with asking!
He can say that he doesn't want to reply or just not reply at all!
Please don't ask more. There's all info you ever need with this screenshot.
BCM94321MC you will get from the most recent Sierra Security Update.
BCM94322MC you will get from High Sierra or Mojave current Security Update.
Just make an USB installer, and install over the actual system.Yes, for Catalina (of course
- Status