Just set your startup disk to the APFS volume using System Preferences, and it should stop showing that.
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
Hybrid Mode v1.3 is tested and released. Find it here. We've addressed most of the issues reported in the repo...Thanks to all of you for doing so. As always, read instructions and notes carefully here. This may not be for you.
You must be on 10.14.1 18B75 - backwards compatibility or forward betas are not supported.
File issues and problems in the repo if you can (just the way I prefer to operate - no offense to this site...)
Some highlights of the additional fixes (mostly CoreUI):
1. Search bar pull downs in apps like Safari and iMessage are back to vibrant in Light:
2. Brightness, Sound and other HUDs are "vibrant" in Light and Dark
3. Sidebar Search element blends correctly with the background
4. While "Inactive" Sidebar selections now blend in correctly
You must be on 10.14.1 18B75 - backwards compatibility or forward betas are not supported.
File issues and problems in the repo if you can (just the way I prefer to operate - no offense to this site...)
Some highlights of the additional fixes (mostly CoreUI):
1. Search bar pull downs in apps like Safari and iMessage are back to vibrant in Light:
2. Brightness, Sound and other HUDs are "vibrant" in Light and Dark
3. Sidebar Search element blends correctly with the background
4. While "Inactive" Sidebar selections now blend in correctly
Before I try this on my MBP5,3 with the latest 10.14.2 beta (18C38b),
will there be any adverse effect? Thanks @pkouame for this update.
Last edited:
Quite possibly and HIGHLY UNRECOMMENDED. Only the latest official releases are supported.
There is a very slim possibility CoreUI and HIToolbox 18C38b are actually identical to their 18B75 counterparts, but I wouldn't bank on it without further analysis. The combination may boot and even work delightfully at first blush, but you will get bitten badly if newer 18C38B frameworks depend on non-existent or altered functionality. I've said this before and can't overemphasize how risky that is. I never play like that in my testbed. Unfortunately we don't have the bandwidth to keep up with fast and furious betas. Not the way this issue is being currently patched. Official releases are all we can handle. So do so at your own risk. You have been warned.
v2.0 (no release date yet) will focus on scripted installation and in-place patching (when reliably possible) as well as less invasive mechanisms under research and development. Stay tuned.
I went ahead and installed the 1.3 version on my 10.14.2 beta 2 MBP5,3. Seems to be working so far. This is one of my sandboxes thus the beta version installed and can afford it to go sideways. Therefore I volunteer as your "guinea pig" and test for future versions. I will also let you know if issues will come up on 1.3. Thanks again for making it available and the warning.
EDIT: And to heed your warning regarding issues that may exist on the next beta versions (your comment on newer frameworks), I will turn it back to v1.2 before upgrading.
Last edited:
No problem my friend. This is all about giving us some choices while understanding all risks and trade-offs.
The good news is CoreUI (where a good portion of these fixes reside) are Data patches that can be very reliably dynamically patched. I have an in-place hex-string patcher that accomplishes this already while verifying and guaranteeing compatibility. So "keeping up with the betas" will not be an issue with v2.0. At least for CoreUI.
The menubar and its transparent menus are code patches, hence more complex. I have an internal version that restores full transparency to the Light Mode menus themselves, but the "bar" itself still glitches so I won't release it yet.
Thanks for volunteering. In fact PM me if you would like to take part in the private repo where the sausage is made (and interesting focused discussions) are on-going. Time is the limiting factor here so all help is appreciated...
From what I understand, you don't have to do an upgrade from the usb stick or reinstall for that matter. You do need to make a new installer though, because the latest version of the patcher has support for 10.14.1. After that just update OTA and then boot into new install drive and apply the post install patches.
For the Brightness background, shouldn't it be switched? Weird how in light mode its a darker picture and in dark its a lighter picture. Is this off-the-rocker Apple's doing or chosen by you? Regardless, thank you for the continuous updates and work you put into this. I can use light mode again!
If you fixed the sub-menus and the HUDs elements vibrancies, then I believe you are really close to fix the top-menu. And if you do that I guess your method could be valid for the next 10.15 when it will.
I reported that when trying to update to 10.14.1 my monitor switched off when the boot reached the bit where it switched to graphics mode.
I can report that moving to HDMI from the VGA connection solves this.
Strange as VGA has worked fine for previous versions up to High Sierra and the Mojave Betas.
I can report that moving to HDMI from the VGA connection solves this.
Strange as VGA has worked fine for previous versions up to High Sierra and the Mojave Betas.
just an GOOD NEWS update for everyone, hopefully this can help someone else out there.
I was trying to update my MBP 8,1 (Sandy Bridge i5 Early 2011) from 10.14 to 10.14.1 with no success using System Preferences OTA OR manually downloading the update from Apple's website and patching it to work through Terminal and BBEdit. And yes I tried booting from USB and installing the patch before the reboot for both methods.
What ended up working for me was making a new bootable drive using the dosdude1 Mojave patcher which included 10.14.1 . I just ran the MacOS installer as normal (you wont lose personal data) then rebooted back into the USB, ran the patch, cleared cache and I booted up see 10.14.1! no errors, freezes or anything. like I said I hope this helps someone else out there having a similar issue running a similar setup (i5/i7 etc.)
I was trying to update my MBP 8,1 (Sandy Bridge i5 Early 2011) from 10.14 to 10.14.1 with no success using System Preferences OTA OR manually downloading the update from Apple's website and patching it to work through Terminal and BBEdit. And yes I tried booting from USB and installing the patch before the reboot for both methods.
What ended up working for me was making a new bootable drive using the dosdude1 Mojave patcher which included 10.14.1 . I just ran the MacOS installer as normal (you wont lose personal data) then rebooted back into the USB, ran the patch, cleared cache and I booted up see 10.14.1! no errors, freezes or anything. like I said I hope this helps someone else out there having a similar issue running a similar setup (i5/i7 etc.)
Thank you,
In fact, I used a different way to do that :
- Mount the EFI Boot volume
- Delete "/BOOT/BOOTX64.EFI", startup.nsh, and apfs.efi
And everything is back in order.
Correct ?
PJN
Hey guys, I just installed 10.14.1 via a patched flash drive on my MacBook 5,2 (installed it over my 10.14.0 installation). However after the installation and reapplying the patches my MacBook doesn't start anymore (keeps kernel panicking on every start). It loads until the screen turns black (normally after the screen turns from white to black a white apple logo should appear – but in my case that never happens). It worked totally fine under 10.14.0. I'm clueless what it could, maybe you guys could shed some light on this issue? I used the latest patcher and the Mac is using only HFS+ file system. I'm just glad I backed the system up with CCC before so if it eventuell wouldn't work, I can always revert.
Thanks for any suggestion!
EDIT: I've tried it again - "Force Cache Rebuild" did the trick.
iSight not working anymore (had working kexts before, don't seem to work on 10.14.1)
Does anybody have working iSight kexts?
EDIT 2: After some reasearch I found that these work fine: https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-136#post-26266085
Thanks for any suggestion!
EDIT: I've tried it again - "Force Cache Rebuild" did the trick.
iSight not working anymore (had working kexts before, don't seem to work on 10.14.1)
Does anybody have working iSight kexts?
EDIT 2: After some reasearch I found that these work fine: https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-136#post-26266085
Last edited:
Please see my post #10354.
Apart from that everything seems to be very fast. It took me around 25-30 min to restore from time machine backup(external 10 year old WD Passport HDD) 40 GB itunes music library. I currently have Snow Leopard, Mountain Lion, Yosemite, El Capitan, High Sierra installed on my system as well.
Jumping the timeline while watching 1080 hd video file is the only thing so far that Mojave currently fails at in comparison to Yosemite, El Capitan and High Sierra(those systems allow very smooth, instant jump to any point on a timeline).
Maybe
Have a look here for patching and hardware requirements:
https://github.com/dokterdok/Continuity-Activation-Tool
Worked for me with MBP 6,2 (10.14.1) and an additional BT dongle...
This has never worked for me on the MB7,1. It always had errors in the system diagnostics and broke the finder column view on every first installation.Maybe
Have a look here for patching and hardware requirements:
https://github.com/dokterdok/Continuity-Activation-Tool
Worked for me with MBP 6,2 (10.14.1) and an additional BT dongle...
It is supposed to be like that and it actually makes sense when it comes to visibility (light symbols in darkmode, dark symbols in lightmode)
On a supported machine with darkmode (unfortunately on a white background):
[doublepost=1541854557][/doublepost]
Can I ask whats the difference, or what's the nicer loading bar? How does it look compared to the 'normal' one?
Hello! I use Mojave on my MBA mid 2011 since first betas of dosdudes tool. I have a problem with every update. Description on tools's website states that updates should auto install with "software update" patch installed. Its installed by default to my machine but after every update I reinstall with post installation utility and force rebuild cache. With recent update autoupdate failed and system were unable to boot and doing patch update didn't worked. I had to reinstall 10.14.
Can you clarify if MBA 2011 is compatible with patched 10.14.1 and if so how should I upgrade to avoid bricking my machine? Should I download and make new USB stick every time. Or autoupdates works for you and patches installed automatically.
P.S. I think update process can be described better in manual
Can you clarify if MBA 2011 is compatible with patched 10.14.1 and if so how should I upgrade to avoid bricking my machine? Should I download and make new USB stick every time. Or autoupdates works for you and patches installed automatically.
P.S. I think update process can be described better in manual
It's just for diagnostic putting "-v" after the boot-args or into com.apple.Boot.plist Kernel Flags, and it is equivalent to press CMD+V after the power-on chime, with "-v" boot will be forced in verbose lines mode, so without the nice Apple logo with loading bar, that is identical to the normal one of course.
This is amazing work! These graphics glitches were exactly the thing that kept me from upgrading to Mojave on my MacBookPro5,5 (from HS). I think I will, however, wait for your 2.0. Are you planning on having it included in dosdude1's patcher application? Or in his updater application?
The menubar sub-menus (and cascading ones) have a specific blur rendering method/function in HIToolbox, hence why it's easier to muck with. Forcing it to use Dark Mode vibrant rendering delivers some decent results without too many system wide side-effects or having to re-write too much code (which is always a concern in choosing the right and safest way to alter these critical frameworks). Still very promising.
One would think the bar itself should be relatively straight forward to spoof at least in the same manner, but Apple's implementation is extremely convoluted with dependencies in both SkyLight and CoreGraphics. For example: the system menus on the left are rendered one way while the "widget" menus on the right another (with a different renderer) You get some very odd combination of effects.
As far as 10.15, I'm pretty sure Apple will never fix these glitches so these approaches may become even more relevant. As long as they continue shipping "deprecated" OpenGL and OpenCL frameworks of course...
[doublepost=1541870764][/doublepost]
Now that we've probably reached the limits of what can be done (safely and reliably) with this kind of approach, ease of installation will be a focus for 2.0. Hopefully you won't have to wait too much longer...
Integrating with the official patcher is always a possibility. Keeping this on a separate track while it becomes more stable is not a bad short term call. Stay tuned.
while it was not corrected your hybrid mode, I had preferred to use flat mode, now in version 1.3 it is much more interesting and I migrated to it.
Great job, needing tests, you know where to find me!
Thank you!
PS: if I find any inconsistency (I believe this is difficult now), I will report it as I have already done in some cases.
However it remains still a mistery why after introducing the dark mode as a new Mojave feature this doesn't glitch with OpenGL instead the old consolidated light mode does. I mean they changed the API calls only for the light mode. Anyway continue to break it sooner or later you will.