Sorry - must have missed that post. What do you mean by "weird" tint? Is it the dark grey color?
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.
macOS 10.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
post a pic of the weird tint
[doublepost=1534737960][/doublepost]DP8 Tomorrow ?????
I don't know the details, but it's a software (rather than Boot ROM) modification from the High Sierra thread. I haven't looked into APFS much because my only computer supports it, but it seems like a safer alternative to the ROM chip patching. Why isn't this an option on Mojave?
When DP8 comes out tomorrow, I need people to do some testing. If you patched your Boot ROM on an unsupported EFI chip and converted to APFS, attempt to use the native software updater. Please reply and record your results, if it works or not. With my expierence, updating using the native updater on a patched EFI chip and corrupts the OS. I attempted it twice with DP7, and same result both times. My theory is that updates only show up in System Preferences on APFS, but the updates only work on supported, nonpatched, native APFS booting EFI chips. However, this is only based off of my experience, since most people had already updated to DP7 when the APFS patcher came out. It has been recorded that the updates are successful on NATIVE APFS booting EFI chips, so I am only asking for those who patched their UNSUPPORTED APFS chips to test the software updater. I will be testing tomorrow as well on a small partition with APFS DP7. Thank you!
I also installed a software based APFS solution early on during the HS "unsupported" saga last year.
It worked well, but was a little awkward (slow and ugly boot messages etc.)
I think dude's solution is cleaner. But I agree, the rom flashing option may not be for everyone. I cringe when someone bricks...
[doublepost=1534741447][/doublepost]
I was the first to use the new rom patcher (2.0) when it came out, and I exercised the entire (preferences) system update cycle as a test a little while back. Smoothly migrating from dp6 to dp7. It was the main reason I migrated from HFS+ to APFS. My system is an unsupported macpro 3.1. No "native" support for APFS out of the box without flashing my chip.
It may be late at night ... so I'm not sure I understand your question at all. Either the rom patcher recognizes your chip or it doesn't and proposes plausible alternatives. If your chip is not on the list, you're sol and only the "man" can address that (contact him). Or you can roll your own utility...
[doublepost=1534742131][/doublepost]@dosdude1 Your latest post-install runs legacyGPUPatch.sh on my macbook pro 5.3 (if I read your macmodels.plist correctly). The shell script tries to copy an NVDAStartup.kext which doesn't exist in the legacynvidia folder. Am I missing something?
I used the APFS Rom Patcher V1 just before I installed Mojave developers beta 2 and I have successfully installed update from the software update since no issues since on my iMac 9,1
@flygbuss I investigated the Quartz Composer screensavers thing a bit more. It seems like no QTZ screensavers run on Mojave. Even ones copied from High Sierra's /System/Library/Screen Savers/. The old ones that used to run on Quartz, like Arabesque and Word of the Day have been ported to .saver files like the rest.
I'm not a developer so I don't have access to the Mojave release notes. Not sure if this is a bug or an intentional removal/deprecation but this is an entirely different issue you should bring up with Apple.
I'm not a developer so I don't have access to the Mojave release notes. Not sure if this is a bug or an intentional removal/deprecation but this is an entirely different issue you should bring up with Apple.
You've already asked, and I already answered this question back in post #5516, take another look, only this time try reading it and following the link.
There was a APFS Patch at one time for The High Sierra Patcher which was a custom EFI boot loader for High Sierra but since then its been greyed out so maybe it might not work for Mojave. I heard Mojave uses a dynamic efi boot loader
No, I removed that kext because it wasn't necessary. I just hadn't updated the script to reflect that.I also installed a software based APFS solution early on during the HS "unsupported" saga last year.
It worked well, but was a little awkward (slow and ugly boot messages etc.)
I think dude's solution is cleaner. But I agree, the rom flashing option may not be for everyone. I cringe when someone bricks...
[doublepost=1534741447][/doublepost]
I was the first to use the new rom patcher (2.0) when it came out, and I exercised the entire (preferences) system update cycle as a test a little while back. Smoothly migrating from dp6 to dp7. It was the main reason I migrated from HFS+ to APFS. My system is an unsupported macpro 3.1. No "native" support for APFS out of the box without flashing my chip.
It may be late at night ... so I'm not sure I understand your question at all. Either the rom patcher recognizes your chip or it doesn't and proposes plausible alternatives. If your chip is not on the list, you're sol and only the "man" can address that (contact him). Or you can roll your own utility...
[doublepost=1534742131][/doublepost]@dosdude1 Your latest post-install runs legacyGPUPatch.sh on my macbook pro 5.3 (if I read your macmodels.plist correctly). The shell script tries to copy an NVDAStartup.kext which doesn't exist in the legacynvidia folder. Am I missing something?
@ASentientBot and @flygbuss - Sure looks like it was deprecated. Much like OpenGL and OpenCL. The old CoreGraphics (Quartz, Quartz2D, QuartExtreme etc.) was leveraging OpenGL heavily. Apple is really clamping down on all OpenGL based technologies.
That was a flawless method as the APFS Boot Rom Patcher can't find my EEPROM and I am a bit nervous as my bottom version is different from what the original bootrom is supposed to be. I either have the late 2008 MacBook or the MacBook Pro 5,2 bootrom version
[doublepost=1534744659][/doublepost]
Makes you wonder what else will be clamped down on by GM release
I also installed a software based APFS solution early on during the HS "unsupported" saga last year.
It worked well, but was a little awkward (slow and ugly boot messages etc.)
I think dude's solution is cleaner. But I agree, the rom flashing option may not be for everyone. I cringe when someone bricks...
[doublepost=1534741447][/doublepost]
I was the first to use the new rom patcher (2.0) when it came out, and I exercised the entire (preferences) system update cycle as a test a little while back. Smoothly migrating from dp6 to dp7. It was the main reason I migrated from HFS+ to APFS. My system is an unsupported macpro 3.1. No "native" support for APFS out of the box without flashing my chip.
It may be late at night ... so I'm not sure I understand your question at all. Either the rom patcher recognizes your chip or it doesn't and proposes plausible alternatives. If your chip is not on the list, you're sol and only the "man" can address that (contact him). Or you can roll your own utility...
[doublepost=1534742131][/doublepost]@dosdude1 Your latest post-install runs legacyGPUPatch.sh on my macbook pro 5.3 (if I read your macmodels.plist correctly). The shell script tries to copy an NVDAStartup.kext which doesn't exist in the legacynvidia folder. Am I missing something?
The boot rom patched ran no issues, it’s when I used the software update pane in system preferences after converting to apfs that the updater did not work (DP6>DP7), tried two times, ended up corrupting the OS and eventually the disk itself. So I was just trying to see if it will work from DP7 to DP8.
Well, I have both an APFS DP7 and APFS DP6 ready for DP8 (hopefully this week) So I plan on testing again via system update. I (and many) will report their results so stay tuned ...
[doublepost=1534745528][/doublepost]
Yes, the much touted "group" FaceTime was dropped suddenly (a "later" release) - Apple's developers are (apparently) still on HFS+ and fixing APFS bugs - we know there are issues with Dark Mode (our old machines are just exacerbating them) - the list goes on... Cupertino is in a world of hurt. My inside track tells me they're scrambling...Makes you wonder what else will be clamped down on by GM release
Hope they are burning the midnight oil September is coming quickly
Hmm, maybe it’s not the updater after all. I created a partition just to test APFS on Mojave. Created it, converted to APFS, installed DP7, still won’t boot. Is there an issue with my EFI chip or the patcher? It seems any install on an APFS won’t boot on my machine, and it doesn’t create the recovery partition. Machine issue or just the patcher?
EDIT: There is a new booting option while holding Option at start, called “EFI Boot”. What would happen if I booted onto this?
EDIT: There is a new booting option while holding Option at start, called “EFI Boot”. What would happen if I booted onto this?
Last edited:
They've diverted most of their engineering staff to iPhone, iPad, iMusic and iOS (where the money is). Macs and macOS are feeling the pain. I see a lot of buggy software and Craig Federighi himself admitted those problems were systemic. I for one hope they cycle through as many betas as is necessary to make this solid. Rushing just to make an artificial quarterly earnings report look good just doesn't make for good hard/software. But then again...that's why I'm not running a Trillion dollar companyHope they are burning the midnight oil September is coming quickly
Not ture!
Mid 2009 MBP and APFS! Works fine here.
BUT: my MBP says my Bios supports only Sata II (1.5GB) but there is a Update from Apple to use Sata III
MBP 5.4 - can i use this firmware?
https://support.apple.com/kb/DL853?locale=de_DE&viewlocale=de_DE
I certainly agree with you and being I was a big Windows fan since Windows 3.11 and now they are not making Windows the flagship of their company I looked for greener pastures< If you want my install after DP8 is installed I will save it for you to see if there are more changes or improvements. Wishing you a good night time for some shut eye
[doublepost=1534747815][/doublepost]
[doublepost=1534747815][/doublepost]
There you go
You DO know there were quite a few of these "boot" loader hacks back in the day. Not to mention rolling point versions of each...And yes I can read and follow links quite well - thank you. Good luck.
@jackluke just have an idea... About transparency issue. Isn't the problem related only with Finder? All works well with light mode, except Finder. Dock bar works well, side bar too. Preferences panel too. The only problem I see is on Finder...maybe some link between Finder and whatever it makes the transparency that is missing?
I'm sorry to say it but this post feels both confusing and confused in many ways.
As I remember it (correct me if wrong), prior to dosdude1 releasing version 1.0 of the boot ROM patch adding native APFS support to unsupported Macs, we had a choice of staying on HFS+ and running a dosdude1 software patch to enable installation of High Sierra. When HS started forcing conversion to APFS for SSD installations, dosdude1 implemented a hack (in the hidden EFI partition?) that enabled support in software for APFS and High Sierra installation. This hack had the scrolling white-on-black text rather like the single user boot screen. Subsequently, he implemented a modification that hid this screen and gave us the usual gray Apple boot screen.
Later in High Sierra, dosdude1 released his clever boot ROM patch that gives native support for APFS to most unsupported Macs, meaning that software APFS hacks in EFI are no longer needed if you have patched the boot ROM to add native APFS support. If you have an install that has been using the software patch for APFS support, and are about to implement the APFS boot ROM patch, I think you'd do better to make a disk backup and start over with a completely fresh OS using the Mojave USB patcher method after patching the boot ROM.
This is where we stand today; there was a slight glitch in the ROM ID function in version 1.0 of the patch but that has been largely fixed in version 2.0.
I have been using the version 1.0 APFS boot ROM patch in an MP 3.1 with GTX680 and Wi-Fi/BT module from an iMac 2014 without problems. It has updated normally to the point where the recovery disk part of the installer fails and I just restart to complete the install. Occasionally, if I am in any doubt about the install or if the install seems glitchy, I run the USB post-install and it has come good.
More recently, I've also been running with the NVMe boot ROM patch supporting HighPoint 7101-1 NVMe storage, and Mojave has updated fine too with this arrangement. When (if beta 8) arrives tomorrow, I'll run it and see what happens but I'm not expecting any serious problems (famous last words).
As I remember it (correct me if wrong), prior to dosdude1 releasing version 1.0 of the boot ROM patch adding native APFS support to unsupported Macs, we had a choice of staying on HFS+ and running a dosdude1 software patch to enable installation of High Sierra. When HS started forcing conversion to APFS for SSD installations, dosdude1 implemented a hack (in the hidden EFI partition?) that enabled support in software for APFS and High Sierra installation. This hack had the scrolling white-on-black text rather like the single user boot screen. Subsequently, he implemented a modification that hid this screen and gave us the usual gray Apple boot screen.
Later in High Sierra, dosdude1 released his clever boot ROM patch that gives native support for APFS to most unsupported Macs, meaning that software APFS hacks in EFI are no longer needed if you have patched the boot ROM to add native APFS support. If you have an install that has been using the software patch for APFS support, and are about to implement the APFS boot ROM patch, I think you'd do better to make a disk backup and start over with a completely fresh OS using the Mojave USB patcher method after patching the boot ROM.
This is where we stand today; there was a slight glitch in the ROM ID function in version 1.0 of the patch but that has been largely fixed in version 2.0.
I have been using the version 1.0 APFS boot ROM patch in an MP 3.1 with GTX680 and Wi-Fi/BT module from an iMac 2014 without problems. It has updated normally to the point where the recovery disk part of the installer fails and I just restart to complete the install. Occasionally, if I am in any doubt about the install or if the install seems glitchy, I run the USB post-install and it has come good.
More recently, I've also been running with the NVMe boot ROM patch supporting HighPoint 7101-1 NVMe storage, and Mojave has updated fine too with this arrangement. When (if beta 8) arrives tomorrow, I'll run it and see what happens but I'm not expecting any serious problems (famous last words).
Agree, in "light mode" also the Launchpad, Mission Control, Dashboard, Notification Center and the Applications "comic cloud" transparencies are fine, the fact is that not exactly only Finder is affected, also Safari's Favorites main page, and maybe any other app that lays on finder's windows drawing. As known Finder is the cell in MacOS, so I guess the problem is wider.
edit:
Anyway you're right, apart menu bar, are affected to flat grey only certain Finder zones: context menu, some side panels, so I'd say the issue could be bordered.
Last edited: